System and method for operating enhanced machine type communication (EMTC) and narrowband Internet of Things (NB-IOT) user equipment (UE) when connected to a 5G core network (5GCN)

Abstract

Some embodiments of the present disclosure include systems, devices, methods, and computer-readable media for use in a wireless network for operating an eMTC (enhanced machine type communication) user equipment (UE) and / or a NB‑IoT UE when connected to a 5G core network (5GCN). For example, some embodiments relate to a user equipment (UE). The UE includes a processor circuit and a radio front-end circuit. The processor circuit can be configured to use the radio front-end circuit and receive an indication from a non-access stratum (NAS) of a cell that a 5G core network (5GCN) is used for the cell. The processor circuit can be further configured to transmit a radio resource control (RRC) connection request using the radio front-end in response to an indication using the 5GCN.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application No. 62 / 796,487, filed on January 24, 2019, which is hereby incorporated by reference in its entirety. Background Art

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

[0004] Some embodiments of the present disclosure include systems, apparatus, methods, and computer-readable media for use in a wireless network operating an eMTC (enhanced machine type communication) user equipment (UE) and / or a narrowband Internet of Things (NB-IoT) UE when connected to a 5G core network (5GCN).

[0005] Some embodiments relate to a user equipment (UE). The UE includes a processor circuit and a radio front end circuit. The processor circuit can be configured to use the radio front end circuit and receive an indication from a non-access layer (NAS) of a cell to use a 5G core network (5GCN) for the cell. The processor circuit can be further configured to transmit a radio resource control (RRC) connection request using the radio front end in response to the indication using the 5GCN.

[0006] Some embodiments relate to a method. The method includes receiving, by a user equipment (UE) and from a non-access stratum (NAS) of a cell, an indication for the cell to use a 5G core network (5GCN). The method further includes transmitting a radio resource control (RRC) connection request to a radio access network (RAN) of the cell in response to the indication of using the 5GCN.

[0007] Some embodiments relate to a user equipment (UE). The UE includes a memory storing instructions and a processor. When executing the instructions, the processor is configured to receive an indication from a non-access stratum (NAS) of a cell that a 5G core network (5GCN) is used for the cell. The processor is further configured to transmit a radio resource control (RRC) connection request to a radio access network (RAN) of the cell in response to the indication of using 5GCN. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Depicted is an example of a MAC Control Element (CE) including a sub-header Logical Channel ID (LCID) according to some embodiments.

[0009] Figure 2Depicted is an example of a MAC Control Element (CE) including an extended sub-header Logical Channel ID (e-LCID) according to some embodiments.

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

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

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

[0013] Figure 6 Depicted are examples of infrastructure equipment according to various embodiments.

[0014] Figure 7 Depicted are exemplary components of a computer platform according to various embodiments.

[0015] Figure 8 Depicted are exemplary components of baseband circuitry and radio frequency circuitry according to various embodiments.

[0016] Fig. 9 is a diagram of various protocol functions that may be used in various protocol stacks according to various embodiments.

[0017] Fig.10 Components of a core network are shown according to various embodiments.

[0018] Fig.11 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.

[0019] Fig.12 Depicted are exemplary flow charts for practicing various embodiments discussed herein, for example, for operating a UE while connected to a 5G Core Network (5GCN).

[0020] Features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the accompanying drawings, in which like reference numerals identify corresponding elements throughout. In the drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit in the corresponding reference numeral. DETAILED DESCRIPTION

[0021] 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 various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may 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 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).

[0022] Rel-15 (3GPP Release 15) eMTC (enhanced machine type communication) and narrowband Internet of Things (NB-IoT) UEs do not support connectivity to 5GCN (5G core network). In SA2meeting#129bis, studies on cellular IoT support and evolution for 5G systems have been completed (details can be found in TR 23.724). RAN2 and RAN3 are expected to develop support for 5GCN connectivity for Rel-16 eMTC and NB-IoT UEs.

[0023] SA2 also sent LS S2-1813400 to the RAN notifying the following key RAN impacts arising from the study:

[0024] -Support extended DRX in CM-IDLE

[0025] - Support for extended DRX in CM-CONNECTED with RRC_INACTIVE (supports sleep cycles until NAS and SMS retransmission timers)

[0026] - Support EDT for data transmitted via NAS and user plane

[0027] -Support inter-UE QoS for data via NAS (resource optimization between different NB-IoT UEs)

[0028] - Supports restrictions on the use of enhanced overlays

[0029] -Deliver expected UE behavior information to the RAN

[0030] - Additional information in the SIB to indicate supported CIoT features; Indication of CIoT features supported by the UE in the RRC

[0031] In this disclosure, various RRC signaling procedures are described to support the above features of Rel-16 eMTC and NB-IoT UEs when connected to 5GCN.

[0032] Currently 5GCN does not support any user plane (UP) IoT optimization similar to EPC (LTE) support for UP IoT EPS optimization. UP IoT 5GS optimization refers to a new solution for UP IoT optimization defined for 5GCN. The present disclosure and methods and devices implementing various aspects thereof are applicable to all UEs supporting coverage enhancement (CE) operation (i.e., including normal LTE UEs operating in bandwidth reduction mode).

[0033] Example Implementation #1 Establishing a Connection to RAN (Radio Access Network) Supporting Connectivity to 5GCN

[0034] RRC Connection Request

[0035] In an embodiment, the eMTC UE may reuse rrcConnectionRequest-r15 when the UE wants to send an RRC Connection Request in its cell using 5G-S-TMSI monitoring paging.

[0036] For NB-IoT (Narrowband Internet of Things) UEs, a new UL CCCH message class extension may be used to define a new Radio Resource Connection (RRC) message information element (IE) (e.g., RRCConnectionRequest-NB-r16-IE). In another option, a key extension of the existing RRCConnectionRequest-NB message is used.

[0037] In another option, the spare bits in the RRCConnectionRequest-NB-r13-IE are used as an indication that the service request is for 5GCN, and the 40-bit string of S-TMSI in the IE InitialUE-Identity corresponds to ng-5G-S-TMSI-Part1.

[0038] Examples of key extensions for RRCConnectionRequest-NB.

[0039]

[0040] Alternatively, an example of an RRCConnectionRequest-NB-r13-IE extension, where if connectTo5GC-r16 is set to "1", InitialUE-Identity corresponds to InitialUE-Identity-5GC.

[0041]

[0042]

[0043] RRC connection reestablishment

[0044] In an implementation scheme, if the NB-IoT UE supports RRC connection reestablishment when AS security has not been enabled, the UE includes the InitialUE-Identity-5GC ID in the RRCConnectionReestablishmentRequest-NB. In one option, the 40-bit string of S-TMSI in the IE ReestabUE-Identity-CP-NB-r14 corresponds to ng-5G-S-TMSI-Part1. The RAN can blindly detect whether the S_TMSI corresponds to ng-5G-S-TMSI-Part1. The spare bit inRRCConnectionReestablishmentRequest-NB-r14-IE can be used to indicate that the S_TMSI corresponds to ng-5G-S-TMSI-Part1.

[0045] Similarly, for NAS security, NAS-MAC and NAS count must be sent to 5GCN. To this end, RAN can introduce new IEs in N2 signaling to include NAS-MAC and NAS-COUNT, so that they are sent to AMF.

[0046] In another option, the RRCConnectionReestablishmentRequest may be critically extended as shown below.

[0047]

[0048]

[0049] In an implementation, the remaining 8 bits of the ng-5G-S-TMSI may be sent in the RRCConnectionReestablishmentComplete-NB message.

[0050]

[0051] UP CIoT 5GS Optimization

[0052] When the UE uses UP CIoT 5GS optimization, the eMTC or NB-IoT UE may reuse the RRCConnectionResumeRequest-r13-IE, where resumeID-r13 is a new ID provided by the RAN corresponding to 5GCN during the suspension procedure. The RAN blindly tries to find out whether resumeID-r13 corresponds to EPC or 5GCN (or the UE is suspended while connected to EPC or 5GC). In another option, 1 spare bit may be used to indicate that the ResumeIdentity-r13 for NB-IoT and the resumeID-r13 or truncatedResumeID-r13 for eMTC correspond to 5GCN. Similarly, if any new RAN-based notification areas are defined for UP CIoT 5GS optimization, 1 spare bit in the ResumeCause (rna-Update) for eMTC and the EstablishmentCause-NB-r13 for NB-IoT may be used for the resumption cause for the RNA update.

[0053] For example, the spare bit connectTo5GC-r16 may be set to '1' to indicate that ResumeIdentity-r13 corresponds to 5GCN.

[0054]

[0055] In another option, a new UL CCCH message class extension is defined to send the RRC Connection Resumption Request message with the Resumption ID corresponding to 5GCN for both eMTC and NB-IoT.

[0056] Example of new UL CCCH message class extension for eMTC UE.

[0057] UL-CCCH-Message

[0058] The UL-CCCH-Message class is a set of RRC messages that can be sent from the UE to the E-UTRAN on the uplink CCCH logical channel.

[0059]

[0060]

[0061]

[0062] Similarly, for eMTC UEs, the spare bit in the RRCConnectionResumeRequest-5GC-r15-IE may be used to indicate that the fullI-RNTI-r15 corresponds to resumeID-r13 or the shortI-RNTI-r15 corresponds to truncatedResumeID-r13 of 5GCN.

[0063]

[0064] Similarly, for eMTC UE, the spare bit in RRCConnectionResumeRequest-r13-IE may be used to indicate that resumeIdentity corresponds to 5GCN.

[0065]

[0066] In another option, RRCConnectionResumeRequest-NB for NB-IoT may be critically extended so that ResumeIdentity-r13 corresponds to 5GCN.

[0067]

[0068] When the UE uses UP CIoT 5GS optimization, the RAN always provides the NCC in the suspend (or release) message, and the eMTC or NB-IoT UE can just reuse the AS security activation procedure defined for RRC inactivity or the entire procedure that is the same as resuming RRC connection from RRC_inactivity. In another option, the AS security activation procedure is the same as Rel-15 EDT, or the resumption procedure is the same as resuming Rel-15 EDT.

[0069] RRC connection setup complete message

[0070] If the RRC Connection Setup or Resume Request message in Msg3 indicates 5GCN, the eMTC UE may reuse the existing RRCConnectionSetupComplete message such that the indicated UE capabilities for the features (ce-ModeB-r13, up-CIoT-EPS-Optimisation-r13, cp-CIoT-EPS-Optimisation-r13) correspond to the same or similar features supported by 5GCN. attachWithoutPDN-Connectivity may be reported to 5GCN during the registration procedure or may also be reported in the RRCConnectionSetupComplete message. A new IE may be introduced to carry the UE capabilities from the RAN to the AMF in N2 signalling.

[0071] In another option, the RRCConnectionSetupComplete message may be extended to indicate capabilities to 5GCN alone.

[0072]

[0073] In addition, the RRC_Inactive feature may be optional for eMTC UE or NB-IoT UE. The UE may report capabilities to the RAN using the UE-EUTRA-Capability IE or UE-Capability-NB IE during initial connection establishment.

[0074] In another option, the UE may report the capabilities in the RRCConnectionSetupComplete message during the RRC connection establishment or registration procedure as shown below. The rrc-Inactive-r16 in the RRCConnectionSetupComplete message may be considered as a preference for the UE to move to the RRC Inactive state when the UE uses CP IoT 5GS optimization or UP IoT 5GS optimization or does not use any optimization.

[0075]

[0076]

[0077] For NB-IoT UEs, the RRCConnectionSetupComplete-NB message may be extended. In one option, since the RRC message in Msg3 indicates that the service request is for 5GCN, the up-CIoT-EPS-Optimisation-r13 capability (or attachWithoutPDN-Connectivity-r13) field may be reused for 5GCN.

[0078]

[0079] Example Implementation #2 Supports Coverage Limitations in RAN to Indicate and Enhance Connectivity with 5GCN

[0080] For eMTC UEs, cellAccessRelatedInfo-5GC-r15 in SIB1 can be reused as an indication of supported connectivity to 5GCN. Existing mechanisms such as cellSelectionInfoCE, PRACH configuration and RSRP-based access barring mechanism can be used for enhanced coverage limitation of RAN.

[0081] Similar to EPC, 5GC (AMF) also stores the usage settings (data or voice) of the UE. Based on the usage settings of the UE, the 5GCN sends an indication to the RAN via N2 signaling whether CE mode B is restricted or unrestricted for the UE. Similarly, the 5GCN can indicate to the RAN via N2 signaling whether the use of coverage enhancement is restricted.

[0082] In addition, SIB2 indicates whether CP or UP 5GS optimization is supported when connected to 5GCN. It also indicates whether CP-EDT and / or UP-EDT is supported when connected to 5GCN.

[0083]

[0084]

[0085] For NB-IoT, information related to new cell access connected to 5GCN and whether the cell is prohibited from connecting to 5GCN can be broadcast in SIB1-NB.

[0086]

[0087]

[0088]

[0089] Example Implementation #3 EDT Process When Optimized Using IoT 5GS

[0090] When EDT is used in UP IoT 5GS optimization or in RRC inactive state, the eMTC UE or NB IoT UE can reuse the same RRC connection recovery request message to connect to the 5GCN in CCCH, which multiplexes the UL data in DTCH in Msg3. The UE can reuse the same PRACH resources configured for EDT to receive a larger UL grant for Msg3. Similarly, the RRC connection release message can be reused in Msg4.

[0091] RRC / MAC Modeling for EDT Data Integrity Protection

[0092] However, in addition, when EDT is used, UL data can be integrity protected. To this end, the calculation of shortResumeMAC-I can be delayed until the hash code of the UL EDT data is available. For example, during the construction of the RRCConnectionResumeRequest message, the RRC first instructs the lower layer to resume integrity protection and the cryptographic algorithm, and constructs the SDU at the PDCP layer or the RLC layer or the MAC layer and requests the hash code of the UL SDU. If the hash code is calculated from the MAC SDU of the UL EDT data, the RLC layer provides the RLC SDU to the MAC layer without performing logical channel optimization through the MAC. Then considering only the hash code of the UL PDU, the RRC calculates shortResumeMAC-I and delivers the RRCConnectionResumeRequest message to the lower layer.

[0093] In another option, the newly calculated shortResumeMAC-I from the MAC SDU of the UL data is provided to the MAC layer and added in front of the MAC SDU and transmitted, while the RRCConnectionResumeRequest message still includes the shortResumeMAC-I calculated in the traditional way. When the RAN receives the UL data, after demultiplexing, the first two bytes or four bytes (16 or 32 bits) of the SDU in the DTCH should correspond to the newly calculated shortResumeMAC-I.

[0094] This RRC / MAC modeling for calculating the new shortResumeMAC-I for EDT is also applicable when the UE is connected to the EPC or when the UE is in RRC Inactive state.

[0095] For both eMTC and NB-IoT, when EDT is used in CP IoT 5GS optimization, a new UL-CCCH message class extension of a new RRCEarlyDataRequest message may be defined, or a critical extension of the existing RRCEarlyDataRequest may be defined, or a new non-critical extension of the RRCEarlyDataRequest may be defined.

[0096] An example of UL-CCCH message class extension is shown below.

[0097]

[0098]

[0099] An example of the key extensions of the RRCEarlyDataRequest message is shown below.

[0100]

[0101] Examples of non-critical extensions

[0102]

[0103]

[0104]

[0105] Similarly, when EDT is completed, the RAN may send a RRCEarlyDataComplete message in Msg4. In one option, a DL-CCCH message class extension may be used to introduce a new rrcEarlyDataComplete-r16 or the existing RRCEarlyDataComplete message may be extended to include more information about 5GCN, such as a shorter wait timer value and carrier redirection information. In another option, extendedWaitTime-r15 is reused (without a new wait time), but it is clear that when connected to 5GCN, a maximum value of 16 for extendedWaitTime-r15 may be configured.

[0106] Example

[0107]

[0108]

[0109] Example Implementation #4 Paging Monitoring When in RRC_IDLE or RRC_INACTIVE

[0110] When the UE is released from the 5GCN but N1 signaling is not disabled (i.e., S1 signaling is not enabled), in one option, the UE determines the paging narrowband (for NB-IoT non-anchor carriers), paging frame and paging time using the UE_ID calculated from the IMSI, and monitors only the S-TMSI or IMSI (I-RNTI inactive in RRC) in the paging message. This is done by the 5GCN (AMF) having a mapping function from NG-5G-S-TMSI to IMSI to calculate the UE ID for paging or the 5GCN requiring the MME to page the UE.

[0111] In another option, the UE monitors all UE IDs, S-TMSI, IMSI and NG-5G-S-TMSI (or I-RNTI) in the paging message, however the paging narrowband (for NB-IoT non-anchor carrier), paging frame and paging time are determined by the UEID calculated from the IMSI.

[0112] In another option, the UE monitors all UE IDs, S-TMSI, IMSI and NG-5G-S-TMSI (or I-RNTI) in the paging message, or in another option, the UE monitors only the NG-5G-S-TMSI (or I-RNTI if in RRC inactive state) in the paging message or both NG-5G-S-TMSI and I-RNTI in RRC inactive state, however, the paging narrowband (for NB-IoT non-anchor carrier), paging frame and paging time are determined by the UE ID calculated from the NG-5G-S-TMSI, as shown in color font below. For eMTC or NB-IoT UEs, the NG-5G-S-TMSI can also be used as a decimal number similar to the IMSI in the traditional UE ID calculation.

[0113] Example from TS 36.304 Section 7.1

[0114] -UE_ID:

[0115] If the UE supports E-UTRA connected to 5GC and NAS is instructed to use 5GC for the selected cell:

[0116] 5G-S-TMSI mod 1024 if P-RNTI is monitored on PDCCH.

[0117] If P-RNTI is monitored on NPDCCH, then 5G-S-TMSI mod 4096.

[0118] 5G-S-TMSI mod16384 if P-RNTI is monitored on MPDCCH or if P-RNTI is monitored on NPDCCH and the UE supports paging on non-anchor carriers and if paging configuration for non-anchor carriers is provided in system information.

[0119] other

[0120] If P-RNTI is monitored on PDCCH, then IMSI mod 1024.

[0121] If P-RNTI is monitored on NPDCCH, then IMSI mod 4096.

[0122] IMSI mod 16384 if P-RNTI is monitored on MPDCCH or if P-RNTI is monitored on NPDCCH and the UE supports paging on non-anchor carriers and if paging configuration for non-anchor carriers is provided in system information.

[0123] In another option, in order to redistribute the paging load between UEs connected to EPC and 5GCN, different weight factors can be defined for NB-IoT UEs connected to 5GCN, such as

[0124] -W(i): weight of NB-IoT paging carrier i.

[0125] -W: The total weight of all NB-IoT paging carriers, i.e., W = W(0) + W(1) + ... + W(Nn-1).

[0126] -W5G(i): Weight of NB-IoT paging carrier I when connected to 5GCN.

[0127] -W5G: The total weight of all NB-IoT paging carriers, i.e., W5G = W5G(0)+W5G(1)+…+W5G(Nn-1).

[0128] Similarly, for eMTC UE, a weight factor or probability factor can be defined to select a PNB when connecting to 5GCN.

[0129] In order to avoid waking up unintended UEs connected to the EPC when paging a UE connected to the 5GCN, a new DCI format for monitoring the P-RNTI on the MPDCCH or NPDCCH may be defined to monitor only the NG-5G-S-TMSI or I-RNTI in the paging message.

[0130] In another option, a new P-RNTI (e.g., P-RNTI-5G) may be defined so that UEs connected to 5GCN do not monitor the legacy P-RNTI on the MPDCCH or NPDCCH.

[0131] In order to reduce the size of paging messages for eMTC and NB-IoT, only the rightmost 40 bits of the NG-5G-S-TMSI may be included in the paging message, or a selected length of the NG-5G-S-TMSI may be included in the paging message.

[0132] Example of UE identity in a paging message.

[0133]

[0134] Alternatively the NG-5G-S-TMSI may be included as a decimal.

[0135]

[0136]

[0137] In another option, to reduce power consumption due to mobility, eMTC / NB-IoT UEs are allowed to camp in cells that do not support connectivity to 5GCN if the UE does not find any cell that supports connectivity to 5GCN. NAS allows the UE to camp in those cells without the need for deregistration and registration procedures. The UE can continue the process of registering to the EPC when there is any MO or MT paging.

[0138] In this case, the UE may continue to monitor the NG-5G-S-TMSI or IMSI and calculate the PO using the NG-5G-S-TMSI. In this case, the AMF also provides paging assistance information to the RAN, which does not support connectivity via S1 signaling by coordinating with the MME (i.e., to determine the PO and page the UE using the NG-5g-S-TMSI or IMSI).

[0139] In another option, the UE switches to conventional paging (monitoring the P-RNTI in the MPDCCH / NPDCCH and monitoring the IMSI or previous S-TMSI or NG-5G-S-STMI in the paging message). The PO is determined using the UE ID based on the IMSI. In this case, the AMF also provides paging assistance information to the RAN, which does not support connectivity via S1 signaling by coordinating with the MME (i.e., the RAN can determine the correct PO with the provided UE ID and page the UE using the NG-5g-S-TMSI or IMSI or previous S-TMSI), or the AMF also requests the MME to page the UE in those cells, or if the AMF does not receive any paging response from the UE.

[0140] Example Implementation #5 Support for RRC_Inactive State

[0141] For eMTC, the RRC inactive configuration (rrc-InactiveConfig-r15) and the steering CN type (cn-Type-r15) in the RRCConnectionRelease message and the carrier redirection information nr-r15 can be reused. When the UE does not support the RRC inactive configuration or the RRC inactive configuration is not provided, the steering CN type (cn-Type-r15) / carrier redirection information nr-r15 in the RRCConnectionRelease message is also applicable. For eDRX, a larger value of the DRX cycle (ran-PagingCycle-r15 of rf512 or rf1024) can be defined by extending the RRCConnectionRelease message. In addition, the parameter nB and the number of paging narrowbands can be defined for the RRC inactive state, or only additional values ​​of nB (T / 512 and T / 1024) can be defined as nB-v16xy.

[0142]

[0143] In another option, the number of paging narrowbands and the new version nB-v16xy may be defined as a radio resource common configuration in the system information.

[0144]

[0145]

[0146] For NB-IoT, this information can be added in the RRCConnectionRelease-NB message.

[0147]

[0148]

[0149] For NB-IoT in RRC inactive state, additional new configurations for paging weights for anchor carriers and non-anchor carriers, NPRACH probability for selecting NPRACH resources in the anchor carrier in each repetition level, and hybrid operation mode configuration may also be defined in RRCConnectionRelease-NB-v16xy-IEs or in SIB22-NB.

[0150] Example from RRCConnectionRelease-NB-v16xy-IE:

[0151]

[0152] In another option, dedicated RRC signaling may be used to provide the RRC inactivity configuration before releasing the UE (ie, not in the RRCConnectionRelease message).

[0153] In another option, when the eMTC or NB-IoT UE supports RRC Inactivity, the NG RAN uses the same UE-specific or default paging DRX cycle, the shortest of them, the notification area information used by the 5GCN, so that the UE monitors the I-RNTI in the paging message and uses the same calculation to determine the PO as if the UE is in idle state when connected to the 5GCN. The UE can still monitor the NG-5G-S-TMSI to know that it is CN paging.

[0154] In another option, RAN does not configure ran-PagingCycle and ran-NotificationAreaInfo as shown below. NG RAN receives assistance information about UE-specific DRX cycle (if any) and notification area information or suggested RAN notification area information from 5GCN (AMF) so that it can send RAN paging to necessary cells. Even if the UE is in RRC Inactive state, the UE does not need to require a new RNA or RNA update timer or a new RAN-based paging DRX cycle.

[0155] Examples of NB-IoT

[0156]

[0157] When in RRC inactivity, the eMTC UE may reuse the same RRCConnectionResumeRequest-5GC-r15-IE for the resumption request.

[0158] For NB-IoT UEs, a spare bit in the RRCConnectionResumeRequest-NB-r13-IE can be used (i.e., when connectTo5GC-Inactive-r16 is set to "1") to indicate that resumeID-r13 corresponds to I-RNTI-r15, and a spare bit can be used to add the establishment cause rna-Update in EstablishmentCause-NB-r13. In this case, delayTolerantAccess-v1330 is not used.

[0159]

[0160]

[0161] In another option, a new key extension of RRCConnectionResumeRequest-NB or a new UL CCCH message class extension may be defined for the RRC Connection Resume Request message (I-RNTI) with UE ID provided for RRC_Inactivity.

[0162]

[0163]

[0164] Similarly, when an eMTC / NB-IoT UE (including a normal LTE UE operating in reduced BW or CE mode) supports RRC Inactivity when connected to 5GCN, the same behavior as RRC_Inactivity may be used when establishing an RRC connection. In another option, the following options may be considered.

[0165] 1. When T300 expires or when cell reselection occurs while T300 or T302 is running, the UE discards the newly derived AS security key and returns to the RRC Inactive state (i.e., the UE returns to its initial state before initiating recovery from the RRC Inactive state.

[0166] 2. When the integrity protection of the RRC message in Msg4 fails, the UE returns to idle (not suspended) without triggering NAS recovery.

[0167] 3. An RRC Connection Release message or an RRC Connection Reject in response to a resume request from RRC Inactivity may also move the UE to RRC Idle with a Suspend indication (i.e., using UP IoT 5GS Optimization) or pure RRC Idle (without suspension).

[0168] 4. The UE may also be moved to pure RRC Idle (without suspension) in response to an RRC Connection Release message or an RRC Connection Reject in response to a Resume Request from RRC Inactivity.

[0169] 5. Similarly, when UP CIoT 5GS optimization is used, an RRC Connection Release message or RRC Connection Reject in response to a resume request from RRC Idle may also move the UE to RRC Inactive or RRC Idle (with or without suspension). In this case, when UP CIoT 5GS optimization is used, the UE activates AS security before sending Msg3.

[0170] 6. In response to an RRC Connection Rejection from a Resume Request for RRC Inactivity the UE may also be moved to RRC Idle with a Suspend Indication (i.e., using UP IoT 5GS Optimization), using the same NCC as used before sending Msg1, using the I-RNTI as the Resume ID, and using the stored UE Inactive AS Context without (or discarding) the rrc-InactiveConfig (i.e., not using ran-PagingCycle, periodic-RNAU-timer, but maintaining the NCC).

[0171] a. In this case, the RAN disconnects the N1 signaling. When the RRCConnectionResumeRequest is sent in the next resumption procedure, the eNB blindly detects whether the resumption ID is related to the I-RNTI that determines the UE's inactive AS context.

[0172] b. In another option, the UE reuses the rrcConnectionResumeRequest-r15 used during RRC inactivity.

[0173] 7. An RRC Connection Reject in response to a Resume Request from RRC Inactivity may also utilize a Suspend Indication (i.e., using UP IoT 5GS Optimization) to move the UE to RRC Idle, where the UE follows the same recovery procedure as the Connection Recovery procedure from RRC_Inactivity.

[0174] a. The only difference is that the UE does not apply rrc-InactiveConfig (ie, does not use ran-PagingCycle, periodic-RNAU-timer, but keeps using NCC) and does not monitor RAN paging.

[0175] 8. If the stored UE context still has a valid rrc-InactiveConfig (i.e., I-RNTI, ran-PagingCycle, ran-NotificationAreaInfo, periodic-RNAU-timer, and nextHopChainingCount) configured previously, the RRCConnectionReject message in response to a resume request from RRC Idle when using UP CIoT 5GS optimization may move the UE to the RRC Inactive state. To this end, the RRCConnectionReject message may be extended to use a new indication rrc-InactiveIndication-r16.

[0176] a. This may occur if the UE moves back to its previous RRC inactive state.

[0177] b. This may happen if the releaseCause received in the RRCConnectionRelease message indicates rrc-Suspend (or similar suspension indication when using UP CIoT 5GS optimization) but rrc-InactiveConfig was also received in the previous connection. In this case, the fullI-RNTI, shortI-RNTI, nextHopChainingCount, ran-NotificationAreaInfo, periodic-RNAU-timer and ran-PagingCycle provided in the rrc-InactiveConfig are stored in the UE context but not used.

[0178] c.rrc-InactiveIndication-r16 is received in the RRCConnectionReject message, but the UE does not have stored fullI-RNTI, shortI-RNTI, nextHopChainingCount, ran-NotificationAreaInfo, periodic-RNAU-timer and ran-PagingCycle, the UE follows the procedure for leaving RRC_CONNECTED with release cause "other" or "RRC recovery failure".

[0179]

[0180] In the RRC inactive state, in one option, the UE is not allowed to use the wake-up signal (WUS) feature. This reduces paging response delays and DL resources. In another option, WUS is supported and the same WUS configuration provided in the system information is used. In another option, a new WUS configuration is provided in the RRC connection release message.

[0181] In RRC Inactive state, long extended DRX can be supported, and all configurations of eDRX including new paging time window (PTW) and new eDRX cycle are controlled by RAN and configured by RAN via RRC Connection Release message. It is only supported if the UE indicates the capability to support eDRX in RRC Inactive, or the network supports it in RRC Idle state, or the network configures it in RRC Idle state. RAN also indicates the use of eDRX in RRC Inactive to AMF.

[0182] The existing calculations of the paging superframe (PH), PTW start (PTW_start) and PTW end (PTW_end) can be reused in RRC inactivity. The UE ID used to calculate PH, PTW_start and PTW_end can be the same as the UE ID based on the NG-5G-S-TMSI used to calculate the paging frame and paging time in both RRC inactive and RRC idle states, or can be the same as the UE_ID_H used for idle mode eDRX, but based on bits b31, b30..., b0 of the NG-5G-S-TMSI in both RRC inactive and RRC idle states.

[0183] Since the anchor RAN buffers the DL data, if the UE uses a long eDRX cycle, the RAN notifies the AMF about the delay to deliver the DL data to the UE. If the UE uses eDRX, it also notifies the AMF about the CN paging response delay. When the UE uses long eDRX with PTW and a cell reselection occurs, the UE may release the eDRX configuration for RRC inactivity and notify the network (perform NAS recovery). In another option, the UE may still keep using eDRX as long as it is within the RAN notification area or CN tracking area. The existing systemInfoModification-eDRX may be reused to update the system information.

[0184] In another option, if the RAN configures long eDRX to the UE, it also provides CN paging assistance information to the AMF via N2 signaling. The RAN may include PH, PTW_start and PTW_end parameters.

[0185] In another option, if the network has configured UE eDRX for RRC idle state, the network (or AMF) provides the same eDRX parameters to the RAN as part of the assistance information to RRC inactive. Therefore, the configured eDRX parameters are the same in RRC idle state and RRC inactive state. If the RAN configures eDRX in RRC inactive, it also indicates to the AMF the situation where the AMF needs to send CN paging. In this case, the RAN only needs to enable the use of eDRX in RRC inactive state via the RRC Connection Release message.

[0186] Example in RRCConnectionRelease-NB-v16xy-IE

[0187]

[0188] In another option, when eDRX is used in RRC inactive state (or RRC idle state), the PTW always starts in subframe x (e.g., =0) and it always ends in subframe y (e.g., =1023), or the PTW length is always L seconds (e.g., =10.24 seconds). The values ​​of X, y, and L can be hard-coded or configured. The paging superframe (PH) can be determined using the following formula. The UE ID can be based on a hash ID or the same UE ID used to calculate PF and PO and Z can be hard-coded or configured (e.g., z=2).

[0189] H-SFN mod z=UE_ID mod z

[0190] Alternatively the pH can be determined using conventional formulas.

[0191] In another option, the RAN indicates the paging superframe (PH) to the UE only in the RRC inactive configuration. This indicates that the UE monitors the PO only in this PH. The RAN may also provide a list of paging superframes (PH) for which the UE may monitor the PO. Alternatively, the RAN may also indicate the starting PH and the number (or in radio frames) length of the H-SFN in case the UE may monitor the PO. The PO calculation is the same as that used for monitoring paging in RRC inactivity.

[0192] In another option, the RAN may configure the UE eDRX offset from H-SFM = x (or = 0) for the number of H-SFNs and the length of the eDRX cycle for the number of H-SFNs in the RRC inactive configuration. The PTW may be a fixed length or may be configured as L radio frames or H-SFNs.

[0193] In another option, the eDRX cycle length, paging superframe (PH), PTW length and PTW offset from SFN=x(=0) are provided in the RRC inactive configuration to avoid any calculations.

[0194] In another option, the RAN may configure a long eDRX cycle (i.e., =1H-SFN, 2H-SN, etc.) and provide a paging superframe (PH) in the configuration. The PTW length may be equal to the default DRX or UE-specific DRX or the shorter of them, so that there is one PO in the long eDRX cycle. In addition, a paging frame (PF) offset from SFN=x (=0) or from the calculated PF may be provided to distribute the paging load.

[0195] When the network configures eDRX for the UE to use in RRC Idle state, all the above options may be applicable.

[0196] Example 6 Using AS RAI

[0197] The UE may use the Access Stratum (AS) Release Assistance Indicator (RAI) by setting BSR=0 to the RAI when the RAI is activated.

[0198] AS RAI may be supported in NR (i.e., immediately moving the UE to RRC Inactive state). When the NG RAN determines that the UE has no additional uplink (UL) data to transmit and the RAN does not have any pending downlink (DL) data for the UE, the RAN may immediately release the UE to RRC_Inactive or RRC Idle with a suspension indication (when AS security is activated) or RRC Idle without suspension (e.g., when AS security is not activated or when the UE is optimized using CPIoT 5GS) upon receiving the AS RAI.

[0199] In another option, the RAN waits for a certain duration (or uses a new release timer) or asks the 5GCN (context release request or N2 RAI) to send an indication of whether there is DL data. Once the RAN confirms that there is no additional DL data for the UE, the RAN may send a RRCConectionRelease message and move the UE to RRC Inactive or RRC Idle (with or without a suspension indication).

[0200] In addition, if the RAN determines that there is only one pending DL data or the 5GCN indicates only one DL data, the data is sent together with the RRC connection release message (the DL data in the DTCH is multiplexed with the RRC release message in the DCCH). If the DL data is CP data, it may be included in the RRC release message, which may be extended to include NAS PDU or a new RRC release message, or the RRC EarlyDataComplete (i.e., moving to the UE in RRC Idle without pausing) message may be used. This indicates that when the UE is not optimized with CP IoT 5GS and RAI is activated, the RRC EarlyDataComplete message may be sent instead of the RRC connection release message without a suspension indication or RRC inactivity configuration and CP DL data.

[0201] When the UE uses EDT, the AS RAI is already implicitly understood by the RAN from Msg3. If the upper layer (i.e. NAS) instructs the AS to trigger the AS RAI, the UE MAC generates a BSR MAC CE with BSR=0 and sends it in the MAC PDU. In addition, if the UE is moving to an RRC connection, the MAC PDU may contain an RRCConnectionSetupComplete message or an RRCConnectionResumeComplete message or an ULInformationTransfer message including a NAS PDU (i.e. DedicatedInfoNAS). However, if the RAN does not activate the AS RAI in Msg4, it cannot be used.

[0202] New AS RAI indication via RRC message

[0203] For both eMTC and NB-IoT, a new AS RAI (different from the existing AS RAI) can be considered as a new indication to inform the RAN that the UE does not expect any additional UL data as well as DL data (e.g., it does not want to receive any DL data). This AS RAI can be triggered upon the indication of the RAI received from the upper layers. Upon receiving this new AS RAI, the UE can release early without waiting for a response from the 5GCN.

[0204] When EDT is used and the upper layers (e.g., NAS) instruct the AS (or RRC) to trigger the AS RAI, the RRCConnectionResumeRequest or RRCConnectionResumeRequest for the EDT message may be extended to include the AS RAI indication as shown below (for both eMTC and NB-IoT). The RAN does not need to be activated to use the AS RAI.

[0205] When EDT is used for CP CIoT EPS optimization, the RRC EarlyDataRequest message may be extended critically or non-critically or a new UL CCCH message class may be used to include a new AS RAI.

[0206] Example of new UL CCCH message class extension.

[0207]

[0208] Example of a non-critical extension.

[0209]

[0210] When EDT is used in UP CIoT 5GS optimization or RRC inactivity, the spare bit can be used for AS RAI indication, or the spare bit can be used to define a new resumption cause in the RRC Connection Resume Request message (e.g., "mo-Data-AS-Rai" for one UL data together with ASRAI) as an indication of AS RAI. In addition, a new ULCCCH message class extension of RRCConnectionResumeRequest can be used to include a new AS RAI.

[0211] Example of extension of RRCConnectionResumeRequest for NB-IoT

[0212]

[0213] Extended example of establishment cause in RRCConnectionResumeRequest for NB-IoT

[0214]

[0215] Extended example of the establishment cause in RRCConnectionResumeRequest for eMTC. Here, the spare bit (resumeFromSuspend) is used to indicate that the I-RNTI corresponds to a resume ID belonging to 5GCN, and the spare bit in the resume cause is used to indicate the AS RAI. resumeFromSuspend is not required when the UE is in RRC_Inactive.

[0216]

[0217]

[0218] Example of a new UL CCCH message class extension (similar spare bits in RRCConnectionResumeRequest-r13-IE may be used).

[0219]

[0220] When EDT is not used and the upper layer (e.g. NAS) instructs the AS (or RRC) to trigger the AS RAI, the RRCConnectionSetupComplete message or the RRCConnectionResumeComplete message or the ULInformationTransfer message can be extended to include the AS RAI indication as shown below (for both eMTC and NB-IoT). The RAN does not need to be activated to use the AS RAI.

[0221]

[0222]

[0223]

[0224]

[0225]

[0226] New AS RAI indication via L2 signaling

[0227] In another option, the new AS RAI also uses the BSR MAC CE with BSR=0, but it is distinguished from the existing AS RAI using the reserved bit in the MAC CE subheader. In another option, the new LCID of the UL-SCH (e.g., Figure 1 As shown) can be used to indicate a new AS RAI. Figure 1 An example of a MAC Control Element (CE) 100 including a sub-header Logical Channel ID (LCID) according to some embodiments is depicted. A new LCID code point may be used to use a short BSR with BSR = 0. Additionally, a fixed size zero-bit MAC CE (only sub-header present) may be used for this purpose.

[0228] A new code point of a fixed size extended LCID (eLCID) with a zero MAC CE may also be used, such as Figure 2 shown. Figure 2 An example of a MAC control element (CE) 200 including an extended sub-header logical channel ID (e-LCID) is depicted in accordance with some embodiments.

[0229] Table 1: Values ​​of eLCID for UL-SCH

[0230] Code Point index eLCID value 000000-000110 32-38 Logical channel identification 000111-1111110 39-954 Reserve 111111 95 AS RAI

[0231] System and implementation

[0232] Figure 3 An exemplary architecture of a system 300 of a network according to various embodiments is shown. The following description is provided for an example system 300 operating in conjunction with 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.

[0233] like Figure 3 As shown, system 300 includes UE 301a and UE 301b (collectively referred to as "UE 301" or "UE301"). In this example, multiple UEs 301 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0234] In some embodiments, any of the UEs 301 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via 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.

[0235] UE 301 may be configured to connect, e.g., be communicatively coupled, to RAN 310. In an embodiment, RAN 310 may be an NG RAN or 5G RAN, 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 310 operating in an NR or 5G system 300, while the term "E-UTRAN" or the like may refer to RAN 310 operating in an LTE or 4G system 300. UE 301 utilizes connections (or channels) 303 and 304, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0236] In this example, connections 303 and 304 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 301 may directly exchange communication data via a ProSe interface 305. ProSe interface 305 may alternatively be referred to as a SL interface 305, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0237] UE 301b is shown as being configured to access AP 306 (also referred to as "WLAN node 306", "WLAN 306", "WLAN terminal 306", "WT 306", etc.) via connection 307. Connection 307 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 306 will include Wireless Fidelity. Router. In this example, the AP 306 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 301b, the RAN 310, and the AP 306 can be configured to utilize LWA operation and / or LWIP operation. The LWA operation can involve the UE 301b in the RRC_CONNECTED state being configured by the RAN nodes 311a-b to utilize the radio resources of LTE and WLAN. The LWIP operation can involve the UE 301b using the WLAN radio resources (e.g., connection 307) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through the connection 307. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0238] The RAN 310 may include one or more AN nodes or RAN nodes 311a and 311b (collectively referred to as "RAN node 311" or "RAN node 311") that enable connections 303 and 304. As used herein, the terms "access node", "access point", 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 311 (e.g., a gNB) operating in an NR or 5G system 300, while the terms "E-UTRAN node" and the like may refer to a RAN node 311 (e.g., an eNB) operating in an LTE or 4G system 300. According to various embodiments, the RAN node 311 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0239] In some embodiments, all or part of the multiple RAN nodes 311 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 311; MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 311; or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, while the lower portions of the PHY layers are operated by individual RAN nodes 311. This virtualization framework allows idle processor cores of the RAN nodes 311 to execute other virtualized applications. In some specific implementations, separate RAN nodes 311 may be represented via separate F1 interfaces ( Figure 3 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 6 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 310 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 311 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 301 and is connected to the 5GC (e.g., Figure 5 CN 520) RAN node.

[0240] In a V2X scenario, one or more of the RAN nodes 311 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 301 (vUE 301). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing 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.

[0241] Any of the RAN nodes 311 may terminate the air interface protocol and may be the first point of contact for the UE 301. In some embodiments, any of the RAN nodes 311 may fulfill various logical functions of the RAN 310, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0242] In an embodiment, multiple UEs 301 may be configured to communicate with each other or with any of multiple RAN nodes 311 on a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0243] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 311 to the UE 301, 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.

[0244] According to various embodiments, UEs 301, 302 and RAN nodes 311, 312 communicate (e.g., transmit and receive) data via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz band.

[0245] To operate in the unlicensed spectrum, the UE 301, 302 and the RAN nodes 311, 312 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 301, 302 and the RAN nodes 311, 312 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.

[0246] LBT is a mechanism for equipment (e.g., UE 301, 302, RAN nodes 311, 312, 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.

[0247] 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 301 or 302, AP 306, 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 CSMA / CA for 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 for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

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

[0249] 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 301, 302 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.

[0250] The PDSCH carries user data and higher layer signaling to the UE 301. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It can also inform the UE 301 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 301b within a cell) can be performed on any of the multiple RAN nodes 311 based on channel quality information fed back from any of the multiple UEs 301. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 301.

[0251] 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).

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

[0253] RAN nodes 311 may be configured to communicate with each other via interface 312. In embodiments where system 300 is an LTE system (eg, when CN 320 is a Figure 4 420 in the EPC 420), the interface 312 may be an X2 interface 312. The X2 interface may be defined between two or more RAN nodes 311 (e.g., two or more eNBs, etc.) connected to the EPC 320, and / or between two eNBs connected to the EPC 320. In some 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 301 for user data; information about PDCP PDUs that were not delivered to the UE 301; 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.

[0254] When system 300 is a 5G or NR system (e.g., when CN 320 is Figure 5In an implementation scheme of the 5GC 520 in the 5GC 320, the interface 312 may be an Xn interface 312. The Xn interface is defined between two or more RAN nodes 311 (e.g., two or more gNBs, etc.) connected to the 5GC 320, between a RAN node 311 (e.g., a gNB) and an eNB connected to the 5GC 320, and / or between two eNBs connected to the 5GC 320. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 301 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 311. The mobility support may include context transfer from the old (source) serving RAN node 311 to the new (target) serving RAN node 311; and control of the user plane tunnel between the old (source) serving RAN node 311 and the new (target) serving RAN node 311. The 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.

[0255] RAN 310 is shown as being communicatively coupled to a core network—in this embodiment, a core network (CN) 320. CN 320 may include a plurality of network elements 322 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 301) connected to CN 320 via RAN 310. The components of CN 320 may be implemented in one physical node or in separate physical nodes, including components for reading and executing instructions from a machine-readable medium or a 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 320 may be referred to as a network slice, and a logical instance of a portion of CN 320 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0256] Generally speaking, the application server 330 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 330 may also be configured to support one or more communication services for the UE 301 via the EPC 320 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0257] In an embodiment, CN 320 may be a 5GC (referred to as "5GC 320" or the like), and RAN 310 may be connected to CN 320 via an NG interface 313. In an embodiment, NG interface 313 may be divided into two parts: an NG user plane (NG-U) interface 314, which carries traffic data between RAN node 311 and UPF; and an S1 control plane (NG-C) interface 315, which is a signaling interface between RAN node 311 and AMF. Figure 5 An implementation of CN 320 as 5GC 320 is discussed in more detail.

[0258] In an embodiment, CN 320 may be a 5G CN (referred to as "5GC 320", etc.), while in other embodiments, CN 320 may be an EPC. In the case where CN 320 is an EPC (referred to as "EPC 320", etc.), RAN 310 may be connected to CN 320 via an S1 interface 313. In an embodiment, S1 interface 313 may be divided into two parts: an S1 user plane (S1-U) interface 314, which carries traffic data between RAN node 311 and S-GW; and an S1-MME interface 315, which is a signaling interface between RAN node 311 and MME. Figure 4 An exemplary architecture is shown in which CN 320 is an EPC 320 .

[0259] Figure 4 FIG. 4 shows an exemplary architecture of a system 400 including a first CN 420 according to various embodiments. In this example, the system 400 may implement the LTE standard, wherein the CN 420 is a Figure 3 In addition, UE 401 can communicate with Figure 3 The UE 301 is the same as or similar to the UE 301, and the E-UTRAN 410 may be Figure 3 The CN 420 may be a RAN that is the same as or similar to the RAN 310 of the mobile network, and may include the RAN node 311 discussed previously. The CN 420 may include an MME 421, an S-GW 422, a P-GW 423, an HSS 424, and an SGSN 425.

[0260] The MME 421 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 401. The MME 421 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 "EPS MM" or "EMM" in an E-UTRAN system) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge of the current location of the UE 401, providing user identity confidentiality to users / subscribers, and / or performing other similar services. Each UE 401 and the MME 421 may include an MM or EMM sublayer, and an MM context may be established in the UE 401 and the MME 421 when the attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE 401. The MME 421 may be coupled to the HSS 424 via an S6a reference point, to the SGSN 425 via an S3 reference point, and to the S-GW 422 via an S11 reference point.

[0261] SGSN 425 may be a node that serves UE 401 by tracking the location of individual UE 401 and performing security functions. In addition, SGSN 425 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 421; handling of UE 401 time zone capabilities as specified by MME 421; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 421 and SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

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

[0263] The S-GW 422 may terminate the S1 interface 313 towards the RAN 410 (at Figure 4 The S-GW 422 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 422 and the MME 421 may provide a control plane between the MME 421 and the S-GW 422. The S-GW 422 may be coupled to the P-GW 423 via the S5 reference point.

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

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

[0266] Figure 5The architecture of a system 500 including a second CN 520 according to various embodiments is shown. The system 500 is shown to include a UE 501, which may be the same or similar to the previously discussed UE 301 and UE 401; a (R) AN 510, which may be the same or similar to the previously discussed RAN 310 and RAN 410, and which may include the previously discussed RAN node 311; and a DN 503, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 520. The 5GC 520 may include an AUSF 522; an AMF 521; an SMF 524; an NEF 523; a PCF 526; an NRF 525; an UDM 527; an AF 528; an UPF 502; and an NSSF 529.

[0267] UPF 502 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 503, and a branch point to support multi-host PDU sessions. UPF 502 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 502 may include an uplink classifier to support routing traffic flows to data networks. DN 503 may represent various network operator services, Internet access, or third-party services. DN 503 may include or be similar to the application server 330 discussed previously. UPF 502 may interact with SMF 524 via the N4 reference point between SMF 524 and UPF 502.

[0268] The AUSF 522 may store data for authentication of the UE 501 and handle authentication-related functions. The AUSF 522 may facilitate a common authentication framework for various access types. The AUSF 522 may communicate with the AMF 521 via the N12 reference point between the AMF 521 and the AUSF 522; and may communicate with the UDM 527 via the N13 reference point between the UDM 527 and the AUSF 522. In addition, the AUSF 522 may present an interface based on the Nausf service.

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

[0270] The AMF 521 may also support NAS signaling with the UE 501 over the N3 IWF interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R) AN 510 and the AMF 521 for the control plane, and may be the termination point for the N3 reference point between the (R) AN 510 and the UPF 502 for the user plane. Thus, the AMF 521 may process N2 signaling for PDU sessions and QoS from the SMF 524 and the AMF 521, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 501 and the AMF 521 via the N1 reference point between the UE 501 and the AMF 521, and relay uplink and downlink user plane packets between the UE 501 and the UPF 502. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 501. The AMF 521 may present an interface based on the Namf service, and may be an N14 reference point between two AMFs 521 and an N14 reference point between the AMF 521 and the 5G-EIR ( Figure 5 The termination point of the N17 reference point between the two (not shown).

[0271] UE 501 may need to register with AMF 521 in order to receive network services. RM is used to register or deregister UE 501 with the network (e.g., AMF 521) and establish a UE context in the network (e.g., AMF 521). UE 501 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 501 is not registered with the network, and the UE context in AMF 521 does not maintain the valid location or routing information of UE 501, so AMF 521 cannot reach UE 501. In the RM-REGISTERED state, UE 501 is registered with the network, and the UE context in AMF 521 may maintain the valid location or routing information of UE 501, so AMF 521 can reach UE 501. In the RM-REGISTERED state, UE 501 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (for example, to notify the network that UE 501 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

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

[0273] The CM may be used to establish and release a signaling connection between the UE 501 and the AMF 521 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 501 and the CN 520, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 501 between the AN (e.g., the RAN 510) and the AMF 521. The UE 501 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 501 operates in the CM-IDLE state / mode, the UE 501 may not have a NAS signaling connection established with the AMF 521 over the N1 interface, and there may be a (R) AN 510 signaling connection (e.g., N2 and / or N3 connection) for the UE 501. When the UE 501 operates in the CM-CONNECTED state / mode, the UE 501 may have a NAS signaling connection established with the AMF 521 through the N1 interface, and there may be a (R)AN 510 signaling connection (e.g., N2 and / or N3 connection) for the UE 501. Establishing an N2 connection between the (R)AN 510 and the AMF 521 may cause the UE 501 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 510 and the AMF 521 is released, the UE 501 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0274] SMF 524 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 501 and a data network (DN) 503 identified by a data network name (DNN). Using NAS SM signaling exchanged over the N1 reference point between UE 501 and SMF 524, a PDU session may be established upon request by UE 501, modified upon request by UE 501 and 5GC 520, and released upon request by UE 501 and 5GC 520. Upon request from an application server, 5GC 520 may trigger a specific application in UE 501. In response to receiving a trigger message, UE 501 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 501. The identified applications in UE 501 may establish a PDU session to a specific DNN. SMF 524 may check whether the UE 501 request complies with user subscription information associated with UE 501. In this regard, SMF 524 may retrieve and / or request to receive update notifications about SMF 524 level subscription data from UDM 527.

[0275] SMF 524 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 roaming scenarios, an N16 reference point between two SMFs 524 may be included in the system 500, which may be located between an SMF 524 in a visited network and another SMF 524 in a home network. In addition, SMF 524 may present an interface based on Nsmf services.

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

[0277] NRF 525 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 525 also maintains information about available NF instances and services supported by these instances. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 525 may present an interface based on Nnrf services.

[0278] The PCF 526 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. The PCF 526 may also implement a FE to access subscription information related to policy decisions in the UDR of the UDM 527. The PCF 526 may communicate with the AMF 521 via the N15 reference point between the PCF 526 and the AMF 521, which may include the PCF 526 in the visited network and the AMF 521 in the case of a roaming scenario. The PCF 526 may communicate with the AF 528 via the N5 reference point between the PCF 526 and the AF528; and communicate with the SMF 524 via the N7 reference point between the PCF 526 and the SMF 524. The system 500 and / or the CN 520 may also include an N24 reference point between the PCF 526 (in the home network) and the PCF 526 in the visited network. In addition, the PCF 526 may present an interface based on Npcf services.

[0279] UDM 527 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 501. For example, subscription data may be transmitted between UDM 527 and AMF via an N8 reference point between UDM 527 and AMF 521. UDM 527 may include two parts: application FE and UDR ( Figure 5 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 527 and PCF 526, and / or structured data for exposure and application data of NEF 523 (including PFD for application detection, application request information of multiple UE 501). Nudr service-based interface can be presented by UDR 221 to allow UDM 527, PCF 526 and NEF 523 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 524 via the N10 reference point between UDM 527 and SMF 524. UDM 527 may also support SMS management, where SMS-FE implements similar application logic discussed previously. In addition, UDM 527 may present an interface based on Nudm services.

[0280] AF 528 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 520 and AF 528 to provide information to each other via NEF 523, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 501 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 502 near UE 501 and perform traffic steering from UPF 502 to DN 503 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 528. In this way, AF 528 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 528 is considered a trusted entity, the network operator can allow AF 528 to interact directly with the relevant NF. In addition, AF 528 can present an interface based on Naf services.

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

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

[0283] CN 120 may also include Figure 5 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF can communicate with UDSF ( Figure 5 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data 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 5 (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.

[0284] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 5These interfaces and reference points are omitted. In one example, CN 520 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 421) and AMF 521 to enable interworking between CN 520 and CN 420. 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.

[0285] Figure 6 An example of infrastructure equipment 600 according to various embodiments is shown. Infrastructure equipment 600 (or "system 600") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 311 and / or AP 306 shown and described previously), an application server 330, and / or any other element / device discussed herein. In other examples, system 600 can be implemented in or by a UE.

[0286] System 600 includes application circuit 605, baseband circuit 610, one or more radio front end modules (RFEM) 615, memory circuit 620, power management integrated circuit (PMIC) 625, power tee circuit 630, network controller circuit 635, network interface connector 640, satellite positioning circuit 645 and user interface 650. In some embodiments, device 600 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.

[0287] The application circuit 605 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 605 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage device to enable various applications or operating systems to run on system 600. In some embodiments, the memory / storage element can be an 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.

[0288] The processor of the application circuit 605 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 605 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; 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 MIPSWarrior P-class processor; etc. In some embodiments, the system 600 may not utilize the application circuit 605, and instead may include a dedicated processor / controller to process IP data received, for example, from the EPC or 5GC.

[0289] In some implementations, the application circuit 605 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. 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), 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 implementations, the circuits of the application circuit 605 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, etc. of the various embodiments discussed herein. In such an embodiment, the circuitry of the application circuit 605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), etc.

[0290] Baseband circuit 610 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 8 The various hardware electronic components of baseband circuit 610 are discussed.

[0291] The user interface circuit 650 may include one or more user interfaces designed to enable a user to interact with the system 600 or a peripheral component interface designed to enable a peripheral component to interact with the system 600. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a 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.

[0292] The radio front end module (RFEM) 615 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 8Antenna array 811), and 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 RFEM615 that combines both millimeter wave antennas and sub-millimeter waves.

[0293] The memory circuit 620 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 620 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0294] The PMIC 625 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as 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 630 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 600 using a single cable.

[0295] The network controller circuit 635 may provide connectivity 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 600 via a network interface connector 640, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 635 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0296] The positioning circuit 645 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., 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 645 includes 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 645 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 645 may also be part of or interact with the baseband circuit 610 and / or RFEM 615 to communicate with nodes and components of the positioning network. The positioning circuit 645 may also provide location data and / or time data to the application circuit 605, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 311, etc.), etc.

[0297] Figure 6 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0298] Figure 7 An example of a platform 700 (or "device 700") according to various embodiments is shown. In an embodiment, the computer platform 700 may be suitable for use as a UE 301, 302, 401, an application server 330, and / or any other element / device discussed herein. The platform 700 may include any combination of components shown in the example. The components of the platform 700 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof suitable for use in the computer platform 700, or implemented as components otherwise incorporated within a chassis of a larger system. Figure 7The block diagram is intended to show a high-level view of the components of computer platform 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0299] The application circuit 705 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The processor (or core) of the application circuit 705 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 700. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0300] The processor of the application circuit 605 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, 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 605 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0301] As an example, the processor of the application circuit 705 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 705 can be part of a system on a chip (SoC), in which the application circuit 705 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0302] Additionally or alternatively, the application circuit 705 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 705 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 705 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in lookup tables (LUTs), etc.

[0303] Baseband circuit 710 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 8 The various hardware electronic components of baseband circuit 710 are discussed.

[0304] The RFEM 715 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 8 Antenna array 811), 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 715 that combines both millimeter wave antennas and sub-millimeter waves.

[0305] The memory circuit 720 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 720 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 720 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 720 may be implemented as one or more of the following: 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 720 may be an on-chip memory or register associated with the application circuit 705. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 720 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 700 may be combined with and Three-dimensional (3D) cross-point (XPOINT) memory.

[0306] Removable memory circuitry 723 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 700. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0307] The platform 700 may further include an interface circuit (not shown) for connecting external devices to the platform 700. External devices connected to the platform 700 via the interface circuit include a sensor circuit 721 and an electromechanical component (EMC) 722, and a removable memory device coupled to a removable memory circuit 723.

[0308] Sensor circuitry 721 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.

[0309] EMC 722 includes devices, modules or subsystems that are intended to enable platform 700 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 722 can be configured to generate messages / signaling and send messages / signaling to other components of platform 700 to indicate the current state of EMC 722. Examples of EMC 722 include one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), 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, platform 700 is configured to operate one or more EMC 722 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0310] In some specific implementations, the interface circuit may connect the platform 700 to the positioning circuit 745. The positioning circuit 745 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 745 may include 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 745 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 745 may also be part of the baseband circuit 610 and / or the RFEM 715 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 745 may also provide position data and / or time data to application circuitry 705, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0311] In some implementations, the interface circuit may connect the platform 700 with a near field communication (NFC) circuit 740. The NFC circuit 740 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where a magnetic field is sensed to enable communication between the NFC circuit 740 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 700. The NFC circuit 740 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 740 by executing an 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 740, or initiate data transfer between the NFC circuit 740 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) close to the platform 700.

[0312] The driver circuit 746 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 700. The driver circuit 746 may include various drivers to allow other components of the platform 700 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 700. For example, the driver circuit 746 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 700, a sensor driver for obtaining sensor readings of the sensor circuit 721 and controlling and allowing access to the sensor circuit 721, an EMC driver for obtaining an actuator position of the EMC 722 and / or controlling and allowing access to the EMC 722, 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.

[0313] A power management integrated circuit (PMIC) 725 (also referred to as “power management circuit 725”) may manage power provided to various components of the platform 700. Specifically, the PMIC 725 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 710. When the platform 700 is capable of being powered by a battery 730, for example, when the device is included in a UE 301, 302, 401, the PMIC 725 may be generally included.

[0314] In some embodiments, the PMIC 725 may control or otherwise be part of various power saving mechanisms of the platform 700. For example, if the platform 700 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the platform 700 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 700 may transition to the RRC_Idle state, where the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 700 enters a very low power state and performs paging, where the device wakes up periodically again to listen to the network and then powers off again. The platform 700 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.

[0315] The battery 730 can power the platform 700, but in some examples, the platform 700 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 730 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 730 can be a typical lead-acid car battery.

[0316] In some implementations, the battery 730 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 700 to track the state of charge (SoCh) of the battery 730. The BMS may be used to monitor other parameters of the battery 730, such as the state of health (SoH) and state of function (SoF) of the battery 730 to provide fault prediction. The BMS may transmit information about the battery 730 to the application circuit 705 or other components of the platform 700. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 705 to directly monitor the voltage of the battery 730 or the current from the battery 730. The battery parameters may be used to determine actions that the platform 700 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0317] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 730. In some examples, the power block XS30 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 700. 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 730 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.

[0318] The user interface circuit 750 includes various input / output (I / O) devices present in or connected to the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and / or a peripheral component interface designed to enable peripheral components to interact with the platform 700. The user interface circuit 750 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary 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 700. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 721 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.

[0319] Although not shown, the components of platform 700 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0320] Figure 8 8 shows exemplary components of a baseband circuit 810 and a radio front end module (RFEM) 815 according to various embodiments. The baseband circuit 810 corresponds to Figure 6 The baseband circuit 610 and Figure 7 Baseband circuit 710. RFEM 815 corresponds to Figure 6 RFEM 615 and Figure 7 RFEM 715. As shown, the RFEM 815 may include a radio frequency (RF) circuit 806, a front end module (FEM) circuit 808, and an antenna array 811 coupled together at least as shown.

[0321] The baseband circuit 810 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 806. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 810 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 810 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 810 is configured to process baseband signals received from the receive signal path of the RF circuit 806 and generate baseband signals for the transmit signal path of the RF circuit 806. The baseband circuit 810 is configured to communicate with the application circuit 605 / 705 (see Figure 6 and Figure 7 ) to generate and process baseband signals and control the operation of RF circuit 806. Baseband circuit 810 may handle various radio control functions.

[0322] The aforementioned circuits and / or control logic components of the baseband circuit 810 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 804A, a 4G / LTE baseband processor 804B, a 5G / NR baseband processor 804C, or some other baseband processors 804D 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 804A-D may be included in a module stored in the memory 804G and executed via a central processing unit (CPU) 804E. In other embodiments, some or all of the functions of the baseband processors 804A-D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 804G may store program code of a real-time OS (RTOS), which, when executed by the CPU 804E (or other baseband processor), will enable the CPU 804E (or other baseband processor) to manage resources of the baseband circuit 810, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 810 includes one or more audio digital signal processors (DSPs) 804F. The audio DSP 804F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0323] In some embodiments, each of processors 804A-804E includes a corresponding memory interface to send data to / receive data from memory 804G. Baseband circuit 810 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 810; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 6 to 8An application circuit interface for sending data to / receiving data from the application circuit 605 / 705; Figure 8 RF circuit 806 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 725.

[0324] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 810 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 interconnection subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 810 may include a protocol processing circuit 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 815).

[0325] although Figure 8Not shown, but in some embodiments, the baseband circuit 810 includes various processing devices (e.g., a "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 810 and / or the RF circuit 806 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 the first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 810 and / or the RF circuit 806 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In the 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., 804G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 810 may also support radio communications of more than one wireless protocol.

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

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

[0328] The RF circuit 806 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 806 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 806 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 808 and providing baseband signals to the baseband circuit 810. The RF circuit 806 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 810 and providing an RF output signal for transmission to the FEM circuit 808.

[0329] In some embodiments, the receive signal path of the RF circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. In some embodiments, the transmit signal path of the RF circuit 806 may include a filter circuit 806c and a mixer circuit 806a. The RF circuit 806 may also include a synthesizer circuit 806d for synthesizing the frequencies used by the mixer circuit 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b may be configured to amplify the down-converted signal, and the filter circuit 806c 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 the baseband circuit 810 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 806a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

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

[0331] In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.

[0332] 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, the RF circuit 806 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 810 may include a digital baseband interface to communicate with the RF circuit 806.

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

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

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

[0336] 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 810 or the application circuit 605 / 705 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 605 / 705.

[0337] The synthesizer circuit 806d of the RF circuit 806 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0338] In some embodiments, the synthesizer circuit 806d 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 used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 806 can include an IQ / polarity converter.

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

[0340] In some embodiments, the FEM circuit 808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 808 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 806). The transmit signal path of the FEM circuit 808 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 806), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 811.

[0341] The antenna array 811 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 810 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 811 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 811 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 811 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 806 and / or the FEM circuit 808 using a metal transmission line or the like.

[0342] The processor of the application circuit 605 / 705 and the processor of the baseband circuit 810 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 810 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 605 / 705 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.

[0343] Fig. 9 Various protocol functions that may be implemented in a wireless communication device according to some embodiments are shown. Specifically, Fig. 9 An arrangement 900 is included to show 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. 9The following description, but Fig. 9 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0344] The protocol layers of arrangement 900 may include one or more of PHY 910, MAC 920, RLC 930, PDCP 940, SDAP 947, RRC 955, and NAS layer 957, in addition to other higher layer functions not shown. These protocol layers may include one or more service access points (e.g., Fig. 9 Items 959, 956, 950, 949, 945, 935, 925 and 915), the one or more service access points can provide communication between two or more protocol layers.

[0345] PHY 910 can send and receive physical layer signals 905, which can be received or sent from one or more other communication devices to one or more other communication devices. Physical layer signals 905 can include one or more physical channels, such as those discussed herein. PHY 910 can 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., RRC 955). PHY 910 can 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 910 can process a request from an instance of MAC 920 via one or more PHY-SAP 915 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 915 can include one or more transmission channels.

[0346] An instance of MAC 920 may process requests from an instance of RLC 930 and provide indications thereto via one or more MAC-SAPs 925. These requests and indications transmitted via MAC-SAPs 925 may include one or more logical channels. MAC 920 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 910 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 910 via transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0347] An instance of RLC 930 may process requests from an instance of PDCP 940 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 935. These requests and indications transmitted via RLC-SAPs 935 may include one or more RLC channels. RLC 930 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 930 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 930 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

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

[0349] An instance of SDAP 947 may process requests from one or more higher layer protocol entities and provide instructions thereto via one or more SDAP-SAPs 949. These requests and instructions transmitted via SDAP-SAPs 949 may include one or more QoS flows. SDAP 947 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 947 may be configured for a separate PDU session. In the UL direction, NG-RAN 310 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 947 of UE 301 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 947 of UE 301 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 510 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 955 configuring the SDAP 947 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 947. In an embodiment, the SDAP 947 may be used only in NR implementations and may not be used in LTE implementations.

[0350] The RRC 955 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 910, MAC 920, RLC 930, PDCP 940, and SDAP 947, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 955 may process requests from one or more NAS entities 957 and provide instructions thereto via one or more RRC-SAPs 956. The main services and functions of the RRC 955 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 301 and the RAN 310 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

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

[0352] According to various embodiments, one or more protocol entities of the arrangement 900 may be implemented in the UE 301, the RAN node 311, the AMF 521 in the NR implementation or the MME 421 in the LTE implementation, the UPF 502 in the NR implementation or the S-GW 422 and the P-GW 423 in the 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 the UE 301, the gNB 311, the AMF 521, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using the services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 311 may host the RRC 955, SDAP 947, and PDCP 940 of the gNB that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 311 may each host the RLC 930, MAC 920, and PHY 910 of gNB 311.

[0353] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 957, RRC 955, PDCP 940, RLC 930, MAC 920, and PHY 910. In this example, an upper layer 960 may be built on top of NAS 957, which includes an IP layer 961, SCTP 962, and an application layer signaling protocol (AP) 963.

[0354] In a NR specific implementation, AP 963 can be an NG application protocol layer (NGAP or NG-AP) 963 for the NG interface 313 defined between the NG-RAN node 311 and the AMF 521, or AP 963 can be an Xn application protocol layer (XnAP or Xn-AP) 963 for the Xn interface 312 defined between two or more RAN nodes 311.

[0355] The NG-AP 963 may support the functionality of the NG interface 313 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 311 and the AMF 521. The NG-AP 963 services may include two groups: UE-associated services (e.g., services related to UE 301, 302) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 311 and the AMF 521). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 311 involved in a specific paging area; a UE context management function for allowing the AMF 521 to establish, modify and / or release the UE context in the AMF 521 and the NG-RAN node 311; a mobility function for the UE 301 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; an NG interface management function for setting up the NG interface and monitoring errors 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 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; a ... via the CN 320 is a configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 311; and / or other similar functions.

[0356] The XnAP 963 may support the functionality of the Xn interface 312 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 311 (or E-UTRAN 410), such as handover preparation and cancellation procedures, SN 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 301, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0357] In an LTE specific implementation, the AP 963 may be an S1 application protocol layer (S1-AP) 963 for the S1 interface 313 defined between the E-UTRAN node 311 and the MME, or the AP 963 may be an X2 application protocol layer (X2AP or X2-AP) 963 for the X2 interface 312 defined between two or more E-UTRAN nodes 311.

[0358] The S1 application protocol layer (S1-AP) 963 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between the E-UTRAN node 311 and the MME 421 within the LTE CN 320. The S1-AP 963 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.

[0359] The X2AP 963 may support the functions of the X2 interface 312 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 320, 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 301, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

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

[0361] In a second example, the user plane protocol stack may include SDAP 947, PDCP 940, RLC 930, MAC 920, and PHY 910 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 301, RAN node 311, and UPF 502 in a NR implementation, or communication between S-GW 422 and P-GW 423 in a LTE implementation. In this example, an upper layer 951 may be built on top of SDAP 947 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 952, a general packet radio service (GPRS) tunneling protocol layer (GTP-U) 953 for a user plane, and a user plane PDU layer (UP-PDU) 963.

[0362] The transport network layer 954 (also referred to as the "transport layer") may be built on top of the IP transport, and the GTP-U 953 may be used on top of the UDP / IP layer 952 (including the UDP layer and the IP layer) to carry the user plane PDU (UP-PDU). 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.

[0363] GTP-U 953 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be a packet in any of the IPv4, IPv6 or PPP formats. UDP / IP 952 can provide a checksum for data integrity, a port number for addressing different functions at the source and destination, and encryption and authentication of the selected data stream. The RAN node 311 and the S-GW 422 can exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 910), an L2 layer (e.g., MAC 920, RLC 930, PDCP 940 and / or SDAP 947), a UDP / IP layer 952, and a GTP-U 953 using an S1-U interface. The S-GW 422 and the P-GW 423 can exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 952, and a GTP-U 953 using an S5 / S8a interface. As previously discussed, the NAS protocol may support mobility and session management procedures of the UE 301 to establish and maintain an IP connection between the UE 301 and the P-GW 423 .

[0364] In addition, despite Fig. 9Not shown, but an application layer may exist above the AP 963 and / or transport network layer 954. The application layer may be a layer where a user of the UE 301, RAN node 311, or other network element interacts with, for example, a software application executed by the application circuitry 605 or the application circuitry 705, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuitry 810) of the UE 301 or RAN node 311. In some implementations, the IP layer and / or the application layer may provide functionality that is the same or similar to 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).

[0365] Fig.10 Components of a core network according to various embodiments are shown. The components of CN 420 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 an embodiment, the components of CN 520 can be implemented in the same or similar manner as discussed herein with respect to the components of CN 420. In some embodiments, NFV is 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 420 may be referred to as a network slice 1001, and each logical instance of CN 420 may provide specific network functions and network characteristics. A logical instance of a portion of CN 420 may be referred to as a network sub-slice 1002 (e.g., network sub-slice 1002 is shown as including P-GW 423 and PCRF 426).

[0366] As used herein, the terms "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in different IP domains or in the case of overlapping IP addresses. A network slice instance may refer to a set of network function (NF) instances and the resources (e.g., computing, storage, and networking resources) required to deploy a network slice.

[0367] Compared to 5G systems (see e.g. Figure 5), a network slice always includes a RAN part and a CN part. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can implement different network slices by scheduling and also by providing different L1 / L2 configurations. If provided by NAS, the UE 501 provides auxiliary information for network slice selection in an appropriate RRC message. Although the network can support a large number of slices, the UE does not need to support more than 8 slices at the same time.

[0368] The network slice may include the CN 520 control plane and user plane NF, the NG RAN 510 in the serving PLMN, and the N3IWF function in the serving PLMN. Each network slice may have a different S-NSSAI and / or may have a different SST. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by the S-NSSAI. The network slice may differ in terms of supported features and network function optimizations, and / or multiple network slice instances may deliver the same service / feature, but differ for different groups of UE 501 (e.g., enterprise users). For example, each network slice may deliver different committed services and / or may be dedicated to a specific customer or enterprise. In this example, each network slice may have a different S-NSSAI with the same SST but with a different slice differentiator. In addition, a single UE may be served simultaneously by one or more network slice instances via a 5G AN and be associated with eight different S-NSSAIs. In addition, an AMF 521 instance serving a single UE 501 may belong to each network slice instance serving the UE.

[0369] Network slicing in NG-RAN 510 involves RAN slice awareness. RAN slice awareness includes differentiated processing for traffic of different network slices that have been pre-configured. Slice awareness in NG-RAN 510 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling including PDU session resource information. How NG-RAN 510 supports enabling slices in terms of NG-RAN functions (e.g., a set of network functions including each slice) depends on the specific implementation. NG-RAN 510 selects the RAN part of the network slice using auxiliary information provided by UE 501 or 5GC 520, which explicitly identifies one or more network slices in the pre-configured network slices in the PLMN. NG-RAN 510 also supports resource management and policy enforcement between slices according to SLA. A single NG-RAN node can support multiple slices, and NG-RAN510 can also appropriately apply appropriate RRM policies for SLA to each supported slice. NG-RAN 510 can also support QoS differentiation within a slice.

[0370] The NG-RAN 510 may also use the UE assistance information to select an AMF 521 during the initial attach, if available. The NG-RAN 510 routes the initial NAS to the AMF 521 using the assistance information. If the NG-RAN 510 cannot select an AMF 521 using the assistance information, or the UE 501 does not provide any such information, the NG-RAN 510 sends the NAS signaling to a default AMF 521, which may be in the AMF 521 pool. For subsequent access, the UE 501 provides a temporary ID assigned to the UE 501 by the 5GC 520 to enable the NG-RAN 510 to route the NAS message to the appropriate AMF 521, as long as the temporary ID is valid. The NG-RAN 510 knows and can reach the AMF 521 associated with the temporary ID. Otherwise, the method for initial attach applies.

[0371] The NG-RAN 510 supports resource isolation between slices. NG-RAN 510 resource isolation can be achieved with the help of RRM policies and protection mechanisms that should avoid starvation of shared resources if one slice breaks the service level agreement for another slice. In some implementations, NG-RAN 510 resources can be fully assigned to a slice. How the NG-RAN 510 supports resource isolation depends on the specific implementation.

[0372] Some slices may be only partially available in the network. The NG-RAN 510 is aware of slices supported in its neighboring cells that may be beneficial for inter-frequency mobility in connected mode. Slice availability may not change within the registration area of ​​the UE. The NG-RAN 510 and 5GC 520 are responsible for handling service requests for slices that may or may not be available in a given area. Granting or denying access to a slice may depend on factors such as support for the slice, availability of resources, and support of the requested service by the NG-RAN 510.

[0373] The UE 501 may be associated with multiple network slices simultaneously. In the case where the UE 501 is associated with multiple slices simultaneously, only one signaling connection is maintained and for intra-frequency cell reselection, the UE 501 attempts to camp on the best cell. For inter-frequency cell reselection, dedicated priorities may be used to control the frequency that the UE 501 camps on. The 5GC 520 will verify that the UE 501 has the right to access the network slice. Knowing the specific slice that the UE 501 is requesting access to may allow the NG-RAN 510 to apply some temporary / local policies before receiving the Initial Context Setup Request message. During the Initial Context Setup, the NG-RAN 510 is informed of the slice whose resources are being requested.

[0374] NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources including a combination of industry standard server hardware, storage hardware or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0375] Fig.11 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.11 A schematic diagram of hardware resources 1100 is shown, including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1100.

[0376] Processor 1110 may include, for example, processor 1112 and processor 1114. Processor 1110 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.

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

[0378] The communication resources 1130 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1104 or one or more databases 1106 via the network 1108. For example, the communication resources 1130 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.

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

[0380] Example Process

[0381] In some embodiments, Figures 3 to 11 The electronic device, network, system, chip or component or part thereof or specific implementation in some other figures of this document may be configured to perform one or more processes, techniques or methods described herein or part thereof. Fig.12 One such process is depicted in . For example, Fig.12 A flowchart 1200 describing a UE (such as UE 301, 401, 501, 700) according to an embodiment of the present disclosure is shown for operating the UE when connected to a 5G core network (5GCN). In an embodiment, the flowchart 1200 may be performed by a processor or processor circuit (including Fig.11 The processor, and / or application circuit 605 or 705, and / or Figure 6 to Figure 7 The baseband circuit 605 or 710 shown is executed or controlled.

[0382] At 1202, an indication is received that a 5G core network (5GCN) is used for the cell. For example, the UE may receive or cause to be received an indication from a NAS (non-access layer) that a 5GC (5G core network) is used for the cell (or that a 5GC is available for use). At 1204, in response to the indication to use the 5GCN, a radio resource control (RRC) connection request is transmitted. For example, when E-UTRA connected to 5GC is supported, the UE sends or causes to be sent an RRC connection request.

[0383] According to some embodiments, sending the RRC connection request may include sending a device identity. The device identity may correspond to 5GCN when at least one of the following: a spare bit is set to "1"; a predefined extension of the RRC connection request message is used; or a UL CCCH message class extension for the RRC connection request message is used.

[0384] According to some embodiments, sending the RRC connection request may include sending or causing sending an RRC connection recovery request. In these examples, the device identity may correspond to: if UP IoT 5GS optimization is used, then the recovery ID; or if the device is in an RRC inactive state, then the I-RNTI.

[0385] According to some embodiments, when AS (access stratum) security has not been enabled, the RRC connection request may correspond to RRCConnectionReestablishmentRequest-NB for NB-IoT, and the device identity may correspond to the 40-bit NG-5GS-TMSI.

[0386] According to some embodiments, method 1200 may further include sending the remaining 6 bits of the device identity in the RRCConnectionReestablishmentComplete-NB message.

[0387] According to some embodiments, method 1200 may further include carrying or causing the device capabilities to be carried in the RRCConnectionSetupComplete message. In some examples, the device capabilities are forwarded by the RAN to the 5GCN.

[0388] According to some embodiments, the device capability may be one of: CE Mode B Support, attachWithoutPDN-Connectivity, up-CIoT-5GS-Optimisation or cp-CIoT-5GS-Optimisation,

[0389] According to some embodiments, method 1200 may further include indicating or causing an indication of whether the RRC Inactive state is supported. Additionally or alternatively, method 1200 may further include indicating in the RRCConnectionSetupComplete message whether immediate use of RRC Inactive is preferred.

[0390] According to some examples, method 1200 may further include sending or causing sending a RAN broadcast notifying whether connectivity to 5GCN is supported. In addition, method 1200 may include sending or causing sending cell access information in SIB1-BR or SIB1-NB, and sending or causing sending whether CIoT 5GS optimization and EDT are supported in the BR version of SIB2 or SIB2-NB.

[0391] According to some embodiments, method 1200 may further include using or causing use of a new UL-CCCH message class extension for a new RRCEarlyDataRequest message. Additionally or alternatively, method 1200 may include using or causing use of a key extension of an existing RRCEarlyDataRequest to carry a full NG-5G-S-TMSI for both eMTC and NB-IoT devices when EDT is used in CP IoT 5GS optimization.

[0392] According to some embodiments, method 1200 may also include extending or causing the RRCEarlyDataComplete message to be extended to include a wait time having a smaller value and redirected carrier information for both eMTC and NB-IoT devices when EDT is used in CP IoT 5GS optimization.

[0393] According to some embodiments, method 1200 may include indicating or causing indication of a new AS RAI to indicate that both the additional UL data and the DL data are not extended using extension of the RRC message. Additionally or alternatively, method 1200 may include using or causing use of one of: a reserved bit in a MAC subheader of an existing Rel-13 AS RAI, a fixed size of a zero-bit MAC CE with a new LCID or eLCID code point, or a reserved bit in an existing AS RAI code point and subheader.

[0394] According to some embodiments, method 1200 may include not using or causing use of a new RNA or RNA update timer, or not using or causing use of a RAN-based paging DRX cycle length when the device is in an RRC inactive state.

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

[0396] Example

[0397] Embodiment 1 may include a device, the device comprising:

[0398] means for receiving an indication from a NAS that a cell uses 5GC; and

[0399] A component for sending an RRC Connection Request when E-UTRA connected to 5GC is supported.

[0400] Embodiment 2 may include an apparatus according to embodiment 1 and / or some other embodiments herein, wherein the device identity corresponds to 5GCN when at least one of the following occurs:

[0401] The spare bit is set to "1";

[0402] Using a predefined extension of the RRC Connection Request message; or

[0403] The UL CCCH message class extension for the RRC Connection Request message is used.

[0404] Embodiment 3 may include an apparatus according to embodiment 2 and / or some other embodiments herein, wherein the component for sending an RRC connection request further includes a component for sending an RRC connection recovery request, and wherein the device identity corresponds to: if UP IoT 5GS optimization is used, then the recovery ID, or if the device is in an RRC inactive state, then the I-RNTI.

[0405] Embodiment 4 may include an apparatus according to embodiment 2 and / or some other embodiments of the present invention, wherein when AS security has not been enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for NB-IoT, and the device identity corresponds to a 40-bit NG-5GS-TMSI.

[0406] Embodiment 5 may include an apparatus according to embodiment 4 and / or some other embodiments herein, further comprising means for sending the remaining 6 bits of the device identity in the RRCConnectionReestablishmentComplete-NB message.

[0407] Embodiment 6 may include the apparatus according to embodiment 1 and / or some other embodiments herein, further comprising:

[0408] Component used to carry device capabilities in the RRCConnectionSetupComplete message, where the device capabilities are forwarded by the RAN to the 5GCN.

[0409] Embodiment 7 may include an apparatus according to embodiment 6 and / or some other embodiments herein, wherein the device capability is one of: CE Mode B Support, attachWithoutPDN-Connectivity, up-CIoT-5GS-Optimisation or cp-CIoT-5GS-Optimisation,

[0410] Embodiment 8 may include the apparatus according to embodiment 1 and / or some other embodiments herein, further comprising:

[0411] A component used to indicate whether the RRC Inactive state is supported in the RRCConnectionSetupComplete message or whether to immediately prefer to use RRC Inactive.

[0412] Embodiment 9 may include a device comprising:

[0413] A means for sending a RAN broadcast notifying whether connectivity to 5GCN is supported;

[0414] A means for sending cell access information in SIB1-BR or SIB1-NB; and

[0415] A component used to signal whether CIoT 5GS optimization and EDT are supported in the BR version of SIB2 or SIB2-NB.

[0416] Embodiment 10 may include a device comprising:

[0417] means for using a new UL-CCCH message class extension for a new RRC EarlyDataRequest message; or

[0418] Components for using key extensions of the existing RRC EarlyDataRequest to carry the full NG-5G-S-TMSI for both eMTC and NB-IoT devices when EDT is used in CP IoT 5GS optimization.

[0419] Embodiment 11 may include a device comprising:

[0420] Components used to extend the RRC Early Data Complete message to include a wait time with a smaller value and redirected carrier information for eMTC and NB-IoT devices when EDT is used in CP IoT 5GS optimization.

[0421] Embodiment 12 may include a device comprising:

[0422] means for indicating a new AS RAI to indicate that both the additional UL data and the DL data are not extended using extension of the RRC message; or

[0423] A means for using one of:

[0424] The reserved bits in the MAC subheader of the existing Rel-13 AS RAI,

[0425] Fixed size of zero-bit MAC CE with new LCID or eLCID code points,

[0426] or reserved bits in existing AS RAI code points and subheaders.

[0427] Embodiment 13 may include a device comprising:

[0428] Components for:

[0429] Do not use new RNA or RNA update timer; or

[0430] Do not use RAN-based paging DRX cycle length,

[0431] When the device is in RRC Inactive state.

[0432] Embodiment 14 may include an apparatus for:

[0433] receiving an indication from NAS for the cell to use 5GC; and

[0434] When E-UTRA connected to 5GC is supported, an RRC Connection Request is sent.

[0435] Embodiment 15 may include an apparatus according to embodiment 14 and / or some other embodiments herein, wherein the device identity corresponds to 5GCN when at least one of the following occurs:

[0436] The spare bit is set to "1";

[0437] Using a predefined extension of the RRC Connection Request message; or

[0438] The UL CCCH message class extension for the RRC Connection Request message is used.

[0439] Embodiment 16 may include an apparatus according to embodiment 15 and / or some other embodiments herein, wherein sending an RRC connection request further includes sending an RRC connection recovery request, and wherein the device identity corresponds to: a recovery ID if UP IoT5GS optimization is used, or an I-RNTI if the device is in an RRC inactive state.

[0440] Embodiment 17 may include an apparatus according to embodiment 15 and / or some other embodiments herein, wherein when AS security has not been enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for NB-IoT, and wherein the device identity corresponds to a 40-bit NG-5GS-TMSI.

[0441] Embodiment 18 may include an apparatus according to embodiment 17 and / or some other embodiments herein, further configured to send the remaining 6 bits of the device identity in an RRCConnectionReestablishmentComplete-NB message.

[0442] Embodiment 19 may include the apparatus according to Embodiment 14 and / or some other embodiments herein, further configured to:

[0443] The device capabilities are carried in the RRCConnectionSetupComplete message, where the device capabilities are forwarded by RAN to 5GCN.

[0444] Embodiment 20 may include an apparatus according to embodiment 19 and / or some other embodiments herein, wherein the device capability is one of: CE Mode B support, attachWithoutPDN-Connectivity, up-CIoT-5GS-Optimisation or cp-CIoT-5GS-Optimisation,

[0445] Embodiment 21 may include the apparatus according to Embodiment 14 and / or some other embodiments herein, further configured to:

[0446] Indicates whether the RRC Inactive state is supported in the RRCConnectionSetupComplete message, or whether RRC Inactive is preferred immediately.

[0447] Embodiment 22 may include an apparatus for:

[0448] Send RAN broadcast notifying whether connectivity to 5GCN is supported;

[0449] Sending cell access information in SIB1-BR or SIB1-NB; and

[0450] Sends whether CIoT 5GS optimization and EDT are supported in the BR version of SIB2 or SIB2-NB.

[0451] Embodiment 23 may include a device for:

[0452] Use a new UL-CCCH message class extension for the new RRC EarlyDataRequest message; or

[0453] When EDT is used in CP IoT 5GS optimization, a key extension of the existing RRC EarlyDataRequest is used to carry the full NG-5G-S-TMSI for both eMTC and NB-IoT devices.

[0454] Embodiment 24 may include an apparatus for:

[0455] Extend the RRC Early Data Complete message to include a waiting time with a smaller value and redirected carrier information for eMTC and NB-IoT devices when EDT is used in CP IoT 5GS optimization.

[0456] Embodiment 25 may include a device for:

[0457] Indicating a new AS RAI to indicate that both the additional UL data and the DL data are not extended using extension of the RRC message; or

[0458] Use one of the following:

[0459] The reserved bits in the MAC subheader of the existing Rel-13 AS RAI,

[0460] Fixed size of zero-bit MAC CE with new LCID or eLCID code points,

[0461] or reserved bits in existing AS RAI code points and subheaders.

[0462] Embodiment 26 may include an apparatus for:

[0463] Do not use new RNA or RNA update timer; or

[0464] Do not use RAN-based paging DRX cycle length,

[0465] When the device is in RRC Inactive state.

[0466] Embodiment 27 may include a method comprising:

[0467] receiving or causing receipt of an indication from the NAS for use of 5GC for the cell; and

[0468] Sends or causes an RRC Connection Request to be sent when E-UTRA connected to 5GC is supported.

[0469] Embodiment 28 may include a method according to embodiment 27 and / or some other embodiments herein, wherein the device identity corresponds to 5GCN when at least one of the following occurs:

[0470] The spare bit is set to "1";

[0471] Using a predefined extension of the RRC Connection Request message; or

[0472] The UL CCCH message class extension for the RRC Connection Request message is used.

[0473] Embodiment 29 may include a method according to embodiment 28 and / or some other embodiments herein, wherein sending or causing sending an RRC connection request includes sending or causing sending an RRC connection recovery request, and wherein the device identity corresponds to: if UP IoT 5GS optimization is used, then the recovery ID, or if the device is in an RRC inactive state, then the I-RNTI.

[0474] Embodiment 30 may include a method according to embodiment 28 and / or some other embodiments of the present invention, wherein when AS security has not been enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for NB-IoT, and the device identity corresponds to a 40-bit NG-5GS-TMSI.

[0475] Embodiment 31 may include a method according to embodiment 30 and / or some other embodiments herein, further comprising sending or causing sending of the remaining 6 bits of the device identity in an RRCConnectionReestablishmentComplete-NB message.

[0476] Embodiment 32 may include the method according to Embodiment 27 and / or some other embodiments herein, further comprising:

[0477] The device capabilities are carried or caused to be carried in the RRCConnectionSetupComplete message, where the device capabilities are forwarded by the RAN to the 5GCN.

[0478] Embodiment 33 may include a method according to embodiment 32 and / or some other embodiments herein, wherein the device capability is one of: CE Mode B Support, attachWithoutPDN-Connectivity, up-CIoT-5GS-Optimisation or cp-CIoT-5GS-Optimisation,

[0479] Embodiment 34 may be the method according to embodiment 27 and / or some other embodiments herein, further comprising:

[0480] Indicating or causing an indication in the RRCConnectionSetupComplete message whether the RRC Inactive state is supported, or whether immediate use of RRC Inactive is preferred.

[0481] Embodiment 35 may include a method comprising:

[0482] sending, or causing to be sent, a RAN broadcast informing whether connectivity to 5GCN is supported; and

[0483] Send or cause to be sent cell access information in SIB1-BR or SIB1-NB, and send or cause to be sent whether CIoT 5GS optimization and EDT are supported in the BR version of SIB2 or SIB2-NB.

[0484] Embodiment 36 may include a method comprising:

[0485] When EDT is used in CP IoT 5GS optimization, a new UL-CCCH message class extension is used or causes to be used for the new RRCEarlyDataRequest message, or a key extension of the existing RRCEarlyDataRequest is used or causes to be used for carrying the full NG-5G-S-TMSI for both eMTC and NB-IoT devices.

[0486] Embodiment 37 may include a method comprising:

[0487] When EDT is used in CP IoT 5GS optimization, the RRCEarlyDataComplete message is extended or caused to be extended to include a waiting time with a smaller value and redirected carrier information for eMTC and NB-IoT devices.

[0488] Embodiment 38 may include a method comprising:

[0489] indicating or causing an indication of a new AS RAI to indicate that no extension of the RRC message is used to extend both the additional UL data and the DL data, or

[0490] Use or cause to be used any of the following:

[0491] The reserved bits in the MAC subheader of the existing Rel-13 AS RAI,

[0492] Fixed size of zero-bit MAC CE with new LCID or eLCID code points,

[0493] or reserved bits in existing AS RAI code points and subheaders.

[0494] Embodiment 39 may include a method comprising:

[0495] When the device is in RRC inactive state:

[0496] not use or cause the use of new RNA or RNA update timers; or

[0497] Do not use or cause to use RAN based paging DRX cycle length.

[0498] Embodiment 40 includes an apparatus according to embodiments 1-13 and / or some other embodiments herein, wherein the apparatus is implemented in or by a user equipment (UE).

[0499] Embodiment 41 includes an apparatus according to embodiments 14-26 and / or some other embodiments herein, wherein the apparatus is implemented in or by a user equipment (UE).

[0500] Embodiment 42 includes an apparatus according to embodiments 23-39 and / or some other embodiments herein, the method being performed by an apparatus implemented in or by a user equipment (UE).

[0501] Embodiment 43 may include a method of sending an RRC connection request when the UE supports E-UTRA connected to 5GC and the NAS is instructed to use 5GC for the selected cell.

[0502] Embodiment 44 may include a method according to embodiment 1 or some other embodiments of the present invention, wherein when the spare bit is set to "1" or a new key extension of the RRC connection request message or a new UL CCCH message class extension of the RRC connection request message is used, the UE identity corresponds to 5GCN.

[0503] Embodiment 45 may include a method according to embodiments 1 and 2 or some other embodiments of the present invention, wherein the RRC connection request corresponds to an RRC connection recovery request, and if UP IoT 5GS optimization is used, the UE identity corresponds to the recovery ID, or if the UE is in an RRC inactive state, the UE identity corresponds to the I-RNTI.

[0504] Embodiment 46 may include a method according to embodiments 1 and 2 or some other embodiments of the present invention, wherein when AS security is not enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for NB-IoT, and the UE identity corresponds to a 40-bit NG-5GS-TMSI.

[0505] Embodiment 47 may include a method according to embodiment 4 or some other embodiments herein, wherein the remaining 6 bits of the UE identity are sent in the RRCConnectionReestablishmentComplete-NB message.

[0506] Embodiment 48 may include the method wherein UE capabilities (e.g., CE Mode B Support, attachWithoutPDN-Connectivity, up-CIoT-5GS-Optimisation, cp-CIoT-5GS-Optimisation) are carried in the RRCConnectionSetupComplete message and the RAN forwards it to the 5GCN.

[0507] Embodiment 49 may include the method wherein the UE indicates in the RRCConnectionSetupComplete message whether it supports the RRC Inactive state or whether it prefers to use RRC Inactive immediately.

[0508] Embodiment 50 may include the method, wherein the RAN broadcasts whether it supports connectivity and cell access information to 5GCN in SIB1-BR (or SIB1-NB), and broadcasts whether it supports CIoT5GS optimization and EDT in the BR version of SIB2 (or SIB2-NB).

[0509] Embodiment 51 may include the method wherein a new UL-CCCH message class extension for a new RRCEarlyDataRequest message is defined or a key extension for the existing RRCEarlyDataRequest is defined to carry the full NG-5G-S-TMSI for both eMTC and NB-IoT UEs when using EDT in CP IoT 5GS optimization.

[0510] Embodiment 52 may include the method wherein when EDT is used in CP IoT 5GS optimization, the RRC EarlyDataComplete message is extended to include a waiting time with a smaller value and redirected carrier information for both eMTC and NB-IoT UEs.

[0511] Embodiment 53 may include a method of indicating a new AS RAI to indicate additional UL data and DL data without using an extension of the RRC message or using reserved bits in the MAC subheader of the existing Rel-13 AS RAI or a fixed size of a zero-bit MAC CE with a new LCID or eLCID code point or the existing AS RAI code point and reserved bits in the subheader are extended (different from the existing Rel-13 AS RAI).

[0512] Embodiment 54 may include the method wherein the UE in RRC Inactive state does not use a new RNA or RNA update timer or does not use a RAN based paging DRX cycle length.

[0513] Embodiment 55 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 39, or any other method or process described herein.

[0514] Embodiment 56 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 in or related to any one of Embodiments 1 to 39 or any other method or process described herein.

[0515] Embodiment 57 may include a device comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 39, or any other method or process described herein.

[0516] Embodiment 58 may include methods, techniques or processes described in or related to any one of Embodiments 1 to 39, or parts or components thereof.

[0517] Embodiment 59 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, or a portion thereof, described in or related to any one of Embodiments 1 to 39.

[0518] Embodiment 60 may include a signal as described or associated with any one of Embodiments 1 to 39, or a portion or component thereof.

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

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

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

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

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

[0524] abbreviation

[0525] For the purposes of this document, the following abbreviations may be applied to the examples and embodiments discussed herein but are not meant to be limiting.

[0526] 3GPP Third Generation Partnership Project

[0527] 4G Fourth Generation

[0528] 5G Fifth Generation

[0529] 5GC 5G Core Network

[0530] ACK

[0531] AF Application Function

[0532] AM Confirmation Mode

[0533] AMBR Aggregate Maximum Bit Rate

[0534] AMF Access and Mobility Management Function

[0535] AN Access Network

[0536] ANR Automatic Neighbor Relation

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

[0538] API Application Programming Interface

[0539] APN Access Point Name

[0540] ARP Assignment Reserve Priority

[0541] ARQ Automatic Repeat Request

[0542] AS Access Layer

[0543] ASN.1 Abstract Syntax Notation

[0544] AUSF authentication server function

[0545] AWGN Additive White Gaussian Noise

[0546] BCH Broadcast Channel

[0547] BER Bit Error Rate

[0548] BFD Beam Fault Detection

[0549] BLER Block Error Rate

[0550] BPSK Binary Phase Shift Keying

[0551] BRAS Broadband Remote Access Server

[0552] BSS Business Support System

[0553] BS Base Station

[0554] BSR Buffer Status Report

[0555] BW Bandwidth

[0556] BWP Bandwidth Part

[0557] C-RNTI Cell Radio Network Temporary Identifier

[0558] CA Carrier Aggregation, Certification Authority

[0559] CAPEX Capital Expenditure

[0560] CBRA Contention-based random access

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

[0562] CCA Clear Channel Assessment

[0563] CCE Control Channel Element

[0564] CCCH Common Control Channel

[0565] CE Coverage Enhancement

[0566] CDM Content Delivery Network

[0567] CDMA Code Division Multiple Access

[0568] CFRA Contention-free random access

[0569] CG Cell Group

[0570] CI Cell ID

[0571] CIoT Cellular Internet of Things

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

[0573] CIM Common Information Model

[0574] CIR Carrier to Interference Ratio

[0575] CK Cryptographic Key

[0576] CM Connection Management, Conditionally Mandatory

[0577] CMAS Commercial Mobile Alert Service

[0578] CMD command

[0579] CMS Cloud Management System

[0580] CO Conditional optional

[0581] CoMP Coordinated Multipoint

[0582] CORESET Control Resource Set

[0583] COTS Commercial Off-the-Shelf

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

[0585] CPD Connection Point Descriptor

[0586] CPE user terminal equipment

[0587] CPICH Common Pilot Channel

[0588] CQI Channel Quality Indicator

[0589] CPU CSI processing unit, central processing unit

[0590] C / R Command / Response field bit

[0591] CRAN Cloud Radio Access Network, Cloud RAN

[0592] CRB Common Resource Block

[0593] CRC Cyclic Redundancy Check

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

[0595] C-RNTI Cell RNTI

[0596] CS Circuit Switched

[0597] CSAR Cloud Service Archive

[0598] CSI Channel State Information

[0599] CSI-IM CSI interference measurement

[0600] CSI-RS CSI reference signal

[0601] CSI-RSRP CSI reference signal received power

[0602] CSI-RSRQ CSI reference signal reception quality

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

[0604] CSMA Carrier Sense Multiple Access

[0605] CSMA / CA CSMA with collision avoidance

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

[0607] CTS Clear to Send

[0608] CW codeword

[0609] CWS Contention Window Size

[0610] D2D Device to Device

[0611] DC Dual Connection, Direct Current

[0612] DCI Downlink Control Information

[0613] DF deployment preferences

[0614] DL Downlink

[0615] DMTF Distributed Management Task Force

[0616] DPDK Data Plane Development Kit

[0617] DM-RS, DMRS Demodulation Reference Signal

[0618] DN Data Network

[0619] DRB Data Radio Bearer

[0620] DRS Discovery Reference Signal

[0621] DRX Discontinuous Reception

[0622] DSL Domain Specific Language Digital Subscriber Line

[0623] DSLAM DSL Access Multiplexer

[0624] DwPTS Downlink Pilot Time Slot

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

[0626] E2E End-to-End

[0627] ECCA Extended Clear Channel Assessment, Extended CCA

[0628] ECCE Enhanced Control Channel Element, Enhanced CCE

[0629] ED Energy Detection

[0630] EDT Energy Delayed Transaction

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

[0632] EGMF exposes governance management functions

[0633] EGPRS Enhanced GPRS

[0634] EIR Equipment Identity Register

[0635] eLAA Enhanced License Assisted Access, enhanced LAA

[0636] EM Component Manager

[0637] eMBB Enhanced Mobile Broadband

[0638] EMS Component Management System

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

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

[0641] EPC Evolved Packet Core

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

[0643] EPRE Energy per resource element

[0644] EPS Evolved Packet System

[0645] EREG Enhanced REG, enhanced resource element group

[0646] ETSI European Telecommunications Standards Institute

[0647] ETWS Earthquake and Tsunami Warning System

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

[0649] E-UTRA Evolved UTRA

[0650] E-UTRAN Evolved UTRAN

[0651] EV2X Enhanced V2X

[0652] F1AP F1 Application Protocol

[0653] F1-C F1 control plane interface

[0654] F1-U F1 User Plane Interface

[0655] FACCH Fast Associated Control Channel

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

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

[0658] FACH Forward Access Channel

[0659] FAUSCH Fast Uplink Signalling Channel

[0660] FB Function Block

[0661] FBI Feedback

[0662] FCC Federal Communications Commission

[0663] FCCH Frequency Correction Channel

[0664] FDD Frequency Division Duplex

[0665] FDM Frequency Division Multiplexing

[0666] FDMA Frequency Division Multiple Access

[0667] FE Front End

[0668] FEC Forward Error Correction

[0669] FFS for further study

[0670] FFT Fast Fourier Transform

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

[0672] FN Frame Number

[0673] FPGA Field Programmable Gate Array

[0674] FR Frequency Range

[0675] G-RNTI GERAN Radio Network Temporary Identity

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

[0677] GSM Gateway GPRS Support Node

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

[0679] gNB Next Generation Node B

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

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

[0682] GNSS Global Navigation Satellite System

[0683] GPRS General Packet Radio Service

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

[0685] GTP GPRS Tunneling Protocol

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

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

[0688] GUMMEI Globally Unique MME Identifier

[0689] GUTI Globally Unique Temporary UE Identifier

[0690] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0691] HANDO, HO switch

[0692] HFN Superframe Number

[0693] HHO Hard Handover

[0694] HLR Home Location Register

[0695] HN Home Network

[0696] HO Handover

[0697] HPLMN Home Public Land Mobile Network

[0698] HSDPA High Speed ​​Downlink Packet Access

[0699] HSN Hopping Sequence Number

[0700] HSPA High Speed ​​Packet Access

[0701] HSS Home Subscriber Server

[0702] HSUPA High Speed ​​Uplink Packet Access

[0703] HTTP Hypertext Transfer Protocol

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

[0705] I-Block Information Block

[0706] ICCID Integrated Circuit Card Identifier

[0707] ICIC Inter-cell Interference Coordination

[0708] ID, identifier

[0709] IDFT Inverse Discrete Fourier Transform

[0710] IE Information Elements

[0711] IBE In-Band Emission

[0712] IEEE Institute of Electrical and Electronics Engineers

[0713] IEI Information Element Identifier

[0714] IEIDL Information Element Identifier Data Length

[0715] IETF Internet Engineering Task Force

[0716] IF infrastructure

[0717] IM Interference Measurement, Intermodulation, IP Multimedia

[0718] IMC IMS credentials

[0719] IMEI International Mobile Equipment Identity

[0720] IMGI International Mobile Group Identity

[0721] IMPI IP Multimedia Privacy Identity

[0722] IMPU IP Multimedia Public Identity

[0723] IMS IP Multimedia Subsystem

[0724] IMSI International Mobile Subscriber Identity

[0725] IoT

[0726] IP Internet Protocol

[0727] Ipsec IP security, Internet Protocol security

[0728] IP-CAN IP connection access network

[0729] IP-M IP Multicast

[0730] IPv4 Internet Protocol version 4

[0731] IPv6 Internet Protocol version 6

[0732] IR

[0733] IS Synchronization

[0734] I-RNTI stands for Radio Network Temporary Identifier

[0735] IRP Integration Reference Point

[0736] ISDN Integrated Services Digital Network

[0737] ISIM IM Service Identity Module

[0738] ISO International Organization for Standardization

[0739] ISP Internet Service Provider

[0740] IWF interworking function

[0741] I-WLAN Intercommunication WLAN

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

[0743] kB kilobyte (1000 bytes)

[0744] kbps kilobits per second

[0745] Kc Cryptographic key

[0746] Ki Individual user authentication key

[0747] KPI Key Performance Indicator

[0748] KQI Key Quality Indicator

[0749] KSI Key Set Identifier

[0750] ksps kilosymbols per second

[0751] KVM Kernel Virtual Machine

[0752] L1 Layer 1 (physical layer)

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

[0754] L2 Layer 2 (Data Link Layer)

[0755] L3 Layer 3 (Network Layer)

[0756] LAA License Assisted Access

[0757] LAN Local Area Network

[0758] LBT Listen before you speak

[0759] LCM Lifecycle Management

[0760] LCR Low Chip Rate

[0761] LCS Location Services

[0762] LCID Logical Channel ID

[0763] LI layer indicator

[0764] LLC Logical Link Control, Low Layer Compatibility

[0765] LPLMN Local PLMN

[0766] LPP LTE Positioning Protocol

[0767] LSB Least Significant Bit

[0768] LTE Long Term Evolution

[0769] LWA LTE-WLAN Aggregation

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

[0771] LTE Long Term Evolution

[0772] M2M Machine to Machine

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

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

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

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

[0777] MANO Management and Orchestration

[0778] MBMS Multimedia Broadcast Multicast Service

[0779] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0780] MCC Mobile Country Code

[0781] MCG Master Cell Group

[0782] MCOT Maximum Channel Occupancy Time

[0783] MCS Modulation and Coding Scheme

[0784] MDAF Management Data Analysis Function

[0785] MDAS Management Data Analysis Service

[0786] Minimization of MDT-driven testing

[0787] ME Mobile Devices

[0788] MeNB Master eNB

[0789] MER message error rate

[0790] MGL Measurement Gap Length

[0791] MGRP measurement gap repetition period

[0792] MIB Master Information Block, Management Information Base

[0793] MIMO Multiple Input Multiple Output

[0794] MLC Mobile Location Center

[0795] MM Mobility Management

[0796] MME Mobility Management Entity

[0797] MN Master Node

[0798] MO measurement object, mobile station calling

[0799] MPBCH MTC Physical Broadcast Channel

[0800] MPDCCH MTC Physical Downlink Control Channel

[0801] MPDSCH MTC Physical Downlink Shared Channel

[0802] MPRACH MTC Physical Random Access Channel

[0803] MPUSCH MTC Physical Uplink Shared Channel

[0804] MPLS Multi-Protocol Label Switching

[0805] MS Mobile Station

[0806] MSB Most Significant Bit

[0807] MSC Mobile Switching Center

[0808] MSI minimum system information, MCH scheduling information

[0809] MSID Mobile Station Identifier

[0810] MSIN Mobile Station Identification Number

[0811] MSISDN Mobile Subscriber ISDN Number

[0812] MT mobile station called, mobile terminal

[0813] MTC Machine Type Communication

[0814] mMTC Massive MTC, massive machine type communication

[0815] MU-MIMO Multi-User MIMO

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

[0817] NACK Negative Acknowledgement

[0818] NAI Network Access Identifier

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

[0820] NCT Network Connection Topology

[0821] NEC network capabilities exposed

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

[0823] NEF Network Exposure Function

[0824] NF Network Function

[0825] NFP Network Forwarding Path

[0826] NFPD Network Forwarding Path Descriptor

[0827] NFV Network Function Virtualization

[0828] NFVI NFV Infrastructure

[0829] NFVO NFV Orchestrator

[0830] NG Next generation, next generation

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

[0832] NM Network Manager

[0833] NMS Network Management System

[0834] N-PoP Network Point of Presence

[0835] NMIB, N-MIB Narrowband MIB

[0836] NPBCH Narrowband Physical Broadcast Channel

[0837] NPDCCH Narrowband Physical Downlink Control Channel

[0838] NPDSCH Narrowband Physical Downlink Shared Channel

[0839] NPRACH Narrowband Physical Random Access Channel

[0840] NPUSCH Narrowband Physical Uplink Shared Channel

[0841] NPSS Narrowband Primary Synchronization Signal

[0842] NSSS Narrowband Secondary Synchronization Signal

[0843] NR New Radio, Neighbor Relations

[0844] NRF NF Repository Functionality

[0845] NRS Narrowband Reference Signal

[0846] NS Network Services

[0847] NSA Non-standalone operation mode

[0848] NSD Network Service Descriptor

[0849] NSR Network Service Record

[0850] NSSAI Network Slice Selection Assistance Information

[0851] S-NNSAI Single NSSAI

[0852] NSSF network slice selection function

[0853] NW Network

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

[0855] NZP Non Zero Power

[0856] O&M Operation and Maintenance

[0857] ODU2 Optical Channel Data Unit - Type 2

[0858] OFDM Orthogonal Frequency Division Multiplexing

[0859] OFDMA Orthogonal Frequency Division Multiple Access

[0860] OOB Out of Band

[0861] OOS Out of Sync

[0862] OPEX Operational Expenses

[0863] OSI Other System Information

[0864] OSS Operation Support System

[0865] OTA

[0866] PAPR Peak to Average Power Ratio

[0867] PAR Peak to Average Ratio

[0868] PBCH Physical Broadcast Channel

[0869] PC Power Control, Personal Computer

[0870] PCC Primary Component Carrier, Primary CC

[0871] Pcell Primary cell

[0872] PCI Physical Cell ID, Physical Cell Identity

[0873] PCEF Policy and Charging Enforcement Function

[0874] PCF Policy Control Function

[0875] PCRF Policy Control and Charging Rules Function

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

[0877] PDCCH Physical Downlink Control Channel

[0878] PDCP Packet Data Convergence Protocol

[0879] PDN Packet Data Network, Public Data Network

[0880] PDSCH Physical Downlink Shared Channel

[0881] PDU Protocol Data Unit

[0882] PEI Persistent Equipment Identifier

[0883] PFD Packet Flow Description

[0884] P-GW PDN Gateway

[0885] PHICH Physical Hybrid ARQ Indicator Channel

[0886] PHY Physical Layer

[0887] PLMN Public Land Mobile Network

[0888] PIN Personal Identification Number

[0889] PM performance measurement

[0890] PMI Precoding matrix indicator

[0891] PNF Physical Network Function

[0892] PNFD Physical Network Functional Descriptor

[0893] PNFR Physical Network Function Record

[0894] POC PTT over Cellular

[0895] PP, PTP Point to Point

[0896] PPP Point-to-Point Protocol

[0897] PRACH Physical RACH

[0898] PRB Physical Resource Block

[0899] PRG Physical Resource Group

[0900] ProSe Proximity-based services

[0901] PRS Positioning Reference Signal

[0902] PRR Packet Receive Radio

[0903] PS Packet Service

[0904] PSBCH Physical Sidelink Broadcast Channel

[0905] PSDCH Physical Sidelink Downlink Channel

[0906] PSCCH Physical Sidelink Control Channel

[0907] PSSCH Physical Sidelink Shared Channel

[0908] PSCell Primary SCell

[0909] PSS Primary Synchronization Signal

[0910] PSTN Public Switched Telephone Network

[0911] PT-RS Phase Tracking Reference Signal

[0912] PTT Push to Talk

[0913] PUCCH Physical Uplink Control Channel

[0914] PUSCH Physical Uplink Shared Channel

[0915] QAM Quadrature Amplitude Modulation

[0916] QCI QoS Class Identifier

[0917] QCL Quasi-Co-sited

[0918] QFI QoS flow ID, QoS flow identifier

[0919] QoS Quality of Service

[0920] QPSK Quadrature (Quaternary) Phase Shift Keying

[0921] QZSS Quasi-Zenith Satellite System

[0922] RA-RNTI Random Access RNTI

[0923] RAB Radio Access Bearer, Random Access Burst

[0924] RACH Random Access Channel

[0925] RADIUS Remote Authentication Dial-In User Service

[0926] RAI Routing Area Identification

[0927] RAN Radio Access Network

[0928] RAND random number (for authentication)

[0929] RAR Random Access Response

[0930] RAT Radio Access Technology

[0931] RAU Routing Area Update

[0932] RB Resource Block, Radio Bearer

[0933] RBG Resource Block Group

[0934] REG Resource Element Group

[0935] Rel Release

[0936] REQ Request

[0937] RF

[0938] RI Rank Indicator

[0939] RIV Resource Indicator Value

[0940] RL Radio Link

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

[0942] RLC AM RLC Acknowledgement Mode

[0943] RLC UM RLC Unacknowledged Mode

[0944] RLF Radio Link Failure

[0945] RLM Radio Link Monitoring

[0946] RLM-RS Reference signal for RLM

[0947] RM Registration Management

[0948] RMC Reference Measurement Channel

[0949] RMSI Remaining MSI, Remaining Minimum System Information

[0950] RN Relay Node

[0951] RNC Radio Network Controller

[0952] RNL Radio Network Layer

[0953] RNTI Radio Network Temporary Identifier

[0954] ROHC Robust Header Compression

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

[0956] RRM Radio Resource Management

[0957] RS reference signal

[0958] RSRP Reference Signal Received Power

[0959] RSRQ Reference Signal Received Quality

[0960] RSSI Reference Signal Strength Indicator

[0961] RSU Road Side Unit

[0962] RSTD Reference Signal Time Difference

[0963] RTP Real Time Protocol

[0964] RTS Ready to Send

[0965] RTT Round Trip Time

[0966] Rx receive, receive, receiver

[0967] S1AP S1 Application Protocol

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

[0969] S1-U S1 for user plane

[0970] S-GW Service Gateway

[0971] S-RNTI SRNC Radio Network Temporary Identifier

[0972] S-TMSI SAE temporary mobile station identifier

[0973] SA Standalone Operation Mode

[0974] SAE system architecture evolution

[0975] SAP Service Access Point

[0976] SAPD Service Access Point Descriptor

[0977] SAPI Service Access Point Identifier

[0978] SCC Secondary Component Carrier, Secondary CC

[0979] Scell

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

[0981] SCG Secondary Cell Group

[0982] SCM Security Context Management

[0983] SCS Subcarrier Spacing

[0984] SCTP Stream Control Transmission Protocol

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

[0986] SDL Supplemental Downlink

[0987] SDNF Structured Data Storage Network Function

[0988] SDP Service Discovery Protocol (Bluetooth related)

[0989] SDSF structured data storage function

[0990] SDU Service Data Unit

[0991] SEAF Security Anchoring Function

[0992] SeNB Assisted eNB

[0993] SEPP Security Edge Protection Proxy

[0994] SFI Slot Format Indicator

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

[0996] SFN System Frame Number

[0997] SgNB

[0998] SGSN Serving GPRS Support Node

[0999] S-GW Service Gateway

[1000] SI System Information

[1001] SI-RNTI System Information RNTI

[1002] SIB System Information Block

[1003] SIM Subscriber Identity Module

[1004] SIP Session Initiation Protocol

[1005] SiP System in Package

[1006] SL Side Link

[1007] SLA Service Level Agreement

[1008] SM Session Management

[1009] SMF session management functions

[1010] SMS Short Message Service

[1011] SMSF SMS Function

[1012] SMTC SSB-based measurement timing configuration

[1013] SN Secondary node, serial number

[1014] SoC System on Chip

[1015] SON Self-Organizing Network

[1016] SpCell Special Cell

[1017] SP-CSI-RNTI Semi-persistent CSIRNTI

[1018] SPS Semi-persistent Scheduling

[1019] SQN Serial Number

[1020] SR Scheduling Request

[1021] SRB Signalling Radio Bearer

[1022] SRS Sounding Reference Signal

[1023] SS Sync Signal

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

[1025] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[1026] SSC Session and Service Continuity

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

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

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

[1030] SSS Secondary synchronization signal

[1031] SSSG Search Space Group

[1032] SSSIF Search Space Set Indicator

[1033] SST Slice / Service Type

[1034] SU-MIMO Single User MIMO

[1035] SUL Supplementary Uplink

[1036] TA timing advance, tracking area

[1037] TAC Tracking Area Code

[1038] TAG Timing Advance Group

[1039] TAU Tracking Area Updates

[1040] TB Transfer Block

[1041] TBS Transport Block Size

[1042] TBD To be defined

[1043] TCI Transmission Configuration Indicator

[1044] TCP transport communication protocol

[1045] TDD Time Division Duplex

[1046] TDM Time Division Multiplexing

[1047] TDMA Time Division Multiple Access

[1048] TE Terminal Equipment

[1049] TEID Tunnel Endpoint Identifier

[1050] TFT Business Flow Template

[1051] TMSI Temporary Mobile Subscriber Identity

[1052] TNL Transport Network Layer

[1053] TPC Transmit Power Control

[1054] TPMI Transmitted Precoding Matrix Indicator

[1055] TR Technical Report

[1056] TRP,TRxP Transmission Receive Point

[1057] TRS Tracking Reference Signal

[1058] TRx Transceiver

[1059] TS Technical Specification, Technical Standard

[1060] TTI Transmission Time Interval

[1061] Tx transmission, transmission, transmitter

[1062] U-RNTI UTRAN Radio Network Temporary Identity

[1063] UART Universal Asynchronous Receiver and Transmitter

[1064] UCI Uplink Control Information

[1065] UE User Equipment

[1066] UDM Unified Data Management

[1067] UDP User Datagram Protocol

[1068] UDSF Unstructured Data Storage Network Function

[1069] UICC Universal Integrated Circuit Card

[1070] UL Uplink

[1071] UM Unconfirmed Mode

[1072] UML Unified Modeling Language

[1073] UMTS Universal Mobile Telecommunications System

[1074] UP User Plane

[1075] UPF User Plane Function

[1076] URI Uniform Resource Identifier

[1077] URL Uniform Resource Locator

[1078] URLLC Ultra-Reliable Low Latency

[1079] USB Universal Serial Bus

[1080] USIM Universal Subscriber Identity Module

[1081] USS UE-specific search space

[1082] UTRA UMTS Terrestrial Radio Access

[1083] UTRAN Universal Terrestrial Radio Access Network

[1084] UwPTS Uplink Pilot Time Slot

[1085] V2I Vehicle to Infrastructure

[1086] V2P Vehicle to Pedestrian

[1087] V2V Vehicle to Vehicle

[1088] V2X: Vehicle-to-Everything

[1089] VIM Virtualization Infrastructure Manager

[1090] VL Virtual Link

[1091] VLAN virtual LAN, virtual local area network

[1092] VM Virtual Machine

[1093] VNF Virtualized Network Function

[1094] VNFFG VNF forwarding graph

[1095] VNFFGD VNF Forwarding Graph Descriptor

[1096] VNFM VNF Manager

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

[1098] VPLMN Visited Public Land Mobile Network

[1099] VPN Virtual Private Network

[1100] VRB Virtual Resource Block

[1101] WiMAX Worldwide Interoperability for Microwave Access

[1102] WLAN Wireless Local Area Network

[1103] WMAN Wireless Metropolitan Area Network

[1104] WPAN Wireless Personal Area Network

[1105] X2-C X2 control plane

[1106] X2-U X2 user plane

[1107] XML Extensible Markup Language

[1108] XRES Expected User Response

[1109] XOR

[1110] ZC Zadoff-Chu

[1111] ZP Zero Power

[1112] the term

[1113] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein but are not intended to be limiting.

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

[1115] 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".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[1134] 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, comprising: Radio front-end circuits; as well as A processor circuit, the processor circuit being configured to: Using the radio front end circuit, receiving an indication from a non-access stratum NAS of a cell to use a 5G core network 5GCN for the cell; In response to the indication to use the 5GCN, using the radio front end circuitry and transmitting a radio resource control (RRC) connection request to a radio access network RAN ​​of the cell, wherein the RRC connection request includes an extension indicating that the 5GCN is supported by the UE; Instructing the access layer AS to release the auxiliary indicator RAI via an RRC message or layer 2 signaling, wherein the AS RAI is used to inform the RAN that the UE does not expect additional uplink data and downlink data; as well as receiving a message from the RAN to release the UE to one of an RRC inactive state, an RRC idle state with a suspension indication, or an RRC idle state without a suspension indication, wherein the message is sent by the RAN upon receiving the AS RAI and determining that the UE has no uplink data to transmit and no downlink data to receive.

2. The UE of claim 1, wherein the processor circuit is further configured to transmit the RRC connection request with a device identity indicating that the 5GCN is supported by the UE.

3. The UE according to claim 1, wherein the processor circuit is further configured to indicate support for the 5GCN by at least one of the following ways: setting a spare bit of the RRC connection request to a value of "1", using a predefined extension of the RRC connection request, or using an uplink UL common control channel CCCH message class extension for the RRC connection request.

4. The UE according to claim 1, wherein the RRC connection request includes an RRC connection recovery request, and the RRC connection recovery request includes a recovery identifier corresponding to the 5GCN.

5. The UE according to claim 1, wherein when the UE is in an RRC inactive state, the RRC connection request includes an identification radio network temporary identifier I-RNTI corresponding to the 5GCN.

6. The UE of claim 1, wherein the UE comprises an Internet of Things (IoT) UE, and when access stratum AS security is not enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for IoT.

7. The UE of claim 1, wherein the processor circuit is further configured to transmit device capabilities in an RRCConnectionSetupComplete message.

8. A method for a user equipment UE, comprising: The UE receives an indication from a non-access layer NAS of a cell that the cell uses a 5G core network 5GCN; In response to the indication to use the 5GCN, transmitting a radio resource control (RRC) connection request to a radio access network (RAN) of the cell, wherein the RRC connection request includes an extension indicating that the 5GCN is supported by the UE; Instructing the access layer AS to release the auxiliary indicator RAI via an RRC message or layer 2 signaling, wherein the AS RAI is used to inform the RAN that the UE does not expect additional uplink data and downlink data; as well as receiving a message from the RAN to release the UE to one of an RRC inactive state, an RRC idle state with a suspension indication, or an RRC idle state without a suspension indication, wherein the message is sent by the RAN upon receiving the AS RAI and determining that the UE has no uplink data to transmit and no downlink data to receive.

9. The method of claim 8, wherein transmitting the RRC connection request comprises transmitting a device identity indicating that the 5GCN is supported by the UE.

10. The method according to claim 8 further includes indicating support for the 5GCN by at least one of the following: setting a spare bit of the RRC connection request to a value of "1", using a predefined extension of the RRC connection request, or using an uplink UL common control channel CCCH message class extension for the RRC connection request.

11. The method of claim 8, wherein transmitting the RRC connection request comprises transmitting an RRC connection recovery request, the RRC connection recovery request comprising a recovery identifier corresponding to the 5GCN.

12. The method of claim 8, wherein transmitting the RRC connection request comprises transmitting an identification radio network temporary identifier (I-RNTI) corresponding to the 5GCN when the UE is in an RRC inactive state.

13. The method of claim 8, wherein the UE comprises an Internet of Things (IoT) UE, and when access layer AS security is not enabled, the RRC connection request corresponds to an RRCConnectionReestablishmentRequest-NB for IoT.

14. The method of claim 8, further comprising transmitting device capabilities in an RRCConnectionSetupComplete message.

15. A user equipment UE, comprising: a memory storing instructions; as well as A processor, wherein when executing the instructions, the processor is configured to: Receiving, from the non-access stratum NAS of the cell, an indication for the cell to use the 5G core network 5GCN; causing, in response to the indication to use the 5GCN, transmission of a radio resource control (RRC) connection request to a radio access network RAN ​​of the cell, wherein the RRC connection request includes an extension indicating that the 5GCN is supported by the UE; Instructing the access layer AS to release the auxiliary indicator RAI via an RRC message or layer 2 signaling, wherein the AS RAI is used to inform the RAN that the UE does not expect additional uplink data and downlink data; as well as receiving a message from the RAN to release the UE to one of an RRC inactive state, an RRC idle state with a suspension indication, or an RRC idle state without a suspension indication, wherein the message is sent by the RAN upon receiving the AS RAI and determining that the UE has no uplink data to transmit and no downlink data to receive.

16. The UE according to claim 15, wherein the processor is configured to indicate support for the 5GCN by at least one of the following ways: setting a spare bit of the RRC connection request to a value of "1", using a predefined extension of the RRC connection request, or using an uplink UL common control channel CCCH message class extension for the RRC connection request.

17. The UE according to claim 15, wherein in order to transmit the RRC connection request, the processor is configured to transmit the RRC connection recovery request including a recovery identifier corresponding to the 5GCN when the UE is in an RRC inactive state, or to transmit an identification radio network temporary identifier I-RNTI corresponding to the 5GCN.

Images