WO2022239349A1 - サーバ、要求エンティティ、及びこれらの方法 - Google Patents
サーバ、要求エンティティ、及びこれらの方法 Download PDFInfo
- Publication number
- WO2022239349A1 WO2022239349A1 PCT/JP2022/006279 JP2022006279W WO2022239349A1 WO 2022239349 A1 WO2022239349 A1 WO 2022239349A1 JP 2022006279 W JP2022006279 W JP 2022006279W WO 2022239349 A1 WO2022239349 A1 WO 2022239349A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- request
- response message
- requesting entity
- eec
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 44
- 230000004044 response Effects 0.000 claims abstract description 112
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000012545 processing Methods 0.000 description 25
- 238000004891 communication Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 21
- 238000010586 diagram Methods 0.000 description 7
- 238000007726 management method Methods 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 5
- 206010000210 abortion Diseases 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 230000001934 delay Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000036541 health Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000005065 mining Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000007639 printing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 235000015842 Hesperis Nutrition 0.000 description 1
- 235000012633 Iberis amara Nutrition 0.000 description 1
- 241001465754 Metazoa Species 0.000 description 1
- 240000007594 Oryza sativa Species 0.000 description 1
- 235000007164 Oryza sativa Nutrition 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000005461 lubrication Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000002184 metal Substances 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 239000002245 particle Substances 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 239000012857 radioactive material Substances 0.000 description 1
- 238000005057 refrigeration Methods 0.000 description 1
- 235000009566 rice Nutrition 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000009958 sewing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 239000004753 textile Substances 0.000 description 1
- 238000011522 transarterial infusion chemotherapy Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000009423 ventilation Methods 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
- 238000005303 weighing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- the present disclosure relates to wireless communication networks, and more particularly to apparatus and methods for edge computing.
- Edge computing aims to move applications, data and computing power (services) from centralized points (e.g., centralized data centers) to locations closer to users (e.g., distributed data centers).
- MEC Multi-access Edge Computing
- ETSI European Telecommunications Standards Institute
- MEC provides application developers and content providers with cloud computing capabilities within the Radio Access Network (RAN) close to mobile subscribers.
- RAN Radio Access Network
- IT information technology
- the Third Generation Partnership Project (3GPP) SA6 working group has started standardization work on an architecture for enabling Edge Applications (see, for example, Non-Patent Document 1).
- This architecture of 3GPP is called EDGEAPP architecture.
- the EDGEAPP architecture is a set of enablements to facilitate communication between application clients (ACs) running on user equipment (UE) and edge-deployed applications (ACs). enabling layer specification.
- edge applications provided by Edge Application Servers (EASs) are sent to the UE's ACs by Edge Configuration Servers (ECS) and Edge Enabler Servers (EES) to the UE's Edge Enabler Clients (EEC).
- the AC running on the UE needs to discover the server application on the edge cloud (i.e., EAS in 3GPP SA6 terminology, or MEC application in ETSI ISG MEC terminology).
- the AC can make use of other clients on the UE, namely the EEC, for server application discovery.
- the EEC provides ACs with discovery of available EASs in edge data networks.
- the UE is initially provisioned from ECS with the information necessary to connect to the Edge Data Network (EDN).
- EDN includes one or more EESs and one or more EASs. More specifically, the UE's EEC communicates with the ECS for service provisioning.
- Service provisioning refers to populating the EEC with information about available edge computing services based on UE location, service requirements, service performances and connectivity. to enable.
- the configuration contains the address information required by the EEC to establish a connection with one or more EESs located in the EDN.
- the EEC makes a service provisioning request to the ECS in order to request resources for service provision in the EDN and information on connection or configuration.
- Information about connection or configuration for example, information about available edge computing services (services), server information in EDN, identifier (ID) and address information (e.g., Internet Protocol (IP) address , Single-Network Slice Selection Assistance Information (S-NSSAI), and service area information), EDN configuration information, and configuration information about the Edge Data Network for the EEC to establish connectivity.
- the EEC performs a registration procedure called EEC registration with the EES in order to provide information that can be used by the EES in edge computing services.
- EEC registration allows the initialization, update and removal of EEC information resources in the EES.
- EEC registration enables sharing of EEC Context between each entity (UE and Application Server) of the EDGEAPP architecture.
- the determination of whether or not EEC registration is permitted is based on Security credentials and/or at least one Application Client Profile (AC Profile(s)) provided by the EEC.
- the EEC makes an EEC registration request to the EES.
- Non-Patent Document 1 EES verifies security credentials provided by EEC, and if AC Profile(s) is provided by EEC, it can satisfy the requirements included in AC Profile(s). to judge whether
- EEC registration requests EEC registration request or EEC registration update request
- requests EEC registration requests
- edge servers include one or more EESs and one or more EASs.
- EEC requesting entity
- One of the objectives to be achieved by the embodiments disclosed in this specification is to provide an apparatus, method, and program that contribute to solving at least one of the above-described problems. It should be noted that this objective is only one of the objectives that the embodiments disclosed herein seek to achieve. Other objects or problems and novel features will become apparent from the description of the specification or the accompanying drawings.
- a first server includes at least one memory and at least one processor coupled to said at least one memory.
- the at least one processor receives a request from the requesting entity to generate an Edge Enabler Client (EEC) Context that includes Security credentials and at least one Application Client Profile and is information about the requesting entity, and transmits the Security credentials.
- EEC Edge Enabler Client
- the at least one processor is configured to, upon identifying the second server, send a first response message to the requesting entity including information indicating that the request was successful.
- the at least one selection criterion includes requirements indicated in the at least one Application Client Profile.
- a method performed by a first server includes the following steps: (a) receiving a request from a requesting entity to create an Edge Enabler Client (EEC) Context that is information about the requesting entity and that includes Security credentials and at least one Application Client Profile; (b) determining whether access to the edge data network can be granted by verifying the security credentials; (c) attempting to identify a second server located within said edge data network based on at least one selection criterion if access to said edge data network can be granted; (d) upon identifying the second server, sending to the requesting entity a first response message containing information indicating that the request was successful, wherein the at least one selection criterion comprises: including the requirements set forth in at least one Application Client Profile; and (e) if access to the edge data network cannot be granted or does not meet the requirements set forth in the at least one Application Client Profile, the second Sending to the requesting entity a second response message containing a failure cause, which is information indicating that the server cannot be determined.
- EEC Edge Enable
- the requesting entity includes at least one memory and at least one processor coupled to said at least one memory.
- the at least one processor sends a request to a first server to generate an Edge Enabler Client (EEC) Context that includes Security credentials and at least one Application Client Profile and is information about the requesting entity; from the first server.
- the at least one processor transmits the request to a first server different from the first server if the response message includes a failure cause that is information indicating that the second server cannot be specified. wherein the failure cause is included in the response message if access to the edge data network cannot be permitted or the requirements indicated in the at least one Application Client Profile are not met.
- EEC Edge Enabler Client
- a method performed by a requesting entity includes the following steps: (a) sending a request to a first server to generate an Edge Enabler Client (EEC) Context that includes Security credentials and at least one Application Client Profile and is information about the requesting entity; (b) receiving a response message to the request from the first server; and (c) if the response message includes a failure cause that is information indicating that the second server cannot be identified, then the first sending said request to a first server different from the server of said at least one Application Client Profile, wherein said failure cause is if access to an edge data network cannot be granted or a requirement indicated in said at least one Application Client Profile is not satisfied, it is included in the response message.
- EEC Edge Enabler Client
- the program includes a group of instructions (software code) for causing the computer to perform the method according to the above second or fourth aspect when read into the computer.
- FIG. 4 is a flow chart showing an example of the operation of the first server according to the embodiment; 4 is a flow chart showing an example of the operation of the first server according to the embodiment; 4 is a flowchart illustrating an example operation of a requesting entity according to an embodiment; FIG. 4 is a sequence diagram showing an example of EEC and EES operations according to the embodiment; 4 is a flowchart illustrating an example operation of a requesting entity according to an embodiment; FIG. 4 is a sequence diagram showing an example of EEC and EES operations according to the embodiment; FIG. 4 is a sequence diagram showing an example of EEC and ECS operations according to the embodiment; 2 is a block diagram showing a configuration example of a UE according to an embodiment; FIG. It is a block diagram which shows the structural example of the server which concerns on embodiment.
- 3GPP system e.g., 5G system (5GS)
- 5GS 5G system
- these embodiments may be applied to other wireless communication systems.
- FIG. 1 shows an example of network architecture according to this embodiment.
- the architecture of Figure 1 corresponds to the 3GPP EDGEAPP architecture.
- Each of the elements shown in FIG. 1 is a functional entity, providing functionality and interfaces defined by 3GPP.
- Each element (functional entity) shown in FIG. 1 can be, for example, a network element on dedicated hardware, a software instance running on dedicated hardware, or an application platform. It can be implemented as an instantiated virtualization function.
- User Equipment (UE) 1 includes Edge Enabler Client (EEC) 2 and one or more Application Clients (ACs) 3.
- EEC 2 and one or more ACs 3 are located in UE1 and operate on UE1.
- the UE 1 uses the access network (e.g., Radio Access Network (e.g., NG Radio Access Network (NG-RAN))) via the 3GPP core network 8 (e.g., 5G Core 5GC)).
- the 3GPP core network 8 e.g., 5G Core 5GC
- EEC2 provides the supporting functions required by AC(s)3. Specifically, EEC2 provides provisioning of configuration information to enable exchange of application data traffic with an Edge Application Server (EAS). Additionally, EEC 2 provides functionality for discovery of one or more EASs available within Edge Data Network (EDN) 4 . The EEC2 uses the EAS endpoint information obtained in EAS discovery for routing outgoing application data traffic to the EAS. In addition, EEC2 provides EES5 and EAS(s)6 registration (i.e., registration, update, and de-registration) functionality.
- EES5 and EAS(s)6 registration i.e., registration, update, and de-registration
- Each AC3 is an application that runs on UE1. Each AC3 connects to one or more EASs and exchanges application data traffic with these EASs in order to utilize edge computing services.
- EDN4 includes one or more Edge Enabler Servers (EES) 5 and one or more Edge Application Servers (EASs) 6.
- EDN4 may be a Local Area Data Network (LADN).
- LADN allows restricted access to a DN (and corresponding Data Network Name (DNN)) in only one or more specific areas. Outside the area, UE1 cannot access the DN (and DNN).
- Areas where LADN DNNs are available are called LADN Service Areas and are configured in the network as a set of Tracking Areas (TAs). DNNs not using LADN features do not have LADN service areas and are not restricted by such features.
- TAs Tracking Areas
- the LADN service area is provided to UE1 by the Access and Mobility Management Function (AMF) in 3GPP core network 8 when UE1 registers. This allows UE1 to know the area where the LADN (or EDN) is available, and does not attempt to access the LADN (or EDN) outside this area.
- AMF Access and Mobility Management Function
- Each EES5 provides supporting functions required by EAS(s)6 and EEC2. Specifically, each EES 5 provides provisioning of configuration information to the EEC 2, thereby enabling exchange of application data traffic with the EAS(s) 6.
- Each EES 5 provides the functionality of EEC 2 and EAS(s) 6 registration (i.e., registration, update, and de-registration).
- Each EES 5 provides the functionality of application context transfer between EESs. This functionality is required for edge application mobility (or application context relocation) for service continuity.
- Edge application mobility relocates an application context or application instance or both for a user (ie AC) from a source EAS (or EDN or LADN) to a target EAS (or EDN or LADN).
- Edge application mobility is triggered by UE mobility events or non-UE mobility events.
- UE mobility events include, for example, intra-EDN UE mobility, inter-EDN UE mobility, and LADN-related UE mobility.
- Non-UE mobility events include, for example, EAS or EDN overload situations, and EAS maintenance (eg, EAS graceful shutdown).
- each EES5 supports the functions of Application Programming Interface (API) invoker and API exposing function.
- Each EES 5 communicates directly (e.g., via Policy Control Function (PCF)) or indirectly with the 3GPP core network 8 to access the services and capabilities of network functions within the 3GPP core network 8. directly (e.g., via Network Exposure Function (NEF) or Service Capability Exposure Function (SCEF)).
- PCF Policy Control Function
- NEF Network Exposure Function
- SCEF Service Capability Exposure Function
- Each EES 5 may support external exposure of 3GPP network functional services and capabilities to the EAS(s) 6 .
- Each EAS 6 is located in the EDN 4 and executes application server functions.
- Application server functionality may be available only at the edge. In other words, the application's server functionality may only be available as an EAS. However, application server functionality may be available both at the edge and in the cloud. In other words, the application server function may be available as an EAS and additionally as an application server in the cloud. Cloud here means a central cloud located farther from UE1 than EDN4. An application server in the cloud therefore means a server located in a centralized location (e.g., centralized data center).
- Each EAS 6 may consume or utilize 3GPP core network capabilities. Each EAS 6 may directly invoke the 3GPP core network function API. Alternatively, each EAS 6 may consume or utilize 3GPP core network capabilities via EES 5 or via NEF or SCEF.
- the Edge Configuration Server (ECS) 7 provides the supporting functions required by the EEC 2 to connect to the EES(s) 5. Specifically, ECS 7 provides provisioning of edge configuration information to EEC 2 .
- Edge setting information includes information to EEC 2 for connecting to EES(s) 5 (e.g., service area information applicable to LADN), and information for establishing connection with EES(s) 5. Contains information (e.g., Uniform Resource Identifier (URI)).
- ECS7 provides EES(s)5 registration (i.e., registration, update, and de-registration) functionality.
- ECS7 supports API invoker and API exposing function functions.
- the ECS 7 communicates directly (e.g., via PCF) or indirectly (e.g., NEF) with the 3GPP core network 8 to access the services and capabilities of network functions within the 3GPP core network 8. or via SCEF).
- the ECS 7 may be located within the Mobile Network Operator (MNO) domain that provides the 3GPP core network 8, or may be located in a third-party domain of a service provider (e.g., Edge Computing Service Provider (ECSP)) .
- MNO Mobile Network Operator
- ECSP Edge Computing Service Provider
- ECS 7 may be connected to multiple EDNs, including EDN 4 .
- FIG. 2 is a flow chart showing an example of the operation of the first server according to this embodiment.
- the first server attempts to identify (discover, select or determine) a preferred or suitable edge server located at EDN 4 in the EEC registration.
- the first server may be EES5 and may attempt to identify one or more EAS(s) upon request from EEC2 of UE1.
- the first server receives a request from a requesting entity.
- the requesting entity may be EEC2 and the first server may be EES5.
- the request may be an EEC registration request or an EEC registration update request.
- the request is also referred to herein as an EEC registration request.
- the first server upon receiving the request, the first server verifies the Security credentials included in the request. Upon verification of the Security credentials, it is determined that the first server can allow access to the edge data network (YES at step 203 ), the procedure proceeds to step 204 .
- the first server attempts to identify a second server that is located within EDN 4 and satisfies at least one selection criterion. In other words, the first server identifies the second server located within EDN 4 based on at least one selection criterion.
- at least one factor considered in at least one selection criterion includes the requirements (at least one AC Profile (AC Profile(s)) included in the request.
- AC Profile(s) may indicate multiple items. Each item exhibits one or more property sets. For example, it includes at least one of "Application Client Type", “Application Client Schedule”, “Expected Application Client Geographical Service Area”, “Service Continuity Support”, or "List of EASs”.
- Application Client Type indicates the AC3 application category or type (e.g., V2X).
- Application Client Schedule indicates AC3's expected operation schedule, eg, time window.
- the Expected Application Client Geographical Service Area indicates the expected location(s) of UE1 during AC3's expected operating schedule, eg a route.
- Service Continuity Support indicates whether service continuity support is required for AC3.
- the List of EASs contains EAS IDs and may further contain Expected Service Key Performance Indicators (KPIs) and Minimum required Service Key Performance Indicators (KPIs).
- Service KPIs indicate service characteristics required by AC3. These service characteristics may be, for example, connection bandwidth, maximum request rate to be generated by the AC, maximum response time, maximum compute resources required by the AC, maximum memory resources required by the AC, or Information specific to the AC type (e.g., video, Virtual Reality (VR), etc.).
- the first server may identify EAS(s) that match the provided AC Profile. The first server may then identify EAS(s) that match all items contained in the AC Profile. Alternatively, the first server may identify EAS(s) that match at least one item contained in the AC Profile. Alternatively, the first server may identify EAS(s) that match all items except the "List of EASs" contained in the AC Profile. Alternatively, the first server may identify EAS(s) that match at least one item other than the "List of EASs" contained in the AC Profile.
- the first server may identify EAS(s) that match at least one item included in the Expected Service KPIs. Alternatively, the first server may identify EAS(s) that match all items included in the Expected Service KPIs.
- the Application Client profile contains other items besides "List of EASs" (i.e., "Application Client Type”, “Application Client Schedule”, “Expected Application Client Geographical Service Area”, “Service Continuity Support”) If so, it may identify EAS(s) that also match at least one such other item in addition to the Expected Service KPIs match described above.
- the first server may identify EAS(s) that match at least one item included in the Minimum required Service KPIs. Alternatively, the first server may identify EAS(s) that match all items included in the Minimum required Service KPIs.
- the Application Client profile contains other items besides "List of EASs" (i.e., "Application Client Type”, “Application Client Schedule”, “Expected Application Client Geographical Service Area”, “Service Continuity Support”) If so, the first server may identify EAS(s) that also match at least one such other item in addition to the Minimum required Service KPIs match described above.
- the first server identifies EAS(s) per AC Profile as described above.
- identifying the EAS(s) may mean that the EAS's information (e.g., characteristics, capabilities, status) matches information about the Application Client contained in the AC Profile.
- this may mean that the EAS's information (e.g., characteristics, performance, status) satisfies the conditions for the Application Client contained in the AC Profile.
- the first server excludes from the selection the second server that determines that it does not meet the requirements (AC Profile(s)) included in the request.
- the second server is the EAS.
- other factors considered in at least one selection criterion are the congestion status of the servers located in EDN4, the location of UE1 (UE location), and the availability of the second server (i.e., EAS). At least one of them may be included.
- the congestion status of the server may indicate whether the server is congested. Alternatively, the congestion status may indicate one of three or more levels of congestion (eg, no congestion, low congestion, medium congestion, high congestion).
- a congestion state may be referred to as a load state.
- the first server may identify a second server that is not congested and satisfies the remaining selection criteria. In one example, the first server may exclude the second server determined to be in a congested state (high load state) from selection targets.
- the second server may dynamically notify the first server of its congestion state. More specifically, the second server notifies the first server of its congestion state when registering the second server with the first server, and notifies the congestion state in response to the change of the congestion state.
- a status update may be communicated to the first server.
- each EAS 6 may notify the EES 5 of its congestion state in the Edge Application Server Registration procedure, and notify the EES 5 of its congestion state update in the Edge Application Server Registration Update procedure.
- the second server may periodically notify the first server of its congestion state.
- the first server may monitor the life and death of the second server. More specifically, when the first server determines that the second server cannot provide the service due to a failure of the second server or a failure of the communication path with the second server, the first server server may manage the second server as critically congested. Alternatively, if the second server undergoes a planned service interruption, such as when it undergoes maintenance, the second server may notify the first server to that effect. In one example, the first server may exclude from selection the second server determined to be unable to provide the service. Alternatively, the first server may obtain the congestion status of the second server from a Network Data Analytics Function (NWDAF) not explicitly shown in FIG. In this case, the first server can obtain congestion information for each second server, each EAS, or each EES by subscribing to a congestion-related service provided by the NWDAF.
- NWDAF Network Data Analytics Function
- the second server may determine whether or not there is congestion, and provide the first server with congestion state information indicating whether or not there is congestion.
- the congestion state information is not limited to two levels.
- the second server may identify one of three or more levels of congestion (e.g., no congestion, low congestion, medium congestion, high congestion) and inform the first server of the identified congestion level. good.
- the congestion state information may be information indicating one of three or more congestion levels.
- the UE location may specify the network to which UE1 is connected or the position of the UE.
- UE location values may be Cell Identity (ID), Tracking Area Identity (TAI), Global Positioning System (GPS) Coordinates, or civic address.
- Selection criteria regarding UE location for selection of EAS(s) by EES5 may require that the location of UE1 is within the EAS service area.
- the EAS service area may be a topological service area or a geographical service area.
- a topological coverage area may be defined by one or more cell IDs and may be defined by one or more TAIs.
- the first server may identify a second server whose UE location is within the EAS (second server) coverage area and fulfills the remaining selection criteria.
- the first server may exclude from selection a second server that is determined to be out of the EAS (second server) service area.
- the EAS service area may be a topological service area (e.g., Cell ID(s), or TAI(s)) or a geographical service area.
- the EAS service area may be the same as or a subset of the EDN service area.
- the EAS service area may be the same as or a subset of the EES service area.
- step 205 the first server responds to the request with a response message containing a failure cause indicating that access to the edge data network cannot be granted.
- the first server may respond to the request with a response message containing a failure cause indicating that the second server (EAS) cannot be determined.
- step 207 the first server (i.e., EES5) sends a response message to the requesting entity (i.e., EEC2) containing information indicating that the request was successful.
- EES5 the first server
- EEC2 the requesting entity
- step 208 the first server (i.e., EES5) responds to the request with a response message containing a failure cause indicating that the requirements contained in the request cannot be met.
- the first server i.e., EES5
- the first server may respond to the request with a response message containing a failure cause indicating that the second server (EAS) cannot be determined.
- the first server selects a preferred or appropriate second A server can be identified, discovered, selected, or determined.
- the first server sends a response message containing a failure cause to the requesting entity when the second server is congested and the failure message sent when the second server cannot find (identify). May be distinguished from a response message containing a failure cause.
- the failure cause value set in the response message if the second server is congested may be different than that set in the response message if the second server cannot be found (determined). This allows the requesting entity to distinguish between types of response messages (or types of failure causes). Furthermore, the requesting entity can take different actions depending on the type of response message (or type of failure cause).
- the response message may indicate a requesting entity-dependent error or condition, specifically HTTP Status code 404 Not Found.
- the cause of failure included in the response message may be information included in Application Client profiles or a value indicating that the conditions cannot be satisfied, specifically "RESOURCE_NOT_FOUND".
- failure based on selection criteria for Application Client profiles here may be failure when EAS(s) matching Application Client profiles are not found.
- the requesting entity e.g., EEC2
- receives a response message containing a failure cause it may act as follows.
- EEC2 aborts EEC registration.
- EEC2 may resend the EEC registration request. If the number of retransmissions reaches a predetermined maximum number, the EEC2 aborts the EEC registration.
- EEC2 may send an EEC registration update request.
- EEC2 may send an EEC de-registration request.
- EEC2 may inform AC3 of the failure cause (or error).
- EEC2 may map failure causes (or errors) to AC-specific failure causes (or errors).
- EEC2 may transparently forward the failure cause (or error) to AC3.
- the EEC 2 may suppress transmission of EEC registration request or EEC registration update request based on the cause of failure of the response message.
- the EEC 2 may suppress transmission of the EEC registration request or the EEC registration update request until the Application Client profiles or part of the information contained therein is changed.
- the EEC registration request or EEC registration update that seeks or contains the same information resource (EEC Context) creation as the failed request until the Application Client profiles or some of the information contained in them is changed.
- Sending of request may be suppressed.
- EEC2 may send an EEC registration request to another EES different from EES5.
- another EES different from the EES 5 may be set in the UE or Mobile Equipment (ME) in advance in the service provisioning procedure.
- the different EES may be selected based on a policy preset in the UE or ME, or may be selected based on the policy of AC3.
- EEC2 will perform a service provisioning request procedure to ECS7 to obtain new EES(s) from ECS7. ) information and may attempt EEC registration with the new EES indicated (configured) in the obtained information.
- the message may indicate a server-dependent error or condition, specifically HTTP Status code 503 Service Unavailable.
- the EEC 2 may operate as follows in the same manner as in the case of receiving a response message containing a failure cause based on the selection criteria for Application Client profiles. For example, EEC2 may abort EEC registration. Alternatively, EEC2 may resend the EEC registration request.
- EEC2 may abort EEC registration if the number of retransmissions of the request (e.g., EEC registration request) reaches a predetermined maximum number.
- EEC2 may send an EEC registration update request.
- EEC2 may send an EEC de-registration request.
- EEC2 may inform AC3 of the failure cause (or error).
- EEC2 may map failure causes (or errors) to AC-specific failure causes (or errors).
- EEC2 may transparently forward the failure cause (or error) to AC3.
- the EEC 2 may suppress transmission of the EEC registration request or EEC registration update request based on the failure cause of the response message.
- the EEC 2 may suppress transmission of the EEC registration request or the EEC registration update request until the Application Client profiles or part of the information contained therein is changed. In other words, the EEC2 will not send an EEC registration request or an EEC registration update request containing the same resource or information as the failed request until the Application Client profiles or some of the information contained in them are changed. good.
- EEC2 may send an EEC registration request to another EES different from EES5. Note that another EES different from EES5 may be set in EEC2 in advance in the service provisioning procedure. Also, a different EES may be selected based on a policy set in advance by the UE or ME, or may be selected based on the policy of AC3.
- EEC2 will perform a service provisioning request procedure to ECS7 to obtain new EES(s) from ECS7. ) information and may attempt EEC registration with the new EES indicated (configured) in the obtained information.
- the first server explicitly or implicitly indicates in the response message that the requesting entity should back off before sending the next request.
- the first server may include in the response message a failure cause indicating that the second server is congested. The failure cause implies that backoff is required.
- the first server may include in the response message a value indicating a particular backoff time, a value indicating a maximum backoff time, or parameters for deriving any of these. .
- the backoff time may also be referred to as a backoff period or backoff window.
- the requesting entity MAY send the next request without backoff if the response message does not indicate that backoff is required. For example, the requesting entity may resend the request message, including the missing information indicated by the failure cause contained in the received response message.
- the requesting entity will backoff before sending the next request. In other words, the requesting entity delays sending the next request until at least the backoff time has passed.
- the backoff time may be specified by the first server or derived by the requesting entity.
- the requesting entity may determine a random backoff time up to the maximum backoff time.
- FIG. 3 is a flow chart showing an example of the operation of the first server according to this embodiment.
- the first server attempts to identify (discover, select or determine) a preferred or suitable edge server located at EDN4.
- the first server may be EES5 and may attempt to identify one or more EASs upon request from EEC2.
- Steps 301-307 are the same as steps 201-207 in FIG.
- the first server i.e., EES5
- the first server responds to the request with a response message containing a failure cause indicating that it is congested.
- the message explicitly or implicitly indicates that a backoff is required before sending the next request. Specifically, if the request fails because the second server is congested (or under high load), the first server indicates in a response message that backoff is required. good too.
- step 307 if the second server is congested (or is in a high load state) but it is determined that the second server can be used, the first server corresponds to the second server. A response message MAY indicate the need for backoff.
- FIG. 4 is a flow chart showing an example of the operation of the requesting entity according to this embodiment.
- the requesting entity may be EEC2.
- the requesting entity sends a request to the first server (e.g., EES5).
- the requesting entity receives a response message from the first server.
- step 402 If the response message in step 402 does not contain a failure cause (NO in step 403), the procedure proceeds to step 404.
- the requesting entity e.g., EEC2 notifies the AC that the request was successful. Note that if the response message in step 402 indicates that a backoff is required, notify the AC that the request was successful and a backoff is required. An AC that is notified that a backoff is required may, for example, send a signal to the EAS after doing the backoff.
- step 403 the procedure proceeds to step 405.
- the requesting entity determines whether the response message indicates that backoff is required. If no backoff is required (NO in step 405), the requesting entity may send the next request without backoff (step 406). If a backoff is required (YES in step 405), the requesting entity does a backoff before sending the next request.
- the first server can delay sending the next request by the requesting entity.
- the request fails due to congestion on the second server, delaying the sending of the next request by the requesting entity can be expected to eliminate or reduce the congestion on the second server.
- FIG. 5 shows an example of operations of EEC2 and EES5 in the EEC registration procedure based on the Request/Response model.
- EEC2 in FIG. 5 corresponds to the requesting entity mentioned above and EES5 in FIG. 5 corresponds to the first server mentioned above.
- EEC2 sends EEC registration request or EEC registration update request to EES5 as the above request.
- the EES 5 verifies the Security credentials contained in the request (corresponding to step 202 of FIG. 2 and step 302 of FIG. 3) and attempts to identify at least one EAS that satisfies at least one selection criterion. (corresponding to step 204 in FIG. 2 and step 304 in FIG. 3). At least one selection criterion considers the requirements (AC Profile(s)) contained in the request. Further, the at least one selection criterion may consider at least one of EAS congestion status, UE location and EAS activity status. At least one selection criterion may consider other factors, eg UE-specific service information in EES5, or ECSP policy. As described with reference to FIG. 3 (step 308), EES 5 responds to EEC 2's request with a response message containing a failure cause if it cannot identify an EAS that satisfies at least one selection criterion. .
- EES 5 responds to EEC 2's request with EEC registration response or EEC registration update response.
- FIG. 5 shows the case where EEC2's request fails. Therefore, the response message of step 503 contains the cause of failure. Furthermore, if the EAS is congested (highly loaded), the response message will either explicitly or implicitly indicate that a backoff is required. A backoff timer value may also be set in the response message in step 503 if the response message explicitly indicates that a backoff is required.
- EEC2 delays sending the next request until at least the backoff time has passed.
- the EEC registration response or EEC registration update response of step 503 may explicitly or implicitly indicate that backoff is required. For example, access from EEC2 to the EAS may be allowed if the EAS is congested but after some backoff action. In this case, at step 504, the EEC2 delays sending the request to the EAS at least until the backoff time has passed.
- This embodiment provides another example of the operation of the first server and the requesting entity.
- An example network architecture according to this embodiment is similar to the example described with reference to FIG.
- the first server may distinguish response messages sent to the requesting entity in an EEC registration when the second server is not operational from response messages sent when the second server cannot be found. good.
- the failure cause value set in the response message if the second server is not up may be different than that set in the response message if the second server cannot be found. This allows the requesting entity to distinguish between types of response messages (or types of failure causes). Furthermore, the requesting entity can take different actions depending on the type of response message (or type of failure cause).
- the requesting entity may act as follows: . If the message is due to the fact that the second server (i.e., EAS) is not operational, EEC2 aborts the EEC registration without retransmitting the EEC registration request or EEC registration update request ( abort). On the other hand, if the message is due to the fact that the second server (i.e., EAS) is not found, EEC2 will resend the EEC registration request or EEC registration update request.
- This embodiment provides a variation of the operation of the first server and requesting entity described in the first embodiment.
- An example network architecture according to this embodiment is similar to the example described with reference to FIG.
- the requesting entity may be EEC2 and the first server may be EES5.
- the requesting entity i.e., EEC2
- EES5 may send an EEC registration request to another EES different from the first server (i.e., EES5) if the EEC registration request fails.
- another EES different from the first server may be preconfigured in the UE or ME in the service provisioning procedure.
- the different EES may be selected based on a policy preset in the UE or ME, or may be selected based on the policy of AC3.
- EEC2 will perform a service provisioning procedure to ECS7 to ensure that new EES(s) from ECS7. It may obtain the information and attempt EEC registration with the new EES indicated (configured) in the obtained information.
- FIG. 6 is a flow chart showing an example of the operation of the requesting entity (i.e., EEC2) according to this embodiment.
- the requesting entity sends an EEC registration request to the first server.
- the first server attempts to identify (discover, select or determine) a preferred or suitable edge server located at EDN4.
- the first server may be EES5 and may attempt to identify one or more EASs upon request from EEC2.
- Steps 601-604 are the same as steps 401-404 in FIG. If the response message in step 602 contains a failure cause (YES in step 603), the procedure proceeds to step 605; If there are still EESs for which EEC registration has not been attempted among the EESs set in the UE or ME (NO in step 605), the EEC2 selects another EES different from the first server (step 606 ), returning to step 601 to attempt EEC registration with the other EES.
- the EEC2 executes the service provisioning procedure for the ECS7, so that the new EES from the ECS7. (s) Acquire information (step 607).
- the EEC 2 then returns to step 601 and attempts EEC registration for the new EES indicated (set) by the new information obtained.
- FIG. 7 shows an example of operations of EEC2 and EES5 in the EEC registration procedure based on the Request/Response model.
- EEC2 in FIG. 5 corresponds to the requesting entity mentioned above and EES5 in FIG. 5 corresponds to the first server mentioned above.
- Steps 701 and 702 are similar to steps 501 and 502 in FIG.
- EES5 responds to EEC2's request with an EEC registration response or EEC registration update response.
- FIG. 7 shows the case where EEC2's request fails. Therefore, the response message of step 703 contains the cause of failure.
- the EEC 2 executes a service provisioning procedure for the ECS 7 (not shown) to obtain new EES(s) information from the ECS 7. to get
- the EEC 2 attempts EEC registration by sending an EEC registration request to the new EES 51 indicated (set) by the new EES(s) information obtained at step 704.
- FIG. 8 corresponds to step 704 in FIG. 7 and shows an example of the operation of EEC2 and ECS7 in the service provisioning procedure based on the Request/Response model.
- EEC2 sends a service provisioning request to ECS7.
- ECS 7 attempts to identify at least one EES that satisfies at least one selection criterion. At least one selection criterion considers the congestion state of the EES. Additionally, the at least one selection criterion may consider one or both of the UE location and at least one Application Client profile provided by the EEC 2 via the request of step 501 . At least one selection criterion may consider other factors, eg UE-specific service information in ECS 7 or ECSP policy.
- ECS7 responds to EEC2's request with a service provisioning response.
- the response message may contain EDN configuration information, and the EDN configuration information may contain information indicating an EES (i.e., EES51) different from EES5.
- the EDN configuration information may contain information indicating multiple items. Each item exhibits one or more property sets.
- EDN configuration information includes "EDN connection information" and "List of EESs", and further includes "Lifetime”.
- EDN connection information indicates information required for EDN connection.
- the information required for EDN connection includes DNN or Access Point Name (APN) and at least one of S-NSSAI or EDN Topological Service Area.
- List of EESs indicates the EES list of the EDN.
- the EES list includes EES ID and EES Endpoint, and at least one of EASIDs, ECSP info, EES Topological Service Area, EES Geographical Service Area, or List of EES DNAI(s). Lifetime indicates the validity period of the EDN configuration information.
- FIG. 9 is a block diagram showing a configuration example of UE1.
- Radio Frequency (RF) transceiver 901 performs analog RF signal processing to communicate with RAN nodes.
- RF transceiver 901 may include multiple transceivers.
- Analog RF signal processing performed by RF transceiver 901 includes frequency upconversion, frequency downconversion, and amplification.
- RF transceiver 901 is coupled with antenna array 902 and baseband processor 903 .
- RF transceiver 901 receives modulation symbol data (or OFDM symbol data) from baseband processor 903 , generates transmit RF signals, and provides transmit RF signals to antenna array 902 .
- RF transceiver 901 also generates baseband received signals based on the received RF signals received by antenna array 902 and provides them to baseband processor 903 .
- RF transceiver 901 may include analog beamformer circuitry for beamforming.
- the analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
- the baseband processor 903 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
- Digital baseband signal processing consists of (a) data compression/decompression, (b) data segmentation/concatenation, (c) transmission format (transmission frame) generation/decomposition, and (d) channel coding/decoding. , (e) modulation (symbol mapping)/demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT).
- control plane processing consists of layer 1 (e.g., transmit power control), layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., attach, mobility and call management). related signaling) communication management.
- layer 1 e.g., transmit power control
- layer 2 e.g., radio resource management and hybrid automatic repeat request (HARQ) processing
- layer 3 e.g., attach, mobility and call management
- the digital baseband signal processing by the baseband processor 903 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer signal processing may be included.
- SDAP Service Data Adaptation Protocol
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- PHY Physical
- Control plane processing by the baseband processor 903 may also include processing of Non-Access Stratum (NAS) protocols, Radio Resource Control (RRC) protocols, MAC Control Elements (CEs), and Downlink Control Information (DCIs).
- NAS Non-Access Stratum
- RRC Radio Resource Control
- CEs MAC Control Elements
- DCIs Downlink Control Information
- the baseband processor 903 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.
- MIMO Multiple Input Multiple Output
- the baseband processor 903 includes a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit ( MPU)).
- DSP Digital Signal Processor
- a protocol stack processor e.g., Central Processing Unit (CPU) or Micro Processing Unit ( MPU)
- the protocol stack processor that performs control plane processing may be shared with the application processor 904, which will be described later.
- the application processor 904 is also called CPU, MPU, microprocessor, or processor core.
- the application processor 904 may include multiple processors (multiple processor cores).
- the application processor 904 includes a system software program (Operating System (OS)) read from the memory 906 or a memory (not shown) and various application programs (e.g., call application, WEB browser, mailer, camera operation application, music playback, etc.).
- OS Operating System
- application programs e.g., call application, WEB browser, mailer, camera operation application, music playback, etc.
- Various functions of the UE 1 are realized by executing the application).
- the baseband processor 903 and application processor 904 may be integrated on one chip, as indicated by the dashed line (905) in FIG.
- baseband processor 903 and application processor 904 may be implemented as one System on Chip (SoC) device 905 .
- SoC devices are sometimes called system Large Scale Integration (LSI) or chipsets.
- the memory 906 is volatile memory, non-volatile memory, or a combination thereof.
- Memory 906 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
- the non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof.
- memory 906 may include external memory devices accessible from baseband processor 903 , application processor 904 , and SoC 905 .
- Memory 906 may include embedded memory devices integrated within baseband processor 903 , within application processor 904 , or within SoC 905 .
- memory 906 may include memory within a Universal Integrated Circuit Card (UICC).
- UICC Universal Integrated Circuit Card
- the memory 906 may store one or more software modules (computer programs) 907 containing instructions and data for processing by the UE 1 as described in multiple embodiments above.
- the baseband processor 903 or the application processor 904 is configured to read and execute the software module 907 from the memory 906 to perform the processing of the UE1 described with reference to the drawings in the above embodiments. may be
- control plane processing and operations performed by UE 1 as described in the above embodiments are performed by other elements apart from RF transceiver 901 and antenna array 902, namely baseband processor 903 and/or application processor 904 and software module 907. can be implemented by a memory 906 that stores the
- FIG. 10 shows a configuration example of EES5.
- EES 6, ECS 7, and EES 51 may also have a configuration similar to that shown in FIG.
- EES5 (or EAS6 or ECS7) includes network interface 1001, processor 1002 and memory 1003.
- FIG. Network interface 1001 is used, for example, to communicate with other network functions (NFs) or nodes.
- Network interface 1001 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).
- NIC network interface card
- the processor 1002 may be, for example, a microprocessor, Micro Processing Unit (MPU), or Central Processing Unit (CPU). Processor 1002 may include multiple processors.
- MPU Micro Processing Unit
- CPU Central Processing Unit
- the memory 1003 is composed of a volatile memory and a nonvolatile memory.
- Memory 1003 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof.
- SRAM Static Random Access Memory
- DRAM Dynamic RAM
- the non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof.
- Memory 1003 may include storage remotely located from processor 1002 . In this case, processor 1002 may access memory 1003 via network interface 1001 or an I/O interface (not shown).
- the memory 1003 stores one or more software modules (computer programs) 1004 including instruction groups and data for performing processing by EES5 (or EAS6 or ECS7) described in the above embodiments. good too.
- the processor 1002 may be configured to read and execute the software module 1004 from the memory 1003 to perform the EES5 (or EAS6 or ECS7) processing described in the above embodiments. good.
- each of the processors of the UE 1, EES 5, EAS 6, and ECS 7 provides instructions for causing a computer to execute the algorithm described using the drawings. Run one or more programs containing the group.
- the program can be stored and delivered to computers using various types of non-transitory computer readable media.
- Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (e.g. floppy disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g. magneto-optical discs), Compact Disc Read Only Memory (CD-ROM), CD-ROM Includes R, CD-R/W, semiconductor memory (e.g.
- the program may also be delivered to the computer on various types of transitory computer readable medium.
- Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves.
- Transitory computer-readable media can deliver the program to the computer via wired channels, such as wires and optical fibers, or wireless channels.
- a wireless terminal in this specification is an entity connected to a network via a wireless interface.
- a wireless terminal (UE) herein is not limited to a dedicated communication device, and may be any device having the communication capabilities of the wireless terminal (UE) described herein, such as: may
- UE User Equipment
- mobile station mobile terminal
- mobile device mobile device
- wireless device wireless device
- UE wireless device
- UE is a stand-alone mobile station such as a terminal, mobile phone, smartphone, tablet, cellular IoT terminal, IoT device, etc.
- UE and wireless terminal also encompass devices that are stationary for extended periods of time.
- UE for example, production equipment / manufacturing equipment and / or energy-related machinery (examples include boilers, engines, turbines, solar panels, wind power generators, hydraulic power generators, thermal power generators, nuclear power generators, storage batteries, nuclear power systems, Nuclear equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metal processing machines, manipulators, robots, robot application systems, tools, dies, rolls, transfer equipment, Lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing machinery, printing-related machinery, paper processing machinery, chemical machinery, mining machinery, mining-related machinery, construction machinery, construction-related machinery, agricultural machinery and/or implements, forestry Machinery and/or equipment, fishing machinery and/or equipment, safety and/or environmental protection equipment, tractors, bearings, precision bearings, chains, gears, power transmissions, lubrication systems, valves, pipe fittings and/or or any of the equipment or machine application systems described above).
- UE is, for example, a transportation device (for example, vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, balloons, etc.). There may be.
- a transportation device for example, vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, balloons, etc.
- a UE may be, for example, an information communication device (eg, a computer and related devices, a communication device and related devices, electronic components, etc.).
- an information communication device eg, a computer and related devices, a communication device and related devices, electronic components, etc.
- UE includes, for example, refrigeration machines, refrigeration-applied products and equipment, commercial and service equipment, vending machines, automatic service machines, office machinery and equipment, consumer electrical and electronic equipment (such as audio equipment, speakers, radios, video equipment, televisions, microwave ovens, rice cookers, coffee makers, dishwashers, washing machines, dryers, fans, ventilation fans and related products, vacuum cleaners, etc.).
- consumer electrical and electronic equipment such as audio equipment, speakers, radios, video equipment, televisions, microwave ovens, rice cookers, coffee makers, dishwashers, washing machines, dryers, fans, ventilation fans and related products, vacuum cleaners, etc.
- the UE may be, for example, an electronic application system or an electronic application device (eg, an X-ray device, a particle accelerator, a radioactive material application device, a sound wave application device, an electromagnetic application device, an electric power application device, etc.).
- an electronic application device eg, an X-ray device, a particle accelerator, a radioactive material application device, a sound wave application device, an electromagnetic application device, an electric power application device, etc.
- UE includes, for example, light bulbs, lighting, weighing machines, analytical instruments, testing machines and measuring machines (examples include smoke alarms, human alarm sensors, motion sensors, wireless tags, etc.), watches (or clocks), physics and chemistry machines, It may be an optical machine, a medical instrument and/or medical system, a weapon, a handicraft tool, or a hand tool.
- UE is, for example, a personal digital assistant or device with wireless communication capabilities (eg, an electronic device (eg, personal computer, electronic measuring instrument, etc.) to which a wireless card, wireless module, etc. is attached or configured to be inserted). ).
- a personal digital assistant or device with wireless communication capabilities eg, an electronic device (eg, personal computer, electronic measuring instrument, etc.) to which a wireless card, wireless module, etc. is attached or configured to be inserted).
- a UE may be, for example, a device or part thereof that provides the following applications, services, and solutions in the "Internet of Things (IoT)" using wired or wireless communication technology.
- IoT devices (or things) comprise appropriate electronics, software, sensors, network connections, etc. that allow devices to collect and exchange data with each other and with other communicating devices.
- IoT devices may be automated equipment following software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction.
- An IoT device may be a device that is installed for an extended period of time and/or remains inactive for an extended period of time. IoT devices may be implemented as part of stationary equipment.
- IoT devices can be embedded in non-stationary devices (eg, vehicles, etc.) or attached to animals or people to be monitored/tracked. IoT technology can be implemented on any communication device that can be connected to a communication network that sends and receives data regardless of control by human input or software instructions stored in memory. IoT devices are sometimes called Machine Type Communication (MTC) devices, Machine to Machine (M2M) communication devices, Narrow Band-IoT (NB-IoT) UE.
- MTC Machine Type Communication
- M2M Machine to Machine
- NB-IoT Narrow Band-IoT
- a UE may support one or more IoT or MTC applications.
- MTC applications Some examples of MTC applications are listed in 3GPP TS22.368 V13.2.0(2017-01-13) Annex B (the contents of which are incorporated herein by reference). This list is not exhaustive and shows MTC applications as an example. In this list, the Service Areas for MTC applications are Security, Tracking & Tracing, Payment, Health, Remote Maintenance/Control, Includes Metering and Consumer Devices.
- MTC applications for security are Surveillance systems, Backup for landline, Control of physical access (e.g. to buildings), and Vehicle / Including Car/driver security.
- MTC applications for track and trace are Fleet Management, Order Management, Telematics Insurance: Pay as you drive (PAYD), Asset Tracking, Navigation (Navigation), Traffic information, Road tolling, and Road traffic optimization/steering.
- MTC applications related to payments include Point of Sales (POS), Vending Machines, and Gaming Machines.
- POS Point of Sales
- Vending Machines Vending Machines
- Gaming Machines Gaming Machines.
- Examples of health-related MTC applications are Monitoring vital signs, Supporting the aged or handicapped, Web Access Telemedicine points, and Remote diagnostics. including.
- MTC applications for remote maintenance/control are Sensors, Lighting, Pumps, Valves, Elevator control, Vending machine control, and Vehicles Includes Vehicle diagnostics.
- MTC applications for metering include Power, Gas, Water, Heating, Grid control, and Industrial metering.
- MTC applications for consumer devices include digital photo frames, digital cameras, and electronic books (ebooks).
- MVNO Mobile Virtual Network Operator
- PBX Private Branch eXchange
- POS Point of sales
- MBMS Multimedia Broadcast and Multicast Service
- V2X Vehicle to Everything: vehicle-to-vehicle communication
- IoT Internet of Things
- Appendix 1 receiving a request from the requesting entity to create an Edge Enabler Client (EEC) Context coupled to the memory and comprising Security credentials and at least one Application Client Profile, information about the requesting entity; determining whether access to the edge data network can be permitted by verifying the security credentials; attempting to identify a second server located within the edge data network based on at least one selection criterion if access to the edge data network can be granted; If the second server is identified, sending a first response message to the requesting entity containing information indicating that the request was successful.
- EEC Edge Enabler Client
- At least one processor configured to with The at least one selection criterion includes requirements indicated by the at least one Application Client Profile; Information indicating that the at least one processor cannot identify the second server when access to the edge data network cannot be permitted or the requirements indicated by the at least one Application Client Profile are not met. configured to send a second response message containing a failure cause to the requesting entity; First server. (Appendix 2) the second response message causes the requesting entity to at least one of abort the request, suppress transmission of the request, resend the request, and notify an application; A first server according to Appendix 1.
- the first server is an Edge Enabler Server (EES); the second server is an Edge Application Server (EAS); the requesting entity is an Edge Enabler Client (EEC) located in User Equipment (UE);
- the first server according to Appendix 1 or 2.
- At least one of the first response message and the second response message includes information indicating that the requesting entity should backoff before sending the next request, A first server according to any one of the preceding clauses.
- At least one of the first response message and the second response message includes information for specifying a specific backoff time or maximum backoff time for the backoff.
- the first server according to appendix 4.
- the information indicating that the backoff should be performed includes information for specifying a specific backoff time or maximum backoff time, and at least one cause of failure, The first server according to appendix 4 or 5.
- (Appendix 7) receiving a request from a requesting entity to create an Edge Enabler Client (EEC) Context that is information about the requesting entity and that includes Security credentials and at least one Application Client Profile; determining whether access to the edge data network can be permitted by verifying the security credentials; attempting to identify a second server located within the edge data network based on at least one selection criterion if access to the edge data network can be granted; upon identifying the second server, sending a first response message to the requesting entity including information indicating that the request was successful;
- the at least one selection criterion includes requirements indicated by the at least one Application Client Profile; If access to the edge data network cannot be permitted, or if the requirements indicated by the at least one Application Client Profile are not met, a second message containing a failure cause that is information indicating that the
- a program for causing a computer to perform a method for a first server comprising: The method includes: receiving a request from a requesting entity to create an Edge Enabler Client (EEC) Context that is information about the requesting entity and that includes Security credentials and at least one Application Client Profile; determining whether access to the edge data network can be permitted by verifying the security credentials; attempting to identify a second server located within the edge data network based on at least one selection criterion if access to the edge data network can be granted; upon identifying the second server, sending a first response message to the requesting entity including information indicating that the request was successful;
- the at least one selection criterion includes requirements indicated by the at least one Application Client Profile; In the method, when access to the edge data network cannot be permitted or requirements indicated by the at least one Application Client Profile are not satisfied, the failure cause is information indicating that the second server cannot be identified.
- a second response message comprising: program. (Appendix 9) a request entity, and and sending a request to a first server to generate an Edge Enabler Client (EEC) Context coupled to said memory and comprising Security credentials and at least one Application Client Profile and being information about said requesting entity.
- EEC Edge Enabler Client
- receiving a response message to the request from the first server if the response message includes a failure cause that is information indicating that the second server cannot be specified, sending the request to a first server different from the first server; at least one processor configured to with The requesting entity, wherein said failure cause is included in said response message if access to an edge data network cannot be granted or a requirement indicated in said at least one Application Client Profile is not met.
- the first server is an Edge Enabler Server (EES); the second server is an Edge Application Server (EAS); the requesting entity is an Edge Enabler Client (EEC) located in User Equipment (UE); A requesting entity as described in Appendix 9.
- EAS Edge Enabler Server
- EAC Edge Enabler Client
- a method performed by a requesting entity comprising: Sending a request to a first server to generate an Edge Enabler Client (EEC) Context that is information about the requesting entity and that includes Security credentials and at least one Application Client Profile; receiving a response message to the request from the first server; sending the request to a first server different from the first server if the response message includes a failure cause that is information indicating that the second server cannot be identified; The method, wherein the failure cause is included in the response message if access to an edge data network cannot be granted or a requirement indicated in the at least one Application Client Profile is not met.
- EEC Edge Enabler Client
- a program for causing a computer to perform a method for a requesting entity comprising: The method includes: Sending a request to a first server to generate an Edge Enabler Client (EEC) Context that is information about the requesting entity and that includes Security credentials and at least one Application Client Profile; receiving a response message to the request from the first server; sending a request to a first server different from the first server if the response message includes a failure cause that is information indicating that the second server cannot be identified;
- EEC Edge Enabler Client
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
(a)Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client(EEC) Contextを生成するための要求を前記要求エンティティから受信すること、
(b)前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定すること、
(c)前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行すること、
(d)前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信すること、ここで、前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含む、及び
(e)前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信すること。
(a)Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client(EEC) Contextを生成するための要求を第1のサーバに送信すること、
(b)前記要求に対するレスポンスメッセージを前記第1のサーバから受信すること、及び
(c)前記レスポンスメッセージが前記第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して前記要求を送信すること、ここで、前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる。
図1は、本実施形態に係るネットワークのアーキテクチャの一例を示している。図1のアーキテクチャは、3GPP EDGEAPPアーキテクチャに相当する。図1に示された要素の各々は機能エンティティであり、3GPPにより定義された機能及びインタフェースを提供する。図1に示された各要素(機能エンティティ)は、例えば、専用ハードウェア(dedicated hardware)上のネットワークエレメントとして、専用ハードウェア上で動作する(running)ソフトウェア・インスタンスとして、又はアプリケーション・プラットフォーム上にインスタンス化(instantiated)された仮想化機能として実装されることができる。
本実施形態は、第1の実施形態で説明された第1のサーバ及び要求エンティティの動作の変形を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1を参照して説明された例と同様である。
本実施形態は、第1のサーバ及び要求エンティティの動作の他の例を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1を参照して説明された例と同様である。
本実施形態は、第1の実施形態で説明された第1のサーバ及び要求エンティティの動作の変形を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1を参照して説明された例と同様である。
メモリ、及び
前記メモリに結合され、且つ
Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信する、
よう構成された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記少なくとも1つのプロセッサは、前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信するよう構成される、
第1のサーバ。
(付記2)
前記第2のレスポンスメッセージは、前記要求エンティティに、前記要求の中止、前記要求の送信の抑止、前記要求の再送、アプリケーションへの通知の少なくとも1つを行わせる、
付記1に記載の第1のサーバ。
(付記3)
前記第1のサーバは、Edge Enabler Server(EES)であり、
前記第2のサーバは、Edge Application Server(EAS)であり、
前記要求エンティティは、User Equipment(UE)に配置されたEdge Enabler Client(EEC)である、
付記1または2に記載の第1のサーバ。
(付記4)
前記第1のレスポンスメッセージおよび前記第2のレスポンスメッセージの少なくともいずれかは、前記要求エンティティが次の要求を送信する前にバックオフを行うべきであることを示す情報を含む、付記1~3のいずれか1項に記載の第1のサーバ。
(付記5)
前記第1のレスポンスメッセージおよび前記第2のレスポンスメッセージの少なくともいずれかは、前記バックオフのための特定のバックオフ時間又は最大バックオフ時間を特定するための情報を含む、
付記4に記載の第1のサーバ。
(付記6)
前記バックオフを行うべきであることを示す情報は、特定のバックオフ時間又は最大バックオフ時間を特定するための情報、及び、失敗原因の少なくとも1つを含む、
付記4または5に記載の第1のサーバ。
(付記7)
Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信すること、を含み、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信すること、をさらに含む、
第1のサーバにより行われる方法。
(付記8)
第1のサーバのための方法をコンピュータに行わせるためのプログラムであって、
前記方法は、
Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信すること、を含み、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記方法は、前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信すること、をさらに含む、
プログラム。
(付記9)
要求エンティティであって、
メモリ、及び
前記メモリに結合され、且つ
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して前記要求を送信する、
よう構成された少なくとも1つのプロセッサと、
を備え、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、要求エンティティ。
(付記10)
前記第1のサーバは、Edge Enabler Server(EES)であり、
前記第2のサーバは、Edge Application Server(EAS)であり、
前記要求エンティティは、User Equipment(UE)に配置されたEdge Enabler Client(EEC)である、
付記9に記載の要求エンティティ。
(付記11)
要求エンティティにより行われる方法であって、
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して前記要求を送信すること、を含み、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、方法。
(付記12)
要求エンティティのための方法を、コンピュータに行わせるためのプログラムであって、
前記方法は、
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して要求を送信すること、を含み、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、プログラム。
2 Edge Enabler Client(EEC)
3 Application client(AC)
4 Edge Data Network(EDN)
5 Edge Enabler Server(EES)
51 Edge Enabler Server(EES)
6 Edge Application Server(EAS)
7 Edge Configuration Server(ECS)
903 ベースバンドプロセッサ
904 アプリケーションプロセッサ
906 メモリ
907 モジュール
1002 プロセッサ
1003 メモリ
1004 モジュール
Claims (12)
- メモリ、及び
前記メモリに結合され、且つ
Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信する、
よう構成された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記少なくとも1つのプロセッサは、前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信するよう構成される、
第1のサーバ。 - 前記第2のレスポンスメッセージは、前記要求エンティティに、前記要求の中止、前記要求の送信の抑止、前記要求の再送、アプリケーションへの通知の少なくとも1つを行わせる、
請求項1に記載の第1のサーバ。 - 前記第1のサーバは、Edge Enabler Server(EES)であり、
前記第2のサーバは、Edge Application Server(EAS)であり、
前記要求エンティティは、User Equipment(UE)に配置されたEdge Enabler Client(EEC)である、
請求項1または2に記載の第1のサーバ。 - 前記第1のレスポンスメッセージおよび前記第2のレスポンスメッセージの少なくともいずれかは、前記要求エンティティが次の要求を送信する前にバックオフを行うべきであることを示す情報を含む、請求項1~3のいずれか1項に記載の第1のサーバ。
- 前記第1のレスポンスメッセージおよび前記第2のレスポンスメッセージの少なくともいずれかは、前記バックオフのための特定のバックオフ時間又は最大バックオフ時間を特定するための情報を含む、
請求項4に記載の第1のサーバ。 - 前記バックオフを行うべきであることを示す情報は、特定のバックオフ時間又は最大バックオフ時間を特定するための情報、及び、失敗原因の少なくとも1つを含む、
請求項4または5に記載の第1のサーバ。 - Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信すること、を含み、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信すること、をさらに含む、
第1のサーバにより行われる方法。 - 第1のサーバのための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、
Security credentials及び少なくとも1つのApplication Client Profileを含み、要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を前記要求エンティティから受信し、
前記Security credentialsを検証することで、エッジデータネットワークへのアクセスを許可できるか否か判定し、
前記エッジデータネットワークへのアクセスを許可できる場合に、少なくとも1つの選択基準に基づいて前記エッジデータネットワーク内に配置される第2のサーバを特定することを試行し、
前記第2のサーバを特定した場合、前記要求が成功したことを示す情報を含む第1のレスポンスメッセージを前記要求エンティティに送信すること、を含み、
前記少なくとも1つの選択基準は、前記少なくとも1つのApplication Client Profileで示される要件を含み、
前記方法は、前記エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合、当該第2のサーバを特定できないことを示す情報である失敗原因を含む第2のレスポンスメッセージを前記要求エンティティに送信すること、をさらに含む、
非一時的なコンピュータ可読媒体。 - 要求エンティティであって、
メモリ、及び
前記メモリに結合され、且つ
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して前記要求を送信する、
よう構成された少なくとも1つのプロセッサと、
を備え、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、要求エンティティ。 - 前記第1のサーバは、Edge Enabler Server(EES)であり、
前記第2のサーバは、Edge Application Server(EAS)であり、
前記要求エンティティは、User Equipment(UE)に配置されたEdge Enabler Client(EEC)である、
請求項9に記載の要求エンティティ。 - 要求エンティティにより行われる方法であって、
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して前記要求を送信すること、を含み、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、方法。 - 要求エンティティのための方法を、コンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、
Security credentials及び少なくとも1つのApplication Client Profileを含み、前記要求エンティティに関する情報であるEdge Enabler Client (EEC) Contextを生成するための要求を第1のサーバに送信し、
前記要求に対するレスポンスメッセージを前記第1のサーバから受信し、
前記レスポンスメッセージが、第2のサーバを特定できないことを示す情報である失敗原因を含むなら、前記第1のサーバとは異なる第1のサーバに対して要求を送信すること、を含み、
前記失敗原因は、エッジデータネットワークへのアクセスが許可できない場合、または前記少なくとも1つのApplication Client Profileで示される要件を満たさない場合に前記レスポンスメッセージに含まれる、非一時的なコンピュータ可読媒体。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023520789A JPWO2022239349A5 (ja) | 2022-02-16 | Edge Enabler Server(EES)、Edge Enabler Client(EEC)、及びこれらの方法 | |
EP22807056.1A EP4340410A1 (en) | 2021-05-10 | 2022-02-16 | Server, request entity, and methods therefor |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021079697 | 2021-05-10 | ||
JP2021-079697 | 2021-05-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022239349A1 true WO2022239349A1 (ja) | 2022-11-17 |
Family
ID=84029099
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/006279 WO2022239349A1 (ja) | 2021-05-10 | 2022-02-16 | サーバ、要求エンティティ、及びこれらの方法 |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP4340410A1 (ja) |
WO (1) | WO2022239349A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021079697A (ja) | 2019-11-13 | 2021-05-27 | 積水化学工業株式会社 | 多層離型フィルム |
-
2022
- 2022-02-16 EP EP22807056.1A patent/EP4340410A1/en active Pending
- 2022-02-16 WO PCT/JP2022/006279 patent/WO2022239349A1/ja active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021079697A (ja) | 2019-11-13 | 2021-05-27 | 積水化学工業株式会社 | 多層離型フィルム |
Non-Patent Citations (3)
Title |
---|
"3 Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.558, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. V2.1.0, 3 May 2021 (2021-05-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 152, XP052000942 * |
3GPP TS 22.368 |
3GPP TS 23.558 |
Also Published As
Publication number | Publication date |
---|---|
EP4340410A1 (en) | 2024-03-20 |
JPWO2022239349A1 (ja) | 2022-11-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7306540B2 (ja) | 無線端末、マスターノード、及びこれらにより行われる方法 | |
JP2021193841A (ja) | gNB−CU、gNB−DU、及びこれらの方法 | |
US20210099870A1 (en) | Method and apparatus for performing authorization for unmanned aerial system service in wireless communication system | |
US20220210636A1 (en) | Method and system of enabling akma service in roaming scenario | |
JP7099536B2 (ja) | コアネットワーク装置、通信端末、コアネットワーク装置の方法、プログラム、及び通信端末の方法 | |
JP2023076602A (ja) | ネットワークノード、User Equipment、及びネットワークノードにより行われる方法 | |
WO2021132096A1 (ja) | Amfノード及びその方法 | |
US20200196227A1 (en) | Network slice instance creation | |
US20230108959A1 (en) | Communication method and apparatus in wireless communication system supporting edge computing | |
JP2021052346A (ja) | 無線端末、コアネットワークノード、及びこれらの方法 | |
WO2022239349A1 (ja) | サーバ、要求エンティティ、及びこれらの方法 | |
WO2022244533A1 (ja) | Smfノード、afノード、ue、及びこれらの方法 | |
WO2022176425A1 (ja) | サーバ、要求エンティティ、及びこれらの方法 | |
JP7052928B2 (ja) | コアネットワークノード、アクセスモビリティ管理装置、及び通信方法 | |
WO2022174368A1 (en) | Technologies for user equipment relay discovery | |
WO2022176426A1 (ja) | サーバ、要求エンティティ、及びこれらの方法 | |
WO2023054198A1 (ja) | 第1のノード、第2のノード、第1のノードによる方法、第2のノードよる方法、ue、及びueによる方法 | |
WO2023054194A1 (ja) | 第1のノード、第2のノード、第1のノードによる方法、及び第2のノードによる方法 | |
JP7428265B2 (ja) | 通信端末及びその方法 | |
US20230144174A1 (en) | Method and apparatus for supporting service continuity policy control | |
WO2023054568A1 (ja) | Amfノード、uav、smfノード、方法、及び非一時的なコンピュータ可読媒体 | |
EP4210302A1 (en) | Apparatus, methods, and computer programs | |
JP7302677B2 (ja) | User Equipment、無線アクセスネットワークノード、及びこれらの方法 | |
WO2023002991A1 (en) | Access and mobility management function (amf) device, user equipment (ue), method of amf device and method of ue | |
EP4349089A1 (en) | Apparatus, methods, and computer programs |
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: 22807056 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18288672 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023520789 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022807056 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022807056 Country of ref document: EP Effective date: 20231211 |