WO2018236867A2 - Séparation de plan de commande et de plan utilisateur dans des systèmes new radio (nr) - Google Patents

Séparation de plan de commande et de plan utilisateur dans des systèmes new radio (nr) Download PDF

Info

Publication number
WO2018236867A2
WO2018236867A2 PCT/US2018/038284 US2018038284W WO2018236867A2 WO 2018236867 A2 WO2018236867 A2 WO 2018236867A2 US 2018038284 W US2018038284 W US 2018038284W WO 2018236867 A2 WO2018236867 A2 WO 2018236867A2
Authority
WO
WIPO (PCT)
Prior art keywords
gnb
interface
message
over
entity
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2018/038284
Other languages
English (en)
Other versions
WO2018236867A3 (fr
Inventor
Alexander Sirotkin
Yifan Yu
Min Huang
Jaemin HAN
Feng Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Intel Corp filed Critical Intel Corp
Priority to EP18820450.7A priority Critical patent/EP3643107B1/fr
Priority to US16/615,081 priority patent/US11197332B2/en
Priority to EP24158242.8A priority patent/EP4346332A3/fr
Publication of WO2018236867A2 publication Critical patent/WO2018236867A2/fr
Publication of WO2018236867A3 publication Critical patent/WO2018236867A3/fr
Anticipated expiration legal-status Critical
Priority to US17/517,182 priority patent/US11632813B2/en
Priority to US18/119,463 priority patent/US12096498B2/en
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • 3GPP LTE Long Term Evolution
  • 3GPP LTE-A Long Term Evolution Advanced
  • 5G Fifth Generation
  • NR New Radio
  • Some embodiments relate to control plane functionality and/or user plane functionality'.
  • Some embodiments relate to splitting of control plane functionality and user plane functionality.
  • FIG 11 A and FIG 1 IB illustrate example operations and example messages that may be exchanged in accordance with some
  • the network 100 may include (and/or support) one or more Evolved Node-B's (eNBs) 104 (which may operate as base stations) for communicating with User Equipment (UE) 102.
  • eNBs Evolved Node-B's
  • the eNBs 104 may include macro eNBs and low power (LP) eNBs, in some embodiments.
  • the network 100 may include (and/or support) one or more Next Generation Node-B's (gNBs) 105.
  • gNBs Next Generation Node-B's
  • one or more eNBs 104 may be configured to operate as gNBs 105. Embodiments are not limited to the number of eNBs 104 shown in FIG. 1 A or to the number of gNBs 105 shown in FIG. 1A. In some embodiments, the network 100 may not necessarily include eNBs 104. Embodiments are also not limited to the connectivity of components shown in FIG. 1 A
  • references herein to an eNB 104 or to a gNB 105 are not limiting.
  • one or more operations, methods and/or techniques may be practiced by a base station component (and/or other component), including but not limited to a gNB 105, an eNB 104, a serving cell, a transmit receive point (TRP) and/or other.
  • the base station component may be configured to operate in accordance with a New Radio (NR) protocol and/or NR standard, although the scope of embodiments is not limited in this respect.
  • the base station component may be configured to operate in accordance with a Fifth Generation (5G) protocol and/or 5G standard, although the scope of embodiments is not limited in this respect.
  • 5G Fifth Generation
  • the gNB 105 may include multiple components.
  • the gNB 105 may comprise one or more of: a central unit control (CU-C) entity 106, a central unit user (CU-U) entity 107, a distributed unit (DU) 108 and/or other components).
  • the CU-C entity 106 and the CU-U entity 107 may communicate over the El interface 109, although the scope of embodiments is not limited in this respect.
  • the CU-C entity 106 and the DU 108 may communicate over the Fl-C interface 110, although the scope of embodiments is not limited in this respect.
  • the CU-C entity 106, the CU-U entity 107, and the DU 108 may be part of a disaggregated gNB 105.
  • One or more of the CU-C entity 106, the CU-U entity 107, and the DU 108 may be co-located, in some embodiments.
  • One or more of the CU-C entity 106, the CU-U entity 107, and the DU 108 may not necessarily be co-located, in some embodiments.
  • Other arrangements are possible, including arrangements in which two or more of the CU-U entity 107, the CU-C entity 106 and the DU 108 are co-located.
  • references herein to communication between the gNB 105 and another component are not limiting. In some embodiments, such communication may be performed between the component (such as the UE 102, MME 122, SGW 124 and/or other) and one of the CU-C entity 106, CU-U entity 107, DU 108.
  • References herein to an operation, technique and/or method performed by the gNB 105 are not limiting. In some embodiments, such an operation, technique and/or method may be performed by one of the CU-C entity 106, CU-U entity 107, DU 108.
  • CU-C entity 106, CU-U entity 107, DU 108 and/or eNBs 104 may be configured to operate in accordance with an NR protocol and/or NR techniques.
  • References to a UE 102, eNB 104, CU-C entity 106, CU-U entity 107, DU 108 and/or gNB 105 as part of descriptions herein are not limiting.
  • descriptions of one or more operations, techniques and/or methods practiced by a gNB 105 are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by an eNB 104 and/or other base station component.
  • the MME 122 is similar in function to the control plane of legacy
  • the MME 122 manages mobility aspects in access such as gateway selection and tracking area list management.
  • the serving GW 124 terminates the interface toward the RAN 101, and routes data packets between the RAN 101 and the core network 120. In addition, it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.
  • the PDN GW 126 terminates an SGi interface toward the packet data network (PDN).
  • PDN packet data network
  • the PDN GW 126 routes data packets between the EPC 120 and the external PDN, and may be a key node for policy enforcement and charging data collection. It may also provide an anchor point for mobility with non-LTE accesses.
  • the external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the PDN GW 126 and the serving GW 124 may be implemented in one physical node or separated physical nodes.
  • the eNBs 104 terminate the air interface protocol and may be the first point of contact for a UE 102.
  • an eNB 104 may fulfill various logical functions for the network 100, including but not limited to RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • the S 1 interface 115 (and/or similar interface) may be split into two parts: the Sl-U, which carries traffic data between the gNBs 105 and the serving GW 124, and the Sl-MME, which is a signaling interface between the gNBs 104 and the MME 122.
  • the X2 interface (and/or similar interface) may enable
  • LP cells are typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with very dense phone usage, such as train stations.
  • the term low power (LP) eNB refers to any suitable relatively low power eNB for implementing a narrower cell (narrower than a macro cell) such as a femtocell, a picocell, or a micro cell.
  • Femtocell eNBs are typically provided by a mobile network operator to its residential or enterprise customers.
  • a femtocell is typically the size of a residential gateway or smaller and generally connects to the user's broadband line.
  • a picocell is a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft.
  • a picocell eNB can generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC)
  • LP eNB may be implemented with a picocell eNB since it is coupled to a macro eNB via an X2 interface.
  • Picocell eNBs or other LP eNBs may incorporate some or all functionality of a macro eNB. In some cases, this may be referred to as an access point base station or enterprise femtocell.
  • various types of gNBs 105 may be used, including but not limited to one or more of the eNB types described above.
  • the network 150 may include one or more components configured to operate in accordance with one or more 3GPP standards, including but not limited to an NR standard.
  • the network 150 shown in FIG. IB may include a next generation RAN (NG-RAN) 155, which may include one or more gNBs 105.
  • the network 150 may include the E-UTRAN 160, which may include one or more eNBs.
  • the E- UTRAN 160 may be similar to the RAN 101 described herein, although the scope of embodiments is not limited in this respect.
  • the network 1 SO may include the MME
  • the MME 165 may be similar to the MME 122 described herein, although the scope of embodiments is not limited in this respect.
  • the MME 165 may perform one or more operations or functionality similar to those described herein regarding the MME 122, although the scope of embodiments is not limited in this respect.
  • the network 150 may include the SGW
  • the SGW 170 may be similar to the SGW 124 described herein, although the scope of embodiments is not limited in this respect.
  • the SGW 170 may perform one or more operations or functionality similar to those described herein regarding the SGW 124, although the scope of embodiments is not limited in this respect.
  • the network 150 may include
  • the network 150 may include component(s) and/or module(s) for functionality for a session management function (SMF) and control plane functionality for PGW (PGW-C), as indicated by 180.
  • the component(s) and/or module(s) indicated by 175 and/or 180 may be similar to the PGW 126 described herein, although the scope of embodiments is not limited in this respect.
  • the component(s) and/or module(s) indicated by 175 and/or 180 may perform one or more operations or functionality similar to those described herein regarding the PGW 126, although the scope of embodiments is not limited in this respect.
  • One or both of the components 170, 172 may perform at least a portion of the functionality described herein for the PGW 126, although the scope of embodiments is not limited in this respect.
  • Embodiments are not limited to the number or ty pe of components shown in FIG IB. Embodiments are also not limited to the connectivity of components shown in FIG. IB.
  • a downlink resource grid may be used for downlink transmissions from an eNB 104 to a UE 102, while uplink
  • a downlink resource grid may be used for downlink transmissions from a gNB 105 to a UE 102, while uplink transmission from the UE 102 to the gNB 105 may utilize similar techniques.
  • Hie grid may be a time- frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element (RE).
  • RE resource element
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
  • FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments.
  • the machine 200 is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed.
  • the machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 200 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 200 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the machine 200 may be a UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, access point (AP), station (ST A), user, device, mobile device, base station, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that
  • Examples as described herein may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the machine 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • the machine 200 may further include a display unit 210, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
  • the machine 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors 221, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • the machine 200 may include an output controller 228, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (JR.), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (JR.), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • JR. infrared
  • the storage device 216 may include a machine readable medium
  • the instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine
  • one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute machine readable media.
  • the machine readable medium may be or may include a non-transitory computer-readable storage medium.
  • the machine readable medium may be or may include a computer-readable storage medium.
  • machine readable medium 222 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
  • the term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable
  • machine readable media may include non-transitory machine readable media.
  • machine readable media may include machine readable media that is not a transitory propagating signal.
  • the instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • wireless data networks e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®
  • IEEE 802.15.4 family of standards e.g., Institute of Electrical and Electronics Engineers (IEEE
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 226.
  • the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input multiple-output
  • MISO multiple-input single-output
  • the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
  • FIG. 3 illustrates a user device in accordance with some aspects.
  • the user device 300 may be a mobile device. In some embodiments, the user device 300 may be or may be configured to operate as a User Equipment (UE). In some embodiments, the user device 300 may be arranged to operate in accordance with a new radio (NR.) protocol. In some embodiments, the user device 300 may be arranged to operate in accordance with a Third Generation Partnership Protocol (3GPP) protocol.
  • the user device 300 may be suitable for use as a UE 102 as depicted in FIG. 1, in some embodiments. It should be noted that in some embodiments, a UE, an apparatus of a UE, a user device or an apparatus of a user device may include one or more of the components shown in one or more of FIGs. 2, 3, and 5. In some embodiments, such a UE, user device and/or apparatus may include one or more additional components.
  • the user device 300 may include an application processor 305, baseband processor 310 (also referred to as a baseband module), radio front end module (RFEM) 315, memory 320, connectivity module 325, near field communication (NFC) controller 330, audio driver 335, camera driver 340, touch screen 345, display driver 350, sensors 355, removable memory 360, power management integrated circuit (PMIC) 365 and smart battery 370.
  • the user device 300 may be a User Equipment (UE).
  • UE User Equipment
  • application processor 305 may include, for example, one or more CPU cores and one or more of cache memory, low dropout voltage regulators (LDOs), interrupt controllers, serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I 2 C) or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (10), memory card controllers such as secure digital / multi-media card (SD/MMC) or similar, universal serial bus (USB) interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low dropout voltage regulators
  • interrupt controllers serial interfaces such as serial peripheral interface (SPI), inter-integrated circuit (I 2 C) or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input-output (10), memory card controllers such as secure digital / multi-media card (SD/MMC) or similar
  • baseband module 310 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, and/or a multi-chip module containing two or more integrated circuits.
  • FIG. 4 illustrates a base station in accordance with some aspects.
  • the base station 400 may be or may be configured to operate as an Evolved Node-B (eNB). In some embodiments, the base station 400 may be or may be configured to operate as a Next Generation Node-B (gNB). In some embodiments, the base station 400 may be arranged to operate in accordance with a new radio (NR.) protocol. In some embodiments, the base station 400 may be arranged to operate in accordance with a Third Generation Partnership Protocol (3GPP) protocol. It should be noted that in some embodiments, the base station 400 may be a stationary non-mobile device. The base station 400 may be suitable for use as an eNB 104 as depicted in FIG. 1 , in some embodiments.
  • the base station 400 may be suitable for use as a gNB 105 as depicted in FIG. 1, in some embodiments.
  • an eNB, an apparatus of an eNB, a gNB, an apparatus of a gNB, a CU-C entity 106, a CU-U entity 107, a DU 108, an apparatus of a CU-C entity 106, an apparatus of a CU-U entity 107, an apparatus of a DU 108, a base station and/or an apparatus of a base station may include one or more of the components shown in one or more of FIGs. 2, 4, and 5.
  • such an eNB, gNB, CU-C entity 106, CU-U entity 107, DU 108, base station and/or apparatus may include one or more additional components.
  • FIG. 4 illustrates a base station or infrastructure equipment radio head 400 in accordance with an aspect.
  • the base station 400 may include one or more of application processor 405, baseband modules 410, one or more radio front end modules 415, memory 420, power management circuitry 425, power tee circuitry 430, network controller 435, network interface connector 440, satellite navigation receiver module 445, and user interface 450.
  • the base station 400 may be an Evolved Node-B (eNB), which may be arranged to operate in accordance with a 3GPP protocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol.
  • the base station 400 may be a Next Generation Node-B (gNB), which may be arranged to operate in accordance with a 3GPP protocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol.
  • gNB Next Generation Node-B
  • application processor 405 may include one or more CPU cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I 2 C or universal programmable serial interface module, real time clock (RTC), timer- counters including interval and watchdog timers, general purpose IO, memory card controllers such as SD/MMC or similar, USB interfaces, MIPI interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I 2 C or universal programmable serial interface module
  • RTC real time clock
  • timer- counters including interval and watchdog timers
  • general purpose IO memory card controllers such as SD/MMC or similar
  • USB interfaces such as SD/MMC or similar
  • MIPI interfaces Joint Test Access Group (JTAG) test access ports.
  • JTAG Joint Test Access Group
  • baseband processor 410 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • memory 420 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magneto-resistive random access memory (MRAM) and/or a three-dimensional cross-point memory.
  • volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magneto-resistive random access memory (MRAM) and/or a three-dimensional cross-point memory.
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • NVM nonvolatile memory
  • Flash memory high-speed electrically erasable memory
  • PRAM phase change random access memory
  • MRAM magneto-res
  • power management integrated circuitry 425 may include one or more of voltage regulators, surge protectors, power alarm detection circuitry and one or more backup power sources such as a battery or capacitor.
  • Power alarm detection circuitry may detect one or more of brown out
  • power tee circuitry 430 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the base station 400 using a single cable.
  • network controller 435 may provide connectivity to a network using a standard network interface protocol such as Ethernet.
  • Network connectivity may be provided using a physical connection which is one of electrical (commonly referred to as copper interconnect), optical or wireless.
  • satellite navigation receiver module 445 may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations such as the global positioning system (GPS), Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS), Galileo and/or BeiDou.
  • the receiver 445 may provide data to application processor 405 which may include one or more of position data or time data
  • application processor 405 may use time data to synchronize operations with other radio base stations.
  • user interface 450 may include one or more of physical or virtual buttons, such as a reset button, one or more indicators such as light emitting diodes (LEDs) and a display screen.
  • LEDs light emitting diodes
  • FIG. 5 illustrates an exemplary communication circuitry according to some aspects.
  • Circuitry 500 is alternatively grouped according to functions. Components as shown in 500 are shown here for illustrative purposes and may include other components not shown here in Fig. 5.
  • the communication circuitry 500 may be used for millimeter wave
  • Communication at any suitable frequency may be performed by the communication circuitry 500 in some aspects.
  • a device such as a UE 102, eNB 104, gNB
  • the user device 300, the base station 400, the machine 200 and/or other device may include one or more components of the communication circuitry 500, in some aspects.
  • the communication circuitry 500 may include protocol processing circuitry 505, which may implement one or more of medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS) functions.
  • Protocol processing circuitry 505 may include one or more processing cores (not shown) to execute instructions and one or more memory structures (not shown) to store program and data information.
  • the communication circuitry 500 may further include digital baseband circuitry 510, which may implement physical layer (PHY) functions including one or more of hybrid automatic repeat request (HARQ) functions, scrambling and/or descrambling, coding and/or decoding, layer mapping and/or de-mapping, modulation symbol mapping, received symbol and/or bit metric determination, multi-antenna port pre-coding and/or decoding which may include one or more of space-time, space-frequency or spatial coding, reference signal generation and/or detection, preamble sequence generation and/or decoding, synchronization sequence generation and/or detection, control channel signal blind decoding, and other related functions.
  • PHY physical layer
  • HARQ hybrid automatic repeat request
  • the communication circuitry 500 may further include transmit circuitry 515, receive circuitry 520 and/or antenna array circuitry 530.
  • the communication circuitry 500 may further include radio frequency (RF) circuitry 525.
  • RF circuitry 525 may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array 530.
  • protocol processing circuitry 505 may include one or more instances of control circuitry (not shown) to provide control functions for one or more of digital baseband circuitry 510, transmit circuitry 515, receive circuitry 520, and/or radio frequency circuitry 525
  • processing circuitry may perform one or more operations described herein and/or other operations).
  • the processing circuitry may include one or more components such as the processor 202, application processor 305, baseband module 310, application processor 405, baseband module 410, protocol processing circuitry 505, digital baseband circuitry 510, similar components) and/or other components).
  • a transceiver may transmit one or more elements (including but not limited to those described herein) and/or receive one or more elements (including but not limited to those described herein).
  • the transceiver may include one or more components such as the radio front end module 315, radio front end module 415, transmit circuitry 515, receive circuitry 520, radio frequency rircuitry 525, similar component(s) and/or other component(s).
  • One or more antennas may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • M1MO multiple-input multiple-output
  • one or more of the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may be a mobile device and/or portable wireless communication device, such as a personal digital assistant
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly.
  • a medical device e.g., a heart rate monitor, a blood pressure monitor, etc.
  • other device may receive and/or transmit information wirelessly.
  • the UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may be configured to operate in accordance with 3GPP standards, although the scope of the embodiments is not limited in this respect.
  • the UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may be configured to operate in accordance with new radio (NR.) standards, although the scope of the embodiments is not limited in this respect.
  • NR. new radio
  • the UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may be configured to operate according to other protocols or standards, including IEEE 802.11 or other IEEE standards.
  • the UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • LT entity 107, DU 108, user device 300, base station 400, machine 200 and/or other device described herein may each be illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • UE 102, eNB 104, gNB 105, CU-C entity 106, CU-U entity 107, DU 108, machine 200, user device 300 and/or base station 400 may include various components shown in FIGs. 2-5. Accordingly, techniques and operations described herein that refer to the UE 102 may be applicable to an apparatus of a UE. In addition, techniques and operations described herein that refer to the eNB 104 may be applicable to an apparatus of an eNB. In addition, techniques and operations described herein that refer to the gNB 105 may be applicable to an apparatus of a gNB. In addition, techniques and operations described herein that refer to the CU-C entity 106, may be applicable to an apparatus of a CU-C entity.
  • CU-U entity 107 may be applicable to an apparatus of a CU-U entity.
  • techniques and operations described herein that refer to the DU 108 may be applicable to an apparatus of a DU.
  • CU-C entity 106 may refer to performance of operations, methods and/or techniques by elements such as the CU-C entity 106, CU-U entity 107, and the DU 108. Such references are not limiting, however.
  • One or more of the operations, methods and/or techniques may be performed by one or more other entities, in some embodiments.
  • an operation, method and/or technique described herein as performed by the CU-C entity 106 may be performed by a gNB-CU control plane (gNB-CU-CP) entity, in some embodiments.
  • gNB-CU-CP gNB-CU control plane
  • an operation, method and/or technique described herein as performed by the CU-U entity 107 may be performed by a gNB-CU user plane (gNB-CU- UP) entity, in some embodiments.
  • an operation, method and/or technique described herein as performed by the DU 108 may be performed by a gNB distributed unit (gNB-DU) entity, in some embodiments.
  • gNB may be configured with logical nodes, including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU).
  • the gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, and a gNB-CU user plane (gNB-CU-UP) for user-plane functionality.
  • the gNB-CU- CP may be configured to communicate with the gNB-CU-UP over an El interface.
  • the gNB-CU-UP may be configured to communicate user plane messages with the gNB-DU over an Fl user-plane interface (Fl-U).
  • the gNB- CU-CP may be configured to communicate control plane messages with the gNB-DU over an Fl control plane interface (Fl-C).
  • An apparatus of the gNB may comprise memory and processing circuitry.
  • the processing circuitry may be configured to initiate an El interface setup procedure to establish the El interface by sending a GNB-CU-UP El setup request message from the gNB- CU-UP to the gNB-CU-CP.
  • the processing circuitry may be further configured to initiate a bearer context setup procedure to establish a bearer context in the gNB-CU-UP by sending a bearer context setup request message from the gNB- CU-CP to the gNB-CU-UP over the El interface.
  • the processing circuitry may be further configured to initiate a UE context setup procedure to establish UE context by sending a UE context setup request message from the gNB-CU-CP to the gNB-DU over the Fl-C, the UE context including a signaling radio bearer (SRB) configuration and a data radio bearer (DRB) configuration.
  • the processing circuitry may be further configured to transfer an initial radio- resource control (RRC) message as an uplink (UL) PDCP-PDU from the gNB- DU to the gNB-CU-CP over the Fl-C.
  • RRC radio- resource control
  • the UE context setup request message may be configured to include quality-of-service parameters for the DRB configuration.
  • the memory may be configured to store the DRB configuration.
  • FIG. 6 illustrates the operation of a method of communication in accordance with some embodiments. It is important to note that embodiments of the method 600 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 6. In some embodiments, the method 600 may include one or more operations not shown in FIG. 6, including but not limited to one or more operations shown in one or more of FIGs. 11-13.
  • embodiments of the method 600 are not necessarily limited to the chronological order that is shown in FIG. 6.
  • a CU-C entity 106 may perform one or more operations of the method 600, but embodiments are not limited to performance of the method 600 and/or operations of it by the CU-C entity 106.
  • a gNB 105, an eNB 104 configured to operate as a gNB 105, an eNB 104, a UE 102 and/or other component may perform one or more operations of the method 600 (and/or similar operations).
  • a gNB 105, an eNB 104 configured to operate as a gNB 105, an eNB 104, a UE 102 and/or other component may perform one or more operations that may be reciprocal to one or more operations of the method 600.
  • DU 108 and/or gNB 105 may be arranged to operate in accordance with a New Radio (NR.) standard and/or protocol, although the scope of embodiments is not limited in this respect.
  • NR. New Radio
  • the method 600 and other methods described herein may refer to CU-C entities 106, CU-U entities 107, DUs 108, eNBs 104, gNBs 105 and/or UEs 102 operating in accordance with 3GPP standards, 5G standards, NR standards and/or other standards, embodiments of those methods are not limited to just those devices, and may also be practiced on other devices, such as a Wi-Fi access point (AP) or user station (STA).
  • AP Wi-Fi access point
  • STA user station
  • the method 600 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.11.
  • the method 600 and/or other methods described herein may also be applicable to an apparatus of a CU-C entity 106, an apparatus of a CU-U entity 107, an apparatus of a DU 108 and/or an apparatus of a gNB 105 and/or an apparatus of another device described above.
  • embodiments are not limited by- references herein (such as in descriptions of the methods 600, 700 and 800 and/or other descriptions herein) to transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements.
  • an element may be generated, encoded or otherwise processed by processing circuitry (such as by a baseband processor included in the processing circuitry) for transmission.
  • the transmission may be performed by a transceiver or other component, in some cases.
  • such an element may be decoded, detected or otherwise processed by the processing circuitry (such as by the baseband processor).
  • the element may be received by a transceiver or other component, in some cases.
  • the processing circuitry and the transceiver may be included in a same apparatus. The scope of embodiments is not limited in this respect, however, as the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.
  • the CU-C entity 106, CU-U entity 107, DU 108 and/or gNB 105 may be arranged to operate in accordance with a New Radio (NR.) protocol and/or standard, although the scope of embodiments is not limited in this respect.
  • NR. New Radio
  • the CU-C entity 106 may be included in a disaggregated Next Generation Node-B (gNB) 1 OS that comprises a central unit (CU) and a distributed unit (DU) 108.
  • the CU may comprise the CU-C entity 106 for control-plane functionality and the CU-U entity 107 for user-plane functionality.
  • the CU-C entity 106 may be configurable for operation in which the CU-C entity 106 and the CU-U entity 107 are not co- located. In some embodiments, the CU-C entity 106 may be configurable for operation in which the CU-C entity 106 and the DU 108 are not co-located. Other arrangements are possible, including arrangements in which two or more of the CU-U entity 107, the CU-C entity 106 and the DU 108 are co-located.
  • the CU-C entity 106 may transmit, to a DU 108, a UE context setup message that includes one or more parameters for an establishment of a data radio bearer (DRB).
  • the UE context setup message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the UE context setup message in operation 605, as any suitable message may be used.
  • one or more messages exchanged between the CU-C entity 106 and the DU 108 may be transmitted on an Fl interface, although the scope of embodiments is not limited in this respect.
  • the DRB may be established for exchange of data packets between a UE 102 and the CU-U entity 107 via the DU 108, although the scope of embodiments is not limited in this respect.
  • the parameters of the UE context setup message of operation 605 may be related to one or more of: a physical (PHY) layer of the DU 108, a medium access control (MAC) layer of the DU 108, a radio link control (RLC) layer of the DU 108 and/or other layer.
  • PHY physical
  • MAC medium access control
  • RLC radio link control
  • the parameters may include one or more of: an aggregate maximum bit rate (AMBR) for the UE, a quality of sendee (QoS) parameter, a latency, a bit error rate, a packet error rate and/or other.
  • AMBR aggregate maximum bit rate
  • QoS quality of sendee
  • the CU-C entity 106 may transmit, to the CU-U entity 107, a UE context setup message that includes information related to the DRB.
  • the UE context setup message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the UE context setup message in operation 610, as any suitable message may be used.
  • one or more messages exchanged between the CU-C entity 106 and the CU-U entity 107 may be transmitted on an El interface, although the scope of embodiments is not limited in this respect.
  • the UE context setup message of operation 610 may include an access stratum (AS) security key for encryption and decryption of the data packets of the DRB. Additional information and/or alternate information may be included in the message of operation 610, in some embodiments.
  • AS access stratum
  • the UE context setup message of operation is
  • 610 and the UE context setup message of operation 605 may be different messages, although the scope of embodiments is not limited in this respect.
  • the CU-C entity 106 may transmit, to the DU
  • a UE context modify message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the UE context modify message in operation 615, as any suitable message may be used.
  • the UE context modify message may include one or more updated values of one of the parameters of the UE context setup message of operation 60S. Additional information and/or alternate information may be included, in some embodiments.
  • the CU-C entity 106 may transmit, to the DU
  • a UE context release message to indicate that the DRB is to be released.
  • the UE context release message may be included in a 3GPP standard, NR. standard and/or other standard, although the scope of embodiments is not limited in this respect.
  • Embodiments are not limited to usage of the UE context release message in operation 620, as any suitable message may be used.
  • the CU-C entity 106 may receive, from a core network (CN), control signaling that indicates mat the UE 102 is to be paged.
  • CN core network
  • the CU-C entity 106 may receive the control signaling from a component of the CN (such as the MME 122, SGW 124 and/or other component), although the scope of embodiments is not limited in this respect.
  • control signaling may indicate that the UE 102 is to be paged for reception of one or more downlink data packets, although the scope of embodiments is not limited in this respect. For instance, the UE 102 may be paged for other purposes, in some cases.
  • control signaling may include information related to one or more of: a paging identifier of the UE 102, paging identifiers of a group of UEs 102 (which may include the UE 102), a paging occasion and/or other information.
  • the CU-C entity 106 may transmit, to the DU 108, a paging configure message.
  • the paging configure message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the paging configure message in operation 630, as any suitable message may be used.
  • the paging configure message may indicate one or more of: a paging identity of the UE 102, a paging occasion in which the UE 102 is to be paged and/or other information.
  • the CU-C entity 106 may transmit, to the DU 108, minimum system information (MSI). In some embodiments, the CU-C entity 106 may determine the MSI, although the scope of embodiments is not limited in this respect.
  • MSI minimum system information
  • the CU-C entity 106 may transmit the MSI to the DU 108 for broadcast by the DU 108, although the scope of embodiments is not limited in this respect.
  • the MSI may include a master information block (MIB) and a type 1 SI block (SIB-1).
  • the MSI may include one or more of: an MIB, an SIB-1 and/or other.
  • the CU-C entity 106 may receive, from the DU 108, a request for on-demand system information.
  • the CU-C entity 106 may determine the on-demand system information.
  • the CU-C entity 106 may transmit, to the DU 108, the on-demand system information.
  • the CU-C entity 106 may receive the request from the DU 108, wherein the DU 108 operates as a relay for the UE 102. In some embodiments, the CU-C entity 106 may receive the request from the DU 108 on behalf of the UE 102.
  • the CU-C entity 106 may transmit the on- demand system information to the DU 108 as part of a downlink RRC message transfer.
  • the CU-C entity 106 may transmit a downlink RRC message transfer that includes the on-demand system information.
  • the downlink RRC message transfer may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the downlink RRC message transfer in operation 650, as any suitable message may be used.
  • the CU-C entity 106 may receive, from the CU- U entity 107, a CU-U error indication message.
  • the CU-U error indication message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect.
  • Embodiments are not limited to usage of the CU-U error indication message in operation 655, as any suitable message may be used.
  • the CU-C entity 106 may transmit, to the DU entity 108, a DL RRC message transfer message.
  • the message may be intended for the UE 102 and forwarded by the DU 108, although the scope of embodiments is not limited in this respect.
  • the message may be used to configure, reconfigure or release RRC connection.
  • the DL RRC message transfer message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the DL RRC message transfer message in operation 660, as any suitable message may be used.
  • the CU-C entity 106 may receive, from the DU entity 108, a UL RRC message transfer message, which may encapsulate the RRC message sent by the UE 102.
  • the message may be used for one or more of: to report measurement results, to respond to an RRC connection request and/or other operation(s).
  • the UL RRC message transfer message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the UL RRC message transfer message in operation 665, as any suitable message may be used.
  • the CU-U error indication message may indicate one or more of: a packet data convergence protocol (PDCP) outage of the DRB, a hardware failure, an unavailability of a transport resource and/or other information. Additional information and/or alternate information may be included, in some embodiments.
  • PDCP packet data convergence protocol
  • the CU-U entity 107 may forward decrypted uplink data packet(s) to the CN, although the scope of embodiments is not limited in this respect. For instance, some embodiments may not necessarily include operation 715.
  • the CU-U entity 107 may be configurable for operation in which the CU-U entity 107 and the CU-C entity 106 are not co- located. In some embodiments, the CU-U entity 107 may be configurable for operation in which the CU-U entity 107 and the DU 108 are not co-located. Other arrangements are possible, including arrangements in which two or more of the CU-U entity 107, the CU-C entity 106 and the DU 108 are co-located.
  • a CU-U entity 107 may comprise memory.
  • the memory may be configurable to store information mat identifies the AS security key.
  • the memory may store one or more other elements and the apparatus may use them for performance of one or more operations.
  • the CU-U entity 107 may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method 700 and/or other methods described herein).
  • the processing circuitry may include a baseband processor.
  • the baseband circuitry and/or the processing circuitry may perform one or more operations described herein, including but not limited to decoding of one or more UE context setup messages.
  • the CU-U entity 107 may include a transceiver to receive one or more UE context setup messages. The transceiver may transmit and/or receive other blocks, messages and/or other elements.
  • the DU 108 may receive, from the CU-C entity 106, a UE context setup message.
  • the UE context setup message may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the UE context setup message in operation 80S, as any suitable message may be used.
  • the UE context setup message may configure a DRB between the UE 102 and the CU-U entity 106 via the DU 108. In some embodiments, the UE context setup message may be used to configure a DRB between the UE 102 and the CU-U entity 106 via the DU 108. In some embodiments, the UE context setup message may include information related to a DRB between the UE 102 and the CU-U entity 106 via the DU 108.
  • the DU 108 may perform one or more operations similar to operations 815-820 for the downlink. For instance, the DU 108 may receive a downlink data packet from CU-U that is intended for the UE 102. The DU 108 may transmit and/or forward the downlink data packet to the UE 102.
  • the DU 108 may receive, from the CU-C entity
  • a paging configure message may be included in a 3GPP standard, NR. standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the paging configure message in operation 825, as any suitable message may be used.
  • the paging configure message may include information related to one or more of: a paging identifier of the UE 102, paging identifiers of a group of UEs 102 (which may include the UE 102), a paging occasion and/or other information.
  • the DU 108 may transmit, to the CU-C entity 106, the request for on-demand system information.
  • the DU 108 may transmit the request to the CU-C entity 106 as part of an uplink RRC message transfer.
  • the DU 108 may transmit an uplink RRC message transfer that includes the request.
  • the uplink RRC message transfer may be included in a 3GPP standard, NR standard and/or other standard, although the scope of embodiments is not limited in this respect. Embodiments are not limited to usage of the uplink RRC message transfer in operation 855, as any suitable message may be used.
  • one or both of operations 855-860 may not necessarily be included.
  • the DU 108 may determine the on- demand information (at operation 865), and may not necessarily send the request to the CU-C entity 106.
  • a first portion of the on-demand system information may be determined by the DU 108 and a second portion of the on- demand system information may be received from the CU-C entity 106.
  • FIG. 9 illustrates examples of protocol layers and functional splits in accordance with some embodiments.
  • FIG. 10 illustrates an example architecture in accordance with some embodiments.
  • FIG. 11 A and FIG. 1 IB illustrate example operations and example messages that may be exchanged in accordance with some embodiments.
  • FIG. 11 may include FIG. 11 A and FIG. 1 IB.
  • FIG. 12 illustrates additional example operations and additional example messages that may be exchanged in accordance with some embodiments.
  • FIG. 13 illustrates additional example operations and additional example messages that may be exchanged in accordance with some embodiments. It should be noted mat the examples shown in FlGs. 9-13 may illustrate some or all of the concepts and techniques described herein in some cases, but embodiments are not limited by the examples.
  • embodiments are not limited by the name, number, type, size, ordering, arrangement and/or other aspects of the operations, messages, gNBs 105, UEs 102, CU-C entities 106, CU-U entities 107, DUs 108, and other elements as shown in FIGs. 9-13. Although some of the elements shown in the examples of FIGs. 9-13 may be included in a 3GPP LTE standard,
  • the RAN architecture 1000 includes C- plane/U-plane separation for CU.
  • NG-C and NG-U may be applicable to RAN3 arrangements.
  • SA2 arrangements may use N2 and N3 instead of NG-C and NG-U, respectively.
  • the CU-C 1030 may perform one or more control functions and may support the PDCP of SRB (shown as PDCP-C 1034).
  • RRC 1032 and/or NGAP of one or more UEs 102 may be performed by the CU-C 1030.
  • functionality related to access/mobility management and performance optimization, including but not limited to RRM, may be implemented in a central manner in CU-C 1030.
  • the CU-C 1030 may have a global view of the network.
  • the distributed unit (DU) 1010 may perform one or more operations related to RLC 1012, PHY 1014 and/or MAC 1016.
  • the Fl-U interface 1022 may perform one or more of: transfer PDCP PDU of DRB/SRB between CU-U 1040 and the DU 1010.
  • the NG-U interface 1062 (and/or N3 interface) may perform one or more of: transfer GTP-U between 5GC 1070 and CU-U 1040; and/or other.
  • the NG-C interface 1060 may perform one or more of: communicate control messages between CU-C 1030 and 5GC 1070; and/or other.
  • one or more messages may be exchanged between two or more of the elements shown in FIG. 10.
  • such messages may be part of an Fl-AP (an application protocol used on the control plane of the Fl interface).
  • Example messages are shown in the table below. The direction of the messages (such as which components may exchange the messages) are also shown.
  • example fields are also shown. Embodiments are not limited to the message names shown in the table. Embodiments are also not limited to the fields shown in the table or to the field names shown in the table. In some embodiments, one or more additional fields may be used in one or more messages.
  • a message shown in the table may not necessarily include all corresponding fields shown in the table.
  • the CU-C 1030 may issue two kinds of paging configuration messages, depending on whether DU 1010 and CU-C 1030 are synchronized.
  • Embodiments are also not limited to the fields shown in the table or to the field names shown in the table. In some embodiments, one or more additional fields may be used in one or more messages. In some embodiments, a message shown in the table may not necessarily include all corresponding fields shown in the table.
  • a recipient may send a response and/or
  • acknowledgement in response to a message from a sender (including but not limited to one of the elements shown in FIG. 10).
  • the scope of embodiments is not limited in this respect, however, as one or more of the operations shown in FIG. 11 may be performed as part of other procedures/processes/methods. In some embodiments, one or more operations shown in FIG. 11 may be performed during an initial attach.
  • the example 1100 may be based at least partly on Fl-U based on GTP-U.
  • a TEID may include information regarding the identity of radio bearers.
  • one or more of the messages included in the above tables may be exchanged between DU 1010, CU-C 1030 and/or CU-U 1040.
  • various RRC messages (such as 1110-1114 and/or other) may be exchanged between the DU 1010 and the UE 102.
  • various RRC messages (such as 1121-1127 and/or other) may be exchanged between the DU 1010 and the CU-C 1030.
  • an example 1200 is shown.
  • the example 1200 may be for intra CU-U handover.
  • the scope of embodiments is not limited in this respect, however, as one or more of the operations shown in FIG. 12 may be performed as part of other
  • one or more of the messages included in the above tables may be exchanged between the UE 102, source DU 1010, target DU 1010, CU-C 1030 and/or CU-U 1040.
  • the handover may be from source DU 1010 to target DU 1010.
  • the same CU-U 1040 may be used before and after the handover.
  • a measurement operation may include one or more of: transmission of a measurement report from UE 102 to source DU 1010; a UL RRC message transfer from source DU 1010 to CU-C 1030; and/or other.
  • the measurement operation may at least partly trigger the handover procedure, in some embodiments.
  • the CU-C 1030 may send an RB configure message (as indicated by 1215) via El to CU-U 1040.
  • the RB configure message 1215 may indicate that a transport layer/network address is to change from source DU 1010 to target DU 1010.
  • the CU-C 1030 may send a UE context setup message and/or RB configure message (as indicated by 1220) via Fl-C to target DU 1010.
  • the messages) indicated by 1220 may be used to set up UE context and radio bearers.
  • the CU-C 1030 may send a DL RRC message (as indicated by 1212) via Fl-C to source DU 1010.
  • the message may include information related to RRC connection reconfiguration.
  • the source DU 1010 may send an RRC message (as indicated by 1213) to the UE 102.
  • the DU 1010 may transparently transfer the message 1212 to the UE 102.
  • the UE context setup and RB configure message (indicated by 1220) sent from CU-C 1030 to target DU 1010 may be included in one message (including but not limited to a combined message).
  • the UE context setup and RB configure message (indicated by 1220) sent from CU-C 1030 to target DU 1010 may be separate messages.
  • an example 1300 is shown.
  • the example 1300 may be for inter CU-U handover.
  • the scope of embodiments is not limited in this respect, however, as one or more of the operations shown in FIG. 13 may be performed as part of other
  • one or more of the messages included in the above tables may be exchanged between the UE 102, source DU 1010, target DU 1010, CU-C 1030, source CU-U 1040 and/or target CU-U 1040.
  • the handover may be from source DU 1010 to target DU 1010.
  • the source CU-U 1040 may be used before the handover and the target CU-U 1040 may be used after the handover.
  • the UE context may be set up in the target CU-U 1040.
  • a user plane and control plane of a radio access system may be separated.
  • the system may include at least the CU-C 1030, the CU-U As40 and the DU 1010.
  • the CU-C 1030 may perform one or more of: radio resource control for UE 102; composition of RRC messages to UE 102 for connection control, handover, measurement, UE capability enquiry and/or other; transfer of NAS message between UE 102 and the core network; reception and analysis of RRC messages from UE 102 (such as measurement report, RRC connection request, acknowledgement of commands issued by the controller and/or other); issue of response(s); initiation of handover; performance of air interface control (such as cell configuration, setting up/modifying/deleting radio bearers that transfer data or signaling with UE 102, setting up/releasing UE context and/or other); performance of radio resource management (such as admission control, load balancing, mobility control and/or other);
  • NG2 AP with the core network to support mobility management and session management; performance of CU-U control; intra-CU mobility management; load balancing; support of inter-CU mobility and/or other.
  • the CU-U 1040 may control transfer of data between UE 102 (via DU 1010) and NG-Core.
  • the DU 1010 may transfer control-plane messages and user data towards UE 102.
  • the system may comprise an interface between CU-C 1030 and CU-U 1040 that may transfer signaling to support part of the functions at CU-C 1030 and CU-U 1040.
  • the system may comprise an interface between the CU-C 1030 and DU 1010 that transfers signaling to support part of the functions at CU-C 1030 and DU 1010.
  • the system may comprise an interface between CU-C 1030 and DU 1010 that transfers signaling/data to support part of the functions at CU-C 1030 and DU 1010.
  • the CU-C 1030 may perform function(s) related to one or more of: PDCP of SRB, RRC, RRM, NG2 AP, inter-gNB AP and/or other control functions.
  • the CU-U 1040 may perform function(s) related to one or more of: SDAP, PDCP of DRB (or SRB) and GTP-U end point.
  • the DU 1010 may perform function(s) related to one or more of: RLC, MAC and PHY.
  • an apparatus of a Next Generation Node-B may comprise processing circuitry.
  • the apparatus may further comprise memory.
  • the gNB may be configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU).
  • the gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, a gNB-CU user plane (gNB-CU-UP) for user-plane functionality.
  • the gNB-CU-CP may be configured to communicate with the gNB-CU-UP over an El interface.
  • the processing circuitry may be further configured to initiate a UE context setup procedure to establish UE context by sending a UE context setup request message from the gNB-CU-CP to the gNB-DU over the Fl-C, the UE context including a signaling radio bearer (SRB) configuration and a data radio bearer (DRB) configuration.
  • the processing circuitry may be further configured to transfer an initial radio- resource control (RRC) message as an uplink (UL) PDCP-PDU from the gNB- DU to the gNB-CU-CP over the Fl-C.
  • RRC radio- resource control
  • the UE context setup request message may be configured to include quality -of-service parameters for the DRB configuration.
  • the memory may be configured to store the DRB configuration.
  • Example 2 the subject matter of Example 1, wherein the gNB- DU may be configured to host radio-link control (RLC), medium-access control (MAC) and physical (PHY) layers of the gNB.
  • the gNB-DU may be configured to communicate with user equipment over a user interface (uu).
  • Example 3 the subject matter of one or any combination of Examples 1-2, wherein the bearer context setup procedure may be performed after completion of the El interface setup procedure.
  • Example 4 the subject matter of one or any combination of Examples 1-3, wherein the processing circuitry may be further configured to transfer an RRC message as a downlink (DL) Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) to the gNB-DU from the gNB-CU-CP over the Fl-C.
  • DL downlink
  • PDCP Packet Data Convergence Protocol
  • PDU Protocol Data Unit
  • Example 5 the subject matter of one or any combination of Examples 1-4, wherein the UE context setup request message may further include one or more of: an aggregate maximum bit rate (AMBR), a latency, a bit error rate, and a packet error rate.
  • AMBR aggregate maximum bit rate
  • Example 8 the subject matter of one or any combination of Examples 1-7, wherein the gNB-CU-CP may be configured to send to the gNB- CU-UP, a second UE context setup request message that includes an access stratum (AS) security key for encryption and decryption of the data packets of the DRB.
  • AS access stratum
  • Example 10 the subject matter of one or any combination of Examples 1-9, wherein the processing circuitry may be further configured to send to the gNB-DU for broadcast, minimum system information (SI) that includes a master information block (M1B) and a type 1 SI block (SIB-1).
  • SI minimum system information
  • M1B master information block
  • SIB-1 type 1 SI block
  • Example 11 the subject matter of one or any combination of Examples 1-10, wherein the processing circuitry may be further configured to receive, from the gNB-DU, a request from a UE for on-demand system information (SI) related to a capability of the UE to camp on a cell that includes the disaggregated gNB.
  • the processing circuitry may be further configured to send to the gNB-DU on the Fl interface, a downlink RRC message transfer that includes the on-demand SI.
  • SI system information
  • a computer-readable storage medium may store instructions for execution by processing circuitry of a Next Generation Node-B
  • the gNB may be configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU).
  • the gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, a gNB-CU user plane (gNB-CU-UP) for user-plane functionality.
  • the gNB-CU- CP may be configured to communicate with the gNB-CU-UP over an El interface, the gNB-CU-UP configured to communicate user plane messages with the gNB-DU over an Fl user-plane interface (Fl-U).
  • the gNB-CU-CP may be configured to communicate control plane messages with the gNB-DU over an Fl control plane interface (Fl-C).
  • the operations may configure the processing circuitry to initiate an El interface setup procedure to establish the El interface.
  • Example 14 the subject matter of Example 13, wherein the gNB-DU may be configured to host radio-link control (RLC), medium-access control (MAC) and physical (PHY) layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • RLC radio-link control
  • MAC medium-access control
  • PHY physical layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • UE User Equipment
  • Example 15 the subject matter of one or any combination of Examples 13-14, wherein the bearer context setup procedure may be performed after completion of the El interface setup procedure.
  • Example 16 the subject matter of one or any combination of Examples 13-15, wherein the operations may further configure the processing circuitry to transfer an RRC message as a downlink (DL) PDCP-PDU to the gNB-DU from the gNB-CU-CP over the Fl-C.
  • DL downlink
  • Example 17 the subject matter of one or any combination of Examples 13-16, wherein the UE context setup request message may further include one or more of: an aggregate maximum bit rate (AMBR), a latency, a bit error rate, and a packet error rate.
  • AMBR aggregate maximum bit rate
  • Example 18 the subject matter of one or any combination of Examples 13-17, wherein the operations may further configure the processing circuitry to initiate the El interface setup procedure by: sending a GNB-CU-UP El setup request message from the gNB-CU-UP to the gNB-CU-CP; or sending a GNB-CU-CP El setup request message from the gNB-CU-CP to the gNB-CU- UP.
  • an apparatus of a Next Generation Node-B may comprise processing circuitry.
  • the apparatus may further comprise memory.
  • the gNB may be configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU).
  • the gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, a gNB-CU user plane (gNB-CU-UP) for user-plane functionality.
  • the gNB-CU-CP may be configured to communicate with the gNB-CU-UP over an El interface.
  • the gNB-CU-UP may be configured to communicate user plane messages with the gNB-DU over an Fl user-plane interface (Fl-U).
  • the gNB-CU-CP may be configured to communicate control plane messages with the gNB-DU over an Fl control plane interface (Fl-C).
  • the processing circuitry may be configured to initiate a UE context setup procedure to establish UE context by sending a UE context setup request message from the gNB-CU-CP to the gNB-DU over the Fl-C, the UE context including a signaling radio bearer (SRB) and a data radio bearer (DRB) configuration.
  • the processing circuitry may be further configured to transfer an initial radio-resource control (RRC) message as an uplink (UL) PDCP-PPDU from the gNB-DU to the gNB-CU-CP over the Fl-C.
  • RRC radio-resource control
  • the processing circuitry may be further configured to transfer another RRC message as a downlink (DL) PDCP-PDU to the gNB-DU from the gNB-CU-CP over the Fl-C.
  • the UE context setup request message may be configured to include quality-of-service parameters for the DRB configuration.
  • the memory may be configured to store the DRB configuration.
  • Example 20 the subject matter of Example 19, wherein the gNB-DU may be configured to host radio-link control (RLC), medium-access control (MAC) and physical (PHY) layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • RLC radio-link control
  • MAC medium-access control
  • PHY physical layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • UE User Equipment
  • Example 21 the subject matter of one or any combination of Examples 19-20, wherein the processing circuitry may be further configured to initiate an El interface setup procedure to establish the El interface by sending a GNB-CU-UP El setup request message from the gNB-CU-UP to the gNB-CU- CP or by sending a GNB-CU-CP El setup request message from the gNB-CU- CP to the gNB-CU-UP.
  • the processing circuitry may be further configured to initiate an error indication procedure to indicate the cause of error for a UE.
  • the processing circuitry may be further configured to initiate a bearer context setup procedure to establish a bearer context in the gNB-CU-UP by sending a bearer context setup request message from the gNB-CU-CP to the gNB-CU-UP over the El interface.
  • the bearer context setup procedure may be performed after completion of the El interface setup procedure.
  • Example 22 the subject matter of one or any combination of Examples 19-21, wherein the gNB-CU-CP may be configured to send, to the gNB-CU-UP, another UE context setup request message that includes an access stratum (AS) security key for encryption and decryption of the data packets of the DRB.
  • AS access stratum
  • Example 23 the subject matter of one or any combination of Examples 19-22, wherein the UE context setup request message may further include one or more of: an aggregate maximum bit rate (AMBR), a latency, a bit error rate, and a packet error rate.
  • AMBR aggregate maximum bit rate
  • a Next Generation Node-B may be configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU).
  • the gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, a gNB-CU user plane (gNB-CU-UP) for user-plane functionality.
  • the gNB-CU-CP may be configured to communicate with the gNB-CU-UP over an El interface.
  • the gNB-CU-UP may be configured to communicate user plane messages with the gNB-DU over an Fl user-plane interface (Fl-U).
  • the gNB-CU-CP may be configured to communicate control plane messages with the gNB-DU over an Fl control plane interface (Fl-C).
  • An apparatus of the gNB may comprise means for initiating an El interface setup procedure to establish the El interface.
  • the apparatus may further comprise means for initiating an error indication procedure to indicate a cause of error for a UE.
  • the apparatus may further comprise means for initiating a bearer context setup procedure to establish a bearer context in the gNB-CU-UP by sending a bearer context setup request message from the gNB-CU-CP to the gNB-CU-UP over the El interface.
  • the apparatus may further comprise means for initiating a UE context setup procedure to establish UE context by sending a UE context setup request message from the gNB-CU-CP to the gNB-DU over the Fl-C, the UE context including a signaling radio bearer (SRB) and a data radio bearer (DRB) configuration.
  • the apparatus may further comprise means for transferring an initial radio-resource control (RRC) message as an uplink (UL) PDCP-PPDU from the gNB-DU to the gNB-CU-CP over the Fl-C.
  • RRC radio-resource control
  • the UE context setup request message may be configured to include quality -of-service parameters for the DRB configuration.
  • Example 25 the subject matter of Example 24, wherein the gNB-DU may be configured to host radio-link control (RLC), medium-access control (MAC) and physical (PHY) layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • RLC radio-link control
  • MAC medium-access control
  • PHY physical layers of the gNB.
  • the gNB-DU may be configured to communicate with User Equipment (UE) over a user interface (uu).
  • UE User Equipment
  • Example 26 the subject matter of one or any combination of Examples 24-25, wherein the bearer context setup procedure may be performed after completion of the El interface setup procedure.
  • Example 27 the subject matter of one or any combination of Examples 24-26, wherein the apparatus may further comprise means for transferring an RRC message as a downlink (DL) PDCP-PDU to the gNB-DU from the gNB-CU-CP over the Fl-C.
  • DL downlink
  • Example 28 the subject matter of one or any combination of Examples 24-27, wherein the UE context setup request message may further include one or more of: an aggregate maximum bit rate (AMBR), a latency, a bit error rate, and a packet error rate.
  • AMBR aggregate maximum bit rate
  • Example 29 the subject matter of one or any combination of Examples 24-28, wherein the apparatus may further comprise means for initiating the El interface setup procedure by: sending a GNB-CU-UP El setup request message from the gNB-CU-UP to the gNB-CU-CP; or sending a GNB- CU-CP El setup request message from the gNB-CU-CP to the gNB-CU-UP.

Landscapes

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

Abstract

Des modes de réalisation de l'invention concernent un nœud B de nouvelle génération (gNB). Le gNB peut être configuré avec des nœuds logiques, comprenant une unité centrale gNB (gNB-CU) et une unité distribuée gNB (gNB-DU). Le gNB-CU peut comprendre un plan de commande gNB-CU (gNB-CU-CP) pour une fonctionnalité de plan de commande, et un plan utilisateur gNB-CU (gNB-CU-UP) pour une fonctionnalité de plan utilisateur. Le gNB peut initier une procédure d'établissement d'interface E1, une procédure d'établissement de contexte de support, et une procédure d'établissement de contexte d'UE, pour établir un contexte d'UE comprenant une configuration de support radio de signalisation (SRB) et de support radio de données (DRB). Le message de demande d'établissement de contexte d'UE peut être configuré pour inclure des paramètres de qualité de service pour la configuration DRB.
PCT/US2018/038284 2017-06-19 2018-06-19 Séparation de plan de commande et de plan utilisateur dans des systèmes new radio (nr) Ceased WO2018236867A2 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP18820450.7A EP3643107B1 (fr) 2017-06-19 2018-06-19 Séparation de plan de commande et de plan utilisateur dans des systèmes new radio (nr)
US16/615,081 US11197332B2 (en) 2017-06-19 2018-06-19 Separation of control plane and user plane in new radio (NR) systems
EP24158242.8A EP4346332A3 (fr) 2017-06-19 2018-06-19 Séparation de plan de commande et de plan utilisateur dans des systèmes de nouvelle radio (nr)
US17/517,182 US11632813B2 (en) 2017-06-19 2021-11-02 Separation of control plane and user plane in new radio (NR) systems
US18/119,463 US12096498B2 (en) 2017-06-19 2023-03-09 Separation of control plane and user plane in new radio (NR) systems

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762521958P 2017-06-19 2017-06-19
US62/521,958 2017-06-19

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/615,081 A-371-Of-International US11197332B2 (en) 2017-06-19 2018-06-19 Separation of control plane and user plane in new radio (NR) systems
US17/517,182 Continuation US11632813B2 (en) 2017-06-19 2021-11-02 Separation of control plane and user plane in new radio (NR) systems

Publications (2)

Publication Number Publication Date
WO2018236867A2 true WO2018236867A2 (fr) 2018-12-27
WO2018236867A3 WO2018236867A3 (fr) 2019-02-07

Family

ID=64737822

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/038284 Ceased WO2018236867A2 (fr) 2017-06-19 2018-06-19 Séparation de plan de commande et de plan utilisateur dans des systèmes new radio (nr)

Country Status (3)

Country Link
US (3) US11197332B2 (fr)
EP (2) EP4346332A3 (fr)
WO (1) WO2018236867A2 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020134913A1 (fr) * 2018-12-29 2020-07-02 华为技术有限公司 Procédé et dispositif pour la configuration d'un support radio de données
WO2020156020A1 (fr) * 2019-02-02 2020-08-06 华为技术有限公司 Procédé et appareil de communication
WO2020156182A1 (fr) * 2019-02-01 2020-08-06 华为技术有限公司 Procédé et appareil de mise à jour d'informations de cellule de desserte
CN112703751A (zh) * 2019-08-14 2021-04-23 诺基亚通信公司 系统信息传递增强
AU2018370642B2 (en) * 2017-11-27 2021-05-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information transmission method and apparatus, and network device
WO2021147107A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé et appareil de communication
WO2021150053A1 (fr) * 2020-01-22 2021-07-29 Samsung Electronics Co., Ltd. Procédé et dispositif pour transmettre des données dans un système de communication sans fil
WO2021158024A1 (fr) * 2020-02-05 2021-08-12 Lg Electronics Inc. Procédé et appareil de commutation de service de multidiffusion et de diffusion entre une multidiffusion et une diffusion individuelle dans un système de communication sans fil
WO2021238383A1 (fr) * 2020-05-27 2021-12-02 华为技术有限公司 Procédé et appareil de communication
EP3799322A4 (fr) * 2018-05-23 2022-03-16 Ntt Docomo, Inc. Station de base
WO2023003438A1 (fr) 2021-07-22 2023-01-26 Samsung Electronics Co., Ltd. Procédé et appareil pour fournir des informations de configuration relatives à une radiomessagerie dans un système de communication sans fil
RU2806798C1 (ru) * 2020-01-23 2023-11-07 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство связи

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924958B (zh) * 2017-03-24 2023-05-16 华为技术有限公司 建立连接的方法和装置
CN110856223B (zh) * 2017-05-05 2020-10-27 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备
KR102386844B1 (ko) * 2017-05-12 2022-04-14 삼성전자 주식회사 클라우드 랜 환경에서 네트워크 엔티티들 간의 통신 방법 및 장치
US11197332B2 (en) 2017-06-19 2021-12-07 Apple Inc. Separation of control plane and user plane in new radio (NR) systems
KR102327904B1 (ko) * 2017-08-09 2021-11-19 지티이 코포레이션 사용자 평면을 분리하기 위한 서비스 품질 구현들
EP3668267B1 (fr) * 2017-08-10 2023-09-20 NTT DoCoMo, Inc. Station de base de radio et procédé de commande de communication
CN109391963B (zh) * 2017-08-11 2022-03-11 华为技术有限公司 一种传输方法和网络设备
US11457383B2 (en) * 2017-09-07 2022-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Control node, process node and methods performed therein for a control process on radio access bearers
KR102645345B1 (ko) * 2017-09-28 2024-03-08 삼성전자주식회사 네트워크 액세스를 위한 방법 및 장치
KR102265526B1 (ko) * 2017-10-12 2021-06-16 에스케이텔레콤 주식회사 기지국장치 및 데이터 및 신호 전송 방법
RU2745330C1 (ru) * 2017-11-16 2021-03-24 Телефонактиеболагет Лм Эрикссон (Пабл) ОБМЕН TEID МЕЖДУ DU И CP-UP В gNB
EP3711365B1 (fr) * 2017-11-17 2022-02-09 Telefonaktiebolaget LM Ericsson (publ) Échange d'informations pour un accès initial d'un équipement utilisateur
WO2019159700A1 (fr) * 2018-02-13 2019-08-22 日本電気株式会社 Première unité, seconde unité, dispositif de communication, dispositif terminal, procédé, programme, et support d'enregistrement
US11212695B2 (en) * 2018-02-15 2021-12-28 Qualcomm Incorporated Configuration, activation and deactivation of packet duplication
US12213005B2 (en) * 2018-03-08 2025-01-28 Nokia Technologies Oy Radio access network controller methods and systems to optimize inter frequency load balancing
HUE063433T2 (hu) * 2018-04-04 2024-01-28 Zte Corp Eljárás és rendszerek üzenetek cseréjére vezeték nélküli hálózatban
EP4436247B1 (fr) * 2018-04-06 2025-11-26 Telefonaktiebolaget LM Ericsson (publ) Gestion de flux qos sur e1
US11622397B2 (en) * 2018-08-10 2023-04-04 Apple Inc. Enhancing user plane contexts management in new radio (NR)
CN118945852A (zh) * 2018-11-02 2024-11-12 北京三星通信技术研究有限公司 在中继网络中传输控制信令的方法及其配置方法和设备
US12284695B2 (en) * 2019-02-15 2025-04-22 Teleonaktiebolaget LM Ericsson (publ) Functional part selection in a disaggregated base station
CN111586887B (zh) * 2019-02-15 2023-03-28 华为技术有限公司 无线回传系统、通信方法及其装置
DE112020002491T5 (de) * 2019-05-23 2022-04-28 Hewlett Packard Enterprise Development Lp System und verfahren zur erleichterung der dynamischen befehlsverwaltung in einer netzwerkschnittstellensteuerung (nic)
WO2022027425A1 (fr) * 2020-08-06 2022-02-10 Zte Corporation Signalisation pour services de diffusion en multidiffusion
CN114286450B (zh) * 2020-09-27 2023-09-19 中国移动通信集团设计院有限公司 承载建立方法、装置、电子设备及存储介质
CN114760623A (zh) * 2021-01-10 2022-07-15 华为技术有限公司 安全策略处理方法以及通信设备
US11917521B2 (en) * 2021-01-20 2024-02-27 Mavenir Systems, Inc. Method and apparatus for unique identification of individual users in the radio access network (RAN) intelligent controller
KR20230011185A (ko) * 2021-07-13 2023-01-20 삼성전자주식회사 무선 통신 시스템에서 식별자를 전달하기 위한 장치 및 방법
US20230328720A1 (en) * 2022-04-08 2023-10-12 EdgeQ, Inc. Downlink and uplink disaggregation in a radio access network
KR20250029559A (ko) * 2023-08-23 2025-03-05 삼성전자주식회사 이동통신 시스템에서 이동성 및 페이징을 위한 방법 및 장치
US20250081046A1 (en) * 2023-08-31 2025-03-06 Qualcomm Incorporated Cellular connection over non-cellular access via gateway

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8982841B2 (en) * 2011-10-27 2015-03-17 Spidercloud Wireless, Inc. Long term evolution architecture and mobility
CN106465448A (zh) * 2015-03-27 2017-02-22 华为技术有限公司 数据传输方法、接入网设备和通信系统
WO2017118935A1 (fr) * 2016-01-08 2017-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Connectivité sans fil simplifiée pour un système de communication cellulaire
EP3902368B1 (fr) * 2016-09-30 2023-05-03 Samsung Electronics Co., Ltd. Procédé et appareil d'établissement de double connectivité pour transmettre des données dans une nouvelle architecture de communication radio
US10469358B2 (en) * 2017-05-18 2019-11-05 Qualcomm Incorporated Wireless multihop relay
US11197332B2 (en) 2017-06-19 2021-12-07 Apple Inc. Separation of control plane and user plane in new radio (NR) systems
US10708968B2 (en) * 2017-08-25 2020-07-07 Kt Corporation Method of controlling mobility of UE and apparatus therefor
EP3706349B1 (fr) * 2017-11-17 2024-10-23 Beijing Xiaomi Mobile Software Co., Ltd. Indication de rétroaction et procédé de rétroaction de demande de répétition automatique hybride, dispositif et station de base
WO2019160549A1 (fr) * 2018-02-15 2019-08-22 Nokia Technologies Oy Sélection coordonnée de composants de plan utilisateur ran et central dans un réseau de communication sans fil
EP3534651A1 (fr) * 2018-02-15 2019-09-04 Comcast Cable Communications, LLC Communications sans fil utilisant des informations d'un dispositif sans fil
US11006312B2 (en) * 2018-04-06 2021-05-11 Apple Inc. PDCP packet-based DDDS frame transmission
US11412554B2 (en) * 2018-05-10 2022-08-09 Apple Inc. E1 interface setup in NG-RAN
US11190989B2 (en) * 2018-05-22 2021-11-30 Apple Inc. Mobility management for inter-gNB (next generation node-b) handover in new radio (NR) systems
EP3808056A1 (fr) * 2018-06-13 2021-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Attribution d'adresse de protocole internet (ip) dans des réseaux à raccordement d'accès intégré (iab)
US20200245135A1 (en) * 2019-01-28 2020-07-30 Qualcomm Incorporated Support for early data transmission with central unit/distributed unit functional split
US11595927B2 (en) * 2019-09-13 2023-02-28 Qualcomm Incorporated Over-the-air synchronization in mobile integrated access and backhaul communications
US11552734B2 (en) * 2019-09-13 2023-01-10 Qualcomm Incorporated Techniques for bi-direction preemption indication transmissions

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "3GPP DRAFT; R3-171724, 3RD GENERATION PARTNERSHIP PROJECT (3GPP", 3 April 2017, MOBILE COMPETENCE CENTRE, article "F1 interface functions"
ERICSSON: "3GPP DRAFT; RP-171215, 3RD GENERATION PARTNERSHIP PROJECT (3GPP", 5 June 2017, MOBILE COMPETENCE CENTRE, article "Separation of CP and UP"
See also references of EP3643107A4

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2018370642B2 (en) * 2017-11-27 2021-05-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information transmission method and apparatus, and network device
US11736956B2 (en) 2018-05-23 2023-08-22 Ntt Docomo, Inc. Base station
EP3799322A4 (fr) * 2018-05-23 2022-03-16 Ntt Docomo, Inc. Station de base
CN111385910A (zh) * 2018-12-29 2020-07-07 华为技术有限公司 一种数据无线承载的配置方法、设备及系统
WO2020134913A1 (fr) * 2018-12-29 2020-07-02 华为技术有限公司 Procédé et dispositif pour la configuration d'un support radio de données
CN111385910B (zh) * 2018-12-29 2022-06-07 华为技术有限公司 一种数据无线承载的配置方法、设备及系统
WO2020156182A1 (fr) * 2019-02-01 2020-08-06 华为技术有限公司 Procédé et appareil de mise à jour d'informations de cellule de desserte
EP3911019A4 (fr) * 2019-02-02 2022-03-16 Huawei Technologies Co., Ltd. Procédé et appareil de communication
WO2020156020A1 (fr) * 2019-02-02 2020-08-06 华为技术有限公司 Procédé et appareil de communication
CN112703751A (zh) * 2019-08-14 2021-04-23 诺基亚通信公司 系统信息传递增强
WO2021150053A1 (fr) * 2020-01-22 2021-07-29 Samsung Electronics Co., Ltd. Procédé et dispositif pour transmettre des données dans un système de communication sans fil
WO2021147107A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé et appareil de communication
RU2806798C1 (ru) * 2020-01-23 2023-11-07 Хуавей Текнолоджиз Ко., Лтд. Способ и устройство связи
US12369080B2 (en) 2020-01-23 2025-07-22 Huawei Technologies Co., Ltd. Communication method and apparatus
WO2021158024A1 (fr) * 2020-02-05 2021-08-12 Lg Electronics Inc. Procédé et appareil de commutation de service de multidiffusion et de diffusion entre une multidiffusion et une diffusion individuelle dans un système de communication sans fil
US12369224B2 (en) 2020-02-05 2025-07-22 Lg Electronics Inc. Method and apparatus for switching of multicast and broadcast service between multicast and unicast in a wireless communication system
WO2021238383A1 (fr) * 2020-05-27 2021-12-02 华为技术有限公司 Procédé et appareil de communication
WO2023003438A1 (fr) 2021-07-22 2023-01-26 Samsung Electronics Co., Ltd. Procédé et appareil pour fournir des informations de configuration relatives à une radiomessagerie dans un système de communication sans fil
EP4374630A4 (fr) * 2021-07-22 2024-11-20 Samsung Electronics Co., Ltd. Procédé et appareil pour fournir des informations de configuration relatives à une radiomessagerie dans un système de communication sans fil

Also Published As

Publication number Publication date
US12096498B2 (en) 2024-09-17
EP4346332A2 (fr) 2024-04-03
US20230232471A1 (en) 2023-07-20
US20200178326A1 (en) 2020-06-04
EP3643107A4 (fr) 2021-03-10
EP4346332A3 (fr) 2024-06-12
US20220061110A1 (en) 2022-02-24
EP3643107C0 (fr) 2024-03-06
WO2018236867A3 (fr) 2019-02-07
EP3643107A2 (fr) 2020-04-29
EP3643107B1 (fr) 2024-03-06
US11197332B2 (en) 2021-12-07
US11632813B2 (en) 2023-04-18

Similar Documents

Publication Publication Date Title
US12096498B2 (en) Separation of control plane and user plane in new radio (NR) systems
US11838979B2 (en) Apparatus of GNB to enable an inactive mode in dual connectivity
US11438811B2 (en) Next Generation Node-B (gNB) and methods for mobility management with separate user plane and control plane in new radio (NR) systems
US11019683B2 (en) Methods to indicate a version of packet data convergence protocol (PDCP) in dual connectivity arrangements
US11895620B2 (en) Next generation Node-B (GNB) and methods to indicate a type of access for paging of a user equipment (UE)
US11490454B2 (en) User equipment (UE), evolved node-B (ENB) and methods of paging in accordance with a relay arrangement
US12047826B2 (en) Evolved node-b (eNB), user equipment (UE) and methods of switching between direct and indirect communication for a relay arrangement
US20190350047A1 (en) User equipment (ue), evolved node-b (enb) and methods to indicate parameters for a relay arrangement
EP3593565A1 (fr) Noeud b évolué (enb), équipement utilisateur (ue) et procédés de commutation entre une communication directe et indirecte pour un agencement de relais
WO2018144758A1 (fr) Nœud b de génération (gnb), équipement utilisateur (ue) et procédés de transfert intercellulaire basés sur la connectivité multiple dans des systèmes de nouvelle radio (nr)
US10721781B2 (en) Evolved node-B (ENB) for management of long term evolution (LTE) wireless local area network (WLAN) aggregation (LWA) and LTE WLAN internet protocol (LWIP)
HK40112132A (en) Separation of control plane and user plane in new radio (nr) systems
HK40027047B (en) Separation of control plane and user plane in new radio (nr) systems
HK40027047A (en) Separation of control plane and user plane in new radio (nr) systems

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: 18820450

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018820450

Country of ref document: EP

Effective date: 20200120