COT sharing procedure for configuration authorization in NR systems operating in unlicensed spectrum

Abstract

A system, apparatus, method and computer-readable medium for a wireless communication system in an unlicensed spectrum are provided. A user equipment (UE) device of the wireless communication system includes a processor circuit and a radio front-end circuit. The processor circuit is configured to obtain a channel occupancy time (COT) in an unlicensed spectrum and determine the number of remaining consecutive subframes allocated for physical uplink shared channel (PUSCH) transmission to a base station. The processor circuit is configured to generate uplink control information (UCI) to indicate a COT sharing boundary occurring at the end of the remaining consecutive subframes. The radio front-end circuit is coupled to the processor circuit and is configured to transmit UCI in a PUSCH transmission during a subframe in the remaining consecutive subframes. The processor circuit is also configured to monitor downlink transmissions from the base station after the COT sharing boundary.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 791,690, filed on January 11, 2019, which is hereby incorporated by reference in its entirety for all purposes. Background Art

[0003] Various embodiments may generally relate to the field of wireless communications. Summary of the invention

[0004] This summary provides a brief description of one or more of the embodiments and / or examples found within the present disclosure.

[0005] The present disclosure describes a user equipment (UE) or an apparatus thereof for a wireless communication system in an unlicensed spectrum. The UE device includes a processor circuit configured to obtain a channel occupancy time (COT) in an unlicensed spectrum and determine the number of remaining consecutive subframes allocated for physical uplink shared channel (PUSCH) transmission to a base station. The processor circuit is configured to generate uplink control information (UCI) to indicate a COT sharing boundary occurring at the end of the remaining consecutive subframes. The UE device also includes a radio front-end circuit coupled to the processor circuit and configured to transmit UCI in a PUSCH transmission during a subframe in the remaining consecutive subframes. The processor circuit is also configured to monitor downlink transmissions from the base station after the COT sharing boundary.

[0006] The present disclosure also describes a method performed by a user equipment (UE) for a wireless communication system in an unlicensed spectrum. The method includes obtaining a channel occupation time (COT) in the unlicensed spectrum, and determining the number of remaining consecutive subframes allocated for physical uplink shared channel (PUSCH) transmission to a base station. The method includes generating uplink control information (UCI) to indicate a COT sharing boundary occurring at the end of the remaining consecutive subframes, and transmitting the UCI from the UE to the base station in a PUSCH transmission during a subframe in the remaining consecutive subframes. The method includes monitoring downlink transmissions from the base station after the COT sharing boundary.

[0007] The present disclosure also describes a computer-readable medium (CRM) comprising computer instructions to be executed by one or more processors of a user equipment (UE) of a wireless communication system in an unlicensed spectrum. The computer instructions cause the one or more processors to obtain a channel occupancy time (COT) in the unlicensed spectrum and determine the number of remaining consecutive subframes allocated for physical uplink shared channel (PUSCH) transmission to a base station. The instructions cause the one or more processors of the UE to generate uplink control information (UCI) to indicate a COT sharing boundary occurring at the end of the remaining consecutive subframes. The instructions cause the one or more processors of the UE to transmit UCI in a PUSCH transmission during one of the remaining consecutive subframes and monitor downlink transmissions from the base station after the COT sharing boundary. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 An example of a user equipment (UE) channel occupancy time (COT) sharing process is shown in accordance with some embodiments.

[0009] Figure 2 Depicted is an example of COT sharing by two UEs according to some embodiments.

[0010] Figure 3 Depicted is an example of COT sharing by two UEs according to some embodiments.

[0011] Figure 4 Depicted are exemplary processes according to some embodiments.

[0012] Figure 5 Depicted is the architecture of a system of networks according to some embodiments.

[0013] Figure 6 An architecture of a system including a first core network according to some embodiments is depicted.

[0014] Figure 7 An architecture of a system including a second core network according to some embodiments is depicted.

[0015] Figure 8 Depicted are examples of infrastructure equipment according to various embodiments.

[0016] Fig. 9 Depicted are exemplary components of a platform according to various embodiments.

[0017] Fig.10 Depicted are exemplary components of baseband circuitry and radio frequency circuitry according to some embodiments.

[0018] Fig.11Depicted are diagrams of various protocol functions that may be used in various protocol stacks according to various embodiments.

[0019] Fig.12 Depicted are block diagrams showing 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. DETAILED DESCRIPTION

[0020] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of the various aspects of each embodiment. However, it will be apparent to those skilled in the art who benefit from the present disclosure that the various aspects of each embodiment can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of the various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0021] Every year, the number of mobile devices connecting to wireless networks increases significantly. In order to keep up with the demand for mobile data traffic, necessary changes must be made to system requirements to be able to meet these demands. The three key areas that require enhancements to achieve this traffic increase are greater bandwidth, lower latency, and higher data rates.

[0022] One of the major limiting factors in wireless innovation is the availability of spectrum. To mitigate this, unlicensed spectrum has been an area of ​​high interest to extend the availability of LTE. “In this context, one of the major enhancements to LTE in 3GPP Release 13 is to enable it to operate in unlicensed spectrum via Licensed Assisted Access (LAA), which extends the system bandwidth by leveraging the flexible carrier aggregation (CA) framework introduced by LTE-Advanced systems.

[0023] Since the main building blocks of the NR framework have been established, a natural enhancement is to allow it to operate on unlicensed spectrum as well (i.e. NR-U). Work on introducing shared / unlicensed spectrum in 5G NR has been initiated and a new work item "NR-based access to unlicensed spectrum" was recently approved in the TSG RAN meeting. Among other things, one of the goals of this new WI is as follows:

[0024] - Physical layer aspects including [RAN1]:

[0025] o Frame structure including single and multiple DL-to-UL and UL-to-DL switching points within a shared COT with associated identified LBT requirements (TR Section 7.2.1.3.1).

[0026] oUL data channel including extension of PUSCH to support PRB-based frequency block interleaved transmission; supporting multiple PUSCH start positions in one or more time slots based on the LBT result with the understanding that the end position is indicated by the UL grant; the design does not require the UE to change the granted TBS for PUSCH transmission based on the LBT result. Necessary PUSCH enhancement is based on CP-OFDM. The applicability of sub-PRB frequency block interleaved transmission for 60kHz is determined by RAN1.

[0027] - Physical layer procedures including [RAN1, RAN2]:

[0028] o For LBE, the channel access mechanism complies with the protocol of the NR-U study project (TR38.889, Section 7.2.1.3.1). Specification work to be performed by RAN1.

[0029] oHARQ Operation: NR HARQ feedback mechanism is baseline NR-U operation with extensions consistent with the protocol during the study phase (NR-U TR Section 7.2.1.3.3), including immediate transmission of HARQ A / N for corresponding data in the same shared COT and transmission of HARQ A / N in subsequent COTs. Potentially supports mechanisms to provide multiple and / or complementary time and / or frequency domain transmission opportunities. (RAN1)

[0030] o Scheduling of PUSCH in accordance with the study protocol (TR 38.889, Section 7.2.1.3.3) for multiple TTIs. (RAN1)

[0031] ο Configuration Authorization Operation: NR Type 1 and Type 2 Configuration Authorization mechanisms are the baseline for NR-U operation with modifications as agreed during the study phase (NR-UTR Section 7.2.1.3.4). (RAN1)

[0032] o Data multiplexing aspects considering LBT and channel access priority (for both UL and DL). (RAN1 / RAN2)

[0033] One of the challenges of NR-U is that the system must maintain fair coexistence with other existing technologies, and to this end, some general limitations may be taken into account when designing the system, depending on the specific frequency band it may operate in. For example, if operating in the 5 GHz band, a listen-before-talk (LBT) process may need to be performed in some parts of the world to acquire the medium before transmission can occur.

[0034] One of the basic operations for configuration grants in NR-U is the UE-acquired COT sharing operation, where the UE acquires a COT and, upon completion of its PUSCH transmission, may share the COT with the gNB. In LAA, this procedure is limited to the COT sharing offset X configured by higher layers, and the UE shall indicate COT sharing using a single bit in subframe n such that the COT sharing boundary occurs at the start of subframe n+X. The UE must blank the final symbol in the last subframe of the PUSCH transmission to allow the gNB to perform CCA. If the gNB acquires the COT upon successful LBT, it may transmit only up to 2 symbols of PDCCH containing only the HARQ feedback and scheduling information for the UE initiating the COT.

[0035] For NR unlicensed operation based on Configuration Grant (CG), a more robust approach is required. Given the different numerology and slot formats, the CG UE must be able to accurately indicate to the gNB where the end symbol of the final PUSCH transmission occurs, and therefore indicate the COT sharing boundary. This becomes very important given that NR unlicensed operation allows COT sharing with different category levels for LBT, thereby allowing the gNB to simplify the contention part of the COT sharing process if the gNB can sufficiently reduce the UL to DL gap. Therefore, the NR-U Configuration Grant COT sharing indication must be robust enough to allow the UE and gNB to take advantage of the flexibility and functionality of NR operation.

[0036] Establish the development of a baseline structure and process for COT sharing with CG UEs using NR configurations licensed resources in unlicensed spectrum.

[0037] When operating on unlicensed spectrum, the CG UE has to contend for access to the channel in order to acquire the Channel Occupancy Time (COT). In this case, the CG UE will transmit in the uplink according to its time domain configuration. However, since the CG UE may not be configured to transmit in the uplink during the entire length of the MCOT, the CG UE may indicate to the gNB the COT sharing points that coincide with the time slots for which the UE's time domain allocation configuration indicates that uplink transmission is not configured. However, additional signaling to the gNB in ​​the UCI is necessary so that the gNB knows exactly in which time slots and symbols the CG UE is sharing the COT. Therefore, a mechanism for the UE-initiated COT sharing procedure and the associated signaling are designed.

[0038] COT Shared Indication Design – Single UE, Full BW Case

[0039] In some embodiments, when a CG UE is allocated full bandwidth and initiates COT using CAT-4 LBT, it will do so on subframes allocated to the CG UE for UL transmissions by higher layers. The CG UE will also know the number of consecutive subframes it has allocated for UL transmissions by higher layers and will therefore transmit PUSCH bursts of length no longer than the consecutive subframes. The UCI will be transmitted along with the PUSCH and will contain information about the number of subframes remaining before the COT sharing boundary. Therefore, based on the signaling in the UCI, the gNB will know exactly which subframe contains the last PUSCH transmission and therefore when the COT sharing boundary occurs.

[0040] In some embodiments, the GC-UCI of the UE includes a 3-bit field for COT sharing offset indication, where the offset is as follows: Figure 1 The bit indication "000" indicates that COT sharing is disabled during the current subframe. For the initial indication for COT sharing, the minimum offset is 2 subframes to allow the gNB sufficient processing time to prepare its DL transmission. The following table summarizes the offsets and their associated bit indications.

[0041]

[0042]

[0043] Table 1: COT shared subframe offset and associated bit indication in UCI

[0044] The UE will use the above table and Figure 1 The subframe offset is used as shown in 102 to indicate the remaining subframes for PUSCH transmission. In the subsequent subframe 104 after the initial COT sharing indication 102, the UE will indicate the remaining number of subframes before the final subframe 106 containing PUSCH transmission using Table 1. In the last subframe of the PUSCH transmission, the UE will indicate an offset of '001'. In the last slot of the last subframe for the UE PUSCH transmission burst, the UE will use the SLIV configuration to determine the length of the last slot 110 and indicate this in the UCI of the final slot using the UCI indication. The gNB will know the exact COT sharing boundary 112 by knowing the final symbol in the final slot 110 located in the final subframe 106, allowing the gNB to know exactly when it can start CCA to obtain the COT from the UE. Figure 1 shows this behavior.

[0045] In some embodiments, X consecutive subframes are allocated to the UE for UL transmission via higher layer configuration. Once the COT sharing boundary is reached, the gNB may immediately start performing CCA to obtain the COT from the UE and decide to transmit to the UE with or without initiating COT in subframe 108, such as Figure 1 As the gNB also knows the SLIV configuration of the UE, it will know the remaining length of the final slot and can therefore prepare for mini-slot DL transmission if enough symbols are available in the slot.

[0046] In some implementations, the CG UE may indicate the COT shared offset value once using the UCI format indicated in Table 1. The offset value X is indicated in subframe n so that the gNB will know that in subframe n+X, the final PUSCH transmission will be as follows: Figure 1 As shown in the figure. Therefore, the gNB will know the subframe containing the COT sharing boundary, monitor the timeslots in the subframe for the end PUSCH indication, and thus determine the earliest opportunity to obtain the COT from the UE. However, the UE will not signal any COT sharing offset indication value in any other subframe, because the gNB can already determine the subframe containing the COT sharing boundary using the given information. Therefore, the COT sharing indication field in all other subframes is set to '000'.

[0047] In some embodiments, the CG UE may set a subframe offset indication to the gNB using parameter X, which will indicate to the gNB when the UE will monitor the timeslot containing the DFI for the PDCCH for the current transmission. The UE will indicate offset X in subframe n using the indication in Table 1, which will inform the gNB that the UE will search for the DFI in time slot n of time slot n+X.

[0048] In some embodiments, the UE's CG-UCI contains a 1-bit field for COT sharing, where "1" means that in X time slots from this signaling, the gNB will be allowed to transmit in a shared COT, and "0" means that the COT is not shared. In one embodiment, this bit field can be interpreted in a recoverable manner: "1" indicates no COT sharing, and "0" is used to indicate COT sharing starting X time slots from the indication of this bit in the UCI. In some embodiments, X can be RRC configured or it can be fixed.

[0049] In some embodiments, in the last slot of the last subframe for the UE PUSCH transmission burst, the UE will determine the length of the last slot using the SLIV configuration and indicate this in the UCI of the last slot using the UCI indication. The gNB will know the exact COT sharing boundary by knowing the last symbol in the last slot in the last subframe, allowing the gNB to know exactly when it can start CCA to obtain the COT from the UE.

[0050] In some embodiments, multiple UL-DL switching points are allowed within the UE's acquired COT. In this case, the UE indicates in the UCI information related to the start of the COT that can be used by the eNB. This can be done with a one-bit field as in the above embodiments, or using a 3-bit indication with an interpretation similar to Table 1.

[0051] In some embodiments, the length of each portion of the shared COT used by the gNB is at least 2 ms long.

[0052] In some embodiments, the gNB provides an indication within one of the DCIs about the length of its transmissions within the shared portion of the COT so that if the gap between transmissions is less than 16 μs, the UE knows when it can acquire the channel and / or start transmitting again without performing LBT.

[0053] The COT acquired by gNB and CG UE is shared

[0054] In some embodiments, the CG UE is allowed to perform transmissions within the gNB's acquired COT in UL time domain resources scheduled by the gNB into the shared COT, but only if the COT is acquired using the maximum priority level value, or for any priority level value.

[0055] In some embodiments, in a newly defined DCI format for single TTI scheduling or multi-TTI scheduling, and / or in a DFI or activation / deactivation DCI, a one-bit field is included to indicate whether COT sharing with a CG UE is enabled.

[0056] If the gNB indicates that sharing is allowed, the CG UE may send data corresponding to any priority level during the UL time domain resources scheduled by the gNB into the shared COT.

[0057] In some embodiments, only continuous transmissions without gaps between UL transmissions are allowed within the UL time domain resources scheduled by the gNB for UL into the shared COT.

[0058] In some embodiments, if there is no PDSCH transmission in the COT, CG transmission within the shared COT of the gNB is not allowed.

[0059] In some implementations, all transmissions belonging to UL resources scheduled by the gNB into the shared COT are counted in the gNB's COT, regardless of whether the resources are used for actual UL transmissions or gaps.

[0060] In some implementations, the gap is not actually counted in the COT of the gNB.

[0061] In some embodiments, the gap between DL and UL may be F symbols, and the UE may use some of the F symbols to perform LBT. If the gap is less than 25 μs, CAT-2 LBT is performed by the CG UE, otherwise CAT-4 LBT is used.

[0062] In some embodiments, the gap between DL and UL can be F symbols, and the UE performs LBT just before the gap so that the UL transmission can start at the boundary of the UL time domain resources scheduled by the gNB into the shared COT. In this case, CAT-4 or CAT-2 LBT is used.

[0063] In some embodiments, the CG UE performs CAT-2 LBT at the boundary of shared UL available resources.

[0064] In some embodiments, CG UE transmissions within the shared COT of the gNB do not extend over the length of the acquired COT.

[0065] Design of UE-initiated COT sharing indication - multiple FDMed UEs

[0066] For a group of frequency division multiplexed (FDMed) UEs that acquire COT simultaneously such that the UE is configured by higher layers to transmit in the current subframe n, they may have different numbers of consecutive configured subframes for PUSCH transmissions. Furthermore, the UEs may have different numbers of PUSCH transmissions to make. Therefore, the UEs will typically end their PUSCH transmissions during different time slots in different subframes. In order to achieve COT sharing operation with multiple simultaneous UEs, the procedure for the UEs should follow the case of a single UE with full BW, so that the UEs will indicate their COT sharing boundary in the same way as if they initiated COT individually. However, once their COT sharing boundary is reached, i.e. their uplink transmission ends, the UEs will start immediately monitoring the channel for downlink transmissions from the gNB. The gNB will receive all uplink transmissions until the nearest COT sharing boundary is reached, at which point the gNB is free to acquire the COT.

[0067] In some implementations, in order for the gNB to inform the group of FDM UEs about the structure of the downlink transmission, the UEs are configured with a common CORESET Search Space (CSS). This can be done in Figure 2 Observe in which the UEs have different uplink burst lengths 202 and 204, and one UE starts monitoring the channel for DCI at the end of its configuration grant transmission 202. After the second UE ends its configuration grant transmission 204, the gNB may Figure 2 In the first case identified as 206 and 208, the COT is obtained and the DCI is sent to the UE.

[0068] In some embodiments, the UE is configured with a UE-specific CSS, such as Figure 3 This is shown as 302 and 306, and the gNB will select the first common case between UEs 304, 306 to transmit the DCI. The UEs will monitor the channel until a common point is reached.

[0069] System and implementation

[0070] Figure 4 An exemplary process according to some embodiments is shown. The exemplary process may be described in detail in relation to Figures 5 to 12 Executed in the system or device described. According to some embodiments, at step 402, the number of consecutive subframes allocated for uplink (UL) transmission is determined. As described above, a configuration grant (CG) UE may be allocated bandwidth and one or more subframes for UL transmission. One or more subframes for UL transmission may be allocated by a higher layer. Therefore, the CG UE may transmit UL bursts within consecutive subframes allocated by the CG UE.

[0071] According to some embodiments, at step 404, uplink control information (UCI) is generated that indicates a channel occupancy time (COT) sharing boundary in one or more of the consecutive subframes allocated to the CG UE. At step 406, the UCI is transmitted to the gNB along with the PUSCH transmission. The UCI is transmitted in one or more of the consecutive subframes allocated to the CG UE. Therefore, the gNB will know exactly when the COT sharing boundary occurs.

[0072] According to some embodiments, at step 408, UCI is generated that indicates a timeslot for monitoring a physical downlink control channel (PDCCH) transmission that includes downlink feedback information (DFI) corresponding to a PUSCH transmission. The PUSCH transmission and the UCI are transmitted in the same timeslot. The timeslot for monitoring the PDCCH transmission represents an offset from the timeslot in which the PUSCH is transmitted with the UCI. As described above, the UE will indicate an offset X in subframe n using the indication in Table 1, which will inform the gNB that the UE will search for a DFI with respect to timeslot n in timeslot n+X.

[0073] According to some embodiments, at step 410, multiple uplink-downlink (UL-DL) switching points are allowed within the acquired COT using UCI for indicating the COT sharing boundary. As described above, the UE indicates in the UCI information related to the start of the COT that can be used by the gNB or eNB or access point. This can be done with a one-bit field as in the above embodiments, or using a 3-bit indication with an interpretation similar to Table I.

[0074] Figure 5 An exemplary architecture of a system 500 of a network according to various embodiments is shown. The following description is provided for an exemplary system 500 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. 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., WMAN, WiMAX, etc.), and the like.

[0075] like Figure 5 As shown, system 500 includes UE 501a and UE 501b (collectively referred to as "multiple UEs 501" or "UE 501"). In this example, UE 501 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-vehicle entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC device, an M2M, an IoT device, etc.

[0076] In some embodiments, any of the UEs 501 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 PLMN, ProSe or D2D communications, sensor networks, or IoT networks. 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-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0077] UE 501 may be configured, for example, to be communicatively coupled to RAN 510. In an embodiment, RAN 510 may be an NGRAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to RAN 510 operating in an NR or 5G system 500, while the term "E-UTRAN" or the like may refer to RAN 510 operating in an LTE or 4G system 500. UE 501 utilizes connections (or channels) 503 and 504, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0078] In this example, connections 503 and 504 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 501 may directly exchange communication data via the ProSe interface 505. The ProSe interface 505 may alternatively be referred to as a SL interface 505, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0079] UE 501b is shown as being configured to access AP 506 (also referred to as "WLAN node 506", "WLAN 506", "WLAN terminal 506", "WT 506", etc.) via connection 507. Connection 507 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 506 will include wireless fidelity Router. In this example, the AP 506 shown is connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, the UE 501b, the RAN 510, and the AP 506 may be configured to utilize LWA operation and / or LWIP operation. The LWA operation may involve the UE 501b in the RRC_CONNECTED state being configured by the RAN nodes 511a-b to utilize the radio resources of LTE and WLAN. The LWIP operation may involve the UE 501b using the WLAN radio resources (e.g., connection 507) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through the connection 507. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0080] The RAN 510 includes one or more AN nodes or RAN nodes 511a and 511b (collectively referred to as "multiple RAN nodes 511" or "RAN node 511") that enable connections 503 and 504. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., 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 a RAN node 511 (e.g., a gNB) operating in an NR or 5G system 500, while the terms "E-UTRAN node" and the like may refer to a RAN node 511 (e.g., an eNB) operating in an LTE or 4G system 500. According to various embodiments, the RAN node 511 may be implemented as one or more of 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.

[0081] In some embodiments, all or part of the multiple RAN nodes 511 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 RAN functional partitioning such as PDCP partitioning, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 511; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 511; or "lower PHY" partitioning, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer are operated by the CRAN / vBBUP, and the lower portions of the PHY layer are operated by individual RAN nodes 511. This virtualization framework allows idle processor cores of multiple RAN nodes 511 to execute other virtualized applications. In some specific implementations, separate RAN nodes 511 may represent a single RAN node 511 connected to the network via a separate F1 interface ( Figure 5 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 8), and the gNB-CU may be operated by a server (not shown) located in the RAN 510 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 511 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 501 and is connected to the 5GC (e.g., Figure 7 CN 720) RAN node.

[0082] In a V2X scenario, one or more of the RAN nodes 511 may be an RSU or act 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, wherein 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, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 501 (vUE 501). 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 vehicle 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, etc. In addition 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. In addition 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 weather-resistant 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.

[0083] Any of the multiple RAN nodes 511 may serve as an endpoint for the air interface protocol and may be the first point of contact for multiple UEs 501. In some embodiments, any of the multiple RAN nodes 511 may perform various logical functions of the RAN 510, 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.

[0084] In an embodiment, UE 501 may be configured to communicate with each other or with any AN node in RAN node 511 using OFDM communication signals on 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), but the scope of the embodiment is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0085] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 511 to the UE 501, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each 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 a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0086] According to various embodiments, UE 501, 502 and RAN nodes 511, 512 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as "licensed spectrum" and / or "licensed frequency band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0087] To operate in the unlicensed spectrum, the UE 501, 502 and the RAN nodes 511, 512 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, the UE 501, 502 and the RAN nodes 511, 512 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.

[0088] LBT is a mechanism for equipment (e.g., UE 501, 502, RAN nodes 511, 512, etc.) to sense a 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 a CCA that utilizes at least an ED to determine whether other signals are present on the channel in order 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 expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0089] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 501 or 502, AP 506, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and YECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of 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.

[0090] The LAA mechanism is built on the 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, so the maximum aggregated bandwidth is 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 may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0091] 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. Other serving cells are referred to as SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 501, 502 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an 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 start positions within the same subframe.

[0092] The PDSCH carries user data and higher layer signaling to multiple UEs 501. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It can also inform the UE 501 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 501b within a cell) can be performed on any of the RAN nodes 511 based on channel quality information fed back from any of the UEs 501. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the multiple UEs 501.

[0093] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, 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 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).

[0094] 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 nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0095] RAN nodes 511 may be configured to communicate with each other via interface 512. In embodiments where system 500 is an LTE system (eg, when CN 520 is a Figure 6 ), the interface 512 may be an X2 interface 512. The X2 interface may be defined between two or more RAN nodes 511 (e.g., two or more eNBs, etc.) connected to the EPC 520, and / or between two eNBs connected to the EPC 520. In some specific 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 transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 501 for user data; information about PDCP PDUs that were not delivered to the UE 501; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0096] When system 500 is a 5G or NR system (e.g., when CN 520 is Figure 7In an implementation scheme of the 5GC 720 in the 5GC 520, the interface 512 may be an Xn interface 512. The Xn interface is defined between two or more RAN nodes 511 (e.g., two or more gNBs, etc.) connected to the 5GC 520, between a RAN node 511 (e.g., a gNB) and an eNB connected to the 5GC 520, and / or between two eNBs connected to the 5GC 520. 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 501 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 511. The mobility support may include context transfer from the old (source) serving RAN node 511 to the new (target) serving RAN node 511; and control of the user plane tunnel between the old (source) serving RAN node 511 and the new (target) serving RAN node 511. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer 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 on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0097] RAN 510 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 520. CN 520 may include a plurality of network elements 522 configured to provide various data and telecommunication services to customers / users (e.g., users of UE 501) connected to CN 520 via RAN 510. The components of CN 520 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 520 may be referred to as a network slice, and a logical instance of a portion of CN 520 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 may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0098] Generally speaking, the application server 530 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 530 may also be configured to support one or more communication services for the UE 501 via the EPC 520 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0099] In an embodiment, CN 520 may be a 5GC (referred to as "5GC 520" or the like), and RAN 510 may be connected to CN 520 via an NG interface 513. In an embodiment, NG interface 513 may be divided into two parts: an NG user plane (NG-U) interface 514, which carries traffic data between RAN node 511 and UPF; and an S1 control plane (NG-C) interface 515, which is a signaling interface between RAN node 511 and AMF. Figure 7 An implementation of CN 520 as 5GC 520 is discussed in more detail.

[0100] In an embodiment, CN 520 may be a 5G CN (referred to as "5GC 520", etc.), while in other embodiments, CN 520 may be an EPC. In the case where CN 520 is an EPC (referred to as "EPC 520", etc.), RAN 510 may be connected to CN 520 via an S1 interface 513. In an embodiment, S1 interface 513 may be divided into two parts: an S1 user plane (S1-U) interface 514, which carries traffic data between RAN node 511 and S-GW; and an S1-MME interface 515, which is a signaling interface between RAN node 511 and MME. Figure 6 An exemplary architecture is shown in which CN 520 is an EPC 520.

[0101] Figure 6 FIG. 6 shows an exemplary architecture of a system 600 including a first CN 620 according to various embodiments. In this example, the system 600 may implement the LTE standard, where the CN 620 is a Figure 5 In addition, UE 601 can communicate with Figure 5 UE 501 is the same as or similar to UE 501, and E-UTRAN 610 may be Figure 5 The CN 620 may be a RAN that is the same as or similar to the RAN 510 of the mobile network, and may include the RAN node 511 discussed previously. The CN 620 may include an MME 621, an S-GW 622, a P-GW 623, an HSS 624, and an SGSN 625.

[0102] The MME 621 may be similar in function to the control plane of a conventional SGSN, and may implement MM functions to keep track of the current location of the UE 601. The MME 621 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPSMM" or "EMM" in the E-UTRAN system) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge of the current location of the UE 601, providing user identity confidentiality to users / subscribers, and / or performing other similar services. Each UE 601 and the MME 621 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in the UE 601 and the MME 621. The MM context may be a data structure or database object that stores MM-related information of the UE 601. The MME 621 may be coupled to the HSS 624 via an S6a reference point, to the SGSN 625 via an S3 reference point, and to the S-GW 622 via an S11 reference point.

[0103] SGSN 625 may be a node that serves UE 601 by tracking the location of individual UE 601 and performing security functions. In addition, SGSN 625 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 621; handling of UE 601 time zone functions, as specified by MME 621; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 621 and SGSN 625 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

[0104] The HSS 624 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 620 may include one or several HSSs 624, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, the HSS 624 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc. The S6a reference point between the HSS 624 and the MME 621 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the EPC 620 between the HSS 624 and the MME 621.

[0105] The S-GW 622 may terminate the S1 interface 513 ( Figure 6 The S-GW 622 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 622 and the MME 621 may provide a control plane between the MME 621 and the S-GW 622. The S-GW 622 may be coupled to the P-GW 623 via the S5 reference point.

[0106] The P-GW 623 may terminate the SGi interface toward the PDN 630. The P-GW 623 may communicate with the PDN 630 via the IP interface 525 (see, e.g., Figure 5 ) routes data packets between EPC 620 and external networks such as a network including an application server 530 (alternatively referred to as an "AF"). In an embodiment, P-GW 623 can communicate with the EPC 620 via an IP communication interface 525 (see, e.g., Figure 5 ) is communicatively coupled to an application server ( Figure 5 Application server 530 or Figure 6The S5 reference point between the P-GW 623 and the S-GW 622 may provide user plane tunneling and tunnel management between the P-GW 623 and the S-GW 622. Due to the mobility of the UE 601 and whether the S-GW 622 needs to be connected to a non-colocated P-GW 623 for the required PDN connectivity, the S5 reference point may also be used for S-GW 622 relocation. The P-GW 623 may also include nodes for policy implementation and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 623 and the packet data network (PDN) 630 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 623 may be coupled to the PCRF 626 via a Gx reference point.

[0107] PCRF 626 is a policy and charging control element of EPC 620. In a non-roaming scenario, there may be a single PCRF 626 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 601. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 601: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 626 may be communicatively coupled to application server 630 via P-GW 623. Application server 630 may signal PCRF 626 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 626 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which function starts QoS and charging as specified by application server 630. The Gx reference point between PCRF 626 and P-GW 623 may allow for the transfer of QoS policies and charging rules from PCRF 626 to PCEF in P-GW 623. The Rx reference point may reside between PDN 630 (or "AF 630") and PCRF 626.

[0108] Figure 7The architecture of a system 700 including a second CN 720 according to various embodiments is shown. The system 700 is shown to include a UE 701, which may be the same or similar to the previously discussed UE 501 and UE 601; a (R) AN 710, which may be the same or similar to the previously discussed RAN 510 and RAN 610, and which may include the previously discussed RAN node 511; and a DN 703, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 720. The 5GC 720 may include an AUSF 722; an AMF 721; an SMF 724; an NEF 723; a PCF 726; an NRF 725; an UDM 727; an AF 728; an UPF 702; and an NSSF 729.

[0109] UPF 702 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 703, and a branch point to support multi-host PDU sessions. UPF 702 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) on the user plane, perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 702 may include an uplink classifier for supporting routing of traffic flows to data networks. DN 703 may represent various network operator services, Internet access, or third-party services. DN 703 may include or be similar to the application server 530 discussed previously. UPF 702 may interact with SMF 724 via the N4 reference point between SMF 724 and UPF 702.

[0110] AUSF 722 may store data for authentication of UE 701 and handle authentication-related functions. AUSF 722 may facilitate a common authentication framework for various access types. AUSF 722 may communicate with AMF 721 via an N12 reference point between AMF 721 and AUSF 722; and may communicate with UDM 727 via an N13 reference point between UDM 727 and AUSF 722. In addition, AUSF 722 may present an interface based on Nausf services.

[0111] AMF 721 may be responsible for registration management (e.g., responsible for registering UE 701, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 721 may be the termination point of the N11 reference point between AMF 721 and SMF 724. AMF 721 may provide transport for SM messages between UE 701 and SMF 724, and act as a transparent proxy for routing SM messages. AMF 721 may also provide a transport mechanism for UE 701 and SMSF ( Figure 7 721 provides transmission for SMS messages between (R)AN 710 and AMF 721). AMF 721 may act as a SEAF, which may include interaction with AUSF 722 and UE 701, receiving intermediate keys established as a result of the UE 701 authentication process. In the case of using USIM-based authentication, AMF 721 may retrieve security material from AUSF 722. AMF 721 may also include an SCM function that receives keys from SEA for deriving access network-specific keys. In addition, AMF 721 may be a termination point for the RAN CP interface, which may include or be an N2 reference point between (R)AN 710 and AMF 721; and AMF 721 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0112] The AMF 721 may also support NAS signaling with the UE 701 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 710 and the AMF 721 for the control plane, and may be the termination point for the N3 reference point between the (R) AN 710 and the UPF 702 for the user plane. Thus, the AMF 721 may process N2 signaling for PDU sessions and QoS from the SMF 724 and the AMF 721, 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 QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 701 and the AMF 721 via the N1 reference point between the UE 701 and the AMF 721, and relay uplink and downlink user plane packets between the UE 701 and the UPF 702. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 701. The AMF 721 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 721 and the AMF 721 and the 5G-EIR ( Figure 7 The termination point of the N17 reference point between the two (not shown).

[0113] UE 701 may need to register with AMF 721 in order to receive network services. RM is used to register UE 701 with the network (e.g., AMF 721) or deregister UE, and establish a UE context in the network (e.g., AMF 721). UE 701 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 701 is not registered with the network, and the UE context in AMF 721 does not maintain the valid location or routing information of UE 701, so AMF 721 cannot reach UE 701. In the RM-REGISTERED state, UE 701 is registered with the network, and the UE context in AMF 721 may maintain the valid location or routing information of UE 701, so AMF 721 can reach UE 701. In the RM-REGISTERED state, UE 701 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 notify the network that UE 701 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0114] AMF 721 may store one or more RM contexts for UE 701, each RM context being associated with a specific access to the network. An RM context may be a data structure, a database object, or the like, which indicates or stores, among other things, a registration status and a periodic update timer for each access type. AMF 721 may also store a 5GC MM context which may be the same or similar to the (E)MM context discussed previously. In various embodiments, AMF 721 may store CE mode B restriction parameters for UE 701 in an associated MM context or RM context. AMF 721 may also derive values ​​from usage setting parameters of the UE already stored in the UE context (and / or MM / RM context) when necessary.

[0115] The CM may be used to establish and release a signaling connection between the UE 701 and the AMF 721 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 701 and the CN 720, 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 an N2 connection of the UE 701 between the AN (e.g., the RAN 710) and the AMF 721. The UE 701 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 701 operates in the CM-IDLE state / mode, the UE 701 may not have a NAS signaling connection established with the AMF 721 over the N1 interface, and there may be a (R)AN 710 signaling connection (e.g., N2 and / or N3 connection) for the UE 701. When the UE 701 operates in the CM-CONNECTED state / mode, the UE 701 may have a NAS signaling connection established with the AMF 721 through the N1 interface, and there may be a (R)AN 710 signaling connection (e.g., N2 and / or N3 connection) for the UE 701. Establishing an N2 connection between the (R)AN 710 and the AMF 721 may cause the UE 701 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 710 and the AMF 721 is released, the UE 701 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0116] SMF 724 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via AMF over N2; and determining the SSC mode of 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 a UE 701 and a data network (DN) 703 identified by a data network name (DNN). The PDU session may be established upon request by UE 701, modified upon request by UE 701 and 5GC 720, and released upon request by UE 701 and 5GC 720 using NAS SM signaling exchanged between UE 701 and SMF 724 over the N1 reference point. Upon request from an application server, 5GC 720 may trigger a specific application in UE 701. In response to receiving the trigger message, UE 701 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 701. The identified applications in UE 701 may establish a PDU session to a specific DNN. SMF 724 may check whether the UE 701 request complies with user subscription information associated with UE 701. In this regard, SMF 724 may retrieve and / or request to receive update notifications about SMF 724 level subscription data from UDM 727.

[0117] SMF 724 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. In a roaming scenario, an N16 reference point between two SMFs 724 may be included in the system 700, which may be located between another SMF 724 in the visited network and the SMF 724 in the home network. In addition, SMF 724 may present an interface based on Nsmf services.

[0118] NEF 723 may provide a device for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 728), edge computing or fog computing systems, etc. In such embodiments, NEF 723 may authenticate, authorize and / or restrict AF. NEF 723 may also convert information exchanged with AF 728 and information exchanged with internal network functions. For example, NEF 723 may convert between AF service identifiers and internal 5GC information. NEF 723 may also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. The information may be stored at NEF 723 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 723, and / or used for other purposes such as analysis. In addition, NEF 723 may present an interface based on Nnef services.

[0119] NRF 725 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 725 also maintains information of available NF instances and the services they support. 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 a program code. In addition, NRF 725 may present an interface based on Nnrf services.

[0120] PCF 726 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. PCF 726 may also implement FE to access subscription information related to policy decisions in the UDR of UDM 727. PCF 726 may communicate with AMF 721 via the N15 reference point between PCF 726 and AMF 721, which may include PCF 726 in a visited network and AMF 721 in a roaming scenario. PCF 726 may communicate with AF 728 via the N5 reference point between PCF 726 and AF728; and communicate with SMF 724 via the N7 reference point between PCF 726 and SMF 724. System 700 and / or CN 720 may also include an N24 reference point between PCF 726 (in the home network) and PCF 726 in the visited network. In addition, PCF 726 may present an interface based on Npcf services.

[0121] UDM 727 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 701. For example, subscription data may be transmitted between UDM 727 and AMF 721 via an N8 reference point between UDM 727 and AMF 721. UDM 727 may include two parts: application FE and UDR ( Figure 7 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 727 and PCF 726, and / or structured data for exposure and application data of NEF 723 (including PFD for application detection, application request information of multiple UE 701). Nudr service-based interface can be presented by UDR 221 to allow UDM 727, PCF 726 and NEF 723 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of related data changes in UDR. UDM may include 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. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. UDR can interact with SMF 724 via the N10 reference point between UDM 727 and SMF 724. UDM 727 may also support SMS management, where SMS-FE implements similar application logic discussed previously. In addition, UDM 727 may present an interface based on Nudm services.

[0122] AF 728 can provide the influence of applications on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 720 and AF 728 to provide information to each other via NEF 723, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 701 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 702 near UE 701 and perform traffic steering from UPF 702 to DN 703 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 728. In this way, AF 728 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 728 is considered a trusted entity, the network operator can allow AF 728 to interact directly with the relevant NF. In addition, AF 728 can present an interface based on Naf services.

[0123] NSSF 729 may select a set of network slice instances to serve UE 701. If necessary, NSSF 729 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. NSSF 729 may also determine the AMF set, or a list of candidate AMFs 721, to serve UE 701 based on appropriate configuration and possibly by querying NRF 725. The selection of a set of network slice instances for UE 701 may be triggered by AMF 721, where UE 701 registers by interacting with NSSF 729, which may cause AMF 721 to change. NSSF 729 may interact with AMF 721 via the N22 reference point between AMF 721 and NSSF 729; and may communicate with AMF 721 via the N31 reference point ( Figure 7 The NSSF 729 may communicate with another NSSF 729 in the visited network (not shown). In addition, the NSSF 729 may present an interface based on the Nnssf service.

[0124] As discussed previously, CN 720 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages from / to other entities, such as SMS-GMSC / IWMSC / SMS routers, to / from UE 701. SMS may also interact with AMF 721 and UDM 727 for notification procedures that UE 701 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 727 when UE 701 is available for SMS).

[0125] CN 120 may also include Figure 7 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 may communicate with any NF and UDSF ( Figure 7 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or individual NFs may each have their own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on the Nudsf service ( Figure 7 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific equipment / 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.

[0126] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 7These interfaces and reference points are omitted. In one example, CN 720 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 621) and an AMF 721, to enable intercommunication between CN 720 and CN 620. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 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.

[0127] Figure 8 An example of infrastructure equipment 800 according to some embodiments is shown. Infrastructure equipment 800 (or "system 800") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 511 and / or AP 506 shown and described previously), an application server 530, and / or any other element / device discussed herein. In other examples, system 800 can be implemented in or by a UE.

[0128] System 800 includes: application circuit 805, baseband circuit 810, one or more radio front end modules (RFEM) 815, memory circuit 820, power management integrated circuit (PMIC) 825, power tee circuit 830, network controller circuit 835, network interface connector 840, satellite positioning circuit 845 and user interface 850. In some embodiments, device 800 may include additional elements, such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the following components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0129] The application circuit 805 includes the following 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, I 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of application circuit 805 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage element to enable various applications or operating systems to run on system 800. In some embodiments, memory / storage element can be on-chip memory circuit, which 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.

[0130] The processor of the application circuit 805 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 805 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 805 may include one or more Intel FPGAs. 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 provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 800 may not utilize application circuit 805, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0131] In some implementations, the application circuit 805 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), and the like; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), and the like; ASICs, such as structured ASICs, and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 805 may include logic blocks or logic architectures, as well as other interconnected resources that may 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 805 may include a memory unit (e.g., an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a static memory (e.g., a static random access memory (SRAM), an anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), etc.

[0132] Baseband circuit 810 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. Fig.10 The various hardware electronic components of baseband circuit 810 are discussed.

[0133] The user interface circuit 850 may include one or more user interfaces designed to enable a user to interact with the system 800 or a peripheral component interface designed to enable a peripheral component to interact with the system 800. 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 touch pad, 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 interface, etc.

[0134] The radio front end module (RFEM) 815 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 separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.10Antenna array 1011), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 815 that combines both millimeter wave antennas and sub-millimeter waves.

[0135] The memory circuit 820 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 820 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0136] The PMIC 825 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 830 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 800 using a single cable.

[0137] The network controller circuit 835 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 800 via a network interface connector 840, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 835 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 835 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0138] The positioning circuit 845 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global navigation satellite 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., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 845 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 845 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 845 may also be part of or interact with the baseband circuit 810 and / or RFEM 815 to communicate with nodes and components of the positioning network. The positioning circuit 845 may also provide location data and / or time data to the application circuit 805, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 511, etc.).

[0139] Figure 8 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.

[0140] Fig. 9 An example of a platform 900 (or "device 900") according to various embodiments is shown. In an embodiment, the computer platform 900 may be suitable for use as a UE 501, 502, 601, an application server 530, and / or any other element / device discussed herein. The platform 900 may include any combination of components shown in the example. The components of the platform 900 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 900, or implemented as components otherwise incorporated within the chassis of a larger system. Fig. 9The block diagram is intended to show a high-level view of the components of computer platform 900. 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.

[0141] The application circuit 905 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 C or general programmable serial interface module, RTC, timer (including interval timer and watchdog timer), general I / O, memory card controller (such as SD MMC or similar controller), USB interface, MIPI interface and JTAG test access port. The processor (or core) of the application circuit 905 can be coupled with or can include a memory / storage element, and can be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 900. In some embodiments, 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.

[0142] The processor 805 of the application circuit 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, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 805 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0143] As an example, the processor of the application circuit 905 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 905 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 905 can be part of a system on a chip (SoC), in which the application circuit 905 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.

[0144] Additionally or alternatively, the application circuit 905 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 905 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 905 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 a lookup table (LUT), etc.

[0145] Baseband circuit 910 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. Fig.10 The various hardware electronic components of baseband circuit 910 are discussed.

[0146] The RFEM 915 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 separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.10 Antenna array 1011), and 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 915 that combines both millimeter wave antennas and sub-millimeter waves.

[0147] The memory circuit 920 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 920 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 (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 920 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 920 may be implemented as one or more of a solder-in package 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 a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 920 may be an on-chip memory or register associated with the application circuit 905. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 920 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 900 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0148] Removable memory circuitry 923 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 900. 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.

[0149] The platform 900 may further include an interface circuit (not shown) for connecting external devices to the platform 900. External devices connected to the platform 900 via the interface circuit include a sensor circuit 921 and an electromechanical component (EMC) 922, and a removable memory device coupled to a removable memory circuit 923.

[0150] Sensor circuitry 921 comprises a device, module, or subsystem that is intended 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 a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a 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.

[0151] The EMC 922 includes devices, modules or subsystems that are intended to enable the platform 900 to change its state, position and / or orientation or to move or control a mechanism or (sub) system. In addition, the EMC 922 may be configured to generate messages / signaling and send messages / signaling to other components of the platform 900 to indicate the current state of the EMC 922. Examples of the EMC 922 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 900 is configured to operate one or more EMCs 922 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0152] In some specific implementations, the interface circuit may connect the platform 900 to the positioning circuit 945. The positioning circuit 945 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 945 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 945 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 945 may also be part of the baseband circuit 810 and / or the RFEM 915 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 945 may also provide position data and / or time data to application circuitry 905 , 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.

[0153] In some implementations, the interface circuit may connect the platform 900 with a near field communication (NFC) circuit 940. The NFC circuit 940 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 940 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 900. The NFC circuit 940 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 circuit 940 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 a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 940, or initiate data transfer between the NFC circuit 940 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 900.

[0154] The driver circuit 946 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 900. The driver circuit 946 may include various drivers to allow other components of the platform 900 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 900. For example, the driver circuit 946 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 900, a sensor driver for obtaining sensor readings of the sensor circuit 921 and controlling and allowing access to the sensor circuit 921, an EMC driver for obtaining an actuator position of the EMC 922 and / or controlling and allowing access to the EMC 922, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0155] A power management integrated circuit (PMIC) 925 (also referred to as “power management circuit 925”) may manage power provided to various components of the platform 900. Specifically, the PMIC 925 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 910. When the platform 900 is capable of being powered by a battery 930, for example, when the device is included in a UE 501, 502, 601, the PMIC 925 may be generally included.

[0156] In some embodiments, the PMIC 925 may control or otherwise be part of various power saving mechanisms of the platform 900. For example, if the platform 900 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 900 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 900 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 900 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers off again. The platform 900 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few 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 be significantly delayed, and it is assumed that the delay is acceptable.

[0157] The battery 930 can power the platform 900, but in some examples, the platform 900 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 930 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, the battery 930 can be a typical lead-acid car battery.

[0158] In some implementations, the battery 930 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 900 to track the state of charge (SoCh) of the battery 930. The BMS may be used to monitor other parameters of the battery 930, such as the state of health (SoH) and state of function (SoF) of the battery 930 to provide fault prediction. The BMS may transmit information about the battery 930 to the application circuit 905 or other components of the platform 900. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 905 to directly monitor the voltage of the battery 930 or the current from the battery 930. The battery parameters may be used to determine actions that the platform 900 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0159] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 930. In some examples, the power block XS30 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 900. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 930 and therefore on 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 Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0160] The user interface circuit 950 includes various input / output (I / O) devices present in or connected to the platform 900, and includes one or more user interfaces designed to implement user interaction with the platform 900 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 900. The user interface circuit 950 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 status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 900. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 921 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used 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. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0161] Although not shown, the components of platform 900 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.

[0162] Fig.10 1010 and exemplary components of a radio front end module (RFEM) 1015 according to various embodiments are shown. The baseband circuit 1010 corresponds to Figure 8 The baseband circuit 810 and Fig. 9 Baseband circuit 910. RFEM 1015 corresponds to Figure 8 RFEM 815 and Fig. 9 RFEM 915. As shown, RFEM 1015 may include radio frequency (RF) circuit 1006, front end module (FEM) circuit 1008, and antenna array 1011 coupled together at least as shown.

[0163] The baseband circuit 1010 includes circuits and / or control logic components that are configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 1006. 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 circuit of the baseband circuit 1010 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 1010 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 circuit 1010 is configured to process baseband signals received from the receive signal path of the RF circuit 1006 and generate baseband signals for the transmit signal path of the RF circuit 1006. The baseband circuit 1010 is configured to communicate with the application circuit 805 / 905 (see Figure 8 and Fig. 9 ) to generate and process baseband signals and control the operation of RF circuit 1006. Baseband circuit 1010 can handle various radio control functions.

[0164] The aforementioned circuits and / or control logic components of the baseband circuit 1010 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 1004A, a 4G / LTE baseband processor 1004B, a 5G / NR baseband processor 1004C, or some other baseband processors 1004D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 1004A-1004D may be included in a module stored in the memory 1004G and executed via a central processing unit (CPU) 1004E. In other embodiments, some or all of the functions of the baseband processors 1004A-D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 1004G may store program code of a real-time OS (RTOS), which, when executed by the CPU 1004E (or other baseband processor), will enable the CPU 1004E (or other baseband processor) to manage resources of the baseband circuit 1010, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-TimeExecutive (VRTX) provided by Express Provided Depend on FreeRTOS and REX OS provided by Open Kernel (OK) OKL4 is provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 1010 includes one or more audio digital signal processors (DSPs) 1004F. The audio DSP 1004F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0165] In some embodiments, each of processors 1004A-1004E includes a corresponding memory interface to send data to / receive data from memory 1004G. Baseband circuit 1010 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 1010; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 8 to XApplication circuit interface for sending data to / receiving data from the application circuit 805 / 905 of T; Fig.10 RF circuit 1006 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 / receiving power or control signals from the PMIC 925.

[0166] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 1010 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnect subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, 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 1010 may include a protocol processing circuit with 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., the radio front end module 1015).

[0167] although Fig.10Not shown, but in some embodiments, the baseband circuit 1010 includes various processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuit") to operate one or more wireless communication protocols and various processing devices to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 1010 and / or the RF circuit 1006 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In a first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 1010 and / or the RF circuit 1006 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In a second example, the protocol processing circuit will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit may include one or more memory structures (e.g., 1004G) 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 circuit 1010 may also support radio communications of more than one wireless protocol.

[0168] The various hardware elements of the baseband circuit 1010 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 1010 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the components of the baseband circuit 1010 and the RF circuit 1006 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 1010 may be implemented as a separate SoC communicatively coupled to the RF circuit 1006 (or multiple instances of the RF circuit 1006). In yet another example, some or all of the components of the baseband circuit 1010 and the application circuit 805 / 905 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0169] In some embodiments, the baseband circuit 1010 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 1010 may support communications with E-UTRAN or other WMANs, WLANs, WPANs. Embodiments in which the baseband circuit 1010 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0170] RF circuit 1006 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1006 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1006 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 1008 and providing baseband signals to baseband circuit 1010. RF circuit 1006 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 1010 and providing RF output signals for transmission to FEM circuit 1008.

[0171] In some embodiments, the receive signal path of the RF circuit 1006 may include a mixer circuit 1006a, an amplifier circuit 1006b, and a filter circuit 1006c. In some embodiments, the transmit signal path of the RF circuit 1006 may include a filter circuit 1006c and the mixer circuit 1006a. The RF circuit 1006 may also include a synthesizer circuit 1006d for synthesizing frequencies used by the mixer circuit 1006a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1006a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1008 based on the synthesized frequency provided by the synthesizer circuit 1006d. The amplifier circuit 1006b may be configured to amplify the down-converted signal, and the filter circuit 1006c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1010 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required. In some embodiments, the mixer circuit 1006a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0172] In some embodiments, mixer circuit 1006a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1006d to generate an RF output signal for FEM circuit 1008. The baseband signal may be provided by baseband circuit 1010 and may be filtered by filter circuit 1006c.

[0173] In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a 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 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may be configured for superheterodyne operation.

[0174] 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 circuit 1006 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1010 may include a digital baseband interface to communicate with RF circuit 1006.

[0175] 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.

[0176] In some embodiments, synthesizer circuit 1006d may 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 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0177] Synthesizer circuit 1006d may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 1006a of RF circuit 1006. In some embodiments, synthesizer circuit 1006d may be a fractional-N / N+1 synthesizer.

[0178] 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 circuit 1010 or the application circuit 805 / 905 according to 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 circuit 805 / 905.

[0179] The synthesizer circuit 1006d of the RF circuit 1006 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.

[0180] In some embodiments, the synthesizer circuit 1006d can be configured to generate a carrier frequency as an 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 can be 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 1006 can include an IQ / polarity converter.

[0181] FEM circuitry 1008 may include a receive signal path that may include circuitry configured to operate on RF signals received from antenna array 1011, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1006 for further processing. FEM circuitry 1008 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 1006 for transmission by one or more antenna elements in antenna array 1011. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in RF circuitry 1006, only in FEM circuitry 1008, or in both RF circuitry 1006 and FEM circuitry 1008.

[0182] In some embodiments, the FEM circuit 1008 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 1008 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 1008 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1006). The transmit signal path of the FEM circuit 1008 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 1006), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 1011.

[0183] The antenna array 1011 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 1010 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 1011 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 1011 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 1011 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 1006 and / or the FEM circuit 1008 using a metal transmission line or the like.

[0184] The processor of the application circuit 805 / 905 and the processor of the baseband circuit 1010 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1010 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 805 / 905 can 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 an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail below.

[0185] Fig.11 Various protocol functions that can be implemented in a wireless communication device according to various embodiments are shown. Specifically, Fig.11The present invention includes an arrangement 1100 showing the interconnection between various protocol layers / entities. Various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards are provided. Fig.11 The following description, but Fig.11 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0186] In addition to other higher layer functions not shown, the protocol layers of arrangement 1100 may also include one or more of PHY 1110, MAC 1120, RLC 1130, PDCP 1140, SDAP 1147, RRC 1155, and NAS layer 1157. These protocol layers may include one or more service access points (e.g., Fig.11 Items 1159, 1156, 1150, 1149, 1145, 1135, 1125 and 1115).

[0187] PHY 1110 can send and receive physical layer signals 1105, which can be received or sent from one or more other communication devices to one or more other communication devices. Physical layer signals 1105 may include one or more physical channels, such as those discussed herein. PHY 1110 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurements used by higher layers (e.g., RRC1155). PHY 1110 may also further perform error detection on transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels and MIMO antenna processing. In an embodiment, an instance of PHY 1110 may process a request from an instance of MAC1120 via one or more PHY-SAP 1115 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 1115 may include one or more transmission channels.

[0188] An instance of MAC 1120 may process requests from and provide indications to an instance of RLC 1130 via one or more MAC-SAPs 1125. These requests and indications transmitted via MAC-SAP 1125 may include one or more logical channels. MAC 1120 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 1110 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 1110 via transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0189] An instance of RLC 1130 may process requests from an instance of PDCP 1140 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 1135. These requests and indications transmitted via RLC-SAPs 1135 may include one or more RLC channels. RLC 1130 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 1130 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 1130 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.

[0190] An instance of PDCP 1140 may process requests from an instance of RRC 1155 and / or an instance of SDAP 1147 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAP) 1145 and provide indications thereto. These requests and indications transmitted via PDCP-SAP 1145 may include one or more radio bearers. PDCP 1140 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reestablished, eliminate duplication of lower layer SDUs when lower layers are reestablished 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.).

[0191] An instance of SDAP 1147 may process requests from one or more higher layer protocol entities and provide instructions thereto via one or more SDAP-SAPs 1149. These requests and instructions transmitted via SDAP-SAPs 1149 may include one or more QoS flows. SDAP 1147 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 1147 may be configured for a separate PDU session. In the UL direction, NG-RAN 510 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 1147 of UE 501 may monitor the QFI of the DL packets of each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 1147 of UE 501 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To implement the reflective mapping, the NG-RAN 710 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 1155 configuring the SDAP 1147 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 1147. In an embodiment, the SDAP 1147 may be used only in NR implementations and may not be used in LTE implementations.

[0192] The RRC 1155 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 1110, MAC 1120, RLC 1130, PDCP 1140, and SDAP 1147, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 1155 may process requests from one or more NAS entities 1157 and provide instructions thereto via one or more RRC-SAPs 1156. The main services and functions of the RRC 1155 may include broadcasting of system information (e.g., included in a MIB or SIB related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between the UE 501 and the RAN 510 (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.

[0193] NAS 1157 may form the highest layer of the control plane between UE 501 and AMF 721. NAS 1157 may support mobility and session management procedures of UE 501 to establish and maintain an IP connection between UE 501 and P-GW in the LTE system.

[0194] According to various embodiments, one or more protocol entities of arrangement 1100 may be implemented in UE 501, RAN node 511, AMF 721 in NR implementation or MME 621 in LTE implementation, UPF 702 in NR implementation or S-GW 622 and P-GW 623 in LTE implementation, 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 501, gNB 511, AMF 721, 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 511 may host the RRC 1155, SDAP 1147, and PDCP 1140 of the gNB that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 511 may each host the RLC 1130, MAC 1120, and PHY 1110 of gNB 511.

[0195] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 1157, RRC 1155, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110. In this example, an upper layer 1160 may be built on top of NAS 1157, which includes an IP layer 1161, SCTP 1162, and an application layer signaling protocol (AP) 1163.

[0196] In a NR specific implementation, AP 1163 can be an NG application protocol layer (NGAP or NG-AP) 1163 for the NG interface 513 defined between the NG-RAN node 511 and the AMF 721, or AP 1163 can be an Xn application protocol layer (XnAP or Xn-AP) 1163 for the Xn interface 512 defined between two or more RAN nodes 511.

[0197] The NG-AP 1163 may support the functions of the NG interface 513 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 511 and the AMF 721. The NG-AP 1163 services may include two groups: UE-associated services (e.g., services related to UE 501, 502) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 511 and the AMF 721). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 511 involved in a specific paging area; a UE context management function for allowing the AMF 721 to establish, modify and / or release the UE context in the AMF 721 and the NG-RAN node 511; a mobility function for the UE 501 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 signaling transport function for transmitting or rerouting NAS messages between the UE 501 and the AMF 721; a NAS node selection function for determining the association between the AMF 721 and the UE 501; an NG interface management function for setting up the NG interface and monitoring errors through the NG interface; a warning message sending function for providing a means to transmit a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 501 and the AMF 721; a NAS node selection function for determining the association between the AMF 721 and the UE 501; a ... 520 Configuration transmission function of requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 511; and / or other similar functions.

[0198] The XnAP 1163 may support the functions of the Xn interface 512 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 511 (or E-UTRAN 610), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, procedures related to dual connectivity, etc. The XnAP global procedures may include procedures that are not related to a specific UE 501, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0199] In an LTE specific implementation, AP 1163 can be an S1 application protocol layer (S1-AP) 1163 for an S1 interface 513 defined between an E-UTRAN node 511 and an MME, or AP 1163 can be an X2 application protocol layer (X2AP or X2-AP) 1163 for an X2 interface 512 defined between two or more E-UTRAN nodes 511.

[0200] The S1 application protocol layer (S1-AP) 1163 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 an interaction unit between the E-UTRAN node 511 and the MME 621 within the LTE CN 520. The S1-AP 1163 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0201] The X2AP 1163 may support the functions of the X2 interface 512 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 520, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure that is not related to a specific UE 501, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

[0202] The SCTP layer (alternatively referred to as the SCTP / IP layer) 1162 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 1162 may ensure reliable delivery of signaling messages between the RAN node 511 and the AMF 721 / MME 621 based in part on the IP protocol supported by the IP 1161. The Internet Protocol layer (IP) 1161 may be used to perform packet addressing and routing functions. In some implementations, the IP layer 1161 may deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 511 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0203] In a second example, the user plane protocol stack may include SDAP 1147, PDCP 1140, RLC 1130, MAC 1120, and PHY 1110 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 501, RAN node 511, and UPF 702 in NR implementation, or communication between S-GW 622 and P-GW 623 in LTE implementation. In this example, the upper layer 1151 may be built on top of SDAP 1147 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 1152, a general packet radio service (GPRS) tunneling protocol for a user plane layer (GTP-U) 1153, and a user plane PDU layer (UPPDU) 1163.

[0204] The transport network layer 1154 (also referred to as the "transport layer") may be built on top of an IP transport, and a GTP-U 1153 may be used on top of a UDP / IP layer 1152 (including a UDP layer and an IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the "Internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets, for example, in any of the IPv4, IPv6, or PPP formats.

[0205] GTP-U 1153 may 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 may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 1152 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 511 and the S-GW 622 may utilize the S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 1110), an L2 layer (e.g., MAC 1120, RLC 1130, PDCP 1140, and / or SDAP 1147), a UDP / IP layer 1152, and a GTP-U 1153. S-GW 622 and P-GW 623 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 1152, and a GTP-U 1153. As previously discussed, the NAS protocol may support the mobility and session management procedures of UE 501 to establish and maintain an IP connection between UE 501 and P-GW 623.

[0206] In addition, despite Fig.11Not shown, but an application layer may exist above the AP 1163 and / or transport network layer 1154. The application layer may be a layer where a user of the UE 501, RAN node 511, or other network element interacts with a software application, for example, executed by the application circuit 805 or the application circuit 905, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuit 1010) of the UE 501 or RAN node 511. In some implementations, the IP layer and / or the application layer may provide the same or similar functionality as layers 5 to 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).

[0207] Fig.12 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, Fig.12 A schematic diagram of hardware resources 1200 is shown, including one or more processors (or processor cores) 1210, one or more memory / storage devices 1220, and one or more communication resources 1230, each of which can be communicatively coupled via a bus 1240. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1202 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1200.

[0208] Processor 1210 may include, for example, processor 1212 and processor 1214. Processor 1210 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.

[0209] The memory / storage device 1220 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1220 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.

[0210] The communication resources 1230 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1204 or one or more databases 1206 via the network 1208. For example, the communication resources 1230 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0211] The instructions 1250 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1210 to perform any one or more of the methodologies discussed herein. The instructions 1250 may reside in whole or in part in at least one of the processor 1210 (e.g., in a cache memory of the processor), the memory / storage device 1220, or any suitable combination thereof. In addition, any portion of the instructions 1250 may be transmitted to the hardware resources 1200 from any combination of the peripheral device 1204 or the database 1206. Thus, the memory of the processor 1210, the memory / storage device 1220, the peripheral device 1204, and the database 1206 are examples of computer-readable and machine-readable media.

[0212] 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 following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits 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 shown in the example section below.

[0213] Example

[0214] Embodiment 1 includes a method comprising configuring authorized resources using NR in an unlicensed spectrum by a CG UE.

[0215] Embodiment 2 includes a method for utilizing COT sharing according to Embodiment 1 or some other embodiments herein.

[0216] Embodiment 3 includes the method according to embodiment 2 or some other embodiments herein, wherein the UE is to transmit UCI with a three-bit field for COT sharing offset indication.

[0217] Embodiment 4 includes the method according to embodiment 2 or some other embodiments herein, further comprising indicating the COT shared offset value using a UCI format.

[0218] Embodiment 5 includes the method according to embodiment 2 or some other embodiments herein, and also includes providing an indication of a subframe offset to the gNB using a parameter indicating when the UE will monitor a time slot of a PDCCH containing a DFI for a current transmission.

[0219] Embodiment 6 includes a method according to embodiment 2 or some other embodiments herein, wherein the UE transmits UCI having a one-bit field for COT sharing, where "1" indicates that in X time slots from the signal, the GNB will be allowed to transmit in the shared COT, and "0" indicates that the COT is not shared.

[0220] Embodiment 7 comprises a method comprising configuring a UE with a common CORESET search space or with a UE-specific CORESET search space.

[0221] Embodiment 8 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 7, or any other method or process described herein.

[0222] Embodiment 9 may include one or more non-transitory computer-readable media, which include 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 or related to any one of Embodiments 1 to 7 or any other method or process described herein.

[0223] Embodiment 10 may include an apparatus including logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 7 or any other method or process described herein.

[0224] Embodiment 11 may include methods, techniques or processes described or related to any one of Embodiments 1 to 7, or parts or components thereof.

[0225] Embodiment 12 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 7, or a portion thereof.

[0226] Embodiment 13 may include a signal as described or related to any one of embodiments 1 to 7, or a portion or component thereof.

[0227] Embodiment 14 may include signals in a wireless network as shown and described herein.

[0228] Embodiment 15 may include a method of communicating in a wireless network as shown and described herein.

[0229] Embodiment 16 may include a system for providing wireless communications as shown and described herein.

[0230] Embodiment 17 may include an apparatus for providing wireless communications as shown and described herein.

[0231] Unless explicitly 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 form disclosed. Modifications and variations are possible in view of the above teachings or may be acquired from the practice of the various embodiments.

[0232] abbreviation

[0233] For the purposes of this document, the following abbreviations may be applied to the examples and implementations discussed herein.

[0234] 3GPP Third Generation Partnership Project

[0235] 4G Fourth Generation

[0236] 5G Fifth Generation

[0237] 5GC 5G Core Network

[0238] ACK

[0239] AF Application Function

[0240] AM Confirmation Mode

[0241] AMBR Aggregate Maximum Bit Rate

[0242] AMF Access and Mobility Management Function

[0243] AN Access Network

[0244] ANR Automatic Neighbor Relation

[0245] AP application protocol, antenna port, access point

[0246] API Application Programming Interface

[0247] APN Access Point Name

[0248] ARP Assignment Reserve Priority

[0249] ARQ Automatic Repeat Request

[0250] AS Access Layer

[0251] ASN.1 Abstract Syntax Notation

[0252] AUSF authentication server function

[0253] AWGN Additive White Gaussian Noise

[0254] BCH Broadcast Channel

[0255] BER Bit Error Rate

[0256] BFD Beam Fault Detection

[0257] BLER Block Error Rate

[0258] BPSK Binary Phase Shift Keying

[0259] BRAS Broadband Remote Access Server

[0260] BSS Business Support System

[0261] BS Base Station

[0262] BSR Buffer Status Report

[0263] BW Bandwidth

[0264] BWP Bandwidth Part

[0265] C-RNTI Cell Radio Network Temporary Identifier

[0266] CA Carrier Aggregation, Certification Authority

[0267] CAPEX Capital Expenditure

[0268] CBRA Contention-based random access

[0269] CC component carrier, country code, encryption checksum

[0270] CCA Clear Channel Assessment

[0271] CCE Control Channel Element

[0272] CCCH Common Control Channel

[0273] CE Coverage Enhancement

[0274] CDM Content Delivery Network

[0275] CDMA Code Division Multiple Access

[0276] CFRA Contention-free random access

[0277] CG Cell Group

[0278] CI Cell ID

[0279] CID Cell ID (eg, positioning method)

[0280] CIM Common Information Model

[0281] CIR Carrier to Interference Ratio

[0282] CK Cryptographic Key

[0283] CM Connection Management, Conditionally Mandatory

[0284] CMAS Commercial Mobile Alert Service

[0285] CMD command

[0286] CMS Cloud Management System

[0287] CO Conditional optional

[0288] CoMP Coordinated Multipoint

[0289] CORESET Control Resource Set

[0290] COTS Commercial Off-the-Shelf

[0291] CP Control Plane, Cyclic Prefix, Attachment Point

[0292] CPD Connection Point Descriptor

[0293] CPE user terminal equipment

[0294] CPICH Common Pilot Channel

[0295] CQI Channel Quality Indicator

[0296] CPU CSI processing unit, central processing unit

[0297] C / R Command / Response field bit

[0298] CRAN Cloud Radio Access Network, Cloud RAN

[0299] CRB Common Resource Block

[0300] CRC Cyclic Redundancy Check

[0301] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0302] C-RNTI Cell RNTI

[0303] CS Circuit Switched

[0304] CSAR Cloud Service Archive

[0305] CSI Channel State Information

[0306] CSI-IM CSI interference measurement

[0307] CSI-RS CSI reference signal

[0308] CSI-RSRP CSI reference signal received power

[0309] CSI-RSRQ CSI reference signal reception quality

[0310] CSI-SINR CSI signal to interference plus noise ratio

[0311] CSMA Carrier Sense Multiple Access

[0312] CSMA / CA CSMA with collision avoidance

[0313] CSS Common Search Space, Cell Specific Search Space

[0314] CTS Clear to Send

[0315] CW codeword

[0316] CWS Contention Window Size

[0317] D2D Device to Device

[0318] DC Dual Connection, Direct Current

[0319] DCI Downlink Control Information

[0320] DF deployment preferences

[0321] DL Downlink

[0322] DMTF Distributed Management Task Force

[0323] DPDK Data Plane Development Kit

[0324] DM-RS, DMRS Demodulation Reference Signal

[0325] DN Data Network

[0326] DRB Data Radio Bearer

[0327] DRS Discovery Reference Signal

[0328] DRX Discontinuous Reception

[0329] DSL Domain Specific Language Digital Subscriber Line

[0330] DSLAM DSL Access Multiplexer

[0331] DwPTS Downlink Pilot Time Slot

[0332] E-LAN ​​Ethernet Local Area Network

[0333] E2E End-to-End

[0334] ECCA Extended Clear Channel Assessment, Extended CCA

[0335] ECCE Enhanced Control Channel Element, Enhanced CCE

[0336] ED Energy Detection

[0337] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0338] EGMF exposes governance management functions

[0339] EGPRS Enhanced GPRS

[0340] EIR Equipment Identity Register

[0341] eLAA Enhanced License Assisted Access, enhanced LAA

[0342] EM Component Manager

[0343] eMBB Enhanced Mobile Broadband

[0344] EMS Component Management System

[0345] eNB Evolved Node B, E-UTRAN Node B

[0346] EN-DC E-UTRA-NR Dual Connectivity

[0347] EPC Evolved Packet Core

[0348] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0349] EPRE Energy per resource element

[0350] EPS Evolved Packet System

[0351] EREG Enhanced REG, enhanced resource element group

[0352] ETSI European Telecommunications Standards Institute

[0353] ETWS Earthquake and Tsunami Warning System

[0354] eUICC embedded UICC, embedded universal integrated circuit card

[0355] E-UTRA Evolved UTRA

[0356] E-UTRAN Evolved UTRAN

[0357] EV2X Enhanced V2X

[0358] F1AP F1 Application Protocol

[0359] F1-C F1 control plane interface

[0360] F1-U F1 User Plane Interface

[0361] FACCH Fast Associated Control Channel

[0362] FACCH / F Fast Associated Control Channel / Full Rate

[0363] FACCH / H Fast Associated Control Channel / Half Rate

[0364] FACH Forward Access Channel

[0365] FAUSCH Fast Uplink Signalling Channel

[0366] FB Function Block

[0367] FBI Feedback

[0368] FCC Federal Communications Commission

[0369] FCCH Frequency Correction Channel

[0370] FDD Frequency Division Duplex

[0371] FDM Frequency Division Multiplexing

[0372] FDMA Frequency Division Multiple Access

[0373] FE Front End

[0374] FEC Forward Error Correction

[0375] FFS for further study

[0376] FFT Fast Fourier Transform

[0377] feLAA Further Enhanced License Assisted Access, further enhanced LAA

[0378] FN Frame Number

[0379] FPGA Field Programmable Gate Array

[0380] FR Frequency Range

[0381] G-RNTI GERAN Radio Network Temporary Identity

[0382] GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

[0383] GGSN Gateway GPRS Support Node

[0384] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Chinese: Global Navigation Satellite System)

[0385] gNB Next Generation Node B

[0386] gNB-CU gNB centralized unit, next generation Node B centralized unit

[0387] gNB-DU gNB distributed unit, next generation Node B distributed unit

[0388] GNSS Global Navigation Satellite System

[0389] GPRS General Packet Radio Service

[0390] GSM Global System for Mobile Communications, Mobile Experts Group

[0391] GTP GPRS Tunneling Protocol

[0392] GTP-U GPRS Tunneling Protocol for the User Plane

[0393] GTS Go to sleep signal (related to WUS)

[0394] GUMMEI Globally Unique MME Identifier

[0395] GUTI Globally Unique Temporary UE Identifier

[0396] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0397] HANDO, HO switch

[0398] HFN Superframe Number

[0399] HHO Hard Handover

[0400] HLR Home Location Register

[0401] HN Home Network

[0402] HO Handover

[0403] HPLMN Home Public Land Mobile Network

[0404] HSDPA High Speed ​​Downlink Packet Access

[0405] HSN Hopping Sequence Number

[0406] HSPA High Speed ​​Packet Access

[0407] HSS Home Subscriber Server

[0408] HSUPA High Speed ​​Uplink Packet Access

[0409] HTTP Hypertext Transfer Protocol

[0410] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL (i.e. port 443))

[0411] I-Block Information Block

[0412] ICCID Integrated Circuit Card Identifier

[0413] ICIC Inter-cell Interference Coordination

[0414] ID

[0415] IDFT Inverse Discrete Fourier Transform

[0416] IE Information Elements

[0417] IBE In-Band Emission

[0418] IEEE Institute of Electrical and Electronics Engineers

[0419] IEI Information Element Identifier

[0420] IEIDL Information Element Identifier Data Length

[0421] IETF Internet Engineering Task Force

[0422] IF Infrastructure

[0423] IM Interference Measurement, Intermodulation, IP Multimedia

[0424] IMC IMS credentials

[0425] IMEI International Mobile Equipment Identity

[0426] IMGI International Mobile Group Identity

[0427] IMPI IP Multimedia Privacy Identity

[0428] IMPU IP Multimedia Public Identity

[0429] IMS IP Multimedia Subsystem

[0430] IMSI International Mobile Subscriber Identity

[0431] IoT

[0432] IP Internet Protocol

[0433] Ipsec IP security, Internet Protocol security

[0434] IP-CAN IP connection access network

[0435] IP-M IP Multicast

[0436] IPv4 Internet Protocol version 4

[0437] IPv6 Internet Protocol version 6

[0438] IR

[0439] IS Synchronization

[0440] IRP Integration Reference Point

[0441] ISDN Integrated Services Digital Network

[0442] ISIM IM Service Identity Module

[0443] ISO International Organization for Standardization

[0444] ISP Internet Service Provider

[0445] IWF interworking function

[0446] I-WLAN Intercommunication WLAN

[0447] K is the constraint length of the convolutional code, USIM individual key

[0448] kB kilobyte (1000 bytes)

[0449] kbps kilobits per second

[0450] Kc Cryptographic key

[0451] Ki Individual user authentication key

[0452] KPI Key Performance Indicator

[0453] KQI Key Quality Indicator

[0454] KSI Key Set Identifier

[0455] ksps kilosymbols per second

[0456] KVM Kernel Virtual Machine

[0457] L1 Layer 1 (physical layer)

[0458] L1-RSRP Layer 1 reference signal received power

[0459] L2 Layer 2 (Data Link Layer)

[0460] L3 Layer 3 (Network Layer)

[0461] LAA License Assisted Access

[0462] LAN Local Area Network

[0463] LBT Listen before you speak

[0464] LCM Lifecycle Management

[0465] LCR Low Chip Rate

[0466] LCS Location Services

[0467] LCID Logical Channel ID

[0468] LI layer indicator

[0469] LLC Logical Link Control, Low Layer Compatibility

[0470] LPLMN Local PLMN

[0471] LPP LTE Positioning Protocol

[0472] LSB Least Significant Bit

[0473] LTE Long Term Evolution

[0474] LWA LTE-WLAN Aggregation

[0475] LWIP LTE / WLAN radio level integration with IPsec tunneling

[0476] LTE Long Term Evolution

[0477] M2M Machine to Machine

[0478] MAC Medium Access Control (Protocol Layer Context)

[0479] MAC Message Authentication Code (Security / Cryptography Context)

[0480] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0481] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0482] MANO Management and Orchestration

[0483] MBMS Multimedia Broadcast Multicast Service

[0484] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0485] MCC Mobile Country Code

[0486] MCG Master Cell Group

[0487] MCOT Maximum Channel Occupancy Time

[0488] MCS Modulation and Coding Scheme

[0489] MDAF Management Data Analysis Function

[0490] MDAS Management Data Analysis Service

[0491] Minimization of MDT-driven testing

[0492] ME Mobile Equipment

[0493] MeNB Master eNB

[0494] MER message error rate

[0495] MGL Measurement Gap Length

[0496] MGRP measurement gap repetition period

[0497] MIB Master Information Block, Management Information Base

[0498] MIMO Multiple Input Multiple Output

[0499] MLC Mobile Location Center

[0500] MM Mobility Management

[0501] MME Mobility Management Entity

[0502] MN Master Node

[0503] MO measurement object, mobile station calling

[0504] MPBCH MTC Physical Broadcast Channel

[0505] MPDCCH MTC Physical Downlink Control Channel

[0506] MPDSCH MTC Physical Downlink Shared Channel

[0507] MPRACH MTC Physical Random Access Channel

[0508] MPUSCH MTC Physical Uplink Shared Channel

[0509] MPLS Multi-Protocol Label Switching

[0510] MS Mobile Station

[0511] MSB Most Significant Bit

[0512] MSC Mobile Switching Center

[0513] MSI minimum system information, MCH scheduling information

[0514] MSID Mobile Station Identifier

[0515] MSIN Mobile Station Identification Number

[0516] MSISDN Mobile Subscriber ISDN Number

[0517] MT mobile station called, mobile terminal

[0518] MTC Machine Type Communication

[0519] mMTC Massive MTC, massive machine type communication

[0520] MU-MIMO Multi-User MIMO

[0521] MWUS MTC wake-up signal, MTC WUS

[0522] NACK Negative Acknowledgement

[0523] NAI Network Access Identifier

[0524] NAS Non-Access Stratum, Non-Access Stratum

[0525] NCT Network Connection Topology

[0526] NEC network capabilities exposed

[0527] NE-DC NR-E-UTRA dual connectivity

[0528] NEF Network Exposure Function

[0529] NF Network Function

[0530] NFP Network Forwarding Path

[0531] NFPD Network Forwarding Path Descriptor

[0532] NFV Network Function Virtualization

[0533] NFVI NFV Infrastructure

[0534] NFVO NFV Orchestrator

[0535] NG Next generation, next generation

[0536] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0537] NM Network Manager

[0538] NMS Network Management System

[0539] N-PoP Network Point of Presence

[0540] NMIB, N-MIB Narrowband MIB

[0541] NPBCH Narrowband Physical Broadcast Channel

[0542] NPDCCH Narrowband Physical Downlink Control Channel

[0543] NPDSCH Narrowband Physical Downlink Shared Channel

[0544] NPRACH Narrowband Physical Random Access Channel

[0545] NPUSCH Narrowband Physical Uplink Shared Channel

[0546] NPSS Narrowband Primary Synchronization Signal

[0547] NSSS Narrowband Secondary Synchronization Signal

[0548] NR New Radio, Neighbor Relations

[0549] NRF NF Repository Functionality

[0550] NRS Narrowband Reference Signal

[0551] NS Network Services

[0552] NSA Non-standalone operation mode

[0553] NSD Network Service Descriptor

[0554] NSR Network Service Record

[0555] NSSAI Network Slice Selection Assistance Information

[0556] S-NNSAI Single NSSAI

[0557] NSSF network slice selection function

[0558] NW Network

[0559] NWUS Narrowband wake-up signal, narrowband WUS

[0560] NZP Non Zero Power

[0561] O&M Operation and Maintenance

[0562] ODU2 Optical Channel Data Unit - Type 2

[0563] OFDM Orthogonal Frequency Division Multiplexing

[0564] OFDMA Orthogonal Frequency Division Multiple Access

[0565] OOB Out of Band

[0566] OOS Out of Sync

[0567] OPEX Operational Expenses

[0568] OSI Other System Information

[0569] OSS Operation Support System

[0570] OTA

[0571] PAPR Peak to Average Power Ratio

[0572] PAR Peak to Average Ratio

[0573] PBCH Physical Broadcast Channel

[0574] PC Power Control, Personal Computer

[0575] PCC Primary Component Carrier, Primary CC

[0576] Pcell Primary cell

[0577] PCI Physical Cell ID, Physical Cell Identity

[0578] PCEF Policy and Charging Enforcement Function

[0579] PCF Policy Control Function

[0580] PCRF Policy Control and Charging Rules Function

[0581] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0582] PDCCH Physical Downlink Control Channel

[0583] PDCP Packet Data Convergence Protocol

[0584] PDN Packet Data Network, Public Data Network

[0585] PDSCH Physical Downlink Shared Channel

[0586] PDU Protocol Data Unit

[0587] PEI Permanent Equipment Identifier

[0588] PFD Packet Flow Description

[0589] P-GW PDN Gateway

[0590] PHICH Physical Hybrid ARQ Indicator Channel

[0591] PHY Physical Layer

[0592] PLMN Public Land Mobile Network

[0593] PIN Personal Identification Number

[0594] PM performance measurement

[0595] PMI Precoding matrix indicator

[0596] PNF Physical Network Function

[0597] PNFD Physical Network Functional Descriptor

[0598] PNFR Physical Network Function Record

[0599] POC PTT over Cellular

[0600] PP, PTP Point to Point

[0601] PPP Point-to-Point Protocol

[0602] PRACH Physical RACH

[0603] PRB Physical Resource Block

[0604] PRG Physical Resource Group

[0605] ProSe Proximity-based Services

[0606] PRS Positioning Reference Signal

[0607] PRR Packet Receive Radio

[0608] PS Packet Service

[0609] PSBCH Physical Sidelink Broadcast Channel

[0610] PSDCH Physical Sidelink Downlink Channel

[0611] PSCCH Physical Sidelink Control Channel

[0612] PSSCH Physical Sidelink Shared Channel

[0613] PSCell Primary SCell

[0614] PSS Primary Synchronization Signal

[0615] PSTN Public Switched Telephone Network

[0616] PT-RS Phase Tracking Reference Signal

[0617] PTT Push to Talk

[0618] PUCCH Physical Uplink Control Channel

[0619] PUSCH Physical Uplink Shared Channel

[0620] QAM Quadrature Amplitude Modulation

[0621] QCI QoS Class Identifier

[0622] QCL Quasi-Co-sited

[0623] QFI QoS flow ID, QoS flow identifier

[0624] QoS Quality of Service

[0625] QPSK Quadrature (Quaternary) Phase Shift Keying

[0626] QZSS Quasi-Zenith Satellite System

[0627] RA-RNTI Random Access RNTI

[0628] RAB Radio Access Bearer, Random Access Burst

[0629] RACH Random Access Channel

[0630] RADIUS Remote Authentication Dial-In User Service

[0631] RAN Radio Access Network

[0632] RAND random number (for authentication)

[0633] RAR Random Access Response

[0634] RAT Radio Access Technology

[0635] RAU Routing Area Update

[0636] RB Resource Block, Radio Bearer

[0637] RBG Resource Block Group

[0638] REG Resource Element Group

[0639] Rel Release

[0640] REQ Request

[0641] RF

[0642] RI Rank Indicator

[0643] RIV Resource Indicator Value

[0644] RL Radio Link

[0645] RLC Radio Link Control, Radio Link Control Layer

[0646] RLC AM RLC Acknowledgement Mode

[0647] RLC UM RLC Unacknowledged Mode

[0648] RLF Radio Link Failure

[0649] RLM Radio Link Monitoring

[0650] RLM-RS Reference signal for RLM

[0651] RM Registration Management

[0652] RMC Reference Measurement Channel

[0653] RMSI Remaining MSI, Remaining Minimum System Information

[0654] RN Relay Node

[0655] RNC Radio Network Controller

[0656] RNL Radio Network Layer

[0657] RNTI Radio Network Temporary Identifier

[0658] ROHC Robust Header Compression

[0659] RRC Radio Resource Control, Radio Resource Control Layer

[0660] RRM Radio Resource Management

[0661] RS reference signal

[0662] RSRP Reference Signal Received Power

[0663] RSRQ Reference Signal Received Quality

[0664] RSSI Reference Signal Strength Indicator

[0665] RSU Road Side Unit

[0666] RSTD Reference Signal Time Difference

[0667] RTP Real Time Protocol

[0668] RTS Ready to Send

[0669] RTT Round Trip Time

[0670] Rx receive, receive, receiver

[0671] S1AP S1 Application Protocol

[0672] S1-MME is used for S1 control plane

[0673] S1-U S1 for user plane

[0674] S-GW Service Gateway

[0675] S-RNTI SRNC Radio Network Temporary Identifier

[0676] S-TMSI SAE temporary mobile station identifier

[0677] SA Standalone Operation Mode

[0678] SAE system architecture evolution

[0679] SAP Service Access Point

[0680] SAPD Service Access Point Descriptor

[0681] SAPI Service Access Point Identifier

[0682] SCC Secondary Component Carrier, Secondary CC

[0683] SCell Secondary Cell

[0684] SC-FDMA Single Carrier Frequency Division Multiple Access

[0685] SCG Secondary Cell Group

[0686] SCM Security Context Management

[0687] SCS Subcarrier Spacing

[0688] SCTP Stream Control Transmission Protocol

[0689] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0690] SDL Supplemental Downlink

[0691] SDNF Structured Data Storage Network Function

[0692] SDP Service Discovery Protocol (Bluetooth related)

[0693] SDSF structured data storage function

[0694] SDU Service Data Unit

[0695] SEAF Security Anchoring Function

[0696] SeNB Assisted eNB

[0697] SEPP Security Edge Protection Proxy

[0698] SFI Slot Format Indicator

[0699] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[0700] SFN System Frame Number

[0701] SgNB

[0702] SGSN Serving GPRS Support Node

[0703] S-GW Service Gateway

[0704] SI System Information

[0705] SI-RNTI System Information RNTI

[0706] SIB System Information Block

[0707] SIM Subscriber Identity Module

[0708] SIP Session Initiation Protocol

[0709] SiP System in Package

[0710] SL Side Link

[0711] SLA Service Level Agreement

[0712] SM Session Management

[0713] SMF session management functions

[0714] SMS Short Message Service

[0715] SMSF SMS Function

[0716] SMTC SSB-based measurement timing configuration

[0717] SN Secondary node, serial number

[0718] SoC System on Chip

[0719] SON Self-Organizing Network

[0720] SpCell Special Cell

[0721] SP-CSI-RNTI Semi-persistent CSI RNTI

[0722] SPS Semi-persistent Scheduling

[0723] SQN Serial Number

[0724] SR Scheduling Request

[0725] SRB Signalling Radio Bearer

[0726] SRS Sounding Reference Signal

[0727] SS Sync Signal

[0728] SSB Synchronization Signal Block, SS / PBCH Block

[0729] SSBRI SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator

[0730] SSC Session and Service Continuity

[0731] SS-RSRP Reference signal received power based on synchronization signal

[0732] SS-RSRQ Reference signal reception quality based on synchronization signal

[0733] SS-SINR Signal to Interference and Noise Ratio based on synchronization signal

[0734] SSS Secondary synchronization signal

[0735] SSSG Search Space Group

[0736] SSSIF Search Space Set Indicator

[0737] SST Slice / Service Type

[0738] SU-MIMO Single User MIMO

[0739] SUL Supplementary Uplink

[0740] TA timing advance, tracking area

[0741] TAC Tracking Area Code

[0742] TAG Timing Advance Group

[0743] TAU Tracking Area Updates

[0744] TB Transfer Block

[0745] TBS Transport Block Size

[0746] TBD To be defined

[0747] TCI Transmission Configuration Indicator

[0748] TCP transport communication protocol

[0749] TDD Time Division Duplex

[0750] TDM Time Division Multiplexing

[0751] TDMA Time Division Multiple Access

[0752] TE Terminal Equipment

[0753] TEID Tunnel Endpoint Identifier

[0754] TFT Business Flow Template

[0755] TMSI Temporary Mobile Subscriber Identity

[0756] TNL Transport Network Layer

[0757] TPC Transmit Power Control

[0758] TPMI Transmitted Precoding Matrix Indicator

[0759] TR Technical Report

[0760] TRP,TRxP Transmission Receive Point

[0761] TRS Tracking Reference Signal

[0762] TRx Transceiver

[0763] TS Technical Specification, Technical Standard

[0764] TTI Transmission Time Interval

[0765] Tx transmission, transmission, transmitter

[0766] U-RNTI UTRAN Radio Network Temporary Identity

[0767] UART Universal Asynchronous Receiver and Transmitter

[0768] UCI Uplink Control Information

[0769] UE User Equipment

[0770] UDM Unified Data Management

[0771] UDP User Datagram Protocol

[0772] UDSF Unstructured Data Storage Network Function

[0773] UICC Universal Integrated Circuit Card

[0774] UL Uplink

[0775] UM Unconfirmed Mode

[0776] UML Unified Modeling Language

[0777] UMTS Universal Mobile Telecommunications System

[0778] UP User Plane

[0779] UPF User Plane Function

[0780] URI Uniform Resource Identifier

[0781] URL Uniform Resource Locator

[0782] URLLC Ultra-Reliable Low Latency

[0783] USB Universal Serial Bus

[0784] USIM Universal Subscriber Identity Module

[0785] USS UE-specific search space

[0786] UTRA UMTS Terrestrial Radio Access

[0787] UTRAN Universal Terrestrial Radio Access Network

[0788] UwPTS Uplink Pilot Time Slot

[0789] V2I Vehicle to Infrastructure

[0790] V2P Vehicle to Pedestrian

[0791] V2V Vehicle to Vehicle

[0792] V2X: Vehicle-to-Everything

[0793] VIM Virtualization Infrastructure Manager

[0794] VL Virtual Link

[0795] VLAN virtual LAN, virtual local area network

[0796] VM Virtual Machine

[0797] VNF Virtualized Network Function

[0798] VNFFG VNF forwarding graph

[0799] VNFFGD VNF Forwarding Graph Descriptor

[0800] VNFM VNF Manager

[0801] VoIP Voice over IP, Voice over Internet Protocol

[0802] VPLMN Visited Public Land Mobile Network

[0803] VPN Virtual Private Network

[0804] VRB Virtual Resource Block

[0805] WiMAX Worldwide Interoperability for Microwave Access

[0806] WLAN Wireless Local Area Network

[0807] WMAN Wireless Metropolitan Area Network

[0808] WPAN Wireless Personal Area Network

[0809] X2-C X2 control plane

[0810] X2-U X2 user plane

[0811] XML Extensible Markup Language

[0812] XRES Expected User Response

[0813] XOR

[0814] ZC Zadoff-Chu

[0815] ZP Zero Power

[0816] the term

[0817] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein.

[0818] 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 a memory (shared, dedicated, or group) configured to provide the described functions, 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 may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a 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 may be referred to as a specific type of circuit.

[0819] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuit" 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 circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[0820] As used herein, the term "interface circuit" refers to a circuit that enables, is a 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, etc.

[0821] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, 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. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0822] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0823] 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.

[0824] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) that is 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.

[0825] 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 a computer device, a mechanical device, a memory space, a processor / CPU time and / or a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage rate, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0826] 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 representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices for transmitting and receiving information over a RAT.

[0827] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0828] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through a wire or other interconnect connection, through a wireless communication channel or link, etc.

[0829] 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.

[0830] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0831] The term "SSB" refers to SS / PBCH block.

[0832] 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.

[0833] 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.

[0834] 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.

[0835] 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.

[0836] 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.

[0837] The term "serving cell" refers to a cell set including a special cell for a UE configured with CA / in RRC_CONNECTED and all secondary cells.

[0838] 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.

Claims

1. A user equipment UE for a wireless communication system in an unlicensed spectrum, wherein the UE is a configuration authorized UE, and the UE comprises: A processor circuit, the processor circuit being configured to: Obtaining a channel occupancy time COT in the unlicensed spectrum; Determining the number of consecutive subframes allocated for physical uplink shared channel PUSCH transmission to the base station according to the time domain configuration of the configuration-authorized UE; determining a number of remaining consecutive subframes among the number of consecutive subframes allocated for the PUSCH transmission to the base station; as well as Generate uplink control information UCI to indicate a COT sharing boundary, the COT sharing boundary occurs at the end of the remaining consecutive subframes, the UCI also indicates a time slot for monitoring physical downlink control channel PDCCH transmission; as well as a radio front end circuit coupled to the processor circuit, the radio front end circuit being configured to: transmitting the UCI in the PUSCH transmission during one of the remaining consecutive subframes, wherein the PUSCH transmission and the UCI are transmitted in a same time slot; and The processor circuit is further configured to: Downlink transmissions from the base station are monitored after the COT sharing boundary. 2 . The UE of claim 1 , wherein the radio front end circuit is further configured to transmit the UCI in more than one subframe of the remaining consecutive subframes. 3 . The UE according to claim 1 , wherein the UCI includes a COT shared offset indication using a plurality of bits, wherein the COT shared offset indication indicates the number of the remaining consecutive subframes.

4. The UE of claim 1 , wherein the UCI includes a COT sharing offset indication in a single bit field, wherein a value assigned to the single bit field indicates no COT sharing, or indicates COT sharing starting from a predetermined number of time slots from a time slot including the UCI. The UE according to claim 4 , wherein the predetermined number of time slots is configured by radio resource control (RRC) signaling.

6. The UE according to claim 1, wherein the processor circuit is further configured to generate the uplink control information UCI to indicate a time slot for monitoring a physical downlink control channel PDCCH transmission, the time slot for monitoring includes downlink feedback information DFI, the downlink feedback information corresponds to a PUSCH transmission in a time slot including the UCI, wherein the time slot for monitoring represents an offset from the time slot including the UCI. 7 . The UE of claim 1 , wherein the processor circuit is further configured to allow multiple uplink-downlink (UL-DL) switching points within the acquired COT using the UCI indicating the COT sharing boundary.

8. A method for wireless communication, the method comprising: Acquiring, by a user equipment UE used in a wireless communication system in an unlicensed spectrum, a channel occupancy time COT in the unlicensed spectrum, wherein the UE is a configuration authorized UE; Determining the number of consecutive subframes allocated for physical uplink shared channel PUSCH transmission to the base station according to the time domain configuration of the configuration-authorized UE; determining, at the UE, a number of remaining consecutive subframes among the number of consecutive subframes allocated for the PUSCH transmission to the base station; Generate uplink control information UCI at the UE to indicate a COT sharing boundary, the COT sharing boundary occurs at the end of the remaining consecutive subframes, and the UCI also indicates a time slot for monitoring physical downlink control channel PDCCH transmission; transmitting the UCI from the UE to the base station in the PUSCH transmission during one of the remaining consecutive subframes, wherein the PUSCH transmission and the UCI are transmitted in the same time slot; as well as Downlink transmissions from the base station are monitored at the UE after the COT sharing boundary. 9 . The method of claim 8 , further comprising transmitting the UCI from the UE to the base station in more than one subframe of the remaining consecutive subframes. 10 . The method of claim 8 , wherein the UCI comprises a COT shared offset indication using a plurality of bits, wherein the COT shared offset indication indicates the number of the remaining consecutive subframes.

11. The method of claim 8, wherein the UCI includes a COT sharing offset indication in a single bit field, wherein a value assigned to the single bit field indicates no COT sharing or indicates COT sharing starting from a predetermined number of time slots from a time slot including the UCI.

12. The method according to claim 11, wherein the predetermined number of time slots is configured by Radio Resource Control (RRC) signaling.

13. The method according to claim 8 further includes generating the uplink control information UCI at the UE to indicate a time slot for monitoring a physical downlink control channel PDCCH transmission, the time slot for monitoring includes downlink feedback information DFI, the downlink feedback information corresponds to a PUSCH transmission in a time slot including the UCI, wherein the time slot for monitoring represents an offset from the time slot including the UCI. 14 . The method of claim 8 , further comprising allowing a plurality of uplink-downlink (UL-DL) switching points within the acquired COT using the UCI indicating the COT sharing boundary.

15. A computer readable medium (CRM) comprising computer instructions, wherein when the computer instructions are executed by one or more processors of a user equipment (UE) for a wireless communication system in an unlicensed spectrum, the one or more processors are caused to: Acquire a channel occupancy time COT in the unlicensed spectrum, wherein the UE is a configuration authorized UE; Determining the number of consecutive subframes allocated for physical uplink shared channel PUSCH transmission to the base station according to the time domain configuration of the configuration-authorized UE; determining a number of remaining consecutive subframes among the number of consecutive subframes allocated for the PUSCH transmission to the base station; Generate uplink control information UCI to indicate a COT sharing boundary, the COT sharing boundary occurs at the end of the remaining consecutive subframes, the UCI also indicates a time slot for monitoring physical downlink control channel PDCCH transmission; as well as transmitting the UCI in the PUSCH transmission during one of the remaining consecutive subframes, wherein the PUSCH transmission and the UCI are transmitted in a same time slot; and Downlink transmissions from the base station are monitored after the COT sharing boundary.

16. The CRM of claim 15, wherein when executed, the computer instructions further cause the one or more processors to transmit the UCI in more than one subframe of the remaining consecutive subframes. 17 . The CRM of claim 15 , wherein the UCI comprises a COT shared offset indication using a plurality of bits, wherein the COT shared offset indication indicates the number of the remaining consecutive subframes.

18. The CRM of claim 15, wherein the UCI includes a COT sharing offset indication in a single bit field, wherein a value assigned to the single bit field indicates no COT sharing, or indicates COT sharing starting from a predetermined number of time slots from a time slot including the UCI, and wherein the predetermined number of time slots is fixed or configured by radio resource control (RRC) signaling.

19. The CRM of claim 15, wherein when executed, the computer instructions further cause the one or more processors to generate the uplink control information UCI to indicate a time slot for monitoring a physical downlink control channel (PDCCH) transmission, the time slot for monitoring comprising downlink feedback information (DFI), the downlink feedback information corresponding to a PUSCH transmission in a time slot including the UCI, wherein the time slot for monitoring represents an offset from the time slot including the UCI.

20. The CRM of claim 15, wherein when executed, the computer instructions further cause the one or more processors to allow multiple uplink-downlink (UL-DL) switch points within the acquired COT using the UCI indicating the COT sharing boundary.

Images