[go: up one dir, main page]

WO2019158010A1 - Procédé, dispositif, et système de gestion de ressources - Google Patents

Procédé, dispositif, et système de gestion de ressources Download PDF

Info

Publication number
WO2019158010A1
WO2019158010A1 PCT/CN2019/074632 CN2019074632W WO2019158010A1 WO 2019158010 A1 WO2019158010 A1 WO 2019158010A1 CN 2019074632 W CN2019074632 W CN 2019074632W WO 2019158010 A1 WO2019158010 A1 WO 2019158010A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
address segment
network element
segment
allocation
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/074632
Other languages
English (en)
Chinese (zh)
Inventor
周汉
夏渊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2019158010A1 publication Critical patent/WO2019158010A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • 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
    • 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, device, and system for address resource management.
  • a packet data unit (PDU) session is managed by a session management function (SMF) network element.
  • SMF session management function
  • the above 5G network architecture is inconsistent with the actual deployment of the operator.
  • the SMF network element and the UPF network element are usually considered in consideration of the complexity of the configuration across the administrative area and the requirement of the operator to hide the network topology.
  • the deployment relationship is a many-to-many relationship.
  • the policy of binding the UPF address segment resource to the SMF is very inflexible. Different address segments cannot be dynamically allocated between SMFs. Therefore, a new address resource management strategy is needed to avoid the problem of address allocation conflicts.
  • the embodiment of the present application provides a method, a device, and a system for managing address resources, and provides a new address resource management policy to avoid conflicts in address allocation.
  • the embodiment of the present application provides the following technical solutions:
  • the first aspect provides a method for managing an address resource, where the method includes: when the address allocation network element learns that the address resource is insufficient; and sends an address segment allocation request message to the central segment management network element, the address segment allocation request message may include the data network. Name DNN.
  • the address segment allocation request message may further include an N3 interface IP address corresponding to the address segment.
  • the address allocation network element may include a session management function, for example, may be an SMF, and the address segment centralized management network element may include a user plane network element or a control plane network element.
  • the central management unit of the address segment is a user plane network element, it can be an UPF.
  • the central management unit of the address segment is a control plane network element, it can be an NRF.
  • the SMF dynamically requests the address segment resource from the UPF, and the SMF dynamically allocates the address segment resource to the UPF in a timely manner by sensing the insufficient address in the available address segment, and prepares the subsequent UE access in time.
  • the address resource is on the other hand, on the premise of avoiding the SMF address allocation conflict, the on-demand allocation of the address segment is realized.
  • This embodiment also provides a recovery mechanism for the address segment, which avoids that a large number of address segments cannot be fully utilized, thereby improving utilization efficiency.
  • the address allocation network element receives an address segment allocation response message sent by the network segment in the address segment, and the address segment allocation response message includes an address segment corresponding to the DNN.
  • the SMF may select the UPF according to the DNN information, obtain an address segment corresponding to the DNN, and the SMF allocates an IP address to the UE in the address segment.
  • the address allocation network element learns that the address resource is insufficient, and may include any one of the following: for example, the address allocation network element learns that the address segment does not exist, or the address in the address segment is exhausted or close to consumption. End, or the address occupancy ratio in the address segment exceeds the threshold.
  • the address allocation network element selects the N3 interface IP address as the local address of the N3 tunnel for the user equipment UE according to the binding relationship between the IP address of the N3 interface and the address segment.
  • the binding relationship can be expressed as follows: [N3Interface IP, UE IP section].
  • the address allocation network element sends an address segment release request message to the address segment centralized management network element, where the address segment release request includes at least one of the following information: releasing the address segment indication information, Address segment information, UE address and timing message.
  • the condition for sending the address segment release request message may include the following two situations:
  • the address allocation network element determines that the UE is the last UE in the occupied address segment, the address allocation network element sends the address segment release request message to the address segment centralized management network element;
  • the address allocation network element learns that the address utilization rate in the address segment is not high, the address allocation network element initiates a PDU session release request to the idle state UE, and instructs the idle state UE to initiate PDU session reconstruction.
  • the address allocation network element receives the address segment centralized management network element in the link establishment or link update or the network element instance status notification process to send at least one of the following information: an address segment, a TEID The segment identifier, the DNN corresponding to the address segment, and the N3 interface IP address corresponding to the initial address segment.
  • the address allocation network element selects the UPF according to the DNN, and obtains the identifier information of the UPF, and the address segment allocation request message carries the identifier information of the UPF.
  • the address allocation network element after receiving the PDU session creation or deletion request message sent by the UE, the address allocation network element sends an address segment allocation request or an address segment release message to the address segment centralized management network element.
  • the address allocation network element may send the address segment allocation request or the address segment release message to the address centralized management network element to include the DNN information carried in the PDU session creation or deletion request message sent by the UE.
  • the centralized management network element of the address segment is the control plane network element NRF: when the UE initiates the PDU session creation process, the SMF sends an available address segment request message to the NRF.
  • the request message may carry the user plane network element information selected by the SMF.
  • a second aspect provides a method for managing an address resource, where the method includes: an address segment centralized management network element receives an address segment allocation request message sent by a session management function SMF, and the address segment allocation request message may include a data network name DNN; an address segment The central management network element allocates an address segment to the SMF according to the DNN.
  • the centralized management network element of the address segment may include a user plane network element or a control plane network element. Specifically, when the central management unit of the address segment is a user plane network element, it can be an UPF. When the central management unit of the address segment is a control plane network element, it can be an NRF.
  • the address segment central management network element sends an address segment allocation response message to the SMF, and the address segment allocation response message includes an address segment.
  • the address segment allocation request further includes the identifier information of the user plane function UPF; the address segment allocation response message may further include an N3 interface IP address or a tunnel endpoint segment identifier associated with the address segment.
  • the IP address segment is uniformly managed by the NRF, and the address segment resource is dynamically requested by the SMF through the SMF.
  • the SMF allocates the address segment resource to the NRF dynamic request in time by sensing the insufficient address in the available address segment.
  • the address resources are prepared in time for the access of the UE or the subsequent UE, and on the other hand, the on-demand allocation of the address segment is realized on the premise of avoiding the conflict of the SMF address allocation.
  • the SMF can also actively trigger the UE to initiate the PDU session release process. In this way, the address of the address segment with low utilization rate is gradually recovered.
  • the centralized management network element of the address segment After no address is occupied by the UE in the address segment, the centralized management network element of the address segment will be The entire address segment is reclaimed, and the address segment can be allocated to the SMF again, and the address segment is effectively allocated between the SMFs, thereby improving the utilization efficiency of the address segment.
  • the address segment central management network element receives the address segment release request message sent by the SMF, and the address segment release request includes at least one of the following information: release address segment indication information, address segment information, and address of the UE. , timing messages.
  • the address segment centralized management network element sends an address segment release response message to the SMF, where the address segment release response message includes a release result of the to-be-recovered address segment information.
  • the central management unit of the address segment can also start a timer, and the timer is used to allocate the address segment that the address allocation network element requests to release to the address allocation network element again when the timer expires. .
  • the address segment centralized management network element sends at least one of the following information to the SMF in the link establishment or link update or the network element instance status notification process: the address segment, the TEID segment identifier, and the The DNN corresponding to the address segment and the N3 interface IP address corresponding to the initial address segment.
  • an address allocation network element is provided, the network element having the functionality to implement the method described in the first aspect above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a fourth aspect provides a centrally managed network element for an address segment, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the target When the mobility management entity is running, the processor executes the computer-executed instructions stored by the memory to cause the target mobility management entity to perform the handover method as described in any of the first aspects above.
  • a fifth aspect a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the first aspect or the second aspect or the first, Any of any possible designs in the two aspects.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the first or second aspects described above or any of the possible designs of the first and second aspects item.
  • a chip system comprising a processor, configured to support a target mobility management entity to implement functions involved in the foregoing aspects, such as a target terminal related message, and send the target terminal to the source mobility management entity.
  • the chip system further includes a memory for storing necessary program instructions and data of the target mobility management entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the technical effects brought by any one of the third aspect to the seventh aspect may refer to the technical effects brought by the first aspect or the second aspect or any possible design manner of the first and second aspects, I will not repeat them here.
  • FIG. 1 is a schematic diagram of a possible network architecture provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a possible networking scenario according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a simplified network architecture provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a resource management method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart diagram of another resource management method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart diagram of another resource management method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of another resource management method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart diagram of another resource management method according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart diagram of another resource management method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart diagram of another resource management method according to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart diagram of another resource management method according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a device according to an embodiment of the present application.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of a possible network architecture of the present application.
  • the network architecture is a 5G network architecture.
  • the network element in the 5G architecture includes an access and mobility management function (AMF) entity, an SMF entity, and a UPF entity; and may also include a policy control function (PCF) entity and a terminal (figure The terminal uses the UE as an example), the radio access network (RAN), and the unified data management (UDM) entity.
  • AMF access and mobility management function
  • PCF policy control function
  • the terminal uses the UE as an example), the radio access network (RAN), and the unified data management (UDM) entity.
  • the control plane function entity is mainly responsible for terminal authentication, application server management, and interaction with the network side control plane.
  • the application server is mainly responsible for providing service authentication and specific services for the terminal.
  • control plane function entity may be a Vehicle to Everything Communication Control Function (V2X Control Function) entity.
  • the application server can be a Vehicle to Everything Communication Application Server (V2X Application Server), which can be used for remote driving, distribution of traffic information, and the like.
  • the RAN device communicates with the AMF entity through the N2 interface, the RAN device communicates with the UPF entity through the N3 interface, the UPF entity and the SMF entity communicate through the N4 interface, and the PCF entity and the control plane control entity pass the N5 interface. Communication, the SMF entity and the PCF entity communicate through the N7 interface, the AMF entity and the UDM entity communicate through the N8 interface, the UPF entity and the UPF entity communicate through the N9 interface, and the SMF entity communicates with the UDM entity through the N10 interface.
  • the AMF entity communicates with the SMF entity through the N11 interface, and the AMF entity communicates with the PCF entity through the N15 interface.
  • the main function of the RAN is to control the user's access to the mobile communication network through wireless.
  • the RAN is part of a mobile communication system. It implements a wireless access technology. Conceptually, it resides between devices (such as mobile phones, a computer, or any remote controller) and provides connectivity to its core network.
  • the RAN device includes, but is not limited to, (g nodeB, gNB), evolved node B (eNB), radio network controller (RNC), node B (node B, NB) in 5G, Base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU), transmission point (transmitting and receiving point, TRP), a transmitting point (TP), a mobile switching center, etc., and may also include a wireless fidelity (wifi) access point (AP) or the like.
  • BSC Base station controller
  • BTS base transceiver station
  • TRP transmission point
  • TRP transmitting and receiving point
  • TP transmitting point
  • AP wireless fidelity
  • the AMF entity is responsible for access management and mobility management of the terminal. In practical applications, it includes the mobility management function in the mobility management entity (MME) in the network framework of long term evolution (LTE). And joined the access management function.
  • MME mobility management entity
  • LTE long term evolution
  • the SMF entity is responsible for session management, such as user session establishment.
  • the UPF entity is a functional network element of the user plane, and is mainly responsible for connecting to an external network, and includes related functions of an LTE serving gateway (SGW) and a public data network gateWay (PDN-GW).
  • SGW LTE serving gateway
  • PDN-GW public data network gateWay
  • the UDM entity can store the subscription information of the user, and implements a backend similar to the Home Subscriber Server (HSS) in the 4G.
  • HSS Home Subscriber Server
  • the PCF entity is used to perform policy control, similar to the Policy and Charging Rules Function (PCRF) in 4G, and is mainly responsible for policy authorization, quality of service (QoS), and generation of charging rules. And the corresponding rules are delivered to the UPF entity through the SMF entity, and the corresponding policies and rules are installed.
  • PCF Policy and Charging Rules Function
  • the terminal in the present application is a device with wireless transceiving function, which can be deployed on land, indoors or outdoors, hand-held or on-board; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example) Aircraft, balloons and satellites, etc.)
  • the terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the RAN device, the SMF entity, the UPF entity, the AMF entity, the PCF entity, and the UDM entity shown in FIG. 1 are only one name, and the name does not limit the device itself.
  • the network element or the entity corresponding to the RAN device, the SMF entity, the UPF entity, the AMF entity, the PCF entity, and the UDM entity may also be other names, which is not specifically limited in this embodiment of the present application. .
  • the name of the message mentioned in this application may also be used as a reference to other message names, and the application is not limited.
  • FIG. 2 shows a networking scenario in a 5G architecture.
  • one UPF can be attributed to multiple SMF management. Therefore, multiple SMFs can learn an internet protocol (IP) address pool supported by the UPF.
  • IP internet protocol
  • An SMF can also manage multiple UPFs.
  • One SMF can learn the IP address pool supported by multiple UPFs.
  • the scenario of the SMF and the UPF can be set up as the SMF Pool and the UPF Pool.
  • the deployment relationship between the SMF and the UPF is N:M.
  • the M and N are positive integers.
  • the address pool of the UPF is divided into multiple address segments, and different address segments are bound to different SMFs. This way of fixed binding is very inflexible.
  • different address segments cannot be dynamically provisioned between SMFs. For example, when the address segment usage rate for this UPF on a SMF is high, and the address segment usage rate for this UPF on other SMFs is low, since the address segment has been bound to the SMF, the usage rate cannot be compared.
  • the address segment on the low SMF is again allocated to the SMF with higher usage.
  • an SMF instance is added to the SMF pool. If no address pool is available in the address pool on the UPF, the new SMF instance cannot be connected.
  • UPF cannot meet the needs of the entire network SMF and UPF interconnection. Therefore, the existing technology cannot solve the problem of address allocation conflicts in the networking scenario, and a new address resource management scheme is needed to avoid multiple SMFs from performing address on the UE in a PDU session management process initiated by different UEs. A conflict occurs when assigning.
  • the embodiment of the present application provides a new address resource management solution.
  • the address pool in the data network (DN) is centrally managed, and the address segment in the address pool is dynamically allocated to the UPF connected to the DN.
  • the IP address of the UE is allocated by the SMF. That is, the address allocation network element is an SMF.
  • the SMF requests the address segment centralized management network element to allocate an available address segment, and the SMF allocates an address for the UE in the available address segment.
  • the SMF again requests the address segment centralized management network element to allocate an available address segment. After the PDU session of all the users in the available address segment is released, the SMF notifies the address segment to centrally manage the network element to recover the address segment.
  • the central management network element of the address segment may include: a user plane network element, such as an UPF; or a control plane network element, such as an NRF. If the centralized management network element of the address segment is a user plane network element, in the 5G system, the user plane network element is a UPF. That is, the SMF requests an available address segment from the UPF.
  • the control plane network element may be a network function repository function (NRF). That is, the SMF requests an available address segment from the NRF.
  • the NRF maintains and maintains whether the address segment is occupied. In this case, the UPF does not need to maintain the status of the address segment. It only needs to advertise all the address segments.
  • the NRF is a function storage function of the network element.
  • the network element function instance in the 5G network can register the services supported by the NRF to the NRF. Other network elements can query the NRF to provide the service network element function through the service discovery mechanism. Example.
  • FIG. 3 shows a simplified system structure diagram provided by an embodiment of the present application, which can be applied to the 5G network architecture shown in FIG. 1 and FIG.
  • the user plane network element may be a UPF in the 5G system. That is, the SMF requests an available address segment from the UPF. The UPF maintains a state in which the address segment is occupied.
  • the control plane network element may be an NRF. That is, the SMF requests an available address segment from the NRF. The NRF maintains and maintains whether the address segment is occupied. In this case, the UPF does not need to maintain the status of the address segment, and only needs to publish the routes of all the address segments.
  • the present application takes the network element such as the SMF entity, the UPF entity, and the NRF entity shown in FIG. 3 as an example for detailed description.
  • the UPF When the centralized management network element of the address segment is the user plane network element UPF, the UPF sends the user plane resource information to the SMF in the process of initiating link establishment or link update between the UPF and the SMF.
  • the user plane resource information may include an available address segment.
  • the user plane resource information may further include at least one of the following information:
  • the data network name (DNN) information associated with the available address segment is the segment identifier of the TEID divided by the SMF, and the UPF is the N3 interface address divided by the SMF.
  • the available address segment is a small range of available address segments, including fewer addresses. If the UPF sends the N3 interface address to the SMF in the link establishment or link update process, the UPF sends the address segment to the SMF together with the N3 interface address binding relationship.
  • the binding relationship can be expressed as [N3Interface IP, UE IP section]. The above steps are optional. You can also notify the SMF of the user plane resource information supported by the UPF in the configuration mode or the UPF NE instance status notification process.
  • the SMF After the SMF receives the foregoing resource information sent by the UPF, in the PDU session establishment procedure initiated by the UE, if the SMF selects the UPF for the UE, the SMF allocates an IP address to the UE in the available address segment. If the resource information further includes TEID segment identification information, the SMF needs to include the TEID segment identification information when the TEID is allocated to the UE. If the resource information further includes a binding relationship between the N3 interface address and the N3 interface address, the SMF allocates the IP address and the N3 interface address to the UE. .
  • the SMF When the SMF receives the UE-initiated PDU session release message, if the UE is the UE that last occupied the address in the address segment, the SMF notifies the UPF to reclaim the address segment.
  • the SMF learns that the address in the available address segment is insufficient, for example, the address segment does not exist, or the address segment resource is exhausted, or is nearly exhausted, or the address occupancy exceeds a certain threshold (more than a certain ratio, etc., such as exceeding a certain Percentage), the SMF applies to the UPF for a new available address segment.
  • the UPF allocates a new available address segment to the SMF.
  • the UPF sends the N3 interface address bound to the new available address segment to the SMF.
  • the SMF When the centralized management network element of the address segment is the control plane network element NRF: when the UE initiates the PDU session establishment procedure, the SMF sends an available address segment request message to the NRF.
  • the request message may carry the user plane network element information selected by the SMF.
  • the NRF returns the available address segment information of the user plane network element to the SMF.
  • the available address segment is a range of available small range address segments that contain fewer addresses.
  • the NRF may send the available address segment to the SMF together with the N3 interface address binding relationship.
  • the binding relationship can be expressed as [N3Interface IP, UE IP section].
  • the SMF After receiving the foregoing resource information sent by the NRF, the SMF allocates an IP address to the UE in the address segment if the SMF selects the user plane network element for the UE in the PDU session establishment process initiated by the UE.
  • the resource information further includes a binding relationship between the N3 interface address and the address segment, the SMF needs to bind the N3 interface address according to the address segment when the SMF allocates an IP address and an N3 interface address to the UE. Relationships are assigned.
  • the SMF When the SMF receives the PDU session release message initiated by the UE, if the UE is the UE that last occupied the address in the address segment, the SMF notifies the control plane network element to recover the address segment.
  • the SMF When the SMF learns that the address in the available address segment is insufficient (for example, the address segment does not exist, or the address group member is exhausted, or is nearly exhausted, or the address occupancy exceeds a certain percentage (percentage)), the SMF applies for a new available to the NRF. Address segment.
  • the NRF allocates a new available address segment to the SMF.
  • the NRF sends the N3 interface address bound to the available address segment to the SMF.
  • the address resource management scheme is described in detail from the address segment centralized management unit to the user plane network element or the control plane network element.
  • the first embodiment is described by taking a user plane network element as an address segment centralized management unit as an example.
  • the user plane network element may be an UPF.
  • the following three processes may be roughly divided into the following:
  • the link establishment or link update procedure of the connection between the UPF and the SMF divides resource information for the SMF.
  • the resource information may include an available IP address segment, and optionally, a TEID segment identifier, DNN information corresponding to the available IP address segment, and an N3 interface address bound to the available address segment. This step is optional.
  • the user plane resource information supported by the UPF can be notified to the SMF by the NRF in the configuration mode or the UPF NE instance status notification process.
  • the SMF allocates an IP address within the available address segment to the UE. If the SMF is aware that the address within the available address segment is insufficient, the SMF requests a new available address segment from the UPF in the flow.
  • Steps 1) and 3) are optional.
  • FIG. 4 shows the link establishment or link update procedure of the above 1) connection between the UPF and the SMF.
  • the UPF initiates an N4 link setup or link update request to the SMF.
  • UPF sends an N4association setup/update request message to the SMF.
  • the N4association setup/update request message carries the available address segments.
  • the available address segment contains a small range of addresses and a relatively small number of addresses.
  • the UPF may further provide the SMF with DNN information corresponding to the available address segment, the UPF is a TEID segment identifier allocated by the SMF, and N3 interface address information associated with (bind) with the available address segment.
  • the SMF After the SMF receives the above message, the SMF returns an N4association setup/update response message to the UPF.
  • the link establishment request may also be initiated by the SMF.
  • the SMF initiates an N4 link setup/update request to the UPF.
  • the specific link establishment/update process may refer to the process in which the foregoing UPF initiates an N4 link setup or update request to the SMF.
  • the main difference is that when the SMF initiates an N4 link setup or update request to the UPF, the UPF passes the N4 association setup/update response message.
  • the above information is sent to the SMF. Other processes are not described here.
  • FIG. 5 shows the above 2) UE initiated PDU Session Establish procedure. The following is specifically explained in conjunction with the flow in FIG.
  • the UE sends a PDU Session Establish Request message to the SMF, where the message carries DNN information.
  • the DNN is used to identify a DN network, and the SMF can select the UPF through the DNN.
  • the SMF receives the DNN information, and the SMF can select the UPF according to the DNN information to obtain an available address segment, and the SMF allocates an IP address to the UE in the available address segment.
  • the SMF allocates the TEID to the UE to include the TEID segment identifier.
  • the SMF selects the N3 interface IP address as the local address of the N3 tunnel when the UE establishes an N3 tunnel on the UPF. .
  • the SMF learns that the address in the available address segment is insufficient (the address segment does not exist or the address group member is exhausted or nearly exhausted or the occupancy rate exceeds a certain percentage (percentage)), the SMF carries the available address segment in the N4Session Establish request message.
  • the New IP Section Retrieve and DNN information request a new available address segment from the UPF.
  • the UPF allocates a new available address segment corresponding to the above DNN and sends it to the SMF in an N4 Session Start response message.
  • the UPF may also send the N3 interface IP address associated with the new available address segment to the SMF.
  • the UPF may also send the tunnel endpoint segment identifier to the SMF.
  • the SMF sends the IP address assigned to the UE to the UE in the PDU Session Establish response message.
  • This step may occur after the step 2, and may also occur after the step 4, which is not limited in the embodiment of the present application.
  • the SMF allocates an IP address to the subsequently accessed UE according to the obtained new available address segment.
  • For the process of assigning an address resource refer to the foregoing steps 1-3 to configure an IP address for the UE, and details are not described herein.
  • FIG. 6 shows the above 3) UE initiated PDU Session Delete procedure. The following is specifically explained in conjunction with the flow in FIG. 6.
  • the UE sends a PDU Session Delete request message to the SMF.
  • the SMF sends an N4Session Delete request message to the UPF. If the SMF is aware that the UE is the UE that occupies the last IP address in the IP Section, the SMF carries an IP Section release indication in the N4Session Delete Request message, instructing the UPF to reclaim the IP Section. The UPF can then reassign the above IP address segment to the SMF (or other SMF).
  • the SMF can also carry the timer information in the N4Session Delete request message.
  • the timer information is used to indicate that after the timer expires, the UPF may re-allocate the IP address segment to the SMF (or other SMF). That is, when the UPF receives the address segment request message sent by the SMF again, the UPF allocates the address segment to the SMF of the request address segment.
  • UPF sends an N4Session Delete response message to the SMF.
  • the above message carries the result of releasing the IP address segment.
  • the SMF returns a PDU Session Delete response message to the UE.
  • the IP address segment is collectively managed by the UPF, and the SMF dynamically requests the address segment resource from the UPF.
  • the SMF dynamically requests the address segment resource to be dynamically requested by the UPF by sensing the insufficient address in the available address segment.
  • the access of the UE prepares the address resource in time, and on the other hand, the on-demand allocation of the address segment is realized under the premise of avoiding the conflict of the SMF address allocation.
  • This embodiment also provides a recovery mechanism for the address segment, which avoids that a large number of address segments cannot be fully utilized, thereby improving utilization efficiency.
  • control plane network element may be an address segment centralized management unit as an example.
  • control plane network element may be an NRF. This embodiment may be roughly divided into three major processes:
  • the link establishment or update process between UPF and SMF may send the TEID segment identifier to the SMF.
  • This step is optional.
  • the user plane resource information supported by the UPF can be notified to the SMF by the NRF in the configuration mode or the UPF NE instance status notification process.
  • UE initiated PDU Session Establish process In the process, if the SMF learns that the address in the available address segment corresponding to the UPF selected by the UE is insufficient (the address segment does not exist, or the address resource is exhausted, or is nearly exhausted or the proportion exceeds a certain percentage (percentage )), the SMF requests the NRF for the new available address segment corresponding to the UPF selected by the UE.
  • Steps 1) and 3) are optional.
  • FIG. 7 shows a process of link establishment or link update procedure of 1) connection between UPF and SMF in Embodiment 2. As shown in Option 1 in Figure 4, the UPF initiates an N4 link setup or link update request to the SMF.
  • UPF sends an N4association setup/update request message to the SMF.
  • the N4association setup/update request message carries the TEID segment identifier assigned by the UPF to the SMF.
  • the SMF After the SMF receives the above message, the SMF returns an N4association setup/update response message to the UPF.
  • the link setup or update request may also be initiated by the SMF.
  • the SMF initiates an N4 link setup/update request to the UPF.
  • the specific link establishment or update process refer to the process in which the UPF initiates an N4 link setup/update request to the SMF in the foregoing Embodiment 2, the main difference is that when the SMF initiates an N4 link setup or update request to the UPF, the UPF passes the N4 association setup.
  • the TEID segment identification information is sent to the SMF in the response message. Other processes are not described here.
  • FIG. 11 is a diagram showing the manner in which the user plane resource information supported by the UPF is notified to the SMF by the NRF through the UPF network element instance status notification process in the first embodiment and the second embodiment.
  • the SMF subscribes to the UPF status notification to the NRF.
  • the DNN may be carried in the subscription message, that is, the SMF subscribes to the NRF to support the UPF status of one or some DNNs.
  • the UPF initiates registration with the NRF and registers its own capabilities, address pool, and supported DNNs to the NRF.
  • the NRF After receiving the registration message of the UPF, the NRF sends an NF status notification to the subscribed SMF according to the subscription message received in step 1 in this embodiment.
  • the user plane resource information of the UPF is carried in the notification message. Specifically, the UPF identification information, the DNN supported by the UPF, and the initial address segment supported by the UPF corresponding to the DNN.
  • the message further carries the TEID segment identifier allocated by the UPF for the SMF, or the N3 interface address information associated with the initial address segment.
  • FIG. 8 shows a PDU Session Establish procedure initiated by the UE in the second embodiment. The following is specifically explained in conjunction with the flow in FIG.
  • the UE sends a PDU Session Establish Request message to the SMF, where the message carries DNN information.
  • the SMF selects the UPF for the UE, and matches the available address segment corresponding to the UPF determined by the selection according to the DNN information, and the SMF allocates an IP address to the UE in the available address segment.
  • the SMF allocates the TEID to the UE to include the TEID segment identifier.
  • the SMF selects the N3 interface IP address as the local address of the N3 tunnel when the UE establishes an N3 tunnel on the UPF.
  • the SMF sends an address segment request message to the NRF, the address segment
  • the request message may carry a UPF ID, and the New IP Section retrieve and the DNN information request a new available address segment from the NRF.
  • the NRF allocates a new available address segment corresponding to the above UPF and DNN, and sends it to the SMF in the address segment request response message.
  • the NRF will also send the N3 interface IP address associated with the new available address segment above to the SMF.
  • the NRF may also send the tunnel endpoint segment identifier (ie, TEID) to the SMF.
  • TEID tunnel endpoint segment identifier
  • the SMF sends an N4Session Establish req message to the UPF. If the SMF does not assign an address to the UE in step 2, the SMF may assign an IP address to the UE in step 5. The SMF may assign an IP address to the UE according to the address segment obtained from step 4.
  • UPF returns the N4Session Establish rsp message to the SMF.
  • the SMF will send the IP address assigned to the UE to the UE in the PDU Session Establish response message.
  • the SMF allocates an IP address to the UE or a subsequently accessed UE according to the obtained new available address segment.
  • Steps 3 and 5 can occur in parallel, and the order of the messages is not limited.
  • steps 3 and 4 in the embodiment of the present application are not limited, and steps 3 and 4 may also be implemented in other messages, for example, the steps 3 and 4 are included in the UPF selection step initiated by the SMF to the NRF.
  • FIG. 9 shows a process of 3) UE-initiated PDU Session Delete in Embodiment 2. The following is specifically explained in conjunction with the flow in FIG.
  • the UE sends a PDU Session Delete request message to the SMF.
  • the SMF learns that the UE is the UE that last occupies the IP address in the IP Section, the SMF sends an IP Section release request message to the NRF, carries the UPF ID in the IP Section release request message, and needs to release the IP Section, or The IP address of the UE,
  • the SMF may further carry the timer information in the PDU Session Delete request message, where the NRF may reclaim the address segment after the timer expires.
  • the NRF can subsequently reassign the recovered IP address segment to the SMF (or other SMF). That is, when the NRF receives the address segment request message sent by the SMF again, the NRF allocates the address segment to the SMF of the request address segment.
  • the NRF sends an IP Section release response message to the SMF.
  • the above message carries the result of releasing the IP address segment.
  • the SMF sends an N4Session Delete request message to the UPF.
  • UPF sends an N4Session Delete response message to the SMF.
  • the SMF returns a PDU Session Delete response message to the UE.
  • Step 2 and step 4 can occur in parallel, and the order of messages is not limited. Steps 2 and 3 can also occur after step 6.
  • the message names of steps 2 and 3 in the embodiment of the present application are not limited.
  • the NRF uniformly manages the IP address segment, and the SMF dynamically requests the address segment resource from the NRF.
  • the SMF notifies the NRF dynamic request to allocate the address segment resource in time by sensing the insufficient address in the available address segment.
  • the access of the UE or the subsequent UE prepares the address resource in time, and on the other hand, the on-demand allocation of the address segment is realized on the premise of avoiding the conflict of the SMF address allocation.
  • This embodiment also provides a recovery mechanism for the address segment, which avoids that a large number of address segments cannot be fully utilized, thereby improving utilization efficiency.
  • the third embodiment shows a method for recovering an address resource, which can be implemented in combination with the foregoing embodiment 1 or the second embodiment.
  • the active recovery mechanism for the address segment resource shown in the third embodiment is The utilization of address resources can be further improved by combining the foregoing embodiments. Specifically, as shown in Figure 10.
  • the SMF can actively initiate the IP address segment recovery function. For example, the SMF learns that the UEs in the available address segments are in an idle state, and the SMF initiates an IP Session release procedure for the UEs, and notifies the UE to re-initiate the PDU session creation.
  • the UE After receiving the message, the UE initiates an IP Session Delete process, in which the SMF recovers the IP address.
  • the SMF When receiving the PDU session delete message of the last UE that occupies the IP address in the address segment, the SMF notifies the UPF or the NRF to reclaim the available address segment.
  • the SMF For the specific process, refer to the implementation manner of the foregoing Embodiment 1 or Embodiment 2.
  • the UE initiates a PDU Session Reestablishment, and the SMF allocates an IP address for the UE to select other available address segments.
  • the address segment request message described in all the foregoing embodiments, and the purpose of the address segment release message are respectively that the address allocation network element requests or allocates (reclaims) the address segment to the address centralized management network element, and the two embodiments of the present application
  • the name of the message is not restricted.
  • the SMF can actively trigger the UE to initiate a PDU session release process.
  • the address of the address segment with low utilization rate is gradually recovered.
  • the address is The segment centralized management network element recovers the entire address segment, and the address segment can be allocated to the SMF again, and the address segment is effectively allocated between the SMFs, thereby improving the utilization efficiency of the address segment.
  • the present application also provides a schematic diagram of a device.
  • the device may be a centrally managed network element for the address segment.
  • the device may be a UPF.
  • the device may perform the method performed by the UPF in any of the foregoing embodiments.
  • the centralized management network element of the address segment is a control plane network element, specifically, it may be an NRF, and the apparatus may perform the method performed by the NRF in any of the foregoing embodiments.
  • the device may also allocate a network element for the address.
  • the SMF is taken as an example.
  • the apparatus can also perform the method performed by the SMF in any of the embodiments described above.
  • the apparatus 1200 includes at least one processor 121, a transceiver 122, and optionally a memory 123.
  • the processor 121, the transceiver 122, and the memory 123 are connected by a communication line.
  • the processor 121 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line can include a path for communicating information between the units.
  • the transceiver 122 is configured to communicate with other devices or communication networks, and the transceiver includes a radio frequency circuit.
  • the memory 123 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device may also be an electrically erasable programmabler-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, or a disc storage ( Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • EEPROM electrically erasable programmabler-only memory
  • CD-ROM compact disc read-only memory
  • CD-ROM compact disc read-only memory
  • disc storage Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 123 may be independently present and connected to the processor 121 via a communication line.
  • the memory 123 can also be integrated with the processor.
  • the memory 123 is used to store application code for executing the solution of the present invention, and is controlled by the processor 121 for execution.
  • the processor 121 is configured to execute application code stored in the memory 123.
  • the processor 121 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1200 can include multiple processors, such as processor 121 and processor 124 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 121 and processor 124 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the function module of the present application may further divide the function modules according to the foregoing method.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation. For example, in the case where each functional module is divided by corresponding functions, FIG. 13 shows a schematic diagram of a device including a processing unit 1301 and a communication unit 1302.
  • the network element can be centrally managed for the address segment.
  • the centralized management network element of the address segment is a user plane network element, specifically, it may be an UPF, and the apparatus may perform the method performed by the UPF in any of the foregoing embodiments.
  • the centralized management network element of the address segment is a control plane network element, specifically, it may be an NRF, and the apparatus may perform the method performed by the NRF in any of the foregoing embodiments.
  • the device may also allocate a network element for the address.
  • the SMF is taken as an example.
  • the apparatus can also perform the method performed by the SMF in any of the embodiments described above.
  • the address segment centralized management network element or the address allocation network element may be presented in the form of dividing each function module corresponding to each function, or may be presented in an integrated manner to divide each functional module.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software 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 invention 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 from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)
  • embodiments of the present application can be provided as a method, apparatus (device), computer readable storage medium, or computer program product.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module” or "system.”
  • a general purpose processor may be a microprocessor.
  • the general purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in the ASIC, and the ASIC may be disposed in the terminal device. Alternatively, the processor and the storage medium may also be disposed in different components in the terminal device.
  • the above-described functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer readable medium or transmitted as one or more instructions or code to a computer readable medium.
  • Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another.
  • the storage medium can be any available media that any general purpose or special computer can access.
  • Such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general purpose or special processor.
  • any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium.
  • DSL digital subscriber line
  • the disks and discs include compact disks, laser disks, optical disks, DVDs, floppy disks, and Blu-ray disks. Disks typically replicate data magnetically, while disks typically optically replicate data with a laser. Combinations of the above may also be included in a computer readable medium.

Landscapes

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

Abstract

L'invention concerne un procédé, un dispositif, et un système de gestion de ressources d'adresse, aptes à attribuer des segments d'adresse d'après des exigences définies, de sorte à éviter un conflit d'attribution d'adresse. Le procédé comprend les étapes suivantes : un élément de réseau d'attribution d'adresse envoie un message de demande d'attribution de segments d'adresse à un élément de réseau de gestion centralisée de segments d'adresse lorsqu'il est déterminé que la ressource d'adresse est insuffisante, et l'élément de réseau de gestion centralisée de segments d'adresse attribue dynamiquement les segments d'adresse à l'élément de réseau d'attribution d'adresse en réponse au message de demande.
PCT/CN2019/074632 2018-02-13 2019-02-02 Procédé, dispositif, et système de gestion de ressources Ceased WO2019158010A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810150773.6 2018-02-13
CN201810150773.6A CN110166580B (zh) 2018-02-13 2018-02-13 资源管理的方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2019158010A1 true WO2019158010A1 (fr) 2019-08-22

Family

ID=67618888

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074632 Ceased WO2019158010A1 (fr) 2018-02-13 2019-02-02 Procédé, dispositif, et système de gestion de ressources

Country Status (2)

Country Link
CN (1) CN110166580B (fr)
WO (1) WO2019158010A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110944335A (zh) * 2019-12-12 2020-03-31 北京邮电大学 用于虚拟现实业务的资源分配方法及装置
CN114363296A (zh) * 2020-09-30 2022-04-15 大唐移动通信设备有限公司 地址冲突检测方法、用户面网元以及控制面网元
CN114726828A (zh) * 2022-05-10 2022-07-08 普联技术有限公司 Ip地址分配方法、装置、设备及存储介质
CN114900499A (zh) * 2022-04-20 2022-08-12 中国电信股份有限公司 Ip地址分配方法、装置、设备及存储介质
CN114980075A (zh) * 2022-05-05 2022-08-30 中国电信股份有限公司 地址分配方法、会话管理功能实体和通信系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114039945B (zh) * 2020-07-21 2023-03-28 中国移动通信有限公司研究院 用户ip地址分配管理方法、装置及会话管理功能实体
CN112235776B (zh) * 2020-08-31 2022-07-12 北京中科晶上科技股份有限公司 一种按需分配ip地址段的方法及ip地址统计系统
CN114363291B (zh) * 2020-09-28 2024-08-16 中国移动通信有限公司研究院 地址分配方法、装置、控制面功能实体及用户面功能实体
CN112492063B (zh) * 2020-12-09 2023-06-09 恒安嘉新（北京）科技股份公司 一种ip地址池分配、申请方法、装置、设备及介质
CN112654090B (zh) * 2020-12-10 2022-08-30 中国联合网络通信集团有限公司 资源分配方法、装置、系统和计算机可读存储介质
CN114844862B (zh) * 2021-01-15 2023-09-05 大唐移动通信设备有限公司 资源处理方法、装置及通信设备
CN115250444A (zh) * 2021-04-12 2022-10-28 华为技术有限公司 一种通信方法、装置及相关设备
CN113282410B (zh) * 2021-05-14 2023-06-23 中国联合网络通信集团有限公司 资源配置方法及装置
CN116074819A (zh) * 2021-11-02 2023-05-05 大唐移动通信设备有限公司 Pdu会话处理方法、网络设备、装置及存储介质
CN114189851A (zh) * 2021-11-30 2022-03-15 中国电信股份有限公司 Ip地址分配方法、smf以及存储介质
CN114390629B (zh) * 2022-01-21 2022-10-21 广州爱浦路网络技术有限公司 5g网络终端回程路由的控制方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685586A (zh) * 2012-09-07 2014-03-26 中兴通讯股份有限公司 一种实现地址共享的方法、装置和系统
WO2017161158A1 (fr) * 2016-03-17 2017-09-21 University Of Florida Research Foundation, Incorporated Procédé d'exploitation de diversité avec codage de réseau
CN107682473A (zh) * 2017-10-31 2018-02-09 新华三信息安全技术有限公司 一种ip地址分配方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554178B (zh) * 2015-12-31 2019-07-19 上海华为技术有限公司 一种地址分配的方法、网关及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103685586A (zh) * 2012-09-07 2014-03-26 中兴通讯股份有限公司 一种实现地址共享的方法、装置和系统
WO2017161158A1 (fr) * 2016-03-17 2017-09-21 University Of Florida Research Foundation, Incorporated Procédé d'exploitation de diversité avec codage de réseau
CN107682473A (zh) * 2017-10-31 2018-02-09 新华三信息安全技术有限公司 一种ip地址分配方法及装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110944335A (zh) * 2019-12-12 2020-03-31 北京邮电大学 用于虚拟现实业务的资源分配方法及装置
CN110944335B (zh) * 2019-12-12 2022-04-12 北京邮电大学 用于虚拟现实业务的资源分配方法及装置
CN114363296A (zh) * 2020-09-30 2022-04-15 大唐移动通信设备有限公司 地址冲突检测方法、用户面网元以及控制面网元
CN114363296B (zh) * 2020-09-30 2023-07-25 大唐移动通信设备有限公司 地址冲突检测方法、用户面网元以及控制面网元
CN114900499A (zh) * 2022-04-20 2022-08-12 中国电信股份有限公司 Ip地址分配方法、装置、设备及存储介质
CN114900499B (zh) * 2022-04-20 2023-10-03 中国电信股份有限公司 Ip地址分配方法、装置、设备及存储介质
CN114980075A (zh) * 2022-05-05 2022-08-30 中国电信股份有限公司 地址分配方法、会话管理功能实体和通信系统
CN114726828A (zh) * 2022-05-10 2022-07-08 普联技术有限公司 Ip地址分配方法、装置、设备及存储介质
CN114726828B (zh) * 2022-05-10 2023-08-08 普联技术有限公司 Ip地址分配方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN110166580A (zh) 2019-08-23
CN110166580B (zh) 2021-12-24

Similar Documents

Publication Publication Date Title
WO2019158010A1 (fr) Procédé, dispositif, et système de gestion de ressources
CN110662270B (zh) 通信方法及装置
EP3732846B1 (fr) Contrôle de qualité de service (qos) dans l'informatique de périphérie mobile (mec)
CN109792651B (zh) 一种通信方法及设备
CN110049070B (zh) 事件通知方法及相关设备
CN110830543B (zh) 通信方法和通信设备
CN110012437B (zh) 一种组播报文的发送方法、装置及系统
JP7389225B2 (ja) セキュリティ保護モードを決定するための方法および装置
EP3742785B1 (fr) Procédé et dispositif de gestion de session
WO2018153253A1 (fr) Procédé, appareil et système de sélection d'une entité fonctionnelle de gestion de session
US12267734B2 (en) Communication method and communications apparatus
WO2022001761A1 (fr) Procédé et appareil de communication
WO2019196811A1 (fr) Procédé de communication, et appareil associé
CN110662308A (zh) 一种通信方法及装置
WO2019134648A1 (fr) Procédé et dispositif de mise en œuvre pour une migration de ressources de plan de commande, et entité de fonction de réseau
WO2019137125A1 (fr) Procédé, dispositif et système de gestion de session
WO2023024910A1 (fr) Procédé et appareil de communication
CN114731723A (zh) 一种通信方法及装置
WO2019223702A1 (fr) Procédé, appareil, et système de gestion de session pdu
WO2020034971A1 (fr) Procédé et appareil d'attribution d'un identifiant ebi
CN115348665A (zh) 一种通信方法、设备及系统
WO2018233451A1 (fr) Procédé, appareil et système de communication
WO2022033543A1 (fr) Procédé de communication de relais, et appareil de communication
CN111510977A (zh) 一种移动性管理方法及装置
WO2023273767A1 (fr) Procédé de communication, entité à fonction de gestion d'accès et de mobilité, dispositif de réseau d'accès radio et support d'enregistrement lisible par ordinateur

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: 19754472

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19754472

Country of ref document: EP

Kind code of ref document: A1