WO2024073921A1 - Procédé et appareil de prise en charge de périphérie - Google Patents

Procédé et appareil de prise en charge de périphérie Download PDF

Info

Publication number
WO2024073921A1
WO2024073921A1 PCT/CN2022/131567 CN2022131567W WO2024073921A1 WO 2024073921 A1 WO2024073921 A1 WO 2024073921A1 CN 2022131567 W CN2022131567 W CN 2022131567W WO 2024073921 A1 WO2024073921 A1 WO 2024073921A1
Authority
WO
WIPO (PCT)
Prior art keywords
sharing
information
dnai
edge
edge sharing
Prior art date
Application number
PCT/CN2022/131567
Other languages
English (en)
Inventor
Tingfang Tang
Haiyan Luo
Original Assignee
Lenovo (Beijing) Limited
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 Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2022/131567 priority Critical patent/WO2024073921A1/fr
Publication of WO2024073921A1 publication Critical patent/WO2024073921A1/fr

Links

Images

Classifications

    • 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/2866—Architectures; Arrangements
    • H04L67/2885—Hierarchically arranged intermediate devices, e.g. for hierarchical caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • 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/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal

Definitions

  • Embodiments of the present application are related to wireless communication technology, and more particularly, related to a method and apparatus of supporting edge sharing.
  • Wireless communication technologies have been developed to support edge computing within 5G architecture.
  • one application service may be served by multiple edge application servers (EAS) typically deployed in different sites. These multiple EAS instances that host the same content or service may use a single Internet protocol (IP) address (anycast address) or different IP addresses.
  • IP Internet protocol
  • UE User equipment
  • AS application server
  • UPF user plane
  • PDU protocol data unit
  • PDU sessions are established between the UE and the PSA UPF.
  • One PDU session may support one or more applications.
  • a suitable EAS e.g., the one closest to the UE
  • UL CL uplink classifier
  • BP branching point
  • DN local data network
  • KI #5 is related to global system for mobile communications association (GSMA) operator platform group (OPG) impacts and improvements for edge hosting environment (EHE) operated by separate party.
  • GSMA global system for mobile communications association
  • OPG operator platform group
  • EHE edge hosting environment
  • An exemplary scenario of EHE sharing is a case of edge node sharing defined in clause 3.3.5 of GSMA OPG. 02, wherein a first EAS hosted by a first operator is to be accessed by the UE via a second operator's network where the UE is served.
  • the first EAS can be called a sharing EAS
  • the first operator can be called a sharing operator
  • the first operator's network can be called a sharing network
  • the second operator can be called a serving operator
  • the second operator's network can be called a serving network.
  • the EHE providing the sharing EAS running the required edge application (s) can be a shared and/or sharing EHE deployed in the sharing network and/or hosting network, or be a sharing node, or sharing edge platform.
  • the sharing EAS is one of the edge application server (s) within the sharing node.
  • the sharing node used herein can also be referred to as other similar concepts here, such as sharing EHE, shared EHE, sharing edge platform etc.
  • the operators with sharing protocols e.g., the first operator and the second operator are partners, wherein each partner can be identified by a partner identity (ID) , e.g., a public land mobile network (PLMN) ID.
  • ID partner identity
  • PLMN public land mobile network
  • the sharing operator can be referred to as a sharing partner
  • the serving operator can be referred to as a serving partner.
  • EAS deployment information e.g., EAS deployment information (EDI) or traffic influence information of the sharing node needs to be sent to the serving network.
  • EDI EAS deployment information
  • exemplary legacy EAS deployment information includes parameter (s) associated with data network access identifier (DNAI) , e.g., "DNAI (s) " ; or "DNS Server Information” ; which is a list of DNS server identifier (consisting of IP address and port) for each DNAI; or "EAS IP address range Information, " which is IP address (s) of the EASs in the local DN for each DNAI.
  • DNAI data network access identifier
  • DNS Server Information which is a list of DNS server identifier (consisting of IP address and port) for each DNAI
  • EAS IP address range Information " which is IP address (s) of the EASs in the local DN for each DNAI.
  • One objective of the present application is to provide a solution of supporting edge sharing, e.g., a method and apparatus of supporting edge sharing, especially of obtaining DNAI information for edge sharing.
  • Some embodiments of the present application provide an apparatus of supporting edge sharing, e.g., a network exposure function (NEF) or the like, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive, from an network function (NF) , a first request including information related to edge sharing, wherein the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes; and determine DNAI information for edge sharing based on the information related to edge sharing and mapping information between DNAI information and the information related to edge sharing.
  • NEF network exposure function
  • Some embodiments of the present application also provide a method of supporting edge sharing, e.g., performed on an NEF or the like, which includes: receiving, from an NF, a first request including information related to edge sharing, wherein the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes; and determining DNAI information for edge sharing based on the information related to edge sharing and mapping information between DNAI information and the information related to edge sharing.
  • the information related to edge sharing further includes at least one of the following for a sharing node of the one or more sharing nodes: internet protocol (IP) address range; fully qualified domain name (FQDN) ; or N6 traffic routing requirements.
  • IP internet protocol
  • FQDN fully qualified domain name
  • the information related to edge sharing further includes at least one of the following related to the sharing node: geographical area; data network name (DNN) ; or single network slice selection assistance information (S-NSSAI) .
  • DNN data network name
  • S-NSSAI single network slice selection assistance information
  • the IP address range includes a plurality of subranges, each subrange corresponding to a DNAI.
  • the first request is to query DNAI information.
  • the processor is configured to: transmit a response indicating the determined DNAI information to the NF; and receive EAS deployment information or traffic influence information with the determined DNAI information.
  • the response further indicates the DNN related to the serving network; and/or in the case that S-NSSAI related to application (s) in a sharing node indicated in the information related to edge sharing is different from S-NSSAI related to the application (s) in a serving network, the response further indicates the S-NSSAI in the serving network.
  • the information related to edge sharing is included in EAS deployment information without DNAI or traffic influence information without DNAI in the first request.
  • the processor is configured to: update the EAS deployment information or the traffic influence information with the determined DNAI information.
  • the processor is further configured to: in the case that DNN related to application (s) in a sharing node indicated in the information related to edge sharing is different from DNN related to the application (s) in a serving network, update the DNN in the sharing node with the DNN in the serving network; and/or in the case that S-NSSAI related to the application (s) in a sharing node indicated in the information related to edge sharing is different from S-NSSAI related to the application (s) in a serving network, update the S-NSSAI in the sharing node with the S-NSSAI in the serving network.
  • the EAS deployment information or the traffic influence information includes priority information.
  • the mapping information is locally configured or is obtained from another NF.
  • Some other embodiments of the present application also provide another apparatus of supporting edge sharing, e.g., an application function (AF) or the like, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmit, to an NF, a first request including information related to edge sharing, wherein the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes; and receive a response at least made based on the information related to edge sharing.
  • AF application function
  • the response indicates DNAI information for edge sharing
  • the processor is configured to: transmit EAS deployment information or traffic influence information with the DNAI information.
  • embodiments of the present application provide solutions of supporting edge sharing, improving manners of obtaining DNAI information for edge sharing, and thus sharing edge node (s) , e.g., sharing EAS (s) can be correctly discovered and traffic associated with edge sharing can be correctly routed.
  • sharing edge node (s) e.g., sharing EAS (s) can be correctly discovered and traffic associated with edge sharing can be correctly routed.
  • FIG. 1 illustrates an exemplary network architecture supporting edge computing, in accordance with some embodiments of the present application.
  • FIG. 2 illustrates an exemplary procedure of supporting edge sharing in Case 1 according to some embodiments of the present application.
  • FIG. 3 illustrates an exemplary procedure of supporting edge sharing in Case 1 according to some other embodiments of the present application.
  • FIG. 4 illustrates an exemplary procedure of supporting edge sharing in Case 2 according to some embodiments of the present application.
  • FIG. 5 illustrates an exemplary procedure of supporting edge sharing in Case 2 according to some other embodiments of the present application.
  • FIG. 6 illustrates an exemplary block diagram of an apparatus of routing control according to some embodiments of the present application.
  • FIG. 7 illustrates an exemplary block diagram of an apparatus of routing control according to some other embodiments of the present application.
  • FIG. 1 illustrates an exemplary network architecture 100 supporting traffic offloading.
  • the network architecture 100 includes several NFs, in which the techniques, processes and methods described herein can be implemented, in accordance with various embodiments.
  • An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
  • a single NF may be implemented by a single entity or multiple entities in conjunction.
  • the network architecture 100 shown in FIG. 1 includes an NEF 102, a policy control function (PCF) 104, an AF 106, an AMF 108, and an SMF 110.
  • Nnef is a service-based interface exhibited by the NEF 102.
  • Npcf is a service-based interface exhibited by the PCF 104.
  • Naf is a service-based interface exhibited by the AF 106.
  • Namf is a service-based interface exhibited by the AMF 108.
  • Nsmf is a service-based interface exhibited by the SMF 110.
  • the network architecture 100 shown in FIG. 1 includes a UE 112 connected to an access network (AN) 114 and the AMF 108.
  • the UE 112 communicates with the AMF 108 via an interface N1.
  • the AN 114 includes one or more base stations (BSs) (not shown) , e.g., enhanced or evolved Node Bs (eNBs) , 5G base stations (gNBs) or the like.
  • BSs base stations
  • eNBs enhanced or evolved Node Bs
  • gNBs 5G base stations
  • the AN 114 may connect to a first DN 122 via a first UPF 116 and a second UPF 118, and to a second DN 124 via the first UPF 116 and a third UPF 120.
  • the AN 114 communicates with the AMF 108 via an interface N2, and communicates with the first UPF 116 via an interface N3.
  • a UPF to steer a traffic can be a UL CL or BP UPF, e.g., the first UPF 116 when there are multiple PSA UPFs, e.g., the second UPF 118 and the third UPF 120 for a PDU session.
  • the UL CL or BP UPF can be a standalone UPF or be co-located with a PSA UPF.
  • the UPF to steer a traffic can also be a PSA UPF or a UPF of N3 terminating point when there is only one PSA UPF for a PDU session, that is, there is no UL CL or BP UPF.
  • the SMF 110 may make routing decisions for traffic of PDU sessions. For example, the SMF 110 may decide to select which one of the first UPF 118 and the second UPF 120 as a PSA for traffic.
  • the first UPF 116, second UPF 118 and third UPF 120 communicate with the SMF 110 via an interface N4, respectively.
  • the UPF 116 communicates with the second UPF 118 and third UPF 120 via an interface N9, respectively.
  • the second UPF 118 and third UPF 120 communicate with the first DN 122 and second DN 124 via an interface N6, respectively.
  • the network architecture 100 may also include other components, for example, other NFs not shown in FIG. 1.
  • Service (or application or the like) providers may deploy applications into one or more DNs, e.g., an edge DN which is a local part of the DN or local access of the DN, or a central DN.
  • the applications may be served by one or more EASs 126 deployed in a DN, e.g., the second DN 124.
  • Other DNs, e.g., the first DN 122 may also include one or more EAS.
  • Multiple EAS instances that host the same content or service may use a single IP address (anycast address) or different IP addresses.
  • the IP address of a suitable EAS (e.g., the one closest to the UE) will be discovered for the application or UE, so that the traffic can be locally routed to the EAS.
  • the traffic can be locally routed to the EAS via UL CL or BP mechanisms or a PDU session established directly with the local DN where the EAS is deployed.
  • the AF 106 can get the traffic routing information (TRI) for the deployed applications.
  • traffic routing control is very important for optimizing service latency, traffic routing path and user service experience.
  • GSMA OPG introduced the concept of Federation of Operator Platforms introduced in GSMA OPG. 02, to allow Application Providers to reach a wider geographical area and user base.
  • a use case defined in clause 3.3.5 of GSMA OPG. 02 is edge node sharing scenario.
  • the DNAI (s) in the serving network used to access the sharing node provided by each partner should be obtained to construct the EAS deployment information or the traffic influence information related to each sharing node.
  • 3GPP TS 23.700-48 has proposed several options for supporting edge sharing studied in KI#5, they all have defects and need improvement.
  • one option is related to a procedure of NEF-based EDI provision to serving operator, wherein the NEF of the sharing network translates the DNAI of the sharing network into the DNAI of the serving network to construct the EDI related to the sharing EAS, which is used in the serving network.
  • the relationship between DNAIs from different operators used for the DNAI translating is not appropriate to be exposed.
  • the relationship between DNAIs from different operators may be not appropriate to be used for DNAI translation because there may be specific configuration for the DNAI accessing specific DN (s) (e.g. specific DNAI may be configured to access the sharing network provided by the sharing PLMN) .
  • Another option is related to a procedure of AF obtaining target DNAI provided by NEF, wherein, the target DNAI can be obtained by the authorized AF by providing one or more of EAS IP address/IP address range and FQDN, and optionally DNN, S-NSSAI, and geographical area etc.
  • the IP address range for a sharing node may be mapped into a list of DNAIs.
  • the IP address range provided by different partners may have different DNAI mapping information based on the configuration, e.g. specific DNAI may be configured to access the sharing DN provided by the sharing PLMN.
  • the DNN (s) /S-NSSAI (s) (or DNN (s) and/or S-NSSAI (s) ) related to the same application service in the serving network (e.g. the DNN (s) and/or S-NSSAI (s) in the in the EHE provided by the serving operator) and sharing node may be different in the edge sharing cases.
  • some embodiments of the present application propose a technical solution of supporting edge sharing, which can at least solve the above issues.
  • a sharing node refers to an edge node providing the sharing EAS running the required edge application, which is deployed by another partner or operator other than the one whose network the UE accesses.
  • a sharing EAS is the edge application server within the sharing node.
  • the sharing node may also be called shared EHE deployed in the hosting network, or sharing edge platform.
  • the operator corresponding to the sharing node is named as sharing operator.
  • a serving network is the network providing the 3GPP network for the UE to access the application.
  • the operator corresponding to the serving networking is called serving operator.
  • Other terminologies may also be used to describe the edge sharing cases.
  • Some embodiments of the present application provide a method of supporting edge sharing, which can be performed by an NEF or the like.
  • the method may include receiving, from an AF or the like, a request including information related to edge sharing.
  • the request is various.
  • the request may be a request to query DNAI information.
  • the request includes EAS development information without DNAI or traffic influence information without DNAI, which implicitly requests updating the EAS development information and traffic influence information with proper DNAI information for edge sharing.
  • the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes, which indicates the partner (or network or operator) to which the information related to edge sharing corresponds or the one or more sharing nodes are provided.
  • the information related to edge sharing at least indicates one or more PLMN IDs for identifying to which partner one or more sharing nodes correspond.
  • the method may further include determining DNAI information for edge sharing based on the information related to edge sharing and mapping information between DNAI information and the information related to edge sharing.
  • the DNAI information can be one or more DNAIs, e.g., one DNAI or a list of DNAIs.
  • exemplary information related to edge sharing may also include an IP address range (or IP range) (e.g. IP address (es) of the EASs in the sharing node or the IP address ranges (IPv4 subnetwork (s) and/or IPv6 prefix (es) of the sharing node where the sharing EAS is deployed for) , or FQDN (e.g. one or more FQDNs which are supported within the sharing node) , or N6 traffic routing requirements for the sharing node (e.g. the tunnel end point in the sharing node) , or any combination of them.
  • IP range e.g. IP address (es) of the EASs in the sharing node or the IP address ranges (IPv4 subnetwork (s) and/or IPv6 prefix (es) of the sharing node where the sharing EAS is deployed for
  • FQDN e.g. one or more FQDNs which are supported within the sharing node
  • N6 traffic routing requirements for the sharing node e.g. the
  • the information related to edge sharing may further include one or more of the following related to the sharing node, e.g., geographical area, DNN, and S-NSSAI etc.
  • exemplary information related to edge sharing may include one or more FQDNs supported by a sharing node and geographical area of a specific application on the sharing node.
  • the related information related to edge sharing may be different or the same.
  • mapping information between DNAI information and the information related to edge sharing is provided for each sharing node with an identifier for identifying to which partner the sharing node corresponds, e.g., a PLMN ID.
  • mapping information between DNAI information and the information related to edge sharing is configured by operation administration and maintenance (OAM) for at least one of NEF or unified data repository (UDR) etc. in each operator. Based on the deployment and configuration of each operator, specific or different DNAI (s) may be used to access different partner (s) .
  • OAM operation administration and maintenance
  • mapping information between DNAI information and the information related to edge sharing is also various. That is, DNAI information for edge sharing can be determined in various manners.
  • Exemplary mapping information may be between sharing node IP address range, e.g., an EAS IP address range and the DNAI information.
  • the mapping information between EAS IP address range and the DNAI information is configured, wherein the EAS IP address range is that of each sharing node and the DNAI information is the corresponding DNAI (s) (e.g., one DNAI or a list of DNAIs) of the serving network to access each sharing node.
  • the EAS IP address range may be split into several corresponding subranges for each DNAI.
  • the EAS IP range may be the IP range of the application server in the sharing node for a specific FQDN or multiple FQDNs or all the applications deployed within the sharing node.
  • N6 traffic routing requirements are N6 traffic routing information, e.g., ipv4 address, ipv6 address or port number (e.g., ipv4 address, ipv6 address or port number of the tunnel end point in the sharing node) etc.
  • the mapping information between N6 traffic routing requirements and the DNAI information is configured by the OAM for NEF and/or UDR, wherein the N6 traffic routing requirements are for each sharing node, e.g. one or a list of ipv4 addresses, ipv6 addresses or port numbers of the tunnel end point in the sharing node.
  • the DNAI information is the corresponding one or more DNAIs (e.g., one DNAI or a list of DNAIs) of the serving network to access each sharing node.
  • the mapping information is between the DNAI information and a combination of various information or parameters.
  • exemplary mapping information may be between the DNAI (s) and a combination of FQDN and geographical area etc.
  • the mapping information between DNAI information and the FQDN (s) and geographical area is configured for each sharing node.
  • exemplary mapping information may be between the DNAI (s) and a combination of EAS IP address range and required FQDN (s) .
  • DNAI information e.g., DNAI information for edge sharing used in EAS deployment information (EDI) (Case 1) and DNAI information for edge sharing used in traffic offload policy (Case 2) .
  • EDI EAS deployment information
  • Case 2 DNAI information for edge sharing used in traffic offload policy
  • the illustrated embodiments mainly focus on how to obtain the DNAI information for creating or updating EAS deployment information or traffic influence information, so that based on the EAS deployment information or traffic influence information, the EAS can be discovered properly or the traffic can be routed properly, and thus some prior or common steps or details are omitted herein for simplicity and clearness.
  • the AF will send the EAS deployment information for edge sharing to the serving network.
  • the AF may belong to the sharing operator or belong to the serving operator. If the AF belongs to the sharing operator (e.g., the NEF or AF provided by the sharing operator) , the AF will act as the 3rd party AF to the serving network and is authorized to interact directly with the serving network. If the AF belongs to the serving operator, the AF is part of the serving network and may be configured with or interact with the sharing node to retrieve the related information for the sharing node.
  • the EAS deployment information indicates how edge services are deployed in each local part of the DN, and the description of EAS deployment information is shown in Table 6.2.3.4-1 in TS 38.23548, which is reproduced below.
  • DNAI information is used to construct the related EAS deployment information and sent to the SMF of the serving network.
  • DNAI information for edge sharing can be obtained for each sharing node by the AF.
  • the AF may be required to have the information of DNS server information for at least one of: each IP address range (or sub-range) or N6 traffic routing requirements, which depends on which information related to edge sharing is needed.
  • FIG. 2 illustrates an exemplary procedure of supporting edge sharing in Case 1 according to some embodiments of the present application.
  • the AF before invoking an edge node development create operation or the like related to sharing nodes, e.g. before invoking an Nnef_EASDeployment_Create service operation with EAS deployment information related to the sharing nodes, the AF first will obtain the DNAI information for edge sharing via step 201.
  • the AF may transmit a request (e.g., an exemplary first request) to the NEF or the like of the serving network to query the DNAI information for edge sharing, e.g., by invoking an Nnef_DNAI_Query service operation similar to that provided in TS 23.700-48 for the procedure of AF obtaining target DNAI.
  • the request at least includes ID (s) of one or more sharing partners to indicate the partner to which the related information corresponds, e.g., one or more PLMN IDs.
  • Each sharing node is associated with a sharing partner. Different sharing nodes may belong to the same or different sharing partner.
  • the request may also include the information related to edge sharing as stated above, e.g., IP address range information, and/or N6 traffic routing requirements, and/or FQDN (s) for each sharing node corresponding to each sharing partner.
  • the information related to edge sharing may also optionally include one or more of: geographical area, DNN (s) , and S-NSSAI (s) etc. information or parameter (s) for each sharing node.
  • the NEF will obtain the required DNAI information based on related mapping information between DNAI information and the information related to edge sharing, e.g., the mapping information configured for the NEF or UDR by the OAM as stated above. Similar to the solution for AF obtaining target DNAI provided by NEF proposed in 3GPP TR 23.700-48, the NEF may determine the related mapping directly according to local configuration, or based on the related mapping information obtained from UDR.
  • the NEF (or via UDR) will obtain the DNAI information for the sharing node, based on the mapping information between the EAS IP address range and the DNAI information.
  • the DNAI information is the corresponding one or more DNAIs of the serving network to access each sharing node.
  • the EAS IP address range may be split into several corresponding subranges for each DNAI. That is, each DNAI is per IP address range or subrange.
  • FQDN (s) , geographical area, and/or DNN (s) /S-NSSAI (s) may be used in combination with IP address range information.
  • the NEF (or via UDR) will obtain the DNAI information for the sharing node based on the mapping information between the N6 traffic routing requirements and the DNAI information.
  • the IP address range or mapping information between DNAI information and IP address range is not available.
  • some applications may be only deployed in some specific areas or the DNAI is configured per geographical area.
  • the mapping information between the FQDN and geographical area and the DNAI information for each sharing node may be configured for the NEF and/or UDR, e.g., by the OAM.
  • the NEF (or via UDR) may obtain the DNAI information for the sharing node based on the mapping with the FQDN and geographical area.
  • the DNN for the same application in the sharing node and the serving network may be different, and the different DNNs will be mapped too. It is similar to S-NSSAI.
  • an application also referred to as "appx”
  • it is deployed in the DNN (and/or S-NSSAI) in the sharing operator’s data network and also in the DNN (and/or S-NSSAI) in the serving operator’s data network.
  • the DNN (s) /S-NSSAI (s) in the sharing node and the DNN (s) /S-NSSAI (s) in serving network for the same applications are different, the DNN (s) /S-NSSAI (s) in serving network will be shared to the sharing operator to access the appx when the related condition is triggered (for example, the service agreement among the sharing operator and the serving operator is reached) .
  • the NEF will send a response, e.g., an Nnef_DNAI_Query response to the AF, which at least includes the determined DNAI information, e.g., a list of DNAI per IP address range determined by the NEF and other related information if necessary (e.g., the DNN (s) /S-NSSAI (s) for an application in the serving network) .
  • a response e.g., an Nnef_DNAI_Query response to the AF, which at least includes the determined DNAI information, e.g., a list of DNAI per IP address range determined by the NEF and other related information if necessary (e.g., the DNN (s) /S-NSSAI (s) for an application in the serving network) .
  • the AF will transmit a request of creating EAS development information (e.g., an exemplary second request) to the NEF of the serving network with EAS deployment information related to the sharing node, wherein, the partner ID corresponding to the EAS development information (e.g., PLMN ID of the sharing node) and the DNAI information received in step 203 will be included.
  • the AF may invoke an Nnef_EAS_Deployment_Create service operation with the PLMN ID and the DNAI information received in step 203.
  • the second request may also include the DNN/S-NSSAI in the serving network.
  • priority information of the EAS deployment information for each sharing node may be included in the second request too, e.g., in the case that there are multiple sharing nodes available which are provided by different sharing partners, e.g., different PLMNs.
  • the priority information indicates priority to choose one sharing node.
  • the priority information may be suggested by the AF based on its own configuration and/or service agreement among the sharing partner (s) and the serving network (s) , e.g., sharing PLMN (s) and the serving PLMN (s) .
  • the priority information may be configured in the serving network, and the related priority is decided by the serving network during the related service procedure based on local configuration, e.g., a UE requesting access a sharing node.
  • steps 207 to 215 are similar to the legacy, and thus will not be illustrated in detail.
  • the NEF will invoke the Nudr_DM_Create service operation to store the EAS deployment information related to the sharing node to the UDR.
  • the NEF will receive the response, e.g., receiving an Nudr_DM_Create response.
  • the NEF will transmit a response to the AF, e.g., by an Nnef_EASDeployment_Create response.
  • the SMF will receive the EAS deployment information similar to that defined in 6.2.3.4.3 of TS23.548.
  • the EAS deployment information will be used for EAS discovery using EAS discovery function (EASDF) among UE, UPF, DNS server, EASDF and SMF as defined in 6.2.3 of TS23.548, wherein the received priority information may be used by the SMF for considering which EAS deployment information to be used for server discovery.
  • EASDF EAS discovery function
  • the AF may send the information related to edge sharing in EAS deployment information for edge sharing without the DNAI information, and the NEF of the serving network will map the information related to edge sharing to required DNAI information and add the required DNAI information into the EAS deployment information received from the AF, so that the EAS deployment information from the AF will be properly updated by the NEF.
  • FIG. 3 illustrates an exemplary procedure of supporting edge sharing in Case 1 according to some other embodiments of the present application.
  • the DNAI information for edge sharing will not be obtained as in step 201 and step 203.
  • the AF will transmit a request (e.g., an exemplary first request) to the NEF of the serving network by invoking an Nnef_EASDeployment_Create service operation, including EAS deployment information related to the sharing node corresponding to a sharing partner, wherein, the partner ID corresponding to the EAS deployment information (e.g., PLMN ID of the sharing node) will also be included while no DNAI information will be included.
  • a request e.g., an exemplary first request
  • the partner ID corresponding to the EAS deployment information e.g., PLMN ID of the sharing node
  • the AF may transmit EAS deployment information without DNAI information via invoking an Nnef_EASDeployment_Create service operation to the NEF of the serving operator.
  • the EAS deployment information may include one or more information or parameters as illustrated in Table 6.2.3.4-1 excluding DNAI (s) , e.g., including DNN, S-NSSAI, FQDN (s) , DNAI (s) , DNS server information, and/or EAS IP address range information etc., which can be used as the information related to edge sharing.
  • priority information of the EAS deployment information for each sharing node may be included too, e.g., in the case that there are multiple sharing nodes available which are provided by different sharing partners, e.g., different PLMNs.
  • the NEF will obtain the DNAI information, e.g., a supported DNAI list based on the information related to edge sharing included in the EAS deployment information, e.g., IP address range and/or N6 traffic routing information etc.
  • the NEF will obtain the DNAI information further based on mapping with at least one of FQDN, DNN, S-NSSAI, or geographical area etc.
  • the NEF will map the received DNN (s) /S-NSSAI (s) in the sharing node to the corresponding DNN (s) /S-NSSAI (s) in the serving network. More details refer to the mapping illustrated in FIG. 2, and will not repeat.
  • the NEF will update the received EAS deployment information based on the determined DNAI information and other related information, e.g., the mapped DNN (s) /S-NSSAI (s) for the same application in the serving network etc. For example, the NEF will add (or insert) the supported DNAI information, update the IP address range information with the supported DNAI information, and update the DNS server information with the supported DNAI information etc.
  • the NEF will add (or insert) the supported DNAI information, update the IP address range information with the supported DNAI information, and update the DNS server information with the supported DNAI information etc.
  • steps 207-215 the following operations in the serving network, e.g., steps 305 to 313 are similar to the legacy, and thus will not be illustrated herein.
  • the AF will send traffic influence information, e.g., the AF influence traffic routing information for the edge sharing to the serving network.
  • traffic influence information or traffic routing information or AF influence traffic routing information is the information included in the AF request or AF update of AF influence on traffic routing procedure.
  • the AF may belong to the sharing operator or belong to the serving operator. If the AF belongs to the sharing operator (e.g., the NEF or AF provided by the sharing operator) , the AF will act as the 3rd party AF to the serving network and is authorized to interact directly with the serving network. If the AF belongs to the serving operator, the AF is a part of the serving network and may be configured with or interact with the sharing node to retrieve the related information for the sharing node.
  • exemplary traffic influence operation includes but not limited to: an Nnef_Trafficinfluence_Create servcie operation, or an Nnef_Trafficinfluence_Update service operation.
  • the AF may transmit a request (e.g., an exemplary first request) to the NEF or the like of the serving network to query the DNAI information for edge sharing, e.g., by invoking an Nnef_DNAI_Query service operation similar to that provided in TS 23.700-48 for the procedure of AF obtaining target DNAI.
  • the request at least includes ID (s) of one or more sharing partners to indicate the partner to which the related information corresponds, e.g., one or more PLMN IDs.
  • Each sharing node is associated with a sharing partner. Different sharing nodes may belong to the same or different sharing partner.
  • the request may also include the information related to edge sharing as stated above, e.g., IP address range information, and/or FQDN, and/or N6 traffic routing requirements for each sharing node corresponding to each sharing partner.
  • the information related to edge sharing may also optionally include one or more of: geographical area, DNN (s) , and S-NSSAI (s) etc. information or parameter (s) for each sharing node.
  • the NEF will obtain the required DNAI information based on related mapping information between DNAI information and the information related to edge sharing, e.g., the mapping information configured for the NEF or UDR by the OAM as stated above. Similar to the solution for AF obtaining target DNAI provided by NEF proposed in 3GPP TR 23.700-48, the NEF may determine the related mapping directly according to local configuration, or based on the related mapping information obtained from UDR.
  • the NEF may obtain the DNAI information for the sharing node, based on the mapping information between the EAS IP address range and the DNAI information.
  • the DNAI information is the corresponding one or more DNAIs of the serving network to access each sharing node.
  • the EAS IP address range may be split into several corresponding subranges for each DNAI. That is, each DNAI is per IP address range or subrange.
  • FQDN (s) , geographical area, and/or DNN (s) /S-NSSAI (s) may be used in combination with IP address range information.
  • the NEF may obtain the DNAI information for the sharing node based on the mapping information between the N6 traffic routing requirements and the DNAI information.
  • the IP address range or mapping information between DNAI information and IP address range may be unavailable.
  • some applications may be only deployed in some specific areas or the DNAI is configured per geographical area.
  • the mapping information between the FQDN and geographical area and the DNAI information for each sharing node may be configured for the NEF and/or UDR, e.g., by the OAM.
  • the NEF (or via UDR) may obtain the DNAI information for the sharing node based on the mapping with the FQDN and geographical area.
  • the DNN for the same application in the sharing node and the serving network may be different, and the different DNNs will be mapped too. It is similar to S-NSSAI. For example, for an application, it is deployed in the DNN (and/or S-NSSAI) in the sharing operator’s data network and also in the DNN (and/or S-NSSAI) in the serving operator’s data network.
  • the DNN (s) /S-NSSAI (s) in sharing node and the DNN (s) /S-NSSAI (s) in serving network for the same application are different, the DNN (s) /S-NSSAI (s) in serving network will be shared to the sharing operator to access the same application when the related condition is triggered.
  • the NEF will send a response, e.g., an Nnef_DNAI_Query response to the AF, which at least includes the determined DNAI information, e.g., a list of DNAI per IP address range and other related information if necessary, e.g., the DNN (s) /S-NSSAI (s) in the serving network.
  • a response e.g., an Nnef_DNAI_Query response to the AF, which at least includes the determined DNAI information, e.g., a list of DNAI per IP address range and other related information if necessary, e.g., the DNN (s) /S-NSSAI (s) in the serving network.
  • the AF will transmit a request (e.g., exemplary second request) related to traffic influence operation to the NEF of the serving network with traffic influence information, wherein, the partner ID corresponding to the traffic routing information (e.g., PLMN ID of the sharing node) and the DNAI information received in step 403 will be included.
  • the second request may also include the DNN (S) /S-NSSAI (S) of the serving network for the application.
  • the AF may transmit an Nnef_Traffic influence_Create request by invoking an Nnef_Trafficinfluence_Create service operation similar to that provided in clause 4.3.6 of 3GPP TS 23.502.
  • priority information of traffic influence information of each sharing node may be included in the traffic influence information too, e.g., in the case that there are multiple sharing nodes available which are provided by different sharing partners, e.g., different PLMNs.
  • the priority information indicates priority to choose one sharing node.
  • the priority information may be suggested by the AF based on its own configuration and/or service agreements among the sharing partner (s) and the serving network (s) , e.g., sharing PLMN (s) and the serving PLMN (s) .
  • the priority information may be configured in the serving network, and the related priority is decided by the serving network during the related service procedure based on local configuration, e.g., a UE requesting access a sharing node.
  • steps 407 to 413 are similar to the legacy, and thus will not be illustrated in detail.
  • the NEF will invoke the Nudr_DM_Create service operation to store the traffic influence related to the sharing node to the UDR.
  • the NEF will receive the response, e.g., receiving an Nudr_DM_Create response.
  • the NEF will respond to the AF, e.g., by an Nnef_Traffic influence_Create response.
  • the SMF will receive traffic offload policy including the AF influence traffic routing information via policy and charging control (PCC) rule (the path for transmitting the related information is UDR-PCF-SMF) similar to that defined in clause 4.3.6 of TS23.502, wherein the received priority information may be used by the SMF for considering which traffic influence information used for routing traffic.
  • PCC policy and charging control
  • the AF may send the information related to edge sharing in the traffic influence information without the DNAI information.
  • the NEF of the serving network will map the information related to edge sharing into required DNAI information and add the required DNAI information into the traffic influence information received from the AF, so that the traffic influence information from the AF will be properly updated by the NEF.
  • An exemplary traffic influence information is AF influence traffic routing information, which can be created, or updated or deleted as defined in clause 4.3.6 of TS 23.502.
  • FIG. 5 illustrates an exemplary procedure of supporting edge sharing in Case 2 according to some other embodiments of the present application.
  • the DNAI information for edge sharing will not be obtained as in steps 401 and 403.
  • the AF will transmit a request (e.g., exemplary first request) related to traffic routing operation to the NEF of the serving network with traffic influence information, wherein, the partner ID corresponding to the traffic influence information (e.g., PLMN ID of the sharing node) will also be included while no the DNAI information will be included.
  • the AF may transmit a Nnef_Trafficeinfluence_Create request by invoking and Nnef_Traffic influence_Create service operation with AF influence traffic routing information related to the sharing node corresponding to the sharing operator.
  • the Nnef_Traffic influence_Create request may include one or more information or parameters for traffic routing excluding DNAI (s) , e.g., DNN, S-NSSAI, FQDN (s) , DNAI (s) , DNS Server Information, and/or EAS IP address range Information etc., which can be used as the information related to edge sharing.
  • DNAI e.g., DNN, S-NSSAI, FQDN (s) , DNAI (s) , DNS Server Information, and/or EAS IP address range Information etc.
  • priority information of the traffic influence information may also be included in the traffic influence information, e.g., in the case that there are multiple sharing nodes available which are provided by different sharing partners, e.g., different PLMNs.
  • the NEF will obtain the DNAI information, e.g., a supported DNAI list based on the information related to edge sharing included in the traffic routing information, e.g., IP address range and/or N6 traffic routing information etc.
  • the NEF will obtain the DNAI information further based on mapping with at least one of FQDN, DNN, S-NSSAI, or geographical area etc.
  • the NEF will map the received DNN (s) /S-NSSAI (s) in the sharing node to the corresponding DNN (s) /S-NSSAI (s) in the serving network. More details refer to the mapping illustrated in FIG. 2, and will not repeat.
  • the NEF will update the received traffic influence information based on the determined DNAI information and other related information, e.g., the mapped DNN (s) /S-NSSAI (s) for the same application in the serving network etc. For example, the NEF will add (or insert) the supported DNAI information into the traffic influence information received from the AF, and update the N6 traffic routing requirements with corresponding DNAI (s) , so that the traffic influence information from the AF will be properly updated by the NEF etc.
  • the NEF will add (or insert) the supported DNAI information into the traffic influence information received from the AF, and update the N6 traffic routing requirements with corresponding DNAI (s) , so that the traffic influence information from the AF will be properly updated by the NEF etc.
  • steps 505 to 511 are similar to the legacy, and thus will not be illustrated herein.
  • some embodiments of the present application also provide an apparatus of supporting edge sharing.
  • FIG. 6 is a block diagram of an apparatus of supporting edge sharing according to some embodiments of the present application.
  • the apparatus 600 may include at least one non-transitory computer-readable medium 601, at least one receiving circuitry 602, at least one transmitting circuitry 604, and at least one processor 606 coupled to the non-transitory computer-readable medium 601, the receiving circuitry 602 and the transmitting circuitry 604.
  • the apparatus 600 may be a NEF or AF configured to perform a method illustrated in the above or the like.
  • the at least one processor 606, transmitting circuitry 604, and receiving circuitry 602 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated.
  • the receiving circuitry 602 and the transmitting circuitry 604 can be combined into a single device, such as a transceiver.
  • the processor 606 may be a central processing unit (CPU) , a digital signaling processing (DSP) , a microprocessor etc.
  • the apparatus 600 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 601 may have stored thereon computer-executable instructions to cause the processor 606 to implement the method with respect to the NEF or AF as described above.
  • the computer-executable instructions when executed, cause the processor 606 interacting with receiving circuitry 602 and transmitting circuitry 604, so as to perform the steps with respect to an NEF or AF as depicted above.
  • FIG. 7 illustrates a block diagram of an apparatus 700 of supporting edge sharing according to some other embodiments of the present application.
  • the apparatus 700 may include at least one processor 702 and at least one transceiver 704.
  • the transceiver 704 may include at least one separate receiving circuitry 706 and transmitting circuitry 708, or at least one integrated receiving circuitry 706 and transmitting circuitry 708.
  • the at least one processor 702 may be a CPU, a DSP, a microprocessor etc.
  • the processor when the apparatus 700 is an NEF, the processor is configured to: receive, from an NF, e.g., an AF, a first request including information related to edge sharing, wherein the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes; and determine DNAI information for edge sharing based on the information related to edge sharing and mapping information between DNAI information and the information related to edge sharing.
  • an NF e.g., an AF
  • the processor may be configured to: transmit, to an NF, e.g., an NEF, a first request including information related to edge sharing, wherein the information related to edge sharing at least indicates one or more identifiers related to one or more sharing nodes; and receive a response at least made based on the information related to edge sharing.
  • an NF e.g., an NEF
  • the method according to embodiments of the present application can also be implemented on a programmed processor.
  • the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application.
  • an embodiment of the present application provides an apparatus including a processor and a memory. Computer programmable instructions for implementing a method stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method.
  • the method may be a method as stated above or other method according to an embodiment of the present application.
  • An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions.
  • the instructions are preferably executed by computer-executable components preferably integrated with a network security system.
  • the non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as random access memory (RAMs) , read only memory (ROMs) , flash memory, electrically erasable programmable read only memory (EEPROMs) , optical storage devices (compact disc (CD) or digital video disc (DVD) ) , hard drives, floppy drives, or any suitable device.
  • the computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
  • an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein.
  • the computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil permettant de prendre en charge une périphérie. Un appareil donné à titre d'exemple, par exemple une NEF, peut comprendre : un émetteur-récepteur ; et un processeur couplé à l'émetteur-récepteur, le processeur étant configuré pour : recevoir, d'une fonction réseau (NF), une première demande comprenant des informations relatives au partage de périphérie, les informations relatives au partage de périphérie indiquant au moins un ou plusieurs identifiants associés à un ou plusieurs nœuds de partage ; et déterminer des informations DNAI pour un partage de périphérie d'après les informations relatives au partage de périphérie et les informations de mappage entre les informations DNAI et les informations relatives au partage de périphérie.
PCT/CN2022/131567 2022-11-11 2022-11-11 Procédé et appareil de prise en charge de périphérie WO2024073921A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/131567 WO2024073921A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de prise en charge de périphérie

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/131567 WO2024073921A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de prise en charge de périphérie

Publications (1)

Publication Number Publication Date
WO2024073921A1 true WO2024073921A1 (fr) 2024-04-11

Family

ID=90607583

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/131567 WO2024073921A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de prise en charge de périphérie

Country Status (1)

Country Link
WO (1) WO2024073921A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103202069A (zh) * 2010-11-12 2013-07-10 高通股份有限公司 用于请求和共享网络性能信息的方法和装置
CN104429027A (zh) * 2012-07-09 2015-03-18 阿尔卡特朗讯 用于在电信网络中建立链路分集业务路径的方法和相关设备
US20180103013A1 (en) * 2016-10-11 2018-04-12 Fujitsu Limited Edge server, encryption communication control method thereof, and terminal
CN112532667A (zh) * 2019-09-19 2021-03-19 贵州白山云科技股份有限公司 一种网络边缘计算方法、装置及介质
CN114221959A (zh) * 2021-12-14 2022-03-22 中国电信股份有限公司 服务共享方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103202069A (zh) * 2010-11-12 2013-07-10 高通股份有限公司 用于请求和共享网络性能信息的方法和装置
CN104429027A (zh) * 2012-07-09 2015-03-18 阿尔卡特朗讯 用于在电信网络中建立链路分集业务路径的方法和相关设备
US20180103013A1 (en) * 2016-10-11 2018-04-12 Fujitsu Limited Edge server, encryption communication control method thereof, and terminal
CN112532667A (zh) * 2019-09-19 2021-03-19 贵州白山云科技股份有限公司 一种网络边缘计算方法、装置及介质
CN114221959A (zh) * 2021-12-14 2022-03-22 中国电信股份有限公司 服务共享方法、装置和系统

Similar Documents

Publication Publication Date Title
US11924641B2 (en) Security management for service access in a communication system
EP4024817A1 (fr) Procédé de détermination de serveur de système de nom de domaine, procédé et appareil de traitement de requête, et système
US11729137B2 (en) Method and device for edge application server discovery
US20220394453A1 (en) Methods, systems, and computer readable media for using service communications proxy (scp) or security edge protection proxy (sepp) to apply or override preferred-locality attribute during network function (nf) discovery
JP2011512715A (ja) ネットワーク・リソースをプールするための方法および装置
EP4298815A1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour atténuer un suivi de localisation et des attaques par déni de service (dos) qui utilisent un service de localisation de fonction d'accès et de gestion de mobilité (amf)
US11888946B2 (en) Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests
US11871309B2 (en) Methods, systems, and computer readable media for network function discovery using preferred-locality information
US11930083B2 (en) Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations
CN114258667A (zh) 用于获得ip地址的方法和装置
JP2024502607A (ja) 加入者識別子の漏洩を防止するための方法、システム、およびコンピュータ可読媒体
JP2020174387A (ja) 訪問国におけるｅＰＤＧの選択処理の機能強化
WO2021253301A1 (fr) Procédé et appareil de fourniture d'informations de découverte de serveur
JP2024509941A (ja) セキュリティエッジ保護プロキシ（ｓｅｐｐ）における代行承認のための方法、システム、およびコンピュータ可読媒体
US20220225074A1 (en) Mobile communication network arrangement and method for operating a mobile communication network arrangement to support inter-core network roaming
US11652782B1 (en) Methods, systems, and computer readable media for dynamically updating domain name system (DNS) records from registered network function (NF) profile information
JP2024509940A (ja) サービス通信プロキシ（ｓｃｐ）における代行承認のための方法、システム、およびコンピュータ可読媒体
AU2021247720A1 (en) Communication method and apparatus
WO2023229855A1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour utiliser des attributs de service de fonction de réseau (nf) associés à des producteurs de service nf enregistrés dans un réseau hiérarchique
WO2024073921A1 (fr) Procédé et appareil de prise en charge de périphérie
US20230217355A1 (en) METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR COMMUNICATING DELEGATED NETWORK FUNCTION (NF) DISCOVERY RESULTS BETWEEN SERVICE COMMUNICATION PROXIES (SCPs) AND USING THE DELEGATED NF DISCOVERY RESULTS FOR ALTERNATE ROUTING
CN117546453A (zh) 用于基于服务质量参数建立网络切片中的消息优先级的方法、系统和计算机可读介质
WO2017147840A1 (fr) Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter
WO2024065793A1 (fr) Procédé et appareil de sélection d'une fonction de réseau de gestion de session
WO2021204292A1 (fr) Procédé, appareil et système de découverte d'application, et support de stockage informatique