WO2022244533A1 - Smfノード、afノード、ue、及びこれらの方法 - Google Patents
Smfノード、afノード、ue、及びこれらの方法 Download PDFInfo
- Publication number
- WO2022244533A1 WO2022244533A1 PCT/JP2022/016629 JP2022016629W WO2022244533A1 WO 2022244533 A1 WO2022244533 A1 WO 2022244533A1 JP 2022016629 W JP2022016629 W JP 2022016629W WO 2022244533 A1 WO2022244533 A1 WO 2022244533A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ladn
- procedure
- edn
- pdu session
- node
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 250
- 230000004044 response Effects 0.000 claims abstract description 61
- 230000006870 function Effects 0.000 claims description 126
- 238000007726 management method Methods 0.000 claims description 47
- 230000009849 deactivation Effects 0.000 claims description 20
- 238000012546 transfer Methods 0.000 claims description 16
- 230000000977 initiatory effect Effects 0.000 claims description 12
- 238000013523 data management Methods 0.000 claims description 6
- 238000001514 detection method Methods 0.000 abstract description 6
- 230000002265 prevention Effects 0.000 abstract 1
- 238000012545 processing Methods 0.000 description 23
- 238000004891 communication Methods 0.000 description 16
- 230000011664 signaling Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000011522 transarterial infusion chemotherapy Methods 0.000 description 6
- QCOXCILKVHKOGO-UHFFFAOYSA-N n-(2-nitramidoethyl)nitramide Chemical compound [O-][N+](=O)NCCN[N+]([O-])=O QCOXCILKVHKOGO-UHFFFAOYSA-N 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000003213 activating effect Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 101150119040 Nsmf gene Proteins 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000006399 behavior 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
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
Definitions
- the present disclosure relates to wireless communication networks, and in particular to PDU Session management.
- the 5G system connects wireless terminals (user equipment (UE)) to data networks (Data Network (DN)).
- connectivity services between UE and DN are supported by one or more Protocol Data Unit (PDU) Sessions (see, for example, Non-Patent Documents 1 and 2).
- a PDU Session is an association, session or connection between a UE and a DN.
- PDU Session is used to provide PDU connectivity service (ie exchange of PDUs between UE and DN).
- a PDU Session is established between the UE and the User Plane Function (UPF) (i.e., PDU Session anchor) to which the DN is attached.
- UPF User Plane Function
- a PDU Session consists of tunnels (N9 tunnels) within the 5G core network (5GC), tunnels (N3 tunnels) between the 5GC and the access network (AN), and one or more radio bearers.
- Non-Patent Document 2 defines a PDU Session establishment procedure and a PDU Session release procedure. More specifically, the PDU Session establishment procedure is described in Chapter 4.3.2.2 of Non-Patent Document 2, for example. The PDU Session release procedure is described, for example, in Chapter 4.3.4.2 of Non-Patent Document 2. Furthermore, Non-Patent Document 2 defines a procedure for deactivating user-plane (UP) connections (or resources) for PDU Session. This procedure is described, for example, in Chapter 4.3.7 of Non-Patent Document 2.
- UP user-plane
- LADN Local Area Data Network
- a LADN Service Area is a set of one or more Tracking Areas (TAs) belonging to the UE's current registration area. If the UE moves out of the LADN service area, the Session Management Function (SMF) shall either release the PDU Session for that LADN or deactivate the UP connection for that PDU Session.
- UP connections include the data radio barer of the Radio Access Network (RAN) and the N3 tunnel between the RAN and UPF.
- deactivating the UP connection means releasing the data radio barer of the (Radio) Access Network ((R)AN) that composes the UP connection and the N3 tunnel between the (R)AN and UPF. is.
- activating the UP connection means establishing (setting) the (R)AN data radio barer that constitutes the UP connection and the N3 tunnel between the (R)AN and UPF.
- 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 3).
- This architecture of 3GPP is called EDGEAPP architecture.
- the EDGEAPP architecture is an enabling layer for facilitating communication between application clients (ACs) running on the UE and applications located at the edge.
- ACs application clients
- EASs Edge Application Servers
- ECS Edge Configuration Servers
- EES Edge Enabler Servers
- EEC Edge Enabler Servers
- EEC Edge Enabler Servers
- edge computing services can be provided via Edge-dedicated Data Networks deployed as LADNs (see Section A.2.4 of Non-Patent Document 3).
- the Public Land Mobile Network PLMN
- EAS Edge Data Network
- a LADN service area is a service area where edge computing is supported.
- Each EAS within a LADN can support a service area equal to or smaller than the LADN.
- the EDGEAPP architecture supports various Application Context Relocation (ACR) procedures for service continuity.
- An application context is a set of data about an AC that exists in EAS.
- Application context relocation involves transferring application context from Source EAS (or old EDN or old LADN) to Target EAS (or new EDN or new LADN).
- Application context relocation is triggered by UE mobility events or non-UE mobility events.
- UE mobility events include, for example, intra-EDN mobility, inter-EDN mobility, and Local Area Data Network (LADN) related mobility.
- Non-UE mobility events include, for example, EAS or EDN overload situations, and EAS maintenance (eg, EAS graceful shutdown).
- 3GPP TS 23.501 V17.0.0 (2021-03) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 17)”, March 2021 3GPP TS 23.502 V17.0.0 (2021-03) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17)”, March 2021 3GPP TS 23.558 V2.0.0 (2021-03) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 17)", March 2021 3GPP TS 23.503 V17.0.0 (2021-03) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 17)”, March 2021
- ACR Application Context Relocation
- LADN EDN
- LADN EDN
- ACR Application Context Relocation
- SMF releases the PDU Session corresponding to the EDN (LADN) or UP connection for the PDU Session. (or resources) must be deactivated.
- LADN EDN
- UP connection the PDU Session for the old EDN (LADN)
- S-EES Source EES
- the UE EEC can send an ACR Request message (Step 5) to the S-EES. maybe not.
- One of the objectives that the embodiments disclosed herein seek to achieve is to provide an apparatus, method, and program that contribute to preventing ACR procedure failures when a UE moves between EDNs (or LADNs). to provide. 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.
- an SMF node includes a memory and at least one processor coupled to said memory.
- the at least one processor is configured to detect an event related to an Application Context Relocation (ACR) procedure after receiving a first event notification from the AMF node indicating that the UE is out of EDN service area or out of LADN service area. be. Further, the at least one processor releases a PDU Session for the LADN associated with the LADN service area in response to detecting an event related to the ACR procedure; It is configured to initiate a procedure to release a PDU Session for EDN or to deactivate a UP connection for said PDU Session.
- ACR Application Context Relocation
- the method performed by the SMF node includes: (a) receiving an event regarding the ACR procedure after receiving a first event notification from the AMF node indicating that the UE is out of EDN service area or out of LADN service area; and (b) in response to detecting an event relating to said ACR procedure, releasing a PDU Session for a LADN associated with said LADN Service Area, an EDN associated with said EDN Service Area. or initiating a procedure to release a PDU Session for the PDU Session or deactivate a UP connection for said PDU Session.
- an Application Function (AF) node includes a memory and at least one processor coupled to said memory.
- the at least one processor is configured to receive event notifications directly from SMF nodes or via Network Exposure Function (NEF) nodes. Further, the at least one processor responds to the event notification directly to the SMF node or via the NEF node after an ACR procedure including application context transfer from S-EAS to T-EAS is completed. configured to send.
- the response is a message that causes the SMF node to initiate a procedure to release a PDU Session for LADN, a procedure to release a PDU Session for EDN, or a procedure to deactivate a UP connection for said PDU Session. is.
- a method performed by an AF node includes (a) receiving an event notification directly from an SMF node or via a NEF node, and (b) an application context from S-EAS to T-EAS. sending a response to said event notification to said SMF node directly or via said NEF node after an ACR procedure including forwarding of is completed.
- the response is a message that causes the SMF node to initiate a procedure to release a PDU Session for LADN, a procedure to release a PDU Session for EDN, or a procedure to deactivate a UP connection for said PDU Session. is.
- a UE in a fifth aspect, includes a memory and at least one processor coupled to the memory.
- the at least one processor selects a mode for continuity of session and service if the first Data Network Name (DNN) corresponds to a LADN of a given type.
- the at least one processor includes a Non-Access Stratum (NAS ) is configured to send messages to AMF nodes.
- the mode for continuity of the one session and service is, before releasing the first PDU Session, when the UE moves out of the LADN service area corresponding to the first DNN.
- NAS Non-Access Stratum
- the method performed by the UE includes: (a) mode for continuity of session and service if the first DNN supports a given type of LADN; and (b) sending a NAS message containing a PDU Session Establishment Request indicating the selected mode to request establishment of a first PDU Session for the first DNN. sending to a node.
- the mode for continuity of the one session and service is, before releasing the first PDU Session, when the UE moves out of the LADN service area corresponding to the first DNN.
- a UE in a seventh aspect, includes a memory and at least one processor coupled to the memory.
- the at least one processor is configured to provide EEC functionality.
- the EEC function includes deciding to perform any of a plurality of ACR procedures given that the UE has moved out of the LADN coverage area associated with the first EDN.
- a method performed by a UE includes providing EEC functionality.
- the EEC function includes deciding to perform any of a plurality of ACR procedures given that the UE has moved out of the LADN coverage area associated with the first EDN.
- the program comprises instructions (software code) for causing a computer to perform the method according to the second, fourth, sixth, or eighth aspect when read into a computer. include.
- FIG. 1 is a diagram illustrating a configuration example of a wireless communication network according to an embodiment
- FIG. FIG. 4 is a diagram illustrating an example of an EDNs deployment model according to the embodiment
- FIG. 2 illustrates an example 3GPP EDGEAPP architecture according to an embodiment
- 4 is a flow chart showing an example of the operation of SMF according to the embodiment
- 4 is a flow chart showing an example of the operation of SMF according to the embodiment
- 4 is a flowchart showing an example of AF operation according to the embodiment
- 4 is a sequence diagram showing an example of operations of AMF, SMF, NEF, and AF according to the embodiment
- FIG. 4 is a sequence diagram showing an example of SMF, NEF, and AF operations according to the embodiment
- FIG. 4 is a sequence diagram showing an example of SMF, NEF, and AF operations according to the embodiment
- FIG. 4 is a sequence diagram showing an example of SMF, NEF, and AF operations according to the embodiment
- FIG. 4 is a
- FIG. 4 is a flow chart showing an example of the operation of SMF according to the embodiment; 4 is a sequence diagram showing an example of operations of AMF, SMF, NEF, and AF according to the embodiment;
- FIG. 4 is a flow chart showing an example of the operation of SMF according to the embodiment; 4 is a sequence diagram showing an example of operations of AMF and SM according to the embodiment;
- FIG. 4 is a flow chart showing an example of the operation of a UE according to the embodiment; 4 is a flowchart illustrating an example of EEC operation of a UE according to an embodiment;
- 2 is a block diagram showing a configuration example of a UE according to an embodiment;
- FIG. 3 is a block diagram showing a configuration example of AMF, SMF, NEF, and AF according to the embodiment;
- 3GPP system e.g., 5G system (5GS)
- 5GS 5G system
- these embodiments may be applied to other wireless communication systems.
- FIG. 1 shows a configuration example of a wireless communication network (ie, 5GS) according to this embodiment.
- Each of the elements shown in FIG. 1 is a network function and provides an interface defined by 3GPP.
- Each element (network function) 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.
- the wireless communication network shown in Fig. 1 may be provided by a Mobile Network Operator (MNO) or may be a Non-Public Network (NPN) provided by a non-MNO. If the wireless communication network shown in Fig. 1 is an NPN, it can be an independent network denoted as Stand-alone Non-Public Network (SNPN) or interlocked with an MNO network denoted as Public network integrated NPN. It may be an NPN with
- a wireless terminal (i.e., UE) 1 uses 3GPP (e.g., 5G) connectivity service and communicates with a data network (DN). More specifically, the UE 1 is connected to a (radio) access network (e.g., 5G Access Network (5GAN)) 2, and one or more in the 3GPP core network 3 (e.g., 5G core network (5GC)) Communicate with the DN via User Plane Functions (UPFs) 33.
- 5GAN 5G Access Network
- 5GC 5G core network
- UPFs User Plane Functions
- the 3GPP core network 3 may be, but is not limited to, 5GC.
- the 3GPP core network 3 may include non-5G (eg future 6G, or non-3GPP) networks.
- FIG. 1 shows three DNs, namely LADN41, LADN42, and DN43.
- UE1 may communicate with one or more of LADN41, LADN42, and DN43 simultaneously.
- UE1 is allowed to access LADN41 via PDU Session for LADN41 only when UE1 is within the LADN service area of LADN41.
- UE 1 is allowed to access LADN 42 via a PDU Session for LADN 42 only when UE 1 is within the LADN service area of LADN 42 .
- a LADN Service Area is a set of one or more Tracking Areas (TAs) belonging to the UE's current registration area.
- TAs Tracking Areas
- PDU Session is an association, session or connection between UE1 and DN.
- PDU Session is used to provide PDU connectivity service (ie exchange of PDUs between UE1 and DN).
- UE1 establishes one or more PDU Sessions between UE1 and UPF 33 (i.e., PDU Session Anchor (PSA)) to which the DN is connected.
- PPA PDU Session Anchor
- one PDU Session consists of a tunnel within 3GPP core network 3 (i.e., N9 tunnel), a tunnel between 3GPP core network 3 and AN2 (i.e., N3 tunnel), and a tunnel between UE1 and AN2. configured by one or more radio bearers in between.
- UE1 concurrently connects to (sub)networks (or entities) represented by multiple DNs or multiple Data Network Access Identifiers (DNAIs) (e.g., LADN41 and DN43).
- Multiple PDU Sessions may be established with each of multiple (PSA) UPFs 33 for access.
- the Access and Mobility Management Function (AMF) 31 is one of the network function nodes within the control plane of the 3GPP core network 3.
- AMF 31 provides termination of the RAN Control Plane (CP) interface (i.e., N2 interface).
- AMF31 terminates a single signaling connection (i.e., N1 NAS signaling connection) with UE1 and provides registration management, connection management and mobility management.
- AMF 31 provides NF services to NF consumers (e.g. other AMFs and SMF 32) over a service-based interface (i.e., Namf interface).
- NF services provided by the AMF 31 include a communication service (Namf_Communication).
- the communication service allows NF consumers (e.g., SMF32) to communicate with UE1 or AN2 via AMF31.
- a Session Management Function (SMF) 32 is one of the network function nodes in the control plane of the 3GPP core network 3. SMF 32 manages PDU Sessions. SMF 32 transmits and receives SM signaling messages (NAS-SM messages, N1 SM messages) to and from the Non-Access-Stratum (NAS) Session Management (SM) layer of UE 1 via the communication service provided by AMF 31. . SMF 32 provides Network Function (NF) services to NF consumers (e.g. AMF 31, other SMFs, and NEF 36) over a service-based interface (i.e., Nsmf interface). NF services provided by SMF 32 include a PDU Session management service (Nsmf_PDUSession).
- Nsmf_PDUSession PDU Session management service
- the NF Service allows NF Consumers (e.g., AMF 31) to handle PDU Sessions.
- the NF services provided by SMF 32 further include an event notification service (Nsmf_EventExposure).
- the service operations exposed by the NF service enable NF consumers (e.g., NEF36, AF5) to get notified of events occurring in PDU Sessions.
- a User Plane Function (UPF) 33 is one of the network function nodes in the user plane of the 3GPP core network 3.
- UPF 33 processes and forwards user data.
- the functionality of UPF 33 is controlled by SMF 32 .
- the UPF 33 may include multiple UPFs (e.g., two UPFs 33 shown in FIG. 1) interconnected via the N9 interface.
- the UP path for one PDU Session of UE1 may contain one or more PDU Session Anchor (PSA) UPFs and may contain one or more Intermediate UPFs (I-UPFs). It can contain one or more Uplink Classifier (UL CL) UPFs (or Branching Point (BP) UPFs).
- the UP path for a PDU Session session is for routing user plane data (e.g.
- IP Internet Protocol
- a DN e.g., LADN41, LADN42, or DN43
- IP Internet Protocol
- the UP path contains at least one UPF 33 and contains the N6 interface with the DN.
- a UP path may include one or more N9 tunnels.
- An N9 tunnel is a tunnel between two UPFs 33 .
- a Policy Control Function (PCF) 34 is one of the network function nodes in the control play of the 3GPP core network 3.
- PCF 34 supports interactions with access and mobility policy enforcement within AMF 31 via a service-based interface (i.e., Npcf interface).
- PCF 34 provides access and mobility management related policies to AMF 31 .
- PCF 34 provides session-related policies to SMF 32 .
- Session-related policies include PDU Session-related policy information and Policy and Charging Control (PCC) rule information.
- PCC rule information includes control information on AF influence on traffic routing (i.e., AF influenced Traffic Steering Enforcement Control information).
- a Unified Data Management (UDM) 35 is one of the network function nodes within the control play of the 3GPP core network 3.
- the UDM 35 provides access to a database (i.e., User Data Repository (UDR)) where subscriber data (subscription information) is stored.
- UDM 35 provides NF services to NF consumers (e.g. AMF 31, SMF 32) over a service-based interface (i.e., Nudm interface).
- NF services provided by UDM 35 include subscriber data management services.
- the NF service enables NF consumers (e.g., AMF 31, PCF 34) to retrieve subscriber data and provides updated subscriber data to NF consumers.
- UDM 35 may be expressed as UDR from the viewpoint of subscriber data management. Similarly, UDR may be expressed as UDM35.
- a Network Exposure Function (NEF) 36 is one of the network function nodes within the control play of the 3GPP core network 3.
- NEF 36 has a role similar to Service Capability Exposure Function (SCEF) of Evolved Packet System (EPS).
- SCEF Service Capability Exposure Function
- EPS Evolved Packet System
- the NEF 36 supports exposure of services and capabilities from the 3GPP system to applications and network functions inside and outside the operator network.
- the NEF 36 provides NF services to NF consumers (e.g. AF5) over a service-based interface (i.e., Nnef interface).
- NF services provided by NEF 36 include an event notification service (Nnef_EventExposure).
- the service operations exposed by the NF service enable NF consumers (e.g., AF5) to get notified of events occurring within the 3GPP system.
- the NF services provided by NEF 36 include a service (Nnef_TrafficInfluence) for Application Function influence on traffic routing.
- the service operations exposed by the NF service allow NF consumers (e.g., AF5) to make requests that affect the traffic routing of a particular UE's PDU Session(s).
- Application Function (AF) 5 interacts with 3GPP core network 3.
- AF5 interacts with 3GPP core network 3 to support Application Function influence on traffic routing.
- AF5 may directly interact with network functions within the 3GPP core network 3.
- AF5 interacts with network functions in 3GPP core network 3 via NEF 36 .
- AF5 may include one or more computers.
- AF 5 communicates with UE 1 at the application layer with one or more servers (e.g., content delivery server, online game server), and cooperates with these one or more servers and 3GPP core network 3 (e.g. , NEF 36, and SMF 32) and interacting controllers (ie, AF in the 3GPP definition).
- servers e.g., content delivery server, online game server
- 3GPP core network 3 e.g. , NEF 36, and SMF 32
- AF 5 may include multiple distributed servers.
- AF 5 may include multiple edge computing servers located (or connected) at LADN 41 and LADN 42, in addition to a central server located (or connected) at DN 43.
- AF5 may communicate with applications running on the processor of UE1 via at least one of LADN41, LADN42 and DN43.
- the configuration example in Figure 1 shows only representative NFs for the sake of convenience of explanation.
- the wireless communication network according to this embodiment may include other NFs not shown in FIG. 1, such as Network Slice Selection Function (NSSF) and Network Data Analytics Function (NWDAF).
- NSSF Network Slice Selection Function
- NWDAAF Network Data Analytics Function
- FIG 2 shows an example of a deployment model for Edge Data Networks (EDNs).
- Public Land Mobile Network (PLMN) 8 includes AN 2 and 3GPP core network 3 .
- EDN A (201) and EDN B (202) are Edge-dedicated Data Networks deployed as LADNs.
- LADN 41 includes EDN A (201)
- LADN 42 includes EDN B (202).
- the service area of EDN NA (201) is the same as the LADN service area of LADN41.
- the service area of EDN B (202) is the same as the LADN service area of LADN42.
- the EES service area in EDN A (201) is equal to or a subset of the EDN service area (i.e., LADN service area of LADN 41).
- each EAS within EDNA (201) is equal to or a subset of the corresponding EES coverage area.
- the EES coverage area in EDN B (202) is equal to or a subset of the EDN coverage area (i.e., the LADN coverage area of LADN 42).
- Each EAS coverage area within EDN B (202) is equal to or a subset of the corresponding EES coverage area.
- DNAIs DN Access Identifiers
- a DNAI is an identifier for user plane access to one or more DNs where an application is deployed.
- FIG. 3 shows an example of the 3GPP EDGEAPP architecture according to this embodiment.
- Each of the elements shown in FIG. 3 is a functional entity, providing functionality and interfaces defined by 3GPP.
- Each element (functional entity) shown in FIG. 3 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.
- the UE 1 includes an Edge Enabler Client (EEC) 11 and one or more Application Clients (ACs) 12.
- EEC 11 and one or more ACs 12 are located in and operate on UE1.
- UE1 communicates with 3GPP core network 3 (e.g., (5GC)) via AN2.
- 3GPP core network 3 e.g., (5GC)
- UE 1 provides EEC 11 and AC(s) 12 connectivity with the data network via AN 2 and 3GPP core network 3 .
- the EEC 11 provides the supporting functions required by the AC(s) 12. Specifically, the EEC 11 provides provisioning of configuration information to enable exchange of application data traffic with an Edge Application Server (EAS). Additionally, EEC 11 provides functionality for discovery of one or more EASs available within EDN 7 . The EEC 11 uses the EAS endpoint information obtained from EAS discovery for routing outgoing application data traffic to the EAS. In addition, the EEC 11 provides functions for EES 71 and EAS(s) 72 registration (i.e., registration, update, and de-registration).
- EES 71 and EAS(s) 72 registration i.e., registration, update, and de-registration
- Each AC 12 is an application that runs on UE 1.
- Each AC 12 connects to one or more EASs and exchanges application data traffic with these EASs in order to utilize edge computing services.
- EDN 7 includes one or more EESs 71 and one or more EASs 72.
- EDN 7 may be LADN.
- EDN 7 in FIG. 3 may be an edge-only data network deployed as LADN 41 or 42 shown in FIGS.
- EESs 71 and EASs 72 may be included in AF 5 shown in FIG.
- Each EES 71 provides supporting functions required by EAS(s) 72 and EEC 11. Specifically, each EES 71 provides provisioning of configuration information to EEC 11 to enable exchange of application data traffic with EAS(s) 72 . Each EES 71 provides the functionality of EEC 11 and EAS(s) 72 registration (i.e., registration, update, and de-registration). Each EES 71 provides the functionality of application context transfer between EASs. This functionality is needed for application context relocation (or edge application mobility) for service continuity.
- An application context is a set of data about an AC that exists in EAS. Application context relocation involves transferring the application context for a user (ie AC) from Source EAS (or old EDN or old LADN) to Target EAS (or new EDN or new LADN).
- UE mobility events include, for example, intra-EDN mobility, inter-EDN mobility, and Local Area Data Network (LADN) related mobility.
- LADN Local Area Data Network
- Non-UE mobility events include, for example, EAS or EDN overload situations, and EAS maintenance (eg, EAS graceful shutdown).
- each EES 71 supports the functions of Application Programming Interface (API) invoker and API exposing function.
- Each EES 71 provides ACR management event notifications functionality to EAS(s) 72 .
- the ACR management event notifications function is a function to notify EASs of UE mobility events or non-UE mobility events that trigger Application Context Relocation (ACR) procedures for one or more UEs.
- Event types include user plane path change detection (i.e., "User plane path change”), user plane path change detection and T-EAS identification (i.e., "ACR monitoring”), user plane path change and T-EAS identification and traffic modification suitable for that T-EAS (i.e., "ACR facilitation"), whether the UE has moved into or out of a particular location or area (i.e., "Presence-In- Area of Interest") (AOI)-Report”).
- EAS(s) 72 pre-subscribe to these events provided by EES 71 in order to receive the notifications they seek.
- the "specific location or area” may be a Tracking Area Identity (TAI) list or Cell IDs, or a TAI list associated with a specific LADN.
- TAI Tracking Area Identity
- Each EES 71 communicates with the 3GPP core network 3 directly (e.g., via the PCF 34) or indirectly (e.g., (via NEF36 or Service Capability Exposure Function (SCEF)).
- SCEF Service Capability Exposure Function
- Each EES 71 may support external exposure of 3GPP network functional services and capabilities to EAS(s) 72 .
- Each EES 71 may support Application Function influence on traffic routing and interact with the 3GPP core network 3 .
- Each EAS 72 is located in the EDN 7 and performs 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's server functionality may be available as an EAS and additionally as an application server in the cloud.
- Cloud here means a central cloud (e.g., DN 43 in FIGS. 1 and 2) located farther from UE1 than EDN7 (e.g., LADN 41 or 42 in FIGS. 1 and 2).
- An application server in the cloud therefore means a server located in a centralized location (e.g., centralized data center).
- Each EAS 72 may consume or utilize 3GPP core network capabilities.
- Each EAS 72 may directly invoke the 3GPP core network function API. Alternatively, each EAS 72 may consume or utilize 3GPP core network capabilities via EES 71 or via NEF 36 or SCEF. Each EAS 72 may support Application Function influence on traffic routing and interact with the 3GPP core network 3 .
- the Edge Configuration Server (ECS) 6 provides the supporting functions required by the EEC 11 to connect to the EES(s) 71. Specifically, ECS 6 provides provisioning of edge configuration information to EEC 11 .
- the edge setting information includes information to the EEC 11 for connecting to the EES(s) 71 (e.g., service area information applicable to LADN), and information for establishing a connection with the EES(s) 71. Contains information (e.g., Uniform Resource Identifier (URI)).
- ECS 6 provides the functionality of EES(s) 71 registration (i.e., registration, update, and de-registration). In addition, ECS6 supports API invoker and API exposing function functions.
- the ECS 6 interacts with the 3GPP core network 3 directly (e.g., via PCF 34) or indirectly (e.g., NEF 36) to access the services and capabilities of network functions within the 3GPP core network 3. or via SCEF).
- the ECS 6 may be located within the MNO domain that provides the 3GPP core network 3, or may be located in a third party domain of a service provider (eg, Edge Computing Service Provider (ECSP)).
- ECS 6 may be located in the central cloud (e.g., DN 43 in Figures 1 and 2).
- ECS 6 may be included in AF 5 shown in FIG.
- ECS 6 may be connected to multiple EDNs.
- SMF 32 does not immediately release the PDU Session for the EDN or LADN, or deactivate the UP connection for the PDU Session. after a while. Specifically, the SMF 32 releases the PDU Session for the EDN or LADN or deactivates the UP connection for the PDU Session in response to detecting an event related to the ACR procedure. SMF 32 may detect an event related to the ACR procedure after receiving a first event notification from AMF 31 indicating that UE 1 is out of EDN service area or out of LADN service area.
- the event related to the ACR procedure may be an event indicating that AF5 has successfully completed the ACR procedure.
- An event related to the ACR procedure may be an event for AF5 to be able to successfully complete the ACR procedure.
- the event related to the ACR procedure may be the receipt or detection of receipt of a response from the AF5 indicating successful completion of the ACR procedure.
- the SMF 32 may send an event notification (also referred to as a second event notification) to AF5 and wait for a response from AF5.
- the second event notification may be a notification indicating that UE1 is out of EDN service area or out of LADN service area, prior notification of release of PDU Session for EDN, PDU for LADN Prior notification of Session release or prior notification of UP connection deactivation may be used.
- the response from AF5 indicating successful completion of the ACR procedure may be a response to notification of the second event. Successful completion of the ACR procedure may include transfer of application context from the Source Edge Application Server (S-EAS) to the Target EAS (T-EAS).
- S-EAS Source Edge Application Server
- T-EAS Target EAS
- an event related to the ACR procedure indicates that the SMF 32 initiates a procedure to release the PDU Session for the EDN or LADN or deactivate the UP connection for the PDU Session. It may be receiving a message from the PCF 34 to do so. In this case, PCF 34 may decide to send the message based on information provided to PCF 34 from AF 5 (e.g., S-EES) via NEF 36 and UDM 35 .
- AF 5 e.g., S-EES
- the event related to the ACR procedure may be the elapse (or expiration) of a predetermined grace period for waiting for AF5 to complete the ACR procedure.
- the SMF 32 has a grace period before starting release of the PDU Session for the EDN or LADN or deactivation of the UP connection. I will wait for it to pass.
- Deactivating the UP connection means releasing the data radio barer of (Radio) Access Network ((R)AN) 2 that composes the UP connection and the N3 tunnel between (R)AN2 and UPF 33. be.
- activating the UP connection means establishing the data radio barer of (Radio) Access Network ((R)AN) 2 that configures the UP connection and the N3 tunnel between (R)AN2 and UPF 33 ( setting).
- the SMF 32 may perform this operation only for specific EDNs, specific LADNs (LADN DNN), specific PDU Sessions, or specific UEs. If UE1 moves out of the LADN service area and the LADN belongs to specific LADNs, the SMF 32 will allow the grace period to elapse before starting release of the PDU Session or deactivation of the UP connection for the LADN. You can wait to do it. Similarly, if UE1 moves out of the EDN service area and the EDN belongs to specific EDNs, the SMF 32 may wait a grace period before initiating release of the PDU Session or deactivation of the UP connection for the EDN. You can wait for .
- Specific LADNs may be defined by the type of LADN. Certain LADNs may be distinguished from other LADNs by their LADN DNN. Specific EDNs may be defined by EDN types. A particular EDN may be distinguished from other EDNs by (EDN) DNN, or by (EDN) DNN and DNAI, or by network slice information, or by (EDN) DNN and network slice information.
- the network slice information may be Single Network Slice Selection Assistance Information (S-NSSAI).
- S-NSSAI Single Network Slice Selection Assistance Information
- a PDU Session for a particular EDN may be associated with a particular network slice (or a particular S-NSSAI).
- a specific EDN can be identified by DNN and network slice information (e.g., S-NSSAI).
- UE1 being out of the EDN service area may mean that UE1 is out of the EES service area or out of the EAS service area.
- the EDN service area may be the same as the EES service area or the EAS service area.
- An EES service area is a service area provided by an EES within an EDN.
- the EAS Service Area is the service area provided by the EAS within the EDN.
- An EES service area may be a topological service area or a geographic service area.
- the EAS service area may be a topological service area or a geographic service area.
- a topological service area is defined in relation to the UE's point of attachment to the network.
- a topological service area may be defined by a set of Cell IDs, a set of TAIs, or a PLMN ID.
- a Geographical Service Area shall be defined by geographic coordinates, an area defined as a circle whose center is denoted by geographic coordinates (a circle whose center is denoted by geographic coordinates), or a polygon (a may be an area defined as a polygon whose corners are denoted by geographical coordinates.
- Geographical service areas can also be represented in other ways, such as well-known buildings, parks, arenas, civic addresses, ZIP codes, and so on.
- the SMF 32 may be preset with specific LADNs or specific EDNs by the MNO.
- the SMF 32 may obtain settings from the AMF 31 or UDM 35 indicating specific LADNs or specific EDNs.
- certain LADNs may be LADNs for EDNs.
- Specific LADNs or specific EDNs may be managed by UDM 35 as subscriber information for UE1. In that case, information about specific LADNs or specific EDNs may be transferred from UDM 35 to AMF 31 by Nudm_SDM_Get service when UE 1 is in the registration procedure.
- the SMF 32 is notified of information about specific LADNs or specific EDNs from the AMF 31 via the Nsmf_PDUSession_CreateSMContextRequest message or the Nsmf_PDUSession_UpdateSMContextRequest message. good.
- SMF 32 may receive information about particular LADNs or particular EDNs from UDM 35 using the Nudm_SDM_Get service, for example when UE 1 establishes a PDU Session for that LADN or that EDN.
- the information about specific LADNs or specific EDNs may be UE local configuration information defined by Non-Patent Document 4. In that case, information about specific LADNs or specific EDNs may be sent from UE 1 via AMF 31 to SMF 32 using NAS messages (or NAS SM messages).
- SMF32 may distinguish a specific PDU Session based on a request from AF5 via NEF36. Specifically, if the SMF 32 has previously received information from the AF 5 indicating that it will wait for a response from the AF 5 before starting the release of the PDU Session or the deactivation of the UP connection, the SMF 32 may send an event notification to AF5 and wait for a response from AF5 before releasing the UP connection or deactivating the UP connection.
- FIG. 4 is a flow chart showing an example of the operation of the SMF 32 according to this embodiment.
- SMF 32 receives a first event notification from AMF 31 indicating that UE1 is out of EDN service area or out of LADN service area.
- SMF 32 detects an event regarding an Application Context Relocation (ACR) procedure.
- ACR Application Context Relocation
- the SMF 32 performs a procedure for releasing the PDU Session for the LADN associated with the LADN service area associated with the EDN service area. Initiate the procedure to release the PDU Session for (or associated with) or deactivate the UP connection for the PDU Session.
- the SMF 32 releases the PDU Session for the EDN or the LADN, or releases the UP connection. Wait for an event related to the ACR procedure before activating.
- SMF 32 may perform the operations of FIG. 4 only for specific EDNs, specific LADNs, specific PDU Sessions, or specific UEs.
- Events related to ACR procedures may include receiving a response from AF5 directly or via NEF36 after sending a second event notification from SMF32 to AF5 directly or via NEF36. If SMF32 has previously received information from AF5 indicating that SMF32 waits for a response from AF5 before starting release of the PDU Session or deactivation of the UP connection, SMF32 releases the PDU Session. or send a second event notification to AF5 and wait for a response from AF5 before deactivating the UP connection. For example, information indicating to wait for an acknowledgment from AF5 before initiating release of the PDU Session or deactivation of the UP connection may be indicated by the indication "AF acknowledgment to be expected" ( indication).
- the SMF 32 has previously received an AF request, which is a request to subscribe to the provision service of the second event notification for PDU Session, directly from the AF 5 or via the NEF 36, and "AF acknowledgment expected If the request contained an indication that "AF acknowledgment to be expected", SMF 32, before releasing the PDU Session or deactivating the UP connection, sends AF 5 a second It may send an event notification and wait for a response from AF5. In other words, the SMF 32 manages the PDU Session release timing based on runtime coordination between 5GC and EDGEAPP using "AF acknowledgment to be expected".
- the second event notification may indicate that UE1 is out of EDN service area or out of LADN service area.
- the second event notification may indicate pre-notification of release of PDU Session for EDN or LADN or pre-notification of deactivation of UP connection.
- a response from AF5 may indicate completion of the ACR procedure, including transfer of application context from S-EAS to T-EAS.
- the event regarding the ACR procedure may include the expiration (or elapse) of a predetermined amount of time for waiting for the completion of the ACR procedure.
- SMF 32 may start a timer to count a predetermined amount of time after receiving a first event notification from AMF 31 indicating that UE 1 is out of EDN service area or out of LADN service area.
- SMF 32 may determine whether starting the timer is required based on DNN or LADN or EDN.
- the SMF 32 may determine whether starting the timer is required based on the type of DNN or LADN or EDN.
- SMF 32 may determine whether the timer is required to start based on whether a DNN or LADN or EDN is associated with the timer.
- the SMF 32 may decide to perform the PDU Session release procedure or the UP connection deactivation procedure based on the detection of events related to the ACR procedure.
- the event related to the ACR procedure may include the SMF 32 receiving a notification or message related to the procedure specified in Chapter 4.3.6.2 of Non-Patent Document 4.
- the SMF 32 may initiate a procedure for releasing the PDU Session for the EDN or the LADN or deactivating the UP connection for the PDU Session by means of the Npcf_SMPolicyControl_UpdateNotify service received from the PCF 34. good. That is, the Npcf_SMPolicyControl_UpdateNotify service called by the PCF 34 instructs the SMF 32 to release the PDU Session for the EDN or LADN, or deactivate the UP connection for the PDU Session.
- PCF 34 may decide to send the instruction based on information provided to PCF 34 from AF 5 (e.g., S-EES) via NEF 36 and UDM 35 .
- AF5 e.g., S-EES
- AF5 e.g., S-EES
- AF5 performs a procedure to release the PDU Session of the EDN or LADN or deactivate the UP connection for the PDU Session to the 3GPP core network. You can point to 3.
- SMF 32 starts releasing the PDU Session for the EDN or LADN or deactivating the UP connection. can wait for the grace period to expire. This can help prevent failure of the ACR procedure when UE1 moves between different LADNs or different EDNs. Specifically, after the UE1 moves out of the EDN service area or out of the LADN service area, the PDU Session is maintained for a while (for example, until an event related to the ACR procedure is detected) due to the old EDN or old LADN.
- the SMF 32 waits until it can guarantee that the ACR procedure has completed successfully, until it presumes that the ACR procedure has completed successfully, or until it confirms that the ACR procedure has completed successfully. Maintain PDU Session for EDN or old LADN. Therefore, UE1 can communicate with the old EDN or the EES of the old LADN (that is, S-EES) via the PDU Session. Therefore, this can increase the probability of successfully completing the ACR procedure with signaling between the S-EES and the EEC 11 of UE1.
- EDN service area management using network slices may be performed.
- an EDN or an EES or EAS within an EDN may be associated with a particular network slice.
- UE1 may be able to access the EDN (or EES or EAS) associated with a particular network slice only when UE1 is authorized to use that network slice.
- a particular network slice may be available throughout the PLMN or only in some topological areas within the PLMN.
- a topological area may be one or more TAs (or TAIs). If a particular network slice is only available on one or more TAs, the registration area of UE1 establishing a PDU Session for accessing the EAS within that EDN is assigned to a particular network slice.
- step 401 in FIG. 4 is the PDU Session due to UE1 moving out of the topological area (e.g., one or more TAs) assigned to the specific network slice (or specific S-NSSAI). This is an instruction to release or deactivate the UP connection.
- UE1 is notified of Allowed NSSAI containing a certain S-NSSAI from 3GPP core network 3 (i.e., AMF31), and there are one or more PDU Sessions of UE1 related to that S-NSSAI.
- AMF31 3GPP core network 3
- PDU Sessions of UE1 related to that S-NSSAI if UE1 has moved out of the topological area assigned to the S-NSSAI (or the current registration area of UE1), then in step 401 of FIG. Notifies the UE1 as an NSSAI, and instructs the SMF 32 to release the PDU Session(s) related to the S-NSSAI.
- step 402 of FIG. 4 In the case where EDN service area management using network slices is performed, the operation of SMF 32 in step 402 of FIG. 4 is the same as that described above.
- step 403 of FIG. 4 in response to detecting an event related to the ACR procedure in step 402, SMF 32 releases UE1's PDU Session(s) associated with the S-NSSAI that has become a Rejected S-NSSAI.
- SMF 32 will wait before initiating the release of the PDU Session or deactivation of the UP connection for the EDN associated with the EDN service area. You can wait for the period to pass. This can help prevent failure of the ACR procedure when UE1 moves between different EDNs. Specifically, after UE1 moves out of the EDN service area, the PDU Session is maintained for the old EDN for a while (for example, until an event related to the ACR procedure is detected). For example, the SMF 32 waits until it can guarantee that the ACR procedure has completed successfully, until it presumes that the ACR procedure has completed successfully, or until it confirms that the ACR procedure has completed successfully.
- UE1 can communicate with the old EDN's EES (that is, S-EES) via the PDU Session. Therefore, this can increase the probability of successfully completing the ACR procedure with signaling between the S-EES and the EEC 11 of UE1.
- EES that is, S-EES
- This embodiment provides a detailed example of the operation of the SMF 32 described in the first embodiment, and a detailed example of the operation of the AMF 31, NEF 36 and AF5 effective therefor.
- An example network architecture according to this embodiment is similar to the example described with reference to FIGS.
- FIG. 5 is a flow chart showing an example of the operation of the SMF 32.
- Step 501 is similar to step 401 of FIG. Specifically, in step 501 , SMF 32 receives a first event notification from AMF 31 indicating that UE 1 is out of EDN service area or out of LADN service area.
- Steps 502 and 503 provide an example of step 402 of FIG.
- SMF 32 sends a second event notification to AF 5 (e.g., S-EES) either directly or via NEF 36 .
- AF 5 e.g., S-EES
- SMF 32 detects that it has received a response to the second event notification from AF 5 directly or via NEF 36 .
- step 504 after detecting that a response to the second event notification has been received, the SMF 32 performs the procedure for releasing the PDU Session for the LADN associated with the LADN service area, Initiate the procedure to release the PDU Session for the EDN or deactivate the UP connection for that PDU Session.
- FIG. 6 is a flow chart showing an example of the operation of AF5 (e.g., S-EES).
- AF5 e.g., S-EES
- receives a second event notification either directly from SMF 32 or via NEF 36 e.g., S-EES.
- AF 5 sends a response to the second event notification to SMF 32 directly or via NEF 36 after the S-EAS to T-EAS ACR procedure is completed.
- the response may trigger SMF 32 to release the PDU Session for EDN or LADN or deactivate the UP connection.
- FIG. 7 is a sequence diagram showing an example of operations of AMF31, SMF32, NEF36, and AF5.
- AF5 may include S-EES.
- AMF 31 sends an event notification to SMF 32 indicating that UE1 is out of EDN service area or out of LADN service area.
- SMF 32 may pre-subscribe to UE mobility event notifications of AMF 31 using event ID "UE moving in or out of Area of Interest". As a result, the SMF 32 can receive notification about the event ID (get notified about the event ID).
- SMF 32 sends to AF 5 via NEF 36 an event notification that explicitly or implicitly indicates that UE 1 is out of the EDN service area or out of the LADN service area.
- SMF 32 responds to detecting an event (e.g., "Presence-In-AOI-Report") subscribed by an NF consumer (i.e., AF5 or NEF 36) by: Invoke Nsmf_EventExposure_Notify service operation to report the event to NEF 36 or AF 5 .
- NEF 36 calls a service operation to report the event to AF 5.
- the service operation called by the NEF 36 may be an improvement of an existing service operation (e.g., Nnef_EventExposure) or a newly defined service operation (e.g., Nnef_AOIEventNotification).
- AF5 sends a response to SMF32 via NEF36.
- AF 5 sends a response (Acknowledgment of AOI EventNotification or Acknowledgment of EventExposure) to the event notification in step 703 to NEF 36.
- the response may indicate completion of the ACR procedure, including transfer of application context from S-EAS to T-EAS (e.g., "ACR complete").
- NEF 36 sends an acknowledgment of event notification to SMF 32 at step 702 .
- step 706 after receiving the response in step 705, the SMF 32 releases the PDU Session for the EDN or LADN or deactivates the UP connection.
- the procedure for releasing the PDU Session or deactivating the UP connection includes signaling between SMF32 and UPF33 and signaling between SMF32 and UE1 via AMF31.
- the procedure for releasing the PDU Session or deactivating the UP connection may be the same as the procedures specified in Chapter 4.3.4.2 or Chapter 4.3.7 of Non-Patent Document 2.
- the AF 5 may pre-subscribe to the notification service for that event.
- FIG. 8 shows an example of a procedure for subscribing to the event notification service by SMF32.
- the AF 5 sends an AF request to the NEF 36 to subscribe to the service of providing event notification for a particular PDU Session.
- the AF request contains the indication "AF acknowledgment to be expected”.
- AF5 may call Nnef_EventExposure_Subscribe operation with event ID "Presence In AOI Report".
- NEF 36 provides UE mobility out of an Area of Interest function as Monitoring Events so that AF 5 can detect movement of UEs. This allows AF 5 to detect the movement event of UE 1 via NEF 36 (Nnef_EventExposure_Subscribe).
- NEF 36 requests subscription to the event notification service of SMF 32 based on the AF request at step 801.
- the request contains the indication "AF acknowledgment to be expected”.
- the NEF 36 may call the Nsmf_EventExposure_Subscribe operation using the Event ID "Presence In AOI Report”.
- SMF 32 notifies AF 5 of the event before releasing the PDU Session or deactivating the UP connection based on the fact that the received request contains an indication that an "AF acknowledgment is expected”. Recognizes that it needs to send and wait for a response from AF5.
- SMF 32 provides UE mobility out of an Area of Interest function so that NEF 36 or AF 5 via NEF 36 can detect the movement of UEs. Thereby, the NEF 36 or the AF 5 via the NEF 36 can receive the movement event notification (Nsmf_EventExposure_Notify) of the UE 1 from the SMF 32 .
- the SMF32 releases the PDU Session for the EDN or the LADN or deactivates the UP connection. Sends an event notification to AF5 and waits for a response from AF5 before commencing initialization. This can help prevent failure of the ACR procedure when UE1 moves between different EDNs corresponding to different LADNs.
- This embodiment provides a detailed example of the operation of the SMF 32 described in the first embodiment, and a detailed example of the operation of the AMF 31, NEF 36 and AF5 effective therefor.
- An example network architecture according to this embodiment is similar to the example described with reference to FIGS.
- FIG. 9 is a flowchart showing an example of the operation of the SMF32.
- Step 901 is similar to step 401 of FIG. Specifically, in step 901, SMF 32 receives a first event notification from AMF 31 indicating that UE1 is out of EDN service area or out of LADN service area. At step 902, the SMF 32 detects expiration of a predetermined time to wait for ACR procedure completion. SMF 32 may start a timer to count the predetermined time after receiving the first event notification. In step 903, after expiration of the predetermined time, the SMF 32 performs a procedure for releasing the PDU Session for the LADN associated with the LADN service area, releasing the PDU Session for the EDN associated with the EDN service area.
- SMF 32 determines whether to start the timer based on whether the EDN or LADN associated with the first event notification is a particular EDN or LADN. You can judge.
- EDN service area management using network slices may be performed.
- an EDN or an EES or EAS within an EDN may be associated with a particular network slice.
- UE1 may be able to access the EDN (or EES or EAS) associated with a particular network slice only when UE1 is authorized to use that network slice.
- EDN or EES or EAS
- the registration area of UE1 establishing a PDU Session for accessing the EAS within that EDN is assigned to a particular network slice.
- an EDN service area is the same as or a subset thereof of one or more TAs (or TAIs) assigned to a particular network slice.
- step 901 in FIG. 9 is the PDU Session due to UE1 moving out of the topological area (e.g., one or more TAs) assigned to the specific network slice (or specific S-NSSAI). This is an instruction to release or deactivate the UP connection.
- UE1 is notified of Allowed NSSAI containing a certain S-NSSAI from 3GPP core network 3 (i.e., AMF31), and there are one or more PDU Sessions of UE1 related to that S-NSSAI.
- 3GPP core network 3 i.e., AMF31
- PDU Sessions of UE1 related to that S-NSSAI if UE1 has moved out of the topological area assigned to the S-NSSAI (or the current registration area of UE1), then in step 901 of FIG. Notifies UE 1 as NSSAI and instructs SMF 32 to release PDU Session(s) related to the S-NSSAI.
- step 902 of FIG. 9 In the case where EDN service area management using network slices is performed, the operation of SMF 32 in step 902 of FIG. 9 is the same as that described above.
- step 903 of FIG. 9 in response to detecting an event related to the ACR procedure in step 902, SMF 32 releases UE1's PDU Session(s) associated with the S-NSSAI that has become a Rejected S-NSSAI.
- FIG. 10 is a sequence diagram showing an example of operations of AMF31, SMF32, NEF36, and AF5.
- AF5 may include S-EES.
- AMF 31 sends an event notification to SMF 32 indicating that UE1 is out of EDN service area or out of LADN service area.
- SMF 32 may pre-subscribe to UE mobility event notifications of AMF 31 using event ID "UE moving in or out of Area of Interest". As a result, the SMF 32 can receive notification regarding the event ID.
- the AMF 31 is outside the topological area (or current registration area of UE 1) assigned to the S-NSSAI associated with the EDN (or EES or EAS).
- it may send an event notification in step 1001, ie an indication to release the PDU Session(s) associated with that S-NSSAI.
- AMF 31 may inform SMF 32 of the release of PDU Session(s) associated with the S-NSSAI by calling Nsmf_PDUSession_ReleaseSMContext service operation.
- the SMF 32 starts a timer.
- the value set for the timer may be determined based on local policy.
- the timer value may be determined based on the subscriber information of UE1.
- UE1 may indicate the timer value in the PDU Session establishment procedure.
- AF5 may indicate the timer value.
- AF 5 may indicate the timer value to SMF 32 via NEF 36 in the procedure for subscribing to the event notification service by SMF 32 .
- the procedure may be similar to that in FIG.
- SMF 32 may send an event notification to AF 5 via NEF 36 that explicitly or implicitly indicates that UE 1 is out of EDN service area or out of LADN service area. good.
- Steps 1003 and 1004 may be similar to steps 702 and 703 of FIG.
- the SMF 32 detects expiration of the timer.
- SMF 32 releases the PDU Session for the EDN or LADN or deactivates the UP connection.
- the procedure for releasing the PDU Session or deactivating the UP connection includes signaling between SMF32 and UPF33 and signaling between SMF32 and UE1 via AMF31.
- the procedure for releasing the PDU Session or deactivating the UP connection may be the same as the procedures specified in Chapter 4.3.4.2 or Chapter 4.3.7 of Non-Patent Document 2.
- the SMF32 releases the PDU Session for the EDN or the LADN or deactivates the UP connection. Wait for the expiration of a predetermined period of time before starting to convert. This can help prevent failure of the ACR procedure when UE1 moves between different EDNs corresponding to different LADNs.
- This embodiment provides a detailed example of the operation of the SMF 32 described in the first embodiment, and a detailed example of the operation of the AMF 31 useful therefor.
- An example network architecture according to this embodiment is similar to the example described with reference to FIGS.
- FIG. 11 is a flowchart showing an example of the operation of the SMF32.
- Step 1101 is similar to step 401 in FIG. Specifically, in step 1101, SMF 32 receives a first event notification from AMF 31 indicating that UE1 is out of EDN service area or out of LADN service area.
- the SMF 32 determines whether the EDN or LADN is of a specific type.
- a particular type of EDN or LADN may be an EDN or LADN that supports (or supports) a mode for continuity of session and service.
- the LADN type may be identified based on the LADN DNN.
- the EDN type may be identified based on the EDN's (EDN) DNN, (EDN) DNN and DNAI, or (EDN) DNN and S-NSSAI. Additionally or alternatively, SMF 32 determines whether the LADN or EDN is associated with a timer. These determinations may be made based on the LADN DNN of the LADN in question. These determinations may be made based on (EDN) DNN of the EDN, (EDN) DNN and DNAI, or (EDN) DNN and S-NSSAI. If the EDN or LADN is of a particular type or is associated with a timer, the SMF 32 starts the timer before releasing the PDU Session for the EDN or LADN or deactivating the UP connection.
- the SMF 32 then starts a timer.
- the value set for the timer may be determined based on local policy.
- the timer value may be determined based on the subscriber information of UE1.
- UE1 may indicate the timer value in the PDU Session establishment procedure.
- the SMF 32 detects expiration of the timer.
- the SMF 32 performs a procedure for releasing the PDU Session for the LADN associated with the LADN Service Area, a procedure for releasing the PDU Session for the EDN associated with the EDN Service Area, or initiate the procedure to deactivate the UP connection for that PDU Session.
- a new DNN information element called "continuity of session and service capable LADN DNN” or “continuity of session and service capable EDN DNN” to aid determination by SMF 32 in step 1102. may be defined.
- SMF 32 may determine whether the EDN or LADN is associated with this new DNN information element.
- the terms “continuity of session and service” and “mode for continuity of session and service” are used.
- the definition of is different from that of "SSC” and “SSC mode” in the current 3GPP specifications described in Non-Patent Documents 1 and 2.
- SSC and “SSC mode” is used to maintain PDU Session connectivity to the same DN (or same DNN), in particular SSC mode 2 and mode 3 have the same DN (or DNN) as the old PDU Session.
- continuity of session and service and “mode for continuity of session and service” are defined by UE1 as the first When moving out of the LADN service area corresponding to one DNN, a new PDU Session service for a second DNN different from the first DNN before releasing the old PDU Session with the first DNN.
- continuity of session and service and mode for continuity of session and service indicate that if UE1 moves out of the LADN service area corresponding to the first DNN, the old PDU Session with the first DNN is Before releasing, it comprises establishing a new PDU Session service for the second DNN to which the application context is transferred from the first DNN.
- FIG. 12 is a sequence diagram showing an example of operations of the AMF 31 and SMF 32.
- AMF 31 sends an event notification to SMF 32 indicating that UE1 is out of EDN service area or out of LADN service area.
- SMF 32 may pre-subscribe to UE mobility event notifications of AMF 31 using event ID "UE moving in or out of Area of Interest". As a result, the SMF 32 can receive notification regarding the event ID.
- the AMF 31 is outside the topological area (or current registration area of UE 1) assigned to the S-NSSAI associated with the EDN (or EES or EAS).
- it may send an event notification in step 1201, ie an indication to release the PDU Session(s) associated with that S-NSSAI.
- AMF 31 may inform SMF 32 of the release of PDU Session(s) associated with the S-NSSAI by calling Nsmf_PDUSession_ReleaseSMContext service operation.
- the SMF 32 determines whether the EDN or LADN is of a specific type. As described above, a particular type of EDN or LADN is an EDN or LADN that supports (or supports) a mode for continuity of session and service, for example but not limited to be. SMF 32 may determine whether the LADN in question is associated with a particular DNN information element, such as the "continuity of session and service capable” information element. Alternatively, SMF 32 may determine whether the EDN is associated with a particular DNN information element, such as the "continuity of session and service capable EDN DNN" information element.
- SMF 32 recognizes that a timer needs to be started before releasing the PDU Session or deactivating the UP connection for the EDN or LADN. The SMF 32 then starts a timer.
- the SMF 32 detects expiration of the timer.
- SMF 32 releases the PDU Session for the EDN or LADN or deactivates the UP connection.
- the procedure for releasing the PDU Session or deactivating the UP connection includes signaling between SMF32 and UPF33 and signaling between SMF32 and UE1 via AMF31.
- the procedure for releasing the PDU Session or deactivating the UP connection may be the same as the procedures specified in Chapter 4.3.4.2 or Chapter 4.3.7 of Non-Patent Document 2.
- the SMF32 releases the PDU Session for the EDN or the LADN or deactivates the UP connection. Wait for the expiration of the predetermined time to wait for the completion of the ACR procedure before starting the initialization. This can help prevent failure of the ACR procedure when UE1 moves between different EDNs corresponding to different LADNs.
- UE1 may perform the operations shown in FIG. 13 when establishing a PDU Session.
- the NAS layer of UE1 selects a mode for continuity of session and service if the DNN (UE requested DNN) corresponds to a given type of EDN or LADN. to select.
- the mode for session and service continuity is that if UE1 moves out of the LADN service area corresponding to the first DNN, the first establishing a new PDU Session service for a second DNN different from the first DNN before releasing the old PDU Session with the DNN.
- the second DNN is the DNN to which application context is transferred from the first DNN.
- the mode selection policy for continuity of the session and service may be configured in UE1 as part of the UE Route Selection Policy (URSP).
- the policy may be preset in UE1.
- the policy may be provided from the PCF 34 to the UE 1 via the AMF 31 in the registration procedure.
- step 1302 UE 1 sends a NAS message to AMF 31 containing a PDU Session Establishment Request indicating the selected session and mode for service continuity to request establishment of a PDU Session for the DNN. do.
- the UE 1 of this embodiment provides the EEC function.
- the EEC 11 of UE1 decides to perform any of several ACR procedures considering that UE1 has moved out of the LADN service area associated with the first EDN.
- FIG. 14 shows an example of the operation of UE1.
- the EEC 11 detects that the UE has moved out of the LADN service area associated with the EDN.
- the EEC 11 decides to perform any of several ACR procedures considering that UE1 has moved out of the LADN service area of the first EDN.
- EEC 11 performs any ACR procedure that does not involve message exchange between EEC 11 and the S-EES in the first EDN when UE 1 moves out of the LADN service area associated with the first EDN. Select and execute.
- the ACR procedure may be the ACR procedure via T-EES (EEC executed ACR via T-EES) described in Chapter 8.8.2.6 of Non-Patent Document 3.
- EEC 11 selects the ACR procedure via Target EES (T-EES) belonging to a second EDN different from the first EDN when UE 1 moves out of the LADN service area associated with the first EDN. to run.
- T-EES Target EES
- UE1's NAS layer may send a notification to UE1's EEC 11 in response to detecting that UE1 is out of the LADN service area associated with the first EDN.
- This notification may indicate the mode for session and service continuity that applies to the PDU Session for the first EDN.
- the notification may indicate a Tracking Area Identity (TAI) corresponding to the location of UE1 outside the LADN service area.
- the NAS layer of UE1 may acquire the TAI based on system information (System Information Block (SIB)) broadcasted in the AN of the destination of UE1.
- SIB System Information Block
- the EEC 11 may select the T-EES based on the TAI included in the notification.
- TAI-based T-EES selection may be based on information already provisioned in UE1.
- the information may be pre-configured in UE1.
- the information may be provided from ECS 6 to EEC 1 in a service provisioning procedure.
- EEC 11 of UE 1 chooses to perform any ACR procedure that does not involve message exchange between EEC 11 and S-EES in the first EDN. This can help prevent failure of the ACR procedure when UE1 moves between different EDNs corresponding to different LADNs.
- FIG. 15 is a block diagram showing a configuration example of UE1.
- Radio Frequency (RF) transceiver 1501 performs analog RF signal processing to communicate with RAN nodes.
- RF transceiver 1501 may include multiple transceivers.
- Analog RF signal processing performed by RF transceiver 1501 includes frequency upconversion, frequency downconversion, and amplification.
- RF transceiver 1501 is coupled with antenna array 1502 and baseband processor 1503 .
- RF transceiver 1501 receives modulation symbol data (or OFDM symbol data) from baseband processor 1503 , generates transmit RF signals, and provides the transmit RF signals to antenna array 1502 .
- RF transceiver 1501 also generates baseband received signals based on the received RF signals received by antenna array 1502 and provides them to baseband processor 1503 .
- RF transceiver 1501 may include analog beamformer circuitry for beamforming.
- the analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
- the baseband processor 1503 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
- digital baseband signal processing by the baseband processor 1503 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 1503 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 1503 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.
- MIMO Multiple Input Multiple Output
- the baseband processor 1503 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 1504, which will be described later.
- the application processor 1504 is also called CPU, MPU, microprocessor, or processor core.
- the application processor 1504 may include multiple processors (multiple processor cores).
- the application processor 1504 includes a system software program (Operating System (OS)) read from the memory 1506 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 1503 and application processor 1504 may be integrated on one chip, as indicated by the dashed line (1505) in FIG.
- baseband processor 1503 and application processor 1504 may be implemented as one System on Chip (SoC) device 1505 .
- SoC devices are sometimes called system Large Scale Integration (LSI) or chipsets.
- the memory 1506 is volatile memory, non-volatile memory, or a combination thereof.
- Memory 1506 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 1506 may include external memory devices accessible from baseband processor 1503 , application processor 1504 , and SoC 1505 .
- Memory 1506 may include embedded memory devices integrated within baseband processor 1503 , within application processor 1504 , or within SoC 1505 . Additionally, memory 1506 may include memory within a Universal Integrated Circuit Card (UICC).
- UICC Universal Integrated Circuit Card
- the memory 1506 may store one or more software modules (computer programs) 1507 containing instructions and data for processing by the UE 1 as described in multiple embodiments above.
- the baseband processor 1503 or the application processor 1504 is configured to read and execute the software module 1507 from the memory 1506 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 1501 and antenna array 1502 : baseband processor 1503 and/or application processor 1504 and software module 1507 . can be realized by a memory 1506 that stores the
- FIG. 16 shows a configuration example of a device that provides AF5 functions.
- Devices providing other network functions such as AMF 31, SMF 32, and NEF 36, may also have a similar configuration as shown in FIG.
- AF5 or AMF31, or SMF32, or NEF36
- FIG. 1601 is used, for example, to communicate with other network functions (NFs) or nodes.
- Network interface 1601 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).
- NIC network interface card
- the processor 1602 may be, for example, a microprocessor, Micro Processing Unit (MPU), or Central Processing Unit (CPU). Processor 1602 may include multiple processors.
- MPU Micro Processing Unit
- CPU Central Processing Unit
- the memory 1603 is composed of a volatile memory and a nonvolatile memory.
- Memory 1603 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 1603 may include storage remotely located from processor 1602 . In this case, processor 1602 may access memory 1603 via network interface 1601 or an I/O interface (not shown).
- the memory 1603 stores one or more software modules (computer programs) 1604 including instructions and data for AF5 (or AMF31, or SMF32, or NEF36) processing described in the above embodiments. may be stored.
- the processor 1602 is configured to read and execute the software module 1604 from the memory 1603 to perform the AF5 (or AMF31, or SMF32, or NEF36) processing described in the above embodiments. may be
- each of the processors of the UE 1, AF 5, AMF 31, SMF 32, and NEF 36 has a executes one or more programs containing the instructions of
- a program includes a set of instructions (or software code) that, when read into a computer, cause the computer to perform one or more of the functions described in the embodiments.
- the program may be stored in a non-transitory computer-readable medium or tangible storage medium.
- computer readable media or tangible storage media may include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drives (SSD) or other memory technology, CDs - ROM, digital versatile disk (DVD), Blu-ray disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc storage or other magnetic storage device.
- the program may be transmitted on a transitory computer-readable medium or communication medium.
- transitory computer readable media or communication media include electrical, optical, acoustic, or other forms of propagated signals.
- a Session Management Function (SMF) node memory; at least one processor coupled to the memory; with The at least one processor after receiving a first event notification from an Access and Mobility Management Function (AMF) node indicating that the User Equipment (UE) is out of Edge Data Network (EDN) service area or out of Local Area Data Network (LADN) service area; Detect events related to Application Context Relocation (ACR) procedures, a procedure for releasing a Protocol Data Unit (PDU) Session for a LADN associated with said LADN Service Area in response to detecting an event relating to said ACR procedure; Initiating a procedure to release a PDU Session or a procedure to deactivate a User Plane (UP) connection for said PDU Session; configured as SMF node.
- AMF Access and Mobility Management Function
- the event related to the ACR procedure is sent from the SMF node directly to an Application Function (AF) node or after sending a second event notification via a Network Exposure Function (NEF) node, and then the LADN associated with the LADN service area. to release the PDU Session for the EDN associated with the EDN Service Area, or to deactivate the UP connection for the PDU Session.
- AF Application Function
- NEF Network Exposure Function
- UDM Unified Data Management
- the second event notification includes notification of information indicating that the UE is outside the EDN service area or outside the LADN service area, The SMF node according to any one of Appendices 2-4.
- the second event notification includes pre-notification of release of the PDU Session for the EDN, pre-notification of release of the PDU Session for the LADN, or pre-notification of deactivation of the UP connection.
- the SMF node according to any one of Appendices 2-4.
- the at least one processor receiving a request to subscribe to the second event notification providing service for the PDU Session from the AF node or the NEF node; A procedure for releasing a PDU Session for an LADN associated with the LADN service area, a procedure for releasing a PDU Session for an EDN associated with the EDN service area, or deactivating a UP connection for the PDU Session.
- detecting an event related to the ACR procedure after receiving the first event notification, provided that the request includes an indication to wait for a response from the AF node before initiating the unifying procedure configured as The SMF node according to any one of Appendices 2-6.
- Events related to the ACR procedure include expiration of time to wait for the completion of the ACR procedure;
- the SMF node according to any one of Appendices 1-7.
- the at least one processor is configured to start a timer to count time to wait for the ACR procedure to complete after receiving the first event notification.
- the SMF node described in Appendix 8. (Appendix 10) The at least one processor determines whether the start of the timer is required prior to the PDU Session release procedure or the UP connection deactivation procedure. ), An SMF node as described in Appendix 9.
- the at least one processor determines whether the timer is required to start before the PDU Session release procedure or the UP connection deactivation procedure, based on the LADN or EDN type. configured to An SMF node as described in Appendix 9.
- the at least one processor determines whether the start of the timer is required before the PDU Session release procedure or the UP connection deactivation procedure, the LADN or the LADN associated with the timer. configured to determine based on whether An SMF node as described in Appendix 9.
- the LADN Service Area or the EDN Service Area is a set of one or more Tracking Areas (TAs), The SMF node according to any one of Appendices 1-12.
- a method performed by a Session Management Function (SMF) node comprising: after receiving a first event notification from an Access and Mobility Management Function (AMF) node indicating that the User Equipment (UE) is out of Edge Data Network (EDN) service area or out of Local Area Data Network (LADN) service area; detecting events related to Application Context Relocation (ACR) procedures; a procedure for releasing a Protocol Data Unit (PDU) Session for a LADN associated with said LADN Service Area in response to detecting an event relating to said ACR procedure; Initiating a procedure for releasing a PDU Session or deactivating a User Plane (UP) connection for said PDU Session; How to prepare.
- SMF Session Management Function
- a program that causes a computer to perform a method for a Session Management Function (SMF) node, the method comprising: after receiving a first event notification from an Access and Mobility Management Function (AMF) node indicating that the User Equipment (UE) is out of Edge Data Network (EDN) service area or out of Local Area Data Network (LADN) service area; detecting events related to Application Context Relocation (ACR) procedures; a procedure for releasing a Protocol Data Unit (PDU) Session for a LADN associated with said LADN Service Area in response to detecting an event relating to said ACR procedure; Initiating a procedure for releasing a PDU Session or deactivating a User Plane (UP) connection for said PDU Session; program.
- SMF Session Management Function
- An Application Function (AF) node memory; at least one processor coupled to the memory; with The at least one processor receive event notifications directly from Session Management Function (SMF) nodes or via Network Exposure Function (NEF) nodes; After completing an Application Context Relocation (ACR) procedure that includes transfer of application context from the Source Edge Application Server (S-EAS) to the Target EAS (T-EAS), send a response to the event notification directly to the SMF node or transmitting through said NEF node; is configured as The response is a procedure for releasing a PDU Session for a Local Area Data Network (LADN), a procedure for releasing a PDU Session for an Edge Data Network (EDN), or a User Plane (UP) connection for the PDU Session.
- LADN Local Area Data Network
- EDN Edge Data Network
- UP User Plane
- the event notification indicates that User Equipment (UE) is out of the service area of the EDN or out of the service area of the LADN, indicating prior notification of release of the PDU Session for the LADN. or indicating pre-notification of deactivation of the UP connection for the PDU Session;
- UE User Equipment
- a method performed by an Application Function (AF) node comprising: receiving event notifications directly from Session Management Function (SMF) nodes or via Network Exposure Function (NEF) nodes; After completing an Application Context Relocation (ACR) procedure that includes transfer of application context from the Source Edge Application Server (S-EAS) to the Target EAS (T-EAS), send a response to the event notification directly to the SMF node or transmitting through said NEF node; with The response is a procedure for releasing a PDU Session for a Local Area Data Network (LADN), a procedure for releasing a PDU Session for an Edge Data Network (EDN), or a User Plane (UP) connection for the PDU Session.
- LADN Local Area Data Network
- EDN Edge Data Network
- UP User Plane
- LADN Local Area Data Network
- EDN Edge Data Network
- UP User Plane
- UE User Equipment
- DNN primary Data Network Name
- LADN Local Area Data Network
- PDU Protocol Data Unit
- the mode for continuity of the one session and service is the first before releasing the first PDU Session when the UE moves out of the LADN service area corresponding to the first DNN.
- AMF Mobility Management Function
- a method performed by User Equipment comprising: If the primary Data Network Name (DNN) corresponds to a given type of Local Area Data Network (LADN), select mode for continuity of session and service thing, Access a Non-Access Stratum (NAS) message containing a PDU Session Establishment Request indicating the selected mode to request establishment of a first Protocol Data Unit (PDU) Session for the first DNN. and Mobility Management Function (AMF) nodes; with The mode for continuity of the one session and service is the first before releasing the first PDU Session when the UE moves out of the LADN service area corresponding to the first DNN. establishing a second PDU Session for a second DNN to which application context is transferred from the DNN of Method.
- DNN Data Network Name
- LADN Local Area Data Network
- NAS Non-Access Stratum
- AMF Mobility Management Function
- DNN Data Network Name
- LADN Local Area Data Network
- NAS Non-Access Stratum
- AMF Mobility Management Function
- UE User Equipment
- EEC Edge Enabler Client
- LADN Local Area Data Network
- EDN Edge Data Network
- the EEC function exchanges messages between the EEC and a Source Edge Enabler Server (S-EES) in the first EDN when the UE moves out of the LADN service area of the first EDN. comprising selecting and executing any ACR procedure that does not include The UE of Supplementary Note 23.
- S-EES Source Edge Enabler Server
- the EEC function performs ACR via Target EES (T-EES) belonging to a second EDN different from the first EDN when the UE moves out of the LADN service area associated with the first EDN. comprising selecting and performing a procedure; The UE of Supplementary Note 23.
- the EEC function shall perform multiple ACR procedures unless the Protocol Data Unit (PDU) Session for the first EDN is subject to a mode for continuity of session and service. comprising determining to perform any of The UE according to any one of clauses 23-25.
- the at least one processor configured to provide Non-Access Stratum (NAS) layer functionality;
- the NAS layer function comprises sending a notification to the EEC function in response to detecting that the UE is outside the LADN service area associated with the first EDN; the notification indicates a mode for continuity of session and service to apply to a Protocol Data Unit (PDU) Session for the first EDN;
- the UE according to any one of clauses 23-26.
- the notification indicates a Tracking Area Identity (TAI) corresponding to the location of the UE outside the LADN service area;
- TAI Tracking Area Identity
- the EEC function comprises selecting a Target EES (T-EES) based on the TAI included in the notification;
- T-EES Target EES
- ACR Application Context Relocation
- EEC Edge Enabler Client
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
図1は、本実施形態に係る無線通信ネットワーク(i.e., 5GS)の構成例を示している。図1に示された要素の各々はネットワーク機能であり、3GPPにより定義されたインタフェースを提供する。図1に示された各要素(ネットワーク機能)は、例えば、専用ハードウェア(dedicated hardware)上のネットワークエレメントとして、専用ハードウェア上で動作する(running)ソフトウェア・インスタンスとして、又はアプリケーション・プラットフォーム上にインスタンス化(instantiated)された仮想化機能として実装されることができる。
本実施形態は、第1の実施形態で説明されたSMF32の動作の詳細な例と、そのために有効なAMF31、NEF36、及びAF5の動作の詳細な例を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1~図3を参照して説明された例と同様である。
本実施形態は、第1の実施形態で説明されたSMF32の動作の詳細な例と、そのために有効なAMF31、NEF36、及びAF5の動作の詳細な例を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1~図3を参照して説明された例と同様である。
本実施形態は、第1の実施形態で説明されたSMF32の動作の詳細な例と、そのために有効なAMF31の動作の詳細な例を提供する。本実施形態に係るネットワークアーキテクチャの例は、図1~図3を参照して説明された例と同様である。
本実施形態に係るネットワークアーキテクチャの例は、図1~図3を参照して説明された例と同様である。
Session Management Function(SMF)ノードであって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出し、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始する、
よう構成される、
SMFノード。
(付記2)
前記ACR手順に関するイベントは、前記SMFノードからApplication Function(AF)ノードへ直接又はNetwork Exposure Function(NEF)ノードを介して第2のイベント通知を送信した後に、前記AFノードから直接又は前記NEFノードを介して前記第2のイベント通知に対応する応答を受信することを含む、
付記1に記載のSMFノード。
(付記3)
前記応答は、Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含む前記ACR手順の完了を示す、
付記2に記載のSMFノード。
(付記4)
前記ACR手順に関するイベントは、前記SMFノードからApplication Function(AF)ノードへ直接又はNetwork Exposure Function(NEF)ノードを介して第2のイベント通知を送信した後に、前記LADNサービスエリアに関連付けられたLADNのためのPDU Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUPコネクションを非活性化する手順を開始することを指示するメッセージをPolicy Control Function(PCF)ノードから受信することを含み、
前記メッセージは、前記AFノードから前記NEFノード及びUnified Data Management(UDM)ノードを介して前記PCFノードに提供される情報に基づいて送信される、
付記1に記載のSMFノード。
(付記5)
前記第2のイベント通知は、前記UEが前記EDNサービスエリア外であること又は前記LADNサービスエリア外であることを示す情報の通知を含む、
付記2~4のいずれか1項に記載のSMFノード。
(付記6)
前記第2のイベント通知は、前記EDNのための前記PDU Sessionの解放の事前通知、前記LADNのための前記PDU Sessionの解放の事前通知、又は前記UPコネクションの非活性化の事前通知を含む、
付記2~4のいずれか1項に記載のSMFノード。
(付記7)
前記少なくとも1つのプロセッサは、
前記PDU Sessionについての前記第2のイベント通知の提供サービスに加入するための要求を前記AFノード又は前記NEFノードから受信し、
前記LADNサービスエリアに関連付けられたLADNのためのPDU Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUPコネクションを非活性化する手順を開始する前に、前記AFノードからの応答を待つことを指示する表示を前記要求が含むことを条件に、前記第1のイベント通知の受信後に前記ACR手順に関するイベントを検出する、
よう構成される、
付記2~6のいずれか1項に記載のSMFノード。
(付記8)
前記ACR手順に関するイベントは、前記ACR手順完了を待つための時間の満了を含む、
付記1~7のいずれか1項に記載のSMFノード。
(付記9)
前記少なくとも1つのプロセッサは、前記第1のイベント通知を受信した後に、前記ACR手順完了を待つための時間をカウントするためにタイマーを開始するよう構成される、
付記8に記載のSMFノード。
(付記10)
前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記EDNのData Network Name(DNN)に基づいて決定するよう構成される、
付記9に記載のSMFノード。
(付記11)
前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記EDNの種別に基づいて決定するよう構成される、
付記9に記載のSMFノード。
(付記12)
前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記LADNが前記タイマーに関連付けられているか否かに基づいて決定するよう構成される、
付記9に記載のSMFノード。
(付記13)
前記LADNサービスエリア又は前記EDNサービスエアリアは、1又はそれ以上のTracking Areas(TAs)のセットである、
付記1~12のいずれか1項に記載のSMFノード。
(付記14)
Session Management Function(SMF)ノードにより行われる方法であって、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出すること、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始すること、
を備える方法。
(付記15)
Session Management Function(SMF)ノードのための方法をコンピュータに行わせるプログラムであって、前記方法は、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出すること、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始すること、
を備える、プログラム。
(付記16)
Application Function(AF)ノードであって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信し、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信する、
よう構成され、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
AFノード。
(付記17)
前記イベント通知は、User Equipment(UE)が前記EDNのサービスエリア外または前記LADNのサービスエリア外であることを示す、前記LADNのための前記PDU Sessionの解放の事前通知を示す、前記EDNのための前記PDU Sessionの解放の事前通知を示す、又は前記PDU Sessionのための前記UPコネクションの非活性化の事前通知を示す、
付記16に記載のAFノード。
(付記18)
Application Function(AF)ノードにより行われる方法であって、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信すること、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信すること、
を備え、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
方法。
(付記19)
Application Function(AF)ノードのための方法をコンピュータに行わせるためのプログラムであって、前記方法は、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信すること、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信すること、
を備え、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
プログラム。
(付記20)
User Equipment(UE)であって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択し、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信する、
よう構成され、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
UE。
(付記21)
User Equipment(UE)により行われる方法であって、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択すること、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信すること、
を備え、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
方法。
(付記22)
User Equipment(UE)のための方法をコンピュータに行わせるためのプログラムであって、前記方法は、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択すること、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信すること、
を備え、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
プログラム。
(付記23)
User Equipment(UE)であって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、Edge Enabler Client(EEC)機能を提供するよう構成され、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
UE。
(付記24)
前記EEC機能は、前記UEが前記第1のEDNの前記LADNサービスエリア外に移動したときに、前記EECと前記第1のEDN内のSource Edge Enabler Server(S-EES)との間のメッセージ交換を含まないいずれかのACR手順を選択して実行することを備える、
付記23に記載のUE。
(付記25)
前記EEC機能は、前記UEが前記第1のEDNに関連する前記LADNサービスエリア外に移動したときに、前記第1のEDNと異なる第2のEDNに属するTarget EES(T-EES)経由のACR手順を選択して実行することを備える、
付記23に記載のUE。
(付記26)
前記EEC機能は、前記第1のEDNのためのProtocol Data Unit (PDU) Sessionがセッションとサービスの継続性のためのモード(mode for continuity of session and service)を適用されないなら、複数のACR手順のうちのいずれかを実行することを決定することを備える、
付記23~25のいずれか1項に記載のUE。
(付記27)
前記少なくとも1つのプロセッサは、Non-Access Stratum(NAS)レイヤ機能を提供するよう構成され、
前記NASレイヤ機能は、前記UEが前記第1のEDNに関連する前記LADNサービスエリア外であることを検出したことに応じて、通知を前記EEC機能に送ることを備え、
前記通知は、前記第1のEDNのためのProtocol Data Unit (PDU) Sessionに適用される1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を示す、
付記23~26のいずれか1項に記載のUE。
(付記28)
前記通知は、前記LADNサービスエリア外の前記UEの位置に対応するTracking Area Identity(TAI)を示す、
付記27に記載のUE。
(付記29)
前記EEC機能は、前記通知に含まれる前記TAIに基づいて、Target EES(T-EES)を選択することを備える、
付記28に記載のUE。
(付記30)
User Equipment(UE)により行われる方法であって、
Edge Enabler Client(EEC)機能を提供することを備え、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
方法。
(付記31)
User Equipment(UE)のための方法をコンピュータに行わせるためのプログラムであって、
前記方法は、Edge Enabler Client(EEC)機能を提供することを備え、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
プログラム。
2 Access Network(AN)
3 3GPPコアネットワーク
5 Application Function(AF)
6 Edge Configuration Server(ECS)
7 Edge Data Network(EDN)
8 Public Land Mobile Network(PLMN)
11 Edge Enabler Client(EEC)
12 Application client(AC)
31 Access and Mobility management Function(AMF)
32 Session Management Function(SMF)
33 User Plane Function(UPF)
34 Policy Control Function(PCF)
35 Unified Data Management(UDM)
36 Network Exposure Function(NEF)
41、42 Local Area Data Network(LADN)
43 Data Network(DN)
71 Edge Enabler Server(EES)
72 Edge Application Server(EAS)
1503 ベースバンドプロセッサ
1504 アプリケーションプロセッサ
1506 メモリ
1507 モジュール
1602 プロセッサ
1603 メモリ
1604 モジュール
Claims (31)
- Session Management Function(SMF)ノードであって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出し、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始する、
よう構成される、
SMFノード。 - 前記ACR手順に関するイベントは、前記SMFノードからApplication Function(AF)ノードへ直接又はNetwork Exposure Function(NEF)ノードを介して第2のイベント通知を送信した後に、前記AFノードから直接又は前記NEFノードを介して前記第2のイベント通知に対応する応答を受信することを含む、
請求項1に記載のSMFノード。 - 前記応答は、Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含む前記ACR手順の完了を示す、
請求項2に記載のSMFノード。 - 前記ACR手順に関するイベントは、前記SMFノードからApplication Function(AF)ノードへ直接又はNetwork Exposure Function(NEF)ノードを介して第2のイベント通知を送信した後に、前記LADNサービスエリアに関連付けられたLADNのためのPDU Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUPコネクションを非活性化する手順を開始することを指示するメッセージをPolicy Control Function(PCF)ノードから受信することを含み、
前記メッセージは、前記AFノードから前記NEFノード及びUnified Data Management(UDM)ノードを介して前記PCFノードに提供される情報に基づいて送信される、
請求項1に記載のSMFノード。 - 前記第2のイベント通知は、前記UEが前記EDNサービスエリア外であること又は前記LADNサービスエリア外であることを示す情報の通知を含む、
請求項2~4のいずれか1項に記載のSMFノード。 - 前記第2のイベント通知は、前記EDNのための前記PDU Sessionの解放の事前通知、前記LADNのための前記PDU Sessionの解放の事前通知、又は前記UPコネクションの非活性化の事前通知を含む、
請求項2~4のいずれか1項に記載のSMFノード。 - 前記少なくとも1つのプロセッサは、
前記PDU Sessionについての前記第2のイベント通知の提供サービスに加入するための要求を前記AFノード又は前記NEFノードから受信し、
前記LADNサービスエリアに関連付けられたLADNのためのPDU Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUPコネクションを非活性化する手順を開始する前に、前記AFノードからの応答を待つことを指示する表示を前記要求が含むことを条件に、前記第1のイベント通知の受信後に前記ACR手順に関するイベントを検出する、
よう構成される、
請求項2~6のいずれか1項に記載のSMFノード。 - 前記ACR手順に関するイベントは、前記ACR手順完了を待つための時間の満了を含む、
請求項1~7のいずれか1項に記載のSMFノード。 - 前記少なくとも1つのプロセッサは、前記第1のイベント通知を受信した後に、前記ACR手順完了を待つための時間をカウントするためにタイマーを開始するよう構成される、
請求項8に記載のSMFノード。 - 前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記EDNのData Network Name(DNN)に基づいて決定するよう構成される、
請求項9に記載のSMFノード。 - 前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記EDNの種別に基づいて決定するよう構成される、
請求項9に記載のSMFノード。 - 前記少なくとも1つのプロセッサは、前記PDU Sessionの解放手順又は前記UPコネクションの非活性化手順の前に前記タイマーの開始が必要とされるか否かを、前記LADN又は前記LADNが前記タイマーに関連付けられているか否かに基づいて決定するよう構成される、
請求項9に記載のSMFノード。 - 前記LADNサービスエリア又は前記EDNサービスエアリアは、1又はそれ以上のTracking Areas(TAs)のセットである、
請求項1~12のいずれか1項に記載のSMFノード。 - Session Management Function(SMF)ノードにより行われる方法であって、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出すること、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始すること、
を備える方法。 - Session Management Function(SMF)ノードのための方法をコンピュータに行わせるプログラムを格納した非一時的なコンピュータ可読媒体であって、前記方法は、
User Equipment(UE)がEdge Data Network(EDN)サービスエリア外又はLocal Area Data Network(LADN)サービスエリア外であることを示す第1のイベント通知をAccess and Mobility management Function(AMF)ノードから受信した後にApplication Context Relocation(ACR)手順に関するイベントを検出すること、
前記ACR手順に関するイベントを検出したことに応答して、前記LADNサービスエリアに関連付けられたLADNのためのProtocol Data Unit (PDU) Sessionを解放する手順、前記EDNサービスエリアに関連付けられたEDNのためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を開始すること、
を備える、非一時的なコンピュータ可読媒体。 - Application Function(AF)ノードであって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信し、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信する、
よう構成され、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
AFノード。 - 前記イベント通知は、User Equipment(UE)が前記EDNのサービスエリア外または前記LADNのサービスエリア外であることを示す、前記LADNのための前記PDU Sessionの解放の事前通知を示す、前記EDNのための前記PDU Sessionの解放の事前通知を示す、又は前記PDU Sessionのための前記UPコネクションの非活性化の事前通知を示す、
請求項16に記載のAFノード。 - Application Function(AF)ノードにより行われる方法であって、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信すること、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信すること、
を備え、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
方法。 - Application Function(AF)ノードのための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、前記方法は、
Session Management Function(SMF)ノードから直接又はNetwork Exposure Function(NEF)ノードを介してイベント通知を受信すること、
Source Edge Application Server(S-EAS)からTarget EAS(T-EAS)へのアプリケーション・コンテキストの転送を含むApplication Context Relocation(ACR)手順が完了した後に、前記イベント通知に対する応答を前記SMFノードに直接又は前記NEFノードを介して送信すること、
を備え、
前記応答は、Local Area Data Network(LADN)のためのPDU Sessionを解放する手順、Edge Data Network (EDN)のためのPDU Sessionを解放する手順、又は前記PDU SessionのためのUser Plane(UP)コネクションを非活性化する手順を、前記SMFノードに開始させるメッセージである、
非一時的なコンピュータ可読媒体。 - User Equipment(UE)であって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択し、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信する、
よう構成され、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
UE。 - User Equipment(UE)により行われる方法であって、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択すること、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信すること、
を備え、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
方法。 - User Equipment(UE)のための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、前記方法は、
第1のData Network Name(DNN)が所定の種別のLocal Area Data Network(LADN)に対応するなら、1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を選択すること、
前記第1のDNNのための第1のProtocol Data Unit (PDU) Sessionの確立を要求するために、前記選択されたモードを示すPDU Session Establishment Requestを包含するNon-Access Stratum(NAS)メッセージをAccess and Mobility management Function(AMF)ノードに送信すること、
を備え、
前記1つのセッションとサービスの継続性のためのモードは、前記UEが前記第1のDNNに対応するLADNサービスエリア外に移動した場合に、前記第1のPDU Sessionを解放する前に前記第1のDNNからアプリケーション・コンテキストを転送する先の第2のDNNのための第2のPDU Sessionを確立することを備える、
非一時的なコンピュータ可読媒体。 - User Equipment(UE)であって、
メモリと、
前記メモリに結合された少なくとも1つのプロセッサと、
を備え、
前記少なくとも1つのプロセッサは、Edge Enabler Client(EEC)機能を提供するよう構成され、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
UE。 - 前記EEC機能は、前記UEが前記第1のEDNの前記LADNサービスエリア外に移動したときに、前記EECと前記第1のEDN内のSource Edge Enabler Server(S-EES)との間のメッセージ交換を含まないいずれかのACR手順を選択して実行することを備える、
請求項23に記載のUE。 - 前記EEC機能は、前記UEが前記第1のEDNに関連する前記LADNサービスエリア外に移動したときに、前記第1のEDNと異なる第2のEDNに属するTarget EES(T-EES)経由のACR手順を選択して実行することを備える、
請求項23に記載のUE。 - 前記EEC機能は、前記第1のEDNのためのProtocol Data Unit (PDU) Sessionがセッションとサービスの継続性のためのモード(mode for continuity of session and service)を適用されないなら、複数のACR手順のうちのいずれかを実行することを決定することを備える、
請求項23~25のいずれか1項に記載のUE。 - 前記少なくとも1つのプロセッサは、Non-Access Stratum(NAS)レイヤ機能を提供するよう構成され、
前記NASレイヤ機能は、前記UEが前記第1のEDNに関連する前記LADNサービスエリア外であることを検出したことに応じて、通知を前記EEC機能に送ることを備え、
前記通知は、前記第1のEDNのためのProtocol Data Unit (PDU) Sessionに適用される1つのセッションとサービスの継続性のためのモード(mode for continuity of session and service)を示す、
請求項23~26のいずれか1項に記載のUE。 - 前記通知は、前記LADNサービスエリア外の前記UEの位置に対応するTracking Area Identity(TAI)を示す、
請求項27に記載のUE。 - 前記EEC機能は、前記通知に含まれる前記TAIに基づいて、Target EES(T-EES)を選択することを備える、
請求項28に記載のUE。 - User Equipment(UE)により行われる方法であって、
Edge Enabler Client(EEC)機能を提供することを備え、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
方法。 - User Equipment(UE)のための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、Edge Enabler Client(EEC)機能を提供することを備え、
前記EEC機能は、前記UEが第1のEdge Data Network(EDN)に関連するLocal Area Data Network(LADN)サービスエリア外に移動したことを考慮して、複数のApplication Context Relocation(ACR)手順のうちのいずれかを実行することを決定することを備える、
非一時的なコンピュータ可読媒体。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023522319A JPWO2022244533A1 (ja) | 2021-05-18 | 2022-03-31 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021-084223 | 2021-05-18 | ||
JP2021084223 | 2021-05-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022244533A1 true WO2022244533A1 (ja) | 2022-11-24 |
Family
ID=84141262
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/016629 WO2022244533A1 (ja) | 2021-05-18 | 2022-03-31 | Smfノード、afノード、ue、及びこれらの方法 |
Country Status (2)
Country | Link |
---|---|
JP (1) | JPWO2022244533A1 (ja) |
WO (1) | WO2022244533A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117580074A (zh) * | 2024-01-16 | 2024-02-20 | 深圳市佳贤通信科技股份有限公司 | 双模基站的网管适配系统及方法 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019194954A1 (en) * | 2018-04-06 | 2019-10-10 | Convida Wireless, Llc | Methods of managing connections to a local area data network (ladn) in a 5g network |
JP2019535194A (ja) * | 2017-03-20 | 2019-12-05 | エルジー エレクトロニクス インコーポレイティド | セッションを管理する方法及びsmfノード |
-
2022
- 2022-03-31 JP JP2023522319A patent/JPWO2022244533A1/ja active Pending
- 2022-03-31 WO PCT/JP2022/016629 patent/WO2022244533A1/ja active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019535194A (ja) * | 2017-03-20 | 2019-12-05 | エルジー エレクトロニクス インコーポレイティド | セッションを管理する方法及びsmfノード |
WO2019194954A1 (en) * | 2018-04-06 | 2019-10-10 | Convida Wireless, Llc | Methods of managing connections to a local area data network (ladn) in a 5g network |
Non-Patent Citations (2)
Title |
---|
HUAWEI, HISILICON, SAMSUNG: "Update in ACR scenarios when used for service continuity planning", 3GPP DRAFT; S6-211115, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e meeting; 20210412 - 20210420, 21 April 2021 (2021-04-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051997649 * |
SAMSUNG: "KI#2, Sol #34 Update for clarifications", 3GPP DRAFT; S2-2005464, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia ;20200819 - 20200902, 13 August 2020 (2020-08-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051920291 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117580074A (zh) * | 2024-01-16 | 2024-02-20 | 深圳市佳贤通信科技股份有限公司 | 双模基站的网管适配系统及方法 |
CN117580074B (zh) * | 2024-01-16 | 2024-04-05 | 深圳市佳贤通信科技股份有限公司 | 双模基站的网管适配系统及方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2022244533A1 (ja) | 2022-11-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210076192A1 (en) | Communications Method and Apparatus | |
CN113396610B (zh) | 用于归属路由漫游的pdu会话建立时的辅助授权 | |
JP2024026269A (ja) | スライス可用性に基づく周波数又は無線アクセス技術(rat)選択 | |
RU2760931C1 (ru) | Поведение ue при отклонении запроса на возобновление | |
US11363447B2 (en) | Method and device for managing and allocating binding service in a wireless network | |
US10264413B1 (en) | Integrated rich communications services (RCS) messaging | |
CN112602295B (zh) | 用于提前通知对网络qos能力的改变的方法 | |
WO2018171309A1 (zh) | 用户面功能实体的选择方法和装置、存储介质 | |
CN112823564B (zh) | 提供动态nef隧道分配的方法和相关的网络节点 | |
CN111937425B (zh) | 用于处理用户平面通信保护的安全策略的方法、用户设备和系统 | |
KR20210117554A (ko) | 무선 통신 시스템에서 저지연 위치 정보 서비스를 제공하기 위한 장치 및 방법 | |
WO2021051420A1 (zh) | 一种dns缓存记录的确定方法及装置 | |
US11489881B2 (en) | Systems and method for selection of a user plane component for internet protocol multimedia subsystem sessions | |
US20220345996A1 (en) | Method and device for management and access control of network slice in wireless communication system | |
CN111955021B (zh) | 5g系统中用于用户平面保护的安全策略的amf控制处理 | |
WO2022244533A1 (ja) | Smfノード、afノード、ue、及びこれらの方法 | |
US20230337056A1 (en) | Coordination of Edge Application Server Reselection using Edge Client Subnet | |
US11228896B2 (en) | Authorization of roaming for new radio subscribers via an alternative radio access technology | |
WO2023028527A1 (en) | Authorization, creation, and management of personal networks | |
CN116803052A (zh) | 用于akma的路由指示符检索 | |
WO2022244532A1 (ja) | Application Functionノード、User Equipment、及びこれらの方法 | |
CN116134955A (zh) | 在无线通信设备处自主激活特征以满足消费通信服务的应用的生存时间 | |
WO2023021800A1 (ja) | サーバ、User Equipment、及びこれらの方法 | |
WO2023017693A1 (ja) | User Equipment、サーバ、及びこれらの方法 | |
US20230362209A1 (en) | Systems and methods for facilitating provisioning of internet protocol multimedia subsystem services |
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: 22804449 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023522319 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18290236 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22804449 Country of ref document: EP Kind code of ref document: A1 |