WO2023141827A1 - Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple - Google Patents

Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple Download PDF

Info

Publication number
WO2023141827A1
WO2023141827A1 PCT/CN2022/074090 CN2022074090W WO2023141827A1 WO 2023141827 A1 WO2023141827 A1 WO 2023141827A1 CN 2022074090 W CN2022074090 W CN 2022074090W WO 2023141827 A1 WO2023141827 A1 WO 2023141827A1
Authority
WO
WIPO (PCT)
Prior art keywords
eas
interest
area
client devices
instance
Prior art date
Application number
PCT/CN2022/074090
Other languages
English (en)
Inventor
Siva VAKEESAR
Xinpeng WEI
Ali HAMIDIAN
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to PCT/CN2022/074090 priority Critical patent/WO2023141827A1/fr
Publication of WO2023141827A1 publication Critical patent/WO2023141827A1/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/14—Session management
    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the invention is related to area of interest-specific information exchanged between a session management function and an edge application server (EAS) discovery function. Furthermore, the invention also relates to corresponding methods and a computer program.
  • EAS edge application server
  • MEC multi-access edge computing
  • UE user equipment
  • MEC allows mobile network operators and 3rd party service providers to host required computing server functionalities and resources close to the current point of attachment of a UE for the purpose of achieving quick offloading of computing tasks, while conserving UE battery energy.
  • Another benefit of MEC is facilitating collaborations among multiple users having to timely accomplish a common task.
  • EAS edge application servers
  • V2X vehicle-to-everything
  • AR augmented reality
  • XR extended reality
  • MEC multi-player gaming
  • NMR extended reality
  • Network latency and data rate play critical roles in delivering uninterrupted gaming experience.
  • QoS quality of service
  • Battery capability of the mobile device is another indispensable consideration because running AR applications requires intensive use of computing resources which results in massive battery consumption. MEC can alleviate these pains for players who are located close to each other.
  • An objective of examples of the invention is to provide a solution which mitigates or solves the drawbacks and problems of conventional solutions.
  • Another objective of examples of the invention is to provide a solution to facilitate application level collaboration among client devices in a given area to achieve a common goal and to enhance QoS experience by, in particular, bringing down end-to-end latency.
  • the above mentioned and other objectives are achieved with a session management function for a communication system, the session management function being configured to
  • the area of interest comprises a plurality of client devices associated with a same application service
  • the first information indicates: an identity of a single EAS instance configured to serve the plurality of client devices in the area of interest, individual identities of the plurality of client devices and a dedicated data network access identifier;
  • the configuration message comprising a second information for the area of interest, wherein the second information indicates: the identity of the single EAS instance and the individual identities of the plurality of client devices.
  • An advantage of the session management function according to the first aspect is that it is able to dynamically get MEC resource information or EAS deployment information provisioned that is specific to a given application service used by two or more client devices that are located in a given area of interests for the purpose of facilitating application level collaboration among all involved client devices.
  • Such dynamic provisioning of EAS deployment information is preferable to static configuration in case EAS load changes fairly dynamically.
  • the configuration message further indicates an instruction for the EAS discovery function to respond to a domain name system, DNS, query from a client device among the plurality of client devices with the identity of the single EAS instance.
  • DNS domain name system
  • An advantage with this implementation form is that the session management function can ensure that application traffic generated by all client devices that use the same application service and are located in a given area of interest gets processed in a single EAS instance.
  • the single EAS instance can thereby take unified actions for all the client devices.
  • the identity of the single EAS instance is an IP address of the single EAS instance.
  • An advantage with this implementation form is that it is easy for any of those identified client devices to connect to the identified EAS instance using an IP address that is an important part of a uniform resource identifier (URI) .
  • URI uniform resource identifier
  • the first information further indicates a valid time period during which the single EAS instance is configured to serve the plurality of client devices in the area of interest.
  • An advantage with this implementation form is that it may be possible that after a time duration the chosen EAS instance may not be optimal. By exchanging a valid time period, the use of a non-optimal EAS instance can be avoided.
  • the first information indicates a group identity for the plurality of client devices; and the session management function is further configured to
  • the identity of the single EAS instance derive the identity of the single EAS instance, the individual identities of the plurality of client devices and the dedicated data network access identifier based on the group identity for the plurality of client devices.
  • An advantage with this implementation form is that the session management function can use the group identity as a key to obtain identities of client devices that are associated with such a group and an EAS instance that can optimally serve those identified client devices. Such an approach can minimize unnecessary data transfer and hence save bandwidth and power.
  • Related data can be fetched from an unified data management/repository (UDM/UDR) .
  • UDM/UDR unified data management/repository
  • the plurality of client devices belongs to two or more public land mobile networks, PLMNs.
  • An advantage with this implementation form is that in this way application level collaboration is made possible among client devices across PLMN borders.
  • the application service is associated with the same data network name, DNN, and/or the same single-network slice selection assistance information, S-NSSAI.
  • An advantage with this implementation form is that it will help the 5G core (5GC) network choose appropriate network functions (NFs) that can handle given application traffic that is to be identified by S-NSSAI within the 5GC and route such traffic to the identified data network.
  • NFs network functions
  • obtaining the first information comprises:
  • the subscribe notification message comprising the first information.
  • An advantage with this implementation form is that the session management function subscribes to get notified when EAS deployment information that is specific to a given area of interests and to a given application service changes.
  • the EAS deployment information in the session management function can thereby be kept up-to-date.
  • the session management function is further configured to
  • An advantage with this implementation form is that when getting notified of EAS deployment information change, the session management function immediately passes such information to the EAS discovery function, so that the EAS discovery function can act accordingly.
  • the session management function is further configured to
  • An advantage with this implementation form is that the data network access identifier can be used as an important criterion by the session management function to identify an appropriate user plane function that can destine application traffic originating from involved client devices running a given application service.
  • the session management function is further configured to
  • the PDU session establishment accept or the PDU session modification command/acknowledgement instructing the client device to clear its DNS cache when the client device moves into another area of interest.
  • An advantage with this implementation form is that the session management ensures that client devices that move from one area of interest to another area of interest use an EAS instance that is more appropriate to a current location.
  • an EAS discovery function for a communication system the EAS discovery function being configured to
  • the configuration message comprising a second information for an area of interest, wherein the area of interest comprises a plurality of client devices associated with a same application service, and wherein the second information indicates: an identity of a single EAS instance configured to serve the plurality of client devices in the area of interest and individual identities of the plurality of client devices.
  • An advantage of the EAS discovery function according to the second aspect is that the EAS discovery function knows how to connect one or more client devices that are located in a given area of interests to a given EAS instance. Thereby, facilitating application level collaboration among the client devices in the area of interest for the purpose of enhance user QoS experience by, for example, bringing down end-to-end latency.
  • the EAS configuration message further indicates an instruction to respond to a DNS query from a client device among the plurality of client device with the identity of the single EAS instance; and the EAS discovery function is further configured to
  • the DNS response indicating the identity of the single EAS instance.
  • An advantage with this implementation form is that the EAS discovery function learns how to respond immediately to a DNS query triggered by any of those identified client devices without having to further forward those queries to other DNS servers. Thereby, ensuring that all involved client devices will make use of the same EAS instance.
  • the identity of the single EAS instance is an IP address of the single EAS instance.
  • An advantage with this implementation form is that it is easy for those client devices to connect to the identified EAS instance using an IP address that is an important part of a uniform resource identifier (URI) .
  • URI uniform resource identifier
  • the second information further indicates a valid time period during which the single EAS instance is configured to serve the plurality of client devices in the area of interest.
  • An advantage with this implementation form is that it may be possible that after a time duration the chosen EAS instance may not be optimal. By exchanging the valid time period, the use of a non-optimal EAS instance can be avoided.
  • the second information indicates a group identity of the plurality of client devices; and wherein the EAS discovery function further is configured to
  • EAS discovery function can use the group identity as a key to obtain identities of client devices that are associated with such a group and the EAS instance that can optimally serve those identified client devices. Such an approach can minimize unnecessary data transfer and hence save bandwidth and power.
  • Related data can be fetched from an unified data management/repository (UDM/UDR) .
  • UDM/UDR unified data management/repository
  • the plurality of client devices belongs to two or more PLMNs.
  • An advantage with this implementation form is that in this way application level collaboration is made possible among client devices across PLMN borders.
  • the application service is associated with the same DNN and/or the same S-NSSAI.
  • An advantage with this implementation form is that it will help the 5GC choose appropriate network functions (NFs) that can handle given application traffic that is to be identified by S-NSSAI within the 5GC and route such traffic to the identified data network.
  • NFs network functions
  • the above mentioned and other objectives are achieved with a method for a session management function, the method comprises
  • the area of interest comprises a plurality of client devices associated with a same application service
  • the first information indicates: an identity of a single EAS instance configured to serve the plurality of client devices in the area of interest, individual identities of the plurality of client devices and a dedicated data network access identifier;
  • the configuration message comprising a second information for the area of interest, wherein the second information indicates: the identity of the single EAS instance and the individual identities of the plurality of client devices.
  • an implementation form of the method comprises the feature (s) of the corresponding implementation form of the session management function.
  • the above mentioned and other objectives are achieved with a method for an EAS discovery function, the method comprises
  • the configuration message comprising a second information for an area of interest, wherein the area of interest comprises a plurality of client devices associated with a same application service, and wherein the second information indicates: an identity of a single EAS instance configured to serve the plurality of client devices in the area of interest and individual identities of the plurality of client devices.
  • an implementation form of the method comprises the feature (s) of the corresponding implementation form of the EAS discovery function.
  • Examples of the invention also relates to a computer program, characterized in program code, which when run by at least one processor causes the at least one processor to execute any method according to examples of the invention.
  • examples of the invention also relate to a computer program product comprising a computer readable medium and the mentioned computer program, wherein the computer program is included in the computer readable medium, and may comprises one or more from the group of: read-only memory (ROM) , programmable ROM (PROM) , erasable PROM (EPROM) , flash memory, electrically erasable PROM (EEPROM) , hard disk drive, etc.
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable PROM
  • flash memory electrically erasable PROM
  • EEPROM electrically erasable PROM
  • Fig. 1 shows a flow chart for dynamically configuring a single EAS instance for a group of UEs according to an example of the invention
  • - Fig. 2 shows a session management function according to an example of the invention
  • FIG. 3 shows a flow chart of a method for a session management function according to an example of the invention
  • FIG. 4 shows a EAS discovery function according to an example of the invention
  • FIG. 5 shows a flow chart of a method for a EAS discovery function according to an example of the invention
  • FIG. 6 shows a communication network according to an example of the invention
  • FIG. 7 shows exchange of information for an area of interest according to an example of the invention
  • FIG. 8 shows area of interest-specific EAS deployment information provisioning according to an example of the invention
  • FIG. 9 shows area of interest-specific EAS deployment information management according to an example of the invention.
  • FIG. 10 shows area of interest-specific baselineDNSPattern management according to an example of the invention.
  • FIG. 11 shows extended external parameter provisioning for single EAS configuration according to an example of the invention.
  • emergency trajectory alignment and cooperative lane change among UEs supporting V2X applications need to meet end-to-end delay requirements of 3ms and 10ms respectively.
  • a real lane-merging scenario involves vehicular UEs or vehicles belonging to different mobile network operators (MNOs) and original equipment manufacturers (OEMs) where there is a need to get data from multiple vehicles and to process it preferably in a single application server belonging to a single MNO or a 3 rd party provider.
  • MNOs mobile network operators
  • OEMs original equipment manufacturers
  • a single edge application server (EAS) should be chosen for a given application type in a given geographical location. This can be challenging in multi-MNO cases where the collaborating UEs belong to different MNOs. Hence, some kind of coordination is required in such multi-MNO cases to ensure that the same MEC resources are utilized to process information generated by all involved collaborating UEs.
  • EASDF edge application server discovery function
  • DNS domain name system
  • a single EAS instance can herein be understood to mean one EAS instance having a common identifier (e.g., addressed with a specific IP address) but may be implemented in one or more logical and/or physical units or devices so that they can optimally serve UEs that are located in a given area of interest.
  • the single EAS instance may e.g., be a standalone server or be distributed over a number of servers.
  • an application function can be used to coordinate with the involved MNOs to ensure that application streams generated by the UEs in a given geographical location get processed locally in a single EAS instance.
  • the AF may belong to a road traffic authority (RTA) and the given geographical location may be a road inter-section point.
  • RTA road traffic authority
  • a MNO may also be referred to as a public land mobile network (PLMN) and each MNO may be assigned a unique PLMN-ID.
  • Fig. 1 shows a flow chart of an example of AFs to enable coordination with 5G core networks (5GCs) of MNOs to configure a single EAS instance for a group of UEs running a given application service in a location-specific way, i.e., to assign a single dedicated EAS instance for a group of UEs running a given application service in a location-specific way.
  • 5GCs 5G core networks
  • the AF configures area of interests with 5GC for dynamic UE collaboration per application.
  • the AF e.g., belonging to a RTA, may coordinate with the 5GCs in terms of how to dynamically configure a single EAS instance for use by a group of UEs of interests that happen to be located in a given area of interest.
  • Such an EAS configuration can be optionally preceded by a dynamic grouping of UEs that happen to be located in a given area of interests while running a particular collaborative application, e.g., road safety or multi- player gaming.
  • the UEs can belong to the same MNO or different MNOs.
  • an AF e.g., belonging to the RTA
  • an AF can define areas of interests that are specific to a road intersection points in terms of presence reporting areas (PRAs) or geographical zone identifiers.
  • the AF may interact with the MNOs to generate required policy rules that can be used to ensure that a single EAS instance is used by two or many UEs that run a similar collaborative application and happen to be present in the same geographical location for their collaborating activities such as e.g., lane-merging or location-based multi-player gaming.
  • One way of achieving this goal is to dynamically form a UE group across the same or different MNOs with those UEs that run a similar collaborative application and happen to be present in a given area of interest, i.e., forming a UE group having a common collaborating interest in a location-specific way.
  • the group to be maintained dynamically per given geographical location can be of 5G virtual network type as specified in clause 5.29.2 of 3GPP TS 23.501 in terms of basic group data or member management data. However, according to examples of the invention the group data will have a number of additional attributes, as will be further described below.
  • Group membership management parameters as specified in clause 4.15.6.3b of 3GPP TS 23.502 can additionally include subscription permanent identifier (SUPI) or public land mobile network (PLMN) -ID along with generic public subscription identifier (GPSI) to see the mapping of GPSI and home PLMN (HPLMN) association.
  • SUPI subscription permanent identifier
  • PLMN public land mobile network
  • GPSI generic public subscription identifier
  • the AF then knows which PLMNs are involved for a given UE group so that it can coordinate with the 5G core networks of those identified PLMNs to provide required configuration details that apply to a particular UE group, e.g., IP address of a single EAS instance to be used in a given location at a given time instance by member UEs of a dynamic UE group.
  • IP address of a single EAS instance to be used in a given location at a given time instance by member UEs of a dynamic UE group.
  • a dynamic UE grouping is not mandatory, what is important is to facilitate dynamic collaboration among UEs that happen to be present in a given area of interests while running a similar collaborative application through the use of a single EAS instance.
  • the AF subscribes in step 2 to one or many access management functions (AMFs) belonging to the same or different MNOs to check whether UEs of interests come into close proximity with each other in a given geographical location or move in or out of a particular area of interest.
  • AMFs access management functions
  • UE mobility with respect to a given area of interests is constantly monitored by an AF with a help of one or many AMFs before triggering dynamic collaboration among identified UEs through the use of a single EAS instance.
  • V2X Vehicle-to-everything
  • application service-specific e.g., road-crossing, lane-merging, advanced-driving or V2X application in general
  • the EAS instance takes a decision in terms of actions to be taken by each UE member, for instance, after processing relevant data streams.
  • a dynamic location-specific UE grouping can help serving session management functions (SMFs) configure to use a single EAS instance irrespective of UE-MNO associations.
  • SMFs serving session management functions
  • An aspect is to dynamically configure EAS instance per area of interests depending on load, residual capacity and proximity of all involved EAS instances with respect to all UEs that happened to be in the given area of interests.
  • AF continuously gets updated by all EAS instances serving a given area of interests and a given application service namely in terms of their current loads, residual processing/memory capacity and bandwidth availability to decide on which EAS instance to use at a given time instance for a given area of interests.
  • IP proximity of candidate EAS instance with respect to every UE that happens to be located within a given area of interests or every UE belonging to a dynamic location-specific UE group formed on demand is considered by an AF when choosing an appropriate EAS instance.
  • an AF will coordinate with the 5GC of all involved MNOs to configure the same EAS instance for every UE that happens to be located within a given area of interests or belongs to a dynamic location-specific UE group at a given time instance.
  • an external parameter provisioning will help 5GC create area of interests-specific UE grouping consisting of UEs that happen to be located in a given area of interests and enforce the use of a single EAS instance by those UEs through creation of appropriate DNS message handling rules to handle DNS queries initiated by any UE belonging to an area of interests-specific UE grouping.
  • the AF checks based on the mobility events from the AMFs whether enough number of UEs of interest from an AF perspective are located in a given area of interest. It is practically possible that UEs may belong to different PLMNs and under such circumstances the AF also checks PLMN association of each UE that is located in a given area of interests. In case UEs belong to different PLMNs, the AF will interact with AMFs belonging to different PLMNs in step 2 of Fig. 1.
  • the AF triggers area of interest-specific EAS deployment information management in step 4 in Fig. 1. If there aren’t enough number of UEs in the area of interest, the AF may go back to step 2 in Fig. 1 and keep monitoring the mobility events from the AMFs. It may be possible that even when a single UE is located in a given area of interest, in V2X scenarios, data from traffic lights need to be processed along with that of the single UE in a location-specific EAS instance. Hence, in the case of V2X application, existence of a single vehicular UE or pedestrian UE may be enough to trigger step 4 in Fig. 1.
  • FIG. 8 An example of the area of interest-specific EAS deployment information management procedure is shown in Fig. 8 and is used to configure a single EAS instance with all involved PLMNs.
  • the AF can trigger the external parameter provisioning procedure as shown in Fig. 11 to the 5GC associated with each involved PLMN to indicate an IP address of an EAS instance that has to be used in relation to processing data streams generated by every UE that happens to be located within a given area of interest or belongs to a dynamic location-specific UE group formed on demand.
  • the SMF belonging to an MNO/PLMN can configure its respective EASDF such that any DNS query from a UE that happens to be located within a given area of interest or a UE belonging to a dynamic location-specific UE group formed on demand may be responded with an IP address of a single EAS instance.
  • an EASDF may not further forward a DNS query to any other DNS server/resolver.
  • the EASDF may resolve a DNS query from any of those UEs based on DNS handling rule as configured by a serving SMF managing a PDU session of a UE that carries data traffic belonging to a collaborative application service.
  • the EASDF may then check the DNS query against the DNS handling rules configured by its respective SMF and send a DNS response with an IP address of a single EAS instance for all UEs in an area of interest.
  • a serving SMF of a UE member can configure its EASDF for a given application service or single-network slice selection assistance information (S-NSSAI) and data network name (DNN) with DNS message handling that governs as to how DNS queries from a UE that happens to be located within a given area of interest or belongs to a dynamic location-specific UE group formed on demand has to be handled.
  • S-NSSAI single-network slice selection assistance information
  • DNN data network name
  • An AF can change a single EAS Instance depending on, for example, its load, residual capacity. The AF collects such information constantly and decide what could be an appropriate EAS instance for a given area of interest at a given time-instance for a given S-NSSAI.
  • an AF can additionally supply extension mechanisms for DNS client subnet (ECS) option to be included in a DNS query generated by any UE that happens to be located within a given area of interest or any member UE of a given UE group running a given application service or using a particular S-NSSAI or DNN. This may not, however, always guarantee the use of the same EAS instance. This is why directly responding a UE DNS query with an IP address of a single EAS instance may be preferred.
  • ECS DNS client subnet
  • the AMF provides the UE mobility related event reporting to an authorised AF once it has subscribed to the UE mobility event notification service to the AMF with one or more of the following parameters:
  • Event reporting type that specifies what to be reported on UE mobility (e.g., UE location, UE mobility on area of interest) .
  • the area of interest may be represented by a list of tracking areas, list of cells or list of (R) AN node identifiers or list of absolute geographical coordinates.
  • the event consumer e.g., SMF
  • the LADN DNN provides the LADN DNN to refer to the LADN service area as the area of interest.
  • the event consumer e.g., SMF or PCF
  • Event reporting information event reporting mode, number of reports, maximum duration of reporting, event reporting condition (e.g., when the target UE moved into a specified area of interest, immediate reporting flag) .
  • NF network function
  • the target of event reporting that indicates any UE that runs a special application service that can be identified by an application identifier or those that use a given S-NSSAI or DNN.
  • An application identifier is an identifier that can be mapped to a specific application traffic detection rule.
  • the AF plays a key role in constantly collecting load and residual capacity of different EAS instances for the purpose of choosing a suitable EAS instance for a given area of interest for a given application service at a given time instance.
  • Fig. 2 shows a session management function (SMF) 100 according to an example of the invention.
  • the SMF 100 comprises a processor 102, a transceiver 104 and a memory 106.
  • the processor 102 is coupled to the transceiver 104 and the memory 106 by communication means 108 known in the art.
  • the SMF 100 may be configured for wireless and/or wired communications in a communication system.
  • the wireless communication capability may be provided with an antenna or antenna array 110 coupled to the transceiver 104, while the wired communication capability may be provided with a wired communication interface 112 e.g., coupled to the transceiver 104.
  • the processor 102 may be referred to as one or more general-purpose CPU, one or more digital signal processor (DSP) , one or more application-specific integrated circuit (ASIC) , one or more field programmable gate array (FPGA) , one or more programmable logic device, one or more discrete gate, one or more transistor logic device, one or more discrete hardware component, or one or more chipsets.
  • the memory 106 may be a read-only memory, a random access memory (RAM) , or a non-volatile RAM (NVRAM) .
  • the transceiver 104 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices, such as network nodes and network servers.
  • the transceiver 104, memory 106 and/or processor 102 may be implemented in separate chipsets or may be implemented in a common chipset.
  • the SMF 100 is configured to perform certain actions can in this disclosure be understood to mean that the SMF 100 comprises suitable means, such as e.g., the processor 102 and the transceiver 104, configured to perform the actions.
  • the SMF 100 is configured to obtain a first information for an area of interest 550, wherein the area of interest 550 comprises a plurality of client devices 610 associated with a same application service.
  • the first information indicates: an identity of a single EAS instance 630 configured to serve the plurality of client devices 610 in the area of interest 550, individual identities of the plurality of client devices 610 and a dedicated data network access identifier (DNAI) .
  • the SMF 100 is further configured to transmit a configuration message 510 to an EAS discovery function 300, the configuration message 510 comprising a second information for the area of interest 550.
  • the second information indicates: the identity of the single EAS instance 630 and the individual identities of the plurality of client devices 610.
  • DNAI is an identifier indicating a user plane access to one or more DN (s) where applications are deployed.
  • Fig. 3 shows a flow chart of a corresponding method 200 which may be executed in a SMF 100, such as the one shown in Fig. 2.
  • the method 200 comprises obtaining 202 a first information for an area of interest 550, wherein the area of interest 550 comprises a plurality of client devices 610 associated with a same application service, i.e., currently running the same application service.
  • the first information indicates: an identity of a single EAS instance 630 configured to serve the plurality of client devices 610 in the area of interest 550, individual identities of the plurality of client devices 610 in the area of interest 550 and a dedicated DNAI.
  • the method 200 further comprises transmitting 204 a configuration message 510 to an EAS discovery function 300, the configuration message 510 comprising a second information for the area of interest 550.
  • the second information indicates: the identity of the single EAS instance 630 and the individual identities of the plurality of client devices 610 in the area of interest 550.
  • Fig. 4 shows an EAS discovery function 300 according to an example of the invention.
  • the EAS discovery function 300 comprises a processor 302, a transceiver 304 and a memory 306.
  • the processor 302 is coupled to the transceiver 304 and the memory 306 by communication means 308 known in the art.
  • a transceiver 304 can enable either wired or wireless connection.
  • the EAS discovery function 300 may further comprise an antenna or antenna array 310 coupled to the transceiver 304, which means that the EAS discovery function 300 is configured for wireless communications in a communication system.
  • the processor 302 may be referred to as one or more general-purpose CPU, one or more digital signal processor (DSP) , one or more application-specific integrated circuit (ASIC) , one or more field programmable gate array (FPGA) , one or more programmable logic device, one or more discrete gate, one or more transistor logic device, one or more discrete hardware component, one or more chipset.
  • the memory 306 may be a read-only memory, a random access memory (RAM) , or a non-volatile RAM (NVRAM) .
  • the transceiver 304 may be a transceiver circuit, a power controller, or an interface providing capability to communicate with other communication modules or communication devices.
  • the transceiver 304, the memory 306 and/or the processor 302 may be implemented in separate chipsets or may be implemented in a common chipset.
  • the EAS discovery function 300 is configured to perform certain actions can in this disclosure be understood to mean that the EAS discovery function 300 comprises suitable means, such as e.g., the processor 302 and the transceiver 304, configured to perform the actions.
  • the EAS discovery function 300 is configured to receive a configuration message 510 from a SMF 100, the configuration message 510 comprising a second information for an area of interest 550, wherein the area of interest 550 comprises a plurality of client devices 610 associated with a same application service.
  • the second information indicates: an identity of a single EAS instance 630 configured to serve the plurality of client devices 610 in the area of interest 550 and individual identities of the plurality of client devices 610.
  • Fig. 5 shows a flow chart of a corresponding method 400 which may be executed in a EAS discovery function 300, such as the one shown in Fig. 4.
  • the method 400 comprises receiving 402 a configuration message 510 from a SMF 100, the configuration message 510 comprising a second information for an area of interest 550, wherein the area of interest 550 comprises a plurality of client devices 610 associated with a same application service.
  • the second information indicates: an identity of a single EAS instance 630 configured to serve the plurality of client devices 610 in the area of interest 550 and individual identities of the plurality of client devices 610.
  • Fig. 6 shows a communication system 500 according to an implementation.
  • the communication system 500 comprises a plurality of client devices 610 located in an area of interest 550.
  • the client devices 610 are either served by a first PLMN or a second PLMN through a respective user plane function (UPF) 640.
  • Each PLMN further comprises a SMF 100 and an EAS discovery function 300 according to an example of the invention.
  • the SMF 100 and the EAS discovery function 300 belonging to the same PLMN exchange information for the area of interest 550 to coordinate a single EAS instance 630 to be used by the client devices 610 in the area of interest 550.
  • the single EAS instance 630 is located in/hosted by a data network DN outside the 5GC of the first and second PLMNs.
  • EAS instances lie outside of the 5GC, in reality, multiple EAS instances 630a, ...630n, may be owned and managed by the first PLMN, the second PLMN, another PLMN or a third party service provider to serve a given area of interest.
  • the invention enables a way to ensure the use of single EAS instance to be used by a group of client devices at given time period that run the same application service and are located in a given area of interest.
  • the invention enables a single EAS instance to be used by all the client devices 610 in the area of interest 550, even when served by different PLMNs.
  • a single EAS instance 630 for the client devices 610 in the area of interest 550 dynamic collaboration for application services among the client devices 610 can be facilitated while enhancing user QoS experience by, for example, bringing down end-to-end latencies.
  • the SMF 100 can be notified in terms of how to route data traffic that is generated by a collaborative application running in each client device 610.
  • a routing involves identifying the right UPF 640 for the purpose of terminating packet data unit (PDU) sessions established by each client device 610 so that related data traffic will be destined to an appropriate single EAS instance 630.
  • PDU packet data unit
  • the SMF 100 may configure an EAS discover function 300 such that application traffic will get processed at a single EAS instance 630.
  • an AF e.g., belonging to the RTA or a gaming studio that released a given multi-player gaming
  • client device 610 mobility with respect to a given area of interest 550 is constantly monitored by an AF with a help of one or many AMFs before triggering dynamic collaboration among identified UEs through the use of a single EAS instance 630.
  • Fig. 7 shows signaling between a SMF 100 and an EAS discovery function 300 for exchange of information for an area of interest 550 according to an example of the invention.
  • the SMF 100 obtains a first information for an area of interest 550.
  • the area of interest 550 comprises a plurality of client devices 610 associated with a same application service. That the plurality of client devices 610 are associated with the same application service can be understood to mean that those client devices 610 run the same application service enabling application-level collaboration to achieve a common goal.
  • all vehicular UEs run, for example, an advance-driving or lane-merging application service enabling interactions in terms of transmitting audio and/or video streams generated by car-mounted sensors/cameras and driving commands signals indicating driving actions to the single EAS instance so that it can process all data streams generated by all involved client devices 610 and take a unified action.
  • That the area of interest 550 comprises the plurality of client devices 610 can be understood to mean that the plurality of client devices 610 are currently located in the area of interest 550.
  • the area of interest 550 may be defined by e.g., presence reporting areas (PRAs) , geographical zone identifiers, or tracking area.
  • PRAs presence reporting areas
  • geographical zone identifiers or tracking area.
  • the plurality of client devices 610 may belong to two or more public land mobile networks (PLMNs) , i.e., two or more of the client devices 610 may be served by different PLMNs. Under such circumstances, serving SMFs belonging to each PLMN can get notified in terms of what EAS instance to be used for the plurality of client devices 610 that reside in the area of interest 550.
  • the application service may be associated with the same data network name (DNN) and/or the same single-network slice selection assistance information (S-NSSAI) . This will help appropriate SMFs 100 and UPFs 640 to be chosen to serve traffic generated by the application service running on a client device.
  • DNN data network name
  • S-NSSAI single-network slice selection assistance information
  • the first information explicitly or implicitly indicates: an identity of a single EAS instance 630 configured to serve the plurality of client devices 610 in the area of interest 550, individual identities of the plurality of client devices 610 and a dedicated data network access identifier (DNAI) .
  • the identity of the single EAS instance 630 may be an IP address of the single EAS instance 630. With an IP address, it is easy for the plurality of client devices 610 to connect to the identified single EAS instance 630 that will facilitate collaboration among the plurality of client devices 610.
  • An IP address can be of IPv4 or IPv6 type.
  • the first information may explicitly indicate the identity of the single EAS instance 630, the individual identities of the plurality of client devices 610 and the dedicated DNAI.
  • the first information may implicitly indicate the identity of the single EAS instance 630, the individual identities of the plurality of client devices 610 and the dedicated DNAI.
  • the first information may e.g., indicate a group identity for the plurality of client devices 610.
  • the SMF 100 may derive the identity of the single EAS instance 630, the individual identities of the plurality of client devices 610 and the dedicated DNAI based on the group identity for the plurality of client devices 610, e.g., from an unified data management/repository (UDM/UDR) .
  • the SMF 100 may derive additional information based on the group identity for the plurality of client devices 610 such as the information listed in Table 1 and Table 2 further below.
  • the first information may further indicate a valid time period during which the single EAS instance 630 is configured to serve the plurality of client devices 610 in the area of interest 550. In this way, the SMF 100 can be made aware of for how long the single EAS instance 630 is expected to serve the plurality of client devices 610 such that distribution of outdated information can be avoided.
  • the SMF 100 may obtain the first information in a number of different ways.
  • the SMF 100 obtains the first information from a network exposure function (NEF) 620 based on an optional message exchange between the SMF 100 and the NEF 600, as indicated with dashed arrows 520, 530 in Fig. 7.
  • the SMF 100 transmits a subscription request message 520 to the NEF 620.
  • the SMF receives a subscribe notification message 530 from the NEF 620, the subscribe notification message 530 comprising the first information.
  • the NEF 620 may in turn have obtained the first information from an AF handling the coordination of the area of interest 550.
  • the SMF 100 transmits a configuration message 510 to the EAS discovery function 300.
  • the configuration message 510 comprising a second information for the area of interest 550 explicitly or implicitly indicating: the identity of the single EAS instance 630 and the individual identities of the plurality of client devices 610.
  • the second information may explicitly indicate the identity of the single EAS instance 630 and the individual identities of the plurality of client devices 610 or implicitly indicate the information with a group identity for the plurality of client devices 610.
  • the SMF 100 transmits the configuration message 510 to the EAS discovery function 300 upon receiving the subscribe notification message 530.
  • the subscribe notification message 530 from the NEF 620 may hence be a trigger condition for the transmission of the configuration message 510. In this way, when the SMF 100 obtains the first information from the NEF 620, the SMF 100 provides the second information to the EAS discovery function 300.
  • the EAS discovery function 300 receives the configuration message 510 from the SMF 100 and hence the second information for the area of interest 550 indicated in the configuration message 510.
  • the EAS discovery function 300 hence obtains the identity of the single EAS instance 630 and individual identities of the plurality of client devices 610 indicated by the second information.
  • the second information indicates a group identity of the plurality of client devices 610
  • the EAS discovery function 300 derives the identity of the single EAS instance 630 and the individual identities of the plurality of client devices 610 based on the group identity of the plurality of client devices 610, e.g., from an UDM/UDR.
  • the SMF 100 may include further information related to domain name system (DNS) queries in the configuration message 510.
  • the configuration message 510 may e.g., further indicate an instruction for the EAS discovery function 300 to respond to a DNS query from a client device 610n among the plurality of client devices 610 with the identity of the single EAS instance 630.
  • the EAS discovery function 300 receives a DNS query 540 from a client device 610n among the plurality of client devices 610, the EAS discovery function 300 transmits a DNS response 560 to the client device 610n, as indicated with dashed arrows 540, 560 in Fig. 7.
  • the DNS response indicates the identity of the single EAS instance 630, e.g., an IP address of the single EAS instance 630.
  • the SMF 100 may include this information in the second information.
  • the second information may in examples further indicate a valid time period during which the single EAS instance 630 is configured to serve the plurality of client devices 610 in the area of interest 550.
  • the EAS discovery function 300 may use this information e.g., to determine when to stop responding to a DNS query with the identity of the single EAS instance 630.
  • the SMF 100 may use the DNAI obtained from the first information to identify a UPF 640 to serve a client device 610n, as indicated by optional step IV in Fig. 7.
  • the SMF 100 may identify a UPF 640 for a protocol data unit (PDU) session establishment request made by a client device 610n among the plurality of client devices 610 based on the dedicated DNAI.
  • An important criterion to be used in the UPF 640 selection is whether a given UPF maintains an N6 interface to connect to the identified single EAS instance 630.
  • the SMF 100 may then transmit a PDU session establishment accept or a PDU session modification command/acknowledgement to the client device 610n.
  • PDU protocol data unit
  • the PDU session establishment accept or the PDU session modification command/acknowledgement instructing the client device 610n to clear its DNS cache when the client device 610n moves into another area of interest 550′. This will ensure that the client device 610n will trigger a new DNS query to get an IP address of a new EAS instance 630′that is meant for the other area of interest 550′into which the client device 610n has moved. If a DNS cache is not cleared, the client device 610n may use the IP address of an EAS instance 630 that provides the application service in a different area of interest 550 which the client device 610n have visited earlier.
  • the instruction may e.g., be indicated using protocol configuration option (PCO) of the PDU session establishment accept or PDU session modification command.
  • PCO protocol configuration option
  • the SMF 100 can subscribe to an AMF for a UE mobility related event reporting or get explicit prompt or instructions from an AF indirectly through an NEF 620.
  • the SMF 100 may in the scenarios below be configured to perform any of the described functions of a 3GPP SMF entity.
  • the EAS discovery function 300 may in the scenarios below be configured to perform any of the described functions of a 3GPP EASDF entity.
  • Fig. 8 shows area of interest-specific EAS deployment information provisioning involving an AF, an NEF and an unified data register (UDR) according to an example of the invention.
  • the AF invokes the service operation Nnef_EASDeployment_Create/Update/Delete towards the NEF for the purpose of creating/updating/deleting area of interest-specific EAS deployment information to be stored in the UDR for a given application identifier or single-network slice selection assistance information (S-NSSAI) .
  • S-NSSAI single-network slice selection assistance information
  • the AF will include information such as dedicated DNAI, IP address of single EAS instances and extension mechanisms for DNS client subnet (ECS) option to be used by all UEs that are present in a given area of interest.
  • ECS DNS client subnet
  • the AF will also additionally include list of generic public subscription identifiers (GPSIs) of UEs/client devices 610 to which this EAS deployment information applies at/for a given time instance/period depending on identities of UEs that happen or are going to be located in a given area of interest.
  • GPSIs generic public subscription identifiers
  • the NEF checks whether the AF is authorized to perform this request and authorised to provision this EAS deployment information based on the operator policies.
  • the NEF derives data network name (DNN) and S-NSSAI from the AF-service-identifier if not received explicitly and translates received external application identifier to application identifier known inside the MNO domain.
  • the NEF derives subscription permanent identifier (SUPI) from GPSI provided by the AF.
  • the NEF may translate presence reporting areas (PRA) or geographical zone identifiers representing a given area of interest into a list of tracking areas, list of cells or list of (radio) access network node identifiers or list of absolute geographical coordinates.
  • PRA presence reporting areas
  • geographical zone identifiers representing a given area of interest into a list of tracking areas, list of cells or list of (radio) access network node identifiers or list of absolute geographical coordinates.
  • step 3 in Fig. 8 the NEF invokes a Nudr_DM_Create/Update/Delete request to the UDR if the AF is authorized.
  • the UDR stores/updates/removes the corresponding information and responds with a Nudr_DM_Create/Update/Delete response to the NEF.
  • the UDR additionally include IDs of UEs to which such EAS deployment information applies.
  • UE IDs include GPSI, SUPI or subscription concealed identifier (SUCI) .
  • step 5 in Fig. 8 the NEF sends Nnef_EASDeployment_Create/Update/Delete response to the AF.
  • the SMF 100 may further receive the area of interest-specific EAS deployment information from UDR through NEF through a Subscribe/Notify procedure as shown in Fig. 9.
  • step 1 in Fig. 9 the SMF 100 subscribes to area of interest-specific EAS deployment information change notification and change of UE presence in terms of identities of UEs that are present in a given area of interest from the NEF by sending a Nnef_EASDeployment_Subscribe request.
  • the SMF 100 may indicate that the current status of EAS deployment information shall be notified immediately (if available) along with IDs of all UEs that are present in a given area of interest.
  • the SMF 100 may further indicate for which (list of) DNN and/or S-NNSAI it subscribes.
  • the NEF acknowledge the subscription with a Nnef_EASDeployment_Subscribe response, as shown in step 2 in Fig. 9.
  • step 3 in Fig. 9 is triggered.
  • EAS deployment information e.g., new EAS instance, new DNAI is to be used
  • new DNAI new DNAI
  • the NEF invokes Nnef_EASDeployment_Notify request (DNN and/or DNAI (s) and/or application (s) EAS deployment information) to provide up-to-date EAS deployment information to the SMF 100 along with IDs of all UEs that are present in the given area of interest that use the particular application identifier or S-NSSAI or DNN.
  • Nnef_EASDeployment_Notify request DNN and/or DNAI (s) and/or application (s) EAS deployment information
  • the SMF 100 acknowledge the received notify request and responds with a Nnef_EASDeployment_Notify response.
  • step 1 in Fig. 10 the SMF 100 may trigger to create/update/delete the baselineDNSPattern pertaining to a given area of interest. Step 1 may be triggered when the following happens:
  • the SMF 100 sends a Neasdf_BaselineDNSPattern_Create/Update/Delete request to the EASDF 300 to provision/update/remove the area of interest–specific baselineDNSPattern along with IDs of UEs to which the baselineDNSPattern applies.
  • UE IDs include GPSI, SUPI or SUCI.
  • step 3 in Fig. 10 the EASDF 300 updates the area of interest–specific baselineDNSPattern and IDs of UEs to which such baselineDNSPattern applies and acknowledges the SMF 100 with a Neasdf_BaselineDNSPattern_Create/Update/Delete response
  • a dynamic UE group can be formed with identities of UEs that happen to be or are going to be located within a given area of interest. This can be achieved using an external parameter provisioning as specified in clause 4.15.6.2 of 3GPP TS 23.502.
  • the service operations related to Nnef_ParameterProvision_Create/Update/Delete are extended, as shown in Fig. 11.
  • any network function such as a policy control function (PCF) , access management function (AMF) or SMF 100 subscribes to unified data management (UDM) notifications of area of interest definitions, new area of interest-specific EAS configuration information in terms of dedicated DNAI, IP address of single EAS instance, extension mechanisms for DNS client subnet (ECS) option to be included into DNS query for a fully qualified domain name (FQDN) that is generated by each UE that happens to be located within a given area of interest or belonging to a given area of interest-specific UE group formed on demand.
  • FQDN fully qualified domain name
  • These area of interests are defined by respective AFs per application identifier, AF-service-identifier or S-NSSAI.
  • An application identifier is an identifier that can be mapped to a specific application traffic detection rule.
  • the NF can subscribe to UDM in this step for any notification that will be triggered in step 8 upon detecting any changes to any area of interests definition (e.g., an area of interest is defined in terms of absolute geographical coordinates or geographic zone identifier (s) or presence reporting areas (PRA) or by a list of PLMN-specific tracking areas, list of cells or list of (R) AN node identifiers) , area of interest-specific EAS configuration information in terms of dedicated DNAI, IP address of single EAS instance, ECS option to be included in a DNS query for an FQDN that is generated by each UE that happens to be located within a given area of interest or belonging to a given area of interest-specific UE group formed on demand.
  • an area of interest is defined in terms of absolute geographical coordinates or geographic zone identifier (s) or presence reporting areas (PRA) or by a list of PLMN-specific tracking areas, list of cells or list of (R) AN node identifiers
  • area of interest-specific EAS configuration information
  • an SMF While an AMF will be interested to get notified when an area of interest definition change, new UEs move into or old UEs move out a given area of interests in step 8, an SMF will be interested to get notified when there is a change in EAS instance or change in UEs that move in or move out of a given area of interest.
  • the AF provides area of interest definitions, new area of interest-specific EAS configuration or UE grouping information in terms of dedicated DNAI, IP address of single EAS instance, ECS option to be included in a DNS query for an FQDN that is generated by each UE that happen to be located within a given area of interest or belonging to a given area of interest-specific UE group formed on demand.
  • a UE can be identified by GPSI, IP address or medium access control (MAC) address whereas a device can be identified by a permanent equipment identifier (PEI) .
  • a transaction reference ID identifies the transaction request between the NEF and the AF.
  • the NEF checks whether the requestor is allowed to perform the requested service operation by checking the requestor's identifier, i.e., AF ID. If the AF is authorised by the NEF to provision the parameters, the NEF requests to create, update and store, or delete the provisioned parameters as part of 5G virtual network (VN) group or new area of interest-specific UE group data using a Nudm_ParameterProvision_Create/Update/Delete request in step 3 in Fig. 11. The message includes the provisioned data and NEF reference ID.
  • VN virtual network
  • Step 7 in Fig. 11 the NEF indicates the reason for a failure to the requesting AF using a Nnef_ParameterProvision_Create/Update/Delete response. Step 8 in Fig. 11 does not apply in this case.
  • the UDM may read from the UDR using a Nudr_DM_Query the corresponding subscription information to validate required data updates and authorize these changes for the 5G VN group or new area of interest-specific UE group related data. If the AF is authorised by the UDM to provision the parameters for the 5G VN group or new area of interest-specific UE group related data, the UDM resolves the GPSI to SUPI for each UE, and requests to create, update or delete the provisioned parameters as part of 5G VN group or new area of interest-specific UE group related data using a Nudr_DM_Create/Update/Delete request, as shown in step 4 in Fig. 11.
  • the Nudr_DM_Create/Update/Delete request includes the provisioned data.
  • the UDR stores the provisioned data as part of the 5G VN group or new area of interest-specific UE group and responds with a Nudr_DM_Create/Update/Delete response, as shown in step 5 in Fig. 11.
  • the UDR When the 5G VN group or new area of interest-specific UE group related data is updated, the UDR notifies each subscribed PCF by sending Nudr_DM_Notify as defined in clause 4.16.12.2 of 3GPP TS 23.502 (not shown in Fig. 11) .
  • the UDM may use the AF ID received from the NEF in step 3 to relate the received parameter with a particular subscribed DNN and/or S-NSSAI.
  • step 6 in Fig. 11 the UDM responds to the request received from the NEF in step 3 with a Nudm_ParameterProvision_Create/Update/Delete response. If the procedure failed, the cause value indicates the reason.
  • NEF responds to the request received from the AF in step 2 with a Nnef_ParameterProvision_Create/Update/Delete response. If the procedure failed, the cause value indicates the reason.
  • step 8 in Fig. 11 the UDM notifies the subscribed NF of the updated 5G VN group or new area of interest-specific UE group related data using a Nudm_SDM_Notification notify. It may be noted that step 8 only occurs if step 5 is successful. In step 8 the UDM performs one of the following:
  • the UDM performs Nudm_SDM_Notification service operation pertaining to AMF-associated parameters such as area of interest.
  • the AMF can make use of area of interest definitions to monitor UE mobility with respect to each defined area of interest when an AF subscribes to such an event notification.
  • the UDM performs Nudm_SDM_Notification service operation pertaining to SMF-associated parameter such as IP address of a single EAS instance to be used by a given UE group member.
  • SMF-associated parameter such as IP address of a single EAS instance to be used by a given UE group member.
  • Such a notification may additionally include ECS option to be included in a DNS query for an FQDN that is generated by each member of a given UE grouping and target DNAI to be used when choosing a PDU session anchor (PSA) user plane function (UPF) that can connect to a desired EAS instance.
  • PDA PDU session anchor
  • UPF user plane function
  • the SMF 100 stores the received SMF-associated parameters and configures an EASDF 300 in terms of how to react when any member UE of a given UE group generates a DNS query.
  • Fig. 11 depicts an external parameter provision of an AF with respect to a single PLMN
  • the same operation can be simultaneously triggered towards all involved PLMNs.
  • 5G group data that is specific to a given area of interest and application service as illustrated in Table 1 below, can be statically configured by an AF with one or many PLMNs.
  • the single EAS instance to be used by a given UE group can vary depending on load, residual capacity, proximity of itself with respect to all involved UE members of a given area of interest-specific UE group.
  • UE group membership management parameters can be dynamic depending on mobility of one or many UEs of interests (i.e., those running a special application service that is identified by an application identifier) with respect to a given area of interest.
  • Such UE membership management parameters and single EAS instance information of 5G VN group or new area of interest-specific UE group related data as maintained by a UDR of a PLMN will get updated depending on a whether a UE which is present in a given area of interest belongs to that PLMN.
  • external parameter provisioning procedure allows an external party to provision information to 5G core network mainly related to expected UE behaviour, service specific parameters, or the 5G VN group information.
  • the expected UE behavioural information consists of information on expected UE movement and communication characteristics.
  • the provisioning information consists of information on 5G VN group, which is a set of UEs using private communication for 5G LAN-type service. This means that UEs belonging to a 5G VN tend to communicate with each other.
  • the additional UE group data can be included as part of existing 5G VN group data as specified in clause 4.15.6.3b of 3GPP TS 23.502, it can also be included as part of new area of interest-specific UE group.
  • Table 1 and Table 2 below depicts additional information that needs to be included as part of area of interest-specific UE group data and membership management parameters, respectively.
  • New proposed parameters are marked in bold and italic style.
  • the new parameters of area of interest-specific UE group data mainly include target DNAI to be used, IP address of a single EAS instance to be used by group, NSI-ID and ECS option to be included in a DNS query for an FQDN that is generated by each member of a given UE grouping.
  • the inclusion of an IP address of a single EAS instance will ensure that all data streams from all member UEs of an area of interest-specific 5G group use the same EAS instance for processing.
  • Table 1 Area of interest-specific UE group data
  • Table 2 Area of interest-specific UE group membership management parameters
  • the AF may first subscribe to an AMF-based Namf_EventExposure service with an event ID pertaining to UE mobility on area of interest event reporting service.
  • Associated event filter indicates a given area of interest.
  • the AF subscribes to every AMFs serving UEs of interests, e.g., vehicular UEs running a special application service that can be identified by an application identifier.
  • the AF determines the identities of UEs that are currently located within a given area of interest, finds out PLMN-IDs of their respective HPLMNs and triggers a Nnef_ParameterProvision_Create/Update/Delete request for the purpose of creating/updating/deleting an area of interest-specific UE or location-specific 5G VN group. As part of this process, it shares information as indicated by Table 1 and Table 2 –these are analogous to tables listed in clauses 4.15.6.3b and 4.15.6.3c of 3GPP TS 23.502 but with the indicated new parameters.
  • the SMF 100 may be a function configured for communication in 3GPP related fifth generation wireless technologies, such as new radio (NR) .
  • the SMF 100 may be configured to operate according to 3GPP TS 23.501, TS 23.502, TS 23.503, TS 29.502 and/or TS 23.548 to provide MEC services to client devices.
  • the EAS discovery function 300 may be a function configured for communication in 3GPP fifth generation wireless technologies, such as new radio (NR) .
  • the EAS discovery function 300 may be configured to operate according to 3GPP TS 23.501 and/or TS 23.548 to provide MEC services to client devices.
  • any method according to examples of the invention may be implemented in a computer program, having code means, which when run by processing means causes the processing means to execute the steps of the method.
  • the computer program is included in a computer readable medium of a computer program product.
  • the computer readable medium may comprise essentially any memory, such as previously mentioned a read-only memory (ROM) , a programmable read-only memory (PROM) , an erasable PROM (EPROM) , a flash memory, an electrically erasable PROM (EEPROM) , or a hard disk drive.
  • the SMF 100 and the EAS discovery function 300 may be implemented in communication devices comprising the necessary communication capabilities in the form of e.g., functions, means, units, elements, etc., for performing or implementing examples of the invention.
  • Examples of other such means, units, elements and functions are: processors, memory, buffers, control logic, encoders, decoders, rate matchers, de-rate matchers, mapping units, multipliers, decision units, selecting units, switches, interleavers, de-interleavers, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, MSDs, TCM encoder, TCM decoder, power supply units, power feeders, communication interfaces, communication protocols, etc. which are suitably arranged together for performing the solution.
  • the processor (s) of communication devices implementing the SMF 100 and the EAS discovery function 300 may comprise, e.g., one or more instances of a central processing unit (CPU) , a processing unit, a processing circuit, a processor, an application specific integrated circuit (ASIC) , a microprocessor, or other processing logic that may interpret and execute instructions.
  • the expression “processor” may thus represent a processing circuitry comprising a plurality of processing circuits, such as e.g., any, some or all of the ones mentioned above.
  • the processing circuitry may further perform data processing functions for inputting, outputting, and processing of data comprising data buffering and device control functions, such as call processing control, user interface control, or the like.

Landscapes

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

Abstract

L'invention concerne des informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple (MEC). Une fonction de gestion de session (SMF) (100) obtient dynamiquement des informations de ressource MEC ou des informations de déploiement de serveur d'application périphérique (EAS) pour une zone d'intérêt (550). Les informations obtenues comprennent une instance EAS unique (630) destinée à être utilisée par une pluralité de dispositifs clients (610) qui se situent dans la zone d'intérêt (550) et exécutent le même service d'application. La SMF (100) transmet des informations concernant l'instance EAS unique (630) et la pluralité de dispositifs clients (630) à une fonction de découverte EAS (300) de façon à ce que la fonction de découverte EAS (300) puisse connecter la pluralité de dispositifs clients (610) dans la zone d'intérêt (550) à l'instance EAS unique (630). À l'aide de l'instance EAS unique (630) pour les dispositifs clients (610) dans la zone d'intérêt (550), la collaboration au niveau de l'application entre les dispositifs clients (610) peut être facilitée tout en améliorant la QOS utilisateur expirant par exemple lors de la réduction d'une latence de bout en bout.
PCT/CN2022/074090 2022-01-26 2022-01-26 Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple WO2023141827A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/074090 WO2023141827A1 (fr) 2022-01-26 2022-01-26 Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/074090 WO2023141827A1 (fr) 2022-01-26 2022-01-26 Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple

Publications (1)

Publication Number Publication Date
WO2023141827A1 true WO2023141827A1 (fr) 2023-08-03

Family

ID=87470158

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/074090 WO2023141827A1 (fr) 2022-01-26 2022-01-26 Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple

Country Status (1)

Country Link
WO (1) WO2023141827A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021040334A1 (fr) * 2019-08-23 2021-03-04 Samsung Electronics Co., Ltd. Procédé et appareil permettant de fournir des données dans un système informatique périphérique
WO2021135663A1 (fr) * 2019-12-31 2021-07-08 华为技术有限公司 Procédé, dispositif et système de détermination d'instance d'application
WO2021189869A1 (fr) * 2019-08-20 2021-09-30 华为技术有限公司 Procédé et appareil d'acquisition d'informations
CN113691969A (zh) * 2021-07-16 2021-11-23 华为技术有限公司 通信方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021189869A1 (fr) * 2019-08-20 2021-09-30 华为技术有限公司 Procédé et appareil d'acquisition d'informations
WO2021040334A1 (fr) * 2019-08-23 2021-03-04 Samsung Electronics Co., Ltd. Procédé et appareil permettant de fournir des données dans un système informatique périphérique
WO2021135663A1 (fr) * 2019-12-31 2021-07-08 华为技术有限公司 Procédé, dispositif et système de détermination d'instance d'application
CN113691969A (zh) * 2021-07-16 2021-11-23 华为技术有限公司 通信方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "DNS configuration to SMF", 3GPP DRAFT; S2-2102595, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic meeting; 20210412 - 20210416, 6 April 2021 (2021-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051993970 *

Similar Documents

Publication Publication Date Title
US20210105196A1 (en) Support group communications with shared downlink data
CN110679185B (zh) 网络切片服务功能
RU2758457C2 (ru) Системы и способы для управления сеансом блока данных протокола (pdu), адаптированного к приложению
US11991145B2 (en) Device and method for providing information of application server in mobile communication system
CN110383790B (zh) 无需会话连续性的网络服务连续性
US11095554B2 (en) Application function in a network and control thereof
KR102166992B1 (ko) 서비스 계층 그룹 동작을 위한 멀티캐스트의 인에이블
EP3059985B1 (fr) Procédés avancés de diffusion géographique dans des réseaux de communications mobiles, et noeuds de réseau correspondants
US7633897B2 (en) Method and apparatus for the discovery of radio access network elements and exchange of capability and data attributes between those elements
CN107079353B (zh) 新服务区中的低等待时间服务连接设立
US20220329649A1 (en) Method for determining application instance, apparatus, and system
CN114616846A (zh) 用于管理边缘应用服务器的发现的方法和系统
US10064096B2 (en) Traffic distribution in heterogenous network environment
US10637794B2 (en) Resource subscription method, resource subscription apparatus, and resource subscription system
EP4205420A1 (fr) Entité de plan d'utilisateur et entité de plan de commande pour échanger des informations de noeud d'accès au réseau
CN107409340B (zh) 流量定向的方法、装置和计算机可读存储介质
US7990943B2 (en) Establishing channels between a domain manager and managed nodes
WO2021051420A1 (fr) Procédé et appareil de détermination d'un enregistrement de cache dns
WO2023141827A1 (fr) Informations spécifiques à une zone d'intérêt pour une informatique périphérique à accès multiple
WO2022233426A1 (fr) Fonction de réseau et fonction de gestion de session pour gérer de multiples dispositifs clients associés à un dispositif
GB2618646A (en) Artificial intelligence and machine learning traffic transport
CN118828464A (zh) 一种通信方法和装置
TW202437785A (zh) 應用上下文遷移方法、通信方法及相關裝置、系統
CN115955716A (zh) 数据收集方法、通信装置及通信系统
CN117042088A (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: 22922677

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE