Equipment access quantity control method and related device
By restricting the allocation of IP addresses in the first network element and responding according to the identification of the network to which the device belongs, the network congestion problem caused by the increase of IoT devices is solved and the user experience is improved.
Patent Information
- Application Number
- CN202310506388.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-05
- Publication Date
- 2024-11-05
AI Technical Summary
With the increase of IoT devices, network congestion problems are becoming increasingly serious, resulting in poor user experience and it is difficult for the existing technology to effectively alleviate it.
By limiting the number of IP addresses allocated in the first network element (such as SMF, UPF, UDM), responding according to the identification of the network to which the device belongs, deciding whether to allocate an IP address or reject a request, thereby controlling the number of device access and alleviating network congestion .
It effectively alleviates network congestion, improves user experience, and controls device access by limiting the number of IP addresses, and ensures network performance.
Smart Images

Figure CN118900469A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method for controlling the number of device accesses and related devices. Background Art
[0002] With the development of Internet of Things technology, various types of terminal devices emerge in an endless stream. In the future, more and more terminal devices will be connected to the Internet, which will easily cause network congestion and poor user experience. Summary of the invention
[0003] The present application provides a method and related apparatus for controlling the number of device accesses, which can alleviate network congestion and improve user experience.
[0004] In the first aspect, the present application provides a method for controlling the number of device accesses, which is executed by a first network element, and the first network element may be an SMF, UPF, or UDM. Optionally, the first network element may also be a module in the SMF, UPF, or UDM. In the method, a first request is received from a first device, and the first request is used to request the allocation of an IP address, and the first request includes a first network identifier of a first network to which the first device belongs. A first response is sent to the first device according to a first quantity, and the first quantity is the maximum number of IP addresses allowed to be allocated to the first network. The first response includes the allocated IP address, or the first response is used to reject the first request.
[0005] In the present application, the first network element determines whether to allocate an IP address to the first device based on the first quantity, so that the network side can control the devices (such as printers, wearable devices, etc.) that access the first network through the first device, that is, by limiting the number of allocated IP addresses to alleviate network congestion, which is conducive to improving user experience.
[0006] In a possible implementation, sending a first response to the first device according to the first quantity includes:
[0007] sending a first response to the first device according to the first number and a second number, the second number being the number of IP addresses allocated to the first network;
[0008] When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request.
[0009] In this implementation, when the number of IP addresses allocated to the first network is greater than or equal to the maximum number of IP addresses that the first network is allowed to allocate, the first request is rejected; when the number of IP addresses allocated to the first network is less than the maximum number of IP addresses that the first network is allowed to allocate, an IP address is allocated to the first network, thereby alleviating network congestion.
[0010] In a possible implementation, when the communication device is an SMF or a module in the SMF, the method further includes:
[0011] Receiving the first network identifier from AMF;
[0012] Sending a subscription data acquisition request to the UDM, where the subscription data acquisition request includes the first network identifier;
[0013] Receive subscription data corresponding to the first network identifier from the UDM, the subscription data including the first quantity.
[0014] In this implementation, the first number can be carried in the contract data to be sent to the SMF, so that the SMF can subsequently determine whether to allocate an IP address to the first device based on the first number.
[0015] In a possible implementation, when the communication device is an SMF or a module in the SMF, the first response includes the allocated IP address; after sending the first response to the first device according to the first quantity, the method further includes:
[0016] Receiving a NAT translation check result from the UPF;
[0017] Determine whether to reject the PDU session corresponding to the first device according to the NAT conversion check result.
[0018] In this implementation, in order to further limit the number of devices accessing the network, UPF is also required to perform NAT conversion check on the data packet sent by the first device. If the IP address in the data packet sent by the first device cannot pass the NAT conversion check, it means that the IP address in the data packet has undergone NAT address conversion. Therefore, UPF can send the NAT conversion check result to SMF, and SMF will reject the PDU session corresponding to the first device, which can also alleviate network congestion and help improve user experience.
[0019] In a possible implementation, when the communication device is an SMF or a module in the SMF, the method further includes:
[0020] A first indication message is sent to the user plane function UPF, wherein the first indication message instructs the UPF to perform a NAT conversion check on the received data packet.
[0021] Optionally, the first indication information may be carried in the N4 session request.
[0022] In a possible implementation, when the communication device is an SMF or a module in the SMF, the method further includes:
[0023] The first amount is sent to the first device.
[0024] In this implementation method, SMF can also send a first number to the first device so that when the first device subsequently sends a first request, it will first determine the relationship between the number of devices currently successfully connected and the first number. Only when the number of devices successfully connected is less than the first number, will the first request be sent to SMF, thereby realizing the first device side's control over the number of access devices in the first network.
[0025] In a possible implementation, when the communication device is a UPF or a module in a UPF, the method further includes:
[0026] Receive the first network identifier and the first quantity from the SMF.
[0027] In this implementation mode, the SMF sends the first network identifier and the first quantity to the UPF, so that the UPF can determine whether to allocate an IP address to the first device based on the first quantity.
[0028] In a possible implementation, when the communication device is a UPF or a module in a UPF, the first response includes an allocated IP address; after sending the first response to the first device according to the first quantity, the method further includes:
[0029] receiving a data packet from the first device;
[0030] Perform a NAT conversion check on the IP address included in the data packet, and send the NAT conversion check result to the SMF.
[0031] In this implementation, in order to further limit the number of devices accessing the network, UPF is also required to perform NAT conversion check on the data packet sent by the first device. If the IP address in the data packet sent by the first device cannot pass the NAT conversion check, it means that the IP address in the data packet has undergone NAT address conversion. Therefore, UPF can send the NAT conversion check result to SMF, and SMF will reject the PDU session corresponding to the first device, which can also alleviate network congestion and help improve user experience.
[0032] In a possible implementation, when the communication device is a UPF or a module in a UPF, the method further includes:
[0033] Receive first indication information from SMF, wherein the first indication information instructs the UPF to perform NAT conversion check on the received data packets.
[0034] Optionally, the first indication information may be carried in the N4 session request.
[0035] In a second aspect, the present application provides a method for controlling the number of device accesses, which is performed by a first device or a module in the first device. In the method, a first request is sent, the first request is used to request the allocation of an Internet Protocol IP address, and the first request includes a first network identifier of a first network to which the first device belongs. A first response is received, the first response includes the allocated IP address, or the first response is used to reject the first request.
[0036] In a possible implementation, the method further includes:
[0037] receiving a first quantity from the SMF;
[0038] The sending of the first request comprises:
[0039] When a second number is less than the first number, a first request is sent, wherein the second number is the number of IP addresses allocated to the first network.
[0040] In a third aspect, the present application provides a method for controlling the number of device accesses, in which a first device sends a first request to a first network element, the first request being used to request allocation of an IP address, and the first request including a first network identifier of a first network to which the first device belongs. The first network element sends a first response to the first device according to a first number, the first number being the maximum number of IP addresses allowed to be allocated to the first network. The first response includes the allocated IP address, or the first response is used to reject the first request.
[0041] In a possible implementation, the first network element sending a first response to the first device according to the first quantity includes:
[0042] The first network element sends a first response to the first device according to the first number and a second number, where the second number is the number of IP addresses allocated to the first network;
[0043] When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request.
[0044] In a possible implementation, the method further includes:
[0045] The AMF sends the first network identifier to the SMF;
[0046] The SMF sends a subscription data acquisition request to the UDM, where the subscription data acquisition request includes the first network identifier;
[0047] The UDM sends the subscription data corresponding to the first network identifier to the SMF, where the subscription data includes the first quantity.
[0048] In a possible implementation, the first network element is a user plane function UPF; and the method further includes:
[0049] The SMF sends the first network identifier and the first quantity to the UPF.
[0050] In a possible implementation, the first response includes an allocated IP address; and the method further includes:
[0051] The first device sends a data packet to the UPF;
[0052] The UPF performs a NAT conversion check on the IP address included in the data packet and sends the NAT conversion check result to the SMF;
[0053] The SMF determines whether to reject the PDU session corresponding to the first device according to the NAT conversion check result.
[0054] In a possible implementation, the method further includes:
[0055] The SMF sends a first indication message to the UPF, wherein the first indication message instructs the UPF to perform a NAT conversion check on the received data packets.
[0056] In a possible implementation, the method further includes:
[0057] The SMF sends the first quantity to the first device;
[0058] The first device sending a first request to the first network element includes:
[0059] When the second number is less than the first number, the first device sends a first request to the first network element, and the second number is the number of IP addresses allocated to the first network.
[0060] In a fourth aspect, the present application provides a device for controlling the number of device accesses, which may be a communication device, which may be an SMF or a UPF. Optionally, the communication device may also be a module in the SMF or the UPF. The device includes: a transceiver unit, which is used to receive a first request from a first device, wherein the first request includes a first network identifier of a first network to which the first device belongs. A processing unit, which is used to determine a first response based on a first quantity. The transceiver unit is used to send a first response to the first device, wherein the first quantity is the maximum number of IP addresses allowed to be allocated to the first network. The first response includes an allocated IP address, or the first response is used to reject the first request.
[0061] In a possible implementation, when sending the first response to the first device according to the first quantity, the processing unit is configured to:
[0062] sending a first response to the first device according to the first number and a second number, the second number being the number of IP addresses allocated to the first network;
[0063] When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request.
[0064] In a possible implementation, when the communication device is an SMF or a module in the SMF, the transceiver unit is further used to:
[0065] Receiving the first network identifier from AMF;
[0066] Sending a subscription data acquisition request to the UDM, where the subscription data acquisition request includes the first network identifier;
[0067] Receive subscription data corresponding to the first network identifier from the UDM, the subscription data including the first quantity.
[0068] In one possible implementation, when the communication device is SMF or a module in SMF, the first response includes an assigned IP address; after sending the first response to the first device according to the first quantity, the transceiver unit is also used to receive the NAT conversion check result from the UPF; the processing unit is used to determine whether to reject the PDU session corresponding to the first device based on the NAT conversion check result.
[0069] In a possible implementation, when the communication device is an SMF or a module in the SMF, the transceiver unit is further used to:
[0070] A first indication message is sent to the user plane function UPF, wherein the first indication message instructs the UPF to perform a NAT conversion check on the received data packet.
[0071] Optionally, the first indication information may be carried in the N4 session request.
[0072] In a possible implementation, when the communication device is an SMF or a module in the SMF, the transceiver unit is further used to:
[0073] The first amount is sent to the first device.
[0074] In a possible implementation, when the communication device is a UPF or a module in a UPF, the transceiver unit is further used to:
[0075] Receive the first network identifier and the first quantity from the SMF.
[0076] In one possible implementation, when the communication device is UPF or a module in UPF, the first response includes an assigned IP address; after sending the first response to the first device according to the first quantity, the transceiver unit is also used to receive a data packet from the first device; the processing unit is used to perform a NAT conversion check on the IP address included in the data packet; the transceiver unit is used to send the NAT conversion check result to the SMF.
[0077] In a possible implementation, when the communication device is a UPF or a module in a UPF, the transceiver unit is further used to:
[0078] Receive first indication information from SMF, wherein the first indication information instructs the UPF to perform NAT conversion check on the received data packets.
[0079] Optionally, the first indication information may be carried in the N4 session request.
[0080] In a fifth aspect, the present application provides a device for controlling the number of device accesses, which is a communication device, which may be a first device, and optionally, may also be a module in the first device. The device includes: a transceiver unit, which is used to send a first request to an SMF or to a unified data management function UPF, wherein the first request includes a first network identifier of a first network to which the first device belongs. The transceiver unit is used to receive a first response from the SMF or the UPF, wherein the first response includes an assigned IP address, or the first response is used to reject the first request.
[0081] In a possible implementation, the transceiver unit is further used for:
[0082] receiving a first quantity from the SMF;
[0083] When sending the first request to the SMF or to the UPF, the transceiver unit is used for:
[0084] When the second number is less than the first number, a first request is sent to the SMF or to the UPF, wherein the second number is the number of IP addresses allocated to the first network.
[0085] In a sixth aspect, the present application provides a communication device, which includes a processor, a transceiver and a memory, wherein the processor, the transceiver and the memory are coupled, and a computer program is stored in the memory; the processor and the transceiver are used to call the computer program in the memory so that the communication device executes any method in the first aspect or the third aspect.
[0086] In one possible design, the communication device may be a chip that implements the above method or a device including a chip.
[0087] In the seventh aspect, the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement any method as in the first aspect or the third aspect through logic circuits or execution code instructions.
[0088] In an eighth aspect, the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, any method in the first aspect or the third aspect is implemented.
[0089] In a ninth aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes any one of the methods in the first aspect or the third aspect.
[0090] In the tenth aspect, the present application provides a communication system, which includes a first device and a first network element, and the first network element may be an SMF, an UPF or an UDM, wherein the first network element is used to execute any one of the methods in the above-mentioned first aspect, and the first device is used to execute any one of the methods in the above-mentioned second aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0091] Figure 1 It is a schematic diagram of the architecture of a communication system;
[0092] Figure 2 It is a schematic diagram of the architecture of another communication system;
[0093] Figure 3This is a flow chart of a method for controlling the number of device accesses provided in an embodiment of the present application;
[0094] Figure 4 This is another flow chart of the method for controlling the number of device accesses provided in an embodiment of the present application;
[0095] Figure 5 It is a schematic diagram of the process of allocating IPv4 addresses by SMF provided in an embodiment of the present application;
[0096] Figure 6 It is a schematic diagram of the source of the contract data in the UDM provided in the embodiment of the present application;
[0097] Figure 7 This is another flow chart of the method for controlling the number of device accesses provided in an embodiment of the present application;
[0098] Figure 8 This is another flow chart of the method for controlling the number of device accesses provided in an embodiment of the present application;
[0099] Fig. 9 This is another flow chart of the method for controlling the number of device accesses provided in an embodiment of the present application;
[0100] Fig.10 This is another flow chart of the method for controlling the number of device accesses provided in an embodiment of the present application;
[0101] Fig.11 is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application;
[0102] Fig.12 It is a schematic diagram of the structure of a possible communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0103] The specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.
[0104] The terms "first" and "second" and the like in the specification, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.
[0105] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0106] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0107] It should be noted that the first network involved in the present application can also be described as a personal IoT network (PIN), wherein the identifier used to identify the first network is referred to as the first network identifier. When the first network is a PIN network, the first network identifier can also be described as a PIN identifier. The PIN network can be a device group consisting of one or more PEGCs and one or more PIN devices (PIN element, PINE), and the network side can manage the device group with PIN as the granularity. The first device involved in the present application can also be described as a PIN network element (PIN elementgateway capability, PEGC), wherein one or more PINEs in the PIN can access the network side through one or more PEGCs, that is, PEGC can be understood as a gateway with terminal functions.
[0108] In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:
[0109] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), new radio (NR) and other fifth generation (5G) systems, sixth generation (6G) systems and other systems evolved after 5G, wireless local area networks (WLAN), etc., without limitation.
[0110] See also Figure 1 , Figure 1 It is a schematic diagram of the architecture of a communication system. Figure 1 As shown, the terminal devices (or PINEs, or smart devices, or IoT terminals, etc.) in the personal IoT network (PIN) can be accessed to the mobile communication network through PEGC to communicate with other devices through the mobile communication network or access services on the Internet. The mobile communication network includes a (radio) access network ((radio) access network, (R) AN) and a core network (CN), wherein the (R) AN (hereinafter described as RAN) is used to access the terminal device to the wireless network, and the CN is used to manage the terminal device. PIN can be a device group consisting of a group of devices, and the network side can perform unified quality of service (QoS) management and control, contract data, and control policy parameter issuance on the device group at the granularity of PIN. Generally speaking, the PINE in the PIN can be specifically accessed to the mobile communication network through PEGC.
[0111] The following are Figure 1 The terminal equipment, RAN and CN involved in the system architecture are described in detail.
[0112] 1. Terminal equipment
[0113] The terminal device in this application is PINE. The terminal device includes a device that provides voice and / or data connectivity to the user. For example, the terminal device is a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of this application do not limit the application scenarios. Terminal equipment may also be sometimes referred to as terminal, user equipment (UE), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE agent or UE device, etc. The terminal may also be fixed or mobile. It is understood that some or all of the functions of the terminal in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).
[0114] In addition, the terminal device can also be: wearable device, which is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring. For example, smart watches, smart bracelets, pedometers, etc. Vehicle-mounted equipment (e.g., automobiles, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, smart home equipment (e.g., refrigerators, televisions, air conditioners, electric meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, flight equipment (e.g., intelligent robots, hot air balloons, drones, airplanes), etc. In this application, for the sake of ease of description, chips deployed in the above-mentioned devices, such as system-on-a-chip (SOC), baseband chips, etc., or other chips with communication functions can also be referred to as terminal devices.
[0115] 2. RAN
[0116] The RAN may include one or more RAN devices (or access network devices), and the interface between the access network device and the terminal device may be a Uu interface (or air interface). Of course, in communications evolved after 5G, the names of these interfaces may remain unchanged, or may be replaced by other names, and this application does not limit this.
[0117] Access network equipment refers to the node or device that connects the terminal device to the wireless network. Access network equipment includes, but is not limited to: next generation node B (gNB), evolved node B (eNB), next generation eNB (ng-eNB), wireless backhaul equipment, radio network controller (RNC), node B (NB), home evolved node B (HeNB) or home node B (HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communication equipment that performs base station functions, etc. It can also include cloud radio access network (cloud radio access network). The centralized unit (CU) and distributed unit (DU) in a C-RAN system, and the network equipment in a non-terrestrial network (NTN) communication system can be deployed on a high-altitude platform or a satellite, etc., and the embodiments of the present application do not specifically limit this.
[0118] 3. CN
[0119] The CN may include one or more CN devices (which may also be understood as network elements or functional network elements or network functions (NF), etc., which are not limited here).
[0120] See also Figure 2 , Figure 2 This is another architecture diagram of a communication system. Figure 2 As shown, the PIN of the communication system includes one or more PINEs (e.g. Figure 2 (a) PINE1 and PINE2, or, Figure 2 (b) of PINE1, PINE2 and PINE3), and one or more PEGCs (e.g. Figure 2 (a) is a scenario including a PEGC, or, Figure 2 (b) is a scenario including two PEGCs, namely PEGC1 and PEGC2). It should be understood that PEGC is a PIN gateway with UE function, PINE is a terminal device in PIN, and PINE accesses the wireless network through PEGC. Optionally, PIN may also include a PIN management network element (PIN element management capability, PEMC), which is not shown in the figure. PEMC can be understood as a PIN network management network element with terminal function.
[0121] Optionally, the communication system may also include the following network functions and entities: network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), access and mobility management function (AMF), authentication server function (AUSF), session management function (SMF), (R)AN, user plane function (UPF), application function (AF) and PIN application server, wherein the PIN application server is equivalent to a data network (DN). Among them:
[0122] 1. User plane network element: As the interface with the data network, it completes functions such as user plane data forwarding, session / flow-level billing statistics, bandwidth limitation, etc. That is, packet routing and forwarding, and QoS processing of user plane data.
[0123] In a 5G communication system, the user plane network element may be a UPF network element.
[0124] 2. Authentication server: performs security authentication of users. In the 5G communication system, the authentication server can be an AUSF network element.
[0125] 3. Mobility management network element: mainly used for mobility management and access management. In the 5G communication system, the access management network element can be an AMF network element, which mainly performs functions such as mobility management and access authentication / authorization. In addition, it is also responsible for transmitting user policies between the terminal and the PCF network element.
[0126] 4. Session management network element: mainly used for session management, allocation and management of Internet Protocol / Internet Protocol (IP) addresses of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification.
[0127] In the 5G communication system, the session management network element can be an SMF network element, which completes terminal IP address allocation, UPF selection, and billing and QoS policy control.
[0128] 5. Application network element: In the 5G communication system, the application network element can be an AF network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data and is mainly used to convey the requirements of the application side to the network side.
[0129] 6. Unified data management network element: responsible for the management of user identification, contract data, authentication data, and user service network element registration management. In the 5G communication system, the unified data management network element can be a UDM network element.
[0130] 7. Policy control network element: including user contract data management function, policy control function, billing policy control function, QoS control, etc., a unified policy framework used to guide network behavior, and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).
[0131] In a 5G communication system, the policy control network element may be a PCF.
[0132] 8. Network Function Repository Functional Network Element: Provides storage and selection functions for network function entity information for other core network elements. In the 5G communication system, this network element can be an NRF network element.
[0133] 9. Network open network element: In the 5G communication system, the network open network element can be a NEF network element, which is mainly used to expose the services and capabilities of 3GPP network functions to AF, and also allows AF to provide information to 3GPP network functions.
[0134] 10. Network slice selection function network element: responsible for selecting network slices for UE. In the 5G communication system, this application network element can be the NSSF network element.
[0135] The above-mentioned functional network element can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). The above-mentioned functional network element can be divided into one or more services, and further, there may be services that exist independently of the network function. In this application, an instance of the above-mentioned functional network element, or an instance of a service included in the above-mentioned functional network element, or an instance of a service that exists independently of the network function can be referred to as a service instance.
[0136] In addition, although not shown, the CN may also include other possible network elements, such as a service communication proxy (SCP), a network slice admission control function (NSACF), a unified data repository (UDR) network element, etc.
[0137] It should be noted that the above functional entity is only a name, and the name itself does not limit the entity. For example, the session management function entity may also be replaced by "session management function" or other names. Moreover, the session management function entity may also correspond to an entity including other functions in addition to the session management function. The user plane function entity may also be replaced by "user plane function" or other names, and the user plane function entity may also correspond to an entity including other functions in addition to the user plane function. A unified explanation is given here, and no further description is given below.
[0138] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are merely examples, and other names may be used in specific implementations, and the embodiments of the present application do not impose any specific limitations on this.
[0139] Among them, Nnssf is the service-based interface provided by NSSF; Nnef is the service-based interface provided by NEF; Nnrf is the service-based interface provided by NRF; Npcf is the service-based interface provided by PCF; Nudm is the service-based interface provided by UDM; Naf is the service-based interface provided by AF; Nausf is the service-based interface provided by AUSF; Namf is the service-based interface provided by AMF; Nsmf is the service-based interface provided by SMF; N1 is the reference point between UE and AMF; N2 is the reference point between (R)AN and AMF; N3 is the reference point between (R)AN and UPF; N4 is the reference point between SMF and UPF; N6 is the reference point between UPF and DN; N9 is the reference point between UPFs. It should be noted that Figure 2The meanings of Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, Nsmf, N1, N2, N3, N4, N6, and N9 can be found in the definitions in the relevant standard protocols and are not limited here.
[0140] The embodiment of the present application provides a method for controlling the number of device accesses and a related device, which can alleviate network congestion and improve user experience. The following is a detailed description of the method for controlling the number of device accesses and the communication device provided by the present application:
[0141] See also Figure 3 , Figure 3 This is a flow chart of a method for controlling the number of device accesses provided by an embodiment of the present application.
[0142] S301, PEGC sends a first request to a first network element. Correspondingly, the first network element receives the first request from the PEGC.
[0143] The first request is used to request the allocation of an IP address. The first request may include the PIN identifier (i.e., PIN ID) of the PIN to which the PEGC belongs. That is, the first request is used to request the allocation of an IP address for the PIN corresponding to the PIN ID. It should be understood that a PIN identifier can be used to identify a PIN. Generally speaking, a PIN may include one or more PINEs and one or more PEGCs. For example, one or more PINEs may access a network through a PEGC (e.g., Figure 2 (a) is a schematic diagram showing that multiple PINEs can access the network through one PEGC), or multiple PINEs can also access the network through multiple PEGCs (e.g. Figure 2 (b) is a schematic diagram of multiple PINEs accessing a network through multiple PEGCs. When a PINE (for example, PINE1) in a PIN needs to access a network, the PINE1 can send a first request to the SMF through the PEGC. Accordingly, the SMF receives the first request sent by PINE1 through the PEGC.
[0144] S302. The first network element sends a first response to the PEGC according to the first quantity.
[0145] It is understandable that the first number in the present application is the maximum number of IP addresses that the PIN is allowed to allocate, that is, the maximum number of IP addresses that can be allocated to the PIN. For example, assuming that the first number = 10, it means that a maximum of 10 IP addresses can be allocated to the PIN. Optionally, the first number can also be described as the upper limit of the number of access devices of the PIN, or the first number can also be described as the maximum number of PINE device access restrictions in the PIN.
[0146] Exemplarily, the first network element may specifically send a first response to the PEGC based on the first quantity and the second quantity. The second quantity is the number of IP addresses allocated to the PIN. Here, "the number of IP addresses allocated to the PIN" can be understood as the number of IP addresses that have been allocated to the PIN and are still within the lease period (or effective period), or the number of IP addresses that have been allocated to the PIN and have not expired or been released. Generally speaking, when the second quantity is less than the first quantity, the first response includes the allocated IP address, and when the second quantity is greater than or equal to the first quantity, the first response is used to reject the first request.
[0147] It should be noted that the first network element in the present application (i.e., the network element that performs address allocation) may be SMF, UPF, or UDM, etc., and the IP address may be an IPv4 address or an IPv6 address, etc. Among them, when the first network element is SMF, SMF may allocate an IPv4 address or an IPv6 address after the PDU session is established (e.g. Figure 4 Alternatively, SMF can also allocate IPv4 addresses during the PDU session establishment process (such as Figure 7 When the first network element is UPF, UPF can allocate IPv4 addresses during the PDU session establishment process (such as Figure 8 When the first network element is a UDM, the UDM can allocate an IPv4 address during the PDU session establishment process (such as Fig. 9 Alternatively, the IPv4 address is allocated after the PDU session is established (as shown in Fig.10 The following describes in detail the IP address allocation in different scenarios.
[0148] See also Figure 4 , Figure 4 This is another flow chart of the device access quantity control method provided in an embodiment of the present application. Figure 4 You can use Figure 2 The architecture shown in Figure 1 shows that different PEGCs select the same AMF, SMF, and UPF. Figure 4 The embodiment shown is mainly described by taking the SMF performing IP address allocation after the PDU session is established as an example. In addition, Figure 4 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 4 In addition, Figure 4 The steps in Figure 4are executed in a different order than those presented, and may not be executed in the order Figure 4 All operations in . Among them:
[0149] S401, PEGC sends a first request to SMF. Correspondingly, SMF receives the first request from PEGC.
[0150] Here, the first request may specifically be a request for requesting an IPv4 address. Optionally, the first request may also be a router solicitation (RS), and the RS request is used to request to obtain an IPv6 address prefix.
[0151] S402: The SMF determines a first response according to the first quantity, and sends the first response to the PEGC. Accordingly, the PEGC receives the first response from the SMF.
[0152] Generally speaking, the SMF may determine the first response specifically based on the first number and the second number, where the second number is the number of IP addresses allocated for the PIN. If the second number is less than the first number, the first response includes the allocated IP addresses, and if the second number is greater than or equal to the first number, the first response is used to reject the first request.
[0153] As described above, when SMF allocates IPv4 addresses after the PDU session is established, it specifically includes the following two situations: 1) SMF allocates IPv4 addresses as a DHCPv4 server; 2) SMF obtains an IPv4 address from an external network as a DHCPv4 client and allocates it to PEGC.
[0154] For example, Figure 5 As shown in (a), the complete process of SMF as a DHCPv4 server to allocate IPv4 addresses is as follows:
[0155] 1. PEGC sends a dynamic host configuration protocol (DHCP) discovery (DHCP DISCOVER) message to SMF.
[0156] 2. SMF sends a DHCP reply (DHCP OFFER) message to PEGC.
[0157] 3. PEGC sends a DHCP request (DHCP REQUEST) message to SMF. Here, DHCP REQUEST is the first request.
[0158] 4. SMF sends a DHCP positive acknowledgment / negative acknowledgment (DHCP ACK / NACK) to PEGC. DHCP ACK indicates agreement to address allocation, and the DHCP ACK includes the IPv4 address, and DHCP NACK indicates refusal to allocate the address. Optionally, DHCPACK may also include information such as the lease term T1 of the IPv4 address, and / or the timeout period T2. Generally speaking, T1 indicates the effective duration of the allocated IPv4 address, and T2 indicates that after the timeout period, the allocated IPv4 address will be automatically released. Here, DHCP ACK / NACK is the first response.
[0159] For example, Figure 5 As shown in (b), the complete process of SMF as a DHCPv4 Client to allocate IPv4 addresses is as follows:
[0160] 0. PEGC sends the first request to SMF.
[0161] 1. SMF sends a DHCP DISCOVER to the DHCPv4 Sever.
[0162] 2. DHCPV4 Sever sends DHCP OFFER to SMF.
[0163] 3. SMF sends a DHCP REQUEST to the DHCPv4 Sever.
[0164] 4. DHCPV4 SEVER sends DHCP ACK / NACK to SMF. DHCP ACK indicates that the address allocation is approved and includes the IPv4 address, while DHCP NACK indicates that the address allocation is rejected. Optionally, the DHCP ACK may also include the lease term T1 of the IPv4 address and / or the timeout period T2.
[0165] 5. SMF sends a first response to PEGC, which includes DHCP ACK / NACK.
[0166] Optionally, when SMF allocates IPv6 addresses after the PDU session is established, the first request may be an RS request, and the first response may be a router advertisement (RA) message. If SMF agrees to allocate the address, the RA message includes an IPv6 address prefix, which may be obtained by SMF from the DHCPv6 Server. After PEGC receives the IPv6 address prefix in the RA message, PEGC may generate an interface identifier based on the IPv6 address prefix, and then generate a complete IPv6 address based on the IPv6 address prefix and the interface identifier. If SMF does not agree to allocate the address, the RA message is used to reject the RS request.
[0167] Optional, please also see Figure 4 , before the above step S401, some or all of the following steps may also be included:
[0168] S4001. PEGC sends a PDU session establishment request (PDU Session Establishment Request) to AMF. Correspondingly, AMF receives the PDU session establishment request from PEGC.
[0169] It should be understood that the PDU session establishment request may include the PIN identifier of the PIN to which the PEGC belongs.
[0170] S4002. AMF selects SMF based on the PIN identifier.
[0171] Optionally, in addition to the PIN identifier, AMF can also select SMF based on information such as the data network name (DNN) and single network slice selection assistance information (S-NSSAI).
[0172] Understandable, such as Figure 2In the architecture shown, there may be one or more PEGCs in a PIN. When there are multiple PEGCs in a PIN, in order to achieve consistency in SMF selection when different PEGCs initiate PDU sessions, the AMF in the embodiment of the present application needs to select the SMF in combination with the PIN identifier. For example, suppose there are two PEGCs, namely PEGC1 and PEGC2, where PEGC1 sends a PDU session establishment request carrying information such as a PIN identifier (for example, PIN identifier 1). Therefore, the AMF can select SMF1 based on information such as PIN identifier 1, DNN, and S-NSSAI. When PEGC2 subsequently initiates a PDU session establishment request, the PDU session establishment request may also carry PIN identifier 1. Since the PIN identifier 1 carried in the PDU session establishment request sent by PEGC2 is consistent / identical to the PIN identifier 1 carried in the PDU session establishment request sent by PEGC1, the AMF will select the same SMF1 based on the PIN identifier, DNN, S-NSSAI and other information, thereby ensuring that the same PIN corresponds to the same SMF.
[0173] S4003, AMF sends a PIN identifier to SMF. Correspondingly, SMF receives the PIN identifier from AMF.
[0174] Exemplarily, the PIN identifier sent by the AMF can be carried in a PDU session create SM context request (PDUSession Create SM Context Request).
[0175] S4004, SMF sends a contract data acquisition request to UDM. Correspondingly, UDM receives the contract data acquisition request from SMF.
[0176] The subscription data acquisition request includes a PIN identifier, and the subscription data acquisition request is used to request the subscription data corresponding to the PIN identifier. Optionally, the subscription data acquisition request can also be used to request connection management information related to PEGC, etc., which is not limited here.
[0177] S4005, UDM sends the contract data corresponding to the PIN identifier to SMF. Correspondingly, SMF receives the contract data corresponding to the PIN identifier from UDM.
[0178] It is understandable that after UDM receives the contract data acquisition request, UDM can feedback the contract data to SMF, and the contract data includes the PIN identifier and the first quantity. Optionally, the contract data can also include the first indication information, DNN, S-NSSAI and other information.
[0179] It should be understood that, in one implementation, the PIN identifier and the first quantity included in the subscription data stored in the UDM may be independently written by the operator. Figure 6 As shown in (a), in another implementation, the PIN identifier and the first quantity included in the subscription data stored in the UDM may also be sent by the management network element (such as PEMC) in the PIN to the AF through the application layer, and then the AF sends the message containing the PIN identifier and the first quantity to the UDM through the NEF network element. Figure 6 As shown in (b), in another implementation, the management network element (such as PEMC) in the PIN may send the PIN identifier to the AF through the application layer, and then the AF may send the PIN identifier to the UDM through the NEF network element, and finally the UDM may generate the contract data including the PIN identifier and the first quantity according to the PIN identifier.
[0180] S4006. SMF sends a PDU Session Create SM Context Response to AMF. Correspondingly, AMF receives the PDU Session Create SM Context Response from SMF.
[0181] S4007. SMF triggers PDU session authentication authorization (PDU Session Authentication Authorization).
[0182] S4008. SMF selects PCF and establishes a management strategy with PCF.
[0183] It should be understood that after SMF receives the contract data of UDM, it can initiate a policy control request for the PIN to PCF, and the policy control request can carry the PIN identifier. Correspondingly, PCF receives the policy control request carrying the PIN identifier from SMF, and feeds back the policy control information, QoS and other information corresponding to the PIN identifier to SMF.
[0184] S4009. SMF selects UPF based on the PIN identifier.
[0185] After the SMF receives the policy control information from the PCF, it can select the UPF. For example, the SMF can select the UPF based on the PIN identifier to ensure that the same PIN corresponds to the same UPF.
[0186] S4010, SMF sends first indication information to UPF. Correspondingly, UPF receives the first indication information from SMF.
[0187] The first indication information instructs the UPF to perform a network address translation (NAT) conversion check on the received data packet. The first indication information may be carried in an N4 session request (N4 Session Request). S4010 is an optional step.
[0188] S4011, SMF sends a PIN identifier and a first quantity to PEGC. Correspondingly, PEGC receives the PIN identifier and the first quantity from SMF.
[0189] Exemplarily, SMF sending the PIN identifier and the first quantity to PEGC can be understood as: SMF sends the PIN identifier and the first quantity to AMF through an N1N2 transfer message (N1N2 Message Transfer), and then AMF sends the PIN identifier and the first quantity to RAN through an N2 non-access layer message (N2 NAS Message), and finally RAN sends the PIN identifier and the first quantity to PEGC through an access network resource configuration (ANResource setup) message.
[0190] Optionally, after PEGC receives the first number corresponding to the PIN identifier from SMF, PEGC may first determine whether the second number is less than the first number before executing the above step S401. When the second number is less than the first number, the first request is sent again, and when the second number is equal to the first number, PEGC does not send the first request, so that the PEGC side can control the PINE accessing the network. S4011 is an optional step.
[0191] It should be noted that the remaining steps of the PDU session establishment process after S4011 refer to the protocol 3GPP TS23.502 and will not be repeated here.
[0192] Optional, please also see Figure 4 , after the above step S402, the following steps may also be included:
[0193] S403, PEGC sends a data packet to UPF. Correspondingly, UPF receives the data packet from PEGC.
[0194] S404. UPF performs NAT conversion check on the IP address included in the data packet.
[0195] In some feasible implementations, the UPF may perform a NAT conversion check on the IP address in the data packet based on the first indication information. Optionally, the protocol may predefine that when the UPF receives a data packet, it needs to perform a NAT conversion check on the IP address in the received data packet.
[0196] It should be understood that after the UPF performs a NAT conversion check on the IP address in the data packet, a NAT conversion check result can be generated. Generally speaking, if the UPF identifies that the data packet sent by the PEGC has been NAT converted, the SMF is informed that the inspection result is that the data packet has been NAT converted. If the UPF identifies that the data packet sent by the PEGC has not been NAT converted, the SMF is informed that the inspection result is that the data packet has not been NAT converted. In other words, the NAT conversion check result includes whether the data packet has been NAT converted, or whether the data packet has not been NAT converted.
[0197] S405, UPF sends the NAT conversion check result to SMF. Correspondingly, SMF receives the NAT conversion check result from UPF.
[0198] S406. SMF determines whether to reject the PDU session corresponding to PEGC based on the NAT conversion check result.
[0199] Generally speaking, if the NAT conversion check result is that the data packet has been NAT converted, then the SMF needs to reject the PDU session corresponding to the PEGC. Here, the reason why the PDU session needs to be rejected is that if the PINE in the PIN network has been NAT converted, then the number of PINE devices connected to the Internet network in the PIN is very likely to be much larger than the first number, which does not meet the need proposed by this application to limit the number of access devices to no more than the first number. If the NAT conversion check result is that the data packet has not been NAT converted, the PDU session corresponding to the PEGC is not rejected.
[0200] In the embodiment of the present application, during the PDU session establishment process, different PEGCs in the same PIN can select the same AMF, SMF and UPF based on the PIN identifier. Further, after the PDU session is established, the PEGC sends a first request to the SMF to request the allocation of an IP address, so the SMF can determine whether to allocate an IP address based on the second number and the first number, so as to achieve SMF's control over the number of PINE device accesses, which is conducive to alleviating network congestion and improving user experience.
[0201] See also Figure 7 , Figure 7 It is a flow chart of a method for controlling the number of device accesses provided in an embodiment of the present application. Figure 7 You can use Figure 2 The architecture shown in Figure 1 shows that different PEGCs select the same AMF, SMF, and UPF. Figure 7 The embodiment shown is mainly described by taking the SMF performing IP address allocation during the PDU session establishment process as an example. Figure 7is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 7 In addition, Figure 7 The steps in Figure 7 are executed in a different order than those presented, and may not be executed in the order Figure 7 All operations in . Among them:
[0202] S701, PEGC sends a PDU session establishment request to AMF. Correspondingly, AMF receives the PDU session establishment request from PEGC.
[0203] Among them, the PDU session establishment request may include a PIN identifier and information requesting address allocation, where the information requesting address allocation can be understood as a first request. The first request in the embodiment of the present application is used to request an IPv4 address. Optionally, the PDU session establishment request itself may have the attribute of requesting address allocation, so after the SMF receives the PDU session establishment request, it can allocate an IP address. In other words, the PDU session establishment request itself is equivalent to the first request. Among them, the SMF can determine what address should be allocated based on the PDU session type of the PDU session establishment request. For example, when the PDU session type is IPv4 type, it can be determined that the allocated IP address is an IPv4 address, and when the PDU session type is IPv6 type, it can be determined that the allocated IP address is an IPv6 address. The embodiment of the present application is mainly illustrated by taking the PDU session type of IPv4 type as an example.
[0204] S702. AMF selects SMF based on the PIN identifier.
[0205] For more information about S702, see Figure 4 The description of S4002 in will not be repeated here.
[0206] S703, AMF sends a PIN identifier and information requesting address allocation to SMF. Correspondingly, SMF receives the PIN identifier and information requesting address allocation from AMF.
[0207] Exemplarily, the PIN identifier and address allocation request information sent by the AMF can be carried in the PDU session creation SM context request.
[0208] S704: SMF sends a contract data acquisition request to UDM. Correspondingly, UDM receives the contract data acquisition request from SMF. The contract data acquisition request includes a PIN identifier.
[0209] S705, UDM sends the contract data corresponding to the PIN identifier to SMF. Correspondingly, SMF receives the contract data corresponding to the PIN identifier from UDM.
[0210] S706, SMF sends a PDU session creation SM context response to AMF. Correspondingly, AMF receives a PDU session creation SM context response from SMF.
[0211] S707. SMF triggers PDU session authentication and authorization.
[0212] S708. SMF selects PCF and establishes a management strategy with PCF.
[0213] S709. SMF selects UPF based on the PIN identifier.
[0214] S710, SMF sends first indication information to UPF. Correspondingly, UPF receives the first indication information from SMF.
[0215] For the understanding of S704 to S710, see Figure 4 The description of S4004 to S4010 will not be repeated here.
[0216] S711. The SMF determines a first response according to the first quantity, and sends the first response to the PEGC. Accordingly, the PEGC receives the first response from the SMF.
[0217] When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request; the second number is the number of IP addresses allocated for the PIN.
[0218] Exemplarily, the above-mentioned SMF sending the first response to PEGC can be understood as: SMF sends the first response to AMF through the N1N2 message, and then AMF sends the first response to RAN through the N1 non-access layer message, and finally RAN sends the first response to PEGC through the access layer resource configuration message.
[0219] Optionally, in addition to feeding back the first response, the SMF may also send a PIN identifier and a corresponding first quantity to the PEGC. It should be understood that after the PEGC receives the PIN identifier and the corresponding first quantity from the SMF, when other PINEs (such as PINE2) in the PIN network need to request an IP address, the PEGC may first determine whether the second quantity is less than the first quantity. When the second quantity is less than the first quantity, the first request is sent, and when the second quantity is equal to the first quantity, the PEGC does not send the first request, where the second quantity is the number of IP addresses allocated to the PIN. Based on this, the PEGC side can implement control over the PINEs accessing the network.
[0220] It should be noted that the remaining steps of the PDU session establishment process after S711 refer to 3GPP TS 23.502 and will not be repeated here.
[0221] Optional, such as Figure 7 As shown, after the PDU session is established, steps S712 to S715 may also be included. For an understanding of S712 to S715, see the above Figure 4 The description of S403 to S406 will not be repeated here.
[0222] In the embodiment of the present application, during the PDU session establishment process, different PEGCs in the same PIN can select the same AMF, SMF and UPF based on the PIN identifier. In addition, during the PDU session establishment process, the PEGC sends information requesting address allocation to the SMF to request the allocation of an IP address, so the SMF can determine whether to allocate an IP address based on the second number and the first number, so as to achieve SMF's control over the number of PINE device accesses, which is conducive to alleviating network congestion and improving user experience.
[0223] See also Figure 8 , Figure 8 This is another flow chart of the device access quantity control method provided in an embodiment of the present application. Figure 8 It can be based on Figure 2 The architecture shown in Figure 1 shows that different PEGCs select the same AMF, SMF, and UPF. Figure 8 The embodiment shown is mainly described by taking the UPF performing IP address allocation during the PDU session establishment process as an example. Figure 8 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 8 In addition, Figure 8 The steps in Figure 8are executed in a different order than those presented, and may not be executed in the order Figure 8 All operations in . Among them:
[0224] Steps S801 to S810 and Figure 7 The steps S701 to S710 in are similar, except that:
[0225] In S810, the N4 session request may include a PIN identifier, a first quantity and information on requesting address allocation (i.e., a first request). Optionally, the N4 session request may also include first indication information. That is, when the UPF allocates an IPv4 address during the PDU session establishment process, the SMF needs to send the first request obtained from the PEGC and the first quantity corresponding to the PIN identifier obtained from the UDM to the UPF, so that the UPF can determine whether to allocate an IP address based on the first quantity and feedback a first response, such as Figure 8 As shown:
[0226] S811. UPF determines a first response according to the first quantity, and sends the first response to SMF. Accordingly, SMF receives the first response from UPF.
[0227] The first response may be an N4 session response, and when the second number is less than the first number, the first response fed back by the UPF includes the allocated IP address. When the second number is greater than or equal to the first number, the first response fed back by the UPF is used to reject the first request, and the second number is the number of IP addresses allocated for the PIN.
[0228] S812: SMF sends a first response to PEGC. Correspondingly, PEGC receives the first response from SMF.
[0229] In some feasible implementations, after the SMF receives the first response from the UPF, the SMF needs to forward the received first response to the PEGC. Exemplarily, the SMF may send the first response to the AMF via an N1N2 message, and then the AMF sends the first response to the RAN via an N1 non-access layer message, and finally the RAN sends the first response to the PEGC via an access layer resource configuration message.
[0230] Optionally, the SMF may also send information such as the PIN identifier and the first quantity to the PEGC to implement the PEGC side's control over the PINEs accessing the network.
[0231] It should be noted that the remaining steps of the PDU session establishment process after S812 refer to the protocol 3GPP TS23.502 and will not be repeated here.
[0232] Optional, such as Figure 8As shown, after the PDU session is established, steps S813 to S816 may also be included. For an understanding of S813 to S816, see the above Figure 4 The description of S403 to S406 will not be repeated here.
[0233] See also Fig. 9 , Fig. 9 This is another flow chart of the device access quantity control method provided in the embodiment of the present application. Different from the scheme of address allocation by SMF or UPF, Fig. 9 The embodiment shown is explained by taking the UPF performing IP address allocation during the PDU session establishment process as an example. It should be understood that when the UPF performs address allocation, it is not limited to the condition that the PEGC selects the same AMF, SMF and UPF. That is, different PEGCs in the PIN can select the same AMF, SMF and UPF, or different PEGCs can also select different AMF, SMF and UPF. In addition, Fig. 9 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Fig. 9 In addition, Fig. 9 The steps in Fig. 9 are executed in a different order than those presented, and may not be executed in the order Fig. 9 All operations in . Among them:
[0234] Steps S901 to S911 and Figure 7 The steps S701 to S711 in are similar, except that:
[0235] In S904, the contract data acquisition request sent by SMF to UDM includes not only the PIN identifier but also the information requesting address allocation. Therefore, after UDM receives the contract data acquisition request, in S905, it can determine whether to allocate an IP address based on the first quantity and feedback the first response in the contract data. Optionally, the contract data may also include first indication information. It should be understood that since the address allocation is performed by UDM, the first quantity may not be included in the contract data in S905. In S911, SMF feeds back the first response carried in the contract data to PEGC.
[0236] It should be noted that the remaining steps of the PDU session establishment process after S911 refer to the protocol 3GPP TS23.502 and will not be repeated here.
[0237] Optional, such as Fig. 9As shown, after the PDU session is established, steps S912 to S915 may also be included. For an understanding of S912 to S915, see the above Figure 4 The description of S403 to S406 will not be repeated here.
[0238] See also Fig.10 , Fig.10 This is another flow chart of the device access quantity control method provided in the embodiment of the present application. Different from the scheme of address allocation by SMF or UPF, Fig.10 The embodiment shown is explained by taking the UPF performing IP address allocation after the PDU session is established as an example. It should be understood that when the UPF performs address allocation, it is not limited to the condition that the PEGC selects the same AMF, SMF and UPF. That is, different PEGCs in the PIN can select the same AMF, SMF and UPF, or different PEGCs can also select different AMF, SMF and UPF. In addition, Fig.10 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Fig.10 In addition, Fig.10 The steps in Fig.10 are executed in a different order than those presented, and may not be executed in the order Fig.10 All operations in . Among them:
[0239] Steps S1001 to S1010 and Figure 4 Steps S4001 to S4010 in are similar, except that:
[0240] In S1005, the first quantity is not included in the contract data. Optionally, the contract data may include first indication information, and the first indication information instructs the UPF to perform a network address translation NAT conversion check on the received data packet. Optionally, the contract data may also include second indication information, and the second indication information indicates that when the SMF receives the address allocation request, it needs to forward the request to the UDM. Optionally, the contract data may not include the second indication information, but the protocol predefines that when the SMF receives the address allocation request, it needs to forward the address allocation request to the UDM.
[0241] It should be noted that the remaining steps of the PDU session establishment process after S1010 refer to the protocol 3GPP TS23.502 and will not be repeated here.
[0242] It should be noted that after the PDU session is established, the following steps are included:
[0243] S101. PEGC sends a first request to UDM.
[0244] Specifically, PEGC may send a first request to UDM through SMF. Exemplarily, the first request may be a request for requesting an IPv4 address.
[0245] S102. The UDM determines a first response according to the first quantity, and sends the first response to the PEGC.
[0246] When the UDM determines that the second number is less than the first number, the first response fed back by the UDM includes the allocated IP address, and when the UDM determines that the second number is greater than or equal to the first number, the first response fed back by the UDM is used to reject the first request, wherein the second number is the number of IP addresses allocated for the PIN. Exemplarily, the first response may be DHCPACK / NACK.
[0247] Optional, such as Fig.10 As shown, after the PDU session is established, steps S103 to S106 may also be included. For an understanding of S103 to S106, see the above Figure 4 The description of S403 to S406 will not be repeated here.
[0248] The following will be combined Figure 11-12 The communication device provided in this application is described in detail.
[0249] It is understandable that in order to implement the functions in the above embodiments, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
[0250] Fig.11 and Fig.12 A schematic diagram of the structure of a possible communication device provided for an embodiment of the present application. These communication devices can be used to implement the functions of the PEGC or the first network element in the above method embodiment, and thus can also achieve the beneficial effects possessed by the above method embodiment. In an embodiment of the present application, the communication device can be a PEGC or a first network element, or a module (such as a chip) applied to the PEGC or the first network element. Exemplarily, the first network element can be an SMF, UPF or UDM, etc., which is not limited here.
[0251] like Fig.11As shown, the communication device 1100 includes a processing unit 1110 and a transceiver unit 1120. The communication device 1100 is used to implement the above Figure 3 or Figure 4 or Figure 7 or Fig.11 or Fig.12 or Fig.10 Functions of the PEGC or the first network element in the method embodiment shown in . Wherein:
[0252] In one implementation, when the communication device is a first network element, the transceiver unit 1120 is used to receive a first request from a first device, where the first request includes a first network identifier of a first network to which the first device belongs. The processing unit 1110 is used to determine a first response according to a first quantity. The transceiver unit 1120 is used to send a first response to the first device, where the first quantity is the maximum number of IP addresses allowed to be allocated to the first network. The first response includes the allocated IP address, or the first response is used to reject the first request.
[0253] In another implementation, when the communication device is a PEGC, the transceiver unit 1120 is configured to send a first request to the SMF or to the unified data management function UPF, wherein the first request includes a first network identifier of a first network to which the first device belongs. The transceiver unit 1120 is configured to receive a first response from the SMF or the UPF, wherein the first response includes an allocated IP address, or the first response is used to reject the first request.
[0254] For more detailed description of the processing unit 1110 and the transceiver unit 1120, please refer to Figure 3 or Figure 4 or Figure 7 or Fig.11 or Fig.12 or Fig.10 The method embodiment shown is described in detail.
[0255] like Fig.12 As shown, the communication device 1200 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It is understood that the interface circuit 1220 can be a transceiver or an input-output interface. Optionally, the communication device 1200 may also include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to execute instructions or storing data generated after the processor 1210 executes instructions.
[0256] When the communication device 1200 is used to implement Figure 3 or Figure 4 or Figure 7 or Fig.11 or Fig.12 or Fig.10 When the method is shown, the processor 1210 is used to implement the function of the above-mentioned processing unit 1110, and the interface circuit 1220 is used to implement the function of the above-mentioned transceiver unit 1120.
[0257] When the communication device is a chip applied to PEGC, the PEGC chip implements the function of PEGC in the above method embodiment. The PEGC chip receives information sent by the first network element to the PEGC through other modules in the PEGC (such as a radio frequency module or an antenna); or the PEGC chip sends information to other modules in the PEGC (such as a radio frequency module or an antenna), and the information is sent by the PEGC to the first network element.
[0258] When the above communication device is a module applied to the first network element, the first network element module implements the function of the first network element in the above method embodiment. The first network element module receives information from other modules in the first network element (such as a radio frequency module or an antenna), and the information is sent to the first network element by the PEGC; or the first network element module sends information to other modules in the first network element (such as a radio frequency module or an antenna), and the information is sent to the PEGC by the first network element.
[0259] It is understandable that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0260] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a first network element or a PEGC. The processor and the storage medium can also exist in the first network element or the PEGC as discrete components.
[0261] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, for example, a floppy disk, a hard disk, a tape; it may also be an optical medium, for example, a digital video disc; it may also be a semiconductor medium, for example, a solid-state hard disk. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
[0262] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.
[0263] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.
Claims
1. A method for controlling the number of device accesses, characterized in that: The method comprises: receiving a first request from a first device, where the first request is used to request allocation of an Internet Protocol (IP) address, and the first request includes a first network identifier of a first network to which the first device belongs; A first response is sent to the first device according to a first number, where the first number is a maximum number of IP addresses that the first network is allowed to allocate, and the first response includes the allocated IP addresses, or the first response is used to reject the first request.
2. The method according to claim 1, characterized in that The sending a first response to the first device according to the first quantity includes: sending a first response to the first device according to the first number and a second number, the second number being the number of IP addresses allocated to the first network; When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: Receiving the first network identifier from an access and mobility management function AMF; Sending a subscription data acquisition request to a unified data management function (UDM), wherein the subscription data acquisition request includes the first network identifier; Receive subscription data corresponding to the first network identifier from the UDM, the subscription data including the first quantity.
4. The method according to claim 3, characterized in that The first response includes an allocated IP address; after sending the first response to the first device according to the first quantity, the method further includes: Receiving a NAT translation check result from the UPF; Determine whether to reject the protocol data unit PDU session corresponding to the first device according to the NAT conversion check result.
5. The method according to claim 4, characterized in that The method further comprises: A first indication message is sent to a user plane function UPF, wherein the first indication message instructs the UPF to perform a network address translation NAT conversion check on a received data packet.
6. The method according to any one of claims 2 to 5, characterized in that: The method further comprises: The first amount is sent to the first device.
7. The method according to claim 1 or 2, characterized in that: The method further comprises: Receive the first network identifier and the first number from a session management function SMF.
8. The method according to claim 7, characterized in that The first response includes an allocated IP address; after sending the first response to the first device according to the first quantity, the method further includes: receiving a data packet from the first device; Perform a NAT conversion check on the IP address included in the data packet, and send the NAT conversion check result to the SMF.
9. The method according to claim 8, characterized in that The method further comprises: Receive first indication information from the SMF, wherein the first indication information instructs the UPF to perform a network address translation NAT conversion check on the received data packet.
10. A method for controlling the number of device accesses, characterized in that: include: Sending a first request, where the first request is used to request allocation of an Internet Protocol IP address, and the first request includes a first network identifier of a first network to which the first device belongs; A first response is received, wherein the first response includes the assigned IP address, or the first response is used to deny the first request.
11. The method according to claim 10, characterized in that The method further comprises: Receiving a first number from a session management function SMF; The sending of the first request comprises: When a second number is less than the first number, a first request is sent, wherein the second number is the number of IP addresses allocated to the first network.
12. A method for controlling the number of device accesses, characterized in that: include: A first device sends a first request to a first network element, where the first request is used to request allocation of an Internet Protocol IP address, and the first request includes a first network identifier of a first network to which the first device belongs; The first network element sends a first response to the first device according to a first quantity, where the first quantity is a maximum number of IP addresses allowed to be allocated to the first network, and the first response includes the allocated IP addresses, or the first response is used to reject the first request.
13. The method according to claim 12, characterized in that The first network element sends a first response to the first device according to the first quantity, including: The first network element sends a first response to the first device according to the first number and a second number, where the second number is the number of IP addresses allocated to the first network; When the second number is less than the first number, the first response includes the allocated IP address; when the second number is greater than or equal to the first number, the first response is used to reject the first request.
14. The method according to claim 12 or 13, characterized in that The method further comprises: The access and mobility management function AMF sends the first network identifier to the session management function SMF; The SMF sends a subscription data acquisition request to the UDM, where the subscription data acquisition request includes the first network identifier; The UDM sends the subscription data corresponding to the first network identifier to the SMF, where the subscription data includes the first quantity.
15. The method according to claim 14, characterized in that The first network element is a user plane function UPF; the method further includes: The SMF sends the first network identifier and the first quantity to the UPF.
16. The method according to any one of claims 12 to 15, characterized in that: The first response includes an assigned IP address; the method further comprising: The first device sends a data packet to a user plane function UPF; The UPF performs a NAT conversion check on the IP address included in the data packet and sends the NAT conversion check result to the SMF; The SMF determines whether to reject the protocol data unit PDU session corresponding to the first device according to the NAT conversion check result.
17. The method according to claim 16, characterized in that The method further comprises: The SMF sends a first indication message to the UPF, where the first indication message instructs the UPF to perform a network address translation NAT conversion check on the received data packets.
18. The method according to any one of claims 12 to 17, characterized in that: The method further comprises: The SMF sends the first quantity to the first device; The first device sending a first request to the first network element includes: When the second number is less than the first number, the first device sends a first request to the first network element, and the second number is the number of IP addresses allocated to the first network.
19. A communication device, comprising a unit or module for executing the method according to any one of claims 1 to 11.
20. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-11 through a logic circuit or executing code instructions.
21. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction. When the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 11 is implemented.
22. A computer program product, characterized in that The method comprises a computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1 to 11 is implemented.
