WO2019024767A1 - 释放ip地址的方法、装置、网络设备及系统 - Google Patents

释放ip地址的方法、装置、网络设备及系统 Download PDF

Info

Publication number
WO2019024767A1
WO2019024767A1 PCT/CN2018/097294 CN2018097294W WO2019024767A1 WO 2019024767 A1 WO2019024767 A1 WO 2019024767A1 CN 2018097294 W CN2018097294 W CN 2018097294W WO 2019024767 A1 WO2019024767 A1 WO 2019024767A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
network device
terminal
pdu session
notification
Prior art date
Application number
PCT/CN2018/097294
Other languages
English (en)
French (fr)
Inventor
朱强华
刘睿智
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18840333.1A priority Critical patent/EP3651537A4/en
Publication of WO2019024767A1 publication Critical patent/WO2019024767A1/zh
Priority to US16/775,903 priority patent/US11381961B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5053—Lease time; Renewal aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a network device, and a system for releasing an internet protocol (IP) address.
  • IP internet protocol
  • a packet data unit (PDU) session is accessed to the data network (DN) through the PDU session anchor, and the relocation process of the PDU session anchor of the PDU session involves the release of the IP address.
  • PDU packet data unit
  • DN data network
  • the relocation process of the PDU session anchor of the PDU session involves the release of the IP address.
  • the network side uses a timer to determine the time point at which the IP address is released.
  • the duration of the timer is determined empirically and is not accurate enough. In this case, if the IP address is released too early, the data transmission may be incorrect. If the IP address is released too late, the IP address will be occupied for too long, resulting in low resource utilization.
  • the embodiment of the present invention provides a method, a device, a network device, and a system for releasing an IP address, so as to solve the problem that the IP address release time is inaccurate.
  • the embodiment of the present application provides the following technical solutions:
  • a method for releasing an IP address comprising: determining, by a first network device, that a PDU session anchor needs to be relocated from a first user plane functional entity, where the first user plane function entity is a terminal a PDU session anchor of a PDU session; the first network device determines that the first IP address of the terminal is no longer used, wherein the first IP address is an IP address used by the terminal in the first PDU session; the first network device releases the first IP address.
  • the first network device after determining that the first IP address of the terminal is no longer used, releasing the first IP address, and no longer determining the time of releasing the first IP address by using a timer value, The first IP address can be released in time, which ensures the correct transmission of data and improves resource utilization.
  • the first network device determines that the first IP address of the terminal is no longer in use, including one of the following:
  • the terminal determines that the connection state of the terminal is an idle state; the terminal synchronizes the connection state of the terminal with the second network device, so that the second network device sends a first notification to the first network device, where the first notification is used to notify the first network device: the terminal The connection state is an idle state, so that the first network device determines that the first IP address is no longer used and releases the first IP address, where the first IP address is an IP address used by the terminal in the first PDU session; the second network device determines The second network device sends a first notification to the first network device, where the first notification includes information that the connection status of the terminal is an idle state; the first network device receives the first notification from the second network device;
  • the fifth network device determines that the connection state of the terminal is an idle state; the fifth network device sends a first notification to the first network device, where the first notification includes information that the connection status of the terminal is an idle state; the first network device is configured from the fifth network device. Receiving a first notification, where the first notification is used to notify the first network device that the connection status of the terminal is an idle state;
  • the first network device determines that the state of the first PDU session is a deactivated state
  • the third network device detects the activity of the first IP address, where the first IP address is an IP address used by the terminal in the first PDU session; if it is detected that the first IP address is inactive, the third network device is to the first network
  • the device sends a second notification, where the second notification is used to notify the first network device that the first IP address is inactive, so that the first network device determines that the first IP address is no longer used and releases the first IP address; the first network device
  • the third network device receives the second notification;
  • the fifth network device determines that the first IP address is inactive, and the fifth network device sends a second notification to the first network device, where the second notification is used to notify the first network device that the first IP address is not active, so that the first network device Determining that the first IP address is no longer used and releasing the first IP address; the first network device receives the second notification from the fifth network device;
  • the third notification is used to notify the first network device that the IP connection of the first IP address is released, so that the first network device determines that the first IP address is no longer used and releases the first IP address, and the third notification includes The information released by the IP connection of the first IP address; the first network device receives the third notification from the fourth network device or the fifth network device.
  • the method further includes: the first network device selecting the second user plane function entity as the terminal The PDU session anchor of the second PDU session; the first network device determines that the first IP address of the terminal is no longer used, including: the terminal or the fifth network device determines that the terminal completes the handover from the first IP address to the second IP address; Or the fifth network device sends a fourth notification to the first network device, where the fourth notification is used to notify the first network device that the terminal completes the switching of the first IP address to the second IP address, so that the first network device determines the first The IP address is no longer used and the first IP address is released; wherein the first IP address is an IP address used by the terminal in the first PDU session, and the PDU session anchor of the first PDU session is a first user plane functional entity; The IP address is an IP address used by the terminal in the second PDU session after the PDU session anchor is relocated from the first
  • the terminal after allocating the second IP address to the terminal, the terminal needs to gradually transfer the service data flow through the first user plane function entity to the user plane path including the second user plane function entity, when the transfer After completing (ie, completing the handover from the first IP address to the second IP address), the terminal transmits the service data flow only on the user plane path including the second user plane function entity by using the second IP address, and therefore, the terminal can be released.
  • First IP address the terminal needs to gradually transfer the service data flow through the first user plane function entity to the user plane path including the second user plane function entity, when the transfer After completing (ie, completing the handover from the first IP address to the second IP address), the terminal transmits the service data flow only on the user plane path including the second user plane function entity by using the second IP address, and therefore, the terminal can be released.
  • the method further includes: the first network device selecting the second user plane function entity as the first PDU a new PDU session anchor of the session; the first network device determines that the first IP address of the terminal is no longer used, including: the terminal or the fifth network device determines that the terminal completes the handover from the first IP address to the second IP address; Or the fifth network device sends a fourth notification to the first network device, where the fourth notification is used to notify the first network device that the terminal completes the switching of the first IP address to the second IP address, so that the first network device determines the first The IP address is no longer used and the first IP address is released; wherein the first IP address is an IP address used by the terminal in the first PDU session, and the PDU session anchor of the first PDU session is a first user plane functional entity; The IP address is an IP address used by the terminal in the second PDU session after the PDU session anchor is relocated from the
  • the terminal after allocating the second IP address to the terminal, the terminal needs to gradually transfer the service data flow through the first user plane function entity to the user plane path including the second user plane function entity, when the transfer After completing (ie, completing the handover from the first IP address to the second IP address), the terminal transmits the service data flow only on the user plane path including the second user plane function entity by using the second IP address, and therefore, the terminal can be released.
  • First IP address the terminal needs to gradually transfer the service data flow through the first user plane function entity to the user plane path including the second user plane function entity, when the transfer After completing (ie, completing the handover from the first IP address to the second IP address), the terminal transmits the service data flow only on the user plane path including the second user plane function entity by using the second IP address, and therefore, the terminal can be released.
  • the method before the first network device receives the second notification from the third network device, the method further includes: the first network device sending a first indication to the third network device, where the first indication is used to indicate The third network device detects the activity of the first IP address; the third network device receives the first indication from the first network device, and the third network device detects the activity of the first IP address, including: the third network device according to the first Indicates that the activity of the first IP address is detected.
  • the first network device determines that the state of the first PDU session is a deactivated state, including: the fifth network device determines that the state of the first PDU session is a deactivated state; and the fifth network device sends the first network to the first network.
  • the device sends a fifth notification, where the fifth notification is used to notify the first network device that the state of the first PDU session is a deactivated state; the first network device receives the fifth notification from the fifth network device; the first network device is configured according to the fifth The state of the first PDU session is determined to be a deactivated state.
  • the method before the first network device releases the first IP address, the method further includes: the first network device sends a second indication to the terminal, the second indication is used to indicate that the terminal releases the first IP address; Receiving a second indication from the first network device; the terminal releasing the first IP address according to the second indication.
  • the first network device may send a second indication to the terminal, and the terminal immediately releases the first IP address after receiving the second indication, so that The first network device releases the first IP address.
  • the method further includes: the first network device sends a third indication to the terminal, where the third indication is used to indicate that the terminal enters the idle state. The first IP address is released; the terminal receives the third indication from the first network device.
  • the first network device may send a third indication to the terminal, so that when the terminal enters the idle state, the first IP address is released, so that the first A network device releases the first IP address when it is determined that the terminal is in an idle state.
  • the method further includes: the terminal releasing the first IP address.
  • the terminal releases the first IP address so that the first network device releases the first IP address.
  • a terminal having a function of implementing an action performed by a terminal in any one of the methods provided by the first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a second network device having a function of implementing an action performed by a second network device of any one of the methods provided by the first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a third network device having a function of implementing an action performed by a third network device of any one of the methods provided by the first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a fourth network device having a function of implementing an action performed by a fourth network device of any one of the methods provided by the first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a first network device includes: a memory, a processor, and a bus; the memory is configured to store a computer to execute instructions, the processor and the memory are connected by a bus, and the processor executes the computer execution of the memory storage An instruction to cause the first network device to implement the actions performed in any of the methods provided in the first aspect.
  • a ninth aspect provides a terminal, where the terminal includes: a memory, a processor, and a bus; the memory is configured to store a computer to execute an instruction, the processor and the memory are connected through a bus, and the processor executes a computer-executed instruction of the memory to enable the terminal to implement The actions performed in any of the methods provided in the first aspect.
  • a second network device includes: a memory, a processor, and a bus; the memory is configured to store a computer to execute an instruction, the processor and the memory are connected by a bus, and the processor executes the computer execution of the memory storage.
  • a third network device includes: a memory, a processor, and a bus; the memory is configured to store a computer to execute instructions, the processor and the memory are connected by a bus, and the processor executes the memory storage computer. The instructions are executed to cause the third network device to perform the actions performed in any of the methods provided in the first aspect.
  • a fourth network device includes: a memory, a processor, and a bus; the memory is configured to store a computer execution instruction, the processor and the memory are connected by a bus, and the processor executes the memory storage computer The instructions are executed to cause the fourth network device to implement the actions performed in any of the methods provided in the first aspect.
  • a fifth network device includes: a memory, a processor, and a bus; the memory is configured to store a computer to execute instructions, the processor and the memory are connected by a bus, and the processor executes the memory storage computer. The instructions are executed to cause the fifth network device to implement the actions performed in any of the methods provided in the first aspect.
  • a computer readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the actions performed by the first network device in any of the methods provided in the first aspect.
  • a computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the actions performed by the terminal in any of the methods provided in the first aspect.
  • a computer readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the actions performed by the second network device in any of the methods provided in the first aspect.
  • a computer readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the actions performed by the fourth network device in any of the methods provided in the first aspect.
  • a computer readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the actions performed by the fifth network device in any of the methods provided in the first aspect.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the actions performed by the first network device in any of the methods provided in the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the actions performed by the terminal in any of the methods provided in the first aspect.
  • a computer program product comprising instructions which, when executed on a computer, cause the computer to perform the actions performed by the second network device in any of the methods provided in the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the actions performed by the third network device in any of the methods provided in the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the actions performed by the fourth network device in any of the methods provided in the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the actions performed by the fifth network device in any of the methods provided in the first aspect.
  • a device comprising a processor, a memory and a transceiver component, the transceiver component comprising an input and output circuit, the memory for storing a computer execution instruction, and the processor implementing the computer execution instruction stored in the memory
  • the action performed by the first network device in any of the methods provided in the first aspect.
  • a device comprising a processor, a memory and a transceiver component, the transceiver component comprising an input and output circuit, the memory for storing a computer execution instruction, and the processor implementing the computer execution instruction stored in the memory
  • the action performed by the terminal in any of the methods provided in the first aspect.
  • a device comprising a processor, a memory and a transceiver component, the transceiver component comprising an input and output circuit, the memory for storing a computer execution instruction, and the processor executing the instruction by executing a computer stored in the memory
  • the actions performed by the second network device in any of the methods provided in the first aspect are implemented.
  • a device comprising a processor, a memory and a transceiver component, the transceiver component comprising an input and output circuit, the memory for storing a computer execution instruction, and the processor implementing the computer execution instruction stored in the memory
  • the action performed by the third network device in any of the methods provided in the first aspect.
  • a device comprising a processor, a memory and a transceiver component, the transceiver component comprising an input/output circuit, the memory for storing a computer execution instruction, and the processor implementing the computer execution instruction stored in the memory.
  • a communication system includes at least: a first network device and a device, and further includes at least one of a second network device, a third network device, a fourth network device, and a fifth network device
  • the first network device may be any one of the first network devices
  • the second network device may be any one of the foregoing second network devices
  • the third network device may be in the foregoing aspect.
  • Any of the third network devices, the fourth network device may be any one of the fourth network devices, and the fifth network device may be any one of the fifth network devices described in the foregoing aspects, where the device may be In any of the devices described in the above aspects, the device may be a terminal.
  • the first network device can release the first IP address without determining that a timer value is used, if the first IP address of the terminal is no longer used.
  • the time for releasing the first IP address is determined, and the first IP address can be released in time, which ensures the correct transmission of data and improves resource utilization.
  • 1 is a schematic diagram of communication of a relocation process of a PDU session anchor of a multiple PDU session
  • FIG. 2 is a schematic diagram of service data flow in a PDU session anchor relocation process in a multi-PDU session scenario according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a network element architecture of a PDU session anchor relocation in a multi-homed PDU session scenario according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of service data flow in a PDU session anchor relocation process in a multi-homed PDU session scenario according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a network element architecture of a PDU session anchor relocation in a UL CL PDU session scenario according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of service data flow in a PDU session anchor relocation process in a UL CL PDU session scenario according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a possible network architecture according to an embodiment of the present application.
  • FIG. 8 is a flowchart of a method for releasing an IP address according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of communication of a method for releasing an IP address according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of communication of another method for releasing an IP address according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of communication of another method for releasing an IP address according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of communication of another method for releasing an IP address according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a device according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a device according to an embodiment of the present application.
  • a PDU session is a connection between a terminal and a DN for providing PDU connectivity services.
  • the PDU connectivity service supported by the core network of the fifth-generation (5G) communication system refers to a service that provides PDU exchange between the terminal and the DN determined by the data network name (DNN).
  • DNN data network name
  • a terminal may connect to the same DN or a different DN through multiple PDU sessions, and the terminal may also connect to the same DN through one or more PDU sessions served by different PDU session anchors.
  • the type of PDU session can be classified into IP type, Ethernet type, or unstructured data type.
  • the type of the PDU session may be an IP type.
  • the PDU session is accessed to the DN through the PDU session anchor.
  • the PDU session anchor can be a user plane function (UPF) entity connected to the DN. Therefore, the PDU session anchor can also be recorded as the PDU session anchor UPF.
  • the method provided by the embodiment of the present application is exemplified in the following, taking the PDU session anchor as the UPF as an example.
  • a PDU session may only be connected to the DN through a PDU session anchor. In this case, if the terminal wants to access the DN through multiple PDU session anchors, multiple PDU sessions need to be established. This is through multiple PDU sessions.
  • the way the anchor accesses the DN is called a multi-PDU session.
  • a PDU session may also be accessed to the DN through multiple PDU session anchors. According to different processing modes, the situation may be divided into a multi-homed PDU session and an uplink classified PDU session.
  • the terminal can connect to the same DN through different PDU session anchors. Connections corresponding to different PDU session anchors belong to different PDU sessions.
  • FIG. 2 is a schematic diagram of a multiple PDU session scenario.
  • the terminal is connected to the DN through the old PDU session anchor, at which point the terminal has been assigned an IP address (IP1).
  • IP1 IP address
  • the SMF selects a new PDU session anchor and establishes a new PDU session, assigning the terminal a new IP address (IP2).
  • IP2 IP address
  • the terminal accesses the DN with a new IP address through the new PDU session anchor.
  • the old PDU session and the new PDU session belong to different PDU sessions.
  • the service data flow that passes through the old PDU session anchor is the service data flow sent by the old IP address on the old user plane path, and the service data flow that passes the new PDU session anchor point is used on the new user plane path.
  • the service data stream sent by the IP address is the service data flow sent by the old IP address on the old user plane path.
  • a PDU session may be associated with multiple sixth protocol Internet Protocol (IPv6) prefixes.
  • IPv6 Internet Protocol
  • the PDU session passes through multiple PDU session anchors (eg, PDUs). Session Anchor 1 and PDU Session Anchor 2) Access DN.
  • PDU session anchors eg, PDUs
  • Session Anchor 1 and PDU Session Anchor 2 Access DN.
  • the user plane path to the different PDU session anchors branches on a common UPF called a "branching point (BP)".
  • the BP sends uplink data to different PDU session anchors and fuses the downlink data to the terminal, for example, merging data of different PDU session anchors connected to the terminal.
  • the terminal may exchange information with the “BP” through an access network (AN), such as a radio access network (RAN).
  • AN access network
  • RAN radio access network
  • FIG. 4 is a schematic diagram of a service data flow in a PDU session anchor relocation process of a multi-homing PDU session when the SSC mode associated with the PDU session anchor is mode 3.
  • the terminal is connected to the DN through the old PDU session anchor, at which point the terminal has been assigned an IP address (IP1).
  • IP1 IP address
  • the process of the SMF changing the PDU session to the new PDU session anchor includes: inserting the BP, the BP can be inserted on the existing UPF, or newly selecting the UPF and inserting the BP, selecting Connect to the BP's new PDU session anchor, update the session context, and configure a new IP address (IP2).
  • the terminal accesses the DN with a new IP address through the new PDU session anchor.
  • the user plane path including the old PDU session anchor point and the user plane path including the new PDU session anchor point are new user plane paths, so that the service data flow passing through the old PDU session anchor point is The service data stream sent by the old IP address on the new user plane path, and the service data stream passing the new PDU session anchor point is the service data stream sent by the new IP address on the new user plane path.
  • the terminal connects to the DN through a PDU session.
  • an "Uplink Classifier (UL CL)" may be included in the user plane path of a PDU session. Therefore, the uplink classification PDU session may also be used. Called a UL CL PDU session. Referring to Figure 5, the UL CL can be inserted into a UPF. The goal of inserting the UL CL is to offload some data that matches the transmission filter provided by the SMF.
  • FIG. 6 is a schematic diagram of data flow during PDU session anchor relocation of a UL CL PDU session when the SSC mode associated with the PDU session anchor is Mode 3.
  • the terminal is connected to the central DN through the old PDU session anchor, at which point the terminal has been assigned an IP address (IP1).
  • IP1 IP address
  • the process of the SMF changing the PDU session to the new PDU session anchor includes: selecting a new PDU session anchor connected to the UL CL, updating the session context, and configuring a new IP address (IP2) ).
  • IP2 IP address
  • the terminal accesses the central DN with a new IP address through the new PDU session anchor.
  • the UL CL can offload data to the central DN through different PDU session anchors.
  • the service data flow that passes through the old PDU session anchor is the service data flow sent by the old IP address on the old user plane path, and the service data flow that passes the new PDU session anchor point is used on the new user plane path.
  • the terminal connects to the DN through a PDU session.
  • the SSC mode of the system architecture of the 5G network can meet the continuity requirements of many different applications and services of the terminal.
  • the SSC mode associated with the PDU session anchor does not change during the lifetime of the PDU session.
  • the SMF may be determined by accepting the SSC mode requested by the terminal, or may be determined by modifying the SSC mode in the request of the terminal by subscription or partial configuration.
  • the SSC modes associated with the PDU session anchor include Mode 1, Mode 2, and Mode 3.
  • the PDU session anchor is maintained during the establishment of the PDU session.
  • IP continuity is always supported regardless of the terminal's mobility event.
  • the network may trigger the release of the PDU session and instruct the terminal to immediately establish a new PDU session to the same DN.
  • the SMF can select a new PDU session anchor for the newly established PDU session.
  • the network allows the terminal to establish a connection with the same DN via a new PDU session anchor before the old PDU session anchor is released.
  • the SMF decides whether to select a PDU session anchor that is suitable for the new situation of the terminal.
  • SSC Mode 3 can be applied to any type of PDU session.
  • SSC mode 3 to ensure business continuity and uninterrupted user service experience, after the new IP address is assigned, the old IP address will remain for a while and then released.
  • the IP address may be a fourth version of an internet protocol version (IPv4) address or an IPv6 prefix, where the IPv6 prefix may be represented as an IP prefix, and its role is equivalent to an IP address in the IPv4.
  • IPv4 internet protocol version
  • IPv6 prefix may be represented as an IP prefix, and its role is equivalent to an IP address in the IPv4.
  • the PDU session is an IP type
  • the IP version has IPv4 and IPv6, and the SMF allocates an IP address to the terminal according to the selected IP version.
  • the core network assigns an IP address to the terminal.
  • the SMF sends the IP address and IPv4 configuration through session management non-access stratum (SM NAS) signaling. Parameters are given to the terminal.
  • SM NAS session management non-access stratum
  • DHCPv4 dynamic host configuration protocol version 4
  • the SMF sends the IP address and IPv4 configuration parameters to the terminal through DHCPv4.
  • the SMF configures the UPF as a PDU session anchor to send all DHCPv4 information between the terminal and the SMF.
  • the core network uses stateless address autoconfiguration (SLAAC) to configure an IPv6 prefix to the terminal.
  • SLAAC stateless address autoconfiguration
  • the SMF uses the stateless dynamic host configuration protocol version (DHCPv6) to send routing advertisement information and IPv6 configuration parameters to the terminal through the PDU session anchor.
  • DHCPv6 stateless dynamic host configuration protocol version
  • the SMF configures the UPF as a PDU session anchor to send all router solicitation (RS)/router advertisement (RA) and DHCPv6 information between the terminal and the SMF.
  • RS router solicitation
  • RA router advertisement
  • the terminal receives the RA message, it constructs a complete IPv6 address through IPv6 SLAAC.
  • the relocation process of the PDU session anchor of the multi-PDU session can be referred to FIG. 1 , and specifically includes the following steps: 101.
  • a session management function (SMF) entity determines a currently served PDU session anchor point (ie, UPF1) needs to be relocated; 102.
  • SMF session management function
  • the SMF entity sends a non-access stratum (NAS) message to the terminal through a core access and mobility management function (AMF) entity, and the NAS message is used for Notifying the terminal that the current PDU session is about to be released, and also for notifying the terminal to re-establish the PDU session;
  • the NAS message may include a PDU session identifier (ID), and the PDU session ID is used by the terminal to determine the PDU session to be released, and the NAS message may further include a timer value indicating how long the network wants to maintain the PDU session, so that the terminal transfers the service data stream before the timer expires;
  • 103 the terminal establishes a new PDU session, and the PDU session anchor point of the new PDU session is UPF2;
  • the terminal or SMF triggers the release of the PDU session. If the SMF releases the PDU session, the SMF releases the old PDU session when the timer expires, releasing the terminal in the old The IP address used in the P
  • the SMF uses a timer to determine the time point at which the IP address is released.
  • the duration of the timer is determined empirically and is not accurate. In this case, if the IP address is released too early, the terminal side may be old. The PDU session has not been released, resulting in an error in data transmission. If the IP address is released too late, the IP address will take too long to reduce resource utilization.
  • the 5G network may include multiple network functions (NF) entities: an authentication server function (authentication server function). Function, AUSF) entity, AMF entity, DN, unified data management (UDM) entity, policy control function (PCF) entity, (R) AN device, UPF entity, terminal, application function (application) Function, AF) entity, SMF entity.
  • NF network functions
  • FIG. 7 is only an exemplary architecture diagram.
  • the 5G network architecture may also include other functional entities, for example, may also include network openness between the AF entity and the PCF entity.
  • a network exposure function (NEF) entity may also include a management and orchestration (MANO) network element and/or a mobile edge orchestrator (MEO) network element, where MANO and MEO are deployed and implemented.
  • MANO management and orchestration
  • MEO mobile edge orchestrator
  • the terminal communicates with the AMF entity through the next generation interface 1 (N1 for short), the (R) AN device communicates with the AMF entity through the N interface 2 (N2 for short), and the (R) AN device passes the N interface 3 (referred to as N3).
  • N3 N3
  • Communicating with the UPF entity the UPF entity communicates with the DN through the N interface 6 (N6 for short), the AMF entity communicates with the SMF entity through the N interface 11 (N11 for short), and the AMF entity communicates with the UDM entity through the N interface 8 (N8 for short).
  • the AMF entity communicates with the AUSF entity through the N interface 12 (N12 for short), and the AMF entity communicates with the PCF entity through the N interface 15 (N15 for short), and the SMF entity communicates with the PCF entity through the N interface 7 (N7 for short), and the SMF entity passes the N interface. 4 (N4 for short) communicates with the UPF entity.
  • the SMF entity communicates with the UDM entity through the N interface 10 (N10 for short).
  • the UDM entity communicates with the AUSF entity through the N interface 13 (N13 for short), and the PCF entity passes the N interface 5 (N5 for short). Communicate with the AF entity.
  • the UDM entity, the AUSF entity, the PCF entity, the AMF entity, and the SMF entity in FIG. 7 may also be collectively referred to as a control plane (CP) functional entity, which is not specifically limited in this embodiment of the present application.
  • CP control plane
  • the main functions of the (R) AN device include: providing a wireless connection; the main functions of the UPF entity include: routing and forwarding data packets, mobility anchors, and uplink classifiers to support routing service flows to DNs and BPs to support multi-homing PDU session, etc.; DN can be service provider, Internet access or third-party service; AMF entity main functions include management user registration, reachability detection, SMF node selection, mobile state transition management, etc.
  • the main functions of SMF entity include: Control session establishment, modification and deletion, user face node selection, etc.; PCF entity main functions include: policy decision points, providing service data flow and application detection, gating, quality of service (QoS) and flow-based The billing control and other rules; the main functions of the AF entity include: interacting with the 3rd generation partnership project (3GPP) core network to provide services to affect service flow routing, access network capability opening, policy control, etc.
  • the main functions of the AUSF entity include: providing authentication services; the main functions of the UDM entity include: storing user subscriptions Data; NEF entities are used to securely open services and capabilities provided by 3GPP network functions, such as third parties, edge computing, AF, and the like.
  • the terminal may also be a station (staion, ST) in a wireless local area network (WLAN), which may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (wireless local Loop, WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device (also known as wearable Smart device).
  • the terminal may also be a terminal device in a next-generation communication system, for example, a terminal device in 5G or a terminal device in a public land mobile network (PLMN) in a future evolution, new radio (NR) communication. Terminal devices in the system, etc.
  • PLMN public land mobile network
  • NR new radio
  • the embodiment of the present application provides a method for releasing an IP address. As shown in FIG. 8, the method includes:
  • the first network device determines that the PDU session anchor needs to be relocated from the first user plane function entity, where the first user plane function entity is a PDU session anchor point of the first PDU session of the terminal.
  • the terminal may have one or more PDU sessions.
  • the first PDU session may be any one of the multiple PDU sessions.
  • the SMF may be in the case that the terminal moves out of the coverage of the first user plane functional entity, or the load of the first user plane functional entity is large, or the terminal is far away from the first user plane functional entity.
  • it is determined that the PDU session anchor needs to be relocated from the first user plane function entity and in other cases, it is determined that the PDU session anchor point needs to be relocated from the first user plane function entity, and no further description is provided herein. .
  • the first network device determines that the first IP address of the terminal is no longer used, and the first IP address is an IP address used by the terminal in the first PDU session.
  • the step 1002 can be implemented in any one of the following five implementation manners.
  • the first network device receives the first notification from the second network device or the fifth network device, where the first notification is used to notify the first network device that the connection state of the terminal is an idle state.
  • the first notification may be an idle state notification.
  • the first network device may determine that the connection state of the terminal is an idle state by receiving the first notification, and the first notification includes information that the connection state of the terminal is an idle state.
  • connection state of the terminal may be an idle state or a connected state. It should be noted that once the connection state of the terminal is idle, the terminal disconnects all PDU sessions, and the first IP of the terminal can be released. address.
  • the second network device can be an AMF.
  • the method may further include: the second network device determines that the connection state of the terminal is an idle state, and the second network device sends the first network device to the first network device.
  • the first notification includes information that the connection status of the terminal is an idle state.
  • Manner 2 The first network device determines that the state of the first PDU session is a deactivated state.
  • the state of the PDU session may include a deactivated state and an activated state.
  • the state of the PDU session is deactivated, data on all PDU sessions is no longer transmitted, and the first IP of the terminal may be released. address.
  • the first network device determines that the status of the first PDU session is a deactivated state, and the method includes: receiving, by the first network device, a fifth notification sent by the fifth network device, where the fifth notification is used to notify the first network device: The state of a PDU session is a deactivated state; the first network device determines, according to the fifth notification, that the state of the first PDU session is a deactivated state.
  • the first network device may also determine, by itself, that the state of the first PDU session is a deactivated state.
  • the fifth notification may be a deactivation state notification
  • the deactivation state notification includes information that the state of the first PDU session is a deactivated state.
  • Manner 3 The first network device receives a second notification from the third network device or the fifth network device, where the second notification is used to notify the first network device that the first IP address is inactive.
  • the second notification may be an IP address inactivity report of the first IP address.
  • the third network device may be a first user plane function entity, when the PDU session is a multi-homing PDU session, the third network device may be a BP, and when the PDU session is a UL CL PDU session, The third network device can be a UL CL.
  • the method may further include: detecting, by the third network device, the activity of the first IP address; and detecting that the first IP address is inactive The third network device sends a second notification to the first network device.
  • the method may further include: the first network device sends a first indication to the third network device, where the first indication is used to indicate the third network The device detects the activity of the first IP address; the third network device receives the first indication from the receiving the first network device; in this case, the third network device detects the activity of the first IP address, which may include: the third network The device detects the activity of the first IP address according to the first indication.
  • the first indication may be an indication that the first network device determines that the PDU session anchor needs to be sent from the first user plane functional entity to the third network device after relocation.
  • the fourth network device receives a third notification from the fourth network device or the fifth network device, where the third notification is used to notify the first network device that the IP connection of the first IP address is released.
  • the third notification may be an IP connection release report for the first IP address.
  • the IP connection release of the first IP address means that all applications of the terminal do not use the first IP address to transmit data or the IP connection of the first IP address is released during the second time period.
  • the second time period may be configured for the network, and may also be determined by other means.
  • the second time period may be 2 ms or 3 ms.
  • the fourth network device may be MANO or AF.
  • the AF can sense the message of the application layer. When all the applications in the terminal do not use the first IP address to send data in the second time period, the AF sends a third notification to the first network device.
  • the application and the terminal may have an IP connection of a first IP address (for example, a transmission control protocol (TCP) connection), and when the IP connection is released, the AF can immediately perceive, in this case, The AF may also send a third notification to the first network device.
  • TCP transmission control protocol
  • the method may further include: the first network device selecting the second user plane function entity as the PDU session anchor of the second PDU session of the terminal;
  • the step 1002 may include: the first network device receives a fourth notification from the terminal or the fifth network device, where the fourth notification is used to notify the first network device that the terminal completes the switching of the first IP address to the second IP address, where The second IP address is an IP address used by the terminal in the second PDU session.
  • the method may further include: the first network device selecting the second user plane function entity as a new PDU session anchor point of the first PDU session;
  • the step 1002 may include: the first network device receives the fourth notification from the terminal or the fifth network device, where the fourth notification is used to notify the first network device that the terminal completes the switching from the first IP address to the second IP address.
  • the second IP address is an IP address used by the terminal in the first PDU session when the PDU session anchor of the first PDU session is the second user plane function entity.
  • the second user plane functional entity may be a new PDU session anchor, and the second IP address may be IP2.
  • the method may further include:
  • the terminal determines that the switching from the first IP address to the second IP address is completed
  • the terminal sends a fourth notification to the first network device.
  • the first network device may send a second indication to the terminal, and after receiving the second indication, the terminal immediately releases the first IP address, so that the first network device releases the first IP address. address.
  • the method may further include: the first network device sends a third indication to the terminal, where the third indication is used to indicate that the terminal releases the first IP address when entering the idle state; the terminal receives from the first network device The third indication; when the connection state of the terminal is an idle state, the terminal releases the first IP address.
  • the first network device may send a third indication to the terminal, so that when the terminal enters the idle state, the first IP address is released, so that the first network device determines that the terminal is idle. Release the first IP address.
  • the first network device Since the first network device may receive multiple third notifications, in this case, the first network device needs to determine whether the IP address in the third notification is an IP address that needs to be released.
  • the first network device may mark the status of the first IP address as to be released after determining that the PDU session anchor in the first PDU session needs to be relocated from the first user plane function entity, so that the first network device receives the After the third notification, the first IP address can be quickly determined to be an IP address to be released.
  • the first user plane function entity and the second user plane function entity are both controlled by the same SMF.
  • the second SMF is served for the terminal, and the first SMF can no longer directly exchange information with the terminal, first.
  • the SMF is an SMF that controls the first user plane functional entity
  • the second SMF is an SMF that controls the second user plane functional entity.
  • the first network device is the first SMF
  • the fifth network device may be the second SMF.
  • the first notification obtained by the fifth network device may be sent by the second network device, and the method for determining the first notification by the second network device may refer to the foregoing.
  • the second notification obtained by the fifth network device may be sent by the third network device.
  • the method for determining the second notification by the third network device may be referred to as above.
  • the fourth notification obtained by the fifth network device may be sent by the terminal, and the method for determining the fourth notification by the terminal may refer to the above;
  • the third notification may be sent by the fourth network device, and the method for determining the third notification by the fourth network device may refer to the above;
  • the fifth network device may determine, by itself, that the state of the first PDU session is a deactivated state.
  • Embodiment 1 provides a method for releasing an IP address. As shown in FIG. 9, the method may include:
  • a first PDU session already exists, and the terminal transmits the service data stream in the first PDU session by using the first IP address.
  • the SMF may determine the PDU session anchor point if the terminal moves out of the coverage of the first UPF, or if the load of the first UPF is large, or if the terminal is far away from the first UPF. It is necessary to relocate from the first UPF, and in other cases, it is determined that the PDU session anchor needs to be relocated from the first UPF, which will not be described one by one.
  • steps 1102a and 1102b are optional steps, and are performed one by one.
  • step 1102a when the application scenario of the method is a multi-PDU session scenario, step 1102a is performed, or when the application scenario of the method is a multi-homing PDU session or a UL CL PDU session scenario, step 1102b is performed.
  • the SMF selects the second UPF, and establishes a second PDU session by using the second UPF.
  • the SMF allocates a second IP address to the terminal. It should be noted that the IP address range of the SMF and the method for allocating the IP address may be configured in advance according to multiple UPFs.
  • the SMF selects the second UPF, and relocates the PDU session anchor point in the first PDU session from the first UPF to the second UPF.
  • the second UPF may be selected by the SMF.
  • the SMF may specifically select the second UPF according to the load of the UPF, the network load, or the distance of the terminal from the UPF.
  • the SMF allocates a second IP address to the terminal, selects a new BP or UL CL, and updates the session context in order to support the path to the second UPF.
  • the IP address range of the SMF and the method for allocating the IP address may be configured in advance according to multiple UPFs.
  • the terminal gradually transfers the traffic data flow through the first UPF to the user plane path including the second UPF.
  • the SMF marks the status of the first IP address as being to be released.
  • the SMF sends a third indication to the terminal.
  • the third indication is used to indicate that the terminal releases the first IP address when entering the idle state, and the third indication may be included in the NAS message. Specifically, the SMF may send the third indication to the AMF first, and the AMF forwards the third indication to the terminal.
  • step 1102a, step 1103, and step 1104 The execution order of any two steps in step 1102a, step 1103, and step 1104 is in no particular order; or, the order of execution of any two of steps 1102b, 1103, and 1104 is in no particular order.
  • the NEF/PCF receives the third notification sent by the MANO/AF.
  • MANO can be replaced with MEO.
  • the NEF/PCF sends the third notification to the SMF.
  • the SMF determines that the state of the first IP address is to be released, and determines to release the first IP address.
  • the SMF sends a second indication to the terminal.
  • the second indication is used to instruct the terminal to release the first IP address, and the second indication may be included in the NAS message.
  • the SMF may send the second indication to the AMF first, and the AMF forwards the second indication to the terminal.
  • the terminal releases the first IP address and the related context according to the second indication sent by the received SMF.
  • step 1111a when the application scenario of the method is a multi-PDU session scenario, step 1111a is performed; when the application scenario of the method is a multi-homing PDU session or a UL CL PDU session scenario, step 1111b is performed.
  • the SMF releases the first PDU session, releases the first IP address, and updates the session context in the first UPF.
  • the SMF releases the first IP address, and updates the session context in the BP or UL CL and the first UPF.
  • Embodiment 2 provides a method for releasing an IP address. As shown in FIG. 10, the method may include: steps 1201-1208b.
  • Steps 1201-1204 may refer to the description of steps 1101-1104 in FIG.
  • Step 1201 is the same as step 1101.
  • the application scenario of the method is a multi-PDU session scenario
  • 1202a is performed, and step 1202a is the same as step 1102a.
  • Step 1202b is executed, step 1202b is the same as step 1102b; step 1203 is the same as step 1103; step 1204 is the same as step 1104.
  • the terminal determines that the connection state of the terminal is an idle state, and the terminal releases the first IP address and synchronizes the connection state with the AMF.
  • connection state of the terminal may be an idle state or a connected state. It should be noted that once the connection state of the terminal is an idle state, the terminal disconnects all the PDU sessions.
  • the AMF sends a first notification to the SMF.
  • the first notification includes information that the connection state of the terminal is an idle state.
  • the SMF determines, according to the received first notification, that the connection state of the terminal is an idle state.
  • step 1208a When the application scenario of the method is a multi-PDU session scenario, step 1208a is performed.
  • step 1208b is performed.
  • the SMF determines that the state of the first IP address is to be released, releases the first PDU session, releases the first IP address, and updates the session context in the first UPF.
  • the SMF determines that the state of the first IP address is to be released, releases the first IP address, and updates the session context in the BP or UL CL and the first UPF.
  • Embodiment 3 provides a method for releasing an IP address. As shown in FIG. 11, the method may include: steps 1301-1309b.
  • Steps 1301-1304 may refer to the description of steps 1101-1104 in FIG.
  • Step 1301 is the same as step 1101.
  • step 1302a is performed.
  • Step 1302a is the same as step 1102a.
  • step 1302b is performed, step 1302b is the same as step 1102b; step 1303 is the same as step 1103; step 1304 is the same as step 1104.
  • the SMF determines that the state of the first PDU session is a deactivated state.
  • the status of the PDU session may be the deactivated state and the activated state.
  • the state of the PDU session is deactivated, the data on all PDU sessions is no longer transmitted, and the IP address of the terminal may be released.
  • Steps 1306-1309b may refer to the description of steps 1108-1111b in FIG.
  • Step 1306 is the same as step 1108; step 1307 is the same as step 1109; step 1308 is the same as step 1110; when the application scenario of the method is a multi-PDU session scenario, step 1309a is performed, step 1309a is the same as step 1111a; When the application scenario is a multi-homing PDU session or a UL CL PDU session scenario, step 1309b is performed, and step 1309b is the same as step 1111b.
  • Embodiment 4 provides a method for releasing an IP address. As shown in FIG. 12, the method may include: steps 1401-1412b.
  • Steps 1401-1404 may refer to the description of steps 1101-1104 in FIG.
  • Step 1401 is the same as step 1101.
  • step 1402a is performed.
  • Step 1402a is the same as step 1102a.
  • step 1402b is executed, step 1402b is the same as step 1102b; step 1403 is the same as step 1103, and step 1404 is the same as step 1104.
  • steps 1405a-1407a are performed.
  • steps 1405b-1407b are performed.
  • the SMF sends a first indication to the first UPF.
  • the first indication is used to indicate that the first UPF detects the activity of the first IP address.
  • the first UPF detects the activity of the first IP address according to the received first indication.
  • the first UPF sends a second notification to the SMF.
  • the second notification includes information that the first IP address is inactive, and the first IP address being inactive may mean that the first IP address is not used for the first time period.
  • the SMF sends a first indication to the BP or UL CL.
  • the first indication is used to indicate that the BP or the UL CL detects the activity of the first IP address.
  • BP or UL CL detects the activity of the first IP address according to the received first indication.
  • the BP or UL CL sends a second notification to the SMF.
  • the second notification includes information that the first IP address is inactive, and the first IP address being inactive may mean that the first IP address is not used for the first time period.
  • the SMF receives the second notification.
  • Steps 1409-1412b may refer to the description of steps 1108-1111b in FIG.
  • Embodiment 5 provides a method for releasing an IP address. As shown in FIG. 13, the method may include: steps 1501-1511b.
  • Steps 1501-1504 may refer to the description of steps 1101-1104 in FIG.
  • Step 1501 is the same as step 1101.
  • step 1502a is performed, and step 1502a is the same as step 1102a.
  • step 1502b is executed, step 1502b is the same as step 1102b; step 1503 is the same as step 1103; step 1504 is the same as step 1104.
  • the terminal completes the switching from the first IP address to the second IP address by using multipath technology.
  • the terminal sends a fourth notification to the SMF.
  • the SMF receives the fourth notification sent by the terminal.
  • Steps 1508-1511 may refer to the description of steps 1108-1111b in FIG.
  • Step 1508 is the same as step 1108; step 1509 is the same as step 1109; step 1510 is the same as step 1110; when the application scenario of the method is a multi-PDU session scenario, step 1511a is performed, step 1511a is the same as step 1111a; When the application scenario is a multi-homed PDU session or a UL CL PDU session scenario, 1511b is executed, and step 1511b is the same as step 1111b.
  • the first SMF determines that the PDU session anchor needs to be relocated from the first UPF.
  • step 1601 there is already a first PDU session, and the terminal transmits the service data stream in the first PDU session by using the first IP address.
  • step 1101 For the method that the first SMF determines that the PDU session anchor needs to be relocated from the first UPF, refer to step 1101 in the above, and details are not described herein again.
  • AMF selects a second SMF.
  • the second SMF may be selected by the AMF or may be selected by the first SMF, and the second SMF is selected by the AMF as an example.
  • the first SMF marks the status of the first IP address as being to be released.
  • the second SMF selects the second UPF.
  • step 1603 and step 1604 are in no particular order.
  • the first SMF sends a third indication to the terminal.
  • the first SMF and the second SMF relocate the first UPF to the second UPF.
  • the third indication is used to indicate that the terminal releases the first IP address when entering the idle state, and the third indication may be included in the NAS message. Specifically, the SMF may send the third indication to the AMF first, and the AMF forwards the third indication to the terminal.
  • the target information may be one or more of the first notification, the second notification, the third notification, the fourth notification, and the fifth notification in the foregoing.
  • the second SMF sends the target information to the first SMF.
  • the first SMF receives the target information.
  • the first SMF determines to release the first IP address according to the status of the first IP address.
  • the first SMF sends a second indication to the second SMF.
  • the terminal can only communicate with the second SMF. Therefore, the first SMF needs to forward the second indication to the terminal through the second SMF.
  • the second SMF forwards the received second indication to the terminal.
  • the second SMF may first send the second indication to the AMF, and the AMF forwards the second indication to the terminal.
  • the terminal releases the first IP address and the related context according to the second indication sent by the received second SMF.
  • the first SMF releases the first IP address, and updates the session context in the BP or UL CL and the first UPF.
  • Embodiment 1 - Embodiment 6 The beneficial effects of Embodiment 1 - Embodiment 6 can be referred to above, and are not described herein again.
  • the first user plane function entity is recorded as the first UPF
  • the second user plane function entity is recorded as the second UPF.
  • step 1102a may need to perform information interaction with one or more of terminal, AMF, first UPF, second UPF, and NEE/PCF in the process of implementation.
  • each network element such as a first network device, a second network device, a device (such as a terminal), etc.
  • each network element includes hardware structures and/or software modules corresponding to the respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform functional unit division on the first network device, the second network device, the device, and the like according to the foregoing method example.
  • each functional unit may be divided according to each function, or two or more functions may be used.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 15 shows a possible schematic diagram of a network device involved in the above embodiment
  • the network device includes a processing unit 2001 and a communication unit 2002, and may further include a storage unit 2003.
  • the structure diagram shown in FIG. 15 may be used to indicate the structures of the first network device, the second network device, the third network device, the fourth network device, or the fifth network device involved in the foregoing embodiments.
  • the processing unit 2001 is configured to perform control management on the action of the first network device, for example, the processing unit 2001 is configured to support
  • the first network device performs the processes 1001-1003 in FIG. 8, the processes 1101-1104, 1107-1109, 1111a, and 1111b in FIG. 9, the processes 1201-1204 and 1207-1208b in FIG. 10, and the process 1301 in FIG. -1307, 1309a, and 1309b, processes 1401-1405a, 1405b, 1408-1410, 1412a, and 1412b in FIG. 12, processes 1501-1504, 1507-1509, 1511a, and 1511b in FIG. 13, process 1601 in FIG.
  • the communication unit 2002 is for supporting communication between the first network device and other network entities, for example, with the terminal, AMF, etc. shown in FIG.
  • the storage unit 2003 is configured to store program codes and data of the first network device.
  • the processing unit 2001 is configured to perform control management on the action of the second network device, for example, the processing unit 2001 is used to support
  • the second network device performs processes 1102a and 1102b, 1104, 1109, 1111a, and 1111b in FIG. 9, processes 1202a, 1202b, 1204, 1205, 1206, 1208a, and 1208b in FIG. 10, processes 1302a, 1302b in FIG. 11, 1304, 1307, 1309a, and 1309b, processes 1402a, 1402b, 1404, 1410, 1412a, and 1412b in FIG.
  • the communication unit 2002 is for supporting communication between the second network device and other network entities, for example, with the terminal, SMF, etc. shown in FIG.
  • the storage unit 2003 is configured to store program codes and data of the second network device.
  • the processing unit 2001 is configured to perform control management on the action of the third network device, for example, when the PDU session is multiple PDUs.
  • the third network device may be the first UPF
  • the processing unit 2001 is configured to support the third network device to perform the processes 1102a, 1102b, 1111a, and 1111b in FIG. 9, processes 1202a, 1202b, 1208a, and 1208b in FIG. 10, Processes 1302a, 1302b, 1309a, and 1309b in FIG. 11, processes 1402a, 1402b, 1406a, 1407a, 1412a, and 1412b in FIG.
  • the third network device may be a BP or a UL CL
  • the processing unit 2001 is configured to support the third network device to perform the processes 1402a, 1402b, 1406b in FIG. 1407b, 1412a, and 1412b, actions performed by the third network devices in processes 1606 and 1614 in FIG. 14 and/or other processes described in the embodiments of the present application.
  • the communication unit 2002 is for supporting communication between the third network device and other network entities, for example, with the terminal, SMF, etc. shown in FIG.
  • the storage unit 2003 is configured to store program codes and data of the third network device.
  • the processing unit 2001 is configured to perform control management on the action of the fourth network device, for example, the processing unit 2001 is used to support The fourth network device performs the process 1105 in FIG. 9, and/or the actions performed by the fourth network device in other processes described in the embodiments of the present application.
  • the communication unit 2002 is for supporting communication of the fourth network device with other network entities, for example, with NEF/PCF and the like shown in FIG.
  • the storage unit 2003 is configured to store program codes and data of the fourth network device.
  • the processing unit 2001 is configured to perform control management on the action of the fifth network device, for example, the processing unit 2001 is configured to support
  • the fifth network device performs the actions performed by the processes 1604, 1606, 1607, 1608, 1612, and 1614 in FIG. 14 and/or the fifth network device in the other processes described in the embodiments of the present application.
  • the communication unit 2002 is for supporting communication between the fifth network device and other network entities, for example, with the first SMF, terminal, etc. shown in FIG.
  • the storage unit 2003 is configured to store program codes and data of the fifth network device.
  • the processing unit 2001 may be a processor or a controller, for example, may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit (Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 2002 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage unit 2003 can be a memory.
  • the network device involved in the embodiment of the present application may be the network device shown in FIG.
  • the network device includes a processor 2101, a communication interface 2102, and a memory 2103.
  • the network device may also include a bus 2104.
  • the communication interface 2102, the processor 2101, and the memory 2103 may be connected to each other through a bus 2104; the bus 2104 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA). Bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 2104 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • Fig. 17 shows a possible structural diagram of the apparatus involved in the above embodiment.
  • the device 22 includes a processing unit 2201 and a communication unit 2202.
  • the processing unit 2201 is configured to control the operation of the device 22, for example, the processing unit 2201 is used to support the device 22 to perform the processes 1102a, 1102b, and 1110 in FIG. 9, the processes 1202a, 1202b, and 1205 in FIG. 10, in FIG.
  • Communication unit 2202 is used to support communication between device 22 and other network devices.
  • device 22 may also include a storage unit 2203 for storing program code and data for device 22.
  • the processing unit 2201 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 2202 is a transceiver, a transceiver circuit, or the like.
  • the storage unit 2203 may be a memory.
  • the processing unit 2201 is a processor
  • the communication unit 2202 includes a transmitter and/or a receiver
  • the storage unit 2203 is a memory
  • the device involved in the embodiment of the present application may be the device shown in FIG.
  • FIG. 18 shows a simplified schematic diagram of one possible design structure of the device 23 involved in the embodiment of the present application.
  • the device 23 includes a transceiver 2301, a processor 2302, and a memory 2303.
  • device 23 may also include a bus 2304.
  • the processor 2302 can also be a controller.
  • the processor 2302 controls and manages the actions of the device 23 for performing the processing performed by the device 23 in the above-described embodiment of the present application.
  • processes 1102a, 1102b, and 1110 in FIG. 9 processes 1202a, 1202b, and 1205 in FIG. 10
  • processes 1302a, 1302b, and 1308 in FIG. 11 processes 1402a, 1402b, and 1411 in FIG. 12, in FIG.
  • the device shown in FIG. 17 or FIG. 18 may be a terminal.
  • the embodiment of the present application also provides a computer readable storage medium, including instructions, when executed on a computer, causing a computer to execute the above method.
  • the embodiment of the present application also provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the above method.
  • the embodiment of the present application further provides a device, which is in the form of a product of a chip, the device includes a processor, a memory, and a transceiver component, the transceiver component includes an input and output circuit, the memory is configured to store a computer execution instruction, and the processor executes The computer-executed instructions stored in the memory implement the above method.
  • the embodiment of the present application further provides a communication system, including at least: a first network device and a device, and further includes at least one of a second network device, a third network device, a fourth network device, and a fifth network device, where
  • the first network device may be any one of the first network devices
  • the second network device may be any one of the foregoing second network devices.
  • the third network device may be the foregoing embodiment. Any of the third network devices, the fourth network device may be any one of the fourth network devices, and the fifth network device may be any of the fifth network devices described in the foregoing embodiments.
  • the device may be any one of the devices described in the foregoing embodiments, and the device may be a terminal.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be wired from a website site, computer, server or data center (eg Coaxial cable, fiber, digital subscriber line (DSL) or wireless (eg infrared, wireless, microwave, etc.) to another website, computer, server or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及通信技术领域。本申请公开了一种释放IP地址的方法、装置、网络设备及系统，以解决IP地址释放时间不准确的问题。该方法包括：第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位，其中，第一用户面功能实体为终端的第一PDU会话的PDU会话锚点；第一网络设备确定终端的第一IP地址不再使用，其中，第一IP地址为终端在第一PDU会话中使用的IP地址；第一网络设备释放第一IP地址。

Description

释放IP地址的方法、装置、网络设备及系统
本申请要求于2017年07月31日提交中国专利局、申请号为201710643427.7、申请名称为“释放IP地址的方法、装置、网络设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种释放互联网协议(internet protocol，IP)地址的方法、装置、网络设备及系统。
背景技术
分组数据单元(packet data unit，PDU)会话通过PDU会话锚点接入到数据网络(data network，DN)，而PDU会话的PDU会话锚点的重定位过程涉及到IP地址的释放。例如，在多PDU会话的场景下，在PDU会话锚点的重定位过程中，需要建立新的PDU会话，释放旧的PDU会话，以及释放终端在旧的PDU会话中使用的IP地址。
现有方案中网络侧采用定时器的方式来确定释放IP地址的时间点，然而定时器的时长是根据经验确定的，不够精确。这种情况下，若IP地址释放的过早，可能导致数据传输出错，若IP地址释放的过晚，会使得占用该IP地址的时间太长，造成资源利用率不高。
发明内容
本申请实施例提供一种释放IP地址的方法、装置、网络设备及系统，以解决IP地址释放时间不准确的问题。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供了一种释放IP地址的方法，该方法包括：第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位，其中，第一用户面功能实体为终端的第一PDU会话的PDU会话锚点；第一网络设备确定终端的第一IP地址不再使用，其中，第一IP地址为终端在第一PDU会话中使用的IP地址；第一网络设备释放第一IP地址。第一方面提供的方法，第一网络设备在确定终端的第一IP地址不再使用的情况下，将第一IP地址释放，而不再通过一个定时器值确定第一IP地址释放的时间，可以保证第一IP地址及时的释放，既保证了数据的正确传输还可以提高资源利用率。
在一种可能的设计中，第一网络设备确定终端的第一IP地址不再使用，包括如下情形之一：
终端确定终端的连接状态为空闲态；终端与第二网络设备同步终端的连接状态，以使得第二网络设备向第一网络设备发送第一通知，第一通知用于通知第一网络设备：终端的连接状态为空闲态，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址，第一IP地址为终端在第一PDU会话中使用的IP地址；第二网络设备确定终端的连接状态为空闲态；第二网络设备向第一网络设备发送第一通知，第一通知包括终端的连接状态为空闲态的信息；第一网络设备从第二网络设备接收第一通知；
第五网络设备确定终端的连接状态为空闲态；第五网络设备向第一网络设备发送第一通知，第一通知包括终端的连接状态为空闲态的信息；第一网络设备从第五网络设备接收第一通知，第一通知用于通知第一网络设备：终端的连接状态为空闲态；
第一网络设备确定第一PDU会话的状态为去激活状态；
第三网络设备对第一IP地址的活跃性进行检测，第一IP地址为终端在第一PDU会话中使用的IP地址；若检测到第一IP地址不活跃，第三网络设备向第一网络设备发送第二通知，第二通知用于通知第一网络设备：第一IP地址不活跃，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址；第一网络设备从第三网络设备接收第二通知；
第五网络设备确定第一IP地址不活跃，第五网络设备向第一网络设备发送第二通知，第二通知用于通知第一网络设备：第一IP地址不活跃，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址；第一网络设备从第五网络设备接收第二通知；
第四网络设备或第五网络设备确定第一IP地址的IP连接释放，第一IP地址为终端在第一PDU会话中使用的IP地址；第四网络设备或第五网络设备向第一网络设备发送第三通知，第三通知用于通知第一网络设备：第一IP地址的IP连接释放，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址，第三通知包括第一IP地址的IP连接释放的信息；第一网络设备从第四网络设备或第五网络设备接收第三通知。
在该种可能的设计中，一旦终端的连接状态为空闲态时，说明终端断开了全部PDU会话的连接，此时即可释放终端的第一IP地址；当PDU会话的状态为去激活状态时，全部的PDU会话上的数据不再传输，此时即可释放终端的第一IP地址；第一IP地址不活跃说明第一IP地址有一段时间未被使用，后期再被使用的概率很低，此时即可释放终端的第一IP地址；由于第一IP地址的IP连接释放后，终端不再使用第一IP地址发送数据，因此，可以释放终端的第一IP地址。
在一种可能的设计中，在第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位之后，该方法还包括：第一网络设备选择第二用户面功能实体作为终端的第二PDU会话的PDU会话锚点；第一网络设备确定终端的第一IP地址不再使用，包括：终端或第五网络设备确定终端完成了从第一IP地址到第二IP地址的切换；终端或第五网络设备向第一网络设备发送第四通知，第四通知用于通知第一网络设备：终端完成了第一IP地址到第二IP地址的切换，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址；其中，第一IP地址为终端在第一PDU会话中使用的IP地址，第一PDU会话的PDU会话锚点为第一用户面功能实体；第二IP地址为将PDU会话锚点从第一用户面功能实体重定位至第二用户面功能实体后，终端在第二PDU会话中使用的IP地址，第二用户面功能实体为第二PDU会话的PDU会话锚点；或者，第二IP地址为将第一PDU会话的PDU会话锚点从第一用户面功能实体重定位至第二用户面功能实体后，终端在第一PDU会话中使用的IP地址；第一网络设备从终端或第五网络设备接收第四通知，其中，第二IP地址为终端在第二PDU会话中使用的IP地址。在该种可能的设计中，在为终端分配第二IP地址之后，终端需要逐渐将经过第 一用户面功能实体的业务数据流转移到包括第二用户面功能实体的用户面路径上，当转移完成(即完成从第一IP地址到第二IP地址的切换)后，终端仅采用第二IP地址在包括第二用户面功能实体的用户面路径上传输业务数据流，因此，可以释放终端的第一IP地址。
在一种可能的设计中，在第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位之后，该方法还包括：第一网络设备选择第二用户面功能实体作为第一PDU会话的新的PDU会话锚点；第一网络设备确定终端的第一IP地址不再使用，包括：终端或第五网络设备确定终端完成了从第一IP地址到第二IP地址的切换；终端或第五网络设备向第一网络设备发送第四通知，第四通知用于通知第一网络设备：终端完成了第一IP地址到第二IP地址的切换，以使得第一网络设备确定第一IP地址不再使用并释放第一IP地址；其中，第一IP地址为终端在第一PDU会话中使用的IP地址，第一PDU会话的PDU会话锚点为第一用户面功能实体；第二IP地址为将PDU会话锚点从第一用户面功能实体重定位至第二用户面功能实体后，终端在第二PDU会话中使用的IP地址，第二用户面功能实体为第二PDU会话的PDU会话锚点；或者，第二IP地址为将第一PDU会话的PDU会话锚点从第一用户面功能实体重定位至第二用户面功能实体后，终端在第一PDU会话中使用的IP地址；第一网络设备从终端或第五网络设备接收第四通知，其中，第二IP地址为第一PDU会话的PDU会话锚点为第二用户面功能实体时，终端在第一PDU会话中使用的IP地址。在该种可能的设计中，在为终端分配第二IP地址之后，终端需要逐渐将经过第一用户面功能实体的业务数据流转移到包括第二用户面功能实体的用户面路径上，当转移完成(即完成从第一IP地址到第二IP地址的切换)后，终端仅采用第二IP地址在包括第二用户面功能实体的用户面路径上传输业务数据流，因此，可以释放终端的第一IP地址。
在一种可能的设计中，在第一网络设备从第三网络设备接收第二通知之前，该方法还包括：第一网络设备向第三网络设备发送第一指示，第一指示用于指示第三网络设备检测第一IP地址的活跃性；第三网络设备从第一网络设备接收第一指示，第三网络设备对第一IP地址的活跃性进行检测，包括：第三网络设备根据第一指示对第一IP地址的活跃性进行检测。
在一种可能的设计中，第一网络设备确定第一PDU会话的状态为去激活状态，包括：第五网络设备确定第一PDU会话的状态为去激活状态；第五网络设备向第一网络设备发送第五通知，第五通知用于通知第一网络设备：第一PDU会话的状态为去激活状态；第一网络设备从第五网络设备接收第五通知；第一网络设备根据第五通知确定第一PDU会话的状态为去激活状态。
在一种可能的设计中，在第一网络设备释放第一IP地址之前，该方法还包括：第一网络设备向终端发送第二指示，第二指示用于指示终端释放第一IP地址；终端从第一网络设备接收第二指示；终端根据第二指示释放第一IP地址。在该种可能的设计中，在第一网络设备确定第一IP地址不再使用后，第一网络设备可以向终端发送第二指示，终端收到第二指示后立即释放第一IP地址，以便第一网络设备释放第一IP地址。
在一种可能的设计中，在第一网络设备确定终端的第一IP地址不再使用之前，该方法还包括：第一网络设备向终端发送第三指示，第三指示用于指示终端进入空闲态 时释放第一IP地址；终端从第一网络设备接收第三指示。在该种可能的设计中，在第一网络设备确定第一IP地址不再使用之前，第一网络设备可以向终端发送第三指示，从而使得终端进入空闲态时释放第一IP地址，以便第一网络设备在确定终端处于空闲态时释放第一IP地址。
在一种可能的设计中，在第一网络设备确定终端的第一IP地址不再使用之前，该方法还包括：第一网络设备将第一IP地址的状态标记为待释放；第一网络设备释放第一IP地址，包括：第一网络设备确定第一IP地址的状态为待释放，并释放第一IP地址。在该种可能的设计中，由于第一网络设备可能接收到多个IP地址的第三通知，该情况下，第一网络设备需要确定第三通知中的IP地址是否为需要释放的IP地址。第一网络设备可以在进行第一PDU会话中的PDU会话锚点重定位后，将第一IP地址的状态标记为待释放，从而使得第一网络设备在接收到第一IP地址的第三通知后可以快速的确定第一IP地址为需要释放的IP地址。
在一种可能的设计中，在终端确定终端的连接状态为空闲态之后，该方法还包括：终端释放第一IP地址。在该种可能的设计中，终端释放第一IP地址，以便第一网络设备释放第一IP地址。
第二方面，提供了一种第一网络设备，该第一网络设备具有实现第一方面提供的任意一种方法中的第一网络设备执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第三方面，提供了一种终端，该终端具有实现第一方面提供的任意一种方法中的终端执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第四方面，提供了一种第二网络设备，该第二网络设备具有实现第一方面提供的任意一种方法中的第二网络设备执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第五方面，提供了一种第三网络设备，该第三网络设备具有实现第一方面提供的任意一种方法中的第三网络设备执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第六方面，提供了一种第四网络设备，该第四网络设备具有实现第一方面提供的任意一种方法中的第四网络设备执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第七方面，提供了一种第五网络设备，该第五网络设备具有实现第一方面提供的任意一种方法中的第五网络设备执行的动作的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。
第八方面，提供了一种第一网络设备，第一网络设备包括：存储器、处理器和总 线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使第一网络设备实现在第一方面提供的任意一种方法中所执行的动作。
第九方面，提供了一种终端，终端包括：存储器、处理器和总线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使终端实现在第一方面提供的任意一种方法中所执行的动作。
第十方面，提供了一种第二网络设备，第二网络设备包括：存储器、处理器和总线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使第二网络设备实现在第一方面提供的任意一种方法中所执行的动作。
第十一方面，提供了一种第三网络设备，第三网络设备包括：存储器、处理器和总线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使第三网络设备实现在第一方面提供的任意一种方法中所执行的动作。
第十二方面，提供了一种第四网络设备，第四网络设备包括：存储器、处理器和总线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使第四网络设备实现在第一方面提供的任意一种方法中所执行的动作。
第十三方面，提供了一种第五网络设备，第五网络设备包括：存储器、处理器和总线；存储器用于存储计算机执行指令，处理器与存储器通过总线连接，处理器执行存储器存储的计算机执行指令，以使第五网络设备实现在第一方面提供的任意一种方法中所执行的动作。
第十四方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第一网络设备在第一方面提供的任意一种方法中所执行的动作。
第十五方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行终端在第一方面提供的任意一种方法中所执行的动作。
第十六方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第二网络设备在第一方面提供的任意一种方法中所执行的动作。
第十七方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第三网络设备在第一方面提供的任意一种方法中所执行的动作。
第十八方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第四网络设备在第一方面提供的任意一种方法中所执行的动作。
第十九方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第五网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第一网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行终端在第一方面提供的任意一种方法中所执行的动作。
第二十二方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时， 使得计算机执行第二网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十三方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第三网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十四方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第四网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第五网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十六方面，提供了一种装置，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现第一网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十七方面，提供了一种装置，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现终端在第一方面提供的任意一种方法中所执行的动作。
第二十八方面，提供了一种装置，该该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现第二网络设备在第一方面提供的任意一种方法中所执行的动作。
第二十九方面，提供了一种装置，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现第三网络设备在第一方面提供的任意一种方法中所执行的动作。
第三十方面，提供了一种装置，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现第四网络设备在第一方面提供的任意一种方法中所执行的动作。
第三十一方面，提供了一种装置，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现第五网络设备在第一方面提供的任意一种方法中所执行的动作。
第三十二方面，提供了一种通信系统，至少包括：第一网络设备和装置，还可以包括第二网络设备、第三网络设备、第四网络设备和第五网络设备中的至少一个，其中，第一网络设备可以为上述方面所述的任意一种第一网络设备，第二网络设备可以为上述方面所述的任意一种第二网络设备，第三网络设备可以为上述方面所述的任意一种第三网络设备，第四网络设备可以为上述方面所述的任意一种第四网络设备，第五网络设备可以为上述方面所述的任意一种第五网络设备，装置可以为上述方面所述的任意一种装置，该装置可以为终端。
相较于现有技术，本申请实施例提供的方案，第一网络设备能够在确定终端的第一IP地址不再使用的情况下，将第一IP地址释放，而不需要通过一个定时器值确定 第一IP地址释放的时间，能够保证第一IP地址及时的释放，既保证了数据的正确传输，还可以提高资源利用率。
附图说明
图1为多PDU会话的PDU会话锚点的重定位过程的通信示意图；
图2为本申请实施例提供的多PDU会话场景下PDU会话锚点重定位过程中的业务数据流的示意图；
图3为本申请实施例提供的多归属PDU会话场景下PDU会话锚点重定位的网元架构示意图；
图4为本申请实施例提供的多归属PDU会话场景下PDU会话锚点重定位过程中的业务数据流的示意图；
图5为本申请实施例提供的UL CL PDU会话场景下PDU会话锚点重定位的网元架构示意图；
图6为本申请实施例提供的UL CL PDU会话场景下PDU会话锚点重定位过程中的业务数据流的示意图；
图7为本申请实施例提供的一种可能的网络架构的示意图；
图8为本申请实施例提供的一种释放IP地址的方法的流程图；
图9为本申请实施例提供的一种释放IP地址的方法的通信示意图；
图10为本申请实施例提供的又一种释放IP地址的方法的通信示意图；
图11为本申请实施例提供的又一种释放IP地址的方法的通信示意图；
图12为本申请实施例提供的又一种释放IP地址的方法的通信示意图；
图13为本申请实施例提供的又一种释放IP地址的方法的通信示意图；
图14为本申请实施例提供的又一种释放IP地址的方法的通信示意图；
图15为本申请实施例提供的一种网络设备的结构示意图；
图16为本申请实施例提供的一种网络设备的结构示意图；
图17为本申请实施例提供的一种装置的结构示意图；
图18为本申请实施例提供的一种装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请的描述中，“多个”是指两个或多于两个。
为了便于理解本申请实施例，下文中将对与本申请相关的概念做简单介绍。
PDU会话
PDU会话是终端和DN之间的连接，用于提供PDU连接性服务。第五代(fifth-generation，5G)通信系统的核心网支持的PDU连接性服务，是指提供终端和由数据网络名称(data network name，DNN)确定的DN之间进行PDU交换的服务。终端可以通过多个PDU会话，来连接到相同的DN或者不同的DN，终端还可以通过由不同的PDU会话锚点提供服务的一个或多个PDU会话，来连接到相同的DN。按 照传输的数据类型，PDU会话的类型可以分为IP类型、以太网类型或非结构数据类型。本申请实施例提供的方法中，PDU会话的类型可以为IP类型。
PDU会话通过PDU会话锚点接入到DN，PDU会话锚点可以为连接到DN的用户面功能(user plane function，UPF)实体，因此，PDU会话锚点也可以记为PDU会话锚点UPF，本文中以PDU会话锚点为UPF为例对本申请实施例提供的方法进行示例性说明。一个PDU会话可能只能通过一个PDU会话锚点连接到DN，该情况下，终端如果希望通过多个PDU会话锚点接入到DN，就需要建立多个PDU会话，这种通过多个PDU会话锚点接入到DN的方式称为多PDU会话(multi-PDU session)。一个PDU会话也可能通过多个PDU会话锚点接入到DN中，按照处理方式的不同，这种情况可以分为多归属PDU会话(multi-homed PDU session)和上行分类PDU会话。
(1)多PDU会话
在多PDU会话中，终端可以通过不同的PDU会话锚点来连接到相同的DN。不同PDU会话锚点对应的连接属于不同的PDU会话。
图2为多PDU会话场景的示意图。如图2所示，终端通过旧的PDU会话锚点连接到DN，此时终端已被分配IP地址(IP1)。当PDU会话锚点需要重定位时，SMF选择一个新的PDU会话锚点并建立新的PDU会话，为终端分配新的IP地址(IP2)。终端通过新的PDU会话锚点以新的IP地址接入到DN。此时旧的PDU会话和新的PDU会话属于不同的PDU会话。其中，经过旧的PDU会话锚点的业务数据流为在旧用户面路径上用旧IP地址发送的业务数据流，经过新的PDU会话锚点的业务数据流为在新用户面路径上用新IP地址发送的业务数据流。
(2)多归属PDU会话
多归属PDU会话的场景下，一个PDU会话可能与多个第六版互联网协议(internet protocol version 6，IPv6)前缀相关。该情况下，参见图3，在与PDU会话锚点相关的SSC模式为模式3时，在多归属PDU会话的PDU会话锚点重定位过程中，PDU会话通过多个PDU会话锚点(例如PDU会话锚点1和PDU会话锚点2)接入DN。通向不同的PDU会话锚点的用户面路径在一个普通的称为“分支点(branching point，BP)”的UPF上分支。BP发送上行数据到不同的PDU会话锚点，并融合下行数据到终端，例如，融合连接到终端的不同PDU会话锚点的数据。其中，终端可以通过接入网(access network，AN)，例如无线接入网(radio access network，RAN)，与“BP”交互信息。
图4为在与PDU会话锚点相关的SSC模式为模式3时，在多归属PDU会话的PDU会话锚点重定位过程中的业务数据流的示意图。如图4所示，终端通过旧的PDU会话锚点连接到DN，此时终端已被分配IP地址(IP1)。当PDU会话锚点需要重定位时，SMF为PDU会话改变到新的PDU会话锚点的过程包括：插入BP，该BP可以在已有的UPF上插入，也可以新选择UPF并插入BP，选择连接到BP的新的PDU会话锚点，更新会话上下文，配置新的IP地址(IP2)。终端通过新的PDU会话锚点以新的IP地址接入到DN。其中，由于插入了BP，包括旧的PDU会话锚点的用户面路径和包括新的PDU会话锚点的用户面路径均为新用户面路径，使得经过旧的PDU会话锚点的业务数据流为在新用户面路径上用旧IP地址发送的业务数据流，经过新的PDU会话锚点的业务数据流为在新用户面路径上用新IP地址发送的业务数据流。该情况下，终 端通过一个PDU会话连接到DN。
(3)上行分类PDU会话
在PDU会话的类型是IPv4类型、IPv6类型或者以太网类型时，在一个PDU会话的用户面路径上可以包括一个“上行分类器(Uplink Classifier，UL CL)”，因此，上行分类PDU会话也可以称为UL CL PDU会话。参见图5，UL CL可以插入到一个UPF上，插入UL CL的目标是将一些匹配有SMF提供的传输滤波器的数据分流。
图6为在与PDU会话锚点相关的SSC模式为模式3时，在UL CL PDU会话的PDU会话锚点重定位过程中数据流的示意图。如图6所示，终端通过旧的PDU会话锚点连接到中心DN，此时终端已被分配IP地址(IP1)。当PDU会话锚点需要重定位时，SMF为PDU会话改变到新的PDU会话锚点的过程包括：选择新的连接到UL CL的PDU会话锚点，更新会话上下文，配置新的IP地址(IP2)。终端通过新的PDU会话锚点以新的IP地址接入到中心DN。另外，参见图6，UL CL可以通过不同的PDU会话锚点将数据分流到中心DN。
其中，经过旧的PDU会话锚点的业务数据流为在旧用户面路径上用旧IP地址发送的业务数据流，经过新的PDU会话锚点的业务数据流为在新用户面路径上用新IP地址发送的业务数据流。该情况下，终端通过一个PDU会话连接到DN。
SSC模式
5G网络的系统架构的SSC模式能够满足终端多种不同应用和服务的连续性要求。与PDU会话锚点相关的SSC模式在PDU会话的生命周期内不改变。SMF在确定与PDU会话锚点相关的SSC模式时，可以通过接受终端请求的SSC模式来确定，也可以通过签约或局部配置来修改终端的请求中的SSC模式来确定。与PDU会话锚点相关的SSC模式包括模式1，模式2和模式3。
对于SSC模式1的PDU会话，在建立PDU会话时，PDU会话锚点一直维护，对于IP类型的PDU会话，IP连续性一直得到支持，与终端的移动事件无关。
对于SSC模式2的PDU会话，网络可能触发PDU会话的释放，并指示终端立即建立到同一个DN的新的PDU会话。在PDU会话释放之后，SMF可以为新建立的PDU会话选择一个新的PDU会话锚点。
对于SSC模式3的PDU会话，网络允许在旧PDU会话锚点释放之前，让终端经过一个新的PDU会话锚点建立与相同DN的连接。当触发条件满足时，SMF决定是否选择一个适合终端的新情况的PDU会话锚点。
SSC模式3可应用于任何类型的PDU会话。在SSC模式3下，为保证业务连续性和不中断的用户服务体验，新的IP地址分配后，旧的IP地址会保持一段时间然后释放。
在本申请实施例中，IP地址可以为第四版互联网协议(internet protocol version 4，IPv4)地址或IPv6前缀，其中，IPv6前缀可表示为IP prefix，其作用相当于IPv4中的IP地址。
IP地址管理
在本申请实施例提供的方法中，PDU会话为IP类型，IP版本有IPv4和IPv6，SMF根据选择的IP版本给终端分配IP地址。
对于IPv4类型的PDU会话，核心网会为终端分配IP地址，在PDU会话建立过程中，SMF通过会话管理非接入层(session management non-access stratum，SM NAS)信令发送IP地址和IPv4配置参数给终端。如果应用第4版动态主机配置协议(dynamic host configuration protocol version 4，DHCPv4)，SMF通过DHCPv4发送IP地址和IPv4配置参数给终端。为此，SMF配置UPF作为PDU会话锚点来发送终端和SMF之间的所有DHCPv4信息。
对于IPv6类型的PDU会话，核心网使用无状态地址自动配置(stateless address autoconfiguration，SLAAC)来配置IPv6前缀给终端。SMF使用无状态的第6版动态主机配置协议(dynamic host configuration protocol version 6，DHCPv6)，通过PDU会话锚点发送路由公告信息和IPv6配置参数给终端。为此，SMF配置UPF作为PDU会话锚点来发送终端和SMF之间的所有的路由器请求(router solicitation，RS)/路由器公告(router advertisement，RA)和DHCPv6信息。终端收到RA消息时，通过IPv6SLAAC来构造一个完整的IPv6地址。
现有方案中，多PDU会话的PDU会话锚点的重定位过程可参见图1，具体包括以下步骤：101、会话管理功能(session management function，SMF)实体确定当前服务的PDU会话锚点(即UPF1)需重定位；102、SMF实体通过核心接入和移动管理功能(core access and mobility management function，AMF)实体向终端发送非接入层(non-access stratum，NAS)消息，NAS消息用于通知终端当前的PDU会话将要释放，还用于通知终端重新建立PDU会话；NAS消息可以包含PDU会话标识(identifier，ID)，PDU会话ID用于终端确定将要释放的PDU会话，NAS消息还可以包括一个指示网络希望维护PDU会话多久的定时器值，以使得终端在定时器到期之前转移业务数据流；103、终端建立新的PDU会话，新的PDU会话的PDU会话锚点为UPF2；104、终端或SMF触发PDU会话的释放，若SMF释放PDU会话，则SMF在定时器到期时释放旧的PDU会话，释放终端在旧的PDU会话中使用的IP地址。
上述流程中，SMF采用定时器的方式来确定释放IP地址的时间点，然而定时器的时长是根据经验确定的，不够精确，该情况下，若IP地址释放的过早，可能终端侧旧的PDU会话还没释放，导致数据传输出错，若IP地址释放的过晚，会使得IP地址占用的时间太长，降低资源利用率。
有鉴于此，本申请实施例提供了一种释放IP地址的方法，使得网络设备能够在合适的时机释放终端的IP地址。本申请实施例的方法可以应用在SSC模式3下PDU会话锚点重定位的场景，例如多PDU会话的场景、多归属PDU会话的场景和UL CL PDU会话的场景。
本申请实施例提供的方法可以应用于图7所示的5G网络，如图7所示，该5G网络可以包括下述多个网络功能(network functions，NF)实体：鉴权服务器功能(authentication server function，AUSF)实体、AMF实体、DN、统一数据管理(unified data management，UDM)实体、策略控制功能(policy control function，PCF)实体、(R)AN设备、UPF实体、终端、应用功能(application function，AF)实体、SMF实体。可理解的是，图7仅为示例性架构图，除图7所示功能实体之外，该5G网络架构还可以包括其他功能实体，例如，在AF实体和PCF实体之间还可能包括网络开放功能(network exposure  function，NEF)实体，还可以包括管理和编排(management and orchestration，MANO)网元和/或移动边缘编排(mobile edge orchestrator，MEO)网元，其中，MANO和MEO是部署和实现时需要的网元，具备网络管理功能。
终端通过下一代网络(next generation)接口1(简称N1)与AMF实体通信，(R)AN设备通过N接口2(简称N2)与AMF实体通信，(R)AN设备通过N接口3(简称N3)与UPF实体通信，UPF实体通过N接口6(简称N6)与DN通信，AMF实体通过N接口11(简称N11)与SMF实体通信，AMF实体通过N接口8(简称N8)与UDM实体通信，AMF实体通过N接口12(简称N12)与AUSF实体通信，AMF实体通过N接口15(简称N15)与PCF实体通信，SMF实体通过N接口7(简称N7)与PCF实体通信，SMF实体通过N接口4(简称N4)与UPF实体通信，SMF实体通过N接口10(简称N10)与UDM实体通信，UDM实体通过N接口13(简称N13)与AUSF实体通信，PCF实体通过N接口5(简称N5)与AF实体通信。
此外，图7中的UDM实体、AUSF实体、PCF实体、AMF实体和SMF实体也可以统称为控制面(control plane，CP)功能实体，本申请实施例对此不作具体限定。
具体的，(R)AN设备主要功能包括：提供无线连接；UPF实体主要功能包括：使数据包路由和转发、移动性锚点、上行分类器来支持路由业务流到DN、BP来支持多归属PDU会话等；DN可以为运营商服务，互联网接入或者第三方服务；AMF实体主要功能包含管理用户注册、可达性检测、SMF节点的选择、移动状态转换管理等；SMF实体主要功能包括：控制会话的建立、修改和删除，用户面节点的选择等；PCF实体主要功能包括：策略决策点，提供基于业务数据流和应用检测，门控，服务质量(quality of service，QoS)和基于流的计费控制等规则；AF实体主要功能包括：与第三代合作伙伴计划(3rd generation partnership project，3GPP)核心网交互来提供服务，来影响业务流路由、接入网能力开放、策略控制等；AUSF实体主要功能包括：提供鉴权服务；UDM实体主要功能包括：存储用户签约数据；NEF实体用于安全地开放由3GPP网络功能提供的服务和能力，如第三方、边缘计算、AF等。
本申请实施例中的终端可以为用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端还可以是无线局域网(wireless local area networks，WLAN)中的站点(staion，ST)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备(也可以称为穿戴式智能设备)。终端还可以为下一代通信系统中的终端设备，例如，5G中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)中的终端设备，新无线(new radio，NR)通信系统中的终端设备等。
本申请实施例提供了一种释放IP地址的方法，如图8所示，该方法包括：
1001、第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位，其中，第一用户面功能实体为终端的第一PDU会话的PDU会话锚点。
其中，终端可能有一个或多个PDU会话，当终端有多个PDU会话时，第一PDU 会话可以为该多个PDU会话中的任意一个PDU会话。
具体的，SMF可以在终端移出了第一用户面功能实体的覆盖范围的情况下，或者，第一用户面功能实体的负载较大的情况下，或者，终端距离第一用户面功能实体较远的情况下，确定PDU会话锚点需要从第一用户面功能实体重定位，还可以在其他情况下，确定PDU会话锚点需要从第一用户面功能实体重定位，在此不再一一说明。
示例性的，基于图2、图4和图6的示例，第一用户面功能实体可以为旧的PDU会话锚点，第一IP地址可以为IP1。
1002、第一网络设备确定终端的第一IP地址不再使用，第一IP地址为终端在第一PDU会话中使用的IP地址。
可选的，步骤1002在具体实现时可以通过以下5种实现方式中的任意一种实现方式实现。
方式一、第一网络设备从第二网络设备或第五网络设备接收第一通知，第一通知用于通知第一网络设备：终端的连接状态为空闲态。
示例性的，第一通知可以为空闲态通知。第一网络设备可以通过接收第一通知确定终端的连接状态为空闲态，第一通知包含终端的连接状态为空闲态的信息。
其中，终端的连接状态可以为空闲态或连接态，需要说明的是，一旦终端的连接状态为空闲态时，说明终端断开了全部PDU会话的连接，此时即可释放终端的第一IP地址。示例性的，第二网络设备可以为AMF。
可选的，在第一网络设备从第二网络设备接收第一通知之前，该方法还可以包括：第二网络设备确定终端的连接状态为空闲态，第二网络设备向第一网络设备发送第一通知，第一通知包括终端的连接状态为空闲态的信息。
可选的，终端确定终端的连接状态为空闲态之后，终端可以与第二网络设备同步终端的连接状态，以使得第二网络设备向第一网络设备发送第一通知。具体的，终端会和AMF同步终端的连接状态，当终端的连接状态为空闲态时，AMF可以向第一网络设备发送第一通知。
方式二、第一网络设备确定第一PDU会话的状态为去激活状态。
可以理解的是，PDU会话的状态可以包括去激活状态和激活状态，当PDU会话的状态为去激活状态时，全部的PDU会话上的数据不再传输，此时即可释放终端的第一IP地址。
可选的，第一网络设备确定第一PDU会话的状态为去激活状态，可以包括：第一网络设备接收第五网络设备发送的第五通知，第五通知用于通知第一网络设备：第一PDU会话的状态为去激活状态；第一网络设备根据第五通知确定第一PDU会话的状态为去激活状态。当然，第一网络设备也可以自己确定第一PDU会话的状态为去激活状态。
示例性的，第五通知可以为去激活状态通知，去激活状态通知包括第一PDU会话的状态为去激活状态的信息。
方式三、第一网络设备从第三网络设备或第五网络设备接收第二通知，第二通知用于通知第一网络设备：第一IP地址不活跃。
示例性的，第二通知可以为第一IP地址的IP地址不活跃报告。
第一IP地址不活跃可以指第一IP地址超过第一时间段未使用。第一时间段可以为网络配置的，还可以为通过其他方式确定的，示例性的，第一时间段可以为3毫秒(ms)或5ms。
当PDU会话为多PDU会话时，第三网络设备可以为第一用户面功能实体，当PDU会话为多归属PDU会话时，第三网络设备可以为BP，当PDU会话为UL CL PDU会话时，第三网络设备可以为UL CL。
可选的，在第一网络设备从第三网络设备接收第二通知之前，该方法还可以包括：第三网络设备对第一IP地址的活跃性进行检测；若检测到第一IP地址不活跃，第三网络设备向第一网络设备发送第二通知。
可选的，在第三网络设备对第一IP地址的活跃性进行检测之前，该方法还可以包括：第一网络设备向第三网络设备发送第一指示，第一指示用于指示第三网络设备检测第一IP地址的活跃性；第三网络设备从接收第一网络设备接收第一指示；该情况下，第三网络设备对第一IP地址的活跃性进行检测，可以包括：第三网络设备根据第一指示对第一IP地址的活跃性进行检测。
示例性的，第一指示可以为第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位之后向第三网络设备发送的指示。
方式四、第一网络设备从第四网络设备或第五网络设备接收第三通知，第三通知用于通知第一网络设备：第一IP地址的IP连接释放。
示例性的，第三通知可以为第一IP地址的IP连接释放报告。
示例性的，第一IP地址的IP连接释放是指在第二时间段内终端的所有应用程序均未使用第一IP地址发送数据或者第一IP地址的IP连接释放。第二时间段可以为网络配置的，还可以为通过其他方式确定的，示例性的，第二时间段可以为2ms或3ms。
其中，第四网络设备可以为MANO或AF。AF可以感知应用层的消息，当终端中的所有应用程序在第二时间段内均不采用第一IP地址发送数据时，AF向第一网络设备发送第三通知。另外，应用程序和终端之间可以有一个第一IP地址的IP连接(例如，传输控制协议(transmission control protocol，TCP)连接)，当IP连接释放时，AF能够立刻感知到，该情况下，AF也可以向第一网络设备发送第三通知。
可选的，在第一网络设备接收第四网络设备发送的第三通知之前，该方法还可以包括：第四网络设备确定第一IP地址的IP连接释放；第四网络设备向第一网络设备发送第三通知。
方式五、当PDU会话为多PDU会话时，在步骤1001之后，该方法还可以包括：第一网络设备选择第二用户面功能实体作为终端的第二PDU会话的PDU会话锚点；该情况下，步骤1002可以包括：第一网络设备从终端或第五网络设备接收第四通知，第四通知用于通知第一网络设备：终端完成了第一IP地址到第二IP地址的切换，其中，第二IP地址为终端在第二PDU会话中使用的IP地址。
当PDU会话为多归属PDU会话或UL CL PDU会话时，在步骤1001之后，该方法还可以包括：第一网络设备选择第二用户面功能实体作为第一PDU会话的新的PDU会话锚点；该情况下，步骤1002可以包括：第一网络设备从终端或第五网络设备接收第四通知，第四通知用于通知第一网络设备：终端完成了第一IP地址到第二IP地址 的切换，其中，第二IP地址为第一PDU会话的PDU会话锚点为第二用户面功能实体时，终端在第一PDU会话中使用的IP地址。
示例性的，基于图2、图4和图6的示例，第二用户面功能实体可以为新的PDU会话锚点，第二IP地址可以为IP2。
可选的，在第一网络设备从终端接收第四通知之前，该方法还可以包括：
终端确定完成了从第一IP地址到第二IP地址的切换；
终端向第一网络设备发送第四通知。
需要说明的是，在为终端分配第二IP地址之后，终端需要逐渐将经过第一用户面功能实体的业务数据流转移到包括第二用户面功能实体的用户面路径上，当转移完成(即完成从第一IP地址到第二IP地址的切换)后，终端仅采用第二IP地址在包括第二用户面功能实体的用户面路径上传输业务数据流。在终端完成了从第一IP地址到第二IP地址的切换之后，第一网络设备释放第一IP地址，删除第一用户面功能实体，PDU会话锚点重定位结束，也就是说在PDU会话锚点重定位结束之后，PDU会话中仅存在一个用户面路径。示例性的，参见图2、图4和图6，PDU会话锚点重定位结束之后的用户面路径为包括新的PDU会话锚点的用户面路径。
1003、第一网络设备释放第一IP地址。
可选的，在步骤1003之前，该方法还可以包括：第一网络设备向终端发送第二指示，第二指示用于指示终端释放第一IP地址；终端从第一网络设备接收第二指示，终端根据第二指示释放第一IP地址。
在第一网络设备确定第一IP地址不再使用后，第一网络设备可以向终端发送第二指示，终端收到第二指示后立即释放第一IP地址，以便第一网络设备释放第一IP地址。
可选的，在步骤1003之前，该方法还可以包括：第一网络设备向终端发送第三指示，第三指示用于指示终端进入空闲态时释放第一IP地址；终端从第一网络设备接收第三指示；当终端的连接状态为空闲态时，终端释放第一IP地址。
在第一网络设备确定第一IP地址不再使用之前，第一网络设备可以向终端发送第三指示，从而使得终端进入空闲态时释放第一IP地址，以便第一网络设备在确定终端处于空闲态时释放第一IP地址。
可选的，在步骤1002之前，该方法还可以包括：第一网络设备将第一IP地址的状态标记为待释放；该情况下，步骤1002在具体实现时可以包括：第一网络设备确定第一IP地址的状态为待释放，并释放第一IP地址。
由于第一网络设备可能接收到多个第三通知，该情况下，第一网络设备需要确定第三通知中的IP地址是否为需要释放的IP地址。第一网络设备可以在确定第一PDU会话中的PDU会话锚点需要从第一用户面功能实体重定位后，将第一IP地址的状态标记为待释放，从而使得第一网络设备在接收到第三通知后可以快速的确定第一IP地址为需要释放的IP地址。
上述实施例中第一用户面功能实体和第二用户面功能实体均由同一个SMF控制。在多归属PDU会话和UL CL PDU会话场景下，还存在以下情况，即在PDU会话锚点重定位之后，为终端服务的为第二SMF，第一SMF不能再直接与终端交互信息，第 一SMF为控制第一用户面功能实体的SMF，第二SMF为控制第二用户面功能实体的SMF。该情况下，第一网络设备为第一SMF，第五网络设备可以为第二SMF。第五网络设备获取的第一通知可以为第二网络设备发送的，第二网络设备确定第一通知的方法可以参见上文；第五网络设备获取的第二通知可以为第三网络设备发送的，第三网络设备确定第二通知的方法可以参见上文；第五网络设备获取的第四通知可以为终端发送的，终端确定第四通知的方法可以参见上文；第五网络设备获取的第三通知可以为第四网络设备发送的，第四网络设备确定第三通知的方法可以参见上文；第五网络设备可以自己确定第一PDU会话的状态为去激活状态。
本申请实施例提供的方法，第一网络设备在确定终端的第一IP地址不再使用的情况下，将第一IP地址释放，而不再通过一个定时器值确定第一IP地址释放的时间，可以保证第一IP地址及时的释放，既保证了数据的正确传输还可以提高资源利用率。
以下从各个网元交互的角度通过多个实施例对上述方法中的各个方案进行示例性说明。需要说明的是，为描述简便，下述各个实施例中，相同或相似的内容可以相互引用。
实施例1
实施例1提供了一种释放IP地址的方法，如图9所示，该方法可以包括：
1101、SMF确定PDU会话锚点需要从第一UPF重定位。
其中，在步骤1101之前，已经存在一个第一PDU会话，终端采用第一IP地址在第一PDU会话中传输业务数据流。
具体的，SMF可以在终端移出了第一UPF的覆盖范围的情况下，或者，第一UPF的负载较大的情况下，或者，终端距离第一UPF较远的情况下，确定PDU会话锚点需要从第一UPF重定位，还可以在其他情况下，确定PDU会话锚点需要从第一UPF重定位，在此不再一一说明。
下述步骤1102a和步骤1102b为可选的步骤，择一进行执行。例如，当该方法的应用场景为多PDU会话场景时，执行步骤1102a，或者，当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1102b。
1102a、SMF选择第二UPF，并采用第二UPF建立第二PDU会话。
在建立第二PDU会话的过程中，SMF为终端分配第二IP地址。需要说明的是，SMF的IP地址范围和分配IP地址的方法可以预先根据多个UPF进行配置。
1102b、SMF选择第二UPF，并将第一PDU会话中的PDU会话锚点从第一UPF重定位至第二UPF。
其中，第二UPF可以为SMF选择出的，SMF具体可以根据UPF的负载、网络负载或者终端距离UPF的远近在多个UPF中择优选择出第二UPF。
在执行步骤1102b的过程中，SMF为终端分配第二IP地址，选择新的BP或UL CL，为了支持通向第二UPF的通路，更新会话上下文。需要说明的是，SMF的IP地址范围和分配IP地址的方法可以预先根据多个UPF进行配置。
在步骤1102a或1102b之后，终端会将经过第一UPF的业务数据流逐渐转移到包含第二UPF的用户面路径中。
1103、SMF将第一IP地址的状态标记为待释放。
1104、SMF向终端发送第三指示。
第三指示用于指示终端进入空闲态时释放第一IP地址，第三指示可以包含在NAS消息中。具体的，SMF可以将第三指示先发送给AMF，AMF将第三指示转发给终端。
步骤1102a、步骤1103和步骤1104中的任意两个步骤的执行顺序不分先后；或者，步骤1102b、步骤1103和步骤1104中的任意两个步骤的执行顺序不分先后。
1105、NEF/PCF接收MANO/AF发送的第三通知。
可选的，MANO可以替换为MEO。
1106、NEF/PCF将第三通知向SMF发送。
1107、SMF接收NEF/PCF发送的第三通知。
1108、SMF确定第一IP地址的状态为待释放，确定释放第一IP地址。
1109、SMF向终端发送第二指示。
第二指示用于指示终端释放第一IP地址，第二指示可以包含在NAS消息中。具体的，SMF可以将第二指示先发送给AMF，AMF将第二指示转发给终端。
1110、终端根据接收到的SMF发送的第二指示释放第一IP地址和相关上下文。
在步骤1110之后，当该方法的应用场景为多PDU会话场景时，执行步骤1111a；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1111b。
1111a、SMF释放第一PDU会话，释放第一IP地址，更新第一UPF中的会话上下文。
1111b、SMF释放第一IP地址，更新BP或UL CL和第一UPF中的会话上下文。
实施例2
实施例2提供了一种释放IP地址的方法，如图10所示，该方法可以包括：步骤1201-1208b。
步骤1201-1204可以参考图9中步骤1101-1104的描述。
其中，步骤1201与步骤1101相同；当该方法的应用场景为多PDU会话场景时，执行1202a，步骤1202a与步骤1102a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1202b，步骤1202b与步骤1102b相同；步骤1203与步骤1103相同；步骤1204与步骤1104相同。
1205、终端确定终端的连接状态为空闲态，终端释放第一IP地址并与AMF同步终端的连接状态。
其中，终端的连接状态可以为空闲态或连接态，需要说明的是，一旦终端的连接状态为空闲态时，说明终端断开了全部PDU会话的连接。
1206、AMF向SMF发送第一通知。
第一通知中包括终端的连接状态为空闲态的信息。
1207、SMF根据接收到的第一通知确定终端的连接状态为空闲态。
当该方法的应用场景为多PDU会话场景时，执行步骤1208a，当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1208b。
1208a、SMF确定第一IP地址的状态为待释放时，释放第一PDU会话，释放第一IP地址，更新第一UPF中的会话上下文。
1208b、SMF确定第一IP地址的状态为待释放时，释放第一IP地址，更新BP或 UL CL和第一UPF中的会话上下文。
实施例3
实施例3提供了一种释放IP地址的方法，如图11所示，该方法可以包括：步骤1301-1309b。
步骤1301-1304可以参考图9中步骤1101-1104的描述。
其中，步骤1301与步骤1101相同；当该方法的应用场景为多PDU会话场景时，执行步骤1302a，步骤1302a与步骤1102a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1302b，步骤1302b与步骤1102b相同；步骤1303与步骤1103相同；步骤1304与步骤1104相同。
1305、SMF确定第一PDU会话的状态为去激活状态。
PDU会话的状态可以为去激活状态和激活状态，当PDU会话的状态为去激活状态时，全部的PDU会话上的数据不再传输，此时即可释放终端的IP地址。
步骤1306-1309b可以参考图9中步骤1108-1111b的描述。
其中，步骤1306与步骤1108相同；步骤1307与步骤1109相同；步骤1308与步骤1110相同；当该方法的应用场景为多PDU会话场景时，执行步骤1309a，步骤1309a与步骤1111a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1309b，步骤1309b与步骤1111b相同。
实施例4
实施例4提供了一种释放IP地址的方法，如图12所示，该方法可以包括：步骤1401-1412b。
步骤1401-1404可以参考图9中步骤1101-1104的描述。
其中，步骤1401与步骤1101相同；当该方法的应用场景为多PDU会话场景时，执行步骤1402a，步骤1402a与步骤1102a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1402b，步骤1402b与步骤1102b相同；步骤1403与步骤1103相同，步骤1404与步骤1104相同。
当该方法的应用场景为多PDU会话场景时，执行步骤1405a-1407a，当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1405b-1407b。
1405a、SMF向第一UPF发送第一指示。
具体的，第一指示用于指示第一UPF对第一IP地址的活跃性进行检测。
1406a、第一UPF根据接收到的第一指示对第一IP地址的活跃性进行检测。
1407a、若检测到第一IP地址不活跃，第一UPF向SMF发送第二通知。
第二通知中包括第一IP地址不活跃的信息，第一IP地址不活跃可以指第一IP地址超过第一时间段未使用。
1405b、SMF向BP或UL CL发送第一指示。
具体的，第一指示用于指示BP或UL CL对第一IP地址的活跃性进行检测。
1406b、BP或UL CL根据接收到的第一指示对第一IP地址的活跃性进行检测。
1407b、若检测到第一IP地址不活跃，BP或UL CL向SMF发送第二通知。
第二通知中包括第一IP地址不活跃的信息，第一IP地址不活跃可以指第一IP地址超过第一时间段未使用。
1408、SMF接收第二通知。
步骤1409-1412b可以参考图9中步骤1108-1111b的描述。
其中，步骤1409与步骤1108相同；步骤1410与步骤1109相同；步骤1411与步骤1110相同；当该方法的应用场景为多PDU会话场景时，执行步骤1412a，步骤1412a与步骤1111a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1412b，步骤1412b与步骤1111b相同。
实施例5
实施例5提供了一种释放IP地址的方法，如图13所示，该方法可以包括：步骤1501-1511b。
步骤1501-1504可以参考图9中步骤1101-1104的描述。
其中，步骤1501与步骤1101相同；当该方法的应用场景为多PDU会话场景时，执行1502a，步骤1502a与步骤1102a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行步骤1502b，步骤1502b与步骤1102b相同；步骤1503与步骤1103相同；步骤1504与步骤1104相同。
1505、终端采用多径技术完成了从第一IP地址到第二IP地址的切换。
1506、终端向SMF发送第四通知。
具体的，终端可以先将第四通知发送至AMF，由AMF将第四通知转发给SMF。第四通知可以包含在NAS消息中。
1507、SMF接收终端发送的第四通知。
步骤1508-1511可以参考图9中步骤1108-1111b的描述。
其中，步骤1508与步骤1108相同；步骤1509与步骤1109相同；步骤1510与步骤1110相同；当该方法的应用场景为多PDU会话场景时，执行步骤1511a，步骤1511a与步骤1111a相同；当该方法的应用场景为多归属PDU会话或UL CL PDU会话场景时，执行1511b，步骤1511b与步骤1111b相同。
实施例6
上述实施例1至实施例5中第一UPF和第二UPF均由同一个SMF控制。在多归属PDU会话和UL CL PDU会话的场景下，还存在以下情况，即在进行PDU会话锚点重定位之后，为终端服务的为第二SMF，第一SMF不能再直接与终端交互信息，第一SMF为第一PDU会话中控制第一UPF的SMF，第二SMF为第一PDU会话中控制第二UPF的SMF。该情况下，第一SMF可以通过接收第二SMF发送的信息确定释放第一IP地址。具体的，参见图14，该方法可以包括：
1601、第一SMF确定PDU会话锚点需要从第一UPF重定位。
其中，在步骤1601之前，已经存在一个第一PDU会话，终端采用第一IP地址在第一PDU会话中传输业务数据流。
第一SMF确定PDU会话锚点需要从第一UPF重定位的方法可以参见上文中的步骤1101，在此不再赘述。
1602、AMF选择第二SMF。
其中，第二SMF可以为AMF选择出的，也可以为第一SMF选择出的，图14中以第二SMF为AMF选择出的为例进行绘制。
1603、第一SMF将第一IP地址的状态标记为待释放。
1604、第二SMF选择第二UPF。
第二SMF具体可以根据UPF的负载、网络负载或者终端距离UPF的远近在多个UPF中择优选择出第二UPF。
步骤1603和步骤1604的执行顺序不分先后。
1605、第一SMF向终端发送第三指示。
1606、第一SMF和第二SMF将第一UPF重定位至第二UPF。
第三指示用于指示终端进入空闲态时释放第一IP地址，第三指示可以包含在NAS消息中。具体的，SMF可以将第三指示先发送给AMF，AMF将第三指示转发给终端。
1607、第二SMF获取目标信息。
具体的，目标信息可以为上文中的第一通知、第二通知、第三通知、第四通知和第五通知中的一个或多个。
1608、第二SMF向第一SMF发送目标信息。
1609、第一SMF接收目标信息。
1610、第一SMF根据第一IP地址的状态，确定释放第一IP地址。
1611、第一SMF向第二SMF发送第二指示。
需要说明的是，由于这种场景下，终端只可以和第二SMF通信，因此，第一SMF需要将第二指示通过第二SMF转发给终端。
1612、第二SMF将接收到的第二指示转发给终端。
具体的，第二SMF可以先将第二指示发送给AMF，AMF将第二指示转发给终端。
1613、终端根据接收到的第二SMF发送的第二指示释放第一IP地址和相关上下文。
1614、第一SMF释放第一IP地址，更新BP或UL CL和第一UPF中的会话上下文。
关于实施例1-实施例6的有益效果可以参见上文，在此不再赘述。
需要说明的是，在本申请实施例中，第一用户面功能实体记为第一UPF，第二用户面功能实体记为第二UPF，在附图中一个步骤横跨多个功能实体时，表示该步骤在实现的过程中可能需要与多个功能实体中的一个或多个进行信息交互。示例性的，参见图9，步骤1102a在实现的过程中SMF可能需要与终端、AMF、第一UPF、第二UPF和NEE/PCF中的一个或多个进行信息交互。
上述主要从各个网元之间交互的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如第一网络设备、第二网络设备、装置(例如终端)等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一网络设备、第二网络设备、装置等进 行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图15示出了上述实施例中所涉及的网络设备的一种可能的结构示意图，该网络设备包括处理单元2001和通信单元2002，还可以包括存储单元2003。图15所示的结构示意图可以用于示意上述实施例中所涉及的第一网络设备、第二网络设备、第三网络设备、第四网络设备或第五网络设备的结构。
当图15所示的结构示意图用于示意上述实施例中所涉及的第一网络设备的结构时，处理单元2001用于对第一网络设备的动作进行控制管理，例如，处理单元2001用于支持第一网络设备执行图8中的过程1001-1003，图9中的过程1101-1104、1107-1109、1111a和1111b，图10中的过程1201-1204和1207-1208b，图11中的过程1301-1307、1309a和1309b，图12中的过程1401-1405a、1405b、1408-1410、1412a和1412b，图13中的过程1501-1504、1507-1509、1511a和1511b，图14中的过程1601、1603、1605、1606、1609-1611和1614，和/或本申请实施例中所描述的其他过程中的第一网络设备执行的动作。通信单元2002用于支持第一网络设备与其他网络实体的通信，例如，与图9中示出的终端、AMF等之间的通信。存储单元2003用于存储第一网络设备的程序代码和数据。
当图15所示的结构示意图用于示意上述实施例中所涉及的第二网络设备的结构时，处理单元2001用于对第二网络设备的动作进行控制管理，例如，处理单元2001用于支持第二网络设备执行图9中的过程1102a和1102b、1104、1109、1111a和1111b，图10中的过程1202a、1202b、1204、1205、1206、1208a和1208b，图11中的过程1302a、1302b、1304、1307、1309a和1309b，图12中的过程1402a、1402b、1404、1410、1412a和1412b，图13中的过程1502a、1502b、1504、1506、1509、1511a和1511b，图14中的过程1602、1605、1606、1612和1614和/或本申请实施例中所描述的其他过程中的第二网络设备执行的动作。通信单元2002用于支持第二网络设备与其他网络实体的通信，例如，与图9中示出的终端、SMF等之间的通信。存储单元2003用于存储第二网络设备的程序代码和数据。
当图15所示的结构示意图用于示意上述实施例中所涉及的第三网络设备的结构时，处理单元2001用于对第三网络设备的动作进行控制管理，例如，当PDU会话为多PDU会话时，第三网络设备可以为第一UPF，处理单元2001用于支持第三网络设备执行图9中的过程1102a、1102b、1111a和1111b，图10中的过程1202a、1202b、1208a和1208b，图11中的过程1302a、1302b、1309a和1309b，图12中的过程1402a、1402b、1406a、1407a、1412a和1412b，图13中的过程1502a、1502b、1511a和1511b，图14中的过程1606和1614；当PDU会话为多归属PDU会话或UL CL PDU会话时，第三网络设备可以为BP或UL CL，处理单元2001用于支持第三网络设备执行图12中的过程1402a、1402b、1406b、1407b、1412a和1412b，图14中的过程1606和1614和/或本申请实施例中所描述的其他过程中的第三网络设备执行的动作。通信单元2002用于支持第三网络设备与其他网络实体的通信，例如，与图12中示出的终端、SMF 等之间的通信。存储单元2003用于存储第三网络设备的程序代码和数据。
当图15所示的结构示意图用于示意上述实施例中所涉及的第四网络设备的结构时，处理单元2001用于对第四网络设备的动作进行控制管理，例如，处理单元2001用于支持第四网络设备执行图9中的过程1105，和/或本申请实施例中所描述的其他过程中的第四网络设备执行的动作。通信单元2002用于支持第四网络设备与其他网络实体的通信，例如，与图9中示出的NEF/PCF等之间的通信。存储单元2003用于存储第四网络设备的程序代码和数据。
当图15所示的结构示意图用于示意上述实施例中所涉及的第五网络设备的结构时，处理单元2001用于对第五网络设备的动作进行控制管理，例如，处理单元2001用于支持第五网络设备执行图14中的过程1604、1606、1607、1608、1612和1614和/或本申请实施例中所描述的其他过程中的第五网络设备执行的动作。通信单元2002用于支持第五网络设备与其他网络实体的通信，例如，与图14中示出的第一SMF、终端等之间的通信。存储单元2003用于存储第五网络设备的程序代码和数据。
其中，处理单元2001可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元2002可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元2003可以是存储器。
当处理单元2001为处理器，通信单元2002为通信接口，存储单元2003为存储器时，本申请实施例所涉及的网络设备可以为图16所示的网络设备。
参阅图16所示，该网络设备包括：处理器2101、通信接口2102、存储器2103。可选的，网络设备还可以包括总线2104。其中，通信接口2102、处理器2101以及存储器2103可以通过总线2104相互连接；总线2104可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线2104可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的单元的情况下，图17示出了上述实施例中所涉及的装置的一种可能的结构示意图。参见图17，装置22包括：处理单元2201和通信单元2202。处理单元2201用于对装置22的动作进行控制管理，例如，处理单元2201用于支持装置22执行图9中的过程1102a、1102b和1110，图10中的过程1202a、1202b和1205，图11中的过程1302a、1302b和1308，图12中的过程1402a、1402b和1411，图13中的过程1502a、1502b、1505、1506和1510，图14中的过程1606和1613和/或本申请实施例中所描述的其他过程中的装置22执行的动作。通信单元2202用于支持装置22与其他网络设备之间的通信。参见图17，装置22还可以包括存储单元2203，用于存储装置22的程序代码 和数据。
其中，处理单元2201可以是处理器或控制器，例如可以CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元2202为收发器、收发电路等。存储单元2203可以是存储器。
当处理单元2201为处理器，通信单元2202包括发射器和/或接收器，存储单元2203为存储器时，本申请实施例所涉及的装置可以为图18所示的装置。
图18示出了本申请实施例中所涉及的装置23的一种可能的设计结构的简化示意图。如图18所示，装置23包括收发器2301、处理器2302、存储器2303。可选的，装置23还可以包括总线2304。其中，处理器2302也可以为控制器。
处理器2302对装置23的动作进行控制管理，用于执行上述本申请实施例中由装置23进行的处理过程。例如，图9中的过程1102a、1102b和1110，图10中的过程1202a、1202b和1205，图11中的过程1302a、1302b和1308，图12中的过程1402a、1402b和1411，图13中的过程1502a、1502b、1505、1506和1510，图14中的过程1606和1613和/或本申请实施例中所描述的其他过程中的装置23执行的动作。
示例性的，图17或图18所示的装置可以是终端。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述方法。
本申请实施例还提供了一种装置，该装置以芯片的产品形态存在，该装置包括处理器、存储器和收发组件，收发组件包括输入输出电路，存储器用于存储计算机执行指令，处理器通过执行存储器中存储的计算机执行指令实现上述方法。
本申请实施例还提供了一种通信系统，至少包括：第一网络设备和装置，还可以包括第二网络设备、第三网络设备、第四网络设备和第五网络设备中的至少一个，其中，第一网络设备可以为上述实施例所述的任意一种第一网络设备，第二网络设备可以为上述实施例所述的任意一种第二网络设备，第三网络设备可以为上述实施例所述的任意一种第三网络设备，第四网络设备可以为上述实施例所述的任意一种第四网络设备，第五网络设备可以为上述实施例所述的任意一种第五网络设备，装置可以为上述实施例所述的任意一种装置，该装置可以为终端。
由于本申请实施例提供的备份服务器可用于执行上述在云数据中心中实现数据转换的方法，因此其所能获得的技术效果可参考上述方法实施例，本申请实施例在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机 可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (30)

  1. 一种释放互联网协议IP地址的方法，其特征在于，所述释放IP地址的方法包括：
    第一网络设备确定分组数据单元PDU会话锚点需要从第一用户面功能实体重定位，其中，所述第一用户面功能实体为终端的第一PDU会话的PDU会话锚点；
    所述第一网络设备确定所述终端的第一IP地址不再使用，其中，所述第一IP地址为所述终端在所述第一PDU会话中使用的IP地址；
    所述第一网络设备释放所述第一IP地址。
  2. 根据权利要求1所述的释放IP地址的方法，其特征在于，所述第一网络设备确定所述终端的第一IP地址不再使用，包括如下情形之一：
    所述第一网络设备从第二网络设备或第五网络设备接收第一通知，所述第一通知用于通知所述第一网络设备：所述终端的连接状态为空闲态；
    所述第一网络设备确定所述第一PDU会话的状态为去激活状态；
    所述第一网络设备从第三网络设备或第五网络设备接收第二通知，所述第二通知用于通知所述第一网络设备：所述第一IP地址不活跃；
    所述第一网络设备从第四网络设备或第五网络设备接收第三通知，所述第三通知用于通知所述第一网络设备：所述第一IP地址的IP连接释放。
  3. 根据权利要求1所述的释放IP地址的方法，其特征在于，在所述第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位之后，所述释放IP地址的方法还包括：
    所述第一网络设备选择第二用户面功能实体作为所述终端的第二PDU会话的PDU会话锚点；
    所述第一网络设备确定所述终端的第一IP地址不再使用，包括：
    所述第一网络设备从所述终端或第五网络设备接收第四通知，所述第四通知用于通知所述第一网络设备：所述终端完成了所述第一IP地址到第二IP地址的切换，其中，所述第二IP地址为所述终端在所述第二PDU会话中使用的IP地址。
  4. 根据权利要求1所述的释放IP地址的方法，其特征在于，在所述第一网络设备确定PDU会话锚点需要从第一用户面功能实体重定位之后，所述释放IP地址的方法还包括：
    所述第一网络设备选择第二用户面功能实体作为所述第一PDU会话的新的PDU会话锚点；
    所述第一网络设备确定所述终端的第一IP地址不再使用，包括：
    所述第一网络设备从所述终端或第五网络设备接收第四通知，所述第四通知用于通知所述第一网络设备：所述终端完成了所述第一IP地址到第二IP地址的切换，其中，所述第二IP地址为所述第一PDU会话的PDU会话锚点为所述第二用户面功能实体时，所述终端在所述第一PDU会话中使用的IP地址。
  5. 根据权利要求2所述的释放IP地址的方法，其特征在于，在所述第一网络设备从第三网络设备接收第二通知之前，所述释放IP地址的方法还包括：
    所述第一网络设备向所述第三网络设备发送第一指示，所述第一指示用于指示所 述第三网络设备检测所述第一IP地址的活跃性。
  6. 根据权利要求2所述的释放IP地址的方法，其特征在于，所述第一网络设备确定所述第一PDU会话的状态为去激活状态，包括：
    所述第一网络设备从第五网络设备接收第五通知，所述第五通知用于通知所述第一网络设备：所述第一PDU会话的状态为去激活状态；
    所述第一网络设备根据所述第五通知确定所述第一PDU会话的状态为去激活状态。
  7. 根据权利要求1-6任一项所述的释放IP地址的方法，其特征在于，在所述第一网络设备释放所述第一IP地址之前，所述释放IP地址的方法还包括：
    所述第一网络设备向所述终端发送第二指示，所述第二指示用于指示所述终端释放所述第一IP地址。
  8. 根据权利要求1-7任一项所述的释放IP地址的方法，其特征在于，在所述第一网络设备确定所述终端的第一IP地址不再使用之前，所述释放IP地址的方法还包括：
    所述第一网络设备向所述终端发送第三指示，所述第三指示用于指示所述终端进入空闲态时释放所述第一IP地址。
  9. 根据权利要求1-8任一项所述的释放IP地址的方法，其特征在于，在所述第一网络设备确定所述终端的第一IP地址不再使用之前，所述释放IP地址的方法还包括：
    所述第一网络设备将所述第一IP地址的状态标记为待释放；
    所述第一网络设备释放所述第一IP地址，包括：所述第一网络设备确定所述第一IP地址的状态为待释放，并释放所述第一IP地址。
  10. 一种释放互联网协议IP地址的方法，其特征在于，所述释放IP地址的方法包括：
    终端确定完成了从第一IP地址到第二IP地址的切换；所述终端向第一网络设备发送第四通知，所述第四通知用于通知所述第一网络设备：所述终端完成了所述第一IP地址到所述第二IP地址的切换，以使得所述第一网络设备确定所述第一IP地址不再使用并释放所述第一IP地址；其中，所述第一IP地址为所述终端在第一分组数据单元PDU会话中使用的IP地址，所述第一PDU会话的PDU会话锚点为第一用户面功能实体；所述第二IP地址为将PDU会话锚点从所述第一用户面功能实体重定位至第二用户面功能实体后，所述终端在第二PDU会话中使用的IP地址，所述第二用户面功能实体为所述第二PDU会话的PDU会话锚点；或者，所述第二IP地址为将所述第一PDU会话的PDU会话锚点从所述第一用户面功能实体重定位至第二用户面功能实体后，所述终端在所述第一PDU会话中使用的IP地址；
    或者，
    终端确定所述终端的连接状态为空闲态；所述终端与第二网络设备同步所述终端的连接状态，以使得所述第二网络设备向第一网络设备发送第一通知，所述第一通知用于通知所述第一网络设备：所述终端的连接状态为空闲态，以使得所述第一网络设备确定第一IP地址不再使用并释放所述第一IP地址，所述第一IP地址为所述终端在 第一分组数据单元PDU会话中使用的IP地址。
  11. 根据权利要求10所述的释放IP地址的方法，其特征在于，在所述终端确定所述终端的连接状态为空闲态之后，所述释放IP地址的方法还包括：
    所述终端释放所述第一IP地址。
  12. 根据权利要求10所述的释放IP地址的方法，其特征在于，在所述终端向第一网络设备发送第四通知之后，所述释放IP地址的方法还包括：
    所述终端从所述第一网络设备接收第二指示，所述第二指示用于指示所述终端释放所述第一IP地址；
    所述终端根据所述第二指示释放所述第一IP地址。
  13. 根据权利要求11所述的释放IP地址的方法，其特征在于，在所述终端释放所述第一IP地址之前，所述释放IP地址的方法还包括：
    所述终端从所述第一网络设备接收第三指示，所述第三指示用于指示所述终端进入空闲态时释放所述第一IP地址。
  14. 一种第一网络设备，其特征在于，所述第一网络设备包括：
    处理单元，用于确定分组数据单元PDU会话锚点需要从第一用户面功能实体重定位，其中，所述第一用户面功能实体为终端的第一PDU会话的PDU会话锚点；以及用于确定所述终端的第一IP地址不再使用，其中，所述第一IP地址为所述终端在所述第一PDU会话中使用的IP地址；以及用于释放所述第一IP地址。
  15. 根据权利要求14所述的第一网络设备，其特征在于，
    所述处理单元用于确定所述终端的第一IP地址不再使用，包括：
    所述处理单元用于确定所述第一PDU会话的状态为去激活状态；
    或者，
    所述第一网络设备还包括：通信单元，
    所述处理单元用于确定所述终端的第一IP地址不再使用，包括如下情形之一：
    所述处理单元用于通过所述通信单元从第二网络设备或第五网络设备接收第一通知，所述第一通知用于通知所述第一网络设备：所述终端的连接状态为空闲态；
    所述处理单元用于通过所述通信单元从第三网络设备或第五网络设备接收第二通知，所述第二通知用于通知所述第一网络设备：所述第一IP地址不活跃；
    所述处理单元用于通过所述通信单元从从第四网络设备或第五网络设备接收第三通知，所述第三通知用于通知所述第一网络设备：所述第一IP地址的IP连接释放。
  16. 根据权利要求14所述的第一网络设备，其特征在于，所述第一网络设备还包括：通信单元；
    所述处理单元，还用于选择第二用户面功能实体作为所述终端的第二PDU会话的PDU会话锚点；
    所述处理单元用于确定所述终端的第一IP地址不再使用，包括：
    所述处理单元用于通过所述通信单元从所述终端或第五网络设备接收第四通知，所述第四通知用于通知所述第一网络设备：所述终端完成了所述第一IP地址到第二IP地址的切换，其中，所述第二IP地址为所述终端在所述第二PDU会话中使用的IP地址。
  17. 根据权利要求14所述的第一网络设备，其特征在于，所述第一网络设备还包括：通信单元；
    所述处理单元，还用于选择第二用户面功能实体作为所述第一PDU会话的新的PDU会话锚点；
    所述处理单元用于确定所述终端的第一IP地址不再使用，包括：
    所述处理单元用于通过所述通信单元从所述终端或第五网络设备接收第四通知，所述第四通知用于通知所述第一网络设备：所述终端完成了所述第一IP地址到第二IP地址的切换，其中，所述第二IP地址为所述第一PDU会话的PDU会话锚点为所述第二用户面功能实体时，所述终端在所述第一PDU会话中使用的IP地址。
  18. 根据权利要求15所述的第一网络设备，其特征在于，
    所述处理单元还用于通过所述通信单元向所述第三网络设备发送第一指示，所述第一指示用于指示所述第三网络设备检测所述第一IP地址的活跃性。
  19. 根据权利要求15所述的第一网络设备，其特征在于，所述第一网络设备还包括：通信单元；所述处理单元用于确定所述第一PDU会话的状态为去激活状态，包括：
    所述处理单元用于通过所述通信单元从第五网络设备接收第五通知，所述第五通知用于通知所述第一网络设备：所述第一PDU会话的状态为去激活状态；以及用于根据所述第五通知确定所述第一PDU会话的状态为去激活状态。
  20. 根据权利要求15-19任一项所述的第一网络设备，其特征在于，
    所述处理单元还用于通过所述通信单元向所述终端发送第二指示，所述第二指示用于指示所述终端释放所述第一IP地址。
  21. 根据权利要求15-20任一项所述的第一网络设备，其特征在于，所述处理单元还用于通过所述通信单元向所述终端发送第三指示，所述第三指示用于指示所述终端进入空闲态时释放所述第一IP地址。
  22. 根据权利要求14-21任一项所述的第一网络设备，其特征在于，
    所述处理单元还用于将所述第一IP地址的状态标记为待释放；
    所述处理单元用于释放所述第一IP地址，包括：所述处理单元用于确定所述第一IP地址的状态为待释放，以及用于释放所述第一IP地址。
  23. 一种装置，其特征在于，所述装置包括：处理单元和通信单元；
    所述处理单元，用于确定完成了从第一IP地址到第二IP地址的切换；以及用于通过所述通信单元向第一网络设备发送第四通知，所述第四通知用于通知所述第一网络设备：所述装置完成了所述第一IP地址到所述第二IP地址的切换，以使得所述第一网络设备确定所述第一IP地址不再使用并释放所述第一IP地址；其中，所述第一IP地址为所述装置在第一分组数据单元PDU会话中使用的IP地址，所述第一PDU会话的PDU会话锚点为第一用户面功能实体；所述第二IP地址为将PDU会话锚点从所述第一用户面功能实体重定位至第二用户面功能实体后，所述装置在第二PDU会话中使用的IP地址，所述第二用户面功能实体为所述第二PDU会话的PDU会话锚点；或者，所述第二IP地址为将所述第一PDU会话的PDU会话锚点从所述第一用户面功能实体重定位至第二用户面功能实体后，所述装置在所述第一PDU会话中使用的IP地址；
    或者，
    所述处理单元，用于确定所述装置的连接状态为空闲态；以及用于通过所述通信单元与第二网络设备同步所述装置的连接状态，以使得所述第二网络设备向第一网络设备发送第一通知，所述第一通知用于通知所述第一网络设备：所述装置的连接状态为空闲态，以使得所述第一网络设备确定第一IP地址不再使用并释放所述第一IP地址，所述第一IP地址为所述装置在第一分组数据单元PDU会话中使用的IP地址。
  24. 根据权利要求23所述的装置，其特征在于，
    所述处理单元，还用于释放所述第一IP地址。
  25. 根据权利要求23所述的装置，其特征在于，
    所述处理单元，还用于通过所述通信单元从所述第一网络设备接收第二指示，所述第二指示用于指示所述装置释放所述第一IP地址；以及用于根据所述第二指示释放所述第一IP地址。
  26. 根据权利要求24所述的装置，其特征在于，
    所述处理单元，还用于通过所述通信单元从所述第一网络设备接收第三指示，所述第三指示用于指示所述装置进入空闲态时释放所述第一IP地址。
  27. 根据权利要求23-26任一项所述的装置，其特征在于，所述装置为终端。
  28. 一种第一网络设备，其特征在于，所述第一网络设备包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述第一网络设备实现如权利要求1-9中任意一项所述的释放IP地址的方法。
  29. 一种终端，其特征在于，所述终端包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述终端实现如权利要求10-13中任意一项所述的释放IP地址的方法。
  30. 一种通信系统，其特征在于，包括：第一网络设备和装置，其中，所述第一网络设备为权利要求14-22中任意一项所述的第一网络设备，所述装置为权利要求23-27中任意一项所述的装置；或者，所述第一网络设备为权利要求28所述的第一网络设备，所述装置为权利要求29所述的终端。
PCT/CN2018/097294 2017-07-31 2018-07-26 释放ip地址的方法、装置、网络设备及系统 WO2019024767A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18840333.1A EP3651537A4 (en) 2017-07-31 2018-07-26 METHOD AND DEVICE FOR RELEASING AN IP ADDRESS, NETWORK DEVICE AND SYSTEM
US16/775,903 US11381961B2 (en) 2017-07-31 2020-01-29 Method, apparatus, network device, and system for releasing IP address

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710643427.7 2017-07-31
CN201710643427.7A CN109548009B (zh) 2017-07-31 2017-07-31 释放ip地址的方法、装置、网络设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/775,903 Continuation US11381961B2 (en) 2017-07-31 2020-01-29 Method, apparatus, network device, and system for releasing IP address

Publications (1)

Publication Number Publication Date
WO2019024767A1 true WO2019024767A1 (zh) 2019-02-07

Family

ID=65233358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097294 WO2019024767A1 (zh) 2017-07-31 2018-07-26 释放ip地址的方法、装置、网络设备及系统

Country Status (4)

Country Link
US (1) US11381961B2 (zh)
EP (1) EP3651537A4 (zh)
CN (1) CN109548009B (zh)
WO (1) WO2019024767A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10764789B2 (en) * 2017-08-11 2020-09-01 Comcast Cable Communications, Llc Application-initiated network slices in a wireless network
US10700882B2 (en) * 2018-07-31 2020-06-30 T-Mobile Usa, Inc. GX session recovery for policy and charging rules function
CN109921898A (zh) * 2019-03-28 2019-06-21 新华三技术有限公司 IPv6无状态地址生成方法及装置
CN112105065B (zh) * 2019-06-17 2022-04-05 华为技术有限公司 通信方法和通信装置
CN110366269B (zh) * 2019-07-30 2021-03-16 中国联合网络通信集团有限公司 会话建立方法及设备
US10841974B1 (en) 2019-08-12 2020-11-17 Verizon Patent And Licensing Inc. System and method for session relocation at edge networks
CN111277470B (zh) * 2020-02-19 2022-07-26 联想(北京)有限公司 一种用户面功能切换方法、装置、系统和存储介质
CN113938353A (zh) * 2020-06-29 2022-01-14 中兴通讯股份有限公司 室内机与室外机之间的多pdn实现方法及存储介质
CN112118331B (zh) * 2020-09-22 2023-01-10 贵州电网有限责任公司 网络资源释放采集方法、装置、系统和电子设备
CN114363296B (zh) * 2020-09-30 2023-07-25 大唐移动通信设备有限公司 地址冲突检测方法、用户面网元以及控制面网元
CN113518344B (zh) * 2021-07-21 2022-05-10 荣耀终端有限公司 用户设备及其节能方法、介质
CN113938514B (zh) * 2021-09-27 2023-06-23 中盈优创资讯科技有限公司 一种基于netlfow的IPV4活跃用户统计方法及装置
KR20240033964A (ko) * 2022-09-06 2024-03-13 주식회사 케이티 이동 단말기의 세컨드 디바이스 접속 제어 방법, 코어망의 세컨드 디바이스 접속 제어 방법 및 세컨드 디바이스 접속 제어 시스템
CN115714970A (zh) * 2022-11-21 2023-02-24 中国人民解放军战略支援部队信息工程大学 5g终端移动中应用层无感的业务连续性传输方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
CN102484827A (zh) * 2009-08-25 2012-05-30 瑞典爱立信有限公司 用于流动订户的移动性锚的重定位
WO2017023346A1 (en) * 2015-07-31 2017-02-09 Intel Corporation Device, system and method using non ip-based eps bearer
CN106851856A (zh) * 2016-12-23 2017-06-13 电信科学技术研究院 一种基于移动中继的无线通信建立方法及网络设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100566988B1 (ko) * 2003-12-31 2006-04-04 엘지전자 주식회사 차세대 이동통신 시스템에서 패킷 착신호의 오디비 처리장치 및 그 방법
US7551585B2 (en) * 2004-12-03 2009-06-23 Telefonaktiebolaget Lm Ericsson (Publ) Seamless handoff for multimedia services
CN102387558B (zh) * 2007-08-21 2015-08-19 华为技术有限公司 一种演进网络切换过程中释放源网络资源的方法及系统
US8964568B2 (en) * 2010-10-22 2015-02-24 Qualcomm Incorporated Systems, methods, and apparatus for managing IP addresses and network traffic in wireless networks
KR102116411B1 (ko) * 2013-05-03 2020-05-29 삼성전자주식회사 이동 통신망에서 ｉｐ 주소 할당 방법 및 그 장치
US10419544B2 (en) * 2015-12-22 2019-09-17 Ribbon Communications Operating Company, Inc. Methods and apparatus for managing the use of IP addresses
US10667181B2 (en) * 2016-04-04 2020-05-26 Motorola Mobility Llc PDU sessions with various types of session continuity
ES2777625T3 (es) * 2016-07-04 2020-08-05 Ericsson Telefon Ab L M Técnica para reubicación de ancla de protocolo de internet
US20200059989A1 (en) * 2017-08-16 2020-02-20 Lenovo (Singapore) Pte. Ltd. Indicating a packet data unit session as unavailable

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686563A (zh) * 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
CN102484827A (zh) * 2009-08-25 2012-05-30 瑞典爱立信有限公司 用于流动订户的移动性锚的重定位
WO2017023346A1 (en) * 2015-07-31 2017-02-09 Intel Corporation Device, system and method using non ip-based eps bearer
CN106851856A (zh) * 2016-12-23 2017-06-13 电信科学技术研究院 一种基于移动中继的无线通信建立方法及网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3651537A4

Also Published As

Publication number Publication date
US11381961B2 (en) 2022-07-05
EP3651537A1 (en) 2020-05-13
CN109548009A (zh) 2019-03-29
US20200169871A1 (en) 2020-05-28
EP3651537A4 (en) 2020-07-15
CN109548009B (zh) 2021-02-23

Similar Documents

Publication Publication Date Title
WO2019024767A1 (zh) 释放ip地址的方法、装置、网络设备及系统
JP7399245B2 (ja) セッション管理のためのシステムおよび方法
US11115876B2 (en) Service continuity implementation method, device, and service continuity implementation system
EP3497970B1 (en) Mobility in 5g with handoff or cell reselection dependent on change of user-plane functionality serving area
EP3461071B1 (en) Communication control method, and related network element
JP7516448B2 (ja) 通信方法及び通信装置
US11683723B2 (en) Methods and system for offloading data traffic
US10945180B2 (en) Mobility management method, apparatus, and system
JP6910549B2 (ja) 伝送制御方法、機器、及びシステム
ES2569203T3 (es) Procedimiento y dispositivo para derivar flujo de IP durante cambio de acceso de 3GPP
US12022377B2 (en) Traffic routing towards local area data network per application function request
KR102586114B1 (ko) 다운링크 데이터의 무질서를 제어하기 위한 방법 및 장치와 컴퓨터 판독가능 매체
US12028753B2 (en) Selection of edge application server
JP2021516499A (ja) 異なるアクセスネットワーク間で移動体通信装置のハンドオーバを実行する方法およびシステム
CN111510977B (zh) 一种移动性管理方法及装置
US12101740B2 (en) Signaling delivery in a wireless network
US11641602B2 (en) Systems and methods for handover of dual connectivity user equipment
WO2018233451A1 (zh) 通信方法、装置和系统
WO2023246086A1 (zh) 一种基于物联网的无线接入、信息处理方法及网络系统
JP2024533856A (ja) 無線ルーティング方法と装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18840333

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018840333

Country of ref document: EP

Effective date: 20200204