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 the priority of Chinese Patent Application No. 202210876527.5, titled "HOTSPOT DEVICE MANAGEMENT METHOD, COMMUNICATION APPARATUS, AND COMMUNICATION SYSTEM", filed with the China National Intellectual Property Administration on July 25, 2022, the entire content of which is incorporated herein by reference.

[0002] 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 Art

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

[0004] However, it is necessary to solve how to effectively manage terminal devices with a hotspot sharing function.

Summary of the Invention

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

[0006] According to a first aspect, embodiments of this application provide a method for managing hotspot devices. The method may be performed by a user plane network element or a module (e.g., a chip) used by a user plane network element. For example, a 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 that a first event should be sent to the policy control network element when a first event occurs. The first event is that the number of devices accessing a terminal device using 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 terminal devices using hotspot sharing technology and to notify the policy control network element when it detects that the number of devices accessing terminal devices using hotspot sharing technology is equal to or greater than the hotspot access threshold. Therefore, the policy control network element knows that the number of devices accessing terminal devices using hotspot sharing technology is equal to or greater than the hotspot access threshold, and based on this, the policy control network element determines the billing or control method for the terminal device, bills appropriately, and controls the terminal device effectively.

[0008] In possible implementations, a user plane network element receives the hotspot access threshold from a policy-controlled network element, or the indication information includes the hotspot access threshold.

[0009] In the above solution, the policy-controlled network element configures the hotspot access threshold for the user plane network element, thereby allowing for precise configuration of the hotspot access threshold.

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

[0011] In the above solution, the user plane network element does not need to determine 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 billing rule from a policy control network element. The first billing rule is determined based on a first event. The user plane network element then bills the terminal device according to the first billing rule.

[0013] The above solution allows for effective configuration of billing rules, enabling proper billing of terminal devices.

[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 is determined based on a first event. The user plane network element controls the terminal device according to the first control policy rule.

[0015] The above solution allows for effective configuration of control policy rules, enabling proper control of terminal devices.

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

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

[0018] In other words, when the number of devices accessing a terminal device using hotspot sharing technology changes, the billing rules are adaptively modified. The above solution allows the billing rules to be changed based on the actual situation so that terminal devices can be billed appropriately. The above explanation is applicable to explanations in other aspects and will not be explained again in detail.

[0019] In a possible implementation, a user plane network element receives a second control policy rule from a policy control network element. The second control policy rule is determined based on a second event. 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 a terminal device using hotspot sharing technology changes, the control policy rules are adaptively modified. The above solution allows the control policy rules to be modified based on the actual situation to properly control the terminal device. The above explanation is applicable to explanations of other aspects and will not be explained again in detail.

[0021] In a possible implementation, a user plane network element receives multiple data packets from a terminal device. Each of these data packets contains a timestamp. Based on the timestamps in each of the data packets, the user plane network element determines a reference value for the clock source corresponding to the data packets. Based on the reference value for the clock source corresponding to the data packets, the user plane network element determines the number of devices that can access the terminal device using hotspot sharing technology.

[0022] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

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

[0024] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

[0025] In possible implementations, a user plane network element obtains network traffic characteristic parameters corresponding to Internet Protocol (IP) addresses within the network. Based on these network traffic characteristic parameters, the user plane network element determines the number of devices that can access terminal devices using hotspot sharing technology.

[0026] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

[0027] In a possible implementation method, a user plane network element obtains a plurality of Hypertext Transfer Protocol (HTTP) request messages. The HTTP request messages include device parameters. The user plane network element determines the number of devices accessing the terminal device using the hotspot sharing technology 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 using the hotspot sharing technology can be accurately determined.

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

[0030] In the above solution, the policy control network element detects the number of devices accessing the terminal device using the hotspot sharing technology for the user plane network element, and indicates to notify the policy control network element when it is detected that the number of devices accessing the terminal device using the hotspot sharing technology is equal to or greater than the hotspot access threshold. Therefore, 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, whereby the policy control network element determines the charging method or control method for the terminal device, charges appropriately, and accurately 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, whereby the hotspot access threshold can be accurately configured.

[0033] In a possible implementation method, the policy control network element determines a first charging rule based on a first event. The first charging rule is used to charge the terminal device. The policy control network element sends the first charging rule to the user plane network element.

[0034] In the above solution, the charging rule is effectively configured to be able to charge the terminal device appropriately.

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

[0036] The above solution allows for effective configuration of control policy rules, enabling proper control of terminal devices.

[0037] In a possible implementation, the policy control network element receives a second event from the user plane network element. This second event indicates that the number of devices accessing the terminal device using hotspot sharing technology is below the hotspot access threshold.

[0038] In a possible implementation, a policy control network element determines a second billing rule based on a second event. This second billing rule is used to charge the terminal device. The policy control network element then transmits the second billing rule to the user plane network element.

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

[0040] According to a third aspect, embodiments of the present application provide a method for managing hotspot devices. The method may be performed by a user plane network element or a module (e.g., a chip) used by a user plane network element. For example, a 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 tells the policy control network element to send the changed number of devices when the number of devices accessing a terminal device using the hotspot sharing technology changes. When the number of devices accessing a 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 hotspot sharing technology, and after detecting a change in the number of devices accessing the terminal device using hotspot sharing technology, it instructs the user plane network element to send the changed number of devices to the policy control network element. Thereafter, the policy control network element determines the billing or control method for the terminal device based on the changed number of devices, bills appropriately, and controls the terminal device effectively.

[0042] In a possible implementation, a user plane network element receives billing rules from a policy control network element. The billing rules are determined based on a second number. The user plane network element then bills the terminal device according to the billing rules.

[0043] The above solution allows for effective configuration of billing rules, enabling proper billing of terminal devices.

[0044] In possible implementations, a user plane network element receives control policy rules from a policy control network element. These control policy rules are determined based on a second number. The user plane network element then controls the terminal device according to the control policy rules.

[0045] The above solution allows for effective configuration of control policy rules, enabling proper control of terminal devices.

[0046] In a possible implementation, a user plane network element receives multiple data packets from a terminal device. Each of these data packets contains a timestamp. Based on the timestamps in each of the data packets, the user plane network element determines a reference value for the clock source corresponding to the data packets. Based on the reference value for the clock source corresponding to the data packets, the user plane network element determines the number of devices that can access the terminal device using hotspot sharing technology.

[0047] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

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

[0049] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

[0050] In possible implementations, a user plane network element obtains network traffic characteristic parameters corresponding to multiple data packets. Based on these network traffic characteristic parameters, the user plane network element determines the number of devices that can access the terminal device using hotspot sharing technology.

[0051] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

[0052] In a possible implementation, a user plane network element receives multiple HTTP request messages. These HTTP request messages contain device parameters. Based on the device parameters in the multiple HTTP request messages, the user plane network element determines the number of devices that will access the terminal device using hotspot sharing technology.

[0053] The above solution allows for the precise determination of the number of devices accessing the terminal device using hotspot sharing technology.

[0054] According to a fourth aspect, embodiments of the present application provide a method for managing hotspot devices. The method may be performed by a policy control network element or a module (e.g., a chip) used by a policy control network element. For example, a policy control network element performs the method. The method includes: The policy control network element transmits indication information to a user plane network element. The indication information tells the policy control network element to transmit the changed number of devices when the number of devices accessing a terminal device using the hotspot sharing technology changes. When the number of devices accessing a 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 hotspot sharing technology, and after detecting a change in the number of devices accessing the terminal device using hotspot sharing technology, it instructs the user plane network element to send the changed number of devices to the policy control network element. This allows the policy control network element to determine a billing or control method for the terminal device based on the changed number of devices, which helps to bill appropriately and control the terminal device effectively.

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

[0057] The above solution allows for effective configuration of billing rules, enabling proper billing of terminal devices.

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

[0059] The above solution allows for effective configuration of control policy rules, enabling proper control of terminal devices.

[0060] According to a fifth aspect, embodiments of this application provide a communication 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 that implements any of the implementation methods of the first aspect. The function may be implemented by hardware or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0061] According to a sixth aspect, an embodiment of this 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 that implements any of the implementation methods of the second aspect. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0062] According to the seventh aspect, embodiments of this application provide a communication 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 that implements any of the implementation methods of the third aspect. The function may be implemented by hardware or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0063] According to the 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 that implements any of the implementation methods of the fourth aspect. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.

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

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

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

[0067] According to the 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 other devices via the interface circuit and to perform any implementation method of the first to fourth aspects. There may be one or more processors.

[0068] According to the thirteenth aspect, embodiments of the present application further provide a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed on a communication device, any implementation method of the first to fourth aspects is performed.

[0069] According to the fourteenth aspect, embodiments of this application further provide a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a communication device, any implementation method of the first to fourth aspects is performed.

[0070] According to the fifteenth aspect, embodiments of the present application further provide a chip system including a processor configured to perform any of the implementation methods of the first to fourth aspects.

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

[0072] According to the 17th aspect, an embodiment of the present application further provides a communication system comprising a user plane network element configured to perform any implementation method of the third aspect and a policy control network element configured to perform any implementation method of the fourth aspect. [Brief explanation of the drawing]

[0073] [Figure 1] This is a diagram illustrating the architecture of a 5G network based on a service-oriented architecture. [Figure 2(a)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 2(b)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 2(c)] This is an illustrative diagram illustrating how to determine the number of devices that can access a terminal device using hotspot sharing technology. [Figure 3(a)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 3(b)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 4] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 5(a)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 5(b)] This is a schematic flowchart of a hotspot device management method according to an embodiment of this application. [Figure 6] This is a diagram of a communication device according to an embodiment of this application. [Figure 7] This is a diagram of a communication device according to an embodiment of this application. [Modes for carrying out the invention]

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

[0075] Terminal devices may be user equipment (UE), mobile stations, or mobile terminals. Figure 1 illustrates this using an example where the terminal device is a UE. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices may be mobile phones, tablet computers, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air transport vehicles (such as unmanned aerial vehicles or helicopters), ships, robots, robotic arms, or smart home devices.

[0076] An access network is used to implement access-related functions and can provide network access for authorized users within a specific area. It can transmit user data by determining transmission links of different quality based on user level and service requirements. The access network transfers control signals and user data between terminal devices and the core network. An access network may include access network devices. Access network devices can be devices that provide access for terminal devices and may include radio access network (RAN) devices and wired access network devices. Figure 1 illustrates this using an example where 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 forms of base stations, such as macro base stations, micro base stations (sometimes called small cells), relay stations, access points, and balloon stations. In systems utilizing different radio access technologies, the names of devices with base station functionality may differ. For example, in a 5G system, the device is called a RAN or next-generation node base station (gNB). In a long-term evolution (LTE) system, the device is called an evolved node B (eNB or eNodeB).

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

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

[0079] AMF is primarily responsible for mobility management on mobile networks, including updating user location, registering users to the network, and switching users.

[0080] SMF is primarily responsible for session management in mobile networks, including session establishment, modification, and release. Specific functions include, for example, assigning IP addresses to users or selecting a UPF (Urban Processing Function) to provide packet forwarding capabilities.

[0081] The UPF is responsible for transferring and receiving user data, receiving user data from the data network and transmitting that user data to terminal devices via access network devices. Alternatively, the UPF can receive user data from terminal devices via access network devices and transfer that user data to the data network.

[0082] 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 application service deployed by the operator, such as an IP Multimedia Subsystem (IMS) voice call service.

[0084] The PCF primarily supports providing an integrated policy framework to control network behavior, providing policy rules for control layer network functions, and is also responsible for obtaining user policy decision-related subscription information. The PCF can provide policies such as QoS policies and slice selection policies to the AMF or SMF.

[0085] Multiple services are deployed on the DN, and the DN can provide services such as data services and / or voice services to terminal devices. For example, the DN is a private network of a smart factory, and sensors installed in the smart factory's workshops may be terminal devices, with a sensor control server deployed within the DN, and the control server can provide services to the sensors. The sensors may communicate with the control server to obtain commands from the control server and, based on those commands, transmit collected sensor data to the control server. In another example, the DN is a company's internal office network, and the company's employees' mobile phones or computers may be terminal devices, and the employees' mobile phones or computers may have access to information and data resources on the company's internal office network.

[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 the 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 the interface between the AMF and the terminal device, and may be configured to transmit non-access stratum (NAS) signaling (including QoS rules from the AMF) to the terminal device, etc.

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

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

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

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

[0092] The network element may be a network element within 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 implementations, the network element or the function described above may be implemented by a single device, by multiple devices working together, or by a single functional module within a single device. This is not particularly limited to the embodiments of this application.

[0093] Network sharing technology is also referred to as hotspot sharing technology. This technology allows devices such as laptops, desktop computers, tablets, or other intelligent terminals to access an intelligent terminal with internet access capabilities via wired or wireless connections (e.g., Wi-Fi, Bluetooth®, or USB physical connection) and provide packet data services to devices other than the intelligent terminal with internet access capabilities. For example, network sharing technology may be tethering, and an intelligent terminal providing tethering functionality may be referred to as a tethering user.

[0094] With the proliferation of intelligent terminals equipped with network sharing technology, numerous non-subscribed devices, such as laptops and tablets, may utilize the network sharing technology of these intelligent terminals to access network traffic. Because operators cannot detect terminal devices accessing the network using network sharing technology, they cannot analyze and determine the actual situation of devices utilizing network traffic, and therefore cannot provide better service to users.

[0095] Figure 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] Policy control network elements transmit indication information to user plane network elements. Specifically, policy control network elements may transmit indication information to user plane network elements via session management network elements.

[0099] When this embodiment of the present 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 an 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 application may be further applied to future communication scenarios, such as 6th generation (6G) communication scenarios. This is not limited to the present application. The implementations of the policy control network elements, session management network elements, and user plane network elements are described uniformly here and are not described in detail later.

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

[0103] Step 202a: When the 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 the first event.

[0105] After receiving 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 the first event has occurred. Therefore, the user plane network element sends the first event to the policy control network element, which in turn allows the policy control network element to 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, suppose the hotspot access threshold is 5, and the indication information tells the policy control network element to report when the number of devices accessing terminal device 1 using hotspot sharing technology is 5 or more. Therefore, the user plane network element detects devices accessing terminal device 1 using hotspot sharing technology. When the user plane network element detects that the number of devices accessing terminal device 1 using hotspot sharing technology is 5 or more, it reports to the policy control network element that the number of devices accessing terminal device 1 using hotspot sharing technology is 5 or more.

[0107] In one implementation, before step 202a, the user plane network element receives the hotspot access threshold from the policy control network element; in other words, the policy control network element provides the hotspot access threshold to the user plane network element. The hotspot access threshold and indication information may be sent in the same message or in different messages.

[0108] In other implementations, the indication information includes the hotspot access threshold.

[0109] In other implementations, the user plane network element determines the hotspot access threshold based on the terminal device's service package. In other words, the hotspot access thresholds corresponding to different service packages may be the same or different.

[0110] In other implementations, user plane network elements determine hotspot access thresholds based on configuration information within the user plane network elements.

[0111] In the above solution, the policy control network element instructs the user plane network element to detect the number of devices accessing terminal devices using hotspot sharing technology and to notify the policy control network element when it detects that the number of devices accessing terminal devices using hotspot sharing technology exceeds the hotspot access threshold. Therefore, the policy control network element knows that the number of devices accessing terminal devices using hotspot sharing technology exceeds the hotspot access threshold, and this helps the policy control network element determine the billing or control method for terminal devices, bill appropriately, and control terminal devices effectively.

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

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

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

[0115] After receiving the first event, the policy control network element determines that the number of devices accessing the terminal device using hotspot sharing technology is equal to or greater than the hotspot access threshold, and updates the billing rule to obtain the first billing rule. The policy control network element then sends the first billing rule to the user plane network element, and the user plane network element bills the terminal device according to the first billing rule.

[0116] For example, compared to the billing rule before the update, the first billing rule increases the price per unit of traffic (or the traffic billing rate), or updates previously non-billed services to start billing. The specific implementation method of the billing rule is not limited to this embodiment of the application. In such a method, the billing rule can be effectively configured to appropriately bill terminal devices.

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

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

[0119] After receiving the first event, the policy control network element determines that the number of devices accessing the terminal device using hotspot sharing technology is equal to or greater than the hotspot access threshold, and updates the control policy rule to obtain the first control policy rule. The policy control network element then 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 to the control policy rule before the update, the first control policy rule may limit the device's traffic bandwidth or reduce the device's traffic network speed. The specific implementation method of the control policy rule is not limited to this embodiment of the application. Such a method may enable the control policy rule to be effectively configured to appropriately control the terminal device.

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

[0122] Step 205a: When the 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 hotspot sharing technology is below the hotspot access threshold.

[0125] The second event can be understood as being different from the first event. Specifically, when the number of devices accessing a terminal device using hotspot sharing technology changes—for example, when that number changes from being greater than the hotspot access threshold to being less than or equal to 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 can dynamically sense the change in number and notify the policy control network element of that change in real time, enabling dynamic management of terminal devices.

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

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

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

[0129] After receiving the second event, the policy control network element learns that the number of devices accessing the terminal device using hotspot sharing technology is below the hotspot access threshold, and updates the billing rule to obtain the second billing rule. The policy control network element then sends the second billing rule to the user plane network element, and the user plane network element bills the terminal device according to the second billing rule.

[0130] For example, compared to the previous billing rule, the second billing rule reduces the price per unit of traffic (or the traffic billing rate), or updates previously billed traffic to non-billed traffic. The specific implementation method of the billing rule is not limited to this embodiment of the application. Such a method allows the billing rule to be effectively configured to appropriately bill terminal devices.

[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 learns that the number of devices accessing the terminal device using hotspot sharing technology is below the hotspot access threshold, and updates the control policy rule to obtain the 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 to the control policy rule before the update, 2 Control policy rules apply to the device. Traffic bandwidth This could involve increasing the traffic network speed of the device, for example. The specific implementation method of the control policy rules is not limited to this embodiment of the application. In such a method, the control policy rules can be effectively configured to properly control the terminal device.

[0135] The following describes implementation methods for a user plane network element to detect the number of devices accessing a terminal device using hotspot sharing technology. Methods 1 to 4 below are provided for illustrative purposes only. Implementation methods for a user plane network element to detect the number of devices accessing a terminal device using hotspot sharing technology are not limited in this application.

[0136] Method 1: A user plane network element receives multiple data packets from a terminal device. Each of the multiple data packets contains a timestamp. Based on the timestamp in each of the multiple data packets, the user plane network element determines a reference value for the clock source corresponding to the multiple data packets. Based on the reference value for the clock source corresponding to the multiple data packets, the user plane network element determines the number of devices that will access the terminal device using hotspot sharing technology.

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

[0138] Both the terminal device and other devices accessing the terminal device using hotspot sharing technology include a timestamp within the data packet when sending it, and the timestamp relates to the clock source of the device generating the data packet. Therefore, user plane network elements can determine the reference value of the clock source corresponding to the data packet based on the timestamp in the captured data packet. Since the reference value of the same clock source is the same, the user plane Network elements This allows for determining the number of devices accessing a terminal device using hotspot sharing technology, based on the number of reference values ​​of different types of clock sources. The reference value of a clock source can be understood as the value of the clock source at a reference point in time. The clock sources of different devices will have different values ​​at the same time; in other words, the reference values ​​of the clock sources of different devices will be different.

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

[0140] The following explains the method using an example. For example, UE1 is a device that enables hotspot sharing, and then devices 1, 2, and 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 hotspot sharing technology is 3.

[0141] When UE1 is powered on, the UE1 clock source generates an initial value (represented by initialTimestamp1), for example, 1000. Then, as time passes, the clock source value increases by a fixed value (represented by numinbysec) every second. The value of numinbysec is 1000. For example, the clock source is updated to 2000 1 second after UE1 is powered on, and to 3000 2 seconds after UE1 is powered on, 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), for example, 2000. Then, as time passes, 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 1 second after device 1 is powered on, the clock source is updated to 4000 2 seconds after device 1 is powered on, and so on. When generating a data packet, device 1 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 t3, the value of the clock source of device 1 is timestamp3, and device 1 includes timestamp3 in the data packet. Similarly, at time t4, the value of the clock source of device 1 is timestamp4, and device 1 includes timestamp4 in the data packet, and so on.

[0143] Similarly, devices 2 and 3 also include the corresponding timestamp in their data packets.

[0144] Therefore, data packets received by the user plane network element from UE1, device 1, device 2, or device 3 include timestamps. The user plane network element may perform the function of obtaining timestamps in multiple data packets through sampling at different time points, and then fitting them onto the multiple timestamps obtained through sampling at multiple time points to obtain multiple lines with the same slope. The number of lines represents the total number of devices from which the multiple data packets originate. It can also be understood that different devices represented by the multiple lines obtained through fitting have different initial values. Since the initial values ​​of different devices when they are powered on are random values, the number of initial values ​​can be considered as the number of devices. Figure 2(c) is used as an example. The user plane network element separately obtains multiple data packets through sampling at time points tx and ty, obtains timestamps in the data packets, and then performs fitting on the multiple timestamps obtained through sampling to obtain four lines. Data packets corresponding to the same line are from the same device. Therefore, the four lines indicate that the multiple utilized data packets are from four devices, which are UE1, device 1, device 2, and device 3. Therefore, the user plane network element determines that the number of devices accessing UE1 using hotspot sharing technology is 4-1=3.

[0145] Method 2: A user plane network element determines the number of devices accessing a terminal device using hotspot sharing technology based on the number and / or type of heartbeat messages detected in one or more cycles. Heartbeat messages originate from the terminal device or from devices accessing the terminal device using hotspot sharing technology.

[0146] The operating system of a terminal device (such as iOS, Android, or Windows) periodically sends heartbeat messages to the application server. The terminal device sends these heartbeat messages to a user plane network element, which then forwards them to the application server. Therefore, the user plane network element can detect the terminal device's heartbeat messages.

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

[0148] In one implementation, if different devices send different types of heartbeat messages, a user plane network element may determine the number of devices that access the terminal device using hotspot sharing technology based on the types of heartbeat messages detected in one or more cycles. 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 hotspot sharing technology. If a user plane network element can detect four types of heartbeat messages from terminal device 1 in one or more cycles, the user plane network element determines that the number of devices that access terminal device 1 using hotspot sharing technology is 4-1=3.

[0149] In other implementations, since devices with the same type of operating system installed have the same heartbeat message transmission cycle, the number of heartbeat messages in one cycle 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 sends heartbeat messages according to cycle T1, and a device with the Apple operating system installed sends heartbeat messages according to cycle T2. In this case, the user plane network element may detect the number of heartbeat messages sent by the Android device in one cycle T1, e.g., K1, and the number of heartbeat messages sent by the Apple device in one cycle 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 can be understood that Method 2 and Method 1 may be used simultaneously. For example, when heartbeat message features are detected, multiple data packets with the same features are determined using Method 1. In this way, the number of devices accessing terminal device 1 using hotspot sharing technology can be determined more accurately.

[0151] Method 3: The user plane network element obtains network traffic characteristic parameters corresponding to multiple data packets. Based on the network traffic characteristic parameters, the user plane network element determines the number of devices that can access the terminal device using hotspot sharing technology.

[0152] Hotspot access is essentially network address translation (NAT) behavior. Traffic identification is essentially classifying IP addresses within the network into NAT device IP addresses and common host IP addresses, which is similar to the identification of hotspot sharing behavior. Terminal devices that enable hotspot sharing can be considered NAT devices, while other devices that do not enable hotspot sharing can be considered common hosts. The general idea of ​​the method is to obtain IP addresses within the 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] Next, the user plane network element further determines the number of devices that access the NAT device using hotspot sharing technology. The specific method is as follows: The user plane network element collects data packets, and then, based on a machine learning / depth model, the user plane network element analyzes the network traffic characteristic parameters corresponding to the collected data packets to determine the number of devices that access the terminal device using hotspot sharing technology. The network traffic characteristic parameters corresponding to the data packets include one or more of the data packet's arrival time, IP layer information within the data packet, and Transmission Control Protocol (TCP) layer information within the data packet. The machine learning / depth model is acquired through prior training based on the network traffic characteristic parameters of multiple collected data packets and the label information of the NAT device.

[0154] Method 4: The user plane network element receives multiple HTTP request messages. The HTTP request messages contain device parameters. Based on the device parameters in the multiple HTTP request messages, the user plane network element determines the number of devices that will access the terminal device using hotspot sharing technology.

[0155] When accessing an HTTP service, a device sends an HTTP request message. The UserAgent field in the message header of the HTTP request message carries one or more parameters, such as the device's operating system type, the device's browser type, or the device type. Therefore, a user plane network element can determine, based on the parameters carried in the message header of the HTTP request message, whether that device is one that accesses terminal devices using hotspot sharing technology, and thus determine the number of devices that access terminal devices using hotspot sharing technology.

[0156] Similarly, the methods described above can be used in combination to determine the number of devices that can access a terminal device using hotspot sharing technology. Further details will not be provided again.

[0157] Figure 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 details on the sending action, please refer to the explanation in step 201a.

[0161] The indication information tells the policy control network element to send the updated number of devices when the number of devices accessing a terminal device using hotspot sharing technology changes.

[0162] Step 202b: When the number of devices accessing a terminal device using 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 a terminal device using hotspot sharing technology will change, 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 hotspot sharing technology, and after detecting a change in the number of devices accessing the terminal device using hotspot sharing technology, it instructs the user plane network element to send the changed number of devices to the policy control network element. This helps the policy control network element determine a billing or control method for the terminal device based on the changed number of devices, thereby billing appropriately and effectively controlling the terminal device.

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

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

[0167] In response, the user plane network element receives the billing rule.

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

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

[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 rule.

[0172] After receiving the second number, the policy control network element determines a control policy rule based on the second number. The policy control network element 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, as described in this embodiment of the application, an interval is specified for the number of devices accessing a terminal device using hotspot sharing technology, and control policy rules are configured for each interval. For example, control policy rule 1 is configured when the number of devices is within the interval range of 0 to 2. Control policy rule 2 is configured when the number of devices is within the interval range of 3 to 5, and so on. The specific implementation method of the control policy rules is not limited to this embodiment of the application. In this method, the control policy rules can be effectively configured to appropriately control the terminal device.

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

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

[0176] Figures 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: The terminal device sends a session establishment request message to the session management network element.

[0178] A terminal device is a device that has internet access capabilities and hotspot sharing capabilities. For example, a terminal device is a smartphone.

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

[0180] In 5G, the session establishment request message can be the 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 the PCRF, and the session management network element (i.e., PGW-C) sends policy establishment request messages to the PCRF via the Gx interface between the PGW-C and the PCRF.

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

[0184] In 5G, the policy establishment request message can be the 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 can be the Npcf_SMPolicyControl_Create_Request message.

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

[0189] In one implementation, 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 RAR message includes a hotspot access threshold exceedance report event and the hotspot access threshold.

[0190] The hotspot access threshold exceedance reporting event is a specific example of the indication information in the embodiment shown in Figure 2(a).

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

[0192] In 4G application scenarios, the event trigger field may be expanded in this application, and the range of event trigger values ​​is broadened. For example, the event trigger value TETHERING_EXCEED_NUM_REPORT is newly added. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeding reporting event. Correspondingly, Tethering-Num-Threshold is further added, corresponding to TETHERING_EXCEED_NUM_REPORT. Tethering-Num-Threshold is an example of a hotspot access threshold. When the event trigger value in a 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 other implementations, in 5G application scenarios, the policy establishment response message includes an SmPolicyDecision. Some of the contents of the 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 range of values ​​for policyCtrlReqTriggers is added. For example, the value TETHERING_EXCEED_NUM_REPORT is added to policyCtrlReqTriggers. TETHERING_EXCEED_NUM_REPORT is an example of a hotspot access threshold exceeding reporting 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 session establishment request messages 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 session establishment request messages to the UPF via the N4 interface between the SMF and the UPF.

[0200] In 5G, a session establishment request message can be an N4 session establishment request message.

[0201] The session establishment request message includes the hotspot access threshold exceedance report event and the hotspot access threshold.

[0202] In one implementation, 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 Exceed Reporting Event. Tethering_num_Threshold is an example of a Hotspot Access Threshold.

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

[0204] For an implementation method in which a user plane network element detects the number of devices accessing a terminal device using hotspot sharing technology, please refer to the relevant explanation in the embodiment shown in Figure 2(a). Further details will not be explained 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 can be an N4 session establishment response message.

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

[0208] In 5G, a session report request message can be an N4 session report request message.

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

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

[0211] For example, a session report request message may include Extended Usage Report Triggers, and Extended Usage Report Triggers may include hotspot threshold exceedance events. Step 308: The session management network element sends a policy update request message to the policy control network element.

[0212] In 5G, a policy update request message can be an Npcf_SMPolicyControl_Update_Request message.

[0213] Policy update request messages include events where the hotspot access threshold has been exceeded.

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

[0215] A hotspot access threshold exceeding event received by a policy control network element triggers the policy control network element to determine billing rule 1 and / or control policy rule 1 for the terminal device, according to a pre-configured 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 can be the Npcf_SMPolicyControl_Update_Response message.

[0218] The policy update response message includes billing rule 1 for the terminal device and / or control policy rule 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, a session modification request message can be an N4 session modification request message.

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

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

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

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

[0225] In 5G, a session report request message can be an N4 session report request message.

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

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

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

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

[0230] In 5G, a policy update request message can be an Npcf_SMPolicyControl_Update_Request message.

[0231] Policy update request messages include events where the hotspot access threshold is below the threshold.

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

[0233] A hotspot access threshold below event received by the policy control network element triggers the policy control network element to determine billing rule 2 and / or control policy rule 2 for the terminal device, according to a pre-configured policy or 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 can be the Npcf_SMPolicyControl_Update_Response message.

[0236] The policy update response message includes billing rule 2 for the terminal device and / or control policy rule 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, a session modification request message can be an N4 session modification request message.

[0239] A session correction request message includes a billing rule 2 for the terminal device and / or a control policy rule 2 for the terminal device. In one implementation, the session correction request message includes a PDR, which includes a billing rule 2 for the terminal device and / or a control policy rule 2 for the terminal device.

[0240] Step 318: The user plane network element charges the terminal device according to billing rule 2 for the terminal device, and / or controls the terminal device according to control policy rule 2 for the terminal device.

[0241] In the above solution, the user plane network element can detect the number of devices accessing terminal devices using hotspot sharing technology, and when it detects that the number of devices accessing terminal devices using hotspot sharing technology exceeds the hotspot access threshold, it can report a hotspot access threshold exceeding event and trigger a policy control network element to determine the corresponding billing rule and / or control policy rule. In addition, when it detects that the number of devices accessing terminal devices using hotspot sharing technology is below the hotspot access threshold, the user plane network element can further report a hotspot access threshold below event and trigger a policy control network element to determine the corresponding billing rule and / or control policy rule. Therefore, this solution can accurately bill and effectively control terminal devices.

[0242] It should be noted that steps 303 and 304 may be understood as a specific implementation of step 201a in the embodiment of Figure 2(a), steps 307 and 308 may be understood as a specific implementation of step 202a in the embodiment of Figure 2(a), steps 310 and 311 may be understood as a specific implementation of steps 203a and 204a in the embodiment of Figure 2(a), steps 313 and 314 may be understood as a specific implementation of step 205a in the embodiment of Figure 2(a), and steps 316 and 317 may be understood as a specific implementation of steps 206a and 207a in the embodiment of Figure 2(a). For specific implementations, please refer to the relevant descriptions in the embodiment of Figure 2(a). Further details will not be explained again.

[0243] Figure 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: The terminal device sends a session establishment request message to the session management network element.

[0245] A terminal device is a device that has internet access capabilities and hotspot sharing capabilities. For example, a terminal device is a smartphone.

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

[0247] In 5G, the session establishment request message can 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 the PCRF, and the session management network element (i.e., PGW-C) sends policy establishment request messages to the PCRF via the Gx interface between the PGW-C and the PCRF.

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

[0251] In 5G, the policy establishment request message can be the 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 can be the Npcf_SMPolicyControl_Create_Request message.

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

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

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

[0258] A CCA message is used as an example. A CCA message now includes an event trigger field.

[0259] In 4G application scenarios, the event triggers may be expanded in this application, and the range of event trigger values ​​may be broadened. For example, the event trigger value TETHERING_NUM_REPORT may be newly added. TETHERING_NUM_REPORT is an example of a hotspot access device count reporting event.

[0260] In other implementations, in 5G application scenarios, the policy establishment response message includes an SmPolicyDecision. Some of the contents of the 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 range of values ​​for policyCtrlReqTriggers is added. For example, the value TETHERING_NUM_REPORT is added to policyCtrlReqTriggers. TETHERING_NUM_REPORT is an example of a hotspot access device count 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 session establishment request messages 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 session establishment request messages to the UPF via the N4 interface between the SMF and the UPF.

[0266] In 5G, a session establishment request message can be an N4 session establishment request message.

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

[0268] In one implementation, the session establishment request message includes a URR, which includes an extended reporting trigger. The extended reporting trigger includes a hotspot access device count reporting event.

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

[0270] For an implementation method in which a user plane network element detects the number of devices accessing a terminal device using hotspot sharing technology, please refer to the relevant explanation in the embodiment shown in Figure 2(a). Further details will not be explained 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 can be an N4 session establishment response message.

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

[0274] In 5G, a session report request message can be an N4 session report request message.

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

[0276] In one implementation, a session reporting request message may include an extended usage reporting trigger, which 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, a policy update request message can be an Npcf_SMPolicyControl_Update_Request message.

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

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

[0280] The number of devices accessing the terminal device using hotspot sharing technology, and the number received by the policy control network element, triggers the policy control network element to determine billing rules and / or control policy rules for the terminal device, according to the configured policy or 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 can be the Npcf_SMPolicyControl_Update_Response message.

[0283] The policy update response message includes billing 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 can 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 rules for the terminal device and / or controls the terminal device according to the control policy rules for the terminal device.

[0288] After that, when 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 step 412 are repeatedly executed.

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

[0290] It should be noted that steps 403 and 404 can be understood as specific implementations of step 201b in the embodiment of Figure 2(b), steps 407 and 408 can be understood as specific implementations of step 202b in the embodiment of Figure 2(b), and steps 410 and 411 can be understood as specific implementations of steps 203b and 204b in the embodiment of Figure 2(b). For specific implementations, please refer to the relevant descriptions in the embodiment of Figure 2(b). Further details will not be explained again.

[0291] Figures 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: The terminal device sends a session establishment request message to the session management network element.

[0293] A terminal device is a device that has internet access capabilities and hotspot sharing capabilities. For example, a terminal device is a smartphone.

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

[0295] In 5G, the session establishment request message can 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 the PCRF, and the session management network element (i.e., PGW-C) sends policy establishment request messages to the PCRF via the Gx interface between the PGW-C and the PCRF.

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

[0299] In 5G, the policy establishment request message can be the 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 can be the Npcf_SMPolicyControl_Create_Request message.

[0303] The policy establishment response message includes a hotspot access threshold exceeding reporting event. The hotspot access threshold exceeding reporting event indicates that an event should be reported when the number of devices accessing a terminal device using hotspot sharing technology exceeds the hotspot access threshold.

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

[0305] The hot spot access threshold exceeded report event is a specific example of the 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 the 4G application scenario, in this application, the event trigger may be extended, and the value range of the event trigger is expanded. For example, the value TETHERING_EXCEED_NUM_REPORT of the event trigger is newly added. TETHERING_EXCEED_NUM_REPORT is an example of the hot spot access threshold exceeded report event.

[0308] In other implementation methods, in the 5G application scenario, the policy establishment response message includes SmPolicyDecision. Some of the 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 this application, the value range of policyCtrlReqTriggers is newly added. For example, the value TETHERING_EXCEED_NUM_REPORT of policyCtrlReqTriggers is newly added. TETHERING_EXCEED_NUM_REPORT is an example of the hot spot 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 session establishment request messages 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 session establishment request messages to the UPF via the N4 interface between the SMF and the UPF.

[0314] In 5G, a session establishment request message can be an N4 session establishment request message.

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

[0316] In one implementation, the session establishment request message includes a URR, which includes an extended reporting trigger. The extended reporting trigger includes a hotspot access threshold exceedance reporting event.

[0317] Step 505: User plane network elements initiate hotspot access detection based on hotspot access threshold exceedance reporting events.

[0318] For an implementation method in which a user plane network element detects the number of devices accessing a terminal device using hotspot sharing technology, please refer to the relevant explanation in the embodiment shown in Figure 2(a). Further details will not be explained 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 can be an N4 session establishment response message.

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

[0322] In 5G, a session report request message can 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 a terminal device using hotspot sharing technology exceeds the hotspot access threshold, the user plane network element sends a session report request message to the session management network element. The session report request message includes a hotspot access threshold exceedance event, which indicates that the number of devices accessing a terminal device using hotspot sharing technology exceeds the hotspot access threshold.

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

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

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

[0328] In 5G, a policy update request message can be an Npcf_SMPolicyControl_Update_Request message.

[0329] Policy update request messages include events where the hotspot access threshold has been exceeded.

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

[0331] A hotspot access threshold exceeding event received by a policy control network element triggers the policy control network element to determine billing rule 1 and / or control policy rule 1 for the terminal device, according to a pre-configured 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 can be the Npcf_SMPolicyControl_Update_Response message.

[0334] The policy update response message includes billing 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, a session modification request message can be an N4 session modification request message.

[0337] A session correction request message includes billing rule 1 and / or control policy rule 1 for the terminal device. In one implementation, the session correction request message includes a PDR, which includes billing 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 billing 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 a user plane network element detects that the number of devices accessing a terminal device using hotspot sharing technology changes from exceeding the hotspot access threshold to falling below the hotspot access threshold, steps 513 to 518 may be performed.

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

[0341] In 5G, a session report request message can be an N4 session report request message.

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

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

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

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

[0346] In 5G, a policy update request message can be an Npcf_SMPolicyControl_Update_Request message.

[0347] Policy update request messages include events where the hotspot access threshold is below the threshold.

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

[0349] A hotspot access threshold below event received by the policy control network element triggers the policy control network element to determine billing rule 2 and / or control policy rule 2 for the terminal device, according to a pre-configured policy or 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 can be the Npcf_SMPolicyControl_Update_Response message.

[0352] The policy update response message includes billing rule 2 and / or control policy rule 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, a session modification request message can be an N4 session modification request message.

[0355] A session correction request message includes billing rule 2 and / or control policy rule 2 for the terminal device. In one implementation, the session correction request message includes a PDR, which includes billing 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 billing rule 2 for the terminal device, and / or controls the terminal device according to control policy rule 2 for the terminal device.

[0357] In the above solution, the user plane network element can detect the number of devices accessing terminal devices using hotspot sharing technology, and when it detects that the number of devices accessing terminal devices using hotspot sharing technology exceeds the hotspot access threshold, it can report a hotspot access threshold exceeding event and trigger a policy control network element to determine the corresponding billing rule and / or control policy rule. In addition, when it detects that the number of devices accessing terminal devices using hotspot sharing technology is below the hotspot access threshold, the user plane network element can further report a hotspot access threshold below event and trigger a policy control network element to determine the corresponding billing rule and / or control policy rule. Therefore, this solution can accurately bill and effectively control terminal devices.

[0358] It should be noted that steps 503 and 504 may be understood as a specific implementation of step 201a in the embodiment of Figure 2(a), steps 507 and 508 may be understood as a specific implementation of step 202a in the embodiment of Figure 2(a), steps 510 and 511 may be understood as a specific implementation of steps 203a and 204a in the embodiment of Figure 2(a), steps 513 and 514 may be understood as a specific implementation of step 205a in the embodiment of Figure 2(a), and steps 516 and 517 may be understood as a specific implementation of steps 206a and 207a in the embodiment of Figure 2(a). For specific implementations, please refer to the relevant descriptions in the embodiment of Figure 2(a). Further details will not be explained again.

[0359] To implement the functions in the embodiments described above, it can be understood that the user plane network element or policy control network element includes a corresponding hardware structure and / or software module for performing each function. Those skilled in the art will readily notice that, in this application, the units and method steps in the examples described in relation to the embodiments disclosed herein can be implemented by hardware, or by 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] Figures 6 and 7 illustrate the structure of possible communication devices according to embodiments of this application. These communication devices may be configured to implement the functions of user plane network elements or policy control network elements in the method embodiments described above, and thus can also implement the advantageous effects of the method embodiments described above. In this embodiment of this application, the communication device may be a user plane network element or a policy control network element, or it may be a module (e.g., a chip) used in a policy control network element or a module (e.g., a chip) used in a user plane network element.

[0361] As shown in Figure 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 the user plane network element or policy control network element in the method embodiment described above.

[0362] When the communication device 600 is configured to implement the functions of the user plane network element in the embodiments of Figures 2(a), 3(a), and 3(b), or Figures 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 that when a first event occurs, the policy control network element should send a first event. The first event is that the number of devices accessing a terminal device using hotspot sharing technology is equal to or greater than the hotspot access threshold. When the first event occurs, the first event is sent to the policy control network element.

[0363] In possible implementations, the transceiver unit 620 is configured to receive the hotspot access threshold from a policy-controlled network element, or the indication information includes the hotspot access threshold.

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

[0365] In a possible implementation, the transceiver unit 620 is configured to receive a first billing rule from a policy-controlled network element. The first billing rule is determined based on a first event. The processing unit 610 is configured to bill terminal devices according to the first billing 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 is determined based on a first event. The processing unit 610 is configured to control terminal devices according to the first control policy rule.

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

[0368] In a possible implementation, the transceiver unit 620 is configured to receive a second billing rule from a policy-controlled network element. The second billing rule is determined based on a second event. The processing unit 610 is configured to bill terminal devices according to the second billing rule.

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

[0370] In a possible implementation, the transceiver unit 620 is configured to receive multiple data packets from a terminal device. Each of the multiple data packets includes a timestamp. The processing unit 610 is configured to determine a reference value for a clock source corresponding to the multiple data packets based on the timestamp in each of the multiple data packets, and to determine the number of devices that access the terminal device using hotspot sharing technology based on the reference value for the clock source corresponding to the multiple data packets.

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

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

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

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

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

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

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

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

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

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

[0381] When the communication device 600 is configured to implement the functions of the user plane network element in the embodiment shown in Figure 2(b) or Figure 4, the transceiver unit 620 is configured to receive indication information from the policy control network element. The indication information tells the policy control network element to send the changed number of devices when the number of devices accessing the terminal device using the hotspot sharing technology changes. 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 billing rules from a policy-controlled network element. The billing rules are determined based on a second number. The processing unit 610 is configured to bill terminal devices according to the billing rules.

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

[0384] In a possible implementation, the transceiver unit 620 is configured to receive multiple data packets from a terminal device. Each of the multiple data packets includes a timestamp. The processing unit 610 is configured to determine a reference value for a clock source corresponding to the multiple data packets based on the timestamp in each of the multiple data packets, and to determine the number of devices that access the terminal device using hotspot sharing technology based on the reference value for the clock source corresponding to the multiple data packets.

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

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

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

[0388] When the communication device 600 is configured to implement the functions of the policy control network element in the embodiment shown in Figure 2(b) or Figure 4, the transceiver unit 620 is configured to transmit indication information to the user plane network element. The indication information tells the policy control network element to transmit the changed number of devices when the number of devices accessing the terminal device using the hotspot sharing technology changes. 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, the processing unit 610 is configured to determine a billing rule based on a second number. The transceiver unit 620 is configured to transmit the billing rule to the user plane network element.

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

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

[0392] As shown in Figure 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 can 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 requested by the processor 710 to execute the instructions, or data generated after the processor 710 has executed the instructions.

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

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

[0395] Those skilled in the art will understand that the various numbers in this application, such as "first" and "second," are used merely to indicate differences for the sake of clarity and are not intended to limit the scope of the embodiments of this application or to indicate an order. The term "and / or" describes an association relationship for describing related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: that only A exists, that both A and B exist, and that 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 a similar expression means any combination of items, including one item (piece) or any combination of multiple items (pieces). For example, at least one item (piece) among a, b, or c can represent 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. "Multiple" means two or more, and other quantifiers are similar.

[0396] The sequence numbers of the processes described above should be understood not to imply the order of execution in the various embodiments of this application. The order of execution of the processes should be determined based on the function and internal logic of the processes and should not be interpreted as any limitation on the implementation process of the embodiments of this application.

[0397] For the purpose of a convenient and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the above systems, apparatuses, and units should be described by referring to the corresponding processes in the above-described method embodiments. Further details will not be described again here.

[0398] Some or all of the embodiments described above may be implemented 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. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated 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, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wireless means (e.g., infrared, radio waves, or microwaves). Computer-readable storage media may be any available media accessible by a computer, or a data storage device that integrates one or more available media, such as a server or data center. Available media 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 embodiments of this application may be implemented or made to work 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. The general-purpose processor may be a microprocessor. Optionally, the general-purpose processor may be alternatively any conventional processor, controller, microcontroller, or state machine. The 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 digital signal processor cores, or any other similar configuration.

[0400] Steps of the methods or algorithms described in embodiments of this application may be directly incorporated into hardware, software units executed by a processor, or a combination thereof. The software units may be stored in removable disks in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disk drives, or any other form of storage medium in the art. For example, the storage medium may be connected to a processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium may be integrated into the processor. The processor and storage medium may be located within an ASIC.

[0401] These computer program instructions may also be loaded onto a computer or other programmable data processing device, so that a series of operations and steps are executed on the computer or other programmable device to generate the processing performed on the computer. Thus, the instructions executed on the computer or other programmable device provide steps to realize a particular function in one or more processes in a flowchart and / or one or more blocks in a block diagram.

[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. Where software is used for implementation, these functions may be stored in a computer-readable storage medium or transmitted to a computer-readable storage medium in the form of one or more instructions or codes. The computer-readable storage medium includes a computer storage medium and a communication medium that enables the movement of computer programs from one place to another. The storage medium may be any available medium that can be accessed by any general-purpose or specialized computer. For example, the computer-readable storage medium may include, but is 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, the program code in the form of instructions or data structures, or in a form that can be read by a general-purpose or specialized computer or general-purpose or specialized processor. In addition, any connection may be appropriately defined as a computer-readable storage medium. For example, if software is transmitted from a website, server, or other remote resource using coaxial cable, fiber optic computer, twisted pair, digital subscriber line, or wireless means such as infrared, radio waves, or microwaves, the software is included in a defined computer-readable storage medium. Disks and discs include compact discs, laser discs, optical discs, digital versatile discs, floppy disks, and Blu-ray discs. Disks generally copy data by magnetic means, and discs generally copy data optically by laser means. Any combination of the above may also be included in a computer-readable storage medium.

[0403] Those skilled in the art should notice that in one or more of the above examples, the functions described in this application may be implemented by hardware, software, firmware, or any combination thereof. When software is used for implementation, the above functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes in a computer-readable medium. The computer-readable medium includes computer storage media and communication media, the communication medium including any medium that enables computer programs to be transmitted from one place to another. The storage medium may be any available medium accessible to a general-purpose or dedicated computer.

[0404] The specific implementation described above further elaborates on the purpose, technical solution, and advantageous effects of this application. It should be understood that the above description is merely a specific implementation of this application and is not intended to limit the scope of protection. Any modifications, equivalent substitutions, or improvements made based on the technical solution of this application should remain within the scope of protection. In accordance with the above description of this specification in this application, art in the art can utilize or practice the contents of this application. Any modifications based on the disclosed contents should be considered limited in the art. The basic principles described in this application can be applied to other modifications without departing from the essence and scope of this application. Therefore, the contents disclosed in this application are not limited to the described embodiments and designs and may be extended to the maximum extent that is not inconsistent with the principles and new features disclosed in this application.

[0405] While this application is described in relation to specific features and embodiments thereof, it is clear that various modifications and combinations can be made thereto without departing from the idea and scope of this application. Accordingly, the specification and accompanying drawings are merely illustrative descriptions of this application as defined by the attached claims and should be considered any or all modifications, variations, combinations or equivalents that cover the scope of this application. It is clear to those skilled in the art that various modifications and variations can be made to this application without departing from the scope of this application. Therefore, this application is intended to cover these modifications and variations that are of this application, as long as they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims

1. A user plane network element receives indication information from a policy control network element, wherein the indication information indicates that a first event should be sent to the policy control network element when a first event occurs, and the first event is that the number of devices accessing a terminal device using hotspot sharing technology is equal to or greater than a hotspot access threshold. When the first event occurs, the user plane network element transmits the first event to the policy control network element. A method for managing hotspot devices, including...

2. The method described above is The user plane network element further includes the step of receiving the hotspot access threshold from the policy control network element, or The indication information includes the hotspot access threshold, The method according to claim 1.

3. The aforementioned 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 the configuration information in the user plane network element. Further including, The method according to claim 1.

4. The aforementioned method, The steps include: receiving a first billing rule from the policy control network element via the user plane network element, wherein the first billing rule is determined based on the first event; The user plane network element charges the terminal device according to the first billing rule. Further including, The method according to any one of claims 1 to 3.

5. The aforementioned method, The steps include: receiving a first control policy rule from a policy control network element via the user plane network element, wherein the first control policy rule is determined based on the first event; The steps include: controlling the terminal device according to the first control policy rule using the user plane network element; Further including, The method according to any one of claims 1 to 3.

6. The aforementioned method, When a second event occurs, the user plane network element transmits the second event to the policy control network element, further comprising the step that the second event indicates 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 3.

7. The aforementioned method, The steps include: receiving a second billing rule from the policy control network element via the user plane network element, wherein the second billing rule is determined based on the second event; The user plane network element charges the terminal device according to the second billing rule. Further including, The method according to claim 6.

8. The aforementioned method, The steps include: receiving a second control policy rule from a policy control network element via the user plane network element, wherein the second control policy rule is determined based on the second event; The user plane network element controls the terminal device in accordance with the second control policy rule. Further including, The method according to claim 6.

9. The aforementioned method, The user plane network element receives a plurality of data packets from the terminal device, each of which includes a timestamp. The user plane network element determines a reference value for a clock source corresponding to each of the plurality of data packets based on the timestamp in each of the plurality of data packets. The user plane network element determines, based on the reference value of the clock source corresponding to the plurality of data packets, the number of devices that access the terminal device using the hotspot sharing technology. Further including, The method according to any one of claims 1 to 3.

10. The aforementioned method, A user plane network element determines, based on the number and / or type of heartbeat messages detected in one or more cycles, the number of devices accessing the terminal device using the hotspot sharing technology, further comprising the step of determining the number of devices accessing the terminal device using the hotspot sharing technology, wherein the heartbeat messages are from the terminal device or from devices accessing the terminal device using the hotspot sharing technology. The method according to any one of claims 1 to 3.

11. The aforementioned method, The user plane network element obtains network traffic characteristic parameters corresponding to multiple data packets, The user plane network element determines the number of devices that access the terminal device using the hotspot sharing technology based on the network traffic characteristic parameters. Further including, The method according to any one of claims 1 to 3.

12. The aforementioned method, The steps include: obtaining a plurality of Hypertext Transfer Protocol (HTTP) request messages using the user plane network element, wherein the HTTP request messages include device parameters; The user plane network element determines, based on the device parameters in the plurality of HTTP request messages, the number of devices that access the terminal device using the hotspot sharing technology. Further including, The method according to any one of claims 1 to 3.

13. A step of transmitting indication information to a user plane network element via a policy control network element, wherein the indication information indicates that a first event should be transmitted to the policy control network element when a first event occurs, and the first event is that the number of devices accessing a terminal device using 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. A method for managing hotspot devices, including...

14. The method described above is The policy control network element further includes the step of transmitting the hotspot access threshold to the user plane network element, or The indication information includes the hotspot access threshold, The method according to claim 13.

15. The aforementioned method, The steps include: determining a first billing rule based on the first event using the policy control network element, wherein the first billing rule is used to charge the terminal device; The policy control network element transmits the first billing rule to the user plane network element. Further including, The method according to claim 13.

16. The aforementioned method, The steps include: determining a first control policy rule based on the first event using the policy control network element, wherein the first control policy rule is used to control the terminal device; The policy control network element transmits the first control policy rule to the user plane network element. Further including, The method according to any one of claims 13 to 15.

17. The aforementioned method, The policy control network element receives a second event from the user plane network element, the second event further comprising the step of 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 15.

18. The aforementioned method, The steps include: determining a second billing rule based on the second event using the policy control network element, wherein the second billing rule is used to charge the terminal device; The policy control network element transmits the second billing rule to the user plane network element. Further including, The method according to claim 17.

19. The aforementioned method, The steps include: determining a second control policy rule based on the second event using the policy control network element, wherein the second control policy rule is used to control the terminal device; The policy control network element transmits the second control policy rule to the user plane network element. Further including, The method according to claim 17.

20. A user plane network element receives indication information from a policy control network element, wherein the indication information indicates that when the number of devices accessing a terminal device using 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 user plane network element transmits the second number to the policy control network element. A method for managing hotspot devices, including...

21. The aforementioned method, The steps include: receiving a billing rule from the policy control network element via the user plane network element, wherein the billing rule is determined based on the second number; The user plane network element charges the terminal device according to the billing rules. Further including, The method according to claim 20.

22. The aforementioned method, The user plane network element receives a control policy rule from the policy control network element, wherein the control policy rule is determined based on the second number. The steps include: controlling the terminal device in accordance with the control policy rules using the user plane network element; Further including, The method according to claim 20 or 21.

23. A step of a policy control network element transmitting indication information to a user plane network element, wherein the indication information indicates that when the number of devices accessing a terminal device using hotspot sharing technology changes, the policy control network element should transmit the changed number of devices. 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. A method for managing hotspot devices, including...

24. The aforementioned method, The steps include: determining a billing rule based on the second number using the policy control network element, wherein the billing rule is used to charge the terminal device; The policy control network element transmits the billing rule to the user plane network element. Further including, The method according to claim 23.

25. The aforementioned method, The steps include: determining a control policy rule based on the second number using the policy control network element, wherein the control policy rule is used to control the terminal device; The policy control network element transmits the control policy rule to the user plane network element. Further including, The method according to 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 another communication device other than the communication device and transmit the signal to the processor, or to transmit a signal from the processor to another communication device other than the communication device, and the processor is configured to carry out the method according to any one of claims 1 to 3, 20, or 21 by utilizing logic circuits or by executing code instructions.

27. ​​A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive a signal from another communication device other than the communication device and transmit the signal to the processor, or to transmit a signal from the processor to another communication device other than the communication device, and the processor is configured to carry out the method according to any one of claims 13 to 15, 23, or 24 by utilizing logic circuits or by executing code instructions.

28. A computer program wherein, when the computer program is executed by a communication device, the method described in any one of claims 1 to 3, 20, or 21 is performed.

29. A computer program wherein, when the computer program is executed by a communication device, the method described in any one of claims 13 to 15, 23, or 24 is performed.

30. A computer-readable storage medium, wherein the storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 3, 20, or 21 is performed.

31. A computer-readable storage medium, wherein the storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 13 to 15, 23, or 24 is performed.

32. A communication system comprising a user plane network element configured to perform the method described in any one of claims 1 to 3, and a policy control network element configured to perform the method described in any one of claims 13 to 15.

33. A communication system comprising a user plane network element configured to perform the method described in claim 20 or 21, and a policy control network element configured to perform the method described in claim 23 or 24.

Images