Hotspot device management method, communication device, and communication system

Abstract

[0009] Embodiments of this application provide a hotspot device management method, a communication device, and a communication system. In the method, a policy control network element instructs a user plane network element to detect the number of devices accessing a terminal device using a hotspot sharing technology, and notify the policy control network element when it detects that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than a hotspot access threshold. Thus, the policy control network element knows that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, and thereby determines a charging method or control method for the terminal device, appropriately charges, and precisely controls the terminal device.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202210876527.5, entitled "HOTSPOT DEVICE MANAGEMENT METHOD, COMMUNICATION APPARATUS, AND COMMUNICATION SYSTEM," filed with the State Intellectual Property Office of China on July 25, 2022, which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD Embodiments of this application relate to the field of communication technology, and in particular to a hotspot device management method, a communication apparatus, and a communication system. [Background technology]

[0003] Currently, terminal devices, such as smartphones, have a hotspot sharing function. When the terminal device enables hotspot sharing, other devices, such as laptops, can access the terminal device through a connection method such as wireless fidelity (Wi-Fi), Bluetooth, or a Universal Serial Bus (USB) physical connection to achieve Internet access.

[0004] However, there is a need to solve how to effectively manage terminal devices with hotspot sharing capabilities. Summary of the Invention

[0005] The embodiments of this application provide a hotspot device management method, a communication apparatus, and a communication system for effectively managing terminal devices with hotspot sharing functions.

[0006] According to a first aspect, an embodiment of the present application provides a hotspot device management method. The method may be performed by a user plane network element or a module (e.g., a chip) used in the user plane network element. For example, the user plane network element performs the method. The method includes: the user plane network element receives indication information from a policy control network element. The indication information indicates to send a first event to the policy control network element when a first event occurs. The first event is that the number of devices accessing the terminal device using a hotspot sharing technology is equal to or greater than a hotspot access threshold. When the first event occurs, the user plane network element sends the first event to the policy control network element.

[0007] In the above solution, the policy control network element instructs the user plane network element to detect the number of devices accessing the terminal device using the hotspot sharing technology, and notify the policy control network element when it detects that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold. Thus, the policy control network element knows that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, and thereby determines a charging method or control method for the terminal device, appropriately charges, and precisely controls the terminal device.

[0008] In a possible implementation method, 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.

[0009] In the above solution, the policy control network element configures the hotspot access threshold for the user plane network element, so that the hotspot access threshold can be configured accurately.

[0010] In a possible implementation method, the user plane network element determines the hotspot access threshold based on the service package of the terminal device, or the user plane network element determines the hotspot access threshold based on configuration information in the user plane network element.

[0011] In the above solution, the user plane network element determines the hotspot access threshold, and the policy control network element does not need to configure the hotspot access threshold for the user plane network element, thereby reducing signaling overhead.

[0012] In a possible implementation, a user plane network element receives a first charging rule from a policy control network element, the first charging rule is determined based on a first event, and the user plane network element charges the terminal device according to the first charging rule.

[0013] In the above solution, the charging rules are effectively configured to charge the terminal device appropriately.

[0014] In a possible implementation, a user plane network element receives a first control policy rule from a policy control network element, the first control policy rule being determined based on a first event, and the user plane network element controls the terminal device according to the first control policy rule.

[0015] In the above solution, the control policy rules are effectively configured to appropriately control the terminal devices.

[0016] In a possible implementation method, when a second event occurs, the user plane network element sends a second event to the policy control network element, where the second event indicates that the number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to a hotspot access threshold.

[0017] In a possible implementation, the user plane network element receives a second charging rule from the policy control network element, the second charging rule is determined based on the second event, and the user plane network element charges the terminal device according to the second charging rule.

[0018] In other words, when the number of devices accessing the terminal device using the hotspot sharing technology changes, the charging rule is adaptively modified. In the above solution, the charging rule is changed based on the actual situation so that the terminal device can be appropriately charged. The above description is applicable to the description in other aspects, and the details will not be described again.

[0019] In a possible implementation, the user plane network element receives a second control policy rule from the policy control network element, the second control policy rule being determined based on a second event, and the user plane network element controls the terminal device according to the second control policy rule.

[0020] In other words, when the number of devices accessing the terminal device using the hotspot sharing technology changes, the control policy rule is adaptively modified. In the above solution, the control policy rule is modified based on the actual situation to appropriately control the terminal device. The above description is applicable to the description in other aspects, and the details will not be described again.

[0021] In a possible implementation method, a user plane network element receives a plurality of data packets from a terminal device, each of the plurality of data packets including a timestamp, the user plane network element determines a clock source reference value corresponding to the plurality of data packets based on the timestamp in each of the plurality of data packets, and the user plane network element determines a number of devices accessing the terminal device using a hotspot sharing technique based on the clock source reference values ​​corresponding to the plurality of data packets.

[0022] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0023] In a possible implementation, the user plane network element determines the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, where the heartbeat messages are from the terminal device or devices accessing the terminal device using the hotspot sharing technology.

[0024] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0025] In a possible implementation method, a user plane network element obtains network traffic characteristic parameters corresponding to an internet protocol (IP) address in a network, and determines, based on the network traffic characteristic parameters, the number of devices that will access the terminal device using a hotspot sharing technology.

[0026] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0027] In a possible implementation method, a user plane network element receives a plurality of Hypertext Transfer Protocol (HTTP) request messages, the HTTP request messages including device parameters, and the user plane network element determines a number of devices to access the terminal device using a hotspot sharing technique based on the device parameters in the plurality of HTTP request messages.

[0028] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0029] According to a second aspect, an embodiment of the present application provides a hotspot device management method. The method may be performed by a policy control network element or a module (e.g., a chip) used in the policy control network element. For example, the policy control network element performs the method. The method includes: the policy control network element sending indication information to a user plane network element. The indication information indicates to send the first event to the policy control network element when a first event occurs. The first event is that the number of devices accessing the terminal device using a hotspot sharing technology is equal to or greater than a hotspot access threshold. When the first event occurs, the policy control network element receives the first event from the user plane network element.

[0030] In the above solution, the policy control network element instructs the user plane network element to detect the number of devices accessing the terminal device using the hotspot sharing technology, and notify the policy control network element when it detects that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold. Thus, the policy control network element knows that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, and thereby determines a charging method or control method for the terminal device, appropriately charges, and precisely controls the terminal device.

[0031] In a possible implementation method, 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.

[0032] In the above solution, the policy control network element configures the hotspot access threshold for the user plane network element, so that the hotspot access threshold can be configured accurately.

[0033] In one possible implementation, the policy control network element determines a first charging rule based on the first event, the first charging rule is utilized to charge the terminal device, and the policy control network element transmits the first charging rule to the user plane network element.

[0034] In the above solution, the charging rules are effectively configured to charge the terminal device appropriately.

[0035] In one possible implementation, the policy control network element determines a first control policy rule based on a first event, the first control policy rule is utilized to control the terminal device, and the policy control network element transmits the first control policy rule to a user plane network element.

[0036] In the above solution, the control policy rules are effectively configured to appropriately control the terminal devices.

[0037] In a possible implementation, the policy control network element receives a second event from the user plane network element, the second event indicating that a number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to a hotspot access threshold.

[0038] In a possible implementation, the policy control network element determines a second charging rule based on the second event, the second charging rule is utilized to charge the terminal device, and the policy control network element transmits the second charging rule to the user plane network element.

[0039] In a possible implementation, the policy control network element determines a second control policy rule based on the second event, the second control policy rule is utilized to control the terminal device, and the policy control network element transmits the second control policy rule to the user plane network element.

[0040] According to a third aspect, an embodiment of the present application provides a hotspot device management method. The method may be performed by a user plane network element or a module (e.g., a chip) used in the user plane network element. For example, the user plane network element performs the method. The method includes: the user plane network element receives indication information from a policy control network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes, the indication information indicates to send the changed number of devices to the policy control network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, the user plane network element sends the second number to the policy control network element.

[0041] In the above solution, the policy control network element detects the number of devices accessing the terminal device using the hotspot sharing technology, and after detecting that the number of devices accessing the terminal device using the hotspot sharing technology changes, indicates the user plane network element to send the changed number of devices to the policy control network element, so that the policy control network element determines a charging method or control method for the terminal device based on the changed number of devices, and charges appropriately and controls the terminal device accurately.

[0042] In a possible implementation method, the user plane network element receives a charging rule from the policy control network element, the charging rule is determined based on the second number, and the user plane network element charges the terminal device according to the charging rule.

[0043] In the above solution, the charging rules are effectively configured to charge the terminal device appropriately.

[0044] In a possible implementation method, the user plane network element receives a control policy rule from the policy control network element, the control policy rule is determined based on the second number, and the user plane network element controls the terminal device according to the control policy rule.

[0045] In the above solution, the control policy rules are effectively configured to appropriately control the terminal devices.

[0046] In a possible implementation method, a user plane network element receives a plurality of data packets from a terminal device, each of the plurality of data packets including a timestamp, the user plane network element determines a clock source reference value corresponding to the plurality of data packets based on the timestamp in each of the plurality of data packets, and the user plane network element determines a number of devices accessing the terminal device using a hotspot sharing technique based on the clock source reference values ​​corresponding to the plurality of data packets.

[0047] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0048] In a possible implementation, the user plane network element determines the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, where the heartbeat messages are from the terminal device or devices accessing the terminal device using the hotspot sharing technology.

[0049] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0050] In a possible implementation method, a user plane network element acquires network traffic characteristic parameters corresponding to a plurality of data packets, and based on the network traffic characteristic parameters, the user plane network element determines a number of devices that will access the terminal device using the hotspot sharing technology.

[0051] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0052] In a possible implementation method, a user plane network element receives a plurality of HTTP request messages, the HTTP request messages including device parameters, and the user plane network element determines the number of devices that will access the terminal device using the hotspot sharing technology based on the device parameters in the plurality of HTTP request messages.

[0053] In the above solution, the number of devices accessing the terminal device can be accurately determined using the hotspot sharing technology.

[0054] According to a fourth aspect, an embodiment of the present application provides a hotspot device management method. The method may be performed by a policy control network element or a module (e.g., a chip) used in the policy control network element. For example, the policy control network element performs the method. The method includes: the policy control network element sending indication information to a user plane network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes, the indication information indicates that the changed number of devices should be sent to the policy control network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, the policy control network element receives the second number from the user plane network element.

[0055] In the above solution, the policy control network element detects the number of devices accessing the terminal device using the hotspot sharing technology, and after detecting that the number of devices accessing the terminal device using the hotspot sharing technology changes, indicates the changed number of devices to the user plane network element to send to the policy control network element, so that the policy control network element can determine a charging method or control method for the terminal device based on the changed number of devices, which helps to appropriately charge and precisely control the terminal device.

[0056] In a possible implementation manner, the policy control network element determines a charging rule based on the second number, and sends the charging rule to the user plane network element.

[0057] In the above solution, the charging rules are effectively configured to charge the terminal device appropriately.

[0058] In a possible implementation, the policy control network element determines the control policy rule based on the second number, and sends the control policy rule to the user plane network element.

[0059] In the above solution, the control policy rules are effectively configured to appropriately control the terminal devices.

[0060] According to a fifth aspect, an embodiment of the present application provides a communications device. The device may be a user plane network element or a module (e.g., a chip) used in a user plane network element. The device has a function for performing any of the implementation methods of the first aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0061] According to a sixth aspect, an embodiment of the present application provides a communications device. The device may be a policy-controlled network element or a module (e.g., a chip) used in a policy-controlled network element. The device has a function for performing any of the implementation methods of the second aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0062] According to a seventh aspect, an embodiment of the present application provides a communications device. The device may be a user plane network element or a module (e.g., a chip) used in a user plane network element. The device has a function for performing any of the implementation methods of the third aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0063] According to an eighth aspect, an embodiment of the present application provides a communication device. The device may be a policy control network element or a module (e.g., a chip) used in a policy control network element. The device has a function for performing any of the implementation methods of the fourth aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0064] According to a ninth aspect, an embodiment of the present application provides a communication device including a processor coupled to a memory. The processor is configured to invoke a program stored in the memory to perform an implementation method of any of the first to fourth aspects. The memory may be located internal or external to the device. Additionally, there may be one or more processors.

[0065] According to a tenth aspect, an embodiment of the present application provides a communication device including a processor and a memory. The memory is configured to store computer instructions. When the device operates, the processor executes the computer instructions stored in the memory to enable the device to perform an implementation method of any of the first to fourth aspects.

[0066] According to an eleventh aspect, an embodiment of the present application provides a communication device including a unit or means configured to perform the steps of the implementation method of any of the first to fourth aspects.

[0067] According to a twelfth aspect, an embodiment of the present application provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to execute the implementation method of any one of the first to fourth aspects. There may be one or more processors.

[0068] According to a thirteenth aspect, an embodiment of the present application further provides a computer-readable storage medium that stores instructions that, when executed on a communication device, cause the implementation method of any one of the first to fourth aspects to be performed.

[0069] According to a fourteenth aspect, an embodiment of the present application further provides a computer program product. The computer program product includes a computer program or instructions. When the computer program or instructions are executed by a communication device, the method according to any one of the first to fourth aspects is performed.

[0070] According to a fifteenth aspect, an embodiment of the present application further provides a chip system including a processor configured to execute the implementation method of any one of the first to fourth aspects.

[0071] According to a sixteenth aspect, an embodiment of the present application further provides a communication system including: a user plane network element configured to perform any of the implementation methods of the first aspect; and a policy control network element configured to perform any of the implementation methods of the second aspect.

[0072] According to a seventeenth aspect, an embodiment of the present application further provides a communication system including: a user plane network element configured to perform any of the implementation methods of the third aspect; and a policy control network element configured to perform any of the implementation methods of the fourth aspect. [Brief explanation of the drawings]

[0073] [Figure 1] 1 is a diagram of the architecture of a 5G network based on a service-oriented architecture. [Figure 2(a)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 2(b)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 2(c)] FIG. 10 is an exemplary diagram of determining the number of devices accessing a terminal device using hotspot sharing technology. [Figure 3(a)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 3(b)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 4] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 5(a)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 5(b)] 1 is a schematic flowchart of a hotspot device management method according to an embodiment of the present application; [Figure 6] 1 is a diagram of a communication device according to an embodiment of the present application; [Figure 7] 1 is a diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0074] Figure 1 is a diagram of a fifth generation (5G) network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1 may include a terminal device, an access network, a core network, and a data network (DN). The terminal device accesses the data network through the access network and the core network.

[0075] The terminal device may be a user equipment (UE), a mobile station, a mobile terminal, or the like. FIG. 1 is described using an example in which the terminal device is a UE. The terminal device may be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, and smart city. The terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a wearable device, a vehicle, an urban air transportation vehicle (such as an unmanned aerial vehicle or a helicopter), a ship, a robot, a robotic arm, a smart home device, or the like.

[0076] An access network is used to implement access-related functions and may provide network access functions for authorized users within a specific area. It may also determine transmission links of different qualities to transmit user data based on user levels and service requirements. The access network transfers control signals and user data between terminal devices and a core network. The access network may include access network devices. The access network devices may provide access for terminal devices and may include radio access network (RAN) devices and wired access network devices. Figure 1 illustrates an example in which the access network device is a RAN. RAN devices are primarily responsible for functions such as radio resource management, quality of service (QoS) management, and data compression and encryption on the air interface side. RAN devices may include various types of base stations, such as macro base stations, micro base stations (sometimes called small cells), relay stations, access points, and balloon stations. In systems using different radio access technologies, the names of devices having base station functions may differ. For example, in a 5G system, the device is referred to as a RAN or next-generation Node base station (gNB), and in a long term evolution (LTE) system, the device is referred to as an evolved NodeB (eNB or eNodeB).

[0077] The access network device and the terminal device may be in a fixed position or may be mobile. The access network device and the terminal device may be located on the ground, including indoors or outdoors, may be handheld or mounted on a vehicle, may be located on the water surface, or may be located on an airplane, balloon, or satellite in the air. The application scenarios of the access network device and the terminal device are not limited in the embodiments of this application.

[0078] The core network is responsible for maintaining subscription data for the mobile network and provides 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: an application function (AF) network element, a unified data management (UDM) network element, a policy control function (PCF) network element, a session management function (SMF) network element, an access and mobility management function (AMF) network element, and a user plane function (UPF) network element. For ease of description, for example, the unified data management network element will be referred to as UDM for short hereinafter, and similarly for the other network elements.

[0079] The AMF is mainly responsible for mobility management in a mobile network, such as user location update, user registration to the network, and user switching.

[0080] The SMF is mainly responsible for session management in a mobile network, such as session establishment, modification, and release. Specific functions include, for example, allocating an IP address to a user or selecting a UPF that provides packet forwarding functionality.

[0081] The UPF is responsible for forwarding and receiving user data, and may receive user data from a data network and transmit the user data to a terminal device via an access network device. Alternatively, the UPF may receive user data from a terminal device via an access network device and forward the user data to a data network.

[0082] The UDM performs functions such as subscription data management and user access authentication.

[0083] The AF forwards application-side requirements on the network side, such as QoS requirements or user status event subscriptions. The AF may be a third-party functional entity or an operator-deployed application service, such as an IP Multimedia Subsystem (IMS) voice call service.

[0084] The PCF is mainly responsible for providing a unified policy framework to control network behavior, providing policy rules for control layer network functions, and obtaining subscription information related to user policy decisions. The PCF may provide policies such as QoS policies and slice selection policies to the AMF or SMF.

[0085] Multiple services may be deployed on the DN, and the DN may provide services such as data services and / or voice services to terminal devices. For example, the DN may be a private network of a smart factory, and a sensor installed in a workplace of the smart factory may be a terminal device, and a control server for the sensor may be deployed within the DN, and the control server may provide services to the sensor. The sensor may communicate with the control server to obtain instructions from the control server and, based on the instructions, transmit collected sensor data to the control server, etc. In another example, the DN may be an internal office network of a company, and a mobile phone or computer of an employee of the company may be a terminal device, and the employee's mobile phone or computer may access information, data resources, etc. on the internal office network of the company.

[0086] In Figure 1, Namf, Npcf, Nsmf, Nudm, and Naf are service-oriented interfaces provided by AMF, PCF, SMF, UDM, and AF, respectively, and are configured to invoke corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers are as follows:

[0087] (1) N1: Represents an interface between the AMF and a terminal device and may be configured to transmit non-access stratum (NAS) signaling (e.g., including QoS rules from the AMF) to the terminal device, etc.

[0088] (2) N2: Represents the interface between the AMF and the RAN and can be configured to transmit radio bearer control information from the core network side to access network devices, etc.

[0089] (3) N3: represents the interface between the RAN and the UPF, and is mainly configured to transmit uplink and downlink user plane data between the access network device and the UPF.

[0090] (4) N4: Represents an interface between the SMF and the UPF and may be configured to transmit information between the control plane and the user plane, including delivery of forwarding rules, QoS rules, and traffic statistics rules from the control plane to the user plane, and reporting of user plane information.

[0091] (5) N6: represents the interface between the UPF and the DN, and is configured to carry uplink and downlink user data flows between the UPF and the DN.

[0092] It may be understood that the network element may be a network element in a hardware device, and the function may be a software function running on dedicated hardware or a virtualized function instantiated on a platform (e.g., a cloud platform). In possible implementation methods, the network element or the above-mentioned function may be implemented by one device, may be implemented by multiple devices in cooperation with each other, or may be implemented by one functional module in one device. This is not particularly limited in the embodiments of this application.

[0093] The network sharing technology is also referred to as a hotspot sharing technology. The application of this technology may enable devices such as laptops, desktop computers, tablets, or other intelligent terminals to access intelligent terminals with Internet access capabilities via connection methods such as wired or wireless (e.g., Wi-Fi, Bluetooth, or USB physical connection) and provide packet data services to devices other than intelligent terminals with Internet access capabilities. For example, the network sharing technology may be tethering, and an intelligent terminal providing the tethering function may be referred to as a tethering user.

[0094] With the widespread use of intelligent terminals with network sharing technology, a large number of non-subscribed devices, such as laptops and tablets, may use the network sharing technology of the intelligent terminals to access network traffic. Because operators cannot detect the terminal devices that use the network sharing technology to access the network, they cannot analyze and determine the actual situation of the devices that use network traffic, and therefore cannot provide better services to users.

[0095] 2(a) is a schematic flowchart of a hotspot device management method according to an embodiment of this application. The method includes the following steps:

[0096] Step 201a: The policy control network element sends indication information to the user plane network element.

[0097] In response, the user plane network element receives the indication information.

[0098] The policy control network element may send the indication information to the user plane network element via the session management network element.

[0099] When this embodiment of this application is applied to a 5G scenario, the policy control network element is a PCF network element, the session management network element is an SMF network element, and the user plane network element is a UPF network element.

[0100] When this embodiment of the application is applied to a 4G scenario, the policy control network element is a Policy and Charging Rules Function (PCRF) network element, the session management network element is a Packet Data Network Gateway-Control Plane (PGW-C) network element, and the user plane network element is a Packet Data Network Gateway-User Plane (PGW-U) network element.

[0101] Of course, this embodiment of the present application can be further applied to future communication scenarios, such as sixth generation (6G) communication scenarios, which are not limited in this application. The implementations of the policy control network element, the session management network element, and the user plane network element are described collectively here and will not be described in detail below.

[0102] The indication information indicates to send a first event to the policy control network element when a first event occurs, wherein the first event is that a number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than a hotspot access threshold, or the first event is that a number of devices accessing the terminal device using the hotspot sharing technology is greater than a hotspot access threshold.

[0103] Step 202a: When a first event occurs, the user plane network element sends the first event to the policy control network element.

[0104] In response, the policy control network element receives a first event.

[0105] After receiving the indication information, the user plane network element detects the number of devices accessing the terminal device using the hotspot sharing technology. When the user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology is greater than the hotspot access threshold, it indicates that a first event occurs. Therefore, the user plane network element sends the first event to the policy control network element, so that the policy control network element can know that the number of devices accessing the terminal device using the hotspot sharing technology is greater than or equal to the hotspot access threshold.

[0106] For example, assume that the hotspot access threshold is 5 and the indication information indicates to report to the policy control network element when the number of devices accessing terminal device 1 using the hotspot sharing technology is 5 or more. Thus, the user plane network element detects devices accessing terminal device 1 using the hotspot sharing technology. When detecting that the number of devices accessing terminal device 1 using the hotspot sharing technology is 5 or more, the user plane network element reports to the policy control network element that the number of devices accessing terminal device 1 using the hotspot sharing technology is 5 or more.

[0107] In one implementation method, before step 202a, 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 indication information may be sent in the same message or in different messages.

[0108] In another implementation, the indication information includes a hotspot access threshold.

[0109] In another implementation method, 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.

[0110] In another implementation method, the user plane network element determines the hotspot access threshold based on configuration information in the user plane network element.

[0111] In the above solution, the policy control network element instructs the user plane network element to detect the number of devices accessing the terminal device using the hotspot sharing technology, and notify the policy control network element when it detects that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold. Thus, the policy control network element knows that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, which helps the policy control network element determine a charging method or control method for the terminal device to appropriately charge and precisely control the terminal device.

[0112] In one implementation method, after step 202a, the following step 203a and / or step 204a may be further performed.

[0113] Step 203a: The policy control network element sends the first charging rule to the user plane network element.

[0114] In response, the user plane network element receives the first charging rule.

[0115] After receiving the first event, the policy control network element learns that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, and updates the charging rule to obtain a 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.

[0116] For example, compared with the charging rule before the update, the first charging rule increases the traffic unit price (or traffic charging rate), or updates the previously non-charging one and starts charging. The specific implementation method of the charging rule is not limited in this embodiment of this application. Therefore, in this method, the charging rule is effectively configured to appropriately charge the terminal device.

[0117] Step 204a: The policy control network element sends a first control policy rule to the user plane network element.

[0118] In response, the user plane network element receives a first control policy rule.

[0119] After receiving the first event, the policy control network element learns that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold, and updates the control policy rule to obtain a first control policy rule. 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.

[0120] For example, compared with the control policy rule before the update, the first control policy rule may limit the traffic bandwidth of the device or reduce the traffic network speed of the device, etc. The specific implementation method of the control policy rule is not limited in this embodiment of this application. In this method, the control policy rule is effectively configured to appropriately control the terminal device.

[0121] In one implementation method, after step 202a, the following step 205a may be further executed.

[0122] Step 205a: When a second event occurs, the user plane network element sends the second event to the policy control network element.

[0123] In response, the policy control network element receives a second event.

[0124] The second event indicates that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or less than the hotspot access threshold.

[0125] The second event may be understood to be an event different from the first event. Specifically, when the number of devices accessing the terminal device using the hotspot sharing technology changes, for example, when the number changes from greater than the hotspot access threshold to less than the hotspot access threshold, the user plane network element notifies the policy control network element of the change in number. In other words, the user plane network element may dynamically sense the change in number and notify the policy control network element of the change in number in real time to perform dynamic management on the terminal device.

[0126] In one implementation method, after step 205a, the following step 206a and / or step 207a may be further executed.

[0127] Step 206a: The policy control network element sends the second charging rule to the user plane network element.

[0128] In response, the user plane network element receives a second charging rule.

[0129] After receiving the second event, the policy control network element determines that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or less than the hotspot access threshold, and updates the charging rule to obtain a second charging rule. The policy control network element then 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.

[0130] For example, compared with the charging rule before the update, the second charging rule reduces the traffic unit price (or traffic charging rate), or updates what was previously charged to non-charging. The specific implementation method of the charging rule is not limited to this embodiment of this application. In this method, the charging rule is effectively configured to appropriately charge the terminal device.

[0131] Step 207a: The policy control network element sends the second control policy rule to the user plane network element.

[0132] In response, the user plane network element receives a second control policy rule.

[0133] After receiving the second event, the policy control network element determines that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or less than the hotspot access threshold, and updates the control policy rule to obtain a second control policy rule. The policy control network element then 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.

[0134] For example, compared with the control policy rule before the update, the first control policy rule increases the bandwidth traffic of the device, or increases the traffic network speed of the device, etc. The specific implementation method of the control policy rule is not limited in this embodiment of this application. In this method, the control policy rule is effectively configured to appropriately control the terminal device.

[0135] The following describes an implementation method for a user plane network element to detect the number of devices accessing a terminal device using a hotspot sharing technology. The following methods 1 to 4 are used merely as examples. The implementation method for a user plane network element to detect the number of devices accessing a terminal device using a hotspot sharing technology is not limited in this application.

[0136] Method 1: A user plane network element receives a plurality of data packets from a terminal device. Each of the plurality of data packets includes a timestamp. The user plane network element determines a clock source reference value corresponding to the plurality of data packets based on the timestamp in each of the plurality of data packets. The user plane network element determines a number of devices accessing the terminal device using a hotspot sharing technique based on the clock source reference values ​​corresponding to the plurality of data packets.

[0137] When the terminal device enables hotspot sharing and other devices access the terminal device using the hotspot sharing technology, the other devices transmit data packets through the terminal device. Therefore, the multiple data packets received from the terminal device by the user plane network element include both the data packets transmitted by the terminal device and the data packets transmitted by the other devices.

[0138] Both the terminal device and other devices accessing the terminal device using the hotspot sharing technology include a timestamp in the data packet when transmitting the data packet, and the timestamp is related to the clock source of the device generating the data packet. Therefore, the user plane network element may determine the reference value of the clock source corresponding to the data packet based on the timestamp in the acquired data packet. Because the reference value of the same clock source is the same, the user plane may determine the number of devices accessing the terminal device using the hotspot sharing technology based on the number of reference values ​​of different types of clock sources. The reference value of the clock source may be understood as the value of the clock source at a reference time point. The clock sources of different devices have different values ​​at the same time point, in other words, the reference values ​​of the clock sources of different devices are different.

[0139] For example, the user plane network element determines that there are five reference values ​​based on timestamps in multiple received data packets. Among the five reference values, one reference value is a reference value of a clock source of a terminal device that enables hotspot sharing, and the other four reference values ​​are reference values ​​of clock sources of other devices that access the terminal device using the hotspot sharing technology. Therefore, the user plane network element determines that the number of devices that access the terminal device using the hotspot sharing technology is four.

[0140] The following describes the method using an example. For example, UE1 is a device that enables hotspot sharing, and then device 1, device 2, and device 3 access UE1 using the hotspot enabled by UE1. The following describes how a user plane network element determines that the number of devices accessing UE1 using the hotspot sharing technology is 3.

[0141] When UE1 is powered on, its clock source generates an initial value (represented by initialTimestamp1), e.g., 1000. Then, over time, the value of the clock source increases by a fixed value (represented by numinbysec) every second. The value of numinbysec is 1000. For example, one second after UE1 is powered on, the clock source is updated to 2000, two seconds after UE1 is powered on, the clock source is updated to 3000, and so on. When generating a data packet, UE1 obtains the current value of its clock source and then uses that value as the timestamp carried in the data packet. For example, at time t1, the value of UE1's clock source is timestamp1, and UE1 includes timestamp1 in the data packet. Similarly, at time t2, the value of UE1's clock source is timestamp2, and UE1 includes timestamp2 in the data packet, and so on.

[0142] Similarly, when device 1 is powered on, the clock source of device 1 generates an initial value (represented by initialTimestamp2), e.g., 2000. Then, over time, the value of the clock source increases by a fixed value (represented by numinbysec) every second. The value of numinbysec is 1000. For example, the clock source is updated to 3000 one second after device 1 is powered on, the clock source is updated to 4000 two seconds after device 1 is powered on, and so on. When generating a data packet, device 1 obtains the current value of device 1's clock source and then uses that value as the timestamp carried in the data packet. For example, at time t3, the value of device 1's clock source is timestamp3, and device 1 includes timestamp3 in the data packet. Similarly, at time t4, the value of device 1's clock source is timestamp4, and device 1 includes timestamp4 in the data packet, and so on.

[0143] Similarly, device 2 and device 3 also include corresponding timestamps in their data packets.

[0144] Therefore, a data packet received by a user plane network element from UE1, device1, device2, or device3 includes a timestamp. The user plane network element may acquire timestamps in multiple data packets through sampling at different times, and perform fitting on the timestamps acquired through sampling at multiple times to obtain multiple straight lines with the same slope. The number of straight lines represents the total number of devices from which the multiple data packets are transmitted. It may also be understood that different devices represented by the multiple straight lines acquired through fitting have different initial values. Because the initial values ​​of different devices when the devices are powered on are random values, the number of initial values ​​may be considered to be the number of devices. Figure 2(c) is used as an example. The user plane network element separately acquires multiple data packets through sampling at time tx and time ty, acquires timestamps in the data packets, and then performs fitting on the timestamps acquired through sampling to obtain four straight lines. Data packets corresponding to the same straight line are from the same device. Therefore, the four straight lines indicate that the multiple used data packets are from four devices, which are UE1, device1, device2, and device3. Therefore, the user plane network element determines that the number of devices accessing UE1 using the hotspot sharing technology is 4-1=3.

[0145] Method 2: The user plane network element determines the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, where the heartbeat messages are from the terminal device or devices accessing the terminal device using the hotspot sharing technology.

[0146] An operating system (such as iOS, Android, or Windows) of a terminal device periodically sends a heartbeat message to an application server. The terminal device sends the heartbeat message to a user plane network element, which then forwards the heartbeat message to the application server. Thus, the user plane network element can detect the heartbeat message of the terminal device.

[0147] For other devices that access the terminal device using the hotspot sharing technology, the operating system of the device also periodically sends a heartbeat message to the application server. When the device sends a heartbeat message, the heartbeat message reaches the user plane network element via the terminal device, and the user plane network element then forwards the heartbeat message to the application server. Therefore, the user plane network element can detect the device's heartbeat message.

[0148] In one implementation method, when different types of heartbeat messages are sent by different devices, the user plane network element may determine the number of devices accessing the terminal device using the hotspot sharing technology based on the types of heartbeat messages detected in one or more periods. For example, terminal device 1 shares a hotspot, and then three devices, namely device 1, device 2, and device 3, all access terminal device 1 using the hotspot sharing technology. If the user plane network element can detect four types of heartbeat messages from terminal device 1 in one or more periods, the user plane network element determines that the number of devices accessing terminal device 1 using the hotspot sharing technology is 4-1=3.

[0149] In another implementation method, since devices with the same type of operating system installed have the same heartbeat message transmission period, the number of heartbeat messages in one period may be detected to determine the number of devices accessing terminal device 1 using the hotspot sharing technology. For example, a device with the Android operating system installed transmits heartbeat messages according to period T1, and a device with the Apple operating system installed transmits heartbeat messages according to period T2. In this case, the user plane network element may detect the number of heartbeat messages sent by Android devices in one period T1, e.g., K1, and the number of heartbeat messages sent by Apple devices in one period T2, e.g., K2. In this way, the user plane network element determines that the number of devices accessing terminal device 1 using the hotspot sharing technology is (K1 + K2) - 1.

[0150] It may be understood that Method 2 and Method 1 may be used simultaneously. For example, when a characteristic of a heartbeat message is detected, multiple data packets having the same characteristic may be determined using Method 1. In this way, the number of devices accessing terminal device 1 using the hotspot sharing technology may be more accurately determined.

[0151] Method 3: A user plane network element acquires network traffic characteristic parameters corresponding to a plurality of data packets, and determines, based on the network traffic characteristic parameters, the number of devices that will access the terminal device using the hotspot sharing technology.

[0152] Hotspot access is essentially a network address translation (NAT) behavior. Traffic identification essentially classifies IP addresses within a network into IP addresses of NAT devices and IP addresses of common hosts, which is similar to identifying hotspot sharing behavior. Terminal devices that enable hotspot sharing functions can be considered NAT devices, and other devices that do not enable hotspot sharing functions are considered common hosts. The general idea of ​​the method is to obtain IP addresses within a network, and then use each IP address as an example in data mining to connect NAT devices to common hosts within the network through data mining.

[0153] The user plane network element then further determines the number of devices that use the hotspot sharing technology to access the NAT device. A specific method is as follows: The user plane network element collects data packets, and then analyzes network traffic characteristic parameters corresponding to the collected data packets based on a machine learning / depth model to determine the number of devices that use the hotspot sharing technology to access the terminal device. The network traffic characteristic parameters corresponding to the data packets include one or more of the following: arrival time of the data packets, IP layer information in the data packets, and Transmission Control Protocol (TCP) layer information in the data packets. The machine learning / depth model is obtained through pre-training based on the network traffic characteristic parameters of multiple collected data packets and label information of the NAT device.

[0154] Method 4: A user plane network element receives a plurality of HTTP request messages, the HTTP request messages including device parameters, and the user plane network element determines the number of devices that will access the terminal device using the hotspot sharing technology based on the device parameters in the plurality of HTTP request messages.

[0155] When accessing an HTTP service, a device sends an HTTP request message. A UserAgent field in a message 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, based on the parameters carried in the message header of the HTTP request message, the user plane network element can determine whether the device is a device that uses the hotspot sharing technology to access the terminal device, and can determine the number of devices that use the hotspot sharing technology to access the terminal device.

[0156] Similarly, the above methods can be used in combination with each other to determine the number of devices accessing the terminal device using the hotspot sharing technology, and the details will not be described again.

[0157] 2(b) is a schematic flowchart of a hotspot device management method according to an embodiment of this application. The method includes the following steps:

[0158] Step 201b: The policy control network element sends indication information to the user plane network element.

[0159] In response, the user plane network element receives the indication information.

[0160] For the send action, see the description of step 201a.

[0161] The indication information indicates that when the number of devices accessing the terminal device using the hotspot sharing technology changes, the number of devices after the change should be sent to the policy control network element.

[0162] Step 202b: When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, the user plane network element sends the second number to the policy control network element.

[0163] In other words, when it is determined that the number of devices accessing the terminal device using the hotspot sharing technology changes, the user plane network element sends the changed number of devices to the policy control network element.

[0164] In the above solution, the policy control network element detects the number of devices accessing the terminal device using the hotspot sharing technology, and after detecting that the number of devices accessing the terminal device using the hotspot sharing technology changes, indicates the changed number of devices to the user plane network element to send to the policy control network element, so that the policy control network element can determine a charging method or control method for the terminal device based on the changed number of devices, thereby helping to charge appropriately and control the terminal device accurately.

[0165] In one implementation method, after step 202b, the following step 203b, step 204b, or step 203b and step 204b may be further executed.

[0166] Step 203b: The policy control network element sends the charging rule to the user plane network element.

[0167] In response, the user plane network element receives the charging rules.

[0168] After receiving the second number, the policy control network element determines a charging rule based on the second number, and then sends the charging rule to the user plane network element, which charges the terminal device according to the charging rule.

[0169] In one implementation method, in this embodiment of the application, intervals are specified for the number of devices accessing the terminal device using the hotspot sharing technology, and a charging rule is configured for each interval. For example, when the number of devices is within the interval range of 0 to 2, charging rule 1 is configured. When the number of devices is within the interval range of 3 to 5, charging rule 2 is configured, etc. The specific implementation method of the charging rules is not limited to this embodiment of the application. In the method, the charging rules are effectively configured to appropriately charge the terminal device.

[0170] Step 204b: The policy control network element sends the control policy rule to the user plane network element.

[0171] In response, the user plane network element receives the control policy rules.

[0172] After receiving the second number, the policy control network element determines a control policy rule based on the second number, and then sends the control policy rule to the user plane network element, which controls the terminal device according to the control policy rule.

[0173] In one implementation method, in this embodiment of the application, intervals are specified for the number of devices accessing the terminal device using the hotspot sharing technology, and a control policy rule is configured for each interval. For example, when the number of devices is within the interval range of 0 to 2, control policy rule 1 is configured. When the number of devices is within the interval range of 3 to 5, control policy rule 2 is configured, etc. The specific implementation method of the control policy rule is not limited to this embodiment of the application. In the method, the control policy rule is effectively configured to appropriately control the terminal device.

[0174] It should be noted that in the embodiment of Figure 2(b), for an implementation method in which the user plane network element detects the number of devices accessing the terminal device using the hotspot sharing technology, reference should be made to the related description in the embodiment of Figure 2(a). Details of the embodiment of Figure 2(b) will not be described again.

[0175] The embodiments of Figures 2(a) and 2(b) are described below in relation to specific embodiments. The following embodiments of Figures 3(a) and 3(b) and Figures 5(a) and 5(b) are specific examples of the embodiment of Figure 2(a), and the following embodiment of Figure 4 is specific examples of the embodiment of Figure 2(b).

[0176] 3(a) and 3(b) are schematic flowcharts of a hotspot device management method according to an embodiment of this application. The method includes the following steps:

[0177] Step 301: A terminal device sends a session establishment request message to a session management network element.

[0178] The terminal device is a device that has Internet access capability and hotspot sharing function, for example, a smartphone.

[0179] In 4G, the session management network element is the PGW-C. In 5G, the session management network element is the SMF.

[0180] In 5G, the session establishment request message may be a Nsmf_PDUSession_CreateSMContext_Request message.

[0181] Step 302: The session management network element sends a policy establishment request message to the policy control network element.

[0182] In 4G, the policy control network element is a PCRF, and the session management network element (i.e., PGW-C) sends a policy establishment request message to the PCRF via the Gx interface between the PGW-C and the PCRF.

[0183] In 5G, the policy control network element is a PCF, and the session management network element (i.e., SMF) sends a policy establishment request message to the PCF via the N7 interface between the SMF and the PCF.

[0184] In 5G, the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.

[0185] The policy establishment request message is used to request a user policy.

[0186] Step 303: The policy control network element sends a policy establishment response message to the session management network element.

[0187] In 5G, the policy establishment response message may be an Npcf_SMPolicyControl_Create_Request message.

[0188] The policy establishment response message includes a hotspot access threshold exceeding reporting event and a hotspot access threshold. The hotspot access threshold exceeding reporting event indicates that an event should be reported when an event occurs in which the number of devices accessing the terminal device using the hotspot sharing technology exceeds the hotspot access threshold. The policy control network element may locally obtain subscription data of the terminal device and obtain the hotspot access threshold corresponding to the terminal device from the subscription data.

[0189] In one implementation method, in 4G, the policy establishment response message includes a credit control answer (CCA) message or a Re-Auth-Request (RAR) message, and the CCA message or the RAR message includes a hotspot access threshold exceeded report event and a hotspot access threshold.

[0190] The hotspot access threshold exceeded report event is a specific example of indication information in the embodiment of FIG. 2(a).

[0191] The CCA message is used as an example. The CCA message currently includes an Event-Trigger field.

[0192] In a 4G application scenario, in this application, the event trigger field may be extended, and the value range of the event trigger is expanded. For example, a new event trigger value, TETHERING_EXCEED_NUM_REPORT, is added. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeded report event. Correspondingly, Tethering-Num-Threshold corresponding to TETHERING_EXCEED_NUM_REPORT is further added. Tethering-Num-Threshold is an example of a hotspot access threshold. When the value of the event trigger in the CCA message is TETHERING_EXCEED_NUM_REPORT, the CCA message further includes Tethering-Num-Threshold. TETHERING_EXCEED_NUM_REPORT and Tethering-Num-Threshold are referred to as an attribute-value pair (AVP).

[0193] In another implementation method, in a 5G application scenario, the policy establishment response message includes SmPolicyDecision. Some contents included in SmPolicyDecision are shown in Table 1.

[0194] [Table 1]

[0195] policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger. In this embodiment of the application, a new value range of policyCtrlReqTriggers is added. For example, a new value of policyCtrlReqTriggers, TETHERING_EXCEED_NUM_REPORT, is added. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeded report event.

[0196] Tethering_num_Threshold is a newly added attribute. Tethering_num_Threshold is an example of a hotspot access threshold.

[0197] Step 304: The session management network element sends a session establishment request message to the user plane network element.

[0198] In 4G, the user plane network element is the PGW-U, and the session management network element (i.e., the PGW-C) sends a session establishment request message to the PGW-U via the Sx interface between the PGW-C and the PGW-U.

[0199] In 5G, the user plane network element is the UPF, and the session management network element (i.e., the SMF) sends a session establishment request message to the UPF via the N4 interface between the SMF and the UPF.

[0200] In 5G, the session establishment request message may be an N4 session establishment request message.

[0201] The session establishment request message includes a hotspot access threshold exceeding reporting event and a hotspot access threshold.

[0202] In one implementation method, the session establishment request message includes a Usage Reporting Rule (URR), which includes Extended Reporting Triggers and a Tethering_num_Threshold. The Extended Reporting Triggers include a hotspot access threshold exceeded reporting event. The Tethering_num_Threshold is an example of the hotspot access threshold.

[0203] Step 305: The user plane network element initiates hot spot access detection based on the hot spot access threshold exceeding reporting event.

[0204] For an implementation method of the user plane network element detecting the number of devices accessing the terminal device using the hotspot sharing technology, please refer to the related description in the embodiment of Figure 2(a), and the details will not be described again.

[0205] Step 306: The user plane network element sends a session establishment response message to the session management network element.

[0206] In 5G, the session establishment response message may be an N4 session establishment response message.

[0207] Step 307: The user plane network element sends a session report request message to the session management network element.

[0208] In 5G, the session report request message may be an N4 session report request message.

[0209] Specifically, when the user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology exceeds a hotspot access threshold, the user plane network element sends a session report request message to the session management network element, where the session report request message includes a hotspot access threshold exceeded event, and the hotspot access threshold exceeded event indicates that the number of devices accessing the terminal device using the hotspot sharing technology exceeds the hotspot access threshold.

[0210] The hotspot access threshold exceeded event is a specific example of the first event in the embodiment of FIG. 2(a).

[0211] For example, the session report request message may include extended usage report triggers, and the extended usage report triggers may include a hotspot threshold exceeded event. Step 308: The session management network element sends a policy update request message to the policy control network element.

[0212] In 5G, the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.

[0213] The policy update request message includes a hotspot access threshold exceeded event.

[0214] Step 309: The policy control network element determines a charging rule 1 and / or a control policy rule 1 for the terminal device.

[0215] The hotspot access threshold exceeded event received by the policy control network element triggers the policy control network element to determine charging rule 1 and / or control policy rule 1 for the terminal device according to a preconfigured policy or subscription policy.

[0216] Step 310: The policy control network element sends a policy update response message to the session management network element.

[0217] In 5G, the policy update response message may be an Npcf_SMPolicyControl_Update_Response message.

[0218] The policy update response message includes charging rules 1 for the terminal device and / or control policy rules 1 for the terminal device.

[0219] Step 311: The session management network element sends a session modification request message to the user plane network element.

[0220] In 5G, the session modification request message may be an N4 session modification request message.

[0221] The session modification request message includes charging rule 1 and / or control policy rule 1 for the terminal device. In one implementation, the session modification request message includes a packet detection rule (PDR), and the PDR includes charging rule 1 and / or control policy rule 1 for the terminal device.

[0222] 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.

[0223] Optionally, when the user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes from exceeding the hotspot access threshold to being below the hotspot access threshold, the following steps 313 to 318 may be further executed after step 312.

[0224] Step 313: The user plane network element sends a session report request message to the session management network element.

[0225] In 5G, the session report request message may be an N4 session report request message.

[0226] Specifically, when a user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes from above the hotspot access threshold to below 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 below-hotspot access threshold event, and the below-hotspot access threshold event indicates that the number of devices accessing the terminal device using the hotspot sharing technology is below the hotspot access threshold.

[0227] The below-hotspot-access-threshold event is a specific example of the second event in the embodiment of FIG. 2(a).

[0228] For example, the session report request message may include an extended usage reporting trigger, and the extended usage reporting trigger may include a below-hotspot access threshold event.

[0229] Step 314: The session management network element sends a policy update request message to the policy control network element.

[0230] In 5G, the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.

[0231] The policy update request message includes the hotspot access below threshold event.

[0232] Step 315: The policy control network element determines a charging rule 2 and / or a control policy rule 2 for the terminal device.

[0233] The below-hotspot access threshold event received by the policy control network element triggers the policy control network element to determine charging rule 2 and / or control policy rule 2 for the terminal device according to a preconfigured policy or a subscription policy.

[0234] Step 316: The policy control network element sends a policy update response message to the session management network element.

[0235] In 5G, the policy update response message may be an Npcf_SMPolicyControl_Update_Response message.

[0236] The policy update response message includes charging rules 2 for the terminal device and / or control policy rules 2 for the terminal device.

[0237] Step 317: The session management network element sends a session modification request message to the user plane network element.

[0238] In 5G, the session modification request message may be an N4 session modification request message.

[0239] The session modification request message includes charging rule 2 for the terminal device and / or control policy rule 2 for the terminal device. In one implementation method, the session modification request message includes a PDR, and the PDR includes charging rule 2 for the terminal device and / or control policy rule 2 for the terminal device.

[0240] 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.

[0241] In the above solution, a user plane network element may detect the number of devices accessing a terminal device using a hotspot sharing technology, and when the user plane network element detects that the number of devices accessing the terminal device using a hotspot sharing technology exceeds a hotspot access threshold, the user plane network element may report an exceed-hotspot-access-threshold event and trigger a policy control network element to determine corresponding charging rules and / or control policy rules. In addition, when the user plane network element detects that the number of devices accessing the terminal device using a hotspot sharing technology is less than the hotspot access threshold, the user plane network element may further report a below-hotspot-access-threshold event and trigger a policy control network element to determine corresponding charging rules and / or control policy rules. Therefore, this solution can accurately charge and effectively control terminal devices.

[0242] It should be noted that steps 303 and 304 can be understood as specific implementations of step 201a in the embodiment of FIG. 2(a), steps 307 and 308 can be understood as specific implementations of step 202a in the embodiment of FIG. 2(a), steps 310 and 311 can be understood as specific implementations of step 203a and step 204a in the embodiment of FIG. 2(a), steps 313 and 314 can be understood as specific implementations of step 205a in the embodiment of FIG. 2(a), and steps 316 and 317 can be understood as specific implementations of step 206a and step 207a in the embodiment of FIG. 2(a). For specific implementations, please refer to the related description in the embodiment of FIG. 2(a). Details will not be described again.

[0243] 4 is a schematic flowchart of a hotspot device management method according to an embodiment of this application. The method includes the following steps:

[0244] Step 401: A terminal device sends a session establishment request message to a session management network element.

[0245] The terminal device is a device that has Internet access capability and hotspot sharing function, for example, a smartphone.

[0246] In 4G, the session management network element is the PGW-C. In 5G, the session management network element is the SMF.

[0247] In 5G, the session establishment request message may be an Nsmf_PDUSession_CreateSMContext request message.

[0248] Step 402: The session management network element sends a policy establishment request message to the policy control network element.

[0249] In 4G, the policy control network element is a PCRF, and the session management network element (i.e., PGW-C) sends a policy establishment request message to the PCRF via the Gx interface between the PGW-C and the PCRF.

[0250] In 5G, the policy control network element is a PCF, and the session management network element (i.e., SMF) sends a policy establishment request message to the PCF via the N7 interface between the SMF and the PCF.

[0251] In 5G, the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.

[0252] The policy establishment request message is used to request a user policy.

[0253] Step 403: The policy control network element sends a policy establishment response message to the session management network element.

[0254] In 5G, the policy establishment response message may be an Npcf_SMPolicyControl_Create_Request message.

[0255] The policy establishment response message includes a hotspot access device number report event, which indicates that when an event occurs in which the number of devices accessing the terminal device using the hotspot sharing technology changes, the number of devices after the change should be reported.

[0256] In one implementation method, in 4G, the policy establishment response message includes a CCA message or an RAR message, and the CCA message or the RAR message includes a hotspot access device number reporting event.

[0257] The hotspot access device number reporting event is a specific example of indication information in the embodiment of FIG. 2(b).

[0258] The CCA message is used as an example. The CCA message currently includes an event trigger field.

[0259] In a 4G application scenario, in this application, the event trigger may be extended, and the value range of the event trigger is expanded. For example, a new event trigger value TETHERING_NUM_REPORT is added. TETHERING_NUM_REPORT is an example of a hotspot access device number reporting event.

[0260] In another implementation method, in a 5G application scenario, the policy establishment response message includes SmPolicyDecision. Some contents included in SmPolicyDecision are shown in Table 2.

[0261] [Table 2]

[0262] policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger. In this embodiment of the application, a new value range of policyCtrlReqTriggers is added. For example, a new value of policyCtrlReqTriggers, TETHERING_NUM_REPORT, is added. TETHERING_NUM_REPORT is an example of a hotspot access device number reporting event.

[0263] Step 404: The session management network element sends a session establishment request message to the user plane network element.

[0264] In 4G, the user plane network element is the PGW-U, and the session management network element (i.e., the PGW-C) sends a session establishment request message to the PGW-U via the Sx interface between the PGW-C and the PGW-U.

[0265] In 5G, the user plane network element is the UPF, and the session management network element (i.e., the SMF) sends a session establishment request message to the UPF via the N4 interface between the SMF and the UPF.

[0266] In 5G, the session establishment request message may be an N4 session establishment request message.

[0267] The session establishment request message includes a hotspot access device number reporting event.

[0268] In one implementation method, the session establishment request message includes a URR, and the URR includes an extended reporting trigger, the extended reporting trigger including a hotspot access device number reporting event.

[0269] Step 405: The user plane network element initiates hot spot access detection based on the hot spot access device number reporting event.

[0270] For an implementation method of the user plane network element detecting the number of devices accessing the terminal device using the hotspot sharing technology, please refer to the related description in the embodiment of Figure 2(a), and the details will not be described again.

[0271] Step 406: The user plane network element sends a session establishment response message to the session management network element.

[0272] In 5G, the session establishment response message may be an N4 session establishment response message.

[0273] Step 407: The user plane network element sends a session report request message to the session management network element.

[0274] In 5G, the session report request message may be an N4 session report request message.

[0275] Specifically, when a user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes, the user plane network element sends a session report request message to a session management network element, where the session report request message includes the number of devices accessing the terminal device using the hotspot sharing technology, and the number is the number of devices after the change.

[0276] In one implementation method, the session report request message may include an extended usage report trigger, and the extended usage report trigger may include the number of devices accessing the terminal device using hotspot sharing technology. Step 408: The session management network element sends a policy update request message to the policy control network element.

[0277] In 5G, the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.

[0278] The policy update request message includes the number of devices that access the terminal device using the hotspot sharing technology.

[0279] Step 409: The policy control network element determines a charging rule and / or a control policy rule for the terminal device.

[0280] The number of devices accessing the terminal device using the hotspot sharing technology and received by the policy control network element triggers the policy control network element to determine charging rules for the terminal device and / or control policy rules for the terminal device according to a configured policy or a subscription policy.

[0281] Step 410: The policy control network element sends a policy update response message to the session management network element.

[0282] In 5G, the policy update response message may be an Npcf_SMPolicyControl_Update_Response message.

[0283] The policy update response message includes charging rules and / or control policy rules for the terminal device.

[0284] Step 411: The session management network element sends a session modification request message to the user plane network element.

[0285] In 5G, the session modification request message may be an N4 session modification request message.

[0286] The session modification request message includes charging rules and / or control policy rules for the terminal device. In one implementation, the session modification request message includes a PDR, and the PDR includes charging rules and / or control policy rules for the terminal device.

[0287] Step 412: The user plane network element charges the terminal device according to the charging rule for the terminal device and / or controls the terminal device according to the control policy rule for the terminal device.

[0288] Thereafter, if the user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes, the following steps 407 to 412 are repeatedly executed.

[0289] In the above solution, a user plane network element can detect the number of devices that use hotspot sharing technology to access a terminal device, and report the detected number of devices that use hotspot sharing technology to access a terminal device to trigger a policy control network element to determine corresponding charging rules and / or control policy rules. Therefore, this solution can accurately charge and effectively control terminal devices.

[0290] It should be noted that step 403 and step 404 can be understood as a specific implementation of step 201b in the embodiment of Fig. 2(b), step 407 and step 408 can be understood as a specific implementation of step 202b in the embodiment of Fig. 2(b), and step 410 and step 411 can be understood as a specific implementation of step 203b and step 204b in the embodiment of Fig. 2(b). For specific implementations, please refer to the related description in the embodiment of Fig. 2(b). Details will not be described again.

[0291] 5(a) and 5(b) are schematic flowcharts of a hotspot device management method according to an embodiment of this application. The method includes the following steps:

[0292] Step 501: A terminal device sends a session establishment request message to a session management network element.

[0293] The terminal device is a device that has Internet access capability and hotspot sharing function, for example, a smartphone.

[0294] In 4G, the session management network element is the PGW-C. In 5G, the session management network element is the SMF.

[0295] In 5G, the session establishment request message may be an Nsmf_PDUSession_CreateSMContext request message.

[0296] Step 502: The session management network element sends a policy establishment request message to the policy control network element.

[0297] In 4G, the policy control network element is a PCRF, and the session management network element (i.e., PGW-C) sends a policy establishment request message to the PCRF via the Gx interface between the PGW-C and the PCRF.

[0298] In 5G, the policy control network element is a PCF, and the session management network element (i.e., SMF) sends a policy establishment request message to the PCF via the N7 interface between the SMF and the PCF.

[0299] In 5G, the policy establishment request message may be an Npcf_SMPolicyControl_Create_Request message.

[0300] The policy establishment request message is used to request a user policy.

[0301] Step 503: The policy control network element sends a policy establishment response message to the session management network element.

[0302] In 5G, the policy establishment response message may be an Npcf_SMPolicyControl_Create_Request message.

[0303] The policy establishment response message includes a hotspot access threshold exceeded reporting event, which indicates to report an event when an event occurs in which the number of devices accessing the terminal device using the hotspot sharing technology exceeds the hotspot access threshold.

[0304] In one implementation method, in 4G, the policy establishment response message includes a CCA message or an RAR message, and the CCA message or the RAR message includes a hotspot access threshold exceeded reporting event.

[0305] The hotspot access threshold exceeded report event is a specific example of indication information in the embodiment of FIG. 2(a).

[0306] The CCA message is used as an example. The CCA message currently includes an event trigger field.

[0307] In a 4G application scenario, in this application, the event trigger may be extended, and the value range of the event trigger is expanded. For example, a new event trigger value, TETHERING_EXCEED_NUM_REPORT, is added. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeding report event.

[0308] In another implementation method, in a 5G application scenario, the policy establishment response message includes SmPolicyDecision. Some contents included in SmPolicyDecision are shown in Table 3.

[0309] [Table 3]

[0310] policyCtrlReqTriggers is an existing attribute, and the value of policyCtrlReqTriggers is represented by PolicyControlRequestTrigger. In this embodiment of the application, a new value range of policyCtrlReqTriggers is added. For example, a new value of policyCtrlReqTriggers, TETHERING_EXCEED_NUM_REPORT, is added. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeded report event.

[0311] Step 504: The session management network element sends a session establishment request message to the user plane network element.

[0312] In 4G, the user plane network element is the PGW-U, and the session management network element (i.e., the PGW-C) sends a session establishment request message to the PGW-U via the Sx interface between the PGW-C and the PGW-U.

[0313] In 5G, the user plane network element is the UPF, and the session management network element (i.e., the SMF) sends a session establishment request message to the UPF via the N4 interface between the SMF and the UPF.

[0314] In 5G, the session establishment request message may be an N4 session establishment request message.

[0315] The session establishment request message includes a hotspot access threshold exceeded reporting event.

[0316] In one implementation method, the session establishment request message includes a URR, and the URR includes an extended reporting trigger, the extended reporting trigger including a hotspot access threshold exceeded reporting event.

[0317] Step 505: The user plane network element initiates hot spot access detection based on a hot spot access threshold exceeding reporting event.

[0318] For an implementation method of the user plane network element detecting the number of devices accessing the terminal device using the hotspot sharing technology, please refer to the related description in the embodiment of Figure 2(a), and the details will not be described again.

[0319] Step 506: The user plane network element sends a session establishment response message to the session management network element.

[0320] In 5G, the session establishment response message may be an N4 session establishment response message.

[0321] Step 507: The user plane network element sends a session report request message to the session management network element.

[0322] In 5G, the session report request message may be an N4 session report request message.

[0323] The hotspot access threshold is pre-configured on the user plane network element. Alternatively, the user plane network element determines the hotspot access threshold based on the service package of the terminal device.

[0324] Specifically, when a user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology exceeds a hotspot access threshold, the user plane network element sends a session report request message to a session management network element, the session report request message including a hotspot access threshold exceeded event, and the hotspot access threshold exceeded event indicates that the number of devices accessing the terminal device using the hotspot sharing technology exceeds the hotspot access threshold.

[0325] The hotspot access threshold exceeded event is a specific example of the first event in the embodiment of FIG. 2(a).

[0326] For example, the session report request message may include an extended usage reporting trigger, and the extended usage reporting trigger may include a hotspot access threshold exceeded event.

[0327] Step 508: The session management network element sends a policy update request message to the policy control network element.

[0328] In 5G, the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.

[0329] The policy update request message includes a hotspot access threshold exceeded event.

[0330] Step 509: The policy control network element determines a charging rule 1 and / or a control policy rule 1 for the terminal device.

[0331] The hotspot access threshold exceeded event received by the policy control network element triggers the policy control network element to determine charging rule 1 and / or control policy rule 1 for the terminal device according to a preconfigured policy or subscription policy.

[0332] Step 510: The policy control network element sends a policy update response message to the session management network element.

[0333] In 5G, the policy update response message may be an Npcf_SMPolicyControl_Update_Response message.

[0334] The policy update response message includes charging rule 1 and / or control policy rule 1 for the terminal device.

[0335] Step 511: The session management network element sends a session modification request message to the user plane network element.

[0336] In 5G, the session modification request message may be an N4 session modification request message.

[0337] The session modification request message includes charging rule 1 and / or control policy rule 1 for the terminal device. In one implementation method, the session modification request message includes a PDR, and the PDR includes charging rule 1 and / or control policy rule 1 for the terminal device.

[0338] Step 512: The user plane network element charges the terminal device according to charging rule 1 for the terminal device and / or controls the terminal device according to control policy rule 1 for the terminal device.

[0339] Optionally, when the user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes from exceeding the hotspot access threshold to being below the hotspot access threshold, the following steps 513 to 518 may be further executed.

[0340] Step 513: The user plane network element sends a session report request message to the session management network element.

[0341] In 5G, the session report request message may be an N4 session report request message.

[0342] Specifically, when a user plane network element detects that the number of devices accessing the terminal device using the hotspot sharing technology changes from above the hotspot access threshold to below 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 below-hotspot access threshold event, and the below-hotspot access threshold event indicates that the number of devices accessing the terminal device using the hotspot sharing technology is below the hotspot access threshold.

[0343] The below-hotspot-access-threshold event is a specific example of the second event in the embodiment of FIG. 2(a).

[0344] For example, the session report request message may include an extended usage reporting trigger, and the extended usage reporting trigger may include a below-hotspot access threshold event.

[0345] Step 514: The session management network element sends a policy update request message to the policy control network element.

[0346] In 5G, the policy update request message may be an Npcf_SMPolicyControl_Update_Request message.

[0347] The policy update request message includes the hotspot access below threshold event.

[0348] Step 515: The policy control network element determines a charging rule 2 and / or a control policy rule 2 for the terminal device.

[0349] The below-hotspot access threshold event received by the policy control network element triggers the policy control network element to determine charging rule 2 and / or control policy rule 2 for the terminal device according to a preconfigured policy or a subscription policy.

[0350] Step 516: The policy control network element sends a policy update response message to the session management network element.

[0351] In 5G, the policy update response message may be an Npcf_SMPolicyControl_Update_Response message.

[0352] The policy update response message includes charging rules 2 and / or control policy rules 2 for the terminal device.

[0353] Step 517: The session management network element sends a session modification request message to the user plane network element.

[0354] In 5G, the session modification request message may be an N4 session modification request message.

[0355] The session modification request message includes charging rule 2 and / or control policy rule 2 for the terminal device. In one implementation method, the session modification request message includes a PDR, and the PDR includes charging rule 2 and / or control policy rule 2 for the terminal device.

[0356] 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.

[0357] In the above solution, a user plane network element may detect the number of devices accessing a terminal device using a hotspot sharing technology, and when the user plane network element detects that the number of devices accessing the terminal device using a hotspot sharing technology exceeds a hotspot access threshold, the user plane network element may report an exceed-hotspot-access-threshold event and trigger a policy control network element to determine corresponding charging rules and / or control policy rules. In addition, when the user plane network element detects that the number of devices accessing the terminal device using a hotspot sharing technology is less than the hotspot access threshold, the user plane network element may further report a below-hotspot-access-threshold event and trigger a policy control network element to determine corresponding charging rules and / or control policy rules. Therefore, this solution can accurately charge and effectively control terminal devices.

[0358] It should be noted that steps 503 and 504 can be understood as specific implementations of step 201a in the embodiment of FIG. 2(a), steps 507 and 508 can be understood as specific implementations of step 202a in the embodiment of FIG. 2(a), steps 510 and 511 can be understood as specific implementations of step 203a and step 204a in the embodiment of FIG. 2(a), steps 513 and 514 can be understood as specific implementations of step 205a in the embodiment of FIG. 2(a), and steps 516 and 517 can be understood as specific implementations of step 206a and step 207a in the embodiment of FIG. 2(a). For specific implementations, please refer to the related description in the embodiment of FIG. 2(a). Details will not be described again.

[0359] It can be understood that to realize the functions in the above embodiments, the user plane network element or the policy control network element includes corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should easily realize that the units and method steps in the examples described in connection with the embodiments disclosed in this application can be realized by hardware or a combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application scenario and the design constraints of the technical solution.

[0360] 6 and 7 are diagrams of possible communication device structures according to embodiments of this application. These communication devices may be configured to implement the functions of the user plane network element or the policy control network element in the above method embodiments, and thus can also realize the advantageous effects of the above method embodiments. In this embodiment of this application, the communication device may be a user plane network element or a policy control network element, or may be a module (e.g., a chip) used in the policy control network element or a module (e.g., a chip) used in the user plane network element.

[0361] 6, the communication device 600 includes a processing unit 610 and a transceiver unit 620. The communication device 600 is configured to implement the functions of a user plane network element or a policy control network element in the above method embodiments.

[0362] When the communication device 600 is configured to implement the functionality of the user plane network element in the embodiments of FIGS. 2(a), 3(a), and 3(b), or 5(a) and 5(b), the transceiver unit 620 is configured to receive indication information from the policy control network element. The indication information indicates to send a first event to the policy control network element when a first event occurs. The first event is that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than a hotspot access threshold. When the first event occurs, the first event is sent to the policy control network element.

[0363] In a possible implementation manner, 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.

[0364] In a possible implementation manner, the processing unit 610 is configured to determine the hotspot access threshold based on a service package of the terminal device, or the processing unit 610 is configured to determine the hotspot access threshold based on configuration information in a user plane network element.

[0365] In a possible implementation, the transceiver unit 620 is configured to receive a first charging rule from a policy control network element, the first charging rule being determined based on a first event, and the processing unit 610 is configured to charge the terminal device according to the first charging rule.

[0366] In a possible implementation, the transceiver unit 620 is configured to receive a first control policy rule from a policy control network element, the first control policy rule being determined based on a first event, and the processing unit 610 is configured to control the terminal device according to the first control policy rule.

[0367] In a possible implementation method, the transceiver unit 620 is configured to send a second event to the policy control network element when a second event occurs, the second event indicating that the number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to a hotspot access threshold.

[0368] In a possible implementation, the transceiver unit 620 is configured to receive a second charging rule from the policy control network element, the second charging rule being determined based on a second event, and the processing unit 610 is configured to charge the terminal device according to the second charging rule.

[0369] In a possible implementation, the transceiver unit 620 is configured to receive a second control policy rule from the policy control network element, the second control policy rule being determined based on a second event, and the processing unit 610 is configured to control the terminal device according to the second control policy rule.

[0370] In a possible implementation method, the transceiver unit 620 is configured to receive a plurality of data packets from a terminal device, each of the plurality of data packets including a timestamp. The processing unit 610 is configured to determine, based on the timestamp in each of the plurality of data packets, a reference value of a clock source corresponding to the plurality of data packets, and to determine, based on the reference values ​​of the clock source corresponding to the plurality of data packets, a number of devices accessing the terminal device using the hotspot sharing technology.

[0371] In a possible implementation, the processing unit 610 is configured to determine the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, where the heartbeat messages are from the terminal device or devices accessing the terminal device using the hotspot sharing technology.

[0372] In a possible implementation method, the processing unit 610 is configured to obtain network traffic characteristic parameters corresponding to the plurality of data packets, and determine, based on the network traffic characteristic parameters, the number of devices that will access the terminal device using the hotspot sharing technology.

[0373] In a possible implementation method, the processing unit 610 is configured to obtain a plurality of HTTP request messages, where the HTTP request messages include device parameters, and determine, based on the device parameters in the plurality of HTTP request messages, a number of devices that will access the terminal device using the hotspot sharing technology.

[0374] When the communication device 600 is configured to implement the functionality of the policy control network element in the embodiments of FIGS. 2(a), 3(a), and 3(b), or 5(a) and 5(b), the transceiver unit 620 is configured to send indication information to the user plane network element. The indication information indicates to send a first event to the policy control network element when a first event occurs. The first event is that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than a hotspot access threshold. When the first event occurs, the first event is received from the user plane network element.

[0375] In a possible implementation manner, the transceiver unit 620 is configured to transmit the hotspot access threshold to the user plane network element, or the indication information includes the hotspot access threshold.

[0376] In a possible implementation, the processing unit 610 is configured to determine a first charging rule based on the first event, and the transceiver unit 620 is configured to transmit the first charging rule to the user plane network element.

[0377] In one possible implementation, the processing unit 610 is configured to determine a first control policy rule based on the first event. The transceiver unit 620 is configured to transmit the first control policy rule to the user plane network element.

[0378] In a possible implementation, the transceiver unit 620 is configured to receive a second event from the user plane network element, the second event indicating that a number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to a hotspot access threshold.

[0379] In a possible implementation, the processing unit 610 is configured to determine a second charging rule based on the second event, and the transceiver unit 620 is configured to transmit the second charging rule to the user plane network element.

[0380] In one possible implementation, the processing unit 610 is configured to determine a second control policy rule based on the second event. The transceiver unit 620 is configured to transmit the second control policy rule to the user plane network element.

[0381] When the communication apparatus 600 is configured to implement the functionality of the user plane network element in the embodiment of FIG. 2(b) or FIG. 4, the transceiver unit 620 is configured to receive indication information from the policy control network element. The indication information indicates that when the number of devices accessing the terminal device using the hotspot sharing technology changes, the changed number of devices should be sent to the policy control network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, the second number is sent to the policy control network element.

[0382] In a possible implementation, the transceiver unit 620 is configured to receive a charging rule from the policy control network element. The charging rule is determined based on the second number. The processing unit 610 is configured to charge the terminal device according to the charging rule.

[0383] In a possible implementation, the transceiver unit 620 is configured to receive a control policy rule from the policy control network element. The control policy rule is determined based on the second number. The processing unit 610 is configured to control the terminal device according to the control policy rule.

[0384] In a possible implementation method, the transceiver unit 620 is configured to receive a plurality of data packets from a terminal device, each of the plurality of data packets including a timestamp. The processing unit 610 is configured to determine, based on the timestamp in each of the plurality of data packets, a reference value of a clock source corresponding to the plurality of data packets, and to determine, based on the reference values ​​of the clock source corresponding to the plurality of data packets, a number of devices accessing the terminal device using the hotspot sharing technology.

[0385] In a possible implementation, the processing unit 610 is configured to determine the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, where the heartbeat messages are from the terminal device or devices accessing the terminal device using the hotspot sharing technology.

[0386] In a possible implementation method, the processing unit 610 is configured to obtain network traffic characteristic parameters corresponding to the plurality of data packets, and determine, based on the network traffic characteristic parameters, the number of devices that will access the terminal device using the hotspot sharing technology.

[0387] In a possible implementation method, the processing unit 610 is configured to obtain a plurality of HTTP request messages, where the HTTP request messages include device parameters, and determine, based on the device parameters in the plurality of HTTP request messages, a number of devices that will access the terminal device using the hotspot sharing technology.

[0388] When the communication apparatus 600 is configured to implement the functionality of the policy control network element in the embodiment of FIG. 2(b) or FIG. 4, the transceiver unit 620 is configured to send indication information to the user plane network element. The indication information indicates that when the number of devices accessing the terminal device using the hotspot sharing technology changes, the changed number of devices is to be sent to the policy control network element. When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, the second number is received from the user plane network element.

[0389] In a possible implementation manner, the processing unit 610 is configured to determine a charging rule based on the second number. The transceiver unit 620 is configured to transmit the charging rule to a user plane network element.

[0390] In a possible implementation manner, the processing unit 610 is configured to determine the control policy rule based on the second number. The transceiver unit 620 is configured to transmit the control policy rule to the user plane network element.

[0391] For more detailed descriptions of the processing unit 610 and the transceiver unit 620, please directly refer to the relevant descriptions in the above method embodiments, and the details will not be described again here.

[0392] 7, the communication device 700 includes a processor 710 and an interface circuit 720. The processor 710 and the interface circuit 720 are coupled to each other. It may be understood that the interface circuit 720 may be a transceiver or an input / output interface. Optionally, the communication device 700 may further include a memory 730 configured to store instructions executed by the processor 710, input data required by the processor 710 to execute the instructions, or data generated after the processor 710 executes the instructions.

[0393] When the communications device 700 is configured to implement the above method embodiments, the processor 710 is configured to implement the functionality of the processing unit 610, and the interface circuit 720 is configured to implement the functionality of the transceiver unit 620.

[0394] It may be understood that the processor in the embodiments of this application may be a central processing unit (CPU), other general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0395] Those skilled in the art will understand that the various numbers, such as "first" and "second," in this application are merely used for distinction purposes to facilitate explanation and are not intended to limit the scope or indicate the order of the embodiments of this application. The term "and / or" describes an association relationship to describe related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. The symbol " / " generally indicates an "or" relationship between related objects. "At least one" means one or more. "At least two" means two or more. "At least one" or similar expressions refer to any combination of items, including any combination of one item (piece) or multiple items (pieces). For example, at least one item (piece) of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, and c may be singular or plural. "Plural" means two or more, and similarly for other quantifiers.

[0396] It should be understood that the sequence numbers of the above processes do not mean the execution order in various embodiments of this application. The execution order of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process of the embodiments of this application.

[0397] For the purpose of convenient and concise description, it can be clearly understood by those skilled in the art that the detailed operation processes of the above systems, devices and units should be referred to the corresponding processes in the above method embodiments, and the details will not be described again here.

[0398] Some or all of the above embodiments may be realized using software, hardware, firmware, or any combination thereof. When software is used for implementation, some or all of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of this application are generated in whole or in part. 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 a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optics, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio wave, or microwave) transmission. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device that integrates one or more available media, such as a server or data center. The available medium may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., digital versatile disks), or semiconductor media (e.g., solid-state drives (SSDs)).

[0399] The various exemplary logic units and circuits described in the embodiments of this application may implement or perform the described functions using designs of general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays, other programmable logic devices, discrete gates, transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor. Optionally, a general-purpose processor may alternatively be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors with a digital signal processor core, or any other similar configuration.

[0400] The steps of a method or algorithm described in the embodiments of this application may be embodied directly in hardware, in a software unit executed by a processor, or a combination thereof. The software unit may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a register, a hard disk drive, or a removable disk in any other form of storage medium known in the art. For example, a storage medium may be connected to the processor, thereby allowing the processor to read information from and write information to the storage medium. Optionally, the storage medium may alternatively be integrated into the processor. The processor and the storage medium may be located in an ASIC.

[0401] These computer program instructions may also be loaded onto a computer or other programmable data processing device, such that a sequence of operations and steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing a particular function in one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0402] For example, in one or more designs, the functions described in this application may be implemented using hardware, software, firmware, or any combination thereof. If software is used for implementation, the functions may be stored in or transmitted over a computer-readable storage medium in the form of one or more instructions or code. Computer-readable storage media includes computer storage media and communication media that enable a computer program to be transferred from one place to another. A storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, computer-readable storage media may include, but are not limited to, RAM, ROM, other optical disk storage, disk storage, other magnetic storage devices, or any other medium that can be used to carry or store program code, whether in the form of instructions or data structures or otherwise readable by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection may be properly defined as a computer-readable storage medium. For example, software is included within the defined computer-readable storage medium if it is transmitted from a website, server, or other remote resource using coaxial cable, fiber optic computer, twisted pair, digital subscriber line, or wirelessly, such as infrared, radio wave, or microwave. Disks and discs include compact discs, laser discs, optical discs, digital versatile discs, floppy disks, and Blu-ray discs. Disks typically copy data by magnetic means, while discs typically copy data optically by laser means. Combinations of the above may also be included within a computer-readable storage medium.

[0403] Those skilled in the art should recognize that the functions described in this application in one or more of the above examples can be realized by hardware, software, firmware, or any combination thereof. When software is used for implementation, the functions described above can be stored in or transmitted as one or more instructions or code in a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any medium that allows a computer program to be transmitted from one place to another. Storage media may be any available medium accessible to a general-purpose or special-purpose computer.

[0404] In the above specific implementation, the objectives, technical solutions, and advantageous effects of this application are further described in detail. It should be understood that the above description is merely a specific implementation of this application and is not intended to limit the protection scope of this application. Any modifications, equivalent replacements, improvements, etc. made based on the technical solutions of this application should fall within the protection scope of this application. According to the above description of this specification in this application, techniques in the art can utilize or implement the content of this application. Any modifications based on the disclosed content should be considered limiting in the art. The basic principles described in this application may be applied to other variations without departing from the essence and scope of this application. Therefore, the content disclosed in this application is not limited to the described embodiments and designs, but may be extended to the largest extent consistent with the principles and novel features disclosed in this application.

[0405] Although this application has been described with reference to specific features and embodiments thereof, it is clear that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Correspondingly, the specification and the accompanying drawings are merely exemplary descriptions of this application as defined by the appended claims, and any or all modifications, variations, combinations, or equivalents covering the scope of this application are deemed to be included. It is clear that those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, this application is intended to cover these modifications and variations of this application as long as they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims

1. receiving, by a user plane network element, indication information from a policy control network element, the indication information indicating that a first event is to be sent to the policy control network element when a first event occurs, the first event being that a number of devices accessing a terminal device using a hotspot sharing technology is equal to or greater than a hotspot access threshold; when the first event occurs, sending, by the user plane network element, the first event to the policy control network element; A hotspot device management method comprising:

2. The method comprises: or further comprising receiving, by the user plane network element, the hotspot access threshold from the policy control network element; the indication information includes the hotspot access threshold; The method of claim 1.

3. The method comprises: determining, by the user plane network element, the hotspot access threshold based on a service package of the terminal device; or determining, by the user plane network element, the hotspot access threshold based on configuration information in the user plane network element; further comprising: The method of claim 1.

4. The method comprises: receiving, by the user plane network element, a first charging rule from the policy control network element, the first charging rule being determined based on the first event; charging, by the user plane network element, the terminal device according to the first charging rule; further comprising: The method according to any one of claims 1 to 3.

5. The method comprises: receiving, by the user plane network element, a first control policy rule from the policy control network element, the first control policy rule being determined based on the first event; controlling, by the user plane network element, the terminal device according to the first control policy rule; further comprising: The method according to any one of claims 1 to 4.

6. The method comprises: and when a second event occurs, sending the second event by the user plane network element to the policy control network element, the second event indicating that the number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to the hotspot access threshold. The method according to any one of claims 1 to 5.

7. The method comprises: receiving, by the user plane network element, a second charging rule from the policy control network element, the second charging rule being determined based on the second event; charging, by the user plane network element, the terminal device according to the second charging rule; further comprising: The method of claim 6.

8. The method comprises: receiving, by the user plane network element, a second control policy rule from the policy control network element, the second control policy rule being determined based on the second event; controlling, by the user plane network element, the terminal device according to the second control policy rule; further comprising:

8. The method according to claim 6 or 7.

9. The method comprises: receiving, by the user plane network element, a plurality of data packets from the terminal device, each of the plurality of data packets including a timestamp; determining, by the user plane network element, a reference value of a clock source corresponding to each of the plurality of data packets based on the timestamp in each of the plurality of data packets; determining, by the user plane network element, the number of devices accessing the terminal device using the hotspot sharing technology based on the reference values ​​of the clock source corresponding to the plurality of data packets; further comprising: The method according to any one of claims 1 to 8.

10. The method comprises: determining, by the user plane network element, the number of devices accessing the terminal device using the hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more periods, wherein the heartbeat messages are from the terminal device or the devices accessing the terminal device using the hotspot sharing technology; The method according to any one of claims 1 to 8.

11. The method comprises: obtaining, by the user plane network element, network traffic characteristic parameters corresponding to a plurality of data packets; determining, by the user plane network element, the number of devices accessing the terminal device using the hotspot sharing technology based on the network traffic characteristic parameters; further comprising: The method according to any one of claims 1 to 8.

12. The method comprises: obtaining, by the user plane network element, a plurality of HyperText Transfer Protocol (HTTP) request messages, the HTTP request messages including device parameters; determining, by the user plane network element, the number of devices accessing the terminal device using the hotspot sharing technology based on device parameters in the plurality of HTTP request messages; further comprising: The method according to any one of claims 1 to 8.

13. sending, by a policy control network element, indication information to a user plane network element, the indication information indicating that a first event is to be sent to the policy control network element when a first event occurs, the first event being that a number of devices accessing a terminal device using a hotspot sharing technology is equal to or greater than a hotspot access threshold; receiving, by the policy control network element, the first event from the user plane network element when the first event occurs; A hotspot device management method comprising:

14. The method comprises: or further comprising transmitting, by the policy control network element, the hotspot access threshold to the user plane network element; the indication information includes the hotspot access threshold; The method of claim 13.

15. The method comprises: determining, by the policy control network element, a first charging rule based on the first event, the first charging rule being utilized to charge the terminal device; sending, by the policy control network element, the first charging rule to the user plane network element; further comprising:

15. The method of claim 13 or 14.

16. The method comprises: determining, by the policy control network element, a first control policy rule based on the first event, the first control policy rule being utilized to control the terminal device; sending, by the policy control network element, the first control policy rule to the user plane network element; further comprising: The method according to any one of claims 13 to 15.

17. The method comprises: receiving, by the policy control network element, a second event from the user plane network element, the second event indicating that the number of devices accessing the terminal device using the hotspot sharing technology is less than or equal to the hotspot access threshold; The method according to any one of claims 13 to 16.

18. The method comprises: determining, by the policy control network element, a second charging rule based on the second event, the second charging rule being utilized to charge the terminal device; and sending, by the policy control network element, the second charging rule to the user plane network element; further comprising:

18. The method of claim 17.

19. The method comprises: determining, by the policy control network element, a second control policy rule based on the second event, the second control policy rule being utilized to control the terminal device; sending, by the policy control network element, the second control policy rule to the user plane network element; further comprising:

19. The method of claim 17 or 18.

20. receiving, by a user plane network element, indication information from a policy control network element, the indication information indicating that when a number of devices accessing a terminal device using a hotspot sharing technology changes, the changed number of devices should be sent to the policy control network element; When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, transmitting the second number by the user plane network element to the policy control network element; A hotspot device management method comprising:

21. The method comprises: receiving, by the user plane network element, a charging rule from the policy control network element, the charging rule being determined based on the second number; charging, by the user plane network element, the terminal device according to the charging rule; further comprising:

21. The method of claim 20.

22. The method comprises: receiving, by the user plane network element, a control policy rule from the policy control network element, the control policy rule being determined based on the second number; controlling, by the user plane network element, the terminal device according to the control policy rule; further comprising:

22. The method of claim 20 or 21.

23. sending, by a policy control network element, indication information to a user plane network element, wherein when a number of devices accessing a terminal device using a hotspot sharing technology changes, the indication information indicates that the changed number of devices should be sent to the policy control network element; When the number of devices accessing the terminal device using the hotspot sharing technology changes from a first number to a second number, receiving the second number from the user plane network element by the policy control network element; A hotspot device management method comprising:

24. The method comprises: determining, by the policy control network element, a charging rule based on the second number, the charging rule being utilized to charge the terminal device; sending, by the policy control network element, the charging rules to the user plane network element; further comprising:

24. The method of claim 23.

25. The method comprises: determining, by the policy control network element, a control policy rule based on the second number, the control policy rule being utilized to control the terminal device; sending, by the policy control network element, the control policy rule to the user plane network element; further comprising:

25. The method of claim 23 or 24.

26. A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive a signal from a communication device other than the communication device and transmit the signal to the processor, or to transmit a signal from the processor to a communication device other than the communication device, and the processor is configured to implement the method of any one of claims 1 to 12, the method of any one of claims 13 to 19, the method of any one of claims 20 to 22, or the method of any one of claims 23 to 25 by utilizing logic circuits or by executing code instructions.

27. 1. A computer program product comprising a computer program, which, when executed by a communications device, performs the method of any one of claims 1 to 12, the method of any one of claims 13 to 19, the method of any one of claims 20 to 22, or the method of any one of claims 23 to 25.

28. A computer-readable storage medium, the storage medium storing a computer program or instructions, the computer program or instructions, when executed by a communication device, performing the method of any one of claims 1 to 12, the method of any one of claims 13 to 19, the method of any one of claims 20 to 22, or the method of any one of claims 23 to 25.

29. A communication system comprising a user plane network element configured to perform the method of any one of claims 1 to 12, and a policy control network element configured to perform the method of any one of claims 13 to 19.

30. A communication system comprising a user plane network element configured to perform the method of any one of claims 20 to 22, and a policy control network element configured to perform the method of any one of claims 23 to 25.

Images