WO2017117044A1 - Architecture de réseau de télécommunications mobiles internationales de nouvelle génération et configuration d'interface de référence pour l'approvisionnement de réseau plat - Google Patents

Architecture de réseau de télécommunications mobiles internationales de nouvelle génération et configuration d'interface de référence pour l'approvisionnement de réseau plat Download PDF

Info

Publication number
WO2017117044A1
WO2017117044A1 PCT/US2016/068497 US2016068497W WO2017117044A1 WO 2017117044 A1 WO2017117044 A1 WO 2017117044A1 US 2016068497 W US2016068497 W US 2016068497W WO 2017117044 A1 WO2017117044 A1 WO 2017117044A1
Authority
WO
WIPO (PCT)
Prior art keywords
imme
base station
network
wtru
ipgw
Prior art date
Application number
PCT/US2016/068497
Other languages
English (en)
Inventor
Byung Lim
Jaehyun AHN
Sung-Yeon Kim
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2017117044A1 publication Critical patent/WO2017117044A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/142—Reselecting a network or an air interface over the same radio air interface technology

Definitions

  • Future IMT systems may require more flexible network nodes.
  • nodes may be configurable, based on Software-Defined Networking (SDN) architecture and network function virtualization (NFV), to provide optimal processing of the node functions and improvement of the operational efficiency of network.
  • SDN Software-Defined Networking
  • NFV network function virtualization
  • a method for use in wireless communication may include: exchanging, by a base station, control plane information directly with an innovated Mobility Management Entity (iMME) over a first interface; exchanging, by the base station, user plane information directly with an innovated Packet Gateway (iPGW) over a second interface, wherein the iPGW is directly connected to the iMME and an external packet data network; and exchanging, by the base station, a portion of the control plane information and a portion of the user plane information with a wireless transmit/receive unit (WTRU) over a third interface.
  • iMME innovated Mobility Management Entity
  • iPGW innovated Packet Gateway
  • WTRU wireless transmit/receive unit
  • the base station may include: an antenna; a processor coupled to the antenna, the processor configured to exchange control plane information directly with an innovated Mobility Management Entity (iMME) over a first interface; the processor further configured to exchange user plane information directly with an innovated Packet Gateway (iPGW) over a second interface, wherein the iPGW is directly connected to the iMME and an external packet data network; and the processor further configured to exchange a portion of the control plane information and a portion of the user plane information with a wireless transmit/receive unit (WTRU) over a third interface.
  • iMME innovated Mobility Management Entity
  • iPGW innovated Packet Gateway
  • FIG. 1A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented
  • 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. 1A;
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram of an example radio access network and an example core network that may be used within the communications system illustrated in FIG. 1A;
  • FIG. 2 is a diagram of conventional cellular network architecture and interface configurations
  • FIG. 3 is a diagram of 4th generation E-UTRAN and EPC network architecture
  • FIG. 4 is a diagram illustrating a migration from the 4G network to a 5G network by flattening
  • FIG. 5 is a diagram illustrating non-roaming architecture for a next generation IMT access network and core network
  • FIG. 6 is a diagram illustrating roaming architecture of home routed traffic for a next generation IMT access network and core network
  • FIG. 7 is a diagram illustrating a network deployment configuration of the I-UTRAN access network equipment and core network equipment
  • FIG. 8 is a diagram illustrating network deployment and operation configuration by a network function virtualization (NFV) and a Software-Defined
  • SDN Networking
  • FIG. 9 is a diagram illustrating a Rl-C interface layer stack between an innovated Node B (iNB) and an innovated MME (iMME);
  • FIG. 10 is a diagram illustrating an iUu interface layer stack between a wireless transmit/receive unit (WTRU) and an iNB and the Rl-C interface layer stack between the iNB and the iMME;
  • WTRU wireless transmit/receive unit
  • FIG. 11 is a diagram illustrating a R2 interface between the MME and the iMME;
  • FIG. 12 is a diagram illustrating a R3 interface layer stack between a Serving GPRS Support Node (SGSN) and the iMME;
  • SGSN Serving GPRS Support Node
  • iMME the iMME
  • FIG. 13 is a diagram illustrating an iUu interface layer stack between the WTRU and the iNB and a Rl-U interface layer stack between the iNB and an innovated packet gateway (iPGW);
  • iPGW innovated packet gateway
  • FIG. 14 is a diagram illustrating an IPS bearer service layered architecture without an innovated roaming gateway (iRGW) entity;
  • FIG. 15 is a diagram illustrating an IPS bearer service layered architecture with the iRGW entity
  • FIGS. 16A-16B are diagrams illustrating an attach procedure
  • FIG. 17 is a diagram illustrating handover within the iMME
  • FIGS. 18A-18B is a diagram illustrating an inter-iMME handover procedure with an iNB change
  • FIG. 19 is a diagram illustrating a logical serving gateway (1SGW) change (inter-iMME) procedure without an iNB change;
  • FIG. 20 is a diagram iUustrating a 1SGW change (within iMME) procedure without an iNB change;
  • FIG. 21 is a diagram illustrating iMME and 1SGW association
  • FIG. 22 is a diagram illustrating a R6 interface setup within a
  • FIG. 23 is a diagram illustrating a network architecture including an iNB having dual physical link interface connectivity
  • FIG. 24 is a diagram illustrating a non-roaming architecture for the next generation IMT access network and core network
  • FIG. 25 is a diagram illustrating a roaming architecture of home routed traffic for a next generation IMT access network and core network;
  • FIG. 26 is a diagram illustrating a network deployment configuration of I-UTRAN and core network equipment
  • FIG. 27 is a diagram illustrating a network architecture that employs NFV and SDN friendly network architectures
  • FIG. 28 is a diagram illustrating a network deployment and operation configuration with a fixed and mobile convergence.
  • FIG. 29 is a diagram illustrating a control plane for a Rl-C interface employed by between a WTRU and iMME;
  • FIG. 30 is a diagram illustrating a control plane for an R2 reference interface employed between an iMME and another iMME;
  • FIG. 31 is a diagram illustrating a user plane for an Rl-U interface employed between a WTRU and an iPGW;
  • FIG. 32 is a diagram illustrating a Rl user plane protocol stack employed between a WTRU and an iNB.
  • FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • 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.
  • 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • 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 pubhc 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.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • 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.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and the like.
  • the communications systems 100 may also include a base station
  • 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 other networks 112.
  • 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, 114b 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.
  • 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.
  • BSC base station controller
  • RNC radio network controller
  • 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.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple -input multiple-output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple -input multiple-output
  • 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).
  • RAT radio access technology
  • 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.
  • 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).
  • HSPA High-Speed Downlink Packet Access
  • HSUPA High-Speed Uplink Packet Access
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • the base station 114a and the WTRUs 102a are identical to 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.
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 IS-95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • the base station 114b in FIG. 1A may be a wireless router, Home
  • Node B, Home eNode B, or access point 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.
  • 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).
  • 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).
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • 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.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the core network 106.
  • 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.
  • 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.
  • 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.
  • the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106 may also serve as a gateway for the WTRUs
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • 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.
  • the networks 112 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.
  • 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.
  • 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.
  • FIG. IB is a system diagram of an example WTRU 102.
  • 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 /touch ad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138.
  • GPS global positioning system
  • 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.
  • 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.
  • a base station e.g., the base station 114a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • 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.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO 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.
  • 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.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • 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.
  • 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 /touchp ad 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 /touchp ad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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.
  • 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.
  • 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.
  • location information e.g., longitude and latitude
  • 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.
  • 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.
  • 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.
  • 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
  • FIG. 1C is a system diagram of the RAN 104 and the core network
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the core network 106.
  • the RAN 104 may include eNode-Bs 140a, 140b, 140c, 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 140a, 140b, 140c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 140a, 140b, 140c may implement MIMO technology.
  • the eNode-B 140a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 140a, 140b, 140c 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. 1C, the eNode-Bs 140a, 140b, 140c may communicate with one another over an X2 interface.
  • the core network 106 shown in FIG. 1C may include a mobility management entity gateway (MME) 142, a serving gateway 144, and a packet data network (PDN) gateway 146. 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.
  • MME mobility management entity gateway
  • PDN packet data network
  • the MME 142 may be connected to each of the eNode-Bs 140a, 140b,
  • the MME 142 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 142 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.
  • the serving gateway 144 may be connected to each of the eNode Bs
  • the serving gateway 144 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the serving gateway 144 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.
  • the serving gateway 144 may also be connected to the PDN gateway
  • the WTRU 146 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.
  • the core network 106 may facilitate communications with other networks.
  • 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.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • WLAN 160 may include an access router 165.
  • the access router may contain gateway functionality.
  • the access router 165 may be in communication with a plurality of access points (APs) 170a, 170b.
  • the communication between access router 165 and APs 170a, 170b may be via wired Ethernet (IEEE 802.3 standards), or any type of wireless communication protocol.
  • AP 170a is in wireless communication over an air interface with WTRU 102d.
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Subscriber
  • LTE Long Term Evolution
  • radio access technology migration is a key driver of the evolution
  • core network migration is parallel to the evolution.
  • FIG. 2 shows legacy cellular networks architectures and interface configurations of the 3G and 4G systems.
  • the network equipment may include a NodeB 202, a RNC 204, a mobile switching center (MSC) 206, a serving GPRS support node (SGSN) 208, and a gateway GPRS support node (GGSN) 210.
  • the RNC 204 function may be decomposed and merged into other network entities.
  • the RNC 204 entity may be eliminated in conventional 4G networks. That is to say, the network may be simplified by reducing the network entity.
  • a new evolved network for the next generation network architecture may be developed by reducing the number of network entities.
  • This new evolved network may meet all of the requirements of conventional networks and may also be compatible with Software-Defined Networking (SDN) and network function virtualization (NFV).
  • SDN Software-Defined Networking
  • NFV network function virtualization
  • the following description may include a flat next generation network having SDN and NFV friendly network architectures.
  • the remaining entities in FIG. 2 may be known in the art.
  • FIG. 3 a diagram of 4th generation E-UTRAN 302 and EPC 304 network architecture is shown.
  • the network architecture shown in FIG. 3 may be flattened and minimized in the network entity by eliminating the serving gateway (S-GW) 306.
  • S-GW serving gateway
  • the control plane and user data plane may be decomposed of the S-GW 306 functions.
  • the functional entities may then be re-organized by combining the control entity function of the S-GW 306 into a MME 308. This may simplify the direct bearer connection between a base station 310 and a packet gateway 312.
  • a control plane and a user data plane may be denoted as “CP” and "UP”, respectively.
  • a control interface may be denoted as “control I/F”, by appending a suffix "C” on a reference label (e.g., Rl- C) or, in some figures, by identifying the interface with a dotted line.
  • a user-data interface may be denoted as "user data I/F”, by appending a suffix "U” on a reference label (e.g., Rl-U) or, in some figures, by identifying the interface with a solid line.
  • the Sl-MME interface may be the reference point for the control plane protocol between E-UTRAN and MME.
  • the Sl-U interface may be the reference point between E-UTRAN and Serving GW for the per bearer user plane tunneling and inter eNodeB path switching during handover.
  • the S3 interface may enable user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state.
  • the S4 interface may provide related control and mobility support between GPRS core and the 3GPP anchor function of the serving GW. In addition, if a direct tunnel is not established, it may provide the user plane tunneling.
  • the S5 interface may provide user plane tunneling and tunnel management between serving GW and PDN GW. It may be used for serving GW relocation due to WTRU mobility and may be used if the serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.
  • the S6a interface may enable transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between the MME and HSS.
  • the Gx interface may provide transfer of (QoS) policy and charging rules from the PCRF to Pohcy and Charging Enforcement Function (PCEF) in the PDN GW.
  • the S8 interface may be an inter-PLMN reference point providing user and control plane between the serving GW in the VPLMN and the PDN GW in the HPLMN.
  • the S8 interface may be the inter PLMN variant of S5.
  • the S9 interface may provide transfer of (QoS) policy and charging control information between the Home PCRF and the Visited PCRF in order to support local breakout function.
  • the S10 interface may be a reference point between MMEs for MME relocation and MME to MME information transfer.
  • the Sl l interface may be a reference point between MME and Serving GW.
  • the S12 interface may be a reference point between UTRAN and Serving GW for user plane tunneling when Direct Tunnel is established. It may be based on the Iu- u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN, or respectively between SGSN and GGSN. Usage of the S12 interface may be an operator configuration option.
  • the S13 interface may enable a WTRU identity check procedure between MME and EIR.
  • the SGi interface may be a reference point between the PDN GW and the packet data network.
  • the packet data network may be an operator external public or private packet data network or an intra operator packet data network (e.g., for provision of IMS services). This reference point corresponds to Gi for 3GPP accesses.
  • the Rx reference point may reside between the Application Function (AF) and the PCRF.
  • the SBc may be a reference point between CBC and MME for warning message delivery and control functions.
  • FIG. 4 a diagram illustrating a migration from the
  • an innovated base station iNodeB (iNB) 402 may provide access connectivity to the next generation radio user terminals including the 4G LTE WTRU and the evolved LTE WTRU.
  • An innovated mobility management entity (iMME) 404 may provide mobility and connectivity management of the WTRU for the next generation and legacy 4G and evolved 4G user equipment.
  • An innovated PDN gateway (iPGW) 406 may have control channel with the iMME and user bearer channel for the WTRU to the Internet.
  • the iMME 404 and iPGW 406 may be part of an innovated Packet Core (IPC) (i.e., core network) 408, and the iNB 402 may be part of an innovated UMTS radio access network (I -UTRAN) 410, which may be referred to as an access network.
  • IPC Packet Core
  • I -UTRAN innovated UMTS radio access network
  • the following description may include network architecture novel network functional entities function and features compared to the legacy 4G LTE system architectures shown in FIGS. 2 and 3.
  • a flat network architecture may be disclosed to reduce the hierarchy of core network architecture by eliminating the S-GW entity in order to make the core network to be flat, as shown in FIG. 4.
  • the description may also include how the newly incorporated features or changed features are workable in the proposed architecture as compared to the legacy LTE features and architecture by using the same name of the entities with the suffix change from "e” to "i” such as from “eNB” and “MME” to "iNB” and “iMME.”
  • the functionality of the S-GW in the legacy LTE architecture may be decomposed into the control plane and user data plane functions.
  • the control entity function of the S-GW may be merged into the MME and the physical entity of the S-GW may be eliminated.
  • the newly defined MME may be referred to as the iMME 404 hereinafter.
  • the user data entity function of the S-GW may be merged into the
  • the newly defined P-GW may be referred to as the iPGW 406 hereinafter.
  • the physical user data plane from the access network may terminate at the iPGW 406 in the core network 408.
  • the iPGW may be directly connected to an external packet data network 412, such as the internet, operator services, etc. Accordingly, the eNB in conventional LTE architecture may become the iNB 402.
  • an innovated roaming gateway may be created.
  • the iRGW may be located in the border of the operators in order to support the S-GW functionality in the roaming home routed traffic case.
  • a new entity may be included, which may be referred to as a logical serving gateway (1SGW).
  • the 1SGW may be utilized for mobility and connection management of WTRUs connected to iNBs 402 within an iPGW 406, where the iNBs 402 are grouped by regional or service specific category.
  • a 1SGW may be associated to an iNB 402 and WTRU by an iMME 404 during an attach procedure and may be changed by an iMME 404 with several triggering conditions (e.g., area change of the WTRU during a handover, the reallocation of a sliced network due to service change, etc.).
  • FIG. 5 a diagram illustrating non-roaming architecture for a next generation IMT access network and core network is shown.
  • FIG. 5 may include interworking architecture for interfacing with elements of a legacy 3GPP access network and core network.
  • FIG. 5 shows a next generation mobile network architecture, which may be evolved out of the 3GPP legacy 4G LTE network architecture.
  • the S-GW may be ehminated.
  • the iMME 404 may be an evolution of the legacy MME entity, and may cover the gap of the mobility management and connectivity management from the anchored hierarchical architecture into the non-anchored flat architecture.
  • a logical hierarchical 1SGW entity may be implemented in the iMME 404 in order to enable mobility and hand off management.
  • the iMME 404 may be connected to a Home Subscriber Server (HSS) 508.
  • HSS Home Subscriber Server
  • the iPGW 406 may be evolved from the legacy PGW entity in order to cover a direct bearer termination of the base station.
  • the iPGW 406 may have multiple functions, such as incoming packet buffering and the support of the legacy network user bearer termination (e.g., in E-UTRAN and UTRAN).
  • the iPGW may be connected to a Policy Control and Charging Rules Function (PCRF) 504, which may be connected to an external packet data network, 412, such as the operator's IP services and/or the internet.
  • PCRF Policy Control and Charging Rules Function
  • the iNB 402 may be an innovated NodeB that may be a terminating point for the new RAT of the next generation mobile communication.
  • the iNB 402 may communicate with the iMME 404 for connection and mobility management, and may communicate with the iPGW 406 for user data bearer transportation.
  • the iNB 402 may communicate with one or more WTRUs 502. It should be noted that the reference interface points shown in FIG. 5 may be renamed from the legacy 3GPP network reference points if they include new features and functions.
  • FIG. 6 a diagram illustrating roaming architecture of home routed traffic for a next generation IMT access network and core network is shown.
  • FIG. 6 may include interworking architecture for interfacing with elements of a legacy 3GPP access network.
  • FIG. 6 shows the next generation mobile network architecture, which may be evolved out of the 3GPP legacy 4G LTE network architecture.
  • the S-GW may be eliminated for home routed traffic.
  • the roaming architecture for local breakout cases can be easily developed as given in the 3GPP roaming architecture. The following description may focus on the home routed traffic case due to the iRGW 602 given in this architecture.
  • home routed traffic may be gated by the S-GW at the visiting public land mobile network (VPLMN), and the P-GW of the home public land mobile network (HPLMN) may terminate the user packet bearer.
  • the iRGW 602 may terminate all the roaming user bearer traffic of the home routed traffic and may communicate with the iPGW 406 of the HPLMN.
  • the iRGW 602 may be used to support roaming traffic.
  • the iRGW 602 may not have an impact on the hierarchy of the network architecture.
  • the iRGW 602 may support the legacy network's roaming traffic by the support of the iMME 404.
  • FIG. 7 a diagram illustrating a network deployment configuration of the I-UTRAN access network equipment and core network equipment is shown.
  • the proposed network architecture may be flat. In other words, there may not be a hierarchical structure among the core network equipment and the interconnecting iNB 402. Because of this flatness, and because the IP bearer transporting IP network may be independent from the 3GPP legacy LTE network, the network may be very flexible and scalable.
  • the network equipment shown in FIG. 7 may be deployed by itself without being combined with the other network equipment due to the flexibility and connectivity in the network.
  • the network equipment may be interconnected for serving the associated network equipment by simply allocating the provisioning data in the operation centers.
  • a requirement of next generation mobile communication systems may be compatibility with NFV and SDN.
  • FIG. 8 a diagram illustrating network deployment and operation configuration by a NFV and a SDN domain control based operation is shown.
  • the IP transport network may be separated from the mobile communication network entities, and the IP transport network may be operable by a SDN control. Accordingly, it may be possible to efficiently manage the IP bearer networks depending on the network loading.
  • the functional entities of the network may be virtualized and may be implemented by a NFV over the IP cloud network. Moreover, the network entities of the virtualized entity and the non-virtualized physical entity can co-exist on the SDN controlled network without impact on the NFV domain.
  • the innovated UTRAN (iUTRAN or I-UTRAN) network may perform one or more of the following functions: header compression and user plane ciphering; iMME 404 selection when no routing to an iMME 404 can be determined from the information provided by the WTRU 502; and transport level packet marking in the uplink, such as setting the DiffServ Code Point based on the QCI of the associated IPS (Innovated Packet Switching system) bearer.
  • IPS Intelligent Packet Switching system
  • the iNB 402 may perform one or more of the following functions.
  • the iNB 402 may host functions for Radio Resource Management, such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and dynamic allocation of resources to WTRUs 502 in uplink, downlink, and sidelink (scheduling).
  • the iNB 402 may host IP header compression and encryption of user data streams.
  • the iNB 402 may host selection of an iMME 404 at WTRU 502 attachment when no routing to an iMME 404 can be determined from the information provided by the WTRU 502.
  • the iNB 402 may host routing of User Plane data towards the iPGW
  • the iNB 402 may host scheduling and transmission of paging messages that may have originated from the iMME 404.
  • the iNB 402 may host scheduling and transmission of broadcast information (originated from the iMME 404 or O&M).
  • the iNB 402 may host measurement and measurement reporting configuration for mobility and scheduling.
  • the iNB 402 may host scheduling and transmission of PWS (which may include ETWS and CMAS) messages that may have originated from the iMME 404.
  • the iNB 402 may host CSG handling.
  • the iNB 402 may host transport level packet marking in the uplink.
  • the iNB 402 may host ISGW relocation without WTRU 502 mobility (e.g., iMME 404 load balancing, service specific network slice change, etc.).
  • the iMME 404 may perform one or more of the following functions.
  • the iMME 404 may perform NAS signaling, NAS signaling security, and inter CN node signaling for mobility between 3GPP access networks.
  • the iMME 404 may perform WTRU 502 Reachability in ICM-IDLE state, including control, execution of paging retransmission and optionally Paging Policy Differentiation, and ICM-IDLE (I CM: IPS Connection Management).
  • the iMME 404 may perform tracking Area list management, mapping from WTRU 502 location (e.g. TAI) to time zone, signaling a WTRU 502 time zone change associated with mobility.
  • the iMME 404 may perform iPGW 406 selection, iMME 404 selection for handovers with an iMME 404 change, SGSN 208 selection for handovers to 2G/3G 3 GPP access networks, and SGW 306 selection for handovers to a 4G 3GPP access network.
  • the iMME 404 may perform authentication, authorization, and bearer management functions, including dedicated bearer establishment.
  • the iMME 404 may perform lawful interception of signaling traffic, warning message transfer (including selection of an appropriate iNB 402), management of ISGW, mobility control within the ISGW, and ISGW selection for handovers with a ISGW change.
  • the iPGW 406 and the iRGW 602 may be implemented in one physical node or separated physical nodes.
  • the iPGW 406 may be the gateway which terminates the SGi interface towards the PDN and the interface towards I-UTRAN.
  • the iPGW 406 may serve as the local mobility anchor point for inter-iNB 402 handover.
  • the iPGW 406 may send one or more "end markers" to the source iNB 402 immediately after switching the path during inter-iNB 402 handover, especially to assist the reordering function in the iNB 402.
  • the iPGW 406 may send one or more "end markers" to the iRGW 602 immediately after switching the path during inter-RAT handover.
  • the iRGW 602 may then forward the "end markers" to the source eNB 310, the source SGSN 208, and/or the source RNC 204.
  • the iPGW 406 may handle ICM-IDLE mode downlink packet buffering, initiation of network triggered service request procedures, and, optionally, Paging Policy Differentiation.
  • the iPGW 406 may also handle one or more of the following functions: packet routing and forwarding, per-user based packet filtering (e.g., by deep packet inspection), lawful interception, WTRU 502 IP address allocation, transport level packet marking in the uplink and downlink based on the QCI of the associated IPS bearer, accounting for inter-operator charging (e.g., for home routed roaming).
  • the iPGW 406 may collect and report the uplink and downlink data volume, for example, per IPS bearer, as received from and sent to the serving node, UL and DL service level charging (e.g., based on SDFs defined by the PCRF or based on deep packet inspection defined by local policy), UL and DL service level gating control, UL and DL service level rate enforcement (e.g., by rate pohcing/shaping per SDF), DHCPv4 (server and client) and DHCPv6 (client and server) functions, and packet screening.
  • UL and DL service level charging e.g., based on SDFs defined by the PCRF or based on deep packet inspection defined by local policy
  • UL and DL service level gating control e.g., UL and DL service level rate enforcement (e.g., by rate pohcing/shaping per SDF)
  • DHCPv4 server and client
  • DHCPv6 client and server
  • the iPGW 406 may include the following functions for the GTP-based interface: UL and DL bearer binding, UL bearer binding verification, and accounting per WTRU 502 and bearer.
  • the iRGW 602 may be the gateway which terminates the interface towards I-UTRAN in VPLMN or terminates the interface towards the 2G/3G/4G RAT.
  • the iRGW 602 may send one or more "end markers" to the source iNB 402, the source eNodeB 310, the source SGSN 208, or the source RNC 204 immediately after switching the path during inter-RAT handover. This may assist the reordering function in the iNB 402.
  • the iRGW 602 may handle mobility anchoring for inter-3GPP mobility.
  • the iRGW 602 may handle ICM- IDLE mode downlink packet buffering, initiation of network triggered service request procedures, and, optionally, Paging Policy Differentiation.
  • the iRGW 602 may handle lawful interception and packet routing and forwarding.
  • the iRGW 602 may handle accounting for inter-operator charging and may generate accounting data per WTRU 502 and bearer.
  • the iRGW 602 may forward the "end markers" to the source iNB 402, the source eNodeB 310, the source SGSN 208, and/or the source RNC 204 when the "end marker" is received from a home iPGW 406 and the iRGW 602 has a downlink user plane established.
  • the iRGW 602 may not send Downlink Data Notification.
  • the ISGW may be the gateway to be used for management of one or more iNBs 402 by the iMME 404.
  • the ISGW may be associated with a number of iNBs 402 by a ISGW ID, which may be managed by the iMME 404.
  • the iNBs 402 may be grouped by location, such as proximity to one another or to the iMME 404.
  • the iNBs 402 may be grouped by service type. For example, a small cell may not be grouped together with a macro cell, even though it may be collocated in the same region, because the small cell may be utilized only for mission critical services (e.g., medical operation, drone competition, etc.).
  • mission critical services e.g., medical operation, drone competition, etc.
  • a single ISGW may be shared by multiple iMMEs 404. Multiple lSGWs may be associated with a single WTRU 502 by the iMME 404. This may be done if the WTRU 502 has multiple types of services.
  • One or more iNBs 402 associated with the same ISGW may be linked to one another by a R6 interface.
  • FIG. 9 a diagram illustrating a Rl-C interface layer stack between the iNB 402 and the iMME 404 is shown.
  • the Rl-C interface layer stack may be in the control plane.
  • the Rl Application Protocol (Rl-AP) 902 may be an Application Layer Protocol between the iNB 402 and the iMME 404.
  • the Stream Control Transmission Protocol (SCTP) 904 may ensure delivery of signaling messages between the iMME 404 and the iNB 402 (Rl).
  • the SCTP 904 may be defined in the Internet Engineering Task Force (IEFT) Request for Comments (RFC) 4960.
  • FIG. 10 a diagram illustrating an iUu interface layer stack between the WTRU 502 and the iNB 402 and the Rl-C interface layer stack between the iNB 402 and the iMME 404 is shown.
  • the layer stacks shown in FIG. 10 show the control plane.
  • the NAS protocol 1002 may support mobility management functionality and user plane bearer activation, modification and deactivation. It may also be responsible for ciphering and integrity protection of NAS signaling.
  • the LTE-Uu may be the radio protocol of E-UTRAN between the WTRU 502 and the iNB 402.
  • FIG. 11 a diagram illustrating a R2 interface between the MME and the iMME is shown.
  • FIG. 11 shows the user plane.
  • a general packet radio service (GPRS) Tunneling Protocol for the control plane (GTP-C) 1102 may tunnel signaling messages between the MME 308 and the iMME 404.
  • GTP-C general packet radio service
  • UDP User Datagram Protocol
  • FIG. 12 a diagram illustrating a R3 interface layer stack between a SGSN 208 and the iMME 404 is shown.
  • FIG. 12 shows the user plane.
  • the tunneling layer may implement Generic Routing Encapsulation (GRE) applicable for Proxy Mobile IPv6 (PMIPv6).
  • GRE Generic Routing Encapsulation
  • FIG. 13 a diagram illustrating an iUu interface layer stack between the WTRU 502 and the iNB 402 and a Rl-U interface layer stack between the iNB 402 and the iPGW 406 is shown.
  • FIG. 13 shows the user plane.
  • the iMME 404 may control the user plane tunnel establishment and may establish User Plane Bearers between the iNB 402 and the iPGW 406.
  • the iUu may be the radio protocols of I-UTRAN between the WTRU 502 and the iNB 402.
  • a data radio bearer 1402 may transport packets of the IPS bearer between a WTRU 502 and one or more iNBs 402. When the data radio bearer 1402 exists, there may be a one-to- one mapping between this data radio bearer 1402 and an IPS bearer 1404.
  • a Rl- U bearer 1406 may transport the packets of a data radio bearer between the iNB 402 and the iPGW 406.
  • the WTRU 502 may store a mapping between an uplink packet filter and a data radio bearer.
  • the iPGW 406 may store a mapping between a downlink packet filter and the Rl-U bearer 1406.
  • the iNB 402 may store a one-to-one mapping between the data radio bearer 1402 and the Rl-U bearer 1406 to create the binding between the data radio bearer 1402 and the Rl- U 1406 bearer in both the uplink and downlink.
  • An end-to-end service 1408 may facilitate web browsing services.
  • the end-to-end service 1408 may provide content to the WTRU 502 from a peer entity 1410, which may be a server.
  • An external bearer 1412 may be a transportation link between the iPGW 406 and the peer entity 1410.
  • a data radio bearer 1502 may transport packets of an IPS bearer between the WTRU 502 and one or more iNBs 402. When the data radio bearer 1502 exists, there may be a one-to- one mapping between this data radio bearer 1502 and an IPS bearer 1504.
  • a Rl- U bearer 1506 may transport packets of the data radio bearer 1502 between the iNB 402 and the iPGW 406.
  • the WTRU 502 may store a mapping between an uplink packet filter and the data radio bearer 1502.
  • the iPGW 406 may store a mapping between a downlink packet filter and the Rl-U bearer 1506.
  • the iNB 402 may store a one-to-one mapping between the data radio bearer 1502 and the Rl-U bearer 1506 to create the binding between a data radio bearer 1502 and the Rl-U bearer 1506 in both the uplink and downlink.
  • a Roaming Bearer 1508 may transport packets of the IPS bearer between the iRGW 602 and the iPGW 406.
  • the Roaming Bearer 1508 may include a GTP (or IP) address of the iPGW 406 (or SGW 306 for LTE, or SGSN 208 and RNC 204 for 3G) as an External Bearer 1510.
  • An end-to-end service 1408 may facilitate web browsing services.
  • the end-to-end service 1512 may provide content to the WTRU 502 from a peer entity 1514, which may be a server.
  • the path of the end-to-end service 1512 may be routed to a home PLMN iPGW 406.
  • the external bearer 1510 may be a transportation link between the iPGW 406 and the peer entity 1514.
  • FIGS. 16A-16B diagrams illustrating an attach procedure are shown.
  • the WTRU 502 may initiate the attach procedure by the transmission of an Attach Request message together with RRC parameters to an iNB 402.
  • the iNB 402 may forward, to a new iMME 1602, the
  • Step 3 if the WTRU 502 identifies itself with a Globally Unique
  • the new iMME 1602 may determine what type entity the old node was (e.g., iMME, MME or SGSN).
  • the iMME 1602 may use the GUTI received from the WTRU to derive the old iMME/MME/SGSN 1604 address, and may send an Identification Request (old GUTI, complete Attach Request message) to the old iMME/MME/SGSN 1604 to request the International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • the old iMME/MME may first verify the Attach Request message by NAS MAC and then may respond with Identification Response (IMSI, MM Context). If the request is sent to an old SGSN, the old SGSN may first verify the Attach Request message by the P-TMSI signature and then may respond with Identification Response (MM Context).
  • IMSI Identification Response
  • MM Context Identification Response
  • the new iMME 1602 may send an Identity Request to the WTRU 502 to request the IMSI.
  • the WTRU 502 may respond with Identity Response (IMSI).
  • IMSI Identity Response
  • the authentication and NAS security may be configured.
  • Step 6 if the iMME has changed since the last detach, there is no vahd subscription context for the WTRU 502 in the iMME 1602, or the WTRU 502 provides an IMSI, the iMME 1602 may send an Update Location Request message to a HSS 508.
  • the HSS 508 may send Cancel Location (IMSI,
  • Cancellation Type to the old iMME/MME 1604.
  • the old iMME/MME 1604 may acknowledge with Cancel Location Ack (IMSI) and may remove the MM and bearer contexts. If the ULR-Flags indicates "Initial-Attach-Indicator" and the HSS 508 has the SGSN registration, then the HSS 508 may send Cancel Location (IMSI, Cancellation Type) to the old SGSN 1604.
  • the CanceUation Type may indicate the old MME/SGSN 1604 to release the old Serving GW resource.
  • the session procedure may be deleted in the old iMME/MME 1604, which may involve the PCRF 504.
  • acknowledgement for Step 6 may be sent.
  • the new iMME 1602 may request a session creation for the iPGW 406. It may also determine a ISGW to be associated with the WTRU 502. Multiple lSGWs may be associated to the WTRU 502.
  • the iMME 1602 may send an Attach Accept message
  • the iNB 402 may forward the RRC Connection Reconfiguration message, including the IPS Radio Bearer Identity, to the WTRU 502 as well as the Attach Accept message.
  • the WTRU 502 may send the RRC Connection Reconfiguration Complete message to the iNB 402.
  • the iNB 402 may send the Initial Context Response message to the iMME 1602, which may complete the initial context setup.
  • the WTRU 502 may send a Direct Transfer message to the iNB 402, which may include the Attach Complete message.
  • the iNB 402 may forward the Attach Complete message to the iMME 1602.
  • the new iMME 1602 may send a Modify Bearer Request (IPS Bearer Identity, iNB address, iNB TEID, Handover Indication, Presence Reporting Area Information) message to the iPGW 406.
  • IPS Bearer Identity iNB address
  • iNB TEID Handover Indication
  • Presence Reporting Area Information iPGW 406.
  • the iPGW 406 may acknowledge by sending a Modify
  • the iPGW 406 may then send its buffered downlink packets.
  • IPS Bearer Identity IPS Bearer Identity
  • Step 21 if the received Request Type does not indicate handover, an IPS bearer was established, the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses, and the iMME 1602 selected a iPGW 406 that is different from the iPGW identity which was indicated by the HSS 508 in the PDN subscription context, the iMME 1602 may send a Notify Request including the APN and iPGW identity to the HSS 508 for mobility with non-3GPP accesses.
  • the message may include information that identifies the PLMN in which the iPGW 406 is located.
  • the HSS 508 may store the APN and iPGW identity pair and may send a Notify Response to the iMME 1602.
  • FIG. 17 a diagram illustrating handover within the iMME 404 is shown. This procedure may be used for handover of a WTRU 502 from a source iNB 1702 to a target iNB 1704 when the iMME 404 is unchanged.
  • the target iNB 1704 may send a Path Switch Request message to the iMME 404 to inform that the WTRU 502 has changed cell.
  • the iMME 404 may send a Modify Bearer Request message to the iPGW 406.
  • a Modify Bearer Response message may be sent back to the iMME 404.
  • the iPGW 406 may send one or more "end marker" packets on the old path immediately after switching the path.
  • the source iNB 1702 may forward the packets to the target iNB 1704.
  • the iMME 404 may confirm the Path Switch Request message with the Path Switch Request Ack message. This may be an acknowledgement of Step 1.
  • the target iNB 1704 may indicate success of the handover to source iNB 1702 and may trigger the release of resources.
  • Step 7 a tracking area update is conducted, if needed.
  • FIGS. 18A-18B diagrams illustrating an inter- iMME handover procedure with an iNB change are shown. This procedure may be used to handover a WTRU 502 from a source iNB 1802 to a target iNB 1804 when the iMME is changed from a source iMME 1806 to a target iMME 1808 (or if the 1SGW is changed without an iMME 404 change).
  • the source iNB 1802 may decide to initiate a Rl-based handover to the target iNB 1804. This may be triggered, for example, by a lack of R6 connectivity to the target iNB 1804, by an error indication from the target iNB 1804 after an unsuccessful R6-based handover, or by dynamic information learned by the source iNB 1802.
  • the source iNB 1802 may send a Handover Required message containing one or more of a Direct Forwarding Path Availability, Source to Target transparent container, target iNodeB Identity, CSG ID, target TAI, etc. to the source iMME 1806.
  • the source iMME 1806 may select the target iMME 1808 using an "iMME Selection Function.” If it has determined to relocate the iMME, it may send a Forward Relocation Request message containing one or more of a WTRU context, Source to Target transparent container, RAN Cause, target iNodeB Identity, CSG ID, CSG Membership Indication, target TAI, UE Time Zone, Serving Network, Local Home Network ID, etc. to the target iMME 1808. [0144] At Step 4, the target iMME 1808 may send a Handover Request message containing one or more of EPS Bearers to Set Up, AMBR, Source to Target transparent container, CSG ID, CSG Membership Indication, etc. to the target iNB 1804. At Step 4a, the target iNB 1804 may send a response to the target iMME 1808.
  • the target iMME 1808 may send a Forward Relocation Response message containing one or more of a Cause, Target to Source transparent container, 1SGW change indication, EPS Bearer Setup List, Addresses, etc. to the source iMME 1806.
  • the source iMME 1806 may send a Handover Command message containing one or more of a Target to Source transparent container, Bearers subject to forwarding, and Bearers to Release to the source iNB 1802.
  • the Handover Command may be constructed using the Target to Source transparent container and may be sent to the WTRU 502 in Step 6a.
  • the source iNB 1802 may send the iNB Status
  • the source iNB 1802 may send an iNB Status Transfer message to the source iMME 1806.
  • the source iNB 1802 may omit sending the iNB Status Transfer message if none of the radio bearers of the WTRU 502 are treated with PDCP status preservation.
  • the source iMME 1806 may send this information to the target iMME 1808 via the Forward Access Context Notification message.
  • the target iMME 1808 may send a Forward Access Context Acknowledge message to the source iMME 1806.
  • the target iMME 1808, or the source iMME 1806 if there is no relocation may send the information to the target iNB 1804 via the iMME Status Transfer message.
  • the source iNB 1802 may start forwarding downlink data from the source iNB 1802 towards the target iNB 1804 for bearers subject to data forwarding. This may be performed by either direct forwarding (Step 8a) or indirect forwarding (Step 8b).
  • Step 9 after the WTRU 502 has successfully synchronized to the target cell, it may send a Handover Confirm message to the target iNB 1804. Downlink packets forwarded from the source iNB 1802 may be sent to the WTRU 502. Also, uplink packets may be sent from the WTRU 502, which are forwarded to the iPGW 406.
  • the target iNB 1804 may send a Handover Notify
  • TAI+ECGI, Local Home Network ID, etc. message to the target iMME 1808.
  • Step 11a if the target iMME 1808 has been relocated, the target iMME 1808 may send a Forward Relocation Complete Notification message to the source iMME 1806.
  • the source iMME 1806 may then send a Forward Relocation Complete Acknowledge message to the target iMME 1808.
  • a timer in the source iMME 1806 may be started to supervise the resources in the source iNB 1802.
  • the target iMME 1808 may send a Modify Bearer
  • the iPGW 406 may send a Modify Bearer Response message to the target iMME 1808.
  • a Tracking Area Update may be performed if needed, which may involve the HSS 508.
  • a context release procedure may be performed on the source iNB 1802 by the source iMME 1806.
  • the iMME (or only the 1SGW without iMME change) may change without an iNB change, which may mean a change of network slice. In this case, there may be no interruption of UL data transmission. However, RRC configuration (e.g., radio bearer configuration) may happen.
  • RRC configuration e.g., radio bearer configuration
  • FIG. 19 a diagram illustrating a 1SGW change
  • Step 1 may be triggered by dynamic information received by the iNB 402 or triggered by dynamic information received by the source iMME 1902 (e.g., network slicing change).
  • the iNB 402 may send Handover Required message containing one or more of Direct Forwarding Path Availability, Source to Target transparent container, target iNodeB Identity, CSG ID, target TAI, etc. to the source iMME 1902.
  • the source iMME 1902 may select the target iMME 1904 using a "MME Selection Function.” If it has determined to relocate the iMME, it may send a Forward Relocation Request message containing one or more of a WTRU context, Source to Target transparent container, RAN Cause, target iNodeB Identity, CSG ID, CSG Membership Indication, target TAI, WTRU Time Zone, Serving Network, Local Home Network ID, etc. to the target iMME 1904.
  • the target iMME 1904 may send a Handover Request message containing one or more of EPS Bearers to Setup, AMBR, Source to Target transparent container, CSG ID, CSG Membership Indication, etc. to the iNB 402.
  • the iNB 402 may respond to the target iMME 1904.
  • the target iMME 1904 may send a Forward Relocation Response message containing one or more of a Cause, Target to Source transparent container, 1SGW change indication, IPS Bearer Setup List, Addresses, etc. to the source iMME 1902.
  • the source iMME 1902 may send a 1SGW change message
  • the iNB 402 may send a RRC reconfiguration message to the WTRU 502.
  • the RRC reconfiguration message may include a configuration change with a NAS layer change (e.g., 1SGW change).
  • the WTRU 502 may send an acknowledgment for Step 6a.
  • the iNB 402 may send a Handover Notify message containing one or more of a TAI+ECGI, Local Home Network ID, etc. to the target iMME 1904.
  • the target iMME 1904 may send a Forward Relocation Complete Notification message to the source iMME 1902.
  • the source iMME 1902 may send a Forward Relocation Complete Acknowledge message to the target iMME 1904.
  • a timer in the source iMME 1902 may be started to supervise resources in the iNB 402.
  • the target iMME 1+04 may send a Modify Bearer
  • the iPGW 406 may send a Modify Bearer Response message to the target iMME 1904.
  • a Tracking Area Update procedure may be performed if needed, which may involve the HSS 508.
  • FIG. 20 a diagram illustrating a 1SGW change
  • Step 1 may be triggered by dynamic information received by the iNB 402 or triggered by dynamic information received by the source iMME 2002 (e.g., network slicing change).
  • the iNB 402 may send a
  • Handover Required message containing one or more of Direct Forwarding Path Availability, Source to Target transparent container, target iNodeB Identity, CSG ID, target TAI, etc. to the source iMME 2002.
  • the source iMME 2002 may change the 1SGW by itself or with another iMME, for example, by iNB addition, iNB removal, iNB relocation, etc.
  • the source iMME 2002 may send a 1SGW change message
  • the iNB 402 may send a RRC reconfiguration message to the WTRU 502.
  • the RRC reconfiguration message may include a configuration change with a NAS layer change (e.g., 1SGW change).
  • the WTRU 502 may send an acknowledgment for Step 4a.
  • the iNB 402 may send a Handover Notify message containing one or more of TAI+ECGI, Local Home Network ID, etc. to the source iMME 2002.
  • the source iMME 2002 may send a Modify Bearer Request message containing at least an iNB address, etc. to the iPGW 406.
  • the iPGW 406 may send a Modify Bearer Response message to the source iMME 2002.
  • a Tracking Area Update procedure may be performed if needed, which may involve the HSS 508.
  • FIG. 21 a diagram illustrating iMME and ISGW association is shown.
  • FIG. 21 may illustrate an initiation of a R6 interface and the generation of a ISGW region.
  • the iMME 404 may manage the mobility of a WTRU 502 within its management range, which may be defined by the ISGW 2102.
  • the ISGW 2102 may have one or more of the following characteristics.
  • the ISGW 2102 may include at least one iNB 402 and at least one iMME 404. Within the ISGW 2102, iNBs 402 may be linked to one another by a R6 interface.
  • the ISGW 2102 may be shared by multiple iMMEs 404.
  • An iNB 402 may be shared by multiple lSGWs 2102.
  • the ISGW 2102 may be shared by multiple iPGWs 406.
  • the ISGW 2102 may be shared by different service bearers.
  • the ISGW 2102 may be identified by identifiers (IDs), such as for example: a type of multicast group ID (IP), a type of dedicated IP (virtual IP), a type of dedicated IP and port number, and/or a type of layer 2 ID (e.g., MAC address, or virtual MAC address).
  • IDs such as for example: a type of multicast group ID (IP), a type of dedicated IP (virtual IP), a type of dedicated IP and port number, and/or a type of layer 2 ID (e.g., MAC address, or virtual MAC address).
  • the iMME 404 may transmit an iNB neighbor list associated with a ISGW to a first iNB 2202 and a second iNB 2204.
  • the iNB neighbor list may be composed of iNB IDs and the corresponding ISGW IDs. Examples of iNB IDs may include one or more of the following: ECGI, physical cell ID, and IP address.
  • the first iNB 2202 may transmit a R6 setup request message to the corresponding second iNB 2204 (e.g., from iNBl 2202 to iNB2 2204).
  • the receiving second iNB 2204 may send a R6 setup response message to the transmitting first iNB 2202.
  • the R6 setup response message may include one or more of the following: neighbor cell ID list, CSG ID, a number of antenna ports, PRACH configuration, and MBSFN subframe information and MBMS service area identity list.
  • WTRU bearer packet data may be relayed by the iPGW, which may mean that packets transported over the cellular link tunnel (i.e., GTP-U tunnel) may terminate at the iPGW.
  • the next generation architecture may also be designed to directly connect with a fixed internet access network and thereby meet the fixed and mobile convergence network requirement for 5G IMT networks.
  • FIG. 23 a diagram illustrating a network architecture including an iNB 402 having dual physical link interface connectivity is shown.
  • FIG. 23 shows the differences between the flattened network illustrated in FIG. 5 (shown on the left) and architecture designed with a direct link to an internet access network (shown on the right).
  • the iNB 402 may have at least two physical link interfaces.
  • a first physical link interface may be an existing physical interface for the Rl-U toward the iPGW 406 and the Rl-C interface toward the iMME 404.
  • a second physical link interface may be a physical interface for the Rl interface toward external packet data network 412, such as an internet access network, as shown in FIG. 23 and described in more detail below.
  • an iNB 402 may support multiple IP connections.
  • LIPA/Selected IP Traffic Offload LIPA/SIPTO
  • MEC mobile edge network
  • GTP-U bearer path from the WTRU 502 to the iPGW 406 in order to support seamless hand off for VoIP services and other data services anchored to the iPGW 406.
  • other data services traffic may be routed directly to the internet access network 412 (e.g., packet data network (PDN)) by the iNB 402.
  • the WTRU data traffic path may be connected directly to the internet access network 412 and latency can be reduced.
  • PDN packet data network
  • FIG. 24 a diagram illustrating a non-roaming architecture for the next generation IMT access network and core network.
  • FIG. 24 shows an interworking architecture with a legacy 3GPP access network is shown.
  • the iNB 402 may have multiple links that are directly connected to the internet access network 412.
  • Rl may be a link interface reference point.
  • the Rl interface may have the same interface function of the Gx interface between the iPGW 406 and Policy Control and Charging Rules Function (PCRF) 504 and the SGi interface between the iPGW 406 and the internet access network 412 shown in both FIG. 5 and FIG. 24.
  • PCRF Policy Control and Charging Rules Function
  • the iMME 404 may maintain the connectivity between the WTRU
  • the iNB 402 attached to the WTRU 502.
  • FIG. 24 shows two iNBs 402, one of which may be an old iNB currently connected to the WTRU 502, and the other of which may be a new iNB to which the WTRU 502 is moving to during a handover operation.
  • the WTRU 502 moves to another iNB (i.e., to a new iNB) while a packet from the network is arriving at the old iNB, the old iNB may forward the packet directly to the new iNB.
  • the old iNB may request an address of the newly connected iNB from the iMME 404, for example, when the old iNB does not have or has lost the link information of the new iNB, and then forward the packet to the new iNB upon receiving its address from the iMME 404.
  • the iNB 402 may count the WTRU's Internet packets that terminate at the Rl interface in order to charge the packet count.
  • the iNB 402 may make available the capability of the Rl interface to the WTRU 502 and iMME 404 through the Rl-AP and NAS protocol. Also, the capability of the Rl interface of the iNB 402 may be provided over the broadcast channel over the Radio Resource Control (RRC) as system information.
  • RRC Radio Resource Control
  • the WTRU 502 may have one of the following options for internet connectivity depending on the WTRU's 502 allowed service capabilities.
  • the WTRU 502 may be connected to the internet access network 412 only through the iPGW 406 (e.g., as the WTRU 502 provided in the network architecture shown in FIG. 5) without any connectivity through the Rl interface.
  • the WTRU 502 may be connected to the internet access network 412 through both the Rl interface and also through the iPGW 406.
  • the WTRU 502 may have multiple internet IP addresses allocated from the iPGW 406 and the iNB 402, respectively.
  • the WTRU 502 may be connected to the internet access network 412 only through the Rl interface of the iNB 402 though the mobility and connectivity management (i.e., iMME 404) of a control interface that is connected through an Rl-C interface.
  • iMME 404 mobility and connectivity management
  • the IP address associated with the connection through the iNB Rl interface may change when a handover between iNBs 402 occurs.
  • the characteristics of the IP connectivity of Rl interfaces can be utilized.
  • the Rl interface may be beneficial to low latency and low mobility users and applications, such as Mobile Edge Computing (MEC) applications.
  • MEC Mobile Edge Computing
  • an IP packet that arrives at the Rl path during a handoff procedure may be forwarded by the old iNB to the new iNB through a R6 reference point/interface path.
  • the Rl interface link may also be increased and may be utilized for the network slicing path for other sliced networks further with multiple number of links such as Rl', Rl" etc.
  • FIG. 25 a diagram illustrating a roaming architecture of home routed traffic for a next generation IMT access network and core network is shown.
  • FIG. 25 also illustrates an interworking architecture with a legacy 3GPP access network and home routed traffic. There may not be a difference for the roaming user data traffic path for the home routed traffic case. Thus, the roaming architecture for local breakout cases may be easily developed as given in the 3GPP roaming architecture.
  • FIG. 26 a diagram illustrating a network deployment configuration of I-UTRAN and core network equipment is shown.
  • FIG. 26 shows a flat network architecture without any hierarchical structure among the core network equipment and also for the interconnecting of the iNBs 402.
  • the network equipment may be deployed individually without being combined with other network equipment due to the flexibility and connectivity in the network.
  • the network equipment may be interconnected for serving the associated network equipment by simply allocating provisioning data in the operation centers.
  • FIG. 27 a diagram illustrating a network architecture that employs NFV and SDN friendly network architectures is shown. Since an IP transport network 2702 is separated from the mobile communication network entities, which may be in a NFV domain 2704, the IP transport network may be operable by a SDN control. Therefore, it may be possible to efficiently manage the IP bearer networks depending on the network loading.
  • the functional entities of the network may be virtualized and may be implemented by the NFV domain 2704 over the IP cloud network, with the exception of some of the features of the iNB 402. Moreover, it should be noted that the network entities of the virtualized entity and the non- virtualized physical entity may co-exist on the SDN controlled IP transport network 2702 without impact on the NFV domain 2704.
  • the network slicing may be applied on the network architecture depending on the quality of service (QoS) or service capability set dependent.
  • FIG. 28 a diagram illustrating a network deployment and operation configuration with a fixed and mobile convergence is shown.
  • FIG. 28 shows that the fixed access network may be directly connected to the IP transport network 2702 where the base station iNB 402 is connected to the network.
  • a fixed and mobile converged network may be achieved by the dual link path connection provided by the iNB architecture. Consequently, the network architectures described herein may be employed in next generation networks because they are flat, MEC enabled, have a fixed and mobile convergence, and NFV/SDN enabled.
  • the network entities used in the flat, fixed, and mobile convergence network architectures described herein may be similar to the network entities described above with reference to FIGS. 2-22, but may have additional characteristics.
  • the WTRU 502 may have multiple IP addresses.
  • a first primary IP address used in the WTRU 502 may be allocated from the iPGW's 406 IP address pool by a Dynamic Host Configuration Protocol (DHCP), and may be used for high speed mobility hand off supporting services, such as Voice over LTE (VoLTE), through IPS bearer traffics.
  • DHCP Dynamic Host Configuration Protocol
  • VoIP Voice over LTE
  • IPS bearer traffics Voice over LTE
  • This primary IP address may be anchored to the iPGW 406 while the WTRU 502 is served within the iPGW 406 serving area.
  • a second, third and fourth IP address may be allocated from the iNB's 402 IP address pools by a DHCP depending on the services and services capabilities of the WTRU 520.
  • the secondary and additional supplementary IP address allocated from the iNB 402 may not be anchored and may be dynamically re-allocated by a DHCP within the IP pool of the serving iNB 402 whenever the WTRU 502 moves from one iNB to a new iNB.
  • the iNB 402 may have two or more physical link interfaces.
  • One of the link interfaces may be a physical interface for reference interfaces provided for Rl-U from the iNB 402 to iPGW 406 and for Rl-C from the iNB 402 to iMME 404.
  • a second interface may be a physical interface for the Rl reference interface for directly connecting the iNB 402 to the internet access network 412.
  • the second interface may preserve the publicly addressable IP address pool of the internet, and the IP address may be allocated to the WTRU 502 by a DHCP when the WTRU 502 requests a direct internet connection to the Rl interface.
  • the iMME 404 may manage the multiple allocated IP addresses, such as the primary IP address allocated from the iPGW 406 and the second, third, and fourth IP address allocated from the iNB 402.
  • the iMME 404 may maintain the WTRU's 502 internet connection when the WTRU 502 moves to other iNB 402 (e.g., via handover) by tracking the WTRU's 502 iNB attachment.
  • the layer stacks used in the flat, fixed, and mobile convergence network architectures described herein may be similar to the layer stacks described above with reference to FIGS. 2-22, but may contain distinct layer stacks.
  • the Rl Application Protocol (Rl-AP) 2902 may be an application layer protocol between the iNB 402 and the iMME 404.
  • the Stream Control Transmission Protocol (SCTP) 2904 may refer to a protocol that ensures delivery of signaling messages between the iMME 404 and the iNB 402 (e.g., via Rl-C).
  • NAS 2906 may refer to a Non Access Stratum (NAS) protocol that supports mobility management functionality and user plane bearer activation, modification and deactivation. NAS 2906 may also be responsible for ciphering and integrity protection of NAS signaling.
  • the iUu interface 2908 may refer to radio protocols between the WTRU 502 and the iNB 402. The remaining layers of the stacks may be known in the art.
  • the GTP-C 3004 may refer to a General Packet Radio Service (GPRS) Tunneling Protocol for the control plane. This protocol may tunnel signaling messages between iMMEs 404.
  • the UDP 3006 may refer to a User Datagram Protocol, which may transfer signaling messages between iMMEs 404. The remaining layers of the stacks may be known in the art.
  • GPRS General Packet Radio Service
  • FIG. 31 a diagram illustrating a user plane for an
  • Rl-U interface 3102 employed between a WTRU 502 and an iPGW 406 is shown.
  • the GTP-U 3104 may refer to a GPRS Tunneling Protocol for the user plane. This protocol may tunnel user data through an Rl interface.
  • the UDP/IP 3106 refers to a UDP/Internet Protocol, which may be backbone network protocols used for routing user data and control signaling.
  • the iUu 2908 refers to the radio protocols between the WTRU 502 and the iNB 402. The remaining layers of the stacks may be known in the art.
  • FIG. 32 a diagram illustrating a Rl user plane protocol stack employed between a WTRU 502 and an iNB 402 is shown.
  • the layers of the stacks may be known in the art.
  • 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).
  • ROM read only memory
  • RAM random access memory
  • 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.

Abstract

Des modes de réalisation comprennent des procédés, des systèmes et des appareils pour système de télécommunications mobiles internationales (IMT) de nouvelle génération comprenant un réseau central plat avec une hiérarchie réduite d'architecture de réseau central. Des modes de réalisation comprennent l'élimination d'une entité physique de la SGW du réseau central; la fusion d'une fonction d'entité de commande de la SGW dans une entité de gestion de mobilité innovante (iMME); et la fusion d'une fonction d'entité de données utilisateur de la SGW en passerelle de réseau de données par paquets innovante (iPGW), l'iMME et l'iPGW étant au même niveau du réseau central. Une station de base peut avoir une première interface de liaison physique configurée pour connecter la station de base à l'iPGW et à l'iMME et une seconde interface de liaison physique configurée pour connecter directement la station de base à un réseau d'accès Internet.
PCT/US2016/068497 2015-12-31 2016-12-23 Architecture de réseau de télécommunications mobiles internationales de nouvelle génération et configuration d'interface de référence pour l'approvisionnement de réseau plat WO2017117044A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562273835P 2015-12-31 2015-12-31
US201562273828P 2015-12-31 2015-12-31
US62/273,835 2015-12-31
US62/273,828 2015-12-31

Publications (1)

Publication Number Publication Date
WO2017117044A1 true WO2017117044A1 (fr) 2017-07-06

Family

ID=57822070

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/068497 WO2017117044A1 (fr) 2015-12-31 2016-12-23 Architecture de réseau de télécommunications mobiles internationales de nouvelle génération et configuration d'interface de référence pour l'approvisionnement de réseau plat

Country Status (1)

Country Link
WO (1) WO2017117044A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110474984A (zh) * 2019-08-16 2019-11-19 东南大学 一种物联网通信网络架构
US10728744B2 (en) 2018-04-27 2020-07-28 Hewlett Packard Enterprise Development Lp Transmission outside of a home network of a state of a MEC application
CN111527725A (zh) * 2017-12-15 2020-08-11 诺基亚技术有限公司 用于通过使用网络分片来控制数据传输的方法
US11172041B2 (en) 2019-08-20 2021-11-09 Cisco Technology, Inc. Communication proxy for devices in mobile edge computing networks

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110286465A1 (en) * 2010-05-21 2011-11-24 Cisco Technology, Inc. Multi-tiered paging support using paging priority

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110286465A1 (en) * 2010-05-21 2011-11-24 Cisco Technology, Inc. Multi-tiered paging support using paging priority

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 13)", 15 December 2015 (2015-12-15), XP051071877, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/Latest_SA2_Specs/Rel-13/> [retrieved on 20151215] *
AGYAPONG PATRICK ET AL: "Design considerations for a 5G network architecture", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER, PISCATAWAY, US, vol. 52, no. 11, 1 November 2014 (2014-11-01), pages 65 - 75, XP011564611, ISSN: 0163-6804, [retrieved on 20141113], DOI: 10.1109/MCOM.2014.6957145 *
INTEL CORPORATION: "View on 5G Radio Technology and Standardization", no. Phoenix, AZ, USA; 20150917 - 20150918, 3 September 2015 (2015-09-03), XP051043764, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/workshop/2015-09-17_18_RAN_5G/Docs/> [retrieved on 20150903] *
JOSEPH LEVY (INTERDIGITAL): "Thoughts on 802.11 in a 3GPP 5G Network ; 11-15-1402-00-0wng-thoughts-on-802-11-in-a-3gpp-5g-network", IEEE DRAFT; 11-15-1402-00-0WNG-THOUGHTS-ON-802-11-IN-A-3GPP-5G-NETWORK, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 WNG, 10 November 2015 (2015-11-10), pages 1 - 20, XP068099390 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111527725A (zh) * 2017-12-15 2020-08-11 诺基亚技术有限公司 用于通过使用网络分片来控制数据传输的方法
US10728744B2 (en) 2018-04-27 2020-07-28 Hewlett Packard Enterprise Development Lp Transmission outside of a home network of a state of a MEC application
CN110474984A (zh) * 2019-08-16 2019-11-19 东南大学 一种物联网通信网络架构
CN110474984B (zh) * 2019-08-16 2021-11-26 东南大学 一种物联网通信网络系统
US11172041B2 (en) 2019-08-20 2021-11-09 Cisco Technology, Inc. Communication proxy for devices in mobile edge computing networks

Similar Documents

Publication Publication Date Title
JP6947878B2 (ja) 無線通信システムにおける登録解除方法及びこのための装置
KR102241996B1 (ko) 무선 통신 시스템에서 네트워크간 상호연동 방법 및 이를 위한 장치
US20220338084A1 (en) Method for managing pdu session in wireless communication system and apparatus therefor
US10721665B2 (en) Systems and methods for establishing and maintaining multiple cellular connections and/or interfaces
CN110402604B (zh) 在无线通信系统中通知移动性事件的方法及其设备
US20200252900A1 (en) Method for performing service request procedure and apparatus therefor in wireless communication system
JP6845263B2 (ja) 無線通信システムにおけるＵＭ ＲＬＣエンティティに関連したＰＤＣＰエンティティの再構成（ｒｅ−ｅｓｔａｂｌｉｓｈｍｅｎｔ）のための方法及びその装置
JP6392831B2 (ja) 選択されたインターネットプロトコルトラフィックオフロードのサポートをブロードキャストするための方法および装置
US20180198672A1 (en) Methods For IP Mobility Management
US20190274076A1 (en) Method for supporting ue mobility in wireless communication system and device therefor
EP3282762A1 (fr) Procédé et appareil pour fonctionnement en mode d&#39;accès multi-rat
US20150195863A1 (en) Ip-layer device-to-device communication in mobile networks
WO2013181501A1 (fr) Service de messagerie courte (sms) sur un cœur de paquet évolué au moyen d&#39;un accès wifi
WO2017117044A1 (fr) Architecture de réseau de télécommunications mobiles internationales de nouvelle génération et configuration d&#39;interface de référence pour l&#39;approvisionnement de réseau plat
CN116711377A (zh) 通信网络的切换

Legal Events

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

Ref document number: 16826839

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16826839

Country of ref document: EP

Kind code of ref document: A1