WO2022121388A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2022121388A1
WO2022121388A1 PCT/CN2021/116143 CN2021116143W WO2022121388A1 WO 2022121388 A1 WO2022121388 A1 WO 2022121388A1 CN 2021116143 W CN2021116143 W CN 2021116143W WO 2022121388 A1 WO2022121388 A1 WO 2022121388A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
charging
remote terminal
policy
terminal device
Prior art date
Application number
PCT/CN2021/116143
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 WO2022121388A1 publication Critical patent/WO2022121388A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method and device.
  • proximity-based services (ProSe) communication is introduced.
  • the terminal equipment outside the coverage area of the wireless network hereinafter collectively referred to as remote terminal equipment, remote terminal
  • the relay device can communicate with the remote terminal device through the PC5 interface, and communicate with the wireless network through the Uu interface.
  • the remote terminal device accesses the wireless network through the relay device
  • what the user plane function (UPF) network element reports to the charging function (charging function, CHF) network element is still the information of the relay device. Charging information, the CHF network element cannot be charged separately for the remote terminal equipment.
  • Embodiments of the present application provide a communication method and apparatus, so that after a remote terminal device is connected to a wireless network, a network element with a charging function can perform separate charging for the remote terminal device.
  • a communication method may include: the policy control network element receives the first identification of the remote terminal equipment from the network element, and sends the first charging policy of the remote terminal equipment to the session management network element according to the first identification.
  • the remote terminal equipment and relay equipment can be mobile phones, computers, virtual reality terminal equipment, augmented reality terminal equipment, vehicle terminal, etc.; or, the remote terminal equipment can also be terminal equipment in some application fields, such as medical, wireless Terminal equipment in application fields such as human driving, smart grid and smart city.
  • the remote terminal device can access the wireless network through the relay device.
  • the remote terminal device may be located outside the signal coverage area of the network and access the wireless network through a wireless connection with the relay device.
  • the wireless network may be a mobile communication system, such as a cellular network in a 4th, 5th or 6th generation mobile communication system.
  • the policy control network element can obtain the first identifier of the remote terminal device from the session management network element, the policy control network element can The management network element sends the first charging policy of the remote terminal device.
  • the session management network element can configure the first reporting rule of the remote terminal device for the user plane network element according to the first charging policy, so that after the remote terminal device accesses the wireless network through the relay device, the user plane network element can
  • the first reporting rule reports the traffic usage of the remote terminal equipment to the network element with the charging function, so as to realize separate billing of the remote terminal equipment according to the traffic usage.
  • the first charging policy may include one or more of the following: session charging rules, or service charging rules.
  • session charging rules are sessions, such as protocol data units (PDUs)
  • session-dimension charging rules are services, such as video, audio, web browsing and other service-dimension charging rules
  • service charging rules are services, such as video, audio, web browsing and other service-dimension charging rules
  • session management network elements can Select a billing rule with a dimension more suitable for the actual business to achieve more accurate billing.
  • the first charging policy may further include: a status subscription indication.
  • the status subscription indicates the connection status and/or the service flow status for subscribing to the remote terminal device.
  • the policy control network element can grasp the connection status of the remote terminal equipment in real time, and notify the user plane network element through the session management network element.
  • the management network element reports wrong traffic usage, such as over-reporting the traffic usage or under-reporting the traffic usage, which leads to the problem that the session management network element incorrectly bills the remote terminal device, thereby improving the accuracy of billing.
  • the method described in the first aspect may further include: the policy control network element obtains the first charging policy according to the first identifier. It can be understood that since there is a corresponding relationship between the identifier and the policy, the first charging policy can be quickly and conveniently obtained through the first identifier.
  • acquiring the first charging policy by the policy control network element according to the first identifier may include: acquiring the first charging policy from the first device by the policy control network element according to the first identifier.
  • the first device may include: a policy control network element, a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element. It can be understood that, since the first charging policy can be stored in each network element, the reliability of storing the first charging policy can be improved.
  • the method described in the first aspect may further include: the policy control network element sends the first indication information to the second device.
  • the second device may include: a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element.
  • the first indication information is used to indicate that the remote terminal device accesses the wireless network through the relay device.
  • the second device can quickly and conveniently determine the first charging policy suitable for relay access.
  • the first charging policy may include one or more of the following: a first identifier, or a port number allocated by the relay device to the remote terminal device.
  • the first reporting rule configured by the session management network element for the user plane network element may also include the first identifier and/or the port number, so that the user plane network element can accurately report the traffic usage of the remote terminal device.
  • the policy control network element receiving the first identifier of the remote terminal device from the session management network element may include: the policy control network element receiving the first message from the session management network element.
  • the first message carries the first identifier, and the first message may be a session policy association establishment request message or a session policy association modification request message.
  • sending the first identifier by multiplexing the session policy association establishment request message or the session policy association change request message can reduce signaling overhead and improve communication efficiency.
  • the first identifier may include one or more of the following: a contracted permanent identifier SUPI allocated by an operator for a remote terminal device, a general public subscription identifier GPSI, a user hidden identifier SUCI, and the relay device is a remote terminal.
  • the port number assigned by the device, or the identifier assigned by the third-party service provider to the remote terminal device, such as QQ number, WeChat account, etc., and the above identifiers of the remote terminal device have a corresponding relationship.
  • the identification used for charging of the remote terminal equipment can be determined based on the corresponding relationship, so as to realize separate charging for the remote terminal equipment, thereby improving the cost of charging. reliability.
  • the method described in the first aspect may further include: when there is a PDU session whose charging policy matches the first charging policy in the protocol data unit PDU session established by the relay device, the policy control The network element sends the second indication information to the session management network element.
  • the second indication information is used to indicate that the remote terminal device is allowed to use the matched PDU session.
  • the method described in the first aspect may further include: when there is no PDU session matching the charging policy and the first charging policy in the protocol data unit PDU session established by the relay device , the policy control network element sends the third indication information to the session management network element.
  • the third indication information may be used to indicate that the remote terminal device is not allowed to use the established PDU session.
  • the session management network element can create a PDU session whose charging policy matches the first charging policy for the remote terminal device to use according to the third indication information, so as to realize that when the charging policy of the established PDU session does not match, the The remote terminal equipment can be accurately billed separately.
  • the third indication information can also be used to indicate that the remote terminal device is disconnected from the relay device.
  • the session management network element can disconnect the connection between the relay device and the remote terminal device according to the third indication information, stop charging the remote terminal device, and release communication resources, thereby improving communication efficiency.
  • the third indication information may include: first sub-information and second sub-information.
  • the first sub-information is used to indicate that there is no matching PDU session in the established PDU session.
  • the second sub-information may be used to indicate that the remote terminal device is not allowed to use the established PDU session; or, the second sub-information may also be used to indicate that the remote terminal device is disconnected from the relay device.
  • the relay device learns the reason why the remote terminal device is not allowed to use the established PDU session or disconnects the connection according to the first sub-information, it can accurately perform corresponding actions, such as creating a PDU session or disconnecting the connection, according to the second sub-information. Disconnect from the remote terminal equipment, thereby improving the reliability of control.
  • the method described in the first aspect may further include: the policy control network element receives the second charging policy from the application function network element.
  • the policy control network element sends the second charging policy to the session management network element.
  • the billing policy can be dynamically updated, so as to achieve more accurate billing.
  • the policy control network element sends a charging policy update failure message or a charging policy creation failure message to the application function network element, so that the application function The network element no longer sends the second charging policy to the policy control network element, so as to avoid charging errors and waste of resources, thereby improving communication efficiency.
  • the method described in the first aspect may further include: the policy control network element receives fourth indication information from the application function network element.
  • the fourth indication information is used to indicate that the second charging policy is not used for charging the device accessing the wireless network through the relay device.
  • the policy control network element may not send the second charging policy to the session management network element according to the fourth indication information, so as to avoid charging errors and waste of resources.
  • the second charging policy is used for charging the device accessing the wireless network through the relay device, and the method described in the first aspect may further include: the policy controlling the network element to update the first charging policy according to the second charging policy billing policy.
  • the remote terminal device is connected to the relay device, and the first charging policy is in an active state; or, the remote terminal device is disconnected from the relay device, and the first charging policy is in an inactive state.
  • the policy control network element can determine which policies are used and which policies are not used through the state of the first charging policy, so as to schedule resources more flexibly, such as configuring or releasing resources, to improve communication efficiency.
  • the connection between the remote terminal device and the relay device or the service flow is disconnected, the method described in the first aspect may further include: the policy control network element sends a charging notification message to the application function network element.
  • the charging notification message is used to notify the connection of the remote terminal device or the disconnection of the service flow.
  • the application function network element can also learn the connection state or service flow state of the remote terminal device, so as to avoid the application function network element not knowing the connection state or service flow state of the remote terminal device and continue to send data and waste resources, thereby improving communication efficiency.
  • a communication method may include: the session management network element sends the first identification of the remote terminal equipment to the policy control network element, and receives the first charging policy of the remote terminal equipment from the policy control network element, so that according to the first charging policy, Send the first reporting rule to the user plane network element.
  • the remote terminal device is connected to the wireless network through the relay device; the first reporting rule is used for the user plane network element to report the traffic usage of the remote terminal device.
  • the method described in the second aspect may further include: the session management network element sends a charging data request message to the charging function network element, where the charging data request message carries the first identifier.
  • the network element of the charging function can separately charge the remote terminal device according to the first identifier.
  • the charging data request message also carries the identifier of the relay device.
  • the network element of the charging function can differentiate the charging according to the first identification of the remote terminal device and the identification of the relay device, so as to ensure the accuracy of the charging.
  • the charging data request message carries one or more of the following information of each remote terminal device: multi-unit usage, rate group, or used unit container.
  • the first charging policy may include one or more of the following: session charging rules, or service charging rules.
  • the first charging policy may further include: a status subscription indication.
  • the state subscription indication is used for the policy control network element to subscribe to the connection state of the remote terminal device.
  • the first charging policy may include one or more of the following: a first identifier, or a port number allocated by the relay device to the remote terminal device.
  • the first charging policy is acquired by the policy control network element from the first device according to the first identifier.
  • the first device may include: a policy control network element, a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element.
  • the session management network element sending the first identifier of the remote terminal device to the policy control network element may include: the session management network element sending the first message to the policy control network element.
  • the first message carries the first identifier, and the first message may be a session policy association establishment request message or a session policy association modification request message.
  • the method described in the second aspect may further include: the session management network element receives the second identifier from the remote terminal device, and sends the second identifier to the unified data management network element; thereby receiving data from the unified data management network element.
  • the first identifier of the management network element may further include: the session management network element receives the second identifier from the remote terminal device, and sends the second identifier to the unified data management network element; thereby receiving data from the unified data management network element.
  • the first identifier of the management network element may further include: the session management network element receives the second identifier from the remote terminal device, and sends the second identifier to the unified data management network element; thereby receiving data from the unified data management network element.
  • the first identifier of the management network element may further include: the session management network element receives the second identifier from the remote terminal device, and sends the second identifier to the unified data management network element; thereby receiving data from the unified data management network element.
  • the first identifier can be obtained from the unified data management network element through the second identifier, thereby improving the reliability of charging.
  • the first identifier may include: a subscription permanent identifier SUPI. It can be understood that, due to the uniqueness of SUPI, the remote terminal equipment can be accurately charged separately through SUPI.
  • SUPI subscription permanent identifier
  • the second identifier may include one or more of the following: the general public subscription identifier GPSI assigned by the operator, the user hidden identifier SUCI, the identifier assigned by the application function network element for the remote terminal device, or the third-party service provider as the remote terminal device.
  • Terminal equipment allocation identification such as QQ number, WeChat account, etc.
  • the first identifier can be obtained through the second identifier, thereby improving the reliability of charging.
  • the method described in the second aspect may further include: the session management network element receives the second charging policy from the policy control network element, and sends the second charging policy to the user plane network element according to the second charging policy.
  • the second reporting rule is the charging policy of the remote terminal device, and the second reporting rule is used for the user plane network element to report the traffic usage of the remote terminal device.
  • the reporting rules of the user plane network elements are updated synchronously, so as to ensure that the user plane network elements can accurately report the traffic usage of the remote terminal equipment.
  • the method described in the second aspect may further include: the session management network element obtains the session management subscription data of the remote terminal device from the unified data management network element, and according to the session management subscription data and the first charging policy, and determine the third charging policy of the remote terminal device; thus, send the third reporting rule to the user plane network element according to the third charging policy.
  • the third reporting rule is used for the user plane network element to report the traffic usage of the remote terminal device.
  • a third charging strategy with a more complete strategy can be determined to achieve more accurate charging.
  • the session management subscription data may include: protocol data unit PDU session charging characteristic information
  • the PDU session charging characteristic information may include: the first part of information
  • the session charging rule of the first charging policy may include: The second part of the information and the third part of the information
  • the session charging rule in the third charging policy may include: the first part of the information and the second part of the information.
  • the first part of the information and the third part of the information are of the same type and different in content, and the first part of the information and the second part of the information are different in type and content.
  • the determined third charging policy may include information that is not included in the PDU session charging characteristic information, so that the third charging policy is more complete and more accurate charging is achieved.
  • the method described in the second aspect may further include: the session management network element sends fifth indication information to the unified data management network element.
  • the fifth indication information is used to indicate that the remote terminal device accesses the wireless network through the relay device.
  • the unified data management network element can quickly and conveniently determine session management subscription data suitable for relay access according to the fifth indication information.
  • the method described in the second aspect may further include: the session management network element receives the second indication information from the policy control network element, and sends the second indication information to the relay device.
  • the second indication information is used to indicate that the remote terminal device is allowed to use the protocol data unit PDU session established by the relay device.
  • the second indication information is carried in the N1 message.
  • the method described in the second aspect may further include: the session management network element receives third indication information from the policy control network element, and sends the third indication information to the relay device.
  • the third indication information is used to indicate: the remote terminal equipment is not allowed to use the protocol data unit PDU session established by the relay equipment; or the third indication information is used to indicate that the remote terminal equipment is disconnected from the relay equipment.
  • the third indication information is carried in the N1 message.
  • the third indication information may include: first sub-information and second sub-information.
  • the first sub-information is used to indicate: there is no matching PDU session in the established PDU session; the second sub-information is used to indicate: the remote terminal device is not allowed to use the established PDU session; or, the second sub-information Used to indicate that the remote terminal device is disconnected from the relay device.
  • a communication device may include: a transceiver module and a processing module, the transceiver module is configured to receive a first identifier of the remote terminal equipment from the session management network element; the processing module is configured to control the transceiver module to send the session management network element to the session management network element according to the first identifier Send the first charging policy.
  • the remote terminal device accesses the wireless network through the relay device.
  • the first charging policy may include one or more of the following: session charging rules, or service charging rules.
  • the first charging policy may further include: a status subscription indication.
  • the status subscription indication is used to subscribe to the connection status of the remote terminal device.
  • the processing module is further configured to control the transceiver module to acquire the first charging policy according to the first identifier.
  • the processing module is further configured to control the transceiver module to obtain the first charging policy from the first device according to the first identifier.
  • the first device may include: a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element.
  • the transceiver module is further configured to send the first indication information to the second device.
  • the second device may include: a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element.
  • the first indication information is used to indicate that the remote terminal device accesses the wireless network through the relay device.
  • the first charging policy may include one or more of the following: a first identifier, or a port number allocated by the relay device to the remote terminal device.
  • the transceiver module is further configured to receive the first message from the session management network element.
  • the first message carries the first identifier, and the first message is a session policy association establishment request message or a session policy association modification request message.
  • the first identifier may include one or more of the following: a subscription permanent identifier SUPI, a general public subscription identifier GPSI, a user hidden identifier SUCI, or a port number allocated by the relay device to the remote terminal device.
  • the transceiver module when there is a PDU session whose charging policy matches the first charging policy in the protocol data unit PDU session established by the relay device, the transceiver module is further configured to send the first charging policy to the session management network element. 2. Instruction information. The second indication information is used to indicate that the remote terminal device is allowed to use the matched PDU session.
  • the transceiver module when there is no PDU session matching the charging policy and the first charging policy in the protocol data unit PDU session established by the relay device, the transceiver module is further configured to report to the session management network The element sends the third indication information.
  • the third indication information is used to indicate that: the remote terminal device is not allowed to use the established PDU session; or, the third indication information is used to indicate that the remote terminal device is disconnected from the relay device.
  • the third indication information may include: first sub-information and second sub-information.
  • the first sub-information is used to indicate that there is no matching PDU session in the established PDU session.
  • the second sub-information is used to indicate that the remote terminal device is not allowed to use the established PDU session; or, the second sub-information is used to indicate that the remote terminal device is disconnected from the relay device.
  • the transceiver module is further configured to receive the second charging policy from the application function network element. If the second charging policy is used for charging the device accessing the wireless network through the relay device, the transceiver module is further configured to send the second charging policy to the session management network element; or, if the second charging policy is not used For the charging of the device accessing the wireless network through the relay device, the transceiver module is further configured to send a charging policy update failure message or a charging policy creation failure message to the application function network element.
  • the transceiver module is further configured to receive fourth indication information from the application function network element, where the fourth indication information is used to indicate that the second charging policy is not used for the device accessing the wireless network through the relay device. billing.
  • the second charging policy is used for charging the device accessing the wireless network through the relay device, and the processing module is further configured to update the first charging policy according to the second charging policy.
  • the remote terminal device is connected to the relay device, and the first charging policy is in an active state; or, the remote terminal device is disconnected from the relay device, and the first charging policy is in an inactive state.
  • the connection between the remote terminal device and the relay device or the service flow is disconnected, and the transceiver module is also used to send a charging notification message to the application function network element.
  • the charging notification message is used to notify the connection of the remote terminal device or the disconnection of the service flow.
  • the transceiver module may include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the apparatus described in the third aspect
  • the receiving module is used to implement the receiving function of the apparatus.
  • the apparatus of the third aspect may further include a storage module, where the storage module stores programs or instructions.
  • the processing module executes the program or the instruction, the apparatus can execute the method described in the first aspect.
  • the communication device described in the third aspect may be the policy control network element in the first aspect, or may be a chip (system) or other components or components provided in the policy control network element, or may include the policy A device for controlling a network element; alternatively, the communication device can also be a network device, or a chip (system) or other components or components that can be provided in the network device, or a device including the network device.
  • a communication device may include: a transceiver module and a processing module.
  • the transceiver module is configured to send the first identification of the remote terminal equipment to the policy control network element, and receive the first charging policy of the remote terminal equipment from the policy control network element.
  • the processing module is configured to control the transceiver module to send the first reporting rule to the user plane network element according to the first charging policy.
  • the remote terminal device accesses the wireless network through the relay device.
  • the first reporting rule is used for the user plane network element to report the traffic usage of the remote terminal device.
  • the transceiver module is further configured to send a charging data request message to the charging function network element, where the charging data request message carries the first identifier.
  • the charging data request message also carries the identifier of the relay device.
  • the charging data request message carries one or more of the following information of each remote terminal device: multi-unit usage, rate group, or used unit container.
  • the first charging policy may include one or more of the following: session charging rules, or service charging rules.
  • the first charging policy may further include: a status subscription indication.
  • the state subscription indication is used for the policy control network element to subscribe to the connection state of the remote terminal device.
  • the first charging policy may include one or more of the following: a first identifier, or a port number allocated by the relay device to the remote terminal device.
  • the first charging policy is acquired by the policy control network element from the first device according to the first identifier.
  • the first device may include: a policy control network element, a unified data management network element, a unified data storage network element, a charging function network element, or an application function network element.
  • the transceiver module is further configured to send the first message to the policy control network element.
  • the first message carries the first identifier, and the first message may be a session policy association establishment request message or a session policy association modification request message.
  • the transceiver module is further configured to receive the second identifier from the remote terminal device, send the second identifier to the unified data management network element, and receive the first identifier from the unified data management network element.
  • the first identifier may include: a subscription permanent identifier SUPI.
  • the second identifier may include one or more of the following: a general public subscription identifier GPSI, a user hidden identifier SUCI, or an identifier allocated by the application function network element to the remote terminal device.
  • the transceiver module is further configured to receive the second charging policy from the policy control network element.
  • the processing module is further configured to control the transceiver module to send the second reporting rule to the user plane network element according to the second charging policy.
  • the second charging policy is the charging policy of the remote terminal device.
  • the second reporting rule is used for the user plane network element to report the traffic usage.
  • the processing module is further configured to control the transceiver module to obtain the session management subscription data of the remote terminal equipment from the unified data management network element; and determine the remote terminal equipment according to the session management subscription data and the first charging policy. and control the transceiver module to send the third reporting rule to the user plane network element according to the third charging policy.
  • the third reporting rule is used for the user plane network element to report the traffic usage.
  • the session management subscription data may include: protocol data unit PDU session charging characteristic information.
  • the PDU session charging feature information may include: the first part of information.
  • the session charging rule of the first charging policy may include: the second part of information and the third part of information.
  • the first part of information and the third part of information are of the same type and different in content, and the first part of information and the second part of information are different in type and content.
  • the session charging rule in the third charging policy may include: the first part of information and the second part of information.
  • the transceiver module is further configured to send fifth indication information to the unified data management network element.
  • the fifth indication information is used to indicate that the remote terminal device accesses the wireless network through the relay device.
  • the transceiver module is further configured to receive the second indication information from the policy control network element, and send the second indication information to the relay device.
  • the second indication information is used to indicate that the remote terminal device is allowed to use the protocol data unit PDU session established by the relay device.
  • the second indication information is carried in the N1 message.
  • the transceiver module is further configured to receive the third indication information from the policy control network element, and send the third indication information to the relay device.
  • the third indication information is used to indicate: the remote terminal equipment is not allowed to use the protocol data unit PDU session established by the relay equipment; or the third indication information is used to indicate that the remote terminal equipment is disconnected from the relay equipment.
  • the third indication information is carried in the N1 message.
  • the third indication information may include: first sub-information and second sub-information.
  • the first sub-information is used to indicate: there is no matching PDU session in the established PDU session; the second sub-information is used to indicate: the remote terminal device is not allowed to use the established PDU session; or, the second sub-information Used to indicate that the remote terminal device is disconnected from the relay device.
  • the transceiver module may include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the apparatus described in the fourth aspect
  • the receiving module is used to implement the receiving function of the apparatus.
  • the apparatus according to the fourth aspect may further include a storage module, where the storage module stores programs or instructions.
  • the processing module executes the program or instruction, the apparatus can execute the method described in the second aspect.
  • the device described in the fourth aspect may be a network device, a chip (system) or other components or components that can be arranged in a network device, or a device including a network device. Not limited.
  • a communication device may include: a processor and a memory.
  • the memory is used to store computer instructions which, when executed by the processor, cause the apparatus to perform the communication method as described in the first aspect.
  • the communication device described in the fifth aspect may further include a transceiver.
  • the transceiver may be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the fifth aspect to communicate with other communication devices.
  • the communication device described in the fifth aspect may be the policy control network element in the first aspect, or a chip (system) or other components or components may be provided in the policy control network element, or include the policy A device for controlling a network element; alternatively, the communication device can also be a network device, or a chip (system) or other components or components that can be provided in the network device, or a device including the network device.
  • a communication device may include: a processor and a memory.
  • the memory is used to store computer instructions which, when executed by the processor, cause the apparatus to perform the communication method as described in the second aspect.
  • the communication apparatus described in the sixth aspect may further include a transceiver.
  • the transceiver may be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the sixth aspect to communicate with other communication devices.
  • the communication device described in the sixth aspect may be the session management network element in the second aspect, or may be a chip (system) or other components or components set in the session management network element, or may include the policy A device for controlling a network element; alternatively, the communication device can also be a network device, or a chip (system) or other components or components that can be provided in the network device, or a device including the network device.
  • a computer-readable storage medium may include a computer program or instructions that, when run on a computer, cause the computer to perform the communication method as described in the first aspect or the second aspect.
  • a computer program product may comprise a computer program or instructions which, when run on a computer, cause the computer to perform the communication method as described in the first aspect or the second aspect.
  • the communication system may include one or more terminal devices, and one or more network devices.
  • FIG. 1 is a schematic diagram 1 of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a second schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a protocol stack of a PDU session in a communication system provided by an embodiment of the present application
  • FIG. 4 is a schematic flowchart 1 of a communication method provided by an embodiment of the present application.
  • FIG. 5 is a second schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a third schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 7 is a fourth schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram 1 of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a second schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as ProSe communication systems, wireless fidelity (WiFi) systems, vehicle-to-everything (V2X) communication systems, inter-device (device-to-everything, V2X) communication systems, todevie, D2D) communication system, vehicle networking communication system, 4th generation (4th generation, 4G) mobile communication system, such as long term evolution (long term evolution, LTE) system, worldwide interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) ) communication systems, fifth generation (5th generation, 5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as sixth generation (6th generation, 6G) mobile communication systems.
  • 4th generation (4th generation, 4G) mobile communication system such as long term evolution (long term evolution, LTE) system, worldwide interoperability for microwave access (worldwide interoperability for microwave access, WiMAX)
  • 5th generation, 5G mobile communication systems
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 1 shows a schematic diagram of the architecture of a 5G communication system to which the communication method provided by the embodiment of the present application is applied.
  • the 5G communication system may include two parts, an access network (AN) and a core network (CN).
  • AN access network
  • CN core network
  • the AN is mainly used to implement functions related to wireless access, and may include a radio access network (radio access network, RAN) network element.
  • CN can mainly include the following network elements: access and mobility management function (AMF) network element, session management function (session management function, SMF) network element, user plane function (user plane function, UPF) network element NE, Policy Control Function (PCF) NE, Unified Data Management (UDM) NE, Unified Data Repository (UDR) NE, Charging Function (CHF) ) network element, network capability exposure function (NEF) network element, and application function (application function, AF) network element.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • UDR Unified Data Repository
  • CHF Charging Function
  • the AMF network element is mainly responsible for the access management in the wireless network, such as user access, user location update, user registration network, cell handover and so on.
  • the RAN network element is mainly used to provide network access functions for authorized terminal equipment in a specific area, such as the network signal coverage area.
  • the SMF network element is mainly responsible for session management in the wireless network, such as the creation, modification, deletion, etc. of a protocol data unit (protocol data unit, PDU) session, and maintaining the PDU session context.
  • protocol data unit protocol data unit
  • the UPF network element is mainly responsible for processing user data packets, such as data packet forwarding and traffic usage statistics.
  • the PCF network element is mainly responsible for providing various policies to the AMF network element and the SMF network element, such as providing the SMF network element with the user's charging policy according to the user's subscription information.
  • the UDM network element is mainly used to store user data, such as subscription information and authentication/authorization information.
  • the UDR network element is mainly used to store the policies required by the PCF network element, such as charging policies or user data of the UMD network element, and can be deployed together with the UDM network element.
  • the CHF network element is mainly responsible for obtaining the user's billing information from the core network element, such as the SMF network element, charging and generating the user's bill.
  • the NEF network element is mainly used to connect the network element in the core network and the external application server, and can provide services such as authentication and forwarding for the external application server to initiate service requests to the core network.
  • AF network elements are mainly used for interaction between PCF network elements for policy control, such as sending charging policies to PCF network elements.
  • the RAN network element in this embodiment of the present application may be a device with a wireless transceiver function or a chip (system) or other component or component of the device, including but not limited to: a wireless fidelity (wireless fidelity, WiFi) system access point (AP), such as home gateway, router, server, switch, bridge, etc., evolved Node B (evolved Node B, eNB), radio network controller (RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit ( baseband unit, BBU), wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP or transmission point, TP), etc., and can also be 5G, such as in the new radio (new radio, NR) system
  • the gNB or, the transmission point (TRP or TP), one or a group (
  • the RAN network element communicates with the AMF network element through the N2 interface (N2 for short), and communicates with the UPF network element through the N3 interface (N3 for short).
  • the UPF network element communicates with the SMF network element through the N4 interface (N4 for short), and communicates with the UPF network element through the N9 interface (N9 for short).
  • the AMF network element communicates with the UDM network element through the N8 interface (N8 for short), communicates with the SMF network element through the N11 interface (N11 for short), communicates with the AMF network element through the N14 interface (N14 for short), and communicates with the N15 interface (N15 for short).
  • PCF network element communication PCF network element communication.
  • the PCF network element communicates with the AF network element through the N5 interface (N5 for short), and communicates with the SMF network element through the N7 interface (N7 for short).
  • the SMF network element communicates with the UDM network element through the N10 interface (N10 for short).
  • the UDR network element communicates with the PCF network element through the N36 interface (N36 for short).
  • the CHF network element communicates with the SMF network element through the N40 interface (N40 for short), and communicates with the PCF network element through the N28 interface (N28 for short).
  • the NEF network element communicates with the UDR network element through the N37 interface (N37 for short), and communicates with the PCF network element through the N30 interface (N30 for short).
  • the above network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the above network elements or functions may be divided into one or more services, and further, services that exist independently of network functions may also appear.
  • the above-mentioned network elements may also use service interfaces to communicate with each other.
  • an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or an instance of a service that exists independently of a network function may be referred to as a service instance.
  • FIG. 2 shows a schematic diagram of the architecture of the 5G communication system shown in FIG. 1 in the ProSe communication scenario.
  • the terminal equipment located in the network can communicate with the AMF network element through the N1 interface (N1 for short), and communicate with the RAN network element through the Uu interface to access the network.
  • a terminal device located outside the network such as outside the coverage area of the network signal (referred to as a remote terminal device)
  • a relay device can access the network through a terminal device (referred to as a relay device) that has been connected to the network.
  • the relay device communicates with the remote terminal device through the PC5 interface, so that the remote terminal device can access the network through the relay device, such as a PDU session using the relay device.
  • FIG. 3 shows a protocol stack of a PDU session of a remote terminal device by using a relay device.
  • the remote terminal device sends a data packet to the relay device through the PC5 interface, and the data packet may include: physical layer (L1 layer), medium access control (media access control, MAC) layer, radio link control sub (radio link control structure, RLC) layer, packet data convergence protocol (packet data convergence protocol, PDCP) layer.
  • Service data adaptation protocol service data adaptation protocol, SDAP
  • IP internet protocol
  • application application
  • the MAC layer, the RLC layer, the PDCP layer and the SDAP layer may belong to the L2 layer.
  • the relay device may sequentially decode the L1 layer and the L2 layer of the data packet, and decode to the IP layer. After that, the relay device encapsulates the L2 layer and the L1 layer in turn based on the protocol stack of the Uu interface, and sends the data packet to the RAN network element through the Uu interface.
  • the RAN network element can also decode the L1 layer and L2 layer of the data packet in sequence, and decode to the IP layer. Afterwards, the RAN network element can re-encapsulate the data packets in the format of the PDU session of the relay device. Wherein, the re-encapsulated data packets may include: L1 layer, L2 layer, user datagram protocol (user datagram protocol, UDP) layer/IP layer, tunnel transmission protocol (GPRS tunnel protocol-U, GTP-U) layer, IP layer . Finally, the RAN network element can send the data packet to the UPF network element through the N3 interface.
  • the UPF network element can send the data packet to the corresponding device according to the route indicated by the data packet, thereby realizing the communication after the remote terminal device accesses the wireless network.
  • the sending of the data packet in the PDU session format by the RAN network element to the UPF network element can be understood as: using the PDU session to send the data packet of the remote terminal device.
  • the remote terminal device and the relay device in this embodiment of the present application may be a terminal with a wireless transceiver function, or a chip (system) or other components or assemblies that may be provided in the terminal.
  • the terminal equipment may also be referred to as user equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment.
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation security ( Wireless terminals in transportation safety), wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, RSUs with terminal functions, etc.
  • a virtual reality virtual reality
  • VR virtual reality
  • AR augmented reality terminal equipment
  • wireless terminals in industrial control wireless terminals in self driving
  • wireless terminals in remote medical wireless terminals in smart grid
  • transportation security Wireless terminals in transportation safety
  • wireless terminals in smart cities wireless terminals in smart homes, vehicle-mounted terminals, RSUs with terminal functions, etc.
  • the terminal device of the present application may also be an in-vehicle module, an in-vehicle module, an in-vehicle component, an in-vehicle chip or an in-vehicle unit built into the vehicle as one or more components or units.
  • FIGS. 1 and 2 are simplified schematic diagrams for easy understanding only, and the communication system may also include other network devices and/or other terminal devices, which are not shown in FIGS. 1 and 2 .
  • FIG. 4 is a first schematic flowchart of a communication method provided by an embodiment of the present application.
  • the communication method can be applied to the communication between the policy control network element, the session management network element, and the user plane network element.
  • the policy control network element may be the PCF network element shown in FIG. 1 and FIG. 2
  • the self-session management network element may be the SMF network element shown in FIG. 1 and FIG. 2
  • the user plane network element may be FIG. 1 and FIG. 2
  • the UPF network element and the unified data management network element shown may be the UDM network element shown in FIG. 1 and FIG. 2
  • the unified data storage network element may be the UDR network element shown in FIG. 1 or FIG. 2 .
  • the communication method may include the following steps:
  • the session management network element sends the first identifier of the remote terminal device to the policy control network element.
  • the remote terminal device accesses the wireless network through the relay device.
  • the identification of the remote terminal device may include a first identification and a second identification.
  • the first identification and the second identification are different, but may have a corresponding relationship.
  • the second identifier may be used by the session management network element to obtain the first identifier.
  • the first identifier can be used for the policy control network element to obtain the first charging policy of the remote terminal device, so as to implement separate charging for the remote terminal device.
  • the first identifier may include one or more of the following: a subscription permanent identifier (SUPI) of the remote terminal device, a generic public subscription identifier (GPSI) of the remote terminal device, or The user concealed identifier (SUCI) of the remote terminal device.
  • SUPI subscription permanent identifier
  • GPSI generic public subscription identifier
  • SUCI user concealed identifier
  • the second identifier may include one or more of the following: the SUPI of the remote terminal device, the GPSI of the remote terminal device, the SUCI of the remote terminal device, the port number allocated by the relay device for the remote terminal device, or the first The identifier assigned by the third-party service provider to the remote terminal device, such as QQ number, WeChat ID, etc.
  • the remote terminal device can communicate with the wireless network through the used PDU session, such as sending the first identifier or the second identifier of the remote terminal device to the session management network element.
  • the relay device may also send a PDU session identifier (PDU Session ID) of the PDU session to the session management network element.
  • PDU Session ID PDU Session ID
  • the session management network element may send the first identifier of the remote terminal device to the policy control network element according to the corresponding relationship between the first identifier and the second identifier.
  • the first identification used for charging the remote terminal device can be determined based on the corresponding relationship, so as to realize separate charging for the remote terminal device, thereby improving the accounting fee reliability.
  • the session management network element can directly obtain the first identifier.
  • the session management network element can obtain the first identifier according to the second identifier.
  • the session management network element can send the second identifier from the UDR network element/UDM network element (in FIG. 4 ) according to the second identifier. not shown) to obtain the first identification.
  • the session management network element may send the second identifier to the UDR network element/UDM network element.
  • the UDR network element/UDM network element stores the first identifier and the corresponding relationship between the first identifier and the second identifier. In this way, the UDR network element/UDM network element can determine the first identifier according to the second identifier and the corresponding relationship, and send the first identifier to the session management network element, so that the session management network element obtains the first identifier.
  • the relay device may send a remote verification request to the UDR network element/UDM network element via the AMF network element (not shown in FIG. 4 ).
  • the verification request carries the second identifier.
  • the UDR network element/UDM network element verifies the legality of the remote terminal device according to the second identifier, it can send the verification result, the first identifier, and the correspondence between the first identifier and the second identifier to the AMF network element.
  • the AMF network element can send the first identifier and the corresponding relationship between the first identifier and the second identifier to the session management network element, so that after receiving the second identifier from the remote terminal device, the session management network element can The identifier and the corresponding relationship are determined, and the first identifier is determined.
  • the session management network element may send the second identifier to the AMF network element, so that the AMF network element can return the corresponding first identifier according to the second identifier and the corresponding relationship.
  • the session management network element can send the first identifier to the policy control network element, such as sending a first message to the policy control network element.
  • the first message carries the first identifier, the SUPI, GPSI or SUCI of the relay device, and the PDU session identifier of the PDU session used by the remote terminal device, and the first message may be a session policy association establishment request (SM Policy). Association Establishment) message or session policy association change request (SM Policy Association Modification) message.
  • sending the first identifier by multiplexing the session policy association establishment request message or the session policy association change request message can reduce signaling overhead and improve communication efficiency.
  • the policy control network element sends the first charging policy of the remote terminal device to the session management network element according to the first identifier.
  • the session management network element receives the first charging policy from the policy control network element.
  • the first charging policy may include one or more of the following: session charging rules or service charging rules. They are described below.
  • the "session charging rule” may also be referred to as: "PDU Session related policy information (PDU Session related policy information)".
  • the session charging rule is a PDU session dimension charging rule, which is used for charging in units of PDU sessions.
  • the session charging rules may include: the charging mode of the PDU session, the rating group (rating group, RG) of the PDU session, and the usage monitoring control policy, etc.
  • the charging method can be online charging or offline charging; online charging means that the CHF network element (not shown in FIG.
  • service charging rules may also be referred to as “policy and charging control (PDU Session related policy information, PCC) rules".
  • a service charging rule is a service-dimensioned charging rule, which is used for charging in units of services, such as videos, calls, and web browsing. Since different services may have different charging methods, the service charging rules may include: the quintuple of each service, the identifier of each service, the charging mode of each service, the rate of each service, Spending limit policies for each service; and, when there is a service sponsored by a third-party service provider, the service charging rules may further include: a sponsor ID (sponsor ID) of the third-party service provider.
  • the quota policy can be used to indicate whether the traffic usage of the remote terminal device exceeds the quota, and to indicate the corresponding rate of the traffic usage of the service exceeding or not exceeding the quota.
  • the rate corresponding to the traffic usage of the service exceeding the limit is the first rate
  • the rate corresponding to not exceeding the limit is the second rate
  • the first rate is lower than the second rate.
  • the sponsorship identifier of the third-party service provider can be used to indicate that the billing of the corresponding service is sponsored by the third-party service provider, that is, the user plane network element can no longer report the traffic amount corresponding to the service sponsored by the third-party service provider to the CHF network element.
  • the network element may also no longer charge for the services sponsored by the third-party service provider.
  • the service charging rule of the remote terminal device may be a general service charging rule that can be configured for each device.
  • the unified charging service refers to the services that most devices have and the charging method is also the same, such as the video service of the mobile phone, the call service, and the like.
  • the service charging rule is a rule that can be configured by each device, the service charging rule may not include an identifier for distinguishing services.
  • the service charging rule of the remote terminal device may be a service accounting rule configured separately for the non-uniform charging service of the remote terminal device. fee rules.
  • the non-uniform billing service refers to a service with a different type and/or different billing method from the unified billing service, such as game video services for VR equipment, AR equipment, and game consoles.
  • the service charging rule may contain the first identification of the remote terminal device, so as to be distinguished from the general service charging rule.
  • the first charging policy may further include: a status subscription indication.
  • state subscription indication may also be referred to as: "policy control request trigger information (policy control request trigger information)".
  • the state subscription indication can be used by the policy control network element to subscribe the service flow state of the remote terminal equipment to the session management network element, and/or the connection state, such as instructing the policy control network element to send a subscription request message to the session management network element.
  • the session management network element can send the subscription notification message of the remote terminal device to the policy control network element, so that the policy control network element can grasp it in time.
  • the service flow status and/or the connection status of the remote terminal device so as to adjust the charging rules in time to ensure the accuracy of charging.
  • the disconnection may be the disconnection of the communication connection between the remote terminal device and the network.
  • the disconnection of the service flow may be that the service flow of some services of the remote terminal device is disconnected, while the service flow of other services of the remote terminal device may not be disconnected. In other words, if the connection of the remote terminal device is disconnected, all service flows of the remote terminal device are disconnected, otherwise, the disconnection of the service flow of the remote terminal device does not affect the communication connection between the remote terminal device and the network.
  • the specific implementation of the policy control network element adjusting the charging rule according to the service flow state of the remote terminal device and/or the connection state can refer to the relevant description in the seventh implementation scenario, which will not be repeated here.
  • the policy control network element may also configure the state of the first charging policy correspondingly according to the connection state of the remote terminal device. For example, if the remote terminal device is in a connected state, the policy control network element can configure the first charging policy to be in an active state; if the remote terminal device is in a disconnected state, the policy control network element can configure the first charging policy is inactive. In this way, the policy control network element can determine whether to use the first charging policy according to the state of the first charging policy, so as to schedule resources more flexibly, such as configuring or releasing resources, to improve communication efficiency.
  • the "policy” described in the embodiments of the present application is the superordinate expression of the "rule” and “instruction”; correspondingly, the “rule” and “instruction” are the subordinate expression of the “policy” .
  • the first charging policy is not limited to: session charging rules, service charging rules and status subscription indication, for example, the first charging policy may only include session charging rules, which is not limited.
  • the session management network element sends the first reporting rule to the user plane network element according to the first charging policy.
  • the first reporting rule may be a part of the rules in the first charging policy, which may be used for user plane network elements to identify, count and report the traffic of the remote terminal equipment, and may include: traffic identification rules and traffic reporting rules.
  • the traffic identification rule can be used for the user plane network element to identify the traffic of the remote terminal device.
  • the traffic identification rule can include the quintuple information of the traffic of the remote terminal device, so that the user plane network element can identify the traffic from the remote terminal device according to the quintuple.
  • the traffic of the remote terminal device is identified in the traffic forwarded by the user plane network element.
  • the traffic reporting rule may be used by the user plane network element to report the traffic usage of the remote terminal device to the session management network element.
  • the traffic reporting rules may include: traffic quotas and reporting triggering rules.
  • the traffic quota may represent the traffic that can be used by the remote terminal device at the current stage.
  • the session management network element may apply to the CHF network element for the traffic quota of the current stage, such as applying to the CHF network element through the N40 session.
  • the CHF network element may configure the current stage traffic quota for the remote terminal device according to the package traffic balance of the remote terminal device. For example, if the package traffic balance is 500 megabytes (MB), the traffic quota configured by the CHF network element can be 50MB. Further, if the traffic quota of the remote terminal device in the current stage has been used up, the session management network element may apply to the CHF network element for the traffic quota of the next stage.
  • the package traffic balance is 500 megabytes (MB)
  • the traffic quota configured by the CHF network element can be 50MB.
  • the session management network element may apply to the CHF network element for the traffic quota of the next stage.
  • the CHF network element can continue to configure the traffic quota of the next stage for the remote terminal device according to the package traffic balance of the remote terminal device, until the package traffic balance of the remote terminal device is insufficient, or the connection of the remote terminal device is disconnected.
  • the reporting triggering rules may include: periodic triggering rules and event triggering rules.
  • the user plane network element can periodically count the traffic of the remote terminal device to obtain the traffic usage of the remote terminal device, and periodically report the traffic usage to the session management network element according to the periodic triggering rule, such as sending N4 Session report message, the N4 session report message carries the traffic usage.
  • the reporting period may be 1 minute, 5 minutes, 30 minutes, 1 hour, 1 day, 1 week, etc.
  • the traffic usage counted by the user plane network element reaches the upper limit of the traffic quota of the remote terminal device, the traffic usage can be reported to the session management network element according to the event triggering rule.
  • the upper limit value may be determined according to the above-mentioned traffic quota, such as 10%, 30%, 50%, 70%, 90%, 100%, etc. of the traffic quota.
  • periodic triggering rules and event triggering rules can also be implemented in combination. For example, if the period triggering rule is triggered first, the user plane NEs report the traffic usage of the current period; if the event triggering rule is triggered first, the user plane NEs report the traffic usage that reaches the upper limit.
  • the specific content of the first charging rule is described above. The following describes how the session management network element sends the first charging rule and how to report the charging information.
  • the session management network element may send N4 session configuration information to the user plane network element through the N4 session, where the N4 session configuration information includes the first reporting rule, and the N4 session configuration information includes the first reporting rule.
  • the N4 session configuration information may be carried in the N4 session establishment request message or the N4 session modification request message.
  • the session management network element can periodically count the traffic consumption of the remote terminal equipment reported by the user plane network element, so as to obtain each cycle. traffic usage. In this way, the session management network element can periodically send the charging information of the remote terminal device to the CHF network element according to the first charging rule and the traffic consumption of each period.
  • the reporting period of the session management network element and the reporting period of the user plane network element may be the same or different.
  • the reporting period of the session management network element may be greater than the reporting period of the user plane network element.
  • the charging information may include the traffic usage and rate of the corresponding period, so that the CHF network element can separately charge the remote terminal device according to the traffic usage and rate.
  • the user plane network element generates and reports the traffic usage of the remote terminal device
  • the specific implementation of the CHF network element's separate billing for the remote terminal device according to the traffic usage can refer to the following ninth implementation scenario. describe.
  • the policy control network element can obtain the first identifier of the remote terminal device from the session management network element, the policy control network element can send the remote terminal device to the session management network element according to the first identifier. the first billing strategy.
  • the session management network element can configure the first reporting rule of the remote terminal device for the user plane network element according to the first charging policy, so that after the remote terminal device accesses the wireless network through the relay device, the user plane network element can The first reporting rule is to report the traffic usage of the remote terminal equipment to the network element with the charging function, so as to implement separate charging for the remote terminal equipment.
  • the method may further include: the policy control network element acquires the first charging policy of the remote terminal device according to the first identifier.
  • the policy control network element may acquire the first charging policy from the first device according to the first identifier.
  • the first device may be used to store the first charging policy, and may specifically include one or more of the following: a policy control network element, a UDM network element, a UDR network element, a CHF network element, or an AF network element (in FIG. 4 ). not shown).
  • Method 1 Obtain from the policy control network element locally.
  • the policy control network element determines, according to the first identifier, whether the policy control network element locally stores the session policy control subscription information of the remote terminal device.
  • the session policy control subscription information includes session policy association information of the remote terminal device, and the session policy association information includes the first charging policy. If the policy control network element locally stores the session policy control subscription information of the remote terminal device, the policy control network element acquires the first charging policy from the session policy control subscription information.
  • Mode 2 Obtain from the UDM network element/UDR network element.
  • the policy control network element determines, according to the first identifier, whether the policy control network element locally stores the session policy control subscription information of the remote terminal device. If the policy control network element does not locally store the session policy control subscription information of the remote terminal device, the policy control network element sends a request message to the UDM network element/UDR network element. The request message may be used to request the session policy control subscription information of the remote terminal device, and may carry the first identifier. Correspondingly, the UDM network element/UDR network element may return the session policy control subscription information of the remote terminal device according to the first identifier.
  • the policy control network element may send the first identifier to the UDM network element/UDR network element through a preset service, such as Nudr_DM_Query service or Nudr_DM_Subscribe service, which is not limited.
  • a preset service such as Nudr_DM_Query service or Nudr_DM_Subscribe service, which is not limited.
  • the policy control network element can acquire the session policy association information of the remote terminal device from the received session policy control subscription information, that is, acquire the first charging policy.
  • the policy control network element determines, according to the first identifier, whether the policy control network element locally stores the session policy control subscription information of the remote terminal device. If the policy control network element does not locally store the session policy control subscription information of the remote terminal device, the policy control network element sends a request message to the CHF network element.
  • the request message may be used to request the session policy control subscription information of the remote terminal device, and may carry the first identifier.
  • the CHF network element may return the corresponding first charging policy to the policy control network element according to the first identifier.
  • the policy control network element may send the first identifier to the UDM network element/UDR network element through a preset service, such as the Nchf_SpendingLimitControl service, which is not limited.
  • the AF network element may send the first charging policy to the policy control network element through a preset service, such as the Npcf_PolicyAuthorization_Create service or the Npcf_PolicyAuthorization_Update service.
  • a preset service such as the Npcf_PolicyAuthorization_Create service or the Npcf_PolicyAuthorization_Update service.
  • the AF network element may send the second message to the NEF network element (not shown in FIG. 4 ).
  • the second message may be a related message used by the third-party service provider for the traffic sponsorship service, and may carry the first charging policy.
  • the NEF network element forwards the second message to the policy control network element, so that the policy control network element obtains the first charging policy from the second message.
  • the policy control network element may determine whether the policy control network element locally stores the session policy control subscription information of the remote terminal device according to the first identifier.
  • the policy control network element can obtain the rules from each network element respectively, and synthesize the separately obtained rules to obtain the first charging policy.
  • the policy control network element can obtain the quota policy of each service in the service charging rules from the CHF network element, and obtain the session charging rules, service charging rules and status subscription instructions from the UDM network element/UDR network element, and the policy The service charging rules obtained by the control network element from the UDM network element/UDR network element do not include the quota policy.
  • the quota policy obtained by the policy control network element from the CHF network element, and the rules and instructions obtained from the UDM network element/UDR network element constitute the first charging policy.
  • the policy control network element may acquire the service charging rules from the AF network element, and acquire the session charging rules and the status subscription indication from the UDM network element/UDR network element.
  • the rules and instructions obtained by the policy control network element from the AF network element, the UDM network element/UDR network element constitute the first charging policy.
  • the policy control network element may obtain the service charging rules from the AF network element, and obtain the session charging rules, the service charging rules and the status subscription indication from the UDM network element/UDR network element. Afterwards, the policy control network element may combine the service charging rules obtained from the AF network element and the UDM network element/UDR network element respectively to obtain the combined service charging rules.
  • service charging rule 1 may include A1 and B1
  • service charging rule 2 may include A2 and C1.
  • A1 and A2 are information of the same type but different values
  • B1 and C1 are information of different types and values.
  • the policy control network element can delete A2 and retain A1, B1 and C1, so that the combined service charging rule can include A1, B1 and C1. In this way, the combined service charging rule, session charging rule and state subscription indication constitute the first charging policy.
  • the policy control network element may directly send the first charging policy to the session management network element.
  • the policy control network element may add the first identifier and/or the port number to the first charging policy.
  • the port number is the port number assigned by the relay device to the remote terminal device.
  • the policy control network element sends the first charging policy to the session management network element, so that the session management network element determines that the first charging policy is the remote terminal device according to the first identifier and/or the port number the charging policy, so as to accurately report the charging information of the remote terminal device.
  • the policy control network element may not determine whether the policy control network element locally stores the session policy control subscription information of the remote terminal device, but directly to the UDM network element or the UDR network element. Or a device such as an AF network element sends a request message for requesting the session policy control subscription information, which is not limited.
  • the method may further include: Step 1, the session management network element obtains the session management subscription data of the remote terminal device from the second device. subscription data).
  • the second device may be used for storing session management subscription data.
  • the second device and the first device may be the same device, or may be different devices.
  • the second device may specifically be a UDM network element.
  • the session management subscription data may include: PDU session charging feature information of the relay device.
  • the PDU session charging feature information may include: PDU session dimension charging rules, which may be used for charging in units of PDU sessions.
  • the session management network element may acquire the session management subscription data of the remote terminal device from the UDM network element according to the obtained first identifier or the second identifier.
  • the session management network element can send a request message to the UDM network element, and the request message carries the first identifier for requesting Session management subscription data for the remote terminal device.
  • the session management network element may send a request message to the UDM network element through a preset service, such as requesting a service through Nudm_SDM_Get, subscribing to a service through Nudm_SDM_Subscribe, etc., which is not limited thereto.
  • a preset service such as requesting a service through Nudm_SDM_Get, subscribing to a service through Nudm_SDM_Subscribe, etc., which is not limited thereto.
  • the UDM network element may locally acquire the session management subscription data from the UDM network element according to the first identifier.
  • the UDM network element may also send a subscription request message to the UDR network element.
  • the subscription request message may be used to request the session management subscription data from the UDR network element, and the subscription request message may carry the first identifier.
  • the UDR network element can send the session management subscription data to the UDM network element according to the subscription request message, so that the UDM network element sends the session management subscription data to the session management network element.
  • the UDM network element may send the above-mentioned subscription request message to the UDR network element through a preset service, for example, through Nudr_DM_Query subscription service, Nudr_DM_subscribe subscription service, etc., which is not limited.
  • the session management network element may first obtain the first identifier from the UDM network element according to the second identifier.
  • the specific implementation of acquiring the first identifier from the UDM network element according to the second identifier may refer to S401, which will not be repeated here.
  • the session management network element acquires the session management subscription data from the UDM network element according to the first identifier.
  • the session management network element acquires the session management subscription data from the UDM network element according to the first identifier.
  • the session management network element may send a request message to the UDM network element.
  • the request message is used to request session management subscription data of the remote terminal device, and may carry the second identifier.
  • the session management network element may send the second identifier to the UDM network element through a preset service, such as requesting a service through Nudm_SDM_Get, subscribing to a service through Nudm_SDM_Subscribe, etc., which is not limited.
  • the UDM network element may locally acquire the first identifier corresponding to the second identifier from the UDM network element according to the second identifier, and then acquire the session management subscription data corresponding to the first identifier.
  • the UDM network element may also send a request message for requesting session management subscription data of the remote terminal device to the UDR network element, where the request message carries the second identifier.
  • the UDR network element can acquire the first identifier according to the second identifier, and acquire the session management subscription data corresponding to the first identifier, so as to send the first identifier and the session management subscription data to the UDM network element.
  • the UDM network element can package and send the first identifier and the session management subscription data to the session management network element, so that the session management network element obtains the session management subscription data and also obtains the first identifier.
  • the UDM network element may send the second identifier to the UDR network element through a preset service, for example, through Nudr_DM_Query subscription service, Nudr_DM_subscribe subscription service, etc., which is not limited.
  • the method may further include: Step 2, the session management network element determines the remote terminal equipment according to the session management subscription data and the first charging policy. the third billing strategy.
  • the PDU session charging characteristic information may include: the first part of information, and the session charging rule of the first charging policy may include: the second part of information and the third part of information.
  • the first part of information and the third part of information are of the same type and different in content, and the first part of information and the second part of information are different in type and content.
  • the session management network element can update the third part of the information in the first charging policy to the first part of the session management subscription data, so as to realize the A charging policy is updated to a third charging policy, so as to implement separate charging for the remote terminal device.
  • the session charging rules of the third charging policy are different from the session charging rules of the first charging policy.
  • the session charging rules of the third charging policy may include: the first part of information and the second part of information, while the third The session charging rules and the status subscription indication in the charging policy are still the same as the session charging rules and the status subscription indication in the first charging policy.
  • the first part of information includes: service A, the rate is RG1; the second part of information includes: service B, the rate is RG2, and the service C, the rate is RG3; the third part of information includes: service A, the rate is RG4 .
  • the first part of the information and the third part of the information are both the charging policy of the service A, indicating that the first part of the information and the third part of the information are of the same type.
  • the rates of the service A in the first part of the information and the third part of the information are different, indicating that the contents of the first part of the information and the third part of the information are different.
  • the services and rates of the first part of the information and the second part of the information are different, indicating that the types and contents of the first part of the information and the second part of the information are different.
  • the session charging rule of the third charging policy may include: service A with a rate of RG4, service B with a rate of RG2, and service C with a rate of RG3.
  • the determination of the third charging policy by the session management network element according to the session management subscription data and the first charging policy is only an exemplary manner, and is not intended to be a limitation. For example, if the content of the PDU session charging feature information is the same as the content of the session charging rule in the first charging policy, the first charging policy does not need to be updated.
  • the method may further include: Step 3, the session management network element sends a third report to the user plane network element according to the third charging policy rule.
  • the specific implementation manner of the session management network element sending the third reporting rule to the user plane network element according to the determined third charging policy may refer to the relevant description in step S403, which is not repeated here.
  • the session management network element may also send a third charging policy to the policy control network element, so that the policy control network element updates the locally stored first charging policy to the third charging policy.
  • the method may further include: the session management network element sends fifth indication information to the second device.
  • the fifth indication information may be used to instruct the remote terminal device to access the wireless network through the relay device, or be used to instruct the way of the remote terminal to access the network.
  • the fifth indication information may be an indication field, such as 1 bit.
  • the network access mode of the terminal device may include: a relay access mode, that is, a mode in which the terminal device accesses the wireless network through a relay device; or a direct access mode, that is, the terminal device directly accesses the wireless network through an access network device access to the wireless network.
  • a relay access mode that is, a mode in which the terminal device accesses the wireless network through a relay device
  • a direct access mode that is, the terminal device directly accesses the wireless network through an access network device access to the wireless network.
  • different access modes may correspond to different session management subscription data.
  • the session charging feature information of the PDUs of the session management subscription data may include: the third-party free-flow charging rules; if the relay access network mode is adopted, the PDUs of the session management subscription data may include: The session charging feature information may include: rules for paying traffic charging. Therefore, the session management network element may also send fifth indication information to the second device, eg, to the UDM network element.
  • the UDM network element may send the session management subscription data corresponding to the relay access mode to the session management network element according to the fifth indication information.
  • the method may further include: the policy control network element sends the first indication information to the second device.
  • the second device may also be used to store the first charging policy.
  • the second device may specifically be a UDR network element, a UDM network element, a CHF network element, or an AF network element, etc., which is not limited.
  • the first indication information may be used to indicate the network access mode of the remote terminal, such as instructing the remote terminal device to access the wireless network through a relay device, and may be an indication field, such as a 1-bit information element.
  • the policy control network element may also send the first indication information to the second device, so that the second device determines according to the first identifier and the first indication information The first charging policy corresponding to the relay access mode.
  • the method may further include: the policy control network element receives the second charging policy from the second device, and sends the second charging policy to the session management network element The second charging strategy.
  • the second device may also be used to store the second charging policy.
  • the second device may specifically be an AF network element.
  • the second charging policy may be different from the first charging policy and the third charging policy.
  • the second charging policy may include: a third-party free-flow charging rule, and the first charging policy and the third charging policy may include: a paid-flow charging rule.
  • the second charging policy may include rules for charging video services, and the first charging policy and the third charging policy may include rules for charging audio services.
  • the AF network element may configure the charging policy of the remote terminal device for the policy control network element, and the charging policy configured by the AF network element may be referred to as the second charging policy.
  • the AF network element may send the second charging policy to the policy control network element.
  • the AF network element may send a charging policy creation request message or a charging policy update request message to the policy control network element, where the charging policy creation request message or the charging policy update request message carries the second charging policy.
  • the AF network element may directly send the second charging policy to the policy control network element. If the AF network element belongs to a third-party service provider, the AF network element can send the second charging policy to the NEF network element (not shown in FIG. 4 ). The NEF network element can verify the authority of the AF network element and then send the policy to the The control network element forwards the second charging policy.
  • the policy control network element can send the second charging policy to the session management network element, so that the session management network element can report to the user plane network element according to the second charging policy.
  • the element sends the second reporting rule, so that the user plane network element can report the traffic usage of the remote terminal device according to the second reporting rule, so as to ensure the accuracy of billing.
  • the specific implementation manner for the session management network element to send the second reporting rule to the user plane network element according to the second charging policy may refer to the relevant description in step S403, which will not be repeated here.
  • the method may further include: the policy control network element receives the fourth information from the AF network element. Instructions.
  • the fourth indication information may be used to indicate that: the second charging policy is not used for the charging of the remote terminal equipment that accesses the wireless network through the relay device, or is not used for the charging of the relay access network, or It is used for billing in direct access to the network.
  • the fourth indication information may be an indication field, such as a 1-bit information element.
  • the AF network element sends a charging policy creation request message or a charging policy update request message to the policy control network element, where the charging policy creation request message or the charging policy update request message carries fourth indication information.
  • the policy control network element may determine whether to receive the fourth indication information from the AF network element within a preset time period after receiving the second charging policy.
  • the second charging policy may be sent to the session management network element, and The locally stored charging policy is updated to be the second charging policy.
  • the policy control network element if the policy control network element locally saves the first charging policy, the first charging policy is updated to the second charging policy; if the policy controls the local network element locally If the updated third charging policy is saved, the updated third charging policy is the second charging policy.
  • the policy control network element may not be sent to the session management network element.
  • the policy control network element may also send a charging policy update failure message or a charging policy creation failure message to the AF network element, so that the AF network element will no longer send the second charging policy to the policy control network element. Avoid billing errors and waste of resources, thereby improving communication efficiency.
  • the AF network element can send a service flow policy cancellation message to the policy control network element according to the received message, such as the charging policy update failure message or the charging policy creation failure message, so that the policy control network element can cancel the service flow policy according to the service flow policy.
  • the cancel message deletes the second charging policy to optimize policy configuration and release redundant resources.
  • the method may further include: the policy control network element sends a charging notification to the second device information.
  • the second device may specifically be an AF network element, and the charging notification message may be used to notify the remote terminal device to disconnect from the relay device, or be used to notify the remote terminal device to be disconnected from the relay device.
  • the service flow of the following device is disconnected.
  • the policy control network element may subscribe the connection status and/or service flow of the remote terminal device to the session management network element subscription service according to the state subscription indication in the first charging policy state, so that the session management network element can send a subscription notification message to the policy control network element after determining that the service flow of the remote terminal device is disconnected, and/or after the connection is disconnected.
  • the subscription notification message may be used to instruct the remote terminal device to disconnect from the relay device, or to instruct the remote terminal device to disconnect from the service flow of the relay device. In this way, the session management network element can send the charging notification message to the AF network element according to the subscription notification message.
  • the AF network element may determine whether to send a service flow policy cancellation message to the policy control network element according to the content of the charging notification message.
  • the AF network element may send a service flow policy cancel message to the policy control network element, that is, instruct the policy control network element to stop charging.
  • the policy control network element if the policy control network element locally stores the first charging policy, the policy control network element can delete the local The stored first charging policy; similarly, if the policy control network element locally stores the second charging policy obtained by updating the first charging policy, the policy control network element can delete the local The saved second billing policy is used to optimize policy configuration and release redundant resources.
  • the AF network element may not send the service flow policy cancellation message to the policy control network element, so that the policy control network element can still send the session
  • the management network element sends the first charging policy or the second charging policy to implement separate charging for other undisconnected services of the remote terminal device.
  • the services of the remote terminal equipment include: audio services and video services, and both audio services and video services are implemented in a relay access mode.
  • the policy control network element may still send the first charging policy or the second charging policy to the session management network element, so as to implement separate charging for the video service.
  • the services of the remote terminal equipment include audio services and video services.
  • the video service that requires relatively high service quality can be implemented through relay access, while the audio service that requires relatively low service quality can be through direct access.
  • the policy control network element may still send the first charging policy or the second charging policy to the session management network element, so as to implement separate charging for the audio service.
  • the following describes in detail how the policy control network element determines whether to send the first charging policy or the second charging policy to the session management network element according to the situation.
  • the policy control network element may send a message to the session management network element.
  • the first charging strategy is to implement separate charging for the remote terminal device.
  • the policy control network element receives the above-mentioned subscription notification message from the session management network element within a preset time period after obtaining the first charging policy, and the subscription notification message indicates that the service flow of the remote terminal equipment is interrupted. If enabled, the policy control network element can send the first charging policy to the session management network element.
  • the policy control network element may not send the first charging policy to the session management network element to save resource overhead.
  • the policy control network element may send the second charging policy to the session management network element.
  • the failure to receive the fourth indication information from the AF network element indicates that the second charging policy can be used for the charging of the device accessing the wireless network through the relay device, that is, for the charging of the remote terminal device.
  • the policy control network element may send the second charging policy to the session management network element.
  • the policy control network element may not send the second charging policy to the session management network element to save resource overhead.
  • the method may further include: the policy control network element sends the second indication information or the third indication information to the session management network element.
  • the second indication information may be used to indicate that the remote terminal device is allowed to use a PDU session that matches the first charging policy among the PDU sessions established by the relay device.
  • the third indication information may be used to indicate that the remote terminal device is not allowed to use the PDU session established by the relay device; or, the third indication information may be used to indicate that the remote terminal device is disconnected from the relay device.
  • the second indication information may include the PDU session identifier of the matched PDU session, so as to indicate that the remote terminal device is allowed to use the matched PDU session.
  • the third indication information may include: first sub-information and second sub-information.
  • the first sub-information may be used to indicate that: in the PDU session established by the relay device, there is no PDU session whose charging policy matches the first charging policy.
  • the second sub-information may be used to indicate that the remote terminal device is not allowed to use the PDU session created by the relay device; or, if the PDU session created by the relay device is not allowed When the number of sessions has reached the upper limit, the second sub-information can be used to indicate that the remote terminal device is disconnected from the relay device.
  • the session management network element can send the second indication information or the third indication information to the relay device, such as sending an N1 session establishment request message or an N1 session establishment request message to the relay device.
  • a session modification request message where the N1 session establishment request message or the N1 session modification request message carries the second indication information or the third indication information.
  • the relay device can create a PDU session according to the second indication information.
  • the relay device can also learn the reason why the remote terminal device is not allowed to use the established PDU session or the reason for disconnecting the relay device from the relay device according to the first sub-information in the third indication information.
  • the second sub-information accurately performs corresponding actions, such as disconnecting the connection with the remote terminal device, stopping charging the remote terminal device, and releasing communication resources, thereby improving the reliability of control and improving communication efficiency.
  • the PDU session matching the first charging policy may refer to a PDU session in which the charging policy matches the first charging policy among the PDU sessions established by the relay device, which is hereinafter referred to as a matching session.
  • the policy control network element can determine whether there is a matching session in the PDU sessions established by the relay device.
  • the above matching can be understood as all the policies in the first charging policy are the same as the charging policy of the PDU session.
  • the charging policy and the first charging policy of the PDU session 1 may be as shown in Table 1 below.
  • the charging policy and the first charging policy of the PDU session 2 may be as shown in Table 2 below.
  • the charging policy and the first charging policy of the PDU session 3 may be as shown in Table 3 below.
  • the charging policy and the first charging policy of the PDU session 4 may be as shown in Table 4 below.
  • the charging policy of PDU session 4 includes policies not included in the first charging policy 4, it does not affect the charging based on the first charging policy 4. It can also be considered that The charging policy of the PDU session 4 is the same as the first charging policy 4 .
  • the method may further include: the session management network element sends a charging data request (charging data request) message to the second device.
  • the second device may specifically be a CHF network element.
  • the session management network element may periodically send the charging data request message to the CHF network element according to the traffic usage of the remote terminal equipment periodically reported by the user plane network element.
  • the charging data request message can be used by the CHF network element to separately charge the remote terminal equipment.
  • the charging data request message can include a charging data update request (charging data request update) message or a charging data request initial request (charging data request initial) messages, without restrictions.
  • the charging data request message may carry the charging information and the first identifier of the remote terminal device, so that the CHF network element can separately charge the remote terminal device according to the charging information and the first identifier.
  • step S401 for the specific implementation manner of the first identifier, reference may be made to the relevant description in step S401, and details are not repeated here.
  • the CHF network element can directly charge the remote terminal device separately according to the charging information and the SUPI. If the first identifier is other identifiers of the remote terminal equipment, such as SUCI, GPSI, identifiers allocated by third-party service providers, etc., the CHF network element can determine the SUPI of the remote terminal equipment according to the corresponding relationship of the first identifier, and then according to the charging The information and this SUPI are billed separately for the remote terminal equipment.
  • the session management network element can determine, according to the PDU session identifier, whether the remote terminal device is using the PDU session created by the relay device, or whether the A PDU session newly created by the successor device for the remote terminal device (hereinafter referred to as a newly created PDU session).
  • the session management network element determines that the above-mentioned PDU session identifier exists in the recorded PDU session identifier, it can be determined that the remote terminal device uses the PDU session created by the relay device. If the session management network element determines that the above-mentioned PDU session identifier does not exist in the recorded PDU session identifiers, it can be determined that the remote terminal device uses the PDU session newly created by the relay device.
  • the charging data request message sent by the session management network element to the CHF network element may be a charging data request update message. If the remote terminal device uses a separately created PDU session, the charging data request message sent by the session management network element to the CHF network element may be an initial charging data request message.
  • the session management network element can also determine whether the PDU session is exclusively used by the remote terminal device or shared by the remote terminal device and other devices according to the above-mentioned PDU session identifier and the first identifier.
  • the session management network element determines that the PDU session is exclusively used by the remote terminal device. If the above-mentioned PDU session identifier is associated with the first identifier and is also associated with an identifier of another device, the session management network element determines that the PDU session is shared and used by the remote terminal device and the other device.
  • the charging data request message may carry the first identifier of the remote terminal device and the charging information of the remote terminal device.
  • the CHF network element can determine that the charging object is the remote terminal device according to the first identifier, and then separately charge the remote terminal device according to the charging information of the remote terminal device.
  • the charging data request message may also carry a session identifier (session identifier) and an identifier of a relay device (such as SUPI).
  • the session identifier is an identifier allocated by the CHF network element for the PDU session in advance to implement charging, and the session identifier can be used by the CHF network element to determine which PDU session is used by the charging object, that is, the remote terminal equipment.
  • the identifier of the relay device can be used by the CHF network element to determine that the PDU session is created by the relay device. In this way, the CHF network element can ensure the integrity of the charging information and avoid charging errors by recording the above session identifier and the identifier of the relay device.
  • the following formula (1) shows the format 1 of the charging data request message in the exclusive usage scenario.
  • Remote UE ID aa(1)
  • Session ID: 11 means: the session ID allocated by the CHF network element for the PDU session is 11;
  • SUPI: xx means: the SUPI of the relay device that creates the PDU session is xx;
  • Remote UE ID: aa means : The first identifier of the remote terminal equipment currently using the PDU session is aa;
  • Multiple Unit Usage: a1 means: the charging category of the remote terminal device aa in this cycle is a1 type of service,
  • “Rating Group: r1” means: the rate of a1 type of service is r1;
  • Used Unit Containe ⁇ yy ⁇ means: the traffic usage of a1 type of service is yy.
  • the CHF network element can determine that the object of independent charging is the remote terminal device aa according to the Remote UE ID being aa. In this way, the CHF network element can take the remote terminal equipment aa as the object, and determine the product value of the traffic yy of the a1 type of service and the rate r1, and the product value r1*yy is the a1 type of the remote terminal equipment aa in this cycle. Call charges, so as to realize separate billing for the remote terminal equipment aa.
  • the following formula (2) shows the format 2 of the charging data request message in the exclusive usage scenario.
  • Session ID: 11 means: the session ID allocated by the CHF network element for the PDU session is 11;
  • SUPI: xx means: the first ID of the remote terminal device is xx;
  • Multiple Unit Usage: a1 means: the charging category of the remote terminal device aa in this cycle is a1 type of service ,
  • “Rating Group:r1” means: the rate of a1 type of service is r1;
  • “Used Unit Containe ⁇ yy ⁇ ” means: the traffic consumption of a1 type of service is yy.
  • the CHF network element can determine that the object of independent charging is the remote terminal equipment aa according to the content of the SUPI of the information element as aa. In this way, the CHF network element can take the remote terminal equipment aa as the object, and determine the product value of the traffic yy of the a1 type of service and the rate r1, and the product value r1*yy is the a1 type of the remote terminal equipment aa in this cycle. Call charges, so that separate billing for the remote terminal equipment aa is also realized.
  • the charging data request message may carry the first identifier and charging information of each device.
  • the first identification and charging information of each device may be packaged into a container.
  • the CHF network element can separately charge multiple devices by analyzing the information in each container.
  • the charging data request message may also carry the session identifier and the identifier of the relay device.
  • the session identifier and the identifier of the relay device For the specific implementation and function of the session identifier and the identifier of the relay device, reference may be made to the foregoing first exemplary manner, which will not be repeated here.
  • formula (2) shows the format 2 of the charging data request message.
  • Session ID: 11 means: the session ID allocated by the CHF network element for the PDU session is 11;
  • SUPI: xx means: the SUPI of the relay device that creates the PDU session is xx;
  • ⁇ Remote UE ID: aa... Used Unit Container ⁇ yy ⁇ is the first container in the message;
  • Remote UE ID: bb...Used Unit Container ⁇ zz ⁇ is the second container in the message.
  • Remote UE ID: aa means: the first identifier of a remote terminal device currently sharing the PDU session is aa;
  • Multiple Unit Usage: a1 means: the charging category of the remote terminal device aa in this cycle is a1 business,
  • Heating Group: r1 means: the rate of the a1 type of service is r1;
  • Usersed Unit Containe ⁇ yy ⁇ means: the traffic consumption of the a1 type of service is yy.
  • the CHF network element can determine that the charging object is the remote terminal device aa according to the independent information element Remote UE ID in the first container being aa. In this way, the CHF network element can take the remote terminal equipment aa as the object, and determine the product value of the traffic yy of the a1 type of service and the rate r1, and the product value r1*yy is the a1 type of the remote terminal equipment aa in this cycle. Call charges, so that under shared use, one of the remote terminal equipment aa is charged separately.
  • Remote UE ID: bb means: the first identifier of another remote terminal device currently sharing the PDU session is bb;
  • Multiple Unit Usage: b1 means: the charging category of the remote terminal device bb in this cycle is the b1 type of service,
  • Heating Group :r2 means: the rate of the b1 type of service is r2;
  • Usersed Unit Containe ⁇ yy ⁇ means: the traffic consumption of the b1 type of service is zz.
  • the CHF network element can determine that the charging object is the remote terminal device bb according to the independent information element Remote UE ID in the second container being bb. In this way, the CHF network element can take the remote terminal equipment bb as the object to determine the product value of the traffic zz of the b1 type service and the rate r2, and the product value r2*zz is the b1 type service of the remote terminal equipment bb in this cycle. Call charges, so as to realize separate billing for another remote terminal device bb under shared use.
  • FIG. 5 is a second schematic flowchart of a communication method provided by an embodiment of the present application.
  • the communication method can be applied to the communication between PCF network elements, SMF network elements, UPF network elements, UDM network elements, UDR network elements, NEF network elements, and AF network elements shown in FIG. 1 and FIG. 2 .
  • the communication method may include the following steps:
  • the remote terminal device sends the first identifier or the second identifier to the SMF network element.
  • the SMF network element receives the first identification or the second identification from the remote terminal device.
  • the remote terminal device may send the first identification or the second identification to the SMF network element via the relay device, the RAN network element (not shown in FIG. 5 ), and the AMF network element (not shown in FIG. 5 ).
  • S501 may refer to the relevant description in S401, which will not be repeated here.
  • the SMF network element acquires the session management subscription data of the remote terminal device from the UDM network element.
  • the SMF network element may acquire the session management subscription data of the remote terminal device from the UDM network element according to the obtained first identifier or the second identifier, so as to be used for the charging policy configuration in S509.
  • S502 is a dotted line in FIG. 5, indicating that S502 is an optional step.
  • the SMF network element can execute S502; otherwise, after S501 , the SMF network element can directly send the first identifier of the remote terminal device to the PCF network element, that is, perform the following S503, and then the PCF network element obtains the session management subscription data of the remote terminal device according to the first identifier.
  • the SMF network element sends the first identifier to the PCF network element.
  • the PCF network element sends the first identifier to the UDM network element or the UDR network element.
  • the PCF network element sends the first indication information to the UDM network element or the UDR network element.
  • S505 may refer to the relevant description in the fourth implementation scenario, which will not be repeated here.
  • S504 and S506 are dotted lines in FIG. 5, indicating that S504 and S506 are optional steps.
  • the PCF network element acquiring the first charging policy from the UDM network element or the UDR network element is only an optional way
  • the PCF network element may also locally acquire the first charging policy from the PCF network element.
  • S505 is shown as a dotted line in FIG. 5, indicating that S505 is also an optional step.
  • the PCF network element can execute S505; otherwise, the PCF network element can S505 is not executed.
  • the execution order of S505 and S504 is not limited.
  • the UDM network element or the UDR network element sends the first charging policy to the PCF network element, and the PCF network element receives the first charging policy from the UDM network element or the UDR network element.
  • the UDM network element or the UDR network element may determine the session corresponding to the first identifier according to the first identifier Policy control subscription information, and send the session policy control subscription information to the PCF network element.
  • the PCF network element can receive the session policy control subscription information, and obtain the session policy association information of the remote terminal device therefrom, that is, obtain the first charging policy.
  • the UDM network element or the UDR network element can determine the The session policy control subscription information corresponding to the first identifier and the first indication information is sent to the PCF network element.
  • the PCF network element can acquire the session policy association information of the remote terminal device from the received session policy control subscription information, that is, acquire the first charging policy suitable for the relay access mode.
  • the PCF network element may also obtain the first charging policy from other network elements.
  • the specific implementation can be combined with the relevant descriptions in reference S402, the second implementation scenario, and the fourth implementation scenario, which will not be repeated here.
  • the PCF network element sends the first charging policy to the SMF network element.
  • the SMF network element sends the first reporting rule to the UPF network element according to the first charging policy.
  • the SMF network element determines the third charging policy of the remote terminal device according to the session management subscription data and the first charging policy.
  • the SMF network element sends the third reporting rule to the UPF network element according to the third charging policy.
  • S507 can refer to the relevant descriptions in S402 and the first implementation scenario
  • the specific implementation of S508 can refer to the related descriptions in S403
  • the specific implementation of S509 can refer to the related descriptions in the second implementation scenario
  • the specific implementation of S510 can refer to the related descriptions in the second implementation scenario.
  • S508-S510 are shown as dotted lines in FIG. 5, indicating that S508-S510 are optional steps. Wherein, if the SMF network element does not need to re-determine the charging policy of the remote terminal device, S508 can be executed; if the SMF network element needs to re-determine the charging policy of the remote terminal device, S509-S510 can be executed.
  • the AF network element sends the second charging policy to the PCF network element, and the PCF network element receives the second charging policy from the AF network element.
  • S511 may refer to the relevant description in the fifth implementation scenario, which will not be repeated here.
  • the AF network element may directly send the second charging policy to the PCF network element. If the AF network element belongs to a third-party service provider, the AF network element can send the second charging policy to the NEF network element (not shown in FIG. 5 ), and after verifying the authority of the AF network element through the NEF network element, the NEF network element will The second charging policy is forwarded to the PCF network element.
  • S511 may be executed at any time after the remote terminal device is accessed through the relay device.
  • this embodiment of the present application takes S511 executed after S506 as an example for description, but this is not a limitation.
  • the AF network element sends fourth indication information to the PCF network element, and the PCF network element receives the fourth indication information from the AF network element.
  • S512 is shown as a dotted line in FIG. 5, indicating that S512 is an optional step.
  • the AF network element can execute S512; otherwise, the AF network element may not execute S512.
  • the execution order of S511 and S512 is not limited.
  • the PCF network element sends the second charging policy to the SMF network element.
  • the PCF network element updates the first charging policy or the third charging policy according to the second charging policy.
  • the SMF network element sends the second reporting rule to the UPF network element according to the second charging policy.
  • the SMF network element By sending the second reporting rule to the UPF network element, the SMF network element enables the UPF network element to report the charging information of the remote terminal device according to the latest second reporting rule, so as to ensure the accuracy of charging.
  • S515 may refer to the relevant description in S403, which will not be repeated here.
  • the PCF network element sends a charging policy update failure message or a charging policy creation failure message to the AF network element.
  • the AF network element sends a service flow policy cancellation message to the PCF network element, and the PCF network element receives the service flow policy cancellation message from the AF network element.
  • S517 is shown as a dotted line in FIG. 5, indicating that S517 is an optional step. In other words, to optimize the configuration and release redundant resources, the AF network element can perform S517; otherwise, the AF network element may not perform S517.
  • S512-S517 are shown as dotted lines in FIG. 5, indicating that S512-S517 are optional steps, and the execution of S512-S515 and S516-S517 is an "or" relationship. For the indication information and the subscription notification message from the SMF network element, S512-S515 can be executed; otherwise, S516-S617 can be executed.
  • FIG. 6 is a third schematic flowchart of a communication method provided by an embodiment of the present application.
  • the communication method can be applied to the communication between PCF network elements, SMF network elements, CHF network elements, UPF network elements, UDM network elements, UDR network elements, NEF network elements, and AF network elements shown in FIG. 1 and FIG. 2 .
  • the communication method may include the following steps:
  • the remote terminal device sends the first identifier or the second identifier to the SMF network element.
  • the SMF network element receives the first identification or the second identification from the remote terminal device.
  • the remote terminal device may send the first identification or the second identification to the SMF network element via the relay device, the RAN network element (not shown in FIG. 6 ), and the AMF network element (not shown in FIG. 6 ).
  • S601 may refer to the relevant description in S401, which will not be repeated here.
  • the SMF network element acquires the session management subscription data of the remote terminal device from the UDM network element.
  • the SMF network element sends the first identifier to the PCF network element.
  • the PCF network element sends the first identifier to the UDM network element or the UDR network element.
  • the PCF network element sends the first indication information to the UDM network element or the UDR network element.
  • S602 can refer to the relevant descriptions in the second and third implementation scenarios
  • the specific implementation of S603 can refer to the relevant descriptions in S401
  • the specific implementation of S604 can refer to the related descriptions in S402 and the fourth implementation scenario
  • S602 is a dotted line in FIG. 6, indicating that S602 is an optional step.
  • the SMF network element can execute S602; otherwise, after S601 , the SMF network element may directly send the first identifier of the remote terminal device to the PCF network element, that is, perform S603.
  • S604 and S606 are dotted lines in FIG. 6, indicating that S604 and S606 are optional steps.
  • the PCF network element acquiring the first charging policy from the UDM network element or the UDR network element is only an optional way.
  • the PCF network element may also locally acquire the first charging policy from the PCF network element.
  • S605 is shown by a dotted line in FIG. 6, which means that S605 is also an optional step.
  • the PCF network element can execute S605; otherwise, the PCF network element can S605 is not executed.
  • the execution order of S605 and S604 is not limited.
  • the UDM network element or the UDR network element sends the first charging policy to the PCF network element, and the PCF network element receives the first charging policy from the UDM network element or the UDR network element.
  • the PCF network element sends the first charging policy to the SMF network element.
  • the SMF network element sends the first reporting rule to the UPF network element according to the first charging policy.
  • the SMF network element determines the third charging policy of the remote terminal device according to the session management subscription data and the first charging policy.
  • the SMF network element sends the third reporting rule to the UPF network element according to the third charging policy.
  • S606 can refer to the relevant descriptions in S506, S402, the first implementation scenario and the fourth implementation scenario
  • the specific implementation of S607 can refer to the relevant descriptions in S402 and the first implementation scenario
  • the specific implementation of S608 Reference may be made to the relevant description in S403, for the specific implementation of S609, reference may be made to the relevant description in the second implementation scenario, and for the specific implementation of S610, reference may be made to the relevant description in S403, which will not be repeated here.
  • S608-S610 are shown as dotted lines in FIG. 6, indicating that S608-S610 are optional steps. Wherein, if the SMF network element does not need to re-determine the charging policy of the remote terminal device, S608 can be executed; if the SMF network element needs to re-determine the charging policy of the remote terminal device, S609-S610 can be executed.
  • the UPF network element reports the charging information of the remote terminal equipment to the SMF network element, and the SMF network element receives the charging information of the remote terminal equipment from the UPF network element.
  • the UPF network element may periodically count the charging information of the remote terminal device according to the configured first charging rule or the third charging rule, and periodically report it to the SMF network element.
  • the charging information of the remote terminal device may include one or more of the following information: multiple unit usage (multiple unit usage), rate group, or used unit container (used unit container).
  • the rate group may include a rate of a PDU session
  • the PDU session is a PDU session used by a remote terminal device.
  • the multi-unit usage may include management parameters for managing quotas for the PDU session and/or reporting the PDU session usage.
  • the unit container used is used to represent the amount of traffic consumed by this PDU session in the current period.
  • the charging information may include: multi-unit usage, rate group, and used unit container as an example for introduction, but this is not a limitation.
  • the SMF network element sends a charging data request message to the CHF network element.
  • the AF network element sends the second charging policy to the PCF network element, and the PCF network element receives the second charging policy from the AF network element.
  • the AF network element sends fourth indication information to the PCF network element, and the PCF network element receives the fourth indication information from the AF network element.
  • S612 can refer to the relevant description of the ninth implementation scenario
  • the specific implementation of S613 can refer to the related description of the fifth implementation scenario
  • the specific implementation of S614 can refer to the sixth and seventh implementation scenarios. Relevant descriptions are not repeated here.
  • S614 is shown as a dotted line in FIG. 6, indicating that S614 is an optional step.
  • the AF network element can execute S614; otherwise, the AF network element may not execute S614.
  • S614 the execution order of S613 and S614 is not limited.
  • the PCF network element sends the second charging policy to the SMF network element.
  • the PCF network element updates the first charging policy or the third charging policy according to the second charging policy.
  • the SMF network element sends the second reporting rule to the UPF network element according to the second charging policy.
  • the PCF network element sends a charging policy update failure message or a charging policy creation failure message to the AF network element.
  • the AF network element sends a service flow policy cancellation message to the PCF network element, and the PCF network element receives the service flow policy cancellation message from the AF network element.
  • S619 is shown as a dotted line in FIG. 6 , indicating that S619 is an optional step. In other words, if the configuration is to be optimized and redundant resources are released, the AF network element can perform S619; otherwise, the AF network element may not perform S619.
  • S614-S619 are shown as dotted lines in FIG. 6, indicating that S614-S619 are optional steps as a whole, and the execution of S614-S617 and S618-S619 is an "or" relationship.
  • the fourth indication information and the subscription notification message from the SMF network element can execute S614-S617; otherwise, execute S618-S619.
  • FIG. 7 is a fourth schematic flowchart of a communication method provided by an embodiment of the present application.
  • the communication method can be applied to the communication between PCF network elements, SMF network elements, CHF network elements, UPF network elements, UDM network elements, UDR network elements, NEF network elements, and AF network elements shown in FIG. 1 and FIG. 2 .
  • the communication method includes the following steps:
  • the remote terminal device sends the first identifier or the second identifier to the SMF network element.
  • the SMF network element receives the first identification or the second identification from the remote terminal device.
  • the remote terminal device may send the first identifier or the second identifier to the SMF network element via the relay device, the RAN network element (not shown in FIG. 7 ), and the AMF network element (not shown in FIG. 7 ).
  • the SMF network element acquires the session management subscription data of the remote terminal device from the UDM network element.
  • the SMF network element sends the first identifier to the PCF network element.
  • the PCF network element sends the first identifier to the UDM network element or the UDR network element.
  • the PCF network element sends the first indication information to the UDM network element or the UDR network element.
  • S702 is a dotted line in FIG. 7, indicating that S702 is an optional step.
  • the SMF network element can execute S702; otherwise, after S701 , the SMF network element may directly send the first identifier of the remote terminal device to the PCF network element, that is, S703 is performed.
  • S704 and S706 are dotted lines in FIG. 7, indicating that S704 and S706 are optional steps.
  • the PCF network element obtains the first charging policy from the UDM network element or the UDR network element is only an optional way, for example, The PCF network element may also locally acquire the first charging policy from the PCF network element.
  • S705 is shown as a dotted line in FIG. 7, indicating that S705 is also an optional step.
  • the PCF network element can execute S705; otherwise, the PCF network element can S705 is not executed.
  • the execution order of S705 and S704 is not limited.
  • the UDM network element or the UDR network element sends the first charging policy to the PCF network element, and the PCF network element receives the first charging policy from the UDM network element or the UDR network element.
  • the PCF network element sends the first charging policy to the SMF network element.
  • S706 can refer to the relevant descriptions in S506, S402, the first implementation scenario, the second implementation scenario and the fourth implementation scenario, and the specific implementation of S707 can refer to S402 and the related descriptions in the first implementation scenario description, which will not be repeated here.
  • the PCF network element sends the second indication information or the third indication information to the SMF network element.
  • execution order of S708 and S707 is not limited.
  • the SMF network element sends the second indication information or the third indication information to the relay device.
  • the SMF network element sends the first reporting rule to the UPF network element according to the first charging policy.
  • the SMF network element determines the third charging policy of the remote terminal device according to the session management subscription data and the first charging policy.
  • the specific implementation of S709 can refer to the relevant description in the eighth implementation scenario
  • the specific implementation of S710 can refer to the related description in S403
  • the specific implementation of S711 can refer to the related descriptions in the second and third implementation scenarios. description, which will not be repeated here.
  • the execution order of S709, S710, and S711 is not limited.
  • the SMF network element sends the third reporting rule to the UPF network element according to the third charging policy.
  • S712 may refer to the relevant description in S403, which will not be repeated here.
  • S710-S712 are shown as dotted lines in FIG. 7, indicating that S710-S712 are optional steps. Wherein, if the SMF network element does not need to re-determine the charging policy of the remote terminal device, S710 can be executed; if the SMF network element needs to re-determine the charging policy of the remote terminal device, S711-S712 can be executed.
  • the UPF network element reports the charging information of the remote terminal equipment to the SMF network element, and the SMF network element receives the charging information of the remote terminal equipment from the UPF network element.
  • S713 may refer to S611, which will not be repeated here.
  • the SMF network element sends a charging data request message to the CHF network element.
  • the AF network element sends the second charging policy to the PCF network element, and the PCF network element receives the second charging policy from the AF network element.
  • the AF network element sends fourth indication information to the PCF network element, and the PCF network element receives the fourth indication information from the AF network element.
  • S715 may refer to the relevant description in the fifth implementation scenario
  • the specific implementation of S716 may refer to the relevant description in the sixth and seventh implementation scenarios.
  • S716 is shown as a dotted line in FIG. 7, indicating that S716 is an optional step.
  • the AF network element can execute S716; otherwise, the AF network element may not execute S716.
  • S716 the execution order of S716 and S715 is not limited.
  • the PCF network element sends the second charging policy to the SMF network element.
  • the PCF network element updates the first charging policy according to the second charging policy.
  • the SMF network element sends the second reporting rule to the UPF network element according to the second charging policy.
  • the PCF network element sends a charging policy update failure message or a charging policy creation failure message to the AF network element.
  • the AF network element sends a service flow policy cancellation message to the PCF network element, and the PCF network element receives the service flow policy cancellation message from the AF network element.
  • the specific implementation of S717 and S718 can refer to the relevant descriptions in the sixth and seventh implementation scenarios
  • the specific implementation of S719 can refer to the relevant descriptions in S403
  • the specific implementation of S720 and S721 can refer to the sixth and seventh scenarios. The relevant descriptions in these implementation scenarios will not be repeated here.
  • S721 is shown as a dotted line in FIG. 7 , indicating that S721 is an optional step. In other words, to optimize configuration and release redundant resources, the AF network element can perform S721; otherwise, the AF network element may not perform S721.
  • S716-S721 are shown as dotted lines in Figure 7, indicating that S716-S721 are optional steps as a whole, and the execution of S716-S719 and S720-S721 is an "or" relationship.
  • the fourth indication information and the subscription notification message from the SMF network element can execute S716-S719; otherwise, execute S720-S721.
  • the policy control network element can obtain the first identifier of the remote terminal device from the session management network element, the policy control network element can send the first identifier of the remote terminal device to the session management network element according to the first identifier. fee strategy.
  • the session management network element can configure the first reporting rule of the remote terminal device for the user plane network element according to the first charging policy, so that after the remote terminal device accesses the wireless network through the relay device, the user plane network element can The first reporting rule is to report the charging information of the remote terminal equipment to the network element of the charging function, so as to realize separate charging for the remote terminal equipment.
  • the communication method provided by the embodiment of the present application has been described in detail above with reference to FIG. 4 to FIG. 7 .
  • a communication apparatus for executing the communication method provided by the embodiment of the present application will be described in detail below with reference to FIG. 8 .
  • FIG. 8 is a first structural schematic diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication apparatus 800 includes: a processing module 801 and a transceiver module 802 .
  • FIG. 8 only shows the main components of the communication device 800.
  • the communication apparatus 800 can be applied to the communication systems shown in FIG. 1 and FIG. 2, and execute the function of the policy control network element in the communication method shown in FIG. 4, or, execute the functions of FIG. Functions of PCF network elements in the communication method shown in 7.
  • the processing module 801 is used to execute S402, S514, S616, and S718.
  • the transceiver module 802 is used for executing S504-S507, S511-S513, S516-S517, S604-S607, S613-S615, S618-S619, S704-S708, S715-S717, S720-S721.
  • the communication device 800 may be a policy control network element or a PCF network element, or may be a chip (system) or other components or components provided in the policy control network element or PCF network element, or may include the policy control network element Element or PCF network element device; or, the communication device 800 may also be a network device, or a chip (system) or other components or components that can be provided in the network device, or a device including the network device.
  • the communication apparatus 800 may be applied to the communication systems shown in FIG. 1 and FIG. 2 to perform the function of the session management network element in the communication method shown in FIG. The functions of the SMF network elements in the communication method shown in FIG. 7 .
  • the processing module 801 is used to execute S403, S509, S609, and S711, and also used to control the transceiver module 802 to execute S502, S508, S510, S515, S602, S608, S610, S617, S702, S712, and S719.
  • the transceiver module 802 is used to execute S401, S501, S503, S601, S603, S611-S612, S701, S703, S709, and S713-S714.
  • the communication apparatus 800 may be a session management network element or an SMF network element, or may be a chip (system) or other components or components provided in the session management network element or SMF network element, or may include the session management network element.
  • the communication apparatus 800 may also be a network device, or a chip (system) or other components or components that may be provided in the network device, or an apparatus including the network device.
  • the transceiver module 802 may include a receiving module and a transmitting module (not shown in FIG. 8 ).
  • the transceiver module 802 is used to implement the sending function and the receiving function of the communication device 800 .
  • the communication apparatus 800 may further include a storage module (not shown in FIG. 8 ), where the storage module stores programs or instructions.
  • the processing module 801 executes the program or instruction
  • the communication device 800 can execute the function of the session management network element in the communication method shown in FIG. 4 , or execute the SMF network element in the communication method shown in FIG. 5 to FIG. 7 . function.
  • the processing module 801 involved in the communication device 800 may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing unit;
  • the transceiver module 802 may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver module Receiver or Transceiver Unit.
  • FIG. 9 is a second schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device, or may be a chip (system) or other components or assemblies that can be provided in the terminal device or the network device.
  • the communication apparatus 900 may include a processor 901 .
  • the communication device 900 may further include a memory 902 and/or a transceiver 903 .
  • the processor 901 is coupled with the memory 902 and the transceiver 903, such as can be connected through a communication bus.
  • Each component of the communication device 900 will be described in detail below with reference to FIG. 9 :
  • the processor 901 is the control center of the communication device 900, which may be one processor or a general term for multiple processing elements.
  • the processor 901 is one or more central processing units (CPUs), may also be a specific integrated circuit (application specific integrated circuit, ASIC), or is configured to implement one or more of the embodiments of the present application
  • An integrated circuit such as: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate array (field programmable gate array, FPGA).
  • the processor 901 may execute various functions of the communication device 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902 .
  • the processor 901 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9 .
  • the communication apparatus 900 may also include multiple processors, for example, the processor 901 and the processor 904 shown in FIG. 2 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 902 is used to store a computer program for executing the solution of the present application, and is executed by the processor 901 to implement the methods provided by the above method embodiments, for example, to execute the policy function network element or SMF in the above method embodiments.
  • the processor 901 For the method of the network element, reference may be made to the foregoing method embodiments, which will not be repeated here.
  • memory 902 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of static storage devices that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices for instructions which may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disks storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or capable of carrying or storing desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 902 may be integrated with the processor 901, or may exist independently, and be coupled to the processor 901 through an interface circuit (not shown in FIG. 9) of the communication device 900, which is not specifically limited in this embodiment of the present application.
  • the transceiver 903 is used for communication with other communication devices 800 .
  • the communication apparatus 900 is a terminal device, and the transceiver 903 may be used to communicate with a network device or communicate with another terminal device.
  • the communication apparatus 900 is a network device, and the transceiver 903 can be used to communicate with a terminal device or communicate with another network device.
  • transceiver 903 includes a receiver and a transmitter (not shown separately in Figure 9). Among them, the receiver is used to realize the receiving function, and the transmitter is used to realize the sending function.
  • the transceiver 903 and the processor 901 are integrated together, or can exist independently, and are coupled to the processor 901 through an interface circuit (not shown in FIG. 9 ) of the communication device 900, which is not specifically described in this embodiment of the present application limited.
  • the structure of the communication device 900 shown in FIG. 9 does not constitute a limitation on the communication device, and an actual communication device may include more or less components than those shown in the figure, or combine some components, or Different component arrangements.
  • An embodiment of the present application further provides a chip system, including: a processor, where the processor is coupled with a memory, the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the The chip system implements the method in any of the foregoing method embodiments.
  • the number of processors in the chip system may be one or more.
  • the processor can be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips.
  • the setting method of the processor is not particularly limited.
  • the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller).
  • controller unit, MCU it can also be a programmable logic device (PLD) or other integrated chips.
  • Embodiments of the present application provide a communication system.
  • the communication system includes one or more network devices; further, the communication system may also include the above-mentioned one or more terminal devices, for example, a remote terminal device and a relay device.
  • processors in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory Fetch memory
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware (eg, circuits), firmware, or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • At least one means one or more, and “plurality” means two or more.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one item (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

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)

Abstract

本申请提供一种通信方法及装置，能够解决在接入远程终端设备后，计费功能网元无法对该远程终端设备单独计费的问题，可应用于LTE、NR、5G等系统中。该方法包括：策略控制网元接收来自网元的远程终端设备的第一标识，并根据第一标识向会话管理网元发送远程终端设备的第一计费策略。

Description

通信方法及装置
本申请要求于2020年12月09日提交国家知识产权局、申请号为202011433627.8、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法及装置。
背景技术
为了向网络覆盖区域外的终端设备提供服务，引入了邻近服务(proximity-based services，ProSe)通信。比如，第五代(5th generation，5G)通信系统中，处于无线网络覆盖区域外的终端设备(下文统称为远程终端设备，remote terminal)，可以通过中继(relay)设备，如处于无线网络覆盖区域内的另一终端设备，接入无线网络，以接收网络服务。其中，中继设备可以通过PC5接口与远程终端设备通信，且通过Uu接口与无线网络通信。
然而，在远程终端设备通过中继设备接入无线网络的情况下，用户面功能(user plane function，UPF)网元向计费功能(charging function，CHF)网元上报的仍然是中继设备的计费信息，CHF网元无法针对远程终端设备单独计费。
发明内容
本申请实施例提供一种通信方法及装置，以实现在远程终端设备接入无线网络后，计费功能网元能够针对该远程终端设备进行单独计费。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种通信方法。该通信方法可以包括：策略控制网元接收来自网元的远程终端设备的第一标识，并根据第一标识向会话管理网元发送远程终端设备的第一计费策略。
其中，远程终端设备和中继设备都可以是手机、电脑、虚拟现实终端设备、增强现实终端设备、车载终端等；或者，远程终端设备也可以是一些应用领域中的终端设备，如医疗、无人驾驶、智能电网智慧城市等应用领域中的终端设备。
此外，远程终端设备可以通过中继设备接入无线网络。比如，远程终端设备可以位于网络的信号覆盖区域以外，并通过与中继设备的无线连接而接入无线网络。
再者，无线网络可以是移动通信系统，如第4代、第5代或第6代移动通信系统中的蜂窝网络。
基于第一方面和下述第二方面所述的通信方法，由于策略控制网元能够从会话管理网元获得远程终端设备的第一标识，因此，策略控制网元可根据第一标识而向会话管理网元发送远程终端设备的第一计费策略。
如此，会话管理网元便可根据第一计费策略为用户面网元配置远程终端设备的第一上报规则，以便用户面网元在远程终端设备通过中继设备接入无线网络后，可根据第一上报规则，向计费功能网元上报远程终端设备的流量用量，从而实现根据流量用 量对远程终端设备单独计费。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：会话计费规则、或业务计费规则。由于会话计费规则是会话，如协议数据单元PDU会话维度的计费规则，而业务计费规则是业务，如视频、音频、浏览网页等业务维度的计费规则，因此，会话管理网元可选择维度更适合实际业务的计费规则，以实现更准确地计费。
可选地，第一计费策略还可以包括：状态订阅指示。其中，状态订阅指示用于订阅远程终端设备的连接状态，和/或，业务流状态。
如此，策略控制网元便可实时掌握远程终端设备的连接状态，并通过会话管理网元通知用户面网元，可以避免因用户面网元未能及时获知远程终端设备的连接状态，而向会话管理网元上报错误的流量用量，比如多报流量用量或少报流量用量，从而导致会话管理网元对远程终端设备的计费错误的问题，进而可以提高计费的准确性。
可选地，第一方面所述的方法还可以包括：策略控制网元根据第一标识，获取第一计费策略。可理解到，由于标识和策略之间具备对应关系，因此，通过第一标识能够快速且便捷地获取第一计费策略。
进一步地，策略控制网元根据第一标识，获取第一计费策略，可以包括：策略控制网元根据第一标识，从第一设备获取第一计费策略。其中，第一设备可以包括：策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。可理解到，由于第一计费策略可存储到各网元，因此，可提高第一计费策略存储的可靠性。
一种可能的设计方案中，第一方面所述的方法还可以包括：策略控制网元向第二设备发送第一指示信息。其中，第二设备可以包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。其中，第一指示信息用于指示：远程终端设备通过中继设备接入无线网络。
如此，第二设备根据第一指示信息，能够快速便捷地确定适用于中继接入的第一计费策略。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：第一标识、或中继设备为远程终端设备分配的端口号。
如此，会话管理网元为用户面网元配置的第一上报规则也可以包括第一标识，和/或，端口号，使得用户面网元可准确上报远程终端设备的流量用量。
一种可能的设计方案中，策略控制网元接收来自会话管理网元的远程终端设备的第一标识可以包括：策略控制网元接收来自会话管理网元的第一消息。其中，第一消息携带第一标识，第一消息可以为会话策略关联建立请求消息或会话策略关联更改请求消息。
如此，通过复用会话策略关联建立请求消息或会话策略关联更改请求消息来发送第一标识，可减少信令开销，以提高通信效率。
一种可能的设计方案中，第一标识可以包括如下一项或多项：运营商为远程终端设备分配的签约永久标识SUPI、一般公共订阅标识GPSI、用户隐藏标识SUCI、中继设备为远程终端设备分配的端口号、或第三方服务商为远程终端设备分配标识，如QQ号、微信号等，且远程终端设备的上述各项标识间具有对应关系。
如此，无论采用何种来源以及何种类型的第一标识，基于该对应关系都可确定该远程终端设备用于计费的标识，从而实现对远程终端设备的单独计费，进而提高计费的可靠性。
一种可能的设计方案中，第一方面所述的方法还可以包括：当中继设备已建立的协议数据单元PDU会话中，存在计费策略与第一计费策略匹配的PDU会话时，策略控制网元向会话管理网元发送第二指示信息。其中，第二指示信息用于指示：允许远程终端设备使用匹配的PDU会话。
如此，通过使用匹配的PDU会话，不仅可实现对该远程终端设备的单独计费，还可减少资源开销，以提高通信效率。
另一种可能的设计方案中，第一方面所述的方法还可以包括：当中继设备已建立的协议数据单元PDU会话中，不存在计费策略与第一计费策略与匹配的PDU会话时，策略控制网元向会话管理网元发送第三指示信息。
其中，第三指示信息可用于指示：不允许远程终端设备使用已建立的PDU会话。
如此，会话管理网元可根据第三指示信息，创建计费策略与第一计费策略匹配的PDU会话供远程终端设备使用，以实现在已建立的PDU会话的计费策略不匹配时，也能够准确地对该远程终端设备单独计费。
以及，第三指示信息还可用于指示：远程终端设备与中继设备断开连接。
如此，会话管理网元可根据第三指示信息，断开中继设备与远程终端设备间的连接，停止对远程终端设备计费，并释放通信资源，从而提高通信效率。
可选地，第三指示信息可以包括：第一子信息和第二子信息。其中，第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话。其中，第二子信息可以用于指示：不允许远程终端设备使用已建立的PDU会话；或者，第二子信息还可以用于指示：远程终端设备与中继设备断开连接。
如此，中继设备根据第一子信息获知不允许远程终端设备使用已建立的PDU会话或者断开连接的原因后，根据第二子信息，便可准确地执行相应的动作，如创建PDU会话或者断开与远程终端设备间的连接，从而提高控制的可靠性。
一种可能的设计方案中，第一方面所述的方法还可以包括：策略控制网元接收来自应用功能网元的第二计费策略。
其中，若第二计费策略用于通过中继设备接入无线网络的设备的计费，则策略控制网元向会话管理网元发送第二计费策略。
如此，可实现动态更新计费策略，从而实现更准确地计费。
若第二计费策略不用于通过中继设备接入无线网络的设备的计费，则策略控制网元向应用功能网元发送计费策略更新失败消息或计费策略创建失败消息，以便应用功能网元不再向策略控制网元发送该第二计费策略，避免计费错误及资源浪费，从而提高通信效率。
可选地，第一方面所述的方法还可以包括：策略控制网元接收来自应用功能网元的第四指示信息。其中，第四指示信息用于指示：第二计费策略不用于通过中继设备接入无线网络的设备的计费。
如此，策略控制网元根据第四指示信息，可不向会话管理网元发送该第二计费策 略，避免计费错误及资源浪费。
可选地，第二计费策略用于通过中继设备接入无线网络的设备的计费，第一方面所述的方法还可以包括：策略控制网元根据第二计费策略，更新第一计费策略。
如此，通过动态更新计费策略，可实现更准确地计费。
一种可能的设计方案中，远程终端设备与中继设备连接，第一计费策略处于激活状态；或者，远程终端设备与中继设备断开连接，第一计费策略处于非激活状态。如此，策略控制网元通过第一计费策略的状态，可确定哪些策略在使用而哪些策略未使用，以更灵活地调度资源，如配置或释放资源，以提高通信效率。
一种可能的设计方案中，远程终端设备与中继设备的连接或业务流断开，第一方面所述的方法还可以包括：策略控制网元向应用功能网元发送计费通知消息。其中，计费通知消息用于通知远程终端设备的连接或业务流断开。
如此，应用功能网元也能够获知远程终端设备的连接状态或业务流状态，避免应用功能网元因未获知远程终端设备的连接状态或业务流状态，继续发数据而浪费资源，从而提高通信效率。
第二方面，提供一种通信方法。该通信方法可以包括：会话管理网元向策略控制网元发送远程终端设备的第一标识，从接收来自策略控制网元的远程终端设备的第一计费策略，从而根据第一计费策略，向用户面网元发送第一上报规则。其中，远程终端设备通过中继设备接入无线网络；第一上报规则用于用户面网元上报远程终端设备的流量用量。
一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元向计费功能网元发送计费数据请求消息，计费数据请求消息携带有第一标识。
如此，计费功能网元根据该第一标识便可对该远程终端设备单独计费。
可选地，计费数据请求消息还携带有中继设备的标识。
如此，计费功能网元根据远程终端设备的第一标识和中继设备的标识，便可区分计费，以保证计费的准确性。
可选地，计费数据请求消息携带有每个远程终端设备的如下一项或多项信息：多单元用量、费率组、或使用的单元容器。
可理解到，由于同一计费数据请求消息可携带每个远程终端设备计费所需的信息，如此，可实现根据同一计费数据请求消息，而对多个远程终端设备分别计费。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：会话计费规则、或业务计费规则。
可选地，第一计费策略还可以包括：状态订阅指示。其中，状态订阅指示用于策略控制网元订阅远程终端设备的连接状态。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：第一标识、或中继设备为所述远程终端设备分配的端口号。
一种可能的设计方案中，第一计费策略为策略控制网元根据第一标识从第一设备获取。其中，第一设备可以包括：策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
一种可能的设计方案中，会话管理网元向策略控制网元发送远程终端设备的第一 标识，可以包括：会话管理网元向策略控制网元发送第一消息。其中，第一消息携带所述第一标识，第一消息可以为会话策略关联建立请求消息或会话策略关联更改请求消息。
一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元接收来自远程终端设备的第二标识，并向统一数据管理网元发送第二标识；从而接收来自统一数据管理网元的第一标识。
如此，即使会话管理网元本地没有第一标识，也可通过第二标识从统一数据管理网元获取该第一标识，从而提高计费的可靠性。
可选地，第一标识可以包括：签约永久标识SUPI。可理解到，由于SUPI的唯一性很强，因此，通过SUPI能够准确地对远程终端设备单独计费。
可选地，第二标识可以包括如下一项或多项：运营商分配的一般公共订阅标识GPSI、用户隐藏标识SUCI、应用功能网元为远程终端设备分配的标识、或第三方服务商为远程终端设备分配标识，如QQ号、微信号等。
如此，无论采用何种来源以及何种类型的第二标识，都可通过第二标识获取到第一标识，从而提高计费的可靠性。
一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元接收来自策略控制网元的第二计费策略，并根据第二计费策略，向用户面网元发送第二上报规则。其中，第二计费策略为远程终端设备的计费策略，第二上报规则用于用户面网元上报远程终端设备的流量用量。
如此，实现同步更新用户面网元的上报规则，以确保用户面网元能够准确上报远程终端设备的流量用量。
一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元从统一数据管理网元获取远程终端设备的会话管理签约数据，并根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略；从而根据第三计费策略，向用户面网元发送第三上报规则。其中，第三上报规则用于用户面网元上报远程终端设备的流量用量。
如此，通过综合会话管理签约数据和第一计费策略，可确定策略更完善的第三计费策略，以实现更准确地计费。
可选地，会话管理签约数据中可以包括：协议数据单元PDU会话计费特性信息，PDU会话计费特性信息中可以包括：第一部分信息，第一计费策略的会话计费规则可以包括：第二部分信息和第三部分信息，第三计费策略中的会话计费规则可以包括：第一部分信息和第二部分信息。其中，第一部分信息与第三部分信息的类型相同且内容不相同，第一部分信息与第二部分信息的类型和内容均不相同。
如此，确定的第三计费策略可包含PDU会话计费特性信息中所没有的信息，使得第三计费策略更完善，以实现更准确地计费。
可选地，第二方面所述的方法还可以包括：会话管理网元向统一数据管理网元发送第五指示信息。其中，第五指示信息用于指示：远程终端设备通过中继设备接入无线网络。
如此，统一数据管理网元根据第五指示信息，能够快速便捷地确定适用于中继接 入的会话管理签约数据。
一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元接收来自策略控制网元的第二指示信息，并向中继设备发送第二指示信息。其中，第二指示信息用于指示：允许远程终端设备使用中继设备已建立的协议数据单元PDU会话。
如此，通过使用匹配的PDU会话，不仅可实现对该远程终端设备的单独计费，还可减少资源开销，从而提高通信效率。
可选地，第二指示信息携带在N1消息中。
如此，通过复用N1消息来发送第二指示信息，可减少信令开销，从而提高通信效率。
另一种可能的设计方案中，第二方面所述的方法还可以包括：会话管理网元接收来自所述策略控制网元的第三指示信息，并向中继设备发送第三指示信息。其中，第三指示信息用于指示：不允许远程终端设备使用中继设备已建立的协议数据单元PDU会话；或者，第三指示信息用于指示：远程终端设备与中继设备断开连接。
可选地，第三指示信息携带在N1消息中。
如此，通过复用N1消息来发送第三指示信息，可减少信令开销，从而提高通信效率。
可选地，第三指示信息可以包括：第一子信息和第二子信息。其中，第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话；第二子信息用于指示：不允许远程终端设备使用已建立的PDU会话；或者，第二子信息用于指示：远程终端设备与中继设备断开连接。
此外，第二方面所述的通信方法的技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第三方面，提供一种通信装置。该通信装置可以包括：收发模块和处理模块，收发模块，用于接收来自会话管理网元的远程终端设备的第一标识；处理模块，用于根据第一标识，控制收发模块向会话管理网元发送第一计费策略。其中，远程终端设备通过中继设备接入无线网络。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：会话计费规则、或业务计费规则。
可选地，第一计费策略还可以包括：状态订阅指示。其中，状态订阅指示用于订阅远程终端设备的连接状态。
可选地，处理模块，还用于根据第一标识，控制收发模块获取第一计费策略。
进一步地，处理模块，还用于根据第一标识，控制收发模块从第一设备获取第一计费策略。其中，第一设备可以包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
一种可能的设计方案中，收发模块，还用于向第二设备发送第一指示信息。其中，第二设备可以包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。其中，第一指示信息用于指示：远程终端设备通过中继设备接入无线网络。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：第一标识、或中继设备为远程终端设备分配的端口号。
一种可能的设计方案中，收发模块，还用于接收来自会话管理网元的第一消息。其中，第一消息携带第一标识，第一消息为会话策略关联建立请求消息或会话策略关联更改请求消息。
一种可能的设计方案中，第一标识可以包括如下一项或多项：签约永久标识SUPI、一般公共订阅标识GPSI、用户隐藏标识SUCI、或中继设备为远程终端设备分配的端口号。
一种可能的设计方案中，当中继设备已建立的协议数据单元PDU会话中，存在计费策略与第一计费策略匹配的PDU会话时，收发模块，还用于向会话管理网元发送第二指示信息。其中，第二指示信息用于指示：允许远程终端设备使用匹配的PDU会话。
另一种可能的设计方案中，当中继设备已建立的协议数据单元PDU会话中，不存在计费策略与第一计费策略与匹配的PDU会话时，收发模块，还用于向会话管理网元发送第三指示信息。其中，第三指示信息用于指示：不允许远程终端设备使用已建立的PDU会话；或者，第三指示信息用于指示：远程终端设备与中继设备断开连接。
可选地，第三指示信息可以包括：第一子信息和第二子信息。其中，第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话。其中，第二子信息用于指示：不允许远程终端设备使用已建立的PDU会话；或者，第二子信息用于指示：远程终端设备与中继设备断开连接。
一种可能的设计方案中，收发模块，还用于接收来自应用功能网元的第二计费策略。若第二计费策略用于通过中继设备接入无线网络的设备的计费，则收发模块，还用于向会话管理网元发送第二计费策略；或者，若第二计费策略不用于通过中继设备接入无线网络的设备的计费，则收发模块，还用于向应用功能网元发送计费策略更新失败消息或计费策略创建失败消息。
可选地，收发模块，还用于接收来自应用功能网元的第四指示信息，其中，第四指示信息用于指示：第二计费策略不用于通过中继设备接入无线网络的设备的计费。
可选地，第二计费策略用于通过中继设备接入无线网络的设备的计费，处理模块，还用于根据第二计费策略，更新第一计费策略。
一种可能的设计方案中，远程终端设备与中继设备连接，第一计费策略处于激活状态；或者，远程终端设备与中继设备断开连接，第一计费策略处于非激活状态。
一种可能的设计方案中，远程终端设备与中继设备的连接或业务流断开，收发模块，还用于向应用功能网元发送计费通知消息。其中，计费通知消息用于通知远程终端设备的连接或业务流断开。
可选地，收发模块可以包括发送模块和接收模块。其中，发送模块用于实现第三方面所述的装置的发送功能，接收模块则用于实现该装置的接收功能。
可选地，第三方面所述的装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得该装置可以执行第一方面所述的方法。
需要说明的是，第三方面所述的通信装置可以为第一方面中的策略控制网元，或者可设置于该策略控制网元中的芯片(系统)或其他部件或组件，或者包含该策略控制网元的装置；或者，该通信装置还可以为网络设备，或者可设置于该网络设备中的芯片(系统)或其他部件或组件，或者包含该网络设备的装置。
此外，第三方面所述的装置的技术效果可以参考第一方面所述的方法的技术效果，此处不再赘述。
第四方面，提供一种通信装置。该通信装置可以包括：收发模块和处理模块。收发模块，用于向策略控制网元发送远程终端设备的第一标识，并接收来自策略控制网元的远程终端设备的第一计费策略。处理模块，用于根据第一计费策略，控制收发模块向用户面网元发送第一上报规则。其中，远程终端设备通过中继设备接入无线网络。其中，第一上报规则用于用户面网元上报远程终端设备的流量用量。
一种可能的设计方案中，收发模块，还用于向计费功能网元发送计费数据请求消息，计费数据请求消息携带有第一标识。
可选地，计费数据请求消息还携带有中继设备的标识。
可选地，计费数据请求消息携带有每个远程终端设备的如下一项或多项信息：多单元用量、费率组、或使用的单元容器。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：会话计费规则、或业务计费规则。
可选地，第一计费策略还可以包括：状态订阅指示。其中，状态订阅指示用于策略控制网元订阅远程终端设备的连接状态。
一种可能的设计方案中，第一计费策略可以包括如下一项或多项：第一标识、或中继设备为远程终端设备分配的端口号。
一种可能的设计方案中，第一计费策略为策略控制网元根据第一标识从第一设备获取。其中，第一设备可以包括：策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
一种可能的设计方案中，收发模块，还用于向策略控制网元发送第一消息。其中，第一消息携带第一标识，第一消息可以为会话策略关联建立请求消息或会话策略关联更改请求消息。
一种可能的设计方案中，收发模块，还用于接收来自远程终端设备的第二标识，并向统一数据管理网元发送第二标识，以及接收来自统一数据管理网元的第一标识。
可选地，第一标识可以包括：签约永久标识SUPI。
可选地，第二标识可以包括如下一项或多项：一般公共订阅标识GPSI、用户隐藏标识SUCI、或应用功能网元为远程终端设备分配的标识。
一种可能的设计方案中，收发模块，还用于接收来自策略控制网元的第二计费策略。处理模块，还用于根据第二计费策略，控制收发模块向用户面网元发送第二上报规则。其中，第二计费策略为远程终端设备的计费策略。其中，第二上报规则用于用户面网元上报流量用量。
一种可能的设计方案中，处理模块，还用于控制收发模块从统一数据管理网元获取远程终端设备的会话管理签约数据；并根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略；以及根据第三计费策略，控制收发模块向用户面网元发送第三上报规则。其中，第三上报规则用于用户面网元上报流量用量。
可选地，会话管理签约数据中可以包括：协议数据单元PDU会话计费特性信息。PDU会话计费特性信息中可以包括：第一部分信息。第一计费策略的会话计费规则可 以包括：第二部分信息和第三部分信息。其中，第一部分信息与第三部分信息的类型相同且内容不相同，第一部分信息与第二部分信息的类型和内容均不相同。第三计费策略中的会话计费规则可以包括：第一部分信息和第二部分信息。
可选地，收发模块，还用于向统一数据管理网元发送第五指示信息。其中，第五指示信息用于指示：远程终端设备通过中继设备接入无线网络。
一种可能的设计方案中，收发模块，还用于接收来自策略控制网元的第二指示信息，并向中继设备发送第二指示信息。其中，第二指示信息用于指示：允许远程终端设备使用中继设备已建立的协议数据单元PDU会话。
可选地，第二指示信息携带在N1消息中。
另一种可能的设计方案中，收发模块，还用于接收来自策略控制网元的第三指示信息，并向中继设备发送第三指示信息。其中，第三指示信息用于指示：不允许远程终端设备使用中继设备已建立的协议数据单元PDU会话；或者，第三指示信息用于指示：远程终端设备与中继设备断开连接。
可选地，第三指示信息携带在N1消息中。
可选地，第三指示信息可以包括：第一子信息和第二子信息。其中，第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话；第二子信息用于指示：不允许远程终端设备使用已建立的PDU会话；或者，第二子信息用于指示：远程终端设备与中继设备断开连接。
可选地，收发模块可以包括发送模块和接收模块。其中，发送模块用于实现第四方面所述的装置的发送功能，接收模块则用于实现该装置的接收功能。
可选地，第四方面所述的装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得该装置可以执行第二方面所述的方法。
需要说明的是，第四方面所述的装置可以是网络设备，也可以是可设置于网络设备中的芯片(系统)或其他部件或组件，还可以是包含网络设备的装置，本申请对此不做限定。
此外，第四方面所述的装置的技术效果可以参考第二方面所述的方法的技术效果，此处不再赘述。
第五方面，提供一种通信装置。该通信装置可以包括：处理器和存储器。存储器用于存储计算机指令，当处理器执行该指令时，以使该装置执行如第一方面所述的通信方法。
在一种可能的设计方案中，第五方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第五方面所述的通信装置与其他通信装置通信。
在本申请中，第五方面所述的通信装置可以为第一方面中的策略控制网元，或者可设置于该策略控制网元中的芯片(系统)或其他部件或组件，或者包含该策略控制网元的装置；或者，该通信装置还可以为网络设备，或者可设置于该网络设备中的芯片(系统)或其他部件或组件，或者包含该网络设备的装置。
此外，第五方面所述的通信装置的技术效果可以参考第一方面所述的通信方法的技术效果，此处不再赘述。
第六方面，提供一种通信装置。该通信装置可以包括：处理器和存储器。存储器用于存储计算机指令，当处理器执行该指令时，以使该装置执行如第二方面所述的通信方法。
在一种可能的设计方案中，第六方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或接口电路。该收发器可以用于第六方面所述的通信装置与其他通信装置通信。
在本申请中，第六方面所述的通信装置可以为第二方面中的会话管理网元，或者可设置于该会话管理网元中的芯片(系统)或其他部件或组件，或者包含该策略控制网元的装置；或者，该通信装置还可以为网络设备，或者可设置于该网络设备中的芯片(系统)或其他部件或组件，或者包含该网络设备的装置。
此外，第六方面所述的通信装置的技术效果可以参考第二方面所述的通信方法的技术效果，此处不再赘述。
第七方面，提供一种计算机可读存储介质。该计算机可读存储介质可以包括：计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第一方面或第二方面所述的通信方法。
第八方面，提供一种计算机程序产品。该计算机程序产品可以包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得计算机执行如第一方面或第二方面所述的通信方法。
第九方面，提供一种通信系统。该通信系统可以包括一个或多个终端设备，以及一个或多个网络设备。
附图说明
图1为本申请实施例提供的通信系统的架构示意图一；
图2为本申请实施例提供的通信系统的架构示意图二；
图3为本申请实施例提供的通信系统中PDU会话的协议栈的示意图；
图4为本申请实施例提供的通信方法的流程示意图一；
图5为本申请实施例提供的通信方法的流程示意图二；
图6为本申请实施例提供的通信方法的流程示意图三；
图7为本申请实施例提供的通信方法的流程示意图四；
图8为本申请实施例提供的通信装置的结构示意图一；
图9为本申请实施例提供的通信装置的结构示意图二。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如ProSe通信系统、无线保真(wireless fidelity，WiFi)系统，车到任意物体(vehicle to everything，V2X)通信系统、设备间(device-todevie，D2D)通信系统、车联网通信系统、第4代(4th generation，4G)移动通信系统，如长期演进(long term evolution，LTE)系统、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)移动通信系统，如新空口(new radio，NR)系统，以及未来的通信系统，如第六代(6th generation，6G)移动通信系统等。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或 特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例地”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，“信息(information)”，“信号(signal)”，“消息(message)”，“信令(singaling)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是相同的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是相同的。
本申请实施例中，有时候下标如W 1可能会笔误为非下标的形式如W1，在不强调其区别时，其所要表达的含义是相同的。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为便于理解本申请实施例，首先以图1和图2中所示出的通信系统为例，详细说明适用于本申请实施例的通信系统。应当指出的是，本申请实施例中的方案还可以应用于其他移动通信系统中，相应的名称也可以用其他移动通信系统中的对应功能的名称进行替代。
示例性地，图1示出了本申请实施例提供的通信方法所适用的一种5G通信系统的架构示意图。该5G通信系统可以包括接入网(access network，AN)和核心网(core network，CN)两部分。
其中，AN主要用于实现无线接入有关的功能，可以包括无线接入网(radio access network，RAN)网元。CN主要可以包括如下网元：接入及移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、统一数据储存(unified data repository，UDR)网元、计费功能(charging function，CHF)网元、网络能力开放功能(network exposure function，NEF)网元，应用功能(application function，AF)网元。
其中，AMF网元主要负责无线网络中的接入管理，如用户接入、用户位置更新、用户注册网络、小区切换等。
RAN网元主要用于为特定区域，如网络信号覆盖区域内的授权终端设备提供入网功能。
SMF网元主要负责无线网络中的会话管理，如协议数据单元(protocol data unit，PDU)会话的创建、修改、删除等，并维护PDU会话上下文。
UPF网元主要负责处理用户的数据包，如数据包转发、流量用量统计等。
PCF网元主要负责向AMF网元、SMF网元提供各种策略，如根据用户的签约信 息为SMF网元提供该用户的计费策略。
UDM网元主要用于存储用户数据，如签约信息、鉴权/授权信息。
UDR网元主要用于储存PCF网元所需的策略，如计费策略或者存储UMD网元的用户数据，且可与UDM网元共同部署。
CHF网元主要负责从核心网的网元，如从SMF网元获取用户的计费信息，计费并生成用户的话单。
NEF网元主要用于连接核心网中的网元与外部的应用服务器，可为外部应用服务器向核心网发起业务请求提供认证、转发等服务。
AF网元主要用于PCF网元之间交互以进行策略控制，如向PCF网元发送计费策略。
可选地，本申请实施例中的RAN网元可以为具有无线收发功能的设备或设备的芯片(系统)或其他部件或组件，包括但不限于：无线保真(wireless fidelity，WiFi)系统中的接入点(access point，AP)，如家庭网关、路由器、服务器、交换机、网桥等，演进型节点B(evolved Node B，eNB)、无线网络控制器(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)，无线中继节点、无线回传节点、传输点(transmission and reception point，TRP或者transmission point，TP)等，还可以为5G，如，新空口(new radio，NR)系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)、具有基站功能的路边单元(road side unit，RSU)等。
可选地，RAN网元通过N2接口(简称N2)与AMF网元通信，通过N3接口(简称N3)与UPF网元通信。UPF网元通过N4接口(简称N4)与SMF网元通信，通过N9接口(简称N9)与UPF网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信，通过N11接口(简称N11)与SMF网元通信，通过N14接口(简称N14)与AMF网元通信，通过N15接口(简称N15)与PCF网元通信。PCF网元通过N5接口(简称N5)与AF网元通信，通过N7接口(简称N7)与SMF网元通信。SMF网元通过N10接口(简称N10)与UDM网元通信。UDR网元通过N36接口(简称N36)与PCF网元通信。CHF网元通过N40接口(简称N40)与SMF网元通信，通过N28接口(简称N28)与PCF网元通信。NEF网元通过N37接口(简称N37)与UDR网元通信，通过N30接口(简称N30)与PCF网元通信。
需要说明的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。上述网元或者功能可划分出一个或多个服务，进一步，还可能会出现独立于网络功能存在的服务。上述网元间也可以采用服务化接口进行相互通信。在本申请中，上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
示例性地，图2示出了图1所示的5G通信系统在ProSe通信场景下的架构示意 图。其中，位于网络内，如网络信号覆盖区域内的终端设备可通过N1接口(简称N1)与AMF网元通信，并通过Uu接口与RAN网元通信，以接入网络。而位于网络外，如网络信号覆盖区域外的终端设备(简称远程终端设备)可通过已接入网络的终端设备(简称中继设备)接入到网络。比如，中继设备通过PC5接口与远程终端设备通信，以便远程终端设备通过中继设备，如使用中继设备的PDU会话，实现接入网络。
示例性地，图3示出了远程终端设备通过使用中继设备的PDU会话的协议栈。远程终端设备通过PC5接口向中继设备发送数据包，该数据包可以包括：物理层(L1层)、介质访问控制(media access control，MAC)层、无线链路控制子(radio link control structure，RLC)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层。服务数据适配协议(service data adaptation protocol，SDAP)层、网际互连协议(internet protocol，IP)层、应用(application)层。其中，MAC层、RLC层、PDCP层和SDAP层可以属于L2层。
可选地，中继设备可依次解码数据包的L1层和L2层，并解码到IP层。之后，中继设备基于Uu接口的协议栈，依次封装L2层和L1层，并通过Uu接口向RAN网元发送该数据包。
RAN网元也可依次解码数据包的L1层和L2层，并解码到IP层。之后，RAN网元可按中继设备的PDU会话的格式重新封装数据包。其中，重新封装的数据包可以包括：L1层、L2层、用户数据报协议(user datagram protocol，UDP)层/IP层、隧道传输协议(GPRS tunnel protocol-U，GTP-U)层、IP层。最后，RAN网元可通过N3接口，向UPF网元发送该数据包。
如此，UPF网元便可根据该数据包指示的路由向相应的设备发送该数据包，从而实现了远程终端设备接入无线网络后的通信。此外，RAN网元向UPF网元发送该PDU会话格式的数据包可以理解为：使用该PDU会话发送该远程终端设备的数据包。
应理解，本申请实施例介绍了远程终端设备发送数据包的流程，而远程终端设备接收数据包的流程可参考远程终端设备发送数据包的流程作相应理解，在此不再赘述。
可选地，本申请实施例中的远程终端设备和中继设备可以为具有无线收发功能的终端或可设置于该终端的芯片(系统)或其他部件或组件。该终端设备也可以称为用户装置、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、车载终端、具有终端功能的RSU等。本申请的终端设备还可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元。
需要说明的是，本申请实施例提供的通信方法，可以适用于图1和图2所示通信系统，具体实现可以参考下述方法实施例，此处不再赘述。
应当指出的是，本申请实施例中的方案还可以应用于其他通信系统中，相应的名称也可以用其他通信系统中的对应功能的名称进行替代。此外，图1和图2仅为便于理解而示例的简化示意图，该通信系统中还可以包括其他网络设备，和/或，其他终端设备，图1和图2中未予以画出。
下面将结合图4-图7对本申请实施例提供的通信方法进行具体阐述。
图4为本申请实施例提供的通信方法的流程示意图一。该通信方法可以适用于策略控制网元、会话管理网元、以及用户面网元之间的通信。其中，策略控制网元可以是图1和图2所示的PCF网元、自会话管理网元可以是图1和图2所示的SMF网元、用户面网元可以是图1和图2所示的UPF网元、统一数据管理网元可以是图1和图2中所示出UDM网元、统一数据储存网元可以是图1或图2中所示出UDR网元。
如图4所示，该通信方法可以包括如下步骤：
S401，会话管理网元向策略控制网元发送远程终端设备的第一标识。
其中，远程终端设备通过中继设备接入无线网络。
其中，远程终端设备的标识可以包括第一标识和第二标识。第一标识和第二标识不同，但可具备对应关系。第二标识可以用于会话管理网元获取第一标识。第一标识可以用于策略控制网元获取远程终端设备的第一计费策略，以实现对远程终端设备的单独计费。
其中，第一标识可以包括如下的一项或多项：该远程终端设备的签约永久标识(subscription permanent identifier，SUPI)、该远程终端设备的一般公共订阅标识(generic public subscription identifier，GPSI)、或者该远程终端设备的用户隐藏标识(subscription concealed identifier，SUCI)。
其中，第二标识可以包括如下的一项或多项：该远程终端设备SUPI、该远程终端设备的GPSI、该远程终端设备的SUCI、中继设备为该远程终端设备分配的端口号、或者第三方服务商为该远程终端设备分配的标识，如QQ号、微信号等。
示例性地，远程终端设备与中继设备连接后，远程终端设备可通过使用的PDU会话与无线网络通信，如向会话管理网元发送远程终端设备的第一标识或第二标识。以及，中继设备还可以向会话管理网元发送该PDU会话的PDU会话标识(PDU Session ID)。如此，会话管理网元可以根据第一标识与第二标识的对应关系，向策略控制网元发送远程终端设备的第一标识。
这样一来，无论采用何种来源以及何种类型的标识，基于该对应关系都可确定用于该远程终端设备计费的第一标识，从而实现对远程终端设备的单独计费，进而提高计费的可靠性。
可选地，在一种可能的设计方案中，若远程终端设备向会话管理网元发送第一标识，则会话管理网元可以直接获得该第一标识。
在另一种可能的设计方案中，若远程终端设备向会话管理网元发送第二标识，则会话管理网元可根据该第二标识来获得第一标识。
例如，可选地，若远程终端设备通过中继设备的PDU会话而向会话管理网元发送第二标识，则会话管理网元可根据第二标识从UDR网元/UDM网元(图4中未示出)获取第一标识。例如，会话管理网元可以向UDR网元/UDM网元发送第二标识。其中， UDR网元/UDM网元储存有第一标识，以及第一标识与第二标识的对应关系。如此，UDR网元/UDM网元可根据该第二标识和对应关系确定该第一标识，并向会话管理网元发送该第一标识，以便会话管理网元获得该第一标识。
又例如，可选地，远程终端设备与中继设备建立连接后，中继设备可经由AMF网元(图4中未示出)向UDR网元/UDM网元发送远程验证请求。其中，该验证请求中携带有第二标识。相应地，UDR网元/UDM网元根据该第二标识验证远程终端设备的合法性后，便可以向AMF网元发送验证结果、第一标识、以及第一标识与第二标识的对应关系。如此，AMF网元可向会话管理网元发送第一标识，以及第一标识与第二标识的对应关系，使得会话管理网元接收到来自远程终端设备的第二标识后，可根据该第二标识和对应关系，确定第一标识。或者，会话管理网元在接收到来自远程终端设备的第二标识后，可向AMF网元发送第二标识，以便AMF网元可根据该第二标识和对应关系，返回对应的第一标识。
进一步地，会话管理网元获取到第一标识后，便可向策略控制网元发送该第一标识，如向策略控制网元发送第一消息。其中，该第一消息携带有第一标识、中继设备的SUPI、GPSI或SUCI、以及远程终端设备使用的PDU会话的PDU会话标识，且该第一消息可为会话策略关联建立请求(SM Policy Association Establishment)消息或会话策略关联更改请求(SM Policy Association Modification)消息。
应理解，通过复用会话策略关联建立请求消息或会话策略关联更改请求消息来发送第一标识，可减少信令开销，以提高通信效率。
S402，策略控制网元根据第一标识，向会话管理网元发送远程终端设备的第一计费策略。
相应地，会话管理网元接收来自策略控制网元的第一计费策略。
其中，第一计费策略可以包括如下一项或多项：会话计费规则、或业务计费规则。下面分别说明。
可选地，“会话计费规则”又可称为：“PDU会话相关策略信息(PDU Session related policy information)”。会话计费规则是PDU会话维度的计费规则，用于以PDU会话为单位进行计费。会话计费规则可以包括：PDU会话的计费方式、PDU会话的费率组(rating group，RG)以及用量监测控制策略等。其中，计费方式可以是在线计费或离线计费；在线计费是指CHF网元(图4中未示出)根据PDU会话的业务配额以及费率进行计费，如限流量、限通话时长的计费；而离线计费是指CHF网元根据PDU会话的费率进行计费，而不限业务配额，如不限流量、不限通话时长的计费。
可选地，“业务计费规则”又可称为：“策略与计费控制(PDU Session related policy information，PCC)规则”。业务计费规则是业务维度的计费规则，用于以业务，如视频、通话、浏览网页等为单位进行计费。由于不同的业务可能有不同的计费方式，因此，业务计费规则可以包括：每种业务的五元组、每种业务的标识、每种业务的计费方式、每种业务的费率、每种业务的限额(spending limit)策略等；以及，在有第三方服务商赞助的业务时，业务计费规则还可以包括：该第三方服务商的赞助标识(sponsor ID)。
其中，限额策略可以用于指示远程终端设备的流量用量是否超出限额，以及用于 指示该业务的流量用量超出或未超出限额各自对应的速率。比如，该业务的流量用量超出限额对应的速率为第一速率，而未超出限额对应的速率为第二速率，且第一速率小于第二速率。
其中，第三方服务商的赞助标识可用于表示对应业务的计费由第三方服务商赞助，即用户面网元可不再向CHF网元上报第三方服务商赞助的业务对应的流量用量，而CHF网元也可以不再对第三方服务商赞助的业务计费。
在一种可能的设计方案中，若远程终端设备的业务为统一计费业务，则远程终端设备的业务计费规则可为各设备都可配置的通用业务计费规则。其中，统一计费业务是指大多数设备都具备且计费方式也相同的业务，如手机的视频业务、通话业务等。
应理解，由于该业务计费规则是各设备都可以配置的规则，因此，该业务计费规则可以不包含用于区分业务的标识。
在另一种可能的设计方案中，若远程终端设备的业务为非统一计费业务，则远程终端设备的业务计费规则可为针对远程终端设备的非统一计费业务而单独配置的业务计费规则。其中，非统一计费业务是指与统一计费业务的类型不同，和/或，计费方式也不相同的业务，如VR设备、AR设备、游戏机的游戏视频业务。
如此，该业务计费规则可以包含该远程终端设备的第一标识，以便与通用业务计费规则区分。
可选地，第一计费策略还可以包括：状态订阅指示。
其中，“状态订阅指示”又可称为：“策略控制请求触发信息(policy control request trigger information)”。该状态订阅指示可用于策略控制网元向会话管理网元订阅该远程终端设备业务流状态，和/或，连接状态，如指示策略控制网元向会话管理网元发送订阅请求消息。
示例性地，策略控制网元在订阅远程终端设备的业务流状态，和/或，连接状态后，若远程终端设备的业务流状态，和/或，连接状态发生变化，如IP地址变化、聚合最大比特速率(aggregate maximum bit rate，AMBR)变化、业务流断开或连接断开等，则会话管理网元可以向策略控制网元发送远程终端设备的订阅通知消息，以便策略控制网元及时掌握该远程终端设备的业务流状态，和/或，连接状态，从而及时调整计费规则，以确保计费的准确性。
其中，连接断开可以是远程终端设备与网络的通信连接断开。业务流断开可以是远程终端设备的某些业务的业务流断开，而远程终端设备还可以有其他业务的业务流未断开。换言之，若远程终端设备的连接断开后，则远程终端设备的所有业务流均断开，反之，远程终端设备的业务流断开并不影响远程终端设备与网络的通信连接。
其中，策略控制网元根据远程终端设备的业务流状态，和/或，连接状态调整计费规则的具体实现，可以参考第七种实现场景中的相关描述，在此不再赘述。
可选地，策略控制网元还可根据远程终端设备的连接状态，对应配置第一计费策略的状态。比如，若远程终端设备处于连接的状态，则策略控制网元可配置第一计费策略处于激活状态；若远程终端设备处于断开连接的状态，则策略控制网元可配置第一计费策略处于非激活状态。如此，策略控制网元根据第一计费策略的状态，可确定第一计费策略是否使用，以更灵活地调度资源，如配置或释放资源，以提高通信效率。
应理解，本申请实施例中所述的“策略”是所述的“规则”和“指示”的上位表述；相应地，所述的“规则”和“指示”则是“策略”的下位表述。当然，第一计费策略也不限于：会话计费规则、业务计费规则和状态订阅指示，比如第一计费策略可以只包括会话计费规则，对此不予限定。
S403，会话管理网元根据第一计费策略，向用户面网元发送第一上报规则。
具体地，第一上报规则可以是第一计费策略中的部分规则，可以用于用户面网元识别、统计并上报远程终端设备的流量，可以包括：流量识别规则以及流量上报规则。
其中，流量识别规则可以用于用户面网元识别远程终端设备的流量，比如，流量识别规则可以包括远程终端设备的流量的五元组信息，以便用户面网元可以根据该五元组，从用户面网元转发的流量中识别出该远程终端设备的流量。
其中，流量上报规则可以用于用户面网元向会话管理网元上报远程终端设备的流量用量。
进一步地，流量上报规则可以包括：流量配额以及上报触发规则。
其中，流量配额可以表示该远程终端设备当前阶段能够使用的流量。具体地，会话管理网元可以向CHF网元申请当前阶段的流量配额，如通过N40会话向CHF网元申请。相应地，CHF网元可以根据远程终端设备的套餐流量余额，而为远程终端设备配置当前阶段的流量配额。比如，套餐流量余额为500兆字节(mega bytes，MB)，CHF网元配置的流量配额可以是50MB。进一步地，若远程终端设备当前阶段的流量配额已用完，则会话管理网元可以向CHF网元申请下一阶段的流量配额。如此，CHF网元可以远程终端设备的套餐流量余额，继续为远程终端设备配置下一阶段的流量配额，直至远程终端设备的套餐流量余额不足，或者，远程终端设备的连接断开。
其中，上报触发规则可以包括：周期触发规则和事件触发规则。例如，用户面网元可以周期性地统计该远程终端设备的流量，以获得该远程终端设备的流量用量，并根据周期触发规则，周期性的向会话管理网元上报该流量用量，如发送N4会话报告消息，该N4会话报告消息携带有流量用量。其中，上报周期可以为1分钟、5分钟、30分钟、1小时、1天、1周等。又例如，若用户面网元统计的流量用量达到该远程终端设备的流量配额的上限值，则可以根据事件触发规则，向会话管理网元上报该流量用量。其中，上限值可以按照上述流量配额确定，如可以为流量配额的10％、30％、50％、70％、90％、100％等。
可选地，周期触发规则和事件触发规则也可以结合实施。例如，若周期触发规则先被触发，则用户面网元上报当前周期的流量用量；若事件触发规则先被触发，则用户面网元上报达到上限值的流量用量。
以上介绍了第一计费规则的具体内容，以下介绍会话管理网元如何发送第一计费规则，以及如何上报计费信息。
示例性地，会话管理网元从第一计费规则中确定出第一上报规则后，可以通过N4会话向用户面网元发送N4会话配置信息，该N4会话配置信息包括第一上报规则，该N4会话配置信息可以携带在N4会话建立请求消息或N4会话修改请求消息中。
进一步地，用户面网元根据第一计费规则上报的远程终端设备的流量用量后，会话管理网元可以周期性地统计用户面网元上报的远程终端设备的流量用量，从而获得 每个周期的流量用量。如此，会话管理网元可以根据第一计费规则以及每个周期的流量用量，周期性的向CHF网元发送远程终端设备的计费信息。
其中，会话管理网元的上报周期与用户面网元的上报周期可以相同，也可以不同。比如，会话管理网元的上报周期可以大于用户面网元的上报周期。
其中，计费信息可以包括对应周期的流量用量和费率，以便CHF网元可以根据该流量用量和费率，实现对远程终端设备单独计费。
需要说明的是，用户面网元生成并上报远程终端设备的流量用量，以及CHF网元根据该流量用量对该远程终端设备单独计费的具体实现，可以参考以下第九种实现场景中的相关描述。
应理解，在本申请实施例中，由于策略控制网元能够从会话管理网元获得远程终端设备的第一标识，故策略控制网元可根据第一标识而向会话管理网元发送远程终端设备的第一计费策略。如此，会话管理网元便可根据第一计费策略为用户面网元配置远程终端设备的第一上报规则，以便用户面网元在远程终端设备通过中继设备接入无线网络后，可根据第一上报规则，向计费功能网元上报远程终端设备的流量用量，从而实现对远程终端设备的单独计费。
可选地，在图4所示出的实施例的第一种实现场景中，该方法还可以包括：策略控制网元根据第一标识，获取远程终端设备的第一计费策略。
具体地，策略控制网元可以根据第一标识，从第一设备获取该第一计费策略。
其中，第一设备可以用于存储第一计费策略，具体可以包括如下的一个或多个：策略控制网元、UDM网元、UDR网元、CHF网元、或AF网元(图4中未示出)。
可理解到，由于第一计费策略可存储到各网元，以互为备份，从而提高第一计费策略存储的可靠性。
下面针对不同的第一设备，对策略控制网元获取该第一计费策略的实现方式分别予以介绍。
方式1、从策略控制网元本地获取。
示例性地，策略控制网元根据第一标识，判断策略控制网元本地是否储存有该远程终端设备的会话策略控制签约信息。其中，该会话策略控制签约信息包括远程终端设备的会话策略关联信息，会话策略关联信息则包括第一计费策略。若策略控制网元本地储存有该远程终端设备的会话策略控制签约信息，则策略控制网元从该会话策略控制签约信息中获取第一计费策略。
方式2、从UDM网元/UDR网元获取。
示例性地，策略控制网元根据第一标识，判断策略控制网元本地是否储存有该远程终端设备的会话策略控制签约信息。若策略控制网元本地未储存有该远程终端设备的会话策略控制签约信息，则策略控制网元向UDM网元/UDR网元发送请求消息。其中，该请求消息可以用于请求远程终端设备的会话策略控制签约信息，可以携带第一标识。相应地，UDM网元/UDR网元可以根据该第一标识返回该远程终端设备的会话策略控制签约信息。
具体地，策略控制网元可以通过预设的服务向UDM网元/UDR网元发送第一标识，如Nudr_DM_Query服务或Nudr_DM_Subscribe服务，对此不予限定。
如此，策略控制网元可从接收到的会话策略控制签约信息中，获取该远程终端设备的会话策略关联信息，即获取第一计费策略。
方式3、从CHF网元获取
示例性地，策略控制网元根据第一标识，判断策略控制网元本地是否储存有该远程终端设备的会话策略控制签约信息。若策略控制网元本地未储存有该远程终端设备的会话策略控制签约信息，则策略控制网元向CHF网元发送请求消息。其中，该请求消息可以用于请求远程终端设备的会话策略控制签约信息，可以携带第一标识。相应地，CHF网元可以根据第一标识向策略控制网元返回对应的第一计费策略。
具体地，策略控制网元可以通过预设的服务向UDM网元/UDR网元发送第一标识，如Nchf_SpendingLimitControl服务，对此不予限定。
方式4、从AF网元获取
若AF网元属于CN，则AF网元可通过预设的服务，如Npcf_PolicyAuthorization_Create服务或Npcf_PolicyAuthorization_Update服务，向策略控制网元发送第一计费策略。
若AF网元属于第三方服务商，则AF网元可向NEF网元(图4未示出)发送第二消息。其中，第二消息可以是第三方服务商用于流量赞助业务的相关消息，可以携带第一计费策略。如此，NEF网元验证AF网元的权限后，NEF网元再向策略控制网元转发该第二消息，以便策略控制网元从第二消息中获取该第一计费策略。
方式5、从多个网元获取
策略控制网元可根据第一标识，判断策略控制网元本地是否储存有该远程终端设备的会话策略控制签约信息。
若策略控制网元本地未储存有该远程终端设备的会话策略控制签约信息，策略控制网元可从各网元分别获取规则，并综合分别获取的规则，从而得到该第一计费策略。
例如，策略控制网元可从CHF网元获取业务计费规则中每种业务的限额策略，并从UDM网元/UDR网元获取会话计费规则、业务计费规则以及状态订阅指示，且策略控制网元从UDM网元/UDR网元获取业务计费规则不包含该限额策略。
这样一来，策略控制网元从CHF网元获取的限额策略、从UDM网元/UDR网元获取的规则和指示，便构成该第一计费策略。
又例如，策略控制网元可从AF网元获取业务计费规则，并从UDM网元/UDR网元获取会话计费规则以及状态订阅指示。这样一来，策略控制网元从AF网元、UDM网元/UDR网元获取的规则和指示，便构成该第一计费策略。
再例如，策略控制网元可从AF网元获取业务计费规则，并从UDM网元/UDR网元获取会话计费规则、业务计费规则以及状态订阅指示。之后，策略控制网元可结合分别从AF网元、以及UDM网元/UDR网元获取的业务计费规则，获得结合后的业务计费规则。比如，业务计费规则1可以包括A1和B1，业务计费规则2可以包括A2和C1，A1和A2是类型相同但取值不相同的信息，B1和C1是类型和取值均不同的信息，那么，策略控制网元可删除A2而保留A1、B1和C1，使得结合后的业务计费规可以包括A1、B1和C1。这样一来，该结合后的业务计费规则、会话计费规则和状态订阅指示，便构成该第一计费策略。
在一种可能的设计方案中，策略控制网元获取第一计费策略后，可直接向会话管理网元发送该第一计费策略。
在另一种可能的设计方案中，策略控制网元获取第一计费策略后，可以将第一标识，和/或，端口号，加入该第一计费策略。其中，端口号为中继设备为远程终端设备分配的端口号。之后，策略控制网元再向会话管理网元发送该第一计费策略，以便会话管理网元根据该第一标识，和/或，该端口号，确定该第一计费策略为远程终端设备的计费策略，从而准确上报该远程终端设备的计费信息。
需要指出的是，上述方式2-方式5中，策略控制网元也可以不判断策略控制网元本地是否储存有该远程终端设备的会话策略控制签约信息，而直接向UDM网元或UDR网元或AF网元等设备发送用于请求该会话策略控制签约信息的请求消息，对此不予限制。
可选地，在图4所示出的实施例的第二种实现场景中，该方法还可以包括：步骤1，会话管理网元从第二设备获取远程终端设备的会话管理签约数据(session management subscription data)。
其中，第二设备可以用于存储会话管理签约数据。第二设备与第一设备可以是相同的设备，或者也可以是不同的设备。在第二种实现场景中，第二设备具体可以是UDM网元。
其中，会话管理签约数据可以包括：中继设备的PDU会话计费特性信息。该PDU会话计费特性信息可以包括：PDU会话维度的计费规则，可以用于以PDU会话为单位进行计费。
具体地，会话管理网元可根据获得的第一标识或第二标识，从UDM网元获取远程终端设备的会话管理签约数据。
一种可能的设计方案，若会话管理网元接收到来自远程终端设备的第一标识，则会话管理网元可以向UDM网元发送请求消息，该请求消息携带该第一标识，以用于请求远程终端设备的会话管理签约数据。
示例性地，会话管理网元可以通过预设服务，向UDM网元发送请求消息，如通过Nudm_SDM_Get请求服务、Nudm_SDM_Subscribe订阅服务等，对此不予限定。
相应地，UDM网元可根据第一标识，从UDM网元本地获取该会话管理签约数据。或者，UDM网元还可以向UDR网元发送订阅请求消息。其中，该订阅请求消息可以用于向UDR网元请求该会话管理签约数据，该订阅请求消息可以携带第一标识。如此，UDR网元可以根据该订阅请求消息而向UDM网元发送会话管理签约数据，以便UDM网元向会话管理网元发送会话管理签约数据。
示例性地，UDM网元可以通过预设服务，向UDR网元发送上述订阅请求消息，如通过Nudr_DM_Query订阅服务、Nudr_DM_subscribe订阅服务等，对此不予限定。
另一种可能的设计方案，若会话管理网元接收到来自远程终端设备的第二标识，会话管理网元可以先根据第二标识从UDM网元获取第一标识。其中，根据第二标识从UDM网元获取第一标识的具体实现可以参考S401，在此不再赘述。
之后，会话管理网元根据第一标识，从UDM网元获取该会话管理签约数据。其中，根据第一标识从UDM网元获取该会话管理签约数据的具体实现方式可以参考前 述各方式中的相关描述，在此不再赘述。
又一种可能的设计方案，若会话管理网元接收到来自远程终端设备的第二标识，会话管理网元可以向UDM网元发送请求消息。该请求消息用于请求远程终端设备的会话管理签约数据，可以携带该第二标识。
示例性地，会话管理网元可以通过预设服务，向UDM网元发送第二标识，如通过Nudm_SDM_Get请求服务、Nudm_SDM_Subscribe订阅服务等，对此不予限定。
相应地，UDM网元可根据第二标识，从UDM网元本地获取第二标识对应的第一标识，再获取该第一标识对应的会话管理签约数据。或者，UDM网元也可以向UDR网元发送用于请求远程终端设备的会话管理签约数据的请求消息，该请求消息携带该第二标识。这样，UDR网元可以根据第二标识获取第一标识，并获取该第一标识对应的会话管理签约数据，从而向UDM网元发送第一标识和会话管理签约数据。如此，UDM网元可以向会话管理网元打包发送第一标识和会话管理签约数据，以便会话管理网元获得会话管理签约数据同时也获得第一标识。
示例性地，UDM网元可以通过预设服务，向UDR网元发送该第二标识，如通过Nudr_DM_Query订阅服务、Nudr_DM_subscribe订阅服务等，对此不予限定。
可选地，在图4所示出的实施例的第二种实现场景中，该方法还可以包括：步骤2，会话管理网元根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略。
其中，该PDU会话计费特性信息可以包括：第一部分信息，而第一计费策略的会话计费规则可以包括：第二部分信息和第三部分信息。其中，第一部分信息与第三部分信息的类型相同且内容不相同，而第一部分信息与第二部分信息的类型和内容均不相同。
示例性地，会话管理网元获得会话管理签约数据和第一计费策略后，可以将第一计费策略中的第三部分信息更新为会话管理签约数据中的第一部分信息，以实现将第一计费策略更新为第三计费策略，以实现对远程终端设备进行单独计费。换言之，第三计费策略的会话计费规则与第一计费策略的会话计费规则不同，第三计费策略的会话计费规则可以包括：第一部分信息和第二部分信息，而第三计费策略中的会话计费规则和状态订阅指示则仍与第一计费策略中的会话计费规则和状态订阅指示相同。
例如，第一部分信息包括：业务A，费率为RG1；第二部分信息包括：业务B，费率为RG2、业务C，费率为RG3；第三部分信息包括：业务A、费率为RG4。
其中，第一部分信息和第三部分信息均为业务A的计费策略，表示第一部分信息和第三部分信息的类型相同。第一部分信息和第三部分信息中业务A的费率不同，表示第一部分信息和第三部分信息的内容不同。第一部分信息和第二部分信息的业务和费率均不同，表示第一部分信息与第二部分信息的类型和内容均不同。
如此，第三计费策略的会话计费规则可以包括：业务A，费率为RG4、业务B，费率为RG2、以及业务C，费率为RG3。
应理解，会话管理网元根据会话管理签约数据和第一计费策略，确定第三计费策略仅为一种示例方式，并不作为限定。比如，若PDU会话计费特性信息的内容与第一计费策略中会话计费规则的内容相同，则无需更新第一计费策略。
可选地，在图4所示出的实施例的第二种实现场景中，该方法还可以包括：步骤3，会话管理网元根据第三计费策略，向用户面网元发送第三上报规则。
其中，会话管理网元根据确定的第三计费策略，向用户面网元发送第三上报规则的具体实现方式可以参考步骤S403中的相关描述，在此不再赘述。
应理解，会话管理网元还可以向策略控制网元发送第三计费策略，以便策略控制网元更新本地保存的第一计费策略为第三计费策略。
可选地，结合前述的第二种实现场景，在图4所示出的实施例的第三种实现场景中，该方法还可以包括：会话管理网元向第二设备发送第五指示信息。
其中，第五指示信息可以用于指示该远程终端设备通过中继设备接入无线网络，或用于指示该远程终端的接入网络方式。第五指示信息可以为指示字段，如为1个比特(bit)。
具体地，终端设备的接入网络方式可以包括：中继接入方式，即终端设备通过中继设备接入无线网络的方式；或者，直接接入方式，即终端设备直接通过接入网络设备接入无线网络的方式。
其中，不同的接入方式可以对应不同的会话管理签约数据。比如，若采用直接接入网络方式，则会话管理签约数据的PDU会话计费特性信息可以包括：第三方免流量计费的规则；若采用中继接入网络方式，则会话管理签约数据的PDU会话计费特性信息可以包括：付费流量计费的规则。因此，会话管理网元还可以向第二设备，如向UDM网元发送第五指示信息。
相应地，UDM网元可以根据第五指示信息，向会话管理网元发送中继接入方式对应的会话管理签约数据。
可选地，在图4所示出的实施例的第四种实现场景中，该方法还可以包括：策略控制网元向第二设备发送第一指示信息。
其中，第二设备还可以用于存储第一计费策略。在第四种实现场景中，第二设备具体可以是UDR网元、UDM网元、CHF网元、或AF网元等，对此不予限制。
其中，第一指示信息可以用于指示该远程终端的接入网络方式，如指示该远程终端设备通过中继设备接入无线网络，可以为指示字段，如为1个比特的信元。
具体地，由于不同的接入方式可以对应不同的计费策略，因此，策略控制网元还可向第二设备发送第一指示信息，以便第二设备根据第一标识和第一指示信息，确定中继接入方式对应的第一计费策略。
可选地，在图4所示出的实施例的第五种实现场景中，该方法还可以包括：策略控制网元接收来自第二设备的第二计费策略，并向会话管理网元发送第二计费策略。
其中，第二设备还可以用于存储第二计费策略。在第五种实现场景中，第二设备具体可以是AF网元。
其中，第二计费策略可以与第一计费策略、第三计费策略不同。比如，第二计费策略可以包括：第三方免流量计费的规则，而第一计费策略和第三计费策略可以包括：付费流量计费的规则。又比如，第二计费策略可以包括：视频业务计费的规则，而第一计费策略和第三计费策略可以包括：音频业务计费的规则。
具体地，AF网元可以为策略控制网元配置远程终端设备的计费策略，该AF网元 配置的计费策略可以称为第二计费策略。
进一步地，AF网元可以向策略控制网元发送该第二计费策略。比如，AF网元可以向策略控制网元发送计费策略创建请求消息或计费策略更新请求消息，该计费策略创建请求消息或计费策略更新请求消息中携带有该第二计费策略。
其中，若AF网元属于CN，则AF网元可直接向策略控制网元发送该第二计费策略。若AF网元属于第三方服务商，则AF网元可向NEF网元(图4未示出)发送该第二计费策略，NEF网元可以在验证AF网元的权限后，再向策略控制网元转发该第二计费策略。
进一步地，策略控制网元接收来自AF网元的第二计费策略后，可以向会话管理网元发送该第二计费策略，以便会话管理网元根据第二计费策略，向用户面网元发送第二上报规则，使得用户面网元可根据该第二上报规则，上报远程终端设备的流量用量，以确保计费的准确性。
其中，会话管理网元根据第二计费策略，向用户面网元发送第二上报规则的具体实现方式可以参考步骤S403中的相关描述，在此不再赘述。
可选地，结合第一种和第五种实现场景，在图4所示出的实施例的第六种实现场景中，该方法还可以包括：策略控制网元接收来自AF网元的第四指示信息。
其中，第四指示信息可以用于指示：该第二计费策略不用于通过中继设备接入无线网络的远程终端设备的计费，或者，不用于中继接入网络方式的计费，或用于直接接入网络方式的计费。该第四指示信息可以为指示字段，比如为1个比特的信元。
示例性地，AF网元向策略控制网元发送计费策略创建请求消息或计费策略更新请求消息，该计费策略创建请求消息或计费策略更新请求消息携带有第四指示信息。
相应地，策略控制网元在接收到第二计费策略之后的预设时长内，可判断是否接收到来自AF网元的第四指示信息。
例如，若策略控制网元在接收到第二计费策略之后的预设时长内，未接收到来自AF网元的第四指示信息，则可以向会话管理网元发送第二计费策略，并更新本地保存的计费策略为第二计费策略。
其中，根据前述第一种实现场景中的相关描述可知，若策略控制网元本地保存的是第一计费策略，则更新第一计费策略为第二计费策略；若策略控制网元本地保存的是已更新的第三计费策略，则更新第三计费策略为第二计费策略。
又例如，若策略控制网元在接收到第二计费策略之后的预设时长内，接收到来自AF网元的第四指示信息，则可以不向会话管理网元发送第二计费策略。并且，策略控制网元还可向AF网元发送计费策略更新失败消息或计费策略创建失败消息，以便AF网元也不再向策略控制网元发送该第二计费策略，如此，以避免计费错误及资源浪费，进而提高通信效率。
相应地，AF网元可根据接收到的消息，如计费策略更新失败消息或计费策略创建失败消息，向策略控制网元发送业务流策略取消消息，以便策略控制网元根据该业务流策略取消消息删除第二计费策略，以优化策略配置，释放冗余资源。
可选地，结合第五种和第六种实现场景，在图4所示出的实施例的第七种实现场景中，该方法还可以包括：策略控制网元向第二设备发送计费通知消息。
其中，在第七种实现场景中，第二设备具体可以是AF网元，计费通知消息可以用于通知远程终端设备与中继设备的连接断开，或者，用于通知远程终端设备与中继设备的业务流断开。
具体地，策略控制网元在获得第一计费策略后，可以根据第一计费策略中的状态订阅指示，向会话管理网元订阅服务订阅远程终端设备的连接状态，和/或，业务流状态，以便会话管理网元在确定远程终端设备的业务流断开，和/或，连接断开后，可以向策略控制网元发送订阅通知消息。其中，该订阅通知消息可以用于指示远程终端设备与中继设备的连接断开，或者，用于指示远程终端设备与中继设备的业务流断开。如此，会话管理网元便可以根据订阅通知消息，向AF网元发送计费通知消息。
相应地，AF网元可以根据计费通知消息的内容，判断是否向策略控制网元发送业务流策略取消消息。
一些实施例中，若计费通知消息用于通知远程终端设备的连接断开，则AF网元可以向策略控制网元发送业务流策略取消消息，即指示策略控制网元停止计费。
相应地，根据前述第五种和第六种实现场景中的相关描述可知，若策略控制网元本地保存的是第一计费策略，则策略控制网元可以根据该业务流策略取消消息删除本地保存的第一计费策略；同理，若策略控制网元本地保存的是由更新第一计费策略获得的第二计费策略，则策略控制网元可以根据该业务流策略取消消息删除本地保存的第二计费策略，以优化策略配置，释放冗余资源。
另一些实施例中，若计费通知消息用于通知远程终端设备的业务流断开，则AF网元可以不向策略控制网元发送业务流策略取消消息，以便策略控制网元仍可向会话管理网元发送第一计费策略或第二计费策略，以实现对远程终端设备其他未断开的业务单独计费。
例如，远程终端设备的业务包括：音频业务和视频业务，且音频业务和视频业务均通过中继接入方式实现。其中，若该音频业务的业务流断开，则策略控制网元仍可以向会话管理网元发送第一计费策略或第二计费策略，以实现对视频业务单独计费。
又例如，远程终端设备的业务包括音频业务和视频业务。其中，因远程终端设备所在位置的网络服务质量相对较差，对服务质量的要求相对较高的视频业务可以通过中继接入方式实现，而对服务质量的要求相对较低的音频业务则可以通过直接接入方式实现。其中，若该视频业务的业务流断开，则策略控制网元仍可以向会话管理网元发送第一计费策略或第二计费策略，以实现对音频业务单独计费。
下面分情况具体介绍策略控制网元如何判断是否向会话管理网元发送第一计费策略或第二计费策略。
第一种情况，若策略控制网元在获得第一计费策略之后的预设时长内，未接收到来自会话管理网元的上述订阅通知消息，则策略控制网元可以向会话管理网元发送第一计费策略，以实现对远程终端设备单独计费。其中，未接收到来自会话管理网元的上述订阅通知消息表示远程终端设备的连接和业务流均未断开。
第二种情况，若策略控制网元在获得第一计费策略之后的预设时长内，接收到来自会话管理网元的上述订阅通知消息，且该订阅通知消息表示远程终端设备的业务流断开，则策略控制网元可以向会话管理网元发送第一计费策略。
第三种情况，若策略控制网元在获得第一计费策略之后的预设时长内，接收到来自会话管理网元的上述订阅通知消息，且该订阅通知消息表示远程终端设备的连接断开，则策略控制网元可以不向会话管理网元发送第一计费策略，以节约资源开销。
第四种情况，若策略控制网元在接收到第二计费策略之后的预设时长内，未接收到来自AF网元的第四指示信息和来自会话管理网元的上述订阅通知阅消息，则策略控制网元可以向会话管理网元发送第二计费策略。其中，未接收到来自AF网元的第四指示信息表示第二计费策略可用于通过中继设备接入无线网络的设备的计费，即用于远程终端设备的计费。
第五种情况，若策略控制网元在接收到第二计费策略之后的预设时长内，未接收到来自AF网元的第四指示信息，但接收到来自会话管理网元的上述订阅通知消息，且该订阅通知消息表示远程终端设备的业务流断开，则策略控制网元可以向会话管理网元发送第二计费策略。
第六种情况，若策略控制网元在接收到第二计费策略之后的预设时长内，接收到来自AF网元的第四指示信息，和/或，接收到来自会话管理网元的上述订阅通知消息，且该订阅通知消息表示远程终端设备的连接断开，则策略控制网元可以不向会话管理网元发送第二计费策略，以节约资源开销。
可选地，在图4所示出的实施例的第八种实现场景中，该方法还可以包括：策略控制网元向会话管理网元发送第二指示信息或第三指示信息。
其中，第二指示信息可以用于指示：允许远程终端设备使用中继设备已建立的PDU会话中与第一计费策略匹配的PDU会话。第三指示信息可以用于指示：不允许远程终端设备使用中继设备已建立的PDU会话；或者，第三指示信息可以用于指示：远程终端设备与中继设备断开连接。
示例性地，第二指示信息中可以包括该匹配的PDU会话的PDU会话标识，以用于指示：允许远程终端设备使用该匹配的PDU会话。
示例性地，第三指示信息可包括：第一子信息和第二子信息。
其中，第一子信息可以用于指示：在中继设备已建立的PDU会话中，不存在计费策略与第一计费策略匹配的PDU会话。
其中，若中继设备已创建的PDU会话数量未达到上限，则第二子信息可用于指示：不允许远程终端设备使用中继设备已建立的PDU会话；或者，若中继设备已创建的PDU会话数量已达到上限，则第二子信息可用于指示：远程终端设备与中继设备断开连接。
相应地，会话管理网元接收到第二指示信息或第三指示信息后，可向中继设备发送该第二指示信息或第三指示信息，如向中继设备发送N1会话建立请求消息或N1会话修改请求消息，该N1会话建立请求消息或N1会话修改请求消息中携带有第二指示信息或第三指示信息。
如此，中继设备可以根据该第二指示信息创建PDU会话。或者，中继设备也可以根据该第三指示信息中的第一子信息，获知不允许远程终端设备使用已建立的PDU会话或者远程终端设备与中继设备断开连接的原因，还可以根据第二子信息准确执行相应动作，如断开与远程终端设备间的连接，停止对远程终端设备计费，并释放通信资 源，从而提高控制的可靠性，提高通信效率。
进一步地，与第一计费策略匹配的PDU会话可以指的是，在中继设备已建立的PDU会话中计费策略与该第一计费策略匹配的PDU会话，后续称为匹配的会话。
具体地，策略控制网元获得第一计费策略后，可判断中继设备已建立的PDU会话中是否存在匹配的会话。
其中，上述匹配可以理解为第一计费策略中的所有策略与PDU会话的计费策略相同。
下面通过一些示例来介绍策略匹配。
示例1：
假设PDU会话1的计费策略和第一计费策略可以如下表1所示。
表1
Figure PCTCN2021116143-appb-000001
根据表1所示可理解到，由于费率不同，可认为PDU会话1的计费策略与第一计费策略1不相同。
示例2：
假设PDU会话2的计费策略和第一计费策略可以如下表2所示。
表2
Figure PCTCN2021116143-appb-000002
根据表2所示可理解到，由于业务类型和费率不同，可认为PDU会话2的计费策略与第一计费策略2不相同。
示例3：
假设PDU会话3的计费策略和第一计费策略可以如下表3所示。
表3
Figure PCTCN2021116143-appb-000003
根据表3所示可理解到，由于第一计费策略3的所有策略与PDU会话3的计费策略都相同，可认为PDU会话3的计费策略与第一计费策略3相同。
示例4：
假设PDU会话4的计费策略和第一计费策略可以如下表4所示。
表4
Figure PCTCN2021116143-appb-000004
根据表4所示可理解到，虽然PDU会话4的计费策略中包含第一计费策略4中没有的策略，但并不影响以第一计费策略4为基准的计费，也可认为PDU会话4的计费策略与第一计费策略4相同。
可选地，在图4所示出的实施例的第九种实现场景中，该方法还可以包括：会话管理网元向第二设备发送计费数据请求(charging data request)消息。
其中，在第九种实现场景中，第二设备具体可以是CHF网元。
其中，会话管理网元可以根据用户面网元周期性上报的远程终端设备的流量用量，周期性地向CHF网元发送该计费数据请求消息。计费数据请求消息可以用于CHF网元对远程终端设备单独计费，计费数据请求消息可以包括计费数据更新请求(charging data request update)消息或计费数据初始请求(charging data request initial)消息，不予限制。计费数据请求消息可以携带远程终端设备的计费信息以及第一标识，以便CHF网元可根据该计费信息以及第一标识，对远程终端设备单独计费。
其中，第一标识的具体实现方式可以参见步骤S401中的相关描述，在此不再赘述。
需要说明的是，若第一标识为远程终端设备的SUPI，CHF网元可直接根据该计费信息以及SUPI，对远程终端设备单独计费。若第一标识为远程终端设备的其他标识，如SUCI、GPSI、第三方服务商分配的标识等，CHF网元可根据该第一标识的对应关系确定远程终端设备的SUPI，再根据该计费信息以及该SUPI，对远程终端设备单独计费。
下面以会话管理网元某一次发送计费数据请求消息为例进行介绍。
示例性地，由于在S401中会话管理网元获得PDU会话的PDU会话标识，会话管理网元可根据该PDU会话标识，确定该远程终端设备使用的是中继设备已创建的PDU会话，还是中继设备为远程终端设备新创建的PDU会话(下文称为新创建的PDU会话)。
具体地，若会话管理网元确定已记录PDU会话标识中存在的上述PDU会话标识，则可以确定远程终端设备使用的是中继设备已创建的PDU会话。若会话管理网元确定已记录PDU会话标识中不存在的上述PDU会话标识，则可以确定远程终端设备使用的是中继设备新创建的PDU会话。
进一步地，若远程终端设备使用的是中继设备已创建的PDU会话，则会话管理网元向CHF网元发送的计费数据请求消息可以为计费数据请求更新消息。若远程终端设备使用的是单独创建的PDU会话，则会话管理网元向CHF网元发送的计费数据请求消息可以为计费数据初始请求消息。
进一步地，会话管理网元还可以根据上述PDU会话标识以及第一标识，确定PDU会话是由远程终端设备独享使用，还是由远程终端设备与其他设备共享使用。
具体地，若上述PDU会话标识与第一标识关联之外，未与其他设备的标识关联，则会话管理网元确定PDU会话是由远程终端设备独享使用。若上述PDU会话标识与第一标识关联之外，还与其他设备的标识关联，则会话管理网元确定PDU会话是由远程终端设备与该其他设备共享使用。
下面分别介绍CHF网元在独享使用和共享使用场景下的计费。
A独享使用：
示例性地，计费数据请求消息可携带远程终端设备的第一标识、以及远程终端设备的计费信息。如此，CHF网元可以根据该第一标识，确定计费对象为远程终端设备，从而再根据远程终端设备的计费信息对该远程终端设备单独计费。
可选地，计费数据请求消息还可以携带会话标识(session identifier)、中继设备的标识(如SUPI)。其中，会话标识为CHF网元为实现计费而事先为该PDU会话分配的标识，会话标识可以用于CHF网元确定计费对象，即远程终端设备，使用的是哪一个PDU会话。中继设备的标识可以用于CHF网元确定该PDU会话由中继设备创建。如此，CHF网元通过记录上述会话标识以及中继设备的标识，可以确保计费信息的完整，避免计费出错。
示例性地，下式(1)示出了计费数据请求消息在独享使用场景下的格式一。
Session ID：11
SUPI：xx
Remote UE ID：aa(1)
Multiple Unit Usage:a1
{Rating Group:r1
Used Unit Container{yy}}
其中，“Session ID：11”表示：CHF网元为PDU会话分配的会话标识为11；“SUPI：xx”表示：创建PDU会话的中继设备的SUPI为xx；“Remote UE ID：aa”表示：当前使用PDU会话的远程终端设备的第一标识为aa；“Multiple Unit Usage:a1”、“Rating Group:r1”和“Used Unit Containe{yy}”构成远程终端设备aa本周期上报的计费信息；“Multiple Unit Usage:a1”表示：远程终端设备aa在本周期的计费类别为a1类业务、“Rating Group:r1”表示：a1类业务的费率为r1；“Used Unit Containe{yy}”则表示：a1类业务的流量用量为yy。
可以理解，由于Remote UE ID为计费数据请求消息中的一个独立信元，CHF网元可以根据Remote UE ID为aa，确定独立计费的对象是远程终端设备aa。如此，CHF网元可以以远程终端设备aa为对象，确定a1类业务的流量yy和费率r1的乘积值，该乘积值r1*yy即为远程终端设备aa的a1类业务在本周期内的话费，从而实现对远程终端设备aa单独计费。
示例性地，下式(2)示出了计费数据请求消息在独享使用场景下的格式二。
Session ID：11
SUPI：xx
Multiple Unit Usage:a1(2)
{Rating Group:r1
Used Unit Container{yy}}
其中，“Session ID：11”表示：CHF网元为PDU会话分配的会话标识为11；“SUPI：xx”表示：远程终端设备的第一标识为xx；“Multiple Unit Usage:a1”、“Rating Group:r1”和“Used Unit Containe{yy}”构成远程终端设备aa本周期上报的计费信息；“Multiple Unit Usage:a1”表示：远程终端设备aa在本周期的计费类别为a1类业务、“Rating Group:r1”表示：a1类业务的费率为r1；“Used Unit Containe{yy}”则表示：a1类业务的流量用量为yy。
可以理解，CHF网元可以根据信元SUPI的内容为aa，确定独立计费的对象是远程终端设备aa。如此，CHF网元可以以远程终端设备aa为对象，确定a1类业务的流量yy和费率r1的乘积值，该乘积值r1*yy即为远程终端设备aa的a1类业务在本周期内的话费，从而也实现对远程终端设备aa单独计费。
B共享使用：
若远程终端设备共享使用，比如，包含远程终端设备在内的多个设备共享使用同一PDU会话，则计费数据请求消息中可以携带每个设备的第一标识和计费信息。
其中，每个设备的第一标识和计费信息可打包到一个容器中。如此，CHF网元通过分析每个容器内的信息，便可实现对多个设备分别计费。
可选地，计费数据请求消息还可以携带会话标识、中继设备的标识。会话标识和中继设备的标识的具体实现以及作用可以参考前述第一种示例性地方式，在此不再赘述。
示例性地，下式(2)示出了计费数据请求消息的格式二。
Session ID：11
SUPI：xx
{Remote UE ID：aa
Multiple Unit Usage:a1
{Rating Group:r1
Used Unit Container{yy}}(2)
}
{Remote UE ID：bb
Multiple Unit Usage:b1
{Rating Group:r2
Used Unit Container{zz}}
}
其中，“Session ID：11”表示：CHF网元为PDU会话分配的会话标识为11；“SUPI：xx”表示：创建PDU会话的中继设备的SUPI为xx；{Remote UE ID：aa……Used Unit Container{yy}}}为消息中的第一个容器；{Remote UE ID：bb……Used Unit Container{zz}}}为消息中的第二个容器。
进一步地，在第一个容器中，“Remote UE ID：aa”表示：当前共享使用PDU会话的一个远程终端设备的第一标识为aa；“Multiple Unit Usage:a1”、“Rating Group:r1”和“Used Unit Containe{yy}”构成远程终端设备aa本周期上报的计费信息；“Multiple  Unit Usage:a1”表示：远程终端设备aa本周期的计费类别为a1类业务、“Rating Group:r1”表示：a1类业务的费率为r1；“Used Unit Containe{yy}”则表示：a1类业务的流量用量为yy。
可以理解，CHF网元可以根据第一个容器中的独立信元Remote UE ID为aa，确定计费对象是远程终端设备aa。如此，CHF网元可以以远程终端设备aa为对象，确定a1类业务的流量yy和费率r1的乘积值，该乘积值r1*yy即为远程终端设备aa的a1类业务在本周期内的话费，从而实现在共享使用下，对其中一个远程终端设备aa单独计费。
进一步地，在第二个容器中，“Remote UE ID：bb”表示：当前共享使用PDU会话的另一个远程终端设备的第一标识为bb；“Multiple Unit Usage:b1”、“Rating Group:r2”和“Used Unit Containe{zz}”构成远程终端设备bb本周期上报的计费信息；“Multiple Unit Usage:b1”表示：远程终端设备bb本周期的计费类别为b1类业务、“Rating Group:r2”表示：b1类业务的费率为r2；“Used Unit Containe{yy}”则表示：b1类业务的流量用量为zz。
可以理解，CHF网元可以根据第二个容器中的独立信元Remote UE ID为bb，确定计费对象是远程终端设备bb。如此，CHF网元可以以远程终端设备bb为对象，确定b1类业务的流量zz和费率r2的乘积值，该乘积值r2*zz即为远程终端设备bb的b1类业务在本周期内的话费，从而实现在共享使用下，对另一个远程终端设备bb单独计费。
以上结合图4介绍了本申请实施例提供的通信方法的整体流程，以下结合图5-图7，详细说明该通信方法在具体应用场景下的流程。
示例性地，图5为本申请实施例提供的通信方法的流程示意图二。该通信方法可以适用于图1和图2所示的PCF网元、SMF网元、UPF网元、UDM网元、UDR网元、NEF网元、AF网元之间的通信。如图5所示，该通信方法可以包括如下步骤：
S501，远程终端设备向SMF网元发送第一标识或第二标识。
相应地，SMF网元接收来自远程终端设备的第一标识或第二标识。
具体地，远程终端设备可以经由中继设备、RAN网元(图5中未示出)、AMF网元(图5中未示出)向SMF网元发送第一标识或第二标识。
其中，S501的具体实现可以参考S401中的相关描述，在此不再赘述。
S502，SMF网元从UDM网元获取远程终端设备的会话管理签约数据。
具体地，SMF网元可根据获得的第一标识或第二标识，从UDM网元获取远程终端设备的会话管理签约数据，以用于S509中的计费策略配置。
其中，S502的具体实现可以参考第二种实现场景和第三种实现场景中的相关描述，在此不再赘述。
需要说明的是，S502在图5中为虚线，表示S502为可选步骤，换言之，若要获取远程终端设备的会话管理签约数据，在S501之后，SMF网元可执行S502；否则，在S501之后，SMF网元可直接向PCF网元发送远程终端设备的第一标识，即执行下述S503，然后由PCF网元根据第一标识获取远程终端设备的会话管理签约数据。
S503，SMF网元向PCF网元发送第一标识。
S504，PCF网元向UDM网元或UDR网元发送第一标识。
其中，S503的具体实现可以参考S401中的相关描述，S504的具体实现可以参考S402和第一种实现场景中的相关描述，在此不再赘述。
S505，PCF网元向UDM网元或UDR网元发送第一指示信息。
其中，S505的具体实现可以参考第四种实现场景中的相关描述，在此不再赘述。
需要说明的是，S504和S506在图5中为虚线，表示S504和S506为可选步骤，换言之，PCF网元从UDM网元或UDR网元获取第一计费策略仅为一种可选方式，比如，PCF网元还可以从PCF网元本地获取第一计费策略。S505在图5中为虚线示出，表示S505也为可选步骤，换言之，若要获取适用于中继接入方式的第一计费策略，PCF网元可执行S505；否则，PCF网元可以不执行S505。此外，S505和S504的执行顺序不限定。
S506，UDM网元或UDR网元向PCF网元发送第一计费策略，PCF网元接收来自UDM网元或UDR网元的第一计费策略。
在一种可能的设计方案中，若PCF网元不需要获取适用于中继接入方式的第一计费策略，UDM网元或UDR网元可根据第一标识，确定第一标识对应的会话策略控制签约信息，并向PCF网元发送该会话策略控制签约信息。
如此，PCF网元可接收到会话策略控制签约信息，并从中获取该远程终端设备的会话策略关联信息，即获得第一计费策略。
在另一种可能的设计方案中，若PCF网元需要获取适用于中继接入方式的第一计费策略，UDM网元或UDR网元可根据该第一标识和第一指示信息，确定与第一标识和第一指示信息对应的会话策略控制签约信息，并向PCF网元发送该会话策略控制签约信息。
如此，PCF网元便可从接收到的会话策略控制签约信息中获取该远程终端设备的会话策略关联信息，即获取到适用于中继接入方式的第一计费策略。
应理解，根据第一种实现场景中的相关描述可知，PCF网元除从UDM网元或UDR网元获取第一计费策略外，PCF网元还可从其他网元获取第一计费策略，具体实现可以结合参考S402、第二种实现场景和第四种实现场景中的相关描述，在此不再赘述。
S507，PCF网元向SMF网元发送第一计费策略。
S508，SMF网元根据第一计费策略，向UPF网元发送第一上报规则。
S509，SMF网元根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略。
S510，SMF网元根据第三计费策略，向UPF网元发送第三上报规则。
其中，S507的具体实现可以参考S402和第一种实现场景中的相关描述，S508的具体实现可以参考S403中的相关描述，S509的具体实现可以参考第二种实现场景中的相关描述，S510的具体实现可以参考S403中的相关描述，在此不再赘述。
需要说明的是，S508-S510在图5中为虚线示出，表示S508-S510为可选步骤。其中，若SMF网元不需要重新确定远程终端设备的计费策略，可执行S508；若SMF网元需要重新确定远程终端设备的计费策略，则可执行S509-S510。
S511，AF网元向PCF网元发送第二计费策略，PCF网元接收来自AF网元的第 二计费策略。
其中，S511的具体实现可以参考第五种实现场景中的相关描述，在此不再赘述。
其中，若AF网元属于CN，AF网元可直接向PCF网元发送该第二计费策略。若AF网元属于第三方服务商，AF网元可向NEF网元(图5未示出)发送该第二计费策略，并经由NEF网元验证AF网元的权限后，NEF网元再向PCF网元转发该第二计费策略。
应理解，S511可在远程终端设备通过中继设备接入后的任意时刻执行，可选地，本申请实施例以S511在S506之后执行为例进行介绍，但并不作为限定。
S512，AF网元向PCF网元发送第四指示信息，PCF网元接收来自AF网元的第四指示信息。
其中，S512的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
需要说明的是，S512在图5中为虚线示出，表示S512为可选步骤，换言之，若要进一步控制第二计费策略的配置，AF网元可执行S512；否则，AF网元可不执行S512。此外，S511和S512的执行顺序不限定。
S513，PCF网元向SMF网元发送第二计费策略。
S514，PCF网元根据第二计费策略，更新第一计费策略或第三计费策略。
其中，S513、S514的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
S515，SMF网元根据第二计费策略，向UPF网元发送第二上报规则。
SMF网元通过向UPF网元发送第二上报规则，使得UPF网元可根据最新的第二上报规则，上报远程终端设备的计费信息，以确保计费的准确性。
其中，S515的具体实现可以参考S403中的相关描述，在此不再赘述。
S516，PCF网元向AF网元发送计费策略更新失败消息或计费策略创建失败消息。
S517，AF网元向PCF网元发送业务流策略取消消息，PCF网元接收来自AF网元的业务流策略取消消息。
其中，S516、S517的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
需要说明的是，S517在图5中为虚线示出，表示S517为可选步骤，换言之，若要优化配置，释放冗余资源，AF网元可执行S517；否则，AF网元可不执行S517。此外，S512-S517图5中为虚线示出，表示S512-S517为可选步骤，且S512-S515与S516-S517的执行为“或”的关系，若确定未接收到来自AF网元的第四指示信息和来自SMF网元的订阅通知消息，可执行S512-S515；否则，则执行S516-S617。
示例性地，图6为本申请实施例提供的通信方法的流程示意图三。该通信方法可以适用于图1和图2所示的PCF网元、SMF网元、CHF网元、UPF网元、UDM网元、UDR网元、NEF网元、AF网元之间的通信。如图6所示，该通信方法可以包括如下步骤：
S601，远程终端设备向SMF网元发送第一标识或第二标识。
相应地，SMF网元接收来自远程终端设备的第一标识或第二标识。
具体地，远程终端设备可以经由中继设备、RAN网元(图6中未示出)、AMF网元(图6中未示出)向SMF网元发送第一标识或第二标识。
其中，S601的具体实现可以参考S401中的相关描述，在此不再赘述。
S602，SMF网元从UDM网元获取远程终端设备的会话管理签约数据。
S603，SMF网元向PCF网元发送第一标识。
S604，PCF网元向UDM网元或UDR网元发送第一标识。
S605，PCF网元向UDM网元或UDR网元发送第一指示信息。
其中，S602的具体实现可以参考第二种和第三种实现场景中的相关描述，S603的具体实现可以参考S401中的相关描述，S604的具体实现可以参考S402和第四种实现场景中的相关描述，S605的具体实现可以参考第四种实现场景中的相关描述，在此不再赘述。
需要说明的是，S602在图6中为虚线，表示S602为可选步骤，换言之，若要获取远程终端设备的会话管理签约数据，在S601之后，SMF网元可执行S602；否则，在S601之后，SMF网元可直接向PCF网元发送远程终端设备的第一标识，即执行S603。
此外，S604和S606在图6中为虚线，表示S604和S606为可选步骤，换言之，PCF网元从UDM网元或UDR网元获取第一计费策略仅为一种可选方式，比如，PCF网元还可以从PCF网元本地获取第一计费策略。S605在图6中为虚线示出，表示S605也为可选步骤，换言之，若要获取适用于中继接入方式的第一计费策略，PCF网元可执行S605；否则，PCF网元可以不执行S605。此外，S605和S604的执行顺序不限定。
S606，UDM网元或UDR网元向PCF网元发送第一计费策略，PCF网元接收来自UDM网元或UDR网元的第一计费策略。
S607，PCF网元向SMF网元发送第一计费策略。
S608，SMF网元根据第一计费策略，向UPF网元发送第一上报规则。
S609，SMF网元根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略。
S610，SMF网元根据第三计费策略，向UPF网元发送第三上报规则。
其中，S606的具体实现可以参考S506、S402、第一种实现场景和第四种实现场景中的相关描述，S607的具体实现可以参考S402和第一种实现场景中的相关描述，S608的具体实现可以参考S403中的相关描述，S609的具体实现可以参考第二种实现场景中的相关描述，S610的具体实现可以参考S403中的相关描述，在此不再赘述。
需要说明的是，S608-S610在图6中为虚线示出，表示S608-S610为可选步骤。其中，若SMF网元不需要重新确定远程终端设备的计费策略，可执行S608；若SMF网元需要重新确定远程终端设备的计费策略，则可执行S609-S610。
S611，UPF网元向SMF网元上报远程终端设备的计费信息，SMF网元接收来自UPF网元的远程终端设备的计费信息。
具体地，UPF网元可根据配置的第一计费规则或第三计费规则，周期性地统计远程终端设备的计费信息，并周期性地上报给SMF网元。
其中，远程终端设备的计费信息可以包括如下一项或多项信息：多单元用量(multiple unit usage)、费率组、或使用的单元容器(used unit container)。其中，费率组可包括PDU会话的费率，该PDU会话为远程终端设备使用的PDU会话。多单元用量可以包括管理参数，该管理参数用于管理该PDU会话的配额和/或报告该PDU会话用量。使用的单元容器用于表示该PDU会话在当前周期内消耗的业务量。
可选地，本申请实施例以计费信息可以包括：多单元用量、费率组和使用的单元容器为例进行介绍，但不作为限定。
S612，SMF网元向CHF网元发送计费数据请求消息。
S613，AF网元向PCF网元发送第二计费策略，PCF网元接收来自AF网元的第二计费策略。
S614，AF网元向PCF网元发送第四指示信息，PCF网元接收来自AF网元的第四指示信息。
其中，S612的具体实现可以参考第九种实现场景的相关描述，S613的具体实现可以参考第五种实现场景中的相关描述，S614的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
需要说明的是，S614在图6中为虚线示出，表示S614为可选步骤，换言之，若要进一步控制第二计费策略的配置，AF网元可执行S614；否则，AF网元可不执行S614。此外，S613和S614的执行顺序不限定。
S615，PCF网元向SMF网元发送第二计费策略。
S616，PCF网元根据第二计费策略，更新第一计费策略或第三计费策略。
S617，SMF网元根据第二计费策略，向UPF网元发送第二上报规则。
S618，PCF网元向AF网元发送计费策略更新失败消息或计费策略创建失败消息。
S619，AF网元向PCF网元发送业务流策略取消消息，PCF网元接收来自AF网元的业务流策略取消消息。
其中，S615、S616的具体实现可以参考第六种和第七种实现场景中的相关描述，S617的具体实现可以参考S403中的相关描述，S618、S619的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
需要说明的是，S619在图6中为虚线示出，表示S619为可选步骤，换言之，若要优化配置，释放冗余资源，AF网元可执行S619；否则，AF网元可不执行S619。此外，S614-S619在图6中为虚线示出，表示S614-S619整体为可选步骤，且S614-S617与S618-S619的执行为“或”的关系，若确定未接收到来自AF网元的第四指示信息和来自SMF网元的订阅通知消息，可执行S614-S617；否则，则执行S618-S619。
示例性地，图7为本申请实施例提供的通信方法的流程示意图四。该通信方法可以适用于图1和图2所示的PCF网元、SMF网元、CHF网元、UPF网元、UDM网元、UDR网元、NEF网元、AF网元之间的通信。如图7所示，该通信方法包括如下步骤：
S701，远程终端设备向SMF网元发送第一标识或第二标识。
相应地，SMF网元接收来自远程终端设备的第一标识或第二标识。
本申请实施例中，远程终端设备可以经由中继设备、RAN网元(图7中未示出)、AMF网元(图7中未示出)向SMF网元发送第一标识或第二标识。
其中，S701的具体实现可以参考S401中的相关描述，在此不再赘述。
S702，SMF网元从UDM网元获取远程终端设备的会话管理签约数据。
S703，SMF网元向PCF网元发送第一标识。
S704，PCF网元向UDM网元或UDR网元发送第一标识。
S705，PCF网元向UDM网元或UDR网元发送第一指示信息。
其中，S702的具体实现可以参考第二种和第三种实现场景中的相关描述，S703的具体实现可以参考S401中的相关描述，S704的具体实现可以参考S402和第一种实现场景中的相关描述，S705的具体实现可以参考第四种实现场景中的相关描述，在此不再赘述。
需要说明的是，S702在图7中为虚线，表示S702为可选步骤，换言之，若要获取远程终端设备的会话管理签约数据，在S701之后，SMF网元可执行S702；否则，在S701之后，SMF网元可直接向PCF网元发送远程终端设备的第一标识，即执行S703。
此外，S704和S706在图7中为虚线，表示S704和S706为可选步骤，换言之，PCF网元从UDM网元或UDR网元获取第一计费策略仅为一种可选方式，比如，PCF网元还可以从PCF网元本地获取第一计费策略。S705在图7中为虚线示出，表示S705也为可选步骤，换言之，若要获取适用于中继接入方式的第一计费策略，PCF网元可执行S705；否则，PCF网元可以不执行S705。此外，S705和S704的执行顺序不限定。
S706，UDM网元或UDR网元向PCF网元发送第一计费策略，PCF网元接收来自UDM网元或UDR网元的第一计费策略。
S707，PCF网元向SMF网元发送第一计费策略。
其中，S706的具体实现可以参考S506、S402、第一种实现场景、第二种实现场景和第四种实现场景中的相关描述，S707的具体实现可以参考S402和第一种实现场景中的相关描述，在此不再赘述。
S708，PCF网元向SMF网元发送第二指示信息或第三指示信息。
其中，S708的具体实现可以参考第八种实现场景中的相关描述，在此不再赘述。
此外，S708和S707的执行顺序不限定。
S709，SMF网元向中继设备发送第二指示信息或第三指示信息。
S710，SMF网元根据第一计费策略，向UPF网元发送第一上报规则。
S711，SMF网元根据会话管理签约数据和第一计费策略，确定远程终端设备的第三计费策略。
其中，其中，S709的具体实现可以参考第八种实现场景中的相关描述，S710的具体实现可以参考S403中的相关描述，S711的具体实现可以参考第二种和第三种实现场景中的相关描述，在此不再赘述。此外，S709、S710和S711的执行顺序不限定。
S712，SMF网元根据第三计费策略，向UPF网元发送第三上报规则。
其中，S712的具体实现可以参考S403中的相关描述，在此不再赘述。
需要说明的是，S710-S712在图7中为虚线示出，表示S710-S712为可选步骤。其中，若SMF网元不需要重新确定远程终端设备的计费策略，可执行S710；若SMF 网元需要重新确定远程终端设备的计费策略，则可执行S711-S712。
S713，UPF网元向SMF网元上报远程终端设备的计费信息，SMF网元接收来自UPF网元的远程终端设备的计费信息。
其中，S713的具体实现可以参考S611，在此不再赘述。
S714，SMF网元向CHF网元发送计费数据请求消息。
其中，S714的具体实现可以参考第九种实现场景中的相关描述，在此不再赘述。
S715，AF网元向PCF网元发送第二计费策略，PCF网元接收来自AF网元的第二计费策略。
S716，AF网元向PCF网元发送第四指示信息，PCF网元接收来自AF网元的第四指示信息。
其中，S715的具体实现可以参考第五种实现场景中的相关描述，S716的具体实现可以参考第六种和第七种实现场景中的相关描述。
需要说明的是，S716在图7中为虚线示出，表示S716为可选步骤，换言之，若要进一步控制第二计费策略的配置，AF网元可执行S716；否则，AF网元可不执行S716。此外，S716和S715的执行顺序不限定。
S717，PCF网元向SMF网元发送第二计费策略。
S718，PCF网元根据第二计费策略，更新第一计费策略。
S719，SMF网元根据第二计费策略，向UPF网元发送第二上报规则。
S720，PCF网元向AF网元发送计费策略更新失败消息或计费策略创建失败消息。
S721，AF网元向PCF网元发送业务流策略取消消息，PCF网元接收来自AF网元的业务流策略取消消息。
其中，S717、S718的具体实现可以参考第六种和第七种实现场景中的相关描述，S719的具体实现可以参考S403中的相关描述，S720、S721的具体实现可以参考第六种和第七种实现场景中的相关描述，在此不再赘述。
需要说明的是，S721在图7中为虚线示出，表示S721为可选步骤，换言之，若要优化配置，释放冗余资源，AF网元可执行S721；否则，AF网元可不执行S721。此外，S716-S721在图7中为虚线示出，表示S716-S721整体为可选步骤，且S716-S719与S720-S721的执行为“或”的关系，若确定未接收到来自AF网元的第四指示信息和来自SMF网元的订阅通知消息，可执行S716-S719；否则，则执行S720-S721。
本申请实施例中，由于策略控制网元能够从会话管理网元获得远程终端设备的第一标识，故策略控制网元可根据第一标识而向会话管理网元发送远程终端设备的第一计费策略。如此，会话管理网元便可根据第一计费策略为用户面网元配置远程终端设备的第一上报规则，以便在远程终端设备通过中继设备接入无线网络后，用户面网元可根据第一上报规则，向计费功能网元上报远程终端设备的计费信息，从而实现对远程终端设备的单独计费。
以上结合图4-图7详细说明了本申请实施例提供的通信方法。以下结合图8详细说明用于执行本申请实施例提供的通信方法的通信装置。
示例性地，图8是本申请实施例提供的通信装置的结构示意图一。如图8所示，通信装置800包括：处理模块801和收发模块802。为了便于说明，图8仅示出了该 通信装置800的主要部件。
一些实施例中，通信装置800可适用于图1和图2中所示出的通信系统中，执行图4中所示出的通信方法中策略控制网元的功能，或者，执行图5-图7中所示出的通信方法中PCF网元的功能。
其中，处理模块801，用于执行S402、S514、S616、S718。
收发模块802，用于执行S504-S507、S511-S513、S516-S517、S604-S607、S613-S615，S618-S619、S704-S708、S715-S717、S720-S721。
需要说明的是，通信装置800可以为策略控制网元或PCF网元，或者可设置于该策略控制网元或PCF网元中的芯片(系统)或其他部件或组件，或者包含该策略控制网元或PCF网元的装置；或者，该通信装置800还可以为网络设备，或者可设置于该网络设备中的芯片(系统)或其他部件或组件，或者包含该网络设备的装置。
另一些实施例中，通信装置800可适用于图1和图2中所示出的通信系统中，执行图4中所示出的通信方法中会话管理网元的功能，或者，执行图5-图7中所示出的通信方法中SMF网元的功能。
其中，处理模块801，用于执行S403、S509、S609、S711，以及还用于控制收发模块802执行S502、S508、S510、S515、S602、S608、S610、S617、S702、S712、S719。
收发模块802，用于执行S401、S501、S503、S601、S603、S611-S612、S701、S703、S709、S713-S714。
需要说明的是，通信装置800可以为会话管理网元或SMF网元，或者可设置于该会话管理网元或SMF网元中的芯片(系统)或其他部件或组件，或者包含该会话管理网元或SMF网元的装置；或者，该通信装置800还可以为网络设备，或者可设置于该网络设备中的芯片(系统)或其他部件或组件，或者包含该网络设备的装置。
可选地，收发模块802可以包括接收模块和发送模块(图8中未示出)。其中，收发模块802用于实现通信装置800的发送功能和接收功能。
可选地，通信装置800还可以包括存储模块(图8中未示出)，该存储模块存储有程序或指令。当处理模块801执行该程序或指令时，使得通信装置800可以执行图4所示出的通信方法中会话管理网元的功能，或者执行图5-图7所示出的通信方法中SMF网元的功能。
应理解，通信装置800中涉及的处理模块801可以由处理器或处理器相关电路组件实现，可以为处理器或处理单元；收发模块802可以由收发器或收发器相关电路组件实现，可以为收发器或收发单元。
此外，通信装置800的技术效果可以参考第图4-图7中任一项所示出的通信方法的技术效果，此处不再赘述。
示例性地，图9为本申请实施例提供的通信装置的结构示意图二。该通信装置可以是终端设备或网络设备，也可以是可设置于终端设备或网络设备的芯片(系统)或其他部件或组件。如图9所示，通信装置900可以包括处理器901。可选地，通信装置900还可以包括存储器902和/或收发器903。其中，处理器901与存储器902和收发器903耦合，如可以通过通信总线连接。
下面结合图9对通信装置900的各个构成部件进行具体的介绍：
其中，处理器901是通信装置900的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器901是一个或多个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
可选地，处理器901可以通过运行或执行存储在存储器902内的软件程序，以及调用存储在存储器902内的数据，执行通信装置900的各种功能。
在具体的实现中，作为一种实施例，处理器901可以包括一个或多个CPU，例如图9中所示出的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置900也可以包括多个处理器，例如图2中所示的处理器901和处理器904。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
其中，所述存储器902用于存储执行本申请方案的计算机程序，并由处理器901来执行，以实现上述各方法实施例提供的方法，例如，执行上述方法实施例中策略功能网元或SMF网元的方法，具体可以参考上述方法实施例，此处不再赘述。
可选地，存储器902可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器902可以和处理器901集成在一起，也可以独立存在，并通过通信装置900的接口电路(图9中未示出)与处理器901耦合，本申请实施例对此不作具体限定。
收发器903，用于与其他通信装置800之间的通信。例如，通信装置900为终端设备，收发器903可以用于与网络设备通信，或者与另一个终端设备通信。又例如，通信装置900为网络设备，收发器903可以用于与终端设备通信，或者与另一个网络设备通信。
可选地，收发器903包括接收器和发送器(图9中未单独示出)。其中，接收器用于实现接收功能，发送器用于实现发送功能。
可选地，收发器903和处理器901集成在一起，也可以独立存在，并通过通信装置900的接口电路(图9中未示出)与处理器901耦合，本申请实施例对此不作具体限定。
需要说明的是，图9中示出的通信装置900的结构并不构成对该通信装置的限定，实际的通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的 部件布置。
此外，通信装置900的技术效果可以参考上述方法实施例所述的通信方法的技术效果，此处不再赘述。
本申请实施例还提供一种芯片系统，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例提供一种通信系统。该通信系统包括一个或多个网络设备；进一步地，该通信系统还可以包括上述一个或多个终端设备，例如，远程终端设备，中继设备。
应理解，在本申请实施例中的处理器可以是中央处理单元(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)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM， DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件(如电路)、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其他的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些 接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其他的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (80)

  1. 一种通信方法，其特征在于，包括：
    策略控制网元接收来自会话管理网元的远程终端设备的第一标识，其中，所述远程终端设备通过中继设备接入无线网络；
    所述策略控制网元根据所述第一标识，向所述会话管理网元发送所述远程终端设备的第一计费策略。
  2. 根据权利要求1所述的通信方法，其特征在于，所述第一计费策略包括如下一项或多项：会话计费规则、或业务计费规则。
  3. 根据权利要求2所述的通信方法，其特征在于，所述第一计费策略还包括：状态订阅指示；
    其中，所述状态订阅指示用于订阅所述远程终端设备的连接状态，和/或，业务流状态。
  4. 根据权利要求2所述的通信方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第一标识，获取所述第一计费策略。
  5. 根据权利要求4所述的通信方法，其特征在于，所述策略控制网元根据所述第一标识，获取所述第一计费策略，包括：
    所述策略控制网元根据所述第一标识，从第一设备获取所述第一计费策略；
    其中，所述第一设备包括：所述策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
  6. 根据权利要求1-5中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述策略控制网元向第二设备发送第一指示信息；
    其中，所述第二设备包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元；
    其中，所述第一指示信息用于指示：所述远程终端设备通过所述中继设备接入无线网络。
  7. 根据权利要求1-6中任一项所述的通信方法，其特征在于，所述第一计费策略包括如下一项或多项：所述第一标识、或所述中继设备为所述远程终端设备分配的端口号。
  8. 根据权利要求1-6中任一项所述的通信方法，其特征在于，所述策略控制网元接收来自会话管理网元的远程终端设备的第一标识，包括：
    所述策略控制网元接收来自所述会话管理网元的第一消息；
    其中，所述第一消息携带所述第一标识，所述第一消息为会话策略关联建立请求消息或会话策略关联更改请求消息。
  9. 根据权利要求1-6中任一项所述的通信方法，其特征在于，所述第一标识包括如下一项或多项：签约永久标识SUPI、一般公共订阅标识GPSI、用户隐藏标识SUCI、或所述中继设备为所述远程终端设备分配的端口号。
  10. 根据权利要求1-9中任一项所述的通信方法，其特征在于，所述方法还包括：
    当所述中继设备已建立的协议数据单元PDU会话中，存在计费策略与所述第一计费策略匹配的PDU会话时，所述策略控制网元向所述会话管理网元发送第二指示信 息；
    其中，所述第二指示信息用于指示：允许所述远程终端设备使用匹配的PDU会话。
  11. 根据权利要求1-9中任一项所述的通信方法，其特征在于，所述方法还包括：
    当所述中继设备已建立的协议数据单元PDU会话中，不存在计费策略与所述第一计费策略与匹配的PDU会话时，所述策略控制网元向所述会话管理网元发送第三指示信息；
    其中，所述第三指示信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第三指示信息还用于指示：所述远程终端设备与所述中继设备断开连接。
  12. 根据权利要求11所述的通信方法，其特征在于，所述第三指示信息包括：第一子信息和第二子信息；
    其中，所述第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话；所述第二子信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第二子信息还用于指示：所述远程终端设备与所述中继设备断开连接。
  13. 根据权利要求1-4中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述策略控制网元接收来自应用功能网元的第二计费策略；
    若所述第二计费策略用于通过中继设备接入无线网络的设备的计费，则所述策略控制网元向所述会话管理网元发送所述第二计费策略；或者，
    若所述第二计费策略不用于通过中继设备接入无线网络的设备的计费，则所述策略控制网元向所述应用功能网元发送计费策略更新失败消息或计费策略创建失败消息。
  14. 根据权利要求13所述的通信方法，其特征在于，所述方法还包括：
    所述策略控制网元接收来自所述应用功能网元的第四指示信息，其中，所述第四指示信息用于指示：所述第二计费策略不用于通过中继设备接入无线网络的设备的计费。
  15. 根据权利要求13或14所述的通信方法，其特征在于，所述第二计费策略用于通过中继设备接入无线网络的设备的计费，所述方法还包括：
    所述策略控制网元根据所述第二计费策略，更新所述第一计费策略。
  16. 根据权利要求1-15中任一项所述的通信方法，其特征在于，
    所述远程终端设备与所述中继设备连接，所述第一计费策略处于激活状态；或者，
    所述远程终端设备与所述中继设备断开连接，所述第一计费策略处于非激活状态。
  17. 根据权利要求1-16中任一项所述的通信方法，其特征在于，所述远程终端设备与所述中继设备的连接或业务流断开，所述方法还包括：
    所述策略控制网元向应用功能网元发送计费通知消息，所述计费通知消息用于通知所述远程终端设备的连接或业务流断开。
  18. 一种通信方法，其特征在于，包括：
    会话管理网元向策略控制网元发送远程终端设备的第一标识，其中，所述远程终端设备通过中继设备接入无线网络；
    所述会话管理网元接收来自所述策略控制网元的所述远程终端设备的第一计费策略；
    所述会话管理网元根据所述第一计费策略，向用户面网元发送第一上报规则，其中，所述第一上报规则用于所述用户面网元上报所述远程终端设备的流量用量。
  19. 根据权利要求18所述的通信方法，其特征在于，所述方法还包括：
    所述会话管理网元向计费功能网元发送计费数据请求消息，所述计费数据请求消息携带有所述第一标识。
  20. 根据权利要求19所述的通信方法，其特征在于，所述计费数据请求消息还携带有所述中继设备的标识。
  21. 根据权利要求19或20所述的通信方法，其特征在于，所述计费数据请求消息携带有每个所述远程终端设备的如下一项或多项信息：多单元用量、费率组、或使用的单元容器。
  22. 根据权利要求18-21中任一项所述的通信方法，其特征在于，所述第一计费策略包括如下一项或多项：会话计费规则、或业务计费规则。
  23. 根据权利要求22所述的通信方法，其特征在于，所述第一计费策略还包括：状态订阅指示；
    其中，所述状态订阅指示用于所述策略控制网元订阅所述远程终端设备的连接状态，和/或，业务流状态。
  24. 根据权利要求18-23中任一项所述的通信方法，其特征在于，所述第一计费策略包括如下一项或多项：所述第一标识、或所述中继设备为所述远程终端设备分配的端口号。
  25. 根据权利要求18-24中任一项所述的通信方法，其特征在于，
    所述第一计费策略为所述策略控制网元根据所述第一标识从第一设备获取；
    其中，所述第一设备包括：所述策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
  26. 根据权利要求18-25中任一项所述的通信方法，其特征在于，所述会话管理网元向策略控制网元发送远程终端设备的第一标识，包括：
    所述会话管理网元向所述策略控制网元发送第一消息；
    其中，所述第一消息携带所述第一标识，所述第一消息为会话策略关联建立请求消息或会话策略关联更改请求消息。
  27. 根据权利要求18-24中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述会话管理网元接收来自所述远程终端设备的第二标识；
    所述会话管理网元向统一数据管理网元发送所述第二标识；
    所述会话管理网元接收来自所述统一数据管理网元的所述第一标识。
  28. 根据权利要求27所述的通信方法，其特征在于，
    所述第一标识包括：签约永久标识SUPI。
  29. 根据权利要求27或28所述的通信方法，其特征在于，
    所述第二标识包括如下一项或多项：一般公共订阅标识GPSI、用户隐藏标识SUCI、或应用功能网元为所述远程终端设备分配的标识。
  30. 根据权利要求18-29中任一项所述的通信方法，其特征在于，所述方法还包括：
    接收来自所述策略控制网元的第二计费策略；
    根据所述第二计费策略，向所述用户面网元发送第二上报规则；
    其中，所述第二计费策略为所述远程终端设备的计费策略，所述第二上报规则用于所述用户面网元上报所述远程终端设备的流量用量。
  31. 根据权利要求18-30中任一项所述的通信方法，其特征在于，所述方法还包括：
    从统一数据管理网元获取所述远程终端设备的会话管理签约数据；
    根据所述会话管理签约数据和所述第一计费策略，确定所述远程终端设备的第三计费策略；
    根据所述第三计费策略，向所述用户面网元发送第三上报规则；
    其中，所述第三上报规则用于所述用户面网元上报所述远程终端设备的流量用量。
  32. 根据权利要求31所述的通信方法，其特征在于，所述会话管理签约数据包括：协议数据单元PDU会话计费特性信息，所述PDU会话计费特性信息包括：第一部分信息，所述第一计费策略的会话计费规则包括：第二部分信息和第三部分信息；
    其中，所述第一部分信息与所述第三部分信息的类型相同且内容不相同，所述第一部分信息与所述第二部分信息的类型和内容均不相同；
    所述第三计费策略中的会话计费规则包括：所述第一部分信息和所述第二部分信息。
  33. 根据权利要求31所述的通信方法，其特征在于，所述方法还包括：
    向所述统一数据管理网元发送第五指示信息；其中，所述第五指示信息用于指示：所述远程终端设备通过所述中继设备接入无线网络。
  34. 根据权利要求18-33中任一项所述的通信方法，其特征在于，所述方法还包括：
    接收来自所述策略控制网元的第二指示信息；其中，所述第二指示信息用于指示：允许所述远程终端设备使用所中继设备已建立的协议数据单元PDU会话；
    向所述中继设备发送所述第二指示信息。
  35. 根据权利要求34所述的通信方法，其特征在于，所述第二指示信息携带在N1消息中。
  36. 根据权利要求18-33中任一项所述的通信方法，其特征在于，所述方法还包括：
    接收来自所述策略控制网元的第三指示信息；
    向所述中继设备发送所述第三指示信息；
    其中，所述第三指示信息用于指示：不允许所述远程终端设备使用所述中继设备已建立的协议数据单元PDU会话；或者，所述第三指示信息用于指示：所述远程终端设备与所述中继设备断开连接。
  37. 根据权利要求36所述的通信方法，其特征在于，所述第三指示信息携带在N1消息中。
  38. 根据权利要求36或37所述的通信方法，其特征在于，所述第三指示信息包括：第一子信息和第二子信息；
    其中，所述第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话；所述第二子信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第二子信息用于指示：所述远程终端设备与所述中继设备断开连接。
  39. 一种通信装置，其特征在于，所述通信装置包括收发模块和处理模块；
    所述收发模块，用于接收来自会话管理网元的远程终端设备的第一标识；
    所述处理模块，用于根据所述第一标识，控制所述收发模块向所述会话管理网元发送第一计费策略；
    其中，所述远程终端设备通过中继设备接入无线网络。
  40. 根据权要求39所述的通信装置，其特征在于，所述第一计费策略包括如下一项或多项：会话计费规则、或业务计费规则。
  41. 根据权要求40所述的通信装置，其特征在于，所述第一计费策略还包括：状态订阅指示；
    其中，所述状态订阅指示用于订阅所述远程终端设备的连接状态。
  42. 根据权要求40所述的通信装置，其特征在于，
    所述处理模块，还用于根据所述第一标识，控制所述收发模块获取所述第一计费策略。
  43. 根据权要求42所述的通信装置，其特征在于，
    所述处理模块，还用于根据所述第一标识，控制所述收发模块从第一设备获取所述第一计费策略；
    其中，所述第一设备包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
  44. 根据权要求39-43中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于向第二设备发送第一指示信息；
    其中，所述第二设备包括：统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元；
    其中，所述第一指示信息用于指示：所述远程终端设备通过所述中继设备接入无线网络。
  45. 根据权要求39-44中任一项所述的通信装置，其特征在于，所述第一计费策略包括如下一项或多项：所述第一标识、或所述中继设备为所述远程终端设备分配的端口号。
  46. 根据权要求39-44中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述会话管理网元的第一消息；
    其中，所述第一消息携带所述第一标识，所述第一消息为会话策略关联建立请求消息或会话策略关联更改请求消息。
  47. 根据权要求39-44中任一项所述的通信装置，其特征在于，所述第一标识包括如下一项或多项：签约永久标识SUPI、一般公共订阅标识GPSI、用户隐藏标识SUCI、或应用功能网元中继设备为应用功能网元远程终端设备分配的端口号。
  48. 根据权要求39-47中任一项所述的通信装置，其特征在于，当所述中继设备已建立的协议数据单元PDU会话中，存在计费策略与所述第一计费策略匹配的PDU会话时，所述收发模块，还用于向所述会话管理网元发送第二指示信息；
    其中，所述第二指示信息用于指示：允许所述远程终端设备使用匹配的PDU会话。
  49. 根据权要求39-47中任一项所述的通信装置，其特征在于，当所述中继设备已建立的协议数据单元PDU会话中，不存在计费策略与所述第一计费策略与匹配的PDU 会话时，所述收发模块，还用于向所述会话管理网元发送第三指示信息；
    其中，所述第三指示信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第三指示信息用于指示：所述远程终端设备与所述中继设备断开连接。
  50. 根据权要求49所述的通信装置，其特征在于，所述第三指示信息包括：第一子信息和第二子信息；
    其中，所述第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会话；
    其中，所述第二子信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第二子信息用于指示：所述远程终端设备与所述中继设备断开连接。
  51. 根据权要求39或42中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自应用功能网元的第二计费策略；
    若所述第二计费策略用于通过所述中继设备接入无线网络的设备的计费，则所述收发模块，还用于向所述会话管理网元发送所述第二计费策略；
    或者，若所述第二计费策略不用于通过所述中继设备接入无线网络的设备的计费，则所述收发模块，还用于向所述应用功能网元发送计费策略更新失败消息或计费策略创建失败消息。
  52. 根据权要求51所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述应用功能网元的第四指示信息；
    其中，所述第四指示信息用于指示：所述第二计费策略不用于通过所述中继设备接入无线网络的设备的计费。
  53. 根据权要求51或52所述的通信装置，其特征在于，所述第二计费策略用于通过所述中继设备接入无线网络的设备的计费；
    所述处理模块，还用于根据所述第二计费策略，更新所述第一计费策略。
  54. 根据权要求39-53中任一项所述的通信装置，其特征在于，所述远程终端设备与所述中继设备连接，所述第一计费策略处于激活状态；或者，
    所述远程终端设备与所述中继设备断开连接，所述第一计费策略处于非激活状态。
  55. 根据权要求39-54中任一项所述的通信装置，其特征在于，所述远程终端设备与所述中继设备的连接或业务流断开；
    所述收发模块，还用于向应用功能网元发送计费通知消息；其中，所述计费通知消息用于通知所述远程终端设备的连接或业务流断开。
  56. 一种通信装置，其特征在于，所述通信装置包括：收发模块和处理模块；
    所述收发模块，用于向策略控制网元发送远程终端设备的第一标识；其中，所述远程终端设备通过中继设备接入无线网络；
    所述收发模块，还用于接收来自所述策略控制网元的所述远程终端设备的所述第一计费策略；
    所述处理模块，用于根据所述第一计费策略，控制所述收发模块向用户面网元发送第一上报规则；
    其中，所述第一上报规则用于所述用户面网元上报所述远程终端设备的流量用量。
  57. 根据权利要求56所述的通信装置，其特征在于，
    所述收发模块，还用于向计费功能网元发送计费数据请求消息，所述计费数据请求消息携带有所述第一标识。
  58. 根据权利要求57所述的通信装置，其特征在于，所述计费数据请求消息还携带有所述中继设备的标识。
  59. 根据权利要求57或58所述的通信装置，其特征在于，所述计费数据请求消息携带有每个所述远程终端设备的如下一项或多项信息：多单元用量、费率组、或使用的单元容器。
  60. 根据权利要求56-59中任一项所述的通信装置，其特征在于，所述第一计费策略包括如下一项或多项：会话计费规则、或业务计费规则。
  61. 根据权利要求60所述的通信装置，其特征在于，所述第一计费策略还包括：状态订阅指示；
    其中，所述状态订阅指示用于所述策略控制网元订阅所述远程终端设备的连接状态。
  62. 根据权利要求56-61中任一项所述的通信装置，其特征在于，所述第一计费策略包括如下一项或多项：所述第一标识、或所述中继设备为所述远程终端设备分配的端口号。
  63. 根据权利要求56-62中任一项所述的通信装置，其特征在于，所述第一计费策略为所述策略控制网元根据所述第一标识从第一设备获取；
    其中，所述第一设备包括：所述策略控制网元、统一数据管理网元、统一数据储存网元、计费功能网元、或应用功能网元。
  64. 根据权利要求56-61中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于向所述策略控制网元发送第一消息；
    其中，所述第一消息携带所述第一标识，所述第一消息为会话策略关联建立请求消息或会话策略关联更改请求消息。
  65. 根据权利要求64所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述远程终端设备的第二标识；
    所述收发模块，还用于向统一数据管理网元发送所述第二标识，以及接收来自所述统一数据管理网元的所述第一标识。
  66. 根据权利要求65所述的通信装置，其特征在于，所述第一标识包括：签约永久标识SUPI。
  67. 根据权利要求65或66所述的通信装置，其特征在于，所述第二标识包括如下一项或多项：一般公共订阅标识GPSI、用户隐藏标识SUCI、或应用功能网元为远程终端设备分配的标识。
  68. 根据权利要求56-67中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述策略控制网元的第二计费策略；
    所述处理模块，还用于根据所述第二计费策略，控制所述收发模块向所述用户面网元发送第二上报规则；
    其中，所述第二计费策略为所述远程终端设备的计费策略；
    其中，所述第二上报规则用于所述用户面网元上报流量用量。
  69. 根据权利要求56-68中任一项所述的通信装置，其特征在于，
    所述处理模块，还用于控制所述收发模块从统一数据管理网元获取所述远程终端设备的会话管理签约数据；
    所述处理模块，还用于根据所述会话管理签约数据和所述第一计费策略，确定所述远程终端设备的第三计费策略；以及根据所述第三计费策略，控制所述收发模块向所述用户面网元发送第三上报规则；
    其中，所述第三上报规则用于所述用户面网元上报流量用量。
  70. 根据权利要求69所述的通信装置，其特征在于，
    所述会话管理签约数据中包括：协议数据单元PDU会话计费特性信息；
    所述PDU会话计费特性信息中包括：第一部分信息；
    所述第一计费策略的会话计费规则包括：第二部分信息和第三部分信息；
    其中，所述第一部分信息与所述第三部分信息的类型相同且内容不相同，所述第一部分信息与所述第二部分信息的类型和内容均不相同；
    所述第三计费策略中的会话计费规则包括：所述第一部分信息和所述第二部分信息。
  71. 根据权利要求69所述的通信装置，其特征在于，
    所述收发模块，还用于向所述统一数据管理网元发送第五指示信息；
    其中，所述第五指示信息用于指示：所述远程终端设备通过所述中继设备接入无线网络。
  72. 根据权利要求56-70中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述收发模块，还用于策略控制网元的第二指示信息；
    所述收发模块，还用于向中继设备发送所述第二指示信息；
    其中，所述第二指示信息用于指示：允许所述远程终端设备使用所述中继设备已建立的协议数据单元PDU会话。
  73. 根据权利要求72所述的通信装置，其特征在于，第二指示信息携带在N1消息中。
  74. 根据权利要求56-70中任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述策略控制网元的第三指示信息；
    所述收发模块，还用于向中继设备发送第三指示信息；
    其中，所述第三指示信息用于指示：不允许所述远程终端设备使用所述中继设备已建立的协议数据单元PDU会话；或者，所述第三指示信息用于指示：所述远程终端设备与所述中继设备断开连接。
  75. 根据权利要求74所述的通信装置，其特征在于，所述第三指示信息携带在N1消息中。
  76. 根据权利要求74或75所述的通信装置，其特征在于，所述第三指示信息包括：第一子信息和第二子信息；
    其中，所述第一子信息用于指示：已建立的PDU会话中，不存在匹配的PDU会 话；所述第二子信息用于指示：不允许所述远程终端设备使用已建立的PDU会话；或者，所述第二子信息用于指示：所述远程终端设备与所述中继设备断开连接。
  77. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机指令，当所述处理器执行该指令时，以使所述装置执行如权利要求1-17中任一项所述的通信方法。
  78. 一种通信装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机指令，当所述处理器执行该指令时，以使所述装置执行如权利要求18-38中任一项所述的通信方法。
  79. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机执行如权利要求1-17中任一项所述的通信方法或者执行如权利要求18-38中任一项所述的通信方法。
  80. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机执行如权利要求1-17中任一项所述的通信方法或者执行如权利要求18-38中任一项所述的通信方法。
PCT/CN2021/116143 2020-12-09 2021-09-02 通信方法及装置 WO2022121388A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011433627.8A CN114615636B (zh) 2020-12-09 2020-12-09 通信方法、装置及介质
CN202011433627.8 2020-12-09

Publications (1)

Publication Number Publication Date
WO2022121388A1 true WO2022121388A1 (zh) 2022-06-16

Family

ID=81856720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/116143 WO2022121388A1 (zh) 2020-12-09 2021-09-02 通信方法及装置

Country Status (2)

Country Link
CN (1) CN114615636B (zh)
WO (1) WO2022121388A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115334484A (zh) * 2022-08-15 2022-11-11 中国电信股份有限公司 多跳近域通信统计方法、装置、电子设备和介质
CN116600283A (zh) * 2023-07-19 2023-08-15 中国电信股份有限公司 网络接入方式识别方法、装置、通信设备、介质及产品
CN117041899A (zh) * 2023-10-10 2023-11-10 联通在线信息科技有限公司 边缘鉴权免流计量方法、装置、电子设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105992184A (zh) * 2015-03-04 2016-10-05 阿尔卡特朗讯 一种对ProSe网络中继服务进行协同计费的方法与设备
CN110445623A (zh) * 2018-05-04 2019-11-12 华为技术有限公司 计费方法、设备及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110247849A (zh) * 2019-05-28 2019-09-17 中国联合网络通信集团有限公司 Ursp的更新方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105992184A (zh) * 2015-03-04 2016-10-05 阿尔卡特朗讯 一种对ProSe网络中继服务进行协同计费的方法与设备
CN110445623A (zh) * 2018-05-04 2019-11-12 华为技术有限公司 计费方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NEC: "Solution for Key Issue #7: Charging for PC5 Direct Communication", 3GPP DRAFT; S2-2000312, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051842384 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115334484A (zh) * 2022-08-15 2022-11-11 中国电信股份有限公司 多跳近域通信统计方法、装置、电子设备和介质
CN116600283A (zh) * 2023-07-19 2023-08-15 中国电信股份有限公司 网络接入方式识别方法、装置、通信设备、介质及产品
CN116600283B (zh) * 2023-07-19 2023-10-03 中国电信股份有限公司 网络接入方式识别方法、装置、通信设备、介质及产品
CN117041899A (zh) * 2023-10-10 2023-11-10 联通在线信息科技有限公司 边缘鉴权免流计量方法、装置、电子设备及存储介质
CN117041899B (zh) * 2023-10-10 2024-02-09 联通在线信息科技有限公司 边缘鉴权免流计量方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN114615636B (zh) 2023-07-14
CN114615636A (zh) 2022-06-10

Similar Documents

Publication Publication Date Title
WO2022121388A1 (zh) 通信方法及装置
WO2020187052A1 (zh) 一种网络切片选择方法及装置
WO2021018021A1 (zh) 计费方法、计费系统和通信装置
US20200053802A1 (en) Session management with relaying and charging for indirect connection for internet of things applications in 3gpp network
WO2020248828A1 (zh) 通信方法、装置及系统
CN113906717B (zh) 本地用户平面功能控制
WO2022152238A1 (zh) 一种通信方法及通信装置
JP6907261B2 (ja) 通信システムにおけるデータフロートランスポートのための改善されたプライオリティハンドリング
WO2021057794A1 (zh) 配置业务的方法、通信装置和通信系统
CN105493525A (zh) 服务层南向接口和服务质量
EP4138439A1 (en) Communication method, apparatus, and system
WO2021134380A1 (zh) 管理QoS的方法、中继终端、PCF网元、SMF网元及远程终端
KR20150113151A (ko) 맞춤가능한 이동 광대역 네트워크 시스템 및 이동 광대역 네트워크를 맞춤화하는 방법
WO2017147772A1 (zh) 一种消息传输方法及核心网接口设备
US12010018B2 (en) Wireless communication method and device
WO2013166913A1 (zh) 小量数据上下行传输方法、及相应终端和移动性管理单元
WO2021254001A1 (zh) 会话建立方法、装置、系统及计算机存储介质
WO2021135650A1 (zh) 通信方法及装置
JP2018521562A (ja) 無線ローカルエリアネットワークの並行処理能力を高めるための方法、装置、およびシステム
US20230171672A1 (en) Route configuration method and apparatus
WO2021238331A1 (zh) 获取网络资源的方法、设备及系统
US9749850B2 (en) System and method operable to enable shortest connection route
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
WO2022237857A1 (zh) 确定安全保护开启方式的方法、通信方法及通信装置
CN108934058B (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: 21902096

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21902096

Country of ref document: EP

Kind code of ref document: A1