EP3834484A1 - Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération - Google Patents

Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération

Info

Publication number
EP3834484A1
EP3834484A1 EP19848227.5A EP19848227A EP3834484A1 EP 3834484 A1 EP3834484 A1 EP 3834484A1 EP 19848227 A EP19848227 A EP 19848227A EP 3834484 A1 EP3834484 A1 EP 3834484A1
Authority
EP
European Patent Office
Prior art keywords
gnb
forwarding
data
list
qos flows
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.)
Pending
Application number
EP19848227.5A
Other languages
German (de)
English (en)
Other versions
EP3834484A4 (fr
Inventor
Jaemin HAN
Feng Yang
Alexander Sirotkin
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
Publication of EP3834484A1 publication Critical patent/EP3834484A1/fr
Publication of EP3834484A4 publication Critical patent/EP3834484A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • 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

Definitions

  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide
  • the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Nodes can include a 5G Node, new radio (NR) node or g Node B (gNB).
  • NR new radio
  • gNB g Node B
  • FIG. 1 illustrates an example handover procedure in accordance with one embodiment.
  • FIG. 2 illustrates an example data forwarding procedure in accordance with one embodiment.
  • FIG. 3 illustrates a method in accordance with one embodiment.
  • FIG. 4 illustrates a method in accordance with one embodiment.
  • FIG. 5 illustrates a system in accordance with one embodiment.
  • FIG. 6 illustrates a system in accordance with one embodiment.
  • FIG. 7 illustrates a device in accordance with one embodiment.
  • FIG. 8 illustrates an example interfaces in accordance with one embodiment.
  • FIG. 9 illustrates components in accordance with one embodiment. DETAILED DESCRIPTION
  • the source proposes data forwarding, and if accepted by the target, it provides forwarding transport network layer (TNL) information (e.g., internet protocol (IP) address and general packet radio service (GPRS) tunneling protocol (GTP)-tunnel endpoint identifier (TEID)) for which the source can forward packets to.
  • TNL forwarding transport network layer
  • IP internet protocol
  • GPRS general packet radio service
  • GTP tunneling protocol-tunnel endpoint identifier
  • TEID tunneling protocol
  • gNB-CU-CP gNB-CU control plane
  • gNB-CU-UP gNB-CU user plane
  • the reason for this request/response approach may be because of the CP-UP separation design choice (to make the user-plane entity as simple as possible) and may be because of the data radio bearer (DRB)-level forwarding for lossless HO.
  • DRB data radio bearer
  • gNB-CU-CP decides quality of service (QoS) flow to DRB mappings and gNB-CU-UP simply accepts or rejects whatever is requested.
  • QoS quality of service
  • the gNB-CU-CP may decide whether to accept per QoS flow DL forwarding proposals and may propagate the accepted flows to the gNB-CU- UP so that the gNB-CU-UP is able to know which QoS flow DL forwarding over the PDU session tunnel will happen or not.
  • the gNB-CU-CP may keep the control, thus allowing the gNB-CU-UP to be simple.
  • a QoS flow may have no option to be rejected if no more resources are left to handle such forwarding in gNB-CU-UP.
  • the gNB-CU-CP may propagate per QoS flow DL forwarding and gNB-CU-UP may decide to accept or not when admitting.
  • the gNB-CU-UP may make decisions by considering the forwarding proposal as well during its admission process.
  • more minute control can be possible for gNB-CU-UP, i.e., to admit a QoS flow while rejecting the forwarding request based on its resource status.
  • Certain such embodiments may require more functionality in the gNB-CU-UP than may have been originally intended.
  • Other embodiments may include a hybrid of the above embodiments wherein both the gNB-CU-CP and the gNB-CU-UP can be involved in decision making for an optimal forwarding acceptance decision.
  • the gNB-CU-CP may first discriminate (make some pre-decision to accept or reject the forwarding proposal), then propagate the forwarding request only for the accepted ones so that the gNB-CU-UP can make further decisions.
  • Certain embodiments of the present disclosure provide several mechanisms that the gNB-CU-UP may be able to know which QoS flow is subject to data forwarding, so that PDU session forwarding can work properly and an unnecessary delay can be avoided during HO involving a gNB-CU-UP change in NG-RAN.
  • FIG. 1 illustrates a simplified example handover procedure 100 from a source gNB 102 to a target gNB 104 in an NG-RAN according to one embodiment.
  • the example handover procedure 100 may be used for inter-gNB handover involving a gNB-CU-UP change.
  • the source gNB 102 includes a Source gNB-DU 106, a Source gNB-CU-UP 108, and a Source gNB-CU-CP 110.
  • the target gNB 104 includes a Target gNB-DU 112, a Target gNB-CU-UP 114, and a Target gNB-CU-CP 116.
  • the example handover procedure 100 is assisted by an access and mobility management function (AMF) and/or a user plane function (UPF) (shown as an AMF/UPF 118).
  • AMF access and mobility management function
  • UPF user plane function
  • the Source gNB-CU-CP 110 sends a handover request 120 to the Target gNB-CU- CP 116, which initiates a Bearer Context Setup Procedure 122.
  • the Bearer Context Setup Procedure 122 may include, for example, a bearer context setup request from the Target gNB-CU-CP 116 to the Target gNB-CU-UP 114, and a bearer context setup response from the Target gNB-CU-UP 114 to the Target gNB-CU-CP 116.
  • the Bearer Context Setup Procedure 122 may also include an Fl interface UE context setup procedure between the Target gNB-DU 112 and the Target gNB-CU-CP 116.
  • the Target gNB-CU-CP 116 responds to the Source gNB-CU-CP 110 with a handover request acknowledge 124 message.
  • the example handover procedure 100 may also include a Context Modification 126 procedure by the source gNB 102, which may include an Fl UE modification procedure to stop uplink (UL) data transmission at the Source gNB-DU 106 and the send the handover command to the UE.
  • the Context Modification 126 procedure may also include a bearer context modification procedure (initiated by the Source gNB-CU-CP 110) to enable the Source gNB-CU-CP 110 to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer.
  • the Source gNB-CU-CP 110 then sends an SN status transfer 128 message to the Target gNB-CU-CP 1 16.
  • the Target gNB-DU 112 may perform a procedure such that the UE is attached via RACH 130.
  • the Target gNB-CU-UP 114 and the Target gNB-CU-CP 116 may perform a Bearer Context Modification Procedure 132, which may include a bearer context modification request from the Target gNB-CU-CP 116 and a bearer context modification response from the Target gNB-CU-UP 114.
  • data forwarding 134 may be performed from the Source gNB-CU-UP 108 to the Target gNB-CU-UP 114 until an end marker packet 136 is received and a new path 138 is provided by a path switch procedure to update the DL TNL address information for the NG-U interface towards the core network.
  • the Target gNB-CU-CP 116 provides a list of accepted QoS flows to the Target gNB-CU-UP 114. Based on the list of accepted QoS flows, Target gNB-CU-UP 114 is configured to handle new packets from the UE (not part of the accepted QoS flows) before receiving the end marker packet 136.
  • the data forwarding 134 from the Source gNB-CU-UP 108 to the Target gNB-CU-UP 114 does not delay the processing of new packets that are associated with QoS flows that have not been proposed for forwarding or proposed but not accepted for forwarding.
  • the example handover procedure 100 may also include the Target gNB-CU-CP 116 sending a UE context release 140 message to the Source gNB-CU-CP 110 to initiate Bearer and UE Context Release 142 procedures.
  • the Source gNB-CU-CP 110 may send a bearer context release command to the Source gNB-CU-UP 108, and the Source gNB-DU 106 may interact with the Source gNB-CU-CP 110 to perform an Fl UE context release procedure to release the UE context in the Source gNB-DU 106.
  • the Source gNB- CU-UP 108 may send a bearer context release complete message to the Source gNB-CU-CP 110 to end the example handover procedure 100.
  • the Target gNB-CU-CP 116 may decide whether to accept a QoS flow DL forwarding proposal and may propagate the accepted flows to the Target gNB-CU-UP 114.
  • the Target gNB-CU-CP 116 may keep all the control of whether to accept or reject the QoS flow DL forwarding proposal from the source gNB 102.
  • the Target gNB-CU-CP 116 may propagate only those forwarding proposals that it has accepted to the Target gNB-CU-UP 114 so that the Target gNB-CU-UP 114 is able to know which QoS flow is subject to DL forwarding.
  • the Target gNB-CU-UP 114 may not have a functionality to reject the forwarding request when admitting the QoS flow, meaning that its forwarding may happen as long as it is admitted
  • FIG. 2 illustrates an example data forwarding procedure 200 wherein the Target gNB-CU-CP 116 sends a list of accepted QoS flows 202 to the Target gNB-CU- UP 1 14.
  • the list of accepted QoS flows 202 may be communicated, for example, via the El control interface between the Target gNB-CU-UP 1 14 and the Target gNB-CU-CP 116.
  • the list of accepted QoS flows 202 may be signaled as an extension of the Data Forwarding Information Request information element (IE), as shown in Table 1.
  • IE Data Forwarding Information Request information element
  • the Data Forwarding Information Request IE may be configured as shown in Table 2.
  • the Data Forwarding Information Request IE offers the possibility for the Target gNB-CET-CP 116 to request data forwarding addresses to the Target gNB-CET-UP 114.
  • the Data Forwarding Information Request IE also offers the possibility for the Target gNB-CET-CP 1 16 to provide the list of accepted QoS flows 202 subject to PDET session level or DRB level data forwarding to the Target gNB-CET-ETP 114 for which DRBs or QoS flows have been offloaded.
  • the QoS flow mapping list in Table 2 may comprise an IE including a list of DRBs with information about the mapped QoS flows, such as a QoS flow identifier, a QoS flow mapping indication, and a maximum number of QoS flows allowed within one PDET session.
  • Sending the list of accepted QoS flows 202 from the Target gNB-CU-CP 116 to the Target gNB-CU-UP 114 allows control aspects (whether to accept or reject forwarding) to be kept in the Target gNB-CU-CP 116, making implementation of the Target gNB-CU-UP 114 more straightforward. As data forwarding handling requires resources, rejecting a QoS flow may be the only option for the Target gNB-CU-UP 114 according to certain
  • the list of accepted QoS flows 202 that are subject to data forwarding may be sent when the Target gNB-CU-CP 116 requests to establish a PDU session over the El interface.
  • the Target gNB-CU-CP 116 may propagate QoS flow DL forwarding and the Target gNB-CU-UP 114 may decide to accept or not when admitting.
  • this embodiment may give control to the Target gNB-CU-UP 114 so that the Target gNB-CU-UP 114 can consider forwarding as well for its admission decision.
  • more minute admission control can be possible for the Target gNB-CU-UP 114, i.e., to admit a QoS flow while rejecting the forwarding request based on its resources status.
  • the forwarding may happen only when the Target gNB-CU-UP 114 accepts the forwarding proposal by the source gNB 102.
  • extensions of the Data Forwarding Information Request IE shown in Table 3
  • the Data Forwarding Information Response IE shown in Table 4
  • the forwarding proposal may be considered together during the admission process, so more minute admission control can be possible in the Target gNB-CU-UP 114 based on resource status.
  • Target gNB-CU-CP 116 there is no discrimination of the forwarding proposal by the Target gNB-CU-CP 116 and more functionality is given to the Target gNB-CEi-UP 114 than may have been identified in its original design purpose.
  • This embodiment may impact the list of QoS flows subject to data forwarding when the Target gNB-CEi-CP 116 requests to establish a PDEI session over the El interface, and the list of QoS flows whose forwarding has been accepted in the response from Target gNB-CU-UP 114 over the El interface.
  • the Target gNB-CU-CP 116 or the Target gNB-CU-UP 114 knows better than the other.
  • a hybrid approach may be used. That is, the Target gNB-CU-CP 116 may first discriminate (makes some pre-decision whether to accept QoS flow DL forwarding proposal by the source gNB 102 or not). The Target gNB-CU-CP 116 may then propagate the forwarding proposal only for the accepted ones to the Target gNB-CU-UP 114. Then the Target gNB- CU-UP 114 makes further decisions on whether to accept or not for those forwarding proposals requested by the Target gNB-CU-CP 116.
  • the discrimination by both the Target gNB-CU-CP 116 and the Target gNB-CU-UP 114 may enable an improved or optimal forwarding acceptance decision from the target gNB 104. Again, however, such an embodiment may provide more functionality to the Target gNB-CU-UP 1 14 than its original design purpose.
  • FIG. 3 illustrates a method 300 for data forwarding during handover from a source gNB to a target gNB of a wireless communication system.
  • the method 300 processes, at a gNB-CU-CP of the target gNB, a proposal to forward one or more DL QoS flows from the source gNB to the target gNB.
  • the method 300 determines, at the gNB-CU-CP, which of the QoS flows to accept or reject for forwarding.
  • the method 300 generates, at the gNB-CU-CP, an indication for a gNB-CU-UP of accepted QoS flows for forwarding.
  • generating the indication comprises generating a data forwarding information request comprising a list of the accepted QoS flows subject to forwarding on one or more forwarding tunnels the data forwarding information request may be used for a PDU session, wherein the one or more forwarding tunnels includes a PDU session forwarding tunnel. Further, or in other embodiments, the data forwarding
  • the list comprises a QoS flow mapping list including a list of DRBs comprising information about mapped QoS flows.
  • FIG. 4 illustrates a method 400 for a gNB-CU-UP.
  • the method 400 processes a list of accepted QoS flows subject to forwarding on one or more forwarding tunnels.
  • the accepted QoS flows correspond to a UE undergoing inter-gNB handover.
  • the method 400 receives new packets from the UE.
  • the method 400 based on the list of accepted QoS flows, handles the new packets before receiving an end marker forwarded.
  • the new packets correspond to one or more QoS flows that are different than the accepted QoS flows.
  • the one or more forwarding tunnels includes a PDU session forwarding tunnel. In another embodiment, the one or more forwarding tunnels includes a DRB forwarding tunnel. In addition, or in other embodiments, the list comprises a QoS flow mapping list including a list of DRBs comprising information about mapped QoS flows.
  • FIG. 5 illustrates an architecture of a system 500 of a network in accordance with some embodiments.
  • the system 500 includes one or more user equipment (UE), shown in this example as a UE 502 and a UE 504.
  • UE user equipment
  • the UE 502 and the UE 504 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UE 502 and the UE 504 can comprise an Internet of Things (IoT) EGE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived EGE connections.
  • An IoT EGE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity- Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT ETEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the EGE 502 and the EGE 504 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN), shown as RAN 506.
  • the RAN 506 may be, for example, an Evolved ETniversal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved ETniversal Mobile Telecommunications System
  • E-UTRAN Evolved ETniversal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UE 502 and the UE 504 utilize connection 508 and connection 510,
  • connection 508 and the connection 510 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UE 502 and the UE 504 may further directly exchange communication data via a ProSe interface 512.
  • the ProSe interface 512 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 504 is shown to be configured to access an access point (AP), shown as AP 514, via connection 516.
  • AP access point
  • the connection 516 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 514 would comprise a wireless fidelity (WiFi®) router.
  • the AP 514 may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 506 can include one or more access nodes that enable the connection 508 and the connection 510.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 506 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 518, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., a low power (LP) RAN node such as LP RAN node 520.
  • LP low power
  • any of the macro RAN node 518 and the LP RAN node 520 can terminate the air interface protocol and can be the first point of contact for the EGE 502 and the EGE 504.
  • any of the macro RAN node 518 and the LP RAN node 520 can fulfill various logical functions for the RAN 506 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the EGE 502 and the EGE 504 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the macro RAN node 518 and the LP RAN node 520 over a multicarrier communication channel in accordance various
  • OFDM Orthogonal Frequency-Division Multiplexing
  • OFDMMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal sub carriers.
  • a downlink resource grid can be used for downlink transmissions from any of the macro RAN node 518 and the LP RAN node 520 to the UE 502 and the UE 504, while uplink transmissions can utilize similar techniques.
  • the grid can 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
  • Each column and each row of the resource grid corresponds 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.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
  • the physical downlink shared channel may carry user data and higher- layer signaling to the EGE 502 and the EGE 504.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the EGE 502 and the EGE 504 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the EGE 504 within a cell) may be performed at any of the macro RAN node 518 and the LP RAN node 520 based on channel quality information fed back from any of the EGE 502 and EGE 504.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UE 502 and the UE 504.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub- block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • the RAN 506 is communicatively coupled to a core network (CN), shown as CN 528— via an Sl interface 522.
  • CN core network
  • the CN 528 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the Sl interface 522 is split into two parts: the S 1 -U interface 524, which carries traffic data between the macro RAN node 518 and the LP RAN node 520 and a serving gateway (S-GW), shown as S-GW 532, and an Sl -mobility management entity (MME) interface, shown as Sl-MME interface 526, which is a signaling interface between the macro RAN node 518 and LP RAN node 520 and the MME(s) 530.
  • S-GW serving gateway
  • MME Sl -mobility management entity
  • the CN 528 comprises the MME(s) 530, the S-GW 532, a Packet Data Network (PDN) Gateway (P-GW) (shown as P-GW 534), and a home subscriber server (HSS) (shown as HSS 536).
  • the MME(s) 530 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MME(s) 530 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 536 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the CN 528 may comprise one or several HSS 536, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 536 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 532 may terminate the Sl interface 322 towards the RAN 506, and routes data packets between the RAN 506 and the CN 528.
  • the S-GW 532 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 534 may terminate an SGi interface toward a PDN.
  • the P-GW 534 may route data packets between the CN 528 (e.g., an EPC network) and external networks such as a network including the application server 542 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface (shown as IP communications interface 538).
  • IP Internet Protocol
  • an application server 542 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 534 is shown to be communicatively coupled to an application server 542 via an IP communications interface 538.
  • the application server 542 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group
  • VoIP Voice-over-Internet Protocol
  • the P-GW 534 may further be a node for policy enforcement and charging data collection.
  • a Policy and Charging Enforcement Function (shown as PCRF 540) is the policy and charging control element of the CN 528.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • PCRFs associated with a UE’s IP- CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN).
  • H-PCRF Home PCRF
  • V-PCRF Visited PCRF
  • the PCRF 540 may be communicatively coupled to the application server 542 via the P-GW 534.
  • the application server 542 may signal the PCRF 540 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 540 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 542.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 6 illustrates an architecture of a system 600 of a network in accordance with some embodiments.
  • the system 600 is shown to include a UE 602, which may be the same or similar to the UE 502 and the UE 504 discussed previously; a 5G access node or RAN node (shown as (R)AN node 608), which may be the same or similar to the macro RAN node 518 and/or the LP RAN node 520 discussed previously; a User Plane Function (shown as UPF 604); a Data Network (DN 606), which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC) (shown as CN 610).
  • R 5G access node or RAN node
  • UPF 604 User Plane Function
  • DN 606 Data Network
  • CN 610 5G Core Network
  • the CN 610 may include an Authentication Server Function (AUSF 614); a Core Access and Mobility Management Function (AMF 612); a Session Management Function (SMF 618); a Network Exposure Function (NEF 616); a Policy Control Function (PCF 622); a Network Function (NF) Repository Function (NRF 620); a ETnified Data Management (ETDM 624); and an Application Function (AF 626).
  • AUSF 614 Authentication Server Function
  • AMF 612 Core Access and Mobility Management Function
  • SMF 618 Session Management Function
  • NEF 616 Network Exposure Function
  • PCF 622 Policy Control Function
  • NRF 622 Policy Control Function
  • NRF 622 Network Function
  • NF Network Function
  • ETnified Data Management ETDM 624
  • AF 626 Application Function
  • the CN 610 may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.
  • the UPF 604 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 606, and a branching point to support multi-homed PDU session.
  • the UPF 604 may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering.
  • UPF 604 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN 606 may represent various network operator services, Internet access, or third party services. DN 606 may include, or be similar to the application server 542 discussed previously.
  • the AUSF 614 may store data for authentication of UE 602 and handle
  • the AUSF 614 may facilitate a common authentication framework for various access types.
  • the AMF 612 may be responsible for registration management (e.g., for registering UE 602, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and
  • AMF 612 may provide transport for SM messages for the SMF 618, and act as a transparent proxy for routing SM messages. AMF 612 may also provide transport for short message service (SMS) messages between UE 602 and an SMS function (SMSF) (not shown by FIG. 6). AMF 612 may act as Security Anchor Function (SEA), which may include interaction with the AUSF 614 and the UE 602, receipt of an intermediate key that was established as a result of the UE 602 authentication process. Where USIM based authentication is used, the AMF 612 may retrieve the security material from the AUSF 614. AMF 612 may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific
  • SCM Security Context Management
  • AMF 612 may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (NI) signaling, and perform NAS ciphering and integrity protection.
  • AMF 612 may also support NAS signaling with a UE 602 over an N3
  • the N3IWF may be used to provide access to untrusted entities.
  • N3IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signaling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2.
  • N3IWF may also relay uplink and downlink control-plane NAS (NI) signaling between the UE 602 and AMF 612, and relay uplink and downlink user-plane packets between the UE 602 and UPF 604.
  • NI uplink and downlink control-plane NAS
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 602.
  • the SMF 618 may be responsible for session management (e.g., session management
  • the SMF 618 may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signaling for PDU session
  • the NEF 616 may provide means for securely exposing the services
  • the NEF 616 may authenticate, authorize, and/or throttle the AFs.
  • NEF 616 may also translate information exchanged with the AF 626 and information exchanged with internal network functions. For example, the NEF 616 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 616 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 616 as structured data, or at a data storage NF using a standardized interfaces. The stored information can then be re-exposed by the NEF 616 to other NFs and AFs, and/or used for other purposes such as analytics.
  • NFs network functions
  • the NRF 620 may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 620 also maintains information of available NF instances and their supported services.
  • the PCF 622 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 622 may also implement a front end (FE) to access subscription information relevant for policy decisions in a ETDR of ETDM 624.
  • FE front end
  • the ETDM 624 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of EGE
  • the UDM 624 may include two parts, an application FE and a ETser Data Repository (UDR).
  • the UDM may include a UDM FE, which is in charge of processing of credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription
  • UDR may interact with PCF 622 .
  • UDM 624 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.
  • the AF 626 may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control.
  • the NCE may be a mechanism that allows the 5GC and AF 626 to provide information to each other via NEF 616, which may be used for edge computing
  • the network operator and third party services may be hosted close to the UE 602 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF 604 close to the UE 602 and execute traffic steering from the UPF 604 to DN 606 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF
  • the AF 626 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 626 is considered to be a trusted entity, the network operator may permit AF 626 to interact directly with relevant NFs.
  • the CN 610 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 602 to/from other entities, such as an SMS-GMSC/IWMSC/SMS- router.
  • the SMS may also interact with AMF 612 and UDM 624 for notification procedure that the UE 602 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 624 when UE 602 is available for SMS).
  • the system 600 may include the following service-based interfaces: Namf:
  • Service-based interface exhibited by AMF Service-based interface exhibited by SMF
  • Nsmf Service-based interface exhibited by SMF
  • Nnef Service-based interface exhibited by NEF
  • Npcf Service-based interface exhibited by PCF
  • Nudm Service-based interface exhibited by UDM
  • Naf Service-based interface exhibited by AF
  • Nnrf Service-based interface exhibited by NRF
  • Nausf Service-based interface exhibited by AUSF.
  • the system 600 may include the following reference points: Nl : Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3 : Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network.
  • Nl Reference point between the UE and the AMF
  • N2 Reference point between the (R)AN and the AMF
  • N3 Reference point between the (R)AN and the UPF
  • N4 Reference point between the SMF and the UPF
  • N6 Reference point between the UPF and a Data Network.
  • an NS reference point may be between the PCF and the AF
  • an N7 reference point may be between the PCF and the SMF
  • an Nl 1 reference point between the AMF and SMF etc.
  • the CN 610 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME(s) 530) and the AMF 612 in order to enable interworking between CN 610 and CN 528.
  • MME e.g., MME(s) 530
  • the system 600 may include multiple RAN nodes (such as (R)AN node 608) wherein an Xn interface is defined between two or more (R)AN node 608 (e.g., gNBs and the like) that connecting to 5GC 410, between a (R)AN node 608 (e.g., gNB) connecting to CN 610 and an eNB (e.g., a macro RAN node 518 of FIG. 5), and/or between two eNBs connecting to CN 610.
  • R radio access control
  • the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
  • the Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
  • the Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 602 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the EGE mobility for connected mode between one or more (R)AN node 608.
  • a connected mode e.g., CM-CONNECTED
  • the mobility support may include context transfer from an old (source) serving (R)AN node 608 to new (target) serving (R)AN node 608; and control of user plane tunnels between old (source) serving (R)AN node 608 to new (target) serving (R)AN node 608.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-EG layer on top of a ETDP and/or IP layer(s) to carry user plane PDETs.
  • the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer.
  • the SCTP layer may be on top of an IP layer.
  • the SCTP layer provides the guaranteed delivery of application layer messages.
  • point-to-point transmission is used to deliver the signaling PDETs.
  • the Xn-ET protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
  • FIG. 7 illustrates example components of a device 700 in accordance with some embodiments.
  • the device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry (shown as RF circuitry 720), front- end module (FEM) circuitry (shown as FEM circuitry 730), one or more antennas 732, and power management circuitry (PMC) (shown as PMC 734) coupled together at least as shown.
  • RF circuitry shown as RF circuitry 720
  • FEM front- end module
  • PMC power management circuitry
  • the components of the illustrated device 700 may be included in a UE or a RAN node.
  • the device 700 may include fewer elements (e.g., a RAN node may not utilize application circuitry 702, and instead include a processor/controller to process IP data received from an EPC).
  • the device 700 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • the application circuitry 702 may include one or more application processors.
  • the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination thereof
  • processors of application circuitry 702 may process IP data packets received from an EPC.
  • the baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 720 and to generate baseband signals for a transmit signal path of the RF circuitry 720.
  • the baseband circuitry 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 720.
  • the baseband circuitry 704 may include a third generation (3G) baseband processor (3G baseband processor 706), a fourth generation (4G) baseband processor (4G baseband processor 708), a fifth generation (5G) baseband processor (5G baseband processor 710), or other baseband processor(s) 712 for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 704 e.g., one or more of baseband processors
  • the functionality of the illustrated baseband processors may be included in modules stored in the memory 718 and executed via a Central Processing Unit (CPU 714).
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, or
  • encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 704 may include a digital signal processor (DSP), such as one or more audio DSP(s) 716.
  • DSP digital signal processor
  • the one or more audio DSP(s) 716 may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WLAN wireless personal area network
  • Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • the RF circuitry 720 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 720 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 720 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 730 and provide baseband signals to the baseband circuitry 704.
  • the RF circuitry 720 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 730 for transmission.
  • the receive signal path of the RF circuitry 720 may include mixer circuitry 722, amplifier circuitry 724 and filter circuitry 726.
  • the transmit signal path of the RF circuitry 720 may include filter circuitry 726 and mixer circuitry 722.
  • the RF circuitry 720 may also include synthesizer circuitry 728 for synthesizing a frequency for use by the mixer circuitry 722 of the receive signal path and the transmit signal path.
  • the mixer circuitry 722 of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 730 based on the synthesized frequency provided by synthesizer circuitry 728.
  • the amplifier circuitry 724 may be configured to amplify the down-converted signals and the filter circuitry 726 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 704 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • the mixer circuitry 722 of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 722 of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 728 to generate RF output signals for the FEM circuitry 730.
  • the baseband signals may be provided by the baseband circuitry 704 and may be filtered by the filter circuitry 726.
  • the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 may be arranged for direct
  • the mixer circuitry 722 of the receive signal path and the mixer circuitry 722 of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 720 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 720.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 728 may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 728 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 728 may be configured to synthesize an output frequency for use by the mixer circuitry 722 of the RF circuitry 720 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 728 may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 704 or the application circuitry 702 (such as an applications processor) depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 702.
  • Synthesizer circuitry 728 of the RF circuitry 720 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • the synthesizer circuitry 728 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency
  • the RF circuitry 720 may include an IQ/polar converter.
  • the FEM circuitry 730 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 732, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 720 for further processing.
  • the FEM circuitry 730 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 720 for transmission by one or more of the one or more antennas 732.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 720, solely in the FEM circuitry 730, or in both the RF circuitry 720 and the FEM circuitry 730.
  • the FEM circuitry 730 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 730 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 730 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 720).
  • the transmit signal path of the FEM circuitry 730 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 720), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 732).
  • PA power amplifier
  • the PMC 734 may manage power provided to the baseband circuitry 704.
  • the PMC 734 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 734 may often be included when the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a EGE.
  • the PMC 734 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 7 shows the PMC 734 coupled only with the baseband circuitry 704.
  • the PMC 734 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 702, the RF circuitry 720, or the FEM circuitry 730.
  • the PMC 734 may control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 is in an
  • RRC Connected state where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 700 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 700 may not receive data in this state, and in order to receive data, it transitions back to an RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 702 and processors of the baseband circuitry 704 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 704 alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 702 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 8 illustrates example interfaces 800 of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 704 of FIG. 7 may comprise 3G baseband processor 706, 4G baseband processor 708, 5G baseband processor 710, other baseband processor(s) 712, CPU 714, and a memory 718 utilized by said processors.
  • each of the processors may include a respective memory interface 802 to send/receive data to/from the memory 718.
  • the baseband circuitry 704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 804 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704), an application circuitry interface 806 (e.g., an interface to send/receive data to/from the application circuitry 702 of FIG. 7), an RF circuitry interface 808 (e.g., an interface to send/receive data to/from RF circuitry 720 of FIG.
  • a memory interface 804 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704
  • an application circuitry interface 806 e.g., an interface to send/receive data to/from the application circuitry 702 of FIG. 7
  • an RF circuitry interface 808 e.g., an interface to send/receive data to/from RF circuitry 720 of FIG.
  • a wireless hardware connectivity interface 810 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 812 e.g., an interface to send/receive power or control signals to/from the PMC 734.
  • FIG. 9 is a block diagram illustrating components 900, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 9 shows a diagrammatic representation of hardware resources 902 including one or more processors 912 (or processor cores), one or more memory/storage devices 918, and one or more communication resources 920, each of which may be communicatively coupled via a bus 922.
  • node virtualization e.g., NFV
  • a hypervisor 904 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 902.
  • the processors 912 may include, for example, a processor 914 and a processor 916.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 918 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 918 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM),
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 920 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 906 or one or more databases 908 via a network 910.
  • the communication resources 920 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
  • NFC components e.g., NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • Instructions 924 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 912 to perform any one or more of the methodologies discussed herein.
  • the instructions 924 may reside, completely or partially, within at least one of the processors 912 (e.g., within the processor’s cache memory), the memory/storage devices 918, or any suitable combination
  • any portion of the instructions 924 may be transferred to the hardware resources 902 from any combination of the peripheral devices 906 or the databases
  • the memory of the processors 912, the memory/storage devices 918, the peripheral devices 906, and the databases 908 are examples of computer-readable and machine-readable media.
  • an apparatus to be employed as a gNB-CU-CP interconnecting a gNB-CU-UP via an El control interface includes means for
  • the gNB-CET-CP determines to accept or reject forwarding proposals by a source and/or to propagate forwarding requests or acceptances to the gNB- CU-UP.
  • the gNB-CU-UP decides to accept or reject forwarding proposals propagated by the gNB-CU-CP together with admission control.
  • the gNB-CU-UP provides the result of acceptance or rejection of forwarding proposals back to the gNB-CU-CP.
  • Example 1 is a computing apparatus for data forwarding during handover from a source g Node B (gNB) to a target gNB of a wireless communication system, the apparatus comprising a memory interface and a processor.
  • the memory interface to send or receive, to or from a memory device, data corresponding to a proposal to forward one or more downlink (DL) quality of service (QoS) flows from the source gNB to the target gNB.
  • DL downlink
  • QoS quality of service
  • the processor to: process, at a gNB central unit control plane entity (gNB-CU-CP) of the target gNB, the proposal; determine, at the gNB-CU-CP, which of the QoS flows to accept or reject for forwarding; and generate, at the gNB-CU-CP, an indication for a gNB central unit user plane entity (gNB-CU-UP) of accepted QoS flows for forwarding.
  • gNB-CU-CP gNB central unit control plane entity
  • Example 2 is the apparatus of Example 1, wherein to generate the indication comprises to generate a data forwarding information request comprising a list of the accepted QoS flows subject to forwarding on one or more forwarding tunnels.
  • Example 3 is the apparatus of Example 2, wherein the data forwarding information request is used for a protocol data unit (PDU) session.
  • PDU protocol data unit
  • Example 4 is the apparatus of Example 3, wherein the one or more forwarding tunnels includes a PDU session forwarding tunnel.
  • Example 5 is the apparatus of Example 2, wherein the data forwarding information request is used for data radio bearer (DRB) level data forwarding.
  • DRB data radio bearer
  • Example 6 is the apparatus of Example 5, wherein the one or more forwarding tunnels includes a DRB forwarding tunnel.
  • Example 7 is the apparatus of Example 2, wherein the list comprises a QoS flow mapping list including a list of data radio bearers (DRBs) comprising information about mapped QoS flows.
  • DRBs data radio bearers
  • Example 8 is a computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor of a g Node B (gNB), cause the processor to: process, at a gNB central unit control plane entity (gNB-CEl-CP) of a target gNB, a proposal to forward one or more downlink (DL) quality of service (QoS) flows from a source gNB to the target gNB; determine, at the gNB-CEl-CP, which of the QoS flows to accept or reject for forwarding; and generate, at the gNB-CEl-CP, an indication for a gNB central unit user plane entity (gNB-CU-UP) of accepted QoS flows for forwarding.
  • gNB-CEl-CP gNB central unit control plane entity
  • gNB-CU-UP gNB central unit user plane entity
  • Example 9 is the computer-readable storage medium of Example 8, wherein to generate the indication comprises generating a data forwarding information request comprising a list of the accepted QoS flows subject to forwarding on one or more
  • Example 10 is the computer-readable storage medium of Example 9, wherein the data forwarding information request is used for a protocol data unit (PDU) session.
  • PDU protocol data unit
  • Example 1 1 is the computer-readable storage medium of Example 10, wherein the one or more forwarding tunnels includes a PDE1 session forwarding tunnel.
  • Example 12 is the computer-readable storage medium of Example 9, wherein the data forwarding information request is used for data radio bearer (DRB) level data forwarding.
  • DRB data radio bearer
  • Example 13 is the computer-readable storage medium of Example 12, wherein the one or more forwarding tunnels includes a DRB forwarding tunnel.
  • Example 14 is the computer-readable storage medium of Example 9, wherein the list comprises a QoS flow mapping list including a list of data radio bearers (DRBs) comprising information about mapped QoS flows.
  • DRBs data radio bearers
  • Example 15 is an apparatus for a g Node B (gNB) central unit user plane entity (gNB-CU-UP), the apparatus comprising a memory interface and a processor.
  • the memory interface to send or receive, to or from a memory device, data corresponding to a list of accepted quality of service (QoS) flows subject to forwarding on one or more forwarding tunnels.
  • QoS quality of service
  • the processor to: process the list of accepted QoS flows subject to forwarding on the one or more forwarding tunnels, the accepted QoS flows corresponding to a user equipment (UE) undergoing inter-gNB handover; receive new packets from the UE; and based on the list of accepted QoS flows, handle the new packets before receiving an end marker forwarded, wherein the new packets correspond to one or more QoS flows that are different than the accepted QoS flows.
  • UE user equipment
  • Example 16 is the apparatus of Example 15, wherein the one or more forwarding tunnels includes a protocol data unit (PDEi) session forward tunnel.
  • PDEi protocol data unit
  • Example 17 is the apparatus of Example 15, wherein the one or more forwarding tunnels includes data radio bearer (DRB) forwarding tunnel.
  • DRB data radio bearer
  • Example 18 is the apparatus of Example 15, wherein the list comprises a QoS flow mapping list including a list of data radio bearers (DRBs) comprising information about mapped QoS flows.
  • DRBs data radio bearers
  • Example 19 is the apparatus of Example 15, wherein the processor is further configured to decide whether to accept or reject forwarding proposals propagated by a target gNB central unit control plane entity (gNB-CEi-CP) from a source gNB during admission control.
  • gNB-CEi-CP target gNB central unit control plane entity
  • Example 20 is a method for a g Node B (gNB) central unit user plane entity (gNB- CU-UP), the method comprising: processing a list of accepted quality of service (QoS) flows subject to forwarding on one or more forwarding tunnels, the accepted QoS flows corresponding to a user equipment (UE) undergoing inter-gNB handover; receiving new packets from the UE; and based on the list of accepted QoS flows, handling the new packets before receiving an end marker forwarded, wherein the new packets correspond to one or more QoS flows that are different than the accepted QoS flows.
  • QoS quality of service
  • Example 21 is the method of Example 20, wherein the one or more forwarding tunnels includes a protocol data unit (PDEI) session forwarding tunnel.
  • PDEI protocol data unit
  • Example 22 is the method of Example 20, wherein the one or more forwarding tunnels includes data radio bearer (DRB) forwarding tunnel.
  • DRB data radio bearer
  • Example 23 is the method of Example 20, wherein the list comprises a QoS flow mapping list including a list of data radio bearers (DRBs) comprising information about mapped QoS flows.
  • DRBs data radio bearers
  • Example 24 is the method of Example 20, further comprising deciding whether to accept or reject forwarding proposals propagated by a target gNB central unit control plane entity (gNB-CEi-CP) from a source gNB during admission control.
  • gNB-CEi-CP target gNB central unit control plane entity

Landscapes

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

Abstract

Des systèmes et un procédé fournissent un transfert d'unités de données de protocole (PDU). Un gNB-CU-CP d'un gNB cible traite une proposition de transfert d'un ou de plusieurs flux de qualité de service (QoS) en liaison descendante d'un gNB source à un gNB cible. Le gNB-CU-CP détermine quels flux de QoS sont acceptés ou rejetés pour le transfert et génère pour un gNB-CU-UP une indication des flux de QoS acceptés pour le transfert. Le gNB-CU-CP peut se propager par proposition de transfert de liaison descendante de flux de QoS et le gNB-CU-UP peut décider d'accepter ou non lors de l'admission. Sur la base de la liste des flux de QoS acceptés, le gNB-CU-UP gère de nouveaux paquets provenant d'un UE avant de recevoir un marqueur de fin transféré, les nouveaux paquets correspondant à un ou plusieurs flux de QoS qui sont différents des flux de QoS acceptés.
EP19848227.5A 2018-08-10 2019-08-08 Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération Pending EP3834484A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862717307P 2018-08-10 2018-08-10
PCT/US2019/045641 WO2020033636A1 (fr) 2018-08-10 2019-08-08 Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération

Publications (2)

Publication Number Publication Date
EP3834484A1 true EP3834484A1 (fr) 2021-06-16
EP3834484A4 EP3834484A4 (fr) 2022-04-27

Family

ID=69415605

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19848227.5A Pending EP3834484A4 (fr) 2018-08-10 2019-08-08 Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération

Country Status (2)

Country Link
EP (1) EP3834484A4 (fr)
WO (1) WO2020033636A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747524A (zh) * 2020-05-29 2021-12-03 北京三星通信技术研究有限公司 支持切换的方法和设备
CN115767652A (zh) * 2021-09-03 2023-03-07 中兴通讯股份有限公司 站点切换方法、基站、存储介质

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3482602B1 (fr) * 2016-07-05 2023-10-18 Apple Inc. Systèmes, procédés et dispositifs de séparation de plan utilisateur de commande pour des réseaux d'accès radio 5g

Also Published As

Publication number Publication date
WO2020033636A1 (fr) 2020-02-13
EP3834484A4 (fr) 2022-04-27

Similar Documents

Publication Publication Date Title
US11877355B2 (en) Efficient and reliable data transfer in 5G systems
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
US20230422102A1 (en) Flexible scope of packet filters for reflective quality of service
US20190394834A1 (en) Measurement gap sharing
US10979958B2 (en) Systems, methods, and apparatuses for providing and obtaining scheduling information for SIB1-BR during handover
US10841808B2 (en) Apparatus and medium for enabling multi-carrier operation
US10631256B2 (en) Power headroom of grantless uplink
US11502805B2 (en) Resource mapping schemes for channel state information reporting on new radio physical uplink control channel
US11838839B2 (en) V2X policy and parameters provisioning to user equipment by a policy and control function
US20210297192A1 (en) Enhanced harq feedback for reliable communications
US11743870B2 (en) Interruption and delay for V2X sidelink carrier aggregation
WO2018085713A2 (fr) Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués
WO2018089879A1 (fr) Configuration de mesurage de gestion de ressources radio
WO2019032532A1 (fr) Nouvelle gestion d'enregistrement radio
CN110582121A (zh) 用于ue请求ue策略初始配给或更新的解决方案
US11375524B2 (en) Time advance adjustment delay for shortened transmission time interval under carrier aggregation or dual connectivity
US20200220673A1 (en) Frame structure for unlicensed narrowband internet-of-things system
EP3834484A1 (fr) Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération
EP3462770A1 (fr) Procédés et appareil pour de multiples associations tnl entre ran et amf pour des déploiements virtualisés
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20201123

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20220325

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/08 20090101ALI20220321BHEP

Ipc: H04W 36/08 20090101ALI20220321BHEP

Ipc: H04W 28/02 20090101ALI20220321BHEP

Ipc: H04W 36/02 20090101ALI20220321BHEP

Ipc: H04W 36/00 20090101AFI20220321BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20240418