Systems, methods, and apparatus, including computer programs, for resource determination for wireless communication

Abstract

A method for a user equipment (UE) that can detect a downlink control information (DCI) format 2_0 is disclosed. The DCI format 2_0 can include an available resource block (RB) set indicator information element (IE) that indicates a status of a listen-before-talk (LBT) subband and a channel occupancy time (COT) duration indicator IE. When there is insufficient time to fully prepare the DCI format 2_0, the available RB set indicator is set to an unknown status.

Description

Technical Field

[0001] This application relates generally to wireless communication systems, and more specifically to the determination of resources for new air interfaces. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include 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, commonly referred to by the industry organization as WiMAX; and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In the fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes and NR nodes (also known as next-generation node B or g NodeB (gNB)).

[0003] The RAN uses Radio Access Technology (RAT) to communicate between RAN nodes and UEs. The RAN can include Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provides access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal System for Mobile Communications (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT, and NG-RAN implements the 5G RAT. In some deployments, E-UTRAN may also implement the 5G RAT.

[0004] 5G NR frequency bands can be divided into two distinct frequency ranges. Frequency range 1 (FR1) includes bands below 6 GHz, some of which may be used by previous standards but could potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency range 2 (FR2) includes bands from 24.25 GHz to 52.6 GHz. The millimeter wave (mmWave) bands in FR2 have a shorter range but higher available bandwidth than those in FR1. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may vary over time or in different regions. Attached Figure Description

[0005] To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0006] Figure 1 It is a flowchart of a method that will be performed by the UE in response to the COT structure according to an implementation plan.

[0007] Figure 2 Provides a UE implementation based on an implementation scheme. Figure 1 An illustration of an example of the method.

[0008] Figure 3 A table detailing the COT structure indications according to one implementation scheme is shown.

[0009] Figure 4 This is a flowchart of a method to be performed by gNB for a COT structure using DCI format 2_0, according to an implementation plan.

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

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

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

[0013] Figure 8 The truncation of the FDRA field is shown according to one implementation scheme.

[0014] Figure 9 This is a flowchart of a method for gNB according to an implementation plan.

[0015] Figure 10 The random access (RA) procedure is illustrated.

[0016] Figure 11 An exemplary service-based architecture according to certain implementation schemes is shown.

[0017] Figure 12 A UE according to one implementation is shown.

[0018] Figure 13 A network node according to one implementation scheme is shown. Detailed Implementation

[0019] The New Radio (NR) interface for operation in unlicensed spectrum (NR-U) has incorporated several enhancements related to resources between User Equipment (UE) and Next-Generation NodeBs (gNBs). While these enhancements are beneficial, they may also introduce overlooked problems. Therefore, several new approaches should be adopted to determine the resources available for wireless communication in order to address these overlooked problems.

[0020] For NR-U operation, the Downlink Control Information (DCI) format 2_0 will be enhanced to provide a Channel Occupied Time (COT) structure to facilitate UE decisions regarding delaying Physical Downlink Control Channel (PDCCH) monitoring or Periodic CSI Reference Signal (CSI-RS) detection. This change to DCI format 2_0 may result in lower power consumption on the UE side. Additionally, the UE can be configured to have up to 64 values ​​for the COT duration in symbols based on the Reference Subcarrier Spacing (SCS). Furthermore, a bitmap will be added to DCI format 2_0 to indicate available LBT bandwidth.

[0021] Additional enhancements to DCI Format 2_0 may include transmitting an "unknown" state to indicate the LBT results of some LBT subbands. As an example, an "unknown" state of an LBT subband may occur at the start of a COT initiated by a gNB, where the gNB completes its LBT operation very late and does not have sufficient time to prepare DCI Format 2_0 to indicate the actual availability of the LBT subbands of the captured COT based on the LBT results. Some implementations described herein provide a way to signal the "unknown" state of an LBT subband within a broadband BWP. Additionally, some implementations describe how to indicate an LBT failure in a given serving cell that has been configured with the Slot Format Indication (SFI) index field in DCI Format 2_0.

[0022] Furthermore, for NR-U operation, two bits of the Frequency Domain Resource Allocation (FDRA) field in the uplink (UL) grant of the Random Access Response (RAR) Medium Access Control (MAC) Protocol Data Unit (PDU) are reused to indicate the channel access parameters for CP extension. The number of bits in the Frequency Domain Resource Allocation (FDRA) field 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 full Resource Block (RB) range of the initial 20MHz UL bandwidth portion (BWP) (e.g., 107 Physical Resource Blocks (PRBs) for a 15kHz SCS and 51 PRBs for a 30kHz SCS) should be 13 bits for 15kHz. However, for interleaved Resource Allocation Type 2, the requested FDRA field size will be 6 bits for a 15kHz SCS and 5 bits for a 30kHz SCS. Some implementations described in this paper describe how to interpret the 12-bit FDRA field in the RAR MAC PDU for resource allocation on an initial 20MHz BWP to properly address the Msg-3 transmission in 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 using two configuration parameters—the starting RB index and the number of consecutive RBs. Additionally, the resource allocation granularity is one RB.

[0024] In Type 2 resource allocation, resources are allocated to one or more interleavings, and each interleaving consists of a set of PRBs. Furthermore, the resource allocation granularity is one interleaving.

[0025] The various operations will be described sequentially as a plurality of discrete operations in a manner most conducive to understanding this disclosure. However, the order of description should not be construed as implying that these operations necessarily depend on a specific order. In particular, these operations do not necessarily need to be performed in the order of presentation.

[0026] Additional details and examples are provided with reference to the following accompanying drawings. Embodiments of this disclosure can be understood with reference to the drawings, wherein similar components are consistently represented by similar numbers. Components of the embodiments of the invention disclosed herein, as generally described and illustrated in the accompanying drawings, can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of embodiments of the systems and methods of this disclosure is not intended to limit the scope of this disclosure as protected by the claims, but rather represents only possible embodiments.

[0027] Figure 1 This is a flowchart of a method 100, which is to be performed by the UE according to some implementation schemes, for receiving COT structure indications using DCI format 2_0 and monitoring the PDCCH within the corresponding COT.

[0028] In decision box 102, method 100 attempts to detect DCI format 2_0 from the gNB during a monitoring opportunity. DCI format 2_0 includes an RB set indicator information element (IE) indicating the state of the Listen-Before-Speak (LBT) subband and a COT duration indicator IE. If the UE does not detect DCI format 2_0 during the monitoring opportunity, method 100 repeats decision box 102 during the next monitoring opportunity 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 specific state of the available RB set indicator IE can be predefined to indicate the "unknown" state of the LBT subband within the active BWP on the corresponding serving cell. For example, the unknown state can be indicated by an available RB set indicator IE that is set to either all zeros or all one. In some embodiments, the available RB set indicator IE "b1b0" is set to 00, 10 to indicate the "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 an unknown state, method 100 proceeds to box 108. In box 108, method 100 begins monitoring all PDCCH candidates configured by DCI format 2_0 on the indicated LBT subband.

[0031] When the UE detects that it has received an "unknown" state of 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 implementations, the UE may implicitly assume an LBT subband where it detects DCI format 2_0 with an unknown state (e.g., all zeros or all one) available and only monitors PDCCH candidates on it. (See reference) Figure 2 Using this alternative method, the UE will only assume that LBT subband #0 is available and monitor PDCCH candidates on that subband. In other words, the UE will not monitor... Figure 2 PDCCH candidate on LBT subband #1.

[0033] In box 106, the method begins monitoring all PDCCH candidates configured on all LBT subbands of the active BWP X symbols after the last symbol of CORESET, where the UE detects DCI format 2_0. The value of X symbols can be fixed in the specification or configured by higher layers, primarily considering the processing wait time of DCI format 2_0.

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

[0035] Figure 2 Provided UE implementation Figure 1 An illustration of an example of method 100 is provided. As shown, the UE receives an available RB set indicator IE 210 with a bitmap 00 indicating an "unknown" state. Additionally, 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). The UE then 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 for subband 208 but not for LBT subband 204.

[0036] Figure 3 Table 300 details the COT structure indication. Table 300 describes the logic that the UE can apply based on the available RB set indicator IE and the COT duration.

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

[0038] Additionally, based on DCI format 2_0 transmitted on the serving cell, some implementations 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 an LBT failure state notification based on the detected DCI format 2_0 transmitted on the serving cell. For example, in some implementations, the UE may consider the LBT to have failed on the serving cell if the IE in the DCI format 2_0 for the serving cell satisfies the condition in index 1. In other words, the "Available RB Set Indicator" IE is set to an "Unknown" state (e.g., all zero), and the "COT Duration Indicator" is set to a predefined value (e.g., all zero). Figure 3 In some implementations shown in Index 2, the combination of the "Available RB Set Indicator" IE is an "Unknown" state (e.g., all zero) and the "COT Duration Indicator" is a predefined non-zero value K used to indicate that the UE skips PDCCH monitoring of the serving cell for a duration of K time slots from the time slot of receiving DCI format 2_0 for energy saving purposes.

[0039] Figure 4 This is a flowchart of method 400, executed by the gNB for a COT structure indication using DCI format 2_0. In block 402, method 400 encodes the included DCI format 2_0. In block 404, method 400 defines the COT duration indicator IE. In block 406, method 400 defines the available RB set indicator IE indicating the state of the LBT subband, wherein if 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, method 400 transmits the DCI format 2_0 to the UE.

[0040] Figures 5 to 7 Three methods for determining resource allocation for Msg-3 transmissions are illustrated. Msg-3 is a scheduled PUSCH transmission (Msg3). In some implementations, if type 1 frequency domain resource allocation is used for an initial BWP on an unlicensed frequency band, this can be considered. Figures 5 to 7 The method described is used to decode the 12-bit FDRA field in a RAR PDU.

[0041] Figure 5 This is a 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 allocated resources on a 20MHz initial BWP, but may result in limitations on the possible length.

[0042] In box 502, method 500 receives a Random Access Response (RAR) grant including a 12-bit Frequency Domain Resource Allocation (FDRA) field. In box 504, method 500 determines the resource allocation type. In decision box 506, method 500 checks whether the resource allocation is type 1 or type 2.

[0043] In box 512, method 500 determines that the resource allocation type is type 1. In box 514, method 500 zero-padding the FDRA field. In box 516, method 500 interprets the 12-bit FDRA using additional bits from the zero-padding. In box 518, method 500 determines the starting position of the transmission Msg-3 for the allocated resource.

[0044] In box 508, method 500 determines that the resource allocation type is type 2. In box 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 implementations, if uplink resource allocation type 2 is used for Msg-3 transmission, then as follows... Figure 8 The diagram shows the truncating of X least significant bits of the 12-bit FDRA field in the RAR, and the truncated FDRA field is used to determine the resource allocation for Msg-3 transmission on the initial BWP. The number of truncated bits can be varied based on the SCS. For example, in some implementations, X = 5 for a 30kHz SCS and X = 6 for a 15kHz SCS.

[0045] Figure 6 This is a flowchart of a method 600 for determining resource allocation for Msg-3 transmission according to a second embodiment. The resource allocation field is interpreted based on a “virtual” BWP overlaid by a 12-bit FDRA field. The obtained start and length are then applied to the initial BWP for transmitting Msg-3.

[0046] A virtual BWP is a portion of the bandwidth of the initial BWP available to the UE. For example, a virtual BWP can cover 15MHz of a 20MHz initial BWP. Virtual BWPs can be predefined or configured by the UE or gNB. The initial BWP refers to the actual BWP allocated for resource usage in Msg-3 transmissions.

[0047] In block 602, method 600 receives a Random Access Response (RAR) grant including a 12-bit Frequency Domain Resource Allocation (FDRA) field. In block 604, method 600 determines the resource allocation type. In block 612, method 600 determines that the resource allocation type is type 1. In block 614, method 600 interprets the 12-bit FDRA field based on the virtual BWP covered by the 12-bit FDRA field. In block 616, method 600 obtains the start position and length of the allocated resources associated with the virtual BWP. In block 618, method 600 transmits Msg-3 transmissions on the initial BWP based on the start position and length of the allocated resources associated with the virtual BWP. For example, in some embodiments, the start position and length of the initial BWP are the start position and length of the allocated resources associated with the virtual BWP.

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

[0049] Figure 7 This is a flowchart of a method 700 for determining resource allocation for Msg-3 transmission according to a third embodiment. In this embodiment, similar to... Figure 6 Method 600 interprets the resource allocation field based on the "virtual" BWP overlaid by the 12-bit FDRA field. Additionally, the starting position and length of the obtained resource allocation are interpreted as resource block groups by multiplying by a scaling factor K before being applied to the initial BWP. 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 using a floor operation. For example, the scaling factor could be:

[0050]

[0051] in:

[0052] N1 is the bandwidth of the initial BWP, and

[0053] N2 is a virtual BWP addressed using type 1 frequency resource allocation with a 12-bit FDRA field.

[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 based on 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 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 implementations, if uplink resource allocation type 2 is used for Msg-3 transmission, then as follows... Figure 8 The diagram shows the truncating of X least significant bits of the 12-bit FDRA field in the RAR, and the truncated FDRA field is used to determine the resource allocation for Msg-3 transmission on the initial BWP. The number of truncated bits can be varied based on the SCS. For example, in some implementations, X = 5 for a 30kHz SCS and X = 6 for a 15kHz SCS.

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

[0057] Figure 9 This is a flowchart of method 900 for gNB. In block 902, method 900 sets the resource allocation type. In block 904, method 900 encodes the Random Access Response (RAR) grant, including the 12-bit Frequency Domain Resource Allocation (FDRA) field. In block 906, method 900, where the resource allocation type is type 1. In block 908, method 900 divides the start position and length of the allocated resources for Msg-3 by a scaling factor associated with the Virtual Bandwidth Part (BWP). In block 910, method 900 encodes the 12-bit FDRA field with the divided start position and length of the allocated resources. In block 912, method 900 transmits the RAR grant to the UE.

[0058] Figure 10The random access (RA) procedure 1000 is illustrated. The RA procedure can take two different forms: contention-based random access (CBRA) and contention-free random access (CFRA).

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

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

[0061] Exemplary System Architecture

[0062] In some implementations, the 5G system architecture supports data connectivity and services, enabling deployment using technologies such as network function virtualization and software-defined networking. The 5G system architecture can leverage service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows for independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) locations). Modular function design allows for function reuse and enables flexible and efficient network slicing. Network functions and their network function services can interact directly or indirectly with another NF and its network function services via a service communication broker. Another intermediate function helps route control plane messages. This architecture minimizes dependencies between the AN and CN. The architecture may include an aggregated core network with a common AN-CN interface integrating different access types (e.g., 3GPP access and non-3GPP access). The architecture also supports a unified authentication framework, stateless NFs that decouple compute and storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, with user plane functions deployed near the AN), and / or roaming in the visited PLMN using both home-routed traffic and local breakout traffic.

[0063] A 5G architecture can be defined as service-based, and interactions between network functions can include service-based representations, where a network function within the control plane (e.g., an AMF) enables other authorized network functions to access its services. Service-based representations can also include point-to-point reference points. Reference point representations can also be used to illustrate interactions between NF services within network functions described by point-to-point reference points (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0064] Figure 11 A service-based architecture 1100 in 5GS according to one implementation 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). Figure 11 It also shows the corresponding service-based interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf, and Nausf, as well as reference points N1, N2, N3, N4, and N6. The following describes the... Figure 11 Some exemplary functions provided by NF are shown in the figure.

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

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

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

[0068] PCF 1108 supports a unified policy framework for managing network behavior. PCF 1108 provides policy rules for control plane functions to enforce them. PCF 1108 accesses subscription information related to policy decisions in the Unified Data Repository (UDR). PCF 1108 can access the UDR located in the same PLMN as PCF.

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

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

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

[0072] AMF 1114 supports the termination of the RAN CP interface (N2), the termination of the NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interfaces to the LI system), transmission of SM messages between the UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transmission of SMS messages between the UE and SMSF, SEAF, location service management for regulated services, transmission of location service messages between the UE and LMF and between the RAN and LMF, EPS bearer ID allocation for interoperability 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 can be supported in a single instance of AMF 1114. Regardless of the number of network functions, in some implementations, only one NAS interface instance per access network between the UE and the CN terminates with 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 functions described above, AMF 1114 may also include the following functions supporting non-3GPP access networks: support for the N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell identifier) ​​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 can be applied; support for NAS signaling by UE via N3IWF / TNGF, where some procedures supported by NAS signaling on 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support for authentication of UEs connected via N3IWF / TNGF; management of mobility, authentication, and separate security context states for UEs connected via non-3GPP access or simultaneously via 3GPP access or non-3GPP access; support for effective coordination of RM management contexts on both 3GPP and non-3GPP access; and / or support for dedicated CM management contexts for UEs connecting via non-3GPP access. Support for all of the above functions may not be required in network slicing instances.

[0074] SMF 1116 supports session management (e.g., session establishment, modification, and publication, including tunnel maintenance between UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where UE IP addresses can be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, the ability to respond to Address Resolution Protocol (ARP) requests and / or IPv6 neighbor request requests with local cached information based on Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 neighbor request requests by providing the 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 request traffic to the SMF for Ethernet PDU sessions), traffic-directing configuration at the UPF to route traffic to the appropriate destination, and 5G VN group management (e.g., maintaining the topology of the involved PSA UPF, in the PSA...). Establish and publish N19 tunnels between UPFs, configure traffic forwarding at the UPF to apply local handover, and / or N6-based or N19-based forwarding, terminate the interface for policy control functions, lawful interception (for SM events and interfaces to the LI system), charge for data collection and support the billing interface, control and coordinate billing data collection at the UPF, terminate the SM portion of NAS messages, downlink data notification, initiator of AN-specific SM information sent to the AN via the AMF through N2, determination of the SSC mode of the session, control plane CIoT 5GS optimization, header compression, act as an I-SMF in the deployment of insertable / removable / repositionable I-SMFs, 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 the VPLMN for SM events and interfaces to LI systems), interaction with external DNs to transmit signaling for PDU session authentication / authorization for external DNs and / or instructing UPF and NG-RAN to perform redundant transmissions on N3 / N9 interfaces. Some or all of the SMF functions may be supported in a single instance of the SMF. However, in some implementations, not all functions need to be supported in instances of network slices. In addition to functionality, 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 the destination NF / NF service; communication security (e.g., authorization for NF service consumers to access NF service manufacturer APIs), load balancing, monitoring, overload control, etc.; and / or optionally interacting with a 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 the SCP. In some implementations, SCP 1118 may be deployed in a distributed manner and / or more than one SCP may exist in the communication path between NF services. SCPs may be deployed at the PLMN level, shared slice level, and slice-specific level. Carrier deployments may be left to ensure that the SCP can communicate with the relevant NRF.

[0076] UE 1120 may include devices with radio communication capabilities. For example, UE 1120 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect 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), pager, laptop computer, desktop computer, wireless handheld device, or any computing device that includes a wireless communication interface. UE is also 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, or reconfigurable mobile device. UE 1120 may include an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may 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 using technologies such as M2M, MTC, or mMTC. M2M or MTC data exchange may be machine-initiated data exchange. An IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0077] UE 1120 can be configured to connect or communicatively couple with (R)AN 1122 via radio interface 1130. This radio interface can be a physical communication interface or layer configured to operate using cellular communication protocols such as GSM, CDMA network protocols, keyless to reach (PTT), cellular PTT (POC), UMTS, 3GPP LTE, 5G, NR, etc. For example, UE 1120 and (R)AN 1122 can use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including PHY, MAC, RLC, PDCP, and RRC layers. DL transmissions can be made from (R)AN 1122 to UE 1120, and UL transmissions can be made from UE 1120 to (R)AN 1122. UE 1120 can also use a sidelink to communicate directly with another UE (not shown) for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to the Physical Side Link Control Channel (PSCCH), Physical Side Link Shared Channel (PSSCH), Physical Side Link Discovery Channel (PSDCH), and Physical Side Link Broadcast Channel (PSBCH).

[0078] (R)AN 1122 may include one or more access nodes, which may be referred to as a base station (BS), NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), RAN node, controller, transport receiving point (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). (R)AN 1122 may include one or more RAN nodes for providing coverage of macrocells, picocells, femtocells, or other types of cells. Macrocells may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow UEs to have unrestricted access with a service subscription. Picocells may cover a relatively small geographic area and may allow UEs to have unrestricted access with a service subscription. Femtocells may cover a relatively small geographic area (e.g., a home) and may allow restricted access for UEs associated with a femtocell (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 Xn interfaces 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. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 1120 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more (R)AN nodes. This mobility support may include context transfer from the old (source) serving (R)AN node to the new (target) serving (R)AN node; and control of user plane tunnels between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

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

[0081] Figure 12 This is a block diagram of a configurable exemplary UE 1200 according to various embodiments of the present disclosure, including instructions executed on a computer-readable medium corresponding to any of the exemplary methods and / or processes described herein. UE 1200 includes one or more processors 1202, transceiver 1204, memory 1206, user interface 1208, and 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 internal memory and / or may include an interface for communicating with external memory (including memory 1206). The internal or external memory may store software code, programs, and / or instructions executable by the one or more processors 1202 to configure and / or facilitate the UE 1200 to perform various operations, including those described herein. For example, the execution of instructions may configure the 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 protocols that can be used in conjunction with one or more transceivers 1204, user interface 1208, and / or control interface 1210. For example, one or more processors 1202 may execute program code stored in 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). Alternatively, processor 1202 may execute program code stored in memory 1206 or other memory that, together with the one or more transceivers 1204, implements the corresponding PHY layer protocol, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

[0083] Memory 1206 may include memory regions for one or more processors 1202 to store variables used in the protocols, configurations, controls, and other functions of UE 1200 (including operations corresponding to or including any of the exemplary methods and / or processes described herein). Furthermore, memory 1206 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or combinations thereof. Additionally, memory 1206 may interact with memory time slots through which one or more removable memory cards of various formats (e.g., SD cards, Memory Sticks, Compact Flash, etc.) can be inserted and removed.

[0084] One or more transceivers 1204 may include radio frequency transmitter and / or receiver circuitry that facilitates communication between the UE 1200 and other equipment supporting similar wireless communication standards and / or protocols. For example, one or more transceivers 1204 may include switches, mixer circuitry, amplifier circuitry, filter circuitry, and synthesizer circuitry. Such RF circuitry may include a receive signal path having circuitry for down-converting RF signals received from a front-end module (FEM) and providing baseband signals to one or more processors 1202. The RF circuitry may also include a transmit signal path that may include circuitry for up-converting the baseband signals provided by the baseband processor and providing an RF output signal for transmission to the FEM. The FEM may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry for further processing. The FEM may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry for transmission by one or more antennas. In various implementations, amplification along the transmit or receive signal path can be performed only in the RF circuitry, only in the FEM, or in both the RF and FEM circuitries. In some implementations, the FEM circuitry may include a TX / RX switch to switch between transmit 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 cooperatively with one or more processors 1202 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies, as described herein with reference to other figures.

[0086] User interface 1208 may take various forms depending on the specific implementation, or may not be present in UE 1200. In some implementations, user interface 1208 includes a microphone, speaker, slide button, pressable button, display, touchscreen display, mechanical or virtual keypad, mechanical or virtual keyboard, and / or any other user interface features typically present on a mobile phone. In other implementations, UE 1200 may include a tablet computing device with a large touchscreen display. In such implementations, one or more mechanical features of user interface 1208 may be replaced by equivalent or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as is well known to those skilled in the art. In other implementations, UE 1200 may be a digital computing device, such as a laptop computer, desktop computer, workstation, etc., which includes a mechanical keyboard that can be integrated, detached, or removable according to a particular exemplary implementation. Such digital computing devices may also include a touchscreen display. Many exemplary embodiments of the UE 1200 with a touchscreen display are capable of receiving user input, such as input related to exemplary methods and / or processes described herein or known to those skilled in the art.

[0087] In some exemplary embodiments of this disclosure, UE 1200 includes an orientation sensor that can be used in various ways by 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 touchscreen display of UE 1200. An indication signal from the orientation sensor can be used by any application executing on UE 1200 to automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates a change of approximately 90 degrees in the physical orientation of the device. Thus, the application is able to maintain the screen display in a user-readable manner regardless of the physical orientation of the device. Additionally, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of this disclosure.

[0088] The control interface 1210 may take various forms depending on the specific implementation. For example, the control interface 1210 may include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“FireWire”) interface, and an I / O interface. 2 Interfaces include C-type interfaces, PCMCIA interfaces, etc. In some exemplary embodiments of this disclosure, control interface 1260 may include an IEEE 802.3 Ethernet interface, as described above. In some embodiments of this disclosure, control interface 1210 may include analog interface circuitry, including, 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 list of features, interfaces, and radio frequency communication standards above is merely exemplary and not limited to the scope of this disclosure. In other words, UE 1200 may include more than Figure 12 Further functionalities are shown, including, for example, a video and / or still image camera, microphone, media player, and / or recorder. Additionally, the one or more transceivers 1204 may include circuitry for communicating using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, one or more processors 1202 may execute software code stored in memory 1206 to control such additional functionalities. For example, directional velocity and / or position estimates output from a GPS receiver can be used by any application executing on the UE 1200, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of this disclosure.

[0090] Figure 13 This is a block diagram of a configurable exemplary network node 1300 according to various embodiments of the present disclosure, including instructions executed on a computer-readable medium corresponding to any of the exemplary methods and / or processes described herein.

[0091] 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. Network node 1300 may include components such as base stations, eNBs, gNBs, access nodes, or network nodes.

[0092] One or more processors 1302 may include any type of processor or processing circuitry and may be configured to perform one of the methods or processes disclosed herein. Memory 1306 may store software code, programs, and / or instructions executable by one or more processors 1302 to configure network node 1300 to perform various operations, including those described herein. For example, execution of such stored instructions may configure network node 1300 to communicate with one or more other devices using protocols according to various embodiments of this disclosure, including one or more methods and / or processes discussed above. Furthermore, execution of such stored instructions may configure and / or facilitate 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-level protocols used in conjunction with radio network interface 1304 and 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 those standardized by 3GPP. The memory 1306 may also store variables used in the protocols, configurations, control, and other functions of the network node 1300. Therefore, 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 devices, or combinations thereof.

[0093] The radio network interface 1304 may include a transmitter, receiver, signal processor, ASIC, antenna, beamforming unit, and other circuitry enabling the network node 1300 to communicate with other equipment (in some embodiments, such as multiple compatible user equipment (UEs)). In some embodiments, the network node 1300 may include various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to further embodiments of this disclosure, the radio network interface 1304 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies. 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 circuitry enabling the network node 1300 to communicate with other equipment in the core network (in some embodiments, such as a circuit-switched (CS) and / or packet-switched (PS) core network). 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 SGW, MME, SGSN, GGSN, and other physical devices, which include functions known to those skilled in the art 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 over Ethernet (IP), SDH over fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art.

[0095] Other interfaces 1308 may include transmitters, receivers, and other circuitry that enables network node 1300 to communicate with external networks, computers, databases, etc., for the operation, management, and maintenance of network node 1300 or other network equipment operatively 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 Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0097] Example Section

[0098] The following examples relate to other implementation schemes.

[0099] Example 1 may include an apparatus comprising means for performing one or more elements of a method or process described or associated with any of the methods or processes described herein.

[0100] Embodiment 2 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described in any of the foregoing embodiments or related to them.

[0101] Example 3 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the methods described or associated with any of the above embodiments or any other methods or processes described herein.

[0102] Example 4 may include any method, technique, or process, or part or component thereof, that is described in or related to any of the above examples.

[0103] Embodiment 5 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0104] Example 6 may include any of the signals or parts or components described or associated with any of the above examples.

[0105] Embodiment 7 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages or parts or components thereof as described in or related to any of the above embodiments, or otherwise described in this disclosure.

[0106] Embodiment 8 may include a data-encoded signal or part or component thereof described or associated with any of the above embodiments, or otherwise described in this disclosure.

[0107] Embodiment 9 may include signals or portions or components thereof encoded as datagrams, packets, frames, segments, PDUs or messages in any of the above embodiments or in connection with them, or otherwise described in this disclosure.

[0108] Example 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 any of the methods, techniques, or processes or portions thereof described in or related to any of the above examples.

[0109] Example 11 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform any of the methods, techniques, or processes or portions thereof described in or associated with any of the above embodiments.

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

[0111] Example 13 may include methods for communicating in a wireless network as shown and described herein.

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

[0113] Example 15 may include a device for providing wireless communication as shown and described herein.

[0114] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

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

[0116] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in another implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0117] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

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

Claims

1. A method for user equipment (UE) operation in unlicensed spectrum, the method comprising: receiving a configuration including a parameter indicating a number of symbols; detecting a downlink control information (DCI) format 2 0, the DCI format 2 0 including: an available resource block (RB) set indicator information element (IE) indicating a status of a listen-before-talk (LBT) subband, and a channel occupancy time (COT) duration indicator IE; determining the status of the LBT subband based on the available RB set indicator IE, wherein a status of the available RB set indicator IE includes an unknown status; determining a value of the COT duration indicator IE; and based on determining that the status of the LBT subband is the unknown status and determining that the value of the COT duration indicator is a non-zero value, monitoring physical downlink control channel (PDCCH) candidates on one or more of the LBT subbands, wherein monitoring PDCCH candidates includes monitoring PDCCH candidates configured on all of the LBT subbands of an active bandwidth part (BWP) after a number of symbols indicated in the parameter from a last symbol of a CORESET including the DCI format 2 0 in response to the LBT subband being in the unknown status and the COT duration timer being a non-zero value.

2. The method of claim 1, further comprising: receiving a subsequent DCI format 2 0 with an active status of the LBT subband, wherein the active status indicates an available LBT subband; and switching from monitoring PDCCH candidates on all LBT subbands to monitoring PDCCH candidates on only the available LBT subband.

3. The method of claim 1, wherein the available RB set indicator IE "b1b0" is set to 00 or 10 for the unknown status, wherein "b0" indicates an availability of an LBT subband in which a UE detects a corresponding DCI format 2 0, and "b0 = 0" refers to a corresponding LBT subband being unavailable due to LBT failure.

4. The method of claim 1, further comprising determining that LBT has failed on a serving cell when the status of the LBT subband is the unknown status and the value of the COT duration indicator is set to both zeros.

5. The method of claim 1, wherein when the status of the LBT subband is the unknown status and the value of the COT duration indicator is the non-zero value, skipping monitoring of PDCCH candidates for a number of slots equal to the value of the COT duration indicator IE.

6. An apparatus for a UE, comprising: a memory interface to access a DCI format 2 0, the DCI format 2 0 including: an available RB set indicator IE indicating a status of an LBT subband, and a COT duration indicator IE; a baseband processing unit coupled to the memory interface, the baseband processing unit: receiving a configuration including a parameter indicating a number of symbols; detecting the DCI format 2 0; determining the status of the LBT subbands based on the available RB set indicator IE, wherein a status of the available RB set indicator IE includes an unknown status; determining a value of the COT duration indicator IE; and based on determining that the status of the LBT subbands is the unknown status and the value of the COT duration indicator is a non-zero value, monitoring PDCCH candidates on one or more of the LBT subbands, wherein monitoring PDCCH candidates includes monitoring PDCCH candidates on the LBT subbands only in which the UE detects the DCI format 2 0 after a number of symbols indicated in the parameters from a last symbol of a CORESET including the DCI format 2 0, in response to the LBT subbands being in the unknown status and the COT duration timer being a non-zero value.

7. The apparatus of claim 6, wherein the baseband processing unit is further to: receive a subsequent DCI format 2 0 with an active status of the LBT subbands, wherein the active status indicates available LBT subbands; and switch from monitoring PDCCH candidates on all LBT subbands to monitoring PDCCH candidates on only the available LBT subbands.

8. The apparatus of claim 6, wherein the available RB set indicator IE is set to 00, 11, or 10 for the unknown status.

9. The apparatus of claim 6, wherein the baseband processing unit is further to determine that LBT has failed on a serving cell when the status of the LBT subbands is the unknown status and the value of the COT duration indicator is set to both zeros.

10. The apparatus of claim 6, wherein when the status of the LBT subbands is the unknown status and the value of the COT duration indicator is the non-zero value, skipping monitoring of PDCCH candidates for a number of slots equal to the value of the COT duration indicator IE.

11. A method for operation of a next generation Node B gNB in unlicensed spectrum, the method comprising: transmitting, to a UE, a configuration including a parameter indicating a number of symbols in which the UE skips monitoring of PDCCH candidates from a last symbol of a CORESET including a DCI format 2 0 when an LBT subband is in an unknown status and a value of a COT duration timer is a non-zero value; encoding the DCI format 2 0, the DCI format 2 0 including: the COT duration indicator IE; and an available RB set indicator IE indicating a status of the LBT subbands, wherein the available RB set indicator IE is set to the unknown status when there is insufficient time to fully prepare the DCI format 2 0; and transmitting the DCI format 2 0 to the UE.

12. The method of claim 11, if the transmitted DCI format 2 0 has the available RB set indicator IE set to the unknown state, transmitting a subsequent DCI format 2 0 with an active state of the LBT subband, wherein the active state indicates available LBT subband.

13. The method of claim 11, wherein the available RB set indicator IE is set to 00, 11, or 10 for the unknown state.

14. The method of claim 11, further comprising indicating that LBT has failed by: setting the state of the LBT subband to the unknown state; and setting the value of the COT duration indicator to both be zero.

15. The method of claim 11, further comprising indicating that the UE can skip PDCCH monitoring for a number of slots equal to the value of the COT duration indicator IE when the state of the LBT subband is the unknown state and the value of the COT duration indicator is a non-zero value.

16. The method of claim 11, wherein the value set for the available RB set indicator IE for the unknown state is a predefined value.

Images