WO2020190965A1 - Conception de signalisation pour un équipement d'utilisateur fonctionnant dans un spectre sans licence - Google Patents

Conception de signalisation pour un équipement d'utilisateur fonctionnant dans un spectre sans licence Download PDF

Info

Publication number
WO2020190965A1
WO2020190965A1 PCT/US2020/023197 US2020023197W WO2020190965A1 WO 2020190965 A1 WO2020190965 A1 WO 2020190965A1 US 2020023197 W US2020023197 W US 2020023197W WO 2020190965 A1 WO2020190965 A1 WO 2020190965A1
Authority
WO
WIPO (PCT)
Prior art keywords
mode
information
determining
circuitry
regional
Prior art date
Application number
PCT/US2020/023197
Other languages
English (en)
Inventor
Salvatore TALARICO
Wenting CHANG
Huaning Niu
Anthony Lee
Original Assignee
Apple Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc. filed Critical Apple Inc.
Publication of WO2020190965A1 publication Critical patent/WO2020190965A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • 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/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • UE User equipment
  • RAN radio access network
  • the present disclosure is directed towards methods, systems, apparatus, computer programs, or combinations thereof, for selecting a mode of operation for a user equipment (UE) that operates within an unlicensed spectrum (e.g., the unlicensed 5 Gigahertz (GHz) frequency band).
  • UE user equipment
  • an unlicensed spectrum e.g., the unlicensed 5 Gigahertz (GHz) frequency band.
  • aspects of the subject matter described in this specification may be embodied in methods that include the actions of: identifying information from which to determine the mode of operation, where the UE is served by a radio access network (RAN) operating in an unlicensed radio frequency spectrum band; determining, based on the information, an indication of regional mode or global mode; and operating in the determined mode of operation.
  • RAN radio access network
  • the previously-described implementation is implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.
  • a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium.
  • the information is the UE’s International Mobile Equipment Identity (IMEI) or country code
  • determining, based on the information, an indication of regional mode or global mode includes: determining, based on the UE’s International Mobile Equipment Identity (IMEI) or country code, geographic information indicative of a current region of the UE; determining operational requirements of the current region; and determining, based on the operational requirements of the current region, the mode of operation.
  • IMEI International Mobile Equipment Identity
  • identifying information from which to determine the mode of operation includes: identifying the information as a field in a received System Information Block Type1 (SIB1).
  • SIB1 System Information Block Type1
  • plmn-IdentityList or trackingAreaCode where the field is plmn-IdentityList or trackingAreaCode, where plmn-IdentityList is indicative of a current UE location or a current UE location area code, where trackingAreaCode is indicative of operator tracking area codes, and where determining, based on the information, an indication of regional mode or global mode includes: using a lookup table that indicates a respective mode of operation that corresponds to each value of plmn-IdentityList or trackingAreaCode to determine the mode of operation that corresponds to values of plmn-IdentityList or trackingAreaCode.
  • ModeOfOperation is a field that is added to legacy SIB1
  • ModeOfOperation field has two enumerated values ⁇ Global, Regional ⁇
  • determining, based on the information, an indication of regional mode or global mode includes: determining, based on the ModeOfOperation field, the mode of operation.
  • the field is an existing field of legacy SIB1 that is reinterpreted to indicate the mode of operation.
  • the information is a physical central frequency of the unlicensed spectrum, where each mode of operation is associated with a respective physical central frequency, and where determining, based on the information, an indication of regional mode or global mode includes: determining the mode of operation that corresponds to the physical central frequency of the unlicensed spectrum.
  • the information is a configuration of a physical random access channel (PRACH), and where determining, based on the information, an indication of regional mode or global mode includes: determining whether the configuration is a legacy configuration; if the PRACH is configured with a legacy configuration, determining to operate in regional mode; and if a new PRACH is used, determining to operate in global mode.
  • PRACH physical random access channel
  • Figure 1 is a contextual diagram of an example of a system, according to some implementations of the present disclosure.
  • Figure 2 is a block diagram of a method, according to some implementations of the present disclosure.
  • Figure 3 is an example architecture of a system of a network, according to some implementations of the present disclosure.
  • Figure 4 is a block diagram of an example of infrastructure equipment, according to some implementations of the present disclosure.
  • Figure 5 is a block diagram of an example of platform, according to some implementations of the present disclosure.
  • FIG. 6 is a block diagram of an example of components of baseband circuitry and radio front end modules (RFEM), according to some implementations of the present disclosure.
  • RFEM radio front end modules
  • Figure 7 is a block diagram of various protocol functions that may be implemented in a wireless communication device, according to some implementations of the present disclosure.
  • Figure 8 is a block diagram of illustrating components 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 described herein, according to some implementations of the present disclosure.
  • a machine-readable or computer-readable medium e.g., a non- transitory machine-readable storage medium
  • the present disclosure is directed to methods, systems, apparatus, computer programs, or combinations thereof, for configuring a UE to operate within an unlicensed spectrum (e.g., the unlicensed 5 Gigahertz (GHz) frequency band).
  • the UE may be configured to operate within a cellular network that is configured to operate in the unlicensed spectrum.
  • This cellular network may generally be referred to as an unlicensed network.
  • the unlicensed spectrum may include radio frequencies that are not exclusively designated for the cellular network.
  • other wireless communication systems which may operate under different standards than the cellular network, may also operate in the unlicensed spectrum. Examples of such wireless communication systems include Institute of Electronic and Electrical Engineers (IEEE) 802.11 standards (e.g.,“Wi-Fi”) and the third generation partnership (3GPP) standard.
  • IEEE Institute of Electronic and Electrical Engineers
  • 3GPP third generation partnership
  • LTE-U Long-Term Evolution Time-Division Duplex
  • LAA license assisted access
  • MF Multefire
  • LTE-U and LAA use carrier aggregation or dual connectivity (DC) to operate using both the licensed and the unlicensed spectrum.
  • Multefire 1.0 may operate as a standalone system that operates solely in the unlicensed spectrum.
  • Multefire 1.0 does not require an anchor in the licensed spectrum. More recently, a new generation of Multefire is being developed, and is generally referred to as Multefire 1.1 or MF-Lite. Although this disclosure generally describes embodiments in the context of Multefire and/or MF-Lite, the disclosed embodiments are not limited to Multefire and may be applicable to other technologies.
  • some unlicensed networks use a frame based equipment (FBE) framework, which uses a Time- Division Duplex-LTE (TDD-LTE) frame structure. While this framework generally simplifies design requirements, networks must still comply with essential requirements provided with the Radio Equipment Directive (RED) and/or with harmonized standard requirements (e.g., European Telecommunications Standards Institute (ETSI)).
  • RED Radio Equipment Directive
  • ETSI European Telecommunications Standards Institute
  • harmonized standard requirements specify that a UE must use listen-before- talk (LBT) functionality if there is a gap longer than 16 microseconds between the end of downlink (DL) transmission and the start of a new uplink (UL) transmission.
  • LBT listen-before- talk
  • an unlicensed network has to comply with the occupied channel bandwidth (OCB) requirements mandated by ETSI broadband radio access networks (BRAN). These requirements specify that at least a 2MHz bandwidth must be occupied.
  • OCB occupied channel bandwidth
  • BRAN ETSI broadband radio access networks
  • OCB occupied channel bandwidth
  • an unlicensed network e.g., MF-Lite
  • global mode the essential requirements provided by the RED or regional requirements (that is, requirements imposed by an operator) must be met.
  • the harmonized standard requirements or global requirements that is, requirements imposed by a global standards organization
  • a UE Given that there are two modes of operation, disclosed are methods and systems for a UE to, explicitly or implicitly, determine the modality in which it should operate. Specifically, the disclosure describes UE determining and/or signaling the UE mode of operation.
  • FIG. 1 is a contextual diagram of an example of a system 100, according to some embodiments.
  • the system 100 includes UE 105, a first RAN 110 including one or more access nodes 110-1, 110-2, 110-x, where x is any non-zero integer, a core network 130 including one or more core network elements 132, a second RAN 120 including one or more access nodes 120-1, 120-2, 120-n, where n is any non-zero integer, and an IP network 140 such as the Internet.
  • a first RAN 110 including one or more access nodes 110-1, 110-2, 110-x, where x is any non-zero integer
  • a core network 130 including one or more core network elements 132
  • a second RAN 120 including one or more access nodes 120-1, 120-2, 120-n, where n is any non-zero integer
  • an IP network 140 such as the Internet.
  • the first RAN 110 may use a frequency in licensed spectrum.
  • licensed spectrum can include spectrum used by Long-Term Evolution (LTE) networks such as 400 MHz to 2.3 GHz, licensed spectrum used by 5G networks such as 28 GHz to 39 GHz, or the like.
  • LTE Long-Term Evolution
  • 5G 5G networks
  • Each of the access nodes 110-1, 110-2, 110-x can include a base station such as a E-UTRAN Node B (eNB) that functions as a point of access for packet switched data being communicated to the core network 130.
  • the eNB can function as a point of access for packet switched data being communicated to the IP network 140.
  • the first RAN can have a coverage area 112.
  • the second RAN 120 may use a frequency in the unlicensed spectrum.
  • the unlicensed spectrum can include spectrum used by a MulteFire network, a MulteFire Lite network, a Wi-Fi network, or the like.
  • the unlicensed spectrum can include, for example, spectrum in the 2.4 GHz band or the 5 GHz band.
  • Each of the access nodes 120-1, 120-2, 120-z can include an access point (AP) for the unlicensed spectrum.
  • the AP can play the role of an eNB for the unlicensed spectrum and generally function like an eNB.
  • each AP can be a point of access for packet switched data being communicated to the core network 130, a different core network (not shown), or IP network 140.
  • each AP in the second RAN 120 can include a MulteFire AP.
  • the second RAN 120 may have a coverage area 122 that falls within the coverage area of the first RAN 110.
  • the UE 105 may be designed or manufactured to operate in a particular mode of operation. Because unlicensed systems are designed to operate in a contained environment, the UE 105 may be imposed by its manufacturer to operate in a certain mode of operation. Thus, in this scenario, the design of the UE 105 may decouple the operating modes.
  • the UE 105 may be configured to determine the mode of operation based on information extracted from its own International Mobile Equipment Identity (IMEI) or country code.
  • the extracted information may be geographic information that indicates to the UE 105 its current location.
  • the geographic information may indicate to the UE 105 the operational requirements of the region in which the UE 105 is located.
  • the UE 105 may determine its mode of operation.
  • the UE 105 may be configured to extract information from SIB1.
  • the information may be extracted from the field plmn- IdentityList or from the field trackingAreaCode.
  • plmn-IdentityList is indicative of a current UE location or a current UE location area code.
  • Plmn-identityList includes two fields: Mobile Country Code (MCC) and Mobile Network Code (MNC).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • trackingAreaCode is used to indicate the operator tracking area codes.
  • the UE 105 may identify the mode of operation based on a lookup table that indicates the respective mode that corresponds to each value of plmn-IdentityList and/or trackingAreaCode. Specifically, the UE 105 may determine the operating mode that corresponds to its value of plmn-IdentityList and/or trackingAreaCode.
  • the PLMN may be private.
  • the UE 105 may need an additional and/or alternative method of determining its mode of operation.
  • a field indication may be added in SIB1 or SIBx to provide explicit indication of the mode of operation.
  • a field ModeOfOperation may be added in SIB1 or SIBx.
  • this field may have one of two enumerated values ⁇ Global, Regional ⁇ .
  • the carrier, manufacturer, or other entity may specify the mode of operation by selecting one of the two enumerated values.
  • the field ModeOfOperation may be a Boolean field.
  • a specific Boolean operator may be indicative of global mode, while another Boolean operator may be indicative of regional mode. For instance,“true” can be designated to indicate either regional mode or global mode.
  • an existing field of legacy SIB1 may be reinterpreted to provide indication of the mode of operation.
  • the field csg-Identity which is a one bit field, may be reinterpreted to carry information related to the mode of operation.
  • a first value may be indicative of global mode and a second value may be indicative of regional mode.
  • “0” may be designated as indicative of regional mode
  • “1” may be designated as indicative of global mode, or vice versa.
  • the field csg-Indication which is a Boolean field, may be reinterpreted to carry information related to the mode of operation.
  • the Boolean operator“true” may be designated to indicate regional mode and the Boolean operator“false” may be designated to indicate global mode, or vice versa.
  • the information related to the mode of operation may be included in the SIBx, either by adding a new field or by reinterpreting an existing field (e.g., a mandatory or optional field).
  • information indicative of the mode of operation may be included in SIB2.
  • a one bit indicator to determine the mode of operation may be added within the informational element (IE) RadioResourceConfigCommon.
  • one of the existing fields in SIB2 e.g., a field within the IE RadioResourceConfigCommon
  • one of the spare bits of the Master Information Block may be reinterpreted to indicate the mode of operation.
  • a first value of the bit may be indicative of global mode and a second value of the bit may be indicative of regional mode. For instance,“0” may be designated as indicative of regional mode and“1” may be designated as indicative of global mode, or vice versa.
  • the UE 105 may determine the mode of operation based on a physical central frequency.
  • each mode of operation may be associated with a respective physical central frequency.
  • the UE 105 may determine the central frequency, and may, in turn, determine the mode of operation based on the determined central frequency.
  • the UE 105 may determine the mode of operation based on PRACH configuration.
  • the UE 105 may first analyze the PRACH configuration to determine whether the configuration is a legacy configuration. If the PRACH is configured with a legacy configuration, then the UE 105 may determine to operate in regional mode. Alternatively, if a new IE PRACH is used and configured, then the UE 105 may determine to operate in global mode.
  • At least one of the components set forth in one or more of the disclosed 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 figures may be configured to operate in accordance with one or more of the processes set forth below.
  • circuitry associated with a UE, base station, network element, etc., as described above in connection with the preceding figure may be configured to operate in accordance with one or more of the examples set forth below.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or embodiments thereof, of Figures 3-8, or some other figure herein can be configured to perform one or more processes, techniques, or methods as described above with respect to Figure 1.
  • FIG. 2 is a flowchart of an example of a process 200 for determining a mode of operation for a UE.
  • process 200 can be performed by UE 105 shown in Figure 1.
  • the processes may be performed, for example, by any suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware, as appropriate.
  • various steps of the processes can be run in parallel, in combination, in loops, or in any order.
  • the process involves identifying information from which to determine the mode of operation, wherein the UE is served by a radio access network (RAN) operating in an unlicensed radio frequency spectrum band.
  • the process involves determining, based on the information, an indication of regional mode or global mode.
  • the process involves operating in the determined mode of operation.
  • the process may involve determining the mode of operation based on information extracted from the UE’s own International Mobile Equipment Identity (IMEI) or country code.
  • IMEI International Mobile Equipment Identity
  • the extracted information may be geographic information that indicates to the UE its current location. The geographic information may indicate to the UE the operational requirements of the region in which the UE is located. Thus, based on the geographic information, the UE may determine its mode of operation.
  • the process may involve extracting information from SIB1.
  • the information may be extracted from the field plmn- IdentityList or from the field trackingAreaCode.
  • plmn-IdentityList is indicative of a current UE location or a current UE location area code.
  • Plmn-IdentityList includes two fields: Mobile Country Code (MCC) and Mobile Network Code (MNC).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • trackingAreaCode is used to indicate the operator tracking area codes.
  • the UE may identify the mode of operation based on a lookup table that indicates the respective mode that corresponds to each value of plmn-IdentityList and/or trackingAreaCode. Specifically, the UE may determine the operating mode that corresponds to its value of plmn-IdentityList and/or trackingAreaCode.
  • the process may involve determining a field indication that is added in SIB1 or SIBx to provide explicit indication of the mode of operation.
  • a field ModeOfOperation may be added in SIB1 or SIBx.
  • this field may have one of two enumerated values ⁇ Global, Regional ⁇ .
  • the carrier, manufacturer, or other entity may specify the mode of operation by selecting one of the two enumerated values.
  • the field ModeOfOperation may be a Boolean field.
  • a specific Boolean operator may be indicative of global mode, while another Boolean operator may be indicative of regional mode. For instance,“true” can be designated to indicate either regional mode or global mode.
  • the process may involve determining an existing field of legacy SIB1.
  • the legacy field may have been reinterpreted to provide indication of the mode of operation.
  • the field csg-Identity which is a one bit field, may be reinterpreted to carry information related to the mode of operation.
  • a first value may be indicative of global mode and a second value may be indicative of regional mode.
  • “0” may be designated as indicative of regional mode
  • “1” may be designated as indicative of global mode, or vice versa.
  • the field csg-Indication which is a Boolean field, may be reinterpreted to carry information related to the mode of operation.
  • the Boolean operator“true” may be designated to indicate regional mode and the Boolean operator“false” may be designated to indicate global mode, or vice versa.
  • the process may involve determining the information related to the mode of operation found in SIBx.
  • the information may be included in the SIBx either by adding a new field or by reinterpreting an existing field (e.g., a mandatory or optional field).
  • information indicative of the mode of operation may be included in SIB2.
  • a one bit indicator to determine the mode of operation may be added within the informational element (IE) RadioResourceConfigCommon.
  • one of the existing fields in SIB2 (e.g., a field within the IE RadioResourceConfigCommon) may be reused as the indicator.
  • one of the spare bits of the Master Information Block may be reinterpreted to indicate the mode of operation.
  • a first value of the bit may be indicative of global mode and a second value of the bit may be indicative of regional mode. For instance,“0” may be designated as indicative of regional mode and“1” may be designated as indicative of global mode, or vice versa.
  • the process may involve determining the mode of operation based on a physical central frequency.
  • each mode of operation may be associated with a respective physical central frequency.
  • the UE may determine the central frequency, and may, in turn, determine the mode of operation based on the determined central frequency.
  • the process may involve determining the mode of operation based on PRACH configuration.
  • the UE may first analyze the PRACH configuration to determine whether the configuration is a legacy configuration. If the PRACH is configured with a legacy configuration, then the UE may determine to operate in regional mode. Alternatively, if a new IE PRACH is used and configured, then the UE may determine to operate in global mode.
  • Figure 3 illustrates an example architecture of a system 300 of a network, in accordance with various embodiments. The following description is provided for an example system 300 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications.
  • 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 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.
  • future 3GPP systems e.g., Sixth Generation (6G)
  • 6G Sixth Generation
  • IEEE 802.16 protocols e.g., WMAN, WiMAX, etc.
  • the system 300 includes UE 301a and UE 301b (collectively referred to as“UEs 301” or“UE 301”).
  • UEs 301 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 consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or“smar
  • any of the UEs 301 may be IoT UEs, which may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D communication, sensor networks, or IoT networks.
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, 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 UEs 301 may be configured to connect, for example, communicatively couple, with a RAN 310.
  • the RAN 310 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN.
  • the term“NG RAN” or the like may refer to a RAN 310 that operates in an NR or 5G system 300
  • the term“E-UTRAN” or the like may refer to a RAN 310 that operates in an LTE or 4G system 300.
  • the UEs 301 utilize connections (or channels) 303 and 304, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).
  • connections 303 and 304 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein.
  • the UEs 301 may directly exchange communication data via a ProSe interface 305.
  • the ProSe interface 305 may alternatively be referred to as a SL interface 305 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.
  • the UE 301b is shown to be configured to access an AP 306 (also referred to as“WLAN node 306,”“WLAN 306,”“WLAN Termination 306,”“WT 306” or the like) via connection 307.
  • the connection 307 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 306 would comprise a wireless fidelity (Wi-Fi®) router.
  • the AP 306 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the UE 301b, RAN 310, and AP 306 may be configured to utilize LWA operation and/or LWIP operation.
  • the LWA operation may involve the UE 301b in RRC_CONNECTED being configured by a RAN node 311a-b to utilize radio resources of LTE and WLAN.
  • LWIP operation may involve the UE 301b using WLAN radio resources (e.g., connection 307) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 307.
  • IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
  • the RAN 310 can include one or more AN nodes or RAN nodes 311a and 311b (collectively referred to as“RAN nodes 311” or“RAN node 311”) that enable the connections 303 and 304.
  • “RAN nodes 311” or“RAN node 311” collectively referred to as“RAN nodes 311” or“RAN node 311”
  • the terms“access node,”“access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users.
  • BS gNode B
  • RSU eNode B
  • TRxP TRxP
  • TRP TRP
  • NG RAN node may refer to a RAN node 311 that operates in an NR or 5G system 300 (for example, a gNB)
  • E-UTRAN node may refer to a RAN node 311 that operates in an LTE or 4G system 300 (e.g., an eNB).
  • the RAN nodes 311 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • LP low power
  • all or parts of the RAN nodes 311 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP).
  • a CRAN and/or a virtual baseband unit pool (vBBUP).
  • vBBUP virtual baseband unit pool
  • the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 311; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 311; or a“lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 311.
  • a RAN function split such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 311
  • a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the C
  • an individual RAN node 311 may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by Figure 3).
  • the gNB-DUs may include one or more remote radio heads or RFEMs (see, e.g., Figure 4), and the gNB-CU may be operated by a server that is located in the RAN 310 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP.
  • one or more of the RAN nodes 311 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 301, and are connected to a 5GC (e.g., CN) via an NG interface (discussed infra).
  • ng-eNBs next generation eNBs
  • 5GC e.g., CN
  • NG interface discussed infra
  • RSU Radio Access Side Unit
  • An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a“UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an“eNB-type RSU,” an RSU implemented in or by 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 301 (vUEs 301).
  • 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 operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to 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 operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services.
  • DSRC Direct Short Range Communications
  • the RSU may operate as a Wi- Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications.
  • the computing device(s) and some or all of the radiofrequency circuitry 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 and/or a backhaul network.
  • Any of the RAN nodes 311 can terminate the air interface protocol and can be the first point of contact for the UEs 301.
  • any of the RAN nodes 311 can fulfill various logical functions for the RAN 310 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 UEs 301 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 311 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 311 to the UEs 301, 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.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid 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.
  • the UEs 301 and the RAN nodes 311 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the“licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to as the“unlicensed spectrum” and/or the“unlicensed band”).
  • the licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.
  • the UEs 301 and the RAN nodes 311 may operate using LAA, eLAA, and/or feLAA mechanisms.
  • the UEs 301 and the RAN nodes 311 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
  • the medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • LBT is a mechanism whereby equipment (for example, UEs 301 RAN nodes 311, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied).
  • the medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
  • CCA which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
  • This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks.
  • ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.
  • the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies.
  • WLAN employs a contention-based channel access mechanism, called CSMA/CA.
  • CSMA/CA contention-based channel access mechanism
  • a WLAN node e.g., a mobile station (MS) such as UE 301, AP 306, or the like
  • the WLAN node may first perform CCA before transmission.
  • a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time.
  • the backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds.
  • the LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN.
  • the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA.
  • the minimum CWS for an LAA transmission may be 9 microseconds; however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.
  • each aggregated carrier is referred to as a CC.
  • a CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz.
  • the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers.
  • individual CCs can have a different bandwidth than other CCs.
  • the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.
  • CA also comprises individual serving cells to provide individual CCs.
  • the coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss.
  • a primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities.
  • the other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL.
  • the SCCs may be added and removed as required, while changing the PCC may require the UE 301 to undergo a handover.
  • LAA SCells may operate in the unlicensed spectrum (referred to as“LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum.
  • LAA SCells When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.
  • the PDSCH carries user data and higher-layer signaling to the UEs 301.
  • the PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 301 about the transport format, resource allocation, and HARQ information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 301b within a cell) may be performed at any of the RAN nodes 311 based on channel quality information fed back from any of the UEs 301.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 301.
  • the PDCCH uses CCEs to convey the control information. Before being mapped to resource 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 REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG.
  • QPSK Quadrature Phase Shift Keying
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
  • the RAN nodes 311 may be configured to communicate with one another via interface 312.
  • the interface 312 may be an X2 interface 312.
  • the X2 interface may be defined between two or more RAN nodes 311 (e.g., two or more eNBs and the like) that connect to EPC 320, and/or between two eNBs connecting to EPC 320.
  • the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C).
  • the X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs.
  • the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 301 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 301; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like.
  • the X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.
  • the interface 312 may be an Xn interface 312.
  • the Xn interface is defined between two or more RAN nodes 311 (e.g., two or more gNBs and the like) that connect to 5GC 320, between a RAN node 311 (e.g., a gNB) connecting to 5GC 320 and an eNB, and/or between two eNBs connecting to 5GC 320.
  • 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 301 in a connected mode (e.g., CM- CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 311.
  • the mobility support may include context transfer from an old (source) serving RAN node 311 to new (target) serving RAN node 311; and control of user plane tunnels between old (source) serving RAN node 311 to new (target) serving RAN node 311.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs.
  • 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 SCTP.
  • the SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages.
  • point-to-point transmission is used to deliver the signaling PDUs.
  • the Xn-U 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.
  • the RAN 310 is shown to be communicatively coupled to a core network-in this embodiment, core network (CN) 320.
  • the CN 320 may comprise a plurality of network elements 322, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 301) who are connected to the CN 320 via the RAN 310.
  • the components of the CN 320 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).
  • NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below).
  • a logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • the application server 330 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.).
  • the application server 330 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 301 via the EPC 320.
  • communication services e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.
  • the CN 320 may be a 5GC (referred to as“5GC 320” or the like), and the RAN 310 may be connected with the CN 320 via an NG interface 313.
  • the NG interface 313 may be split into two parts, an NG user plane (NG- U) interface 314, which carries traffic data between the RAN nodes 311 and a UPF, and the S1 control plane (NG-C) interface 315, which is a signaling interface between the RAN nodes 311 and AMFs.
  • NG- U NG user plane
  • N-C S1 control plane
  • the CN 320 may be a 5G CN (referred to as“5GC 320” or the like), while in other embodiments, the CN 320 may be an EPC).
  • the RAN 310 may be connected with the CN 320 via an S1 interface 313.
  • the S1 interface 313 may be split into two parts, an S1 user plane (S1-U) interface 314, which carries traffic data between the RAN nodes 311 and the S-GW, and the S1-MME interface 315, which is a signaling interface between the RAN nodes 311 and MMEs.
  • S1-U S1 user plane
  • FIG. 4 illustrates an example of infrastructure equipment 400 in accordance with various embodiments.
  • the infrastructure equipment 400 (or“system 400”) may be implemented as a base station, radio head, RAN node such as the RAN nodes 311 and/or AP 306 shown and described previously, application server(s) 330, and/or any other element/device discussed herein.
  • the system 400 could be implemented in or by a UE.
  • the system 400 includes application circuitry 405, baseband circuitry 410, one or more radio front end modules (RFEMs) 415, memory circuitry 420, power management integrated circuitry (PMIC) 425, power tee circuitry 430, network controller circuitry 435, network interface connector 440, satellite positioning circuitry 445, and user interface 450.
  • the device 400 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. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.
  • Application circuitry 405 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • LDOs low drop-out voltage regulators
  • interrupt controllers serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or
  • the processors (or cores) of the application circuitry 405 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 400.
  • the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
  • the processor(s) of application circuitry 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof.
  • the application circuitry 405 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
  • the processor(s) of application circuitry 405 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium(TM), Inc.; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior P-class processors; and/or the like.
  • the system 400 may not utilize application circuitry 405, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.
  • the application circuitry 405 may include one or 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.
  • the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • ASICs such as structured ASICs and the like
  • PSoCs programmable SoCs
  • the circuitry of application circuitry 405 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry 405 may include memory cells (e.g., erasable programmable read- only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.
  • memory cells e.g., erasable programmable read- only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)
  • SRAM static random access memory
  • LUTs look-up-tables
  • the baseband circuitry 410 may be implemented, for example, as a solder- down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • the various hardware electronic elements of baseband circuitry 410 are discussed infra with regard to Figure 6.
  • User interface circuitry 450 may include one or more user interfaces designed to enable user interaction with the system 400 or peripheral component interfaces designed to enable peripheral component interaction with the system 400.
  • User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc.
  • Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.
  • USB universal serial bus
  • the radio front end modules (RFEMs) 415 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs).
  • the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 611 of Figure 6 infra), and the RFEM may be connected to multiple antennas.
  • both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 415, which incorporates both mmWave antennas and sub-mmWave.
  • the memory circuitry 420 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high- speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • Memory circuitry 420 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.
  • the PMIC 425 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor.
  • the power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions.
  • the power tee circuitry 430 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 400 using a single cable.
  • the network controller circuitry 435 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol.
  • Network connectivity may be provided to/from the infrastructure equipment 400 via network interface connector 440 using a physical connection, which may be electrical (commonly referred to as a“copper interconnect”), optical, or wireless.
  • the network controller circuitry 435 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 435 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
  • the positioning circuitry 445 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS).
  • GNSS global navigation satellite system
  • Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like.
  • GPS Global Positioning System
  • GLONASS Global Navigation System
  • Galileo system China's BeiDou Navigation Satellite System
  • a regional navigation system or GNSS augmentation system e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zeni
  • the positioning circuitry 445 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.
  • the positioning circuitry 445 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • the positioning circuitry 445 may also be part of, or interact with, the baseband circuitry 410 and/or RFEMs 415 to communicate with the nodes and components of the positioning network.
  • the positioning circuitry 445 may also provide position data and/or time data to the application circuitry 405, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes 311, etc.), or the like.
  • interface circuitry may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies.
  • IX interconnect
  • ISA industry standard architecture
  • EISA extended ISA
  • PCI peripheral component interconnect
  • PCIx peripheral component interconnect extended
  • PCIe PCI express
  • the bus/IX may be a proprietary bus, for example, used in a SoC based system.
  • Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.
  • FIG. 5 illustrates an example of a platform 500 (or“device 500”) in accordance with various embodiments.
  • the computer platform 500 may be suitable for use as UEs 301, application servers 330, and/or any other element/device discussed herein.
  • the platform 500 may include any combinations of the components shown in the example.
  • the components of platform 500 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 500, or as components otherwise incorporated within a chassis of a larger system.
  • the block diagram of Figure 5 is intended to show a high level view of components of the computer platform 500. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
  • Application circuitry 505 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports.
  • the processors (or cores) of the application circuitry 505 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 500.
  • the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
  • any suitable volatile and/or non-volatile memory such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.
  • the processor(s) of application circuitry 405 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof.
  • the application circuitry 405 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.
  • the processor(s) of application circuitry 505 may include an Intel® Architecture CoreTM based processor, such as a QuarkTM, an AtomTM, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, CA.
  • the processors of the application circuitry 505 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., QualcommTM processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)TM processor(s); a MIPS-based design from MIPS Technologies, Inc.
  • AMD Advanced Micro Devices
  • APUs Accelerated Processing Units
  • A5-A9 processor(s) from Apple® Inc.
  • SnapdragonTM processor(s) from Qualcomm® Technologies, Inc. Texas Instruments, Inc.
  • OMAP Open Multimedia Applications Platform
  • the application circuitry 505 may be a part of a system on a chip (SoC) in which the application circuitry 505 and other components are formed into a single integrated circuit, or a single package, such as the EdisonTM or GalileoTM SoC boards from Intel® Corporation.
  • SoC system on a chip
  • application circuitry 505 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.
  • FPDs field-programmable devices
  • PLDs programmable logic devices
  • CPLDs complex PLDs
  • HPLDs high-capacity PLDs
  • PSoCs programmable SoCs
  • the circuitry of application circuitry 505 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein.
  • the circuitry of application circuitry 505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.
  • memory cells e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)
  • SRAM static random access memory
  • LUTs look-up tables
  • the baseband circuitry 510 may be implemented, for example, as a solder- down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.
  • the various hardware electronic elements of baseband circuitry 510 are discussed infra with regard to Figure 6.
  • the RFEMs 515 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs).
  • the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM.
  • the RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 611 of Figure 6 infra), and the RFEM may be connected to multiple antennas.
  • both mmWave and sub- mmWave radio functions may be implemented in the same physical RFEM 515, which incorporates both mmWave antennas and sub-mmWave.
  • the memory circuitry 520 may include any number and type of memory devices used to provide for a given amount of system memory.
  • the memory circuitry 520 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc.
  • RAM random access memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • NVM nonvolatile memory
  • Flash memory high-speed electrically erasable memory
  • PRAM phase change random access memory
  • MRAM magnetoresistive random access memory
  • the memory circuitry 520 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like.
  • JEDEC Joint Electron Device
  • Memory circuitry 520 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA).
  • the memory circuitry 520 may be on-die memory or registers associated with the application circuitry 505.
  • memory circuitry 520 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others.
  • SSDD solid state disk drive
  • HDD hard disk drive
  • micro HDD micro HDD
  • resistance change memories phase change memories
  • holographic memories holographic memories
  • chemical memories among others.
  • the computer platform 500 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • the memory circuitry 523 may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 500. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.
  • flash memory cards e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like
  • USB flash drives e.g., USB flash drives, optical discs, external HDDs, and the like.
  • the platform 500 may also include interface circuitry (not shown) that is used to connect external devices with the platform 500.
  • the external devices connected to the platform 500 via the interface circuitry include sensor circuitry 521 and electro- mechanical components (EMCs) 522, as well as removable memory devices coupled to removable memory circuitry 523.
  • EMCs electro- mechanical components
  • the sensor circuitry 521 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc.
  • sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio
  • EMCs 522 include devices, modules, or subsystems whose purpose is to enable platform 500 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 522 may be configured to generate and send messages/signalling to other components of the platform 500 to indicate a current state of the EMCs 522.
  • EMCs 522 examples include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components.
  • platform 500 is configured to operate one or more EMCs 522 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.
  • the interface circuitry may connect the platform 500 with positioning circuitry 845.
  • the positioning circuitry 845 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS.
  • GNSS navigation satellite constellations
  • Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like.
  • the positioning circuitry 845 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes.
  • the positioning circuitry 845 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance.
  • the positioning circuitry 845 may also be part of, or interact with, the baseband circuitry 410 and/or RFEMs 515 to communicate with the nodes and components of the positioning network.
  • the positioning circuitry 845 may also provide position data and/or time data to the application circuitry 505, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like
  • the interface circuitry may connect the platform 500 with Near-Field Communication (NFC) circuitry 840.
  • NFC circuitry 840 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 840 and NFC-enabled devices external to the platform 500 (e.g., an“NFC touchpoint”).
  • RFID radio frequency identification
  • NFC circuitry 840 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller.
  • the NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 840 by executing NFC controller firmware and an NFC stack.
  • the NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals.
  • the RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 840, or initiate data transfer between the NFC circuitry 840 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 500.
  • a passive NFC tag e.g., a microchip embedded in a sticker or wristband
  • another active NFC device e.g., a smartphone or an NFC-enabled POS terminal
  • the driver circuitry 846 may include software and hardware elements that operate to control particular devices that are embedded in the platform 500, attached to the platform 500, or otherwise communicatively coupled with the platform 500.
  • the driver circuitry 846 may include individual drivers allowing other components of the platform 500 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 500.
  • I/O input/output
  • driver circuitry 846 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 500, sensor drivers to obtain sensor readings of sensor circuitry 521 and control and allow access to sensor circuitry 521, EMC drivers to obtain actuator positions of the EMCs 522 and/or control and allow access to the EMCs 522, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
  • a display driver to control and allow access to a display device
  • a touchscreen driver to control and allow access to a touchscreen interface of the platform 500
  • sensor drivers to obtain sensor readings of sensor circuitry 521 and control and allow access to sensor circuitry 521
  • EMC drivers to obtain actuator positions of the EMCs 522 and/or control and allow access to the EMCs 522
  • a camera driver to control and allow access to an embedded image capture device
  • audio drivers to control and allow access to one or more audio devices.
  • the management integrated circuitry (PMIC) 525 may manage power provided to various components of the platform 500.
  • the PMIC 525 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMIC 525 may often be included when the platform 500 is capable of being powered by a battery 830, for example, when the device is included in a UE 301.
  • the PMIC 525 may control, or otherwise be part of, various power saving mechanisms of the platform 500. For example, if the platform 500 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 platform 500 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 500 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.
  • DRX Discontinuous Reception Mode
  • the platform 500 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 platform 500 may not receive data in this state; in order to receive data, it must transition back to 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.
  • a battery 830 may power the platform 500, although in some examples the platform 500 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid.
  • the battery 830 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 830 may be a typical lead-acid automotive battery.
  • the battery 830 may be a“smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry.
  • BMS Battery Management System
  • the BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 830.
  • the BMS may be used to monitor other parameters of the battery 830 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 830.
  • the BMS may communicate the information of the battery 830 to the application circuitry 505 or other components of the platform 500.
  • the BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 505 to directly monitor the voltage of the battery 830 or the current flow from the battery 830.
  • ADC analog-to-digital
  • the battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, and the like.
  • a power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 830.
  • the power block XS30 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 500.
  • a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 830, and thus, the current required.
  • the charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.
  • User interface circuitry 850 includes various input/output (I/O) devices present within, or connected to, the platform 500, and includes one or more user interfaces designed to enable user interaction with the platform 500 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 500.
  • the user interface circuitry 850 includes input device circuitry and output device circuitry.
  • Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like.
  • the output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information.
  • Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 500.
  • the output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like.
  • the sensor circuitry 521 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like).
  • EMCs e.g., an actuator to provide haptic feedback or the like.
  • NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.
  • the components of platform 500 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time- Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies.
  • the bus/IX may be a proprietary bus/IX, for example, used in a SoC based system.
  • Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to- point interfaces, and a power bus, among others.
  • FIG. 6 illustrates example components of baseband circuitry 610 and radio front end modules (RFEM) 615 in accordance with various embodiments.
  • the baseband circuitry 610 corresponds to the baseband circuitry 410 and 510 of Figures 7 and 8, respectively.
  • the RFEM 615 corresponds to the RFEM 415 and 515 of Figures 7 and 8, respectively.
  • the RFEMs 615 may include Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, antenna array 611 coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the baseband circuitry 610 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry 606.
  • 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 610 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast- Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 610 is configured to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • the baseband circuitry 610 is configured to interface with application circuitry 405/505 (see Figures 4 and 5) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 610 may handle various radio control functions.
  • the aforementioned circuitry and/or control logic of the baseband circuitry 610 may include one or more single or multi-core processors.
  • the one or more processors may include a 3G baseband processor 604A, a 4G/LTE baseband processor 604B, a 5G/NR baseband processor 604C, or some other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., Sixth generation (6G), etc.).
  • 6G Sixth generation
  • some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
  • CPU Central Processing Unit
  • baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells.
  • the memory 604G may store program code of a real-time OS (RTOS), which when executed by the CPU 604E (or other baseband processor), is to cause the CPU 604E (or other baseband processor) to manage resources of the baseband circuitry 610, schedule tasks, etc.
  • RTOS real-time OS
  • the RTOS may include Operating System Embedded (OSE)TM provided by Enea®, Nucleus RTOSTM provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadXTM provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein.
  • the baseband circuitry 610 includes one or more audio digital signal processor(s) (DSP) 604F.
  • the audio DSP(s) 604F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • each of the processors 604A-604E include respective memory interfaces to send/receive data to/from the memory 604G.
  • the baseband circuitry 610 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory xternal to the baseband circuitry 610; an application circuitry interface to send/receive data to/from the application circuitry 405/505 of FIGS.7-9); an RF circuitry interface to send/receive data to/from RF circuitry 606 of Figure 6; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/ Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 525.
  • NFC Near Field Communication
  • Wi-Fi® components Wi-Fi® components
  • baseband circuitry 610 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem.
  • the digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem.
  • Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein.
  • the audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components.
  • baseband circuitry 610 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 615).
  • the baseband circuitry 610 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a“multi-protocol baseband processor” or“protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions.
  • the PHY layer functions include the aforementioned radio control functions.
  • the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols.
  • the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 610 and/or RF circuitry 606 are part of mmWave communication circuitry or some other suitable cellular communication circuitry.
  • the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions.
  • the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 610 and/or RF circuitry 606 are part of a Wi-Fi communication system.
  • the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions.
  • the protocol processing circuitry may include one or more memory structures (e.g., 604G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data.
  • the baseband circuitry 610 may also support radio communications for more than one wireless protocol.
  • the various hardware elements of the baseband circuitry 610 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs.
  • the components of the baseband circuitry 610 may be suitably combined in a single chip or chipset, or disposed on a same circuit board.
  • some or all of the constituent components of the baseband circuitry 610 and RF circuitry 606 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP).
  • SoC system on a chip
  • SiP System-in-Package
  • the constituent components of the baseband circuitry 610 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 606 (or multiple instances of RF circuitry 606).
  • some or all of the constituent components of the baseband circuitry 610 and the application circuitry 405/505 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a“multi-chip package”).
  • the baseband circuitry 610 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 610 may support communication with an E- UTRAN or other WMAN, a WLAN, a WPAN.
  • Embodiments in which the baseband circuitry 610 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 610.
  • RF circuitry 606 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 610 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down- converted signals and the filter circuitry 606c 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 signals.
  • Output baseband signals may be provided to the baseband circuitry 610 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 610 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a 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 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a 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 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 610 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+1 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 610 or the application circuitry 405/505 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 405/505.
  • Synthesizer circuitry 606d of the RF circuitry 606 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 (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (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.
  • 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.
  • synthesizer circuitry 606d 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.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of antenna elements of antenna array 611.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry 608.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 608 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 608 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 606).
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 611.
  • PA power amplifier
  • the antenna array 611 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals.
  • digital baseband signals provided by the baseband circuitry 610 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 611 including one or more antenna elements (not shown).
  • the antenna elements may be omnidirectional, direction, or a combination thereof.
  • the antenna elements may be formed in a multitude of arranges as are known and/or discussed herein.
  • the antenna array 611 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards.
  • the antenna array 611 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 606 and/or FEM circuitry 608 using metal transmission lines or the like.
  • Processors of the application circuitry 405/505 and processors of the baseband circuitry 610 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 610 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 405/505 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers).
  • Layer 3 may comprise a RRC layer, described in further detail below.
  • Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below.
  • Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.
  • Figure 7 illustrates various protocol functions that may be implemented in a wireless communication device according to various embodiments.
  • Figure 7 includes an arrangement 700 showing interconnections between various protocol layers/entities.
  • the following description of Figure 7 is provided for various protocol layers/entities that operate in conjunction with the 5G/NR system standards and LTE system standards, but some or all of the aspects of Figure 7 may be applicable to other wireless communication network systems as well.
  • the protocol layers of arrangement 700 may include one or more of PHY 710, MAC 720, RLC 730, PDCP 740, SDAP 747, RRC 755, and NAS layer 757, in addition to other higher layer functions not illustrated.
  • the protocol layers may include one or more service access points (e.g., items 759, 756, 750, 749, 745, 735, 725, and 715 in Figure 7) that may provide communication between two or more protocol layers.
  • the PHY 710 may transmit and receive physical layer signals 705 that may be received from or transmitted to one or more other communication devices.
  • the physical layer signals 705 may comprise one or more physical channels, such as those discussed herein.
  • the PHY 710 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC 755.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY 710 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing.
  • FEC forward error correction
  • an instance of PHY 710 may process requests from and provide indications to an instance of MAC 720 via one or more PHY-SAP 715.
  • requests and indications communicated via PHY-SAP 715 may comprise one or more transport channels.
  • Instance(s) of MAC 720 may process requests from, and provide indications to, an instance of RLC 730 via one or more MAC-SAPs 725. These requests and indications communicated via the MAC-SAP 725 may comprise one or more logical channels.
  • the MAC 720 may perform mapping between the logical channels and transport channels, multiplexing of MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 710 via the transport channels, de-multiplexing MAC SDUs to one or more logical channels from TBs delivered from the PHY 710 via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.
  • Instance(s) of RLC 730 may process requests from and provide indications to an instance of PDCP 740 via one or more radio link control service access points (RLC-SAP) 735. These requests and indications communicated via RLC-SAP 735 may comprise one or more RLC channels.
  • the RLC 730 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the RLC 730 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs upper layer protocol data units
  • ARQ automatic repeat request
  • the RLC 730 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re- establishment.
  • Instance(s) of PDCP 740 may process requests from and provide indications to instance(s) of RRC 755 and/or instance(s) of SDAP 747 via one or more packet data convergence protocol service access points (PDCP-SAP) 745. These requests and indications communicated via PDCP-SAP 745 may comprise one or more radio bearers.
  • PDCP-SAP packet data convergence protocol service access points
  • the PDCP 740 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re- establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • SNs PDCP Sequence Numbers
  • Instance(s) of SDAP 747 may process requests from and provide indications to one or more higher layer protocol entities via one or more SDAP-SAP 749. These requests and indications communicated via SDAP-SAP 749 may comprise one or more QoS flows.
  • the SDAP 747 may map QoS flows to DRBs, and vice versa, and may also mark QFIs in DL and UL packets.
  • a single SDAP entity 747 may be configured for an individual PDU session.
  • the NG-RAN 310 may control the mapping of QoS Flows to DRB(s) in two different ways, reflective mapping or explicit mapping.
  • the SDAP 747 of a UE 301 may monitor the QFIs of the DL packets for each DRB, and may apply the same mapping for packets flowing in the UL direction. For a DRB, the SDAP 747 of the UE 301 may map the UL packets belonging to the QoS flows(s) corresponding to the QoS flow ID(s) and PDU session observed in the DL packets for that DRB. To enable reflective mapping, the NG-RAN may mark DL packets over the Uu interface with a QoS flow ID.
  • the explicit mapping may involve the RRC 755 configuring the SDAP 747 with an explicit QoS flow to DRB mapping rule, which may be stored and followed by the SDAP 747.
  • the SDAP 747 may only be used in NR implementations and may not be used in LTE implementations.
  • the RRC 755 may configure, via one or more management service access points (M-SAP), aspects of one or more protocol layers, which may include one or more instances of PHY 710, MAC 720, RLC 730, PDCP 740 and SDAP 747.
  • M-SAP management service access points
  • an instance of RRC 755 may process requests from and provide indications to one or more NAS entities 757 via one or more RRC-SAPs 756.
  • the main services and functions of the RRC 755 may include broadcast of system information (e.g., included in MIBs or SIBs related to the NAS), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE 301 and RAN 310 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting.
  • the MIBs and SIBs may comprise one or more IEs, which may each comprise individual data fields or data structures.
  • the NAS 757 may form the highest stratum of the control plane between the UE 301 and the AMF.
  • the NAS 757 may support the mobility of the UEs 301 and the session management procedures to establish and maintain IP connectivity between the UE 301 and a P-GW in LTE systems.
  • one or more protocol entities of arrangement 700 may be implemented in UEs 301, RAN nodes 311, AMF in NR implementations or MME in LTE implementations, UPF in NR implementations or S- GW and P-GW in LTE implementations, or the like to be used for control plane or user plane communications protocol stack between the aforementioned devices.
  • one or more protocol entities that may be implemented in one or more of UE 301, gNB 311, AMF, etc. may communicate with a respective peer protocol entity that may be implemented in or on another device using the services of respective lower layer protocol entities to perform such communication.
  • a gNB- CU of the gNB 311 may host the RRC 755, SDAP 747, and PDCP 740 of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 311 may each host the RLC 730, MAC 720, and PHY 710 of the gNB 311.
  • a control plane protocol stack may comprise, in order from highest layer to lowest layer, NAS 757, RRC 755, PDCP 740, RLC 730, MAC 720, and PHY 710.
  • upper layers 760 may be built on top of the NAS 757, which includes an IP layer 761, an SCTP 762, and an application layer signaling protocol (AP) 763.
  • AP application layer signaling protocol
  • the AP 763 may be an NG application protocol layer (NGAP or NG-AP) 763 for the NG interface 313 defined between the NG-RAN node 311 and the AMF, or the AP 763 may be an Xn application protocol layer (XnAP or Xn- AP) 763 for the Xn interface 312 that is defined between two or more RAN nodes 311.
  • NGAP NG application protocol layer
  • XnAP or Xn- AP Xn application protocol layer
  • the NG-AP 763 may support the functions of the NG interface 313 and may comprise Elementary Procedures (EPs).
  • An NG-AP EP may be a unit of interaction between the NG-RAN node 311 and the AMF.
  • the NG-AP 763 services may comprise two groups: UE-associated services (e.g., services related to a UE 301) and non-UE- associated services (e.g., services related to the whole NG interface instance between the NG-RAN node 311 and AMF).
  • These services may include functions including, but not limited to: a paging function for the sending of paging requests to NG-RAN nodes 311 involved in a particular paging area; a UE context management function for allowing the AMF to establish, modify, and/or release a UE context in the AMF and the NG-RAN node 311; a mobility function for UEs 301 in ECM-CONNECTED mode for intra-system HOs to support mobility within NG-RAN and inter-system HOs to support mobility from/to EPS systems; a NAS Signaling Transport function for transporting or rerouting NAS messages between UE 301 and AMF; a NAS node selection function for determining an association between the AMF and the UE 301; NG interface management function(s) for setting up the NG interface and monitoring for errors over the NG interface; a warning message transmission function for providing means to transfer warning messages via NG interface or cancel ongoing broadcast of warning messages; a Configuration Transfer function for requesting and transferring of
  • the XnAP 763 may support the functions of the Xn interface 312 and may comprise XnAP basic mobility procedures and XnAP global procedures.
  • the XnAP basic mobility procedures may comprise procedures used to handle UE mobility within the NG RAN 311 (or E-UTRAN), such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like.
  • the XnAP global procedures may comprise procedures that are not related to a specific UE 301, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, and the like.
  • the AP 763 may be an S1 Application Protocol layer (S1-AP) 763 for the S1 interface 313 defined between an E-UTRAN node 311 and an MME, or the AP 763 may be an X2 application protocol layer (X2AP or X2-AP) 763 for the X2 interface 312 that is defined between two or more E-UTRAN nodes 311.
  • S1-AP S1 Application Protocol layer
  • X2AP or X2-AP X2 application protocol layer
  • the S1 Application Protocol layer (S1-AP) 763 may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may comprise S1-AP EPs.
  • An S1-AP EP may be a unit of interaction between the E-UTRAN node 311 and an MME within an LTE CN 320.
  • the S1-AP 763 services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E- RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E- RAB E-UTRAN Radio Access Bearer
  • RAM Radio Access Management
  • the X2AP 763 may support the functions of the X2 interface 312 and may comprise X2AP basic mobility procedures and X2AP global procedures.
  • the X2AP basic mobility procedures may comprise procedures used to handle UE mobility within the E-UTRAN 320, such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like.
  • the X2AP global procedures may comprise procedures that are not related to a specific UE 301, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, cell activation procedures, and the like.
  • the SCTP layer (alternatively referred to as the SCTP/IP layer) 762 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations).
  • the SCTP 762 may ensure reliable delivery of signaling messages between the RAN node 311 and the AMF/MME based, in part, on the IP protocol, supported by the IP 761.
  • the Internet Protocol layer (IP) 761 may be used to perform packet addressing and routing functionality. In some implementations the IP layer 761 may use point-to-point transmission to deliver and convey PDUs.
  • the RAN node 311 may comprise L2 and L1 layer communication links (e.g., wired or wireless) with the MME/AMF to exchange information.
  • a user plane protocol stack may comprise, in order from highest layer to lowest layer, SDAP 747, PDCP 740, RLC 730, MAC 720, and PHY 710.
  • the user plane protocol stack may be used for communication between the UE 301, the RAN node 311, and UPF in NR implementations or an S-GW and P-GW in LTE implementations.
  • upper layers 751 may be built on top of the SDAP 747, and may include a user datagram protocol (UDP) and IP security layer (UDP/IP) 752, a General Packet Radio Service (GPRS) Tunneling Protocol for the user plane layer (GTP-U) 753, and a User Plane PDU layer (UP PDU) 763.
  • the transport network layer 754 (also referred to as a“transport layer”) may be built on IP transport, and the GTP-U 753 may be used on top of the UDP/IP layer 752 (comprising a UDP layer and IP layer) to carry user plane PDUs (UP-PDUs).
  • the IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routing functionality.
  • the IP layer may assign IP addresses to user data packets in any of IPv4, IPv6, or PPP formats, for example.
  • the GTP-U 753 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP/IP 752 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 311 and the S-GW may utilize an S1-U interface to exchange user plane data via a protocol stack comprising an L1 layer (e.g., PHY 710), an L2 layer (e.g., MAC 720, RLC 730, PDCP 740, and/or SDAP 747), the UDP/IP layer 752, and the GTP-U 753.
  • L1 layer e.g., PHY 710
  • L2 layer e.g., MAC 720, RLC 730, PDCP 740, and/or SDAP 747
  • the S-GW and the P-GW may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer 752, and the GTP-U 753.
  • NAS protocols may support the mobility of the UE 301 and the session management procedures to establish and maintain IP connectivity between the UE 301 and the P-GW.
  • an application layer may be present above the AP 763 and/or the transport network layer 754.
  • the application layer may be a layer in which a user of the UE 301, RAN node 311, or other network element interacts with software applications being executed, for example, by application circuitry 405 or application circuitry 505, respectively.
  • the application layer may also provide one or more interfaces for software applications to interact with communications systems of the UE 301 or RAN node 311, such as the baseband circuitry 610.
  • the IP layer and/or the application layer may provide the same or similar functionality as layers 5-7, or portions thereof, of the Open Systems Interconnection (OSI) model (e.g., OSI Layer 7 - the application layer, OSI Layer 6 - the presentation layer, and OSI Layer 5 - the session layer).
  • OSI Open Systems Interconnection
  • Figure 11 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 11 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.
  • node virtualization e.g., NFV
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800.
  • the processors 810 may include, for example, a processor 812 and a processor 814.
  • the processor(s) 810 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 radio-frequency 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 radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 820 may include, but are not limited to, any type of volatile or nonvolatile 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 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
  • the communication resources 830 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor's cache memory), the memory/storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes, un appareil, des programmes informatiques ou des combinaisons de ceux-ci, permettant de sélectionner un mode de fonctionnement pour un équipement d'utilisateur (UE) qui fonctionne dans un spectre sans licence. Un procédé consiste à identifier des informations à partir desquelles déterminer le mode de fonctionnement, l'UE étant desservi par un réseau d'accès radio (RAN) fonctionnant dans une bande de spectre de radiofréquences sans licence ; déterminer, en fonction des informations, une indication de mode régional ou de mode global ; et fonctionner dans le mode de fonctionnement déterminé.
PCT/US2020/023197 2019-03-21 2020-03-17 Conception de signalisation pour un équipement d'utilisateur fonctionnant dans un spectre sans licence WO2020190965A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962821595P 2019-03-21 2019-03-21
US62/821,595 2019-03-21
US201962841092P 2019-04-30 2019-04-30
US62/841,092 2019-04-30

Publications (1)

Publication Number Publication Date
WO2020190965A1 true WO2020190965A1 (fr) 2020-09-24

Family

ID=70334035

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/023197 WO2020190965A1 (fr) 2019-03-21 2020-03-17 Conception de signalisation pour un équipement d'utilisateur fonctionnant dans un spectre sans licence

Country Status (1)

Country Link
WO (1) WO2020190965A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1843613A1 (fr) * 2006-04-03 2007-10-10 Research In Motion Limited Système et procédé pour faciliter la configuration et détermination du mode d'un appareil utilisateur sans-fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1843613A1 (fr) * 2006-04-03 2007-10-10 Research In Motion Limited Système et procédé pour faciliter la configuration et détermination du mode d'un appareil utilisateur sans-fil

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 15)", 22 December 2018 (2018-12-22), XP051686556, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/3guInternal/3GPP%5Fultimate%5Fversions%5Fto%5Fbe%5Ftransposed/sentToDpc/23003%2Df60%2Ezip> [retrieved on 20181222] *
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 8)", 3GPP STANDARD; 3GPP TS 36.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V8.2.0, 1 May 2008 (2008-05-01), pages 1 - 151, XP050377645 *
ITL: "Considerations on supporting dual mode for NR-V2X", vol. RAN WG2, no. Athens, Greece; 20190325 - 20190301, 15 February 2019 (2019-02-15), XP051603423, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F105/Docs/R2%2D1902077%2Ezip> [retrieved on 20190215] *

Similar Documents

Publication Publication Date Title
US11936583B2 (en) SSB pattern and DMRS design for PBCH in 5G NR
US20220159740A1 (en) Mapping between prach preambles and pusch resource units for 2-step rach
US12035381B2 (en) Link establishment in relay nodes
US12101179B2 (en) Methods for fast secondary cell activation and deactivation
US20220182867A1 (en) Measurement gap pattern use and management for wireless communication systems
US20210392673A1 (en) Enhanced physical uplink control channel (pucch) transmission for high reliability
US20220167359A1 (en) Methods for fast serving cell activation with short channel-state information reporting
EP3984255B1 (fr) Transmission de rétroaction de demande de répétition automatique hybride (harq) de liaison latérale (sl) basée sur la localisation
US11985651B2 (en) Dynamic indication of soft resource availability
US20220158897A1 (en) End-to-end radio access network (ran) deployment in open ran (o-ran)
US12041487B2 (en) User equipment based packet data convergence protocol (PDCP) duplication activation and deactivation
US20220167223A1 (en) Methods for Enhanced Handover Using Conditional and Simultaneous Connectivity Handover
US20220141752A1 (en) Methods for Data Transmission in Relay Node
WO2020223703A1 (fr) Configuration de canal d&#39;accès aléatoire dans un réseau d&#39;accès intégré et de liaison terrestre
WO2020102076A1 (fr) Commutation de faisceau dans une agrégation de porteuses non contiguës intra-bande
US12120545B2 (en) Cross-layer quality of service (QoS) indication for sidelink communications
US11064566B2 (en) Symbol puncture for unlicensed narrowband internet of things (NB IoT)
CN112713977A (zh) 用于探测参考信号传输的方法
WO2020223653A1 (fr) Amélioration de la signalisation de transfert intercellulaire entre nœuds pour un transfert intercellulaire conditionnel
WO2020190965A1 (fr) Conception de signalisation pour un équipement d&#39;utilisateur fonctionnant dans un spectre sans licence

Legal Events

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

Ref document number: 20720558

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20720558

Country of ref document: EP

Kind code of ref document: A1