Method of first communication apparatus, first communication apparatus, method of edge node, method of first core network node, method of first edge node, edge node, first core network node and first edge node

The method ensures session persistence in 5G networks by using persistent IP addresses and prefixes, addressing the issue of inconsistent traffic routing due to IP address changes, and maintaining service continuity for UEs in 5G networks.

WO2024248116A1PCT designated stage expired Publication Date: 2024-12-05NEC CORP

Patent Information

Application Number
PCT/JP2024/019978
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2024-05-31
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

In 5G networks, session persistence is disrupted when IP addresses assigned to User Equipment (UE) change, causing incoming packets to be recognized as new sessions and routed to different Edge Application Servers, leading to inconsistent traffic routing.

Method used

Implementing a method where an Internet Protocol (IP) address and prefix are used persistently, even when updated, by sending and receiving these identifiers and prefixes, ensuring that traffic from a collection of UEs is consistently routed to the same Edge Application Server through SessionPersistency mechanisms.

Benefits of technology

Guarantees session persistence even with IP address updates, ensuring that traffic from dynamic ad-hoc groups of UEs is consistently routed to the same Edge Application Server, maintaining service continuity and reducing latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024019978_05122024_PF_FP_ABST
    Figure JP2024019978_05122024_PF_FP_ABST
Patent Text Reader

Abstract

An aspect of this disclosure includes a method of a first communication apparatus. The method includes communicating with a second communication apparatus. The method includes sending an Internet Protocol (IP) address and a prefix. The IP address and the prefix are used persistently.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD OF FIRST COMMUNICATION APPARATUS, FIRST COMMUNICATION APPARATUS, METHOD OF EDGE NODE, METHOD OF FIRST CORE NETWORK NODE, METHOD OF FIRST EDGE NODE, EDGE NODE, FIRST CORE NETWORK NODE AND FIRST EDGE NODE

[0001] The present disclosure relates to a method of a first communication apparatus, a first communication apparatus, a method of an edge node, a method of a first core network node, a method of a first an edge node, an edge node, a first core network node, a first edge node and so on.

[0002] Edge Computing enables network operators and the 3rdparty service providers to host application servers close to the UE's access point of attachment, so as to achieve a service delivery through reduced end-to-end latency and load on the transport network.

[0003] Fig. 1 shows an architectural view of an edge computing system specified in TS 23.548 [NPL9]. In the context of the present application, a Data Network (DN) can be categorized as a central DN or a local part of a DN.

[0004] The central DN attached to a User Plane Function (UPF) in a 5G core (5GC) via an N6 reference point is located at a far side of the 5G system relative to UEs. On the other hand, the local part of the DN attached to another UPF in 5GC via the N6 reference point is located at a location closer to UEs. The local part of the DN can be deployed in a distributed way.

[0005] On the local part of the DN, Edge Application Servers (EASs) are application servers that are deployed to provide edge application services for UEs.

[0006] In the case of a platooning use case, all the member UEs involved need to have similar mobility characteristics, i.e., moving in the same direction and with similar speed, located in proximity to each other, and so on.

[0007] The platooning use case, therefore, requires that a collection of UEs forming a dynamic ad-hoc group should use the same Edge Application Servers and / or the same local part of the DN and / or the same access to the local part of the DN.

[0008] Fig. 2 shows an example where edge applications are deployed on a containerized architecture.

[0009] In this context of Fig. 2, the edge application services offered by a 5G system (5GS) are exposed to UEs and consumed by two groups of UEs represented with solid and dotted lines.

[0010] The edge application service is hosted by an Edge Hosting Environment (EHE) in a local part of the DN.

[0011] Within the EHE, each edge application is deployed in containers that are hosted by one or more server machines.

[0012] The server machines can be physical or virtual server machines.

[0013] A load balancer (LB) is a network device that can distribute incoming traffic from an external environment to the edge applications deployed in containers.

[0014] On the external side, the load balancer accepts incoming traffic from a group of UEs, and directs the incoming traffic to an edge application through a common IP address that is externally routable.

[0015] In this case, there are two common IP addresses represented with solid and dotted lines for the two groups of UEs.

[0016] On the internal side, the load balancer distributes the incoming traffic to edge applications running in containers.

[0017] A new feature introduced with the load balancer is session persistency which directs the incoming traffic to the same edge application.

[0018] As shown in Fig. 2, two-incoming traffic streams with solid lines are directed to the same edge application and another two-incoming traffic streams with dotted lines are also directed to the same edge application.

[0019] This behavior is achieved by referring to a source or to a destination address, session cookies, SSL session ID, etc., taken from the incoming traffic.

[0020] For example, the source IP address of an initial incoming packet on the external side is checked by the session persistence feature and then the source IP address is recorded in the load balancer.

[0021] Then the load balancer determines a certain edge application and routes the incoming packet to the edge application.

[0022] At the arrival of the 2ndand further incoming packets, they are also checked and routed to the same edge application which is determined at the arrival of the 1stincoming packet if the source IP address is the same.

[0023] With this session persistence feature, traffic from a collection of UEs forming a dynamic ad-hoc group is routed to the same edge application that is implemented in the Edge Application Server.

[0024] NPL1: 3GPP TR 21.905, "Vocabulary for 3GPP Specifications", V16.0.0 (2019-06) NPL 2: 3GPP TS 23.501, "System architecture for the 5G System (5GS)", V18.1.0 (2023-03) NPL 3: 3GPP TS 23.502, "Procedures for the 5G System (5GS)", V18.1.1 (2023-04) NPL 4: 3GPP TS 23.503, "Policy and charging control framework for the 5G System (5GS); Stage 2", V18.1.0 (2023-03) NPL 5: 3GPP TS 23.288, "Architecture enhancements for 5G System (5GS) to support network data analytics services", V18.1.0 (2023-03) NPL 6: 3GPP TS 24.501, "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3", V16.6.0 (2020-09) NPL 7: 3GPP TS 33.501, "Security architecture and procedures for 5G system", V16.4.0 (2020-09) NPL 8: 3GPP TS38.413, "NG-RAN; NG Application Protocol (NGAP)", V17.4.0 (2023-03) NPL 9: 3GPP TS 23.548, "5G System Enhancements for Edge Computing; Stage 2", V18.1.1 (2023-03) NPL 10: 3GPP TS 23.558, "Architecture for enabling Edge Applications", V18.2.0 (2023-03)

[0025] In a recent deployment based on the containerized architecture, the same edge application may not be selected because there is a case where IP addresses given to UEs are changed.

[0026] As introduced in the background, a group of UEs may move from one location to another location in an operator's service area while changing the attachment to the 5GS.

[0027] In this context, the PDU sessions between the UEs and the 5GS may be re-established and the IP addresses given to the UEs in the group could be replaced with different IP addresses assigned by SMF in the 5GS.

[0028] Due to the change of the IP addresses, the arrival packets before and after the change cannot be recognized as a single and continuous stream of packets by the session persistence feature.

[0029] Finally, the arriving packets are handled as a new session and then may be routed to a different EAS.

[0030] An issue to be at least partially resolved in this application is, therefore, how to guarantee the session persistence even if the given IP address is updated by the 5GS.

[0031] In one aspect, the present disclosure provides a method of a first communication apparatus comprising: communicating with a second communication apparatus; and sending an Internet Protocol (IP) address and a prefix, wherein the IP address and the prefix are used persistently.

[0032] In one aspect, the present disclosure provides a method of a first communication apparatus comprising: receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus; and using the IP address and the prefix persistently.

[0033] In one aspect, the present disclosure provides a method of a first communication apparatus comprising: communicating with a second communication apparatus; and sending an identifier and a prefix, wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and wherein the prefix is used persistently.

[0034] In one aspect, the present disclosure provides a method of a first communication apparatus comprising: receiving an identifier and a prefix, wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently; and assigning the IP address to the UE and using the prefix persistently.

[0035] In one aspect, the present disclosure provides a first communication apparatus comprising: means for communicating with a second communication apparatus; and means for sending an Internet Protocol (IP) address and a prefix, wherein the IP address and the prefix are used persistently.

[0036] In one aspect, the present disclosure provides a first communication apparatus comprising: means for receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus, wherein the IP address and the prefix are used persistently; and means for using the IP address and the prefix persistently.

[0037] In one aspect, the present disclosure provides a first communication apparatus comprising: means for communicating with a second communication apparatus; and means for sending an identifier and a prefix, wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and wherein the prefix is used persistently.

[0038] In one aspect, the present disclosure provides a first communication apparatus comprising: means for receiving an identifier and a prefix, wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and wherein the prefix is used persistently; and means for assigning the IP address to the UE and using the prefix persistently.

[0039] In one aspect, the present disclosure provides a method of an edge node comprising: sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event; in a case where one of the at least one event occurs, receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node; and in a case where one of the at least one event occurs, sending, to the first core network node, third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

[0040] In one aspect, the present disclosure provides a method of a first core network node comprising: receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0041] In one aspect, the present disclosure provides a method of a first edge node comprising: sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event; in a case where one of the at least one event occurs, receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF; and in a case where one of the at least one event occurs, sending, to the second edge node, a third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

[0042] In one aspect, the present disclosure provides a method of a first core network node comprising: receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0043] In one aspect, the present disclosure provides an edge node comprising: means for sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event; means for receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node in a case where one of the at least one event occurs; and means for sending, to the first core network node, third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

[0044] In one aspect, the present disclosure provides a first core network node comprising: means for receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and means for performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0045] In one aspect, the present disclosure provides a first edge node comprising: means for sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event; means for receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF in a case where one of the at least one event occurs; and means for sending, to the second edge node, a third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

[0046] In one aspect, the present disclosure provides a first core network node comprising: means for receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and means for performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0047] Fig.1 is a diagram of 5GS providing access to EAS with UL CL / BP for non-roaming scenario.Fig.2 is a diagram of Container-based deployment for an Edge Service.Fig. 3A is a signaling diagram of an example of the First Aspect.Fig. 3B is a signaling diagram of an example of the First Aspect.Fig. 4 is a signaling diagram of a variant 1 of the First Aspect.Fig. 5A is a signaling diagram of an example of the Second Aspect.Fig. 5B is a signaling diagram of an example of the Second Aspect.Fig. 6 is a signaling diagram of a variant 1 of the Second Aspect.Fig. 7 is a diagram illustrating a system overview.Fig. 8 is a block diagram illustrating a UE.Fig. 9 is a block diagram illustrating an (R)AN node.Fig. 10 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 11 is a block diagram illustrating an RU.Fig. 12 is a block diagram illustrating a DU.Fig. 13 is a block diagram illustrating a CU.Fig. 14 is a block diagram illustrating an AMF.Fig. 15 is a block diagram illustrating an SMF.Fig. 16 is a block diagram illustrating a UPF.Fig. 17 is a block diagram illustrating a PCF.Fig. 18 is a block diagram illustrating an NEF.Fig. 19 is a block diagram illustrating a UDM.Fig. 20 is a block diagram illustrating an NSSF.Fig. 21 is a block diagram illustrating an AF.

[0048] Abbreviations   For the purposes of the present document, the abbreviations given in TR 21.905 [NPL1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [NPL1]. 4G-GUTI  4G Globally Unique Temporary UE Identity 5GC    5G Core Network 5GLAN    5G Local Area Network 5GS    5G System 5G-AN    5G Access Network 5G-AN PDB  5G Access Network Packet Delay Budget 5G-EIR    5G-Equipment Identity Register 5G-GUTI  5G Globally Unique Temporary Identifier 5G-BRG  5G Broadband Residential Gateway 5G-CRG  5G Cable Residential Gateway 5G GM    5G Grand Master 5G-RG    5G Residential Gateway 5G-S-TMSI  5G S-Temporary Mobile Subscription Identifier 5G VN    5G Virtual Network 5QI    5G QoS Identifier ABBA    Anti-Bidding-down Between Architectures AF    Application Function AMF    Access and Mobility Management Function API    Application Programming Interface AS    Access Stratum ATSSS    Access Traffic Steering, Switching, Splitting ATSSS-LL  ATSSS Low-Layer AUSF    Authentication Server Function AUTN    Authentication token BBF    Broadband Forum BMCA    Best Master Clock Algorithm BSF    Binding Support Function CAG    Closed Access Group CAPIF    Common API Framework for 3GPP northbound APIs CHF    Charging Function CN PDB  Core Network Packet Delay Budget CP    Control Plane CU    Centralized Unit DAPS    Dual Active Protocol Stacks DL    Downlink DN    Data Network DNAI    DN Access Identifier DNN    Data Network Name DRX    Discontinuous Reception DS-TT    Device-side TSN translator DU    Distributed Unit ePDG    evolved Packet Data Gateway EAP    Extensible Authentication Protocol EAS    Edge Application Server EBI    EPS Bearer Identity EES    Edge Enabler Server EHE    Edge Hosting Environment EPS    Evolved Packet System EUI    Extended Unique Identifier FAR    Forwarding Action Rule FN-BRG  Fixed Network Broadband RG FN-CRG  Fixed Network Cable RG FN-RG    Fixed Network RG FQDN    Fully Qualified Domain Name GFBR    Guaranteed Flow Bit Rate GMLC    Gateway Mobile Location Centre GPSI    Generic Public Subscription Identifier GUAMI    Globally Unique AMF Identifier GUTI    Globally Unique Temporary UE Identity HR    Home Routed (roaming) IAB    Integrated access and backhaul IMEI    International Mobile Equipment Identity IMEI / TAC  IMEI Type Allocation Code IMS    IP Multimedia Subsystem IOWN    Innovative Optical and Wireless Network IPUPS    Inter PLMN UP Security I-SMF    Intermediate SMF I-UPF    Intermediate UPF LADN    Local Area Data Network LBO    Local Break Out (roaming) LMF    Location Management Function LoA    Level of Automation LPP    LTE Positioning Protocol LRF    Location Retrieval Function LTE    Long Term Evolution MAC    Medium Access Control MCC    Mobile country code MCX    Mission Critical Service MDBV    Maximum Data Burst Volume MFBR    Maximum Flow Bit Rate MICO    Mobile Initiated Connection Only MNC    Mobile Network Code MO    Mobile Originated MPS    Multimedia Priority Service MPTCP    Multi-Path TCP Protocol MT    Mobile Terminated MT    Mobile Termination N3IWF    Non-3GPP InterWorking Function N5CW    Non-5G-Capable over WLAN NAI    Network Access Identifier NAS    Non-Access Stratum NEF    Network Exposure Function NF    Network Function NGAP    Next Generation Application Protocol ngKSI    Next Generation Key Set Identifier NID    Network identifier NPN    Non-Public Network NR    New Radio NRF    Network Repository Function NSI ID    Network Slice Instance Identifier NSSAA    Network Slice-Specific Authentication and Authorization NSSAAF  Network Slice-Specific Authentication and Authorization Function NSSAI    Network Slice Selection Assistance Information NSSF    Network Slice Selection Function NSSP    Network Slice Selection Policy NW-TT    Network-side TSN translator NWDAF  Network Data Analytics Function O-RAN    Open RAN Alliance O-DU    O-RAN Distributed Unit O-CU    O-RAN Centralized Unit O-RU    O-RAN Radio Unit PCF    Policy Control Function PDB    Packet Delay Budget PDCP    Packet Data Convergence Protocol PDR    Packet Detection Rule PDU    Protocol Data Unit PEI    Permanent Equipment Identifier PER    Packet Error Rate PFD    Packet Flow Description PLMN    Public Land Mobile Network PNI-NPN  Public Network Integrated Non-Public Network PPD    Paging Policy Differentiation PPF    Paging Proceed Flag PPI    Paging Policy Indicator PSA    PDU Session Anchor PTP    Precision Time Protocol QFI    QoS Flow Identifier QoE    Quality of Experience QoS    Quality of Service RACS    Radio Capabilities Signalling optimisation (R)AN    (Radio) Access Network RG    Residential Gateway RU    Radio Unit RIM    Remote Interference Management RLC    Radio Link Control RQA    Reflective QoS Attribute RQI    Reflective QoS Indication RRC    Radio Resource Control RSN    Redundancy Sequence Number SA NR    Standalone New Radio SBA    Service Based Architecture SBI    Service Based Interface SCP    Service Communication Proxy SD    Slice Differentiator SDAP    Service Data Adaptation Protocol SEAF    Security Anchor Functionality SEPP    Security Edge Protection Proxy SMF    Session Management Function SMS    Short Message Service SMSF    Short Message Service Function SN    Sequence Number SN name  Serving Network Name. SNPN    Stand-alone Non-Public Network S-NSSAI  Single Network Slice Selection Assistance Information SOR    Steering Of Roaming SSC    Session and Service Continuity SSCMSP  Session and Service Continuity Mode Selection Policy SST    Slice / Service Type SUCI    Subscription Concealed Identifier SUPI    Subscription Permanent Identifier SV    Software Version TAI    Tracking Area Identity TCP    Transmission Control Protocol TNAN    Trusted Non-3GPP Access Network TNAP    Trusted Non-3GPP Access Point TNGF    Trusted Non-3GPP Gateway Function TNL    Transport Network Layer TNLA    Transport Network Layer Association TSC    Time Sensitive Communication TSCAI    TSC Assistance Information TSN    Time Sensitive Networking TSN GM  TSN Grand Master TSP    Traffic Steering Policy TT    TSN Translator TWIF    Trusted WLAN Interworking Function UCMF    UE radio Capability Management Function UDM    Unified Data Management UDR    Unified Data Repository UDSF    Unstructured Data Storage Function UE    User Equipment UL    Uplink UL CL    Uplink Classifier UP    User Plane UPF    User Plane Function URLLC    Ultra Reliable Low Latency Communication URRP-AMF  UE Reachability Request Parameter for AMF URSP    UE Route Selection Policy UU    Interface between User Equipment and Radio Access Network VID    VLAN Identifier VLAN    Virtual Local Area Network W-5GAN  Wireline 5G Access Network W-5GBAN  Wireline BBF Access Network W-5GCAN  Wireline 5G Cable Access Network W-AGF    Wireline Access Gateway Function WLAN    Wireless Local Area Network WUS    Wake Up Signal

[0049] Definitions   For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [NPL1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [NPL1].

[0050] General Quoting TS 23.558 [NPL10], -  AF is an Application Function -  AF_EAS is a type of an AF and the application server resident in an Edge Hosting Environment (EHE) of a local part of DN, performing the server functions. -  AF_EES is another type of an AF and has functionalities, for example, enabling exchange of application data traffic with the EAS; providing API invoker and API exposing functions; interacting with 3GPP Core Network (e.g., NEF); supporting external exposure of 3GPP network and service capabilities to the EAS(s) The section for system overview describes NEF, UDM, PCF and SMF.

[0051] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0052] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0053] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.

[0054] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0055] In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0056] As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.

[0057] Each of Aspects and elements included in the each Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.

[0058] Any lists described in following aspects include at least one parameter or multiple parameters.

[0059] An example object of this disclosure is to provide a method and apparatus that can solve the above problem.

[0060] A method of a first communication apparatus according to example aspect of this disclosure includes communicating with a second communication apparatus. The method includes sending an Internet Protocol (IP) address and a prefix. The IP address and the prefix are used persistently.

[0061] A method of a first communication apparatus according to example aspect of this disclosure includes receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus. The method includes using the IP address and the prefix persistently.

[0062] A method of a first communication apparatus according to example aspect of this disclosure includes communicating with a second communication apparatus. The method includes sending an identifier and a prefix. The identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently. The prefix is used persistently.

[0063] A method of a first communication apparatus according to example aspect of this disclosure includes receiving an identifier and a prefix. The identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently. The method includes assigning the IP address to the UE and using the prefix persistently.

[0064] A first communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a second communication apparatus. The at least one hardware processor is configured to send an Internet Protocol (IP) address and a prefix. The IP address and the prefix are used persistently.

[0065] A first communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive an Internet Protocol (IP) address and a prefix from a second communication apparatus. The IP address and the prefix are used persistently. The at least one hardware processor is configured to use the IP address and the prefix persistently.

[0066] A first communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a second communication apparatus. The at least one hardware processor is configured to send an identifier and a prefix. The identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently. The prefix is used persistently.

[0067] A first communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive an identifier and a prefix. The identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently. The prefix is used persistently. The at least one hardware processor is configured to assign the IP address to the UE and using the prefix persistently.

[0068] A method of an edge node according to example aspect of this disclosure includes sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event. The method includes, in a case where one of the at least one event occurs, receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node. The method includes, in a case where one of the at least one event occurs, sending, to the first core network node, third message including information on SessionPersistency. The information on SessionPersistency includes information on Persistent UE IP address, and information on Persistent prefix. The information on Persistent UE IP address is not changed (in other words, it is persistent or it is determined) in a case where the at least one event occurred. The Persistent prefix is not changed (in other words, it is persistent or it is determined) in a case where the at least one event occurred.

[0069] A method of a first core network node according to example aspect of this disclosure includes receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix. The method includes performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0070] A method of a first edge node according to example aspect of this disclosure includes sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event. The method includes, in a case where one of the at least one event occurs, receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF. The method includes, in a case where one of the at least one event occurs, sending, to the second edge node, a third message including information on SessionPersistency. The information on SessionPersistency includes information on Persistent UE IP address, and information on Persistent prefix. The information on Persistent UE IP address is not changed (in other words, it is persistent or it is determined) in a case where the event occurred. The Persistent prefix is not changed (in other words, it is persistent or it is determined) in a case where the IP addresses are replaced with different IP addresses.

[0071] A method of a first core network node according to example aspect of this disclosure includes receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently. The method includes performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0072] An edge node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event. The at least one hardware processor is configured to receive, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node in a case where one of the at least one event occurs. The at least one hardware processor is configured to send, to the first core network node, third message including information on SessionPersistency in a case where one of the at least one event occurs. The information on SessionPersistency includes information on Persistent UE IP address, and information on Persistent prefix. The information on Persistent UE IP address is not changed (in other words, it is persistent or it is determined ) in a case where the at least one event occurred. The Persistent prefix is not changed (in other words, it is persistent or it is determined ) in a case where the at least one event occurred.

[0073] A first core network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix. The at least one hardware processor is configured to performe, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0074] A first edge node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event. The at least one hardware processor is configured to receive, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF in a case where one of the at least one event occurs. The at least one hardware processor is configured to send, to the second edge node, a third message including information on SessionPersistency in a case where one of the at least one event occurs. The information on SessionPersistency includes information on Persistent UE IP address, and information on Persistent prefix. The information on Persistent UE IP address is not changed (in other words, it is persistent or it is determined) in a case where the event occurred. The Persistent prefix is not changed (in other words, it is persistent or it is determined) in a case where the IP addresses are replaced with different IP addresses.

[0075] A method of a first core network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently. The at least one hardware processor is configured to perform, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0076] First aspect (Solution 1)   This solution comprises processes that an Application Function_ Edge Enabler Server (AF_EES) requests to preserve the IP address and prefix assigned to a UE at PDU establishment.

[0077] The prefix, also denoted as prefix value, may be a shortened form of a subnet mask (a subnet mask value).   The subnet mask may be an information indicating that which part of an IP address is a host part and a network part.

[0078] In this solution, SessionPersistency is a newly introduced feature that is an information element or a data object that includes any of the following properties. - - Target UE Identifier indicates an identifier that uniquely identifies a UE or a collection of UEs. The property for Target UE Identifier can be a list of items for each Target UE Identifier. Target UE Identifier(s) can, for example, substituted by e.g., any of Generic Public Subscription Identifier (GPSI), or External Group ID. - GPSI indicates a public identifier for addressing a 3GPP subscription in different data networks outside of the 3GPP system. - External Group ID is an identifier for a 5G Virtual Network (5G VN) group corresponds to a unique set of 5G VN group data parameters. - A Persistent UE IP address indicates an IP address(s) assigned by the SMF to the UE. The persistent UE IP address may not be changed (in other words, it may be persistent or it may be determined ) if an event occurred like the IP address(es) of the UE(s) are replaced with different IP addresses (for example, PDU sessions between the UE(s) and the 5GS are re-established). A property for the Persistent UE IP address can be a list of items for each Persistent UE IP address. - A Persistent prefix is a network address specified by an AF_EAS, AF_EES or SMF. The Persistent prefix may not be changed (in other words, it may be persistent or it may be determined ) if an event occurred like the IP address(es) of the UE(s) are replaced with different IP addresses (for example, PDU sessions between the UE(s) and the 5GS are re-established). A property for the Persistent prefix can be a list of items for the Persistent prefix. That is, the SessionPersistency can include at least one of the Target UE Identifier, the Persistent UE IP address and / or the Persistent prefix.

[0079] The detailed processes of the first aspect are described below with reference to Figs. 3A and 3B.

[0080] Step1-1   Quoting TS 23.501 [NPL2], Nnef_EventExposure service provides support for event exposure.

[0081] Quoting TS 23.502 [NPL3], Nnef_EventExposure_Subscribe operation in Nnef_EventExposure service is an operation that the consumer subscribes to receive an event, or if the event is already defined in NEF, then the subscription can be updated.

[0082] In step1-1, the publisher is the NEF and the subscriber is the AF_EES.

[0083] The AF EES subscribes to Nnef_EventExposure service with a collection of following parameters.

[0084] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0085] Quoting TS 23.501 [NPL2], an Event ID identifies the type of event being subscribed to (e.g., PDU Session Release, UE mobility out of an Area of Interest, etc.).

[0086] In this step1-1, the Event ID indicates an identifier that is mapped onto "PDU Session Status".   For example, it is expected that the NEF notifies the AF_EES when PDU session(s) for the targeted UE is established.

[0087] The Target UE Identifier(s) indicates identifier(s) uniquely identifying a UE or a collection of UEs.

[0088] The Target UE Identifier(s) in this step1-1 may be substituted by e.g. any of GPSI, or External Group ID.

[0089] A Notification endpoint is mapped to a point to receive a notification. The Notification endpoint may indicate a point to receive a notification in this disclosure.

[0090] The Notification endpoint can be mapped onto an identifier represented by e.g. a Uniform Resource Identifier (URI) to have the notification on the AF_EES.

[0091] For example, the AF_EES may transmit at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the NEF.   For example, the AF_EES may transmit the Nnef_EventExposure_Subscribe including at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the NEF.

[0092] Step1-2:   This is a response to the subscription described in the step1-1.   For example, the NEF may transmit the response to the AF_EES in a case where the NEF receives at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint from the AF_EES.   For example, the NEF may transmit the response to the AF_EES in a case where the NEF receives the Nnef_EventExposure_Subscribe from the AF_EES.

[0093] Step1-3:   Quoting TS 23.501 [NPL2], Nudm_EventExposure service allows the NF consumer to subscribe to receive an event and provides a monitoring indication of the event to the subscribed NF consumer.

[0094] Quoting TS 23.502 [NPL3], Nudm_EventExposure_Subscribe service operation in Nudm_EventExposure service is an operation that the NF consumer may subscribe to in order to receive an event.

[0095] In this step1-3, the publisher is the UDM and the subscriber is the NEF described in the step1-1.

[0096] The NEF subscribes to Nudm_EventExposure service with a collection of following parameters.

[0097] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0098] An Event ID may be substituted by the Event ID described in the step1-1.

[0099] The Target UE Identifier(s) in this step1-3 may be substituted by the Target UE Identifier(s) described in the step1-1.

[0100] A Notification endpoint is mapped to a point to receive a notification.

[0101] The notification endpoint can be mapped onto an identifier represented by e.g. a Uniform Resource Identifier (URI) to have the notification on the NEF.

[0102] For example, the NEF may transmit at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the UDM.   For example, the NEF may transmit the Nudm_EventExposure_Subscribe including at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the UDM.   The Event ID, and the Target UE Identifier(s) in the step 1-3 may be same ones in the step 1-1.   For example, the NEF may transmit the Nudm_EventExposure_Subscribe or at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the UDM in a case where the NEF transmits the response to the AF_EES in step 1-2.

[0103] Step1-4:   This is a response to the subscription described in the step1-3.   For example, the UDM may transmit the response to the NEF in a case where the UDM receives at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint from the NEF.   For example, the UDM may transmit the response to the NEF in a case where the UDM receives the Nudm_EventExposure_Subscribe from the NEF.

[0104] Step1-5:   Quoting TS 23.501 [NPL2], Nsmf_EventExposure service exposes the events happening on the PDU Sessions to the consumer NFs.

[0105] Quoting TS 23.502 [NPL3], Nsmf_EventExposure_Subscribe service operation in Nsmf_EventExposure service is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE.

[0106] In this step1-5, the publisher is the SMF and the subscriber is the UDM described in the step1-3.

[0107] The UDM subscribes to Nsmf_EventExposure service with a collection of following parameters.

[0108] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0109] An Event ID may be substituted by the Event ID described in the step1-3.

[0110] The Target UE Identifier(s) in this step1-5 may be substituted by the Target UE Identifier(s) described in the step1-3.

[0111] A Notification endpoint is mapped to a point to receive a notification.

[0112] The Notification endpoint can be mapped onto the notification endpoint that is described in the step1-3.

[0113] For example, the UDM may transmit at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the SMF.   For example, the UDM may transmit the Nsmf_EventExposure_Subscribe including at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the SMF. The Event ID, the Target UE Identifier(s) and the Notification endpoint in the step 1-5 may be same ones in the step 1-3.   For example, the UDM may transmit the Nsmf_EventExposure_Subscribe or at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the SMF in a case where the UDM transmits the response to the NEF in step 1-4.

[0114] Step1-6:   This is a response to the subscription described in the step1-5.   For example, the SMF may transmit the response to the UDM in a case where the SMF receives at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint from the UDM.   For example, the SMF may transmit the response to the UDM in a case where the SMF receives the Nsmf_EventExposure_Subscribe from the UDM.

[0115] Step1-7:   Quoting TS 23.502 [NPL3], Nsmf_EventExposure_Notify service operation reports notifications to the notification endpoint.

[0116] In this step1-7, the NF to be notified is the NEF described in the step1-5.

[0117] If there is an event that is relevant to PDU Sessions for the targeted UEs, the SMF notifies to the notification endpoint of the NEF described in the step1-5 with a collection of following parameters.

[0118] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0119] A notification describes the PDU Session Establishment of the UE identified by the Target UE Identifier(s) described in the step1-5. For example, the notification may indicate that the PDU session for the UE identified by the Target UE Identifier(s) described in the step1-5 is established.

[0120] The UE's IP address (the UE's IP address may be referred as UE IP address) is mapped onto the IP address assigned by the SMF to the UE. For example, the UE's IP address may be the IP address assigned by the SMF to the UE. For example, the UE's IP address may be the IP address assigned by the SMF to the UE identified by the Target UE Identifier(s) described in the step1-5.

[0121] A prefix (the prefix may be referred as Prefix allocation) is mapped to the network address of the IP address assigned by the SMF to the UE. For example, the prefix may be the network address of the IP address assigned by the SMF to the UE. For example, the prefix may be the network address of the IP address assigned by the SMF to the UE identified by the Target UE Identifier(s) described in the step1-5.

[0122] For example, in a case where the PDU session for the UE identified by the Target UE Identifier(s) described in the step1-5 is established, the SMF may transmit at least one of the UE's IP address and the prefix.

[0123] For example, in a case where the PDU session for the UE identified by the Target UE Identifier(s) described in the step1-5 is established, the SMF may transmit Nsmf_EventExposure_Notify including at least one of the UE's IP address and the prefix.

[0124] For example, in a case where the Event ID indicates an identifier that is mapped onto "PDU Session Status" (or in a case where the Event ID indicates "PDU Session Status") and the Target UE identifier(s) indicates UE 1, the SMF may monitor whether the PDU session for the UE 1 is established.   In a case where the SMF detects that the PDU session for the UE 1 is established, the SMF may transmit, to the NEF which is indicated by the Notification endpoint (e.g., the Notification endpoint may indicate the NEF), at least one of the notification (e.g., the notification may indicate that the PDU session for the UE 1 is established), the UE's IP address (e.g., the UE's IP address may indicate that the UE 1's IP address assigned by the SMF) and the prefix (e.g., the prefix may indicate the network address of the IP address assigned by the SMF to the UE 1).   In a case where the SMF detects that the PDU session is established, the SMF may transmit Nsmf_EventExposure_Notify including at least one of the notification, the UE's IP address and the prefix to the NEF. The notification may indicate that the PDU session is established.

[0125] For example, the SMF may detect that the PDU session is established in a case where the SMF perform process(es) in the PDU session establishment procedure specified in TS 23.502 [NPL3] and the PDU session is established.

[0126] Step1-8:   Quoting TS 23.502 [NPL3], Nnef_EventExposure_Notify service operation reports notifications to the notification endpoint.

[0127] The NEF notifies to the Notification endpoint of the AF_EES described in the step1-1 with a collection of following parameters.

[0128] The parameters are not an exhaustive list and only certain parameters focused on in this application.

[0129] A notification describes the PDU Session Establishment of the UE identified by the Target UE Identifier(s) described in the step1-7.

[0130] The UE's IP address is mapped onto the IP address assigned by the SMF to the UE described in the step1-7.

[0131] The prefix is mapped to the network address of the IP address assigned by the SMF to the UE described in the step1-7.

[0132] For example, the NEF may transmit at least one of the notification, the UE's IP address and the prefix to the AF_EES.   For example, the NEF may transmit the Nnef_EventExposure_Notify including at least one of the notification, the UE's IP address and the prefix to the AF_EES.   The notification, the UE's IP address and the prefix in the step 1-8 may be same ones in the step 1-7.

[0133] The AF_EES may apply a configuration for a session persistency into the load balancer.

[0134] For example, if key-value representation is used, the value of the IP address and / or the prefix described in the step1-7 can be used for source address-based session persistency.   For example, in a case where the AF_EES receives at least one of the notification, the UE's IP address and the prefix from the NEF, the AF_EES may apply at least one of the UE's IP address and the prefix into the load balancer, for configuring the session persistency.   For example, in a case where the AF_EES receives at least one of the notification, the UE's IP address and the prefix from the NEF, the AF_EES may apply at least one of the UE's IP address and the prefix into the load balancer, for configuring the session persistency for the UE indicated by the Target UE Identifier(s).

[0135] Step1-9:   Quoting TS 23.502 [NPL3], Nnef_TrafficInfluence_Create operation authorizes requests and forwards the requests for traffic influence.

[0136] In this step1-9, the AF_EES creates Nnef_TrafficInfluence with parameters in a SessionPersistency information element (IE).

[0137] The SessionPersistency IE includes Persistent UE IP address and a Persistent prefix.

[0138] The Persistent UE IP address is an IP address applied into the load balancer in step1-8. For example, in a case where the above-mentioned UE 1's IP address is applied into the load balancer by the AF_EES in step 1-8, the Persistent UE IP address may be the UE 1's IP address.

[0139] The Persistent prefix is a prefix applied into the load balancer in the step1-8. For example, in a case where the prefix is the network address of the above-mentioned UE 1's IP address and this prefix is applied into the load balancer by the AF_EES in step 1-8, the Persistent prefix may be this prefix applied into the load balancer.   For example, the AF_EES may transmit the Persistent UE IP address and the Persistent prefix to the NEF.   For example, the AF_EES may transmit the SessionPersistency IE including the Persistent UE IP address and the Persistent prefix to the NEF.   For example, the AF_EES may create the Persistent UE IP address and the Persistent prefix based on the UE IP address and the prefix applied to the load balancer, and transmit the Persistent UE IP address and the Persistent prefix to the NEF.   For example, the AF_EES may create the Persistent UE IP address and the Persistent prefix based on the UE IP address and the prefix applied to the load balancer, and transmit the SessionPersistency IE including the Persistent UE IP address and the Persistent prefix to the NEF.   For example, the AF_EES may transmit Nnef_TrafficInfluence_Create including the SessionPersistency IE to the NEF.

[0140] Further transactions for Traffic Influence by NEF, UDM, PCF, SMF are not described because the transactions follow the steps for TrafficInfluence service operations among NEF, UDM, PCF and SMF in TS 23.502 [NPL3].

[0141] The AF_EES can send, to the NEF, the Session Persistency including Persistent UE IP address and Persistent prefix.

[0142] For example, based on the TrafficInfluence service operations, the SMF may receive the SessionPersistency IE.     For example, based on the TrafficInfluence service operations, the NEF may send the SessionPersistency IE to the SMF directly or via other network nodes (including e.g., at least one of UDM, PCF etc.).

[0143] Step1-10:   The SMF updates the UE address management configurations (e.g. DHCP) with the SessionPersistency IE described in the step1-9 to make the IP address and prefix assignment for the UE persistent. For example, the SMF can update the UE address management configurations (e.g. DHCP) with the SessionPersistency IE to make the IP address and prefix assignment for the UE persistent if the SMF receives the SessionPersistency IE from one of the NEF, the UDM or the PCF.   For example, the SMF may assign, to the UE, the IP address indicated by the Persistent UE IP address, and use the prefix for the UE.   For example, in a case where a PDU session for the UE 1 is established after the SMF receives the SessionPersistency IE, the SMF may assign, to the UE 1, the IP address indicated by the Persistent UE IP address persistently, and use the prefix for the UE 1 persistently. For example, the Persistent UE IP address may be an IP address used persistently. For example, the Persistent prefix may be a prefix used persistently. For example, the Persistent UE IP address may be an IP address used by the SMF persistently. For example, the Persistent prefix may be a prefix used by the SMF persistently.

[0144] Variant 1 of the solution 1   The detailed processes of the Variant 1 of the solution 1 are described below with reference to Fig. 4.

[0145] The AF_EAS may execute step1-1 in the solution1.

[0146] Step1-1-1:   EventExposure_Subscribe operation allows a consumer subscribe (e.g., AF_EAS) subscribes for events in order to receive notifications from a producer (e.g., AF_EES) if a described event in the subscription request is met, or if the event is already defined in AF_EES, then the subscription can beupdated.

[0147] The EventExposure service in this step1-1-1 publishes notifications related to PDU Sessions towards the subscriber.

[0148] In this step 1-1-1, the publisher is the AF_EES and the subscriber is the AF_EAS.

[0149] AF_EAS subscribes to the EventExposure service in the AF_EES with a collection of parameters.

[0150] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0151] Quoting TS 23.501 [NPL2], an Event ID identifies the type of event being subscribed to (e.g. PDU Session Release, UE mobility out of an Area of Interest, etc.).

[0152] In this step1--1-1, the Event ID indicates an identifier that is mapped onto "PDU Session Status".   For example, it is expected that the NEF notifies the AF_EES when PDU session(s) for the targeted UE is established.

[0153] The Target UE Identifier(s) indicates identifier(s) uniquely identifying a UE or a collection of UEs.

[0154] The Target UE Identifier(s) in this step1-1-1 may be substituted by e.g. any of GPSI, or External Group ID.

[0155] A Notification endpoint is mapped to a point to receive a notification.

[0156] The notification endpoint can be mapped onto an identifier represented by e.g. a Uniform Resource Identifier (URI) to have the notification on the AF_EAS.

[0157] For example, the AF_EAS may transmit at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the AF_EES.   For example, the AF_EAS may transmit the EventExposure_Subscribe including at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint to the AF_EES.     Definition of the Event ID, the Target UE Identifier(s) and the Notification endpoint of the solution 1 may be applied to the Event ID, the Target UE Identifier(s) and the Notification endpoint in Variant 1 of the solution 1.     For example, the AF_EAS may have at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint in advance. For example, the AF_EAS may receive at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint from other network node(s). For example, the AF_EAS may create at least one of the Event ID, the Target UE Identifier(s) and the Notification endpoint based on local configuration in the AF_EAS or operator's policy.

[0158] Step1-1-2:   Based on the received parameters described in the step1-1-1, the AF_EES executes the steps described in the solution1.

[0159] If a PDU session for a targeted UE is established, then the event (e.g., the notification indicating that the PDU session for a targeted UE is established) is notified to the AF_EES.

[0160] So, the AF_EES notifies the event to the endpoint described in the step1-1-1. For example, in a case where the endpoint indicates the AF_EAS, the AF_EES may notify the event to the AF_EAS.   For example, in a case where the endpoint indicates the AF_EAS, the AF_EES may transmit the notification, the UE's IP address and the prefix to the AF_EAS. Definition of the notification, the UE's IP address and the prefix of the solution 1 may be applied to the notification, the UE's IP address and the prefix in Variant 1 of the solution 1.

[0161] Having the notification, the AF_EAS applies a configuration for a session persistency into the load balancer. For example, the AF_EAS may apply the configuration for a session persistency into the load balancer in the same manner as the AF_EES in the solution 1.

[0162] For example, the IP address or prefix described in the step1-1-2 can be used for source address-based session persistency.

[0163] Step1-1-3:   Quoting TS 23.558 [NPL10], EES_TrafficInfluence service exposes services to authorize Traffic Influence information.

[0164] TrafficInfluence_Create operation authorizes requests and forwards the request for traffic influence.

[0165] The AF_EAS creates EAS_TrafficInfluence with the following parameters in a SessionPersistency IE.

[0166] The parameters are not an exhaustive list and only certain parameters are focused on in this application.

[0167] The SessionPersistency IE includes a Persistent UE IP address and a Persistent prefix.

[0168] The Persistent UE IP address is an IP address applied into the load balancer in step1-1-2.

[0169] The Persistent prefix is a prefix applied into the load balancer in the step1-1-2.

[0170] For example, the AF_EAS may create the Persistent UE IP address and the Persistent prefix, and transmit the SessionPersistency IE including the Persistent UE IP address and the Persistent prefix to the AF_EES in the same manner as the AF_EES in the solution 1. For example, the AF_EAS may transmit EAS_TrafficInfluence including the SessionPersistency IE.

[0171] Further transactions for Traffic Influence by NEF, UDM, PCF, SMF are not described because the transactions follow the steps for TrafficInfluence service operations among NEF, UDM, PCF and SMF in TS 23.502 [NPL3].

[0172] For example, the AF_EES may transmit the SessionPersistency IE to the NEF. For example, based on the TrafficInfluence service operations, the SMF may receive the SessionPersistency IE.     For example, based on the TrafficInfluence service operations, the NEF may send the SessionPersistency IE to the SMF directly or via other network nodes (including e.g., at least one of UDM, PCF etc.).

[0173] The AF_EAS can send, to the AF_EES, the Session Persistency including UE Identifier(s) and Persistent prefix.

[0174] Step1-1-4:   The SMF updates the UE address management configurations (e.g. DHCP) with the SessionPersistency IE described in the step1-1-3 to make the IP address and prefix assignment for the UE persistent. For example, the SMF may update the UE address management configurations in the same manner as the SMF in the solution 1

[0175] For example, the SMF can update the UE address management configurations (e.g. DHCP) with the SessionPersistency IE to make the IP address and prefix assignment for the UE persistent if the SMF receives the SessionPersistency IE from one of the NEF, the UDM or the PCF.

[0176] According to solution 1 and the variant of the solution 1, they have for example an advantage by using SessionPersistency which is that the traffic can be routed from a collection of UE(s) in a 5GS to the same AF_EAS in an Edge Hosting Environment (EHE) in a local part of DN.

[0177] For example, the solution 1 and the variant of the solution 1 include a case where SMF in the 5GS specifies and assigns IP addresses and prefixes for a group of UEs. According to the solution 1 and the variant of the solution 1, even if SMF may assign IP addresses with different prefix or the same prefix at PDU establishment and update the IP addresses and prefix for UE(s), the changes can be notified to AF_EAS or AF_EES in an Edge Hosting Environment (EHE) in a local part of DN. Following the notification, the AF_EAS or AF_EES in an Edge Hosting Environment (EHE) in a local part of DN can apply the properties of SessionPersistency into the load balancer so that the traffic can be routed from a collection of UE(s) in a 5GS to the same AF_EAS. In addition, the AF_EAS or AF_EES can request SMF to preserve the assigned IP address and prefix for UE. Therefore, the traffic can persistently be routed from a collection of UE(s) in a 5GS to the same AF_EAS n an Edge Hosting Environment (EHE) in a local part of DN. Hence, the solution 1 and the variant of the solution 1 can solve the above-mentioned problem.

[0178] Second aspect (Solution 2)   This solution comprises process for session persistency instructed by the AF_EES.

[0179] It is assumed that a group subscription data with an external group identifier for a collection of UEs is created (or generated) by the operator.

[0180] The detailed processes of the second aspect are described below with reference to Figs. 5A and 5B.

[0181] In this aspect, it is assumed that a group subscription data with an external group identifier for a collection of UEs by created in the operator.

[0182] Step2-1:   Quoting TS 23.501 [NPL2], Nudm_SDM service allows NF consumers to retrieve user subscription data when necessary and provides updated user subscriber data to the subscribed NF consumers.

[0183] Quoting TS 23.502 [NPL3], Nudm_SDM service_Subscribe service operation is that the NF consumer subscribes for updates to Subscription Data indicated by the 'subscription data type' input.

[0184] The publisher in this step2-1 is the UDM and the subscriber in this step2-1 is the SMF.

[0185] The SMF subscribes to the Nudm_SDM service with Nudm_SDM_Subscribe operation so that 5G VN group data for a collection of UE is notified.

[0186] For example, the SMF may transmit the external group identifier for the collection of UEs to the UDM.   For example, the SMF may transmit Nudm_SDM_Subscribe including the external group identifier for the collection of UEs to the UDM.

[0187] Step2-2:   This is a response to Nudm_SDM service_Subscribe described in the step2-1.   For example, the UDM may transmit the response to the SMF in a case where the UDM receives the external group identifier from the SMF.   For example, the UDM may transmit the response to the SMF in a case where the UDM receives the Nudm_SDM_Subscribe from the SMF.

[0188] Step2-3   Quoting TS 23.501 [NPL2], Nnef_ParameterProvision service supports the provision of information which can be used for the UE in the 5GS.

[0189] Quoting TS 23.502 [NPL3], Nnef_ParameterProvision_Create service operation is that the consumer creates a 5G VN group, or Multicast MBS related information group.

[0190] The producer in this step2-3 is the NEF and the consumer in this step2-3 is the AF_EES. The AF_EES creates a 5G VN group data with Nnef_ParameterProvision_Create operation with the following 5G VN group data.

[0191] The parameters in the 5G VN group data are not an exhaustive list and only certain parameters are focused on in this application. The parameters in the 5G VN group data include at least one of an external group identifier, the SessionPersistency IE, the Target UE Identifier(s), and the persistent prefix.

[0192] An external group identifier may be substituted by the external group identifier described earlier. For example, the external group identifier in the step 2-3 may be the external group identifier described earlier.

[0193] The SessionPersistency IE includes a Target UE Identifier(s) and a Persistent prefix.

[0194] The Target UE Identifier(s) indicates identifier(s) described with reference to step1-1 of the first aspect. For example, the AF_EES may have the Target UE Identifier(s) in advance. For example, the AF_EES may receive the Target UE Identifier(s) from other network node(s). For example, the AF_EES may create or update the Target UE Identifier(s) based on local configuration in the AF_EES or operator's policy.

[0195] The Persistent prefix is a network address used when the SMF assigns an IP address to a UE identified by the Target UE Identifier(s). For example, the AF_EES may have the Persistent prefix in advance. For example, the AF_EES may receive the Persistent prefix from other network node(s). For example, the AF_EES may create or update the Persistent prefix based on local configuration in the AF_EES or operator's policy.

[0196] The Persistent prefix is mapped to the network address of the IP address assigned by the SMF to the UE described in the step1-7 of the first aspect.

[0197] For example, the AF_EES may transmit at least one of the external group identifier, the Target UE Identifier(s) and the Persistent prefix to the NEF.

[0198] For example, the AF_EES may transmit, to the NEF, the 5G VN group data including the external group identifier and the SessionPersistency IE including the Target UE Identifier(s) and the Persistent prefix.   For example, the AF_EES may transmit Nnef_ParameterProvision_Create including at least one of the external group identifier, the Target UE Identifier(s) and the Persistent prefix to the NEF.

[0199] For example, the AF EES may perform the process in step 2-3 in a case where the 5G VN group data is created or updated.   For example, the AF EES may perform the process in step 2-3 in a case where the 5G VN group data (e.g., at least one of the Target UE Identifier(s) and the Persistent prefix) is received.   For example, the AF EES may perform the process in step 2-3 based on local configuration in the AF_EES or operator's policy.

[0200] For example, the 5G VN group data may include at least one of the external group identifier and the SessionPersistency IE.   For example, the SessionPersistency IE may include the Target UE Identifier(s) and the Persistent prefix.

[0201] Step2-4:   Quoting TS 23.501 [NPL2], Nudm_ParameterProvision service supports the provision of information which can be used for the UE in the 5GS.

[0202] Quoting TS 23.502 [NPL3], Nudm_ParameterProvision_Create service operation is that the consumer creates a Network Configuration with one or more parameters, a 5G VN group related information (e.g. 5G VN group data, 5G VN membership management), or Multicast MBS related information.

[0203] The producer in this step2-4 is the UDM and the consumer in this step2-4 is the NEF.

[0204] The NEF creates a 5G VN group data with Nudm_PrarameterProvision_Create operation with the following 5G VN group data.

[0205] The parameters in the 5G VN group data are not an exhaustive list and only certain parameters are focused on in this application.

[0206] The 5G VN group data is substituted by the 5G VN group data created at the step2-3.

[0207] The 5G VN group data may include at least the SessionPersistency IE.   For example, the NEF may transmit, to the UDM, the received 5G VN group data.   For example, the NEF may transmit, to the UDM, Nudm_PrarameterProvision_Create including the received 5G VN group data.   For example, the NEF may transmit, to the UDM, at least one of the received Target UE Identifier(s) and the received Persistent prefix.     For example, the NEF may transmit, to the UDM, Nudm_PrarameterProvision_Create including at least one of the received Target UE Identifier(s) and the received Persistent prefix.

[0208] Step2-5:   Quoting TS 23.501 [NPL2], Nudr_DM service allows NF consumers to retrieve, create, update, subscribe for change notifications, unsubscribe for change notifications and delete data stored in the UDR, based on the set of data applicable to the consumer.

[0209] Quoting TS 23.502 [NPL3], Nudr_DM_Create service operation is that the NF service consumer intends to insert a new data record into the UDR, e.g. an NF service consumer intends to insert a new application data record into the UDR.

[0210] The producer in this step2-5 is the UDR and the consumer in this step2-5 is the UDM.

[0211] The UDM creates a 5G VN group data with Nudr_DM_Create operation with the following 5G VN group data.

[0212] The parameters in the 5G VN group data, including at least the SessionPersistency IE, are not an exhaustive list and only certain parameters are focused on in this application.

[0213] The 5G VN group data is substituted by the 5G VN group data created at the step2-4.

[0214] For example, the UDM may transmit, to the UDR, the received 5G VN group data.   For example, the UDM may transmit, to the UDR, Nudr_DM_Create including the received 5G VN group data.   For example, the UDM may transmit, to the UDR, at least one of the received Target UE Identifier(s) and the received Persistent prefix.   For example, the UDM may transmit, to the UDR, Nudr_DM_Create including at least one of the received Target UE Identifier(s) and the received Persistent prefix.

[0215] Step2-6:   This is a response to Nudr_DM_Create described in the step2-5.   For example, the UDR may transmit the response to the UDM in a case where the UDR receives the 5G VN group data (e.g., at least one of the Target UE Identifier(s) and the Persistent prefix) from the UDM.   For example, the UDR may transmit the response to the UDM in a case where the UDR receives the Nudr_DM_Create from the UDM.

[0216] Step2-7:   This is a response to Nudm_ParameterProvision_Create described in the step2-4.   For example, the UDM may transmit the response to the NEF in a case where the UDM receives the response to Nudr_DM_Create in the step 2-6.

[0217] Step2-8:   This is a response to Nnef_ParameterProvision_Create described in the step2-3.   For example, the NEF may transmit the response to the AF_EES in a case where the NEF receives the response to Nudm_ParameterProvision_Create in the step 2-7.

[0218] If the response in the step2-8 is a success, then the AF_EES applies a configuration for a session persistency into the load balancer.

[0219] For example, the Target UE Identifier(s) and / or the Persistent prefix described in the step2-3 can be used for source address-based session persistency.

[0220] For example, the AF_EES may apply at least one of the Target UE Identifier and the Persistent prefix into the load balancer.

[0221] Step2-9:   Quoting TS 23.502 [NPL3], Nudm_SDM service_Notify service operation is that the UDM notifies the NF consumer of the updates of Subscription Data.

[0222] As described in the step2-1, the SMF has subscribed to the Nudm_SDM service, the UDM notifies the SMF that indicates a creation of 5G VN group data with Session Persistency (SessionPersistency IE).   For example, the UDM may transmit, to the SMF, the received 5G VN group data.   For example, the UDM may transmit, to the SMF, Nudm_SDM service_Notify or Nudm_SDM_Notification including the received 5G VN group data.   For example, the UDM may transmit, to the SMF, at least one of the received Target UE Identifier(s) and the received Persistent prefix.   For example, the UDM may transmit, to the SMF, Nudm_SDM service_Notify or Nudm_SDM_Notification including at least one of the received Target UE Identifier(s) and the received Persistent prefix.   For example, the UDM may perform the process in the step 2-9 after the step 2-4 (e.g., in a case where the UDM receives at least one of the Target UE Identifier(s) and the Persistent prefix).   For example, the UDM may perform the process in the step 2-9 after the step 2-5 (e.g., in a case where the UDM transmits at least one of the Target UE Identifier(s) and the Persistent prefix).   For example, the UDM may perform the process in the step 2-9 after the step 2-6 (e.g., in a case where the UDM receives the response in the step 2-6).   For example, the UDM may perform the process in the step 2-9 after the step 2-7 (e.g., in a case where the UDM transmits the response in the step 2-7).

[0223] Step2-10:   The SMF updates the UE address management configurations (e.g. DHCP) with the Session Persistency IE described in the step2-9 to make the IP address and prefix assignment for the UE persistent.

[0224] For example, the SMF can update the UE address management configurations (e.g. DHCP) with the SessionPersistency IE to make the IP address and prefix assignment for the UE persistent if the SMF receives the SessionPersistency IE from one of the NEF, the UDM or the PCF.   At a PDU establishment between the SMF and a UE in the group, the Target UE Identifier(s) and persistent prefix are used when the SMF assigns an IP address to the UE in the group.

[0225] The SMF performs a PDU establishment with a UE in the group using the target UE identifier and persistent prefix are used when the SMF assigns an IP address to the UE in the group.   For example, the SMF may assign the same IP address persistently to the UE indicated by the Target UE Identifier(s). For example, the SMF may use the Persistent prefix for the UE indicated by the Target UE Identifier(s). For example, in a case where a PDU session for the UE which is indicated by the Target UE Identifier is established, the SMF may assign, to the UE, the IP address persistently, and use the Persistent prefix for the UE persistently. For example, the Target UE Identifier(s) may be an identifier(s) of a UE(s) which an IP address is assigned persistently. For example, the Persistent prefix may be a prefix used persistently. For example, the Persistent prefix may be a prefix used persistently for a UE(s) indicated by the Target UE Identifier(s). For example, the Persistent prefix may be a prefix used by the SMF persistently.

[0226] Variant 1 of the solution 2   There is another case where the AF_EAS may prepare an information element, SessionPersistency, to describe a targeted collection of UEs and a common prefix in the step2-2, and then execute the step2-3.

[0227] The detailed processes of the Variant 1 of the solution 2 are described as below with reference to Fig. 6.

[0228] The AF_EAS may execute the step1-1 in solution1.

[0229] Step2-1-1:   ParameterProvision_Create operation is that the consumer subscribes to receive an event, or if the event is already defined in AF_EES, then the subscription is updated.

[0230] The AF_EAS creates a 5G VN group data with ParameterProvision_Create operation with the following 5G VN group data.

[0231] The parameters in the 5G VN group data are not an exhaustive list only certain parameters are focused on in this application.   The parameters in the 5G VN group data include at least one of an external group identifier, Session Persistency, UE Identifier(s), and Persistent prefix.

[0232] An external group identifier may be substituted by the external group identifier described earlier.

[0233] The SessionPersistency may include the Target UE Identifier(s) and the Persistent prefix.

[0234] The SessionPersistency (the SessionPersistency IE) may be substituted by the SessionPersistency created at step1-9 of solution 1.

[0235] The SessionPersistency may be substituted by the SessionPersistency created at step2-3 of solution 2.

[0236] The AF_EES executes the process(es) in the solution 2 with the 5G VN group data with the SessionPersistency IE described in this step 2-1-1.

[0237] The AF_EAS can send, to the AF_EES, Session Persistency including UE Identifier(s) and Persistent prefix.

[0238] For example, the AF_EAS may transmit at least one of the Target UE Identifier(s) and the Persistent prefix to the AF_EES.   For example, the AF_EAS may transmit the ParameterProvision_Create including at least one of the Target UE Identifier(s) and the Persistent prefix to the AF_EES.   Definition of the Target UE Identifier(s) and the Persistent prefix of the solution 2 may be applied to the Target UE Identifier(s) and the Persistent prefix in Variant 1 of the solution 2.   For example, the AF_EAS may have the Target UE Identifier(s) in advance. For example, the AF_EAS may receive the Target UE Identifier(s) from other network node(s). For example, the AF_EAS may create the Target UE Identifier(s) based on local configuration in the AF_EAS or operator's policy.   For example, the AF_EAS may have the Persistent prefix in advance. For example, the AF_EAS may receive the Persistent prefix from other network node(s). For example, the AF_EAS may create the Persistent prefix based on local configuration in the AF_EAS or operator's policy.

[0239] For example, in a case where the AF_EES receives at least one of the Target UE Identifier(s) and the Persistent prefix from the AF_EAS, the AF_EES may perform the step 2-3 in solution 2 using the at least one of the Target UE Identifier(s) and the Persistent prefix. Then, other processes (e.g., steps 2-4 to 2-8) in solution 2 may continue. Before or after step 2-1-1, steps 2-1 and 2-2 in solution 2 may be performed.

[0240] Step2-1-2:   This is a response to ParameterProvision_Create described in the step2-1-1.   For example, the AF_EES may transmit the response after performing solution 2.   For example, the AF_EES may transmit the response after step 2-8 in solution 2.

[0241] According to solution 2 and the variant of the solution 2, they have for example an advantage by using SessionPersistency which is that the traffic can be routed from a collection of UE(s) in a 5GS to the same AF_EAS in an Edge Hosting Environment (EHE) in a local part of DN.

[0242] For example, the solution 2 and the variant of the solution 2 include a case where AF_EAS or AF_EES in an Edge Hosting Environment (EHE) in a local part of DN specifies IP addresses (or Target UE Identifier(s)) and prefixes for a group of UEs and then requests SMF to assign the IP addresses and prefixes for a group of UEs (or requests the SMF to assign the IP addresses and prefixes persistently for the UE identified by the Target UE Identifier(s)). According to the solution 2 and the variant of the solution 2, before PDU session establishment, SessionPersistency is given by AF_EAS or AF_EES in an Edge Hosting Environment (EHE) in a local part of DN to SMF in the 5GS. Following the given SessionPersistency, SMF assigns and preserve IP addresses and prefixes for a group of UEs. On the other hand, the AF_EAS or AF_EES in an Edge Hosting Environment (EHE) in a local part of DN can apply the properties of SessionPersistency into the load balancer. As a result, the traffic can persistently be routed from a collection of UE(s) in a 5GS to the same AF_EAS and an Edge Hosting Environment (EHE) in a local part of DN. Hence, the solution 2 and the variant of the solution 2 can solve the above-mentioned problem.

[0243] System overview   Fig. 7 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) device (known as a user equipment (UE)) to which the above aspects are applicable. The telecommunication system 1 represents a system overview in which an end-to-end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.   The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RATs including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).   The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.   The (R)AN node 5 may be split into one or more control plane (CP) functions and one or more user plane (UP) functions. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane function is aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called 'dual connectivity' or 'Multi connectivity'.   The (R)AN node 5 can also support a communication using satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.   In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN) Global Forum.

[0244] The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in a logical node can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).   A Network Function can be deployed as distributed, redundant, stateless, and scalable, and provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV). The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0245] As is well known, a UE 3 may enter and leave areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0246] The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Slice Selection Function (NSSF) 76. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, and PCF 73 for the roaming-out UE 3.

[0247] The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2" / "N3" interface(s) and / or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In the case where the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type.

[0248] The "Uu" interface may include a Control plane and User plane.   The User plane of the Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.   The Control plane of the Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of the Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.   For example, the following messages are communicated over the RRC layer to support AS signaling. - RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup Request message.   - - establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue. - RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup message.   - - masterCellGroup and radioBearerConfig - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the RRC Setup Complete message.   - - guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity

[0249] The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and / or the like). The N1 interface is responsible for providing a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface. - Registration Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Registration Request message.   - - 5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters. - Registration Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Registration Accept message.   - - 5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI. - Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be included together in the Registration Complete message.   - - SOR transparent container. - Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be included together in the Authentication Request message.   - - ngKSI,ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message. - Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Response message.   - - Authentication response message identity, Authentication response parameter and EAP message. - Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Result message.   - - ngKSI, EAP message and ABBA. - Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Authentication Failure message.   - - Authentication failure message identity, 5GMM cause and Authentication failure parameter. - Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be populated together in the Authentication Reject message.   - - EAP message. - Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Request message.   - - ngKSI,Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. - Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Accept message.   - - PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. - Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Service Reject message.   - - 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list. - Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by aspects in this disclosure, any of the following parameters may be populated together in the Configuration Update Command message.   - - Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI. - Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by aspects in this disclosure, the following parameter may be populated together in the Configuration Update Complete message.   - - Configuration update complete message identity.

[0250] User equipment (UE)   Fig. 8 is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signalling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 10. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.

[0251] The UE 3 may, for example, support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0252] The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).

[0253] The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).

[0254] The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).

[0255] The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).

[0256] The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).

[0257] The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like.

[0258] The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)). The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies.

[0259] Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked.

[0260] It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0261] It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0262] The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device).

[0263] The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).

[0264] (R)AN node   Fig. 9 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. an RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0265] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.

[0266] The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimation and / or moving trajectory estimation.

[0267] The (R)AN node 5 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0268] System overview of (R)AN node 5 based on O-RAN architecture   Fig. 10 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.

[0269] The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

[0270] The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes 7 via an appropriate interface (such as the so-called "N3" interface(s) and / or the like).

[0271] Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionality to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.

[0272] Radio Unit (RU)   Fig. 11 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0273] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer.

[0274] The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation. The RU 60 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.

[0275] Distributed Unit (DU)   Fig. 12 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421 is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0276] The DU 61 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0277] As described above, the DU 61 can be integrated / combined with the RU 60 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above.

[0278] Centralized Unit (CU)   Fig. 13 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421 is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0279] The CU 62 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0280] As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above.

[0281] Access Management Function (AMF)   Fig. 14 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421 is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0282] The AMF 70 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0283] Session Management Function (SMF)   Fig. 15 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and / or may be downloaded via the telecommunication network or from a removable memory device (RMD), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421 is responsible for handling (generating / sending / receiving) signalling between the SMF 71 and other nodes, such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a Hypertext Transfer Protocol (HTTP) restful methods based on the service based interfaces) relating to session management procedures (for the UE 3).

[0284] The SMF 71 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0285] User Plane Function (UPF)   Fig. 16 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421 is responsible for handling (generating / sending / receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a GPRS Tunneling Protocol (GTP) for User plane) relating to User data handling (for the UE 3).

[0286] The UPF 72 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0287] Policy Control Function (PCF)   Fig. 17 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421 is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0288] The PCF 73 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0289] Network Exposure Function (NEF)   Fig. 18 is a block diagram illustrating the main components of the NEF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the NEF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421 is responsible for handling (generating / sending / receiving) signalling between the NEF 74 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network exposure function procedures (for the UE 3).

[0290] The NEF 74 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0291] Unified Data Management (UDM)   Fig. 19 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421 is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0292] The UDM 75 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0293] Network Data Analytics Function (NWDAF)   Fig. 20 is a block diagram illustrating the main components of the NSSF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with the software stored in a memory 764. The Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421 is responsible for handling (generating / sending / receiving) signalling between the NSSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0294] The NSSF 76 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0295] Application Function (AF)   Fig. 21 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421 is responsible for handling (generating / sending / receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). For example, the AF_EES and the AF_EAS may have same components to the AF 201.

[0296] The AF 201 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0297] Modifications and Alternatives   Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.

[0298] In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.

[0299] Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and / or timers; and / or the like.

[0300] In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.

[0301] In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.

[0302] Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0303] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0304] As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.

[0305] It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[0306] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0307] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0308] While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).

[0309] Supplementary notes   The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.

[0310] Supplementary note 1. A method of a first communication apparatus comprising:   communicating with a second communication apparatus; and   sending an Internet Protocol (IP) address and a prefix,   wherein the IP address and the prefix are used persistently.

[0311] Supplementary note 2. The method according to supplementary note 1,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0312] Supplementary note 3. The method according to supplementary note 1 or 2,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

[0313] Supplementary note 4. The method according to supplementary note 1 or 2, further comprising:   performing EventExposure_Subscribe operation,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS).

[0314] Supplementary note 5. A method of a first communication apparatus comprising:   receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus; and   using the IP address and the prefix persistently.

[0315] Supplementary note 6. The method according to supplementary note 5,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0316] Supplementary note 7. The method according to supplementary note 5 or 6,   wherein the first communication apparatus is a Session Management Function (SMF), and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

[0317] Supplementary note 8. A method of a first communication apparatus comprising:   communicating with a second communication apparatus; and   sending an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently.

[0318] Supplementary note 9. The method according to supplementary note 8,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0319] Supplementary note 10. The method according to supplementary note 8 or 9,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

[0320] Supplementary note 11. The method according to supplementary note 8 or 9,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS),   wherein the sending the identifier and the prefix includes sending the identifier and the prefix to the second communication apparatus, and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

[0321] Supplementary note 12. A method of a first communication apparatus comprising:   receiving an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently; and   assigning the IP address to the UE and using the prefix persistently.

[0322] Supplementary note 13. The method according to supplementary note 12,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0323] Supplementary note 14. The method according to supplementary note 12 or 13,   wherein the first communication apparatus is a Session Management Function (SMF).

[0324] Supplementary note 15. A first communication apparatus comprising:   means for communicating with a second communication apparatus; and   means for sending an Internet Protocol (IP) address and a prefix,   wherein the IP address and the prefix are used persistently.

[0325] Supplementary note 16. The first communication apparatus according to supplementary note 15,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0326] Supplementary note 17. The first communication apparatus according to supplementary note 15 or 16,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

[0327] Supplementary note 18. The first communication apparatus according to supplementary note 15 or 16, further comprising:   means for performing EventExposure_Subscribe operation,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS).

[0328] Supplementary note 19. A first communication apparatus comprising:   means for receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus,   wherein the IP address and the prefix are used persistently; and   means for using the IP address and the prefix persistently.

[0329] Supplementary note 20. The first communication apparatus according to supplementary note 19,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0330] Supplementary note 21. The first communication apparatus according to supplementary note 19 or 20,   wherein the first communication apparatus is a Session Management Function (SMF), and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

[0331] Supplementary note 22. A first communication apparatus comprising:   means for communicating with a second communication apparatus; and   means for sending an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently.

[0332] Supplementary note 23. The first communication apparatus according to supplementary note 22,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0333] Supplementary note 24. The first communication apparatus according to supplementary note 22 or 23,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

[0334] Supplementary note 25. The first communication apparatus according to supplementary note 22 or 23,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS),   wherein the sending the identifier and the prefix includes sending the identifier and the prefix to the second communication apparatus, and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

[0335] Supplementary note 26. A first communication apparatus comprising:   means for receiving an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently; and   means for assigning the IP address to the UE and using the prefix persistently.

[0336] Supplementary note 27. The first communication apparatus according to supplementary note 26,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

[0337] Supplementary note 28. The first communication apparatus according to supplementary note 26 or 27,   wherein the first communication apparatus is a Session Management Function (SMF).

[0338] Supplementary note 29. A method of an edge node comprising:   sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   in a case where one of the at least one event occurs, receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node; and   in a case where one of the at least one event occurs, sending, to the first core network node, third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

[0339] Supplementary note 30. A method of a first core network node comprising:   receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and   performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0340] Supplementary note 31. A method of a first edge node comprising:   sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   in a case where one of the at least one event occurs, receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF; and   in a case where one of the at least one event occurs, sending, to the second edge node, a third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

[0341] Supplementary note 32. A method of a first core network node comprising:   receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and   performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0342] Supplementary note 33. An edge node comprising:   means for sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   means for receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node in a case where one of the at least one event occurs; and   means for sending, to the first core network node, third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

[0343] Supplementary note 34. A first core network node comprising:   means for receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and   means for performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

[0344] Supplementary note 35. A first edge node comprising:   means for sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   means for receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF in a case where one of the at least one event occurs; and   means for sending, to the second edge node, a third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

[0345] Supplementary note 36. A first core network node comprising:   means for receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and   means for performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

[0346] This application is based upon and claims the benefit of priority from Indian patent applications No. 202311037562, filed on May 31, 2023, the disclosure of which is incorporated herein in its entirety by reference.

[0347] 1  telecommunication system 3  UE 31  transceiver circuit 32  antenna 33  controller 34  user interface 35  USIM 36  memory 361  operating system 362  communications control module 3621  transceiver control module 5   (R)AN node 51  transceiver circuit 52  antenna 53  network interface 54  controller 55  memory 551  operating system 552  communications control module 5521  transceiver control module 60  RU 601  transceiver circuit 602  antenna 603  network interface 604  controller 605  memory 6051  operating system 6052  communications control module 60521  transceiver control module 61  DU 611  transceiver circuit 612  network interface 613  controller 614  memory 6141  operating system 6142  communications control module 61421  transceiver control module 62  CU 621  transceiver circuit 622  network interface 623  controller 624  memory 6241  operating system 6242  communications control module 62421  transceiver control module 7  core network 70  AMF 701  transceiver circuit 702  network interface 703  controller 704  memory 7041  operating system 7042  communications control module 70421  transceiver control module 71  SMF 711  transceiver circuit 712  network interface 713  controller 714  memory 7141  operating system 7142  communications control module 71421  transceiver control module 72  UPF 721  transceiver circuit 722  network interface 723  controller 724  memory 7241  operating system 7242  communications control module 72421  transceiver control module 73  PCF 731  transceiver circuit 732  network interface 733  controller 734  memory 7341  operating system 7342  communications control module 73421  transceiver control module 74  NEF 741  transceiver circuit 742  network interface 743  controller 744  memory 7441  operating system 7442  communications control module 74421  transceiver control module 75  UDM 751  transceiver circuit 752  network interface 753  controller 754  memory 7541  operating system 7542  communications control module 75421  transceiver control module 76  NSSF 761  transceiver circuit 762  network interface 763  controller 764  memory 7641  operating system 7642  communications control module 76421  transceiver control module 20  data network 201  AF 2011  transceiver circuit 2012  network interface 2013  controller 2014  memory 20141  operating system 20142  communications control module 201421  transceiver control module

Claims

1. A method of a first communication apparatus comprising:   communicating with a second communication apparatus; and   sending an Internet Protocol (IP) address and a prefix,   wherein the IP address and the prefix are used persistently.

2. The method according to claim 1,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

3. The method according to claim 1 or 2,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

4. The method according to claim 1 or 2, further comprising:   performing EventExposure_Subscribe operation,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS).

5. A method of a first communication apparatus comprising:   receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus; and   using the IP address and the prefix persistently.

6. The method according to claim 5,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

7. The method according to claim 5 or 6,   wherein the first communication apparatus is a Session Management Function (SMF), and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

8. A method of a first communication apparatus comprising:   communicating with a second communication apparatus; and   sending an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently.

9. The method according to claim 8,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

10. The method according to claim 8 or 9,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

11. The method according to claim 8 or 9,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS),   wherein the sending the identifier and the prefix includes sending the identifier and the prefix to the second communication apparatus, and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

12. A method of a first communication apparatus comprising:   receiving an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently; and   assigning the IP address to the UE and using the prefix persistently.

13. The method according to claim 12,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

14. The method according to claim 12 or 13,   wherein the first communication apparatus is a Session Management Function (SMF).

15. A first communication apparatus comprising:   means for communicating with a second communication apparatus; and   means for sending an Internet Protocol (IP) address and a prefix,   wherein the IP address and the prefix are used persistently.

16. The first communication apparatus according to claim 15,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

17. The first communication apparatus according to claim 15 or 16,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

18. The first communication apparatus according to claim 15 or 16, further comprising:   means for performing EventExposure_Subscribe operation,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS).

19. A first communication apparatus comprising:   means for receiving an Internet Protocol (IP) address and a prefix from a second communication apparatus,   wherein the IP address and the prefix are used persistently; and   means for using the IP address and the prefix persistently.

20. The first communication apparatus according to claim 19,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

21. The first communication apparatus according to claim 19 or 20,   wherein the first communication apparatus is a Session Management Function (SMF), and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

22. A first communication apparatus comprising:   means for communicating with a second communication apparatus; and   means for sending an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently.

23. The first communication apparatus according to claim 22,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

24. The first communication apparatus according to claim 22 or 23,   wherein the first communication apparatus is an Application Function_Edge Enabler Server (AF_EES), and   wherein the second communication apparatus is a Network Exposure Function (NEF).

25. The first communication apparatus according to claim 22 or 23,   wherein the first communication apparatus is an Application Function_Edge Application Server (AF_EAS),   wherein the sending the identifier and the prefix includes sending the identifier and the prefix to the second communication apparatus, and   wherein the second communication apparatus is an Application Function_Edge Enabler Server (AF_EES).

26. A first communication apparatus comprising:   means for receiving an identifier and a prefix,   wherein the identifier is an identifier of a User Equipment (UE) which an Internet Protocol (IP) address is assigned persistently, and   wherein the prefix is used persistently; and   means for assigning the IP address to the UE and using the prefix persistently.

27. The first communication apparatus according to claim 26,   wherein the IP address and the prefix are used persistently in a case where a Protocol Data Unit (PDU) session is established.

28. The first communication apparatus according to claim 26 or 27,   wherein the first communication apparatus is a Session Management Function (SMF).

29. A method of an edge node comprising:   sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   in a case where one of the at least one event occurs, receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node; and   in a case where one of the at least one event occurs, sending, to the first core network node, third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

30. A method of a first core network node comprising:   receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and   performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

31. A method of a first edge node comprising:   sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   in a case where one of the at least one event occurs, receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF; and   in a case where one of the at least one event occurs, sending, to the second edge node, a third message including information on SessionPersistency, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

32. A method of a first core network node comprising:   receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and   performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

33. An edge node comprising:   means for sending, to a first core network node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   means for receiving, from the first core network node, second message including a UE's IP addresses and a prefix value assigned by a second core network node in a case where one of the at least one event occurs; and   means for sending, to the first core network node, third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the at least one event occurred, the Persistent prefix being not changed in a case where the at least one event occurred.

34. A first core network node comprising:   means for receiving, from a second core network node or a first edge node, a SessionPersistency including a persistent UE IP address and a persistent prefix; and   means for performing, with a UE of a group, a PDU session establishment procedure using the persistent UE IP address and the persistent prefix.

35. A first edge node comprising:   means for sending, to a second edge node, a first message including at least one Event ID identifier indicating that type of at least one event occurred and at least one Target UE Identifier for identifying at least one UE related to the at least one event;   means for receiving, from the second edge node, a second message including a UE's IP addresses and a prefix value assigned by SMF in a case where one of the at least one event occurs; and   means for sending, to the second edge node, a third message including information on SessionPersistency in a case where one of the at least one event occurs, the information on SessionPersistency including information on Persistent UE IP address, and information on Persistent prefix, the information on Persistent UE IP address being not changed in a case where the event occurred, the Persistent prefix being not changed in a case where the IP addresses are replaced with different IP addresses.

36. A first core network node comprising:   means for receiving, from a second core network node or a first edge node, a SessionPersistency including a target UE identifier for identifying at least one UE and a persistent prefix indicating a prefix used persistently; and   means for performing, with a UE of a group, a PDU session establishment procedure using the target UE identifier and the persistent prefix.

Citation Information

Patent Citations

  • Session Management for Aerial System

    US20220248363A1

Cited By

  • Communication method, communication device and communication system

    CN120568387A