Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/78—Architectures of resource allocation
  • H04L47/781—Centralised allocation of resources
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/04—Network management architectures or arrangements
  • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/04—Network management architectures or arrangements
  • H04L41/052—Network management architectures or arrangements using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

• Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to congestion control for remote direct-memory access (RDMA) in next-generation cellular networks.
• RDMA remote direct-memory access
• RDMA Remote Direct Memory Access
• OS operating system
• RDMA bypasses the OS and allows programs to have lower latency, higher throughput, and a smaller CPU footprint relative to traditional interfaces.
• embodiments of the present disclosure provide solutions for RDMA over Cellular Network (RoCN).
• Figure 1 illustrates an example of RDMA protocol stack options in accordance with various embodiments.
• Figure 2 illustrates an example of a protocol stack for RoCN Functions in accordance with various embodiments.
• FIG. 3 illustrates an example of RoCN transport control is end to end between UE and Comp SF/DSF (UE is IP or non-IP based) for solution 1 (Option 1) in accordance with various embodiments.
• Figure 4 illustrates an example of an RoCN transport control that is end to end between UE and Comp SF/DSF (UE is non IP based) for solution 1 (Optionl) in accordance with various embodiments.
• Figure 5 illustrates an example of an RDMA transport control that is end to end between UE and xNB for solution 2in accordance with various embodiments.
• Figure 6 illustrates an example of a transport protocol BTH Format in accordance with various embodiments.
• Figure 7 illustrates an example of an RoCN-aware MAC that is end to end between UE and xNB for solution 1 (Option 2)in accordance with various embodiments.
• Figure 8 illustrates an example of an RoCN information update between RoCN coontrol at Comp SF and xNB in accordance with various embodiments.
• Figure 9 illustrates an example of an RDMA-aware MAC that is end to end between UE and xNB for solution 2 (Option 2) in accordance with various embodiments.
• Figure 10 illustrates an example of an extended ANBR for xNB to instruct a rate change for RoCN traffic in accordance with various embodiments.
• Figure 11 illustrates an example of an extended ANBRQ for UE to query for a rate change for RoCN traffic in accordance with various embodiments.
• Figure 12 schematically illustrates a wireless network in accordance with various embodiments.
• Figure 13 schematically illustrates components of a wireless network in accordance with various embodiments.
• Figure 14 is a block diagram illustrating components, 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.
• a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
• FIGS 15, 16, and 17 depict examples of procedures for practicing the various embodiments discussed herein.
• RDMA protocol stacks defined based on different media and transport protocols as shown in Figure 1.
• RDMA can be enabled between UE and RAN as an option for computing offloading and data services in some embodiments.
• the IB transport protocol as shown in Figure 1 generally requires that the underlying network as “lossless” network, which is fulfilled in ethemet by the Datacenter Bridging (DCB) protocols including Priority Flow Control (PFC, IEEE 802.1Qbb) and Explicit Congestion Notification (ECN, RFC3168), congestion control mechanisms, etc.
• DCB Datacenter Bridging
• PFC Priority Flow Control
• ECN Explicit Congestion Notification
• congestion control mechanisms etc.
• different congestion control algorithms and mechanisms can be applied and optimized based on the topology and traffic characteristics of a datacenter cloud.
• the congestion control for RDMA in the next generation cellular network with a cloudified infrastructure is different from the Ethemet infrastructure in at least the following aspects:
• Comp SF compute service function
• DSF Data storage function
• CNP congestion notification packet
• ANBR/ANBRQ mechanisms are defined to let RAN proactively adjust the rate for multi-media services, separate from ECN. It can be leveraged for RDMA congestion control purposes as well.
• RDMA for cellular network
• RoCN RDMA over Cellular Network
• ANBR Access Network Bitrate Recommendation
• ANBRQ Access Network Bitrate Recommendation
• This disclosure takes ANBR/ANBRQ message as an example.
• the solutions do not limit the use of new messages with required information for RoCN.
• RoCN RoCN transport protocol
• RoCN control RoCN Connection Management
• CM RoCN Connection Management
• the RoCN control is the function to handle congestion control for RoCN traffic.
• RSR RoCN Sender Report
• RRR RoCN Receiver Report
• RAI RoCN Application Information
• ANBR/ANBRQ are extended with required information for RoCN between UE and xNB.
• the RoCN functions for cellular network can be partitioned as illustrated in Figure 2:
• CM RoCN Connection Management
• QP RoCN QueuePair
• RoCN transport protocol to handle RDMA user plane traffic, send/receive RoCN packets.
• RoCN transport control to exchange information about RoCN traffic such as traffic statistics, congestion control information, QoS, packet delay for per QP basis or per end points basis.
• the protocol stack for the three functions are shown in Figure 2 for the option where the three functions (the RoCN CM function and two RoCN transport control functions) are on the same RoCN end point. However, there are different options to deploy the functions.
• the protocols in dotted boxes are optional.
• the RoCN CM function can also be combined with a Radio Resource Control (RRC) function as an enhancement.
• RRC Radio Resource Control
• the RDMA CM information can be carried as Information Elements (IES) for RRC.
• Some embodiments may include solutions for computing scaling between UE and the cellular network to provide computing (e.g., solution 1) as a service or computing as resource (e.g., solution 2).
• solution 1 a service
• computing as resource e.g., solution 2
• the mechanisms proposed in this disclosure apply to both solutions.
• RoCN transport protocol resides end to end between UE and Comp SF/DSF to handle RoCN traffic, e.g., for computing offloading and data plane traffic.
• the RoCN transport control can reside between UE and Comp SF/DSF or between xNB and Comp SF/DSF. Details for these two options are shown below.
• Embodiments may enable the xNB to support the RoCN PDU, a new PDU type “RoCN” or “RDMA” is defined in addition to the existing PDU types, e.g., IP, non-IP, ethemet, etc.
• Option 1 RoCN transport control protocol end to end between UE and Comp SF/DSF
• Figure 3 leverages GTP between xNB and Comp SF/DSF to support IP based or non-IP based UE.
• GTP is used between xNB and Comp SF/DSF
• the protocol stack from LI up to RoCN layer including GTP tunneling can be integrated in the RoCN Network Interface Card (RNIC) on the Comp SF/DSF side.
• RNIC RoCN Network Interface Card
• a RoCN packet received at the xNB side from UE generally needs to be processed in the user space for PHY MAC and possible part of PDCP before being sent to the GTP or UDP/IP interfaces.
• an indicator in PHY is needed to allow the xNB to put the MAC PDU to the memory space mapped to the related RoCN interface (for DU/CU combined case).
• RLC may need to be aware of RoCN as well (for DU/CU split case). This applies to all the options described in this disclosure.
• the RoCN traffic can be made aware to the PHY layer by the following approaches:
• option 1 allocate RoCN traffic to certain carriers or resource blocks in a carrier
• option 2 add a physical channel to carry the RoCN traffic indicator
• option 3 add an information field to the physical control information to carry the RoCN traffic indicator
• Figure 4 indicates an option to support Non-IP UE and the xNB is responsible to map the radio bearer ID to UDP/IP address and port number by the adaptation layer without GTP tunneling between xNB and Comp SF/DSF.
• RoCN control The primary functionality of RoCN control is to exchange end to end information between RoCN end points for congestion control, QoS tracking, e.g., UE and Comp SF/DSF.
• the RoCN control information can be carried in RDMA data packets, defined as a special RDMA packet similar to CNP packet format.
• the information exchanged for RoCN control include but not limited to
• These RoCN packets are considered as L4 packets which can be carried as lower layer MTUs.
• UDP/IP header can be added to indicate the network end points for routing similar to RoCEv2.
• BTH Base Transfer Header
• the OpCode 10110-11111 are reserved for extension, which can be extended to include RSR, RRR, RAI packets.
• the following table exemplifies the extension.
• the RSR, RRR, RAI can be sent with different connection mode such as reliable connection or unreliable datagram. Therefore, only the 5 digit [0-4] of the OpCode is shown below with different choice of 3 digit [5-7] to indicate the transmission mode.
• the RSR, RRR, RAI can be defined similar to current CNP where the 3 digit [5-7] is defined the same as 100.
• the 5-digit OpCode can be used to indicate RSR, RRR, RAI extensions.
• the Destination QP can be configured as a special number such as “0” to indicate that it is for RoCN control purpose.
• the partition key can indicate a specific network slice by using a S- NSSAI, application ID, etc.
• the RSR include but not limited to the following information
• the parameters and its statistics from the sender’s point of view such as QP IDs, the average sent data rate, time interval, range of transmission rate, packet interval, traffic type, packet number and time stamp, retransmissions, transmission mode, etc.
• the RRR include but not limited to the following information
• the parameters and its statistics from the receiver’s point of view such as QP IDs, average received data rate, time interval, range of transmission rate, packet interval, traffic type, packet number and time stamp, retransmissions, transmission mode, etc.
• the RAI include but not limited to the following information
• Application specific information such as application ID, application status, application observed QoS and application associated QP related configurations.
• the RSR, RRR, RAI can be QP specific or non-QP specific. If it is QP specific, different statistics and parameters can be provided to different QPs.
• the RoCN control function can also be in the xNB and Comp SF/DSF at the network side, which doesn’t require standardization of the message exchange between RoCN control, but a standardized message exchange similar to Option 1 between RoCN end points can also apply for interoperability at the network side.
• RoCN control is not associated with RoCN.
• the MAC layer can be enhanced for congestion control purposes for RoCN traffic as shown in Figure 7.
• the RoCN control function can be associated or not associated with a specific UE, PDU session or a QP.
• the RRR, RSR and RAI packets need to include the related UE ID, session ID or QP ID to indicate that the included information is UE specific, a session specific or a QP specific.
• the information about a UE, session or QP needs to be sent to the xNB from Comp CF and other data plane control functions after the QP is set up. This message exchange is shown in Figure 8.
• the RoCN CM procedure create the required QP for UE and generate related information.
• the RoCN control sends a RoCN information update request to the xNB including the information such as the QP IDs associated with a session ID or a UE ID.
• Other related configurations can be sent through RRR, RSR, RAI.
• the xNB sends a RoCN information update response to indicate the information is received.
• the RDMA aware MAC can be enhanced for congestion control purposes as shown in Figure 9.
• ANBR is proposed in 5GNR for the access network to instruct a recommended bitrate for multimedia traffic based on some metrics from the gNB such as congestion.
• the UE can also send ANBRQ to gNB to request an increase of the bitrate.
• the ANBR and ANBRQ messages are mapped to MAC CEs.
• the ANBR/ ANBRQ can be extended to adjust the RoCN rates for congestion control purposes. It can apply to both Solution 1 and Solution 2.
• the ANBR/ ANBRQ can be at bearer level or QP level depending on the decisions from xNB for ANBR and UE for ANBRQ. The message flow is shown in Figure 10 and Figure 11.
• xNB can make a decision about rate adjustment for RoCN traffic, which can be QP specific or non-QP specific. The decision can be based on the information collected in the xNB such as buffer status, ECN, or information received RoCN control packets as described in Option 1.
• the xNB sends a ANBR for RoCN message to instruct the UE for a rate adjustment.
• This ANBR message can include the following information a. QP ID for the RoCN traffic or a bearer ID for multiple QP traffic. How UE will adjust the RoCN traffic rate is implementation specific.
• Multiple rate recommendations can be included in one ANBR message
• UE can make a decision about rate increase for RoCN traffic due to information collected by the UE such as buffer status, QoS, application requirement, etc..
• the increase can be at QP level or non-QP level. If the rate increase is at bearer level, the UE can provide a target combined rate for all the QPs for a bearer.
• the UE sends a ANBRQ to xNB to query for a rate adjustment.
• This ANBRQ message can include the following information a. QP ID for the RoCN traffic or a bearer ID for multiple QP traffic. How xNB can adjust the RoCN traffic rate can be defined by adjustment rules.
• the rate adjustment/increase rule for multiple QPs For example, a proportional rule can indicate the data rate for each QP can be increased with the same factor.
• Multiple rate queries can be included in one ANBRQ message
• FIGS 12-13 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
• Figure 12 illustrates a network 1200 in accordance with various embodiments.
• the network 1200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
• 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
• the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.
• the network 1200 may include a UE 1202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1204 via an over-the-air connection.
• the UE 1202 may be communicatively coupled with the RAN 1204 by a Uu interface.
• the UE 1202 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
• the network 1200 may include a plurality of UEs coupled directly with one another via a sidelink interface.
• the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
• the UE 1202 may additionally communicate with an AP 1206 via an over-the-air connection.
• the AP 1206 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1204.
• the connection between the UE 1202 and the AP 1206 may be consistent with any IEEE 802.11 protocol, wherein the AP 1206 could be a wireless fidelity (Wi-Fi®) router.
• the UE 1202, RAN 1204, and AP 1206 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
• Cellular- WLAN aggregation may involve the UE 1202 being configured by the RAN 1204 to utilize both cellular radio resources and WLAN resources.
• the RAN 1204 may include one or more access nodes, for example, AN 1208.
• AN 1208 may terminate air-interface protocols for the UE 1202 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1208 may enable data/voice connectivity between CN 1220 and the UE 1202.
• the AN 1208 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
• the AN 1208 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
• the AN 1208 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
• the RAN 1204 may be coupled with one another via an X2 interface (if the RAN 1204 is an LTE RAN) or an Xn interface (if the RAN 1204 is a 5G RAN).
• the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
• the ANs of the RAN 1204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1202 with an air interface for network access.
• the UE 1202 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1204.
• the UE 1202 and RAN 1204 may use carrier aggregation to allow the UE 1202 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
• a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
• the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
• the RAN 1204 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
• the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
• the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
• LBT listen-before-talk
• the UE 1202 or AN 1208 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
• An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
• An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
• an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
• the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
• the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
• the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
• the RAN 1204 may be an LTE RAN 1210 with eNBs, for example, eNB 1212.
• the LTE RAN 1210 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
• the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
• the LTE air interface may operating on sub-6 GHz bands.
• the RAN 1204 may be an NG-RAN 1214 with gNBs, for example, gNB 1216, or ng-eNBs, for example, ng-eNB 1218.
• the gNB 1216 may connect with 5G-enabled UEs using a 5 G NR interface.
• the gNB 1216 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
• the ng-eNB 1218 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
• the gNB 1216 and the ng-eNB 1218 may connect with each other over an Xn interface.
• the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 1214 and a UPF 1248 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1214 and an AMF 1244 (e.g., N2 interface).
• NG-U NG user plane
• N3 interface e.g., N3 interface
• N-C NG control plane
• the NG-RAN 1214 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
• the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
• the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
• the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
• the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
• the 5G-NR air interface may utilize BWPs for various purposes.
• BWP can be used for dynamic adaptation of the SCS.
• the UE 1202 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1202, the SCS of the transmission is changed as well.
• Another use case example of BWP is related to power saving.
• multiple BWPs can be configured for the UE 1202 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
• a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 1202 and in some cases at the gNB 1216.
• a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
• the RAN 1204 is communicatively coupled to CN 1220 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1202).
• the components of the CN 1220 may be implemented in one physical node or separate physical nodes.
• NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1220 onto physical compute/storage resources in servers, switches, etc.
• a logical instantiation of the CN 1220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1220 may be referred to as a network sub-slice.
• the CN 1220 may be an LTE CN 1222, which may also be referred to as an EPC.
• the LTE CN 1222 may include MME 1224, SGW 1226, SGSN 1228, HSS 1230, PGW 1232, and PCRF 1234 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1222 may be briefly introduced as follows.
• the MME 1224 may implement mobility management functions to track a current location of the UE 1202 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
• the SGW 1226 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1222.
• the SGW 1226 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 SGSN 1228 may track a location of the UE 1202 and perform security functions and access control. In addition, the SGSN 1228 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1224; MME selection for handovers; etc.
• the S3 reference point between the MME 1224 and the SGSN 1228 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
• the HSS 1230 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
• the HSS 1230 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
• An S6a reference point between the HSS 1230 and the MME 1224 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1220.
• the PGW 1232 may terminate an SGi interface toward a data network (DN) 1236 that may include an application/content server 1238.
• the PGW 1232 may route data packets between the LTE CN 1222 and the data network 1236.
• the PGW 1232 may be coupled with the SGW 1226 by an S5 reference point to facilitate user plane tunneling and tunnel management.
• the PGW 1232 may further include a node for policy enforcement and charging data collection (for example, PCEF).
• the SGi reference point between the PGW 1232 and the data network 12 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
• the PGW 1232 may be coupled with a PCRF 1234 via a Gx reference point.
• the PCRF 1234 is the policy and charging control element of the LTE CN 1222.
• the PCRF 1234 may be communicatively coupled to the app/content server 1238 to determine appropriate QoS and charging parameters for service flows.
• the PCRF 1232 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
• the CN 1220 may be a 5GC 1240.
• the 5GC 1240 may include an AUSF 1242, AMF 1244, SMF 1246, UPF 1248, NSSF 1250, NEF 1252, NRF 1254, PCF 1256, UDM 1258, and AF 1260 coupled with one another over interfaces (or “reference points”) as shown.
• Functions of the elements of the 5GC 1240 may be briefly introduced as follows.
• the AUSF 1242 may store data for authentication of UE 1202 and handle authentication- related functionality.
• the AUSF 1242 may facilitate a common authentication framework for various access types.
• the AUSF 1242 may exhibit an Nausf service-based interface.
• the AMF 1244 may allow other functions of the 5GC 1240 to communicate with the UE 1202 and the RAN 1204 and to subscribe to notifications about mobility events with respect to the UE 1202.
• the AMF 1244 may be responsible for registration management (for example, for registering UE 1202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
• the AMF 1244 may provide transport for SM messages between the UE 1202 and the SMF 1246, and act as a transparent proxy for routing SM messages.
• AMF 1244 may also provide transport for SMS messages between UE 1202 and an SMSF.
• AMF 1244 may interact with the AUSF 1242 and the UE 1202 to perform various security anchor and context management functions.
• AMF 1244 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1204 and the AMF 1244; and the AMF 1244 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
• AMF 1244 may also support NAS signaling with the UE 1202 over an N3 IWF interface.
• the SMF 1246 may be responsible for SM (for example, session establishment, tunnel management between UPF 1248 and AN 1208); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1248 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 1244 overN2 to AN 1208; and determining SSC mode of a session.
• SM for example, session establishment, tunnel management between UPF 1248 and AN 1208
• UE IP address allocation and management including optional authorization
• selection and control of UP function configuring traffic steering at UPF 1248 to route traffic to proper destination
• termination of interfaces toward policy control functions controlling part of policy enforcement, charging, and QoS
• lawful intercept for SM events and interface to LI system
• SM may refer to management of a PDU session
• a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1202 and the data network 1236.
• the UPF 1248 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1236, and a branching point to support multi-homed PDU session.
• the UPF 1248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a 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 perform downlink packet buffering and downlink data notification triggering.
• UPF 1248 may include an uplink classifier to support routing traffic flows to a data network.
• the NSSF 1250 may select a set of network slice instances serving the UE 1202.
• the NSSF 1250 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
• the NSSF 1250 may also determine the AMF set to be used to serve the UE 1202, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1254.
• the selection of a set of network slice instances for the UE 1202 may be triggered by the AMF 1244 with which the UE 1202 is registered by interacting with the NSSF 1250, which may lead to a change of AMF.
• the NSSF 1250 may interact with the AMF 1244 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 1250 may exhibit an Nnssf service-based interface.
• the NEF 1252 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1260), edge computing or fog computing systems, etc.
• the NEF 1252 may authenticate, authorize, or throttle the AFs.
• NEF 1252 may also translate information exchanged with the AF 1260 and information exchanged with internal network functions. For example, the NEF 1252 may translate between an AF-Service-Identifier and an internal 5GC information.
• NEF 1252 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1252 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1252 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1252 may exhibit an Nnef servicebased interface.
• the NRF 1254 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 1254 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1254 may exhibit the Nnrf service-based interface.
• the PCF 1256 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
• the PCF 1256 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1258.
• the PCF 1256 exhibit an Npcf service-based interface.
• the UDM 1258 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1202. For example, subscription data may be communicated via an N8 reference point between the UDM 1258 and the AMF 1244.
• the UDM 1258 may include two parts, an application front end and a UDR.
• the UDR may store subscription data and policy data for the UDM 1258 and the PCF 1256, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1202) for the NEF 1252.
• the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1258, PCF 1256, and NEF 1252 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
• the UDM may include a UDM- FE, which is in charge of processing 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 information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
• the UDM 1258 may exhibit the Nudm service-based interface.
• the AF 1260 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
• the 5GC 1240 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 1202 is attached to the network. This may reduce latency and load on the network.
• the 5GC 1240 may select a UPF 1248 close to the UE 1202 and execute traffic steering from the UPF 1248 to data network 1236 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1260. In this way, the AF 1260 may influence UPF (re)selection and traffic routing.
• the network operator may permit AF 1260 to interact directly with relevant NFs. Additionally, the AF 1260 may exhibit an Naf service-based interface.
• the data network 1236 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 1238.
• FIG. 13 schematically illustrates a wireless network 1300 in accordance with various embodiments.
• the wireless network 1300 may include a UE 1302 in wireless communication with an AN 1304.
• the UE 1302 and AN 1304 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
• the UE 1302 may be communicatively coupled with the AN 1304 via connection 1306.
• the connection 1306 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
• the UE 1302 may include a host platform 1308 coupled with a modem platform 1310.
• the host platform 1308 may include application processing circuitry 1312, which may be coupled with protocol processing circuitry 1314 of the modem platform 1310.
• the application processing circuitry 1312 may run various applications for the UE 1302 that source/sink application data.
• the application processing circuitry 1312 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
• the protocol processing circuitry 1314 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1306.
• the layer operations implemented by the protocol processing circuitry 1314 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
• the modem platform 1310 may further include digital baseband circuitry 1316 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1314 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
• PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
• the modem platform 1310 may further include transmit circuitry 1318, receive circuitry 1320, RF circuitry 1322, and RF front end (RFFE) 1324, which may include or connect to one or more antenna panels 1326.
• the transmit circuitry 1318 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.
• the receive circuitry 1320 may include an analog-to-digital converter, mixer, IF components, etc.
• the RF circuitry 1322 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
• RFFE 1324 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
• transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
• the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
• the protocol processing circuitry 1314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
• a UE reception may be established by and via the antenna panels 1326, RFFE 1324, RF circuitry 1322, receive circuitry 1320, digital baseband circuitry 1316, and protocol processing circuitry 1314.
• the antenna panels 1326 may receive a transmission from the AN 1304 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1326.
• a UE transmission may be established by and via the protocol processing circuitry 1314, digital baseband circuitry 1316, transmit circuitry 1318, RF circuitry 1322, RFFE 1324, and antenna panels 1326.
• the transmit components of the UE 1304 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1326.
• the AN 1304 may include a host platform 1328 coupled with a modem platform 1330.
• the host platform 1328 may include application processing circuitry 1332 coupled with protocol processing circuitry 1334 of the modem platform 1330.
• the modem platform may further include digital baseband circuitry 1336, transmit circuitry 1338, receive circuitry 1340, RF circuitry 1342, RFFE circuitry 1344, and antenna panels 1346.
• the components of the AN 1304 may be similar to and substantially interchangeable with like- named components of the UE 1302.
• the components of the AN 1308 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
• Figure 14 is a block diagram illustrating components, 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.
• Figure 14 shows a diagrammatic representation of hardware resources 1400 including one or more processors (or processor cores) 1410, one or more memory/storage devices 1420, and one or more communication resources 1430, each of which may be communicatively coupled via a bus 1440 or other interface circuitry.
• a hypervisor 1402 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1400.
• the processors 1410 may include, for example, a processor 1412 and a processor 1414.
• the processors 1410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
• CPU central processing unit
• RISC reduced instruction set computing
• CISC complex instruction set computing
• GPU graphics processing unit
• DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
• the memory/storage devices 1420 may include main memory, disk storage, or any suitable combination thereof.
• the memory/storage devices 1420 may include, but are not limited to, any type of volatile, non-volatile, or semi-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), Flash memory, solid-state storage, etc.
• 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 1430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1404 or one or more databases 1406 or other network elements via a network 1408.
• the communication resources 1430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
• Instructions 1450 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1410 to perform any one or more of the methodologies discussed herein.
• the instructions 1450 may reside, completely or partially, within at least one of the processors 1410 (e.g., within the processor’s cache memory), the memory/storage devices 1420, or any suitable combination thereof.
• any portion of the instructions 1450 may be transferred to the hardware resources 1400 from any combination of the peripheral devices 1404 or the databases 1406. Accordingly, the memory of processors 1410, the memory/storage devices 1420, the peripheral devices 1404, and the databases 1406 are examples of computer-readable and machine-readable media. EXAMPLE PROCEDURES
• process 1500 may include, at 1505, determining, based on remote direct memory access (RDMA) information, RDMA over cellular network (RoCN) control information that includes: an RoCN sender report (RSR) including transmission and reception statistics from a sender, an RoCN receiver report (RRR) including reception statistics from receivers, or RoCN application information (RAI) including application-specific information.
• RSR remote direct memory access
• RRR RoCN receiver report
• RAI RoCN application information
• the process further includes, at 1510, encoding an RDMA data packet for transmission to a next-generation NodeB (gNB) that includes the RoCN control information.
• gNB next-generation NodeB
• the process 1600 includes, at 1605, receiving, from a user equipment (UE), a remote direct memory access (RDMA) data packet that includes RDMA over cellular network (RoCN) control information, wherein the RoCN control information includes: an RoCN sender report (RSR) including transmission and reception statistics from a sender, an RoCN receiver report (RRR) including reception statistics from receivers, or RoCN application information (RAI) including application-specific information.
• the process further includes, at 1610, receiving, from an RoCN control function at a computing service function (Comp SF), an RoCN information update request that includes: a queue pair (QP) identifier, a UE identifier, or a session identifier.
• the process 1700 includes, at 1705, determining a rate adjustment associated with remote direct memory access (RDMA) over cellular network (RoCN) traffic.
• the process further includes, at 1710, encoding an access network bitrate recommendation (ANBR) message for transmission to a user equipment (UE) that includes an indication of the RoCN traffic rate adjustment.
• RDMA remote direct memory access
• ANBR access network bitrate recommendation
• At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
• the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
• circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
• Example 1 may include a function partition of RoCN comprising: o The RoCN transport protocol to handle the application RDMA traffic; o The RoCN control for congestion and rate control; and/or o The RoCN Connection Management to setup RoCN connections, manage keys, etc.
• Example 2 may include the protocol stacks to enable RoCN congestion control, e.g., including one or more of: o Option 1 : the RoCN control is end to end between UE and another RoCN end points such as the Comp SF/DSF o Option 2: the RoCN control is end to end between xNB and another RoCN end points such as the Comp SF/DSF in the cellular network side
• Example 3 may include the indicator at PHY (DU/CU combined case) or RLC (DU/CU split case) on the xNB side to allow a RoCN packet to be identified and put into the associated memory space for processing to achieve zero copy at xNB, e.g., including one or more of: o option 1 : allocate RoCN traffic to certain carriers or resource blocks in a carrier o option 2: add a physical channel to carry the RoCN traffic indicator o option 3 : add an information field to the physical control information to carry the RoCN traffic
• Example 4 may include the message exchange of RSR, RRR, RAI for the above options for RoCN control, e.g., including one or more of: o Information such as sender’s data rate, latency, etc. identified in RSR o Information such as receiver’s data rate, latency, etc. identified in RRR o Information such as application observed QoS and requirements in RAI o
• o Information such as sender’s data rate, latency, etc. identified in RSR o Information
• receiver’s data rate, latency, etc. identified in RRR o Information such as application observed QoS and requirements in RAI o
• Example 5 may include the message exchange between xNB and RoCN end points to update the RoCN related information such as whether the RoCN control is based on UE ID, session ID or QP ID in addition to RSR, RRR, RAI.
• Example 6 may include the ANBR/ANBRQ extension for RoCN between UE and xNB.
• Example 7 may include the information identified for ANBR for RoCN extension in Figure 10 Step 2.
• Example 8 may include the information identified for ANBRQ for RoCN extension in Figure 11 Step 2.
• Example XI includes an apparatus of a user equipment (UE) comprising: memory to store remote direct memory access (RDMA) information; and processing circuitry, coupled with the memory, to: determine, based on the RDMA information, RDMA over cellular network (RoCN) control information that includes: an RoCN sender report (RSR) including transmission and reception statistics from a sender, an RoCN receiver report (RRR) including reception statistics from receivers, or RoCN application information (RAI) including application-specific information; and encode an RDMA data packet for transmission to a next-generation NodeB (gNB) that includes the RoCN control information.
• RSR RoCN sender report
• RRR RoCN receiver report
• RAI RoCN application information
• gNB next-generation NodeB
• Example X2 includes the apparatus of example XI or some other example herein, wherein the RDMA data packet includes an extended base transfer header (BTH) that includes an indication of a partition key associated with a network slice, a destination queue pair (QP), and a packet sequence number (PSN).
• BTH extended base transfer header
• QP destination queue pair
• PSN packet sequence number
• Example X3 includes the apparatus of example XI or some other example herein, wherein the extended BTH indicates a connection mode associated with the RSR, RRR, or RAI.
• Example X4 includes the apparatus of example XI or some other example herein, wherein the RSR, RRR, or RAI includes an indication of one or more statistics in an extended header (EH).
• EH extended header
• Example X5 includes the apparatus of example XI or some other example herein, wherein the RSR includes a sender’s parameter or statistic that includes an indication of: a QP identifier, an average sent data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• the RSR includes a sender’s parameter or statistic that includes an indication of: a QP identifier, an average sent data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• Example X6 includes the apparatus of example XI or some other example herein, wherein the RSR includes an initial configuration for a QP-related or non-QP related statistic or parameter expected to be received in an RRR packet.
• Example X7 includes the apparatus of example XI or some other example herein, wherein the RRR includes a receiver’s parameter or statistic that includes an indication of: a QP identifier, an average received data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• the RRR includes a receiver’s parameter or statistic that includes an indication of: a QP identifier, an average received data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• Example X8 includes the apparatus of any of examples XI -X7, wherein the applicationspecific information in the RAI includes an indication of: an application identifier, an application status, an application observed quality of service (QoS) configuration, or an application associated QP-related configuration.
• the applicationspecific information in the RAI includes an indication of: an application identifier, an application status, an application observed quality of service (QoS) configuration, or an application associated QP-related configuration.
• QoS quality of service
• Example X9 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: receive, from a user equipment (UE), a remote direct memory access (RDMA) data packet that includes RDMA over cellular network (RoCN) control information, wherein the RoCN control information includes: an RoCN sender report (RSR) including transmission and reception statistics from a sender, an RoCN receiver report (RRR) including reception statistics from receivers, or RoCN application information (RAI) including application-specific information; and receive, from an RoCN control function at a computing service function (Comp SF), an RoCN information update request that includes: a queue pair (QP) identifier, a UE identifier, or a session identifier.
• RSR RoCN sender report
• RRR RoCN receiver report
• RAI RoCN application information
• Comp SF computing service function
• an RoCN information update request that includes: a queue pair (QP) identifie
• Example XI 0 includes the one or more computer-readable media of example X9 or some other example herein, wherein the RDMA data packet includes an extended base transfer header (BTH) that includes an indication of a partition key associated with a network slice, a destination queue pair (QP), and a packet sequence number (PSN), and wherein the extended BTH indicates a connection mode associated with the RSR, RRR, or RAI.
• BTH extended base transfer header
• QP destination queue pair
• PSN packet sequence number
• Example XI 1 includes the one or more computer-readable media of example X9 or some other example herein, wherein the RSR, RRR, or RAI includes an indication of one or more statistics in an extended header (EH).
• EH extended header
• Example X12 includes the one or more computer-readable media of example X9 or some other example herein, wherein the RSR includes a sender’s parameter or statistic that includes an indication of: a QP identifier, an average sent data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• the RSR includes a sender’s parameter or statistic that includes an indication of: a QP identifier, an average sent data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• Example XI 3 includes the one or more computer-readable media of example X9 or some other example herein, wherein the RSR includes an initial configuration for a QP-related or non- QP related statistic or parameter expected to be received in an RRR packet.
• Example X14 includes the one or more computer-readable media of example X9 or some other example herein, wherein the RRR includes a receiver’s parameter or statistic that includes an indication of: a QP identifier, an average received data rate, a time interval, a range of transmission rate, a packet interval, a traffic type, a packet number, a time stamp, a number of retransmissions, or a transmission mode.
• Example XI 5 includes the one or more computer-readable media of any of examples X9- X14, wherein the application-specific information in the RAI includes an indication of: an application identifier, an application status, an application observed quality of service (QoS) configuration, or an application associated QP-related configuration.
• QoS application observed quality of service
• Example XI 6 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: determine a rate adjustment associated with remote direct memory access (RDMA) over cellular network (RoCN) traffic; and encode an access network bitrate recommendation (ANBR) message for transmission to a user equipment (UE) that includes an indication of the RoCN traffic rate adjustment.
• gNB next-generation NodeB
• RDMA remote direct memory access
• RoCN cellular network
• ANBR access network bitrate recommendation
• Example XI 7 includes the one or more computer-readable media of example XI 6 or some other example herein, wherein RoCN traffic rate adjustment is queue pair (QP)-specific.
• Example XI 8 includes the one or more computer-readable media of example XI 6 or some other example herein, wherein the ANBR message includes a QP identifier for the RoCN traffic, or a bearer identifier for multiple-QP traffic.
• Example XI 9 includes the one or more computer-readable media of example XI 6 or some other example herein, wherein the indication of the RoCN traffic rate adjustment in the ANBR message includes a value of a recommended data rate, or a factor or rate difference for a recommended data rate.
• Example X20 includes the one or more computer-readable media of example XI 6 or some other example herein, wherein the RoCN traffic rate adjustment is a first RoCN traffic rate adjustment, and wherein the media further stores instructions to cause the gNB to: receive, from the UE, an access network bitrate query (ANBRQ) message that includes a request for a second RoCN traffic rate adjustment.
• ANBRQ access network bitrate query
• Example X21 includes the one or more computer-readable media of example X20 or some other example herein, wherein the ANBRQ message includes an indication of a QP identifier for the RoCN traffic or a bearer identifier for multiple-QP traffic.
• Example X22 includes the one or more computer-readable media of example X20 or some other example herein, wherein the second RoCN traffic rate adjustment in the ANBRQ message the includes a value of a recommended data rate, or a factor or rate difference for a recommended data rate.
• Example X23 includes the one or more computer-readable media of any of examples X20-X22, wherein the ANBRQ message includes an indication of a rate adjustment rule for multiple QPs.
• Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X23, or any other method or process described herein.
• Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1- X23, or any other method or process described herein.
• Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X23, or any other method or process described herein.
• Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X23, or portions or parts thereof.
• Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X23, or portions thereof.
• Example Z06 may include a signal as described in or related to any of examples 1- X23, or portions or parts thereof.
• Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X23, or portions or parts thereof, or otherwise described in the present disclosure.
• PDU protocol data unit
• Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X23, or portions or parts thereof, or otherwise described in the present disclosure.
• Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X23, or portions or parts thereof, or otherwise described in the present disclosure.
• PDU protocol data unit
• Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X23, or portions thereof.
• Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X23, or portions thereof.
• Example Z12 may include a signal in a wireless network as shown and described herein.
• Example Z13 may include a method of communicating in a wireless network as shown and described herein.
• Example Z14 may include a system for providing wireless communication as shown and described herein.
• Example Z15 may include a device for providing wireless communication as shown and described herein.
• Enhancement CDM Content COTS Commercial C-RNTI Cell Delivery Network Off-The-Shelf RNTI CDMA Code- CP Control Plane, CS Circuit Division Multiple Cyclic Prefix, Switched Access 40 Connection 75 CSAR Cloud Service
• Gateway Function 45 Premise 80 Interference CHF Charging Equipment Measurement
• CID Cell-ID (e g., CQI Channel CSI-RSRP CSI positioning method) 50 Quality Indicator 85 reference signal CIM Common CPU CSI processing received power Information Model unit, Central CSI-RSRQ CSI CIR Carrier to Processing Unit reference signal Interference Ratio C/R received quality CK Cipher Key 55 Command/Resp 90 CSI-SINR CSI CM Connection onse field bit signal-to-noise and Management, CRAN Cloud Radio interference
• Conditional Access ratio Mandatory Network, Cloud CSMA Carrier Sense CMAS Commercial 60 RAN 95 Multiple Access Mobile Alert Service CRB Common CSMA/CA CSMA CMD Command Resource Block with collision CMS Cloud CRC Cyclic avoidance Management System Redundancy Check CSS Common CO Conditional 65 CRI Channel -State 100 Search Space, CellOptional Information specific Search CoMP Coordinated Resource Space Multi-Point Indicator, CSI-RS CTF Charging CORESET Control Resource Trigger Function Resource Set 70 Indicator 105 CTS Clear-to-Send CW Codeword 35 DSL Domain ECSP Edge
• EREG enhanced REG Associated Control Assisted enhanced resource 55 Channel/Half Access, further element groups rate 90 enhanced LAA ETSI European FACH Forward Access FN Frame Number
• GSM EDGE for Mobile Speed Downlink RAN
• GGSN Gateway GPRS GTP GPRS 75 HSPA High Speed Support Node Tunneling Protocol Packet Access GLONASS GTP-UGPRS HSS Home
• NodeB Number 95 IAB Integrated distributed unit HHO Hard Handover Access
• Ll-RSRP Layer 1 LWA LTE-WLAN Service reference signal aggregation MBSFN received power LWIP LTE/WLAN Multimedia
• N-PoP Network Point NR New Radio, Multiplexing of Presence Neighbour Relation OFDMA
• Narrowband MIB 55 Function Frequency Division
• Computer 40 PDU Protocol Data PRACH Physical PCC Primary Unit 75 RACH Component Carrier, PEI Permanent PRB Physical Primary CC Equipment resource block PCell Primary Cell Identifiers PRG Physical PCI Physical Cell 45 PFD Packet Flow resource block ID, Physical Cell Description 80 group Identity P-GW PDN Gateway ProSe Proximity
• PDCCH Physical PNFD Physical PSCCH Physical Downlink Control Network Function Sidelink Control
• PDCP Packet Data 65 PNFR Physical PSSCH Physical Convergence Protocol Network Function 100 Sidelink Shared
• Subscriber 65 Information 100 Subscriber Identity
• TPC Transmit Power UDP User Datagram Control 70 Protocol UTRA UMTS 35 VoIP Voice-over-IP,
• VL Virtual Link 55 WPANWireless VLAN Virtual LAN, Personal Area Network Virtual Local Area X2-C X2-Control Network plane
• VNFMVNF Manager For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.
• circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
• FPD field-programmable device
• FPGA field-programmable gate array
• PLD programmable logic device
• CPLD complex PLD
• HPLD high-capacity PLD
• DSPs digital signal processors
• the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
• the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
• processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
• Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
• processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes.
• Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
• the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
• CV computer vision
• DL deep learning
• application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
• interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
• interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
• user equipment or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
• user equipment or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
• user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
• network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
• network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
• computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
• appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
• program code e.g., software or firmware
• a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
• resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
• a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
• a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
• network resource or “communication resource” may refer to resources that are accessible by computer devices/ systems via a communications network.
• system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
• channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
• channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
• link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
• instantiate refers to the creation of an instance.
• An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
• Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
• directly coupled may mean that two or more elements are in direct contact with one another.
• communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
• information element refers to a structural element containing one or more fields.
• field refers to individual contents of an information element, or a data element that contains content.
• SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .
• SSB refers to an SS/PBCH block.
• Primary Cell refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
• Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
• Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
• Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
• Secondary Cell refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
• serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.
• Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

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

Priority Applications (1)

Applications Claiming Priority (2)

Publications (1)

Family

ID=82742559

Family Applications (2)

Family Applications After (1)

Country Status (2)

Families Citing this family (1)

Citations (4)

Family Cites Families (3)

• 2022
  • 2022-02-07 WO PCT/US2022/015530 patent/WO2022170214A1/en active Application Filing
  • 2022-02-07 KR KR1020237030802A patent/KR20230153401A/ko unknown
  • 2022-02-07 WO PCT/US2022/015528 patent/WO2022170213A1/en active Application Filing

Patent Citations (4)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events