IP address allocation method, IP address acquisition method, IP address allocation device, IP address acquisition device and electronic equipment

Abstract

The invention discloses an IP address allocation method, an IP address acquisition method, an IP address allocation device, an IP address acquisition device and electronic equipment, and belongs to the technical field of communication. The method comprises: a network side device receives request information sent by a terminal, the request information comprising a demand capability identifier, and the demand capability identifier is used for indicating that the terminal needs a static IP address; the network side equipment allocates a target static IP address to the terminal based on the capability information; wherein the target static IP address is a dedicated IP address which can be used by the terminal within a preset time period; the request information comprises at least one of the following items: a registration request, a re-registration request, a PDU session establishment request, an attachment request and a PDN connection request.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to an IP address allocation method, an IP address acquisition method, a device and an electronic device. BACKGROUND

[0002] In the related art, when a network side device receives a request of terminal registration into a network, the network side device allocates an Internet Protocol (IP) address to the terminal through a specific signaling process, so that the terminal can access the Internet or a specific network domain using the IP address obtained from the network side device after registration into the network, to realize information interaction between the terminal and a service server, such as chatting using an instant messaging application or watching a video using a video application.

[0003] With the development of 5G private networks, edge computing, video monitoring and the Internet of Things, in some cases, the communication between the terminal and the service server based on Transmission Control Protocol (TCP) / IP requires a fixed IP address, however, the existing IP address allocation method may cause the terminal and the service server to be unable to communicate. SUMMARY

[0004] The purpose of the embodiments of the present application is to provide an IP address allocation method, an IP address acquisition method, a device and an electronic device, which can ensure normal communication between the terminal and the service server.

[0005] In a first aspect, an IP address allocation method is provided, which is executed by a network side device, and the method comprises: the network side device receiving request information sent by a terminal, the request information comprising a demand capability identifier, the demand capability identifier being used to indicate that the terminal demands a static IP address; the network side device allocating a target static IP address to the terminal based on the capability information; wherein the target static IP address is a special IP address available to the terminal within a preset time length; and the request information comprises at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attachment request and a PDN connection request.

[0006] In a second aspect, an IP address acquisition method is provided, which is executed by a terminal, and the method comprises: the terminal sending request information to a network side device, the request information comprising a demand capability identifier, the demand capability identifier being used to indicate that the terminal demands a static IP address; and the terminal receiving response information sent by the network side device, the response information comprising a target static IP address allocated to the terminal by the network side device; wherein the target static IP address is a special IP address available to the terminal within a preset time length; and the request information comprises at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attachment request and a PDN connection request.

[0007] Thirdly, an IP address allocation device is provided, comprising: a receiving module and a processing module; the receiving module is configured to receive request information sent by a terminal, the request information including a required capability identifier, the required capability identifier indicating that the terminal requires a static IP address; the processing module is configured to allocate a target static IP address to the terminal based on the capability information; wherein the target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, and a PDN connection request.

[0008] Fourthly, an IP address acquisition device is provided, comprising: a sending module and a receiving module; the sending module is used to send request information to a network-side device, the request information including a capability requirement identifier, the capability requirement identifier indicating that the terminal requires a static IP address; the receiving module is used to receive response information sent by the network-side device, the response information including a target static IP address allocated by the network-side device to the terminal; wherein, the target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, and a PDN connection request.

[0009] Fifthly, an IP address allocation apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, and an IP address acquisition apparatus is provided, the apparatus being configured to perform the steps of the method described in the second aspect.

[0010] In a sixth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0011] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive request information sent by a terminal, the request information including a required capability identifier, the required capability identifier indicating that the terminal requires a static IP address; the processor is used to allocate a target static IP address to the terminal based on the capability information; wherein the target static IP address is a dedicated IP address that the terminal can use within a preset time period; the above request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

[0012] Eighthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0013] In a ninth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send request information to a network-side device, the request information including a required capability identifier, the required capability identifier indicating that the terminal requires a static IP address; the communication interface is also used to receive response information sent by the network-side device, the response information including a target static IP address allocated by the network-side device to the terminal; wherein the target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, and a PDN connection request.

[0014] In a tenth aspect, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first or second aspect.

[0015] Eleventhly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the methods described in the first or second aspect.

[0016] In a twelfth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first or second aspect.

[0017] In this embodiment, the network-side device receives request information sent by the terminal. The request information includes a capability requirement identifier, indicating that the terminal requires a static IP address. Based on the capability information, the network-side device allocates a target static IP address to the terminal. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the network-side device can trigger the allocation of a static IP address to the terminal based on the terminal's capability information requiring a static IP address, and continuously allocate this static IP address to the terminal within a preset time period, thereby ensuring that the service server and the terminal can access each other and communicate normally. Attached Figure Description

[0018] Figure 1This is a flowchart illustrating an IP address allocation method provided in some embodiments of this application;

[0019] Figure 2 This is a flowchart illustrating an IP address acquisition method provided in some embodiments of this application;

[0020] Figure 3 This is a schematic diagram of a static IP switch control provided in some embodiments of this application;

[0021] Figure 4 This is a schematic diagram of the signaling interaction process between the terminal and the network-side device provided in some embodiments of this application;

[0022] Figure 5 This is a flowchart illustrating the IP address allocation method and IP address acquisition method between a terminal and a network-side device provided in some embodiments of this application;

[0023] Figure 6 This is a schematic diagram of the signaling interaction process between the terminal and the network-side device provided in some embodiments of this application;

[0024] Figure 7 These are schematic diagrams of IP address allocation devices provided in some embodiments of this application;

[0025] Figure 8 This is one of the schematic diagrams of an IP address acquisition device provided in some embodiments of this application;

[0026] Figure 9 This is a second schematic diagram of an IP address acquisition device provided in some embodiments of this application;

[0027] Figure 10 These are schematic diagrams of the communication device structure provided in some embodiments of this application;

[0028] Figure 11 These are schematic diagrams of the hardware structure of a terminal provided in some embodiments of this application;

[0029] Figure 12 These are schematic diagrams of the hardware structure of network-side devices provided in some embodiments of this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0031] The following explains some terms and nouns used in the embodiments of this application.

[0032] An IP address is a unique logical address used to identify network devices, such as computers, routers, mobile phones, or PCs. It enables communication between devices based on the TCP / IP protocol. Common formats include IPv4, such as 192.168.1.1, and IPv6, such as 2001:0db8:85a3::8a2e:0370:7334.

[0033] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0034] The terms "first," "second," etc., used in this application's specification are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, in the specification, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0035] The terms "at least one," "at least one," etc., used in this application's specification refer to any one, any two, or a combination of two or more of the included objects. For example, "at least one of a, b, and c" can mean: "a," "b," "c," "a and b," "a and c," "b and c," and "a, b, and c," where a, b, and c can be single or multiple. Similarly, "at least two" refers to two or more, and its meaning is similar to that of "at least one."

[0036] The identifiers in this application are text, symbols, images, etc. used to indicate information, and may be used as carriers for displaying information in the form of identifiers or other containers, including but not limited to text identifiers, image identifiers, symbol identifiers, etc.

[0037] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0038] The terminal in this application embodiment can also be referred to as user equipment (UE). The terminal can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the embodiments in this application do not limit the specific type of terminal.

[0039] In the embodiments of this application, the network-side equipment may include access network equipment or core network equipment. The access network equipment may also be referred to as a Radio Access Network (RAN) device, a Radio Access Network function, or a Radio Access Network unit. The access network equipment may include a base station, a Wireless Local Area Network (WLAN) access point (AP), or a Wireless Fidelity (WiFi) node, etc. Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), and Non-Terrestrial Network (NTN) equipment (such as satellite or high-altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0040] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Function (BSF), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0041] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0042] The IP address allocation method, IP address acquisition method, apparatus, and electronic device provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0043] Currently, in the 3rd Generation Partnership Project (3GPP) protocol standard, the way for a terminal to obtain an IP address is: it is allocated by the network-side equipment, specifically, it is obtained through certain signaling processes between the terminal and the network-side equipment.

[0044] In related technologies, each time a terminal registers and joins the network, it obtains an IP address assigned to it by the network-side device through a specific signaling process. After obtaining the internal network IP address assigned by the operator's network-side device, the terminal will be mapped to an external network address through its firewall, thereby accessing the Internet or a specific network domain to realize information interaction between the terminal and the business server, such as using instant messaging applications to chat or using video applications to watch videos.

[0045] Typically, network-side devices assign IP addresses to terminals in two ways: dynamic IP address allocation and static IP address allocation. Dynamic IP address allocation is the most common method for terminals to obtain an IP address from the operator's intranet. Each time a terminal requests an IP address from the network-side device, the device selects an IP address from its available IP address pool, often assigning a different IP address than the one previously assigned.

[0046] However, with the development of 5G private networks, edge computing, video surveillance, and the Internet of Things (IoT), the demand for static IP addresses by terminals in a communication network is increasing. Communication between terminals and business servers based on the TCP / IP protocol typically requires fixed IP addresses, i.e., static IP addresses. If network-side devices use dynamic IP address allocation, assigning a different IP address to each terminal each time, it will prevent communication between the terminal and the business server. For example, it will mainly affect downlink data transmission, causing the server to fail to transmit data to the terminal. Thus, dynamic IP address allocation cannot meet the usage requirements of these business areas and seriously affects the communication user experience, thereby reducing the possibility of applying communication technology in different fields.

[0047] As mentioned above, in the current 3GPP, operators typically use dynamic IP address allocation to assign IP addresses to terminals via their core networks. However, this method results in complex and unreliable communication links between service servers and their corresponding terminals, and significantly increases industrial costs. With the development of mobile communication applications in various fields and scenarios, and the increasing demand for static IP addresses from terminals, static IP address allocation may gradually become the primary means of assigning IP addresses to terminals.

[0048] However, if network-side devices use static IP address allocation, specific configurations are required on the network-side devices for the end-user's subscription data to ensure that the network-side devices assign the same IP address each time an IP address is allocated to the end-user. Therefore, currently, the implementation of static IP address allocation either involves complex management processes on the operator's side to operate on single-user subscription information, or it requires specific modifications to the operator's core network architecture. However, such modifications are usually not standardized and can only be applied to a specific modified network.

[0049] Therefore, the current 3GPP mechanism for allocating terminal IP addresses does not meet the development and application needs of various industries, and it is necessary to improve the design of network-side equipment's ability to allocate static IP addresses to specific terminals.

[0050] In the IP address allocation method provided in this application embodiment, the network-side device receives request information sent by the terminal. The request information includes a capability requirement identifier, which indicates that the terminal requires a static IP address. Based on the capability information, the network-side device allocates a target static IP address to the terminal. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the network-side device can trigger the allocation of a static IP address to the terminal based on the terminal's capability information requiring a static IP address, and continuously allocate this static IP address to the terminal within a preset time period, thereby ensuring that the service server and the terminal can access each other and communicate normally.

[0051] The execution entity of the IP address allocation method provided in this application embodiment can be an IP address allocation device. Exemplarily, the IP address allocation device can be a network-side device, or a network element within that network-side device, such as an AMF, SMF, or UPF. The following will use a network-side device as an example to executor the IP address allocation method provided in this application embodiment.

[0052] This application provides an IP address allocation method. Figure 1 A flowchart illustrating an IP address allocation method provided in an embodiment of this application is shown. This method can be applied to network-side devices. Figure 1 As shown, the IP address allocation method provided in this application embodiment may include the following steps 201 and 202.

[0053] Step 201: The network-side device receives the request information sent by the terminal.

[0054] In some embodiments of this application, the request information includes a requirement capability identifier.

[0055] In some embodiments of this application, the aforementioned requirement capability identifier is used to indicate that the terminal requires a static IP address.

[0056] In some embodiments of this application, the aforementioned required capability identifier is obtained from the request information sent by the terminal.

[0057] For example, the aforementioned requirement capability identifier can be obtained from the information carried in the request signaling sent from the terminal.

[0058] In some embodiments of this application, the aforementioned requirement capability identifier is used to characterize that the terminal currently needs to use a fixed IP address for a period of time, i.e., a static IP address.

[0059] In some embodiments of this application, the aforementioned static IP address is an IP address assigned to the terminal by the network-side device using a static IP address allocation method.

[0060] In some embodiments of this application, the above-mentioned static IP address allocation method is a method in which the network-side device allocates the same IP address to the terminal every time the terminal initiates a request.

[0061] It is understandable that the counterpart to a static IP address is a dynamic IP address. A dynamic IP address is an IP address assigned to a terminal by the network-side device using a dynamic IP address allocation method. This dynamic IP address allocation method involves the network-side device randomly assigning a different IP address to the terminal each time it initiates a request.

[0062] In some embodiments of this application, the above-mentioned request information includes any of the following: registration request, re-registration request, PDU (Protocol Data Unit) session establishment request, attach request, and Public Data Network (PDN) connection request.

[0063] For example, the above registration request and re-registration request are request information for a terminal requesting registration or re-registration in 5G.

[0064] For example, the above attachment request is a request information for a terminal to register in 4G.

[0065] For example, when a terminal initiates a registration request, the aforementioned required capability identifier can be carried in the registration request signaling.

[0066] For example, when a terminal initiates a re-registration request, if the terminal has completed deregistration, the terminal needs to send a re-registration request to the network-side device. At this time, the aforementioned required capability identifier can be carried in the re-registration request signaling.

[0067] For example, when a terminal initiates a PDU session establishment request, the aforementioned required capability identifier can be carried in the PDU session establishment request signaling.

[0068] Step 202: The network-side device assigns a target static IP address to the terminal based on the required capability identifier.

[0069] In some embodiments of this application, the target static IP address is a dedicated IP address that the terminal can use within a preset time period.

[0070] In some embodiments of this application, the aforementioned dedicated IP address is used to indicate that the IP address is for the exclusive use of the terminal within a preset time period.

[0071] In some embodiments of this application, the aforementioned preset duration can be user-defined, default to the network-side device, or agreed upon by the protocol.

[0072] For example, the preset duration can be the timing duration of a timer.

[0073] In some embodiments of this application, when the network-side device receives a terminal's required capability identifier, and the required capability identifier indicates that the terminal requires a static IP address, it selects an unused IP address as the terminal's target static IP address and assigns the target static IP address to the terminal.

[0074] In some embodiments of this application, the network-side device assigns a target static IP address to the terminal via instruction signaling.

[0075] Optionally, in some embodiments of this application, when the network-side device allows the terminal to use a static IP address and supports the ability to allocate a static IP address, the network-side device allocates a target static IP address to the terminal based on the required capability identifier.

[0076] It is understandable that the above statement "the network-side device allows the terminal to use a static IP address and supports the allocation of a static IP address" indicates that the network-side device has the ability to allocate a static IP address to the terminal and believes that the requesting terminal can be authorized to use the target static IP address allocated by the network-side device.

[0077] In the IP address allocation method provided in this application embodiment, the network-side device receives request information sent by the terminal. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. Based on the capability information, the network-side device allocates a target static IP address to the terminal. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the network-side device can trigger the allocation of a static IP address to the terminal based on the terminal's required static IP address capability information, and continuously allocate the static IP address to the terminal within a preset time period, thereby ensuring that the service server and the terminal can access each other and communicate normally.

[0078] Optionally, in some embodiments of this application, step 202 described above can be implemented by step 202a described below.

[0079] Step 202a: Based on the required capability identifier, the network-side device selects an unused IP address from the first IP address set or the second IP address set as the target static IP address, and assigns the target static IP address to the terminal.

[0080] In some embodiments of this application, the first IP address set is allocated to terminals that have the ability to use static IP addresses.

[0081] For example, the aforementioned first set of IP addresses can be a static IP address pool, and the IP addresses in the static IP address pool are only available to terminals that require static IP addresses.

[0082] It is understandable that when the network-side device uses a static IP address allocation method, the network-side device can select an unused IP address from the aforementioned static IP address pool and allocate it to the terminal as the target static IP address.

[0083] In some embodiments of this application, the second IP address set is allocated to any terminal.

[0084] For example, the aforementioned second set of IP addresses can be a dynamic IP address pool, in which IP addresses can be assigned to any terminal for use. That is, regardless of whether the terminal has the ability to require a static IP address, an IP address from the dynamic IP address pool can be assigned to the terminal.

[0085] It is understandable that regardless of whether the network-side device uses a static IP address allocation method or a dynamic IP address allocation method, the network-side device can select unused IP addresses from the aforementioned dynamic IP address pool and allocate them to the terminal.

[0086] In this way, the network-side device selects an IP address from the corresponding set of IP addresses based on different IP address allocation methods, thereby improving the flexibility of the network-side device in allocating IP addresses to the terminal.

[0087] Optionally, in some embodiments of this application, after step 202 above, the IP address allocation method provided by the embodiments of this application further includes steps 203 and 204.

[0088] Step 203: The network-side device starts the first timer.

[0089] In some embodiments of this application, after the network-side device assigns a target static IP address to the terminal, a first timer is started.

[0090] Step 204: During the duration of the first timer, the network-side device does not assign the target static IP address to other terminals.

[0091] In some embodiments of this application, the aforementioned timing duration is either agreed upon according to a protocol or customized, and this application does not impose any restrictions.

[0092] In some embodiments of this application, the target static IP address is not assigned to other terminals during the duration of the first timer. That is, the network-side device can set the target static IP address to a dedicated state, and when the IP address is in this state, the IP address is only available for use by the terminal corresponding to that IP address.

[0093] In some embodiments of this application, the target static IP address is used only by the terminal in the above-mentioned dedicated state, that is, in the above-mentioned dedicated state, other terminals outside of the terminal are displayed as disabled.

[0094] It is understandable that once a terminal is assigned a target static IP address, the terminal and that target static IP address are associated. Each time the terminal needs a static IP address assigned by the network-side device, the network-side device assigns the target static IP address in that dedicated state to the terminal.

[0095] In this way, the network-side equipment can ensure that the target static IP address corresponding to the terminal will not be used by other terminals, thus ensuring the accuracy of IP address allocation.

[0096] Optionally, in some embodiments of this application, after step 202 above, the IP address allocation method provided in this application includes step 205.

[0097] Step 205: The network-side device saves the target static IP address to the corresponding subscription data of the terminal.

[0098] In some embodiments of this application, the aforementioned contract data is data stored in the contract data network element.

[0099] In some embodiments of this application, the aforementioned contracted data network element includes the IP address information corresponding to each terminal.

[0100] For example, when the IP address of a terminal changes, the network-side device updates the IP address corresponding to that terminal in the subscribed data network element.

[0101] In this way, when assigning IP addresses to terminals, network-side devices can first obtain the IP address based on the subscription data corresponding to the terminal, thus simplifying the process of obtaining the IP address.

[0102] The execution subject of the IP address acquisition method provided in this application embodiment can be an IP address acquisition device. Exemplarily, the IP address acquisition device can be an electronic device or a terminal, or a component within the electronic device or terminal, such as an integrated circuit or a chip. The following will use a terminal as an example to executively describe the IP address acquisition method provided in this application embodiment.

[0103] This application provides a method for obtaining an IP address. Figure 2 A flowchart illustrating an IP address acquisition method provided in an embodiment of this application is shown. This method can be applied to electronic devices. Figure 2 As shown, the IP address acquisition method provided in this application embodiment may include the following steps 301 and 302.

[0104] Step 301: The terminal sends a request message to the network-side device.

[0105] In some embodiments of this application, the request information includes a requirement capability identifier.

[0106] In some embodiments of this application, the aforementioned requirement capability identifier is used to indicate that the terminal requires a static IP address.

[0107] In some embodiments of this application, the aforementioned required capability identifier is obtained from the request information sent by the terminal.

[0108] For example, the aforementioned requirement capability identifier can be obtained from the information carried in the request signaling sent from the terminal.

[0109] In some embodiments of this application, the aforementioned requirement capability identifier is used to characterize that the terminal currently needs to use a fixed IP address for a period of time, i.e., a static IP address.

[0110] In some embodiments of this application, the aforementioned static IP address is an IP address assigned to the terminal by the network-side device using a static IP address allocation method.

[0111] In some embodiments of this application, the above-mentioned static IP address allocation method is a method in which the network-side device allocates the same IP address to the terminal every time the terminal initiates a request.

[0112] It is understandable that the counterpart to a static IP address is a dynamic IP address. A dynamic IP address is an IP address assigned to a terminal by the network-side device using a dynamic IP address allocation method. This dynamic IP address allocation method involves the network-side device randomly assigning a different IP address to the terminal each time it initiates a request.

[0113] In some embodiments of this application, the above request information includes any of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

[0114] For example, the above registration request and re-registration request are request information for a terminal requesting registration or re-registration in 5G.

[0115] For example, the above attachment request is a request information for a terminal to register in 4G.

[0116] For example, when a terminal initiates a registration request, the aforementioned required capability identifier can be carried in the registration request signaling.

[0117] For example, when a terminal initiates a re-registration request, if the terminal has completed deregistration, the terminal needs to send a re-registration request to the network-side device. At this time, the aforementioned required capability identifier can be carried in the re-registration request signaling.

[0118] For example, when a terminal initiates a PDU session establishment request, the aforementioned required capability identifier can be carried in the session establishment request signaling.

[0119] Optionally, in some embodiments of this application, step 301 described above can be implemented by step 301a described below.

[0120] Step 301a: The terminal sends a request signaling to the network-side device.

[0121] In some embodiments of this application, the aforementioned request signaling carries a required capability identifier.

[0122] In some embodiments of this application, the above-mentioned request signaling is any one of the following: registration request signaling, re-registration request signaling, PDU session establishment request signaling, attach request signaling, and PDN connection request signaling.

[0123] In some embodiments of this application, enabling the static IP address function indicates that the terminal has a need to use a static IP address. Disabling the static IP address function indicates that the terminal does not have a need to use a static IP address.

[0124] For example, the terminal can use a switch control to control whether the static IP address function is enabled or disabled.

[0125] In the IP address acquisition method provided in this application embodiment, the terminal sends request information to the network-side device. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. The terminal receives response information from the network-side device, which includes a target static IP address allocated to the terminal by the network-side device. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the terminal triggers the network-side device to allocate a static IP address to the terminal by sending request information carrying a required capability identifier indicating the need for a static IP address. This static IP address is continuously allocated to the terminal within a preset time period, thereby ensuring that the service server and the terminal can access each other and communicate normally.

[0126] Optionally, in some embodiments of this application, before step 301 above, the IP address acquisition method provided in this application embodiment further includes steps 303 and 304.

[0127] Step 303: The terminal receives the user's first input to the static IP address switch control.

[0128] Step 304: The terminal responds to the first input and enables the static IP address function.

[0129] In some embodiments of this application, the first input is used to enable the static IP address function.

[0130] In some embodiments of this application, the first input may include touch input by the user clicking on the first page, or voice command input by the user, or specific gesture input by the user. The specific input may be determined according to actual usage needs, and this application does not limit it.

[0131] For example, the aforementioned touch input includes user swiping input or clicking input on the display screen of the electronic device. Specific gestures in this application embodiment can be any one of a single-click gesture, a swipe gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the clicking input in this application embodiment can be a single-click input, a double-tap input, or any number of clicks, etc., and the aforementioned clicking input can also be a long-press input or a short-press input.

[0132] In some embodiments of this application, the above-described static IP address switch control is used to control the enabling or disabling of the static IP address function.

[0133] In some embodiments of this application, the static IP address switch control includes an on state and an off state.

[0134] For example, when the above-mentioned static IP address switch control is in the on state, the static IP address function is enabled.

[0135] For example, when the above-mentioned static IP address switch control is in the off state, the static IP address function is disabled.

[0136] For example, such as Figure 3 As shown, in the network settings interface 31 of the terminal, the static IP address switch control 32 is displayed, and at this time the static IP address switch control 32 is in the on state.

[0137] It is understandable that enabling the static IP address function mentioned above can be interpreted as enabling the function of requiring a static IP address on the terminal.

[0138] In this way, the terminal can flexibly choose whether or not it needs a static IP address according to its business needs, thereby improving the flexibility of obtaining a static IP address.

[0139] The following description, in conjunction with the accompanying drawings, provides an exemplary illustration of the signaling interaction process between the terminal and network-side devices for obtaining and allocating IP addresses.

[0140] Example 1: In a 5G scenario, if the terminal is not currently registered in the network, when the terminal initiates registration with the network-side device and enables the static IP address switch, a negotiation mechanism between the network side and the terminal will be initiated. The terminal reports its requirement for a static IP address to the network-side device through the following specific signaling procedure. The network-side device, according to its own policy, allocates a static IP address to the terminal, namely the aforementioned target static IP address. Furthermore, the terminal will obtain the same IP address allocated to it by the network side each time it registers with the network.

[0141] like Figure 4 and Figure 5 As shown, the above IP address allocation method and IP address acquisition method include the following steps A1 to A8, wherein, Figure 4 This is a flowchart illustrating the signaling interaction between the terminal and network-side equipment. Figure 5 This is a flowchart illustrating the strategy for terminals to obtain static IP addresses allocated by the network side.

[0142] Step A1: The terminal initiates a registration request (Attach Request) to the mobility and session management network element, reporting the requirement to enable the static IP address capability.

[0143] In this embodiment, the terminal initiates a terminal registration request to the core network, i.e., the mobility and session management network element of the aforementioned network-side equipment, via the wireless access point.

[0144] Step A1-1: Before the terminal initiates a registration request to the mobility and session management network element, the terminal sets the static IP address switch control to the on state to enable the static IP address function.

[0145] Step A1-2: The terminal includes the required capability identifier in the registration request signaling element sent to the network-side device.

[0146] It should be noted that the aforementioned mobility and session management network elements may include at least one of SMF, AMF, or UPF. The inclusion of a required capability identifier in the information element can also be represented by setting the static IP address requirement in the information element to True.

[0147] Step A2: The terminal and the core network complete authentication and authorization.

[0148] In this embodiment, during the authentication and authorization process described above, the mobility and session management network element in the core network obtains or updates the terminal's subscription data from the subscription data network element.

[0149] It should be noted that if a static IP address is configured between the terminal and the operator during the contract signing process, the network-side device can directly select the static IP address as the target static IP address.

[0150] Step A3: The core network terminal mobility and session management network element sends a registration request acceptance signaling to the terminal.

[0151] Step A4: The terminal replies to the mobility and session management network element of the core network via the wireless access point to confirm registration completion.

[0152] Step A5: The terminal initiates a PDU session establishment request.

[0153] It should be noted that after the terminal completes step A4, it can immediately execute step A5, or it can execute step A5 after a period of time. This embodiment does not impose any restrictions.

[0154] Step A6: The mobility and session management network element of the core network obtains or updates the terminal subscription data from the subscription data network element.

[0155] Step A7: The core network establishes a PDU session for the terminal, sends a PDU session establishment acceptance message to the terminal, and sends the assigned target static IP address to the terminal.

[0156] In this embodiment, upon receiving capability information reported by the terminal, the network-side device decides, based on its own policies and capabilities, whether to assign a static IP address to the terminal.

[0157] Understandably, network-side devices decide whether to assign a static IP address to a terminal based on their own capabilities—whether they allow the user to use a static IP address or whether they support the ability to assign static IP addresses. For example, by default, network-side devices allow this capability for all IoT cards and private network user cards, but do not support it for other user cards.

[0158] Step A7-1: If the network-side device decides to assign a static IP address to the terminal, proceed to step A7-2. Otherwise, proceed to step A7-4.

[0159] Step A7-2: The network-side device allocates an unused IP address for this terminal from the static IP address pool (i.e., the first IP address set mentioned above) or the dynamic IP address pool (i.e., the second IP address set), and starts the static IP address switch timer (i.e., the first timer mentioned above).

[0160] For example, if the duration of the first timer is 7 days, then within those 7 days, regardless of whether the IP address has been assigned to this terminal, the network-side device will not assign the IP address to other terminals, and will record and update the information of this static IP address in the contracted data network element of the network-side device.

[0161] Step A7-3: In each signaling process such as terminal registration and network access, if the terminal requests an IP address and enables the static IP address switch, the network-side device will assign this IP address to the terminal and refresh the static IP address switch timer.

[0162] Step A7-4: The network-side device randomly assigns a dynamic IP address to the terminal.

[0163] Step A8: The wireless access point and terminal complete the Radio Resource Control (RRC) configuration.

[0164] Thus, this embodiment provides a method for terminals to autonomously decide and choose to obtain a static IP address. Each time a terminal registers and uses the communication services provided by the operator, it can autonomously decide whether it needs to obtain a static IP address to meet its business requirements. This solves the problem of service servers and terminals being unable to communicate with each other due to network-side devices randomly assigning a new dynamic IP address because of terminal re-registration, thereby improving the application capabilities of mobile communication in areas such as 5G private networks and edge computing.

[0165] For example, after a terminal activates the static IP address requirement switch, it immediately initiates a registration and network access request and a PDU session establishment request to negotiate with the network side for a static IP address. Simultaneously, in the network-side device's signaling process, the subscribed data network element records / updates this static IP address information. After the terminal obtains a static IP address for the first time, the network-side device will reserve the right to allocate this IP address for the terminal regardless of whether it is currently online or performs re-registration. Each time the terminal initiates an IP address request process with the network-side device within the preset duration of a subsequent timer (and the static IP address requirement switch is activated), it will be allocated the previous IP address, and the timer will be refreshed. Furthermore, if the preset timer duration has elapsed since the terminal requested a static IP address, and the IP address has been reclaimed by the network-side device (e.g., the terminal may have been powered off or disconnected from the network), the network-side device will no longer retain the specific allocation of this IP address and can allocate it to other registered terminals. It should be noted that the network-side device stops retaining the specific allocation of this IP address by updating the terminal's subscription data. After the timer expires, the subscribed data network element deletes the static IP address information from the terminal's subscription data.

[0166] Example 2: In a 5G scenario, if the terminal is already registered in the network, it needs to initiate a deregistration process with the network-side device first. Then, the terminal actively re-initiates the registration and network access process and the PDU session establishment process. When the terminal initiates registration with the network-side device and the static IP address switch is enabled, a negotiation mechanism between the network side and the terminal will be initiated. The terminal reports its requirement for a static IP address to the network-side device through the following specific signaling process. The network-side device allocates a static IP address to the terminal according to its own policy, namely the aforementioned target static IP address. Furthermore, the terminal will obtain the same IP address allocated to it by the network side each time it registers and accesses the network (and the static IP address requirement switch is enabled).

[0167] like Figure 6 As shown, the above IP address allocation method and IP address acquisition method include the following steps A1 to A9, wherein, Figure 6 This is a flowchart of the signaling interaction between the terminal and the network-side equipment.

[0168] Step A1: The terminal initiates a registration request to the contracted data network element.

[0169] For example, the above request type is re-registration.

[0170] Step A2: The terminal initiates a registration request (Attach Request) to the mobility and session management network element, reporting the requirement to enable the static IP address capability.

[0171] In this embodiment, after the terminal completes the deregistration process, it initiates a registration request to the mobility and session management network element.

[0172] In this embodiment, the terminal initiates a terminal registration request to the core network, i.e., the mobility and session management network element of the aforementioned network-side equipment, via the wireless access point.

[0173] Step A2-1: Before the terminal initiates a registration request to the mobility and session management network element, the terminal sets the static IP address switch control to the on state to enable the static IP address function.

[0174] Step A2-2: The terminal includes a required capability identifier in the registration request signaling element sent to the network-side device, which is a capability identifier used to indicate the above-mentioned capability information.

[0175] It should be noted that the aforementioned mobility and session management network elements may include at least one of SMF, AMF, or UPF.

[0176] Step A3: The terminal and the core network complete authentication and authorization.

[0177] In this embodiment, during the authentication and authorization process described above, the mobility and session management network element in the core network obtains or updates the terminal's subscription data from the subscription data network element.

[0178] It should be noted that if a static IP address is configured between the terminal and the operator during the contract signing process, the network-side device can directly select the static IP address as the target static IP address.

[0179] Step A4: The core network terminal mobility and session management network element sends a registration request acceptance signaling to the terminal.

[0180] Step A5: The terminal replies to the mobility and session management network element of the core network via the wireless access point to confirm registration completion.

[0181] Step A6: The terminal initiates a PDU session establishment request.

[0182] It should be noted that after the terminal completes step A4, it can immediately execute step A5, or it can execute step A5 after a period of time. This embodiment does not impose any restrictions.

[0183] Step A7: The mobility and session management network element of the core network obtains or updates the terminal subscription data from the subscription data network element.

[0184] Step A8: The core network establishes a PDU session for the terminal, sends a PDU session establishment acceptance message to the terminal, and sends the assigned target static IP address to the terminal.

[0185] In this embodiment, upon receiving capability information reported by the terminal, the network-side device decides, based on its own policies and capabilities, whether to assign a static IP address to the terminal.

[0186] Understandably, network-side devices decide whether to assign a static IP address to a terminal based on their own capabilities—whether they allow the user to use a static IP address or whether they support the ability to assign static IP addresses. For example, by default, network-side devices allow this capability for all IoT cards and private network user cards, but do not support it for other user cards.

[0187] Step A8-1: If the network-side device decides to assign a static IP address to the terminal, proceed to step A8-2. Otherwise, proceed to step A8-4.

[0188] Step A8-2: The network-side device allocates an unused IP address for this terminal from the static IP address pool (i.e., the first IP address set mentioned above) or the dynamic IP address pool (i.e., the second IP address set), and starts the static IP address switch timer (i.e., the first timer mentioned above).

[0189] For example, if the duration of the first timer is 7 days, then within those 7 days, regardless of whether the IP address has been assigned to this terminal, the network-side device will not assign the IP address to other terminals, and will record and update the information of this static IP address in the contracted data network element of the network-side device.

[0190] It should be noted that if a terminal initiates a PDU session release or deregistration request process, such as when the phone switches airplane mode on or off, or when the phone is powered on or off, or if the network-side device forcibly releases the IP address, or if the user's subscription data changes, such as during core network version upgrades or maintenance, or when the phone's data plan changes, the network-side device will release the IP address assigned to the terminal. This IP address may then be assigned to other terminals.

[0191] Step A8-3: In each signaling process such as terminal registration and network access, if the terminal requests an IP address, the network-side device will assign this IP address to the terminal and refresh the static IP address switch timer.

[0192] Step A8-4: The network-side device randomly assigns a dynamic IP address to the terminal.

[0193] Step A9: The wireless access point and terminal complete the Radio Resource Control (RRC) configuration.

[0194] Thus, this embodiment provides a method for terminals to autonomously decide and choose to obtain a static IP address. Each time a terminal registers and uses the communication services provided by the operator, it can autonomously decide whether it needs to obtain a static IP address to meet its business requirements. This solves the problem of service servers and terminals being unable to communicate with each other due to network-side devices randomly assigning a new dynamic IP address because of terminal re-registration, thereby improving the application capabilities of mobile communication in areas such as 5G private networks and edge computing.

[0195] It should be noted that when a terminal registers for network access based on different Data Network Name (DNN) / Access Point Name (APN), it can adopt different strategies for obtaining an IP address.

[0196] For example, the terminal is equipped with two types of IP address acquisition switches: one is a global terminal static IP address acquisition switch, and the other is a static IP address acquisition switch based on DNN / APN.

[0197] For example, when the same terminal registers with DNN1, it obtains a static IP address. When it registers with DNN2, the network-side device still assigns it a dynamic IP address.

[0198] This allows for improved personalization strategies for terminals and increased utilization of the IP address pool on the network side.

[0199] Each of the above-described method embodiments, or various possible implementations of each method embodiment, can be executed individually or in combination of any two or more. The specific implementation can be determined according to actual usage requirements, and this application does not impose any restrictions on this.

[0200] It should be noted that the above-described method embodiments can be applied to both 5G and 4G networks.

[0201] When the terminal is assigned an IPv4 address, it can be used normally. When the terminal is assigned an IPv6 address prefix (an IPv6 address consists of two parts: a network prefix and an interface identifier), the terminal generates an interface identifier based on the MAC address (EUI-64) and obtains the complete IPv6 address before it can be used normally.

[0202] This application provides an IP address allocation device. As an example, the IP address allocation device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can include, but is not limited to, the types of terminals listed above, and the network-side device can include, but is not limited to, the types of network-side devices listed above. This application does not impose specific limitations.

[0203] The IP address allocation device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as Central Processing Units (CPUs), microprocessors, Digital Signal Processors (DSPs), Artificial Intelligence (AI) processors, Graphics Processing Units (GPUs), Application Specific Integrated Circuits (ASICs), Network Processors (NPs), Field Programmable Gate Arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0204] For details, see Figure 7 When the IP address allocation device is a network-side device or a component of a network-side device, the IP address allocation device 600 includes a receiving module 601 and a processing module 602.

[0205] The receiving module 601 is used to receive request information sent by the terminal. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address.

[0206] The aforementioned processing module 602 is used to allocate a target static IP address to the aforementioned terminal based on the aforementioned required capability identifier.

[0207] The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, Protocol Data Unit (PDU) session establishment request, attach request, and Public Data Network (PDN) connection request.

[0208] Optionally, in some embodiments of this application, the processing module 602 is specifically used to allocate a target static IP address to the terminal based on the required capability identifier, provided that the network-side device allows the terminal to use a static IP address and supports the ability to allocate static IP addresses.

[0209] Optionally, in some embodiments of this application, the processing module 602 is specifically used to select an unused IP address from the first IP address set or the second IP address set as the target static IP address based on the demand capability identifier, and to allocate the target static IP address to the terminal.

[0210] The first set of IP addresses is allocated to terminals that have the ability to use static IP addresses; the second set of IP addresses is allocated to any terminal.

[0211] Optionally, in some embodiments of this application, the processing module 602 is further configured to start a first timer after allocating a target static IP address to the terminal based on the aforementioned requirement capability identifier.

[0212] The aforementioned processing module 602 is also configured to prevent the target static IP address from being assigned to other terminals during the duration of the first timer.

[0213] Optionally, in some embodiments of this application, the processing module 602 is further configured to allocate a target static IP address to the terminal based on the required capability identifier, and then save the target static IP address to the subscription data corresponding to the terminal.

[0214] In the IP address allocation device provided in this application embodiment, the IP address allocation device receives request information sent by a terminal. The request information includes a capability requirement identifier, which indicates that the terminal requires a static IP address. Based on the capability information, the IP address allocation device allocates a target static IP address to the terminal. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the IP address allocation device can trigger the allocation of a static IP address to the terminal based on the terminal's capability information requiring a static IP address, and continuously allocate this static IP address to the terminal within a preset time period. This allows the IP address allocation device to allocate a fixed IP address to the terminal for its use, thereby ensuring normal communication between the terminal and the service server.

[0215] For details, see Figure 8 When the IP address acquisition device is a terminal or a component in a terminal, the IP address acquisition device 700 includes a sending module 701 and a receiving module 702.

[0216] The aforementioned sending module 701 is used to send request information to the network-side device. The request information includes a required capability identifier, which is used to indicate that the terminal requires a static IP address.

[0217] The receiving module 702 is used to receive response information sent by the network-side device, the response information including the target static IP address allocated by the network-side device to the terminal.

[0218] The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

[0219] Optionally, in some embodiments of this application, combined with Figure 8 ,like Figure 9 As shown, the above-mentioned device 700 also includes a processing module 703; the above-mentioned receiving module 702 is further used to receive the user's first input on the static IP address switch control before sending request information to the network-side device;

[0220] The aforementioned processing module 703 is used to enable the aforementioned static IP address function in response to the aforementioned first input.

[0221] In the IP address acquisition device provided in this application embodiment, the IP address acquisition device sends request information to the network-side device. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. The IP address acquisition device receives response information sent by the network-side device. The response information includes a target static IP address allocated to the terminal by the network-side device. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request. In this solution, the IP address acquisition device triggers the network-side device to allocate a static IP address to the terminal by sending request information carrying a required capability identifier indicating the need for a static IP address. This static IP address is continuously allocated to the IP address acquisition device within a preset time period, enabling the IP address acquisition device to communicate normally with the service server using the target static IP address.

[0222] The IP address allocation device provided in this application embodiment can achieve... Figure 1 The method implementation embodiments achieve the same technical effect by implementing each process, and the provided IP address acquisition method can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0223] like Figure 10As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described IP address allocation method and IP address acquisition method embodiments, and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above-described IP address allocation method embodiment; when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described IP address acquisition method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0224] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 2 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 8 and Figure 9 The IP address acquisition device shown. Specifically, Figure 11 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0225] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0226] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 11 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0227] It should be understood that, in this embodiment, the input unit 104 may include a graphics processor 1041 and a microphone 1042. The graphics processor 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0228] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 101 can transmit it to the processor 110 for processing; in addition, the radio frequency unit 101 can send uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0229] The memory 109 can be used to store software programs or instructions, as well as various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.), etc. Furthermore, the memory 109 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (Synchlink DRAM, SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0230] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0231] The radio frequency unit 101 is used to send request information to the network side device. The request information includes a required capability identifier, which is used to indicate that the terminal requires a static IP address.

[0232] The radio frequency unit 101 is also used to receive response information sent by the network-side device, the response information including the target static IP address allocated by the network-side device to the terminal.

[0233] The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

[0234] Optionally, in some embodiments of this application, the user input unit 107 described above is further configured to receive the user's first input to the static IP address switch control before sending request information to the network-side device;

[0235] The processor 110 is configured to enable the static IP address function in response to the first input.

[0236] In the terminal provided in this application embodiment, the terminal sends request information to the network-side device. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. The terminal receives response information from the network-side device, which includes a target static IP address allocated to the terminal by the network-side device. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the terminal triggers the network-side device to allocate a static IP address to the terminal by sending request information carrying a required capability identifier indicating the need for a static IP address. This static IP address is continuously allocated to the terminal within a preset time period, enabling the terminal to communicate normally with the service server using the target static IP address.

[0237] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0238] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 1 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0239] Specifically, embodiments of this application also provide a network-side device. For example... Figure 12 As shown, the network-side device 900 includes: a processor 901, a network interface 902, and a memory 903. This network-side device can be... Figure 7The IP address allocation device shown is illustrated. The network interface 902 is, for example, a common public radio interface (CPRI).

[0240] The network interface 902 is used to receive request information sent by the terminal. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address.

[0241] The aforementioned processor 901 is used to assign a target static IP address to the aforementioned terminal based on the aforementioned required capability identifier;

[0242] The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, Protocol Data Unit (PDU) session establishment request, attach request, and Public Data Network (PDN) connection request.

[0243] Optionally, in some embodiments of this application, the processor 901 is specifically used to allocate a target static IP address to the terminal based on the required capability identifier, provided that the network-side device allows the terminal to use a static IP address and supports the ability to allocate static IP addresses.

[0244] Optionally, in some embodiments of this application, the processor 901 is specifically used to select an unused IP address from a first IP address set or a second IP address set as the target static IP address based on the required capability identifier, and to allocate the target static IP address to the terminal.

[0245] The first set of IP addresses is allocated to terminals that have the ability to use static IP addresses; the second set of IP addresses is allocated to any terminal.

[0246] Optionally, in some embodiments of this application, the processor 901 is further configured to start a first timer after allocating a target static IP address to the terminal based on the aforementioned required capability identifier.

[0247] The processor 901 is also configured to not assign the target static IP address to other terminals during the duration of the first timer.

[0248] Optionally, in some embodiments of this application, the processor 901 is further configured to allocate a target static IP address to the terminal based on the aforementioned requirement capability identifier, and then save the target static IP address to the subscription data corresponding to the terminal.

[0249] In the network-side device provided in this application embodiment, the network-side device receives request information sent by a terminal. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. Based on the capability information, the network-side device allocates a target static IP address to the terminal. The target static IP address is a dedicated IP address that the terminal can use within a preset time period. The request information includes at least one of the following: a registration request, a re-registration request, a PDU session establishment request, an attach request, or a PDN connection request. In this solution, the network-side device can trigger the allocation of a static IP address to the terminal based on the terminal's required static IP address capability information, and continuously allocate this static IP address to the terminal within a preset time period. This allows the network-side device to allocate a fixed IP address to the terminal for its use, thereby ensuring communication between the terminal and the network-side device.

[0250] Furthermore, the network-side device 900 in this embodiment of the application also includes: a program or instructions stored in a memory 903 and executable on a processor 901, wherein the processor 901 calls the program or instructions in the memory 903 to execute. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0251] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described IP address allocation method and IP address acquisition method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0252] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0253] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described IP address allocation method and IP address acquisition method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0254] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0255] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the IP address allocation method and IP address acquisition method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0256] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0257] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0258] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for allocating network protocol IP addresses, characterized in that, The method includes: The network-side device receives a request message sent by the terminal. The request message includes a required capability identifier, which indicates that the terminal requires a static IP address. The network-side device assigns a target static IP address to the terminal based on the required capability identifier; The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, Protocol Data Unit (PDU) session establishment request, attach request, and Public Data Network (PDN) connection request.

2. The method according to claim 1, characterized in that, The network-side device allocates a target static IP address to the terminal based on the required capability identifier, including: If the network-side device allows the terminal to use a static IP address and supports the ability to allocate static IP addresses, the network-side device allocates a target static IP address to the terminal based on the required capability identifier.

3. The method according to claim 1, characterized in that, The network-side device allocates a target static IP address to the terminal based on the required capability identifier, including: Based on the required capability identifier, the network-side device selects an unused IP address from the first IP address set or the second IP address set as the target static IP address, and assigns the target static IP address to the terminal. The first set of IP addresses is allocated to terminals that have the ability to use static IP addresses; the second set of IP addresses is allocated to any terminal.

4. The method according to claim 1, characterized in that, After the network-side device assigns a target static IP address to the terminal based on the required capability identifier, the method further includes: Start the first timer; During the duration of the first timer, the target static IP address will not be assigned to other terminals.

5. The method according to claim 1, characterized in that, After the network-side device assigns a target static IP address to the terminal based on the required capability identifier, the method further includes: The network-side device saves the target static IP address to the subscription data corresponding to the terminal.

6. A method for obtaining an IP address, characterized in that, The method includes: The terminal sends a request message to the network-side device. The request message includes a required capability identifier, which indicates that the terminal requires a static IP address. The terminal receives response information sent by the network-side device, the response information including a target static IP address allocated to the terminal by the network-side device; The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

7. The method according to claim 6, characterized in that, Before the terminal sends the request information to the network-side device, the method further includes: The terminal receives the user's first input to the static IP address switch control; The terminal responds to the first input by enabling the static IP address function.

8. An IP address allocation device, characterized in that, The IP address allocation device includes: a receiving module and a processing module; The receiving module is used to receive request information sent by the terminal. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. The processing module is used to allocate a target static IP address to the terminal based on the required capability identifier received by the receiving module. The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

9. An IP address acquisition device, characterized in that, The IP address acquisition device includes: a sending module and a receiving module; The sending module is used to send request information to the network-side device. The request information includes a required capability identifier, which indicates that the terminal requires a static IP address. The receiving module is used to receive response information sent by the network-side device, the response information including the target static IP address allocated by the network-side device to the terminal; The target static IP address is a dedicated IP address that the terminal can use within a preset time period; the request information includes at least one of the following: registration request, re-registration request, PDU session establishment request, attach request, and PDN connection request.

10. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the IP address allocation method as described in any one of claims 1 to 5, or the steps of the IP address acquisition method as described in any one of claims 6 to 7.

Images