Method and system for compressing and decompressing information centric network names at a packet data convergence protocol (PDCP)
By compressing and decompressing the ICN name and common fields in the PDCP layer, the problem of inefficient use of spectrum resources caused by long ICN names is solved, and the wireless transmission efficiency of the cellular network is improved.
Patent Information
- Application Number
- CN202080017161.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-02-28
- Filing Date
- 2020-02-28
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-02-28
AI Technical Summary
In cellular networks, the long length of the information center network (ICN) name leads to inefficient spectrum resource usage, and the header compression of the existing PDCP layer is not suitable for ICN, resulting in inefficient wireless transmission.
Compress and decompress ICN names and common fields at the Packet Data Aggregation Protocol (PDCP) layer, optimize the transmission of ICN names through mapping and segmentation techniques to achieve improved spectrum efficiency.
Through the compression and decompression of ICN names, the efficiency of spectrum resource utilization in the cellular network is improved, the packet error rate is reduced, and the wireless transmission efficiency is improved.
Smart Images

Figure CN113491095B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application No. 62 / 811,829, filed on February 28, 2019, which is hereby incorporated by reference in its entirety. Technical Field
[0003] Various embodiments may generally relate to the field of wireless communications. Summary of the Invention
[0004] Some embodiments of the present disclosure include systems, apparatus, methods, and computer-readable media for use in wireless networks for compressing and decompressing Information Centric Network (ICN) names and / or ICN common fields at a Packet Data Convergence Protocol (PDCP) layer.
[0005] Some embodiments relate to an electronic device. The electronic device includes a processor circuit and a radio front-end circuit coupled to the processor circuit. The processor circuit can be configured to receive a first ICN packet including an Information Centric Network (ICN) name or an ICN common field and compress the ICN name or the ICN common field at a Packet Data Convergence Protocol (PDCP) layer. The processor circuit can be further configured to provide the compressed ICN name or the compressed ICN common field to a lower protocol layer. The radio front-end circuit can be configured to transmit a second ICN packet including the compressed ICN name or the compressed ICN common field.
[0006] Some embodiments relate to a method. The method includes receiving, at an electronic device, a first Information Centric Network (ICN) packet including an ICN name or an ICN common field. The method also includes compressing the ICN name or the ICN common field at a Packet Data Convergence Protocol (PDCP) layer at the electronic device and providing the compressed ICN name or the compressed ICN common field to a lower protocol layer at the electronic device. The method may also include transmitting, by the electronic device, a second ICN packet including the compressed ICN name or the compressed ICN common field.
[0007] Some embodiments relate to an electronic device. The electronic device includes a processor circuit and a radio front-end circuit coupled to the processor circuit. The processor circuit can be configured to receive, using the radio front-end circuit, a first Information Centric Network (ICN) packet including at least one of a compressed ICN name or a compressed ICN common field. The processor circuit can be further configured to decompress the compressed ICN name or the compressed ICN common field at a Packet Data Convergence Protocol (PDCP) layer and provide the decompressed ICN name or the decompressed ICN common field to a higher protocol layer.
[0008] Some embodiments relate to a method. The method includes receiving, at an electronic device, a first Information Centric Network (ICN) packet including at least one of a compressed ICN name or a compressed ICN common field. The method may also include decompressing the compressed ICN name or the compressed ICN common field at a Packet Data Convergence Protocol (PDCP) layer at the electronic device, and providing the decompressed ICN name or the decompressed ICN common field to a higher protocol layer at the electronic device. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 Depicted are exemplary information-centric networks (ICNs) according to some embodiments.
[0010] Figure 2 Depicted are exemplary packet formats for interest packets and data packets according to some embodiments.
[0011] Figure 3 Depicted is an architecture for a system of networks according to some embodiments.
[0012] Figure 4 An architecture of a system including a first core network is depicted according to some embodiments.
[0013] Figure 5 Depicted is an architecture of a system including a second core network according to some embodiments.
[0014] Figure 6 Depicted are examples of infrastructure equipment according to various embodiments.
[0015] Figure 7 Depicted are exemplary components of a computer platform according to various embodiments.
[0016] Figure 8 Depicted are exemplary components of baseband circuitry and radio frequency circuitry according to various embodiments.
[0017] Figure 9 is a diagram of various protocol functions that may be used in various protocol stacks, according to various embodiments.
[0018] Figure 10 Depicted are block diagrams illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary embodiments.
[0019] Figure 11 Depicted are exemplary flow charts for practicing various embodiments discussed herein, for example, exemplary flow charts for compressing and decompressing Information Centric Network (ICN) names and / or ICN common fields at a Packet Data Convergence Protocol (PDCP) layer.
[0020] Figure 12 Depicted are exemplary flow diagrams for practicing various embodiments discussed herein, for example, exemplary flow diagrams for compressing Information Centric Network (ICN) names and / or ICN common fields at a Packet Data Convergence Protocol (PDCP) layer.
[0021] Figure 13 Depicted are exemplary flow diagrams for practicing various embodiments discussed herein, for example, exemplary flow diagrams for decompressing an Information Centric Network (ICN) name and / or ICN common fields at a Packet Data Convergence Protocol (PDCP) layer.
[0022] Features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the accompanying drawings, in which like reference numerals identify corresponding elements throughout. In the drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference numeral. DETAILED DESCRIPTION
[0023] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration and not limitation, so as to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).
[0024] According to some examples, the network architecture is based on the Internet Protocol (IP) and is host-centric. Therefore, communication is host-to-host, and content delivery relies on a session between two endpoints.
[0025] Figure 1 An exemplary information-centric network (ICN) 100 is shown, according to some embodiments. In an ICN, access to content is accomplished through a pull-based model, where a client 104 (also referred to as a consumer) sends an interest packet 103 to a network device (e.g., a source 110) through an access node (AN) 106 and an ICN router 108, requesting a given content by the name of the interest packet. According to some embodiments, the source 110 replies with the requested content (e.g., sending a data packet 105). In some embodiments, the source 110 can exchange interest packets 103 and / or data packets 105 with the AN 106 without using an ICN router 108.
[0026] In some embodiments, the format of the interest packets 103 and / or data packets 105 exchanged between the client 104 and the access node 106 can be designed for over-the-air (OTA) transmission, while the format of the interest packets 103 and / or data packets 105 exchanged between the AN 106 and the source 108 can traverse the network infrastructure (e.g., backhaul, wireline, optical fiber, etc.). As will be described in further detail herein, the client 104 and the AN 106 can perform compression / decompression of the Information Center Network (ICN) name or ICN public field at the Packet Data Convergence Protocol (PDCP) layer. The AN 106 can then exchange the interest packets 103 and / or data packets 105 with the ICN router 108 (or directly with the server 110) using the uncompressed ICN name / public field.
[0027] Client 104 may correspond to Figure 3 UE 301a or 301b; AN 106 may correspond to Figure 3 RAN node 311a or 311b; and the source 108 may correspond to Figure 3 application server 330.
[0028] Figure 2 An exemplary packet format 200 for interest packets 202 and data packets 204 is depicted according to some embodiments. According to some embodiments, the names 206 and 208 may have no restrictions on their respective lengths, as per the packet format specification. However, this may be constrained based on the layer 2 maximum transmission unit (MTU) and the fact that the data packet 204 includes a name 208 in addition to content / data. In some examples, the larger the size of the names 206 / 208, the more information exchange efficiency is reduced.
[0029] In cellular networks (e.g., 4G and 5G networks), the Packet Data Convergence Protocol (PDCP) layer uses the Robust Header Compression (ROHC) protocol to provide several services, including header compression (and decompression), to upper layers (e.g., the Radio Resource Control (RRC) and / or Service Data Adaptation Protocol (SDAP) layers). (See, for example, 3GPP TS 38.323, v15.4.0 (2019-01)). According to some examples, header compression is important for making wireless transmission more efficient.
[0030] Transmitting ICN names over the air may inefficiently use spectrum resources due to the nature of the length of the names and may prevent lower layers from controlling the names used by applications to request and / or generate data.
[0031] In some examples, PDCP header compression is not used in the PDCP layer of ICN-based cellular networks. In these examples, not using header compression (especially for interest packets) can lead to low wireless transmission efficiency. Some exemplary embodiments of the present disclosure address these challenges.
[0032] Some exemplary embodiments of the present disclosure address the inefficient use of spectrum resources in ICN-based cellular networks. This can be achieved, for example, by implementing a PDCP layer (e.g., Figure 9 This can be achieved by compressing / decompressing the ICN name at the PDCP 940). Figure 1 This is done in the client 104 and AN 106 as shown.
[0033] In some current PDCP specifications (eg, TS 38.323), the PDCP layer supports header compression and decompression using the Robust Header Compression (ROHC) protocol, which is defined only for IP-based protocols and has several profiles as shown in Table 1.
[0034] Profile Identifier use refer to 0x0000 No compression RFC 5795 0x0001 RTP / UDP / IP RFC 3095, RFC 4815 0x0002 UDP / IP RFC 3095, RFC 4815 0x0003 ESP / IP RFC 3095, RFC 4815 0x0004 IP RFC 3843, RFC 4815 0x0006 TCP / IP RFC 6846 0x0101 RTP / UDP / IP RFC 5225 0x0102 UDP / IP RFC 5225 0x0103 ESP / IP RFC 5225 0x0104 IP RFC 5225
[0035] Table 1 - Supported header compression protocols and profiles
[0036] According to some embodiments, ICN names are not restricted in the Named Data Networking (NDN) packet specification, and the maximum supported size of the PDCP Service Data Unit (SDU) is 9000 bytes. In these examples, when the ICN (interest and / or data) packet is larger than the PDCP SDU size, ICN name compression may be applied first, and then segmentation may be applied. Segmentation at the PDCP layer is possible using a protocol such as the Named Data Networking Link Protocol (NDNLP). However, for ICN name compression / segmentation to be applied at the PDCP layer, NDNLP segmentation must be disabled. Segmentation at the PDCP layer may follow a packet format similar to NDNLP segmentation.
[0037] According to some embodiments, the ICN application of source 108 generates one or more streams to produce data for the ICN application. For example, an ICN video streaming application may generate one stream (or multiple streams) for video and one stream (or two streams) for audio. An example of a name used in a non-limiting example of an ICN application (only one stream) may be " / netflix / movies / action / rambo / res1080". Typically, interest packets in one stream are created / sent in sequential order (%FE%00, %FE%01, %FE%02...). As shown in Table 2, compressing the name from " / netflix / movies / action / rambo / res1080" to " / 1" can achieve a packet size reduction of approximately 52%. Real-life applications may use longer names, thereby achieving higher efficiency at the PDCP layer.
[0038]
[0039] Table 2 Interest group sizes for compressed and uncompressed names
[0040] According to some embodiments, several approaches can be used to implement name compression / mapping. One possible implementation is for RRC to configure the ICN compression parameters via Information Element (IE) PDCP Configuration (see, for example, 3GPP TS 38.331 v15.4.0 (2019-01)) using the ICN name registered by the User Equipment (UE) (when the UE is the producer) in the ICN-CF via the control plane.
[0041]
[0042] Table 3 TLV-Type Number Allocation
[0043] Another possible specific implementation of ICN name compression is by creating a mapping in the UE and the AN (as used herein, "AN" may refer to a gNB, eNB, or any other access node). That is, the PDCP layer reads the ICN packet defined in the TLV (Type-Length-Value or Tag-Length-Value) format. First, the outer TLV that defines the packet type is read (as shown in Table 3, the type of the interest packet = 5, and the type of the data packet = 6). Then the type = 7 is read, which defines / contains the information / value of the ICN name. Based on this name, the PDCP layer can initiate the mapping <id, name>, where "id" is a unique sequential number assigned to each name. This mapping is stored in the UE and the AN for the PDCP to access when compressing and decompressing the name. The PDCP is used to exchange information about this mapping between the UE and the AN in the PDU packet, where the PDU type (3 bits) can be standardized and can be any bit value between 011 and 111, because 000, 001, and 010 have been used for other purposes. As shown in the example in Table 2, the first element of the mapping <id, name> can be <1,netflix / movies / action / rambo / res1080>, and the information of this mapping is sent from the transmitting PDCP side (UE or gNB / eNB) to the receiving PDCP side (gNB / eNB or UE) through the PDCP control PDU packet.
[0044] According to some embodiments, considering that the interest packets in a stream can be created / sent in sequential order / numbering (%FE%00, %FE%01, %FE%02, etc.), a part (or all) of the sequential numbering (e.g., %FE%00, %FE%01, %FE%02) can be compressed.
[0045] In another exemplary specific implementation, in the case where the PDCP layer does not have the specific implementation / capability of reading the TLV packet format, the mapping can be completed by layer 3 (i.e., the ICN layer). In this example, in the UE, the ICN layer can create the mapping <id, name> and pass this information to the PDCP layer. In the gNB / eNB, the networking capability can depend on different network elements (e.g., the ICN Point of Attachment [ICN-PoA], which is connected to the gNB / eNB or can be integrated into the gNB / eNB [e.g., gNB / eNB + ICN-PoA]). If the former is applied, the ICN-PoA can create the mapping <id, name> and send this information to the gNB / eNB.
[0046] In addition to compressing the ICN name, embodiments of the present disclosure may also extend to all common fields of interest packets and data packets, which include GenericNameComponent, ImplicitSha256DigestComponent, and ParametersSha256DigestComponent. In some examples, the GenericNameComponent (same as Name) has no size limit. In some examples, each of the ImplicitSha256DigestComponent and ParametersSha256DigestComponent should not be higher than 32 octets. Compressing all common fields can result in a smaller packet size, thus achieving higher spectral efficiency and a lower packet error rate. For this case, the mapping can be <id, common field>, where "id" is a sequential number and "common field" is a set of TLV components of an ICN (interest or data) packet for Name, GenericNameComponent, ImplicitSha256DigestComponent, and ParametersSha256DigestComponent.
[0047] System and implementation
[0048] Figure 3 An exemplary architecture of a system 300 of a network according to various embodiments is shown. The following description is provided for an example system 300 operating in conjunction with the LTE system standard and the 5G or NR system standard provided by the 3GPP technical specification. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied 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., WLAN, WiMAX, etc.), and the like.
[0049] As Figure 3As shown, system 300 includes UE 301a and UE 301b (collectively referred to as "UE 301" or "UE 301"). In this example, multiple UEs 301 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.
[0050] In some embodiments, any of the UEs 301 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.
[0051] UE 301 may be configured to connect, e.g., be communicatively coupled, to RAN 310. In an embodiment, RAN 310 may be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., may refer to RAN 310 operating in an NR or 5G system 300, while the term "E-UTRAN," etc., may refer to RAN 310 operating in an LTE or 4G system 300. UE 301 utilizes connections (or channels) 303 and 304, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).
[0052] In this example, connections 303 and 304 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, 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 other communication protocol discussed herein. In an embodiment, the UE 301 may directly exchange communication data via a ProSe interface 305. The ProSe interface 305 may alternatively be referred to as an SL interface 305 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.
[0053] UE 301b is shown as being configured to access AP 306 (also referred to as "WLAN node 306," "WLAN 306," "WLAN terminal 306," "WT 306," etc.) via connection 307. Connection 307 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 306 would include Wireless Fidelity. Router. In this example, AP 306 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 301b, RAN 310, and AP 306 can be configured to utilize LWA operation and / or LWIP operation. LWA operation can involve RAN nodes 311a-b configuring UE 301b in the RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP operation can involve UE 301b using WLAN radio resources (e.g., connection 307) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 307. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.
[0054] RAN 310 may include one or more AN nodes or RAN nodes 311a and 311b (collectively referred to as "RAN node 311" or "RAN node 311") that enable connections 303 and 304. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to RAN nodes 311 (e.g., gNBs) operating in NR or 5G systems 300, while the terms "E-UTRAN node" and the like may refer to RAN nodes 311 (e.g., eNBs) operating in LTE or 4G systems 300. According to various embodiments, the RAN node 311 may be implemented as one or more dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.
[0055] In some embodiments, all or part of the multiple RAN nodes 311 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 311; a MAC / PHY split, where the 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, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, while the lower portions of the PHY layers are operated by individual RAN nodes 311. This virtualization framework allows idle processor cores of the RAN nodes 311 to execute other virtualized applications. In some implementations, a separate RAN node 311 may represent a separate RAN node 311 connected to the RAN via a separate F1 interface ( Figure 3 In these implementations, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 6), and the gNB-CU may be operated by a server (not shown) located in the RAN 310 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 311 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminations to the UE 301 and is connected to the 5GC (e.g., via an NG interface (discussed below)). Figure 5 RAN node of CN 520).
[0056] In a V2X scenario, one or more of the RAN nodes 311 may be or function as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The 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 so on. In one example, an RSU is a computing device coupled to RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 301 (vUEs 301). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision 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 communication services. Additionally or alternatively, 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. Some or all of the computing device and the RSU's RF circuitry 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 backhaul network.
[0057] Any of the RAN nodes 311 may terminate the air interface protocol and may be the first point of contact for the UE 301. In some embodiments, any of the RAN nodes 311 may fulfill various logical functions of the RAN 310, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
[0058] In an embodiment, multiple UEs 301 may be configured to communicate with each other or with any of multiple RAN nodes 311 using OFDM communication signals over a multi-carrier communication channel according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.
[0059] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 311 to the UE 301, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink in each time slot. This type of time-frequency plane representation is common for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.
[0060] According to various embodiments, the UE 301 and the RAN node 311 communicate data (e.g., transmit data and receive data) over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.
[0061] To operate in the unlicensed spectrum, the UE 301 and the RAN node 311 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 301 and the RAN node 311 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
[0062] LBT is a mechanism for equipment (e.g., UE 301, RAN node 311, etc.) to sense the medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.
[0063] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 301, AP 306, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.
[0064] The LAA mechanism is built on the Carrier Adaptation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100 MHz. In an FDD system, 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. In some cases, each CC can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL and UL.
[0065] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 301 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. 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 the same subframe.
[0066] The PDSCH carries user data and higher layer signaling to the UE 301. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It can also inform the UE 301 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 301b within a cell) can be performed on any of the multiple RAN nodes 311 based on channel quality information fed back from any of the multiple UEs 301. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 301.
[0067] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).
[0068] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to a set of nine physical resource elements, called EREGs, including four physical resource elements. In some cases, an ECCE may have other numbers of EREGs.
[0069] RAN nodes 311 may be configured to communicate with each other via interface 312. In embodiments where system 300 is an LTE system (eg, when CN 320 is a Figure 4 4 ), 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, etc.) connected to the EPC 320, and / or between two eNBs connected to the EPC 320. In some implementations, 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 a flow control mechanism for user packets transmitted over the X2 interface and may be used to convey information regarding the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information regarding user data transmitted from the MeNB to the SeNB; information regarding successful in-sequence delivery of PDCP PDUs for user data from the SeNB to the UE 301; information regarding PDCP PDUs that were not delivered to the UE 301; information regarding the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.
[0070] When system 300 is a 5G or NR system (e.g., when CN 320 is Figure 5In an embodiment (when the 5GC 520 is included in the 5GC 520), 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, etc.) connected to the 5GC 320, between a RAN node 311 (e.g., a gNB) and an eNB connected to the 5GC 320, and / or between two eNBs connected to the 5GC 320. In some specific implementations, 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 functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 301 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more RAN nodes 311. This mobility support may include context transfer from the old (source) serving RAN node 311 to the new (target) serving RAN node 311; and control of the user plane tunnel between the old (source) serving RAN node 311 and the new (target) serving RAN node 311. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be built on top of the IP layer and may provide guaranteed delivery of application layer messages. Within the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.
[0071] RAN 310 is shown as being communicatively coupled to a core network—in this embodiment, core network (CN) 320. CN 320 may include multiple network elements 322 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 301) connected to CN 320 via RAN 310. Components of CN 320 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from machine-readable media or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instance of CN 320 may be referred to as a network slice, and a logical instance of a portion of CN 320 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.
[0072] Generally speaking, the application server 330 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 330 may also be configured to support one or more communication services for the UE 301 via the EPC 320 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).
[0073] In an embodiment, CN 320 may be a 5GC (referred to as "5GC 320" or the like), and RAN 310 may be connected to CN 320 via an NG interface 313. In an embodiment, NG interface 313 may be divided into two parts: an NG user plane (NG-U) interface 314, which carries traffic data between RAN node 311 and UPF; and an S1 control plane (NG-C) interface 315, which is a signaling interface between RAN node 311 and AMF. Figure 5 An implementation of CN 320 as 5GC 320 is discussed in more detail.
[0074] In an embodiment, CN 320 may be a 5G CN (referred to as "5GC 320," etc.), while in other embodiments, CN 320 may be an EPC. In the case where CN 320 is an EPC (referred to as "EPC 320," etc.), RAN 310 may be connected to CN 320 via an S1 interface 313. In an embodiment, S1 interface 313 may be divided into two parts: an S1 user plane (S1-U) interface 314, which carries traffic data between RAN node 311 and S-GW; and an S1-MME interface 315, which is a signaling interface between RAN node 311 and MME.
[0075] Figure 4 FIG. 4 shows an exemplary architecture of a system 400 including a first CN 420 according to various embodiments. In this example, the system 400 may implement the LTE standard, wherein the CN 420 is a Figure 3 In addition, UE 401 can communicate with Figure 3 The UE 301 is the same as or similar to the UE 301, and the E-UTRAN 410 can be Figure 3 The CN 420 may be the same as or similar to the RAN 310 of the mobile network, and may include the RAN node 311 discussed previously. The CN 420 may include an MME 421, an S-GW 422, a P-GW 423, an HSS 424, and an SGSN 425.
[0076] MME 421 can be functionally similar to the control plane of a traditional SGSN and can implement MM functionality to keep track of the current location of UE 401. MME 421 can perform various MM procedures to manage mobility aspects of access, such as gateway selection and tracking area list management. MM (also known as "EPS MM" or "EMM" in E-UTRAN systems) can refer to all applicable procedures, methods, data stores, etc. used to maintain knowledge of the current location of UE 401, provide user identity confidentiality to users / subscribers, and / or perform other similar services. Each UE 401 and MME 421 can include an MM or EMM sublayer, and upon successful completion of the attach procedure, an MM context can be established in both UE 401 and MME 421. An MM context can be a data structure or database object that stores MM-related information for UE 401. MME 421 can be coupled to HSS 424 via the S6a reference point, to SGSN 425 via the S3 reference point, and to S-GW 422 via the S11 reference point.
[0077] SGSN 425 may be a node that serves UE 401 by tracking the location of individual UE 401 and performing security functions. Furthermore, SGSN 425 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 421; handling of UE 401 time zone capabilities as specified by MME 421; and MME selection for handover to E-UTRAN 3GPP access networks. The S3 reference point between MME 421 and SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and / or active states.
[0078] HSS 424 may include a database for network users, including subscription-related information used to support network entities handling communication sessions. EPC 420 may include one or several HSSs 424, depending on the number of mobile subscribers, device capabilities, network organization, and the like. For example, HSS 424 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, and the like. The S6a reference point between HSS 424 and MME 421 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access EPC 420 between HSS 424 and MME 421.
[0079] The S-GW 422 may terminate the S1 interface 313 towards the RAN 410 (at Figure 4 The S-GW 422 is a RAN-based mobile gateway ("S1-U") and routes data packets between the RAN 410 and the EPC 420. Additionally, the S-GW 422 can be the local mobility anchor for inter-RAN node handovers and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcing certain policies. The S11 reference point between the S-GW 422 and the MME 421 can provide the control plane between the MME 421 and the S-GW 422. The S-GW 422 can be coupled to the P-GW 423 via the S5 reference point.
[0080] The P-GW 423 may terminate the SGi interface towards the PDN 430. The P-GW 423 may communicate with the PDN 430 via the IP interface 325 (see, e.g., Figure 3 ) routes data packets between EPC 420 and external networks such as a network including application server 330 (alternatively referred to as "AF"). In an embodiment, P-GW 423 can communicate via IP communication interface 325 (see, e.g., Figure 3 ) is communicatively coupled to an application server ( Figure 3 Application server 330 or Figure 4430). The S5 reference point between the P-GW 423 and the S-GW 422 may provide user plane tunneling and tunnel management between the P-GW 423 and the S-GW 422. The S5 reference point may also be used for S-GW 422 relocation due to the mobility of the UE 401 and whether the S-GW 422 needs to connect to a non-collocated P-GW 423 for the required PDN connectivity. The P-GW 423 may also include nodes for policy enforcement and charging data collection, such as a PCEF (not shown). Additionally, the SGi reference point between the P-GW 423 and the packet data network (PDN) 430 may be an operator external public, private PDN, or an intra-operator packet data network, for example, for providing IMS services. The P-GW 423 may be coupled to the PCRF 426 via a Gx reference point.
[0081] PCRF 426 is the policy and charging control element of EPC 420. In a non-roaming scenario, a single PCRF 426 may exist in the Home Public Land Mobile Network (HPLMN) associated with UE 401's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, two PCRFs may be associated with UE 401's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 426 may be communicatively coupled to application server 430 via P-GW 423. Application server 430 may signal PCRF 426 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 426 may configure the rules to a PCEF (not shown) with the appropriate TFT and QCI, which initiates QoS and charging as specified by application server 430. The Gx reference point between PCRF 426 and P-GW 423 may allow for the transfer of QoS policies and charging rules from PCRF 426 to PCEF in P-GW 423. The Rx reference point may reside between PDN 430 (or "AF 430") and PCRF 426.
[0082] Figure 5The architecture of a system 500 including a second CN 520 according to various embodiments is shown. The system 500 is shown to include a UE 501, which may be the same as or similar to the previously discussed UE 301 and UE 401; an (R)AN 510, which may be the same as or similar to the previously discussed RAN 310 and RAN 410, and may include the previously discussed RAN node 311; and a DN 503, which may be, for example, an operator service, internet access, or a third-party service; and a 5GC 520. The 5GC 520 may include an AUSF 522; an AMF 521; an SMF 524; an NEF 523; a PCF 526; an NRF 525; an UDM 527; an AF 528; an UPF 502; and an NSSF 529.
[0083] The UPF 502 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 503, and a branching point to support multi-homed PDU sessions. The UPF 502 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, perform lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 502 may include an uplink classifier to support routing traffic flows to the data network. The DN 503 may represent various network operator services, internet access, or third-party services. The DN 503 may include or be similar to the application server 330 discussed previously. The UPF 502 may interact with the SMF 524 via the N4 reference point between the SMF 524 and the UPF 502.
[0084] The AUSF 522 may store data used for authentication of the UE 501 and handle authentication-related functions. The AUSF 522 may facilitate a common authentication framework for various access types. The AUSF 522 may communicate with the AMF 521 via the N12 reference point between the AMF 521 and the AUSF 522; and may communicate with the UDM 527 via the N13 reference point between the UDM 527 and the AUSF 522. In addition, the AUSF 522 may present an interface based on the NAUSF service.
[0085] The AMF 521 may be responsible for registration management (e.g., registering the UE 501, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. The AMF 521 may be the termination point of the N11 reference point between the AMF 521 and the SMF 524. The AMF 521 may provide transport for SM messages between the UE 501 and the SMF 524 and act as a transparent proxy for routing SM messages. The AMF 521 may also provide a communication channel between the UE 501 and the SMSF ( Figure 5 501). The AMF 521 may act as a SEAF, which may include interaction with the AUSF 522 and the UE 501, receiving intermediate keys established as a result of the UE 501 authentication process. In the case of using USIM-based authentication, the AMF 521 may retrieve security material from the AUSF 522. The AMF 521 may also include an SCM function that receives keys for deriving access network specific keys from the SEA. In addition, the AMF 521 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the (R)AN 510 and the AMF 521; and the AMF 521 may be the termination point of NAS (N1) signaling, and perform NAS encryption and integrity protection.
[0086] The AMF 521 may also support NAS signaling with the UE 501 over the N3 IWF interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R)AN 510 and the AMF 521 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 510 and the UPF 502 for the user plane. Thus, the AMF 521 may process N2 signaling for PDU sessions and QoS from the SMF 524 and the AMF 521, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account the QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 501 and the AMF 521 via the N1 reference point between the UE 501 and the AMF 521, and relay uplink and downlink user plane packets between the UE 501 and the UPF 502. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 501. The AMF 521 may present an interface based on Namf services and may be an N14 reference point between two AMFs 521 and an N14 reference point between the AMF 521 and the 5G-EIR ( Figure 5 The termination point of the N17 reference point between the two reference points (not shown).
[0087] UE 501 may need to register with AMF 521 in order to receive network services. RM is used to register UE 501 with the network (e.g., AMF 521) or deregister the UE and establish a UE context in the network (e.g., AMF 521). UE 501 may operate in RM-REGISTERED state or RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 501 is not registered with the network, and the UE context in AMF 521 does not maintain valid location or routing information of UE 501, so AMF 521 cannot reach UE 501. In the RM-REGISTERED state, UE 501 is registered with the network, and the UE context in AMF 521 may maintain valid location or routing information of UE 501, so AMF 521 can reach UE 501. In the RM-REGISTERED state, UE 501 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to inform the network that UE 501 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.
[0088] The AMF 521 may store one or more RM contexts for the UE 501, where each RM context is associated with a specific access to the network. The RM context may be a data structure, a database object, or the like that indicates or stores, among other things, the registration status and periodic update timer for each access type. The AMF 521 may also store a 5GC MM context that may be the same as or similar to the (E)MM context discussed previously. In various embodiments, the AMF 521 may store the CE Mode B restriction parameters for the UE 501 in the associated MM context or RM context. The AMF 521 may also derive values from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.
[0089] The CM can be used to establish and release a signaling connection between the UE 501 and the AMF 521 over the N1 interface. The signaling connection is used to enable NAS signaling exchanges between the UE 501 and the CN 520, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and the UE 501's N2 connection between the AN (e.g., the RAN 510) and the AMF 521. The UE 501 can operate in one of two CM states: CM-IDLE mode or CM-CONNECTED mode. When the UE 501 operates in the CM-IDLE state / mode, the UE 501 may not have a NAS signaling connection established with the AMF 521 over the N1 interface, and a (R)AN 510 signaling connection (e.g., an N2 and / or N3 connection) may exist for the UE 501. When the UE 501 operates in the CM-CONNECTED state / mode, the UE 501 may have a NAS signaling connection established with the AMF 521 through the N1 interface, and there may be a (R)AN 510 signaling connection (e.g., N2 and / or N3 connection) for the UE 501. Establishing an N2 connection between the (R)AN 510 and the AMF 521 may cause the UE 501 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 510 and the AMF 521 is released, the UE 501 may transition from the CM-CONNECTED mode to the CM-IDLE mode.
[0090] The SMF 524 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring the UPF's traffic steering to route traffic to the correct destination; terminating the interface towards the policy control function; the control portion of policy enforcement and QoS; lawful interception (for SM events and interfaces with the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 501 and the data network (DN) 503 identified by a data network name (DNN). A PDU session may be established upon request by UE 501, modified upon request by UE 501 and 5GC 520, and released upon request by UE 501 and 5GC 520 using NAS SM signaling exchanged between UE 501 and SMF 524 over the N1 reference point. Upon request from an application server, 5GC 520 may trigger a specific application in UE 501. In response to receiving the trigger message, UE 501 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 501. The identified applications in UE 501 may establish a PDU session to a specific DNN. SMF 524 may check whether the UE 501 request complies with user subscription information associated with UE 501. In this regard, SMF 524 may retrieve and / or request to receive update notifications regarding SMF 524-level subscription data from UDM 527.
[0091] The SMF 524 may include the following roaming functions: handling local execution to apply QoS SLAs (VPLMN); charging data collection and billing interfaces (VPLMN); lawful interception (for SM events and interfaces with LI systems, in VPLMN); and support for interaction with external DNs to transport signaling for PDU session authorization / authentication through external DNs. In roaming scenarios, an N16 reference point between two SMFs 524 may be included in the system 500, which may be located between an SMF 524 in a visited network and another SMF 524 in a home network. In addition, the SMF 524 may present an interface based on Nsmf services.
[0092] NEF 523 can provide a means for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 528), edge computing or fog computing systems, etc. In such embodiments, NEF 523 can authenticate, authorize, and / or restrict the AF. NEF 523 can also convert information exchanged with AF 528 and information exchanged with internal network functions. For example, NEF 523 can convert between AF service identifiers and internal 5GC information. NEF 523 can also receive information from other network functions (NFs) based on their exposed capabilities. This information can be stored as structured data at NEF 523 or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by NEF 523 to other NFs and AFs and / or used for other purposes such as analysis. In addition, NEF 523 can present an interface based on NNEF services.
[0093] The NRF 525 may support service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to the NF instances. The NRF 525 also maintains information about available NF instances and the services supported by these instances. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of program code. In addition, the NRF 525 may present an interface based on Nnrf services.
[0094] The PCF 526 can provide control plane functions for enforcing their policy rules and can also support a unified policy framework for managing network behavior. The PCF 526 can also implement FEs to access subscription information related to policy decisions in the UDM 527's UDR. The PCF 526 can communicate with the AMF 521 via the N15 reference point between the PCF 526 and the AMF 521, which can include the PCF 526 in the visited network and the AMF 521 in roaming scenarios. The PCF 526 can communicate with the AF 528 via the N5 reference point between the PCF 526 and the AF 528, and with the SMF 524 via the N7 reference point between the PCF 526 and the SMF 524. The system 500 and / or CN 520 can also include an N24 reference point between the PCF 526 (in the home network) and the PCF 526 in the visited network. In addition, the PCF 526 can present an Npcf service-based interface.
[0095] The UDM 527 may process subscription-related information to support network entities in handling communication sessions and may store subscription data for the UE 501. For example, subscription data may be transferred between the UDM 527 and the AMF 521 via the N8 reference point between the UDM 527 and the AMF. The UDM 527 may include two parts: the application FE and the UDR ( Figure 5 FE and UDR are not shown). The UDR can store subscription data and policy data of the UDM 527 and PCF 526, and / or structured data for exposure and application data of the NEF 523 (including PFD for application detection, application request information of multiple UEs 501). An interface based on Nudr service can be presented by the UDR 221 to allow the UDM 527, PCF 526 and NEF 523 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of changes to relevant data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. The UDR can interact with the SMF 524 via the N10 reference point between the UDM 527 and the SMF 524. UDM 527 may also support SMS management, where SMS-FE implements similar application logic discussed previously. Additionally, UDM 527 may present an interface based on Nudm services.
[0096] AF 528 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC 520 and AF 528 to provide information to each other via the NEF 523, which can be used in edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 501 access point to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 502 near the UE 501 and perform traffic steering from the UPF 502 to the DN 503 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 528. In this way, the AF 528 can influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 528 is considered a trusted entity, the network operator may allow the AF 528 to interact directly with the relevant NF. In addition, the AF 528 can present an interface based on the NAF service.
[0097] The NSSF 529 may select a set of network slice instances to serve the UE 501. If required, the NSSF 529 may also determine the allowed NSSAIs and the mapping to the subscribed S-NSSAIs. The NSSF 529 may also determine the set of AMFs to serve the UE 501, or a list of candidate AMFs 521, based on appropriate configuration and possibly by querying the NRF 525. The selection of a set of network slice instances for the UE 501 may be triggered by the AMF 521, where the UE 501 registers by interacting with the NSSF 529, which may result in a change in the AMF 521. The NSSF 529 may interact with the AMF 521 via the N22 reference point between the AMF 521 and the NSSF 529; and may communicate via the N31 reference point ( Figure 5 The NSSF 529 may communicate with another NSSF 529 in the visited network (not shown). In addition, the NSSF 529 may present an interface based on the Nnssf service.
[0098] As previously discussed, CN 520 may include an SMSF that may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 501 to / from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 521 and UDM 527 for notification procedures that UE 501 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 527 when UE 501 is available for SMS).
[0099] CN 120 may also include Figure 5 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF can communicate with UDSF ( Figure 5 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data into or from the UDSF (e.g., UE context). A single NF may share a UDSF for storing its respective unstructured data, or each NF may have its own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on Nudsf services ( Figure 5 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific device / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.
[0100] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 5These interfaces and reference points are omitted. In one example, CN 520 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 421) and an AMF 521, to enable intercommunication between CN 520 and CN 420. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by the 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.
[0101] Figure 6 An example of infrastructure equipment 600 according to various embodiments is shown. Infrastructure equipment 600 (or "system 600") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 311 and / or AP 306 shown and described previously), an application server 330, and / or any other element / device discussed herein. In other examples, system 600 can be implemented in or by a UE.
[0102] System 600 includes application circuitry 605, baseband circuitry 610, one or more radio front-end modules (RFEMs) 615, memory circuitry 620, a power management integrated circuit (PMIC) 625, a power tee circuit 630, a network controller circuit 635, a network interface connector 640, satellite positioning circuitry 645, and a user interface 650. In some embodiments, device 600 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device. For example, the circuitry may be separately included in more than one device for a CRAN, vBBU, or other similar implementation.
[0103] The application circuit 605 includes circuits such as, but not limited to, one or more processors (processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a serial bus. 26 or a general purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general purpose input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 605 can be coupled to or can include a memory / storage element and can be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 600. In some specific implementations, the memory / storage element can be an on-chip memory circuit that can 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.
[0104] The processor of the application circuit 605 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 (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating in accordance with various embodiments herein. As an example, the processor of the application circuit 605 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, the system 600 may not utilize application circuitry 605 and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.
[0105] In some implementations, the application circuit 605 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) and high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 605 may include logic blocks or logic architectures, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such an embodiment, the circuitry of the application circuit 605 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-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in lookup tables (LUTs), etc.
[0106] The baseband circuit 610 may be implemented, for example, as a solder-in 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. Figure 8 The various hardware electronic components of baseband circuitry 610 are discussed.
[0107] The user interface circuit 650 may include one or more user interfaces designed to enable a user to interact with the system 600, or peripheral component interfaces designed to enable peripheral components to interact with the system 600. The user interface may include, but is 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 touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.
[0108] The radio front end module (RFEM) 615 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 8The antenna array 811 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 615 that combines both millimeter wave antennas and sub-millimeter wave antennas.
[0109] The memory circuit 620 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 620 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.
[0110] The PMIC 625 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 630 may provide power drawn from the network cable to provide both power and data connectivity for the infrastructure equipment 600 using a single cable.
[0111] The network controller circuit 635 can provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on GRE tunnels, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity can be provided to / from the infrastructure equipment 600 via the network interface connector 640 using a physical connection, which can be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 635 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0112] The positioning circuit 645 includes circuits for receiving and decoding signals transmitted / broadcasted by the positioning network of the global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc.). The positioning circuit 645 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 645 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 645 may also be part of or interact with the baseband circuit 610 and / or RFEM 615 to communicate with nodes and components of the positioning network. The positioning circuit 645 may also provide location data and / or time data to the application circuit 605, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 311, etc.).
[0113] Figure 6 The components shown may communicate with each other using interface circuitry that 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. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.
[0114] Figure 7 An example of a platform 700 (or "device 700") according to various embodiments is shown. In an embodiment, computer platform 700 may be suitable for use as UE 301, 401, 501, application server 330, and / or any other element / device discussed herein. Platform 700 may include any combination of components shown in the examples. Components of platform 700 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof suitable for use in computer platform 700, or as components otherwise incorporated within the chassis of a larger system. Figure 7The block diagram is intended to show a high-level view of the components of computer platform 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.
[0115] Application circuit 705 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The application circuit 705 may include one or more of a C or general-purpose programmable serial interface module, an RTC, timers (including interval timers and watchdog timers), general-purpose I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 705 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 700. In some specific implementations, the memory / storage element may be an on-chip memory circuit that 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.
[0116] The processor of the application circuit 605 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 DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating according to various embodiments herein.
[0117] As an example, the processor of the application circuit 705 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 705 can be part of a system on a chip (SoC), in which the application circuit 705 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.
[0118] Additionally or alternatively, the application circuit 705 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of the application circuit 705 may include logic blocks or logic fabrics, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 705 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), antifuse), and the like) for storing logic blocks, logic fabrics, data, and the like in lookup tables (LUTs) and the like.
[0119] The baseband circuit 710 may be implemented, for example, as a solder-in 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. Figure 8 The various hardware electronic components of baseband circuit 710 are discussed.
[0120] The RFEM 715 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 8 The antenna array 811 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 715, which combines both millimeter-wave antennas and sub-millimeter-wave antennas.
[0121] Memory circuit 720 may include any number and type of memory devices used to provide a fixed amount of system memory. For example, memory circuit 720 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), and the like. Memory circuit 720 may be developed according to Joint Electron Device Engineering Council (JEDEC) low-power double data rate (LPDDR)-based designs, such as LPDDR2, LPDDR3, and LPDDR4. Memory circuit 720 may be implemented as one or more of the following: a solder-in packaged integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 720 may be an on-chip memory or register associated with the application circuit 705. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 720 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 700 may be combined with and Three-dimensional (3D) cross-point (XPOINT) memory.
[0122] Removable memory circuitry 723 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 700. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.
[0123] Platform 700 may also include an interface circuit (not shown) for connecting external devices to platform 700. External devices connected to platform 700 via the interface circuit include sensor circuit 721 and electromechanical components (EMC) 722, as well as a removable memory device coupled to removable memory circuit 723.
[0124] Sensor circuitry 721 comprises a device, module, or subsystem whose purpose is to detect events or changes in its environment and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a fluid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.
[0125] The EMC 722 includes devices, modules, or subsystems designed to enable the platform 700 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. In addition, the EMC 722 can be configured to generate messages / signaling and send messages / signaling to other components of the platform 700 to indicate the current state of the EMC 722. Examples of EMC 722 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, the platform 700 is configured to operate one or more EMCs 722 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.
[0126] In some implementations, the interface circuitry may connect the platform 700 to the positioning circuitry 745. The positioning circuitry 745 includes circuitry for receiving and decoding signals transmitted / broadcasted by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.). The positioning circuitry 745 includes various hardware components (e.g., including hardware devices for facilitating over-the-air (OTA) communications, such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network, such as nodes of the navigation satellite constellation. In some embodiments, the positioning circuitry 745 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuitry 745 may also be part of or interact with the baseband circuitry 610 and / or RFEM 715 to communicate with nodes and components of the positioning network. Positioning circuitry 745 may also provide position data and / or time data to application circuitry 705 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.
[0127] In some implementations, the interface circuitry may connect the platform 700 to a near-field communication (NFC) circuitry 740. The NFC circuitry 740 is configured to provide contactless, short-range communication based on the radio frequency identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuitry 740 and an NFC-enabled device (e.g., an "NFC touchpoint") external to the platform 700. The NFC circuitry 740 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuitry 740 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 transmit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuitry 740, or initiate data transfer between the NFC circuitry 740 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) in close proximity to the platform 700.
[0128] Driver circuitry 746 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to platform 700. Driver circuitry 746 may include various drivers to allow other components of platform 700 to interact with or control various input / output (I / O) devices that may be present within or connected to platform 700. For example, driver circuitry 746 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface of platform 700, a sensor driver for acquiring sensor readings from sensor circuitry 721 and controlling and enabling access to sensor circuitry 721, an EMC driver for acquiring actuator positions of EMC 722 and / or controlling and enabling access to EMC 722, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.
[0129] A power management integrated circuit (PMIC) 725 (also referred to as "power management circuit 725") can manage the power provided to various components of the platform 700. Specifically, the PMIC 725 can control power source selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 710. When the platform 700 is capable of being powered by a battery 730, for example, when the device is included in a UE 301, 401, or 501, the PMIC 725 is typically included.
[0130] In some embodiments, the PMIC 725 may control or otherwise be part of various power-saving mechanisms of the platform 700. For example, if the platform 700 is in the RRC_Connected state, where the device remains connected to the RAN node because it expects to receive traffic immediately, after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the platform 700 may be powered down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 700 may transition to the RRC_Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The platform 700 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network, and then powers down again. The platform 700 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can prevent the device from using the network for periods exceeding the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will incur significant delays, assuming that the delay is acceptable.
[0131] Battery 730 can power platform 700, but in some examples, platform 700 can be installed in a fixed location and can have a power source coupled to the power grid. Battery 730 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, battery 730 can be a typical lead-acid automobile battery.
[0132] In some implementations, the battery 730 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 700 to track the state of charge (SoCh) of the battery 730. The BMS may be used to monitor other parameters of the battery 730, such as the state of health (SoH) and state of function (SoF) of the battery 730 to provide fault prediction. The BMS may transmit information about the battery 730 to the application circuit 705 or other components of the platform 700. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 705 to directly monitor the voltage of the battery 730 or the current from the battery 730. The battery parameters may be used to determine actions that the platform 700 may perform, such as transmission frequency, network operation, sensing frequency, etc.
[0133] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 730. In some examples, the power block 730 can be replaced with a wireless power receiver to wirelessly obtain power, for example, via a loop antenna in the computer platform 700. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 730 and, therefore, the required current. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Consortium, or the Rezence charging standard published by the Wireless Power Consortium.
[0134] The user interface circuit 750 includes various input / output (I / O) devices present in or connected to the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and / or peripheral component interfaces designed to enable interaction between peripheral components and the platform 700. The user interface circuit 750 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), wherein the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the platform 700. The output device circuitry may also include a speaker or other audio emitting device, a printer, etc. In some embodiments, the sensor circuitry 721 may function as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may function as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power port, etc.
[0135] Although not shown, the components of platform 700 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.
[0136] Figure 8 Exemplary components of a baseband circuit 810 and a radio front end module (RFEM) 815 are shown according to various embodiments. The baseband circuit 810 corresponds to Figure 6 The baseband circuit 610 and Figure 7 Baseband circuit 710. RFEM 815 corresponds to Figure 6 RFEM 615 and Figure 7 RFEM 715. As shown, RFEM 815 may include radio frequency (RF) circuitry 806, front end module (FEM) circuitry 808, and an antenna array 811 coupled together at least as shown.
[0137] The baseband circuitry 810 includes circuitry and / or control logic configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuitry 806. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 810 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 810 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other embodiments. The baseband circuitry 810 is configured to process baseband signals received from the receive signal path of the RF circuitry 806 and to generate baseband signals for the transmit signal path of the RF circuitry 806. The baseband circuitry 810 is configured to communicate with the application circuitry 605 / 705 (see Figure 6 and Figure 7 ) are connected to generate and process baseband signals and control the operation of RF circuit 806. Baseband circuit 810 can handle various radio control functions.
[0138] The aforementioned circuits and / or control logic components of the baseband circuitry 810 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 804A, a 4G / LTE baseband processor 804B, a 5G / NR baseband processor 804C, or some other baseband processor 804D for other existing, developing, or future generations (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 804A to 804D may be included in modules stored in the memory 804G and executed via the central processing unit (CPU) 804E. In other embodiments, some or all of the functions of the baseband processors 804A to 804D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 804G may store program code for a real-time OS (RTOS) that, when executed by the CPU 804E (or other baseband processor), enables the CPU 804E (or other baseband processor) to manage resources of the baseband circuit 810, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-TimeExecutive (VRTX) provided by Express ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) The baseband circuit 810 may include one or more audio digital signal processors (DSPs) 804F. The audio DSPs 804F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.
[0139] In some embodiments, each of processors 804A to 804E includes a corresponding memory interface to send data to / receive data from memory 804G. Baseband circuit 810 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 810; an interface for sending data to / receiving data from a memory external to baseband circuit 810; Figures 6 to 8Application circuit interface for sending data to / receiving data from the application circuit 605 / 705; Figure 8 RF circuit 806 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / from the PMIC 725.
[0140] In an alternative embodiment (which may be combined with the above embodiment), the baseband circuit 810 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem via an interconnect subsystem. The digital baseband subsystem 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, a point-to-point connection, a network on chip (NOC) structure, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 810 may include a protocol processing circuit having one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., a radio front-end module 815).
[0141] although Figure 8Although not shown, in some embodiments, the baseband circuitry 810 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuitry 810 and / or the RF circuitry 806 are part of millimeter wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuitry 810 and / or the RF circuitry 806 are part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In the second example, the protocol processing circuitry will operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 804G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 810 may also support radio communications for more than one wireless protocol.
[0142] The various hardware elements of the baseband circuit 810 discussed herein may be implemented as, for example, a solder-in substrate comprising one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In one example, the components of the baseband circuit 810 may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In another example, some or all of the components of the baseband circuit 810 and the RF circuit 806 may be implemented together, such as, for example, a system on a chip (SoC) or a system-in-package (SiP). In another example, some or all of the components of the baseband circuit 810 may be implemented as a separate SoC communicatively coupled to the RF circuit 806 (or multiple instances of the RF circuit 806). In yet another example, some or all of the components of the baseband circuit 810 and the application circuit 605 / 705 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").
[0143] In some embodiments, the baseband circuitry 810 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 810 can support communications with E-UTRAN or other WMANs, WLANs, or WPANs. Embodiments in which the baseband circuitry 810 is configured to support radio communications using more than one wireless protocol may be referred to as multi-mode baseband circuitry.
[0144] RF circuitry 806 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 806 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 806 can include a receive signal path that can include circuitry for down-converting RF signals received from FEM circuitry 808 and providing baseband signals to baseband circuitry 810. RF circuitry 806 can also include a transmit signal path that can include circuitry for up-converting baseband signals provided by baseband circuitry 810 and providing an RF output signal to FEM circuitry 808 for transmission.
[0145] In some embodiments, the receive signal path of RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b, and filter circuitry 806c. In some embodiments, the transmit signal path of RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a. RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing frequencies used by mixer circuitry 806a in the receive and transmit signal paths. In some embodiments, mixer circuitry 806a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d. Amplifier circuitry 806b may be configured to amplify the downconverted signal, and filter circuitry 806c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 810 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 806a of the receive signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.
[0146] In some embodiments, mixer circuit 806a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 806d to generate an RF output signal for FEM circuit 808. The baseband signal can be provided by baseband circuit 810 and can be filtered by filter circuit 806c.
[0147] In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature down conversion and quadrature up conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down conversion and direct up conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.
[0148] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 810 may include a digital baseband interface to communicate with RF circuitry 806.
[0149] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.
[0150] In some embodiments, synthesizer circuit 806 d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 806 d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.
[0151] Synthesizer circuit 806d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 806a of RF circuit 806. In some embodiments, synthesizer circuit 806d may be a fractional-N / N+1 synthesizer.
[0152] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuitry 810 or the application circuitry 605 / 705 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuitry 605 / 705.
[0153] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0154] In some embodiments, the synthesizer circuit 806d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 806 can include an IQ / polarity converter.
[0155] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 811, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission by one or more antenna elements in the antenna array 811. In various embodiments, amplification by the transmit or receive signal path may be performed only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.
[0156] In some embodiments, the FEM circuitry 808 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 808 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuitry 806), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 811.
[0157] The antenna array 811 includes one or more antenna elements, each configured to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals. For example, a digital baseband signal provided by the baseband circuit 810 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 811, which includes one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can be formed into various arrangements as known and / or discussed herein. The antenna array 811 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. The antenna array 811 can be formed as patches of metal foil of various shapes (e.g., patch antennas) and can be coupled to the RF circuitry 806 and / or the FEM circuitry 808 using metal transmission lines, etc.
[0158] The processors of the application circuitry 605 / 705 and the processors of the baseband circuitry 810 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 810 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processors of the application circuitry 605 / 705 may utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which is described in further detail below. As mentioned herein, layer 2 may include the MAC layer, the RLC layer, and the PDCP layer, which are described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which is described in further detail below.
[0159] Figure 9 1 shows various protocol functions that may be implemented in a wireless communication device according to some embodiments. Specifically, Figure 9 The present invention includes an arrangement 900 showing the interconnection between various protocol layers / entities. The present invention provides various protocol layers / entities for operating in conjunction with the 5G / NR system standard and the LTE system standard. Figure 9The following description, but Figure 9 Some or all aspects of the present invention may also be applicable to other wireless communication network systems.
[0160] In addition to other higher layer functions not shown, the protocol layers of arrangement 900 may include one or more of PHY 910, MAC 920, RLC 930, PDCP 940, SDAP 947, RRC 955, and NAS layer 957. These protocol layers may include one or more service access points (e.g., Figure 9 Items 959, 956, 950, 949, 945, 935, 925, and 915), the one or more service access points may provide communication between two or more protocol layers.
[0161] PHY 910 can transmit and receive physical layer signals 905, which can be received from or transmitted to one or more other communication devices. Physical layer signals 905 may include one or more physical channels, such as those discussed herein. PHY 910 may also 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 (e.g., RRC 955). PHY 910 may also further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In an embodiment, an instance of PHY 910 may process a request from an instance of MAC 920 via one or more PHY-SAP 915 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 915 may include one or more transport channels.
[0162] An instance of MAC 920 may process requests from an instance of RLC 930 via one or more MAC-SAPs 925 and provide instructions thereto. These requests and instructions transmitted via MAC-SAP 925 may include one or more logical channels. MAC 920 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 910 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 910 via transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.
[0163] Instances of RLC 930 may process requests from instances of PDCP 940 via one or more Radio Link Control Service Access Points (RLC-SAPs) 935 and provide indications thereto. These requests and indications transmitted via RLC-SAPs 935 may include one or more RLC channels. RLC 930 may operate in multiple modes of operation, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC 930 may perform transmission of upper layer protocol data units (PDUs), error correction via Automatic Repeat Request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 930 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.
[0164] An instance of PDCP 940 may process requests from an instance of RRC 955 and / or an instance of SDAP 947 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAPs) 945 and provide instructions thereto. These requests and instructions conveyed via PDCP-SAP 945 may include one or more radio bearers. PDCP 940 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), enforce in-sequence delivery of upper layer PDUs upon lower layer reestablishment, eliminate duplication of lower layer SDUs upon lower layer reestablishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).
[0165] An instance of SDAP 947 can process requests from one or more higher layer protocol entities via one or more SDAP-SAPs 949 and provide instructions thereto. These requests and instructions transmitted via SDAP-SAP 949 may include one or more QoS flows. SDAP 947 can map QoS flows to DRBs and vice versa, and can also mark the QFI in DL and UL packets. A single SDAP entity 947 can be configured for a separate PDU session. In the UL direction, NG-RAN 310 can control the mapping of QoS flows to DRBs in two different ways: reflective mapping or explicit mapping. For reflective mapping, the SDAP 947 of UE 301 can monitor the QFI of the DL packets of each DRB and apply the same mapping to packets flowing in the UL direction. For a DRB, the SDAP 947 of UE 301 can map the UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflective mapping, the NG-RAN 510 may tag DL packets with a QoS flow ID over the Uu interface. Explicit mapping may involve the RRC 955 configuring the SDAP 947 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by the SDAP 947. In an embodiment, the SDAP 947 may be used only in NR implementations and may not be used in LTE implementations.
[0166] The RRC 955 may configure aspects of one or more protocol layers, which may include one or more instances of the PHY 910, MAC 920, RLC 930, PDCP 940, and SDAP 947, via one or more Management Service Access Points (M-SAPs). In an embodiment, instances of the RRC 955 may process requests from and provide instructions to one or more NAS entities 957 via one or more RRC-SAPs 956. Primary services and functions of the RRC 955 may include broadcasting of system information (e.g., included in a MIB or SIB related to the NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of the RRC connection between the UE 301 and the 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. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.
[0167] The NAS 957 may form the highest layer of the control plane between the UE 301 and the AMF 521. The NAS 957 may support the mobility and session management procedures of the UE 301 to establish and maintain an IP connection between the UE 301 and the P-GW in the LTE system.
[0168] According to various embodiments, one or more protocol entities of arrangement 900 may be implemented in UE 301, RAN node 311, AMF 521 in NR implementations or MME 421 in LTE implementations, UPF 502 in NR implementations or S-GW 422 and P-GW 423 in LTE implementations, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 301, gNB 311, AMF 521, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 311 may host the RRC 955, SDAP 947, and PDCP 940 of the gNB that control the operation of one or more gNB-DUs, and the gNB-DUs of gNB 311 may each host the RLC 930, MAC 920, and PHY 910 of gNB 311.
[0169] In a first example, the control plane protocol stack may include, in order from highest layer to lowest layer, NAS 957, RRC 955, PDCP 940, RLC 930, MAC 920, and PHY 910. In this example, upper layers 960 may be built on top of NAS 957, including an IP layer 961, SCTP 962, and an application layer signaling protocol (AP) 963.
[0170] In an NR implementation, the AP 963 may be an NG application protocol layer (NGAP or NG-AP) 963 for the NG interface 313 defined between the NG-RAN node 311 and the AMF 521, or the AP 963 may be an Xn application protocol layer (XnAP or Xn-AP) 963 for the Xn interface 312 defined between two or more RAN nodes 311.
[0171] The NG-AP 963 may support the functionality of the NG interface 313 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 311 and the AMF 521. NG-AP 963 services may include two groups: UE-associated services (e.g., services related to the UE 301) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 311 and the AMF 521). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 311 involved in a specific paging area; a UE context management function for allowing the AMF 521 to establish, modify and / or release the UE context in the AMF 521 and the NG-RAN node 311; a mobility function for the UE 301 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; an NG interface management function for setting up the NG interface and monitoring errors over the NG interface; a warning message sending function for providing a means to transfer a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signalling transport function for transferring or rerouting NAS messages between the UE 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; a ... 320 Configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 311; and / or other similar functions.
[0172] The XnAP 963 may support the functions of the Xn interface 312 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 311 (or E-UTRAN 410), such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, and procedures related to dual connectivity. The XnAP global procedures may include procedures unrelated to a specific UE 301, such as Xn interface setup and reset procedures, NG-RAN update procedures, and cell activation procedures.
[0173] In an LTE implementation, the AP 963 may be an S1 application protocol layer (S1-AP) 963 for the S1 interface 313 defined between the E-UTRAN node 311 and the MME, or the AP 963 may be an X2 application protocol layer (X2AP or X2-AP) 963 for the X2 interface 312 defined between two or more E-UTRAN nodes 311.
[0174] The S1 application protocol layer (S1-AP) 963 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be the interaction unit between the E-UTRAN node 311 and the MME 421 within the LTE CN 320. S1-AP 963 services may include 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, RAN Information Management (RIM), and configuration transfer.
[0175] The X2AP 963 may support the functionality of the X2 interface 312 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures for handling 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, and procedures related to dual connectivity. The X2AP global procedures may include procedures unrelated to a specific UE 301, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, and cell activation procedures.
[0176] The SCTP layer (alternatively referred to as the SCTP / IP layer) 962 can 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). SCTP 962 can ensure reliable delivery of signaling messages between the RAN node 311 and the AMF 521 / MME 421 based in part on the IP protocol supported by IP 961. The Internet Protocol layer (IP) 961 can be used to perform packet addressing and routing functions. In some implementations, the IP layer 961 can use point-to-point transport to deliver and transmit PDUs. In this regard, the RAN node 311 can include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.
[0177] In a second example, the user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 947, PDCP 940, RLC 930, MAC 920, and PHY 910. The user plane protocol stack may be used for communication between UE 301, RAN node 311, and UPF 502 in an NR implementation, or for communication between S-GW 422 and P-GW 423 in an LTE implementation. In this example, upper layers 951 may be built on top of SDAP 947 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 952, a general packet radio service (GPRS) tunneling protocol layer (GTP-U) for the user plane 953, and a user plane PDU layer (UP PDU) 963.
[0178] The transport network layer 954 (also referred to as the "transport layer") can be built on top of the IP transport, and the GTP-U 953 can be used on top of the UDP / IP layer 952 (including the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.
[0179] GTP-U 953 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 952 can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data flows. The RAN node 311 and the S-GW 422 can exchange user plane data using the S1-U interface via a protocol stack including the L1 layer (e.g., PHY 910), the L2 layer (e.g., MAC 920, RLC 930, PDCP 940, and / or SDAP 947), the UDP / IP layer 952, and the GTP-U 953. The S-GW 422 and the P-GW 423 can exchange user plane data using the S5 / S8a interface via a protocol stack including the L1 layer, the L2 layer, the UDP / IP layer 952, and the GTP-U 953. As previously discussed, the NAS protocol may support mobility and session management procedures of the UE 301 to establish and maintain an IP connection between the UE 301 and the P-GW 423 .
[0180] In addition, despite Figure 9Not shown, an application layer may exist above the AP 963 and / or transport network layer 954. The application layer may be the layer where a user of the UE 301, RAN node 311, or other network element interacts with a software application, for example, executed by the application circuitry 605 or the application circuitry 705, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system of the UE 301 or RAN node 311, such as the baseband circuitry 810. In some implementations, the IP layer and / or the application layer may provide functionality that is the same as or similar to layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).
[0181] Figure 10 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 10 A schematic diagram of hardware resources 1000 is shown, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices / subslices to utilize the hardware resources 1000.
[0182] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 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.
[0183] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0184] The communication resources 1030 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via the network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, (or Low power consumption) components, components and other communication components.
[0185] The instructions 1050 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 1010 to perform any one or more of the methodologies discussed herein. The instructions 1050 may reside entirely or partially within at least one of the processors 1010 (e.g., within a cache memory of the processor), the memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.
[0186] Exemplary Process
[0187] In some embodiments, Figures 3 to 10 The electronic devices, networks, systems, chips or components or portions thereof or specific implementations in some other figures herein may be configured to perform one or more processes, techniques or methods described herein or portions thereof. Figure 11 One such process is depicted in . In some embodiments, Figure 11 A flowchart 1100 is shown that describes an electronic device, such as a client 104 and / or UE 301, 401, 501, 700, for use in a wireless network for compressing and decompressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, Figure 11 A flowchart 1100 is shown that describes an electronic device for use in a wireless network, such as an access node 106 and / or a RAN 311a, 311b, 600, for compressing and decompressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, the flowchart 1100 may be executed by a processor or processor circuit (including a processor circuit) described in various embodiments herein. Figure 10 The processor and / or Figures 6 and 7 The application circuit 605 or 705 and / or the baseband circuit 610 or 710 shown are executed or controlled.
[0188] At 1102, an ICN name or ICN common field in a packet is compressed or decompressed. In some embodiments, the name may be included in (or otherwise become part of) the ICN common field. At 1104, the packet including the compressed ICN name or compressed ICN field is provided to a lower layer for over-the-air transmission. Additionally or alternatively, step 1104 may include providing the decompressed ICN name or decompressed ICN field to a higher layer. Figure 12 and Figure 13 Steps 1102 and 1104 are further discussed in more detail.
[0189] The process 1100 may be performed at a PDCP layer (e.g., PDCP 940). Thus, a higher layer may refer to any layer above PDCP 940 (e.g., RRC 955, SDAP 947, etc.), such as Figure 9 In contrast, a lower layer may refer to any layer below the PDCP 940 (e.g., RLC 930), as shown. Figure 9 shown.
[0190] In some embodiments, process 1100 may be performed by a client 104 (e.g., a UE) or an AN 106 (e.g., an eNB / gNB) for over-the-air transmission in a cellular network.
[0191] If the process 1100 is performed by the client 104, the process may include compressing the packet and providing it to a lower layer, and the packet may be an interest packet. Alternatively, the process 1100 may include decompressing the packet and providing it to a higher layer, and the packet may be a data packet.
[0192] If the process 1100 is performed by the AN 106, the process may include compressing the packet and providing it to a lower layer, and the packet may be a data packet. Alternatively, the process 1100 may include decompressing the packet and providing it to a higher layer, and the packet may be an interest packet.
[0193] In some embodiments, Figures 3 to 10 The electronic devices, networks, systems, chips or components or portions thereof or specific implementations in some other figures herein may be configured to perform one or more processes, techniques or methods described herein or portions thereof. Figure 12 One such process is depicted in . In some embodiments, Figure 12A flowchart 1200 is shown that describes an electronic device, such as a client 104 and / or UE 301, 401, 501, 700, for use in a wireless network for compressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, Figure 12 A flowchart 1200 is shown that describes an electronic device for use in a wireless network, such as an access node 106 and / or a RAN 311a, 311b, 600, for compressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, the flowchart 1200 may be executed by a processor or processor circuit (including a processor circuit) described in various embodiments herein. Figure 10 The processor and / or Figures 6 and 7 The application circuit 605 or 705 and / or the baseband circuit 610 or 710 shown are executed or controlled.
[0194] At 1202, a first Information Centric Network (ICN) packet including an ICN name or an ICN common field is received. For example, an electronic device (e.g., a UE or an access node) receives the first ICN packet including the ICN name or the ICN common field. According to some examples, the electronic device is a user equipment (UE), and the UE is configured to receive the first ICN packet (e.g., an ICN interest packet) from an upper protocol layer. Additionally or alternatively, the electronic device is an access node (AN), and the AN is configured to receive the first ICN packet (e.g., an ICN data packet) from a source device or an ICN router.
[0195] At 1204, the ICN name or ICN common field is compressed at a Packet Data Convergence Protocol (PDCP) layer. For example, the electronic device compresses the ICN name or ICN common field at the PDCP layer. According to some embodiments, the electronic device is configured to compress the ICN name or ICN common field based on one or more ICN compression parameters received using an information element (IE). Additionally or alternatively, the electronic device is configured to compress the ICN name based on a predetermined mapping between the ICN name and a compression value. In some examples, the electronic device may compare the size of the second ICN packet to a threshold value and compress the ICN name or ICN common field in response to the size of the second ICN packet being greater than the threshold value.
[0196] At 1206, the compressed ICN name or the compressed ICN common field is provided to a lower protocol layer. For example, the electronic device provides the compressed ICN name or the compressed ICN common field to a lower protocol layer for over-the-air transmission.
[0197] At 1208, a second ICN packet including the compressed ICN name or the compressed ICN common field is transmitted. For example, the electronic device may transmit the second ICN packet. In some examples where the electronic device is a user equipment (UE), the UE may transmit the second ICN packet to an access node (AN). In some examples where the electronic device is an access node (AN), the AN may transmit the second ICN packet to the UE.
[0198] In some embodiments, Figures 3 to 10 The electronic devices, networks, systems, chips or components or portions thereof or specific implementations in some other figures herein may be configured to perform one or more processes, techniques or methods described herein or portions thereof. Figure 13 One such process is depicted in . In some embodiments, Figure 13 A flowchart 1300 is shown that describes an electronic device, such as a client 104 and / or UE 301, 401, 501, 700, for use in a wireless network for decompressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, Figure 13 A flowchart 1300 is shown that describes an electronic device for use in a wireless network, such as an access node 106 and / or a RAN 311a, 311b, 600, for compressing an Information Centric Network (ICN) name and / or an ICN common field at a Packet Data Convergence Protocol (PDCP) layer, according to an embodiment of the present disclosure. In some embodiments, the flowchart 1300 may be executed by a processor or processor circuit (including a processor circuit) described in various embodiments herein. Figure 10 The processor and / or Figures 6 and 7 The application circuit 605 or 705 and / or the baseband circuit 610 or 710 shown are executed or controlled.
[0199] At 1302, a first Information Centric Network (ICN) packet including at least one of a compressed ICN name or a compressed ICN common field is received. For example, the electronic device receives the first ICN packet. According to some examples, the electronic device is a user equipment (UE), and the UE is configured to receive the first ICN packet (e.g., an ICN data packet) from an access node (AN). Additionally or alternatively, the electronic device is an access node (AN), and the AN is configured to receive the first ICN packet (e.g., an ICN interest packet) from the user equipment (UE).
[0200] At 1304, the compressed ICN name or the compressed ICN common field is decompressed at a Packet Data Convergence Protocol (PDCP) layer. For example, the electronic device decompresses the compressed ICN name or the compressed ICN common field at the PDCP layer. According to some embodiments, the electronic device is configured to decompress the compressed ICN name or the compressed ICN common field based on one or more ICN compression parameters received using an Information Element (IE). Additionally or alternatively, the electronic device is configured to decompress the compressed ICN name based on a predetermined mapping between the ICN name and the compression value.
[0201] At 1306, the decompressed ICN name or the decompressed ICN public field is provided to a higher protocol layer. For example, the electronic device provides the decompressed ICN name or the decompressed ICN public field to a higher protocol layer.
[0202] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Examples section.
[0203] Example
[0204] Embodiment 1 may include a method for Information Centric Network (ICN) name compression / decompression for the PDCP layer.
[0205] Embodiment 2 may include a method of compressing / decompressing ICN common fields (eg, Name, GenericNameComponent, ImplicitSha256DigestComponent, and ParametersSha256DigestComponent) at or for the PDCP layer.
[0206] Embodiment 3 may comprise a method comprising compressing the ICN name at the PDCP layer using a mapping.
[0207] Embodiment 4 may include a method comprising compressing an ICN name at an ICN layer and passing the information to a PDCP layer.
[0208] Embodiment 5 may comprise a method comprising compressing the ICN common field at the PDCP layer using a mapping.
[0209] Embodiment 6 may include a method comprising compressing the ICN name at (or for) the PDCP layer via an Information Element (IE) PDCP Configuration of RRC.
[0210] Embodiment 7 may include a method comprising compressing an ICN common field at (or for) the PDCP layer via an Information Element (IE) PDCP configuration of RRC.
[0211] Embodiment 8 may include a method comprising compressing ICN common fields at the ICN layer and passing the information to the PDCP layer.
[0212] Example 9 may include a method comprising:
[0213] Receiving an ICN packet having an ICN name or an ICN common field;
[0214] Compressing the ICN name or the ICN common field by an operation at the PDCP layer; and
[0215] The compressed ICN name or ICN common field is provided to lower protocol layers for over-the-air transmission.
[0216] Embodiment 10 may include the method of embodiment 9 or some other embodiment herein, wherein the ICN packet is an ICN interest packet or an ICN data packet.
[0217] Embodiment 11 may include the method of embodiment 9 or some other embodiment herein, further comprising segmenting the ICN packet into a plurality of packets at the PDCP layer.
[0218] Embodiment 12 may include the method according to embodiment 9 or some other embodiment herein, further comprising: receiving configuration information related to one or more ICN compression parameters in an information element; and compressing the ICN name or ICN common field based on the one or more ICN compression parameters.
[0219] Embodiment 13 may include a method according to embodiment 12 or some other embodiment herein, wherein the information element is received via RRC signaling.
[0220] Embodiment 14 may include a method as in embodiment 9 or some other embodiment herein, wherein the compression is based on a predetermined mapping between ICN names and compression values.
[0221] Embodiment 15 may include a method comprising: compressing or decompressing an ICN name or an ICN common field in a packet; and providing the packet to a lower layer or a higher layer.
[0222] Embodiment 16 may include the method of embodiment 15 or some other embodiment herein, wherein the method includes compressing the ICN name or ICN common fields and providing the packet to lower layers for transmission to the access node or UE.
[0223] Embodiment 17 may include the method of embodiment 15 or some other embodiment herein, wherein the method includes decompressing the ICN name or the ICN common field and providing the packet to higher layers of the access node or UE.
[0224] Embodiment 18 may include the method according to embodiment 15 or some other embodiment herein, wherein the method is performed by a PDCP layer of an access node or a UE.
[0225] Embodiment 19 may include a method as described in embodiment 15 or some other embodiment herein, wherein the packet is an interest packet or a data packet.
[0226] Embodiment 20 may include a method comprising: receiving an ICN packet having a compressed ICN name or ICN common field; decompressing the compressed ICN name or ICN common field through a PDCP operation; and providing the decompressed ICN name or ICN common field to a higher protocol layer.
[0227] Embodiment 21 may include a method according to embodiment 20 or some other embodiment herein, wherein the ICN packet is an ICN interest packet or an ICN data packet.
[0228] Embodiment 22 may include a method according to embodiment 20 or some other embodiment herein, further comprising: receiving configuration information related to one or more ICN compression parameters in an information element; and decompressing the ICN name or ICN common field based on the one or more ICN compression parameters.
[0229] Embodiment 23 may include a method according to embodiment 22 or some other embodiment herein, wherein the information element is received via RRC signaling.
[0230] Embodiment 24 may include a method as in embodiment 20 or some other embodiment herein, wherein the decompression is based on a predetermined mapping between ICN names and compressed values.
[0231] Embodiment Z01 may comprise an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 24, or any other method or process described herein.
[0232] Embodiment Z02 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of embodiments 1 to 24 or any other method or process described herein.
[0233] Embodiment Z03 may comprise an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 24, or any other method or process described herein.
[0234] Embodiment Z04 may include the methods, techniques, or processes described in or related to any one of Embodiments 1 to 24, or portions or components thereof.
[0235] Embodiment Z05 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of Embodiments 1 to 24, or a portion thereof.
[0236] Embodiment Z06 may include a signal as described in or related to any one of Embodiments 1 to 24, or a portion or component thereof.
[0237] Embodiment Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message as described or associated with any one of embodiments 1 to 24, or a portion or component thereof, or as otherwise described in this disclosure.
[0238] Embodiment Z08 may include a signal encoded with data as described in or associated with any one of Embodiments 1 to 24, or a portion or component thereof, or as otherwise described in this disclosure.
[0239] Embodiment Z09 may include a signal encoding a datagram, packet, frame, segment, protocol data unit (PDU) or message as described in or associated with any of embodiments 1 to 24, or a portion or component thereof, or otherwise described in this disclosure.
[0240] Embodiment Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described in or related to any one of embodiments 1 to 24, or a portion thereof.
[0241] Embodiment Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of embodiments 1 to 24, or a portion thereof.
[0242] Embodiment Z12 may include signals in a wireless network as shown and described herein.
[0243] Embodiment Z13 may include a method of communicating in a wireless network as shown and described herein.
[0244] Embodiment Z14 may include a system for providing wireless communications as shown and described herein.
[0245] Embodiment Z15 may include an apparatus for providing wireless communications as shown and described herein.
[0246] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.
[0247] abbreviation
[0248] For the purposes of this document, the following abbreviations may be applied to the examples and embodiments discussed herein but are not meant to be limiting.
[0249] 3GPP Third Generation Partnership Project
[0250] 4G fourth generation
[0251] 5G fifth generation
[0252] 5GC 5G core network
[0253] ACK
[0254] AF application function
[0255] AM Confirmation Mode
[0256] AMBR Aggregate Maximum Bit Rate
[0257] AMF Access and Mobility Management Function
[0258] ANR Automatic Neighbor Relation
[0259] AP application protocol, antenna port, access point
[0260] API Application Programming Interface
[0261] APN Access Point Name
[0262] ARP Allocation Preservation Priority
[0263] ARQ Automatic Repeat Request
[0264] AS access layer
[0265] ASN.1 Abstract Syntax Notation
[0266] AUSF authentication server function
[0267] AWGN Additive White Gaussian Noise
[0268] BCH Broadcast Channel
[0269] BER Bit Error Rate
[0270] BFD beam failure detection
[0271] BLER Block Error Rate
[0272] BPSK Binary Phase Shift Keying
[0273] BRAS Broadband Remote Access Server
[0274] BSS Business Support System
[0275] BS Base Station
[0276] BSR Buffer Status Report
[0277] BW Bandwidth
[0278] BWP Bandwidth Part
[0279] C-RNTI Cell Radio Network Temporary Identifier
[0280] CA Carrier Aggregation, Certification Authority
[0281] CAPEX Capital Expenditure
[0282] CBRA Contention-based random access
[0283] CC component carrier, country code, encryption checksum
[0284] CCA Clear Channel Assessment
[0285] CCE Control Channel Element
[0286] CCCH Common Control Channel
[0287] CE Coverage Enhancement
[0288] CDM Content Delivery Network
[0289] CDMA Code Division Multiple Access
[0290] CFRA Contention-Free Random Access
[0291] CG Cell Group
[0292] CI Cell Identifier
[0293] CID Cell ID (e.g., positioning method)
[0294] CIM Common Information Model
[0295] CIR Carrier to Interference Ratio
[0296] CK Cryptographic Key
[0297] CM Connection Management, Conditionally Mandatory
[0298] CMAS Commercial Mobile Alert Service
[0299] CMD command
[0300] CMS Cloud Management System
[0301] CO conditional optional
[0302] CoMP Coordinated Multipoint
[0303] CORESET Control Resource Set
[0304] COTS Commercial Off-the-Shelf
[0305] CP Control Plane, Cyclic Prefix, Connection Point
[0306] CPD Connection Point Descriptor
[0307] CPE user terminal equipment
[0308] CPICH Common Pilot Channel
[0309] CQI Channel Quality Indicator
[0310] CPU CSI processing unit, central processing unit
[0311] C / R Command / Response field bit
[0312] CRAN Cloud Radio Access Network, Cloud RAN
[0313] CRB Common Resource Block
[0314] CRC Cyclic Redundancy Check
[0315] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator
[0316] C-RNTI Cell RNTI
[0317] CS Circuit Switched
[0318] CSAR Cloud Service Archive
[0319] CSI Channel State Information
[0320] CSI-IM CSI interference measurement
[0321] CSI-RS CSI reference signal
[0322] CSI-RSRP CSI reference signal received power
[0323] CSI-RSRQ CSI reference signal reception quality
[0324] CSI-SINR CSI signal to interference plus noise ratio
[0325] CSMA Carrier Sense Multiple Access
[0326] CSMA / CA CSMA with collision avoidance
[0327] CSS Common Search Space, Cell Specific Search Space
[0328] CTS Clear to Send
[0329] CW codeword
[0330] CWS Contention Window Size
[0331] D2D device to device
[0332] DC dual connection, direct current
[0333] DCI Downlink Control Information
[0334] DF deployment preferences
[0335] DL Downlink
[0336] DMTF Distributed Management Task Force
[0337] DPDK Data Plane Development Kit
[0338] DM-RS, DMRS Demodulation Reference Signal
[0339] DN Data Network
[0340] DRB Data Radio Bearer
[0341] DRS Discovery Reference Signal
[0342] DRX Discontinuous Reception
[0343] DSL Domain Specific Language Digital Subscriber Line
[0344] DSLAM DSL Access Multiplexer
[0345] DwPTS Downlink Pilot Time Slot
[0346] E-LAN Ethernet Local Area Network
[0347] E2E End-to-End
[0348] ECCA Extended Clear Channel Assessment, Extended CCA
[0349] ECCE Enhanced Control Channel Element, Enhanced CCE
[0350] ED Energy Detection
[0351] EDGE Enhanced Data rates for GSM Evolution (GSM Evolution)
[0352] EGMF exposes governance management functions
[0353] EGPRS Enhanced GPRS
[0354] EIR Equipment Identity Register
[0355] eLAA Enhanced License Assisted Access, enhanced LAA
[0356] EM Element Manager
[0357] eMBB Enhanced Mobile Broadband
[0358] EMS Element Management System
[0359] eNB Evolved Node B, E-UTRAN Node B
[0360] EN-DC E-UTRA-NR Dual Connectivity
[0361] EPC Evolved Packet Core
[0362] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel
[0363] EPRE Energy per resource element
[0364] EPS Evolved Packet System
[0365] EREG Enhanced REG, Enhanced Resource Element Group
[0366] ETSI European Telecommunications Standards Institute
[0367] ETWS Earthquake and Tsunami Warning System
[0368] eUICC embedded UICC, embedded universal integrated circuit card
[0369] E-UTRA Evolved UTRA
[0370] E-UTRAN Evolved UTRAN
[0371] EV2X Enhanced V2X
[0372] F1AP F1 Application Protocol
[0373] F1-C F1 control plane interface
[0374] F1-U F1 User Plane Interface
[0375] FACCH Fast Associated Control Channel
[0376] FACCH / F Fast Associated Control Channel / Full Rate
[0377] FACCH / H Fast Associated Control Channel / Half Rate
[0378] FACH Forward Access Channel
[0379] FAUSCH Fast Uplink Signaling Channel
[0380] FB function block
[0381] FBI feedback
[0382] FCC Federal Communications Commission
[0383] FCCH Frequency Correction Channel
[0384] FDD Frequency Division Duplex
[0385] FDM Frequency Division Multiplexing
[0386] FDMA Frequency Division Multiple Access
[0387] FE Front End
[0388] FEC Forward Error Correction
[0389] FFS for further research
[0390] FFT Fast Fourier Transform
[0391] feLAA Further Enhanced Licensing Assisted Access, further enhanced LAA
[0392] FN Frame Number
[0393] FPGA Field Programmable Gate Array
[0394] FR frequency range
[0395] G-RNTI GERAN Radio Network Temporary Identifier
[0396] GERAN GSM EDGE RAN, GSM EDGE Radio Access Network
[0397] GGSN Gateway GPRS Support Node
[0398] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Chinese: Global Navigation Satellite System)
[0399] gNB Next Generation Node B
[0400] gNB-CU gNB centralized unit, next generation Node B centralized unit
[0401] gNB-DU gNB distributed unit, next generation Node B distributed unit
[0402] GNSS Global Navigation Satellite System
[0403] GPRS General Packet Radio Service
[0404] GSM Global System for Mobile Communications, Mobile Experts Group
[0405] GTP GPRS Tunneling Protocol
[0406] GTP-U GPRS Tunneling Protocol for the User Plane
[0407] GTS Go to sleep signal (related to WUS)
[0408] GUMMEI Globally Unique MME Identifier
[0409] GUTI Globally Unique Temporary UE Identifier
[0410] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request
[0411] HANDO, HO switch
[0412] HFN Superframe Number
[0413] HHO Hard Handover
[0414] HLR Home Location Register
[0415] HN Home Network
[0416] HO Handover
[0417] HPLMN Home Public Land Mobile Network
[0418] HSDPA High Speed Downlink Packet Access
[0419] HSN Hopping Sequence Number
[0420] HSPA High Speed Packet Access
[0421] HSS Home Subscriber Server
[0422] HSUPA High Speed Uplink Packet Access
[0423] HTTP Hypertext Transfer Protocol
[0424] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443)
[0425] I-Block Information Block
[0426] ICCID Integrated Circuit Card Identifier
[0427] ICIC Inter-cell Interference Coordination
[0428] ID identification, identifier
[0429] IDFT Inverse Discrete Fourier Transform
[0430] IE Information Element
[0431] IBE In-Band Emission
[0432] IEEE Institute of Electrical and Electronics Engineers
[0433] IEI Information Element Identifier
[0434] IEIDL Information Element Identifier Data Length
[0435] IETF Internet Engineering Task Force
[0436] IF Infrastructure
[0437] IM interference measurement, intermodulation, IP multimedia
[0438] IMC IMS credentials
[0439] IMEI International Mobile Equipment Identity
[0440] IMGI International Mobile Group Identity
[0441] IMPI IP Multimedia Privacy Identity
[0442] IMPU IP Multimedia Public Identity
[0443] IMS IP Multimedia Subsystem
[0444] IMSI International Mobile Subscriber Identity
[0445] IoT
[0446] IP Internet Protocol
[0447] IPsec IP security, Internet Protocol Security
[0448] IP-CAN IP connection access network
[0449] IP-M IP Multicast
[0450] IPv4 Internet Protocol version 4
[0451] IPv6 Internet Protocol version 6
[0452] IR
[0453] IS Synchronization
[0454] IRP Integration Reference Point
[0455] ISDN Integrated Services Digital Network
[0456] ISIM IM Service Identity Module
[0457] ISO International Organization for Standardization
[0458] ISP Internet Service Provider
[0459] IWF interworking function
[0460] I-WLAN Intercommunication WLAN
[0461] K is the constraint length of the convolutional code, USIM individual key
[0462] kB kilobyte (1000 bytes)
[0463] kbps kilobits per second
[0464] Kc cryptographic key
[0465] Ki individual user authentication key
[0466] KPI Key Performance Indicator
[0467] KQI Key Quality Indicator
[0468] KSI Key Set Identifier
[0469] ksps kilosymbols per second
[0470] KVM Kernel Virtual Machine
[0471] L1 Layer 1 (physical layer)
[0472] L1-RSRP Layer 1 reference signal received power
[0473] L2 Layer 2 (Data Link Layer)
[0474] L3 Layer 3 (Network Layer)
[0475] LAA License Assisted Access
[0476] LAN Local Area Network
[0477] LBT Listen before speaking
[0478] LCM Lifecycle Management
[0479] LCR Low Chip Rate
[0480] LCS Location Services
[0481] LCID Logical Channel ID
[0482] LI layer indicator
[0483] LLC Logical Link Control, low layer compatibility
[0484] LPLMN Local PLMN
[0485] LPP LTE Positioning Protocol
[0486] LSB Least Significant Bit
[0487] LTE Long Term Evolution
[0488] LWA LTE-WLAN aggregation
[0489] LWIP LTE / WLAN radio-level integration with IPsec tunneling
[0490] LTE Long Term Evolution
[0491] M2M Machine to Machine
[0492] MAC Medium Access Control (Protocol Layer Context)
[0493] MAC Message Authentication Code (Security / Cryptography Context)
[0494] MAC-A MAC for authentication and key agreement (TSG T WG3 context)
[0495] MAC-I MAC for data integrity of signaling messages (TSG T WG3 context)
[0496] MANO Management and Orchestration
[0497] MBMS Multimedia Broadcast Multicast Service
[0498] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
[0499] MCC Mobile Country Code
[0500] MCG Master Cell Group
[0501] MCOT Maximum Channel Occupancy Time
[0502] MCS modulation and coding scheme
[0503] MDAF management data analysis function
[0504] MDAS Management Data Analysis Service
[0505] Minimization of MDT-driven testing
[0506] ME Mobile Equipment
[0507] MeNB Master eNB
[0508] MER message error rate
[0509] MGL Measuring Gap Length
[0510] MGRP measurement gap repetition period
[0511] MIB Master Information Block, Management Information Base
[0512] MIMO Multiple Input Multiple Output
[0513] MLC Mobile Location Center
[0514] MM Mobility Management
[0515] MME Mobility Management Entity
[0516] MN Master Node
[0517] MO measurement object, mobile calling
[0518] MPBCH MTC physical broadcast channel
[0519] MPDCCH MTC Physical Downlink Control Channel
[0520] MPDSCH MTC Physical Downlink Shared Channel
[0521] MPRACH MTC Physical Random Access Channel
[0522] MPUSCH MTC Physical Uplink Shared Channel
[0523] MPLS Multi-Protocol Label Switching
[0524] MS Mobile Station
[0525] MSB Most Significant Bit
[0526] MSC Mobile Switching Center
[0527] MSI minimum system information, MCH scheduling information
[0528] MSID Mobile Station Identifier
[0529] MSIN Mobile Station Identification Number
[0530] MSISDN Mobile Subscriber ISDN Number
[0531] MT mobile station called, mobile terminal
[0532] MTC Machine Type Communication
[0533] mMTC Massive MTC, Massive Machine Type Communication
[0534] MU-MIMO Multi-User MIMO
[0535] MWUS MTC wake-up signal, MTC WUS
[0536] NACK Negative Acknowledgement
[0537] NAI Network Access Identifier
[0538] NAS Non-Access Stratum, Non-Access Stratum
[0539] NCT Network Connection Topology
[0540] NEC Network Capabilities Exposure
[0541] NE-DC NR-E-UTRA dual connectivity
[0542] NEF network exposure function
[0543] NF Network Function
[0544] NFP Network Forwarding Path
[0545] NFPD Network Forwarding Path Descriptor
[0546] NFV Network Function Virtualization
[0547] NFVI NFV Infrastructure
[0548] NFVO NFV Orchestrator
[0549] NG Next Generation, Next Generation
[0550] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
[0551] NM Network Manager
[0552] NMS Network Management System
[0553] N-PoP Network Point of Presence
[0554] NMIB, N-MIB Narrowband MIB
[0555] NPBCH Narrowband Physical Broadcast Channel
[0556] NPDCCH Narrowband Physical Downlink Control Channel
[0557] NPDSCH Narrowband Physical Downlink Shared Channel
[0558] NPRACH Narrowband Physical Random Access Channel
[0559] NPUSCH Narrowband Physical Uplink Shared Channel
[0560] NPSS Narrowband Primary Synchronization Signal
[0561] NSSS Narrowband Secondary Synchronization Signal
[0562] NR New Radio, Neighbor Relations
[0563] NRF NF Repository Functionality
[0564] NRS Narrowband Reference Signal
[0565] NS Network Service
[0566] NSA non-standalone operation mode
[0567] NSD Network Service Descriptor
[0568] NSR Network Service Record
[0569] NSSAI Network Slice Selection Assistance Information
[0570] S-NNSAI Single NSSAI
[0571] NSSF network slice selection function
[0572] NW Network
[0573] NWUS narrowband wake-up signal, narrowband WUS
[0574] NZP Non-Zero Power
[0575] O&M Operations and Maintenance
[0576] ODU2 Optical Channel Data Unit - Type 2
[0577] OFDM Orthogonal Frequency Division Multiplexing
[0578] OFDMA Orthogonal Frequency Division Multiple Access
[0579] OOB Out-of-Band
[0580] OOS out of sync
[0581] OPEX operating expenses
[0582] OSI Other System Information
[0583] OSS Operation Support System
[0584] OTA (Over the Air)
[0585] PAPR Peak to Average Power Ratio
[0586] PAR Peak to Average Ratio
[0587] PBCH Physical Broadcast Channel
[0588] PC Power Control, Personal Computer
[0589] PCC Primary Component Carrier, Primary CC
[0590] PCell Primary Cell
[0591] PCI Physical Cell ID, Physical Cell Identity
[0592] PCEF Policy and Charging Enforcement Function
[0593] PCF Policy Control Function
[0594] PCRF Policy Control and Charging Rules Function
[0595] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer
[0596] PDCCH Physical Downlink Control Channel
[0597] PDCP Packet Data Convergence Protocol
[0598] PDN Packet Data Network, Public Data Network
[0599] PDSCH Physical Downlink Shared Channel
[0600] PDU Protocol Data Unit
[0601] PEI Permanent Equipment Identifier
[0602] PFD Packet Flow Description
[0603] P-GW PDN Gateway
[0604] PHICH Physical Hybrid ARQ Indicator Channel
[0605] PHY Physical Layer
[0606] PLMN Public Land Mobile Network
[0607] PIN Personal Identification Number
[0608] PM performance measurement
[0609] PMI Precoding Matrix Indicator
[0610] PNF Physical Network Function
[0611] PNFD Physical Network Function Descriptor
[0612] PNFR Physical Network Function Record
[0613] POC PTT over Cellular
[0614] PP, PTP point-to-point
[0615] PPP Point-to-Point Protocol
[0616] PRACH Physical RACH
[0617] PRB Physical Resource Block
[0618] PRG Physical Resource Group
[0619] ProSe proximity-based services
[0620] PRS Positioning Reference Signal
[0621] PRR Packet Receive Radio
[0622] PS Packet Service
[0623] PSBCH Physical Sidelink Broadcast Channel
[0624] PSDCH Physical Sidelink Downlink Channel
[0625] PSCCH Physical Sidelink Control Channel
[0626] PSSCH Physical Sidelink Shared Channel
[0627] PSCell Primary SCell
[0628] PSS Primary Synchronization Signal
[0629] PSTN Public Switched Telephone Network
[0630] PT-RS Phase Tracking Reference Signal
[0631] PTT Push to Talk
[0632] PUCCH Physical Uplink Control Channel
[0633] PUSCH Physical Uplink Shared Channel
[0634] QAM Quadrature Amplitude Modulation
[0635] QCI QoS Class Identifier
[0636] QCL quasi-co-sited
[0637] QFI QoS flow ID, QoS flow identifier
[0638] QoS Quality of Service
[0639] QPSK Quadrature (Quaternary) Phase Shift Keying
[0640] QZSS Quasi-Zenith Satellite System
[0641] RA-RNTI Random Access RNTI
[0642] RAB Radio Access Bearer, Random Access Burst
[0643] RACH Random Access Channel
[0644] RADIUS Remote Authentication Dial-In User Service
[0645] RAN Radio Access Network
[0646] RAND random number (for authentication)
[0647] RAR Random Access Response
[0648] RAT Radio Access Technology
[0649] RAU Routing Area Update
[0650] RB Resource Block, Radio Bearer
[0651] RBG Resource Block Group
[0652] REG Resource Element Group
[0653] Rel release
[0654] REQ Request
[0655] RF
[0656] RI rank indicator
[0657] RIV Resource Indicator Value
[0658] RL Radio Link
[0659] RLC Radio Link Control, Radio Link Control Layer
[0660] RLC AM RLC Acknowledgement Mode
[0661] RLC UM RLC Unacknowledged Mode
[0662] RLF Radio Link Failure
[0663] RLM Radio Link Monitoring
[0664] RLM-RS Reference signal for RLM
[0665] RM Registration Management
[0666] RMC Reference Measurement Channel
[0667] RMSI Remaining MSI, Remaining Minimum System Information
[0668] RN relay node
[0669] RNC Radio Network Controller
[0670] RNL Radio Network Layer
[0671] RNTI Radio Network Temporary Identifier
[0672] ROHC Robust Header Compression
[0673] RRC Radio Resource Control, Radio Resource Control Layer
[0674] RRM Radio Resource Management
[0675] RS reference signal
[0676] RSRP Reference Signal Received Power
[0677] RSRQ Reference Signal Received Quality
[0678] RSSI Received Signal Strength Indicator
[0679] RSU Road Side Unit
[0680] RSTD Reference Signal Time Difference
[0681] RTP Real-Time Protocol
[0682] RTS Ready to Send
[0683] RTT Round Trip Time
[0684] Rx receive, receive, receiver
[0685] S1AP S1 Application Protocol
[0686] S1-MME is used for S1 control plane
[0687] S1-U S1 for user plane
[0688] S-GW Service Gateway
[0689] S-RNTI SRNC Radio Network Temporary Identifier
[0690] S-TMSI SAE temporary mobile station identifier
[0691] SA standalone operation mode
[0692] SAE system architecture evolution
[0693] SAP Service Access Point
[0694] SAPD Service Access Point Descriptor
[0695] SAPI Service Access Point Identifier
[0696] SCC Secondary Component Carrier, Secondary CC
[0697] SCell Secondary Cell
[0698] SC-FDMA Single Carrier Frequency Division Multiple Access
[0699] SCG Secondary Cell Group
[0700] SCM Security Context Management
[0701] SCS subcarrier spacing
[0702] SCTP Stream Control Transmission Protocol
[0703] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer
[0704] SDL Supplementary Downlink
[0705] SDNF Structured Data Storage Network Function
[0706] SDP Session Description Protocol
[0707] SDSF structured data storage function
[0708] SDU Service Data Unit
[0709] SEAF Security Anchoring Function
[0710] SeNB Assisted eNB
[0711] SEPP Security Edge Protection Proxy
[0712] SFI Slot Format Indicator
[0713] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference
[0714] SFN System Frame Number
[0715] SgNB auxiliary gNB
[0716] SGSN Serving GPRS Support Node
[0717] S-GW Service Gateway
[0718] SI System Information
[0719] SI-RNTI System Information RNTI
[0720] SIB System Information Block
[0721] SIM Subscriber Identity Module
[0722] SIP Session Initiation Protocol
[0723] SiP System-in-Package
[0724] SL Side Link
[0725] SLA Service Level Agreement
[0726] SM Session Management
[0727] SMF session management functions
[0728] SMS Short Message Service
[0729] SMSF SMS function
[0730] SMTC SSB-based measurement timing configuration
[0731] SN Secondary node, serial number
[0732] SoC System on Chip
[0733] SON self-organizing network
[0734] SpCell Special Cell
[0735] SP-CSI-RNTI Semi-persistent CSI RNTI
[0736] SPS Semi-persistent Scheduling
[0737] SON serial number
[0738] SR Scheduling Request
[0739] SRB Signalling Radio Bearer
[0740] SRS Sounding Reference Signal
[0741] SS synchronization signal
[0742] SSB Synchronization Signal Block, SS / PBCH Block
[0743] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator
[0744] SSC Session and Service Continuity
[0745] SS-RSRP is the reference signal received power based on the synchronization signal.
[0746] SS-RSRQ Reference signal reception quality based on synchronization signal
[0747] SS-SINR Signal to Interference and Noise Ratio based on synchronization signal
[0748] SSS Secondary synchronization signal
[0749] SSSG Search Space Group
[0750] SSSIF Search Space Set Indicator
[0751] SST Slice / Serving Type
[0752] SU-MIMO Single-User MIMO
[0753] SUL Supplementary Uplink
[0754] TA timing advance, tracking area
[0755] TAC Tracking Area Code
[0756] TAG Timing Advance Group
[0757] TAU Tracking Area Updates
[0758] TB transfer block
[0759] TBS transport block size
[0760] TBD To be defined
[0761] TCI Transmission Configuration Indicator
[0762] TCP transport communication protocol
[0763] TDD Time Division Duplex
[0764] TDM Time Division Multiplexing
[0765] TDMA Time Division Multiple Access
[0766] TE terminal equipment
[0767] TEID Tunnel Endpoint Identifier
[0768] TFT business flow template
[0769] TMSI Temporary Mobile Subscriber Identity
[0770] TNL Transport Network Layer
[0771] TPC Transmit Power Control
[0772] TPMI transmitted precoding matrix indicator
[0773] TR Technical Report
[0774] TRP,TRxP Transmission Receive Point
[0775] TRS Tracking Reference Signal
[0776] TRx transceiver
[0777] TS Technical Specification, Technical Standard
[0778] TTI Transmission Time Interval
[0779] Tx transmission, transmission, transmitter
[0780] U-RNTI UTRAN Radio Network Temporary Identity
[0781] UART Universal Asynchronous Receiver and Transmitter
[0782] UCI Uplink Control Information
[0783] UE User Equipment
[0784] UDM Unified Data Management
[0785] UDP User Datagram Protocol
[0786] UDSF Unstructured Data Storage Network Function
[0787] UICC Universal Integrated Circuit Card
[0788] UL Uplink
[0789] UM Unconfirmed Mode
[0790] UML Unified Modeling Language
[0791] UMTS Universal Mobile Telecommunications System
[0792] UP User Plane
[0793] UPF User Plane Function
[0794] URI Uniform Resource Identifier
[0795] URL Uniform Resource Locator
[0796] URLLC Ultra-Reliable Low Latency
[0797] USB Universal Serial Bus
[0798] USIM Universal Subscriber Identity Module
[0799] USS UE-specific search space
[0800] UTRA UMTS Terrestrial Radio Access
[0801] UTRAN Universal Terrestrial Radio Access Network
[0802] UwPTS Uplink Pilot Time Slot
[0803] V2I Vehicle to Infrastructure
[0804] V2P Vehicle to Pedestrian
[0805] V2V Vehicle to Vehicle
[0806] V2X: Vehicle-to-Everything Connection
[0807] VIM Virtualization Infrastructure Manager
[0808] VL Virtual Link
[0809] VLAN virtual LAN, virtual local area network
[0810] VM virtual machine
[0811] VNF Virtualized Network Function
[0812] VNFFG VNF forwarding graph
[0813] VNFFGD VNF Forwarding Graph Descriptor
[0814] VNFM VNF Manager
[0815] VoIP Voice over IP, Voice over Internet Protocol
[0816] VPLMN Visited Public Land Mobile Network
[0817] VPN Virtual Private Network
[0818] VRB Virtual Resource Block
[0819] WiMAX Worldwide Interoperability for Microwave Access
[0820] WLAN Wireless Local Area Network
[0821] WMAN Wireless Metropolitan Area Network
[0822] WPAN Wireless Personal Area Network
[0823] X2-C X2 control plane
[0824] X2-U X2 user plane
[0825] XML Extensible Markup Language
[0826] XRES Expected User Response
[0827] XOR
[0828] ZC Zadoff-Chu
[0829] ZP Zero Power
[0830] the term
[0831] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein and are not intended to be limiting.
[0832] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" can also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit.
[0833] As used herein, the term "processor circuitry" means, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms "application circuitry" and / or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry."
[0834] As used herein, the term "interface circuit" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.
[0835] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can represent a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.
[0836] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc.
[0837] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.
[0838] As used herein, the terms "appliance," "computer appliance," and the like refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.
[0839] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to the computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to the computing, storage, and / or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resources" may refer to any type of shared entity that provides a service and may include computing resources and / or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.
[0840] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terms indicating a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for transmitting and receiving information.
[0841] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.
[0842] As used herein, the terms "coupled," "communicably coupled," and their derivatives are used. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements are in indirect contact with one another but still cooperate or interact with one another, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to one another. The term "directly coupled" may mean that two or more elements are in direct contact with one another. The term "communicably coupled" may mean that two or more elements may be in contact with one another by means of communication, including through wires or other interconnections, through wireless communication channels or links, and the like.
[0843] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.
[0844] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
[0845] The term "SSB" refers to SS / PBCH block.
[0846] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
[0847] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.
[0848] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.
[0849] The term "secondary cell group" refers to a subset of serving cells including a PSCell for a UE configured with DC and zero or more secondary cells.
[0850] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell.
[0851] The term "serving cell" refers to a cell group including a special cell for a UE configured with CA and in RRC_CONNECTED and all secondary cells.
[0852] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.
[0853] As described above, various aspects of the present technology may include collecting and using data available from various sources to, for example, improve or enhance functionality. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users.
[0854] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information. Such policies should be easily accessible to users and updated as the collection and / or use of data changes. Personal information collected from users should be used for the entity's legitimate and reasonable purposes and not shared or sold beyond those legitimate uses. Furthermore, such collection / sharing should only be done with the user's informed consent. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to the personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific type of personal information collected and / or accessed, and to applicable laws and standards, including jurisdictional considerations. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.
[0855] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware components and / or software components to prevent or block access to such personal information data. For example, the present technology can be configured to allow users to selectively “opt in” or “opt out” of collecting personal information data at any time, for example, during or after registration for a service. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.
[0856] Furthermore, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods, where appropriate.
[0857] Thus, while the present disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology will not be unable to function properly due to the lack of all or a portion of such personal information data.
Claims
1. An electronic device, comprising: A processor circuit, the processor circuit being configured to: Receiving a first ICN packet including an information center network ICN name or an ICN common field; compressing the ICN name or the ICN common field at a Packet Data Convergence Protocol (PDCP) layer; as well as providing a compressed ICN name or a compressed ICN common field to a lower protocol layer; and a radio front end circuit coupled to the processor circuit and configured to transmit a second ICN packet including a compressed ICN name or a compressed ICN common field, wherein: The radio front end circuit is further configured to receive one or more ICN compression parameters using an information element IE, and The processor circuit is configured to compress the ICN name or the ICN common field based on the one or more ICN compression parameters. 2 . The electronic device of claim 1 , wherein the first ICN packet comprises a first ICN interest packet and the second ICN packet comprises a second ICN interest packet. 3 . The electronic device of claim 1 , wherein the first ICN packet comprises a first ICN data packet and the second ICN packet comprises a second ICN data packet. 4 . The electronic device of claim 1 , wherein the processor circuit is further configured to segment the first ICN packet into a plurality of packets at the PDCP layer. 5 . The electronic device of claim 1 , wherein the radio front end circuit is configured to receive the IE using radio resource control (RRC) signaling. 6 . The electronic device of claim 1 , wherein the processor circuit is configured to compress the ICN name based on a predetermined mapping between the ICN name and a compression value.
7. The electronic device of claim 1 , wherein the processor circuit is configured to: comparing the size of the second ICN packet with a threshold; and In response to the size of the second ICN packet being greater than the threshold, compressing the ICN name or the ICN common field.
8. The electronic device according to claim 1, wherein: The electronic device is an access node AN, The radio front end circuit is configured to receive the first ICN packet from a source device or an ICN router, and The radio front end circuitry is configured to transmit the second ICN packet to a user equipment UE.
9. The electronic device according to claim 1, wherein: The electronic device is a user equipment UE, The radio front end circuit is configured to receive the first ICN packet from an upper protocol layer, and The radio front end circuit is configured to transmit the second ICN packet to an access node AN.
10. A method for wireless communication, the method comprising: Receiving, at the electronic device, a first ICN packet including an information centric network ICN name or an ICN common field; Using an information element IE to receive one or more ICN compression parameters; compressing the ICN name or the ICN common field based on the one or more ICN compression parameters at a Packet Data Convergence Protocol (PDCP) layer at the electronic device; providing, at the electronic device, a compressed ICN name or a compressed ICN common field to a lower protocol layer; as well as A second ICN packet including the compressed ICN name or the compressed ICN common field is transmitted by the electronic device. 11 . The method of claim 10 , wherein the first ICN packet comprises a first ICN interest packet and the second ICN packet comprises a second ICN interest packet.
12. The method of claim 10, wherein the first ICN packet comprises a first ICN data packet and the second ICN packet comprises a second ICN data packet.
13. The method of claim 10, wherein compressing the ICN name comprises compressing the ICN name based on a predetermined mapping between the ICN name and a compression value.
14. The method according to claim 10, further comprising: Comparing the size of the second ICN packet with a threshold; as well as In response to the size of the second ICN packet being greater than the threshold, compressing the ICN name or the ICN common field.
15. The method according to claim 10, wherein the electronic device is an access node AN, and the method further comprises: receiving the first ICN packet from a source device or an ICN router; as well as The second ICN packet is transmitted to a user equipment UE.
16. An electronic device comprising: Radio front-end circuits; and a processor circuit coupled to the radio front end circuit and configured to: receiving, using the radio front end circuitry, a first ICN packet including at least one of a compressed Information Centric Network (ICN) name or a compressed ICN common field; Decompressing the compressed ICN name or the compressed ICN common field at a Packet Data Convergence Protocol (PDCP) layer; as well as Provide the decompressed ICN name or decompressed ICN common fields to higher protocol layers, where: The radio front end circuit is further configured to receive one or more ICN compression parameters using an information element IE, and The processor circuit is configured to decompress the compressed ICN name or the compressed ICN common field based on the one or more ICN compression parameters. 17 . The electronic device of claim 16 , wherein the processor circuit is configured to decompress the compressed ICN name based on a predetermined mapping between ICN names and compressed values.
Citation Information
Patent Citations
A node and method for handling information centric networking based communications
CN107113536A
Method and apparatus for serving quality of service (QOS) flow in a wireless communication system
CN109302751A
Information centric networking for long term evolution
US20180007177A1
Method for congestion control in a network
WO2018225039A1
