WO2024078753A1 - Commutation de chemin d'accès - Google Patents

Commutation de chemin d'accès Download PDF

Info

Publication number
WO2024078753A1
WO2024078753A1 PCT/EP2023/067176 EP2023067176W WO2024078753A1 WO 2024078753 A1 WO2024078753 A1 WO 2024078753A1 EP 2023067176 W EP2023067176 W EP 2023067176W WO 2024078753 A1 WO2024078753 A1 WO 2024078753A1
Authority
WO
WIPO (PCT)
Prior art keywords
access path
access
registration
network
user equipment
Prior art date
Application number
PCT/EP2023/067176
Other languages
English (en)
Inventor
Apostolis Salkintzis
Original Assignee
Lenovo (Singapore) Pte. Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2024078753A1 publication Critical patent/WO2024078753A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed

Definitions

  • the technical field is an access path switching procedure applicable in particular to an Access Traffic Steering, Switching, and Splitting feature of 3GPP, allowing a User Equipment to utilize multiple access paths simultaneously.
  • 3GPPTM The 3rd Generation Partnership Project
  • 3GPP is an umbrella term for a number of standards organizations which develop protocols for mobile telecommunications.
  • 3GPP is currently in the process of developing standards for 5G NR and related 5G standards, including 5G-Advanced.
  • the Access Traffic Steering, Switching, and Splitting (ATSSS) feature provides enhanced data communication capabilities by allowing a User Equipment (UE) to utilize multiple access paths simultaneously. This is achieved by establishing a multiaccess data connection (referred to in the 3GPP specs as Multiaccess Packet Data Unit (MA PDU) session) that supports two access paths, one 3GPP access path, using an access network defined by 3GPP such a NG-RAN, and one non-3GPP access path, using an access network not defined by 3GPP such as WiFiTM.
  • MA PDU Multiaccess Packet Data Unit
  • Every data packet that should be transmitted via the multiaccess data connection is transmitted either over the 3GPP access path or over the non-3GPP access path, according to multiaccess rules (also known as ATSSS rules), which are provided to a User equipment (UE) during the establishment of the multiaccess data connection.
  • multiaccess rules also known as ATSSS rules
  • the ATSSS feature supports also a capability known as "non-3GPP access path switching," which enables a UE to switch its non-3GPP access path between different non-3GPP access networks.
  • a UE initially establishes a non-3GPP access path via an "untrusted" non- 3GPP access network, served by a non-3GPP Interworking Function (N3IWF).
  • N3IWF non-3GPP Interworking Function
  • This non- 3GPP access path can be subsequently switched to a "trusted" non-3GPP access network, served by a Trusted Non-3GPP Gateway Function (TNGF).
  • TNGF Trusted Non-3GPP Gateway Function
  • the UE maintains its Multiaccess PDU (MA PDU) Session and continues data communication using both the 3GPP access path and the newly switched non-3GPP access path.
  • MA PDU Multiaccess PDU
  • Non-3GPP access path switching can be beneficial for a number of reasons including enhanced security, improved connectivity, or optimized network usage. For example, a UE might switch from an untrusted to a trusted network when it detects a degradation in service quality.
  • Figure 1 illustrates the key principle of the “non-3GPP access path switching” procedure (defined in Release 18 specifications) which enables the switching of a non-3GPP access path of an MA PDU Session, from a source non-3GPP access path to a target non-3GPP access path, both included in the same 5G Core (5GC) network (or PLMN).
  • the switching procedure is triggered by a Registration Request message sent by the UE over the target non-3GPP access path.
  • the 5GC network receives this message it determines that the UE wants to switch the existing (source) non-3GPP access path to a new (target) non-3GPP access path.
  • the UE has also a 3GPP access path (as part of the established MA PDU Session) but switching this 3GPP access path to a new non-3GPP access path is not specified in Release 18. Therefore, by sending the Registration Request message via the new non-3GPP access path, the 5GC network implicitly determines which of the existing access paths of the MA PDU Session should be transferred (switched) to the access path via which the Registration Request was received.
  • Source non-3GPP access path switched to a target 3GPP access path (non- 3GPP to 3GPP).
  • the first two scenarios are schematically illustrated in Figures 2 and 3 respectively.
  • the existing “non-3GPP access path switching” procedure as defined in Release 18 cannot be applied to these further scenarios.
  • the UE has a MA PDU Session composed of two 3GPP access paths.
  • the 5GC network receives the Registration Request message via the target 3GPP access path, it cannot determine which of the existing two 3GPP access paths the UE wishes to switch to the target access path.
  • the MA PDU Session can be composed of more than two access paths, e.g., two 3GPP access paths and one non-3GPP access, for example where a UE is simultaneously using terrestrial 3GPP access, non-terrestrial 3GPP access (via satellite), and non-3GPP access via Wi-Fi.
  • two 3GPP access paths e.g., two 3GPP access paths and one non-3GPP access
  • a UE is simultaneously using terrestrial 3GPP access, non-terrestrial 3GPP access (via satellite), and non-3GPP access via Wi-Fi.
  • a User Equipment comprising a transceiver and processing circuitry configured to perform a first registration with a core network of a mobile communication network, via a first access network, perform a second registration with the core network, via a second access network, and establish a multiaccess data connection with the core network comprising a first access path associated with the first registration and a second access path associated with the second registration.
  • the processing circuitry is configured to receive, from the core network, first and second access path identities associated with the first access path and the second access path respectively.
  • the processing circuitry is further configured to initiate a third registration with the core network, via a third access network, including providing to the core network one of the first and second path identities as a source access path identity, and switch one of the access paths of the multiaccess data connection from the first or second access path, identified by the source access path identity, to a third access path associated with the third registration.
  • a network device for use in a core network of a mobile communication network and comprising a transceiver and processing circuitry configured to perform a first registration of a User Equipment, via a first access network, perform a second registration of the User Equipment, via a second access network, and initiate establishment of a multiaccess data connection with the User Equipment comprising a first access path associated with the first registration and a second access path associated with the second registration.
  • the processing circuitry is configured to send to the User Equipment first and second access path identities associated with the first access path and the second access path respectively.
  • the transceiver and processing circuitry are further configured to initiate a third registration of the User Equipment, via a third access network, including receiving from the User Equipment one of the first and second path identities as a source access path identity, and initiate switching of one of the access paths of the multiaccess data connection from the first or second access path, identified by the source access path identity, to a third access path associated with the third registration.
  • the network node may be configured to operate as an Access and Mobility Management Function (AMF) of a 5G core network.
  • AMF Access and Mobility Management Function
  • the transceiver and processing circuitry may be configured to initiate establishment of a multiaccess data connection with the User Equipment by forwarding a request from the UE to a Session Management Function (SMF) of the 5G core network.
  • SMF Session Management Function
  • the transceiver and processing circuitry may be configured to initiate switching of one of the access paths of the multiaccess data connection from the first or second access path, identified by the source access path identity, to a third access path by forwarding a request from the UE to a Session Management Function (SMF) of the 5G core network.
  • SMF Session Management Function
  • a method implemented at a User Equipment comprising performing a first registration with a core network of a mobile communication network, via a first access network, performing a second registration with the core network, via a second access network, and establishing a multiaccess data connection with the core network comprising a first access path associated with the first registration and a second access path associated with the second registration.
  • the User Equipment receives, from the core network, first and second access path identities associated with the first access path and the second access path respectively, initiates a third registration with the core network, via a third access network, including providing to the core network one of the first and second path identities as a source access path identity, and switches one of the access paths of the multiaccess data connection from the first or second access path, identified by the source access path identity, to a third access path associated with the third registration.
  • a network device for use in a core network of a mobile communication network and comprising a transceiver and processing circuitry configured to receive a request to initiate establishment of a multiaccess data connection with a User Equipment and comprising a first access path associated with a first registration and a second access path associated with a second registration, the request including first and second access path identities associated with the first access path and the second access path respectively.
  • the transceiver and processing circuitry are further configured respond to said request by establishing the multiaccess data connection with the User Equipment.
  • the transceiver and processing circuitry are further configured to receive a request to initiate switching of one of the access paths of the multiaccess data connection from the first or second access path, identified by a source access path identity contained in the request, to a third access path associated with the third registration, and to respond by completing the switching.
  • the network entity of the further aspect may be configured to operate as a Session Management Function (SMF).
  • SMF Session Management Function
  • Figure 1 illustrates schematically a non-3GPP access path switching procedure defined in Release 18 specifications and which enables the switching of a non-3GPP access path from a source non-3GPP access path to a target non-3GPP access path;
  • Figure 2 illustrates a required 3GPP access path switching procedure of Release 19 specifications and which involves the switching of a 3GPP access path from a source 3GPP access path to a target 3GPP access path;
  • Figure 3 illustrates a required 3GPP access path switching procedure of Release 19 specifications and which involves the switching of a 3GPP access path from a source non-3GPP access path to a target 3GPP access path;
  • Figure 4 illustrates schematically a mobile communication system including a 5G core network and a User Equipment
  • Figure 5 illustrates an access path switching procedure according to an embodiment and which involves the switching of an access path from a source access path to a target access path using access path identities;
  • Figure 6 illustrates signalling in the network of Figure 4 according to an embodiment
  • Figure 7 illustrates signalling in the network of Figure 4 according to an embodiment
  • Figure 8 is a flow diagram illustrating an embodiment
  • Figure 9 illustrates schematically an embodiment of a User Equipment
  • Figure 10 illustrates schematically an embodiment of a network apparatus.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
  • the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the- shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • the disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
  • embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code.
  • the storage devices may be tangible, non-transitory, and/or non-transmission.
  • the storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
  • LAN local area network
  • WLAN wireless LAN
  • WAN wide area network
  • ISP Internet Service Provider
  • a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list.
  • a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one or more of” includes any single item in the list or a combination of items in the list.
  • one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one of” includes one and only one of any single item in the list.
  • “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C.
  • a member selected from the group consisting of A, B, and C includes one and only one of A, B, or C, and excludes combinations of A, B, and C.”
  • “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
  • each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • FIG. 4 illustrates a remote unit 105 (UE) connected to a 5G core (5GC) network 140 via two types of access networks:
  • a 3GPP access network 110 (“First Access Network”) comprising a Cellular Base Station 111 to which the UE is connected, and
  • a non-3GPP access network 120 (“Second Access Network”) comprising an Access Point 121 to which the UE is also connected.
  • the First Access Network 110 uses a 3GPP-defined type of wireless communication (e.g., NG-RAN), while the Second Access Network 120 uses a non-3GPP-defined type of wireless communication (e.g., WLAN/Wi-Fi).
  • the Second Access Network is connected to the 5GC network via a suitable Interworking Function 122 (e.g., a N3IWF or TNGF).
  • the 5G-RAN 118 in the Figure refers to any type of 5G access network that can provide access to the 5GC 140, including the 3GPP access network 120 and the non-3GPP access network 130.
  • Unified Data Management (UDM) 149.
  • Session Management Function (SMF) 145 Session Management Function 145
  • Access and Mobility Management Function 143
  • PCF Policy Control Function
  • the UE 105 can establish a multiaccess data connection 148 with the UPF 141 in the 5GC 140 and which can support data communication using multiple access types including data communication 113 with the (first) access type of the First Access Network 110 (e.g., NG-RAN) and data communication 123 with the (second) access type of the Second Access Network 120 (e.g., Wi-Fi access).
  • the multiaccess data connection 148 is also known as a “multiaccess PDU Session” and supports two user-plane connections: one user-plane connection using communication over 3GPP access 115 and another user-plane connection using communication over non-3GPP access 125.
  • a MA PDU Session may have two or more user-plane connections, each one using communication over a different type of access network.
  • Each user-plane connection is also referred to as an “access path”.
  • the user-plane connection using communication over 3GPP access 115 is also referred to as first access path 115
  • the user-plane connection using communication over non-3GPP access 125 is also referred to as second access path 125.
  • the PCF 147 creates steering rules, which are translated by the SMF 145 to steering rules 108 for the Uplink (UL) traffic and steering rules 109 for the Downlink (DL) traffic and which rules are forwarded to the UE 105 and to UPF 141 respectively.
  • the steering rules for the Uplink (UL) traffic are called ATSSS rules, and the steering rules for the Downlink (DL) traffic are called Multi Access Rules (MAR).
  • MAR Multi Access Rules
  • the steering rules specify how the UL traffic and how the DL traffic of the MA PDU Session is to be routed across the two user-plane connections, or across the access paths of the MA PDU Session.
  • the UE 105 may use the MA PDU Session 148 to communicate with a Remote Host 155, connectable via a Data Network 150.
  • Figure 4 further illustrates a Third Access Network 130 of a third access type, which type may be the same as or different from the access types of the First and Second Access Networks.
  • the UE 105 can connect to the Third Access Network 130 via a Cellular Base Station 131 although no MA PDU Session access path has yet been established via the Third Access Network 130.
  • the UE can apply the procedure specified below to switch either the first access path 115 or the second access path 125 of the MA PDU Session to a third access path (not shown) established via the Third Access Network 130.
  • the third access path will use user-plane resources between the remote unit (UE) 105 and the UPF 141 , via the Third Access Network 130.
  • each access path of a MA PDU Session has an identity which is assigned by the AMF 143 during the registration procedure.
  • the UE 105 wants to switch a source access path to a target access path (e.g. the “third access path”) the UE sends a Registration Request message to the AMF 143 over the third access path and includes in this message the identity of the source access path that is to be transferred.
  • Each access path can be either a 3GPP access path or a non-3GPP access path.
  • the principle shown in Figure 5 can be used to (a) switch a 3GPP access path to another 3GPP access path, or (b) switch a 3GPP access path to a non-3GPP access path, or (c) switch a non-3GPP access path to a 3GPP access path.
  • the access networks shown in Figure 5 may be of different types or may be of the same type.
  • the first access network and the third access network could both be terrestrial NG-RAN networks.
  • Figure 6 illustrates in detail a modified procedure for (a) MA PDU Session Establishment and (b) Access Path Switching. It illustrates in particular the following steps:
  • Step 1 The UE registers to the 5G core network via a first access network node (e.g., gNB-1) in a first access network.
  • the existing 5G registration procedure is applied.
  • the AMF supports ATSSS and access path switching, it assigns an access path identity and provides this to the UE within the Registration Accept message.
  • This access path identity can later be used by the UE to indicate that an MA PDU Session should establish user-plane resource over the first access network, or to indicate that this access path should be switched to a different access path.
  • the access path identity assigned by the AMF may be either a numeral value (e.g., “70”, “71”, etc.) or another type of value.
  • Step 2 The UE registers to the 5G core network via a second access network node (e.g., a gNB-2) in a second access network, using the same procedure as in step 1 .
  • second access network could be the same type or different type from the first access network.
  • the first access network could be a terrestrial 3GPP access network
  • the second access network could either a terrestrial 3GPP access network (using a different gNB) or a non-3GPP access network, such as a Wi-Fi network.
  • Steps 3, 4 An MA PDU Session is established that can transfer data over the first access path and the second access path.
  • the UE sends an UL NAS Transport message to the AMF containing a PDU Session Establishment Request message.
  • the UE indicates to the AMF that (a) it requests a MA PDU session, (b) it supports access path switching and (c) it wants the MA PDU Session to comprise a first access path and a second access path.
  • the last component (c) is optional and, when not provided, the AMF assumes that the MA PDU Session should contain all the access paths via which the UE is already registered.
  • the “access path switching supported” indication is an extension of the existing “non-3GPP access path switching supported” indication and indicates that the UE supports path switching for all types of accesses.
  • the AMF sends a Nsmf_PDUSession_CreateSMContext Request message to the SMF in order to establish the user-plane resources for the requested MA PDU Session.
  • This message indicates that both the UE and the AMF support access path switching, and it also indicates the identities of the access paths on which user-plane resources should be established.
  • the SMF selects a UPF for the MA PDU Sessions and establishes an N4 Session with the selected UPF.
  • the SMF sends an Namf_Communication_N1 N2MessageTransfer Request message, which contains the first access path identity indicating that the AMF should establish user-plane resources over the first access path.
  • This message contains also a PDU Session Establishment Accept message (not shown in the Figure) which should be transferred to the UE via the first access path.
  • This message indicates that the SMF supports access path switching, so the UE may later initiate an access path switching procedure (as in step 6). It also contains ATSSS rules which are applied by the UE to determine how to route uplink traffic across the first access path and the second access path.
  • Step 5 After the establishment of the MA PDU Session, user-plane traffic is transmitted over the first access path and the second access path based on the ATSSS rules provided to UE and based on the multiaccess N4 rules provided to UPF.
  • Step 6 The UE initiates an access path switching procedure to transfer the second access path to a third access path.
  • the UE sends another Registration Request message to the AMF via the third access path.
  • the UE includes the identity of the MA PDU Session (in the List of PDU Session to be Activated) and requests “path switching while using old resources”, i.e., to maintain the user-plane resources via the old (source) access path until the user-plane resource via the new (target) access path are established.
  • the UE includes the identity of the source access path that should be switched to the third access path.
  • the AMF sends an Nsmf_PDUSession_UpdateSMContext Request message to the SMF to trigger the establishment of user-plane resources over the third access path and to release the user-plane resources for the second access path in the UPF.
  • the AMF assigns an identity to the third access path and includes in the request message the identity of the third access path (target) and the identity of the second access path (source).
  • the SMF establishes the user-plane resources over the third access path and then the AMF triggers the release of the user-plane resources over the second access path. Finally, the AMF sends a Registration Accept message to the UE to indicate that the UE has registered via the third access path and that the second access path has been successfully transferred to the third access path. In the message, the AMF includes the identity of the third access path, which may be used later by the UE to refer to this access path (e.g., to switch it to another access path).
  • Step 7 After the access path switching is completed, the user-plane traffic of the MA PDU Session is transmitted over the first access path and the third access path based on the ATSSS rules provided to UE and based on the multiaccess N4 rules provided to UPF.
  • Figure 7 illustrates an alternative procedure that can be used to implement access path switching satisfying the requirements of Release 19. This involves the following steps.
  • the UE registers to the 5G core network via a first access network node (e.g., gNB-1) in a first access network, and registers also to the 5G core network via a second access network node (e.g., gNB-2) in a second access network.
  • the second access network could be the same as or different from the first access network.
  • the first access network could be a terrestrial 3GPP access network while the second access network could either a terrestrial 3GPP access network (using a different gNB) or a non-3GPP access network, such as a Wi-Fi network.
  • the registration procedures are executed with no changes. Up to this point no access path identifiers have been exchanged.
  • Steps 3, 4 An MA PDU Session is established that can transfer data over the first access path and the second access path.
  • the UE sends an UL NAS Transport message to the AMF containing a PDU Session Establishment Request message.
  • this message does not contain the identities of the access paths that should be supported by the MA PDU Session.
  • the “access path switching supported” indication is an extension of the existing “non-3GPP access path switching supported” indication and indicates that the UE supports path switching for all types of accesses.
  • the AMF sends a Nsmf_PDUSession_CreateSMContext Request message to the SMF in order to establish the user-plane resources for the requested MA PDU Session.
  • This message indicates that both the UE and the AMF support access path switching, and it also indicates the identities of the access paths on which the user-plane resources should be established. These identities are assigned by the AMF. In the example shown in Figure 7 the AMF knows that the UE is registered via two access paths, so it assigns an identity to each one of these access paths.
  • the SMF selects a UPF for the MA PDU Sessions and establishes an N4 Session with the selected UPF.
  • the SMF sends an Namf_Communication_N1 N2MessageTransfer Request message, which contains the first access path identity indicating that the AMF should establish user-plane resources over the first access path.
  • This message contains also a PDU Session Establishment Accept message (not shown in the Figure) which should be transferred to the UE via the first access path.
  • This message indicates that the SMF supports access path switching so that the UE may later initiate an access path switching procedure (as in step 6). It also contains ATSSS rules, which are applied by the UE to determine how to route uplink traffic across the first access path and the second access path.
  • the PDU Session Establishment Accept message contains the access path identities assigned by the AMF and provided to the SMF in step 3b. In this way the UE is informed about the identity associated with each access path of the MA PDU Session.
  • Each access path identity assigned by the AMF may be either a numeral value associated with an access type (e.g., “70” for the path over untrusted non-3GPP access and “71” for the path over NR-LEO) or a descriptive value (e.g., “NR-LEO” or “untrusted non-3GPP access” or “E-UTRA”, etc.).
  • RAT radio access technology
  • each access path is associated with a NAS signalling connection between the UE and the AMF.
  • the SMF sends to the AMF (in step 4f) another Namf_Communication_N1 N2MessageTransfer Request message, which contains the second access path identity indicating that the AMF should establish user-plane resources over the second access path.
  • Steps 5-7 These are the same as the correspondingly numbered steps of Figure 6.
  • the third registration request contains the source access path identity and the third registration accept contains the target access path identity.
  • the registration procedure is still impacted (as it needs to support new information elements), but this is only needed when the registration is used for access path switching. In all other cases, the registration procedure is not impacted.
  • FIG. 8 is a flow diagram illustrating various steps in a method implemented at a User Equipment. Illustrated specifically are the following steps:
  • 600 Performing a first registration with a core network of a mobile communication network, via a first access network; 601 : Performing a second registration with the core network, via a second access network; and
  • the User Equipment receives, from the core network, first and second access path identities associated with the first access path and the second access path respectively. NB. This step may be performed at any suitable point or points during or after step 600.
  • 604 Switching one of the access paths of the multiaccess data connection from the first or second access path, identified by the source access path identity, to a third access path associated with the third registration.
  • FIG. 9 depicts a user equipment (UE) apparatus 700 that, in various embodiments, is used to implement one or more of the solutions described above.
  • the user equipment apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.
  • the input device 715 and the output device 720 are combined into a single device, such as a touchscreen.
  • the user equipment apparatus 700 may not include any input device 715 and/or output device 720.
  • the user equipment apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720.
  • the transceiver 725 includes at least one transmitter 730 and at least one receiver 735.
  • the transceiver 725 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121.
  • the transceiver 725 may support at least one network interface 740 and/or application interface 745.
  • the application interface(s) 745 may support one or more APIs.
  • the network interface(s) 740 may support 3GPP reference points, such as Uu, N1 , PC5, etc. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.
  • the processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 705 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller.
  • the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein.
  • the processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.
  • the processor 705 controls the user equipment apparatus 700 to implement the above described UE behaviors.
  • the processor 705 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • an application processor also known as “main processor” which manages application-domain and operating system (“OS”) functions
  • a baseband processor also known as “baseband radio processor” which manages radio functions.
  • FIG. 10 depicts a network apparatus 800 that may be present within the core network, according to embodiments of the disclosure.
  • the network apparatus 800 may include a processor 805, a memory 810, an input device 815, an output device 820, and a transceiver 825.
  • the input device 815 and the output device 820 are combined into a single device, such as a touchscreen.
  • the network apparatus 800 may not include any input device 815 and/or output device 820.
  • the network apparatus 800 may include one or more of: the processor 805, the memory 810, and the transceiver 825, and may not include the input device 815 and/or the output device 820.
  • the transceiver 825 includes at least one transmitter 830 and at least one receiver 835.
  • the transceiver 825 communicates with one or more UEs via one or more intermediate components.
  • the transceiver 825 may support at least one network interface 840 and/or application interface 845.
  • the application interface(s) 845 may support one or more APIs.
  • the processor 805, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 805 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.
  • the processor 805 executes instructions stored in the memory 810 to perform the methods and routines described herein.
  • the processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825.

Landscapes

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

Abstract

Équipement utilisateur (UE) conçu pour effectuer un premier enregistrement avec un réseau central par l'intermédiaire d'un premier réseau d'accès et un deuxième enregistrement avec le réseau central par l'intermédiaire d'un deuxième réseau d'accès, et pour déclencher l'établissement d'une connexion de données multi-accès comprenant des premier et deuxième chemins d'accès associés respectivement aux premier et deuxième enregistrements. L'UE est conçu pour recevoir des première et seconde identités de chemin d'accès associées respectivement au premier chemin d'accès et au deuxième chemin d'accès. L'UE est en outre conçu pour déclencher un troisième enregistrement avec le réseau central par l'intermédiaire d'un troisième réseau d'accès, consistant à fournir au réseau central une identité de chemin d'accès source et pour déclencher une commutation de l'un des chemins d'accès de la connexion de données multi-accès à partir du premier ou du deuxième trajet d'accès identifié par l'identité du chemin d'accès source, à un troisième chemin d'accès associé au troisième enregistrement.
PCT/EP2023/067176 2023-06-12 2023-06-23 Commutation de chemin d'accès WO2024078753A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20230100467 2023-06-12
GR20230100467 2023-06-12

Publications (1)

Publication Number Publication Date
WO2024078753A1 true WO2024078753A1 (fr) 2024-04-18

Family

ID=87067055

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/067176 WO2024078753A1 (fr) 2023-06-12 2023-06-23 Commutation de chemin d'accès

Country Status (1)

Country Link
WO (1) WO2024078753A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18)", vol. SA WG2, no. V18.1.1, 5 April 2023 (2023-04-05), pages 1 - 829, XP052284561, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.502/23502-i11.zip 23502-i11.docx> [retrieved on 20230405] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Access Traffic Steering, Switching and Splitting support in the 5G system architecture (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.793, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.4.0, 30 April 2018 (2018-04-30), pages 1 - 58, XP051451218 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on access traffic steering, switching and splitting support in the 5G system architecture; Phase 3 (Release 18)", no. V0.2.0, 18 April 2022 (2022-04-18), pages 1 - 66, XP052145997, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.700-53/23700-53-020.zip 23700-53-020_rm.doc> [retrieved on 20220418] *

Similar Documents

Publication Publication Date Title
US11737045B2 (en) Connection processing method and apparatus in multi-access scenario
US11528770B2 (en) Session management method, apparatus, and system
JP7485772B2 (ja) プライベートネットワークにおける緊急サービスを処理するための方法、装置、およびコンピュータプログラム製品
CN110049070B (zh) 事件通知方法及相关设备
CN110291837B (zh) 网络注册和网络切片选择系统和方法
JP7075066B2 (ja) ネットワークスライス選択ポリシを用いたｕｅの構成および更新
JP6908720B2 (ja) コアネットワーク制御プレーンデバイス選択方法および装置
RU2754775C1 (ru) Обработка сетевых функций в контексте мобильности между функциями управления
US20210400489A1 (en) 3gpp private lans
EP3860176B1 (fr) Procédé, appareil, et système d&#39;obtention d&#39;informations de capacité de terminal
CN111918279B (zh) 一种寻址方法、通信装置及系统
CN111512653B (zh) 通过桥接实体路由漫游用户设备的注册请求的技术
WO2020217224A1 (fr) Comportement amf et scp dans la découverte déléguée de pcf
US20220303935A1 (en) Amf re-allocation solution with network slice isolation
US20220272577A1 (en) Communication method and communication apparatus
CN116058000A (zh) 用于在重定位时协调到边缘应用服务器的无缝服务连续性的机制
US20230362748A1 (en) Wireless communication method, communication apparatus, and communication system
WO2023087965A1 (fr) Procédé et appareil de communication
KR20240060670A (ko) 통신 방법 및 장치
WO2024078753A1 (fr) Commutation de chemin d&#39;accès
CN116097751A (zh) 利用smf重新选择来重新锚定
WO2021201729A1 (fr) Libération ou reprise plus rapide pour un ue dans un état inactif
CN113329448A (zh) 一种通信的方法及装置
US20230354241A1 (en) Methods and Apparatus for Supporting the Communication of Path Switching Capability Information Between User Equipment and a Network Device To Enable Efficient Switching of Multi-Access (MA) Traffic Between Non-3GPP Access Paths
WO2024066924A1 (fr) Procédé et appareil de configuration de politique de terminal utilisateur, et support et puce

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23736009

Country of ref document: EP

Kind code of ref document: A1