System, method and apparatus for resource allocation for scheduled PUSCH transmission in unlicensed spectrum

Abstract

A method for resource allocation for Msg‑3 transmission on an unlicensed spectrum may include receiving a random access response (RAR) grant including a 12-bit frequency domain resource allocation (FDRA) field. If the resource allocation type is type 1, some embodiments may zero-fill the FDRA field to interpret the 12-bit FDRA and determine the starting position of the allocated resources, where the scheduled PUSCH transmission is transmitted in the unlicensed spectrum. Some embodiments may use a virtual bandwidth part (BWP) to obtain the starting position and length of the allocated resources.

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, and more particularly to resource allocation for Msg-3 transmissions on unlicensed spectrum. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency Range 1 (FR1) includes frequency bands below 6 GHz, some of which may be used by previous standards but can potentially be expanded to cover potential new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 have a shorter range but higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 is a flow chart of a method to be performed by a UE for a COT structure indication according to one embodiment.

[0007] Figure 2 A UE implementation according to an embodiment is provided Figure 1 An illustration of an example of a method.

[0008] Figure 3 A table detailing COT structural indications according to one embodiment is shown.

[0009] Figure 4 is a flowchart of a method to be performed by a gNB for a COT structure indication using DCI format 2_0 according to one embodiment.

[0010] Figure 5 is a flowchart of a method for determining resource allocation for Msg-3 transmission according to the first embodiment.

[0011] Figure 6 is a flowchart of a method for determining resource allocation for Msg-3 transmission according to the second embodiment.

[0012] Figure 7 is a flowchart of a method for determining resource allocation for Msg-3 transmission according to the second embodiment.

[0013] Figure 8 Truncation of the FDRA field is shown according to one embodiment.

[0014] Fig. 9 is a flowchart of a method for a gNB according to one embodiment.

[0015] Fig.10 The random access (RA) procedure is shown.

[0016] Fig.11 An exemplary service-based architecture is shown in accordance with certain embodiments.

[0017] Fig.12 A UE according to one embodiment is shown.

[0018] Fig.13 A network node according to one embodiment is shown. DETAILED DESCRIPTION

[0019] New Radio (NR) for operation in unlicensed spectrum (NR-U) has adopted several enhancements related to resources between user equipment (UE) and next generation NodeB (gNB). These enhancements, while beneficial, may also introduce overlooked issues. Therefore, several new ways to determine resources for wireless communication should be adopted to address these overlooked issues.

[0020] For NR-U operation, the downlink control information (DCI) format 2_0 will be enhanced to provide a channel occupation time (COT) structure to facilitate the UE to make decisions on postponing physical downlink control channel (PDCCH) monitoring or periodic CSI reference signal (CSI-RS) detection. This change to DCI format 2_0 may result in less power consumption on the UE side. In addition, the UE can be configured with up to 64 values ​​of COT duration in symbols based on the reference subcarrier spacing (SCS). In addition, a bitmap is added to DCI format 2_0 to indicate the available LBT bandwidth.

[0021] Additional enhancements to DCI format 2_0 may include moving away from transmitting an "unknown" status to indicate LBT results for some LBT subbands. As an example, the "unknown" status for the LBT subband may occur at the start of a gNB-initiated COT, where the gNB completes the LBT operation very late and does not have enough time to prepare DCI format 2_0 to indicate the actual availability of the LBT subband for the seized COT based on the results of the LBT. Some embodiments described herein provide a way to signal an "unknown" status for LBT subbands within a wideband BWP. In addition, some embodiments describe how to indicate an LBT failure for a given serving cell that has been configured with a slot format indication (SFI) index field in DCI format 2_0.

[0022] In addition, for NR-U operation, 2 bits of the frequency domain resource allocation (FDRA) field in the uplink (UL) grant of the random access response (RAR) (Random Access Response) medium access control (MAC) protocol data unit (PDU) are reused to indicate the channel access parameters of CP extension. The number of bits of the frequency domain resource allocation field (FDRA) in NR-U is reduced from 14 to 12 for operation with shared spectrum channel access. However, if resource allocation type 1 is used, the FDRA field size for addressing the complete resource block (RB) range of the 20MHz initial UL bandwidth part (BWP) (e.g., 107 physical resource blocks (PRBs) for 15kHz SCS and 51 PRBs for 30kHz SCS) for 15kHz should be 13 bits. However, for interleaving-based resource allocation type 2, the requested FDRA field size will be 6 bits for 15kHz SCS and 5 bits for 30kHz SCS. Some embodiments herein describe how to interpret the 12-bit FDRA field in the RAR MAC PDU for resource allocation on a 20MHz initial BWP to appropriately address the Msg-3 transmission of the NR-U design. Msg-3 refers to the scheduled PUSCH transmission (Msg3).

[0023] In type 1 resource allocation, resources are allocated to one or more consecutive RBs by using two configuration parameters: the starting RB index and the number of consecutive RBs. In addition, the resource allocation granularity is one RB.

[0024] In type 2 resource allocation, resources are allocated to one or more interlaces, and each interlace consists of a group of PRBs. In addition, the resource allocation granularity is one interlace.

[0025] Various operations will be described in sequence as multiple discrete operations in a manner that is most helpful for understanding the present disclosure. However, the order of description should not be understood to imply that these operations are necessarily order-dependent. Specifically, these operations do not necessarily need to be performed in the order presented.

[0026] Additional details and examples are provided with reference to the following figures. The embodiments of the present disclosure may be understood with reference to the accompanying drawings, wherein like parts are represented by like numbers throughout. The components of the embodiments of the present disclosure as generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the systems and methods of the present disclosure is not intended to limit the scope of the present disclosure protected by the claims, but merely represents possible embodiments.

[0027] Figure 1 is a flow chart of a method 100 to be performed by a UE for receiving a COT structure indication using DCI format 2_0 and monitoring a PDCCH within a corresponding COT according to some embodiments.

[0028] In decision block 102, method 100 attempts to detect DCI format 2_0 from the gNB during a monitoring occasion. DCI format 2_0 includes an RB set indicator information element (IE) indicating the state of a listen-before-talk (LBT) subband and a COT duration indicator IE. If the UE does not detect DCI format 2_0 during the monitoring occasion, method 100 repeats decision block 102 during the next monitoring occasion to continue attempting to detect DCI format 2_0.

[0029] When method 100 detects DCI format 2_0, method 100 proceeds to decision box 104, where the UE determines the state of the LBT subband based on the available RB set indicator IE. In some embodiments, a special state of the available RB set indicator IE may be predefined to indicate an "unknown" state of the LBT subband within the active BWP on the corresponding serving cell. For example, an unknown state may be indicated by an available RB set indicator IE set to all zeros or all ones. In some embodiments, the available RB set indicator IE "b1b0" is set to 00, 10 to indicate an "unknown" state, where "b1" is associated with LBT subband 1 and "b0" is associated with LBT subband 0, and the UE detects DCI format 2_0 on LBT subband 0. In some embodiments, method 100 may include determining a value "K" from the COT duration indicator IE.

[0030] When the Available RB Set Indicator IE is not in the unknown state, the method 100 proceeds to block 108. In block 108, the method 100 starts monitoring all PDCCH candidates configured by DCI format 2_0 on the indicated LBT subband.

[0031] When the UE detects that the UE receives an "unknown" state for the LBT subband of the serving cell and the corresponding COT duration 120 is valid, the method proceeds to block 106. The unknown state can be determined by the available RB set indicator IE in DCI format 2_0, and the COT duration can be considered valid when the Cot duration indicator IE is set to a non-zero value "K".

[0032] Alternatively, in some embodiments, the UE may implicitly assume an LBT subband where it detects that DCI format 2_0 with an unknown state (e.g., all zeros or all ones) is available and only monitors PDCCH candidates thereon. Figure 2 , using this alternative method, the UE will only assume that LBT subband #0 is available and monitor PDCCH candidates on this subband. In other words, the UE will not monitor Figure 2 PDCCH candidates on LBT subband #1 in.

[0033] In block 106, the method starts monitoring all PDCCH candidates configured on all LBT subbands of the active BWP after X symbols from the last symbol of the CORESET, where the UE detects DCI format 2_0. The value of X symbols may be fixed in the specification or configured by higher layers, mainly considering the processing latency of DCI format 2_0.

[0034] In some embodiments, within the COT duration "K", if a separate DCI format 2_0 is received later, the UE switches to monitoring only the PDCCH candidates on the LBT subband indicated by the separate DCI format 2_0 with a valid LBT subband state (i.e., not the "unknown" state). For example, the UE may receive a subsequent DCI format 2_0 with a valid state for the LBT subband. The valid state indicates an available LBT subband. Therefore, the UE may switch from monitoring PDCCH candidates on all LBT subbands to monitoring PDCCH candidates on only available LBT subbands based on the valid state received at a later time.

[0035] Figure 2 Provides UE implementation Figure 1 1 is an illustration of an example of method 100 of . As shown, the UE receives an available RB set indicator IE 210 with a bitmap 00 indicating an "unknown" state. In addition, the COT duration is a non-zero number. Due to the COT duration and the unknown state, the UE monitors both LBT subbands of the PDCCH (i.e., subband 202 and subband 206). Then, the UE receives a subsequent available RB set indicator IE 212 indicating that available LBT subband 208 is available and LBT subband 204 is unavailable. Therefore, the UE performs subband monitoring on subband 208 but not on LBT subband 204.

[0036] Figure 3 A table 300 is shown detailing the COT structure indication. Table 300 describes the logic that the UE may apply based on the Available RB Set Indicator IE and the COT duration.

[0037] As reference Figure 1 to Figure 2 As described, if the following IE in DCI format 2_0 for the serving cell satisfies the condition in index 2, the UE can skip PDCCH monitoring of the serving cell. In other words, the "Available RB Set Indicator" IE is set to an "unknown" state (e.g., all zeros), and the "COT Duration Indicator" is set to a non-zero value (e.g., K time slots).

[0038] In addition, based on the DCI format 2_0 transmitted on the serving cell, some embodiments may include a solution for indicating the LBT failure state of a given serving cell. Correspondingly, the UE may stop PDCCH monitoring of the serving cell after receiving a notification of the LBT failure state based on the detected DCI format 2_0 transmitted on the serving cell. For example, in some embodiments, if the IE in the DCI format 2_0 for the serving cell satisfies the condition in index 1, the UE may consider that LBT has failed on the serving cell. In other words, the "Available RB Set Indicator" IE is set to an "unknown" state (e.g., all zeros), and the "COT Duration Indicator" is set to a predefined value (e.g., all zeros). In such a case, Figure 3 In some embodiments shown in Index 2 of , the combination of the “Available RB Set Indicator” IE is in the “Unknown” state (e.g., all zeros) and the “COT Duration Indicator” is a predefined non-zero value K used to instruct the UE to skip PDCCH monitoring of the serving cell for a duration of K time slots from the time slot in which DCI format 2_0 is received for energy saving purposes.

[0039] Figure 4 is a flow chart of a method 400 to be performed by a gNB for a COT structure indication using DCI format 2_0. In block 402, the method 400 encodes the DCI format 2_0 included. In block 404, the method 400 COT duration indicator IE. In block 406, the method 400 indicates an available RB set indicator IE of the state of the LBT subband, wherein when there is insufficient time to fully prepare the DCI format 2_0, the available RB set indicator IE is set to an unknown state. In block 408, the method 400 transmits the DCI format 2_0 to the UE.

[0040] Figures 5 to 7 Three methods of determining resource allocation for Msg-3 transmission are shown. Msg-3 is a scheduled PUSCH transmission (Msg3). In some embodiments, if type 1 frequency domain resource allocation is used for the initial BWP on an unlicensed band, then Figures 5 to 7 The method in is used to interpret the 12-bit FDRA field in the RAR PDU.

[0041] Figure 5 Flowchart of a method 500 for determining resource allocation for Msg-3 transmission according to a first embodiment. In this embodiment, the UE uses zero padding to introduce a bit at the MSB of the FDRA field. This embodiment provides sufficient flexibility in the starting position of the allocated resources on the 20MHz initial BWP, but may result in a limitation on the possible length.

[0042] In block 502, method 500 receives a random access response (RAR) grant including a 12-bit frequency domain resource allocation (FDRA) field. In block 504, method 500 determines the resource allocation type. In decision block 506, method 500 checks whether the resource allocation is type 1 or type 2.

[0043] In block 512, method 500 determines that the resource allocation type is Type 1. In block 514, method 500 zero-fills the FDRA field. In block 516, method 500 interprets the 12-bit FDRA with the additional bits from the zero-fill. In block 518, method 500 determines the starting position of transmission Msg-3 of the allocated resources.

[0044] In block 508, method 500 determines that the resource allocation type is type 2. In block 510, when the resource allocation type is type 2, method 500 truncates the FDRA field to determine the resource allocation for Msg-3. In some embodiments, if uplink resource allocation type 2 is used for Msg-3 transmission, then Figure 8 The X least significant bits of the 12-bit FDRA field in the RAR are truncated as shown, and the truncated FDRA field is used to determine the resource allocation for the Msg-3 transmission on the initial BWP. The number of truncated bits can vary based on the SCS. For example, in some embodiments, for a 30kHz SCS, X=5 and for a 15kHz SCS, X=6.

[0045] Figure 6 is a flow chart of a method 600 for determining resource allocation for Msg-3 transmission according to the second embodiment. The resource allocation field is interpreted according to the "virtual" BWP covered by the 12-bit FDRA field. The obtained start and length are then applied to the initial BWP for transmitting Msg-3.

[0046] The virtual BWP is a portion of the bandwidth of the initial BWP available to the UE. For example, the virtual BWP may cover 15MHz of the 20MHz initial BWP. The virtual BWP may be predefined or configured by the UE or gNB. The initial BWP refers to the actual BWP for resource allocation available for Msg-3 transmission.

[0047] In box 602, method 600 receives a random access response (RAR) grant including a 12-bit frequency domain resource allocation (FDRA) field. In box 604, method 600 determines the resource allocation type. In box 612, method 600 determines that the resource allocation type is type 1. In box 614, method 600 interprets the 12-bit FDRA field according to the virtual BWP covered by the 12-bit FDRA field. In box 616, method 600 obtains the starting position and length of the allocated resources associated with the virtual BWP. In box 618, method 600 transmits the Msg-3 transmission on the initial BWP based on the starting position and length of the allocated resources associated with the virtual BWP. For example, in some embodiments, the initial BWP starting position and length are the starting position and length of the allocated resources associated with the virtual BWP.

[0048] In block 608, the method 600 determines that the resource allocation type is type 2. In block 610, when the resource allocation type is type 2, the method 600 truncates the FDRA field to determine the resource allocation for Msg-3. In some embodiments, if uplink resource allocation type 2 is used for Msg-3 transmission, then Figure 8 The X least significant bits of the 12-bit FDRA field in the RAR are truncated as shown, and the truncated FDRA field is used to determine the resource allocation for the Msg-3 transmission on the initial BWP. The number of truncated bits can vary based on the SCS. For example, in some embodiments, for a 30kHz SCS, X=5 and for a 15kHz SCS, X=6.

[0049] Figure 7 is a flow chart of a method 700 for determining resource allocation for Msg-3 transmission according to a third embodiment. In this embodiment, similar to Figure 6 In the method 600, the resource allocation field is interpreted according to the "virtual" BWP covered by the 12-bit FDRA field. In addition, the starting position and length of the obtained resource allocation are interpreted in resource block groups by multiplying by the scaling factor K before applying to the initial BWP. By using a floor operation, the scaling factor can be set to be less than or equal to the bandwidth of the initial BWP divided by the bandwidth of the virtual BWP. For example, the scaling factor can be:

[0050]

[0051] in:

[0052] N 1 is the bandwidth of the initial BWP, and

[0053] N 2 It is a virtual BWP addressed by the 12-bit FDRA field using Type 1 frequency resource allocation.

[0054] In block 702, method 700 receives a random access response (RAR) grant including a 12-bit frequency domain resource allocation (FDRA) field. In block 704, method 700 determines the resource allocation type. In block 712, method 700 determines that the resource allocation type is type 1. In block 714, method 700 interprets the 12-bit FDRA field according to the virtual BWP covered by the 12-bit FDRA field. In block 716, method 700 obtains the starting position and length of the allocated resources associated with the virtual BWP. In block 718, method 700 determines the actual starting position and length by multiplying the obtained starting position and length associated with the virtual BWP by a scaling factor. In block 720, method 700 transmits a Msg-3 transmission at the actual starting position and length on the initial BWP.

[0055] In block 708, method 700 determines that the resource allocation type is type 2. In block 710, when the resource allocation type is type 2, method 700 truncates the FDRA field to determine the resource allocation for Msg-3. In some embodiments, if uplink resource allocation type 2 is used for Msg-3 transmission, then Figure 8 The X least significant bits of the 12-bit FDRA field in the RAR are truncated as shown, and the truncated FDRA field is used to determine the resource allocation for the Msg-3 transmission on the initial BWP. The number of truncated bits can vary based on the SCS. For example, in some embodiments, for a 30kHz SCS, X=5 and for a 15kHz SCS, X=6.

[0056] Figure 8 A truncation of the FDRA field 800 in the RAR determined for Msg-3 resources for a 30 KHz SCS is shown.

[0057] Fig. 9 9 is a flow chart of a method 900 for a gNB. In block 902, the method 900 sets a resource allocation type. In block 904, the method 900 encodes a random access response (RAR) grant including a 12-bit frequency domain resource allocation (FDRA) field. In block 906, the method 900 wherein when the resource allocation type is type 1. In block 908, the method 900 divides the starting position and length of the allocated resources for Msg-3 by a scaling factor associated with a virtual bandwidth part (BWP). In block 910, the method 900 encodes the 12-bit FDRA field with the divided starting position and length of the allocated resources. In block 912, the method 900 transmits the RAR grant to the UE.

[0058] Fig.10Shown is a random access (RA) procedure 1000. The RA procedure may take two different forms: contention-based random access (CBRA) and contention-free random access (CFRA).

[0059] In CBRA, the UE randomly selects a RA preamble from a pool of preambles shared with other UEs in the cell. The UE transmits 1002 a random access preamble (Msg1) 1002 to the gNB. The gNB receives the random access preamble (Msg1) 1002. The gNB transmits a random access response (Msg2) 1012 to the UE. The UE decodes the random access response (Msg2) 1012 content and transmits a scheduled PUSCH transmission (Msg3) (Msg3 is also referred to herein as Msg-3) 1010 to the gNB. In the next step, the gNB transmits a contention resolution (Msg4) 1014 to resolve any contention between UE resource pools.

[0060] In CFRA, the UE uses a dedicated preamble specifically provided to this UE by the network via RRC signaling or PDCCH command. The gNB transmits a random access preamble allocation 1006 to the UE. The UE decodes the random access preamble allocation 1006 and transmits a random access preamble (Msg1) 1004. The gNB receives the random access preamble (Msg1) 1004 and transmits a random access response (Msg2) 1008.

[0061] Exemplary System Architecture

[0062] In certain embodiments, the 5G system architecture supports data connectivity and services, enabling deployment to use technologies such as network function virtualization and software defined networks. The 5G system architecture can utilize service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows independent scalability, evolution, and flexible deployment (e.g., centralized locations or distributed (remote) locations). Modular function design allows functional reuse, and flexible and effective network slicing can be achieved. Network functions and their network function services can interact with another NF and its network function services directly or indirectly via a service communication agent. Another intermediate function can help route control plane messages. The architecture minimizes the dependency between AN and CN. The architecture may include an aggregated core network with a public AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture may also support a unified authentication framework, stateless NFs with decoupling of computing resources from storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, user plane functions may be deployed near the AN), and / or roaming in the visited PLMN with both home-routed traffic as well as local breakout traffic.

[0063] The 5G architecture may be defined as service-based, and the interactions between network functions may include a service-based representation, where a network function (e.g., AMF) within the control plane enables other authorized network functions to access its services. The service-based representation may also include a point-to-point reference point. The reference point representation may also be used to show the interactions between NF services in a network function described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0064] Fig.11 A service-based architecture 1100 in 5GS according to one embodiment is shown. As described in 3GPP TS23.501, the service-based architecture 1100 includes NFs such as NSSF 1102, NEF 1104, NRF 1106, PCF 1108, UDM 1110, AUSF 1112, AMF 1114, and SMF 1116 for communicating with UE 1120, (R)AN 1122, UPF 1124, and DN 1126. NFs and NF services can communicate directly (referred to as direct communication) or indirectly via SCP 1118 (referred to as indirect communication). Fig.11 Also shown are corresponding service-based interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf and Nausf and reference points N1, N2, N3, N4 and N6. Fig.11 Some exemplary functions provided by NF are shown in FIG.

[0065] NSSF 1102 supports functions such as: selecting a set of network slice instances to serve the UE; determining the allowed NSSAIs and, if necessary, determining the mapping to the subscribed S-NSSAI; determining the configured NSSAI and, if necessary, determining the mapping to the subscribed S-NSSAI; and / or determining the set of AMFs to be used to serve the UE, or based on the configuration, possibly determining a list of candidate AMFs by querying the NRF.

[0066] NEF 1104 supports the exposure of capabilities and events. NF capabilities and events can be securely exposed by NEF 1104 (e.g., for 3rd parties, application functions and / or edge computing). NEF 1104 can store / retrieve information as structured data using a standardized interface (Nudr) to UDR. NEF 1104 can also securely provide information to the 3GPP network from external applications, and can provide application functions to securely provide information (e.g., expected UE behavior, 5GLAN group information, and service-specific information) to the 3GPP network, where NEF 1104 can authenticate and authorize and help limit application functions. NEF 1104 can provide internal-external information conversion by converting between information exchanged with AF and information exchanged with internal network functions. For example, NEF 1104 converts between AF service identifiers and internal 5G core information (such as DNN and S-NSSAI). NEF1104 can handle the masking of network and user sensitive information of external AF according to network policy. NEF 1104 may receive information from other network functions (based on the exposed capabilities of other network functions) and store the received information as structured data using a standardized interface to UDR. The stored information may be accessed by NEF 1104 and re-exposed to other network functions and application functions, and used for other purposes such as analysis. For external exposure of services related to a specific UE, NEF 1104 may reside in the HPLMN. Depending on the operator agreement, NEF 1104 in the HPLMN may have an interface with the NF in the VPLMN. SCEF+NEF may be used for service exposure when the UE is able to switch between EPC and 5GC.

[0067] The NRF 1106 supports the service discovery function by receiving NF discovery requests from NF instances or SCPs and providing information of the discovered NF instances to the NF instances or SCPs. The NRF 1106 may also support P-CSCF discovery (a special case of SMF discovery of AFs), maintain NF profiles of available NF instances and their supported services, and / or notify subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances together with their NF services. In the context of network slicing, multiple NRFs may be deployed at different levels, such as PLMN level (NRF configured with information of the entire PLMN), shared slice level (NRF configured with information belonging to a network slice set), and / or slice-specific level (NRF configured with information belonging to S-NSSAI), based on network specific implementation. In the context of roaming, multiple NRFs may be deployed in different networks, wherein the NRF in the visited PLMN (referred to as vNRF) is configured with information of the visited PLMN, and wherein the NRF in the home PLMN (referred to as hNRF) is configured with information of the home PLMN, referenced by the vNRF via the N27 interface.

[0068] The PCF 1108 supports a unified policy framework to govern network behavior. The PCF 1108 provides policy rules for control plane functions to implement them. The PCF 1108 accesses subscription information related to policy decisions in a unified data repository (UDR). The PCF 1108 can access a UDR located in the same PLMN as the PCF.

[0069] The UDM 1110 supports generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI for each subscriber in the 5G system), unhiding of the privacy-preserving subscription identifier (SUCI), access authorization based on subscription data (e.g., roaming restrictions), UE's serving NF registration management (e.g., storing the service AMF for the UE, storing the PDU session storage service SMF for the UE), service / session continuity (e.g., by maintaining SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in outbound roaming situations where the UDM is the only contact point for the LI), subscription management, SMS management, 5G LAN group management processing, and / or external parameter configuration (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM 1110 uses subscription data (including authentication data) that may be stored in the UDR, in which case the UDM implements the application logic and may not require internal user data storage, and several different UDMs may serve the same user in different transactions. The UDM 1110 may be located in the HPLMN of the subscriber it serves and may access information of the UDR located in the same PLMN.

[0070] AF 1128 interacts with the core network to provide services such as supporting: application impact on traffic routing; access to NEF 1104; interaction with the policy framework for policy control; and / or IMS interaction with 5GC. Based on operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions may use an external exposure framework via NEF 1104 to interact with related network functions.

[0071] AUSF 1112 supports authentication for 3GPP access and untrusted non-3GPP access. AUSF 1112 may also provide support for network slice-specific authentication and authorization.

[0072] AMF 1114 supports termination of RAN CP interface (N2), termination of NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interface to LI system), transmission of SM messages between UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transmission of SMS messages between UE and SMSF, SEAF, location service management for regulatory services, transmission of location service messages between UE and LMF and between RAN and LMF, EPS bearer ID allocation for interworking with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, configuration of external parameters (expected UE behavior parameters or network configuration parameters) and / or network slice-specific authentication and authorization. Some or all of the AMF functions may be supported in a single instance of AMF 1114. Regardless of the number of network functions, in some embodiments, only one NAS interface instance per access network between UE and CN terminates at one of the network functions that implements at least NAS security and mobility management. AMF 1114 may also include policy-related functions.

[0073] In addition to the above functions, AMF 1114 may also include the following functions to support non-3GPP access networks: support N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell identity) and procedures (e.g., handover related) defined on 3GPP access may not be applicable, and non-3GPP access specific information not applicable to 3GPP access may be applied; support NAS signaling with UE through N3IWF / TNGF, where some procedures supported by NAS signaling through 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support authentication of UE connected through N3IWF / TNGF; management of mobility, authentication and separate security context states of UE connected via non-3GPP access or via 3GPP access or non-3GPP access at the same time; support coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support dedicated CM management context for UE connected via non-3GPP access. It may not be necessary to support all of the above functions in the instance of network slicing.

[0074] SMF 1116 supports session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where the UE IP address can be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions for responding to address resolution protocol requests and / or IPv6 neighbor solicitation requests based on local cache information of Ethernet PDUs (e.g., SMF responds to ARP and / or IPv6 neighbor solicitation requests by providing a MAC address corresponding to the IP address sent in the request), selection and control of user plane functions (including controlling the UPF to proxy ARP or IPv6 neighbor discovery or forwarding all ARP / IPv6 neighbor solicitation traffic to the SMF for Ethernet PDU sessions), traffic steering configuration at the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the PSA UPFs involved, in the PSA Establish and publish N19 tunnels between UPFs, configure traffic forwarding at UPF to apply local switching and / or N6-based forwarding or N19-based forwarding), terminate interfaces towards policy control functions, lawful interception (for SM events and interfaces to LI systems), charge for data collection and support billing interfaces, control and coordinate billing data collection at UPF, terminate the SM part of NAS messages, downlink data notification, initiator of AN-specific SM information sent to AN via AMF over N2, determination of SSC mode for session, control plane CIoT 5GS optimization, header compression, act as I-SMF in deployments where I-SMF can be inserted / removed / relocated, configure external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local implementation to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN) and / or lawful interception (in VPLMN for SM events and interface to LI system), interaction with external DN to transmit signaling for PDU session authentication / authorization for external DN and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interface. Some or all of the SMF functions may be supported in a single instance of SMF. However, in some embodiments, not all functions need to be supported in an instance of a network slice. In addition to the functions, SMF 1116 may include policy-related functions.

[0075] SCP 1118 includes one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to destination NF / NF service; communication security (e.g., authorization of NF service consumer to access NF service manufacturer API), load balancing, monitoring, overload control, etc.; and / or optionally interacting with UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID / CHF group ID / HSS group ID based on UE identity (e.g., SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported in a single instance of SCP. In some embodiments, SCP 1118 may be deployed in a distributed manner and / or more than one SCP may be present in the communication path between NF services. SCP may be deployed at PLMN level, shared slice level, and slice-specific level. Operator deployment may be left to ensure that SCP can communicate with relevant NRFs.

[0076] UE 1120 may include a device with radio communication capabilities. For example, UE 1120 may include a smart phone (e.g., a handheld touch screen mobile computing device that can be connected to one or more cellular networks). UE 1120 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld device, or any computing device including a wireless communication interface. UE is also referred to as a client, a mobile phone, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio equipment, a reconfigurable radio equipment, or a reconfigurable mobile device. UE 1120 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. IoT UE may utilize technology (e.g., M2M, MTC, or mMTC technology) to exchange data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communication, a sensor network, or an IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0077] UE 1120 may be configured to be connected or communicatively coupled to (R)AN 1122 via a radio interface 1130, which may be a physical communication interface or layer configured to operate with a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, etc. For example, UE 1120 and (R)AN 1122 may use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer. DL transmissions may be from (R)AN 1122 to UE 1120, and UL transmissions may be from UE 1120 to (R)AN 1122. UE 1120 may also communicate directly with another UE (not shown) using a side link for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0078] (R)AN 1122 may include one or more access nodes, which may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, controllers, transmission reception points (TRPs), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations, which provide coverage within a geographic area (e.g., a cell). (R)AN 1122 may include one or more RAN nodes for providing macro cells, pico cells, femto cells, or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access to a UE with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to a UE associated with the femto cell (e.g., a UE in a closed subscriber group (CSG), a UE of a user in a home, etc.).

[0079] Although not shown, multiple RAN nodes (such as (R)AN 1122) may be used, with an Xn interface defined between two or more nodes. 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 UE 1120 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes. The mobility support may include context transfer from an old (source) serving (R)AN node to a new (target) serving (R)AN node; and control of a user plane tunnel between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

[0080] UPF 1124 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 1126, and a branch point to support multi-donor PDU sessions. UPF 1124 may also perform packet routing and forwarding, packet inspection, user plane portion of policy rule enforcement, lawful interception of packets (UP collection); traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 1124 may include an uplink classifier for supporting routing of traffic flows to data networks. DN 1126 may represent various network operator services, Internet access, or third-party services. DN 1126 may include, for example, an application server.

[0081] Fig.12 1 is a block diagram of an exemplary UE 1200 that can be configured according to various embodiments of the present disclosure, including by executing instructions corresponding to any exemplary method and / or process described herein on a computer-readable medium. The UE 1200 includes one or more processors 1202, a transceiver 1204, a memory 1206, a user interface 1208, and a control interface 1210.

[0082] The one or more processors 1202 may include, for example, an application processor, an audio digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 1202 may include an internal memory and / or may include an interface for communicating with an external memory (including memory 1206). The internal or external memory may store software code, programs, and / or instructions for execution by one or more processors 1202 to configure and / or facilitate UE 1200 to perform various operations, including the operations described herein. For example, the execution of the instructions may configure UE 1200 to communicate using one or more wired or wireless communication protocols (including one or more wireless communication protocols standardized by 3GPP, such as those commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc.) or any other current or future protocol that may be used in conjunction with one or more transceivers 1204, user interface 1208, and / or control interface 1210. For another example, the one or more processors 1202 may execute program code stored in the memory 1206 or other memory corresponding to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). For another example, the processor 1202 may execute program code stored in the memory 1206 or other memory, which together with the one or more transceivers 1204 implements corresponding PHY layer protocols, such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0083] The memory 1206 may include a memory area for one or more processors 1202 to store variables used in protocols, configurations, controls, and other functions of the UE 1200 (including operations corresponding to or including any of the exemplary methods and / or processes described herein). In addition, the memory 1206 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. In addition, the memory 1206 may interact with a memory slot through which removable memory cards of one or more formats (e.g., SD card, memory stick, compact flash, etc.) may be inserted and removed.

[0084] One or more transceivers 1204 may include radio frequency transmitter and / or receiver circuits that facilitate UE 1200 to communicate with other equipment supporting similar wireless communication standards and / or protocols. For example, one or more transceivers 1204 may include switches, mixer circuits, amplifier circuits, filter circuits, and synthesizer circuits. Such RF circuits may include a receive signal path having a circuit for down-converting an RF signal received from a front-end module (FEM) and providing a baseband signal to a baseband processor of one or more processors 1202. The RF circuit may also include a transmit signal path, which may include a circuit for up-converting a baseband signal provided by a baseband processor and providing an RF output signal for transmission to the FEM. The FEM may include a receive signal path, which may include a circuit configured to operate on an RF signal received from one or more antennas, amplify the receive signal, and provide an amplified version of the receive signal to the RF circuit for further processing. The FEM may also include a transmit signal path, which may include a circuit configured to amplify a transmit signal provided by the RF circuit for transmission by one or more antennas. In various embodiments, amplification through the transmit or receive signal path may be accomplished in the RF circuitry only, in the FEM only, or in both the RF circuitry and the FEM circuitry. In some embodiments, the FEM circuitry may include a TX / RX switch to switch between transmit mode and receive mode operation.

[0085] In some exemplary embodiments, the one or more transceivers 1204 include transmitters and receivers that enable the device 1200 to communicate with various 5G / NR networks according to various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate in cooperation with the one or more processors 1202 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques, such as described herein with reference to other figures.

[0086] The user interface 1208 may take various forms according to a particular embodiment, or may not be present in the UE 1200. In some embodiments, the user interface 1208 includes a microphone, a speaker, a slidable button, a depressible button, a display, a touch screen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface feature that is typically present on a mobile phone. In other embodiments, the UE 1200 may include a tablet computing device with a larger touch screen display. In such embodiments, one or more mechanical features of the mechanical features of the user interface 1208 may be replaced by a virtual user interface feature (e.g., a virtual keypad, a virtual button, etc.) that is equivalent or functionally equivalent to that implemented using a touch screen display, as is familiar to those of ordinary skill in the art. In other embodiments, the UE 1200 may be a digital computing device, such as a laptop computer, a desktop computer, a workstation, etc., which includes a mechanical keyboard that can be integrated, disassembled, or removable according to a particular exemplary embodiment. Such digital computing devices may also include a touch screen display. Many exemplary embodiments of the UE 1200 with a touch screen display are capable of receiving user input, such as input related to the exemplary methods and / or processes described herein or known to one of ordinary skill in the art.

[0087] In some exemplary embodiments of the present disclosure, UE 1200 includes an orientation sensor that can be used in various ways by the features and functions of UE 1200. For example, UE 1200 can use the output of the orientation sensor to determine when a user has changed the physical orientation of the touch screen display of UE 1200. The indication signal from the orientation sensor can be used for any application executed on UE 1200, so that the application can automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. In this way, regardless of the physical orientation of the device, the application can maintain the screen display in a user-readable manner. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.

[0088] The control interface 1210 can take various forms depending on the particular implementation. For example, the control interface 1210 can include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I 2 C interface, PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface, such as described above. In some exemplary embodiments of the present disclosure, the control interface 1210 may include an analog interface circuit, which includes, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0089] Those skilled in the art will recognize that the above list of features, interfaces, and radio frequency communication standards is merely exemplary and does not limit the scope of the present disclosure. Fig.12 1200, including, for example, video and / or still image cameras, microphones, media players and / or recorders, etc. In addition, the one or more transceivers 1204 may include circuits for communicating using additional radio frequency communication standards including Bluetooth, GPS and / or others. In addition, the one or more processors 1202 may execute software code stored in the memory 1206 to control such additional functions. For example, the directional speed and / or position estimate output from the GPS receiver may be used for any application executed on the UE 1200, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of the present disclosure.

[0090] Fig.13 is a block diagram of an exemplary network node 1300 that may be configured according to various embodiments of the present disclosure, including by executing instructions on a computer-readable medium corresponding to any of the exemplary methods and / or processes described herein.

[0091] The network node 1300 includes one or more processors 1302, a radio network interface 1304, a memory 1306, a core network interface 1310, and other interfaces 1308. The network node 1300 may include, for example, a base station, an eNB, a gNB, an access node, or a component of a network node.

[0092] The one or more processors 1302 may include any type of processor or processing circuit, and may be configured to perform one of the methods or processes disclosed herein. The memory 1306 may store software codes, programs and / or instructions executed by the one or more processors 1302 to configure the network node 1300 to perform various operations, including the operations described herein. For example, the execution of such stored instructions may configure the network node 1300 to communicate with one or more other devices using protocols according to various embodiments of the present disclosure (including one or more methods and / or processes discussed above). In addition, the execution of such stored instructions may also configure and / or facilitate the network node 1300 to communicate with one or more other devices using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP and RRC layer protocols standardized by 3GPP for LTE, LTE-A and / or NR or any other higher layer protocol used in combination with the radio network interface 1304 and the core network interface 1310). By way of example and not limitation, the core network interface 1310 includes an S1 interface, and the radio network interface 1304 may include a Uu interface, such as standardized by 3GPP. The memory 1306 may also store variables used in protocols, configuration, control, and other functions of the network node 1300. Thus, the memory 1306 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof.

[0093] The radio network interface 1304 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuits that enable the network node 1300 to communicate with other equipment (in some embodiments, such as multiple compatible user equipment (UE)). In some embodiments, the network node 1300 may include various protocols or protocol layers, such as PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to other embodiments of the present disclosure, the radio network interface 1304 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technology. In some embodiments, the functionality of such a PHY layer may be provided collaboratively by the radio network interface 1304 and one or more processors 1302.

[0094] The core network interface 1310 may include a transmitter, a receiver, and other circuits that enable the network node 1300 to communicate with other equipment in the core network (in some embodiments, such as circuit switching (CS) and / or packet switching core (PS) networks). In some embodiments, the core network interface 1310 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 1310 may include one or more interfaces to one or more SGWs, MMEs, SGSNs, GGSNs, and other physical devices, including functions known to those of ordinary skill in the art that exist in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 1310 may include one or more of asynchronous transfer mode (ATM), Internet Protocol (IP) on Ethernet, SDH on optical fiber, T1 / E1 / PDH on copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

[0095] Other interfaces 1308 may include transmitters, receivers, and other circuits that enable network node 1300 to communicate with external networks, computers, databases, etc., for operation, management, and maintenance of network node 1300 or other network equipment operably connected to the network node.

[0096] 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 examples 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 examples. 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 examples shown in the examples section below.

[0097] Examples

[0098] The following examples relate to additional embodiments.

[0099] Embodiment 1 may include an apparatus comprising means for performing one or more elements of a method as described in or in connection with any of the methods or processes described herein.

[0100] Embodiment 2 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 of the above embodiments or any other method or process described herein.

[0101] Embodiment 3 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

[0102] Embodiment 4 may include any of the methods, techniques or processes described in or related to the above embodiments, or parts or components thereof.

[0103] Embodiment 5 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, process, or portion thereof described in or related to any one of the above embodiments.

[0104] Embodiment 6 may include signals or parts or components thereof as described in or related to any one of the above embodiments.

[0105] Embodiment 7 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0106] Embodiment 8 may include a signal encoded with data or a portion or component thereof as described in or related to any of the above embodiments, or described in other ways in this disclosure.

[0107] Embodiment 9 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0108] Embodiment 10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described in or related to any of the above embodiments.

[0109] Embodiment 11 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process or a portion thereof described in or related to any one of the above embodiments.

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

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

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

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

[0114] 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 obtained from the practice of the various embodiments.

[0115] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0116] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0117] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0118] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for operation of a user equipment (UE) in an unlicensed spectrum, the method comprising: receiving a random access response RAR grant including a 12-bit frequency domain resource allocation FDRA field; determining a resource allocation type of the allocated resources of the 12-bit FDRA field, wherein when the allocated resources are allocated to one or more consecutive resource blocks using two configuration parameters including a starting resource block index and a number of consecutive RBs, the resource allocation type is a type 1 resource allocation, and when the allocated resources are allocated to one or more interlaces and each interlace includes a group of physical resource blocks, the resource allocation type is a type 2 resource allocation; as well as When the resource allocation type is type 1 and the allocated resources are on a 20 MHz initial bandwidth part BWP on an unlicensed band: zero-padding the 12-bit FDRA field, wherein the zero-padding comprises introducing a bit at a most significant bit (MSB) of the 12-bit FDRA field; and A starting position of the allocated resources, where a scheduled Physical Uplink Shared Channel (PUSCH) transmission is to be transmitted in the unlicensed spectrum, is determined based on the 12-bit FDRA field and the additional MSBs according to the zero padding.

2. The method of claim 1 , further comprising truncating the 12-bit FDRA field to determine resource allocation for a scheduled PUSCH transmission when the resource allocation type is type 2.

3. The method of claim 2, wherein the five least significant bits (LSBs) of the 12-bit FDRA field are truncated for a 30 kHz subcarrier spacing (SCS). 4 . The method of claim 2 , wherein six LSBs of the 12-bit FDRA field are truncated for a 15 kHz SCS.

5. A device for a UE, comprising: A memory interface, the memory interface being used to access a random access response RAR grant including a 12-bit frequency domain resource allocation FDRA field; A baseband processing unit, the baseband processing unit is coupled to the memory interface, the baseband processing unit: receiving a first bandwidth configuration corresponding to the virtual BWP, Decoding the RAR authorization; determining a resource allocation type of the allocated resources of the 12-bit FDRA field, wherein when the allocated resources are allocated to one or more consecutive resource blocks using two configuration parameters including a starting resource block index and a number of consecutive RBs, the resource allocation type is a type 1 resource allocation, and when the allocated resources are allocated to one or more interlaces and each interlace includes a group of physical resource blocks, the resource allocation type is a type 2 resource allocation; as well as When the resource allocation type is type 1 and the allocated resources are on a 20 MHz initial bandwidth part BWP on an unlicensed frequency band, interpreting the 12-bit FDRA field according to the virtual bandwidth portion BWP covered by the 12-bit FDRA field, Obtaining the starting position and length of the allocated resources associated with the virtual BWP; The scaling factor K is determined by: wherein N1 is a second bandwidth corresponding to an initial BWP in an unlicensed spectrum, and N2 is the first bandwidth corresponding to the virtual BWP addressed by the 12-bit FDRA field using a Type 1 frequency resource allocation; multiplying the obtained starting position and length associated with the virtual BWP by a scaling factor K to obtain the starting position and length of the initial BWP; and A scheduled physical uplink shared channel (PUSCH) transmission is transmitted on the initial BWP of the unlicensed spectrum based on the starting position and the length of the initial BWP.

6. The apparatus of claim 5, wherein the virtual BWP comprises a portion of a bandwidth available to the initial BWP for the UE. 7 . The apparatus of claim 6 , wherein the scaling factor is less than or equal to a bandwidth of the initial BWP divided by a bandwidth of the virtual BWP.

8. The apparatus of claim 5, wherein the baseband processing unit further truncates the 12-bit FDRA field to determine resource allocation for the scheduled PUSCH transmission when the resource allocation type is type 2.

9. A method for operation of a next generation NodeB, gNB, in an unlicensed spectrum, the method comprising: Set the resource allocation type of the allocated resources of the 12-bit frequency domain resource allocation FDRA field, wherein when the allocated resources are allocated to one or more consecutive resource blocks using two configuration parameters including a starting resource block index and a number of consecutive RBs, the resource allocation type is a type 1 resource allocation, and when the allocated resources are allocated to one or more interlaces and each interlace includes a set of physical resource blocks, the resource allocation type is a type 2 resource allocation; encoding a random access response RAR grant including the 12-bit FDRA field, wherein when the resource allocation type is the type 1, configuring a first bandwidth corresponding to the virtual BWP; The scaling factor K is determined by: wherein N1 is a second bandwidth corresponding to an initial BWP in an unlicensed spectrum, and N2 is the first bandwidth corresponding to the virtual BWP addressed by the 12-bit FDRA field using a Type 1 frequency resource allocation; dividing the starting position and length of the allocated resources for the scheduled physical uplink shared channel (PUSCH) transmission by the scaling factor; as well as encoding the 12-bit FDRA field with the divided starting position and length of the allocated resources; as well as The RAR grant is transmitted to the UE.

10. The method of claim 9, wherein the virtual BWP comprises a portion of a bandwidth available for an initial BWP of the gNB.

11. The method of claim 9, wherein the scaling factor is set to be less than or equal to a bandwidth of an initial BWP divided by a bandwidth of the virtual BWP by using a round-down operation.

12. The method of claim 9, further comprising transmitting the scheduled PUSCH transmission according to the starting position and length of allocated resources.

13. The method of claim 9, wherein the RAR authorization is transmitted outside of the virtual BWP.

14. The method of claim 9, wherein when the resource allocation type is type 2, the 12-bit FDRA field is encoded such that five or six LSBs can be truncated by the UE to determine the resource allocation for the scheduled PUSCH transmission.

Images