WO2024114539A1 - 地址分配方法、装置和用户平面功能实体 - Google Patents

地址分配方法、装置和用户平面功能实体 Download PDF

Info

Publication number
WO2024114539A1
WO2024114539A1 PCT/CN2023/134079 CN2023134079W WO2024114539A1 WO 2024114539 A1 WO2024114539 A1 WO 2024114539A1 CN 2023134079 W CN2023134079 W CN 2023134079W WO 2024114539 A1 WO2024114539 A1 WO 2024114539A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
user plane
plane function
locator
private network
Prior art date
Application number
PCT/CN2023/134079
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 中兴通讯股份有限公司
Publication of WO2024114539A1 publication Critical patent/WO2024114539A1/zh

Links

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
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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
    • 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/5046—Resolving address allocation conflicts; Testing of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to an address allocation method, device and user plane functional entity.
  • DNN Data Network Name
  • the Session Management Function usually randomly assigns an IP address to the UE accessing the session.
  • the IP address assigned by this allocation method often conflicts with the IP address corresponding to the private network Universal Resource Locator (URL).
  • the embodiments of the present application provide an address allocation method, device and electronic device, which can solve the problem of conflict between the allocated IP address and the IP address corresponding to the private network URL in the related art.
  • an embodiment of the present application provides an address allocation method, the method comprising: a user plane function receives a session policy message sent by a session management function, the session policy message carrying a private network uniform resource locator; the user plane function obtains a first IP address according to the session policy message. address, the first IP address is an IP address corresponding to the private network uniform resource locator; the user plane function allocates a second IP address according to the first IP address, wherein the second IP address is different from the first IP address.
  • an embodiment of the present application provides an address allocation method, the method comprising: a session management function receives a session policy message sent by a policy control function, the session policy message carrying a private network uniform resource locator; the session management function sends the session policy message to a user plane function, so that the user plane function obtains a first IP address according to the session policy message, the first IP address being an IP address corresponding to the private network uniform resource locator; and allocating a second IP address according to the first IP address, wherein the second IP address is different from the first IP address.
  • an embodiment of the present application provides an address allocation device, which includes: a receiving module, used to receive a session policy message sent by a session management function, the session policy message carrying a private network uniform resource locator; an acquisition module, used to acquire a first IP address according to the session policy message, the first IP address being an IP address corresponding to the private network uniform resource locator; an allocation module, used to allocate a second IP address according to the first IP address, wherein the second IP address is different from the first IP address.
  • an embodiment of the present application provides a user plane functional entity, which includes a processor and a memory, wherein the memory stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
  • an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.
  • an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.
  • an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the first aspect or the second aspect. The method described in the aspect.
  • FIG1 is a functional principle diagram of a network-side private network DNN session provided in the related art
  • FIG2 is a schematic diagram of a service flow provided on the basis of FIG1;
  • FIG3 is a network topology diagram provided in an embodiment of the present application.
  • FIG4 is a flow chart of an address allocation method provided in an embodiment of the present application.
  • FIG5 is a flow chart of another address allocation method provided in an embodiment of the present application.
  • FIG6 is a flow chart of another address allocation method provided in an embodiment of the present application.
  • FIG7 is a flow chart of another address allocation method provided in an embodiment of the present application.
  • FIG8 is an interactive schematic diagram of an address allocation process provided in an embodiment of the present application.
  • FIG9 is an interactive schematic diagram of another address allocation process provided in an embodiment of the present application.
  • FIG10 is a structural block diagram of an address allocation device provided in an embodiment of the present application.
  • FIG. 11 is a structural block diagram of a user plane functional entity provided in an embodiment of the present application.
  • first, second, etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first”, “second”, etc. are generally of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • the "and/or” in the specification and claims represents at least one of the connected objects, and the character “and/or” means at least one of the connected objects. “/” generally indicates that the previous and next related objects are in an “or” relationship.
  • FIG1 is a functional schematic diagram of a network-side private network DNN session provided in the related art.
  • the Policy Control Function (PCF) 1 can transmit the specified URL (i.e., service URL, which can be in IP format, Fully Qualified Domain Name (FQDN) format, etc.), the private network access point name (APN), and slices and other DNN session policy information to the SMF1 network element on the N7 interface based on the contract information.
  • SMF1 can send the received private network DNN rules to the public network user plane management function (UPF) 1 through the signaling of the N4 interface.
  • URL i.e., service URL, which can be in IP format, Fully Qualified Domain Name (FQDN) format, etc.
  • API Private network access point name
  • UPF public network user plane management function
  • the public network UPF1 can trigger the detection report to the public network SMF1, and the public network SMF1 can trigger the establishment of a private network DNN session and select SMF2 as the anchor point SMF of the private network session.
  • SMF1 can allocate UE IP1 for public network sessions
  • SMF2 can allocate UE IP2 for private network sessions.
  • the uplink message can be addressed IP1>IP2 on the public network UPF1
  • the downlink message can be addressed IP2>IP1 on the public network UPF1.
  • FIG2 is a schematic diagram of a service flow provided on the basis of FIG1.
  • FIG2 includes two service flows, namely a public network service flow and a private network service flow.
  • the dotted line in FIG2 can be used to indicate signaling, and the solid line can be used to indicate data.
  • the public network service flow involves IP1, IP3 and IP4, where IP1, IP3 and IP4 are all public network IP addresses.
  • the UE side involves two addresses, IP1 and IP4, and the public network server side involves two addresses, IP3 and IP4. There is no IP conflict on either the UE side or the public network server side.
  • the private network service flow involves IP1, IP2 and IP5 (IP addresses corresponding to the private network URL), among which IP1, IP2 and IP5 are all private network IP addresses.
  • IP1, IP2 and IP5 are all private network IP addresses.
  • the UE side involves two addresses, IP1 and IP5;
  • the private network server side involves two addresses, IP2 and IP5. Since IP1 on the UE side is randomly assigned by SMF1, IP1 and IP5 may conflict. Once IP1 and IP5 conflict, the UE will fail to send the uplink message to the private network.
  • the embodiment of the present application creatively proposes an address allocation method, device and user plane functional entity, which can effectively avoid the IP address of the target UE from being inconsistent with the IP address corresponding to the private network URL. There is a conflict.
  • FIG3 is a network topology diagram provided by an embodiment of the present application.
  • the network topology may include a target UE, a radio access network (RAN), an access mobility management function (AMF) 1, a network repository function (NRF) 1, PCF1, a public network SMF1, a private network SMF2, a public network UPF1, a private network UPF2, a private network, a large network (public network), etc.
  • the left side of the dotted line in FIG3 may indicate the private network roaming location corresponding to the target UE
  • the right side of the dotted line may indicate the private network belonging location corresponding to the target UE.
  • FIG3 corresponds to a scenario in which the target UE accesses the private network roaming location.
  • PCF1 may send the private network DNN session policy to the public network SMF1.
  • the public network SMF1 may send the received private network DNN session policy to the public network UPF1 through the N4 interface. Therefore, the public network UPF1 can actively perform DNS learning on the service URL in the FQDN format received in the private network DNN session policy, and allocate an IP address to the target UE to avoid conflicts between the IP address of the target UE and the IP address corresponding to the service URL in the FQDN format.
  • the public network UPF1 performing active DNS learning may include: when the service URL sent by PCF1 is in FQDN format, the public network UPF1 actively learns the IP address corresponding to the service URL in FQDN format through a DNS request message.
  • the way in which the public network UPF1 allocates addresses may be the address allocation method recommended in the 16th public version protocol of the 3rd Generation Partnership Project (3GPP).
  • 3GPP 3rd Generation Partnership Project
  • the address allocation method provided in the embodiment of the present application can obtain the IP address corresponding to the service URL in FQDN format through active DNS learning of the public network UPF1, and allocate a non-conflicting IP address to the target UE according to the IP address corresponding to the service URL, so that the target UE can access the private network normally.
  • the address allocation method described above is only an example of the present application and cannot be regarded as a limitation of the present application.
  • the public network UPF1 can obtain the IP address corresponding to the service URL in a variety of ways, and the address allocation method provided in the embodiment of the present application is not only applicable to the service URL in FQDN format, but also to the service URL in IP format. They will be introduced one by one later.
  • FIG4 is a flow chart of an address allocation method provided in an embodiment of the present application. As shown in FIG4, the address allocation method provided in an embodiment of the present application may include the following steps:
  • Step 410 the user plane function receives a session policy message sent by the session management function, wherein the session policy message carries a private network uniform resource locator;
  • both SMF and UPF can support the establishment of network-side private network sessions locally or roaming in a private network.
  • SMF can be a public network SMF, such as the public network SMF1 shown in Figure 3.
  • UPF can be a public network UPF, such as the public network UPF1 shown in Figure 3.
  • the UPF may receive a session policy message sent by the SMF, wherein the session policy message may be a message that the PCF actively sends to the SMF or returns to the SMF after receiving a request from the SMF.
  • the session policy message may carry a private network DNN policy.
  • the private network DNN policy may include a private network URL.
  • the private network DNN policy may also include at least one of a private network DNN and a private network slice.
  • the private network URL may be a URL in FQDN format, a URL in IP format, or a URL in subdomain format.
  • Step 420 The user plane function obtains a first IP address according to the session policy message, where the first IP address is an IP address corresponding to the private network uniform resource locator;
  • the first IP address may be at least one IP address or an IP address segment, wherein the at least one IP address may be one IP address, such as 119.147.50.92, or multiple IP addresses, such as 180.97.33.107 and 180.97.33.108.
  • the UPF may first extract the locator in the target format from the session policy message, and then The first IP address corresponding to the locator in the target format is obtained by using a DNS server or a preset mapping table, wherein the mapping table may store the correspondence between the locator in the target format and the IP address.
  • a target format e.g., FQDN format
  • the UPF can directly obtain the first IP address corresponding to the locator in IP format from the session policy message.
  • Step 430 The user plane function allocates a second IP address based on the first IP address, wherein the second IP address is different from the first IP address.
  • the second IP address may be an address assigned by the UPF to the target UE in the network-side private network session.
  • the second IP address being different from the first IP address may indicate that the second IP address is different from any address in the first IP address, that is, there is no conflict between the second IP address and the first IP address, and the first IP address does not contain an address that is the same as the second IP address.
  • UPF can allocate a second IP address that is different from the first IP address in at least two of the following ways.
  • the first way UPF can first determine the address in the pre-configured IP list that conflicts with the first IP address, and remove or block the conflicting address from the pre-configured IP list, and then select an IP address from the remaining IP list as the second IP address.
  • the second way UPF can randomly select an IP address from the pre-configured IP address list, and determine whether the selected IP address conflicts with the first IP address. If there is no conflict, the selected IP address is used as the second IP address. If there is a conflict, continue to select until the randomly selected IP address does not conflict with the first IP address. Finally, the randomly selected IP address that does not conflict with the first IP address is used as the second IP address.
  • the address allocation method provided in the embodiment of the present application can obtain a first IP address corresponding to a private network uniform resource locator according to a session policy message, and further enable a user plane function to specifically allocate a second IP address different from the first IP address according to the first IP address, thereby ensuring that there is no conflict between the first IP address and the second IP address during the session, and thereby enabling the device corresponding to the second IP address to access the private network normally.
  • the address allocation method for avoiding address conflicts provided in the embodiment of the present application is not limited to private network URLs in IP format, but is also applicable to private network URLs in domain name format.
  • the private network URL can enhance the experience of public network users accessing the private network.
  • this application can also further promote the popularization of the network-side private network DNN session function in government, enterprise and campus intranets.
  • an address conflict detection can be performed first, and then it can be determined whether it is necessary to re-allocate an IP address to the target UE.
  • the address allocation method before the user plane function in step 430 allocates the second IP address according to the first IP address, the address allocation method also includes: the user plane function obtains a third IP address; wherein the third IP address is an IP address that has been allocated to the target UE; the user plane function allocates the second IP address according to the first IP address, including: in the case where the first IP address and the third IP address conflict, the second IP address is allocated.
  • the target UE in the case where an IP address has been allocated to the target UE, it can be further determined whether the allocated IP address conflicts with the first IP address, and in the case of a conflict, the IP address is re-allocated to the target UE, so as to ensure that the IP address of the target UE during the private network session on the network side does not conflict with the IP address corresponding to the private network URL, so that the target UE can access the private network normally.
  • the third IP address can be the IP address of the target UE in the public network service flow, for example, when a user who has not signed up for a private network service goes online through the target UE, the SMF or UPF allocates the address to the target UE.
  • the conflict between the first IP address and the third IP address can indicate that there is an address in the first IP address that is the same as the third IP address.
  • the third IP address can be directly used as the second IP address without reallocation.
  • the private network URL can be a locator in various formats. Since the methods for obtaining the first IP address are different for locators in different formats, the specific process of obtaining the first IP address according to the private network URLs in different formats will be further described later in this application.
  • the private network uniform resource locator is a locator in IP format
  • the user platform in step 420 The user plane function obtains the first IP address according to the session policy message, which may include: the user plane function extracts the locator in the IP format from the session policy message, and uses the locator in the IP format as the first IP address. In this way, the UPF can quickly obtain the first IP address without adding additional signaling interaction, which is conducive to improving address allocation efficiency.
  • the second IP address can be reported to other network elements in the network side private network session.
  • the address allocation method also includes: the user plane function sends a target message to the session management function, and the target message carries the second IP address.
  • the UPF can report the allocated second IP address to the SMF, so that the SMF can further transmit the IP address of the target UE to other network elements to ensure normal transmission of signaling.
  • the UPF After the UPF allocates the second IP address, it can send a target message carrying the second IP address to the SMF. At the same time, after receiving the target message, the SMF can send a session policy update message to the PCF, wherein the session policy update message carries the second IP address. After receiving the session policy update message, the PCF can return a successful response to the SMF.
  • FIG5 is a flow chart of another address allocation method provided in an embodiment of the present application. As shown in FIG5, the address allocation method provided in an embodiment of the present application includes the following steps:
  • Step 510 the user plane function receives a session policy message sent by the session management function, wherein the session policy message carries a private network uniform resource locator;
  • the private network uniform resource locator is a locator in a target format.
  • the target format may be a FQDN format.
  • Step 520 When the user plane function detects that the private network uniform resource locator in the session policy message is a locator in a target format, the user plane function sends an address resolution request to a domain name server, where the address resolution request carries the locator in the target format;
  • a Domain Name Server may be a server for converting a domain name into a corresponding IP address.
  • An address resolution request may be used to instruct the DNS server to resolve a locator in a target format into a corresponding IP address.
  • the UPF can send an address resolution request carrying the locator in the target format to the DNS.
  • the domain name server can resolve the acquired locator in the target format and determine its corresponding IP address.
  • the DNS server address can be configured on the UPF so that after the UPF detects the locator in the target format, it can actively send an address resolution request to the DNS server corresponding to the address.
  • Step 530 the user plane function receives the first IP address sent by the domain name server
  • the first IP address is an IP address corresponding to the locator of the target format
  • the first IP address resolved by the DNS server may be a single IP address, multiple IP addresses, or an IP address segment. After the UPF receives the first IP address sent by the DNS server, it may perform subsequent steps.
  • Step 540 The user plane function allocates a second IP address based on the first IP address, wherein the second IP address is different from the first IP address.
  • step 430 The specific method of allocating the second IP address can refer to the above description of step 430, which will not be described in detail here.
  • the address allocation method provided in the embodiment of the present application can use the DNS server to parse the locator of the target format and accurately obtain the first IP address corresponding to the locator of the target format, which is conducive to the targeted allocation of a second IP address different from the first IP address according to the first IP address, thereby ensuring that there is no conflict between the first IP address and the second IP address during the session, and further allowing the device corresponding to the second IP address to access the private network normally.
  • the address allocation method also includes: the user plane function records the correspondence between the target format locator and the first IP address in a target mapping table. In this way, by learning the correspondence between the target format locator and the first IP address, a target mapping table is generated, and the UPF can subsequently directly use the target format locator to obtain the first IP address.
  • the locator mapping table obtains the IP address corresponding to the locator of some target formats, reduces signaling interaction, and can improve the address allocation efficiency to a certain extent.
  • FIG6 is a flow chart of another address allocation method provided in an embodiment of the present application. As shown in FIG6 , the address allocation method provided in an embodiment of the present application includes the following steps:
  • Step 610 the user plane function receives a session policy message sent by the session management function, wherein the session policy message carries a private network uniform resource locator;
  • the private network uniform resource locator is a locator in a target format.
  • the target format may be a FQDN format.
  • Step 620 the user plane function searches a target mapping table for an IP address corresponding to the locator of the target format; wherein the target mapping table is used to store a correspondence between a uniform resource locator and an IP address;
  • the URL in the target mapping table may include at least one locator in a target format.
  • the corresponding relationship between the URL and the IP address in the target mapping table may be a one-to-one corresponding relationship or a one-to-many corresponding relationship.
  • the UPF may use the locator of the target format as an index to determine whether there is an IP address corresponding to the locator of the target format in the target mapping table.
  • Step 630 When the user plane function obtains an IP address corresponding to the locator of the target format through query, the user plane function determines the IP address obtained through query as the first IP address;
  • the UPF can query and obtain the corresponding IP address.
  • UPF can directly use the target mapping table to obtain the first IP address.
  • Step 640 The user plane function allocates a second IP address based on the first IP address, wherein the second IP address is different from the first IP address.
  • the address allocation method provided in the embodiment of the present application queries the IP address corresponding to the locator of the target format in the target mapping table, so that the UPF can preferentially use the target mapping table for address resolution, thereby avoiding sending unnecessary address resolution requests to the DNS server, and further reducing the signaling interaction between the UPF and the DNS server, thereby improving the address allocation efficiency to a certain extent.
  • the obtaining of the first IP address according to the session policy message further includes: the user plane function sending an address resolution request to a domain name server when the IP address corresponding to the locator of the target format is not queried; the address resolution request carries the locator of the target format; the user plane function receives the first IP address sent by the domain name server.
  • the DNS server can continue to be used to resolve the locator of the target format, ensuring that the UPF can accurately obtain the first IP address corresponding to the locator of the target format.
  • the UPF cannot query and obtain the IP address corresponding to the locator of the target format.
  • the UPF may continue to send an address resolution request carrying the locator in the target format to the DNS, and receive the first IP address corresponding to the locator in the target format from the DNS server.
  • FIG7 is a flow chart of another address allocation method provided in an embodiment of the present application. As shown in FIG7 , the address allocation method provided in an embodiment of the present application includes the following steps:
  • Step 710 the session management function receives a session policy message sent by the policy control function, wherein the session policy message carries a private network uniform resource locator;
  • the session policy message may be a message that the PCF actively sends to the SMF or that is returned to the SMF after receiving a request from the SMF.
  • the session policy message may carry a private network DNN policy.
  • the private network DNN policy may include a private network URL.
  • the private network DNN policy may also include at least one of a private network DNN and a private network slice.
  • the private network URL may be a URL in FQDN format, a URL in IP format, or a URL in subdomain format.
  • Step 720 The session management function sends the session policy message to the user plane function, so that the user plane function obtains a first IP address according to the session policy message, where the first IP address is an IP address corresponding to the private network uniform resource locator; and allocates a second IP address according to the first IP address, where the second IP address is different from the first IP address.
  • the first IP address may be at least one IP address or an IP address segment.
  • the UPF may first extract the locator in the target format from the session policy message, and then use the DNS server or a preset mapping table to obtain the first IP address corresponding to the locator in the target format.
  • the mapping table may store the correspondence between the locator in the target format and the IP address.
  • the UPF can directly obtain the first IP address corresponding to the locator in IP format from the session policy message.
  • the second IP address may be an address assigned by the UPF to the target UE in the network-side private network session.
  • the second IP address being different from the first IP address may indicate that the second IP address is different from any address in the first IP address, that is, there is no conflict between the second IP address and the first IP address, and the first IP address does not contain an address that is the same as the second IP address.
  • the address allocation method provided in the embodiment of the present application enables the UPF to obtain a first IP address corresponding to the private network uniform resource locator according to a session policy message, and further allocates a second IP address different from the first IP address in a targeted manner based on the first IP address. This can ensure that there is no conflict between the first IP address and the second IP address during the session, so that the device corresponding to the second IP address can access the private network normally.
  • the address allocation method further comprises: the session management function sends a request message to the user plane function, the request message being used to request the user plane function to allocate an IP address.
  • the IP address can be allocated by the UPF based on the request message sent by the SMF.
  • the second IP address can be passed to other network elements in the network side private network session.
  • the address allocation method further includes: the session management function receives the target message of the user plane function, the target message carries the second IP address; the session management function sends a session policy update message to the policy control function, the session policy update message carries the second IP address.
  • the SMF can receive the second IP address sent by the UPF.
  • the target UE's IP address is then transmitted to other network elements in the private network session on the network side to ensure normal signaling transmission.
  • SMF can receive the target message carrying the second IP address returned by UPF, and send a session policy update message to PCF, wherein the session policy update message carries the second IP address. After receiving the session policy update message, PCF can return a successful response to SMF.
  • FIG8 is an interactive schematic diagram of an address allocation process provided in an embodiment of the present application.
  • FIG8 is directed to a scenario in which a user who has signed a contract for a private network goes online for a large network session.
  • a private network URL service URL
  • the address allocation process in an embodiment of the present application may include the following steps:
  • Step 801 The user who signed up for the private network initiates a session establishment request, and AMF sends a session establishment request message to SMF1 (corresponding to the session management function above);
  • a user who has signed a contract for a private network can initiate a session establishment request through the target UE.
  • Step 802 SMF1 sends a request for obtaining session policy information (corresponding to the above session policy message) to PCF;
  • Step 803 PCF returns a response message to SMF1, wherein the response message carries session policy information, and the session policy information includes the private network DNN policy (private network DNN, private network slice, private network service URL, and the private network service URL is in FQDN format) signed by the user.
  • the response message carries session policy information
  • the session policy information includes the private network DNN policy (private network DNN, private network slice, private network service URL, and the private network service URL is in FQDN format) signed by the user.
  • Step 804 SMF1 sends the private network DNN policy to UPF1 (corresponding to the user plane function above) through the Packet Forwarding Control Protocol (PFCP) message, and requests UPF1 to allocate UE IP at the same time;
  • PFCP Packet Forwarding Control Protocol
  • Step 805 UPF1 detects that the service URL (corresponding to the above private network URL) in the private network DNN session policy is in FQDN format, and actively sends a request to the DNS server to request resolution of the IP address corresponding to the FQDN of the service URL;
  • Step 806 the DNS server returns the IP address corresponding to the FQDN of the service URL to UPF1 (corresponding to the first IP address above);
  • Step 807 UPF1 allocates UE IP addresses, performs address conflict prevention during allocation, allocates addresses that do not conflict with the IP corresponding to the FQDN (corresponding to the second IP above), and returns a message of successful session policy installation to SMF1, and returns the successfully allocated UE IP to SMF1;
  • Step 808 SMF1 sends a session policy update message to PCF, carrying the allocated UE IP;
  • Step 809 PCF returns a success response to SMF1;
  • Step 810 SMF1 returns a session establishment success response message to AMF1.
  • the address allocation method provided in the embodiment of the present application can, on the one hand, realize the allocation of an IP address to the target UE by the UPF, and on the other hand, can use the DNS server to parse the locator in the FQDN format to accurately obtain the IP address corresponding to the locator in the FQDN format, so that the UPF can specifically allocate a non-conflicting IP address to the target UE according to the IP address corresponding to the locator in the FQDN format, thereby ensuring that the target UE can access the private network normally after the IP address is allocated.
  • FIG9 is an interactive diagram of another address allocation process provided in an embodiment of the present application.
  • FIG9 is directed to a scenario in which a user who has not signed a contract for a private network logs on to a large network session, and the user signs a contract for a private network service, and the PCF actively issues a private network DNN policy.
  • a private network URL service URL
  • the address allocation process in an embodiment of the present application may include the following steps:
  • Step 901 After the user signs up for the private network DNN service, PCF proactively sends the private network DNN policy (corresponding to the private network session policy message above) to SMF1, carrying the service URL in FQDN format.
  • PCF proactively sends the private network DNN policy (corresponding to the private network session policy message above) to SMF1, carrying the service URL in FQDN format.
  • Step 902 the big network session SMF1 responds successfully
  • Step 903 SMF1 sends the private network DNN policy to UPF1 through the PFCP message;
  • Step 904 UPF1 detects that the service URL (corresponding to the above private network URL) in the private network DNN session policy is in FQDN format, and actively sends a request to the DNS server to request resolution of the IP address corresponding to the FQDN of the service URL;
  • Step 905 the DNS server returns the IP address corresponding to the FQDN of the service URL to UPF1 (corresponding to the first IP address above);
  • Step 906 UPF1 performs address conflict detection. If the IP corresponding to the FQDN of the service URL conflicts with the current UE IP address of the session (corresponding to the third IP address above), the UE IP address reallocation is initiated, and the UE IP that does not conflict with the IP address corresponding to the FQDN (corresponding to the second IP address above) is reallocated, and the reallocated UE IP is returned to SMF1.
  • Step 907 SMF1 sends a session policy update message to PCF, wherein the session policy update message carries the reallocated UE IP;
  • Step 908 PCF returns a success response to SMF1.
  • the address allocation method provided in the embodiment of the present application can, when an IP address has been allocated to the target UE, further determine whether the allocated IP address conflicts with the IP address corresponding to the private network URL, and if there is a conflict, re-allocate a different IP address to the target UE, thereby ensuring that there is no conflict between the IP address of the target UE and the IP address corresponding to the private network URL during the private network session on the network side, so that the target UE can access the private network normally.
  • Fig. 10 is a structural block diagram of an address allocation device provided in an embodiment of the present application.
  • the address allocation device 1000 provided in an embodiment of the present application includes: a receiving module 1010 , an acquiring module 1020 and an allocating module 1030 .
  • the receiving module 1010 is used to receive a session policy message sent by a session management function, wherein the session policy message carries a private network uniform resource locator;
  • the acquisition module 1020 is used to acquire a first IP address according to the session policy message, where the first IP address is an IP address corresponding to the private network uniform resource locator;
  • the allocation module 1030 is configured to allocate a second IP address according to the first IP address, wherein the second IP address is different from the first IP address.
  • the address allocation device provided in the embodiment of the present application can obtain a first IP address corresponding to a private network uniform resource locator according to a session policy message, and further allocate a second IP address different from the first IP address in a targeted manner according to the first IP address, thereby ensuring that there is no conflict between the first IP address and the second IP address during the session, and thereby enabling the device corresponding to the second IP address to access the private network normally.
  • the acquisition module 1020 before allocating the second IP address according to the first IP address, is also used to: acquire a third IP address; wherein the third IP address is an IP address allocated to the target UE; in the process of allocating the second IP address according to the first IP address, the allocation module 1030 is specifically used to: allocate the second IP address when there is a conflict between the first IP address and the third IP address.
  • the private network uniform resource locator is a locator in a target format; in the process of obtaining the first IP address according to the session policy message, the acquisition module 1020 is specifically used to: when it is detected that the private network uniform resource locator in the session policy message is a locator in a target format, send an address resolution request to a domain name server, the address resolution request carrying the locator in the target format; and receive the first IP address sent by the domain name server.
  • the address allocation device 1000 also includes a storage module, and after receiving the first IP address sent by the domain name server, the storage module is used to record the correspondence between the locator of the target format and the first IP address in a target mapping table.
  • the private network uniform resource locator is a locator in a target format; in the process of obtaining the first IP address according to the session policy message, the acquisition module 1020 is specifically used to: query the IP address corresponding to the locator in the target format in the target mapping table; wherein the target mapping table is used to store the correspondence between the uniform resource locator and the IP address; in the case where the IP address corresponding to the locator in the target format is queried, the IP address obtained by the query is determined as the first IP address.
  • the acquisition module 1020 in the process of obtaining the first IP address according to the session policy message, is specifically used to: send an address resolution request to a domain name server when no IP address corresponding to the locator of the target format is queried; the address resolution request carries the locator of the target format; and receive the first IP address sent by the domain name server.
  • the target format is a fully qualified domain name format.
  • the private network uniform resource locator is a locator in IP format
  • the acquisition module 1020 in the process of the user plane function obtaining the first IP address according to the session policy message, is specifically used to: extract the locator in IP format from the session policy message, and use the locator in IP format as the first IP address.
  • the address allocation device 1000 further includes a sending module, and after allocating the second IP address according to the first IP address, the sending module is used to send a target message to the session management function, and the target message carries the second IP address.
  • the embodiment of the present application further provides another address allocation device, which includes: a receiving module and a sending module.
  • the receiving module is used to receive a session policy message sent by a policy control function, wherein the session policy message carries a private network uniform resource locator;
  • the sending module is used to send the session policy message to the user plane function, so that the user plane function obtains a first IP address according to the session policy message, where the first IP address is an IP address corresponding to the private network uniform resource locator; and allocates a second IP address according to the first IP address, where the second IP address is different from the first IP address.
  • the sending module is further used to: send a request message to the user plane function, wherein the request message is used to request the user plane function to allocate an IP address.
  • the receiving module after sending the session policy message to the user plane function, is also used to: receive a target message of the user plane function, the target message carrying the second IP address; the sending module is also used to: send a session policy update message to the policy control function, the session policy update message carrying the second IP address.
  • the embodiment of the present application further provides a user plane function entity 1100, which can be various types of computers.
  • the user plane function entity 1100 includes: a processor 1110, a memory 1120, and the memory 1120 stores programs or Instructions, when the program or instructions are executed by the processor 1110, the steps of any address allocation method described in Figures 4 to 6 are implemented.
  • An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored on which a program or instruction is stored.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information.
  • Information can be computer readable instructions, data structures, program modules or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种地址分配方法、装置和用户平面功能实体，属于通信技术领域。该方法包括：用户平面功能接收会话管理功能发送的会话策略消息，会话策略消息携带专网统一资源定位符(410)；用户平面功能根据会话策略消息，获取第一IP地址，第一IP地址为与专网统一资源定位符对应的IP地址(420)；用户平面功能根据第一IP地址，分配第二IP地址，其中，第二IP地址与第一IP地址不同(430)。

Description

地址分配方法、装置和用户平面功能实体
相关申请的交叉引用
本申请要求在2022年12月01日提交中国专利局、申请号为202211530852.2、发明名称为“地址分配方法、装置和用户平面功能实体”的中国专利申请的优先权，该中国专利申请的全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种地址分配方法、装置和用户平面功能实体。
背景技术
由于网络侧专网数据网络名称(Data Network Name，DNN)会话方案可以帮助用户设备(User Equipment，UE)在不修改终端和承载数据的情况下，实现专网和公网无感知切换，因而，其得到了广泛应用。
相关技术中，在实现网络侧专网DNN会话时，会话管理功能(Session Management Function，SMF)通常会为接入会话的UE随机分配IP地址。然而，这种分配方式分配的IP地址往往会与专网统一资源定位符(Universal Resource Locator，URL)对应的IP地址存在冲突。
发明内容
本申请实施例提供一种地址分配方法、装置和电子设备，能够解决相关技术中分配的IP地址与专网URL对应的IP地址存在冲突的问题。
第一方面，本申请实施例提供了一种地址分配方法，该方法包括：用户平面功能接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；所述用户平面功能根据所述会话策略消息，获取第一IP 地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；所述用户平面功能根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
第二方面，本申请实施例提供了一种地址分配方法，该方法包括：会话管理功能接收策略控制功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；所述会话管理功能向用户平面功能发送所述会话策略消息，使得所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；并根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
第三方面，本申请实施例提供了一种地址分配装置，该装置包括：接收模块，用于接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；获取模块，用于根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；分配模块，用于根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
第四方面，本申请实施例提供了一种用户平面功能实体，该用户平面功能实体包括处理器和存储器，所述存储器存储程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第五方面，本申请实施例提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面或第二方面所述的方法的步骤。
第六方面，本申请实施例提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面或第二方面所述的方法。
第七方面，本申请实施例提供一种计算机程序产品，该程序产品被存储在存储介质中，该程序产品被至少一个处理器执行以实现如第一方面或第二 方面所述的方法。
附图说明
图1是相关技术中提供的一种网络侧专网DNN会话功能原理图；
图2是在图1的基础上提供的一种业务流的示意图；
图3是本申请实施例提供的一种的网络拓扑结构图；
图4是本申请实施例提供的一种地址分配方法的流程图；
图5是本申请实施例提供的另一种地址分配方法的流程图；
图6是本申请实施例提供的另一种地址分配方法的流程图；
图7是本申请实施例提供的另一种地址分配方法的流程图；
图8是本申请实施例提供的一种地址分配流程的交互示意图；
图9是本申请实施例提供的另一种地址分配流程的交互示意图；
图10是本申请实施例提供的一种地址分配装置的结构框图；
图11是本申请实施例提供的一种用户平面功能实体的结构框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”等所区分的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符 “/”，一般表示前后关联对象是一种“或”的关系。
图1是相关技术中提供的一种网络侧专网DNN会话功能原理图。如图1所示，当用户签约专网业务时，策略控制功能(Policy Control Function，PCF)1可以基于签约信息在N7接口传递指定的URL(即service URL，其格式可以为IP格式、全限定域名(Fully Qualified Domain Name，FQDN)格式等)、专网接入点名称(Access Point Name，APN)和切片等多DNN会话策略信息给SMF1网元。SMF1可以将接收到的专网DNN规则通过N4接口的信令下发给公网用户平面管理功能(User Plane Function，UPF)1。当用户访问专网DNN业务时，公网UPF1可以触发探测上报给公网SMF1，公网SMF1可以触发专网DNN会话的建立，选择SMF2作为专网会话的锚点SMF。
其中，SMF1可以为公网会话分配UE IP1，SMF2可以为专网会话分配UE IP2，当用户访问专网时，上行报文可以在公网UPF1上进行地址转换IP1>IP2，下行报文可以在公网UPF1上进行地址转换IP2>IP1。
图2是在图1的基础上提供的一种业务流的示意图。如图2所示，图2中包括两条业务流，分别为公网业务流和专网业务流。另外图2中虚线可以用于指示信令，实线可以用于指示数据。公网业务流涉及到IP1、IP3和IP4，其中IP1，IP3和IP4均为公网IP地址。其中，UE侧涉及到IP1和IP4两个地址，公网服务器侧涉及到IP3和IP4两个地址，无论是UE侧还是公网服务器侧都不存在IP冲突。
专网业务流涉及到IP1、IP2和IP5(专网URL对应的IP地址)，其中，IP1、IP2和IP5均为私网IP地址。其中，UE侧涉及到IP1和IP5两个地址；专网服务器侧涉及到IP2和IP5两个地址。由于UE侧IP1由SMF1随机分配，导致IP1与IP5可能冲突。而一旦IP1和IP5存在冲突，UE访问专网的上行报文会发送失败。
有鉴于此，本申请实施例创造性提出了一种地址分配方法、装置和用户平面功能实体，可以有效避免目标UE的IP地址与专网URL对应的IP地址 存在冲突。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的地址分配方法、装置和用户平面功能实体进行详细地说明。
图3是本申请实施例提供的一种网络拓扑结构图。该网络拓扑中可以包括目标UE、无线电接入网(Radio Access Network，RAN)、接入移动管理功能(Access Mobility Management Function，AMF)1、网络存储功能(Network Repository Function，NRF)1、PCF1、公网SMF1、专网SMF2、公网UPF1、专网UPF2、专网、大网(公网)等。其中，图3中虚线左侧可以指示目标UE对应的专网漫游地，虚线右侧可以指示目标UE对应的专网归属地。图3对应于目标UE在专网漫游地接入的场景。以FQDN格式的专网URL(service URL)为例，在此场景下，PCF1可以下发专网DNN会话策略给公网SMF1。公网SMF1可以将接收到的专网DNN会话策略通过N4接口下发给公网UPF1。从而，公网UPF1可以对接收到的专网DNN会话策略中FQDN格式的service URL进行主动DNS学习，并为目标UE分配IP地址，避免目标UE的IP地址与FQDN格式的service URL对应的IP地址冲突。
其中，公网UPF1进行主动DNS学习可以包括：当PCF1下发的service URL为FQDN格式时，公网UPF1通过DNS请求报文主动学习到此FQDN格式的service URL对应的IP地址。公网UPF1分配地址的方式可以为第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)第16个公开版本协议中推荐的地址分配方式。在公网UPF1学习到FQDN格式的service URL对应的IP地址后，公网UPF1可以为目标UE分配与学习到的IP地址不存在冲突的IP地址。
本申请实施例提供的地址分配方法，可以通过公网UPF1的主动DNS学习获取FQDN格式的service URL对应的IP地址，并根据service URL对应的IP地址为目标UE分配不存在冲突的IP地址，使得目标UE可以正常访问专网。
需要说明的是，上文所描述的地址分配方法仅是本申请的一种示例，不能视为对本申请的限制。实际上，公网UPF1可以通过多种方式获取service URL对应的IP地址，且本申请实施例提供的地址分配方法不仅适用于FQDN格式的service URL，同样适用于IP格式的service URL。后文将会一一介绍。
图4是本申请实施例提供的一种地址分配方法的流程图。如图4所示，本申请实施例提供的地址分配方法可以包括如下步骤：
步骤410，用户平面功能接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
在本申请实施例中，SMF和UPF均可以支持专网本地或者漫游地建立网络侧专网会话。SMF可以为公网SMF，例如图3所示的公网SMF1。UPF可以为公网UPF，例如图3所示的公网UPF1。
在目标UE访问专网时，UPF可以接收SMF下发的会话策略消息。其中，会话策略消息可以为PCF主动下发给SMF或在接收到SMF的请求后返回给SMF的消息。
所述会话策略消息中可以携带专网DNN策略。其中，所述专网DNN策略中可以包括专网URL。同时，除专网URL之外，专网DNN策略中还可以包括专网DNN、专网切片中的至少一者。
所述专网URL可以为FQDN格式的URL、IP格式的URL或子域名格式的URL。
步骤420，所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；
所述第一IP地址可以为至少一个IP地址，或者一个IP地址段。其中，至少一个IP地址可以是一个IP地址，例如119.147.50.92，也可以是多个IP地址，例如180.97.33.107和180.97.33.108。
在会话策略消息中携带的专网URL为目标格式(例如FQDN格式)的定位符的情况下，UPF可以先从会话策略消息中提取目标格式的定位符，再 利用DNS服务器或者预设的映射表，获取目标格式的定位符对应的第一IP地址。其中，映射表中可以存储目标格式的定位符和IP地址的对应关系。
在会话策略消息中携带的专网URL为IP格式的定位符的情况下，UPF可以直接从会话策略消息中获取IP格式的定位符对应的第一IP地址。
步骤430，所述用户平面功能根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
所述第二IP地址可以为UPF为网络侧专网会话中的目标UE分配的地址。第二IP地址与第一IP地址不同可以表示第二IP地址与第一IP地址中的任一地址都不同，即第二IP地址与第一IP地址不存在冲突，第一IP地址中不包含与第二IP地址相同的地址。
确定第一IP地址后，UPF可以通过以下至少两种方式分配与第一IP地址不同的第二IP地址。第一种方式：UPF可以先确定预先配置的IP列表中与第一IP地址存在冲突的地址，并将存在冲突的地址从预先配置的IP列表中移除或屏蔽，再从剩余的IP列表中选取一个IP地址作为第二IP地址。第二种方式：UPF可以从预先配置的IP地址列表中随机选取一个IP地址，并判断选取的IP地址是否与第一IP地址存在冲突，在不存在冲突的情况下，将选取的IP地址作为第二IP地址。在存在冲突的情况下，继续选取，直到随机选取的IP地址与第一IP地址不存在冲突。最后将随机选取的且与第一IP地址不存在冲突的IP地址作为第二IP地址。
本申请实施例提供的地址分配方法，可以根据会话策略消息获取与专网统一资源定位符对应的第一IP地址，并进一步根据第一IP地址，令用户平面功能针对性地分配与第一IP地址不同的第二IP地址，从而能够保证会话过程中第一IP地址与第二IP地址不存在冲突，进而使得第二IP地址对应的设备可以正常访问专网。
另外需要说明的是，相较于现有技术，本申请实施例提供的可以避免地址冲突的地址分配方法不局限于IP格式的专网URL，同样适用于域名格式 的专网URL，可以增强公网用户访问专网网络的体验。同时，由于大部分政府、企业和校园的专网service URL采用FQDN格式(比纯IP地址格式更安全)，因此本申请也可以进一步推动网络侧专网DNN会话功能在政府、企业和校园内网的普及。
在一些场景下，例如公网用户通过目标UE上线大网会话后签约专网业务的场景，为了保证网络侧专网会话正常，可以先进行地址冲突检测，再确定是否需要重新为目标UE分配IP地址。在本申请的一个实施例中，在步骤430所述用户平面功能根据所述第一IP地址，分配第二IP地址之前，所述地址分配方法还包括：所述用户平面功能获取第三IP地址；其中，所述第三IP地址为针对目标UE已分配的IP地址；所述用户平面功能根据所述第一IP地址，分配第二IP地址，包括：在所述第一IP地址与所述第三IP地址存在冲突的情况下，分配第二IP地址。如此，可以在已针对目标UE分配IP地址的情况下，进一步判断已经分配的IP地址是否与第一IP地址存在冲突，并在存在冲突的情况下，重新为目标UE分配IP地址，以此保证网络侧专网会话过程中目标UE的IP地址与专网URL对应的IP地址不存在冲突，使得目标UE可以正常访问专网。
第三IP地址可以为公网业务流中目标UE的IP地址，例如未签约专网业务的用户通过目标UE上线大网会话时，SMF或者UPF为目标UE分配的地址。第一IP地址与第三IP地址存在冲突可以表示第一IP地址中存在与第三IP地址相同的地址。
在第一IP地址与第三IP地址不存在冲突的情况下，可以直接将第三IP地址作为第二IP地址，无需重新分配。
如上文所描述，专网URL可以为多种格式的定位符。由于针对不同格式的定位符，获取第一IP地址的方式不同。因而，本申请后文将进一步介绍根据不同格式的专网URL，获取第一IP地址的具体过程。在本申请的一个实施例中，所述专网统一资源定位符为IP格式的定位符，步骤420所述用户平 面功能根据所述会话策略消息，获取第一IP地址，可以包括：所述用户平面功能从所述会话策略消息中，提取所述IP格式的定位符，并将所述IP格式的定位符作为第一IP地址。如此，UPF可以快速获取第一IP地址，无需增加额外的信令交互，有利于提高地址分配效率。
UPF分配第二IP地址后，可以将第二IP地址上报给网络侧专网会话中的其他网元。在本申请的一个实施例中，在步骤430所述用户平面功能根据所述第一IP地址，分配第二IP地址之后，所述地址分配方法还包括：所述用户平面功能向会话管理功能发送目标消息，所述目标消息携带所述第二IP地址。如此，UPF可以将分配好的第二IP地址上报给SMF，使得SMF可以进一步向其他网元传递目标UE的IP地址，保证信令正常传输。
UPF分配第二IP地址之后，可以将携带有第二IP地址的目标消息发送给SMF。同时，SMF接收目标消息后可以向PCF发送会话策略更新消息，其中，会话策略更新消息中携带第二IP地址。PCF接收到会话策略更新消息后可以返回成功响应给SMF。
图5是本申请实施例提供的另一种地址分配方法的流程图。如图5所示，本申请实施例提供的地址分配方法包括如下步骤：
步骤510，用户平面功能接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
其中，所述专网统一资源定位符为目标格式的定位符。
所述目标格式可以为FQDN格式。
步骤520，在所述用户平面功能检测到所述会话策略消息中的所述专网统一资源定位符为目标格式的定位符的情况下，所述用户平面功能向域名服务器发送地址解析请求，所述地址解析请求携带所述目标格式的定位符；
域名服务器(Domain Name Server，DNS服务器)可以为用于进行域名和与之相对应的IP地址转换的服务器。地址解析请求可以用于指示DNS服务器将目标格式的定位符解析为相应的IP地址。
若会话策略消息中的专网URL为目标格式的定位符，则UPF可以向DNS发送携带有目标格式的定位符的地址解析请求。从而域名服务器可以对获取到的目标格式的定位符进行解析，确定其对应的IP地址。在本申请实施例中，可以在UPF上配置DNS服务器地址，使得UPF检测到目标格式的定位符后可以主动向该地址对应的DNS服务器发送地址解析请求。
步骤530，所述用户平面功能接收所述域名服务器发送的第一IP地址；
其中，所述第一IP地址为与所述目标格式的定位符对应的IP地址；
DNS服务器解析得到的第一IP地址可以为单个IP地址、多个IP地址或者一个IP地址段。UPF接收DNS服务器发送的第一IP地址后，可以执行后续步骤。
步骤540，所述用户平面功能根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
第二IP地址的具体分配方法可以参照上文对步骤430的描述。在此不再赘述。
本申请实施例提供的地址分配方法，可以利用DNS服务器对目标格式的定位符进行解析，准确获取目标格式的定位符对应的第一IP地址，有利于根据第一IP地址针对性分配与第一IP地址不同的第二IP地址，从而能够保证会话过程中第一IP地址与第二IP地址不存在冲突，进而使得第二IP地址对应的设备可以正常访问专网。
由于UPF在不同时间节点可能会检测到会话策略消息中携带的相同的目标格式的定位符，因而在UPF上记录目标格式的定位符和从DNS服务器接收的目标格式的定位符对应的第一IP地址可以避免需要重复向DNS服务器发送相同的地址解析请求。在本申请的一个实施例中，在步骤540之后，所述地址分配方法还包括：所述用户平面功能将所述目标格式的定位符和所述第一IP地址的对应关系记录在目标映射表中。如此，通过学习目标格式的定位符和第一IP地址的对应关系，生成目标映射表，UPF后续可以直接利用目 标映射表获取部分目标格式的定位符对应的IP地址，减少信令交互，能够在一定程度上提高地址分配效率。
图6是本申请实施例提供的另一种地址分配方法的流程图。如图6所示，本申请实施例提供的地址分配方法包括如下步骤：
步骤610，用户平面功能接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
其中，所述专网统一资源定位符为目标格式的定位符。
所述目标格式可以为FQDN格式。
步骤620，所述用户平面功能在目标映射表中查询与所述目标格式的定位符对应的IP地址；其中，所述目标映射表用于存储统一资源定位符和IP地址之间的对应关系；
目标映射表中URL可以包括至少一个目标格式的定位符。目标映射表中URL与IP地址之间的对应关系可以为一一对应关系或者一对多对应关系。
UPF在目标映射表中进行查询时可以以目标格式的定位符为索引，确定目标映射表中是否存在与目标格式的定位符对应的IP地址。
步骤630，所述用户平面功能在查询得到与所述目标格式的定位符对应的IP地址的情况下，将查询得到的所述IP地址确定为第一IP地址；
可以理解的是，当目标映射表中包括与目标格式的定位符一致的URL，以及该URL对应的IP地址时，UPF可以查询得到对应的IP地址。
在此情况下，UPF可以直接利用目标映射表获取第一IP地址。
步骤640，所述用户平面功能根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
本申请实施例提供的地址分配方法，通过在目标映射表中查询与目标格式的定位符对应的IP地址，使得UPF可以优先利用目标映射表进行地址解析，从而能够避免向DNS服务器发送不必要的地址解析请求，进而可以减少UPF与DNS服务器之间的信令交互，在一定程度上提高地址分配效率。
可选地，在本申请的一个实施例中，所述根据所述会话策略消息，获取第一IP地址，还包括：所述用户平面功能在未查询得到与所述目标格式的定位符对应的IP地址的情况下，向域名服务器发送地址解析请求；所述地址解析请求携带所述目标格式的定位符；所述用户平面功能接收所述域名服务器发送的第一IP地址。如此，在目标映射表中信息有限的情况下，可以继续使用DNS服务器对目标格式的定位符进行解析，确保UPF能够准确获取目标格式的定位符对应的第一IP地址。
可以理解的是，当目标映射表中不包括与目标格式的定位符一致的URL时，UPF无法查询得到目标格式的定位符对应的IP地址。
在此情况下，UPF可以继续向DNS发送携带目标格式的定位符的地址解析请求，并从DNS服务器接收目标格式的定位符对应的第一IP地址。
图7是本申请实施例提供的另一种地址分配方法的流程图。如图7所示，本申请实施例提供的地址分配方法包括如下步骤：
步骤710，会话管理功能接收策略控制功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
其中，会话策略消息可以为PCF主动下发给SMF或在接收到SMF的请求后返回给SMF的消息。
所述会话策略消息中可以携带专网DNN策略。其中，所述专网DNN策略中可以包括专网URL。同时，除专网URL之外，专网DNN策略中还可以包括专网DNN、专网切片中的至少一者。
所述专网URL可以为FQDN格式的URL、IP格式的URL或子域名格式的URL。
步骤720，所述会话管理功能向用户平面功能发送所述会话策略消息，使得所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；并根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
所述第一IP地址可以为至少一个IP地址，或者一个IP地址段。
在会话策略消息中携带的专网URL为目标格式(例如FQDN格式)的定位符的情况下，UPF可以先从会话策略消息中提取目标格式的定位符，再利用DNS服务器或者预设的映射表，获取目标格式的定位符对应的第一IP地址。其中，映射表中可以存储目标格式的定位符和IP地址的对应关系。
在会话策略消息中携带的专网URL为IP格式的定位符的情况下，UPF可以直接从会话策略消息中获取IP格式的定位符对应的第一IP地址。
所述第二IP地址可以为UPF为网络侧专网会话中的目标UE分配的地址。第二IP地址与第一IP地址不同可以表示第二IP地址与第一IP地址中的任一地址都不同，即第二IP地址与第一IP地址不存在冲突，第一IP地址中不包含与第二IP地址相同的地址。
本申请实施例提供的地址分配方法，通过令UPF根据会话策略消息获取与专网统一资源定位符对应的第一IP地址，并进一步根据第一IP地址，针对性地分配与第一IP地址不同的第二IP地址，能够保证会话过程中第一IP地址与第二IP地址不存在冲突，使得第二IP地址对应的设备可以正常访问专网。
可选地，在本申请的一个实施例中，所述地址分配方法还包括：所述会话管理功能向所述用户平面功能发送请求消息，所述请求消息用于请求所述用户平面功能分配IP地址。如此，基于SMF发送的请求消息可以实现由UPF分配IP地址。
确定第二IP地址后，可以将第二IP地址传递给网络侧专网会话中的其他网元。在本申请的一个实施例中，在步骤720所述会话管理功能向用户平面功能发送所述会话策略消息之后，所述地址分配方法还包括：所述会话管理功能接收所述用户平面功能的目标消息，所述目标消息携带所述第二IP地址；所述会话管理功能向策略控制功能发送会话策略更新消息，所述会话策略更新消息携带所述第二IP地址。如此，SMF可以接收UPF发送的第二IP 地址，并进一步向网络侧专网会话中的其他网元传递目标UE的IP地址，保证信令正常传输。
UPF分配第二IP地址之后，SMF可以接收UPF返回的携带有第二IP地址的目标消息，并向PCF发送会话策略更新消息，其中，会话策略更新消息中携带第二IP地址。PCF接收到会话策略更新消息后可以返回成功响应给SMF。
为便于理解，后文结合具体场景和交互流程对本申请实施例提供的地址分配方法进行详细说明。
图8是本申请实施例提供的一种地址分配流程的交互示意图。图8针对的场景是已签约专网用户上线大网会话的场景。以FQDN格式的专网URL(service URL)为例，在此场景下，本申请实施例中地址分配流程可以包括如下步骤：
步骤801，签约专网用户发起会话建立请求，AMF向SMF1(对应于上文会话管理功能)发送会话建立请求消息；
可以理解的是，签约专网用户可以通过目标UE发起会话建立请求。
步骤802，SMF1向PCF发送会话策略信息获取(对应于上文会话策略消息)请求；
步骤803，PCF向SMF1返回响应消息，其中，响应消息中携带会话策略信息，会话策略信息中包含用户签约的专网DNN策略(专网DNN、专网切片、专网service URL，专网service URL为FQDN格式)；
步骤804，SMF1通过报文转发控制协议(Packet Forwarding Control Protocol，PFCP)消息将专网DNN策略下发给UPF1(对应于上文用户平面功能)，同时请求UPF1分配UE IP；
步骤805，UPF1检测到专网DNN会话策略中的service URL(对应于上文专网URL)为FQDN格式，主动发送请求给DNS服务器请求解析service URL的FQDN对应的IP地址；
步骤806，DNS服务器向UPF1返回service URL的FQDN对应的IP地址(对应于上文第一IP地址)；
步骤807，UPF1进行UE IP地址的分配，分配时进行地址防冲突，分配不与FQDN对应IP冲突的地址(对应于上文第二IP)，并向SMF1返回会话策略安装成功消息，并返回分配成功的UE IP给SMF1；
步骤808，SMF1向PCF发送会话策略更新消息，同时携带分配的UE IP；
步骤809，PCF返回成功响应给SMF1；
步骤810，SMF1向AMF1返回会话建立成功响应消息。
本申请实施例提供的地址分配方法，一方面可以实现由UPF为目标UE分配IP地址，另一方面可以利用DNS服务器对FQDN格式的定位符进行解析，准确获取FQDN格式的定位符对应的IP地址，使得UPF可以根据FQDN格式的定位符对应的IP地址针对性地为目标UE分配不存在冲突的IP地址，从而能够保证分配IP地址后目标UE可以正常访问专网。
图9是本申请实施例提供的另一种地址分配流程的交互示意图。图9针对的场景是未签约专网用户上线大网会话后，用户发生签约专网业务，PCF主动下发专网DNN策略的场景。以FQDN格式的专网URL(service URL)为例，在此场景下，本申请实施例中地址分配流程可以包括如下步骤：
步骤901，用户签约专网DNN业务后，PCF主动向SMF1下发专网DNN策略(对应于上文专网会话策略消息)，携带FQDN格式的service URL；
步骤902，大网会话SMF1响应成功；
步骤903，SMF1通过PFCP消息将专网DNN策略下发给UPF1；
步骤904，UPF1检测到专网DNN会话策略中的service URL(对应于上文专网URL)为FQDN格式，主动发送请求给DNS服务器请求解析service URL的FQDN对应的IP地址；
步骤905，DNS服务器向UPF1返回service URL的FQDN对应的IP地址(对应于上文第一IP地址)；
步骤906，UPF1进行地址冲突检测，如果service URL的FQDN对应的IP和会话当前的UE IP地址(对应于上文第三IP地址)冲突，则发起UE IP地址的重分配，重新分配不与FQDN对应的IP地址冲突的UE IP(对应于上文第二IP地址)，并返回重新分配的UE IP给SMF1；
步骤907，SMF1给PCF发送会话策略更新消息，其中，会话策略更新消息中携带重新分配的UE IP；
步骤908，PCF返回成功响应给SMF1。
本申请实施例提供的地址分配方法，可以在已针对目标UE分配IP地址的情况下，进一步判断已经分配的IP地址是否与专网URL对应的IP地址存在冲突，并在存在冲突的情况下，重新为目标UE分配不同的IP地址，以此保证网络侧专网会话过程中目标UE的IP地址与专网URL对应的IP地址不存在冲突，使得目标UE可以正常访问专网。
图10是本申请实施例提供的一种地址分配装置的结构框图。如图10所示，本申请实施例提供的地址分配装置1000包括：接收模块1010、获取模块1020和分配模块1030。
所述接收模块1010，用于接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
所述获取模块1020，用于根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；
所述分配模块1030，用于根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
本申请实施例提供的地址分配装置，可以根据会话策略消息获取与专网统一资源定位符对应的第一IP地址，并进一步根据第一IP地址，针对性地分配与第一IP地址不同的第二IP地址，从而能够保证会话过程中第一IP地址与第二IP地址不存在冲突，进而使得第二IP地址对应的设备可以正常访问专网。
可选地，在本申请的一个实施例中，在根据所述第一IP地址，分配第二IP地址之前，所述获取模块1020还用于：获取第三IP地址；其中，所述第三IP地址为针对目标UE已分配的IP地址；在根据所述第一IP地址，分配第二IP地址的过程中，所述分配模块1030具体用于：在所述第一IP地址与所述第三IP地址存在冲突的情况下，分配第二IP地址。
可选地，在本申请的一个实施例中，所述专网统一资源定位符为目标格式的定位符；在所述根据所述会话策略消息，获取第一IP地址的过程中，所述获取模块1020具体用于：在检测到所述会话策略消息中的所述专网统一资源定位符为目标格式的定位符的情况下，向域名服务器发送地址解析请求，所述地址解析请求携带所述目标格式的定位符；接收所述域名服务器发送的第一IP地址。
可选地，在本申请的一个实施例中，所述地址分配装置1000还包括存储模块，在接收所述域名服务器发送的第一IP地址之后，所述存储模块，用于将所述目标格式的定位符和所述第一IP地址的对应关系记录在目标映射表中。
可选地，在本申请的一个实施例中，所述专网统一资源定位符为目标格式的定位符；在所述根据所述会话策略消息，获取第一IP地址的过程中，所述获取模块1020具体用于：在目标映射表中查询与所述目标格式的定位符对应的IP地址；其中，所述目标映射表用于存储统一资源定位符和IP地址之间的对应关系；在查询得到与所述目标格式的定位符对应的IP地址的情况下，将查询得到的所述IP地址确定为第一IP地址。
可选地，在本申请的一个实施例中，在所述根据所述会话策略消息，获取第一IP地址的过程中，所述获取模块1020具体用于：在未查询得到与所述目标格式的定位符对应的IP地址的情况下，向域名服务器发送地址解析请求；所述地址解析请求携带所述目标格式的定位符；接收所述域名服务器发送的第一IP地址。
可选地，在本申请的一个实施例中，所述目标格式为全限定域名格式。
可选地，在本申请的一个实施例中，所述专网统一资源定位符为IP格式的定位符，在所述用户平面功能根据所述会话策略消息，获取第一IP地址的过程中，所述获取模块1020具体用于：从所述会话策略消息中，提取所述IP格式的定位符，并将所述IP格式的定位符作为第一IP地址。
可选地，在本申请的一个实施例中，所述地址分配装置1000还包括发送模块，在根据所述第一IP地址，分配第二IP地址之后，所述发送模块，用于向会话管理功能发送目标消息，所述目标消息携带所述第二IP地址。
除图10所示地址分配装置之外，本申请实施例还提供了另一种地址分配装置。所述地址分配装置包括：接收模块和发送模块。
所述接收模块，用于接收策略控制功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
所述发送模块用于向用户平面功能发送所述会话策略消息，使得所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；并根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
可选地，在本申请的一个实施例中，所述发送模块还用于：向所述用户平面功能发送请求消息，所述请求消息用于请求所述用户平面功能分配IP地址。
可选地，在本申请的一个实施例中，在向用户平面功能发送所述会话策略消息之后，所述接收模块还用于：接收所述用户平面功能的目标消息，所述目标消息携带所述第二IP地址；所述发送模块还用于：向策略控制功能发送会话策略更新消息，所述会话策略更新消息携带所述第二IP地址。
此外，如图11所示，本申请实施例还提供一种用户平面功能实体1100，所述用户平面功能实体1100可以为各种类型的计算机等。所述用户平面功能实体1100包括：处理器1110，存储器1120，所述存储器1120上存储程序或 指令，所述程序或指令被所述处理器1110执行时实现如图4-图6所描述的任一种地址分配方法的步骤。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被所述处理器1110执行时实施上文所描述的任一种地址分配方法的步骤。
本领域内的技术人员应明白，本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (15)

  1. 一种地址分配方法，包括：
    用户平面功能接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
    所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；
    所述用户平面功能根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
  2. 根据权利要求1所述的方法，其中，在所述用户平面功能根据所述第一IP地址，分配第二IP地址之前，所述方法还包括：
    所述用户平面功能获取第三IP地址；其中，所述第三IP地址为针对目标UE已分配的IP地址；
    所述用户平面功能根据所述第一IP地址，分配第二IP地址，包括：
    在所述第一IP地址与所述第三IP地址存在冲突的情况下，分配第二IP地址。
  3. 根据权利要求1所述的方法，其中，所述专网统一资源定位符为目标格式的定位符；所述根据所述会话策略消息，获取第一IP地址，包括：
    在所述用户平面功能检测到所述会话策略消息中的所述专网统一资源定位符为目标格式的定位符的情况下，所述用户平面功能向域名服务器发送地址解析请求，所述地址解析请求携带所述目标格式的定位符；
    所述用户平面功能接收所述域名服务器发送的第一IP地址。
  4. 根据权利要求3所述的方法，其中，在所述用户平面功能接收所述域名服务器发送的第一IP地址之后，所述方法还包括：
    所述用户平面功能将所述目标格式的定位符和所述第一IP地址的对应关系记录在目标映射表中。
  5. 根据权利要求1所述的方法，其中，所述专网统一资源定位符为目标格式的定位符；所述根据所述会话策略消息，获取第一IP地址，包括：
    所述用户平面功能在目标映射表中查询与所述目标格式的定位符对应的IP地址；其中，所述目标映射表用于存储统一资源定位符和IP地址之间的对应关系；
    所述用户平面功能在查询得到与所述目标格式的定位符对应的IP地址的情况下，将查询得到的所述IP地址确定为第一IP地址。
  6. 根据权利要求5所述的方法，其中，所述根据所述会话策略消息，获取第一IP地址，还包括：
    所述用户平面功能在未查询得到与所述目标格式的定位符对应的IP地址的情况下，向域名服务器发送地址解析请求；所述地址解析请求携带所述目标格式的定位符；
    所述用户平面功能接收所述域名服务器发送的第一IP地址。
  7. 根据权利要求3-6任一项所述的方法，其中，所述目标格式为全限定域名格式。
  8. 根据权利要求1所述的方法，其中，所述专网统一资源定位符为IP格式的定位符，所述用户平面功能根据所述会话策略消息，获取第一IP地址，包括：
    所述用户平面功能从所述会话策略消息中，提取所述IP格式的定位符，并将所述IP格式的定位符作为第一IP地址。
  9. 根据权利要求1所述的方法，其中，在所述用户平面功能根据所述第一IP地址，分配第二IP地址之后，所述方法还包括：
    所述用户平面功能向会话管理功能发送目标消息，所述目标消息携带所述第二IP地址。
  10. 一种地址分配方法，包括：
    会话管理功能接收策略控制功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
    所述会话管理功能向用户平面功能发送所述会话策略消息，使得所述用户平面功能根据所述会话策略消息，获取第一IP地址，所述第一IP地址为 与所述专网统一资源定位符对应的IP地址；并根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
  11. 根据权利要求10所述的地址分配方法，其中，所述方法还包括：
    所述会话管理功能向所述用户平面功能发送请求消息，所述请求消息用于请求所述用户平面功能分配IP地址。
  12. 根据权利要求10所述的地址分配方法，其中，在所述会话管理功能向用户平面功能发送所述会话策略消息之后，所述方法还包括：
    所述会话管理功能接收所述用户平面功能的目标消息，所述目标消息携带所述第二IP地址；
    所述会话管理功能向策略控制功能发送会话策略更新消息，所述会话策略更新消息携带所述第二IP地址。
  13. 一种地址分配装置，包括：
    接收模块，用于接收会话管理功能发送的会话策略消息，所述会话策略消息携带专网统一资源定位符；
    获取模块，用于根据所述会话策略消息，获取第一IP地址，所述第一IP地址为与所述专网统一资源定位符对应的IP地址；
    分配模块，用于根据所述第一IP地址，分配第二IP地址，其中，所述第二IP地址与所述第一IP地址不同。
  14. 一种用户平面功能实体，包括处理器和存储器，所述存储器存储程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1-8任一项所述的方法的步骤。
  15. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被执行时实现如权利要求1-12任一项所述的方法的步骤。
PCT/CN2023/134079 2022-12-01 2023-11-24 地址分配方法、装置和用户平面功能实体 WO2024114539A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211530852.2A CN118138568A (zh) 2022-12-01 2022-12-01 地址分配方法、装置和用户平面功能实体
CN202211530852.2 2022-12-01

Publications (1)

Publication Number Publication Date
WO2024114539A1 true WO2024114539A1 (zh) 2024-06-06

Family

ID=91238257

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/134079 WO2024114539A1 (zh) 2022-12-01 2023-11-24 地址分配方法、装置和用户平面功能实体

Country Status (2)

Country Link
CN (1) CN118138568A (zh)
WO (1) WO2024114539A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019174437A1 (zh) * 2018-03-12 2019-09-19 华为技术有限公司 地址管理方法、设备及***
CN114465987A (zh) * 2021-12-10 2022-05-10 达闼机器人股份有限公司 网络地址分配方法、物联网***、装置、设备和存储介质
CN114726829A (zh) * 2022-04-02 2022-07-08 中国电信股份有限公司 通信方法、用户面网关及通信***
CN114938508A (zh) * 2022-05-31 2022-08-23 中国联合网络通信集团有限公司 5g专网网络控制方法、装置、电子设备及存储介质
CN115529294A (zh) * 2022-04-27 2022-12-27 ***通信集团设计院有限公司 业务处理方法、装置、设备及存储介质
CN115529342A (zh) * 2022-04-27 2022-12-27 ***通信集团设计院有限公司 业务访问处理方法、装置、设备及存储介质
CN116866297A (zh) * 2023-07-26 2023-10-10 中国电信股份有限公司技术创新中心 双域专网的地址匹配方法、装置、通信设备和存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019174437A1 (zh) * 2018-03-12 2019-09-19 华为技术有限公司 地址管理方法、设备及***
CN114465987A (zh) * 2021-12-10 2022-05-10 达闼机器人股份有限公司 网络地址分配方法、物联网***、装置、设备和存储介质
CN114726829A (zh) * 2022-04-02 2022-07-08 中国电信股份有限公司 通信方法、用户面网关及通信***
CN115529294A (zh) * 2022-04-27 2022-12-27 ***通信集团设计院有限公司 业务处理方法、装置、设备及存储介质
CN115529342A (zh) * 2022-04-27 2022-12-27 ***通信集团设计院有限公司 业务访问处理方法、装置、设备及存储介质
CN114938508A (zh) * 2022-05-31 2022-08-23 中国联合网络通信集团有限公司 5g专网网络控制方法、装置、电子设备及存储介质
CN116866297A (zh) * 2023-07-26 2023-10-10 中国电信股份有限公司技术创新中心 双域专网的地址匹配方法、装置、通信设备和存储介质

Also Published As

Publication number Publication date
CN118138568A (zh) 2024-06-04

Similar Documents

Publication Publication Date Title
US20220272146A1 (en) Point of presence management in request routing
US7558880B2 (en) Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device
US9300623B1 (en) Domain name system cache integrity check
CN103051740B (zh) 域名解析方法、dns服务器及域名解析***
EP2266064B1 (en) Request routing
US11025584B2 (en) Client subnet efficiency by equivalence class aggregation
US11956210B2 (en) Method and apparatus for transmitting application programming interface API request
WO2019223887A1 (en) Methods for processing encrypted domain name server, dns, queries received from user equipment in a telecommunication network
TW202021315A (zh) 網路服務系統及網路服務方法
CN111327668B (zh) 网络管理方法、装置、设备和存储介质
CN103795581A (zh) 地址处理方法和设备
EP3043534B1 (en) Managing traffic overload on a dns server
CN106878485B (zh) 一种报文处理方法及装置
WO2024114539A1 (zh) 地址分配方法、装置和用户平面功能实体
CN113301173A (zh) 域名更新***及方法、消息转发方法、服务器
CN114945015B (zh) 信息获取方法、装置及存储介质
CN106664327A (zh) 域名***访问方法及设备
CN113992583B (zh) 一种表项维护方法及装置
CN115277213B (zh) 报文转板处理方法及装置
CN111404761A (zh) 内容成环检测处理方法、装置和计算机可读存储介质
CN111385371A (zh) Mac地址获取方法、装置和设备
CN111147618B (zh) 一种通信方法、装置、电子设备和存储介质
EP3657741B1 (en) Data packet routing method and data packet routing device
JP6487870B2 (ja) 名前解決装置、名前解決方法及び名前解決プログラム
CN116938873A (zh) 域名查询请求报文的分流方法、网元及介质

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

Country of ref document: EP

Kind code of ref document: A1