WO2017197372A1

WO2017197372A1 - Methods, apparatuses and system directed to supporting interaction of various types of mobility in next generation wireless networks

Info

Publication number: WO2017197372A1
Application number: PCT/US2017/032565
Authority: WO
Inventors: Guanzhou Wang; Mahmoud Watfa; Ulises Olvera-Hernandez
Original assignee: IDAC Holdings Inc
Current assignee: IDAC Holdings Inc
Priority date: 2016-05-13
Filing date: 2017-05-12
Publication date: 2017-11-16
Anticipated expiration: 2018-11-13

Abstract

Methods, apparatuses, systems, devices, and computer program products directed to supporting various types of mobility in next generation wireless networks are provided. Among new methodologies and/or technologies provided herein is a method implemented in a network that supports network layer mobility management and that includes in a mobility management function (MMF), which method includes receiving, at the MMF from a wireless transmit/receive unit (WTRU), a first message indicating support for non-network layer mobility management; determining, at the MMF, the WTRU is approved to use the non-network layer mobility management; and receiving, at the MMF from the WTRU, a second message indicating an approval to use the non-network layer mobility management. In an embodiment, the method may include performing a procedure and/or configuring the network to support non-network layer mobility management.

Description

METHODS, APPARATUSES AND SYSTEM DIRECTED TO SUPPORTING INTERACTION OF VARIOUS TYPES OF MOBILITY IN NEXT GENERATION

WIRELESS NETWORKS

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62/336,556 filed 13-May-2016 (Attorney Docket Reference 13101US01), which is incorporated herein by reference.

BACKGROUND

[0002] Field

[0003] This application is related to wireless communication, and more particularly, to methods, apparatuses, systems, devices, and computer program products directed to supporting various types of mobility in wireless networks, such as next generation wireless networks.

[0004] Related Art

[0005] In legacy wireless networks, the mobility framework is designed and optimized for human communication and assumes a paradigm that all wireless terminals roam at one particular speed. There is no differentiation in mobility support for wireless terminals that have various mobility levels. A universal mobility framework is applied to all the devices regardless of their mobility levels or whether or not the devices need service continuity. The mobility framework for a next generation wireless networks and/or communications system should support different types of device mobility and provide different mobility solutions.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref ") in the Figures indicate like elements, and wherein:

[0007] FIG. 1 A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented;

[0008] FIG. IB is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0009] FIGs. 1C, ID and IE are system diagrams of example radio access networks and example core networks that may be used within the communications system illustrated in FIG. 1 A; [0010] FIG. 2 illustrates an example environment in which embodiments may be practiced or implemented;

[0011] FIG. 3 illustrates an example of a gateway tunnel protocol (GTP) based mobility support mechanism for a long term evolution (LTE) evolved packet core (EPC) of a communications system;

[0012] FIG. 4 is a flow diagram illustrating an example session initiation protocol (SIP) re- INVITE procedure for terminal mobility;

[0013] FIG. 5 illustrates a protocol stack including a Host Identity Layer situated between an internet protocol (IP) layer and transmission control protocol (TCP) layer;

[0014] FIG. 6 illustrates an example multipath TCP (MPTCP) operation;

[0015] FIG. 7 is a flow diagram illustrating an example procedure for negotiating non-network layer mobility management in a network that supports network layer mobility management;

[0016] FIG. 8 is a flow diagram illustrating an example procedure for negotiating non-network layer mobility management in a network that supports network layer mobility management;

[0017] FIG. 9 is a flow diagram illustrating an example procedure for negotiating non-network layer mobility management in a network that supports network layer mobility management;

[0018] FIG. 10 is a flow diagram illustrating an example procedure for carrying IP address location at a (radio) access network ((R)AN);

[0019] FIG. 11 is a flow diagram illustrating an example procedure for carrying IP address location at a (R)AN; and

[0020] FIG. 12 illustrates an example high level procedure for location tracking when using non- network layer mobility management.

DETAILED DESCRIPTION

[0021] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. [0022] Example Communications System

[0023] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. Wired networks are well-known. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1E, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

[0024] FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented. Example communications system 100 is provided for the purpose of illustration only and is not limiting of the disclosed embodiments. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ 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), and the like.

[0025] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.

[0026] The communications systems 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node- B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0027] The base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the 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, i.e., one for each sector of the cell. In another embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0028] 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, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0029] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0030] In another 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 LTE- Advanced (LTE- A).

[0031] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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), GSM EDGE (GERAN), and the like.

[0032] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 1 14b may not be required to access the Internet 110 via the core network 106.

[0033] The RAN 104 may be in communication with the core network 106, 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 of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 and/or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing an E-UTRA radio technology, the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology. [0034] The core network 106 may also serve 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 circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired or wireless communications networks owned and/or operated by other service providers. For example, the networks 1 12 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in FIG. 1A 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.

[0036] FIG. IB is a system diagram of an example WTRU 102. Example WTRU 102 is provided for the purpose of illustration only and is not limiting of the disclosed embodiments. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 106, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0037] 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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, 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. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0038] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0039] In addition, although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MTMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0040] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

[0041] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 106 and/or the removable memory 132. The non-removable memory 106 may include random-access memory (RAM), readonly 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0042] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the 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 (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0043] 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) regarding 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 over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0044] The processor 118 may further be coupled to other peripherals 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 peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0045] FIG. 1C is a system diagram of the RAN 104 and the core network 106 according to an embodiment. As noted above, the RAN 104 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 106. As shown in FIG. 1C, the RAN 104 may include Node-Bs 140a, 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 104. The RAN 104 may also include RNCs 142a, 142b. It will be appreciated that the RAN 104 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment. [0046] As shown in FIG. 1C, the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b. The Node-Bs 140a, 140b, 140c may communicate with the respective RNCs 142a, 142b via an Iub interface. The RNCs 142a, 142b may be in communication with one another via an Iur interface. Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected. In addition, each of the RNCs 142a, 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, and the like.

[0047] The core network 106 shown in FIG. 1C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

[0048] The RNC 142a in the RAN 104 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 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.

[0049] The RNC 142a in the RAN 104 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0050] As noted above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

[0051] FIG. ID is a system diagram of the RAN 104 and the core network 106 according to another embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 106. [0052] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each 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 MTMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0053] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. As shown in FIG. ID, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0054] The core network 106 shown in FIG. ID may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

[0055] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI 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, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. 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 or WCDMA.

[0056] The serving gateway 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like. [0057] The serving gateway 164 may also be connected to the PDN gateway 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.

[0058] The core network 106 may facilitate communications with other networks. For example, the core network 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 core network 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN 108. In addition, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

[0059] FIG. IE is a system diagram of the RAN 104 and the core network 106 according to another embodiment. The RAN 104 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. As will be further discussed below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 104, and the core network 106 may be defined as reference points.

[0060] As shown in FIG. IE, the RAN 104 may include base stations 170a, 170b, 170c, and an ASN gateway 172, though it will be appreciated that the RAN 104 may include any number of base stations and ASN gateways while remaining consistent with an embodiment. The base stations 170a, 170b, 170c may each be associated with a particular cell (not shown) in the RAN 104 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the base stations 170a, 170b, 170c may implement MIMO technology. Thus, the base station 170a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. The base stations 170a, 170b, 170c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 172 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 106, and the like. [0061] The air interface 116 between the WTRUs 102a, 102b, 102c and the RAN 104 may be defined as an Rl reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 106. The logical interface between the WTRUs 102a, 102b, 102c and the core network 106 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.

[0062] The communication link between each of the base stations 170a, 170b, and 170c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the base stations 170a, 170b, 170c and the ASN gateway 172 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0063] As shown in FIG. IE, the RAN 104 may be connected to the core network 106. The communication link between the RAN 104 and the core network 106 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example. The core network 106 may include a mobile IP home agent (MTP-HA) 174, an authentication, authorization, accounting (AAA) server 176, and a gateway 178. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

[0064] The MIP-HA 174 may be responsible for IP address management, and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and/or different core networks. The MIP-HA 174 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. The AAA server 176 may be responsible for user authentication and for supporting user services. The gateway 178 may facilitate interworking with other networks. For example, the gateway 178 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. In addition, the gateway 178 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers. [0065] Although not shown in FIG. IE, it will be appreciated that the RAN 104 may be connected to other ASNs and the core network 106 may be connected to other core networks. The communication link between the RAN 104 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 104 and the other ASNs. The communication link between the core network 106 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.

[0066] FIG. 2 illustrates an example communications system 200 in which embodiments may be practiced or implemented. The communications system 200 is provided for the purpose of illustration only and is not limiting of disclosed embodiments. As shown in FIG. 2, the communications system 200 includes a base station 214 and WTRUs 202a, 202b. As would be understood by a person of skill in the art, the communications system 200 may include additional elements not shown in FIG. 2.

[0067] The base station 214 may be any of the base stations 114 (FIG. 1A), Node-Bs 140 (FIG. 1C), eNode-Bs 160 (FIG. ID) and base stations 170 (FIG. IE), for example. The base station 214 may include functionality similar to, and/or different from, the base stations 114, Node-Bs 140, eNode-Bs 160 and base stations 170, as well. For example, the base station 214 may include functionality to support features of 5G and to implement the procedures, techniques, etc. included herein.

[0068] The base station 214 may be configured for small cell operation and/or deployment. The base station 214 may be configured to support any of centimeter wave (cmW) and millimeter wave (mmW) operation. For simplicity of exposition, the term "xmW" may be used herein to refer to any of cmW and mmW. The base station 214 may be additionally and/or alternatively configured to support various (e.g., all or some) functionality and/or features for small cell operation and/or deployment as specified in 3GPP Release 12 and newer releases. In this regard, the base station 214 may be capable of operating an xmW air interface in parallel, simultaneously and/or otherwise in connection with an LTE, LTE-A or like-type (collectively "LTE") air interface. The base station 214 may be equipped with at least one of various advanced antenna configurations and beamforming techniques, such as those that may allow the base station 214 to simultaneously transmit LTE downlink channels in a wide beam pattern and xmW channels in one or more narrow beam patterns. The base station 214 may also be configured to utilize an LTE uplink configuration adapted with features and procedures (e.g., those detailed herein) to support WTRUs that lack, or do not use their, xmW uplink transmission capabilities.

[0069] Each of the WTRUs 202a, 202b may be any of the WTRUs 102 (FIGs. 1A-1E), for example. Each of the WTRUs 202a, 202b may include functionality similar to, and/or different from, the WTRUs 102, as well. The WTRUs 202a, 202b may include functionality to support features of 5G and to implement the procedures, techniques, etc. included herein. For simplicity of exposition, when "WTRU 202" is used herein, it may refer to any of the WTRUs 202a, 202b.

[0070] Each of the WTRUs 202a, 202b may be configured to support xmW operation. The WTRUs 202a, 202b may be further configured to support various (e.g., all or some) functionality and/or features for user equipment operation and/or deployment as specified in 3GPP Release 12. Each of the WTRUs 202a, 202b may be capable of operating LTE and xmW air interfaces in parallel, simultaneously and/or otherwise in connection with each other. Each of the WTRUs 202a, 202b may have two sets of antennas and accompanying RF chains; one configured for operating in a LTE band and the other configured for operating in a xmW frequency band. However, the present disclosure is not limited thereto, and a WTRU may have any number of sets of antennas and accompanying RF chains. Each of the WTRUs 202a, 202b may include one or more baseband processors, and the baseband processors may include separate, or at least partially combined, functionality for baseband processing of the LTE frequency band and the xmW frequency band. The baseband processing functions may share hardware blocks for the xmW and LTE air interfaces, for example.

[0071] Introduction

[0072] The mobility management framework of a conventional core network, such as the evolved packet core (EPC), is based on a network (e.g., IP) layer mobility support mechanism, namely, the gateway tunnel protocol (GTP). FIG. 3 is a block diagram illustrating an example of a GTP -based mobility support mechanism for an LTE EPC 306 of a communications system 300. The GTP- based mobility support mechanism, LTE EPC 306 and communications system 300 are provided for the purpose of illustration only and are not limiting of disclosed embodiments.

[0073] The LTE EPC 306 may include a mobility anchor 366, an SGW 364 and an MME 362. The mobility anchor 366 may be, for example, a PGW as shown, or a centralized network entity. In addition to the LTE EPC 306, the communications system 300 may include a RAN 304 currently serving a WTRU 302 having established a PDN connection with a PDN 312. As would be understood by a person of skill in the art, the communications system 300, RAN 304, and/or the LTE EPC 306 may include additional elements not shown in FIG. 3.

[0074] During, or in connection with, establishment of the PDN connection, the WTRU 302 may attach to the mobility anchor 366, the WTRU 302 may be allocated an IP address ("IP1 ") by the mobility anchor 366, and a GTP tunnel 301 may be established between the mobility anchor 366 and the access network 304 currently serving the WTRU 302. The GTP tunnel 301 may include an S5 segment 303 and an SI segment 305. The S5 segment 303 may be between, and may define respective endpoints at, the mobility anchor 366 and a SGW 364. The SI segment 305 may be between, and may define respective endpoints at the SGW 364 and the access network 304 currently serving the WTRU 302.

[0075] Following connection establishment, the WTRU 302 may remain attached to the mobility anchor 366 when moving around, .e.g., between eNodeBs 360a, 360b. The IP address, IP1, may be used as both an identifier and address locator of the WTRU 302.

[0076] The WTRU 302 may trigger a serving access network change responsive to a change in physical location (e.g., with respect to respective coverage areas of cells associated with the eNodeBs 360a, 360b). The serving access network change may be, for example, an inter-eNodeB in-session handover, a tracking area update (TAU) procedure (e.g., one that involves a SGW reallocation), and the like. The GTP -based mobility support mechanism of the LTE EPC 306 may be used to facilitate the serving access network change, or alternatively, be used in connection with the serving access network change being carried out.

[0077] Pursuant to the GTP -based mobility support mechanism, one or more segments of the GTP tunnel 301, except for the attachment to the mobility anchor 366, may be relocated (e.g., torn down and re-established; tunnel endpoints reassigned, etc.) to accommodate the change in the location of the WTRU 302. In the example shown, the SI segment 305 may be relocated from between the SGW 364 and the eNodeB 360a to between the SGW 364 and the eNodeB 360b. A consequence of the GTP -based mobility support mechanism is that, for data to be exchanged between the WTRU 302 and the PDN 312 , the data need only to follow the initially established and/or re-established (collectively "(re-)established") GTP tunnel. The WTRU IP address, IPl, remains unchanged when the WTRU 302 moves across access networks, and tunnel management is transparent to the WTRU 302. [0078] Representative Mobility for Next Generation Networks

[0079] Although a universal mobility framework akin to those used in legacy mobility frameworks might be sufficient, a mobility framework of a next generation network and/or communications system may support (e.g., may include various mobility and/or mobility management mechanisms and/or procedures to provide, facilitate or otherwise support) additional or different types of mobility. Supporting additional or different types of mobility may be beneficial for a variety of reasons. Among the variety of reasons is avoidance of computational, storage and signaling costs (or alternatively freeing up of such resources that would otherwise be) associated with traditional network layer mobility support or other one-size-fits-all mobility support. For example, not all WTRUs have the same level of mobility ("mobility level"); some WTRUs may move at high speed, some WTRUs may follow nomadic patterns, and some WTRUs may be stationery. Alternatively, some or all of the WTRUs may be at different mobility levels at different times. Using different mobility support mechanisms for different mobility levels (e.g., high mobility, medium mobility, low mobility, no mobility and mobility on demand) may allow for efficiencies over traditional network layer mobility support or other one-size-fits-all mobility support. The efficiencies may result from not having the computational, storage and/or signaling compromises and/or resource wastage designed into the traditional network layer mobility support or other one-size-fits-all mobility support.

[0080] As another example, different applications and/or services being used by a WTRU may be able to handle mobility events at the application layer. Using such mobility support mechanisms, alone or in combination with other non-network-layer mobility support mechanisms, may allow for efficiencies over traditional network layer mobility support or other one-size-fits-all mobility support, e.g., due to not needing the traditional network layer mobility support.

[0081] Overview

[0082] This disclosure is drawn, inter alia, to methods, apparatuses, systems, devices, and computer program products directed to supporting various types of mobility in next generation communication systems. Among the new methodologies and/or technologies provided herein are various methods, apparatuses, systems, devices, and computer program products that may be implemented in a communications system to support various types of mobility management. The various types of mobility management may include any of a (e.g., traditional) network layer mobility management and a mobility management other than the network layer mobility management (also referred to herein as "non-network-layer mobility management").

[0083] Among the new methodologies and/or technologies provided herein is a method implemented in a network that supports the various types of mobility management, including, for example, network layer mobility management and that includes in a mobility management function. As used herein, the terms "mobility management function" and its abbreviation, "MMF", may refer to one or more network elements that are configured to and/or carry out network access and/or mobility management functionality, including any attributed functionally disclosed herein and/or in accordance (or in connection) with such disclosed functionality. The MMF, for example, may carry out network access and/or mobility management functionality akin to an LTE MME and/or a 5G access and mobility management function (AMF) along with any attributed functionally disclosed herein and/or in accordance (or in connection) with such disclosed functionality.

[0084] The method may include receiving, at the MMF from a wireless transmit/receive unit (WTRU), a first message indicating any of (i) support for non-network layer mobility management, (ii) to forego the network layer mobility management, and (iii) application information related to the non-network layer mobility management. The method may also include determining, at the MMF, that the WTRU is approved to use the non-network layer mobility management (e.g., based on any of subscription information associated with the WTRU and an application server verification). The method may further include receiving, at the MMF from the WTRU, a second message indicating an approval to use the non-network layer mobility management.

[0085] In an embodiment, the method may include performing a procedure and/or configuring the network to support non-network layer mobility management. In an embodiment, performing a procedure and/or configuring the network to support non-network layer mobility management may include any of: reserving, or allocating in-advance, one or more IP addresses in one or more adjacent (radio) access network ((R)ANs) to hasten IP address allocation when the WTRU moves to one of the (R)ANs; performing idle mode location tracking; and performing connected mode location tracking.

[0086] In an embodiment, determining that the WTRU is approved to use the non-network layer mobility management may include determining whether the WTRU is authorized to use the non- network layer mobility management. In an embodiment, determining that the WTRU is approved to use the non-network layer mobility management may include verifying with an application server that the application server supports the non-network layer mobility management.

[0087] In an embodiment, the method may further include foregoing procedures to support network layer mobility management for the WTRU. In an embodiment, the second message may also indicate network layer mobility management is not supported for the WTRU. In an embodiment, the first message may be an attach message. In an embodiment, the second message may be an attach accept message. In an embodiment, the first message may also indicate a non- network layer mobility support mechanism.

[0088] In an embodiment, the method may further include receiving, from the WTRU, a third message indicating a non-network layer mobility support mechanism. In an embodiment, the non- network layer mobility support mechanism may be any of an application layer mobility support mechanism, a transport layer mobility support mechanism and a host identity layer mechanism.

[0089] In an embodiment, the first message may also indicate non-network layer mobility configuration information.

[0090] In an embodiment, the method may further include receiving, from the WTRU, a third message indicating non-network layer mobility configuration information. In an embodiment, the non-network layer mobility configuration information may include any of a list of application identifiers (IDs) that will be running on the WTRU, a list of service IDs that will be running on the WTRU, application user information, transport address information of an application server of each application, and a non-network layer mobility support mechanism used by each application.

[0091] In an embodiment, the first message may be a service request message. In an embodiment, the second message may be a non-access stratum message.

[0092] In an embodiment, the method may further include receiving, at the MMF from the WTRU, a fourth message indicating a request for network layer mobility management; and sending, from the MMF to the WTRU, a fifth message confirming support for network layer mobility management.

[0093] Among new methodologies and/or technologies provided herein is a method that may be implemented in a WTRU and that may include sending, to a MMF of a network that supports network layer mobility management, a first message indicating support for non-network layer mobility management; and receiving, from the MMF, a second message indicating an approval to use the non-network layer mobility management. [0094] In an embodiment, the second message may also indicate network layer mobility management is not supported for the WTRU. In an embodiment, the first message may be an attach message. In an embodiment, the second message may be an attach accept message. In an embodiment, the first message may also indicate a non-network layer mobility support mechanism.

[0095] In an embodiment, the method may further include sending, to the MMF, a third message indicating a non-network layer mobility support mechanism. In an embodiment, the non-network layer mobility support mechanism is any of an application layer mobility support mechanism, a transport layer mobility support mechanism and a host identity layer mechanism. In an embodiment, the first message may also indicate non-network layer mobility configuration information.

[0096] In an embodiment, the method may further include sending, to the MMF, a third message indicating non-network layer mobility configuration information. In an embodiment, the non- network layer mobility configuration information may include any of a list of application IDs that will be running on the WTRU, a list of service IDs that will be running on the WTRU, application user information, transport address information of an application server of each application, and a non-network layer mobility support mechanism used by each application.

[0097] In an embodiment, the method may further include obtaining, from an application executing on the WTRU, an indication that the application supports non-network layer mobility management, wherein the first message indicating support for non-network layer mobility management may be sent responsive to the indication that the application supports non-network layer mobility management.

[0098] In an embodiment, the first message may be a service request message. In an embodiment, the second message may be a NAS message. In an embodiment, the indication that the application supports non-network layer mobility management is obtained responsive to the WTRU initiating a service request procedure. In an embodiment, the WTRU may initiate the service request procedure based on the application being launched in idle mode and triggering the WTRU to switch to connected mode.

[0099] In an embodiment, the indication that the application supports non-network layer mobility management may be garnered from information received from the application including any of an indication that the application is capable of handling mobility in the application layer, an indication that the application does not require IP preservation, an indication that the application does not require session continuity, an indication that the application does not require service continuity, an indication that the application does not require network-layer mobility support, an indication of a mobility mechanism used in the application layer, an application ID, an application server transport address, and an application user ID.

[0100] In an embodiment, the method further comprising determining that an application executing on the WTRU does not support non-network layer mobility management; sending, to the MMF, a fourth message indicating support for network layer mobility management; and receiving, from the MMF, a fifth message confirming support for network layer mobility management.

[0101] Pursuant to the new methodologies and technologies provided herein an agreement between the WTRU and network to skip usual network-layer-mobility support and use application layer mobility support may be reached (e.g., as discussed supra and infra by the WTRU sending a request and relevant information to the network, and network verifying the request with the application server) The new methodologies and technologies herein provide special handling to support non-network-layer mobility, including:.

[0102] (i) IP address reservation or allocation in-advance in adjacent RANs to speed up the

IP address allocation procedure when WTRU moves to a new RAN;

[0103] (ii) a centralized database that keeps a record of WTRU' s current IP address and RAN ID to facilitate the idle mode location tracking; and

[0104] (iii) the application layer of the WTRU may subscribe to idle/connected mode mobility events and act accordingly on the events for application layer mobility management.

[0105] Representative alternatives to GTP and/or other network layer mobility protocol mechanisms are provided herein (e.g., supra and/or infra). The provided alternative ("non-network- layer") mobility support mechanisms are for the purpose of illustration only and are not limiting of disclosed embodiments. Various other non-network-layer mobility support mechanisms apparent to those skilled in the art are intended to fall within the scope of the appended claims. The non- network mobility support mechanisms may include any of above network layer mobility support mechanisms, application layer mobility support mechanisms and transport layer mobility support mechanisms. A few examples of the non-network-layer mobility mechanisms follow.

[0106] Example SIP Re-INVITE Method

[0107] Session Initiation Protocol (SIP) is an application layer protocol for internet multimedia session establishment, modification and termination. SIP can support WTRU mobility. For example, a SIP media session may be kept alive after the WTRU moves to a different IP domain/subnet using re-INVITE method.

[0108] FIG. 4 is a flow diagram illustrating an example SIP re-INVITE procedure 400 for terminal mobility. The example re-INVITE procedure 400 may be used to support mobility of a mobile host (MH) 402 mid-call with a correspondent host (CH) 406, for example.

[0109] At some point during a SIP media session, the MH 402 may move to a new IP subnet (401). After moving to the new IP subnet, the MH 402 may acquire a new IP address using DHCP (403). The MH 402 may register the new IP address ("MH 402 new IP/contact") with a SIP Registrar/Proxy 404 (405). The MH 402 may initiate a re-INVITE message to the CH 406 (407). The re-INVITE message may include a "contact" header field, and the "contact" header field may be populated with (updated to) the MH 402 new IP/contact address. Additionally or alternately, the re-INVITE message may include a SDP description having a connection address field ("c="), and the connection address field ("c=") in the SDP description may be populated with (updated to) the MH 402 new IP/contact address. After exchange of "200 OK" and "SIP ACK" messages (409, 411), the CH 406 may modify session parameters according to the connection (MH 402 new IP/contact) address in the SDP, and the media session may be re-established between the MH 402 and the CH 406.

[0110] One advantage of the SIP re-INVITE procedure 400 is that it is very simple. A drawback of using the SIP re-INVITE procedure 400 alone is that several sources of delay may be introduced, such as delays associated with acquisition of the new IP address, re-establishment of the TCP connection, etc., and may cause undesirable service disruptions. Provided herein are further solutions that may be used to mitigate the amount and/or sources of delay.

[0111] Host Identity Protocol (HIP)

[0112] It has been long recognized that one root cause for today's IP mobility and multi-homing issues lies in the fact that an IP address serves both as a locator and an identifier of a host. That is, the IP address describes both a current topological location and an identity of the host as seen by upper layer applications. Because of its role as the identity of the host, the IP address is preserved when the location of the host changes. GTP, mobile IP (MIP) and like-type mobility schemes are solutions that preserve the IP address for the application layer, e.g., by using an IP anchor, providing a mapping between a "home address" and a "care-of address", etc. [0113] Host identity protocol (HIP) addresses the dual purpose of the IP address by introducing a separate name space, namely, "Host Identity". In HIP, a Host Identity is a public cryptographic key from a public-private key pair. A host possessing the corresponding private key can prove ownership of the public key, and thus, prove its identity.

[0114] A Host Identity layer may sit between the IP layer and TCP layer, such as shown in FIG. 5. The IP address may keep its locator role and the Host Identity layer maintains a mapping between identities and locators. Upper layer applications may be bound to Host Identities instead of IP addresses, and may not need to be concerned about the locator changes. When a mobile host changes its location, the HIP may be used to transfer the information to all peer hosts. The Host Identity public key may be represented by its 128-bit hash value Host Identity Tag (HIT) or 32-bit Local Scope Identifier (LSI).

[0115] Multi-path TCP

[0116] A traditional TCP session is bound to a single network interface. This single network interface is usually identified by a single IP address. There is no way to make use of multiple network interfaces in a device, such as cellular network, Wi-Fi, Bluetooth, etc., at the same time for a single TCP session. And when a communication moves from one interface to another the TCP connection has to be broken and re-established again. Multipath TCP aims to improve on traditional TCP to make use of multiple network interfaces at the same time and make lossless handoffs from one interface to another.

[0117] FIG. 6 illustrates an example multipath TCP (MPTCP) operation. A MPTCP session starts the same way as a traditional TCP session, with a typical 3 -way handshake. But a MPTCP capable host may indicate MP CAPABLE in the SYN packet. If a receiving host supports MPTCP, the MPTCP indication may be included in the SYN-ACK packet. After the MPTCP session is established, either party may initiate another TCP connection (probably from a different interface), and may join the new TCP connection as a subflow to the original MPTCP session. The subflow may be added by sending a SYN packet with a MP JOIN option. The information on which MPTCP session is to be joined may also be included.

[0118] After the MPTCP session has more than one subflow, it is up to the host on each end to decide how to split traffic between them. A single receive window applies to the session as a whole. Each subflow may appear as a traditional TCP connection, with its own sequence number. The MPTCP session as a whole has a separate sequence number. The subflows can be established or torn down during the life of the MPTCP session.

[0119] In a legacy 3 GPP core network, numerous system procedures are required by the GTP- based mobility management mechanism, including, for example, IP anchor gateway (such as P- GW) selection, IP address allocation by the IP anchor gateway, GTP tunnel establishment and management procedures, measurement configuration and reporting for handover purposes, etc. These procedures usually involve large overhead of network signaling and also extra WTRU power consumption.

[0120] As noted herein infra and supra, there are some alternative mobility support mechanisms in the application layer. If a WTRU has applications that can handle the mobility support at application layer instead of usual network layer, it is beneficial for the WTRU to skip or forego the heavy-weight network-layer mobility related procedures. This is also one goal of next generation networks support for various type of mobility, including "on-demand" mobility. Achievement of this may result from addressing various issues. A first issue addressed by the methodologies and technologies provided herein is to make the network understand that the WTRU has the capability in the application or other applicable layer. This may not be simply achieved by having some indication or flag in subscription data of the WTRU and/or in capability information of the WTRU sent to the network for one or more of the following reasons.

[0121] (i) The WTRU may have various applications/services. Some of them may not require network-layer mobility support but others may still require such.

[0122] (ii) The fact that the client applications on the WTRU side support the application or transport layer mobility management does not necessarily mean that the corresponding application servers support such feature.

[0123] A second issue addressed by the methodologies and technologies provided herein are new procedures and configurations needed to support non-network-network mobility functions. There are at least two types of WTRU in question, for example, type 1 and type 2. For a type 1 WTRU- there may be only one potential application in the WTRU and it supports application layer (or other non-network layer) mobility management. For a type 2 WTRU - there are various applications in the WTRU. Some of them may support application layer (or other non-network) mobility management and others do not. For those that support the non-network mobility management, each application may support it in a different way. For a type 2 WTRU, for example, the WTRU support for application layer mobility management may be application-specific or dependent. For type 2 WTRU, there might be different possible scenarios when accessing the network, including:

[0124] Scenario A: the WTRU has not been given any network-layer mobility management configuration (e.g., the WTRU has just attached to the network), and then the WTRU initiates an application or service that doesn't require network-layer mobility management.

[0125] Scenario B: the WTRU has been given network-layer mobility management configurations, and then the WTRU initiates an application or service that does not require usual network-layer mobility management.

[0126] Scenario C: the WTRU has been given non-network-layer (e.g., application layer) mobility management configurations, and then the WTRU initiates an application or service that require usual network-layer mobility management support.

[0127] For different types of WTRUs and different scenarios, different mobility related procedures and configurations may be desired and corresponding WTRU and network behaviors are provided herein.

[0128] Performance of non-network-layer mobility support

[0129] Although non-network-layer mobility support may be used by applications that do not have stringent requirements on mobility performance such as service continuity, deterioration of user experience during a mobility event may be a concern. For example, the assignment of a new IP address, typically using DHCP procedures, when a WTRU moves to a new access point may introduce a significant delay. The subsequent application layer signaling to switch the communication to the new IP may add even more delay. The service interruptions caused by these delay may be mitigated pursuant to the methodologies and technologies provided herein.

[0130] Representative Non-Network Layer Mobility Support

[0131] Pursuant to a request for non-network mobility support, the network may be made aware of a WTRU's capability of application layer mobility support, and in turn, enable the network to handle the WTRU in a different way from the way it handles WTRUs with network layer mobility support.

[0132] FIG. 7 is a flow diagram illustrating an example procedure 700 for negotiating non- network layer mobility management in a network that supports (e.g., natively supports) network layer mobility management. The network may include a MMF 762, an HSS 780, a service capability exposure function (SCEF) 782 and one or more network slices (not shown). The MMF 762 may be associated with any of the network slices or the network as a whole. The network may be part of a communications system. The communications system may include a (radio) access network (R)AN (not shown) currently serving a WTRU 702 and may include or interface with one or more application servers 784. As would be understood by a person of skill in the art, the network, communications system and (R)AN may include additional elements not shown in FIG. 7.

[0133] The WTRU 702 may be configured as a type 1 WTRU. The WTRU 702 may be configured (dynamically, semi-statically or statically) with an attribute that indicates no network- layer mobility support is needed (e.g., is currently needed). In connection with accessing the network, the WTRU 702 may send to the MMF 762 a first message that may indicate, and/or include information indicating, no network layer mobility support is required (701). The first message may be, for example, an attach, a registration, an initial or other like-type message. The first message may also indicate, include information indicating and/or include various application- related information. The application-related information may include any of (i) a list of application identifiers (IDs) associated to applications that are and/or will be running on the WTRU 702; (ii) a list of service IDs of services that are and/or will be running on the WTRU 702; (iii) application user information, such as, application user IDs associated with the applications; (iv) transport address information, such as, IP address, port number, etc., of a server associated with each application; and (v) a mobility mechanism used by each application, such as SIP re-Invite, HIP, Multi-path TCP, etc.

[0134] As an alternative, the WTRU 702 may provide the indication of no network-layer mobility support required (i.e., an indication of support for non-network layer mobility management) in the first message, and provide the application-related information in another message, such as, e.g., in response to a request of the MMF 762 or other network element. In one embodiment, the WTRU 702 may provide some of the application-related information, and the network (MMF 762) may retrieve the remaining and/or applicable application information. For example, the WTRU 702 may only provide or indicate the list of application IDs, and the network (MMF 762) may retrieve other application-related information using the listed application IDs.

[0135] The MMF 762 may obtain user subscription information from the HSS 780 (703). The MMF may determine, based on the user subscription information, whether non-network-layer mobility support is authorized for the WTRU 702 (705). Although not shown, the procedure 700 may terminate if non-network-layer mobility support is not authorized. Alternatively, the procedure 700 may be adapted or supplemented allow for the WTRU 702 request and/or receive authorization for non-network-layer mobility support.

[0136] The MMF 762 may carry out non-network layer mobility support verification messaging or otherwise interact with the corresponding application servers 784 to verify the mobility mechanisms that the WTRU 702 claims to support are supported at the application servers 784 (707). Although not shown separately, the MMF 762 may carry out the non-network layer mobility support verification messaging or otherwise interact with the application servers 784 via the SCEF 782.

[0137] The MMF 762 may send to the WTRU 702 a second message that indicates, or includes information indicating, confirmation(s) from the network that the indicated non-network-mobility support is allowed (granted) for any positive verification responses from the application servers 784 (709). The second message may be, for example, an attach accept, registration response, an initial response or other like-type message. The MMF 762 may proceed to apply special handling for the non-network-layer mobility support corresponding to the confirmed positive verification responses from the application servers 784 (711), such as described herein. In an embodiment, the MMF 762 may begin to apply the special handling for the non-network-layer mobility support, and then send the second message.

[0138] As an alternative, the MMF 762 may be locally configured with a list of application IDs that support the non-network-layer mobility. The MMF 762 may check the WTRU applications against the local configured application IDs instead of (or alternatively, along with) carrying out the non-network layer mobility support verification messaging or otherwise interacting with the corresponding application servers 784 to verify the mobility mechanisms.

[0139] FIG. 8 is a flow diagram illustrating an example procedure 800 for negotiating non- network layer mobility management in a network that supports (e.g., natively supports) network layer mobility management. The procedure 800 of FIG. 8 is similar to the procedure 700 of FIG. 7, except that the MMF 762 may determine whether non-network-mobility support is approved (granted) based on positive verification responses from the application servers 784 and/or the subscription information (709).

[0140] FIG. 9 is a flow diagram illustrating an example procedure 900 for negotiating non- network layer mobility management in a network that supports (e.g., natively supports) network layer mobility management. The network may include a MMF 968, an HSS 980, an SCEF 982 and one or more network slices (not shown). The MMF 968 may be associated with any of the network slices or the network as a whole. The network may be part of a communications system. The communications system may include a (R)AN (not shown) currently serving a WTRU 902 and may include or interface with one or more application servers 984. As would be understood by a person of skill in the art, the network, communications system and (R)AN may include additional elements not shown in FIG. 9. .

[0141] The WTRU 902 may use application layer signaling (901) to trigger the application servers 984 to set, in the core network (e.g., in the HSS 980) via APIs of the SCEF 982, a flag ("mobility support flag") that indicates that non-network layer mobility is supported in the application servers 984 (903, 905, 907). The MMF 962 may verify that the non-network layer mobility is supported in the application servers 984 by downloading user subscription data and determining whether the mobility support flag is set (909).

[0142] For a type 2 WTRU, whether the network-layer mobility support is used or not may depend on currently active applications of the WTRU. When a new application is launched in idle mode and triggers the WTRU to switch to connected mode (for example, by initiating a service request procedure) the WTRU may receive from the application information indicating or indicative of a mobility support preference for the application. This information may include any of the following: (i) an indication that the application is capable of handling mobility in the application layer; (ii) an indication that the application does not require IP preservation or session/service continuity; (iii) an indication that the application does not require network-layer mobility support; (iv) a mobility mechanism used in the application layer; (v) an application ID; (vi) an application server transport address; (vii) an application user ID; (vii) etc.

[0143] The WTRU may determine whether the network-layer mobility support is used or not based on the application's input, which may include a corresponding indication in a service request message. The WTRU may also take into consideration other factors in determining the indication, such as whether the network or network slice supports non-network layer mobility handling. An absence of the indication in the service request message may be interpreted as the default option that the network-layer mobility support is required.

[0144] If after the WTRU enters connected mode and another application is launched, the new application may issue a different mobility support preference. The WTRU may reevaluate whether or which network layer or non-network layer mobility support is required and may update the network with the new requirement.

[0145] If after the WTRU exits from connected mode and enters idle mode, a new application is launched and triggers the WTRU to enter connected mode again, the new application may issue yet a different mobility support preference. The WTRU may again reevaluate whether or which network layer or non-network layer mobility support is required and include a new indication in the service request message. The new indication may be same as or different from the indication sent in the previous service request message.

[0146] Upon receiving the indication from the WTRU, the network may once again check whether non-network layer mobility management is supported or not at the application server side (e.g., using the procedures described above in connection with FIGs. 7-9).

[0147] Representative Procedures and/or Configurations for Supporting Non-Network Layer Mobility Management

[0148] Any of the WTRU and the network may carryout special handling of some system procedures and configurations when network layer mobility is not required and/or when using non- network layer mobility management.

[0149] Although one motivation for skipping or foregoing network layer mobility procedures is that applications may be able to handle mobility at the application layer, the representative procedures and technologies provided herein may also apply to other cases where network-layer mobility support is not warranted, such as for stationary devices.

[0150] The representative procedures and technologies provided herein assume that the network has decided not to provide network layer mobility support responsive to a WTRU request and verification with the corresponding application server for non-network layer mobility support.

[0151] Example IP Address Reservation/Allocation-in-Advance

[0152] FIG. 10 is a flow diagram illustrating an example procedure 1000 for carrying out IP address allocation at a (R)AN 1004 serving a WTRU 1002. The (R)AN 1004 may be part of a communications system. The communications system may include a core network (not shown). The core network may include a MMF 1062, a DHCP server 1090 and one or more network slices (not shown). The MMF 1062 may be associated with any of the network slices or the network as a whole. As would be understood by a person of skill in the art, the network, communications system and (R)AN may include additional elements not shown in FIG. 10. Although not shown, the procedure 1000 may include or be adapted to include one or more processes for negotiating non- network layer mobility management in the core network, e.g., one or more applicable processes of any of the example procedures 700, 800 and 900.

[0153] The WTRU 1002 may be configured as any of a type 1 WTRU and a type 2 WTRU. The WTRU 702 may be configured (dynamically, semi-statically or statically) with an attribute that indicates no network-layer mobility support is needed (e.g., is currently needed). In connection with a network access (e.g., attach) procedure, the WTRU 1002 may send to the MMF 1062 a first message that may indicate, and/or include information indicating, no network layer mobility support is required (1001). The first message may be, for example, an attach, a registration, an initial or other like-type message. The first message may also indicate, include information indicating and/or include various application-related information.

[0154] The MMF 1090 may request the (R)AN 1004 to assign/allocate-in-advance a local IP address ("reserved IP address"). The MMF 1062 may obtain information for carrying out the IP address allocation, such as whether the WTRU requests IPv4 or IPv6 or both, during the network access procedure. The MMF 1062 may forward or otherwise send the information to the (R)AN 1004 for the IP address allocation (1003).

[0155] The (R)AN 1004 may delegate the IP address allocation to the DHCP server 1090, and may receive the reserved IP address from the DHCP server 1090 (e.g., in response to a request) (1005). As an alternative, the (R)AN 1004 may support the IP address allocation locally. For instance, the (R)AN 1004 may have an internal DHCP server function and an assigned pool of IP addresses, which may be utilized to carry out the IP address allocation.

[0156] The (R)AN 1004 may forward or otherwise send the reserved IP address to the MMF 1062 (1007). The reserved IP address together with an ID of the RAN 1004 may be forwarded or otherwise sent to the WTRU 1002 by the MMF 1062 (1009). Alternatively, the serving RAN 1004 may send the reserved IP address together with its ID to the WTRU.

[0157] Referring now to FIG. 11, a flow diagram illustrating an example procedure 1100 for carrying out IP address allocation at a (R)AN 1104 serving a WTRU 1102 is shown. The (R)AN 1104 may be part of a communications system. The communications system may include a core network (not shown). The core network may include a MMF 1162, a DHCP server 1190 and one or more network slices (not shown). The MMF 1162 may be associated with any of the network slices or the network as a whole. As would be understood by a person of skill in the art, the network, communications system and (R)AN may include additional elements not shown in FIG. 11. Although not shown, the procedure 1100 may include or be adapted to include one or more processes for negotiating non-network layer mobility management in the core network, e.g., one or more applicable processes of any of the example procedures 700, 800 and 900. The procedure 1100 of FIG. 11 is similar to the procedure 1000 of FIG. 10, except where denoted with different reference numerals.

[0158] Pursuant to the procedure 1100, the WTRU 1102 may send to the MMF 1162 in connection with a network access (e.g., attach) procedure a first message that may indicate, and/or include information indicating, no network layer mobility support is required (1001). The first message may be, for example, an attach, a registration, an initial or other like-type message. The first message may also indicate, include information indicating and/or include various application- related information.

[0159] The MMF 1162 may send to the WTRU 1 102 a second message that indicates, or includes information indicating, confirmation(s) from the network that the indicated non-network-mobility support is allowed (granted), e.g., for any positive verification responses from one or more application servers (not shown) (1101). The WTRU 1102 may initiate an IP allocation request to the RAN 1104 (1103) after receiving and/or responsive to the second message and/or the confirmation(s). The (R)AN 1104 may delegate the IP address allocation to the DHCP server 1190, and may receive the reserved IP address from the DHCP server 1190 (e.g., in response to a request) (1005). Alternatively, the (R)AN 1104 may support the IP address allocation locally, e.g., using an internal DHCP server function and an assigned pool of IP addresses. The (R)AN 1104 may forward or otherwise send the reserved IP address to the WTRU 1102 (1107). Alternatively, the (R)AN 1104 may forward or otherwise send the reserved IP address to the MMF 1162, and the reserved IP address together with an ID of the RAN 1104 may be forwarded or otherwise sent to the WTRU 1102 by the MMF 1162 (1009).

[0160] In an embodiment, after a new IP address is assigned at a new (R)AN, the new (R)AN may inform a previous serving (R)AN (e.g., (R)ANs 1004 or 1104) so the serving (R)AN can recollect the old IP address and assign it to other WTRUs.

[0161] In an embodiment, a MMF may select and/or request one or more (R)ANs adjacent to a (R)AN serving a WTRU to reserve IP addresses for the WTRU in connection with negotiating non- network layer mobility management in a network. The (R)ANs that are selected to reserve IP addresses for the WTRU may be predicted by the MMF based on WTRU mobility characteristics and/or network topology. The IP allocation at the selected (R)ANs may be requested by the MMF at the same time as the MMF requests an IP allocation at the currently connected (R)AN. Alternatively, it can be triggered at a later time, for example, when WTRU detects through measurement that it may enter a new (R)AN soon. In another alternative, the current serving (R)AN may request adjacent (R)ANs to reserve IP address for a WTRU, e.g., based on the measurement report received from and/or associated with the WTRU. The reserved IP address(es), together with the ID(s) of the (R)AN(s) reserving the IP address(es), may be forwarded to the WTRU by the MMF and/or the serving (R)AN. When the WTRU accesses a new (R)AN and finds that it has reserved IP address in that (R)AN, it may skip the IP address allocation procedure by indicating to the network it has already the IP address and may use the reserved IP address for application layer mobility handling.

[0162] A benefit of having IP addresses reserved before connecting to the (R)ANs is that a delay inherent in carrying out IP address allocation might be mitigated when the WTRU moves to a new RAN, and may improve user experience which might otherwise be compromised by this delay and consequent service interruption. For non-IP type communications, the IP address allocation procedure is not needed. Other like-type addressing procedures may be carried out instead.

[0163] Example Idle Mode Location Tracking

[0164] A WTRU without network-layer mobility support that acquires a local IP address from a serving (R)AN may update any of an application server and communication peer with the acquired IP address via application layer or transport layer specific methods. For example, a SIP host may re-register with a SIP server or proxy when moving to a new (R)AN and acquiring a new IP address.

[0165] Pursuant to the methodologies and technologies herein the IP address of a WTRU may be used as a locator of the WTRU (e.g., without utilizing usual location area update procedures). The downlink data may be routed directly to the (R)AN to which the WTRU is currently connected using the acquired IP address as the destination IP address (e.g., without utilizing conventional network initiated paging procedures). Air interface paging may still be necessary.

[0166] FIG. 12 illustrates an example high level procedure 1200 for location tracking of a WTRU 1202 when using non-network layer mobility management. The procedure 1200 may be carried out in a communications system that may include an ingress/egress GW 1266, a first (R)AN 1204a currently serving (or connected with) the WTRU 1202, and a second (R)AN 1204b neighboring the first (R)AN 1204a and communicatively coupled to the ingress/egress GW 1266. The ingress/egress GW 1266 and the second (R)AN 1204b may separately communicatively couple (or interface) with a (e.g., centralized) database function 1292. The ingress/egress GW 1266 may also communicatively couple with an application server 1284. As would be understood by a person of skill in the art, communications system may include additional elements not shown in FIG. 12, and the procedure 12 may be carried out in other communications systems, as well.

[0167] The database function 1292 may maintain in a database/memory a mapping between an ID of the WTRU 1202 (WTRU ID) and its current IP address and an ID of a (R) AN (R)AN_ID associated to the current IP address. When the WTRU 1202 moves to a new (R)AN and is assigned a new IP address, the WTRU 1202 or the serving RAN may initiate an update to the mapping in the database. When downlink data, such as an application layer triggering message, arrives at the ingress GW 1266, which may maintain a mapping between the WTRU ID and an old IP address of the WTRU 1202, may query the database to get the WTRU's current IP address. The ingress gateway then may replace the destination IP with the new IP address and may forward the data to the (R)AN current serving the WTRU 1202 if a routing path is available. If a path is not available, the ingress GW 1266 may request a gateway controller (not shown) to set up a routing path.

[0168] After receiving the data, the WTRU 1202 may initiate an application layer procedure to update the server 1284 or its peer of its new IP address. A subsequent communication may use the new IP address. A benefit of updating the new IP address in this way is that it avoids application layer signaling for updating to new IP address every time that the WTRU 1202 accesses a new (R)AN.

[0169] Referring to FIG. 12, at (1), the WTRU 1202 may be assigned IP1 in the first (R)AN 1204a . At (2), the WTRU 1202 may move to the second (R)AN 1204b. At (3), the WTRU 1202 may be assigned a new IP2 in the second (R)AN 1204b. At (4), the second (R)AN 1204 may update the database with (UE ID: IP2) mapping. At (5), incoming data with destination IPl arrives at the ingress GW 1266. At (6), the ingress GW 1266 queries the database function 1292 for the new IP address of the WTRU 1202 using the WTRU ID. At (7), the database function 1292 may return a query result. At (8), the ingress GW 1266 may replace IPl with IP2 in the data and may forward it to the second (R)AN 1204b. At (9), the WTRU 1202 may initiate the application layer signaling with the server to update its current IP address. [0170] Representative Data Routing Example

[0171] A difference in data routing between network layer (e.g., GTP -based) mobility support and non-network layer mobility support is that the GTP tunnel might not be available for data routing with the non-network layer mobility support. For IP data routing, the lack of GTP tunnels is generally not problematic because the IP is a routable protocol. If the IP address is locally assigned and used as a true locator of the WTRU, then the data may be routed. The use of SDN technology may make it even more efficient. The example procedure described with respect to FIG. illustrates IP data routing without GTP tunneling. Details of non-IP data routing may be found in U.S. Provisional Patent Application No. 62/279,509, filed 15-Jan-2016 (Attorney Docket 12897US01), which is incorporated herein by reference, and more enhancements are currently under study.

[0172] Example Mobility Event Notification

[0173] In idle mode, a WTRU may measure radio signal strength and quality of cells in proximity (e.g., its current cell or cells ("cell(s)") and/or one or more neighboring cells) and/or obtain other cell selection/reselection ("(re)selection") criteria, and autonomously determine whether to (and based on the determination) select to the current cell(s) to camp or to reselect to one or more other cells. When using network layer mobility support, the idle mode mobility events (e.g., cell (re) selection) and idle mode measurements and/or results thereof need not be reported to a RAN. As such, the network and the WTRU application layer are unaware of the idle mode mobility events and idle mode measurements and/or results thereof. When the mobility support needs to be handled at the application layer (or other non-network layer), the WTRU idle mode mobility event may be provided to the concerning applications.

[0174] In an embodiment, the applications may subscribe to a mobility event notification service provided from a cellular module, entity, unit, etc. (collectively "unit") of the WTRU. Pursuant to the mobility event notification service, may include the following events: WTRU has selected a PLMN; WTRU has camped in a cell; WTRU has reselected to a new cell/RAN; WTRU has lost radio coverage or there is radio link failure, WTRU has entered/exit power saving mode (PSM) or long DRX mode, etc.

[0175] When such events occur, the cellular module of the WTRU may send an event notification to the subscribing applications. The notification may include one or more of the following information: [0176] · the Event ID which identifies what type of mobility event has occurred;

[0177] · the Application ID that has subscribed to the events;

[0178] · the details of the mobility event. For example, the type of the cell (e.g., small cell or Home eNB) that's been selected or reselected; for another example, the potential period of unreachability if PSM mode is entered.

[0179] The application layer, upon receiving these mobility events, may carry out any of the following:

[0180] · initiate a new IP address allocation request to the new serving RAN

[0181] · initiate necessary application layer signaling to deal with the mobility events. For example, it may request the resending of any possibly lost data during the PSM mode when it has exit the PSM mode

[0182] In connected mode, the WTRU is usually controlled by the network to make measurements and report the measurement result and mobility events to the network, for the network to make mobility decisions such as handover. Similar to the idle mode, the application layer may subscribe to connected mode mobility event notification defined in the cellular standards

[0183] The application layer may also configure non-standardized events according to their needs. For example, if the connected mode handover decision is made by the WTRU autonomously without network control, the application server may receive an event notification when the cellular module has made such a decision. This way, the application traffic may be withheld upon receiving such a notification. As another example, the application layer may receive another notification when the WTRU has successfully established a connection with a new RAN. The applications may start to request a new IP address, and may resume traffic sending using the new IP address.

[0184] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0185] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE" may mean (i) a wireless transmit and/or receive unit (WTRU), such as described supra; (ii) any of a number of embodiments of a WTRU, such as described supra; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU, such as described supra; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU, such as described supra; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1E.

[0186] In addition, the methods provided 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 electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD- ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0187] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0188] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices containing processors are noted. These devices may contain at least one Central Processing Unit (CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0189] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0190] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM")) or non-volatile (e.g., Read-Only Memory (ROM")) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0191] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device. [0192] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost vs. efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0193] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0194] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

[0195] The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0196] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0197] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero.

[0198] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0199] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0200] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, ]f 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMS What is claimed is:

1. A method implemented in a network that natively supports network layer mobility management and that includes a mobility management function (MMF), the method comprising:

receiving, at the MMF from a wireless transmit/receive unit (WTRU), a first message indicating any of (i) support for non-network layer mobility management, (ii) to forego the network layer mobility management, and (iii) application information related to the non-network layer mobility management;

determining, at the MMF element, that the WTRU is approved to use the non-network layer mobility management based on any of subscription information associated with the WTRU and an application server verification;

sending, from the MMF element to the WTRU, a second message indicating an approval to use the non-network layer mobility management; and

preforming, at least in part by the MMF element, a procedure to support the non-network layer mobility management.

2. The method of the preceding claim, wherein preforming a procedure to support the non-network layer mobility management comprises configuring the network to the non-network layer mobility management.

3. The method of any of the claims 1-2, wherein determining that the WTRU is approved to use the non-network layer mobility management comprises determining whether the WTRU is authorized to use the non-network layer mobility management based at least in part on the subscription information.

4. The method of any of the claims 1-2, further comprising: receiving, at the MMF element, subscription information, wherein determining that the WTRU is approved to use the non-network layer mobility management comprises determining whether the WTRU is authorized to use the non-network layer mobility management based at least in part on the subscription information.

5. The method of any of the claims 1-4, wherein determining that the WTRU is approved to use the non-network layer mobility management comprises verifying with an application server that the application server supports the non-network layer mobility management.

6. The method of any of the claims 1-5, further comprising: foregoing procedures to support network layer mobility management for the WTRU.

7. The method of any of the claims 1-6, wherein the second message also indicates network layer mobility management is not supported for the WTRU.

8. The method of any of the claims 1-7, wherein the first message is any of an attach message and a registration request message.

9. The method of any of the claims 1-8, wherein the second message is any of an attach accept message and a registration response message.

10. The method of any of the claims 1-9, wherein the first message also indicates a non-network layer mobility support mechanism.

11. The method of any of the claims 1-9, further comprising receiving, from the WTRU, a third message indicating a non-network layer mobility support mechanism.

12. The method of any of the claims 10-11, wherein the non-network layer mobility support mechanism is any of an application layer mobility support mechanism, a transport layer mobility support mechanism and a host identity layer mechanism.

13. The method of any of the claims 1-12, wherein the first message also indicates non-network layer mobility configuration information.

14. The method of any of the claims 1-12, further comprising receiving, from the WTRU, a third message indicating non-network layer mobility configuration information.

15. The method of any of the claims 13-14, wherein the non-network layer mobility configuration information comprises any of a list of application identifiers (IDs), a list of service IDs, application user information, transport address information of an application server, and a non-network layer mobility support mechanism.

16. The method of any of the claims 1-7 and 11-15, wherein the first message is a service request message.

17. The method of any of the claims 1-7 and 11-16, wherein the second message is a non-access stratum message.

18. The method of any of the claims 1-17, further comprising: receiving, at the MMF from the WTRU, a fourth message indicating a request for network layer mobility management; and

sending, from the MMF to the WTRU, a fifth message confirming support for network layer mobility management.

19. The method of any of the claims 1-18, further comprising:

performing a procedure and/or configuring the network to support non-network layer mobility management.

20. The method of claim 19, wherein performing a procedure and/or configuring the network to support non-network layer mobility management comprises any of:

reserving, or allocating in-advance, one or more IP addresses in one or more adjacent radio access network (RANs) to hasten IP address allocation when the WTRU moves to one of the RANs;

performing idle mode location tracking; and

performing connected mode location tracking.

21. The method of claim 20, wherein performing idle mode location tracking comprises:

maintaining in a centralized database a current IP address allocated to the WTRU and a

RAN ID of a RAN in which the WTRU is camped.

22. A mobility management function (MMF) of a network that natively supports network layer mobility management), the MMF configured to:

receive, from a wireless transmit/receive unit (WTRU), a first message indicating any of (i) support for non-network layer mobility management, (ii) to forego the network layer mobility management, and (iii) application information related to the non-network layer mobility management;

determine that the WTRU is approved to use the non-network layer mobility management based on subscription information associated with the WTRU and an application server verification;

send, to the WTRU, a second message indicating an approval to use the non-network layer mobility management; and

preform, at least in part, a procedure to support the non-network layer mobility management.

23. The MMF of the preceding claim, wherein the MMF is configured to preform a procedure to support the non-network layer mobility management at least in part by configuring the network to the non-network layer mobility management.

24. The MMF of any of the claims 22-23, wherein the MMF is configured to determine that the WTRU is approved to use the non-network layer mobility management at least in part by determining whether the WTRU is authorized to use the non-network layer mobility management based at least in part on the subscription information.

25. The MMF of any of the claims 22-23, wherein the MMF is further configured to: receive the subscription information, wherein the MMF is configured to determine that the WTRU is approved to use the non-network layer mobility management at least in part by determining whether the WTRU is authorized to use the non-network layer mobility management based at least in part on the subscription information.

26. The MMF of any of the claims 22-25, wherein the MMF is configured to determine that the WTRU is approved to use the non-network layer mobility management at least in part by verifying with an application server that the application server supports the non-network layer mobility management.

27. The MMF of any of the claims 22-26, where in the MMF is configured to:

forego procedures to support network layer mobility management for the WTRU.

28. The MMF of any of the claims 22-27, wherein the second message also indicates network layer mobility management is not supported for the WTRU.

29. The MMF of any of the claims 22-28, wherein the first message also indicates a non-network layer mobility support mechanism.

30. The MMF of any of the claims 22-29, wherein the first message also indicates non-network layer mobility configuration information.

31. The MMF of any of the claims 22-29, wherein the MMF is configured to receive, from the WTRU, a third message indicating non-network layer mobility configuration information.

32. The MMF of any of the claims 30-31, wherein the non-network layer mobility configuration information comprises any of a list of application identifiers (IDs), a list of service IDs, application user information, transport address information of an application server, and a non-network layer mobility support mechanism.

33. A method implemented in a wireless transmit/receive unit (WTRU), the method comprising: sending, to a mobility management function (MMF) of a network that supports network layer mobility management, a first message indicating support for non-network layer mobility management; and

receiving, from the MMF, a second message indicating an approval to use the non-network layer mobility management.

34. The method of the preceding claim, wherein the second message also indicates network layer mobility management is not supported for the WTRU.

35. The method of any of the claims 33-34, wherein the first message also indicates non-network layer mobility configuration information.

36. The method of any of the claims 33-34, further comprising sending, to the MMF, a third message indicating non-network layer mobility configuration information.

37. The method of any of the claims 35-36, wherein the non-network layer mobility configuration information comprises any of a list of application identifiers (IDs), a list of service IDs, application user information, transport address information of an application server, and a non-network layer mobility support mechanism used by each application.

38. A wireless transmit/receive unit (WTRU), which may include any of a receiver, a transmitter and a processor, configured to perform a method as in at least one of the claims 33-37.

39. A network configured to perform a method as in at least one of the claims 1-21.

40. A system configured to perform a method as in at least one of the claims 1-31 and 33-37.

41. A tangible computer readable storage medium having stored thereon computer executable instructions for performing a method as in at least one of the preceding claims.