WO2024021833A1 - 一种热点设备的管理方法、通信装置及通信系统 - Google Patents

一种热点设备的管理方法、通信装置及通信系统 Download PDF

Info

Publication number
WO2024021833A1
WO2024021833A1 PCT/CN2023/096796 CN2023096796W WO2024021833A1 WO 2024021833 A1 WO2024021833 A1 WO 2024021833A1 CN 2023096796 W CN2023096796 W CN 2023096796W WO 2024021833 A1 WO2024021833 A1 WO 2024021833A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
user plane
terminal device
policy
plane network
Prior art date
Application number
PCT/CN2023/096796
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 WO2024021833A1 publication Critical patent/WO2024021833A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • Embodiments of the present application relate to the field of communication technology, and in particular, to a management method for hotspot equipment, a communication device, and a communication system.
  • terminal devices such as smartphones have hotspot sharing functions.
  • other devices such as laptops can use wireless fidelity (WiFi), Bluetooth or Universal Serial Bus (Universal Serial Bus).
  • WiFi wireless fidelity
  • Bluetooth Bluetooth
  • Universal Serial Bus Universal Serial Bus
  • Bus, USB physical connection and other connection methods are connected to the terminal device to achieve the purpose of accessing the Internet.
  • Embodiments of the present application provide a management method, communication device and communication system for hotspot equipment, so as to effectively manage terminal equipment with hotspot sharing functions.
  • embodiments of the present application provide a method for managing hotspot devices.
  • the method can be executed by a user plane network element or a module (such as a chip) applied to a user plane network element.
  • the method includes: the user plane network element receives instruction information from the policy control network element, and the instruction information indicates that when the first event occurs, the third event is sent to the policy control network element.
  • An event the first event is that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold; when the first event occurs, the user plane network element sends the third event to the policy control network element. an event.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and when it is detected that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot
  • the policy control network element is notified, so that the policy control network element learns that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot access threshold, so that the policy control network element can make decisions on the terminal device.
  • the billing method or control method enables reasonable billing and precise control of terminal equipment.
  • the user plane network element receives the hotspot access threshold from the policy control network element; or, the indication information includes the hotspot access threshold.
  • the policy control network element configures the hotspot access threshold for the user plane network element, which can achieve accurate configuration of the hotspot access threshold.
  • the user plane network element determines the hotspot access based on the service package of the terminal device. threshold; or, the user plane network element determines the hotspot access threshold based on the configuration information in the user plane network element.
  • the user plane network element determines the hotspot access threshold, and there is no need for the policy control network element to configure the hotspot access threshold to the user plane network element, which can reduce signaling overhead.
  • the user plane network element receives a first charging rule from the policy control network element, and the first charging rule is determined based on the first event; the user plane network element receives a first charging rule based on the first event.
  • a charging rule is used to charge the terminal device.
  • the above solution can effectively set charging rules and achieve reasonable charging of terminal equipment.
  • the user plane network element receives a first control policy rule from the policy control network element, and the first control policy rule is determined based on the first event; the user plane network element receives a first control policy rule based on the first event; A control policy rule controls the terminal device.
  • the above solution can effectively set control policy rules and achieve reasonable control of terminal devices.
  • the user plane network element when a second event occurs, sends the second event to the policy control network element.
  • the second event represents the number of devices connected to the terminal device through hotspot sharing technology. Less than or equal to the hotspot access threshold.
  • the user plane network element receives a second charging rule from the policy control network element, and the second charging rule is determined based on the second event; the user plane network element receives a second charging rule based on the second event.
  • Charging rules charge the terminal device.
  • the charging rules will be adaptively modified.
  • the above solution can change the charging rules according to the actual situation and achieve reasonable accounting for the terminal device. fee.
  • the above description is applicable to the description of other aspects and will not be described again.
  • the user plane network element receives a second control policy rule from the policy control network element, and the second control policy rule is determined based on the second event; the user plane network element receives a second control policy rule based on the second event. 2. Control policy rules to control the terminal device.
  • control policy rules when the number of devices connected to the terminal device through hotspot sharing technology changes, the control policy rules will be adaptively modified.
  • the above solution can change the control policy rules according to the actual situation to achieve reasonable control of the terminal device. .
  • the above description is applicable to the description of other aspects and will not be described again.
  • the user plane network element receives multiple data packets from the terminal device, and each of the multiple data packets contains a timestamp; the user plane network element receives a time stamp based on the multiple data packets.
  • the timestamp in each data packet of the packet determines the reference value of the clock source corresponding to the multiple data packets; the user plane network element determines the connection through the hotspot sharing technology based on the reference value of the clock source corresponding to the multiple data packets. The number of devices connected to this terminal device.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element determines the number of devices connected to the terminal device through hotspot sharing technology based on the number and/or type of heartbeat messages detected in one or more cycles.
  • the heartbeat message originates from the terminal device or a device connected to the terminal device through hotspot sharing technology.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element obtains the network traffic characteristic parameters corresponding to the Internet Protocol (IP) address in the network; the user plane network element determines the hotspot sharing technology based on the network traffic characteristic parameters. The number of devices connected to this terminal device.
  • IP Internet Protocol
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element obtains multiple Hyper Text Transfer Protocol (Hyper Text Transfer Protocol) Protocol, HTTP) request message, the HTTP request message includes device parameters; the user plane network element determines the number of devices connected to the terminal device through the hotspot sharing technology according to the device parameters in the multiple HTTP request messages.
  • HTTP Hyper Text Transfer Protocol
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • embodiments of the present application provide a method for managing hotspot devices, which method can be executed by a policy control network element or a module (such as a chip) applied to the policy control network element.
  • the method includes: the policy control network element sends instruction information to the user plane network element.
  • the instruction information indicates that when the first event occurs, the first event is sent to the policy control network element.
  • event the first event is that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold; when the first event occurs, the policy control network element receives the third message from the user plane network element. an event.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and when it is detected that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot
  • the policy control network element is notified, so that the policy control network element learns that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot access threshold, so that the policy control network element can make decisions on the terminal device.
  • the billing method or control method enables reasonable billing and precise control of terminal equipment.
  • the policy control network element sends the hotspot access threshold to the user plane network element; or the indication information includes the hotspot access threshold.
  • the policy control network element configures the hotspot access threshold for the user plane network element, which can achieve accurate configuration of the hotspot access threshold.
  • the policy control network element determines a first charging rule based on the first event, and the first charging rule is used to charge the terminal device; the policy control network element provides the user with access to the network. Yuan sends the first billing rule.
  • the above solution can effectively set charging rules and achieve reasonable charging of terminal equipment.
  • the policy control network element determines a first control policy rule based on the first event, and the first control policy rule is used to control the terminal device; the policy control network element sends a message to the user plane network element Send the first control policy rule.
  • the above solution can effectively set control policy rules and achieve reasonable control of terminal devices.
  • the policy control network element receives a second event from the user plane network element.
  • the second event indicates that the number of devices connected to the terminal device through hotspot sharing technology is less than or equal to the number of devices connected to the hotspot. Enter the threshold.
  • the policy control network element determines a second charging rule based on the second event, and the second charging rule is used to charge the terminal device; the policy control network element provides the user with access to the network. Yuan sends the second billing rule.
  • the policy control network element determines a second control policy rule based on the second event, and the second control policy rule is used to control the terminal device; the policy control network element sends a message to the user plane network element. Send the second control policy rule.
  • embodiments of the present application provide a method for managing hotspot devices, which method can be executed by a user plane network element or a module (such as a chip) applied to a user plane network element.
  • the method includes: the user plane network element receives indication information from the policy control network element.
  • the indication information indicates that when the number of devices connected to the terminal device through hotspot sharing technology changes, Then the changed number of devices is sent to the policy control network element; when the number of devices connected to the terminal device through the hotspot sharing technology changes from the first number to the second number, the user plane network element sends the changed number to the policy control network element. Yuan sends the second amount.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and after detecting that the number of devices connected to the terminal device through hotspot sharing technology changes, Send the changed number of devices to the policy control network element, so that the policy control network element decides the billing method or control method for the terminal device based on the changed number of devices, achieving reasonable billing and precise control of the terminal device. .
  • the user plane network element receives a charging rule from the policy control network element, and the charging rule is determined based on the second quantity; and then the user plane network element, according to the charging rule, Charge the terminal device.
  • the above solution can effectively set charging rules and achieve reasonable charging of terminal equipment.
  • the user plane network element receives a control policy rule from the policy control network element, and the control policy rule is determined based on the second quantity; the user plane network element responds to the control policy rule based on the control policy rule.
  • the terminal device is controlled.
  • the above solution can effectively set control policy rules and achieve reasonable control of terminal devices.
  • the user plane network element receives multiple data packets from the terminal device, and each of the multiple data packets contains a timestamp; the user plane network element receives a time stamp based on the multiple data packets.
  • the timestamp in each data packet of the packet determines the reference value of the clock source corresponding to the multiple data packets; the user plane network element determines the connection through the hotspot sharing technology based on the reference value of the clock source corresponding to the multiple data packets. The number of devices connected to this terminal device.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element determines the number of devices connected to the terminal device through hotspot sharing technology based on the number and/or type of heartbeat messages detected in one or more cycles.
  • the heartbeat message originates from the terminal device or a device connected to the terminal device through hotspot sharing technology.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element obtains the network traffic characteristic parameters corresponding to multiple data packets; the user plane network element determines the device that is connected to the terminal device through the hotspot sharing technology based on the network traffic characteristic parameters. quantity.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the user plane network element obtains multiple HTTP request messages, and the HTTP request messages include device parameters; the user plane network element determines the hotspot sharing technology based on the device parameters in the multiple HTTP request messages. The number of devices connected to this terminal device.
  • the above solution can accurately determine the number of devices connected to the terminal device through hotspot sharing technology.
  • embodiments of the present application provide a method for managing hotspot devices, which method can be executed by a policy control network element or a module (such as a chip) applied to the policy control network element.
  • the method includes: the policy control network element sends instruction information to the user plane network element.
  • the instruction information indicates that when the number of devices connected to the terminal device through hotspot sharing technology changes, Then the changed number of devices is sent to the policy control network element; when the number of devices connected to the terminal device through the hotspot sharing technology changes from the first number to the second number, the policy control network element receives data from the user plane The second number of network elements.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and after detecting that the number of devices connected to the terminal device through hotspot sharing technology changes, Send the changed number of devices to the policy control network element, so that the policy control network element can decide the charging method or control method for the terminal device based on the changed number of devices, which helps to achieve reasonable accounting for the terminal device. cost and precise control.
  • the policy control network element determines the charging rule according to the second quantity; the policy control network element sends the charging rule to the user plane network element.
  • the above solution can effectively set charging rules and achieve reasonable charging of terminal equipment.
  • the policy control network element determines the control policy rule according to the second quantity; the policy control network element sends the control policy rule to the user plane network element.
  • the above solution can effectively set control policy rules and achieve reasonable control of terminal devices.
  • embodiments of the present application provide a communication device, which may be a user plane network element or a module (such as a chip) applied in a user plane network element.
  • the device has the function of implementing any implementation method of the above-mentioned first aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a policy control network element or a module (such as a chip) applied in the policy control network element.
  • the device has the function of implementing any implementation method of the above second aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a user plane network element or a module (such as a chip) applied in a user plane network element.
  • the device has the function of implementing any implementation method of the above third aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a policy control network element or a module (such as a chip) applied in the policy control network element.
  • the device has the function of implementing any implementation method of the fourth aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, including a processor coupled to a memory.
  • the processor is configured to call a program stored in the memory to execute any implementation method in the above first to fourth aspects.
  • the memory may be located within the device or external to the device.
  • the processor can be one or more.
  • embodiments of the present application provide a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory, so that the device executes Any implementation method in the above first to fourth aspects.
  • embodiments of the present application provide a communication device, including units or means for executing each step of any implementation method in the above-mentioned first to fourth aspects.
  • embodiments of the present application provide a communication device, including a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and perform any implementation method in the above-mentioned first to fourth aspects.
  • the processor includes one or more.
  • embodiments of the present application further provide a computer-readable storage medium in which instructions are stored, and when run on a communication device, the instructions in the first to fourth aspects are achieved. Any implementation method of is executed.
  • embodiments of the present application further provide a computer program product.
  • the computer program product includes a computer program or instructions.
  • the computer program or instructions are run by a communication device, any one of the above first to fourth aspects is enabled.
  • the implementation method is executed.
  • embodiments of the present application further provide a chip system, including: a processor, configured to execute any of the implementation methods in the above first to fourth aspects.
  • embodiments of the present application further provide a communication system, including: performing any of the steps of the first aspect.
  • embodiments of the present application further provide a communication system, including: a user plane network element used to perform any implementation method in the above third aspect, and a user plane network element used to perform any implementation method in the above fourth aspect.
  • Policy controls network elements.
  • Figure 1 is a schematic diagram of the 5G network architecture based on service-based architecture
  • Figure 2(a) is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application
  • Figure 2(b) is a schematic flow chart of a hotspot device management method provided by an embodiment of the present application
  • Figure 2(c) is an example diagram of determining the number of devices connected to the terminal device through hotspot sharing technology
  • Figure 3 is a schematic flow chart of a hotspot device management method provided by an embodiment of the present application.
  • Figure 4 is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • FIG 1 is a schematic diagram of the fifth generation (5G) network architecture based on service-based architecture.
  • the 5G network architecture shown in Figure 1 can include terminal equipment, access network, core network and data network (DN).
  • Terminal equipment accesses the data network through the access network and core network.
  • the terminal equipment can be user equipment (UE), mobile station, mobile terminal, etc.
  • Figure 1 takes the terminal device as a UE as an example for description.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), and the Internet of Things (internet of things, IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, urban air vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.
  • the access network is used to implement access-related functions. It can provide network access functions for authorized users in a specific area, and can determine transmission links of different qualities to transmit user data based on user levels, business needs, etc.
  • the access network forwards control signals and user data between terminal equipment and the core network.
  • the access network may include access network equipment, which may be equipment that provides access for terminal equipment, and may include wireless access network (radio access network, RAN) equipment and wired access network equipment.
  • Figure 1 takes the access network device as RAN as an example for description.
  • RAN equipment is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, balloon stations, etc.
  • base stations such as macro base stations, micro base stations (also called small stations), relay stations, access points, balloon stations, etc.
  • gNB next-generation Node base station
  • LTE long term evolution
  • eNodeB evolved node B
  • Access network equipment and terminal equipment can be fixed-position or removable. Access network equipment and terminal equipment can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. The embodiments of this application do not limit the application scenarios of access network equipment and terminal equipment.
  • the core network is responsible for maintaining the contract data of the mobile network and providing functions such as session management, mobility management, policy management, and security authentication for terminal devices.
  • the core network includes but is not limited to one or more of the following network elements: application function (AF) network element, unified data management (UDM) network element, policy control function (PCF) network Element, session management function (SMF) network element, access and mobility management function (AMF) network element, user plane function (UPF) network element.
  • AF application function
  • UDM unified data management
  • PCF policy control function
  • SMF session management function
  • AMF access and mobility management function
  • UPF user plane function
  • AMF is mainly responsible for mobility management in mobile networks, such as user location update, user registration network, user switching, etc.
  • SMF is mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users, selecting UPF that provides message forwarding functions, etc.
  • UPF is mainly responsible for forwarding and receiving user data. It can receive user data from the data network and transmit it to the terminal device through the access network device. It can also receive user data from the terminal device through the access network device and forward it to the data network.
  • UDM includes functions such as execution and management of contract data and user access authorization.
  • AF transmits the requirements from the application side to the network side, such as QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IP Multimedia Subsystem (IMS) voice call service.
  • IMS IP Multimedia Subsystem
  • PCF mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.
  • PCF can provide policies to AMF or SMF, such as QoS policies, slice selection policies, etc.
  • DN on which a variety of services can be deployed, can provide data and/or voice services to terminal devices.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of employees of the company can be used as terminal devices.
  • the employees' mobile phones or computers can access information and data resources on the company's internal office network.
  • Namf, Npcf, Nsmf, Nudm, and Naf are the service interfaces provided by the above-mentioned AMF, PCF, SMF, UDM, and AF respectively, and are used to call the corresponding service operations.
  • N1, N2, N3, N4 and N6 are interface serial numbers. The meanings of these interface serial numbers are as follows:
  • N1 The interface between AMF and terminal equipment can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to terminal equipment.
  • NAS non-access stratum
  • N2 The interface between AMF and RAN, which can be used to transmit wireless bearer control information from the core network side to the access network equipment.
  • N3 The interface between RAN and UPF, mainly used to transfer uplink and downlink users between access network equipment and UPF surface data.
  • N4 The interface between SMF and UPF can be used to transfer information between the control plane and the user plane, including controlling the delivery of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane, as well as user plane information. Report.
  • N6 The interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the above network element or function can be implemented by one device, can be implemented by multiple devices, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • Network sharing technology also known as hotspot sharing technology
  • the application of this technology can connect devices such as laptops (Laptops), desktops, tablets (Tablets) or other smart terminals through wired or wireless (such as WiFi, Bluetooth or USB physical Connection) and other connection methods are connected to a smart terminal with Internet access capabilities, so that packet data services can be provided for devices other than the smart terminal with Internet access capabilities.
  • the network sharing technology may be network sharing technology (Tethering), in which an intelligent terminal that provides the Tethering function may be called a Tethering user.
  • Figure 2(a) is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application. The method includes the following steps:
  • Step 201a The policy control network element sends instruction information to the user plane network element.
  • the user plane network element receives the indication information.
  • the policy control network element sends the instruction information to the user plane network element.
  • the policy control network element can send the instruction information to the user plane network element through the session management network element.
  • the policy control network element is the PCF network element
  • the session management network element is the SMF network element
  • the user plane network element is the UPF network element.
  • the policy control network element is the Policy and Charging Rules Function (PCRF) network element
  • the session management network element is the packet data network gateway-control plane (Packet Data Network Gateway-Control Plane, PGW-C) network element.
  • PGW-C Packet Data Network Gateway-Control Plane
  • This user plane network element is a Packet Data Network Gateway-User Plane (PGW-U) network element.
  • the embodiments of this application can also be applied to future communication scenarios, such as the sixth generation (6th generation, 6G) communication scenario, and this application does not limit this.
  • 6G sixth generation
  • the implementation of policy control network elements, session management network elements, and user plane network elements are uniformly explained, and will not be described in detail later.
  • the indication information indicates that when the first event occurs, the first event is sent to the policy control network element.
  • the first event is that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot access threshold, or the first event is that the number of devices connected to the terminal device through hotspot sharing technology is greater than the hotspot access threshold. .
  • Step 202a When the first event occurs, the user plane network element sends the first event to the policy control network element.
  • the policy control network element receives the first event.
  • the user plane network element After receiving the above instruction information, the user plane network element detects the number of devices connected to the terminal device through hotspot sharing technology. When the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology is greater than The hotspot access threshold indicates that the first event occurs, so the user plane network element sends the first event to the policy control network element, thus The policy control network element can learn that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot access threshold.
  • the indication information is used to indicate that when the number of devices accessing the terminal device 1 through the hotspot sharing technology is greater than or equal to 5, it is reported to the policy control network element. Therefore, the user plane network element detects the devices connected to the terminal device 1 through the hotspot sharing technology. When it is detected that the number of devices connected to the terminal device 1 through the hotspot sharing technology is greater than or equal to 5, it reports to the policy control network element. : The number of devices connected to terminal device 1 through hotspot sharing technology is greater than or equal to 5.
  • the user plane network element receives the hotspot access threshold from the policy control network element, that is, the policy control network element provides the hotspot access threshold to the user plane network element.
  • the hotspot access threshold and the above indication information may be sent in the same message, or may be sent in different messages.
  • the above indication information includes the above hotspot access threshold.
  • the user plane network element determines the hotspot access threshold based on the service package of the terminal device. That is, the hotspot access thresholds corresponding to different service packages may be the same or different.
  • the user plane network element determines the hotspot access threshold based on the configuration information in the user plane network element.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and when it is detected that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot
  • the policy control network element is notified, so that the policy control network element learns that the number of devices connected to the terminal device through hotspot sharing technology is greater than or equal to the hotspot access threshold, so that the policy control network element can make decisions on the terminal device.
  • the billing method or control method helps to achieve reasonable billing and precise control of terminal equipment.
  • step 202a after the above step 202a, the following steps 203a and/or 204a may also be performed.
  • Step 203a The policy control network element sends the first charging rule to the user plane network element.
  • the user plane network element receives the first charging rule.
  • the policy control network element After receiving the first event, the policy control network element learns that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold, and then the policy control network element updates the charging rules and obtains the first charging rule. . Then the policy control network element sends the first charging rule to the user plane network element, and the user plane network element charges the terminal device according to the first charging rule.
  • the first charging rule increases the traffic unit price (or traffic usage rate), or the previous no-billing is updated to start charging.
  • the embodiments of this application do not limit the specific implementation method of the charging rules. Therefore, this method can effectively set charging rules and achieve reasonable charging of terminal devices.
  • Step 204a The policy control network element sends the first control policy rule to the user plane network element.
  • the user plane network element receives the first control policy rule.
  • the policy control network element After receiving the first event, the policy control network element learns that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold, and then the policy control network element updates the control policy rules to obtain the first control policy rules . Then the policy control network element sends the first control policy rule to the user plane network element, and the user plane network element controls the terminal device according to the first control policy rule.
  • the first control policy rule limits the traffic bandwidth of the device or reduces the traffic network speed of the device, and so on.
  • the embodiments of this application do not limit the specific implementation method of the control policy rules. This method can effectively set control policy rules and achieve reasonable control of terminal devices.
  • step 205a may also be performed.
  • Step 205a When the second event occurs, the user plane network element sends the second event to the policy control network element.
  • the policy control network element receives the second event.
  • the second event indicates that the number of devices accessed to the terminal device through the hotspot sharing technology is less than or equal to the hotspot access threshold.
  • the second event is an event different from the first event, that is, when the number of devices connected to the terminal device through the hotspot sharing technology changes, for example, the number changes from greater than the hotspot access threshold to less than Or equal to the hotspot access threshold, the user plane network element notifies the policy control network element of the change in this number.
  • the user plane network element can dynamically sense the change in the number and notify the policy control network element of the change in the number in real time, thereby realizing dynamic management of the terminal equipment.
  • step 205a after the above step 205a, the following steps 206a and/or 207a may also be performed.
  • Step 206a The policy control network element sends the second charging rule to the user plane network element.
  • the user plane network element receives the second charging rule.
  • the policy control network element After receiving the second event, the policy control network element learns that the number of devices connected to the terminal device through the hotspot sharing technology is less than or equal to the hotspot access threshold, and then the policy control network element updates the charging rules and obtains the second charging rules. . Then the policy control network element sends the second charging rule to the user plane network element, and the user plane network element charges the terminal device according to the second charging rule.
  • the second charging rule lowers the traffic unit price (or traffic usage rate) compared with the charging rule before the update, or updates the previous charging rule to no charging.
  • the embodiments of this application do not limit the specific implementation method of the charging rules. This method can effectively set charging rules and achieve reasonable charging of terminal devices.
  • Step 207a The policy control network element sends the second control policy rule to the user plane network element.
  • the user plane network element receives the second control policy rule.
  • the policy control network element After receiving the second event, the policy control network element learns that the number of devices connected to the terminal device through the hotspot sharing technology is less than or equal to the hotspot access threshold, and then the policy control network element updates the control policy rules to obtain the second control policy rules . Then the policy control network element sends the second control policy rule to the user plane network element, and the user plane network element controls the terminal device according to the second control policy rule.
  • the first control policy rule increases the bandwidth traffic of the device or increases the traffic network speed of the device, and so on.
  • the embodiments of this application do not limit the specific implementation method of the control policy rules. This method can effectively set control policy rules and achieve reasonable control of terminal devices.
  • the following describes the implementation method for user plane network elements to detect the number of devices connected to terminal devices through hotspot sharing technology.
  • the following methods 1 to 4 are only examples, and this application does not limit the implementation method of the user plane network element detecting the number of devices connected to the terminal device through the hotspot sharing technology.
  • Method 1 The user plane network element receives multiple data packets from the terminal device. Each data packet in the multiple data packets contains a timestamp. The user plane network element receives multiple data packets based on the timestamp in each data packet of the multiple data packets. , determine the reference value of the clock source corresponding to multiple data packets, and the user plane network element determines the number of devices connected to the terminal device through the hotspot sharing technology based on the reference value of the clock source corresponding to the multiple data packets.
  • the terminal device has hotspot sharing turned on and other devices are connected to the terminal device through hotspot sharing technology, the other devices will send data packets through the terminal device. Therefore, the user plane network element receives multiple packets from the terminal device.
  • the data packet includes both the data packet sent by the terminal device and the data packet sent by the other device.
  • the user plane network element can determine the reference value of the clock source corresponding to the data packet based on the timestamp in the obtained data packet.
  • the reference value of the clock source can be understood as the value of the clock source at a certain reference time.
  • the clock sources of different devices have different values at the same time, that is, the reference values of the clock sources of different devices are different.
  • the user plane network element determines that there are five reference values based on the timestamps in multiple received data packets, then one of the five reference values is the clock source of the terminal device with hotspot sharing turned on.
  • the other four benchmark values are the benchmark values of the clock sources of other devices connected to the terminal device through hotspot sharing technology. Therefore, the user plane network element determines the number of devices connected to the terminal device through hotspot sharing technology. is 4.
  • UE1 is a device with hotspot sharing enabled, and then device 1, device 2, and device 3 access UE1 through the hotspot enabled by UE1.
  • the following describes the method for user plane network elements to identify that the number of devices connected to UE1 through hotspot sharing technology is 3.
  • the clock source of UE1 When UE1 is powered on, the clock source of UE1 will generate an initial value (represented by initialTimestamp1), for example, the initial value is 1000. Then as time goes by, every time 1 second passes, the value of the clock source will increase by a fixed amount (expressed in numinbysec), and the value of numinbysec is 1000. For example, 1 second after UE1 is powered on, the clock source is updated to 2000, 2 seconds after UE1 is powered on, the clock source is updated to 3000, and so on. When UE1 generates a data packet, it will obtain the current value of UE1's clock source, and then the data packet will carry this value as a timestamp.
  • the value of the clock source of UE1 is timestamp1, and UE1 carries the timestamp1 in the data packet.
  • the value of the clock source of UE1 is timestamp2, and UE1 carries the timestamp2 in the data packet, and so on.
  • the clock source of device 1 when device 1 is powered on, the clock source of device 1 will generate an initial value (represented by initialTimestamp2), for example, the initial value is 2000. Then as time goes by, every time 1 second passes, the value of the clock source will increase by a fixed amount (expressed in numinbysec), and the value of numinbysec is 1000. For example, the clock source is updated to 3000 1 second after device 1 is powered on, and the clock source is updated to 4000 2 seconds after device 1 is powered on, and so on. When device 1 generates a data packet, it will obtain the current value of device 1's clock source, and then carry this value in the data packet as a timestamp.
  • the value of the clock source of device 1 is timestamp3, and device 1 carries this timestamp3 in the data packet.
  • the value of the clock source of device 1 is timestamp4, and device 1 carries the timestamp4 in the data packet, and so on.
  • device 2 and device 3 will also carry corresponding timestamps in the data packets.
  • the data packets received by the user plane network element from UE1, device 1, device 2 or device 3 will all carry a timestamp.
  • the user plane network element can sample the timestamps in multiple data packets at different times. By performing function fitting on the multiple timestamps sampled at multiple times, multiple straight lines with the same slope can be obtained.
  • the number of these straight lines Characterizing the total number of devices from which the multiple data packets originate, it can also be understood that the multiple straight lines obtained through fitting represent different initial values of different devices. Since the initial values of different devices are random when they are powered on, the number of initial values can be regarded as the number of devices.
  • the user plane network element samples multiple data packets at time tx and time ty respectively and obtains the timestamps in the data packets, and then fits the multiple timestamps obtained by sampling to obtain four straight lines. .
  • the corresponding data packets on the same straight line come from the same device, so the four straight lines indicate that the multiple data packets used come from four devices.
  • Method 2 The user plane network element determines the number of devices connected to the terminal device through hotspot sharing technology based on the number and/or type of heartbeat messages detected in one or more cycles.
  • the heartbeat messages originate from the terminal device or through Hotspot Devices that share technology access to end devices.
  • the operating system of the terminal device (such as IOS, Android, Windows) will periodically send heartbeat messages to the application server.
  • the terminal device sends the heartbeat message to the user plane network element, and then the user plane network element forwards the heartbeat message to the application server. Therefore, the user plane network element can detect the heartbeat message of the terminal device.
  • the operating system of the device will also periodically send heartbeat messages to the application server.
  • the heartbeat message reaches the user plane network element through the terminal device, and then The user plane network element then forwards the heartbeat message to the application server. Therefore, the user plane network element can detect the heartbeat message of the device.
  • the terminal device 1 since devices with the same type of operating system have the same heartbeat message sending period, it is possible to determine the number of heartbeat messages accessed to the terminal device 1 through the hotspot sharing technology by detecting the number of heartbeat messages in a period. Number of devices. For example, a device installed with the Android operating system sends heartbeat messages according to the T1 cycle, and a device installed with the Apple operating system sends heartbeat messages according to the T2 cycle. Then the user plane network element can detect the number of heartbeat messages sent by the Android device in a T1 period.
  • the user plane network element determines that the number of devices connected to terminal device 1 through hotspot sharing technology is (K1+ K2)-1.
  • method 2 can be used at the same time as method 1.
  • method 1 is used to judge multiple data packets with the same characteristics, so that the number of devices connected to the terminal device 1 through the hotspot sharing technology can be determined more accurately.
  • Method 3 The user plane network element obtains network traffic characteristic parameters corresponding to multiple data packets.
  • the user plane network element determines the number of devices connected to the terminal device through hotspot sharing technology based on the network traffic characteristic parameters.
  • Hotspot access is essentially a network address translation (NAT) behavior.
  • the essence of traffic identification is to divide the IP addresses in the network into the IP address of the NAT device and the IP address of the ordinary host. This is different from the behavior of hotspot sharing.
  • the terminal device with the hotspot sharing function enabled can be regarded as a NAT device, and other devices without the hotspot sharing function enabled can be regarded as an ordinary host.
  • the general idea of this method is to obtain the IP addresses in the network, and then use each IP address as an instance in data mining to combine the NAT devices in the network with ordinary hosts through data mining.
  • the user plane network element further determines the number of devices connected to the NAT device through hotspot sharing technology.
  • the specific method is: the user plane network element collects data packets, and then the user plane network element analyzes the collected data based on machine learning/deep models. Analyze the network traffic characteristic parameters corresponding to the packet to determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the network traffic characteristic parameters corresponding to the data packet include one or more of the data packet arrival time, IP layer information in the data packet, and Transmission Control Protocol (TCP) layer information in the data packet.
  • TCP Transmission Control Protocol
  • Method 4 The user plane network element obtains multiple HTTP request messages.
  • the HTTP request messages include device parameters, user
  • the surface network element determines the number of devices connected to the terminal device through hotspot sharing technology based on the device parameters in multiple HTTP request messages.
  • the device When the device accesses the HTTP service, it sends an HTTP request message.
  • the UserAgent field in the header of the HTTP request message carries one or more parameters such as the operating system type of the device, the browser type of the device, or the device type. Therefore, the user interface
  • the network element can determine whether the device is a device connected to the terminal device through hotspot sharing technology based on the parameters carried in the header of the HTTP request message, and then determine the number of devices connected to the terminal device through hotspot sharing technology.
  • the above methods can be used in combination with each other to determine the number of devices connected to the terminal device through hotspot sharing technology. No longer.
  • Figure 2(b) is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application. The method includes the following steps:
  • Step 201b The policy control network element sends instruction information to the user plane network element.
  • the user plane network element receives the indication information.
  • step 201a For this sending action, please refer to the description of step 201a.
  • the instruction information indicates that when the number of devices connected to the terminal device through the hotspot sharing technology changes, the changed number of devices is sent to the policy control network element.
  • Step 202b When the number of devices connected to the terminal device through the hotspot sharing technology changes from the first number to the second number, the user plane network element sends the second number to the policy control network element.
  • the user plane network element determines that the number of devices connected to the terminal device through the hotspot sharing technology has changed, it sends the changed number of devices to the policy control network element.
  • the policy control network element instructs the user plane network element to detect the number of devices connected to the terminal device through hotspot sharing technology, and after detecting that the number of devices connected to the terminal device through hotspot sharing technology changes, Send the changed number of devices to the policy control network element, so that the policy control network element decides the charging method or control method for the terminal device based on the changed number of devices, thereby helping to achieve reasonable accounting for the terminal device. cost and precise control.
  • step 202b after the above step 202b, the following step 203b, or step 204b, or step 203b and step 204b may also be performed.
  • Step 203b The policy control network element sends the charging rules to the user plane network element.
  • the user plane network element receives the charging rule.
  • the policy control network element After receiving the second quantity, the policy control network element determines the charging rule based on the second quantity. Then the policy control network element sends charging rules to the user plane network element, and the user plane network element charges the terminal device according to the charging rules.
  • embodiments of the present application define intervals for the number of devices connected to the terminal device through hotspot sharing technology, and set a charging rule for each interval. For example, when the number of devices falls within the range of 0 to 2, billing rule 1 is set; when the number of devices falls within the range of 3 to 5, billing rule 2 is set, and so on.
  • the embodiments of this application do not limit the specific implementation method of the charging rules. This method can effectively set charging rules and achieve reasonable charging of terminal devices.
  • Step 204b The policy control network element sends control policy rules to the user plane network element.
  • the user plane network element receives the control policy rule.
  • the policy control network element After receiving the second quantity, the policy control network element determines the control policy rules according to the second quantity. Then, the policy control network element sends control policy rules to the user plane network element, and the user plane network element controls the terminal device according to the control policy rules. system.
  • embodiments of the present application define intervals for the number of devices connected to the terminal device through hotspot sharing technology, and set a control policy rule for each interval. For example, when the number of devices falls within the range of 0 to 2, set control policy rule 1; when the number of devices falls within the range of 3 to 5, set control policy rule 2, and so on.
  • the embodiments of this application do not limit the specific implementation method of the control policy rules. This method can effectively set control policy rules and achieve reasonable control of terminal devices.
  • the user plane network element detects the number of devices connected to the terminal device through the hotspot sharing technology. You can refer to the embodiment of Figure 2(a) above. The relevant description will not be repeated in the embodiment of Figure 2(b).
  • FIG. 2(a) and FIG. 2(b) will be described below with reference to specific embodiments.
  • the embodiments in FIGS. 3 and 5 below are specific examples of the embodiment in FIG. 2(a)
  • the embodiment in FIG. 4 below is a specific example of the embodiment in FIG. 2(b) .
  • FIG. 3 is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application. The method includes the following steps:
  • Step 301 The terminal device sends a session establishment request message to the session management network element.
  • the terminal device is a device with Internet access capability and hotspot sharing function.
  • the terminal device is a smartphone or the like.
  • the session management network element is PGW-C.
  • the session management network element is SMF.
  • the session establishment request message can be an Nsmf_PDUSession_CreateSMContext Request message.
  • Step 302 The session management network element sends a policy establishment request message to the policy control network element.
  • the policy control network element is PCRF
  • the session management network element ie, PGW-C
  • PGW-C sends a policy establishment request message to PCRF through the Gx interface between PGW-C and PCRF.
  • the policy control network element is PCF
  • the session management network element sends a policy establishment request message to PCF through the N7 interface between SMF and PCF.
  • the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.
  • This policy establishment request message is used to request user policies.
  • Step 303 The policy control network element sends a policy establishment response message to the session management network element.
  • the policy establishment response message may be the Npcf_SMPolicyControl_Create_Request message.
  • the policy establishment response message includes a hotspot access exceeding threshold reporting event and a hotspot access threshold.
  • the hotspot access exceeding threshold reporting event is used to indicate when the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold. If an event reaches the threshold, the event is reported.
  • the policy control network element can obtain the subscription data of the terminal device locally, and obtain the hotspot access threshold corresponding to the terminal device from the subscription data.
  • the policy establishment response message includes a credit control answer (credit control answer, CCA) message or a re-authorization request (Re-Auth-Request, RAR) message.
  • CCA credit control answer
  • RAR re-authorization request
  • the hotspot access exceeding threshold reporting event is a specific example of the indication information in the embodiment of FIG. 2(a).
  • the CCA message currently includes the Event-Trigger field.
  • this application can extend the Event-Trigger field and add the Event-Trigger The value range.
  • the value of the newly added Event-Trigger is TETHERING_EXCEED_NUM_REPORT.
  • the TETHERING_EXCEED_NUM_REPORT is an example of an event reported when hotspot access exceeds the threshold.
  • the Tethering-Num-Threshold corresponding to TETHERING_EXCEED_NUM_REPORT is also added, and the Tethering-Num-Threshold is an example of a hotspot access threshold.
  • the CCA message When the value of Event-Trigger in the CCA message is TETHERING_EXCEED_NUM_REPORT, the CCA message also includes Tethering-Num-Threshold. Among them, the TETHERING_EXCEED_NUM_REPORT and the Tethering-Num-Threshold are called an attribute value pair (AVP).
  • AVP attribute value pair
  • the policy establishment response message includes SmPolicyDecision. Part of the content contained in the SmPolicyDecision is shown in Table 1.
  • policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger.
  • PolicyControlRequestTrigger a new value range of policyCtrlReqTriggers is added.
  • the value of the newly added policyCtrlReqTriggers is TETHERING_EXCEED_NUM_REPORT.
  • the TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access exceeding a threshold reporting event.
  • Tethering_num_Threshold is a new attribute
  • the Tethering_num_Threshold is an example of a hotspot access threshold.
  • Step 304 The session management network element sends a session establishment request message to the user plane network element.
  • the user plane network element is PGW-U
  • the session management network element ie, PGW-C
  • PGW-C sends a session establishment request message to PGW-U through the Sx interface between PGW-C and PGW-U.
  • the user plane network element is UPF
  • the session management network element sends a session establishment request message to UPF through the N4 interface between SMF and UPF.
  • the session establishment request message may be an N4 Session Establish Request message.
  • the session establishment request message includes a hotspot access exceeding threshold reporting event and a hotspot access threshold.
  • the session establishment request message includes a usage reporting rule (Usage Reporting Rule, URR), and the URR includes Extended Reporting Triggers and Tethering_num_Threshold.
  • URR Usage Reporting Rule
  • the Extended Reporting Triggers include hotspot access exceeding the threshold reporting event, and the Tethering_num_Threshold is an example of the hotspot access threshold.
  • Step 305 The user plane network element reports an event based on the hotspot access exceeding the threshold and starts hotspot access detection.
  • Step 306 The user plane network element sends a session establishment response message to the session management network element.
  • the session establishment response message may be an N4 Session Establish Response message.
  • Step 307 The user plane network element sends a session report request message to the session management network element.
  • the session reporting request message may be an N4 Session Reporting Request message.
  • the user plane network element when the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold, the user plane network element sends a session report request message to the session management network element.
  • the session report request message includes a hotspot access exceeds threshold event, which indicates that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold.
  • the hotspot access exceeding the threshold event is a specific example of the first event in the embodiment of FIG. 2(a).
  • the session report request message includes ExtendedUsage Report Triggers
  • the ExtendedUsage Report Triggers may include a hotspot access exceeding a threshold event.
  • Step 308 The session management network element sends a policy update request message to the policy control network element.
  • the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.
  • the policy update request message includes a hotspot access exceeding a threshold event.
  • Step 309 The policy control network element determines the charging rule 1 and/or the control policy rule 1 for the terminal device.
  • the policy control network element receives a hotspot access exceeding a threshold event, which triggers the policy control network element to determine the charging rule 1 and/or the control policy rule 1 for the terminal device according to the preconfigured policy or subscription policy.
  • Step 310 The policy control network element sends a policy update response message to the session management network element.
  • the policy update response message may be the Npcf_SMPolicyControl_Update_Response message.
  • the policy update response message includes the charging rule 1 for the terminal device and/or the control policy rule 1 for the terminal device.
  • Step 311 The session management network element sends a session modification request message to the user plane network element.
  • the session modification request message may be an N4 Session Modification Request message.
  • the session modification request message includes charging rule 1 and/or control policy rule 1 for the terminal device.
  • the session modification request message includes a packet detection rule (Packet Detection Rule, PDR), and the PDR includes a charging rule 1 and/or a control policy rule 1 for the terminal device.
  • PDR Packet Detection Rule
  • Step 312 The user plane network element charges the terminal device according to the charging rule 1 for the terminal device, and/or controls the terminal device according to the control policy rule 1 for the terminal device.
  • the following steps may be performed after step 312. 313 to step 318.
  • Step 313 The user plane network element sends a session report request message to the session management network element.
  • the session reporting request message may be an N4 Session Reporting Request message.
  • the user plane network element when the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology changes from exceeding the hotspot access threshold to being lower than the hotspot access threshold, the user plane network element sends a message to the session management network element.
  • the session report request message includes a hotspot access lower than threshold event.
  • the hotspot access lower than threshold event indicates that the number of devices connected to the terminal device through the hotspot sharing technology is lower than the hotspot access threshold.
  • the event that the hotspot access is lower than the threshold is a specific example of the second event in the embodiment of FIG. 2(a).
  • the session report request message includes ExtendedUsage Report Triggers
  • the ExtendedUsage Report Triggers can include hotspot access lower than threshold events.
  • Step 314 The session management network element sends a policy update request message to the policy control network element.
  • the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.
  • the policy update request message includes the event that the hotspot access is below the threshold.
  • Step 315 The policy control network element determines the charging rule 2 and/or the control policy rule 2 for the terminal device.
  • the policy control network element receives an event that the hotspot access is lower than the threshold, triggering the policy control network element to determine the charging rule 2 and/or the control policy rule 2 for the terminal device according to the preconfigured policy or subscription policy.
  • Step 316 The policy control network element sends a policy update response message to the session management network element.
  • the policy update response message may be the Npcf_SMPolicyControl_Update_Response message.
  • the policy update response message includes the charging rule 2 for the terminal device and/or the control policy rule 2 for the terminal device.
  • Step 317 The session management network element sends a session modification request message to the user plane network element.
  • the session modification request message may be an N4 Session Modification Request message.
  • the session modification request message includes the charging rule 2 for the terminal device and/or the control policy rule 2 for the terminal device.
  • the session modification request message includes a PDR, and the PDR includes a charging rule 2 for the terminal device and/or a control policy rule 2 for the terminal device.
  • Step 318 The user plane network element charges the terminal device according to the charging rule 2 for the terminal device, and/or controls the terminal device according to the control policy rule 2 for the terminal device.
  • the user plane network element can detect the number of devices connected to the terminal device through hotspot sharing technology, and report when it detects that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold.
  • the event that hotspot access exceeds the threshold triggers the policy control network element to determine the corresponding charging rules and/or control policy rules.
  • the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology is lower than the hotspot access threshold, it can report the hotspot access lower than threshold event and trigger the policy control network element to determine the corresponding billing rules and/or control policy rules. Therefore, this solution can achieve precise billing and effective control of terminal equipment.
  • steps 303 and 304 can be understood as a specific implementation of step 201a in the embodiment of Figure 2(a), and the above-mentioned steps 307 and 308 can be understood as an implementation of the above-mentioned Figure 2(a).
  • the above steps 310 and 311 can be understood as a specific implementation of step 203a and step 204a in the embodiment of Figure 2(a).
  • the above steps 313 and 314 can be understood as It is a specific implementation of step 205a in the embodiment of Figure 2(a).
  • the above steps 316 and 317 can be understood as a specific implementation of step 206a and step 207a in the embodiment of Figure 2(a). , its specific implementation can refer to the relevant description in the embodiment of Figure 2(a), and will not be described again.
  • FIG. 4 is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application. The method includes the following steps:
  • Step 401 The terminal device sends a session establishment request message to the session management network element.
  • the terminal device is a device with Internet access capability and hotspot sharing function.
  • the terminal device is a smartphone or the like.
  • the session management network element is PGW-C.
  • the session management network element is SMF.
  • the session establishment request message can be an Nsmf_PDUSession_CreateSMContext Request message.
  • Step 402 The session management network element sends a policy establishment request message to the policy control network element.
  • the policy control network element is PCRF
  • the session management network element ie, PGW-C
  • PGW-C sends a policy establishment request message to PCRF through the Gx interface between PGW-C and PCRF.
  • the policy control network element is PCF
  • the session management network element sends a policy establishment request message to PCF through the N7 interface between SMF and PCF.
  • the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.
  • This policy establishment request message is used to request user policies.
  • Step 403 The policy control network element sends a policy establishment response message to the session management network element.
  • the policy establishment response message may be the Npcf_SMPolicyControl_Create_Request message.
  • the policy establishment response message includes a hotspot access device number reporting event.
  • the hotspot access device number reporting event is used to indicate that when an event occurs that the number of devices connected to the terminal device through hotspot sharing technology changes, then Report the number of changed devices.
  • the policy establishment response message includes a CCA message or a RAR message
  • the CCA message or RAR message includes a hotspot access device quantity reporting event.
  • the hotspot access device quantity reporting event is a specific example of the indication information in the embodiment of FIG. 2(b).
  • the CCA message currently includes the Event-Trigger field.
  • this application can expand the Event-Trigger and increase the value range of the Event-Trigger.
  • the value of the newly added Event-Trigger is TETHERING_NUM_REPORT.
  • the TETHERING_NUM_REPORT is the number of hotspot access devices reporting events. An example of.
  • the policy establishment response message includes SmPolicyDecision. Part of the content contained in the SmPolicyDecision is shown in Table 2.
  • policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger.
  • PolicyControlRequestTrigger a new value range of policyCtrlReqTriggers is added.
  • the new value range of policyCtrlReqTriggers is TETHERING_NUM_REPORT.
  • the TETHERING_NUM_REPORT is an example of a hotspot access device number reporting event.
  • Step 404 The session management network element sends a session establishment request message to the user plane network element.
  • the user plane network element is PGW-U
  • the session management network element ie, PGW-C
  • PGW-C sends a session establishment request message to PGW-U through the Sx interface between PGW-C and PGW-U.
  • the user plane network element is UPF
  • the session management network element sends a session establishment request message to UPF through the N4 interface between SMF and UPF.
  • the session establishment request message may be an N4 Session Establish Request message.
  • the session establishment request message includes a number reporting event of hotspot access devices.
  • the session establishment request message includes a URR
  • the URR includes Extended Reporting Triggers.
  • the Extended Reporting Triggers include hotspot access device number reporting events.
  • Step 405 The user plane network element reports events according to the number of hotspot access devices and starts hotspot access detection.
  • Step 406 The user plane network element sends a session establishment response message to the session management network element.
  • the session establishment response message may be an N4 Session Establish Response message.
  • Step 407 The user plane network element sends a session report request message to the session management network element.
  • the session reporting request message may be an N4 Session Reporting Request message.
  • the user plane network element when the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology changes, the user plane network element sends a session report request message to the session management network element.
  • the session report request message includes The number of devices with hotspot sharing technology connected to the terminal device. This number refers to the number of devices after the change.
  • the session report request message may include ExtendedUsage Report Triggers, and the ExtendedUsage Report Triggers may include the number of devices connected to the terminal device through hotspot sharing technology.
  • Step 408 The session management network element sends a policy update request message to the policy control network element.
  • the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.
  • the policy update request message includes the number of devices connected to the terminal device through hotspot sharing technology.
  • Step 409 The policy control network element determines charging rules and/or control policy rules for the terminal device.
  • the policy control network element receives the number of devices connected to the terminal device through hotspot sharing technology, and triggers the policy control network element to determine the charging rules for the terminal device and/or control for the terminal device according to the preconfigured policy or contract policy. Policy rules.
  • Step 410 The policy control network element sends a policy update response message to the session management network element.
  • the policy update response message may be the Npcf_SMPolicyControl_Update_Response message.
  • the policy update response message includes charging rules and/or control policy rules for the terminal device.
  • Step 411 The session management network element sends a session modification request message to the user plane network element.
  • the session modification request message may be an N4 Session Modification Request message.
  • the session modification request message includes charging rules and/or control policy rules for the terminal device.
  • the session modification request message includes a PDR, and the PDR includes charging rules and/or control policy rules for the terminal device.
  • Step 412 The user plane network element charges the terminal device according to the charging rules for the terminal device, and/or controls the terminal device according to the control policy rules for the terminal device.
  • the user plane network element detects that the number of devices connected to the terminal device through the hotspot sharing technology changes, the above steps 407 to 412 are repeatedly executed.
  • the user plane network element can detect the number of devices connected to the terminal device through hotspot sharing technology, and report the detected number of devices connected to the terminal device through hotspot sharing technology, triggering the policy control network element to determine Corresponding billing rules and/or control policy rules. Therefore, this solution can achieve precise billing and effective control of terminal equipment.
  • steps 403 and 404 can be understood as a specific implementation of step 201b in the embodiment of Figure 2(b), and the above-mentioned steps 407 and 408 can be understood as an implementation of the above-mentioned Figure 2(b).
  • the above-mentioned steps 410 and 411 can be understood as a specific implementation of step 203b and step 204b in the embodiment of Figure 2(b).
  • please refer to Figure 2( Relevant descriptions in the embodiment of b) will not be repeated. narrate.
  • FIG. 5 is a schematic flowchart of a hotspot device management method provided by an embodiment of the present application. The method includes the following steps:
  • Step 501 The terminal device sends a session establishment request message to the session management network element.
  • the terminal device is a device with Internet access capability and hotspot sharing function.
  • the terminal device is a smartphone or the like.
  • the session management network element is PGW-C.
  • the session management network element is SMF.
  • the session establishment request message can be an Nsmf_PDUSession_CreateSMContext Request message.
  • Step 502 The session management network element sends a policy establishment request message to the policy control network element.
  • the policy control network element is PCRF
  • the session management network element ie, PGW-C
  • PGW-C sends a policy establishment request message to PCRF through the Gx interface between PGW-C and PCRF.
  • the policy control network element is PCF
  • the session management network element sends a policy establishment request message to PCF through the N7 interface between SMF and PCF.
  • the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.
  • This policy establishment request message is used to request user policies.
  • Step 503 The policy control network element sends a policy establishment response message to the session management network element.
  • the policy establishment response message may be the Npcf_SMPolicyControl_Create_Request message.
  • the policy establishment response message includes a hotspot access exceeding threshold reporting event.
  • the hotspot access exceeding threshold reporting event is used to indicate that when the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold, an event occurs. Then report the incident.
  • the policy establishment response message includes a CCA message or a RAR message
  • the CCA message or RAR message includes a hotspot access exceeding a threshold reporting event.
  • the hotspot access exceeding threshold reporting event is a specific example of the indication information in the embodiment of FIG. 2(a).
  • the CCA message currently includes the Event-Trigger field.
  • this application can extend the Event-Trigger and increase the value range of the Event-Trigger.
  • the value of the new Event-Trigger is TETHERING_EXCEED_NUM_REPORT.
  • the TETHERING_EXCEED_NUM_REPORT is an example of an event reported when hotspot access exceeds the threshold.
  • the policy establishment response message includes SmPolicyDecision. Part of the content contained in the SmPolicyDecision is shown in Table 3.
  • policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger.
  • PolicyControlRequestTrigger a new value range of policyCtrlReqTriggers is added.
  • the new value range of policyCtrlReqTriggers is TETHERING_EXCEED_NUM_REPORT.
  • the TETHERING_EXCEED_NUM_REPORT is an example of an event reported when hotspot access exceeds the threshold.
  • Step 504 The session management network element sends a session establishment request message to the user plane network element.
  • the user plane network element is PGW-U
  • the session management network element ie, PGW-C
  • PGW-C sends a session establishment request message to PGW-U through the Sx interface between PGW-C and PGW-U.
  • the user plane network element is UPF
  • the session management network element sends a session establishment request message to UPF through the N4 interface between SMF and UPF.
  • the session establishment request message may be an N4 Session Establish Request message.
  • the session establishment request message includes a hotspot access exceeding threshold reporting event.
  • the session establishment request message includes a URR
  • the URR includes Extended Reporting Triggers.
  • the Extended Reporting Triggers include hotspot access exceeding the threshold reporting event.
  • Step 505 The user plane network element reports an event based on the hotspot access exceeding the threshold and starts hotspot access detection.
  • Step 506 The user plane network element sends a session establishment response message to the session management network element.
  • the session establishment response message may be an N4 Session Establish Response message.
  • Step 507 The user plane network element sends a session report request message to the session management network element.
  • the session reporting request message may be an N4 Session Reporting Request message.
  • the hotspot access threshold is preconfigured on the user plane network element.
  • the user plane network element determines the hotspot access threshold based on the service package of the terminal device.
  • the user plane network element when the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold, the user plane network element sends a session report request message to the session management network element.
  • the session report request message includes a hotspot access exceeds threshold event, which indicates that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold.
  • the hotspot access exceeding the threshold event is a specific example of the first event in the embodiment of FIG. 2(a).
  • the session report request message includes ExtendedUsage Report Triggers
  • the ExtendedUsage Report Triggers may include a hotspot access exceeding a threshold event.
  • Step 508 The session management network element sends a policy update request message to the policy control network element.
  • the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.
  • the policy update request message includes a hotspot access exceeding a threshold event.
  • Step 509 The policy control network element determines the charging rule 1 and/or the control policy rule 1 for the terminal device.
  • the policy control network element receives a hotspot access exceeding a threshold event, which triggers the policy control network element to determine the charging rule 1 and/or the control policy rule 1 for the terminal device according to the preconfigured policy or subscription policy.
  • Step 510 The policy control network element sends a policy update response message to the session management network element.
  • the policy update response message may be the Npcf_SMPolicyControl_Update_Response message.
  • the policy update response message includes charging rule 1 and/or control policy rule 1 for the terminal device.
  • Step 511 The session management network element sends a session modification request message to the user plane network element.
  • the session modification request message may be an N4 Session Modification Request message.
  • the session modification request message includes charging rule 1 and/or control policy rule 1 for the terminal device.
  • the session modification request message includes a PDR, and the PDR includes the charging rule 1 and/or the control policy rule 1 for the terminal device.
  • Step 512 The user plane network element charges the terminal device according to the charging rule 1 for the terminal device, and/or Control the terminal device according to the control policy rule 1 for the terminal device.
  • the following steps 513 to 518 can also be performed. .
  • Step 513 The user plane network element sends a session report request message to the session management network element.
  • the session reporting request message may be an N4 Session Reporting Request message.
  • the user plane network element when the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology changes from exceeding the hotspot access threshold to being lower than the hotspot access threshold, the user plane network element sends a message to the session management network element.
  • the session report request message includes a hotspot access lower than threshold event.
  • the hotspot access lower than threshold event indicates that the number of devices connected to the terminal device through the hotspot sharing technology is lower than the hotspot access threshold.
  • the event that the hotspot access is lower than the threshold is a specific example of the second event in the embodiment of FIG. 2(a).
  • the session report request message includes ExtendedUsage Report Triggers
  • the ExtendedUsage Report Triggers may include a hotspot access lower than threshold event.
  • Step 514 The session management network element sends a policy update request message to the policy control network element.
  • the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.
  • the policy update request message includes the event that the hotspot access is below the threshold.
  • Step 515 The policy control network element determines the charging rule 2 and/or the control policy rule 2 for the terminal device.
  • the policy control network element receives an event that the hotspot access is lower than the threshold, triggering the policy control network element to determine the charging rule 2 and/or the control policy rule 2 for the terminal device according to the preconfigured policy or subscription policy.
  • Step 516 The policy control network element sends a policy update response message to the session management network element.
  • the policy update response message may be the Npcf_SMPolicyControl_Update_Response message.
  • the policy update response message includes charging rule 2 and/or control policy rule 2 for the terminal device.
  • Step 517 The session management network element sends a session modification request message to the user plane network element.
  • the session modification request message may be an N4 Session Modification Request message.
  • the session modification request message includes charging rules 2 and/or control policy rules 2 for the terminal device.
  • the session modification request message includes a PDR, and the PDR includes charging rules 2 and/or control policy rules 2 for the terminal device.
  • Step 518 The user plane network element charges the terminal device according to the charging rule 2 for the terminal device, and/or controls the terminal device according to the control policy rule 2 for the terminal device.
  • the user plane network element can detect the number of devices connected to the terminal device through hotspot sharing technology, and report when it detects that the number of devices connected to the terminal device through hotspot sharing technology exceeds the hotspot access threshold.
  • the event that hotspot access exceeds the threshold triggers the policy control network element to determine the corresponding charging rules and/or control policy rules.
  • the user plane network element detects that the number of devices connected to the terminal device through hotspot sharing technology is lower than the hotspot access threshold, it can report the hotspot access lower than threshold event and trigger the policy control network element to determine the corresponding billing rules and/or control policy rules. Therefore, this solution can achieve precise billing and effective control of terminal equipment.
  • steps 503 and 504 can be understood as a specific implementation of step 201a in the embodiment of Figure 2(a), and the above-mentioned steps 507 and 508 can be understood as an implementation of the above-mentioned Figure 2(a).
  • the above steps 510 and 511 can be understood as a specific implementation of step 203a and step 204a in the embodiment of Figure 2(a).
  • the above steps 513 and 514 can be understood as It is a specific implementation of step 205a in the embodiment of Figure 2(a).
  • the above steps 516 and 517 can be understood as a specific implementation of step 206a and step 207a in the embodiment of Figure 2(a).
  • its specific implementation can refer to the relevant information in the embodiment of Figure 2(a) Description, no more details.
  • the user plane network element or the policy control network element includes corresponding hardware structures and/or software modules that perform each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software driving the hardware depends on the specific application scenarios and design constraints of the technical solution.
  • Figures 6 and 7 are schematic structural diagrams of possible communication devices provided by embodiments of the present application. These communication devices can be used to implement the functions of user plane network elements or policy control network elements in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be a user plane network element or a policy control network element, or may be a module (such as a chip) applied to a policy control network element or a module (such as a chip) applied to a user plane network element. ).
  • the communication device 600 shown in FIG. 6 includes a processing unit 610 and a transceiver unit 620.
  • the communication device 600 is used to implement the functions of the user plane network element or the policy control network element in the above method embodiment.
  • the transceiver unit 620 is used to receive instruction information from the policy control network element.
  • the instruction information Indicate that when the first event occurs, the first event is sent to the policy control network element.
  • the first event is that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold; when the first event occurs, the first event is sent to the policy control network element. When an event occurs, the first event is sent to the policy control network element.
  • the transceiver unit 620 is configured to receive the hotspot access threshold from the policy control network element; or, the indication information includes the hotspot access threshold.
  • the processing unit 610 is configured to determine the hotspot access threshold based on the service package of the terminal device; or, the processing unit 610 is configured to determine the hotspot access threshold based on the configuration information in the user plane network element. Hotspot access threshold.
  • the transceiver unit 620 is configured to receive the first charging rule from the policy control network element, where the first charging rule is determined based on the first event; the processing unit 610 is configured to receive the first charging rule based on the first event.
  • the first charging rule charges the terminal device.
  • the transceiver unit 620 is configured to receive the first control policy rule from the policy control network element, where the first control policy rule is determined based on the first event; the processing unit 610 is configured to receive the first control policy rule based on the first event.
  • the first control policy rule controls the terminal device.
  • the transceiver unit 620 is configured to send the second event to the policy control network element when a second event occurs.
  • the second event represents the access to the terminal device through the hotspot sharing technology.
  • the number is less than or equal to the hotspot access threshold.
  • the transceiver unit 620 is configured to receive a second charging rule from the policy control network element, where the second charging rule is determined based on the second event; the processing unit 610 is configured to receive the second charging rule based on the second event.
  • the second charging rule charges the terminal device.
  • the transceiver unit 620 is configured to receive a second control policy rule from the policy control network element, where the second control policy rule is determined based on the second event; the processing unit 610 is configured to receive a second control policy rule based on the second event.
  • the second control policy rule controls the terminal device.
  • the transceiver unit 620 is configured to receive multiple data packets from the terminal device, each of the multiple data packets includes a timestamp; the processing unit 610 is configured to receive a time stamp based on the multiple data packets. packets for each The timestamp in the data packet determines the baseline value of the clock source corresponding to the multiple data packets; based on the baseline value of the clock source corresponding to the multiple data packets, determines the number of devices connected to the terminal device through hotspot sharing technology .
  • the processing unit 610 is configured to determine the number of devices connected to the terminal device through hotspot sharing technology based on the number and/or type of heartbeat messages detected in one or more cycles, The heartbeat message originates from the terminal device or a device connected to the terminal device through hotspot sharing technology.
  • the processing unit 610 is used to obtain network traffic characteristic parameters corresponding to multiple data packets; and determine the number of devices connected to the terminal device through hotspot sharing technology based on the network traffic characteristic parameters.
  • the processing unit 610 is configured to obtain multiple HTTP request messages, where the HTTP request messages include device parameters; and based on the device parameters in the multiple HTTP request messages, determine whether the device is accessed through the hotspot sharing technology. The number of devices in the terminal device.
  • the transceiver unit 620 is used to send indication information to the user plane network element, and the indication information indicates , when the first event occurs, the first event is sent to the policy control network element.
  • the first event is that the number of devices connected to the terminal device through the hotspot sharing technology is greater than or equal to the hotspot access threshold; when the first event When an event occurs, the first event from the user plane network element is received.
  • the transceiver unit 620 is configured to send the hotspot access threshold to the user plane network element; or, the indication information includes the hotspot access threshold.
  • the processing unit 610 is configured to determine a first charging rule according to the first event; the transceiving unit 620 is configured to send the first charging rule to the user plane network element.
  • the processing unit 610 is configured to determine a first control policy rule according to the first event; the transceiving unit 620 is configured to send the first control policy rule to the user plane network element.
  • the transceiver unit 620 is configured to receive a second event from the user plane network element.
  • the second event indicates that the number of devices connected to the terminal device through hotspot sharing technology is less than or equal to the hotspot. access threshold.
  • the processing unit 610 is configured to determine a second charging rule according to the second event; the transceiving unit 620 is configured to send the second charging rule to the user plane network element.
  • the processing unit 610 is configured to determine a second control policy rule according to the second event; the transceiving unit 620 is configured to send the second control policy rule to the user plane network element.
  • the transceiver unit 620 is used to receive indication information from the policy control network element.
  • the indication information indicates that when passing If the number of devices connected to the terminal device through hotspot sharing technology changes, the changed number of devices will be sent to the policy control network element; when the number of devices connected to the terminal device through hotspot sharing technology changes from the first number is the second quantity, and sends the second quantity to the policy control network element.
  • the transceiver unit 620 is configured to receive the charging rule from the policy control network element, and the charging rule is determined based on the second quantity; the processing unit 610 is configured to receive the charging rule based on the charging rule. , perform billing on the terminal device.
  • the transceiver unit 620 is configured to receive a control policy rule from the policy control network element, where the control policy rule is determined based on the second number; the processing unit 610 is configured to receive a control policy rule based on the control policy rule. , to control the terminal device.
  • the transceiver unit 620 is used to receive multiple data packets from the terminal device. Each data packet in the multiple data packets contains a timestamp; the processing unit 610 is configured to determine the reference value of the clock source corresponding to the multiple data packets based on the timestamp in each data packet of the multiple data packets. ; According to the reference value of the clock source corresponding to the multiple data packets, determine the number of devices connected to the terminal device through the hotspot sharing technology.
  • the processing unit 610 is configured to determine the number of devices connected to the terminal device through hotspot sharing technology based on the number and/or type of heartbeat messages detected in one or more cycles, The heartbeat message originates from the terminal device or a device connected to the terminal device through hotspot sharing technology.
  • the processing unit 610 is used to obtain network traffic characteristic parameters corresponding to multiple data packets; and determine the number of devices connected to the terminal device through hotspot sharing technology based on the network traffic characteristic parameters.
  • the processing unit 610 is configured to obtain multiple HTTP request messages, where the HTTP request messages include device parameters; and based on the device parameters in the multiple HTTP request messages, determine whether the device is accessed through the hotspot sharing technology. The number of devices in the terminal device.
  • the transceiver unit 620 is used to send indication information to the user plane network element.
  • the indication information indicates that when passing If the number of devices connected to the terminal device through hotspot sharing technology changes, the changed number of devices will be sent to the policy control network element; when the number of devices connected to the terminal device through hotspot sharing technology changes from the first number is the second quantity, and receives the second quantity from the user plane network element.
  • the processing unit 610 is configured to determine a charging rule according to the second quantity; the transceiving unit 620 is configured to send the charging rule to the user plane network element.
  • the processing unit 610 is configured to determine the control policy rule according to the second quantity; the transceiving unit 620 is configured to send the control policy rule to the user plane network element.
  • the communication device 700 shown in FIG. 7 includes a processor 710 and an interface circuit 720.
  • the processor 710 and the interface circuit 720 are coupled to each other.
  • the interface circuit 720 may be a transceiver or an input-output interface.
  • the communication device 700 may also include a memory 730 for storing instructions executed by the processor 710 or input data required for the processor 710 to run the instructions or data generated after the processor 710 executes the instructions.
  • the processor 710 is used to realize the function of the above processing unit 610
  • the interface circuit 720 is used to realize the function of the above transceiver unit 620.
  • processor in the embodiment of the present application can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • At least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be Single or multiple. "Multiple" means two or more, and other quantifiers are similar.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, digital versatile optical disk), or semiconductor media (eg, solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application may be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic, Discrete hardware components, or any combination of the foregoing, designed to implement or operate the functions described.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any conventional processor, controller, microcontroller or state machine.
  • a processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of this application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • Software units can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (EPROM), Register, hard disk, removable disk and any other form of storage media in this field.
  • the storage medium can be connected to the processor, so that the processor can read information from the storage medium and can store and write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium can be housed in an ASIC.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • Computer-readable media includes computer storage media and communications media that facilitate transfer of a computer program from one place to another.
  • the storage medium can be any available media that can be accessed using or special computers.
  • such computer-readable media may include, but is not limited to, RAM, ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that may be used to carry or store instructions or data structures and other devices that may be general or specialized.
  • the disks and discs include compressed disks, laser disks, optical disks, digital versatile disks, floppy disks and Blu-ray discs. Disks usually use magnetic reproduction to copy data, while discs usually use lasers to optically copy data. Combinations of the above can also be contained in a computer-readable medium.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种热点设备的管理方法、通信装置及通信系统。该方法中，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值的时候通知策略控制网元，从而策略控制网元获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，以便于策略控制网元决策对该终端设备的计费方式或控制方式，实现对终端设备的合理计费和精准控制。

Description

一种热点设备的管理方法、通信装置及通信系统
相关申请的交叉引用
本申请要求在2022年07月25日提交中国专利局、申请号为202210876527.5、申请名称为“一种热点设备的管理方法、通信装置及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种热点设备的管理方法、通信装置及通信系统。
背景技术
目前，终端设备比如智能手机，具备热点分享功能，当该终端设备开启了热点分享，则其它设备比如笔记本电脑，可以通过无线保真(wireless fidelity，WiFi)、蓝牙或通用串行总线(Universal Serial Bus，USB)物理连接等连接方式接入到该终端设备，实现上网目的。
然而，如何有效地管理具备热点分享功能的终端设备，有待解决。
发明内容
本申请实施例提供一种热点设备的管理方法、通信装置及通信系统，用以实现有效地管理具备热点分享功能的终端设备。
第一方面，本申请实施例提供一种热点设备的管理方法，该方法可以由用户面网元或应用于用户面网元的模块(如芯片)来执行。以用户面网元执行该方法为例，该方法包括：用户面网元接收来自策略控制网元的指示信息，该指示信息指示，当第一事件发生，则向该策略控制网元发送该第一事件，该第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；当该第一事件发生，该用户面网元向该策略控制网元发送该第一事件。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值的时候通知策略控制网元，从而策略控制网元获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，以便于策略控制网元决策对该终端设备的计费方式或控制方式，实现对终端设备的合理计费和精准控制。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的该热点接入阈值；或者，该指示信息包括该热点接入阈值。
上述方案，由策略控制网元为用户面网元配置热点接入阈值，能够实现准确配置热点接入阈值。
一种可能的实现方法中，该用户面网元根据该终端设备的业务套餐，确定该热点接入 阈值；或者，该用户面网元根据该用户面网元中的配置信息，确定该热点接入阈值。
上述方案，由用户面网元确定热点接入阈值，不需要策略控制网元向用户面网元配置热点接入阈值，可以减少信令开销。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的第一计费规则，该第一计费规则是根据该第一事件确定的；该用户面网元根据该第一计费规则，对该终端设备进行计费。
上述方案，能够有效设置计费规则，实现对终端设备的合理计费。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的第一控制策略规则，该第一控制策略规则是根据该第一事件确定的；该用户面网元根据该第一控制策略规则，对该终端设备进行控制。
上述方案，能够有效设置控制策略规则，实现对终端设备的合理控制。
一种可能的实现方法中，当发生第二事件，该用户面网元向该策略控制网元发送该第二事件，该第二事件表示通过热点分享技术接入到该终端设备的设备的数量小于或等于该热点接入阈值。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的第二计费规则，该第二计费规则是根据该第二事件确定的；该用户面网元根据该第二计费规则，对该终端设备进行计费。
也就是说，当通过热点分享技术接入到该终端设备的设备的数量有变化时，计费规则会适应性修改，上述方案，能够根据实际情况更改计费规则，实现对终端设备的合理计费。上述描述适用于其他方面的描述，不再赘述。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的第二控制策略规则，该第二控制策略规则是根据该第二事件确定的；该用户面网元根据该第二控制策略规则，对该终端设备进行控制。
也就是说，当通过热点分享技术接入到该终端设备的设备的数量有变化时，控制策略规则会适应性修改，上述方案，能够根据实际情况更改控制策略规则，实现对终端设备的合理控制。上述描述适用于其他方面的描述，不再赘述。
一种可能的实现方法中，该用户面网元接收来自该终端设备的多个数据包，该多个数据包中的每个数据包中包含时间戳；该用户面网元根据该多个数据包的每个数据包中的时间戳，确定该多个数据包对应的时钟源的基准值；该用户面网元根据该多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到该终端设备的设备的数量，该心跳消息来源于该终端设备或通过热点分享技术接入到该终端设备的设备。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元获取网络中的互联网协议(internet protocol，IP)地址对应的网络流量特征参数；该用户面网元根据该网络流量特征参数，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元获取多个超文本传输协议(Hyper Text Transfer  Protocol，HTTP)请求消息，该HTTP请求消息包括设备参数；该用户面网元根据该多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
第二方面，本申请实施例提供一种热点设备的管理方法，该方法可以由策略控制网元或应用于策略控制网元的模块(如芯片)来执行。以策略控制网元执行该方法为例，该方法包括：策略控制网元向用户面网元发送指示信息，该指示信息指示，当第一事件发生，则向该策略控制网元发送该第一事件，该第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；当该第一事件发生，该策略控制网元接收来自该用户面网元的该第一事件。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值的时候通知策略控制网元，从而策略控制网元获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，以便于策略控制网元决策对该终端设备的计费方式或控制方式，实现对终端设备的合理计费和精准控制。
一种可能的实现方法中，该策略控制网元向该用户面网元发送该热点接入阈值；或者，该指示信息包括该热点接入阈值。
上述方案，由策略控制网元为用户面网元配置热点接入阈值，能够实现准确配置热点接入阈值。
一种可能的实现方法中，该策略控制网元根据该第一事件，确定第一计费规则，第一计费规则用于对终端设备进行计费；该策略控制网元向该用户面网元发送该第一计费规则。
上述方案，能够有效设置计费规则，实现对终端设备的合理计费。
一种可能的实现方法中，该策略控制网元根据该第一事件，确定第一控制策略规则，第一控制策略规则用于对终端设备进行控制；该策略控制网元向该用户面网元发送该第一控制策略规则。
上述方案，能够有效设置控制策略规则，实现对终端设备的合理控制。
一种可能的实现方法中，该策略控制网元接收来自该用户面网元的第二事件，该第二事件表示通过热点分享技术接入到该终端设备的设备的数量小于或等于该热点接入阈值。
一种可能的实现方法中，该策略控制网元根据该第二事件，确定第二计费规则，第二计费规则用于对终端设备进行计费；该策略控制网元向该用户面网元发送该第二计费规则。
一种可能的实现方法中，该策略控制网元根据该第二事件，确定第二控制策略规则，第二控制策略规则用于对终端设备进行控制；该策略控制网元向该用户面网元发送该第二控制策略规则。
第三方面，本申请实施例提供一种热点设备的管理方法，该方法可以由用户面网元或应用于用户面网元的模块(如芯片)来执行。以用户面网元执行该方法为例，该方法包括：用户面网元接收来自策略控制网元指示信息，该指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向该策略控制网元发送变化后的设备的数量；当通过热点分享技术接入到该终端设备的设备的数量从第一数量变为第二数量，该用户面网元向该策略控制网元发送该第二数量。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量发生变化后， 向策略控制网元发送变化后的设备的数量，从而策略控制网元根据变化后的设备的数量，决策对该终端设备的计费方式或控制方式，实现对终端设备的合理计费和精准控制。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的计费规则，该计费规则是根据该第二数量确定的；进而该用户面网元根据该计费规则，对该终端设备进行计费。
上述方案，能够有效设置计费规则，实现对终端设备的合理计费。
一种可能的实现方法中，该用户面网元接收来自该策略控制网元的控制策略规则，该控制策略规则是根据该第二数量确定的；该用户面网元根据该控制策略规则，对该终端设备进行控制。
上述方案，能够有效设置控制策略规则，实现对终端设备的合理控制。
一种可能的实现方法中，该用户面网元接收来自该终端设备的多个数据包，该多个数据包中的每个数据包中包含时间戳；该用户面网元根据该多个数据包的每个数据包中的时间戳，确定该多个数据包对应的时钟源的基准值；该用户面网元根据该多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到该终端设备的设备的数量，该心跳消息来源于该终端设备或通过热点分享技术接入到该终端设备的设备。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元获取多个数据包对应的网络流量特征参数；该用户面网元根据该网络流量特征参数，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，该用户面网元获取多个HTTP请求消息，该HTTP请求消息包括设备参数；该用户面网元根据该多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到该终端设备的设备的数量。
上述方案，能够实现准确确定通过热点分享技术接入到该终端设备的设备的数量。
第四方面，本申请实施例提供一种热点设备的管理方法，该方法可以由策略控制网元或应用于策略控制网元的模块(如芯片)来执行。以策略控制网元执行该方法为例，该方法包括：策略控制网元向用户面网元发送指示信息，该指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向该策略控制网元发送变化后的设备的数量；当通过热点分享技术接入到该终端设备的设备的数量从第一数量变为第二数量，该策略控制网元接收来自该用户面网元的该第二数量。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量发生变化后，向策略控制网元发送变化后的设备的数量，从而策略控制网元能够根据变化后的设备的数量，决策对该终端设备的计费方式或控制方式，有助于实现对终端设备的合理计费和精准控制。
一种可能的实现方法中，该策略控制网元根据该第二数量，确定计费规则；该策略控制网元向该用户面网元发送该计费规则。
上述方案，能够有效设置计费规则，实现对终端设备的合理计费。
一种可能的实现方法中，该策略控制网元根据该第二数量，确定控制策略规则；该策略控制网元向该用户面网元发送该控制策略规则。
上述方案，能够有效设置控制策略规则，实现对终端设备的合理控制。
第五方面，本申请实施例提供一种通信装置，该装置可以是用户面网元或应用于用户面网元中的模块(如芯片)。该装置具有实现上述第一方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请实施例提供一种通信装置，该装置可以是策略控制网元或应用于策略控制网元中的模块(如芯片)。该装置具有实现上述第二方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请实施例提供一种通信装置，该装置可以是用户面网元或应用于用户面网元中的模块(如芯片)。该装置具有实现上述第三方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请实施例提供一种通信装置，该装置可以是策略控制网元或应用于策略控制网元中的模块(如芯片)。该装置具有实现上述第四方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，本申请实施例提供一种通信装置，包括与存储器耦合的处理器，该处理器用于调用所述存储器中存储的程序，以执行上述第一方面至第四方面中的任意实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器可以是一个或多个。
第十方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机指令，当该装置运行时，该处理器执行该存储器存储的计算机指令，以使该装置执行上述第一方面至第四方面中的任意实现方法。
第十一方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第四方面中的任意实现方法的各个步骤的单元或手段(means)。
第十二方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述第一方面至第四方面中的任意实现方法。该处理器包括一个或多个。
第十三方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在通信装置上运行时，使得上述第一方面至第四方面中的任意实现方法被执行。
第十四方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序或指令，当计算机程序或指令被通信装置运行时，使得上述第一方面至第四方面中的任意实现方法被执行。
第十五方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面至第四方面中的任意实现方法。
第十六方面，本申请实施例还提供一种通信系统，包括：用于执行上述第一方面的任 意实现方法中的用户面网元，以及用于执行上述第二方面中的任意实现方法的策略控制网元。
第十七方面，本申请实施例还提供一种通信系统，包括：用于执行上述第三方面中的任意实现方法的用户面网元，以及用于执行上述第四方面中的任意实现方法的策略控制网元。
附图说明
图1为基于服务化架构的5G网络架构示意图；
图2(a)为本申请实施例提供的一种热点设备的管理方法的流程示意图；
图2(b)为本申请实施例提供的一种热点设备的管理方法的流程示意图；
图2(c)为确定通过热点分享技术接入到终端设备的设备的数量的示例图；
图3为本申请实施例提供的一种热点设备的管理方法的流程示意图；
图4为本申请实施例提供的一种热点设备的管理方法的流程示意图；
图5为本申请实施例提供的一种热点设备的管理方法的流程示意图；
图6为本申请实施例提供的一种通信装置示意图；
图7为本申请实施例提供的一种通信装置示意图。
具体实施方式
图1为基于服务化架构的第五代(5th generation，5G)网络架构示意图。图1所示的5G网络架构中可包括终端设备、接入网、核心网以及数据网络(data network，DN)。终端设备通过接入网和核心网接入数据网络。
终端设备可以是用户设备(user equipment，UE)、移动台、移动终端等。图1以终端设备为UE为例进行描述。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。
接入网用于实现接入有关的功能，可以为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输链路以传输用户数据。接入网在终端设备与核心网之间转发控制信号和用户数据。接入网可以包括接入网设备，接入网设备可以是为终端设备提供接入的设备，可以包括无线接入网(radio access network，RAN)设备和有线接入网设备。图1以接入网设备为RAN为例进行描述。RAN设备，主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。RAN设备可以包括各种形式的基站，例如宏基站，微基站(也可称为小站)，中继站，接入点，气球站等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为RAN或者下一代基站(next-generation Node basestation，gNB)，在长期演进(long term evolution，LTE)系统中，称为演进的节点B (evolved NodeB，eNB或eNodeB)。
接入网设备和终端设备可以是固定位置的，也可以是可移动的。接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和终端设备的应用场景不做限定。
核心网负责维护移动网络的签约数据，为终端设备提供会话管理、移动性管理、策略管理以及安全认证等功能。核心网中包括但不限于以下一个或多个网元：应用功能(application function，AF)网元、统一数据管理(unified data management，UDM)网元、策略控制功能(policy control function，PCF)网元、会话管理功能(session management function，SMF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、用户面功能(user plane function，UPF)网元。为方便描述，举例来说，下文将统一数据管理网元简称为UDM，其他网元类似。
AMF，主要负责移动网络中的移动性管理，例如用户位置更新、用户注册网络、用户切换等。
SMF，主要负责移动网络中的会话管理，例如会话建立、修改、释放。具体功能例如为用户分配IP地址，选择提供报文转发功能的UPF等。
UPF，主要负责用户数据的转发和接收，可以从数据网络接收用户数据，通过接入网络设备传输给终端设备；还可以通过接入网设备从终端设备接收用户数据，转发至数据网络。
UDM，包含执行管理签约数据、用户接入授权等功能。
AF，传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。
PCF，主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。PCF可以向AMF或SMF提供策略，例如QoS策略、切片选择策略等。
DN，其上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1中Namf、Npcf、Nsmf、Nudm、Naf分别为上述AMF、PCF、SMF、UDM、AF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4以及N6为接口序列号，这些接口序列号的含义如下：
1)、N1：AMF与终端设备之间的接口，可以用于向终端设备传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
2)、N2：AMF与RAN之间的接口，可以用于传递核心网侧至接入网设备的无线承载控制信息等。
3)、N3：RAN与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户 面数据。
4)、N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
5)、N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。作为一种可能的实现方法，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
网络共享技术，也称为热点分享技术，该技术的应用可以将笔记本电脑(Laptop)、台式机、平板电脑(Tablet)或其它智能终端等设备通过有线或者无线(例如，WiFi、蓝牙或USB物理连接)等连接方式接入具备上网功能的智能终端，从而能够为该具备上网功能的智能终端以外的设备提供分组数据业务。例如，该网络共享技术可以为网络共用技术(Tethering)，其中，提供Tethering功能的智能终端可以称为Tethering用户。
随着拥有网络共享技术的智能终端的普及，大量的笔记本电脑、平板电脑等非签约设备可以通过智能终端的网络共享技术使用网络流量。由于运营商无法感知使用网络共享技术接入网络的终端设备，因此运营商无法针对使用网络流量的设备的实际情况进行分析和判断，从而无法更好的为用户提供服务。
图2(a)为本申请实施例提供的一种热点设备的管理方法的流程示意图。该方法包括以下步骤：
步骤201a，策略控制网元向用户面网元发送指示信息。
相应地，用户面网元接收该指示信息。
其中，策略控制网元向用户面网元发送指示信息，具体的，策略控制网元可以通过会话管理网元向用户面网元发送该指示信息。
当本申请实施例应用于5G场景，则该策略控制网元是PCF网元，该会话管理网元是SMF网元，该用户面网元是UPF网元。
当本申请实施例应用于4G场景，则该策略控制网元是策略与计费规则功能(Policy and Charging Rules Function，PCRF)网元，该会话管理网元是分组数据网络网关-控制面(Packet Data Network Gateway-Control Plane，PGW-C)网元，该用户面网元是分组数据网络网关-用户面(Packet Data Network Gateway-User Plane，PGW-U)网元。
当然，本申请实施例还可以应用于未来通信场景，如第六代(6th generation，6G)通信场景，本申请对此不做限定。这里对策略控制网元、会话管理网元、用户面网元的实现做统一说明，后续不赘述。
该指示信息指示，当第一事件发生，则向策略控制网元发送第一事件。该第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，或者该第一事件为通过热点分享技术接入到终端设备的设备的数量大于热点接入阈值。
步骤202a，当第一事件发生，用户面网元向策略控制网元发送第一事件。
相应地，策略控制网元接收该第一事件。
用户面网元在收到上述指示信息后，对通过热点分享技术接入到终端设备的设备的数量进行检测，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量大于热点接入阈值，表明第一事件发生，因此用户面网元向策略控制网元发送该第一事件，从而 策略控制网元能够获知：通过热点分享技术接入到终端设备的设备的数量大于或等于该热点接入阈值。
示例性的，假设热点接入阈值为5，指示信息用于指示，当通过热点分享技术接入到终端设备1的设备的数量大于或等于5，则向策略控制网元上报。因此用户面网元对通过热点分享技术接入到终端设备1的设备进行检测，当检测到通过热点分享技术接入到终端设备1的设备的数量大于或等于5，则向策略控制网元上报：通过热点分享技术接入到终端设备1的设备的数量大于或等于5。
一种实现方法中，在上述步骤202a之前，用户面网元从策略控制网元接收上述热点接入阈值，也即策略控制网元向用户面网元提供该热点接入阈值。该热点接入阈值与上述指示信息可以是在同一个消息中发送，也可以是在不同的消息中发送。
又一种实现方法中，上述指示信息包括上述热点接入阈值。
又一种实现方法中，用户面网元根据终端设备的业务套餐，确定热点接入阈值。也即，不同的业务套餐所对应的热点接入阈值可以是相同的，也可以是不同的。
又一种实现方法中，用户面网元根据用户面网元中的配置信息，确定热点接入阈值。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值的时候通知策略控制网元，从而策略控制网元获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，以便于策略控制网元决策对该终端设备的计费方式或控制方式，有助于实现对终端设备的合理计费和精准控制。
一种实现方法中，在上述步骤202a之后，还可以执行以下步骤203a和/或步骤204a。
步骤203a，策略控制网元向用户面网元发送第一计费规则。
相应地，用户面网元接收该第一计费规则。
策略控制网元在收到第一事件之后，获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，则策略控制网元更新计费规则，得到第一计费规则。然后策略控制网元向用户面网元发送第一计费规则，用户面网元根据第一计费规则对终端设备进行计费。
比如，该第一计费规则相较于更新前的计费规则，提升了流量单价(或流量使用费率)，或者是由之前的不计费更新为开始计费。本申请实施例对计费规则的具体实现方法不做限定。因而该方法能够有效设置计费规则，实现对终端设备的合理计费。
步骤204a，策略控制网元向用户面网元发送第一控制策略规则。
相应地，用户面网元接收该第一控制策略规则。
策略控制网元在收到第一事件之后，获知通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值，则策略控制网元更新控制策略规则，得到第一控制策略规则。然后策略控制网元向用户面网元发送第一控制策略规则，用户面网元根据第一控制策略规则对终端设备进行控制。
比如，该第一控制策略规则相较于更新前的控制策略规则，限制设备的流量带宽或降低设备的流量网速，等等。本申请实施例对控制策略规则的具体实现方法不做限定。该方法能够有效设置控制策略规则，实现对终端设备的合理控制。
一种实现方法中，在上述步骤202a之后，还可以执行以下步骤205a。
步骤205a，当第二事件发生，用户面网元向策略控制网元发送第二事件。
相应地，策略控制网元接收该第二事件。
该第二事件表示通过热点分享技术接入到终端设备的设备的数量小于或等于热点接入阈值。
可以理解的是，第二事件为与第一事件不同的事件，也就是说，当通过热点分享技术接入到终端设备的设备的数量发生了变动，比如数量从大于热点接入阈值变更为小于或等于热点接入阈值，用户面网元向策略控制网元告知该数量的变动。换句话说，该用户面网元可以动态地感知该数量的变动，并实时告知该策略控制网元该数量的变动，从而实现对终端设备的动态的管理。
一种实现方法中，在上述步骤205a之后，还可以执行以下步骤206a和/或步骤207a。
步骤206a，策略控制网元向用户面网元发送第二计费规则。
相应地，用户面网元接收该第二计费规则。
策略控制网元在收到第二事件之后，获知通过热点分享技术接入到终端设备的设备的数量小于或等于热点接入阈值，则策略控制网元更新计费规则，得到第二计费规则。然后策略控制网元向用户面网元发送第二计费规则，用户面网元根据第二计费规则对终端设备进行计费。
比如，该第二计费规则相较于更新前的计费规则，降低了流量单价(或流量使用费率)，或者是由之前的计费更新为不计费。本申请实施例对计费规则的具体实现方法不做限定。该方法能够有效设置计费规则，实现对终端设备的合理计费。
步骤207a，策略控制网元向用户面网元发送第二控制策略规则。
相应地，用户面网元接收该第二控制策略规则。
策略控制网元在收到第二事件之后，获知通过热点分享技术接入到终端设备的设备的数量小于或等于热点接入阈值，则策略控制网元更新控制策略规则，得到第二控制策略规则。然后策略控制网元向用户面网元发送第二控制策略规则，用户面网元根据第二控制策略规则对终端设备进行控制。
比如，该第一控制策略规则相较于更新前的控制策略规则，提升设备的带宽流量或提升设备的流量网速，等等。本申请实施例对控制策略规则的具体实现方法不做限定。该方法能够有效设置控制策略规则，实现对终端设备的合理控制。
下面介绍用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法。以下方法1至方法4仅作为示例，本申请不限定用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法。
方法1，用户面网元接收来自终端设备的多个数据包，多个数据包中的每个数据包中包含时间戳，用户面网元根据多个数据包的每个数据包中的时间戳，确定多个数据包对应的时钟源的基准值，用户面网元根据多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到终端设备的设备的数量。
如果该终端设备开启了热点分享，且有其它设备通过热点分享技术接入到该终端设备，则其它设备将会通过该终端设备发送数据包，因此用户面网元接收的来自终端设备的多个数据包中，既包含该终端设备发出的数据包，也包含该其它设备发出的数据包。
不管是终端设备，还是通过热点分享技术接入到该终端设备的其它设备，在发送数据包时，均会在数据包中携带时间戳，该时间戳与产生该数据包的设备的时钟源有关。因此用户面网元可以根据获取到的数据包中的时间戳，确定数据包对应的时钟源的基准值。由 于同一个时钟源的基准值相同，因此用户面可以根据不同种类的时钟源的基准值的数量，确定通过热点分享技术接入到终端设备的设备的数量。其中，时钟源的基准值可以理解为时钟源在某个参考时刻的取值。不同设备的时钟源在同一时刻的取值不同，也即不同设备的时钟源的基准值不同。
比如，用户面网元根据收到的多个数据包中的时间戳，确定存在5种基准值，则该5种基准值中，有1个基准值是开启了热点分享的终端设备的时钟源的基准值，其它4个基准值是通过热点分享技术接入到该终端设备的其它设备的时钟源的基准值，因此用户面网元确定通过热点分享技术接入到该终端设备的设备的数量为4。
下面结合一个示例对该方法进行说明。例如，UE1是开启了热点分享的设备，然后设备1、设备2和设备3通过UE1开启的热点接入该UE1。下面介绍用户面网元识别出通过热点分享技术接入到UE1的设备的数量为3的方法。
UE1在开机时，UE1的时钟源会产生一个初始值(用initialTimestamp1表示)，例如该初始值为1000。然后随着时间的推移，时间每经过1秒，该时钟源的数值会增加一个固定量(用numinbysec表示)，该numinbysec取值为1000。比如在UE1开机1秒之后时钟源更新为2000，在UE1开机2秒之后时钟源更新为3000，以此类推。UE1在产生数据包时，会获取UE1的时钟源的当前取值，然后数据包中将携带该取值作为时间戳(timestamp)。例如，在t1时刻，UE1的时钟源的取值为timestamp1，UE1在数据包中携带该timestamp1。类似的，在t2时刻，UE1的时钟源的取值为timestamp2，UE1在数据包中携带该timestamp2，以此类推。
同样的，设备1在开机时，设备1的时钟源会产生一个初始值(用initialTimestamp2表示)，例如该初始值为2000。然后随着时间的推移，时间每经过1秒，该时钟源的数值会增加一个固定量(用numinbysec表示)，该numinbysec取值为1000。比如在设备1开机1秒之后时钟源更新为3000，在设备1开机2秒之后时钟源更新为4000，以此类推。设备1在产生数据包时，会获取设备1的时钟源的当前取值，然后将该取值作为timestamp携带在数据包中。例如，在t3时刻，设备1的时钟源的取值为timestamp3，设备1在数据包中携带该timestamp3。类似的，在t4时刻，设备1的时钟源的取值为timestamp4，设备1在数据包中携带该timestamp4，以此类推。
类似的，设备2、设备3也会在数据包中携带相应的timestamp。
因此用户面网元收到的来自UE1、设备1、设备2或设备3的数据包中均会携带一个时间戳。用户面网元可以在不同的时刻采样得到多个数据包中的时间戳，通过对该多个时刻采样得到的多个时间戳进行函数拟合，得到多条斜率相同的直线，该直线的数量表征了该多个数据包来源的设备的总数量，也可以理解为，通过拟合得到的多条直线所代表的不同的设备的初始值不同。由于不同的设备在开机时的初始值为随机值，所以初始值的数量可以视为设备的数量。以图2(c)为例，用户面网元在时刻tx和时刻ty分别采样得到多个数据包并获取数据包中的timestamp，然后对采样得到的多个timestamp进行拟合，得到4条直线。其中同一条直线上对应的数据包是来源于同一个设备，因此4条直线则表示采用的多个数据包是来源于4个设备，该4个设备即为UE1、设备1、设备2和设备3。因此用户面网元确定通过热点分享技术接入到UE1的设备的数量为4-1＝3。
方法2，用户面网元根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到终端设备的设备的数量，心跳消息来源于终端设备或通过热点 分享技术接入到终端设备的设备。
终端设备的操作系统(如IOS、Android、Windows)会周期性地向应用服务器发送心跳消息，终端设备发出心跳消息，到达用户面网元，然后用户面网元再将心跳消息转发至应用服务器。因此用户面网元可以检测到该终端设备的心跳消息。
针对通过热点分享技术接入到终端设备的其它设备，该设备的操作系统也会周期性地向应用服务器发送心跳消息，当设备发出心跳消息，该心跳消息经由终端设备到达用户面网元，然后用户面网元再将心跳消息转发至应用服务器。因此用户面网元可以检测到该设备的心跳消息。
一种实现方法中，如果不同设备发出的心跳消息的类型不同，则用户面网元可以根据在一个或多个周期内检测到的心跳消息的类型，确定通过热点分享技术接入到该终端设备的设备的数量。例如，终端设备1分享热点，然后有3个设备，分别为设备1、设备2和设备3均通过热点分享技术接入到终端设备1。如果用户面网元能够在一个或多个周期内检测到来自终端设备1的4种类型的心跳消息，则用户面网元确定通过热点分享技术接入到终端设备1的设备的数量为4-1＝3。
又一种实现方法中，由于安装相同类型的操作系统类型的设备的心跳消息发送周期相同，因此可以通过检测一个周期内的心跳消息的数量，来确定通过热点分享技术接入到终端设备1的设备的数量。比如安装安卓操作系统的设备按照T1周期发送心跳消息，安装苹果操作系统的设备按照T2周期发送心跳消息，则用户面网元可以在一个T1时长的周期内检测安卓设备发出的心跳消息的数量，比如为K1，以及在一个T2时长的周期内检测苹果设备发出的心跳消息的数量，比如为K2，则用户面网元确定通过热点分享技术接入到终端设备1的设备的数量为(K1+K2)-1。
可以理解的是，该方法2可以和方法1同时使用。例如，在检测心跳消息的特征的同时，对于相同特征的多个数据包使用方法1进行判断，这样可以更加精准的确定出通过热点分享技术接入到终端设备1的设备的数量。
方法3，用户面网元获取多个数据包对应的网络流量特征参数，用户面网元根据网络流量特征参数，确定通过热点分享技术接入到终端设备的设备的数量。
热点接入本质上是一种网络地址转换(network address translation，NAT)行为，流量识别本质是将网络中的IP地址划分为NAT设备的IP地址与普通主机的IP地址，这与热点分享行为的识别有一定相似性，其中，开启了热点分享功能的终端设备可视作NAT设备，其它未开启热点分享功能的设备视作普通主机。该方法的总体思想是获取网络中的IP地址，然后以各个IP地址作为数据挖掘中的实例，通过数据挖掘将网络中的设备NAT设备与普通主机。
然后，用户面网元进一步确定通过热点分享技术接入到NAT设备的设备的数量，具体方法为：用户面网元采集数据包，然后用户面网元根据机器学习/深度模型对采集到的数据包对应的网络流量特征参数进行分析，确定通过热点分享技术接入到终端设备的设备的数量。其中，数据包对应的网络流量特征参数包括数据包到达时间、数据包中的IP层信息、数据包中的传输控制协议(Transmission Control protocol，TCP)层信息中的一个或多个。该机器学习/深度模型是预先根据收集到的多个数据包中的网络流量特征参数以及NAT设备的标签信息训练得到的。
方法4，用户面网元获取多个HTTP请求消息，HTTP请求消息包括设备参数，用户 面网元根据多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到终端设备的设备的数量。
设备访问HTTP业务时，发送HTTP请求消息，该HTTP请求消息的消息头中的UserAgent字段携带设备的操作系统类型、设备的浏览器类型或设备类型等参数中的一个或多个参数，因此用户面网元可以根据该HTTP请求消息的消息头中携带的参数，判断该设备是否为通过热点分享技术接入到终端设备的设备，进而确定通过热点分享技术接入到终端设备的设备的数量。
类似的，上述多种方法可以相互结合使用来确定通过热点分享技术接入到终端设备的设备的数量。不再赘述。
图2(b)为本申请实施例提供的一种热点设备的管理方法的流程示意图。该方法包括以下步骤：
步骤201b，策略控制网元向用户面网元发送指示信息。
相应地，用户面网元接收该指示信息。
该发送动作可以参考步骤201a的描述。
指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向策略控制网元发送变化后的设备的数量。
步骤202b，当通过热点分享技术接入到终端设备的设备的数量从第一数量变为第二数量，用户面网元向策略控制网元发送第二数量。
也即，当用户面网元确定通过热点分享技术接入到终端设备的设备的数量发生变化，则向策略控制网元发送变化的设备的数量。
上述方案，策略控制网元指示用户面网元对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量发生变化后，向策略控制网元发送变化后的设备的数量，从而策略控制网元根据变化后的设备的数量，决策对该终端设备的计费方式或控制方式，进而有助于实现对终端设备的合理计费和精准控制。
一种实现方法中，在上述步骤202b之后，还可以执行以下步骤203b，或执行步骤204b，或执行步骤203b和步骤204b。
步骤203b，策略控制网元向用户面网元发送计费规则。
相应地，用户面网元接收该计费规则。
策略控制网元在收到第二数量之后，根据第二数量确定计费规则。然后策略控制网元向用户面网元发送计费规则，用户面网元根据计费规则对终端设备进行计费。
一种实现方法中，本申请实施例对通过热点分享技术接入到终端设备的设备的数量划定区间，针对每个区间设置一种计费规则。比如，当设备的数量属于0至2这个区间，则设置计费规则1，当设备的数量属于3至5这个区间，则设置计费规则2，以此类推。本申请实施例对计费规则的具体实现方法不做限定。该方法能够有效设置计费规则，实现对终端设备的合理计费。
步骤204b，策略控制网元向用户面网元发送控制策略规则。
相应地，用户面网元接收该控制策略规则。
策略控制网元在收到第二数量之后，根据第二数量确定控制策略规则。然后，策略控制网元向用户面网元发送控制策略规则，用户面网元根据控制策略规则对终端设备进行控 制。
一种实现方法中，本申请实施例对通过热点分享技术接入到终端设备的设备的数量划定区间，针对每个区间设置一种控制策略规则。比如，当设备的数量属于0至2这个区间，则设置控制策略规则1，当设备的数量属于3至5这个区间，则设置控制策略规则2，以此类推。本申请实施例对控制策略规则的具体实现方法不做限定。该方法能够有效设置控制策略规则，实现对终端设备的合理控制。
需要说明的是，该图2(b)的实施例中，用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法，可以参考上述图2(a)的实施例中的相关描述，该图2(b)的实施例中不再赘述。
下面结合具体实施例，对上述图2(a)、图2(b)的实施例进行说明。其中，以下图3和图5的实施例是上述图2(a)的实施例的具体示例，以下图4的实施例是上述图2(b)的实施例的具体示例。
图3为本申请实施例提供的一种热点设备的管理方法的流程示意图。该方法包括以下步骤：
步骤301，终端设备向会话管理网元发送会话建立请求消息。
该终端设备是具备上网能力且具备热点分享功能的设备。比如，该终端设备是智能手机等。
在4G中，会话管理网元是PGW-C。在5G中，会话管理网元是SMF。
在5G中，该会话建立请求消息可以是Nsmf_PDUSession_CreateSMContext Request消息。
步骤302，会话管理网元向策略控制网元发送策略建立请求消息。
在4G中，策略控制网元是PCRF，会话管理网元(即PGW-C)通过PGW-C与PCRF之间的Gx接口向PCRF发送策略建立请求消息。
在5G中，策略控制网元是PCF，会话管理网元(即SMF)通过SMF与PCF之间的N7接口向PCF发送策略建立请求消息。
在5G中，该策略建立请求消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立请求消息用于请求用户策略。
步骤303，策略控制网元向会话管理网元发送策略建立响应消息。
在5G中，该策略建立响应消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立响应消息中包括热点接入超过阈值上报事件和热点接入阈值，该热点接入超过阈值上报事件用于指示，当发生通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值的事件，则上报该事件。其中，策略控制网元可以从本地获取终端设备的签约数据，并从签约数据中获取该终端设备对应的热点接入阈值。
一种实现方法中，在4G中，该策略建立响应消息中包括信用控制结果(credit control answer，CCA)消息或重授权请求(Re-Auth-Request，RAR)消息，该CCA消息或RAR消息中包括热点接入超过阈值上报事件和热点接入阈值。
其中，该热点接入超过阈值上报事件是上述图2(a)的实施例中的指示信息的一个具体示例。
以CCA消息为例，该CCA消息目前包括Event-Trigger字段。
在4G应用场景中，本申请可以对Event-Trigger字段进行扩展，增加该Event-Trigger 的取值范围，比如新增该Event-Trigger的取值为TETHERING_EXCEED_NUM_REPORT，该TETHERING_EXCEED_NUM_REPORT是热点接入超过阈值上报事件的一个示例。相应地，还增加与TETHERING_EXCEED_NUM_REPORT对应的Tethering-Num-Threshold，该Tethering-Num-Threshold是热点接入阈值的一个示例。当CCA消息中的Event-Trigger取值为TETHERING_EXCEED_NUM_REPORT，则该CCA消息中还包括Tethering-Num-Threshold。其中，该TETHERING_EXCEED_NUM_REPORT与该Tethering-Num-Threshold称为一个属性值对(attributevalue pair，AVP)。
又一种实现方法中，在5G应用场景中，该策略建立响应消息中包括SmPolicyDecision。该SmPolicyDecision中包含的部分内容如表1所示。
表1
其中，policyCtrlReqTriggers是已经存在的属性，policyCtrlReqTriggers的取值用PolicyControlRequestTrigger表示。本申请实施例新增policyCtrlReqTriggers的取值范围，比如新增policyCtrlReqTriggers的取值为TETHERING_EXCEED_NUM_REPORT，该TETHERING_EXCEED_NUM_REPORT是热点接入超过阈值上报事件的一个示例。
其中，Tethering_num_Threshold是新增的属性，该Tethering_num_Threshold是热点接入阈值的一个示例。
步骤304，会话管理网元向用户面网元发送会话建立请求消息。
在4G中，用户面网元是PGW-U，会话管理网元(即PGW-C)通过PGW-C与PGW-U之间的Sx接口向PGW-U发送会话建立请求消息。
在5G中，用户面网元是UPF，会话管理网元(即SMF)通过SMF与UPF之间的N4接口向UPF发送会话建立请求消息。
该5G中，该会话建立请求消息可以是N4 Session Establish Request消息。
该会话建立请求消息中包括热点接入超过阈值上报事件和热点接入阈值。
一种实现方法中，该会话建立请求消息中包括用量上报规则(Usage Reporting Rule，URR)，该URR中包括Extended Reporting Triggers和Tethering_num_Threshold。该Extended Reporting Triggers中包括热点接入超过阈值上报事件，该Tethering_num_Threshold是热点接入阈值的一个示例。
步骤305，用户面网元根据热点接入超过阈值上报事件，启动热点接入检测。
其中，用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法， 可以参考上述图2(a)的实施例中的相关描述，不再赘述。
步骤306，用户面网元向会话管理网元发送会话建立响应消息。
该5G中，该会话建立响应消息可以是N4 Session Establish Response消息。
步骤307，用户面网元向会话管理网元发送会话报告请求消息。
该5G中，该会话报告请求消息可以是N4 Session Reporting Request消息。
具体的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值，则用户面网元向会话管理网元发送会话报告请求消息，该会话报告请求消息中包括热点接入超过阈值事件，该热点接入超过阈值事件表示通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值。
其中，该热点接入超过阈值事件是上述图2(a)的实施例中的第一事件的一个具体示例。
示例性地，该会话报告请求消息中包括ExtendedUsage Report Triggers，该ExtendedUsage Report Triggers中可以包含热点接入超过阈值事件。步骤308，会话管理网元向策略控制网元发送策略更新请求消息。
在5G中，该策略更新请求消息可以是Npcf_SMPolicyControl_Update_Request消息。
该策略更新请求消息中包括热点接入超过阈值事件。
步骤309，策略控制网元确定针对终端设备的计费规则1和/或控制策略规则1。
策略控制网元收到的热点接入超过阈值事件，触发策略控制网元根据预配置策略或签约策略，确定针对终端设备的计费规则1和/或控制策略规则1。
步骤310，策略控制网元向会话管理网元发送策略更新响应消息。
在5G中，该策略更新响应消息可以是Npcf_SMPolicyControl_Update_Response消息。
该策略更新响应消息中包括针对终端设备的计费规则1和/或针对终端设备的控制策略规则1。
步骤311，会话管理网元向用户面网元发送会话修改请求消息。
该5G中，该会话修改请求消息可以是N4 Session Modification Request消息。
该会话修改请求消息中包括针对终端设备的计费规则1和/或控制策略规则1。一种实现方法中，该会话修改请求消息中包括包检测规则(Packet Detection Rule，PDR)，该PDR中包括针对终端设备的计费规则1和/或控制策略规则1。
步骤312，用户面网元根据针对终端设备的计费规则1对终端设备进行计费，和/或根据针对终端设备的控制策略规则1对终端设备进行控制。
可选的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量，由超过热点接入阈值变为低于热点接入阈值，则在步骤312之后还可以执行以下步骤313至步骤318。
步骤313，用户面网元向会话管理网元发送会话报告请求消息。
该5G中，该会话报告请求消息可以是N4 Session Reporting Request消息。
具体的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量，由超过热点接入阈值变为低于热点接入阈值，则用户面网元向会话管理网元发送会话报告请求消息，该会话报告请求消息中包括热点接入低于阈值事件，该热点接入低于阈值事件表示通过热点分享技术接入到终端设备的设备的数量低于热点接入阈值。
其中，该热点接入低于阈值事件是上述图2(a)的实施例中的第二事件的一个具体示例。
示例性地，该会话报告请求消息中包括ExtendedUsage Report Triggers，该 ExtendedUsage Report Triggers中可以包含热点接入低于阈值事件。
步骤314，会话管理网元向策略控制网元发送策略更新请求消息。
在5G中，该策略更新请求消息可以是Npcf_SMPolicyControl_Update_Request消息。
该策略更新请求消息中包括热点接入低于阈值事件。
步骤315，策略控制网元确定针对终端设备的计费规则2和/或控制策略规则2。
策略控制网元收到的热点接入低于阈值事件，触发策略控制网元根据预配置策略或签约策略，确定针对终端设备的计费规则2和/或控制策略规则2。
步骤316，策略控制网元向会话管理网元发送策略更新响应消息。
在5G中，该策略更新响应消息可以是Npcf_SMPolicyControl_Update_Response消息。
该策略更新响应消息中包括针对终端设备的计费规则2和/或针对终端设备的控制策略规则2。
步骤317，会话管理网元向用户面网元发送会话修改请求消息。
该5G中，该会话修改请求消息可以是N4 Session Modification Request消息。
该会话修改请求消息中包括针对终端设备的计费规则2和/或针对终端设备的控制策略规则2。一种实现方法中，该会话修改请求消息中包括PDR，该PDR中包括针对终端设备的计费规则2和/或针对终端设备的控制策略规则2。
步骤318，用户面网元根据针对终端设备的计费规则2对终端设备进行计费，和/或根据针对终端设备的控制策略规则2对终端设备进行控制。
上述方案，用户面网元能够对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值时，上报热点接入超过阈值事件，触发策略控制网元确定相应的计费规则和/或控制策略规则。以及用户面网元还可以在检测到通过热点分享技术接入到终端设备的设备的数量低于热点接入阈值时，上报热点接入低于阈值事件，触发策略控制网元确定相应的计费规则和/或控制策略规则。因此该方案能够实现根据对终端设备的精确计费和有效控制。
需要说明的是，上述步骤303和步骤304可以理解是上述图2(a)的实施例中的步骤201a的一种具体实现，上述步骤307和步骤308可以理解是上述图2(a)的实施例中的步骤202a的一种具体实现，上述步骤310和步骤311可以理解是上述图2(a)的实施例中的步骤203a和步骤204a的一种具体实现，上述步骤313和步骤314可以理解是上述图2(a)的实施例中的步骤205a的一种具体实现，上述步骤316和步骤317可以理解是上述图2(a)的实施例中的步骤206a和步骤207a的一种具体实现，其具体实现可以参考图2(a)的实施例中的相关描述，不再赘述。
图4为本申请实施例提供的一种热点设备的管理方法的流程示意图。该方法包括以下步骤：
步骤401，终端设备向会话管理网元发送会话建立请求消息。
该终端设备是具备上网能力且具备热点分享功能的设备。比如，该终端设备是智能手机等。
在4G中，会话管理网元是PGW-C。在5G中，会话管理网元是SMF。
在5G中，该会话建立请求消息可以是Nsmf_PDUSession_CreateSMContext Request消息。
步骤402，会话管理网元向策略控制网元发送策略建立请求消息。
在4G中，策略控制网元是PCRF，会话管理网元(即PGW-C)通过PGW-C与PCRF之间的Gx接口向PCRF发送策略建立请求消息。
在5G中，策略控制网元是PCF，会话管理网元(即SMF)通过SMF与PCF之间的N7接口向PCF发送策略建立请求消息。
在5G中，该策略建立请求消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立请求消息用于请求用户策略。
步骤403，策略控制网元向会话管理网元发送策略建立响应消息。
在5G中，该策略建立响应消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立响应消息中包括热点接入设备的数量上报事件，该热点接入设备的数量上报事件用于指示，当发生通过热点分享技术接入到终端设备的设备的数量发生变化的事件，则上报变化后的设备的数量。
一种实现方法中，在4G中，该策略建立响应消息中包括CCA消息或RAR消息，该CCA消息或RAR消息中包括热点接入设备的数量上报事件。
其中，该热点接入设备的数量上报事件是上述图2(b)的实施例中的指示信息的一个具体示例。
以CCA消息为例，该CCA消息目前包括Event-Trigger字段。
在4G应用场景中，本申请可以对Event-Trigger进行扩展，增加该Event-Trigger的取值范围，比如新增该Event-Trigger的取值为TETHERING_NUM_REPORT，该TETHERING_NUM_REPORT是热点接入设备的数量上报事件的一个示例。
又一种实现方法中，在5G应用场景中，该策略建立响应消息中包括SmPolicyDecision。该SmPolicyDecision中包含的部分内容如表2所示。
表2
其中，policyCtrlReqTriggers是已经存在的属性，policyCtrlReqTriggers的取值用PolicyControlRequestTrigger表示。本申请实施例新增policyCtrlReqTriggers的取值范围，比如新增该policyCtrlReqTriggers的取值为TETHERING_NUM_REPORT。该TETHERING_NUM_REPORT是热点接入设备的数量上报事件的一个示例。
步骤404，会话管理网元向用户面网元发送会话建立请求消息。
在4G中，用户面网元是PGW-U，会话管理网元(即PGW-C)通过PGW-C与PGW-U之间的Sx接口向PGW-U发送会话建立请求消息。
在5G中，用户面网元是UPF，会话管理网元(即SMF)通过SMF与UPF之间的N4接口向UPF发送会话建立请求消息。
该5G中，该会话建立请求消息可以是N4 Session Establish Request消息。
该会话建立请求消息中包括热点接入设备的数量上报事件。
一种实现方法中，该会话建立请求消息中包括URR，该URR中包括Extended Reporting  Triggers。该Extended Reporting Triggers中包括热点接入设备的数量上报事件。
步骤405，用户面网元根据热点接入设备的数量上报事件，启动热点接入检测。
其中，用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法，可以参考上述图2(a)的实施例中的相关描述，不再赘述。
步骤406，用户面网元向会话管理网元发送会话建立响应消息。
该5G中，该会话建立响应消息可以是N4 Session Establish Response消息。
步骤407，用户面网元向会话管理网元发送会话报告请求消息。
该5G中，该会话报告请求消息可以是N4 Session Reporting Request消息。
具体的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量发生变化，则用户面网元向会话管理网元发送会话报告请求消息，该会话报告请求消息中包括通过热点分享技术接入到终端设备的设备的数量，该数量指的是变化后的设备的数量。
一种实现方法中，该会话报告请求消息中可以包括ExtendedUsage Report Triggers，该ExtendedUsage Report Triggers中可以包含通过热点分享技术接入到该终端设备的设备的数量。步骤408，会话管理网元向策略控制网元发送策略更新请求消息。
在5G中，该策略更新请求消息可以是Npcf_SMPolicyControl_Update_Request消息。
该策略更新请求消息中包括通过热点分享技术接入到终端设备的设备的数量。
步骤409，策略控制网元确定针对终端设备的计费规则和/或控制策略规则。
策略控制网元收到的通过热点分享技术接入到终端设备的设备的数量，触发策略控制网元根据预配置策略或签约策略，确定针对终端设备的计费规则和/或针对终端设备的控制策略规则。
步骤410，策略控制网元向会话管理网元发送策略更新响应消息。
在5G中，该策略更新响应消息可以是Npcf_SMPolicyControl_Update_Response消息。
该策略更新响应消息中包括针对终端设备的计费规则和/或控制策略规则。
步骤411，会话管理网元向用户面网元发送会话修改请求消息。
该5G中，该会话修改请求消息可以是N4 Session Modification Request消息。
该会话修改请求消息中包括针对终端设备的计费规则和/或控制策略规则。一种实现方法中，该会话修改请求消息中包括PDR，该PDR中包括针对终端设备的计费规则和/或控制策略规则。
步骤412，用户面网元根据针对终端设备的计费规则对终端设备进行计费，和/或根据针对终端设备的控制策略规则对终端设备进行控制。
后续，如果用户面网元检测到通过热点分享技术接入到终端设备的设备的数量发生变化，则重复执行上述步骤407至步骤412。
上述方案，用户面网元能够对通过热点分享技术接入到终端设备的设备的数量进行检测，并上报检测到的通过热点分享技术接入到终端设备的设备的数量，触发策略控制网元确定相应的计费规则和/或控制策略规则。因此该方案能够实现根据对终端设备的精确计费和有效控制。
需要说明的是，上述步骤403和步骤404可以理解是上述图2(b)的实施例中的步骤201b的一种具体实现，上述步骤407和步骤408可以理解是上述图2(b)的实施例中的步骤202b的一种具体实现，上述步骤410和步骤411可以理解是上述图2(b)的实施例中的步骤203b和步骤204b的一种具体实现，其具体实现可以参考图2(b)的实施例中的相关描述，不再赘 述。
图5为本申请实施例提供的一种热点设备的管理方法的流程示意图。该方法包括以下步骤：
步骤501，终端设备向会话管理网元发送会话建立请求消息。
该终端设备是具备上网能力且具备热点分享功能的设备。比如，该终端设备是智能手机等。
在4G中，会话管理网元是PGW-C。在5G中，会话管理网元是SMF。
在5G中，该会话建立请求消息可以是Nsmf_PDUSession_CreateSMContext Request消息。
步骤502，会话管理网元向策略控制网元发送策略建立请求消息。
在4G中，策略控制网元是PCRF，会话管理网元(即PGW-C)通过PGW-C与PCRF之间的Gx接口向PCRF发送策略建立请求消息。
在5G中，策略控制网元是PCF，会话管理网元(即SMF)通过SMF与PCF之间的N7接口向PCF发送策略建立请求消息。
在5G中，该策略建立请求消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立请求消息用于请求用户策略。
步骤503，策略控制网元向会话管理网元发送策略建立响应消息。
在5G中，该策略建立响应消息可以是Npcf_SMPolicyControl_Create_Request消息。
该策略建立响应消息中包括热点接入超过阈值上报事件，该热点接入超过阈值上报事件用于指示，当发生通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值的事件，则上报该事件。
一种实现方法中，在4G中，该策略建立响应消息中包括CCA消息或RAR消息，该CCA消息或RAR消息中包括热点接入超过阈值上报事件。
其中，该热点接入超过阈值上报事件是上述图2(a)的实施例中的指示信息的一个具体示例。
以CCA消息为例，该CCA消息目前包括Event-Trigger字段。
在4G应用场景中，本申请可以对Event-Trigger进行扩展，增加该Event-Trigger的取值范围，比如新增该Event-Trigger的取值为TETHERING_EXCEED_NUM_REPORT。该TETHERING_EXCEED_NUM_REPORT是热点接入超过阈值上报事件的一个示例。
又一种实现方法中，在5G应用场景中，该策略建立响应消息中包括SmPolicyDecision。该SmPolicyDecision中包含的部分内容如表3所示。
表3
其中，policyCtrlReqTriggers是已经存在的属性，policyCtrlReqTriggers的取值用PolicyControlRequestTrigger表示。本申请实施例新增policyCtrlReqTriggers的取值范围，比如新增policyCtrlReqTriggers的取值为TETHERING_EXCEED_NUM_REPORT。该TETHERING_EXCEED_NUM_REPORT是热点接入超过阈值上报事件的一个示例。
步骤504，会话管理网元向用户面网元发送会话建立请求消息。
在4G中，用户面网元是PGW-U，会话管理网元(即PGW-C)通过PGW-C与PGW-U之间的Sx接口向PGW-U发送会话建立请求消息。
在5G中，用户面网元是UPF，会话管理网元(即SMF)通过SMF与UPF之间的N4接口向UPF发送会话建立请求消息。
该5G中，该会话建立请求消息可以是N4 Session Establish Request消息。
该会话建立请求消息中包括热点接入超过阈值上报事件。
一种实现方法中，该会话建立请求消息中包括URR，该URR中包括Extended Reporting Triggers。该Extended Reporting Triggers中包括热点接入超过阈值上报事件。
步骤505，用户面网元根据热点接入超过阈值上报事件，启动热点接入检测。
其中，用户面网元检测通过热点分享技术接入到终端设备的设备的数量的实现方法，可以参考上述图2(a)的实施例中的相关描述，不再赘述。
步骤506，用户面网元向会话管理网元发送会话建立响应消息。
该5G中，该会话建立响应消息可以是N4 Session Establish Response消息。
步骤507，用户面网元向会话管理网元发送会话报告请求消息。
该5G中，该会话报告请求消息可以是N4 Session Reporting Request消息。
其中，热点接入阈值是预配置在用户面网元上的。或者用户面网元根据终端设备的业务套餐确定热点接入阈值。
具体的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值，则用户面网元向会话管理网元发送会话报告请求消息，该会话报告请求消息中包括热点接入超过阈值事件，该热点接入超过阈值事件表示通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值。
其中，该热点接入超过阈值事件是上述图2(a)的实施例中的第一事件的一个具体示例。
示例性地，该会话报告请求消息中包括ExtendedUsage Report Triggers，该ExtendedUsage Report Triggers中可以包含热点接入超过阈值事件。
步骤508，会话管理网元向策略控制网元发送策略更新请求消息。
在5G中，该策略更新请求消息可以是Npcf_SMPolicyControl_Update_Request消息。
该策略更新请求消息中包括热点接入超过阈值事件。
步骤509，策略控制网元确定针对终端设备的计费规则1和/或控制策略规则1。
策略控制网元收到的热点接入超过阈值事件，触发策略控制网元根据预配置策略或签约策略，确定针对终端设备的计费规则1和/或控制策略规则1。
步骤510，策略控制网元向会话管理网元发送策略更新响应消息。
在5G中，该策略更新响应消息可以是Npcf_SMPolicyControl_Update_Response消息。
该策略更新响应消息中包括针对终端设备的计费规则1和/或控制策略规则1。
步骤511，会话管理网元向用户面网元发送会话修改请求消息。
该5G中，该会话修改请求消息可以是N4 Session Modification Request消息。
该会话修改请求消息中包括针对终端设备的计费规则1和/或控制策略规则1。一种实现方法中，该会话修改请求消息中包括PDR，该PDR中包括针对终端设备的计费规则1和/或控制策略规则1。
步骤512，用户面网元根据针对终端设备的计费规则1对终端设备进行计费，和/或根 据针对终端设备的控制策略规则1对终端设备进行控制。
可选的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量，由超过热点接入阈值变为低于热点接入阈值，则还可以执行以下步骤513至步骤518。
步骤513，用户面网元向会话管理网元发送会话报告请求消息。
该5G中，该会话报告请求消息可以是N4 Session Reporting Request消息。
具体的，当用户面网元检测到通过热点分享技术接入到终端设备的设备的数量，由超过热点接入阈值变为低于热点接入阈值，则用户面网元向会话管理网元发送会话报告请求消息，该会话报告请求消息中包括热点接入低于阈值事件，该热点接入低于阈值事件表示通过热点分享技术接入到终端设备的设备的数量低于热点接入阈值。
其中，该热点接入低于阈值事件是上述图2(a)的实施例中的第二事件的一个具体示例。
示例性地，该会话报告请求消息中包括ExtendedUsage Report Triggers，该ExtendedUsage Report Triggers中可以包含热点接入低于阈值事件。
步骤514，会话管理网元向策略控制网元发送策略更新请求消息。
在5G中，该策略更新请求消息可以是Npcf_SMPolicyControl_Update_Request消息。
该策略更新请求消息中包括热点接入低于阈值事件。
步骤515，策略控制网元确定针对终端设备的计费规则2和/或控制策略规则2。
策略控制网元收到的热点接入低于阈值事件，触发策略控制网元根据预配置策略或签约策略，确定针对终端设备的计费规则2和/或控制策略规则2。
步骤516，策略控制网元向会话管理网元发送策略更新响应消息。
在5G中，该策略更新响应消息可以是Npcf_SMPolicyControl_Update_Response消息。
该策略更新响应消息中包括针对终端设备的计费规则2和/或控制策略规则2。
步骤517，会话管理网元向用户面网元发送会话修改请求消息。
该5G中，该会话修改请求消息可以是N4 Session Modification Request消息。
该会话修改请求消息中包括针对终端设备的计费规则2和/或控制策略规则2。一种实现方法中，该会话修改请求消息中包括PDR，该PDR中包括针对终端设备的计费规则2和/或控制策略规则2。
步骤518，用户面网元根据针对终端设备的计费规则2对终端设备进行计费，和/或根据针对终端设备的控制策略规则2对终端设备进行控制。
上述方案，用户面网元能够对通过热点分享技术接入到终端设备的设备的数量进行检测，并在检测到通过热点分享技术接入到终端设备的设备的数量超过热点接入阈值时，上报热点接入超过阈值事件，触发策略控制网元确定相应的计费规则和/或控制策略规则。以及用户面网元还可以在检测到通过热点分享技术接入到终端设备的设备的数量低于热点接入阈值时，上报热点接入低于阈值事件，触发策略控制网元确定相应的计费规则和/或控制策略规则。因此该方案能够实现根据对终端设备的精确计费和有效控制。
需要说明的是，上述步骤503和步骤504可以理解是上述图2(a)的实施例中的步骤201a的一种具体实现，上述步骤507和步骤508可以理解是上述图2(a)的实施例中的步骤202a的一种具体实现，上述步骤510和步骤511可以理解是上述图2(a)的实施例中的步骤203a和步骤204a的一种具体实现，上述步骤513和步骤514可以理解是上述图2(a)的实施例中的步骤205a的一种具体实现，上述步骤516和步骤517可以理解是上述图2(a)的实施例中的步骤206a和步骤207a的一种具体实现，其具体实现可以参考图2(a)的实施例中的相关 描述，不再赘述。
可以理解的是，为了实现上述实施例中功能，用户面网元或策略控制网元包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图6和图7为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中用户面网元或策略控制网元的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是用户面网元或策略控制网元，也可以是应用于策略控制网元的模块(如芯片)或应用于用户面网元的模块(如芯片)。
图6所示的通信装置600包括处理单元610和收发单元620。通信装置600用于实现上述方法实施例中用户面网元或策略控制网元的功能。
当该通信装置600用于实现上述图2(a)、图3或图5实施例中的用户面网元的功能，收发单元620，用于接收来自策略控制网元的指示信息，该指示信息指示，当第一事件发生，则向该策略控制网元发送该第一事件，该第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；当该第一事件发生，向该策略控制网元发送该第一事件。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的该热点接入阈值；或者，该指示信息包括该热点接入阈值。
一种可能的实现方法中，处理单元610，用于根据该终端设备的业务套餐，确定该热点接入阈值；或者，处理单元610，用于根据该用户面网元中的配置信息，确定该热点接入阈值。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的第一计费规则，该第一计费规则是根据该第一事件确定的；处理单元610，用于根据该第一计费规则，对该终端设备进行计费。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的第一控制策略规则，该第一控制策略规则是根据该第一事件确定的；处理单元610，用于根据该第一控制策略规则，对该终端设备进行控制。
一种可能的实现方法中，收发单元620，用于当发生第二事件，向该策略控制网元发送该第二事件，该第二事件表示通过热点分享技术接入到该终端设备的设备的数量小于或等于该热点接入阈值。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的第二计费规则，该第二计费规则是根据该第二事件确定的；处理单元610，用于根据该第二计费规则，对该终端设备进行计费。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的第二控制策略规则，该第二控制策略规则是根据该第二事件确定的；处理单元610，用于根据该第二控制策略规则，对该终端设备进行控制。
一种可能的实现方法中，收发单元620，用于接收来自该终端设备的多个数据包，该多个数据包中的每个数据包中包含时间戳；处理单元610，用于根据该多个数据包的每个 数据包中的时间戳，确定该多个数据包对应的时钟源的基准值；根据该多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，处理单元610，用于根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到该终端设备的设备的数量，该心跳消息来源于该终端设备或通过热点分享技术接入到该终端设备的设备。
一种可能的实现方法中，处理单元610，用于获取多个数据包对应的网络流量特征参数；根据该网络流量特征参数，确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，处理单元610，用于获取多个HTTP请求消息，该HTTP请求消息包括设备参数；根据该多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到该终端设备的设备的数量。
当该通信装置600用于实现上述图2(a)、图3或图5实施例中的策略控制网元的功能，收发单元620，用于向用户面网元发送指示信息，该指示信息指示，当第一事件发生，则向该策略控制网元发送该第一事件，该第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；当该第一事件发生，接收来自该用户面网元的该第一事件。
一种可能的实现方法中，收发单元620，用于向该用户面网元发送该热点接入阈值；或者，该指示信息包括该热点接入阈值。
一种可能的实现方法中，处理单元610，用于根据该第一事件，确定第一计费规则；收发单元620，用于向该用户面网元发送该第一计费规则。
一种可能的实现方法中，处理单元610，用于根据该第一事件，确定第一控制策略规则；收发单元620，用于向该用户面网元发送该第一控制策略规则。
一种可能的实现方法中，收发单元620，用于接收来自该用户面网元的第二事件，该第二事件表示通过热点分享技术接入到该终端设备的设备的数量小于或等于该热点接入阈值。
一种可能的实现方法中，处理单元610，用于根据该第二事件，确定第二计费规则；收发单元620，用于向该用户面网元发送该第二计费规则。
一种可能的实现方法中，处理单元610，用于根据该第二事件，确定第二控制策略规则；收发单元620，用于向该用户面网元发送该第二控制策略规则。
当该通信装置600用于实现上述图2(b)或图4实施例中的用户面网元的功能，收发单元620，用于接收来自策略控制网元指示信息，该指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向该策略控制网元发送变化后的设备的数量；当通过热点分享技术接入到该终端设备的设备的数量从第一数量变为第二数量，向该策略控制网元发送该第二数量。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的计费规则，该计费规则是根据该第二数量确定的；处理单元610，用于根据该计费规则，对该终端设备进行计费。
一种可能的实现方法中，收发单元620，用于接收来自该策略控制网元的控制策略规则，该控制策略规则是根据该第二数量确定的；处理单元610，用于根据该控制策略规则，对该终端设备进行控制。
一种可能的实现方法中，收发单元620，用于接收来自该终端设备的多个数据包，该 多个数据包中的每个数据包中包含时间戳；处理单元610，用于根据该多个数据包的每个数据包中的时间戳，确定该多个数据包对应的时钟源的基准值；根据该多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，处理单元610，用于根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到该终端设备的设备的数量，该心跳消息来源于该终端设备或通过热点分享技术接入到该终端设备的设备。
一种可能的实现方法中，处理单元610，用于获取多个数据包对应的网络流量特征参数；根据该网络流量特征参数，确定通过热点分享技术接入到该终端设备的设备的数量。
一种可能的实现方法中，处理单元610，用于获取多个HTTP请求消息，该HTTP请求消息包括设备参数；根据该多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到该终端设备的设备的数量。
当该通信装置600用于实现上述图2(b)或图4实施例中的策略控制网元的功能，收发单元620，用于向用户面网元发送指示信息，该指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向该策略控制网元发送变化后的设备的数量；当通过热点分享技术接入到该终端设备的设备的数量从第一数量变为第二数量，接收来自该用户面网元的该第二数量。
一种可能的实现方法中，处理单元610，用于根据该第二数量，确定计费规则；收发单元620，用于向该用户面网元发送该计费规则。
一种可能的实现方法中，处理单元610，用于根据该第二数量，确定控制策略规则；收发单元620，用于向该用户面网元发送该控制策略规则。
有关上述处理单元610和收发单元620更详细的描述可以直接参考上述方法实施例中相关描述直接得到，这里不加赘述。
图7所示的通信装置700包括处理器710和接口电路720。处理器710和接口电路720之间相互耦合。可以理解的是，接口电路720可以为收发器或输入输出接口。可选的，通信装置700还可以包括存储器730，用于存储处理器710执行的指令或存储处理器710运行指令所需要的输入数据或存储处理器710运行指令后产生的数据。
当通信装置700用于实现上述方法实施例时，处理器710用于实现上述处理单元610的功能，接口电路720用于实现上述收发单元620的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也不表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是 单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(erasable programmable read-only memory，EPROM)、寄存器、硬盘、可移动磁盘本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通 用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (30)

  1. 一种热点设备的管理方法，其特征在于，包括：
    用户面网元接收来自策略控制网元的指示信息，所述指示信息指示，当第一事件发生，则向所述策略控制网元发送所述第一事件，所述第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；
    当所述第一事件发生，所述用户面网元向所述策略控制网元发送所述第一事件。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的所述热点接入阈值；或者，
    所述指示信息包括所述热点接入阈值。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述用户面网元根据所述终端设备的业务套餐，确定所述热点接入阈值；或者，
    所述用户面网元根据所述用户面网元中的配置信息，确定所述热点接入阈值。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的第一计费规则，所述第一计费规则是根据所述第一事件确定的；
    所述用户面网元根据所述第一计费规则，对所述终端设备进行计费。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的第一控制策略规则，所述第一控制策略规则是根据所述第一事件确定的；
    所述用户面网元根据所述第一控制策略规则，对所述终端设备进行控制。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    当发生第二事件，所述用户面网元向所述策略控制网元发送所述第二事件，所述第二事件表示通过热点分享技术接入到所述终端设备的设备的数量小于或等于所述热点接入阈值。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的第二计费规则，所述第二计费规则是根据所述第二事件确定的；
    所述用户面网元根据所述第二计费规则，对所述终端设备进行计费。
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的第二控制策略规则，所述第二控制策略规则是根据所述第二事件确定的；
    所述用户面网元根据所述第二控制策略规则，对所述终端设备进行控制。
  9. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述终端设备的多个数据包，所述多个数据包中的每个数据包中包含时间戳；
    所述用户面网元根据所述多个数据包的每个数据包中的时间戳，确定所述多个数据包对应的时钟源的基准值；
    所述用户面网元根据所述多个数据包对应的时钟源的基准值，确定通过热点分享技术接入到所述终端设备的设备的数量。
  10. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元根据在一个或多个周期内检测到的心跳消息的数量和/或类型，确定通过热点分享技术接入到所述终端设备的设备的数量，所述心跳消息来源于所述终端设备或通过热点分享技术接入到所述终端设备的设备。
  11. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元获取多个数据包对应的网络流量特征参数；
    所述用户面网元根据所述网络流量特征参数，确定通过热点分享技术接入到所述终端设备的设备的数量。
  12. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元获取多个超文本传输协议HTTP请求消息，所述HTTP请求消息包括设备参数；
    所述用户面网元根据所述多个HTTP请求消息中的设备参数，确定通过热点分享技术接入到所述终端设备的设备的数量。
  13. 一种热点设备的管理方法，其特征在于，包括：
    策略控制网元向用户面网元发送指示信息，所述指示信息指示，当第一事件发生，则向所述策略控制网元发送所述第一事件，所述第一事件为通过热点分享技术接入到终端设备的设备的数量大于或等于热点接入阈值；
    当所述第一事件发生，所述策略控制网元接收来自所述用户面网元的所述第一事件。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元向所述用户面网元发送所述热点接入阈值；或者，
    所述指示信息包括所述热点接入阈值。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第一事件，确定第一计费规则，所述第一计费规则用于对所述终端设备进行计费；
    所述策略控制网元向所述用户面网元发送所述第一计费规则。
  16. 如权利要求13至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第一事件，确定第一控制策略规则，所述第一控制策略规则用于对所述终端设备进行控制；
    所述策略控制网元向所述用户面网元发送所述第一控制策略规则。
  17. 如权利要求13至16中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元接收来自所述用户面网元的第二事件，所述第二事件表示通过热点分享技术接入到所述终端设备的设备的数量小于或等于所述热点接入阈值。
  18. 如权利要求17所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第二事件，确定第二计费规则，所述第二计费规则用于对所述终端设备进行计费；
    所述策略控制网元向所述用户面网元发送所述第二计费规则。
  19. 如权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第二事件，确定第二控制策略规则，所述第二控制策略规则用于对所述终端设备进行控制；
    所述策略控制网元向所述用户面网元发送所述第二控制策略规则。
  20. 一种热点设备的管理方法，其特征在于，包括：
    用户面网元接收来自策略控制网元指示信息，所述指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向所述策略控制网元发送变化后的设备的数量；
    当通过热点分享技术接入到所述终端设备的设备的数量从第一数量变为第二数量，所述用户面网元向所述策略控制网元发送所述第二数量。
  21. 如权利要求20所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的计费规则，所述计费规则是根据所述第二数量确定的；
    所述用户面网元根据所述计费规则，对所述终端设备进行计费。
  22. 如权利要求20或21所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收来自所述策略控制网元的控制策略规则，所述控制策略规则是根据所述第二数量确定的；
    所述用户面网元根据所述控制策略规则，对所述终端设备进行控制。
  23. 一种热点设备的管理方法，其特征在于，包括：
    策略控制网元向用户面网元发送指示信息，所述指示信息指示，当通过热点分享技术接入到终端设备的设备的数量发生变化，则向所述策略控制网元发送变化后的设备的数量；
    当通过热点分享技术接入到所述终端设备的设备的数量从第一数量变为第二数量，所述策略控制网元接收来自所述用户面网元的所述第二数量。
  24. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第二数量，确定计费规则，所述计费规则用于对所述终端设备进行计费；
    所述策略控制网元向所述用户面网元发送所述计费规则。
  25. 如权利要求23或24所述的方法，其特征在于，所述方法还包括：
    所述策略控制网元根据所述第二数量，确定控制策略规则，所述控制策略规则用于对所述终端设备进行控制；
    所述策略控制网元向所述用户面网元发送所述控制策略规则。
  26. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至12中任一项所述的方法，或实现如权利要求13至19中任一项所述的方法，或实现如权利要求20至22中任一项所述的方法，或实现如权利要求23至25中任一项所述的方法。
  27. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被通信装置执行时，实现如权利要求1至12中任一项所述的方法，或实现如权利要求13至19中任一项所述的方法，或实现如权利要求20至22中任一项所述的方法，或实现如权利要求23至25中任一项所述的方法。
  28. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至12中任一项所述的方法，或实现如权利要求13至19中任一项所述的方法，或实现如权利要求20至22中任一 项所述的方法，或实现如权利要求23至25中任一项所述的方法。
  29. 一种通信系统，其特征在于，包括用于执行如权利要求1至12中任一项所述方法的用户面网元，和用于执行如权利要求13至19中任一项所述方法的策略控制网元。
  30. 一种通信系统，其特征在于，包括用于执行如权利要求20至22中任一项所述方法的用户面网元，和用于执行如权利要求23至25中任一项所述方法的策略控制网元。
PCT/CN2023/096796 2022-07-25 2023-05-29 一种热点设备的管理方法、通信装置及通信系统 WO2024021833A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210876527.5 2022-07-25
CN202210876527.5A CN117499877A (zh) 2022-07-25 2022-07-25 一种热点设备的管理方法、通信装置及通信系统

Publications (1)

Publication Number Publication Date
WO2024021833A1 true WO2024021833A1 (zh) 2024-02-01

Family

ID=89674986

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/096796 WO2024021833A1 (zh) 2022-07-25 2023-05-29 一种热点设备的管理方法、通信装置及通信系统

Country Status (2)

Country Link
CN (1) CN117499877A (zh)
WO (1) WO2024021833A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105578465A (zh) * 2015-12-18 2016-05-11 努比亚技术有限公司 分享移动终端的便携式热点接入管理方法、装置及移动终端
WO2016107177A1 (zh) * 2014-12-30 2016-07-07 华为技术有限公司 一种计费方法、装置及系统
CN112954669A (zh) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 共享终端业务控制方法、装置、网元及存储介质
WO2022008089A1 (en) * 2020-07-08 2022-01-13 Telefonaktiebolaget Lm Ericsson (Publ) User equipment tethering policy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016107177A1 (zh) * 2014-12-30 2016-07-07 华为技术有限公司 一种计费方法、装置及系统
CN105578465A (zh) * 2015-12-18 2016-05-11 努比亚技术有限公司 分享移动终端的便携式热点接入管理方法、装置及移动终端
CN112954669A (zh) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 共享终端业务控制方法、装置、网元及存储介质
WO2022008089A1 (en) * 2020-07-08 2022-01-13 Telefonaktiebolaget Lm Ericsson (Publ) User equipment tethering policy

Also Published As

Publication number Publication date
CN117499877A (zh) 2024-02-02

Similar Documents

Publication Publication Date Title
WO2021243618A1 (zh) 一种资源调度的方法、装置、通信设备及存储介质
US10952053B2 (en) System and method for machine to machine subscriber information and retrieval protection
EP3767890A1 (en) Method and apparatus for monitoring service quality
JP2020099101A (ja) ３ｇｐｐネットワークにおけるスモールデータ使用有効化
WO2017193427A1 (zh) 分组交换业务识别方法及终端
KR20200139771A (ko) 5g 네트워크에서의 로컬 영역 데이터 네트워크(ladn)에 대한 접속들을 관리하는 방법들
EP4138439A1 (en) Communication method, apparatus, and system
US10509682B2 (en) De-allocation elasticity application system
JP2021532641A (ja) サービス品質監視方法およびシステムならびにデバイス
US20220329994A1 (en) Network Information Delivery towards Application at Device Side
WO2017076126A1 (zh) 一种会话切换的方法、设备及系统
US11784877B2 (en) Systems and methods to control operation of virtualized networks
US11330050B2 (en) Edge sharing orchestration system
KR102476193B1 (ko) 레이트 제어 방법, 장치, 및 시스템
KR20220019290A (ko) 애플리케이션 기능과 코어 네트워크 사이에서 협상된 백그라운드 데이터 전송 정책을 업데이트하는 방법, 정책 제어 기능 및 애플리케이션 기능
TW202312761A (zh) 5g網路中之封包酬載資料之選擇性壓縮
WO2024021833A1 (zh) 一种热点设备的管理方法、通信装置及通信系统
US11736623B2 (en) Systems and methods for granular charging in mobile wireless networks
US9913163B2 (en) UE control of downlink data
WO2023030077A1 (zh) 一种通信方法、通信装置及通信系统
WO2023109581A1 (zh) 检测方法、通信装置及通信系统
EP4391629A1 (en) Communication method and related device
WO2023213226A1 (zh) 一种授权的方法和装置
WO2023155111A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2024130482A1 (en) Method and apparatus for managing data channel for terminal device

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: 23845047

Country of ref document: EP

Kind code of ref document: A1