Method and device for user plane relocation

By updating N2 SM information and re-establishing channels in the 5G network, the invalid data path and service request process interruption during UPF relocation is solved, and network continuity and reliability under WTRU mobility and SMF changes are achieved.

CN113473561BActive Publication Date: 2024-11-15INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110684663.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-06-19
Filing Date
2018-06-19
Publication Date
2024-11-15
Estimated Expiration
2038-06-19

AI Technical Summary

Technical Problem

In 5G networks, when user plane function (UPF) relocation, it is difficult for the prior art to effectively manage invalid data paths and service request processes, especially in the case of WTRU mobility and SMF changes, which may lead to data path corruption and service interruption. .

Method used

By receiving N2 SM information at the AMF node, determining the location of the WTRU and updating the N2 SM information, if the WTRU is outside the available area, requesting to update the N2 SM information and re-establishing the channel when the invalid data path is invalid, ensuring PDU session continuity and data path stability.

Benefits of technology

The user plane function relocation in the case of WTRU mobility and SMF changes is realized, avoiding interruptions in invalid data paths and service requests, and ensuring network continuity and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113473561B_ABST
    Figure CN113473561B_ABST
Patent Text Reader

Abstract

A system, method and apparatus for an access control and mobility management function (AMF) node is disclosed, comprising: a processor configured to receive N2 session management (SM) information from a session management function (SMF) node, wherein the N2SM information indicates an available area for N2 information, receive a service request from a wireless transmit receive unit (WTRU), determine whether to update the N2SM information based on the location of the WTRU and the available area for N2 information, wherein if the WTRU is outside the available area for N2 information, the processor is configured to request second N2SM information from the SMF node and update the N2SM information with the second N2SM information, and send an N2 request with the N2SM information to an access network associated with the WTRU. The available area for N2 information may be one or more of: a user plane function (UPF) node serving area, a WTRU tracking area, or a radio access network (RAN) cell coverage area.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of Chinese patent application 201880041103.9, entitled “User Plane Relocation Method and Device”, filed on June 19, 2018.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 521,878, filed on June 19, 2017, the entire contents of which are incorporated herein by reference. Background Art

[0004] Wireless communication systems continue to evolve. The new fifth generation may be referred to as 5G. An example of a previous generation of mobile communication systems may be referred to as fourth (4G) Long Term Evolution (LTE). Summary of the invention

[0005] A system, method and apparatus for an access control and mobility management function (AMF) node is disclosed, comprising: a processor configured to receive N2 session management (SM) information from a session management function (SMF) node, wherein the N2 SM information indicates an available area for the N2 information, receive a service request from a wireless transmit receive unit (WTRU), determine whether to update the N2 SM information based on the location of the WTRU and the available area for the N2 information, wherein if the WTRU is outside the available area for the N2 information, the processor is configured to request second N2 SM information from the SMF node and update the N2 SM information with the second N2 SM information, and send an N2 request with the N2 SM information to an access network associated with the WTRU. The available area for the N2 information may be one or more of: a user plane function (UPF) node serving area, a WTRU tracking area, or a radio access network (RAN) cell coverage area. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0007] Figure 1B is a diagram showing the Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown in FIG.

[0008] Figure 1C is a diagram showing the Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) used within the communication system shown in .

[0009] Figure 1D is a diagram showing the Figure 1A System diagram of another example RAN and another example CN used within the communication system shown in .

[0010] Figure 2 An example model of the architecture of a 5G and / or NextGen network is shown.

[0011] Figure 3 An exemplary user plane function (UPF) relocation due to WTRU mobility is shown, wherein the UPF relocation is performed without session management function (SMF) changes.

[0012] Figure 4 An example UPF relocation due to WTRU mobility is shown, where the UPF relocation is performed in the case of a SMF change.

[0013] Figure 5 An example architecture with one or more SMFs is shown, where an access control and mobility management function (AMF) can select and / or communicate with an intermediate SMF (I-SMF).

[0014] Figure 6 An example architecture with one or more SMFs is shown, where the AMF can communicate with an anchor SMF (A-SMF).

[0015] Figure 7 An example of an invalid data path occurring in UPF relocation due to WTRU mobility in idle mode is shown.

[0016] Figure 8 An exemplary network-triggered service request process is shown.

[0017] Fig. 9 An example UPF relocation during a network-triggered service request process is shown.

[0018] Fig.10 An example UPF relocation during a network-triggered service request process is shown.

[0019] Fig.11 An example UPF relocation during a network-triggered service request process is shown.

[0020] Fig.12 An exemplary N9 data path release process is shown.

[0021] Fig.13 An example architecture with one or more SMFs is shown.

[0022] Fig.14 An example AMF ID provided to the A-SMF via the I-SMF is shown.

[0023] Fig.15 An example AMF ID provided to the A-SMF via the I-SMF is shown. DETAILED DESCRIPTION

[0024] A detailed description of illustrative embodiments will now be described with reference to the various drawings. Although this specification provides detailed examples of possible implementations, it should be noted that these details are intended to be exemplary and not to limit the scope of the application in any way.

[0025] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.

[0026] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a “station” and / or “STA”, which may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

[0027] The communication system 100 may also include a base station 114a and / or a base station 114b. Each base station 114a, 114b may be any type of device configured to facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), and wireless routers, among others. Although each base station 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.

[0028] The base station 114a may be part of the RAN 104 / 113, and the RAN may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals may be transmitted and / or received in a desired spatial direction.

[0029] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0030] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using new radio (NR).

[0033] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0034] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), and GSM EDGE (GERAN), among others.

[0035] Figure 1AThe base station 114b in the example may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, and the like). Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not need to access the Internet 110 via the CN 106 / 115.

[0036] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0037] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer network devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet Protocol Suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the other networks 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as the RAN 104 / 113.

[0038] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0039] Figure 1B is a system diagram showing an example WTRU 102. Figure 1B As shown, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing components while remaining consistent with an embodiment.

[0040] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, however it should be appreciated that the processor 118 and the transceiver 120 may also be integrated into one electronic component or chip.

[0041] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in an embodiment, the transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In an embodiment, the transmit / receive component 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.

[0042] Although in Figure 1B 102 as a single component, but the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving radio signals over the air interface 116.

[0043] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive component 122 and to demodulate signals received by the transmit / receive component 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0044] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. The processor 118 may also output user data to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store information in any suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memories that are not physically located in the WTRU 102, such as, for example, a server or a home computer (not shown).

[0045] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power for use by other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0046] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be appreciated that the WTRU 102 may acquire location information via any suitable positioning method while remaining consistent with an embodiment.

[0047] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. The peripherals 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0048] The WTRU 102 may include a full-duplex radio in which the reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous for the radio. The full-duplex radio may include an interference management unit 139 that reduces and / or substantially eliminates self-interference by means of hardware (e.g., chokes) or by signal processing by a processor (e.g., a separate processor (not shown) or by the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio that transmits and receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)).

[0049] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c using an E-UTRA radio technology over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0050] The RAN 104 may include eNode-Bs 160a, 160b, 160c, however it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0051] Each eNodeB 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0052] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing components is described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.

[0053] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, performing bearer activation / deactivation processing, and selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0054] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during inter-eNB handovers, triggering paging processing when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0055] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0056] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or be in communication with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0057] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain typical embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.

[0058] In a typical embodiment, the other network 112 may be a WLAN.

[0059] A WLAN using an infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or be connected to a distributed system (DS) or other types of wired / wireless networks that send services into and / or out of the BSS. Services originating from outside the BSS and destined for the STA may be reached by the AP and delivered to the STA. Services originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Services between STAs within the BSS may be sent through the AP, for example, the source STA may send services to the AP and the AP may deliver services to the destination STA. Services between STAs within the BSS may be considered and / or referred to as point-to-point services. The point-to-point services may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly therebetween). In certain typical embodiments, the DLS may use 802.11e DLS or 802.11z channelized DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad hoc" communication mode.

[0060] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a width that is dynamically set with the aid of signaling. The primary channel may be a working channel of the BSS and may be used by STAs to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs (e.g., each STA) including the AP may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a specified BSS, one STA (e.g., only one station) may transmit at any given time.

[0061] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).

[0062] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can separate the data into two streams. Inverse fast Fourier transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0063] 802.11af and 802.11ah support working modes below 1 GHz. Compared with 802.11n and 802.11ac, the channel working bandwidth and carrier used in 802.11af and 802.11ah are reduced. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to certain typical embodiments, 802.11ah can support instrument type control / machine type communication, such as MTC devices in macro coverage areas. MTC can have certain capabilities, such as limited capabilities including support (e.g., only support) certain and / or limited bandwidths. MTC devices can include a battery, and the battery life of the battery is higher than a threshold (e.g., for maintaining a very long battery life).

[0064] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), the WLAN system includes a channel that can be designated as a primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a certain STA, where the STA originates from all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz and / or other channel bandwidth operating modes, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the width of the primary channel can be 1MHz. Carrier sensing and / or network allocation vector (NAV) settings can depend on the state of the primary channel. If the primary channel is busy (eg, because a STA (which only supports 1 MHz operating mode) is transmitting to the AP), the entire available band may be considered busy even though most of the band remains idle and available for use.

[0065] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

[0066] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c using NR radio technology over the air interface 116. The RAN 113 may also communicate with the CN 115.

[0067] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may use beamforming processing to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to the WTRU 102a and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit a plurality of component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on an unlicensed spectrum while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0068] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths).

[0069] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.

[0070] Each gNB 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network slicing, implement dual connectivity, implement interworking between NR and E-UTRA, route user plane data to user plane functions (UPFs) 184a, 184b, and route control plane information to access and mobility management functions (AMFs) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.

[0071] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned components is described as part of the CN 115, it should be understood that any of these components may be owned and / or operated by entities other than the CN operator.

[0072] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 182b may use network slicing processing to customize the CN support provided to the WTRU 102a, 102b, 102c based on the type of service used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) using other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0073] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and may configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU / UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0074] The UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide the WTRU 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRU 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering downlink packets, and providing mobility anchor processing, etc.

[0075] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local DNs 185a, 185b via an N3 interface connected to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the data networks (DNs) 185a, 185b and through the UPFs 184a, 184b.

[0076] In view of Figures 1A-1D and about Figures 1A-1D , one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0077] The simulation device can be designed to implement one or more tests about other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices can perform one or more or all functions while being implemented and / or deployed as a part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as a part of a wired and / or wireless communication network. The simulation device can be directly coupled to other equipment to perform the test, and / or can use over-the-air wireless communication to perform the test.

[0078] The one or more simulation devices can perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test lab and / or a test scenario of a wired and / or wireless communication network that is not deployed (e.g., tested) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (as an example, the circuits can include one or more antennas).

[0079] For example, the examples provided herein do not limit the applicability of the present subject matter to other wireless technologies by using the same or different principles as applicable.

[0080] An example 5G network may be described herein. Figure 2 An example architecture of a 5G and / or NextGen network is shown. Figure 2 In the present invention, the radio access network (RAN) may refer to a radio access network based on a 5G radio access technology (RAT) and / or an evolved E-UTRA that may be connected to a next-generation core network. The access control and mobility management function (AMF) may include one or more of the following functions: registration management, connection management, reachability management, and / or mobility management, etc. The session management function (SMF) may include one or more of the following functions: session management (for example, which may include session establishment and / or modification and release), wireless transmit / receive unit (WTRU) Internet Protocol (IP) address allocation, and / or selection and control of user plane (UP) functions, etc. The user plane function (UPF) may include one or more of the following functions: packet routing and forwarding, packet inspection, and / or service usage reporting, etc.

[0081] UPF and / or SMF relocation may be described herein. In deployment, a 5G network may include one or more of the UPFs and / or SMFs. Each UPF and / or SMF may serve an area (e.g., a specific area). During the mobility of the WTRU, if the WTRU moves out of the current UPF and / or SMF service area, the network may assign one or more other UPFs and / or SMFs to serve the WTRU. In some scenarios described herein, the first UPF (or SMF) may be described as an anchor UPF (or SMF), and subsequent UPFs (or SMFs) (e.g., based on mobility) may be described as intermediate UPFs (or SMFs).

[0082] The UPF may change without a corresponding SMF change (e.g., based on mobility), such as Figure 3 can be seen in. Figure 3 An example UPF relocation due to WTRU mobility is shown, where the UPF relocation is performed without SMF changes. Procedures for UPF relocation without SMF changes may be described herein. Figure 3 As shown, a WTRU in UPF service area 1 may establish a protocol data unit (PDU) session with UPF-1, and the WTRU may move to UPF service area 2, where the (e.g., previous) RAN may not be able to (e.g., directly) contact the UPF-1. The network may assign UPF-2 to serve the WTRU.

[0083] If the network maintains the PDU session continuity, the network may assign UPF-2 as an intermediate node, and a channel may be established between UPF-2 and UPF-1, and UPF-2 may forward one or more (e.g., all) data packets between UPF-1 and the WTRU. The UPF (e.g., UPF-1) that initially serves the PDU session may be referred to as an anchor-UPF (A-UPF), and the UPF (e.g., UPF-2) assigned by the network due to WTRU mobility may be referred to as an intermediate-UPF (I-UPF).

[0084] If the network does not maintain the PDU session continuity, the network may inform the WTRU to re-establish the PDU session and may assign UPF-2 as the anchor node for the new PDU session. The old PDU session (eg, the old PDU session associated with UPF-1) may be released.

[0085] This article may describe the process of UPF relocation with SMF changes. Figure 4An example UPF relocation due to WTRU mobility is shown, where the UPF relocation is performed with a SMF change. If the WTRU moves to UPF service area 3, where the UPF-3 cannot be controlled by SMF-1, the network may assign SMF-2 to control UPF-3 for the WTRU's PDU session. If the network assigns SMF-2 to control UPF-3, a channel may be established between UPF-3 (e.g., I-UPF) and UPF-1 (e.g., A-UPF). One or more (e.g., all) data packets between UPF-1 (e.g., A-UPF) and the WTRU may be forwarded by UPF-3 (e.g., I-UPF). The SMF-2 may be referred to as an intermediate SMF (e.g., I-SMF), which controls the I-UPF. The SMF-1 may be referred to as an anchor SMF (e.g., A-SMF), which may control the A-UPF.

[0086] AMF can communicate with SMF, and SMF can communicate with UPF. In the example where there are anchor SMF and intermediate SMF and anchor UPF and intermediate UPF, one or more architectures can be provided, for example, based on the interaction between AMF and SMF.

[0087] Figure 5 An example architecture with multiple SMFs is shown. For example, the AMF may select and / or communicate with the I-SMF. One or more (e.g., all) session management (SM) non-access stratum (NAS) messages received from a WTRU (not shown) may be sent by the AMF to the I-SMF. The I-SMF may collaborate with the A-SMF, for example, to control the data plane.

[0088] Figure 6 An example architecture with multiple SMFs is shown. For example, the AMF may select and / or communicate with the A-SMF. One or more (e.g., all) SM NAS messages received from a WTRU (not shown) may be sent by the AMF to the A-SMF. The A-SMF may collaborate with the I-SMF, for example, to control the data plane.

[0089] During network-triggered service requests, invalid data paths may occur in UPF relocation. Figure 7An example of an invalid data path that occurs in UPF relocation due to WTRU mobility in idle mode is shown. For example, during a network triggered (NW triggered) service request process, the SMF may send UPF information to the current RAN via the AMF. The WTRU may perform a service request process (e.g., in response to being paged). Once awake, the WTRU may enter connected mode and report its location. The SMF may reallocate the UPF (e.g., switch from an old I-UPF to a new I-UPF). In some examples, the SMF may send N2 SM information (e.g., which may include I-UPF channel information) to the AMF in an N11 message. If the SMF sends AMF N2 SM information related to the old I-UPF (e.g., before the WTRU service request and / or before the UPF is reallocated), and if the AMF sends the N2 SM information to the RAN (e.g., related to the old I-UPF), the data path may be invalid (e.g., the RAN may not be able to establish a channel to the old I-UPF).

[0090] The numbers / elements shown in the call flow may be presented for reference purposes. Thus, the numbered actions may be performed in a different order (e.g., in whole or in part) and / or some actions may be skipped.

[0091] Figure 8 An exemplary network-triggered (NW-triggered) service request procedure is shown. Figure 8 0) and the I-UPF receives downlink data for the PDU session (e.g., at 1), the network may initiate a NW-triggered service request process by paging the WTRU and / or establishing a PDU data path.

[0092] When the WTRU is in an idle state, the WTRU may move out of a service area (e.g., the service area of ​​the old I-UPF). When the WTRU is in an idle state, if the WTRU moves out of the service area of ​​the old I-UPF, then Figure 8 The tunnel established in the exemplary process shown (e.g., between the RAN and the old I-UPF) may not be established correctly. For example, the tunnel established between the RAN and the old I-UPF may not be established correctly because the RAN serving the WTRU may not be able to communicate with the old I-UPF. If the tunnel is not established correctly, packets for one or more WTRUs may be dropped.

[0093] When the WTRU is idle, signaling (e.g., additional signaling) in the UPF relocation with SMF change may occur. When the WTRU enters the idle state, the data path for the PDU session between the RAN and the I-UPF may be released, and the data path between the I-UPF and the A-UPF may be maintained. For example, in Figure 5 In the exemplary architecture shown, if the WTRU moves out of the I-SMF service area (e.g., moves to the service area of ​​a new I-SMF (not shown)) during the WTRU's mobility, the AMF may select a new I-SMF and the new I-SMF may initiate one or more N9 data path switching procedures. For example, the N9 data path switching procedure may select a new I-UPF and may update the A-UPF (e.g., the N9 channel information stored in the A-UPF).

[0094] The WTRU may be in an idle state and have no data packets. The WTRU may continue to move out of the new I-UPF service area (e.g., the N9 data path switching process may not be required). One or more N9 data path switching processes described herein may be skipped (e.g., to reduce additional unnecessary messages).

[0095] Figure 5 and Figure 6 The I-SMF and / or A-SMF described in the specification may process one or more different messages from the AMF, or process one or more different messages sent to the AMF. For example, the I-SMF may generate an N11 message for downlink data notification (e.g., because the I-UPF may be controlled by the I-SMF). The A-SMF may process a resource request message from the AMF (e.g., because the A-SMF may be an endpoint for communicating with a policy framework and / or a charging system).

[0096] SMF (e.g. Figure 5 I-SMF or Figure 6 The A-SMF of the architecture can communicate with the AMF (e.g., directly). Figure 5 In the one or more SMF architectures shown, one or more (e.g., all) resource request related messages from AMF may (e.g., must) be passed from I-SMF to A-SMF. Figure 6 In the one or more SMF architectures shown, one or more (e.g., all) service request related messages from the I-SMF can (e.g., must) be passed by the A-SMF to the AMF.

[0097] UPF relocation during network-triggered service requests may be implemented.

[0098] For example, when receiving a downlink data notification from the I-UPF, and if the SMF cannot determine whether the UPF will be relocated, the SMF may not send the N2SM information (e.g., which may include the I-UPF channel information) to the AMF in the N11 message. The AMF may initiate a paging procedure to the WTRU. If the AMF receives a service request from the WTRU and the AMF does not receive the N2 SM information from the SMF, the AMF may provide the WTRU location to the SMF. The SMF may send the N2 SM information (e.g., when the UPF is relocated).

[0099] Fig. 9 An example UPF relocation during a network triggered service request procedure is shown.The WTRU may have established a PDU session via the old I-UPF and A-UPF, and the WTRU may be in an idle state (eg, at 0).

[0100] The old I-UPF may receive downlink (DL) data for the PDU session (e.g., at 1). The old I-UPF may notify the SMF of the DL data event (e.g., at 2). The SMF may send an N11 message to indicate that DL data is received (e.g., at 3). The SMF may not be able to determine whether the WTRU is in the service area of ​​the UPF (e.g., because the SMF may not know the current location of the WTRU). If the SMF cannot determine whether the UPF will be relocated, the SMF may not include the N2 SM information (e.g., in the N11 message).

[0101] The SMF may include a WTRU location request indication to request (e.g., explicitly request) the WTRU and the AMF to perform one or more procedures associated with the WTRU location (e.g., at 9-13). The AMF may perform a paging procedure (e.g., at 4 and / or 5). The WTRU may send a service request to the AMF (e.g., at 6 and / or 7). The RAN may include the WTRU location in the message. The AMF may determine whether to request SM information (e.g., N2 SM information) from the SMF (e.g., at 9-13) based on, for example, whether SM information (e.g., N2 SM information) is received at 3. If the N2 SM information is not received, the AMF may continue to send the N11 message to the SMF (e.g., at 9). If the N2 SM information is received, one or more of the procedures / messages from 9 to 13 may be skipped. The AMF may send an N11 message with the WTRU location to the SMF (e.g., at 9). The SMF may determine whether the I-UPF is relocated based on the WTRU location and may update the N4 session with the A-UPF (e.g., at 10-12). A data path may be established (eg, at 13-18).

[0102] Fig.10An example of UPF relocation during a network-triggered service request process is shown. For example, when a downlink data notification is received from an I-UPF, and if the SMF cannot determine whether the UPF will be relocated, the SMF may send SM information (e.g., N2 SM information) to the AMF. The SM information (e.g., N2 SM information) may indicate the validity area of ​​the N2 information and may include an available area (e.g., a current I-UPF service area or a tracking area / cell list set). The AMF may receive a service request from a WTRU (e.g., after paging), and the AMF may determine whether the WTRU is located in the available area of ​​the N2 SM information (e.g., based on the WTRU location information determined from the service request). The AMF may determine whether to update the N2 SM information. The AMF may determine the N2 SM information to request for update. The AMF may determine to use the N2 SM information received in 3 (e.g., in 8) for the WTRU based on the WTRU location.

[0103] If the WTRU is not located within the available area of ​​the N2 SM information from the SMF (e.g., if the AMF determines based on the N2 SM information that the WTRU is not located within the available area), the AMF may send the WTRU location to the SMF and may request updated N2 SM information from the SMF (e.g., via Fig.10 one or more of 9-13 in ).

[0104] If the WTRU is located in an available area for the N2 SM information (e.g., if the AMF determines that the WTRU is located in the available area based on the N2 SM information (e.g., received in 3), the AMF may forward the N2 SM information (e.g., may forward an N2 request (e.g., which may include the N2 SM information in 14)) to the RAN (e.g., 14 (e.g., skipping 9-13)). The WTRU and the RAN may establish a radio resource control (RRC) connection (e.g., at 15) and establish a channel from the A-UPF to the new I-UPF for data packets.

[0105] Compare Fig.10 and Fig. 9 Many elements of the process are similar. Fig.10 and Fig. 9 , 3 and 8 are different. For example, in Fig.10 In (e.g., at 3), the SMF may include N2SM information (e.g., old I-UPF channel information) and / or related availability areas (e.g., old I-UPF node service area, WTRU tracking area, or RAN cell coverage area). Fig.10In (e.g., at 8), the AMF may determine whether the N2 SM information is available for the WTRU based on the WTRU location.

[0106] In one example, the AMF may receive the UPF service area information from the SMF at the time of PDU session establishment. The AMF may store the UPF service area information with the corresponding PDU session ID. The AMF may use the stored UPF service area information during the service request procedure to determine whether the WTRU is located in the UPF service area (e.g., Fig.10 8 in ), to determine whether the received N2 SM information (e.g., in 3) is available to the WTRU based on the WTRU location. If the WTRU is not located in the received UPF service area, the AMF may request new SM information (e.g., N2 SM information) from the SMF (e.g., through one or more 9-13).

[0107] Fig.11 An example of UPF relocation during a network-triggered service request process is shown. For example, the SMF may receive a downlink data notification from the I-UPF (e.g., at 2). The SMF may send SM information (e.g., N2 SM information) to the AMF (e.g., via an N11 message; 3). The WTRU may be paged (e.g., 4-5). The AMF may receive a service request from the WTRU (e.g., 6-7), and the AMF may forward the SM information (e.g., N2 SM information) to the RAN (e.g., 8). The AMF may provide the WTRU location to the SMF (e.g., at 11). The SMF may determine whether the I-UPF is relocated. If the SMF determines that the I-UPF is relocated, the SMF may notify the RAN about the updated N2 SM information.

[0108] like Fig.11As shown, at 11, the AMF may include the WTRU location in the N11 message. When the SMF receives the WTRU location from the AMF (e.g., at 11), the SMF may determine whether to perform I-UPF relocation (e.g., at 12). If the SMF determines that the I-UPF is not relocated, one or more of 13-14 may be skipped (e.g., because it may not be necessary to determine a new I-UPF). If the SMF determines that the I-UPF is relocated, the SMF may determine a new I-UPF based on the WTRU location information (e.g., at 13). The SMF may update the N4 session with the A-UPF (e.g., at 14). When the SMF performs UPF selection (e.g., in 12), the SMF may include updated N2 SM information (e.g., if any, in 15). For example, the updated N2 SM information may include channel information of the new I-UPF. If the AMF receives new N2 SM information (e.g., in 15), the AMF may forward the new N2 SM information to the RAN to update the N2 SM information. The RAN node may reply to the AMF. For example, upon receiving the N2 SM tunnel information, the RAN node may reply to the AMF using an N2 confirmation (ACK) message.

[0109] When the WTRU is idle, signaling (eg, additional signaling) in UPF relocation with SMF change may be reduced. Fig.12 An exemplary N9 data path release procedure is shown. For example, if the AMF determines that the N9 data path may not be maintained, the SMF may trigger the N9 data path release. For example, the WTRU may move out of the I-UPF service area (e.g., the N9 data path maintenance may be skipped). The N9 release indication may be included in the N11 PDU session deactivation request. The N9 release indication may instruct the I-SMF to release the N3 data path and / or release the N9 data path. When the N9 data path is released, additional signaling in a UPF relocation with SMF change (e.g., when the WTRU is idle) may be skipped. When the AMF selects an I-SMF (e.g., such as Figure 5 The processes described herein may be available when communicating with the architecture described in (or through the I-SMF).

[0110] Can be Fig.12 The N9 data path release procedure shown provides one or more of the following elements. The WTRU may communicate with the I-SMF and / or A-SMF (e.g., Fig.12The AMF may release the N9 data path based on the WTRU status. The AMF may release the N9 data path when the N2 interface is released. The AMF may release the N9 data path based on one or more local policies.

[0111] The AMF may send a PDU session deactivation request (e.g., N11 PDU session deactivation request) to the I-SMF (e.g., in 3). The N11 PDU session deactivation request may include a release indication (e.g., N9 release indication). The N11 PDU session deactivation request may include an AMF ID and may be forwarded to the A-SMF. When the N9 data path is released, the AMF ID may be used for (e.g., directly) communication between the A-SMF and the AMF. The I-SMF may send an N11 PDU deactivation request to the A-SMF (e.g., in 4). The N11 PDU deactivation request may include an AMF ID. When the A-SMF receives the deactivation request message, the A-SMF may store the AMF ID for future communication with the AMF (e.g., when the N9 data path is released). The A-SMF may modify the N4 session with the A-UPF to release the N9 data path (e.g., in 5). The A-SMF may send a response to the I-SMF (e.g., in 6). For example, the A-SMF may send a PDU Deactivation Confirmation Response to the I-SMF. The I-SMF may modify the N4 session with the I-UPF to release one or more (e.g., all) WTRU contexts, including the N9 data path (e.g., in 7). The I-SMF may remove the WTRU context stored in the I-SMF.

[0112] The AMF may (e.g., directly) send a PDU session deactivation request (e.g., N11 PDU session deactivation request) to the A-SMF. Fig.123'. The AMF ID may be included so as to be forwarded to the A-SMF. For example, when the N9 data path is released, the A-SMF may communicate directly with the AMF based on the AMF ID. The A-SMF may modify the N4 session with the A-UPF to release the N9 data path (e.g., in 4'). The A-SMF may send a response to the AMF (e.g., in 5'). For example, the A-SMF may send an N11 PDU confirmation response to the AMF. The AMF may send an N11 PDU session deactivation request to the I-SMF (e.g., in 6'). The N11 PDU session deactivation request may include an N9 release indication. The I-SMF may modify the N4 session with the I-UPF to release one or more (e.g., all) WTRU contexts, including the N9 data path (e.g., in 7'). The I-SMF may remove the WTRU context stored in the I-SMF.

[0113] Fig.13 An example architecture with one or more SMFs is shown. For example, the AMF may communicate with the A-SMF and / or the I-SMF. During the PDU session establishment, registration process, and / or AMF relocation process, the AMF ID may be provided to the A-SMF and / or the I-SMF. The A-SMF and / or the I-SMF may know the AMF ID (e.g., Fig.12 shown). Fig.13 The architecture shown may allow A-SMF and / or I-SMF to interact with AMF for a specific PDU session. The AMF ID may be passed to the A-SMF and / or I-SMF. One or more of the following processes may be performed to communicate to the A-SMF and / or I-SMF using the AMF ID.

[0114] Fig.14 An example AMF ID provided to the A-SMF by the I-SMF is shown. For example, the AMF ID may be provided to the I-SMF (e.g., first) and then to the A-SMF. The WTRU may generate a PDU Session Establishment Request (e.g., Fig.14 1). The PDU session establishment request may include a PDU session ID and / or a service and session continuity (SSC) mode. The AMF may perform SMF selection to select A-SMF and / or I-SMF (e.g., 2). The AMF may send a PDU session establishment request to the I-SMF in an N11 message (e.g., 3). The AMF may include the AMF ID in the message. The I-SMF may send SM information and / or the AMF ID related to the PDU session to the A-SMF (e.g., 4). The A-SMF may store the AMF ID for future communication directly with the AMF. The A-SMF may establish a connection with the A-UPF (e.g., Fig.14The PDU Session Establishment Accept message may be sent back to the I-SMF (e.g., 6). The I-SMF may establish a session (e.g., N4 session) with the I-UPF (e.g., 7). A channel between the RAN and the I-UPF may be established (e.g., 8-11).

[0115] Fig.15 An example AMF ID provided to A-SMF by I-SMF is shown. For example, the AMF ID may be provided to A-SMF first and then to I-SMF. Fig.15 One or more of the elements shown in Fig.14 The one or more elements shown in are the same as those shown in (e.g., except that the AMF ID may be provided to the A-SMF first and then the AMF ID may be provided to the I-SMF).

[0116] Although the features and elements are described above in particular combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor memory devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and optical media (e.g., CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU (e.g., UE), terminal, base station, RNC, or any host computer.

Claims

1. An access control and mobility management function AMF node, the AMF node comprising: A processor, the processor being configured to: receiving a session management (SM) message from a session management function (SMF) node, wherein the SM message indicates an available area for session information; receiving a service request from a wireless transmit receive unit WTRU; sending a request for updated SM information from the SMF node based on determining that the WTRU is outside the availability area for the session information by using the WTRU location information determined from the service request; updating the SM information using the updated SM information received from the SMF node; as well as The SM information is sent to an access network associated with the WTRU.

2. The AMF node according to claim 1, wherein the available area for the session information is one or more of the following: a user plane function (UPF) node serving area, a WTRU tracking area, or a radio access network (RAN) cell coverage area.

3. The AMF node according to claim 1, wherein the available area for the session information is an intermediate user plane function (UPF) node serving area.

4. The AMF node according to claim 3, wherein when the AMF node receives the SM information, the WTRU is in idle mode, and wherein a protocol data unit (PDU) session is maintained between the intermediate UPF node and the anchor UPF node.

5. The AMF node according to claim 1, wherein: The processor is further configured to store a session identifier and a node service area.

6. The AMF node according to claim 1, wherein the processor is further configured to send the location of the WTRU to the SMF node.

7. The AMF node according to claim 1, wherein: The processor is further configured to receive an ACK message for the SM information from an access network.

8. A method for network-triggered service request, the method comprising: At an access control and mobility management function AMF node, receiving session management (SM) information from a session management function (SMF) node, wherein the SM information includes an available area for session information; At the AMF node, receiving a service request from a wireless transmit receive unit WTRU; sending, at the AMF node, a request for updated SM information from the SMF node based on determining that the WTRU is outside the availability area for the session information by using the WTRU location information determined from the service request; updating the SM information using the updated SM information received from the SMF node; as well as Send SM information to an access network associated with the WTRU.

9. The method of claim 8 further comprising paging the WTRU.