DE102020120785A1 - MECHANISMS FOR OPERATING DOWNLINK BROADBAND CARRIERS IN THE UNLICENSED BAND - Google Patents

Abstract

Apparatus and methods for wireless communication in a fifth generation (5G) or new radio (NR) system, including selecting a bandwidth in the unlicensed spectrum for communication over the 5G or NR system; Performing a channel scan for a plurality of sub-bands in the bandwidth; and transmitting one or more 5G or NR downlink channels, the transmission of the 5G or NR downlink channels depending on a result of the channel scan.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Application No. 62 / 888,283 , which was filed on August 16, 2019.

TECHNICAL AREA

Various aspects can generally concern the area of wireless communication.

BACKGROUND

Mobile communication has advanced significantly from the early speech systems to today's highly developed integrated communication platforms. The next-generation wireless communication system, e.g. the fifth generation (5G) or Neuer-Funk (New Radio - NR), will provide access to information and the sharing of data anywhere and anytime by different users and applications. NR is expected to be a unified network / system designed for very different and sometimes contradicting performance dimensions and services. Such different multi-dimensional requirements can be driven by different services and applications. In general, NR can evolve on the basis of the 3GPP (Third Generation Partnership Project) Long Term Evolution (LTE) - with the added potential of new radio access technologies (RATs) to make users' lives better, easier and more seamless To enrich wireless connectivity solutions. NR will enable anything that is wirelessly connected and provide fast, rich content and services.

Figure list

• 1 zeigt ein beispielhaftes Bandbreiten-Teildiagramm gemäß einiger Aspekte.
• 2 zeigt ein beispielhaftes Diagramm für die GC-PDCCH-Übertragung gemäß einigen Aspekten.
• 3 zeigt eine beispielhafte DCI-Information gemäß einiger Aspekte.
• 4 zeigt ein beispielhaftes Diagramm, in dem die Anpassung von PDSCH auf der Grundlage von LBT gemäß einigen Aspekten dargestellt ist.
• 5-7 zeigen beispielhafte Prozessflussdiagramme gemäß einiger Aspekte.
• 8 zeigt eine beispielhafte Architektur eines Systems eines Netzwerks gemäß einiger Aspekte.
• 9 zeigt eine beispielhafte Architektur eines Systems gemäß einiger Aspekte.
• 10 zeigt eine beispielhafte Architektur eines Systems gemäß einiger Aspekte.
• 11 zeigt eine beispielhafte Infrastrukturausstattung gemäß einiger Aspekte.
• 12 zeigt eine beispielhafte Plattform gemäß einiger Aspekte.
• 13 zeigt beispielhaft Komponenten der Basisbandschaltung und Funk-Frontend-Module (RFEM) gemäß einiger Aspekte.
• 14 zeigt beispielhafte Protokollfunktionen, die gemäß einigen Aspekten in einem Drahtlos-Kommunikationsgerät implementiert werden können.
• 15 zeigt eine beispielhafte Darstellung von Komponenten, die in der Lage sind, Anweisungen von einem maschinenlesbaren oder computerlesbaren Medium gemäß einigen Aspekten zu lesen.

In the drawings, reference characters generally refer to the same parts in the different views. The drawings are not necessarily to scale, rather emphasis generally being placed on illustrating the principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which:

• 1 FIG. 10 shows an exemplary bandwidth sub-diagram according to some aspects.
• 2 FIG. 10 shows an example diagram for GC-PDCCH transmission in accordance with some aspects.
• 3 FIG. 10 shows exemplary DCI information according to some aspects.
• 4th FIG. 13 is an exemplary diagram showing the adjustment of PDSCH based on LBT according to some aspects.
• 5-7 show example process flow diagrams according to some aspects.
• 8th FIG. 10 shows an example architecture of a system of a network in accordance with some aspects.
• 9 Figure 3 shows an example architecture of a system according to some aspects.
• 10 Figure 3 shows an example architecture of a system according to some aspects.
• 11 shows an exemplary infrastructure equipment according to some aspects.
• 12 shows an example platform according to some aspects.
• 13 shows examples of components of the baseband circuit and radio front-end modules (RFEM) according to some aspects.
• 14th FIG. 10 shows example protocol functions that may be implemented in a wireless communication device in accordance with some aspects.
• 15th FIG. 10 is an exemplary illustration of components capable of reading instructions from a machine-readable or computer-readable medium in accordance with some aspects.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details such as particular structures, architectures, interfaces, techniques, etc. are set forth in order to provide a thorough understanding of the various aspects. However, it will be apparent to those having the benefit of the present disclosure that the various aspects of the various aspects can be practiced in other examples that vary from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted in order not to obscure the descriptions of the various aspects in unnecessary detail. For the purposes of this document, the term “A or B” means (A), (B) or (A and B).

For the purposes of this document, the following terms and definitions apply to the examples and aspects discussed herein.

The term “circuit” refers to a circuit or a system of multiple circuits that is configured to perform a specific function in an electronic device. The circuit or the system of circuits can be part of one or more hardware components or comprise one or more hardware components, such as a logic circuit, a processor (shared, dedicated or group) and / or memory (shared, dedicated or group), a application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a system-on-chip (SoC) System-in-package (SiP), a multi-chip package (MCP), a digital signal processor (DSP), etc., which are set up to provide the functionality described. In addition, the term “circuit” can also refer to a combination of one or more hardware elements with the program code that is used to carry out the functionality of this program code. Some types of circuitry may execute one or more software or firmware programs to provide at least some of the functionality described. Such a combination of hardware elements and program code can be referred to as a certain type of circuit.

As used herein, the term "processor circuit" refers to circuits that are capable of sequentially and automatically executing a series of arithmetic or logic operations or of recording, storing and / or transmitting digital data is part of these circuits or has them. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a two-core processor, a three-core processor, a quad-core processor and / or any other device capable of to execute or otherwise operate computer-executable commands, such as program code, software modules and / or functional processes. The terms “application circuit” and / or “baseband circuit” can be viewed as a synonym for “processor circuit” and can be designated as such.

As used herein, the term “memory” and / or “memory circuit” refers to one or more hardware devices for storing data, including random access memory (RAM), magnetoresistive RAM (MRAM), phase change random access memory Access (PRAM), dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), core memory, read only memory (ROM), magnetic disk storage media, optical storage media, flash storage devices or other machine-readable media for storing data. The term “computer readable medium” may include, but is not limited to, memory, portable or stationary storage devices, optical storage devices, and various other media capable of storing, containing, or transmitting instructions or data.

The term “interface circuits” as used here refers to circuits that enable the exchange of information between two or more components or devices, is part of them, or has circuits. The term "interface circuits" can refer to one or more hardware interfaces, e.g. buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

The term “user device” or “UE” as used herein refers to a device with radio communication capabilities and can be a remote user of network resources on a communication network describe. The term "user device" or "UE" can be used as a synonym for client, mobile, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio, reconfigurable mobile device, etc., and can be referred to as such. Additionally, the term “user equipment” or “UE” can include any type of wireless / wired device or any computing device including a wireless communication interface.

As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, radio network control unit, RAN device, RAN node, gateway, server, virtualized VNF, NFVI and / or similar are viewed and / or referred to as such.

The term “computer system” as used herein refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled to one another. In addition, the term “computer system” and / or “system” can refer to a plurality of computer devices and / or a plurality of computer systems that are communicatively coupled to one another and are set up in such a way that they share computer and / or network resources.

The term “device”, “computing device” or the like, as used here, refers to a computing device or computer system with program code (e.g. software or firmware) that is specially designed to provide a particular computer resource. A “virtual device” is a virtual machine image that is implemented by a hypervisor-equipped device that virtualizes or emulates a computing device or is otherwise designed to provide a particular computing resource.

The term “element” refers to a unit that is indivisible on a certain level of abstraction and has a clearly defined boundary, whereby an element can be any type of unit, for example one or more devices, systems, controls, network elements, modules etc. or combinations thereof.

The term “device” refers to a physical unit which is embedded in another physical unit or connected to another physical unit in its vicinity and which is able to transmit digital information from or to this physical unit.

The term “entity” refers to a specific component of an architecture or device, or to information that is transmitted as a payload.

The term "control" refers to an element or entity that has the ability to influence a physical entity, e.g. by changing its state or by moving the physical entity.

The term "cloud computing" or "cloud" refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and management on demand and without active user management. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are called up via a defined interface (e.g. an API or similar). The term “computing resource” or simply “resource” refers to any physical or virtual component or the use of such components with limited availability within a computer system or network. Examples of computing resources indicate the use / access to servers, processor (s), storage devices, storage devices, storage areas, networks, electrical energy, input / output devices (peripheral devices), mechanical devices, network connections (e.g. channels / links, Ports, network sockets, etc.), operating systems, virtual machines (VMs), software / applications, computer files and / or the like. A “hardware resource” can refer to computing, storage and / or network resources that are provided by physical hardware elements. A “virtualized resource” can refer to computing, storage and / or network resources made available to an application, device, system, etc. by a virtualization infrastructure. The term " Network resource ”or“ communication resource ”may refer to resources that can be accessed by computing devices / systems over a communication network. The term “system resources” can refer to any type of shared unit that provides services and can include computing and / or network resources. System resources can be viewed as a series of coherent functions, network data objects, or services that can be accessed through a server if these system resources are located on one or more hosts and are uniquely identifiable.

The term “channel” used here refers to any transmission medium, be it tangible or intangible, that is used to communicate data or a data stream. The term "channel" can be synonymous with and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term that designates a path or medium over which data is communicated. In addition, the term “link” as used here refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

As used herein, the term "communication protocol" (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and / or system to communicate with other devices and / or systems, including instructions for packaging / Unpackaging of data, modulation / demodulation of signals, implementation of protocol stacks and / or the like.

The terms “instantiating”, “instantiating” and the like used here refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, which can occur e.g. during the execution of program code.

The terms “coupled”, “communicatively coupled” and derivatives thereof are used here. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with one another, can mean that two or more elements are indirectly in contact with one another, but still cooperate or interact with one another, and / or can mean that one or more other elements are coupled or connected between the elements to be coupled together. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” can mean that two or more elements may be in contact with one another through a communication medium, including through a wire or other interconnection, through a wireless communication channel, or ink, and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or a data element that contains content.

The term “access control” refers to a validation process in communication systems, in which a check is carried out before a connection is established to determine whether the current resources are sufficient for the proposed connection.

The term “SMTC” refers to an SSB-based measurement timing configuration that is set up by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS / PBCH block.

The term “primary cell” refers to the MCG cell that operates on the primary frequency and in which the UE either carries out the procedure for establishing a connection for the first time or initiates the procedure for establishing a new connection.

The term “primary SCG cell” refers to the SCG cell in which the UE performs random access when it performs the “reconfiguration with synchronization” procedure for direct current operation.

The term “secondary cell” refers to a cell that provides additional radio resources in addition to a special cell for a UE set up with CA.

The term “secondary cell group” refers to the subset of serving cells, including the PSCell and zero or more secondary cells for a DC-equipped UE.

The term “service-providing cell” refers to the primary cell for a UE in RRC_CONNECTED that is not set up with CA / DC, with only one service-providing cell from the primary cell. When a UE is established in RRC_CONNECTED with CA / DC, the term "serving cell" refers to the set of cells including the special cell (s) and any secondary cells.

The term “special cell” refers to the PC cell of the MCG or the PSCelle of the SCG for DC operation; otherwise the term “special cell” refers to the P-cell.

An important improvement for LTE in Release 13 was to enable the operation of cellular networks in the unlicensed spectrum via Licensed Assisted Access (LAA). Since then, using 3GPP's access to unlicensed frequencies has been seen as one of the most promising solutions for dealing with the ever-growing wireless traffic. One of the most important considerations for operating LTE in the unlicensed spectrum is ensuring fair coexistence with established systems such as wireless local access networks (WLANs), which have been the focus of standardization efforts of the LAA since release 13.

Following the trend of LTE improvements, a study point (SI) on NR-based access to unlicensed spectrum (NR-unlicensed) was presented in 3GPP Release 15. In the context of this SI, one of the main objectives is to identify additional functionalities that are required for a physical layer design (PHY) (e.g. PHY XV10 of the XV ) from NR are required for operation in the unlicensed spectrum. In particular, it is desirable to minimize the design effort by identifying the essential improvements required for the NR design of Release 15 to enable unlicensed operation while avoiding unnecessary deviations from the licensed NR framework of Release 15. Coexistence methods that are already defined for LTE-based LAA contexts can be assumed as the basis for the operation of NR-unlicensed systems, whereby improvements compared to these existing methods cannot be ruled out. The NR-based operation in unlicensed frequency ranges should not impair the WiFi services (data, video and voice services) used more than an additional WiFi network on the same carrier.

NR unlicensed technologies can be categorized into different modes including Carrier Aggregation (CA), Dual Connectivity (DC), and Standalone Network Modes (SA). The aspect of the channel access mechanism is one of the basic building blocks for NR unlicensed technologies, which is essential for all deployment options. The introduction of listen before talk (LBT) in the LTE-based LAA system not only met the regulatory requirements, but also provided fair coexistence with neighboring systems that share the unlicensed spectrum. The LBT-based channel access mechanism is basically similar to the Carrier Sense Multiple Access with collision avoidance (CSMA / CA) principle of the WLAN. Every node that wants to transmit in the unlicensed spectrum first conducts a channel query before initiating a transmission. To avoid collisions, an additional random back-off mechanism is used if more than one node detects the channel as unused and sends it at the same time.

• Breitbandbetrieb (in ganzzahligen Vielfachen von 20MHz) für DL und UL für NR-U, unterstützt mit mehreren Bedienungszellen, und Breitbandbetrieb (in ganzzahligen
• Vielfachen von 20MHz) für DL und UL für NR-U, unterstützt mit einer Bedienungszelle mit einer Bandbreite > 20MHz mit potentieller Zeitplanungseinschränkung vorbehaltlich der
• Eingabe von RAN2 und RAN4 über die Durchführbarkeit des Betriebs des Breitbandträgers, wenn LBT in einer oder mehreren LBT-Bandbreiten innerhalb des Breitbandträgers erfolglos ist.
• Für alle Breitbandbetriebsfälle wird die CCA in Einheiten von 20MHz durchgeführt (zumindest für 5GHz).

In the case of NR unlicensed, a cell can have a carrier bandwidth (BW) that is greater than 20 MHz, like the NR broadband operation (WB). However, due to the licensed band limitation, the LBT must be performed based on the 20MHz sub-band, which can also be referred to as LBT BW. Since several LBT-BWs can be located within one cell for WBT operation, operation can depend on how many LBT-BWs are available that can be used by implementing separate LBTs. For this purpose, the NR-U study / work item description defines the WB process as follows:

• Broadband operation (in integer multiples of 20MHz) for DL and UL for NR-U, supported with several operator cells, and broadband operation (in integer
• Multiples of 20MHz) for DL and UL for NR-U, supported with a control cell with a bandwidth> 20MHz with potential scheduling constraints subject to
• Entering RAN2 and RAN4 on the feasibility of operating the broadband bearer if LBT is unsuccessful in one or more LBT bandwidths within the broadband bearer.
• For all broadband operations, the CCA is carried out in units of 20MHz (at least for 5GHz).

The present disclosure provides mechanisms for the operation of WB cells and, in particular, the WB operation for NR-U. The aspects provided herein enable a more precise and efficient operation of WB methods with LBT operation compared to existing and / or previous solutions.

1 shows an exemplary WB configuration 100 , in which an active BWP is set up for a user device (UE) (eg UE XQ01 of Figure XQ) that is greater than 20 MHz. There can be several LBT-BWP within the active BWP, e.g. B. 4 LBT-BWP in the BWP, as in 1 is shown. Instead of “LBT bandwidth”, “LBT-BW” or the like, the terminology “LBT subband” can also be used here.

• - Option 1a: Mehrere BWPs sind einzurichten, mehrere BWPs können aktiviert werden, die Übertragung des Physikalischer-Abwärtsverbindung-Geteilter-Kanal (Physical Downlink Shared Channel - PDSCH) kann auf einem oder mehreren BWPs erfolgen.
• - Option 1b: Mehrere BWPs können eingerichtet werden, mehrere BWPs können aktiviert werden, die Übertragung von PDSCH kann auf einer einzigen BWP erfolgen.
• - Option 2: Mehrere BWPs können eingerichtet werden, eine einzige BWP kann aktiviert werden, die NodeB der nächsten Generation (gNB) überträgt PDSCH auf einer einzigen BWP, wenn Clear Channel Assessment (CCA) an der gNB für die gesamte BWP erfolgreich ist.
• - Option 3: Mehrere BWPs können eingerichtet sein, eine einzelne BWP kann aktiviert sein, die gNB überträgt PDSCH auf Teilen oder der Gesamtheit einer einzelnen BWP, wenn CCA am gNB erfolgreich ist.

WBT operation may depend on how many LBT BWs are available that can be used in response to successful LBT results. Several options can be provided for DL-WB operation, which are listed below:

• - Option 1a: Several BWPs are to be set up, several BWPs can be activated, the transmission of the physical downlink shared channel (PDSCH) can take place on one or more BWPs.
• - Option 1b: Several BWPs can be set up, several BWPs can be activated, the transmission of PDSCH can take place on a single BWP.
• - Option 2: Several BWPs can be set up, a single BWP can be activated, the next generation NodeB (gNB) transmits PDSCH on a single BWP if Clear Channel Assessment (CCA) at the gNB is successful for the entire BWP.
• - Option 3: Several BWPs can be set up, a single BWP can be activated, the gNB transmits PDSCH on parts or the entirety of a single BWP if CCA is successful at the gNB.

Options 1a and 1b can require multiple active BWPs, but options 2 and 3 can operate under a single active BWP. A major difference between Option 2 and Option 3 can be the condition of the PDSCH transmissions. With option 2, the PDSCH can be transmitted over the entire BWP if the CCA is successful for all LBT-BWP. With option 3, the PDSCH can be transmitted over the part of the BWP in which the CCA is successful. With option 2, the operation is simple, because if one of the LBT-BWs CCA fails, nothing is transmitted in the downlink (DL). With option 3, however, the available subbands for PDSCH transmission depend on the CCA of each LBT-BW. And if some LBT-BW fail within the BWP CCA, the neighboring LBT-BW can experience interference from the device using the subband. Therefore, a guard tape for the edge of the available sub-bands may need to be considered for Option 3.

In accordance with some aspects, the UE can be set up in such a way that it supports a mechanism for recognizing whether a gNB (e.g. RAN node XQ11 of FIG. XQ) is transmitting over several carriers or several LBT-BWs in one carrier. For this purpose, it may be desirable to explicitly specify the LBT-BWs of the gNB transmitted from the gNB to the UEs, since a blind detection of available LBT-BWs may not be reliable enough and can lead to many unnecessary operations in the event of an error. In addition, the UE blind detection itself will involve additional implementation effort. In some aspects, the DCI format 2_0 / group common PDCCH (GC-PDCCH) can be used to indicate a channel occupancy time structure (COT).

GC-PDCCH can be used to transmit at least slot format-related information. The DCI format 2_0 can be used for the notification of the slot format. The DCI format 2 0 with CRC encrypted by SFI-RNTI can have 1-N slot indicators (for example slot format indicator 1, slot format indicator 2,..., Slot format indicator N), where N is a number. The size of the DCI format 2_0 can be set up to 128 bits by higher layers. In various respects, the DCI format 2_0 can also contain a reference to the COT structure in the time domain.

According to some aspects, the DCI format 2_0 can be used both for available LBT BW information (frequency domain COT structure) and for the COT structure in the time domain. If the available LBT-BW information is transmitted in DCI format 2_0 via GC-PDCCH, it may have to be clarified in which LBT-BW the GC-PDCCH is transmitted, as some LBT-BWs may be available and the remaining LBT- BWs for the transfer GC-PDCCH are not available. According to some aspects, it can be assumed that each LBT-BW has at least one control unit (KERNSATZ - CORESET), and it can be assumed that at least one PDCCH candidate for GC-PDCCH is set up for each LBT-BW. With these aspects in mind, the gNB can PDCCH transmitted in one of the PDCCH candidates positioned within an available LBT BW (ie LBT sub-band) in which the LBT is successful, according to 2 .

In a CA scenario between licensed tape and unlicensed tape (eg LAA scenario) it is also possible in some aspects to transmit the GC-PDCCH using the licensed tape in order not to set up multiple PDCCH candidates for the GC-PDCCH and to provide higher reliability of the GC-PDCCH.

If the indication in DCI format 2_0 is supported via GC-PDCCH in one of the available LBT-BWs, additional procedures can be defined according to those discussed below.

In one aspect, a cluster-based configuration can be set up for the configuration of the CORESET, which corresponds to the GC-PDCCH. A cluster-based configuration can include that the CORESET resources are divided up for each LBT BW and each LBT BW has part of the CORESET resources. There may be PDCCH candidates who are restricted to each LBT BW. Therefore, even if a single CORESET is set up, GC-PCCH can be transmitted with the PDCCH candidate, which is restricted to the LBT BW in which the LBT is successful.

In one aspect, at least one PDCCH candidate must be guaranteed for the cluster-based configuration, since only a single LBT-BW is available via LBT outputs. Therefore the number of PDCCH candidates per PDCCH aggregation level must be at least equal to the number of LBT-BWs. Like in the 3 according to the example provided in 3 is shown, the number of PDCCH candidates for DCI 2_0, taking into account 5 LBT-BWS in a 100 MHz BW carrier, must possibly be 5.

In one aspect based on a gNB implementation, the GC-PDCCH may not be prepared at the beginning of the gNB-acquired COT. In this case, some aspects of the GC-PDCCH can be transmitted during the next monitoring events of the GC-PDCCH. It is therefore possible that the gNB has set up several monitoring options for GC-PDCCH within the COT for these aspects.

In another aspect, it may not be easy to reformat the PDSCH based on the LBT results. Therefore, for some aspects in the first or a few slot (phase 1), the PDSCH is mapped under the assumption that the entire BWP is available and the gNB may puncture the LBT-BW if the CCA is not successful. After sufficient time for gNB, the gNB can adjust the PDSCH according to the available LBT BWs in the remaining time of the same COT (phase 2), as in 4th is shown.

4th shows an exemplary scenario 400 a BWP during a COT according to some aspects. The GC-PDCCH is represented by 402, with 412 showing the bandwidth to which the data mapping is applied during phase 1 and 412 the bandwidth to which the data mapping is applied during phase 2. During phase 1, the data mapping is applied across the entire BWP, with the puncture in the LBT BW if the LBT fails.

As in 4th is shown, the UE can try to receive the entire BW of the BWP during phase 1. However, the UE can try to blindly recognize with the help of the demodulation reference signal (DMRS) which LBT-BWP are available, or it can try to decode GC-PDCCH as quickly as possible and do the decoding with the knowledge of the punctured parts perform. In some aspects, during phase 2, the UE knows which LBT-BWs are available and performs a rate adjustment around the LBT-BW that may not be available due to an LBT failure.

In one aspect, a downlink control unit (DCI) such as DCI 2_0 has available LBT bandwidth information as a BITMAP of N bits, where N is the number of LBT bandwidth (20 MHz) and each bit of the BITMAP indicates whether the LBT is successful or not in the corresponding LBT bandwidth.

In one aspect, DCI 2_0 may have the information about the available LBT bandwidth as N bits, where N indicates any combination of the available LBT bandwidths within the carrier. In one aspect of the disclosure, if the LBT result is not available due to the time constraint, the gNB can indicate that all LBT bandwidths are available. In another aspect of the disclosure, when the LBT result is not available due to the time constraint, the gNB can indicate that the LBT result is not yet available by reserving 1 state of N bits. In another aspect of the disclosure, if the LBT result is not available due to a time constraint, the gNB may indicate that not all LBT bandwidths are available. In another aspect of the disclosure, the information about the available LBT bandwidth can be set up by a higher layer which, for example, can specify which types of combinations of available LBT-BW can be displayed.

In other aspects, the UE can try to use the entire planned BW for the coding of PUSCH for the transmission of Physical Uplink Shared Channel (PUSCH) in the uplink (UL). Then the UE can puncture the data that is mapped on LBT BW if CCA is not successful. There can be only one phase for UL and puncturing may only need to be applied to the LBT BW if CCA is not successful throughout the COT duration.

In other aspects, a primary channel is defined in accordance with regulatory requirements. The selection of the primary channel can be left to the gNB implementation, or it can be selected uniformly from a grid of the available channels. In other aspects it can be determined. In this context, the GC-PDCCH that provides the LBT BW information can be provided within the primary channel and may not be prepared at the beginning of the gNB-acquired COT. In this case, the DL transmission via the active BWP can depend on the success of the LBT via the primary channel. In some aspects, a UE can always expect transmission over the primary channel. In the event that the primary channel is not known a priori and with the exception of the first DL burst, for which the UE has to carry out a blind detection to determine the primary channel, the primary channel can always be on the same channel in all subsequent DL bursts. Regulatory requirements only stipulate that the primary channel cannot be changed more than once per second, but they do not limit the amount of time in which the same channel can be used as the primary channel. The behavior of the UE in this case can be described as follows: 1) Phase 1- the UE tries to find the primary channel by recognizing the DMRS and / or decoding the GC-PDCCH, unless the primary channel is known a priori or has already been recognized in a previous DL burst (if the primary channel is known a priori or has already been recognized, it can simply decode the GC-PDCCH without blind detection and extract the information relating to the LBT BW); 2) Phase 2 - once the LBT BW is known, the UE can perform a radio frequency (RF) retuning and decode the information about the intended activated BWP.

5 shows an exemplary process 500 with corresponding characteristics 502-504 according to some aspects. process 500 may also have other features described here.

6th shows an exemplary process 600 with corresponding characteristics 602-604 according to some aspects. The process 600 may also have other features described here.

7th shows an exemplary process 700 with corresponding characteristics 702-706 according to some aspects. process 700 may have other features described here.

8th shows an exemplary architecture of a system 800 of a network according to various aspects. The following description is for an example system 800 that works in conjunction with the LTE system standards and 5G or NR system standards in accordance with the technical specifications of 3GPP. However, the example aspects are not limited in this regard, and the aspects described can also apply to other networks that benefit from the principles described here, such as future 3GPP systems (e.g. systems of the sixth generation (6G)), IEEE 802.16 protocols (e.g. WMAN, WiMAX etc.) or something similar.

As in 8th is shown, the system 800 the UE 801a and the UE 801b (together as "UE 801 "Or" UE 801 “Labeled). In this example the UEs are 801 represented as smartphones (e.g. portable mobile computer devices with touchscreens that can be connected to one or more cellular networks), but can also have all mobile or non-mobile computer devices, such as entertainment electronics devices, mobile phones, smartphones, function phones, tablet computers , portable computing devices, personal digital assistants (PDAs), pagers, handheld wireless devices, desktop computers, laptop computers, infotainment devices (IVI) in the vehicle, entertainment devices (ICE) in the car, an instrument cluster (IC), head-up Display (HUD) devices, on-board diagnostic devices (OBD), mobile dash-top equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs) ), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "intelligent" devices, MTC devices, M2M, devices for the Internet of Things (IoT) and / or the like.

In some aspects, each of the UEs 801 be an IoT UE that may have a network access layer designed for low power IoT applications using short lived UE connections. An IoT UE can use technologies such as machine-to-machine (M2M) or machine-type communication (MTC) for data exchange with an MTC server or device via a public mobile land mobile network (PLMN), proximity services (ProSe) or device -to-device communication (D2D), use sensor networks or IoT networks. The M2M or MTC data exchange can be a machine-initiated data exchange. An IoT network describes interconnected IoT UEs that can have uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UEs can run background applications (e.g. keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network. Some of these aspects may be with the UEs 801 around narrow-band (NB) -IoT UEs 801 act. NB-IoT provides access to network services via a physical layer that is optimized for very low power consumption (e.g. the full carrier bandwidth (BW) is 180 kHz, the distance between the subcarriers can be 3.75 kHz or 15 kHz). A number of Evolved UMTS Terrestrial Radio Access (E-UTRA) functions are not used for NB-IoT and must be used by the Radio Access Network (RAN) nodes 811 and the UEs 801 that only use NB-IoT may not be supported.

In various aspects, the UEs 801 MultiFire (MF) UEs 801 be. MF UEs 801 are LTE-based UEs 801 who work (exclusively) in the unlicensed spectrum. This unlicensed spectrum is defined in the MF specifications provided by the MulteFire forum and can be, for example, 1.9 GHz (Japan), 3.5 GHz and 5 GHz. MulteFire is closely based on the 3GPP standards and builds on elements of the 3GPP specifications for LAA / eLAA and extends the LTE standard to work in the global unlicensed spectrum. In some aspects, LBT can be implemented to coexist with other networks with unlicensed spectrum, such as Wi-Fi, other LAA networks, or the like. In various aspects, some or all of the UEs 801 NB-IoT UEs 801 who work according to MF. According to such aspects, these UEs 801 as "MF NB-IoT UEs 801 ", But the term" NB-IoT UE 801 "To a" MF UE 801 "Or a" MF and NB-IoT UE 801 "Unless otherwise stated. Therefore, the terms “NB-IoT UE 801 "," MF UE 801 "And" MF NB-IoT UE 801 “May be used interchangeably throughout this disclosure.

The UEs 801 can be set up, for example a communicative coupling with RAN 810 to manufacture. In aspects, the RAN 810 be a next generation (NG) RAN or a 5G RAN. According to the term "NG RAN" or similar used here, the term "NG RAN" or similar can refer to a RAN 810 referring to that in an NR or 5G system 800 is operated. The UEs 801 use links (or channels) 803 and 804, respectively, each of which has a physical communication interface or layer (discussed in more detail below). The connections 803 and 804 may have several different physical DL channels and several different physical UL channels. The physical DL channels include, for example, PDSCH, physical multicast channel (PMCH), PDCCH, extended PDCCH (EPDCCH), MTC PDCCH (MPDCCH), relay PDCCH (R-PDCCH), shortened PDCCH (SPDCCH), Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Channel Hybrid ARQ Display Channel (PHICH), Physical Narrowband Broadcast Channel (NPBCH), Physical Narrowband -Control channel for the downlink (NPDCCH), physical narrowband control channel for the common downlink (NPDSCH) and / or all other physical DL channels mentioned here. The physical UL channels include, for example, the physical random access channel (PRACH), PUSCH, physical uplink control channel (PUCCH), shortened PUCCH (SPUCCH), narrowband PRACH (Narrowband PRACH - NPRACH), Narrowband PUSCH (Narrowband PUSCH - NPUSCH) and / or all other physical UL channels mentioned here.

In this example the connections are 803 and 804 shown as an air interface to enable communicative coupling and may be consistent with cellular communication protocols such as a 5G protocol, an NR protocol, and / or any of the other communication protocols discussed herein. In aspects, the UEs 801 Communication data directly via a ProSe interface 805 change. The ProSe interface 805 can alternatively be used as a side link (Sidelink - SL) interface 805 and may have one or more physical and / or logical channels including, but not limited to, the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH) , Physical Sidelink Downlink Channel - PSDCH) and Physical Sidelink Broadcast Channel (PSBCH).

It is shown that the UE 801b is set up to use the connection 807 to an access point (AP) 806 (also called "WLAN node 806 ", "WIRELESS INTERNET ACCESS 806 "," WLAN termination 806 "," WT 806 "Or similarly named). The connection 807 can have a local wireless connection, eg a connection according to any IEEE 802.11 protocol, where the AP 806 would have a Wireless Fidelity (Wi-Fi®) router. This example shows that the AP 806 Connected to the Internet without being connected to the wireless system's core network (described in more detail below). The UE 801b , RAN 810 and AP 806 can be set up from different perspectives to use LTE WLAN aggregation (LWA) and / or LTE / WLAN radio level integration with Internet Protocol Security (IPsec) tunnel (LWIP). The LWA operation may include the UE 801b in RRC CONNECTED by a RAN node 811a-b is set up to use the radio resources of LTE and WLAN. LWIP operation may include the UE 801b the radio resources of the wireless local area network (WLAN) (e.g. connection 807 ) uses IPsec protocol to tunnel over the connection 807 to authenticate and encrypt sent packets (e.g. IP packets). IPsec tunneling can involve encapsulating all of the original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN 810 can be one or more access network (AN) nodes or RAN nodes 811a and 811b (together as "RAN node 811 "Or" RAN node 811 "Denotes) that the connections 803 and 804 enable. The terms “access node”, “access point” or similar used here can describe devices that provide the radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, MF-APs, TRxPs or TRPs, etc. one cell). According to the term "NG RAN node" or similar used here, the term "NG RAN node" or similar can refer to a RAN node 811 in an NR or 5G system 800 (e.g. a gNB) is operated. In various aspects, the RAN nodes 811 implemented as one or more dedicated physical devices such as a macro cell base station and / or a low power base station (LP) to provide femtocells, picocells or other similar cells with smaller coverage areas, lower user capacity or higher BW compared to macro cells.

In some aspects, all or part of the RAN nodes 811 implemented as one or more software units running on server computers as part of a virtual network that can be referred to as a Cloud RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). According to these aspects, the CRAN or vBBUP can implement a RAN function division, such as e.g. B. a PDCP division (Packet Data Convergence Protocol), in which the RRC and PDCP layers through the CRAN / vBBUP and other L2 protocol units through individual RAN nodes 811 operate; a division of the medium access control (MAC) / physical layer (PHY), in the RRC, PDCP, radio link control (RLC) and MAC layers by the CRAN / vBBUP and the PHY layer individual RAN nodes 811 operate; or a "lower PHY" division where RRC, PDCP, RLC, MAC layers and upper sections of the PHY layer by the CRAN / vBBUP and lower sections of the PHY layer by individual RAN nodes 811 operate. This virtualized framework enables the released processor cores of the RAN nodes 811 to run other virtualized applications. In some implementations, a single RAN node can be used 811 represent individual distributed gNB units (gNB-DUs) that are connected to a gNB central unit (gNB-CU) via individual F1 interfaces (in 8th not shown). In these implementations, the gNB-DUs can have one or more remote radio heads or radio front-end modules (RFEMs) (see e.g. 11 ), and the gNB-CU can be accessed from a server located in the RAN 810 (not shown), or operated by a server pool in a similar way to the CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes can be 811 Next Generation eNBs (NG-eNBs) which are RAN nodes that E-UTRA user plane and control plane protocol terminations to the UEs 801 and via an NG interface with an SG core network (5GC) (e.g. core network (CN) 1020 in 10 ) are connected (see below).

In Vehicle to Everything (V2X) scenarios, one or more of the RAN nodes 811 Be or act as road side units (RSUs). The term Road Side Unit or "RSU" can refer to any transportation infrastructure unit used for V2X communications. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, with an RSU implemented in or by a UE as “UE-Type-RSU”, an RSU implemented in or by an eNB as “ENB-Typ-RSU”, an RSU implemented in or by a gNB can be designated as “gNB-Typ-RSU” and the like. In one example, an RSU is a computing unit that is coupled to a radio frequency circuit located on a roadside and provides connectivity support for passing vehicles of the UEs 801 (VUEs 801 ) provides. The RSU can also have an internal data storage circuit in order to store the geometry of the intersection maps, traffic statistics, media and applications / software for recording and controlling the moving vehicle and pedestrian traffic. The RSU can operate on the 5.9 GHz Short Range Direct Communication (DSRC) band to provide the very low latency communication required for high speed events such as accident avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can operate on the V2X cellular band to provide the very low latency communication mentioned above as well as other cellular communication services. Additionally or alternatively, the RSU can operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks in order to provide uplink and downlink communication. The computing device (s) and some or all of the radio frequency circuitry of the RSU may be housed in a weatherproof enclosure suitable for outdoor installation and may have a network interface controller to provide a wired connection (e.g., ethernet) to a traffic signal Control and / or a backhaul network.

Each of the RAN nodes 811 can terminate the air interface protocol and can be the first point of contact for the UEs 801 be. In some aspects, each of the RAN nodes can 811 various logical functions for the RAN 810 including, but not limited to, radio network control unit (RNC) functions such as radio bearer management, uplink and downlink, dynamic radio resource management and packet scheduling as well Mobility management.

In aspects, the UEs 801 be set up so that they are using OFDM communication signals (Orthogonal Frequency Division Multiplexing - Orthogonal Frequency Division Multiplexing) with each other or with each of the RAN nodes 811 Can communicate via a multi-carrier communication channel according to various communication technologies, such as OFDMA communication technology (Orthogonal Frequency Division Multiple Access) (e.g. for downlink communications) or a single carrier frequency division multiple access (single carrier Frequency Division Multiple Access - SC-FDMA) communication technology (e.g. for uplink and ProSe or sidelink communications), although the scope of the aspects is not limited in this regard. The OFDM signals can have a plurality of orthogonal sub-carriers.

die Indizes im Frequenz- bzw. Zeitbereich sind. RE (k,1) am Antennenanschluss p entspricht dem komplexen Wert a_(k,1)^((p)). Ein Antennenport ist so definiert, dass der Kanal, über den ein Symbol am Antennenport p übertragen wird, von dem Kanal abgeleitet werden kann, über den ein anderes Symbol am gleichen Antennenport übertragen wird. Es gibt ein Ressourcengitter pro Antennenport. Der Satz der unterstützten Antennenports hängt von der Konfiguration des Referenzsignals in der Zelle ab, und diese Aspekte werden in 3GPP TS 36.211 näher erläutert.Downlink and uplink transmissions can be organized in frames with a duration of 10 ms, with each frame having ten sub-frames of 1 ms. A slot duration is 14 symbols with a normal cyclic prefix (CP) and 12 symbols with an extended CP and scales in time depending on the subcarrier spacing used, so that there is always an integer number of slots in a subframe. In some implementations, a DL resource grid may be used for DL transmissions from each of the RAN nodes 811 to the UEs 801 used during UL transmissions from the UEs 801 to the RAN nodes 811 use a suitable UL resource grid in a similar manner. These resource grids can relate to time-frequency grids and indicate the physical resource in the DL or UL in each slot. Each column and each row of the DL resource grid corresponds to an OFDM symbol or an OFDM subcarrier, and each column and each row of the UL resource grid corresponds to an SC-FDMA symbol or an SC-FDMA subcarrier. The duration of the resource grid in the time domain corresponds to a slot in a radio frame. The resource grids have a number of resource blocks (RBs) which describe the mapping of certain physical channels onto resource elements (REs). In the frequency domain, this can represent the smallest amount of resources that can currently be allocated. Each RB has a collection of REs. A RE is the smallest time / frequency unit in a resource grid. Each RE is uniquely identified by the index pair (k, 1) in a slot, where $k=\mathrm{0,}...,N_{\text{RB}}^{\text{DL}}{N}_{\text{sc}}^{\text{RB}}-1\text{and}l=\mathrm{0,}...,N_{\text{symb}}^{\text{DL}}-1$

the indices are in the frequency or time domain. RE (k, 1) at the antenna connection p corresponds to the complex value a_ (k, 1) ^ ((p)). An antenna port is defined in such a way that the channel via which a symbol is transmitted at the antenna port p can be derived from the channel via which another symbol is transmitted at the same antenna port. There is one resource grid per Antenna port. The set of antenna ports supported depends on the configuration of the reference signal in the cell, and these aspects are further explained in 3GPP TS 36.211.

Jeder Rahmen ist in zwei gleich große Halbrahmen s mit jeweils fünf Teilrahmen unterteilt, wobei jeder Teilrahmen einen Halbrahmen 0 mit den Teilrahmen 0 - 4 und einen Halbrahmen 1 mit den Teilrahmen 5 - 9 aufweist. Auf einem Träger kann es einen Satz von Rahmen in der UL und einen Satz von Rahmen in der DL geben. Die Uplink-Rahmennummer i für die Übertragung vom UE 801 beginnt T_TA = (N_TA + N_TA,offset)T_c vor dem Beginn des korrespondierenden Downlink-Rahmens am UE, wobei N_TA,offset dem UE bereitgestellt wird und ein Wert eines Timing-Vorversatzes für eine Server-Zelle um n-TimingAdvanceOffset für die Server-Zelle ist. Wenn das UE nicht mit einem n-TimingAdvanceOffset für eine versorgende Zelle bereitgestellt wird, kann das UE einen Standardwert N_TA,offset für den Zeitvorversatz bestimmen. Wenn das UE mit zwei UL-Trägern für eine versorgende Zelle eingerichtet ist, gilt für beide Träger der gleiche Wert für den Timing-Vorversatz N_TA,offset. Für die Unterträgerabstandskonfiguration µ sind die Schlitze $n_{\text{s}}^{\mu }\in \left\{\mathrm{0,}\dots ,N_{\text{slot}}^{\text{subframe},\mu }-1\right\}$

in aufsteigender Reihenfolge innerhalb eines Teilrahmens und $n_{\text{s}\text{,f}}^{\mu }\in \left\{\mathrm{0,}\dots ,N_{\text{slot}}^{\text{frame},\mu }-1\right\}$

in aufsteigender Reihenfolge innerhalb eines Rahmens nummeriert. Es gibt $N_{\text{symb}}^{\text{slot}}$

aufeinanderfolgende OFDM-Symbole in einem Schlitz, wobei $N_{\text{symb}}^{\text{slot}}$

von dem zyklischen Präfix gemäß den Tabellen 4.3.2-1 und 4.3.2-2 unten abhängt. Tabelle 4.3.2-1: Anzahl von OFDM-Symbolen pro Schlitz, Schlitzen pro Rahmen, und Schlitzen pro Teilrahmen für normalen zyklischen Präfix. µ $N_{\text{symb}}^{\text{slot}}$

$N_{\text{slot}}^{\text{frame}\text{,}\mu }$

$N_{\text{slot}}^{\text{subframe}\text{,}\mu }$

0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16 Tabelle 4.3.2-2: Anzahl von OFDM-Symbolen pro Schlitz, Schlitzen pro Rahmen, und Schlitzen pro Teilrahmen für erweiterten zyklischen Präfix. µ $N_{\text{symb}}^{\text{slot}}$

$N_{\text{slot}}^{\text{frame}\text{,}\mu }$

$N_{\text{slot}}^{\text{subframe}\text{,}\mu }$

2 12 40 4 In NR / 5G implementations, DL and UL transmissions are organized into frames with a duration of 10 ms, each having ten sub-frames of 1 ms. The number of consecutive OFDM symbols per sub-frame is $N_{\text{symb}}^{\text{subframe},\mu }=N_{\text{symb}}^{\text{slot}}{N}_{\text{slot}}^{\text{subframe},\mu }.$

Each frame is divided into two half-frames s of equal size, each with five sub-frames, each sub-frame having a half-frame 0 with the sub-frames 0-4 and a half-frame 1 with the sub-frames 5-9. On a carrier there can be one set of frames in the UL and one set of frames in the DL. The uplink frame number i for transmission from the UE 801 begins T _TA = (N _TA + N _{TA, offset} ) T _c before the beginning of the corresponding downlink frame at the UE, where N _{TA, offset is made available to} the UE and a value of a timing advance for a server cell by n- TimingAdvanceOffset for the server cell is. If the UE is not provided with an n-TimingAdvanceOffset for a serving cell, the UE can determine a standard value N _{TA, offset} for the time advance. If the UE is set up with two UL carriers for a serving cell, the same value for the timing advance N _{TA, offset} applies to both carriers. For the subcarrier spacing configuration µ are the slots $n_{\text{s}}^{\mu }\in \left\{\mathrm{0,}...,N_{\text{slot}}^{\text{subframe},\mu }-1\right\}$

in ascending order within a sub-frame and $n_{\text{s}\text{, f}}^{\mu }\in \left\{\mathrm{0,}...,N_{\text{slot}}^{\text{frame},\mu }-1\right\}$

numbered in ascending order within a frame. There are $N_{\text{symb}}^{\text{slot}}$

consecutive OFDM symbols in a slot, where $N_{\text{symb}}^{\text{slot}}$

depends on the cyclic prefix according to Tables 4.3.2-1 and 4.3.2-2 below. Table 4.3.2-1: Number of OFDM symbols per slot, slots per frame, and slots per sub-frame for normal cyclic prefix. µ $N_{\text{symb}}^{\text{slot}}$

$N_{\text{slot}}^{\text{frame}\text{,}\mu }$

$N_{\text{slot}}^{\text{subframe}\text{,}\mu }$

0 14th 10 1 1 14th 20th 2 2 14th 40 4th 3 14th 80 8th 4th 14th 160 16 Table 4.3.2-2: Number of OFDM symbols per slot, slots per frame, and slots per sub-frame for extended cyclic prefix. µ $N_{\text{symb}}^{\text{slot}}$

$N_{\text{slot}}^{\text{frame}\text{,}\mu }$

$N_{\text{slot}}^{\text{subframe}\text{,}\mu }$

2 12 40 4th

in einem Teilrahmen wird zeitlich mit dem Beginn des OFDM-Symbols $n_{\text{s}}^{\mu }{N}_{\text{symb}}^{\text{slot}}$

im gleichen Teilrahmen ausgerichtet. OFDM-Symbole in einem Schlitz können als „Downlink“, „flexibel“ oder „Uplink“ klassifiziert werden, wobei Downlink-Übertragungen nur in „Downlink“- oder „flexiblen“ Symbolen erfolgen und die UEs 801 nur in „Uplink“- oder „flexiblen“ Symbolen übertragen.The beginning of $n_{\text{s}}^{\mu }$

in a subframe is timed to the beginning of the OFDM symbol $n_{\text{s}}^{\mu }{N}_{\text{symb}}^{\text{slot}}$

aligned in the same sub-frame. OFDM symbols in a slot can be classified as “downlink”, “flexible” or “uplink”, with downlink transmissions only taking place in “downlink” or “flexible” symbols and the UEs 801 Only transmitted in "uplink" or "flexible" symbols.

Unterträgern und $N_{\text{symb}}^{\text{subframe}\text{,}\mu }$

OFDM-Symbolen definiert, beginnend mit dem gemeinsamen RB $N_{\text{grid}}^{\text{start},\mu }$

das durch Signalisierung auf höherer Ebene angezeigt wird. Es gibt einen Satz von Ressourcengittern pro Übertragungsrichtung (d.h. Uplink oder Downlink), wobei der Index x auf DL für Downlink und x auf UL für Uplink gesetzt ist. Es gibt ein Ressourcengitter für einen bestimmten Antennenanschluss p, die Konfiguration des Unterträgerabstands µ und die Übertragungsrichtung (d.h. Downlink oder Uplink).For each numerology and each carrier a resource grid is made $N_{\text{grid},x}^{\text{size},\mu }{N}_{\text{sc}}^{\text{RB}}$

Subcarriers and $N_{\text{symb}}^{\text{subframe}\text{,}\mu }$

OFDM symbols are defined starting with the common RB $N_{\text{grid}}^{\text{begin},\mu }$

which is indicated by signaling at a higher level. There is one set of resource grids per transmission direction (ie uplink or downlink), with the index x being set to DL for downlink and x to UL for uplink. There is a resource grid for a specific antenna connection p, the configuration of the subcarrier spacing µ and the transmission direction (ie downlink or uplink).

aufeinanderfolgende Subträger im Frequenzbereich. Übliche RBs sind von 0 und aufwärts im Frequenzbereich für die Unterträgerabstandskonfiguration µ nummeriert. Die Mitte des Unterträgers 0 des gemeinsamen Ressourcenblocks 0 für die Unterträgerabstandskonfiguration µ fällt mit ‚Punkt A‘ zusammen. Die Beziehung zwischen der Nummer des gemeinsamen Ressourcenblocks $n_{\text{CRB}}^{\mu }$

im Frequenzbereich und den Ressourcenelementen (k,l) für die Unterträgerabstandskonfiguration µ ist gegeben durch $n_{\text{CRB}}^{\mu }=\left[\frac{k}{N_{\text{sc}}^{\text{RB}}}\right],$

wobei k relativ zu Punkt A so definiert ist, dass k = 0 dem um Punkt A zentrierten Unterträger entspricht. Punkt A dient als gemeinsamer Bezugspunkt für Ressourcenblockgitter und wird aus offsetToPointA für eine Primärzellen-(PCell)-Abwärtsstrecke erhalten, wobei offsetToPointA den Frequenzversatz zwischen Punkt A und dem untersten Unterträger des untersten Ressourcenblocks darstellt, die den durch den Parameter subCarrierSpacingCommon der höheren Schicht bereitgestellten Subträgerabstand aufweist und sich mit dem Synchronisierungssignal (SS)/PBCH-Block überlappt, der von dem UE für die anfängliche Zellenauswahl verwendet wird, ausgedrückt in Einheiten von Ressourcenblöcken unter Annahme eines 15 kHz-Subträgerabstands für FR1 und eines 60 kHz-Subträgerabstands für FR2; und absoluteFrequencyPointA für alle anderen Fälle, in denen absoluteFrequencyPointA die Frequenzlage von Punkt A darstellt, ausgedrückt gemäß Absolute Radio Frequency Channel Number (ARFCN).An RB is defined as $N_{\text{sc}}^{\text{RB}}=12$

successive subcarriers in the frequency domain. Common RBs are numbered from 0 and up in the frequency domain for the subcarrier spacing configuration µ. The center of the subcarrier 0 of the common resource block 0 for the subcarrier spacing configuration µ coincides with 'Point A'. The relationship between the number of the shared resource block $n_{\text{CRB}}^{\mu }$

in the frequency domain and the resource elements (k, l) for the subcarrier spacing configuration µ is given by $n_{\text{CRB}}^{\mu }=\left[\frac{k}{N_{\text{sc}}^{\text{RB}}}\right],$

where k is defined relative to point A such that k = 0 corresponds to the subcarrier centered around point A. Point A serves as a common reference point for resource block lattices and is obtained from offsetToPointA for a primary cell (PCell) downlink, where offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which is the subcarrier spacing provided by the parameter subCarrierSpacingCommon of the higher layer and overlaps with the sync signal (SS) / PBCH block used by the UE for the initial cell selection, expressed in units of resource blocks, assuming a 15 kHz subcarrier spacing for FR1 and a 60 kHz subcarrier spacing for FR2; and absoluteFrequencyPointA for all other cases in which absoluteFrequencyPointA represents the frequency position of point A, expressed according to the Absolute Radio Frequency Channel Number (ARFCN).

wobei i i die Nummer der BWP ist. Die Beziehung zwischen dem physischen Ressourcenblock $n_{\text{PRB}}^{\mu }$

in BWPi und der gemeinsamen RB $n_{\text{CRB}}^{\mu }$

ist gegeben durch $n_{\text{CRB}}^{\mu }=n_{\text{PRB}}^{\mu }+N_{\text{BWP},i}^{\text{start},\mu },\text{ wobei }{N}_{\text{BWP},i}^{\text{start},\mu }$

der gemeinsame RB ist, wobei BWP relativ zum gemeinsamen RB 0 beginnt. Virtuelle RBs (VRBs) sind innerhalb einer BWP definiert und von 0 bis $N_{\text{BWP},i}^{\text{size}}-\mathrm{1,}$

nummeriert, wobei i die Nummer der BWP ist.A physical RB (PRB) for the subcarrier configuration µ are set up within a bandwidth part (BWP) and from 0 to $N_{\text{BWP},i}^{\text{size},\mu }-1$

where ii is the number of the BWP. The relationship between the physical resource block $n_{\text{PRB}}^{\mu }$

in BWPi and the common RB $n_{\text{CRB}}^{\mu }$

is given by $n_{\text{CRB}}^{\mu }=n_{\text{PRB}}^{\mu }+N_{\text{BWP},i}^{\text{begin},\mu },\text{in which}{N}_{\text{BWP},i}^{\text{begin},\mu }$

is the common RB, where BWP starts relative to the common RB 0. Virtual RBs (VRBs) are defined within a BWP and from 0 to $N_{\text{BWP},i}^{\text{size}}-\mathrm{1,}$

numbered, where i is the number of the BWP.

Ein Antennenanschluss ist so definiert, dass der Kanal, über den ein Symbol auf dem Antennenanschluss übertragen wird, von dem Kanal abgeleitet werden kann, über den ein anderes Symbol auf demselben Antennenanschluss übertragen wird. Man spricht von zwei Antennenports, wenn die großräumigen Eigenschaften des Kanals, über den ein Symbol auf einem Antennenport übertragen wird, von dem Kanal abgeleitet werden können, über den ein Symbol auf dem anderen Antennenport übertragen wird. Die großräumigen Eigenschaften weisen einen oder mehrere der Parameter Verzögerungsspreizung, Doppler-Spreizung, Doppler-Verschiebung, mittlere Verstärkung, mittlere Verzögerung und räumlicher Empfang (Rx) auf.Each element in the resource grid for the configuration of the antenna connection p and the subcarrier spacing µ is designated as RE and uniquely identified by (k, l) _{p, µ} , where k is the index in the frequency domain and 1 refers to the symbol position in the time domain relative to a reference point relates. The resource element (k, 1) _{p, µ} corresponds to a physical resource and the complex value $a_{k,l}^{\left(p,\mu \right)}.$

An antenna connector is defined so that the channel over which a symbol is transmitted on the antenna connector can be derived from the channel over which another symbol is transmitted on the same antenna connector. One speaks of two antenna ports when the large-scale properties of the channel over which a symbol is transmitted on one antenna port can be derived from the channel over which a symbol is transmitted on the other antenna port. The large-scale properties have one or more of the parameters delay spread, Doppler spread, Doppler shift, mean gain, mean delay and spatial reception (Rx).

und die Anzahl der Ressourcenblöcke $N_{\text{BWP},i}^{\text{size},\mu }$

in einer BWP kann $N_{\text{grid},x}^{\text{start}\text{,}\mu }\le N_{\text{BWP},i}^{\text{start},\mu }<N_{\text{grid},x}^{\text{start}\text{,}\mu }+N_{\text{grid},x}^{\text{size},\mu }$

$\text{bzw}.N_{\text{grid},x}^{\text{start},\mu }<N_{\text{BWP},i}^{\text{start},\mu }+N_{\text{BWP},i}^{\text{size},\mu }\le N_{\text{grid},x}^{\text{start},\mu }+N_{\text{grid},x}^{\text{size},\mu }$

erfüllen. Die UEs 801 können mit bis zu vier BWPs in dem DL eingerichtet werden, wobei eine einzelne DL-BWP zu einem gegebenen Zeitpunkt aktiv ist. Von den UEs 801 wird nicht erwartet, dass sie außerhalb einer aktiven BWP PDSCH-, PDCCH- oder CSI-Referenzsignale (CSI-RS) empfangen (mit Ausnahme von Radio Resource Management (RRM)). Die UEs 801 können mit bis zu vier BWPs in dem UL eingerichtet werden, wobei eine einzelne UL BWP zu einem gegebenen Zeitpunkt aktiv ist. Wenn ein UE 801 mit einem zusätzlichen UL eingerichtet ist, kann das UE 801 mit bis zu vier zusätzlichen BWPs im zusätzlichen UL eingerichtet werden, wobei ein einziges zusätzliches UL BWP zu einem gegebenen Zeitpunkt aktiv ist. Die UEs 801 senden kein PUSCH oder PUCCH außerhalb einer aktiven BWP, und für eine aktive Zelle senden die UEs 801 kein Sounding Reference Signal (SRS) außerhalb einer aktiven BWP.A BWP is a subset of adjoining common RBs for a certain numerology µ _i in BWP i on a given carrier. The starting position $N_{\text{BWP},i}^{\text{begin},\mu }$

and the number of resource blocks $N_{\text{BWP},i}^{\text{size},\mu }$

in a BWP can $N_{\text{grid},x}^{\text{begin}\text{,}\mu }\le N_{\text{BWP},i}^{\text{begin},\mu }<N_{\text{grid},x}^{\text{begin}\text{,}\mu }+N_{\text{grid},x}^{\text{size},\mu }$

$\text{or}.N_{\text{grid},x}^{\text{begin},\mu }<N_{\text{BWP},i}^{\text{begin},\mu }+N_{\text{BWP},i}^{\text{size},\mu }\le N_{\text{grid},x}^{\text{begin},\mu }+N_{\text{grid},x}^{\text{size},\mu }$

fulfill. The UEs 801 can be set up with up to four BWPs in the DL, with a single DL-BWP being active at a given point in time. From the UEs 801 They are not expected to receive PDSCH, PDCCH or CSI reference signals (CSI-RS) outside of an active BWP (with the exception of Radio Resource Management (RRM)). The UEs 801 can be set up with up to four BWPs in the UL, with a single UL BWP active at any given time. If a UE 801 is set up with an additional UL, the UE 801 can be set up with up to four additional BWPs in the additional UL, with a single additional UL BWP active at any given time. The UEs 801 do not send a PUSCH or PUCCH outside an active BWP, and for an active cell the UEs send 801 No Sounding Reference Signal (SRS) outside of an active BWP.

Die NBs sind in der Reihenfolge der steigenden PRB-Zahl nummeriert $n_{\text{NB}}=\mathrm{0,}\dots ,N_{\text{NB}}^{\text{DL}}-\mathrm{1,}$

wobei Schmalband n_NB PRB-Indizes: $$\{\begin{array}{ll}6n_{\text{NB}}+i_0+i\hfill & \text{if }{N}_{\text{RB}}^{\text{UL}}\text{ mod }2=0\hfill \\ 6n_{\text{NB}}+i_0+i\hfill & \text{if }{N}_{\text{RB}}^{\text{UL}}\text{ mod }2=1\text{ and }{n}_{\text{NB}}<N_{\text{RB}}^{\text{UL}}/2\hfill \\ 6n_{\text{NB}}+i_0+i+1\hfill & \text{if }{N}_{\text{RB}}^{\text{UL}}\text{ mod }2=1\text{ and }{n}_{\text{NB}}\ge N_{\text{RB}}^{\text{UL}}/2\hfill \end{array}$$

aufweisen, wobei $$\begin{array}{l}i=\mathrm{0,1,}\dots \mathrm{,5}\hfill \\ i_0=\left[\frac{N_{\text{RB}}^{\text{UL}}}{2}\right]-\frac{6N_{\text{RB}}^{\text{UL}}}{2}\hfill \end{array}.$$

An NB is defined as six non-overlapping, consecutive PRBs in the frequency domain. The total number of DL-NBs in the DL transmission BW set up in the cell is given by $N_{\text{NB}}^{\text{DL}}=\left[\frac{N_{\text{RB}}^{\text{DL}}}{\mathrm{6th}}\right].$

The NBs are numbered in the order of increasing PRB number $n_{\text{NB}}=\mathrm{0,}...,N_{\text{NB}}^{\text{DL}}-\mathrm{1,}$

where narrow band n _NB PRB indices: $$\{\begin{array}{ll}\mathrm{6th}{n}_{\text{NB}}+i_0+i\hfill & \text{if}{N}_{\text{<figure-callout id="2" label="RB UL mod" filenames="DE102020120785A1\_0042.png,DE102020120785A1\_0044.png" state="{{state}}">RB</figure-callout>}}^{\text{UL}}\text{mod}2=0\hfill \\ \mathrm{6th}{n}_{\text{NB}}+i_0+i\hfill & \text{if}{N}_{\text{<figure-callout id="2" label="RB UL mod" filenames="DE102020120785A1\_0042.png,DE102020120785A1\_0044.png" state="{{state}}">RB</figure-callout>}}^{\text{UL}}\text{mod}2=1\text{other}{n}_{\text{NB}}<N_{\text{RB}}^{\text{UL}}/2\hfill \\ \mathrm{6th}{n}_{\text{NB}}+i_0+i+1\hfill & \text{if}{N}_{\text{<figure-callout id="2" label="RB UL mod" filenames="DE102020120785A1\_0042.png,DE102020120785A1\_0044.png" state="{{state}}">RB</figure-callout>}}^{\text{UL}}\text{mod}2=1\text{other}{n}_{\text{NB}}\ge N_{\text{RB}}^{\text{UL}}/2\hfill \end{array}$$

have, where $$\begin{array}{l}i=\mathrm{0.1,}...\mathrm{,\; 5}\hfill \\ i_0=\left[\frac{N_{\text{RB}}^{\text{UL}}}{2}\right]-\frac{\mathrm{6th}{\mathrm{<figure-callout\; id="2"\; label="N\; RB\; UL"\; filenames="DE102020120785A1\_0042.png,DE102020120785A1\_0044.png"\; state="\{\{state\}\}">N</figure-callout>}}_{\text{RB}\text{UL}}^{}}{2}\hfill \end{array}.$$

ist ein Breitband als vier nicht überlappende Schmalbänder im Frequenzbereich definiert. Die Gesamtzahl der Uplink-Breitbänder in der Uplink-Übertragungsbandbreite, die in der Zelle eingerichtet ist, ist gegeben durch $N_{\text{WB}}^{\text{UL}}=\left[\frac{N_{\text{NB}}^{\text{UL}}}{4}\right]$

a und die Breitbänder $n_{\text{WB}}=\mathrm{0,}\dots ,N_{\text{WB}}^{\text{UL}}-1$

sind in der Reihenfolge der zunehmenden Schmalbandzahl nummeriert, wobei sich Breitband n_WB aus Schmalband-Indizes 4n_WB+i zusammensetzt, wobei i=0,1....,3. Wenn $N_{\text{NB}}^{\text{UL}}<\mathrm{4,}\text{ dann }{N}_{\text{WB}}^{\text{UL}}=1$

und das einzelne Breitband setzt sich aus dem/den $N_{\text{NB}}^{\text{UL}}$

nicht überlappenden Schmalband(bändern) zusammen.If $N_{\text{NB}}^{\text{UL}}\ge \mathrm{4,}$

Broadband is defined as four non-overlapping narrow bands in the frequency domain. The total number of uplink broadbands in the uplink transmission bandwidth established in the cell is given by $N_{\text{WB}}^{\text{UL}}=\left[\frac{N_{\text{NB}}^{\text{UL}}}{\mathrm{4th}}\right]$

a and the full range drivers $n_{\text{WB}}=\mathrm{0,}...,N_{\text{WB}}^{\text{UL}}-1$

are numbered in the order of the increasing number of narrow bands, where broad band n _{WB is} composed of narrow band indices 4n _WB + i, where i = 0.1 ..., 3. If $N_{\text{NB}}^{\text{UL}}<\mathrm{4,}\text{then}{N}_{\text{WB}}^{\text{UL}}=1$

and the individual broadband is made up of the $N_{\text{NB}}^{\text{UL}}$

non-overlapping narrow band (s) together.

There are several different physical channels and physical signals that are transmitted via RBs and / or individual REs. A physical channel corresponds to a number of REs that carry information from higher layers. UL physical channels can include PUSCH, PUCCH, PRACH and / or any other UL physical channel (s) discussed herein, and DL physical channels can include PDSCH, PBCH, PDCCH and / or any other physical DL discussed herein -Channel / have any other physical DL channels. A physical signal is used by the physical layer (e.g. PHY 1410 of the 14th ), but does not carry any information that originates from higher layers. UL physical signals may include demodulation reference signal (DMRS), phase tracking reference signal (PTRS), SRS and / or other UL physical signals discussed herein, and DL physical signals may include DMRS, PTRS, CSI-RS, primary synchronization signal (PSS ), secondary synchronization signal (SSS), and / or other physical DL signals discussed herein.

The PDSCH transmits user data and higher layer signals to the UEs 801 . As a rule, the DL planning (assignment of control units and shared channel resource blocks to the UE 801 within a cell) at each of the RAN nodes 811 based on channel quality information received from one of the UEs 801 be returned. The downlink resource allocation information can be sent on the PDCCH for each of the UEs 801 is used (e.g. assigned). The PDCCH uses Control Channel Elements (CCEs) to transmit control information (e.g., DCI), and a set of CCEs can be related to a "Control Region". Control channels are formed by aggregating one or more CCEs, with different code rates being implemented for the control channels by aggregating a different number of CCEs. The CCEs are numbered from 0 to N _{CCE, k} -1, where N _{CCE, k} -1 is the number of CCEs in the control region of sub-frame k. Before mapping to REs, the complex-valued PDCCH symbols can first be organized in quadruplets, which can then be permuted with the aid of a sub-block interleaver for rate adaptation. Each PDCCH can be transmitted using one or more of these CCEs, and each CCE can correspond to nine sets of four physical REs, referred to as Resource Element Groups (REGs) become. Four QPSK (Quadrature Phase Shift Keying) symbols can be assigned to each REG. The PDCCH can be transmitted with one or more CCEs depending on the size of the DCI and the channel conditions. Four or more different PDCCH formats with a different number of CCEs can be defined (e.g. aggregation level, L = 1, 2, 4 or 8 in LTE and L = 1, 2, 4, 8 or 16 in NR). The UE 801 monitors a set of PDCCH candidates on one or more activated service-providing cells, as established by higher level signaling for control information (e.g. DCI), which monitoring implies attempting to match each of the PDCCHs (or PDCCH candidates) in the set according to to decode all monitored DCI formats (e.g. DCI formats 0 to 6-2, DCI formats 0_0 to 2_3). The UE 801 monitor (or attempt to decode) appropriate sets of PDCCH candidates in one or more configured monitoring occasions according to the appropriate search space configurations. A DCI carries DL, UL, or SL scheduling information, requests for reports on aperiodic channel quality indicators (CQI), common LAA information, multicast control channel change notifications (MCCH), UL power control commands for a cell and / or a radio network -Temporary Identifier (Radio Network Temporary Identifier - RNTI), notification of a group of UEs 801 via a slot format, notification of a group of UEs via the PRB and OFDM symbol (s), whereby the UE can assume that no transmission is intended for the UE, TPC commands for PUCCH and PUSCH and / or TPC Commands for PUCCH and PUSCH.

Some aspects may use control channel information resource allocation concepts that are an extension of the concepts described above. For example, some aspects may use an EPDCCH that uses PDSCH resources for the transmission of control information. The EPDCCH can be transmitted using one or more Enhanced CCEs (ECCEs). Similar to the above, each ECCE can correspond to nine sets of four physical resource elements called Enhanced REGs (EREGs). An ECCE may have a different number of EREGs in some situations.

As already indicated, the PDCCH can be used to plan DL transmissions on PDSCH and UL transmissions on PUSCH, with the DCI on PDCCH having, among other things, downlink assignments that at least relate to the modulation and coding format, resource assignment and HARQ information included on DL-SCH; and / or uplink scheduling assignments containing at least modulation and coding format, resource assignment and HARQ information related to UL-SCH. In addition to scheduling, the PDCCH can be used for the activation and deactivation of configured PUSCH transmissions with configured assignment, the activation and deactivation of semi-persistent PDSCH transmissions, the notification of one or more UEs 801 be used over a slotted format; Notification of one or more UEs 801 via the PRB (s) and the OFDM symbol (s), where a UE 801 can assume that no transmission is intended for the UE; Transmission of TPC commands for PUCCH and PUSCH; Transmission of one or more TPC commands for SRS transmissions by one or more UEs 801 ; Switching over an active BWP for a UE 801 ; and initiating a random access process.

RBs im Frequenzbereich und $N_{\text{symb}}^{\text{CORESET}}\in \left\{\mathrm{1,2,3}\right\}$

Symbole im Zeitbereich aufweisen. Ein CORESET weist sechs REGs auf, die in aufsteigender Reihenfolge in einer zeitlichen Reihenfolge nummeriert sind, wobei eine REG gleich einem RB während eines OFDM-Symbols ist. Die UEs 801 können mit mehreren CORESETS eingerichtet werden, wobei jeder CORESET nur einer CCE-zu-REG-Abbildung zugeordnet ist. Verschachtelte und nicht verschachtelte CCE-zu-REG-Abbildung werden in einem CORESET unterstützt. Jede REG, die einen PDCCH trägt, trägt seine eigene DMRS.In NR implementations, the UEs monitor 801 corresponding sets of PDCCH candidates in one or more configured monitoring occasions in one or more established control units (core sets - CORESETs) according to the corresponding search space configurations (or attempt to decode them). A CORESET can have a set of PRBs with a duration of 1 to 3 OFDM symbols. A CORESET can additionally or alternatively $N_{\text{RB}}^{\text{CORESET}}$

RBs in the frequency domain and $N_{\text{symb}}^{\text{CORESET}}\in \left\{\mathrm{1,2,3}\right\}$

Have symbols in the time domain. A CORESET has six REGs that are numbered in ascending order in a time sequence, one REG being equal to one RB during an OFDM symbol. The UEs 801 can be set up with several CORESETS, whereby each CORESET is only assigned to one CCE-to-REG mapping. Nested and non-nested CCE-to-REG mapping are supported in a CORESET. Each REG that carries a PDCCH carries its own DMRS.

The UEs communicate according to various aspects 801 and the RAN nodes 811 Data (e.g., sending and receiving) over a licensed medium (also referred to as "licensed spectrum" and / or "licensed tape") and an unlicensed shared medium (also called "unlicensed spectrum" and / or "unlicensed tape" designated). The licensed spectrum can have channels that operate in the frequency range from about 400 MHz to about 3.8 GHz, while the unlicensed spectrum can include the 5 GHz band.

In order to work in the unlicensed spectrum, the UEs 801 and the RAN nodes 811 work with LAA, eLAA and / or feLAA mechanisms. In these implementations, the UEs 801 and the RAN nodes 811 perform one or more known medium and / or carrier detection processes to determine whether one or more channels in the unlicensed spectrum are not available or otherwise occupied prior to transmission in the unlicensed spectrum. The medium / carrier detection operations can be performed according to a Listen Before Talk (LBT) protocol.

LBT is a mechanism in which a device (e.g. the UE 801 RAN node 811 etc.) a medium (e.g. a channel or a carrier frequency) detects and transmits when it is determined that the medium is unused (or when it is determined that a particular channel in the medium is not in use). The medium sensing process may include CCA, which uses at least energy detection (ED) to determine the presence or absence of other signals on a channel to determine whether a channel is busy or idle. This LBT mechanism enables cellular / LAA networks to coexist with established systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a designated transmission band for a specified period of time and comparing the sensed RF energy with a predefined or established threshold.

The established systems in the 5 GHz band are typically WLANs based on IEEE 802.11 technologies. WLAN uses a conflict-based channel access mechanism, the so-called Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). When a WLAN node (e.g. a mobile station (MS) like the UE 801 , AP 806 or similar) intends to transmit, the WLAN node can first perform CCA before the transmission. In addition, a backoff mechanism is used to avoid collisions in situations in which more than one WLAN node perceives the channel as inactive and transmits at the same time. The backoff mechanism can be a counter that is randomly drawn within the Contention Window Size (CWS), which is increased exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some implementations, the LBT method for DL or UL transmission bursts including PDSCH or PUSCH transmissions may have an LAA conflict window, the length of which between the ECCA (Extended Clear Channel Assessment) slots X and Y is variable, where X is and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (µs); however, the size of the CWS and a maximum channel occupancy time (MCOT) (e.g. a transmission burst) may be based on official regulations.

The LAA mechanisms are based on carrier aggregation (CA) technologies from LTE-enhanced systems. According to the CA, each aggregated carrier is referred to as a component carrier (CC). A CC can have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz, and a maximum of five CCs can be aggregated, so that a maximum aggregated bandwidth is 100 MHz. In Frequency Division Duplex (FDD) systems, the number of aggregated carriers for DL and UL may be different, with the number of UL CCs being equal to or less than the number of DL component carriers. In some cases, individual CCs may have a different bandwidth than other CCs. In TDD systems, the number of CCs and BWs of the individual CCs according to DL and UL is usually the same.

CA also has individual service-providing cells to provide individual CCs. The coverage of the supplying cells can differ, for example, because the CCs experience different path losses on different frequency bands. A primary service-providing cell or PCell can provide a PCC for both UL and DL and handle RRC and NAS-related activities. The other service-providing cells are called SCells, and each SCell can provide an individual SCC for both UL and DL. The SCCs can be added and removed as needed, while a change in the PCC is a handover of the UE 801 may require. With LAA, eLAA and further improved Licensed Assisted Access (feLAA), some or all of the SCells can operate in the unlicensed spectrum (according to “LAA-SCells”), and the LAA-SCells are supported by a PCell that operates in the licensed spectrum. If a UE is set up with more than one LAA S cell, the UE can receive UL grants for the LAA S cells set up that indicate different PUSCH start positions within the same sub-frame.

The RAN nodes 811 can be set up to interface with each other 812 to communicate.

In aspects in which the system 800 is a 5G or NR system (e.g. if CN 820 a 5GC 1020 according to 10 is), the interface can 812 an Xn interface 812 be. The Xn interface is defined between two or more RAN nodes 811 (e.g. two or more gNBs and the like) that connect to 5GC 820 establish between a RAN node 811 (e.g. a gNB) that connects to 5GC 820 and an eNB and / or between two eNBs that connect to 5GC 820 produce. In some implementations, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U interface can provide a non-guaranteed delivery of PDUs (User Plane Protocol Data Units) and support / provide functions for data forwarding and control of the data flow. The Xn-C can provide management and error handling functions, functions for managing the Xn-C interface, mobility support for the UE 801 in a connected mode (e.g. CM-CONNECTED) including functions for managing the UE mobility for the connected mode between one or more RAN nodes 811 exhibit. Mobility support can include a conte 13 transfer from an old (source) serving RAN node 811 to a new (target) serving RAN node 811 exhibit; and control of user-level tunnels between an old (source) serving RAN node 811 to a new (target) serving RAN node 811 . A protocol stack of the Xn-U can have a transport network layer that is built on the IP transport layer (Internet Protocol), as well as a GTP-U layer on a UDP (User Datagram Protocol) and / or IP (Internet Protocol) layer (en) to transport user-level PDUs. The Xn-C protocol stack can have a signaling protocol of the application layer (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is based on the Stream Control Transmission Protocol (SCTP). The SCTP can be on an IP layer and guarantee the delivery of messages to the application layer. In the Transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be identical or similar to the user level and / or control unit (s) protocol stack (s) illustrated and described herein.

It is shown that the RAN 810 communicatively to a core network - in this aspect CN 820 - is paired. The CN 820 can be a plurality of network elements 822 that is set up to serve customers / subscribers (e.g. users of the UEs 801 ) via the RAN 810 with the CN 820 are connected to offer various data and telecommunications services. The components of the CN 820 may be implemented in a physical node or in separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some aspects, network functions virtualization (NFV) can be used to virtualize some or all of the network node functions described above via executable instructions stored in one or more computer-readable storage media (described in detail below). A logical instantiation of the CN 820 can be referred to as a network slice, and a logical instantiation of part of the CN 820 can be referred to as a network sub-slice. NFV architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, on physical resources, including a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to perform virtual or reconfigurable implementations of one or more Evolved Packet Core (EPC) components / functions.

In general, the application server can 830 be an element that offers applications that use IP carrier resources with the core network (e.g. UMTS PS domain, LTE PS data services, etc.). The application server 830 can also be set up to provide one or more communication services (e.g. VoIP sessions, PTT sessions, group communication sessions, social network services etc.) for the UEs 801 via the EPC 820 to support.

In aspects, the CN 820 be a 5G core network (5G CN) (also called "5GC 820 “Or similar), and the RAN 810 can via an NG interface 813 with the CN 820 be connected. The NG interface 813 can be divided into two parts, an NG user plane (NG-U) interface 814 , the traffic data between the RAN nodes 811 and a User Plane Function (UPF), and the S1 Control Plane (NG-C) interface 815 that provide a signaling interface between the RAN nodes 811 and the Access and Mobility Management Functions (AMFs). Aspects that the CN 820 around a 5GC 820 acts are in terms of 10 discussed in more detail.

In aspects, the CN 820 be a 5G-CN (also called “5GC 820 “Or similar), while the CN 820 may be an EPC in other aspects). When the CN 820 an EPC (also called "EPC 820 “Or similar), the RAN 810 via an S1 interface 813 with the CN 820 get connected. The S1 -Interface 813 can be split into two parts, an S1 user level (S1-U) interface 814 , which the traffic data between the RAN nodes 811 and the S-GW, and the S1-MME interface 815 that provide a signaling interface between the RAN nodes 811 and represents MMEs.

9 shows an example architecture of a system 900 including a first CN 920 according to various aspects. In this example the system 900 implement the LTE standard, with the core network (CN) 920 an EPC 920 is that of the CN 820 of the 8th corresponds. In addition, the UE 901 same or similar to the UE 801 out 8th be, and the E-UTRAN 910 can be a RAN that is the same or similar to the RAN 810 out 8th and that is the RAN nodes discussed earlier 811 may have. The CN 920 can the MMEs 921 , a serving gateway (S-GW) 922 , a packet data network gateway (P-GW) 923 , a home subscriber server (HSS) 924 and a Serving General Packet Radio Services (GPRS) Support Node (SGSN) 925 exhibit.

The MMEs 921 are similar in function to the control unit of the old SGSN and can implement MM functions to determine the current location of the UE 901 to pursue. The MMEs 921 can carry out various methods of mobility management (MM) in order to manage mobility aspects during access, such as gateway selection and management of tracking area lists. MM (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) can refer to any applicable procedures, methods, data storage, etc. used to establish knowledge of the current location of the UE 901 maintain, provide confidentiality of user identity and / or provide other similar services to users / subscribers. Every UE 901 and the MME 921 may have an MM or EMM sublayer, and an MM context may be in the UE 901 and the MME 921 be set up when an attachment process is successfully completed. The MM context can be a data structure or a database object, the MM-related information of the UE 901 saves. The MMEs 921 can with the HSS 924 via an S6a reference point, with the SGSN 925 via an S3 reference point and with the S-GW 922 be coupled via an S11 reference point.

The SGSN 925 can be a node that owns the UE 901 served by having the location of a single UE 901 tracks and performs security functions. In addition, the SGSN 925 Inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks, packet data network (PDN) and S-GW selection according to the specifications of the MMEs 921 , the handling of time zone functions of the UE 901 according to the specifications of the MMEs 921 and perform the MME selection for handovers to the E-UTRAN 3GPP access network. The S3 reference point between the MMEs 921 and the SGSN 925 can enable the exchange of user and owner information for mobility between 3GPP access networks in idle and / or active states.

The Home Subscriber Server (HSS) 924 may have a database for network users, including subscription-related information to aid in the handling of communication sessions by the network entities. The EPC 920 can be one or more HSS 924 depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, the HSS 924 Provide support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, etc. An S6a reference point between the HSS 924 and the MMEs 921 can transmit subscription and authentication data for authentication / authorization of user access to the EPC 920 between the HSS 924 and the MMEs 921 enable.

The S-GW 922 can use the S1 interface 813 ("S1-U" in 9 ) to the RAN 910 terminate and route data packets between the RAN 910 and the EPC 920 continue. In addition, the S-GW 922 be a local mobility anchor point for handovers between RAN nodes and also provide an anchor for mobility between 3GPPs. Other responsibilities may include lawful interception, charging, and some policy enforcement. The S11 reference point between the S-GW 922 and the MMEs 921 can be a control unit between the MMEs 921 and the S-GW 922 provide. The S-GW 922 can be connected to the P-GW via an S5 reference point 923 be coupled.

The P-GW 923 can be an SGi interface to a PDN 930 to lock. The P-GW 923 can send data packets between the EPC 920 and external networks, such as a network with the application server 830 (alternatively referred to as "AF"), via an IP interface 825 forward (see e.g. 8th ). In a way, the P-GW 923 via an IP communication interface 825 (see e.g. 8th ) communicative with an application server (application server 830 in 8th or PDN 930 in 9 ) coupled. The S5 reference point between the P-GW 923 and the S-GW 922 tunneling at user level and tunnel management between the P-GW 923 and the S-GW 922 provide. The S5 reference point can also be used for relocating the S-GW 922 due to the mobility of the UE 901 be used, and if the S-GW 922 a connection to a non-collocated P-GW for the required PDN connectivity 923 must produce. The P-GW 923 may also have a node for the enforcement of guidelines and the collection of charge data (e.g. PCEF (not shown)). In addition, the SGi reference point between the P-GW 923 and the packet data network (PDN) 930 be an external public, a private PDN or an operator-internal packet data network, e.g. for the provision of IMS services. The P-GW 923 can be connected to a control unit (Policy Control and Charging Rules Function, PCRF) via a Gx reference point 926 be coupled.

PCRF 926 is the policy and fee control unit of the EPC 920 . In a non-roaming scenario, a single PCRF 926 in the Home Public Land Mobile Network (HPLMN) with a session of the Internet Protocol Connectivity Access Network (IP-CAN) of the UE 901 be connected. In a roaming scenario with local traffic breakthrough, there may be two PCRFs that are associated with a UE's IP-CAN session 901 a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Public Land Mobile Network (VPLMN). The PCRF 926 can via the P-GW 923 communicative with the application server 930 be coupled. The application server 930 can the PCRF 926 signal to indicate a new service flow and to select the appropriate quality of service (QoS) and charging parameters. The PCRF 926 this rule can be converted into a strategy and charging enforcement function (Policy and Charging Enforcement Function - PCEF) (not shown) with the corresponding traffic flow template (TFT) and QoS class of identifier (Class of Identifier - QCI ), whereby the QoS and charging according to the specifications of the application server 930 begins. The Gx reference point between the PCRF 926 and the P-GW 923 may allow the QoS policy and accounting rules to be transferred from the PCRF 926 to the PCEF in the P-GW 923 . An Rx reference point can be between the PDN 930 (or "Application Function (AF) 930 “) And the PCRF 926 lie.

10 shows an architecture of a system 1000 including a second CN 1020 according to various aspects. The system 1000 is represented by a UE 1001 that are the same or similar to the UEs discussed above 801 and UE 901 can be; a (R) AN 1010 that are the same or similar to the previously discussed RAN 810 and RAN 910 can be and the previously discussed RAN nodes 811 may contain; and a DN 1003 which may, for example, have operator services, internet access or third-party services; and a 5GC 1020 . The 5GC 1020 an authentication server function (AUSF) 1022 ; an AMF 1021 ; a session management function (SMF) 1024 ; a network exposure function (NEF) 1023 ; a policy control function (PCF) 1026 ; a network function repository function (NRF) 1025 ; uniform data management (UDM) 1027 ; an application function (AF) 1028 ; a user level function (UPF) 1002 ; and a network interface selection function (NSSF) 1029 exhibit.

The UPF 1002 Can be used as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session point to connect to the data network (DN) 1003 and serve as a branch point to support multi-homed PDU sessions. The UPF 1002 can also perform packet routing and forwarding, perform packet inspection, enforce the part of the policy rules for the user level, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS handling for a user level (e.g. packet filtering, gating, UL / DL Rate enforcement), perform uplink traffic check (e.g. SDF-to-QoS flow mapping), perform packet marking on the transport level in the uplink and downlink as well as packet buffering in the downlink and triggering of data notifications in the downlink UPF 1002 may have an uplink classifier that supports the forwarding of traffic flows to a data network. The DN 1003 can represent various network operator services, internet access or third party services. DN 1003 can use the previously discussed application server 830 have or be similar to it. The UPF 1002 can with the SMF 1024 via an N4 reference point between the SMF 1024 and the UPF 1002 to interact.

The AUSF 1022 can provide data to authenticate UE 1001 store and process authentication-related functions. The AUSF 1022 can enable a common authentication framework for different types of access. The AUSF 1022 can with the AMF 1021 via an N12 reference point between the AMF 1021 and the AUSF 1022 communicate; and they can with the UDM 1027 via an N13 reference point between the UDM 1027 and the AUSF 1022 communicate. In addition, the AUSF 1022 have a service-based Nausf interface.

The AMF 1021 can be used for registration management (e.g. for the registration of UE 1001 etc.), connection management, availability management, mobility management and lawful interception of AMF-related events, as well as for access authentication and authorization be responsible. The AMF 1021 can be an end point for the reference point N11 between the AMF 1021 and the SMF 1024 be. The AMF 1021 can transport SM messages between the UE 1001 and the SMF 1024 and act as a transparent proxy for forwarding SM messages. AMF 1021 can also transport SMS messages between the UE 1001 and provide an SMSF (in 10 not shown). AMF 1021 can act as a Security Anchor Function (SEAF) that allows interaction with the AUSF 1022 and the UE 1001 , the receipt of an intermediate key as a result of the authentication process of the UE 1001 has been set. If the authentication based on the Universal Subscriber Identity Module (USIM) is used, the AMF 1021 the security material from the AUSF 1022 recall. AMF 1021 can also have an SCM function (Security Context Management), which receives a key from the SEAF, which it uses to derive network access-specific keys. In addition, the AMF 1021 be an endpoint of a RAN control unit that has an N2 reference point between the (R) AN 1010 and the AMF 1021 may have or be such; and the AMF 1021 can be an endpoint of NAS (N1) signaling and perform NAS encryption and integrity protection.

AMF 1021 can also do NAS signaling with a UE 1001 support via an N3 Interworking Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. N3IWF can be an endpoint for the N2 interface between the (R) AN 1010 and the AMF 1021 for the control and an end point for the N3 reference point between the (R) AN 1010 and the UPF 1002 for the user level. As such, the AMF 1021 the N2 signaling from the SMF 1024 and the AMF 1021 for PDU sessions and QoS, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 packets of the user level in the uplink and QoS according to the N3 packet marking, taking into account the QoS requirements associated with this marking received via N2 are, enforce. N3IWF can also send NAS signals from the uplink and downlink control unit between the UE 1001 and the AMF 1021 via an N1 reference point between the UE 1001 and the AMF 1021 Forward and uplink and downlink user plane packets between the UE 1001 and the UPF 1002 hand off. The N3IWF also provides mechanisms for setting up the IPsec tunnel with the UE 1001 ready. The AMF 1021 may have a service based Namf interface and may be a termination point for an N14 reference point between two AMFs 1021 and an N17 reference point between the AMF 1021 and a 5G device identity register (5G-EIR) (in 10 not shown).

The UE 1001 may need to contact the AMF 1021 register in order to receive network services. The registration management (RM) becomes the registration or deregistration of the UE 1001 in the network (e.g. AMF 1021 ) and to set up a UE context in the network (e.g. AMF 1021 ) is used. The UE 1001 can operate in an RM REGISTERED state or an RM DEREGISTERED state. The UE is in the RM-DEREGISTRATED state 1001 not registered on the network, and the UE context in AMF 1021 does not contain valid location or routing information for the UE 1001 so that the UE 1001 for the AMF 1021 is not reachable. The UE is in the RM REGISTERED state 1001 registered in the network, and the UE context13 in AMF 1021 can provide a valid location or routing information for the UE 1001 included so that the UE 1001 from the AMF 1021 is attainable. In the RM REGISTERED state, the UE 1001 perform procedures for updating the mobility registration, perform periodic procedures for updating the registration triggered by the expiration of the periodic update timer (e.g. to notify the network that the UE 1001 still active) and perform a registry update process to update UE capability information or renegotiate protocol parameters with the network.

The AMF 1021 can have one or more RM contexts for the UE 1001 with each RM context associated with a specific access to the network. The RM context can be a data structure, a database object, etc. which, among other things, displays or stores a registration status per access type and the periodic update timer. The AMF 1021 can also store a 5GC-MM context which can be identical or similar to the (E) MM context discussed above. In various aspects, the AMF 1021 a CE mode B restriction parameter of the UE 1001 Save in an associated MM context or RM context. The AMF 1021 If necessary, can also derive the value from the UE usage setting parameters of the UE already stored in the UE context (and / or MM / RM context).

Connection Management (CM) can be used to establish a signaling connection between the UE 1001 and the AMF 1021 to be established and released via the N1 interface. The signaling link is used to facilitate the NAS signal exchange between the UE 1001 and the CN 1020 to enable, and assigns both the signaling connection between the UE and the AN (e.g. RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 1001 between the AN (e.g. RAN 1010 ) and the AMF 1021 on. The UE 1001 can work in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. If the UE 1001 is operated in the CM-IDLE state / mode, the UE 1001 no NAS signal connection with the AMF 1021 via the N1 interface, and an (R) AN 1010 signal connection (eg N2 and / or N3 connections) for the UE 1001 consist. If the UE 1001 is operated in CM-CONNECTED state / mode, the UE 1001 an established NAS signaling connection with the AMF 1021 via the N1 interface, and an (R) AN 1010 signaling connection (eg N2 and / or N3 connections) for the UE 1001 to be available. Establishing an N2 connection between the (R) AN 1010 and the AMF 1021 can lead to the UE 1001 passes from CM-IDLE mode to CM-CONNECTED mode, and the UE 1001 can switch from CM-CONNECTED mode to CM-IDLE mode if the N2 signaling between the (R) AN 1010 and the AMF 1021 will be annulled.

The SMF 1024 can be responsible for the session management (SM) (e.g. session establishment, modification and release, including maintaining tunnels between UPF and AN nodes); Assignment and management of IP addresses of the UE (including optional authorization); Selection and control of the function of the user level (UP) (UPF); Set up traffic control at the UPF to direct traffic to the correct destination; Termination of interfaces to policy control functions; Control of part of the policy enforcement and QoS; lawful interception (for SM events and interface to the LI system); Termination of SM parts of NAS messages; Downlink data notification; Initiation of AN-specific SM information that is sent to AN via AMF via N2; and determining the session and service continuity (SSC) mode of a session. SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU connectivity service that enables the exchange of PDUs between the UE 1001 and a data network (DN) 1003 , which is identified by a data network name (DNN), provides or enables. PDU sessions can be initiated at the request of UE 1001 set up on request from UE 1001 and 5GC 1020 modified and on request from UE 1001 and 5GC 1020 using NAS-SM signaling via the N1 reference point between the UE 1001 and the SMF 1024 is exchanged, be released. Upon request from an application server, the 5GC 1020 a particular application in the UE 1001 trigger. In response to receiving the trigger message, the UE 1001 the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 1001 hand off. The identified application (s) in the UE 1001 can set up a PDU session to a specific DNN. The SMF 1024 can check whether the UE 1001 -Requirements with the with the UE 1001 associated user subscription information is compliant. In this context, the SMF 1024 Update notifications for subscription data at SMF 1024 level from UDM 1027 retrieve and / or request.

The SMF 1024 can roam: handle local enforcement to apply QoS Service Level Agreements (SLAs) (VPLMN); Data Collection and Calculation Fee Collection Interface (VPLMN); lawful interception (in the VPLMN for SM events and interface to the LI system); and support of the interaction with external DN for the transport of signaling for the authorization / authentication of PDU sessions by external DN. An N16 reference point between two SMFs 1024 can in the system 1000 that in roaming scenarios between another SMF 1024 in a visited network and the SMF 1024 can be in the home network. In addition, the SMF 1024 have the service-based nsmf interface.

The NEF 1023 can provide means to securely provide the services and capabilities that 3GPP network functions for third parties, internal detection / recovery, application functions (e.g. AF 1028 ), Edge computing or fog computing systems, etc. can be provided. With these aspects in mind, the NEF 1023 authenticate, authorize and / or throttle the application functions (AFs). NEF 1023 can also with the AF 1028 Translate exchanged information and information exchanged with internal network functions. For example, the NEF 1023 Translate between an AF service identification and internal 5GC information. NEF 1023 can also receive information from other network functions (NFs) based on the disclosed capabilities of other network functions. This information can be found on the NEF 1023 as structured data or in a data storage network function (NF) using standardized interfaces. The stored information can then be used by the NEF 1023 re-exposed to other NFs and NFs and / or used for other purposes such as analysis. In addition, the NEF 1023 have an Nnef service based interface.

The NRF 1025 can support functions for service detection, receive NF detection requests from NF entities and provide the information of the detected NF entities to the NF entities. The NRF 1025 also manages information about available NF instances and the services they support. The terms “instantiate”, “instantiate” and the like used here can refer to the creation of an instance, and an “instance” can refer to a specific occurrence of an object, which can occur, for example, during the execution of program code. In addition, the NRF 1025 have the service-based Nnrf interface.

The PCF 1026 can provide policy rules to control the control unit (s) in order to enforce them, and it can also support a unified policy framework for controlling network behavior. The PCF 1026 can also implement a FE to access subscription information used for policy making in a UDR of the UDM 1027 are relevant. The PCF 1026 can with the AMF 1021 via an N15 reference point between the PCF 1026 and the AMF 1021 communicate that a PCF 1026 in a visited network and the AMF 1021 in the case of roaming scenarios. The PCF 1026 can with the AF 1028 via an N5 reference point between the PCF 1026 and the AF 1028 communicate; and with the SMF 1024 via an N7 reference point between the PCF 1026 and the SMF 1024 . The system 1000 and / or CN 1020 can also have an N24 reference point between the PCF 1026 (in the home network) and a PCF 1026 in a visited network. In addition, the PCF 1026 have a service-based npcf interface.

The UDM 1027 can process subscription-related information to aid in the handling of communication sessions by the network entities and can process subscription data from UE 1001 to save. For example, subscription data can be shared between the UDM 1027 and the AMF 1021 via an N8 reference point between the UDM 1027 and the AMF. The UDM 1027 can have two parts, an application front end (FE) and a unified data repository (UDR) (FE and UDR are in 10 not shown). The UDR can store subscription data and policy data for the UDM 1027 and the PCF 1026 and / or structured data for exposure and application data (including packet flow descriptions - PFDs) for application recognition, application request information for multiple UEs 1001 ) for the NEF 1023 to save. The interface based on the Nudr service can be used by the UDR 221 are presented to the UDM 1027 , PCF 1026 and NEF 1023 allow access to a specific set of the stored data as well as reading, updating (e.g. adding, changing), deleting and subscribing to the notification of relevant data changes in the UDR. The UDM may have a UDM FE that is responsible for processing credentials, location management, subscription management, and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs the processing of authentication credentials, the handling of the user identification, the access authorization, the registration / mobility management and the subscription management. The UDR can work with the SMF 1024 via an N10 reference point between the UDM 1027 and the SMF 1024 to interact. UDM 1027 can also support SMS management, with an SMS VU implementing the similar application logic as discussed above. In addition, the UDM 1027 have the nudm service based interface.

The AF 1028 can provide application influence on traffic routing, provide access to the NCE, and interact with the controller for policy control. The NCE can be a mechanism that allows the 5GC 1020 and the AF 1028 allows each other information about NEF 1023 that can be used for edge computing implementations. In such implementations, the services of the network operator and third parties in the vicinity of the service access point UE 1001 be accommodated in order to achieve efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can use a UPF 1002 near the UE 1001 choose and control the traffic from the UPF 1002 up to DN 1003 Execute via the N6 interface. This can be done on the subscription data of the UE, the location of the UE and that of the AF 1028 information provided. In this way the AF 1028 Influence the UPF (re-) selection and traffic routing. Based on the provision by the network operator, the network operator can, if AF 1028 is considered a trustworthy entity, the AF 1028 allow you to interact directly with the relevant NFs. In addition, the AF 1028 have a service-based NAF interface.

NSSF 1029 can have a number of network interface instances for the UE 1001 choose. The NSSF 1029 can also determine the permitted NSSAI and the assignment to the subscribed S-NSSAIs if necessary. The NSSF 1029 can also determine the AMF rate used to operate the UE 1001 used or a list of AMF candidates 1021 based on appropriate configuration and possibly by querying the NRF 1025 . The selection of a set of intersection entities for the UE 1001 can through the AMF 1021 , where the UE 1001 is registered through interaction with the NSSF 1029 triggered, resulting in a change in the AMF 1021 can lead. The NSSF 1029 can with the AMF 1021 via an N22 reference point between AMF 1021 and NSSF 1029 to interact; and she can be with another NSSF 1029 Communicate in a visited network via an N31 reference point (not through 10 shown). In addition, the NSSF 1029 have a service-based nnssf interface.

As mentioned earlier, the CN 1020 have an SMS function (SMSF) responsible for checking and verifying SMS subscriptions and forwarding SM messages to / from the UE 1001 to / from other locations, such as an SMS-GMSC / IWMSC / SMS router, can be responsible. The SMS can also be sent with AMF 1021 and UDM 1027 for a notification procedure that the UE 1001 is available for SMS transmission (e.g. setting a UE not reachable flag and notifying UDM 1027 when the UE 1001 is available for SMS).

The CN 820 may have other elements that are included in 10 not shown, such as a data storage system / a data storage architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP) and the like. The data storage system can have a structured data storage function (SDSF), an unstructured data storage network function (UDSF) and / or the like. Each NF can transfer unstructured data to / from the UDSF (e.g. UE contexts) via the N18 reference point between each NF and the UDSF (not through 10 shown) save and retrieve. Individual NFs can share a UDSF to store their respective unstructured data, or individual NFs can each have their own UDSF, which is located at or near the individual NFs. In addition, the UDSF can have a service-based Nudsf interface (in 10 not shown). The 5G EIR can be an NF that checks the status of Permanent Equipment Identifiers (PEIs) to determine if certain devices / units have been blacklisted by the network; and the SEPP can be a non-transparent proxy that takes over the hiding of the topology, the filtering of messages and the control of inter-PLMN control units.

In addition, there can be many more reference points and / or service based interfaces between the NF services in the NFs; however, for the sake of clarity, these interfaces and reference points have been included in 10 omitted. In one example, the CN 1020 have an Nx interface, which is an inter-CN interface between the MME (e.g. MME 921 ) and the AMF 1021 is a collaboration between CN 1020 and CN 920 to enable. Further example interfaces / reference points may include a service-based N5g-EIR interface that includes a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network, and an N31 reference point between the NSSF in the visited network and the NSSF in the Has home network.

11 shows an example of the infrastructure equipment 1100 according to various aspects. The infrastructure equipment 1100 (or "System 1100 “) Can be used as a base station, radio head, RAN node like the previously shown and described RAN nodes 811 and / or AP 806 , Application server 830 and / or any other element / device discussed herein. In other examples, the system could 1100 implemented in or by a UE.

The system 1100 instructs the application circuit 1105 , the baseband circuit 1110 , one or more radio front end modules (RFEMs) 1115 , the memory circuit 1120 , the power management integrated circuit (PMIC) 1125 , the power tee circuit 1130, the network control unit 1135 , the network interface connector 1140 , the satellite positioning circuit 1145 and the user interface 1150 on. In some aspects the device can 1100 have additional elements, such as memory / archive storage, display, camera, sensor or input / output interface (I / O). In other aspects, the components described below can be included in more than one device. For example, the mentioned circuits can have separately in more than one device for CRAN, vBBU or other similar implementations.

Application circuits 1105 have circuits such as, but not limited to, one or more processors (or processor cores), cache memories and one or more low drop-out voltage regulators (LDOs), interrupt controls, serial interfaces such as serial peripheral interfaces (SPIs) ), I2C or universal programmable serial interface modules, real-time clock (RTC), timer counters including interval and watchdog timers, general-purpose input / output (I / O or IO), control units for memory cards such as Secure Digital (SD) MultiMediaCard ( MMC) or similar, Universal Serial Bus (USB) - Interfaces, MIPI (Mobile Industry Processor Interface), and JTAG (Joint Test Access Group) test access ports. The processors (or cores) of the application circuit 1105 may be coupled to or have storage / archive storage elements and are configured to execute instructions stored in the storage / archive storage with various applications or operating systems on the system 1100 can be executed. In some implementations, the storage / archival storage elements can be on-chip storage circuits that can include suitable volatile and / or non-volatile storage such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state storage, and / or any other type of memory device technology such as those discussed here.

The processor (s) of the application circuit 1105 can, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more RISC processors (RISC = Reduced Instruction Set Computing), one or more ARM processors (ARM = Acorn RISC Machine), one or more CISC processors (Complex Instruction Set Computing), one or more digital signal processors (DSP), one or more FPGAs (Field Programmable Gate Arrays), one or more programmable logic components (PLDs), one or more application specific integrated circuits (ASICs), one or more microprocessors or control units, or a suitable combination thereof. In some aspects, the application circuit 1105 comprise or be a special purpose processor / controller operating in accordance with the various aspects set forth herein. As examples, the processor (s) of the application circuit 1105 one or more Pentium® processor (s), Intel® CoreTM processor (s) or Intel® Xeon® processor (s) and / or similar. Intel, Pentium, Intel Core and Xeon are trademarks of Intel Corporation or its subsidiaries. In some aspects the system uses 1100 possibly not the application circuit 1105 and instead may have a special purpose control unit to process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuit 1105 have one or more hardware accelerators, which can be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators can have, for example, computer vision (CV) and / or deep learning (DL) accelerators. The programmable processing components can be, for example, one or more FPDs (Field-Programmable Devices) such as Field-Programmable Gate Arrays (FPGAs) and the like, programmable logic components (PLDs) such as complex PLDs (CPLDs), high-performance PLDs (HCPLDs) and the like, ASICs such as structured ASICs and the like, programmable SoCs (PSoCs) and the like. In such implementations, the application circuit 1105 Include logic blocks or a logic structure and other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, etc. of the various aspects discussed herein. In such aspects, the circuit may be the application circuit 1105 Have memory cells (e.g. erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g. static memory with random access (SRAM), anti-fuses, etc.) that are used to store logic blocks, logical Structure, data, etc. in look-up tables (LUTs) and the like.

The baseband circuit 1110 can for example be designed as a soldering substrate that has one or more integrated circuits (ICs), as a single packaged integrated circuit that is soldered to a main circuit board, or as a multi-chip module that contains two or more integrated circuits. The various electronic hardware elements of the baseband circuit 1110 are further below in relation to 13 discussed.

The user interface circuit 1150 may have one or more user interfaces designed to facilitate the user's interaction with the system 1100 enable, or interfaces for peripheral components, which are designed in such a way that they allow the interaction of peripheral components with the system 1100 enable. User interfaces can include one or more physical or virtual buttons (e.g., a reset button), one or more displays (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, speakers, or others sound devices, microphones, a printer, a scanner, a headset, a screen or a display device, etc. Peripheral component interfaces can include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, a power interface, and so on.

The radio front-end modules (RFEMs) 1115 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs can be physically separate from the mmWave-RFEM. The RFICs can have connections to one or more antennas or antenna arrays (see, for example, antenna array 1311 in 13 ), and the RFEM can be connected to several antennas. In alternative implementations, both mmWave and sub-mmWave radio functions can be used in the same physical RFEM 1115 which includes both mmWave antennas and sub-mmWave.

The memory circuit 1120 may include one or more volatile memories including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), as well as non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. and may include Intel® 3D XPOINTTM technology. Intel and 3D XPoint are trademarks of Intel Corporation or its subsidiaries. The memory circuit 1120 can be implemented according to one or more solder packaged integrated circuits, socketed memory modules, and plug-in memory cards.

The PMIC 1125 may include voltage regulators, surge protectors, circuitry to detect power alarms, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuit can detect one or more brown break (undervoltage) and overvoltage (overvoltage) states. The power supply T-power supply 1130 can provide electrical power from a network cable to provide both power and data connectivity for infrastructure equipment 1100 provided via a single cable.

The network control circuit 1135 can provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or any other suitable protocol. Network connectivity can be to / from the infrastructure equipment 1100 via the network interface connection 1140 may be provided using a physical connection which may be electrical (commonly referred to as a “copper connection”), optical, or wireless. The network control unit 1135 may have one or more dedicated processors and / or FPGAs to communicate using one or more of the above protocols. In some implementations, the network controller circuit can 1135 have multiple control units to provide connectivity to other networks using the same or different protocols.

The positioning circuit 1145 comprises a circuit for receiving and decoding signals transmitted / broadcast by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou navigation satellite system, a regional navigation system, or a GNSS expansion system (e.g., navigation with Indian constellation (NAVIC), Japan's quasi-zenith satellite system (QZSS), France's Doppler orbitography and satellite-based radio positioning (DORIS), etc.), or the like. The positioning circuit 1145 has various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communication) to communicate with components of a positioning network such as navigation satellite constellation nodes. In some aspects the positioning circuit 1145 have a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master clock to perform position tracking / estimation without GNSS support. The positioning circuit 1145 can also be part of the baseband circuit 1110 and / or the RFEMs 1115 or interact with them to communicate with the nodes and components of the positioning network. The positioning circuit 1145 can also include position data and / or time data for the application circuit 1105 provide this data for synchronizing operations with various infrastructures (e.g. RAN nodes 811 etc.) or the like.

In the 11 The components shown can communicate with one another via interface circuits that can have any number of bus and / or interconnect technologies (IX), such as industry standard architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI Express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, for example in a SoC-based System is used. Other Bus / IX systems may have other Bus / IX systems, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus.

12 shows an example of a platform 1200 (or "Device 1200 “) According to various aspects. According to various aspects, the computer platform 1200 for use as a UE 801 , 901 , 1001 , Application server 830 and / or any other element / device discussed herein may be suitable. The platform 1200 can have any combination of the components shown in the example. The components of the platform 1200 can be integrated circuits (ICs), parts thereof, discrete electronic devices or other modules, logic, hardware, software, firmware, or a combination thereof, adapted to the computer platform 1200 , or as components that are otherwise integrated into a housing of a larger system. The block diagram of 12 is intended to be a view of the components of the computer platform 1200 show at high level. However, some of the illustrated components may be omitted, additional components may be included, and a different arrangement of the illustrated components may appear in other implementations.

The application circuit 1205 has circuits such as, but not limited to, one or more processors (or processor cores), cache memories and one or more LDOs, interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface modules, RTC, timer counters including interval and watchdog timers, general purpose I / O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces and JTAG test access ports. The processors (or cores) of the application circuit 1205 may be coupled to storage / archive storage elements or comprise storage / archive storage elements and are arranged to execute commands stored in the storage / archive storage with various applications or operating systems on the system 1200 can be executed. In some implementations, the memory / storage elements may be on-chip memory circuits that may include suitable volatile and / or non-volatile memories, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology such as those discussed here.

The processor (s) of the application circuit 1105 For example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more digital signal processors (DSPs) , one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or control units, a multithreaded processor, an ultra-low voltage processor, an embedded processor, another known processing element, or a suitable combination thereof. In some aspects, the application circuit 1105 comprise or be a special purpose processor / controller operating in accordance with the various aspects set forth herein.

As examples, the processor (s) of the application circuit 1205 have a platform based on the Intel® Core ™ processor, such as the Intel® Quark ™ processor, the Intel Atom® processor, the Intel® Core ™ i3 processor, the Intel® Core ™ i5 processor, the Intel® Core ™ i7 processor or an MCU-class processor or similar. Intel, Intel Core, Quark and Intel Atom are trademarks of Intel Corporation or its subsidiaries. In some implementations, the application circuit 1205 Be part of a system on a chip (SoC) that houses the application circuitry 1205 and other components are molded into a single integrated circuit or package, such as the Intel® Edison or Intel Galileo SoC boards from Intel® Corporation.

Additionally or alternatively, the application circuit 1205 Have circuits such as, for example, but not limited to, one or more FPDs (Field-Programmable Devices) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs) and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs) and the like. In such aspects, the circuit may be the application circuit 1205 Have logic blocks or a logic structure and other interconnected resources that can be programmed to perform various functions, such as the procedures, methods, functions, etc., of the various aspects discussed herein. In such aspects, the circuit of the application circuit 1205 Have memory cells (e.g. erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g. static memory with random access (SRAM), anti-fuses, etc.) that are used to store logic blocks, logical Structure, data, etc. in look-up tables (LUTs) and the like.

The baseband circuit 1210 can for example be designed as a soldering substrate that has one or more integrated circuits, as a single packaged integrated circuit that is soldered to a main circuit board, or as a multi-chip module that contains two or more integrated circuits. The various electronic hardware elements of the baseband circuit 1210 are further below in relation to 13 discussed.

The RFEMs 1215 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs can be physically separate from the mmWave-RFEM. The RFICs can have connections to one or more antennas or antenna arrays (see, for example, antenna array 1311 in 13 ), and the RFEM can be connected to several antennas. In alternative implementations, both mmWave and sub-mmWave radio functions can be used in the same physical RFEM 1215 which includes both mmWave antennas and sub-mmWave.

The memory circuit 1220 can have any number and type of memory modules that are used to provide a certain amount of system memory. For example, the memory circuit 1220 one or more volatile memories including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory) ), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc. The memory circuit 1220 can be developed according to a JEDEC design (Joint Electron Devices Engineering Council) based on LPDDRs (Low Power Double Data Rate), such as LPDDR2, LPDDR3, LPDDR4 or the like. The memory circuit 1220 Can be used as one or more solderable integrated circuits, single-die-housing (SDP), dual-die-housing (DDP) or quad-die-housing (Q17P), socketed memory modules, dual-inline memory modules (DIMMs) including microDIMMs or MiniDIMMs can be implemented and / or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuit can 1220 an on-die memory or register associated with the application circuit 1205 are connected. In order to provide permanent storage of information such as data, applications, operating systems, etc., the memory circuit 1220 have one or more mass storage units, which can include a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro-HDD, resistance change memory, phase change memory, holographic memory or chemical memory, among other things. For example, the computer platform 1200 contain the Intel® 3D XPOINTTM technology. Intel and 3D XPoint are trademarks of Intel Corporation or its subsidiaries.

The replaceable memory circuit 1223 may include devices, circuits, housings, connectors or sockets, etc., that are used to couple portable data storage devices to the platform 1200 be used. These portable data storage devices can be used for mass storage purposes and can include, for example, flash memory cards (e.g. Secure Digital (SD) cards, microSD cards, xD picture cards and the like) as well as USB flash drives, optical disks, external hard drives and the like.

The platform 1200 can also have an interface circuit (not shown) for connecting external devices to the platform 1200 is used. The external devices that interface with the platform 1200 are connected, have the sensor circuit 1221 and the electro-mechanical components (EMCs) 1222 as well as removable storage devices that use the removable storage circuit 1223 are coupled.

The sensor circuit 1221 comprises devices, modules or subsystems, the purpose of which is to detect events or changes in their environment and to send the information (sensor data) about the detected events to another device, module, subsystem, etc. Examples of such sensors include, but are not limited to, Inertial Measurement Units (IMUs) including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes and / or magnetometers; Level sensors; Flow sensors; Temperature sensors (e.g. thermistors); Pressure sensors; barometric pressure sensors; Gravimeter; Altimeter; Image capture devices (e.g. cameras or lensless bezels); Light detection and distance sensors (LiDAR); Proximity sensors (for example infrared radiation detectors and the like), depth sensors, ambient light sensors, ultrasonic transmitters / receivers; Microphones or other similar audio capture devices; etc.

EMCs 1222 have devices, modules or subsystems, the purpose of which is the platform 1200 to enable them to change their state, their position and / or orientation or to move or control a mechanism or a (sub) system. In addition, EMCs 1222 be set up to generate messages / signals and to other components of the platform 1200 to send a current state of the EMC 1222 to display. Examples of EMC 1222 have one or more circuit breakers, relays including electromechanical relays (EMR) and / or semiconductor relays (SSR), actuators (e.g. valve actuators, etc.), an acoustic sound generator, an optical warning device, motors (e.g. DC motors, stepper motors, etc.), wheels, thrusters , Propellers, claws, clamps, hooks and / or other electromechanical components. The platform 1200 is set up to accommodate one or more EMCs 1222 based on one or more sensed events and / or instructions or controls received from a service provider and / or various customers.

In some implementations, the interface circuit may be the platform 1200 with the positioning circuit 1245 connect. The positioning circuit 1245 comprises circuits for receiving and decoding signals that are sent / transmitted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include the GPS of the United States, GLONASS of Russia, the Galileo system of the European Union, the BeiDou navigation satellite system of China, a regional navigation system or GNSS extension system (e.g. NAVIC), QZSS of Japan, DORIS of France, etc. ) or the like. The positioning circuit 1245 has various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communication) to communicate with the components of a positioning network, such as the constellation node of a navigation satellite. In some aspects the positioning circuit 1245 have a micro PNT IC that uses a master clock to perform position tracking / estimation without GNSS support. The positioning circuit 1245 can also be part of the baseband circuit 1110 and / or the RFEMs 1215 or interact with them to communicate with the nodes and components of the positioning network. The position determination circuit 1245 can also include position data and / or time data for the application circuit 1205 provide that can use this data to synchronize operations with various infrastructures (e.g. radio base stations), for tum-by-tum navigation applications or the like.

In some implementations, the interface circuit may be the platform 1200 with the NFC circuit (near-field communication) 1240 connect. The NFC circuit 1240 is configured to provide non-contact near field communication based on radio frequency identification standards (RFID), where magnetic field induction is used to facilitate communication between the NFC circuit 1240 and NFC-enabled devices external to the platform 1200 to enable (e.g. an "NFC touchpoint"). The NFC circuit 1240 has an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller can be a chip / IC that controls the NFC circuit 1240 Provides NFC functionality by running the NFC controller firmware and an NFC batch. The NFC stack can be run by the processor to control the NFC controller and the NFC controller firmware can be run by the NFC controller to control the antenna element to receive short range RF signals sends out. The RF signals can power a passive NFC tag (such as a microchip embedded in a sticker or armband) to send stored data to the NFC circuit 1240 to transfer, or data transfer between the NFC circuit 1240 and another active NFC device (e.g. a smartphone or an NFC-enabled POS terminal) that is near the platform 1200 initiate.

The driver circuit 1246 may have software and hardware elements that are used to control certain devices that are in the platform 1200 embedded on the platform 1200 connected or otherwise communicative with the platform 1200 are coupled. The driver circuit 1246 may have individual drivers that are different from other components of the platform 1200 allow using different input / output devices (I / O devices) within the platform 1200 exist or be connected to it, interact with it or control it. For example, the driver circuit 1246 have a display driver to control a display device and to enable access to it, a touchscreen driver to a touchscreen interface of the platform 1200 to control and enable access to it, sensor drivers, to take sensor readings of the sensor circuit 1221 to get and the sensor circuit 1221 to control and enable access to EMC drivers, to actuator positions of EMCs 1222 to get and / or the EMCs 1222 to control and enable access to it, a camera driver to control an embedded image capture unit and to enable access to it, audio drivers to control one or more audio devices and to enable access to it.

The integrated power management circuit (PMIC) 1225 (Also called "performance management circuit." 1225 “Denoted) can manage the performance of the various components of the platform 1200 is made available. Especially with regards to baseband switching 1210 can the PMIC 1225 take control of power source selection, voltage scaling, battery charging, or direct current (DC) to DC conversion. The PMIC 1225 can often be included when the platform 1200 with a battery 1230 can be operated, e.g. if the device is in a UE 801 , 901 , 1001 is included.

In some aspects, the PMIC 1225 various power saving mechanisms of the platform 1200 control or otherwise be part of it. When the platform 1200 is in an RRC_Connected state, for example, in which it is still connected to the RAN node, since it expects to receive data traffic shortly, it can enter a state after a period of inactivity known as Discontinuous Reception Mode (DRX) referred to as. In this state the platform can 1200 switch off for short time intervals and thus save electricity. If there is no traffic activity for an extended period of time, the platform can 1200 Go into an RRC idle state in which it interrupts the connection to the network and does not perform any operations such as channel quality feedback, handover, etc. The platform 1200 goes into a very low power state and paging, where it periodically wakes up to eavesdrop on the network and then switches off again. In this state the platform receives 1200 possibly no data; to receive data, it changes back to the RRC_Connected state. An additional power-saving mode can allow a device to be unavailable to the network for longer periods than a paging interval (from seconds to a few hours). During this time, the device can be completely inaccessible to the network and shut down completely. Any data sent during this time will result in a large delay, and this delay is assumed to be acceptable.

One battery 1230 can the platform 1200 power although the platform 1200 may, in some examples, be mounted in a fixed location and have a power supply coupled to the utility grid. With the battery 1230 it can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery can 1230 be a typical lead-acid automotive battery.

In some implementations, the battery can 1230 be an "intelligent battery" that has a battery management system (BMS) or an integrated battery monitoring circuit or is coupled to it. The BMS can be in the platform 1200 be included to the state of charge (SoCh) of the battery 1230 to pursue. The BMS can monitor other parameters of the battery 1230 can be used to provide failure predictions such as the state of health (SoH) and health (SoF) of the battery 1230 . The BMS can take the information from the battery 1230 to the application circuit 1205 or other components of the platform 1200 to transfer. The BMS can also have an analog-to-digital converter (ADC) which it provides to the application circuit 1205 allows the voltage of the battery 1230 or the current flow from the battery 1230 monitor directly. The battery parameters can be used to determine the actions of the platform 1200 can perform, such as transmission frequency, network operation, sampling frequency and the like.

A power block or other grid-connected power supply can be coupled to the BMS to power the battery 1230 to load. In some examples, the XS30 power block can be replaced by a wireless power receiver to receive power wirelessly, for example through a loop antenna in the computer platform 1200 . In these examples, a wireless battery charger circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 1230 and thus depend on the electricity required. Charging can be done with the Airfuel standard published by the Airfuel Alliance, the Qi standard for wireless charging published by the Wireless Power Consortium or the Rezence charging standard published by the Alliance for Wireless Power.

The user interface circuit 1250 has various input / output (I / O) devices within the platform 1200 present or connected to this, and has one or more user interfaces that allow the user to interact with the platform 1200 are intended to enable and / or interfaces for peripheral components that allow the peripheral components to interact with the platform 1200 should enable. The user interface circuit 1250 has an input device circuit and an output device circuit. The input device circuitry includes any physical or virtual means for accepting input, including one or more physical or virtual ones Buttons (for example a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, microphones, a scanner, a headset and / or the like. The circuit of the output device has all physical or virtual means to display information or otherwise transmit information, such as sensor values, actuator positions or other similar information. The circuitry of the output device can have any number and / or combination of audio or visual displays, including but not limited to one or more simple visual outputs / displays (e.g. binary status displays (e.g. light emitting diodes (LEDs)) and multi-digit visual outputs or more complex outputs such as Display devices or touch screens (e.g. liquid crystal displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects and the like through the operation of the platform 1200 is created or produced. The circuit of the output device can also have loudspeakers or other sound-output devices, printers and / or the like. In some aspects, the sensor circuit 1221 can be used as an input device circuit (e.g. an image recording device, motion recording device or the like) and one or more EMCs can be used as an output device circuit (e.g. an actuator to provide haptic feedback or the like). In another example, an NFC circuit having an NFC control unit coupled to an antenna element and a processing device may be included for reading electronic tags and / or for connection to another NFC-enabled device. Peripheral component interfaces can include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc., among others.

Although not shown, the components of the platform 1200 Communicate with each other using a suitable bus or interconnect technology (IX) which can have any number of technologies including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay System or any number of other technologies. The bus / IX can be a proprietary bus / IX that is used, for example, in a SoC-based system. Other Bus / IX systems may have other Bus / IX systems, such as e.g. B. an I2C interface, an SPI interface, point-to-point interfaces and a power bus, among others.

13 shows example components of the baseband circuit 1310 and the radio front-end module (RFEM) 1315 according to various aspects. The baseband circuit 1310 corresponds to the baseband circuit 1110 and 1210 of the 11 and 12 . The RFEM 1315 corresponds to the RFEM 1115 and 1215 of the 11 or. 12 . As shown, the RFEMs 1315 the high frequency circuit 1306 , the front-end module circuit 1308 and the antenna array 1311 which are coupled to one another at least as shown.

The baseband circuit 1310 comprises a circuit and / or control unit which is configured to carry out various radio / network protocol and radio control functions that enable communication with one or more radio networks via the RF circuit 1306 enable. The radio control functions may include, but are not limited to, signal modulation / demodulation, coding / decoding, radio frequency shifting, etc., among others. In some aspects, the modulation / demodulation circuit can be the baseband circuit 1310 Have Fast Fourier Transform (FFT), precoding or constellation mapping / decoding functionality. In some aspects, the coding / decoding circuit can be the baseband circuit 1310 Convolution, tail-biting convolution, turbo, Viterbi or LDPC coding / decoding functionality (LDPC = Low Density Parity Check). Aspects of modulation / demodulation and encoder / decoder functionality are not limited to these examples and may have other suitable functions in other aspects. The baseband circuit 1310 is set up to process baseband signals from a receive signal path of the RF circuit 1306 are received, and baseband signals for a transmit signal path of the RF circuit 1306 to create. The baseband circuit 1310 is set up to interface with the application circuit 1105 / 1205 (please refer 11 and 12 ) for generating and processing the baseband signals and for controlling operations of the RF circuit 1306 to build. The baseband circuit 1310 can take over various functions of the radio control.

The above-mentioned circuit and / or control unit of the baseband circuit 1310 can have one or more single or multi-core processors. The one or more processors can, for example, be a 3G baseband processor 1304A , a 4G / LTE baseband processor 1304B, a 5G / NR baseband processor 1304C or one or more other baseband processor (s) 1304D for other generations existing, under development or to be developed in the future (e.g. sixth generation (6G) etc.). In other aspects, some or all of the functionality of the baseband processors 1304A-D in modules that are in memory 1304G are stored and via a central unit (CPU) 1304E are executed. In other aspects, some or all of the functionality of the baseband processors 1304A-D as hardware accelerators (eg FPGAs, ASICs, etc.) which are loaded with the corresponding bit streams or logic blocks that are stored in the corresponding memory cells. In various aspects, the memory can 1304G Store the program code of a real-time operating system (RTOS) that, when sent by the CPU 1304E (or another baseband processor) is running the CPU 1304E (or another baseband processor) should cause the resources of the baseband circuit 1310 manage, schedule tasks, etc. Examples of the RTOS can include: Operating System Embedded (OSE) ™ provided by Enea®, Nucleus RTOS ™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX ™ powered by Express Logic®, FreeRTOS, REX OS powered by Qualcomm®, OKL4 powered by Open Kernel (OK) Labs®, or any other suitable RTOS such as those discussed herein. It also has the baseband circuit 1310 one or more digital audio signal processor (s) (DSP) 1304F on. The audio DSP (s) 1304F have elements for compression / decompression and echo cancellation and may have other suitable processing elements in other aspects.

In some aspects, the processors do 1304A-1304E corresponding memory interfaces for sending / receiving data to / from memory 1304G on. The baseband circuit 1310 can also have one or more interfaces for communicative coupling with other circuits / devices, such as an interface for sending / receiving data to / from the memory external to the baseband circuit 1310 ; an application circuit interface for sending / receiving data to / from the application circuit 1105 / 1205 of the 1310 . 11-13); an RF circuit interface for sending / receiving data to / from the RF circuit 1306 of the 13 ; an interface for wireless hardware connectivity for sending / receiving data to / from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth® / Bluetooth® Low Energy components, Wi-Fi® Components and / or the like); and a power management interface for sending / receiving power or control signals to / from the PMIC 1225 .

In alternative aspects (which can be combined with the aspects described above) the baseband circuit 1310 one or more digital baseband systems that are coupled to each other and to a CPU subsystem, an audio subsystem and an interface subsystem via an interconnection subsystem. The digital baseband subsystems can also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via a further interconnect subsystem. Each of the interconnect subsystems can have a bus system, point-to-point connections, network-on-chip (NOC) structures and / or another suitable bus or interconnect technology, such as those dealt with here. The audio subsystem can include a DSP circuit, a buffer memory, a program memory, a speech processing accelerator circuit, a data converter circuit such as an analog-to-digital and digital-to-analog converter circuit, an analog circuit with one or more amplifiers and filters, and / or other similar components . In one aspect of the present disclosure, the baseband circuit 1310 a protocol processing circuit with one or more instances of control circuits (not shown) in order to provide control functions for the digital baseband circuit and / or high-frequency circuit (for example the radio front-end modules 1315 ).

Although in 13 not shown, the baseband circuit 1310 in some aspects, single processing device (s) for operating one or more wireless communication protocols (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") and single processing device (s) for implementing functions of the PHY layer. In these respects, the functions of the PHY layer include the radio control functions mentioned above. In these aspects, the protocol processing circuit operates or implements various protocol layers / units of one or more wireless communication protocols. In a first example, the protocol processing circuit can operate LTE protocol units and / or 5G / NR protocol units if the baseband circuit 1310 and / or the RF circuit 1306 Are part of the mmWave communication circuit or other suitable cellular communication circuit. In the first example, the protocol processing circuit would perform MAC, RLC, PDCP, Service Data Adaptation Protocol (SDAP), RRC and NAS functions. In a second example, the protocol processing circuit can operate one or more IEEE-based protocols if the baseband circuit 1310 and / or the RF circuit 1306 Are part of a Wi-Fi communication system. In the second example, the protocol processing circuit would perform Wi-Fi MAC and LLC (Logical Link Control) functions. The protocol processing circuit can have one or more memory structures (e.g. 1304G ) to store program code and data for the operation of the protocol functions, and one or more processing cores to store the program code and perform various operations on the data. The baseband circuit 1310 can also support radio communication for more than one wireless protocol.

The various hardware elements of the baseband circuit 1310 discussed herein can be implemented as, for example, a solder substrate with one or more integrated circuits (ICs), a single packaged IC that is soldered onto a main circuit board, or a multi-chip module that contains two or more ICs. In one example, the components of the baseband circuit 1310 suitably combined in a single chip or chipset or arranged on a single circuit board. In another example, some or all of the components of the baseband circuit 1310 and the RF circuit 1306 implemented together, such as a system on a chip (SoC) or system-in-package (SiP). In another example, some or all of the components of the baseband circuit can be used 1310 implemented as a separate SoC that is communicative with the RF circuit 1306 (or multiple instances of the RF circuit 1306 ) is coupled. According to another example, some or all of the components of the baseband circuit 1310 and the application circuit 1105 / 1205 implemented together as individual SoCs that are mounted on the same circuit board (e.g. a “multi-chip package”).

In some aspects, the baseband circuit can 1310 provide communication that is compatible with one or more wireless technologies. For example, the baseband circuit 1310 support communication with an E-UTRAN or another WMAN, a WLAN, a WPAN in some aspects. Aspects in which the baseband circuit 1310 is set up to support radio communication with more than one wireless protocol can be referred to as a multimode baseband circuit.

The RF circuit 1306 can enable communication with wireless networks using modulated electromagnetic radiation over a non-fixed medium. In several ways the RF circuit can 1306 Include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. The RF circuit 1306 may have a received signal path that includes a circuit for down-converting the from the FEM circuit 1308 received RF signals and for providing baseband signals for the baseband circuit 1310 may contain. The RF circuit 1306 can also have a transmission signal path that includes a circuit for up-converting the output from the baseband circuit 1310 provided baseband signals and to provide RF output signals for the FEM circuit 1308 may have for transmission.

In some aspects, the receive signal path of the RF circuit 1306 a mixer circuit 1306a , an amplifier circuit 1306b and a filter circuit 1306c exhibit. In some aspects, the transmit signal path may be the RF circuit 1306 a filter circuit 1306c and a mixer circuit 1306a exhibit. The RF circuit 1306 can also use a synthesizer circuit 1306d for synthesizing a frequency for use by the mixer circuit 1306a of the received signal path and the transmitted signal path. In some aspects the mixer circuit is 1306a The received signal path is set up to receive RF signals from the FEM circuit 1308 are received based on that from the synthesizer circuit 1306d down-convert the synthesized frequency provided. The amplifier circuit 1306b may be arranged to amplify the down-converted signals and the filter circuit 1306c may be a low pass filter (LPF) or a band pass filter (BPF), which are arranged to remove unwanted signals from the down-converted signals to produce output baseband signals. Output baseband signals can be sent to the baseband circuit for further processing 1310 to be provided. In some cases the output baseband signals may be zero frequency baseband signals, although this is not a requirement. In some aspects, the mixer circuit can 1306a of the received signal path comprise passive mixers, although the scope of the aspects is not limited in this regard.

In some aspects the mixer circuit is 1306a of the transmit signal path is set up to input baseband signals based on that from the synthesizer circuit 1306d upconverting the synthesized frequency provided to produce RF output signals for the FEM circuit 1308 to create. The baseband signals can be from the baseband circuit 1310 can be provided by the FEM circuit 1306c be filtered.

In some aspects, the mixer circuit 1306a of the received signal path and the mixer circuit 1306a of the transmission signal path have two or more mixers and be arranged for a quadrature downward or upward conversion. In some aspects, the mixer circuit 1306a of the received signal path and the mixer circuit 1306a of the transmission signal path has two or more mixers and be arranged for image suppression (for example Hartley image suppression). In some aspects, the mixer circuit 1306a of the received signal path and the mixer circuit 1306a of the transmission signal path can be designed for direct downward or direct upward conversion. The mixer circuit 1306a of the received signal path and the mixer circuit 1306a of the transmission signal path can be set up for super-heterodyne operation in some aspects.

In some aspects, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the aspects is not limited in these respects. In some alternative aspects, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternative aspects, the RF circuit 1306 Analog-to-digital converter (ADC) and digital-to-analog converter (DAC), and the baseband circuit 1310 can use a digital baseband interface to communicate with the RF circuit 1306 exhibit.

In some dual-mode aspects, a separate radio integrated circuit can be provided to process signals for each spectrum, although the scope of the aspects is not limited in this regard.

In some aspects, the synthesizer circuit 1306d a fractional-N synthesizer or a fractional-N / N + 1 synthesizer, although the scope of the aspects in this regard is not limited as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1306d a delta-sigma synthesizer, a frequency multiplier or a synthesizer which has a phase-locked loop with a frequency divider.

The synthesizer circuit 1306d can be configured to provide an output frequency for use by the mixer circuit 1306a the RF circuit 1306 based on a frequency input and a divider control unit. In some aspects, the synthesizer circuit 1306d be a fractional N / N + 1 synthesizer.

In some cases the frequency input can be provided by a voltage controlled oscillator (VCO), although this is not a requirement. Depending on the desired output frequency, the divider control unit can either be from the baseband circuit 1310 or from the application circuit 1105 / 1205 to be provided. In some cases, a divider control input (e.g., N) can be determined from a look-up table stored on one of the application circuitry 1105 / 1205 specified channel.

The synthesizer circuit 1306d the RF circuit 1306 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some aspects, the divider can be a dual module divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some aspects, the DMD may be configured to divide the input signal by either N or N + 1 (e.g., based on an implementation) to provide a fractional division ratio. In some example aspects, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D flip-flop. In these aspects, the delay elements can be set up such that a VCO period is divided into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to ensure that the total delay through the delay line is one VCO cycle.

In some aspects, the synthesizer circuit 1306d be set up to generate a carrier frequency as the output frequency, while in other aspects the output frequency can be a multiple of the carrier frequency (e.g. twice the carrier frequency, four times the carrier frequency) and is used in conjunction with a quadrature generator and divider circuit to multiply Generate signals on the carrier frequency with several different phases in relation to each other. In some aspects, the output frequency can be a LO frequency (fLO). In some aspects, the RF circuit 1306 have an IQ / polar converter.

The FEM circuit 1308 may have a received signal path that may have a circuit that is configured to communicate with those of the antenna array 1311 received RF signals works, the received signals are amplified and the amplified versions of the received signals are added to the RF circuit 1306 for further processing. The FEM circuit 1308 can also have a transmission signal path, which can have a circuit which is set up such that it sends signals for transmission amplified by the RF circuit 1306 for transmission through one or more antenna elements of the antenna array 1311 to be provided. In various aspects, the amplification through the transmit or receive signal paths can be carried out exclusively in the RF circuit 1306 , exclusively in the FEM circuit 1308 or both in the RF circuit 1306 as well as in the FEM circuit 1308 respectively.

In some aspects, the FEM circuit can 1308 have a TX / RX switch to switch between transmit and receive mode. The FEM circuit 1308 can have a receive signal path and a transmit signal path. The received signal path of the FEM circuit 1308 may have a low noise amplifier (LNA) to amplify received RF signals and the amplified received RF signals as an output (eg to the RF circuit) 1306 ) to provide. The transmission signal path of the FEM circuit 1308 can use a power amplifier (PA) to amplify RF input signals (e.g. provided by the RF circuit) 1306 ) and one or more filters for generating RF signals for subsequent transmission through one or more antenna elements of the antenna array 1311 exhibit.

The antenna array 1311 comprises one or more antenna elements, each of which is arranged to convert electrical signals into radio waves that travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals are generated by the baseband circuit 1310 are provided, converted into analog RF signals (e.g. modulated waveform), which are amplified and transmitted via the antenna elements of the antenna array 1311 , which has one or more antenna elements (not shown), are transmitted. The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can be formed in a variety of arrangements as are known and / or discussed herein. The antenna array 1311 may have microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. The antenna array 1311 can be formed as a patch of metal foil (e.g., a patch antenna) in a variety of shapes and can be connected to the RF circuit 1306 and / or the FEM circuit 1308 be coupled using metal transmission lines or the like.

Application circuit processors 1105 / 1205 and processors of the baseband circuit 1310 can be used to execute elements of one or more instances of a protocol stack. For example, processors can use the baseband circuit 1310 used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functionality while processors of the application circuit 1105 / 1205 Be able to use data (e.g. packet data) received from these layers, and also perform Layer 4 functionality (e.g. TCP and UDP layers). As mentioned herein, layer 3 can comprise an RRC layer, which is described in more detail below. As mentioned herein, Layer 2 can comprise a MAC layer, an RLC layer and a PDCP layer, which are described in more detail below. As indicated herein, Layer 1 can comprise a PHY layer of a UE / RAN node, which is described in more detail below.

14th illustrates various protocol functions that can be implemented in a wireless communication device in accordance with various aspects. 14th in particular has an arrangement 1400 that has connections between different protocol layers / units. The following description of 14th is intended for different protocol layers / units working in conjunction with the 5G / NR system standards and LTE system standards, but some or all aspects of 14th can also be applicable to other wireless communication network systems.

The protocol layers of the arrangement 1400 can be one or more of the protocol layers PHY 1410 , MAC 1420 , RLC 1430 , PDCP 1440 , SDAP 1447 , RRC 1455 and NAS layer 1457 have, in addition to other, not shown functions of higher layers. The protocol layers can have one or more service access points (e.g. the points 1459 , 1456 , 1450 , 1449 , 1445 , 1435 , 1425 and 1415 in 14th ) that can provide communication between two or more protocol layers.

The PHY 1410 can send physical layer signals 1405 send and receive that can be received by or sent to one or more other communication devices. The physical layer signals 1405 may have one or more physical channels, such as those discussed here. The PHY 1410 can also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g. for initial synchronization and handover purposes) and other measurements performed by higher layers such as the RRC 1455 , be used. The PHY 1410 can also detect errors on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, modulation / physical demodulation Perform channels, interleaving, rate matching, mapping to physical channels and MIMO antenna processing. In some ways, an instance of the PHY 1410 via one or more PHY-SAP 1415 Inquiries from and references to an instance of the MAC 1420 process and provide. In some aspects, PHY-SAP 1415 transmitted inquiries and notices have one or more transport channels.

The instance (s) of the MAC 1420 can (can) requests from an instance of the RLC 1430 via one or more MAC SAPs 1425 edit and notices to an instance of the RLC 1430 provide. This via the MAC-SAP 1425 Queries and notifications transmitted can have one or more logical channels. The MAC 1420 the assignment between the logical channels and transport channels, the multiplexing of MAC-SDUs from one or more logical channels on TBs, which are sent to the PHY via the transport channels 1410 are to be delivered, the de-multiplexing of MAC-SDUs on one or more logical channels of TBs, which are used by the PHY 1410 be delivered via transport channels, multiplexing MAC-SDUs on TBs, scheduling information reporting, performing error correction by HARQ and prioritizing the logical channels.

Instance (s) of RLC 1430 can (can) requests from an instance of PDCP 1440 via one or more service access points to control the radio link (RLC-SAP) 1435 process and provide information to them. This via RLC-SAP 1435 Queries and notifications transmitted can have one or more RLC channels. The RLC 1430 can operate in a variety of modes including transparent mode (TM), unacknowledged mode (UM), and confirmed mode (AM). The RLC 1430 can perform transmission of upper-tier PDUs, automatic repeat request (ARQ) error correction for AM data transmissions, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmissions. The RLC 1430 can also perform re-segmentation of RLC data PDUs for AM data transmissions, rearrange RLC data PDUs for UM and AM data transmissions, detect duplicate data for UM and AM data transmissions, RLC SDUs for UM and AM -Discard data transfers, detect protocol errors for AM data transfers, and perform RLC recovery.

Instance (s) of PDCP 1440 can request requests from and references to instance (s) of RRC 1455 and / or instance (s) of SDAP 1447 via one or more service access points of the packet data convergence protocol (PDCP-SAP) 1445 process and provide. This via PDCP-SAP 1445 Queries and notices transmitted can have one or more radio bearers. The PDCP 1440 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform sequential delivery of upper tier PDUs when lower tier recovery, duplicate lower tier SDUs when lower tier recovery for radio bearers mapped on RLC AM, encrypt and decrypt data of the control level, carry out the integrity protection and the integrity check of data of the control level, control the time-controlled deletion of data and carry out security operations (e.g. encryption, decryption, integrity protection, integrity verification, etc.).

Instance (s) of SDAP 1447 can (can) inquiries from and references to one or more protocol units of higher layers via one or more SDAP-SAP 1449 process and provide. This via SDAP-SAP 1449 Queries and notifications transmitted can have one or more QoS flows. SDAP 1447 can map QoS flows on data radio bearers (DRBs) and vice versa and also mark QoS flow identifiers (QFIs) in DL and UL packets. A single SDAP unit 1447 can be set up for a single PDU session. In the UL direction, the NG-RAN 810 control the mapping of QoS flows to DRB (s) in two different ways: reflective mapping or explicit mapping. In the case of reflective imaging, the SDAP 1447 of a UE 801 monitor the QFIs of the DL packets for each DRB and apply the same mapping for packets flowing in the UL direction. For a DRB, the SDAP 1447 of the UE 801 Map the UL packets belonging to the QoS flows corresponding to the QoS Flow ID (s) and PDU session observed in the DL packets for that DRB. In order to enable reflexive mapping, the NG-RAN 1010 Mark DL packets via the Uu interface with a QFI. With the explicit assignment, the RRC 1455 the SDAP 1447 set up with an explicit QoS flow-to-DRB mapping rule that is stored and used by the SDAP 1447 can be followed. In a sense, the SDAP 1447 can only be used in NR implementations and not in LTE implementations.

The RRC 1455 can set up aspects of one or more protocol layers via one or more service access points (M-SAP), which one or more instances of PHY 1410 , MAC 1420 , RLC 1430 , PDCP 1440 and SDAP 1447 can have. Regarding aspects, an instance of RRC 1455 Requests from one or more NAS units 1457 via one or more RRC SAPs 1456 edit and provide information to them. The most important services and functions of the RRC 1455 can include the transmission of system information (SI) (e.g. in master information blocks (MIBs) or system information blocks (SIBs) with regard to the NAS), the transmission of system information with regard to the access layer (AS), paging, structure , Maintenance and release of an RRC connection between the UE 801 and the RAN 810 (e.g. RRC connection paging, RRC connection setup, RRC connection modification and RRC connection release), setup, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility and measurement configuration for the UE measurement reporting. The MIBs and SIBs can have one or more IEs, each of which can contain individual data fields or data structures.

The NAS 1457 can be the highest layer of the control unit between the UE 801 and the AMF 1021 form. The NAS 1457 can increase the mobility of the UEs 801 and the session management procedures for establishing and maintaining IP connectivity between the UE 801 and a P-GW in LTE systems.

According to various aspects, one or more protocol units of the arrangement 1400 in the UEs 801 , RAN node 811 , AMF 1021 in NR implementations or MME 921 in LTE implementations, UPF 1002 in NR implementations or S-GW 922 and P-GW 923 be implemented in LTE implementations or the like used for control or the user plane communication protocol stack between the above devices. Under such aspects, one or more protocol entities residing in one or more of the UE 801 , gNB 811 , AMF 1021 etc., communicate with a corresponding peer protocol unit, which can be implemented in or on another device, the services of the corresponding protocol units of the lower layer being used to carry out this communication. In some aspects, a gNB-CU of the gNB 811 the RRC 1455 , SDAP 1447 and PDCP 1440 of the gNB, who control the operation of one or more gNB-DUs, and the gNB-DUs of the gNB 811 can each use the RLC 1430 , MAC 1420 and PHY 1410 of the gNB 811 host.

In a first example, a protocol stack of the control unit can be assigned in the order from highest to lowest layer NAS 1457 , RRC 1455 , PDCP 1440 , RLC 1430 , MAC 1420 and PHY 1410 exhibit. In this example, the top layers 1460 on the NAS 1457 be built up of an IP layer 1461 , an SCTP 1462 and an application layer signaling protocol (AP) 1463 having.

In NR implementations, the AP 1463 an NG application protocol layer (NGAP or NG-AP) 1463 for the NG interface 813 be that between the NG-RAN nodes 811 and the AMF 1021 is defined, or the AP 1463 can be an Xn application protocol layer (XnAP or Xn-AP) 1463 for the Xn interface 812 be that between two or more RAN nodes 811 is defined.

The NG-AP 1463 can use the functions of the NG interface 813 support and may have elementary procedures (EPs). An NG-AP EP can be an interaction unit between the NG-RAN nodes 811 and the AMF 1021 be. The NG-AP 1463 services can have two groups: UE-associated services (e.g. services in connection with a UE 801 ) and non-UE-associated services (eg services in connection with the entire NG interface instance between the NG-RAN node 811 and the AMF 1021 ). These services may have functions including, but not limited to, paging for sending paging requests to NG-RAN nodes 811 involved in a particular paging area; a UE context management function that makes it the AMF 1021 enables a UE context in the AMF 1021 and the NG-RAN node 811 set up, modify and / or release; a mobility function for the UEs 801 in ECM-CONNECTED mode for system-internal HOs to support mobility within the NG-RAN and cross-system HOs to support mobility from / to EPS systems; a NAS signal transport function for transporting or redirecting NAS messages between the UE 801 and the AMF 1021 ; a NAS node selection function for determining an association between the AMF 1021 and the UE 801 ; NG interface management function (s) for setting up the NG interface and for monitoring for errors via the NG interface; a warning message transmission function for providing means for transmitting warning messages via the NG interface or for canceling the current broadcast of warning messages; a configuration transfer function for requesting and transferring RAN configuration information (eg, SON- Information, performance measurement (PM) data, etc.) between two RAN nodes 811 via CN 820 ; and / or other similar functions.

The XnAP 1463 can use the functions of the Xn interface 812 support and may include basic XnAP mobility schemes and XnAP global schemes. The XnAP basic mobility procedures may include procedures that are used to handle UE mobility within the NG RAN 811 (or E-UTRAN 910 ) such as handover preparation and cancellation procedures, SN status transfer procedures, UE context inquiry and UE context release procedures, RAN paging procedures, procedures related to double connectivity and the like. The XnAP global procedures can have procedures that do not relate to a specific UE 801 such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, and the like.

In a second example, a user-level protocol stack in order from highest layer to lowest layer can SDAP 1447 , PDCP 1440 , RLC 1430 , MAC 1420 and PHY 1410 exhibit. The user level protocol stack may be used for communication between the UE 801 , the RAN node 811 and UPF 1002 in NR implementations or an S-GW 922 and P-GW 923 used in LTE implementations. In this example, the top layers 1451 on the SDAP 1447 and establish a UDP and IP security layer (UDP / IP) 1452 , a General Packet Radio Service (GPRS) tunneling protocol for the user plane layer (GTP-U) 1453 and a user level PDU (UP PDU) layer 1463 exhibit.

The transport network layer 1454 (also known as the "transport layer") can be built on top of IP transport, and GTP-U 1453 can be on the UDP / IP layer 1452 (including a UDP layer and an IP layer) can be used to carry user level PDUs (UP PDUs). The IP layer (also referred to as the “Internet layer”) can be used to perform packet addressing and routing functionality. The IP layer can, for example, assign IP addresses to the user data packets in one of the formats IPv4, IPv6 or PPP.

The GTP-U 1453 can be used for transferring user data within the GPRS core network and between the radio access network and the core network. The transported user data can be, for example, packets in one of the formats IPv4, IPv6 or PPP. UDP / IP 1452 can provide checksums for data integrity, port numbers for addressing various functions at the source and destination as well as encryption and authentication for the selected data streams. The RAN node 811 and the S-GW 922 can use a SI-U interface to exchange user plane data over a protocol stack that includes an L1 layer (e.g. PHY 1410 ), an L2 layer (e.g. MAC 1420 , RLC 1430 , PDCP 1440 and / or SDAP 1447 ), the UDP / IP layer 1452 and the GTP-U 1453 having. The S-GW 922 and the P-GW 923 can use an S5 / S8a interface to exchange user-level data via a protocol stack that has an L1 layer, an L2 layer and the UDP / IP layer 1452 and the GTP-U 1453 having. As mentioned earlier, NAS protocols can increase the mobility of the UE 801 and support the session management process to ensure IP connectivity between the UE 801 and the P-GW 923 establish and maintain.

In addition, although in 14th not shown, an application layer above the AP 1463 and / or the transport network layer 1454 to be available. The application layer can be a layer in which a user of the UE 801 , of the RAN node 811 or another network element interacts with software applications, e.g. from the application circuit 1105 or the application circuit 1205 are executed. The application layer can also provide one or more interfaces for software applications that communicate with communication systems of the UE 801 or RAN node 811 interact, such as the baseband circuit 1310 . In some implementations, the IP layer and / or the application layer can provide the same or similar functionality as layers 5-7 or parts thereof of the OSI model (Open Systems Interconnection) (e.g. OSI layer 7 - the application layer, OSI layer 6 - the presentation layer and OSI layer 5 - the session layer).

15th FIG. 12 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, in accordance with some example aspects. Specifically shows 15th a schematic representation of the hardware resources 1500 that have one or more processors (or processor cores) 1510 , one or more storage / archive storage devices 1520 and one or more communication resources 1530 each having a bus 1540 can be communicatively coupled. For aspects where node virtualization (e.g. NFV) can be a hypervisor 1502 be executed in order to provide an execution environment for one or more network slices / sub-slices to the hardware resources 1500 to use.

The processors 1510 can eg use a processor 1512 and a processor 1514 exhibit. The processor (s) 1510 can, for example, a central processing unit (CPU), a RISC processor (RISC = Reduced Instruction Set Computing), a CISC processor (CISC = Complex Instruction Set Computing), a graphics processing unit (GPU = Graphics Processing Unit), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The storage / archive storage devices 1520 may include main memory, disk storage, or any suitable combination thereof. The storage / archive storage devices 1520 can include all types of volatile or non-volatile memories, such as dynamic memories with random access (DRAM), static memories with random access (SRAM), erasable programmable read-only memories (EPROM), electrically erasable programmable read-only memories (EEPROM), flash memories , Solid state storage, etc.

The communication resources 1530 may be connection or network interface components or other suitable devices for communication with one or more peripheral devices 1504 or one or more databases 1506 over a network 1508 exhibit. The communication resources 1530 can, for example, have wired communication components (eg for coupling via USB), cellular communication components, NFC components, Bluetooth® components (or Bluetooth® Low Energy), Wi-Fi® components and other communication components.

The instructions 1550 software, a program, an application, an applet, an application or other executable code can have the at least one of the processors 1510 causes one or more of the methods discussed here to be performed. The instructions 1550 can be wholly or partially in at least one of the processors 1510 (e.g. in the cache memory of the processor), the memory / archive storage units 1520 or a suitable combination thereof. In addition, each part of the instructions 1550 from any combination of peripheral devices 1504 or the databases 1506 on the hardware resources 1500 be transmitted. The memory of the processors are accordingly 1510 who have favourited Storage / Archive Storage Units 1520 who have favourited Peripherals 1504 and the databases 1506 Examples of computer readable and machine readable media.

For one or more aspects, at least one of the components shown in one or more of the preceding figures can be set up to carry out one or more operations, techniques, processes and / or methods according to the example section below. For example, as described above in connection with one or more of the preceding figures, the baseband circuit can be configured to operate in accordance with one or more of the examples listed below. Another example: A circuit that is connected to a UE, a base station, a network element, etc., as described above in connection with one or more of the preceding figures, can be set up in such a way that it operates according to one or more of the below in Examples section listed works.

Example 1 includes a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: transmitting or causing a base station to transmit downlink channels using unlicensed channels Spectrum, the transmission of PDSCH depending on the LBT results of each LBT bandwidth.

Example 2 includes the method of Example 1 and / or one or more other examples wherein the PDSCH is only transmitted using the LBT bandwidth if CCA is successful.

Example 3 includes the method of Example 1 and / or some other examples herein, wherein a common group PDCCH is transmitted over one of the LBT bandwidths at which CCA is successful.

Example 4 includes the method of Example 1 and / or some other examples wherein candidate positions for a group-shared PDCCH are positioned in each LBT bandwidth within the bandwidth slice.

Example 5 includes the method of Example 1 and / or some other examples using a licensed carrier for the transmission of GC-PDCCH.

Example 6 has the method of Example 1 and / or some other examples, with GC-PDCCH being transmitted at the beginning of a COT.

Example 7 has the procedure of Example 1 and / or some other examples with GC-PDCCH transmitted in the middle of a COT.

Example 8 includes the method of Example 1 and / or some other examples, with GC-PDCCH being transmitted multiple times within a COT.

Example 9 includes the method of Example 1 and / or some other examples herein, where the first part of a COT PDSCH is encoded using the entire bandwidth parts, but is actually transmitted using the available LBT bandwidth by not including data available LBT bandwidth can be dotted around.

Example 10 includes the method of Example 1 and / or some other examples herein, wherein for the first part of a COT PDSCH is encoded by rate matching data around the unavailable LBT bandwidth.

Example 11 includes the method of Example 1 and / or some other examples contained herein, using a BITMAP to display available LBT-BWs in GC-PDCCH.

Example 12 includes the method of Example 1 and / or some other examples herein where a GC-PDCCH can indicate that the LBT result is not available.

Example 13 includes the method from Example 1 and / or some other examples, with a cluster-based CORESET set up for a GC-PDCCH.

Example 14 includes a method comprising: attempting or causing an attempt to decode received downlink control information (DCI); and the identification, based on the decoded DCI, of LBT bandwidth information (BW) and a time domain channel occupancy time structure (COT).

Example 15 includes the method of Example 14 and / or one or more other examples, wherein the LBT-BW information has a frequency domain COT structure.

Example 16 has the method of Example 14-15 and / or some other examples, where the DCI is in DCI format 20.

Example 17 includes the methodology of Examples 14-16 and / or some other examples herein, further comprising: Receiving the DCI over a Group Shared (GC) Downlink Physical Control Channel (PDCCH).

Example 18 includes the method of Example 17 and / or some other examples included herein, where attempting to decode includes: attempting or causing attempt to decode at least one PDCCH candidate for the GC-PDCCH that is within an available LBT BW is positioned.

Example 19 includes the methodology of Examples 17-18 and / or some other examples contained herein, further including: Receipt of the GC-PDCCH in a licensed tape or an unlicensed tape.

Example 20 contains the methodology of Examples 17-19 and / or some other examples listed herein, including: Receipt of GC-PDCCH the next time the GC-PDCCH is monitored, if the GC-PDCCH does not start a next generation of nodeB (gNB ) acquired COT is being prepared.

Example 21 includes the methodology of Examples 17-20 and / or some other examples herein, using a Physical Downlink Shared Channel (PDSCH) the assumption that a whole BWP is available and the LBT BW is punctured if CCA is unsuccessful.

Example 22 has the method of Examples 17-20 and / or some other examples herein, wherein the gNB is to adjust the PDSCH according to available LBT BWs in the remaining time of an equal COT.

Example 23 includes the method of Examples 17-20 and / or some other examples and further includes: Performing or causing the blind detection of available LBT-BWs using a demodulation reference signal (DMRS).

Example 24 contains the method of Examples 17-20 and / or some other examples herein, including trying or causing the attempt to decode the GC-PDCCH as quickly as possible using knowledge of one or more punched parts.

Example 25 includes the method of Example 24 and / or some other examples including: Performing or causing a rate adjustment to be performed for LBT BWs that are not available due to LBT failure.

Example 26 includes the method of Examples 14-25 and / or some other examples included herein including: Encoding or causing a PUSCH transmission (Physical Uplink Shared Channel) to be encoded using an entire planned BW ; and transferring or arranging for the transfer of the PUSCH.

Example 27 includes the method of Example 26 and / or some other examples contained herein, further including: puncturing or causing data associated with LBT BW to be punctured if CCA is unsuccessful.

Example 28 includes the method of Example 27 and / or some other examples, where there is a phase and only the puncture is used for the LBT BW in which the CCA is unsuccessful for the entire duration of the COT.

Example 29 has the method of Examples 22-28 and / or some other examples, wherein the GC-PDCCH with the indication of the LBT BW is carried in a primary channel and is not prepared at the beginning of the gNB-acquired COT.

Example 30 includes the method of Example 29 and / or some other examples contained herein, further comprising: during a first phase: attempting or causing the attempt to find the primary channel by detecting a DMRS and / or decoding the GC-PDCCH unless the primary channel is known a priori or has already been detected in an earlier downlink burst; Attempting or causing the attempt to decode the GC-PDCCH without any blind detection; Extracting or making an attempt to extract the information relating to the LBT bandwidth; and during a second phase: performing or initiating the RF retuning and attempting or initiating the attempt to decode information about an intended activated BWP.

Example 31 includes the method of Examples 14-30 and / or some other examples, where the method is intended to be performed by a user equipment (UE).

Example 32 includes a communication device comprising: a memory; and one or more processors operatively coupled to the memory and configured to: select a bandwidth in the unlicensed spectrum for communication over the 5G or NR system; perform a channel scan operation for a plurality of sub-bands in the bandwidth; and encoding one or more 5G or NR downlink channels for transmission, the encoding of the 5G or NR downlink channels for transmission being based on a result of the channel scanning operation.

Example 33 has the subject matter of Example (s) 32 and further shows that the channel scan operation comprises a clear channel evaluation (CCA) operation.

Example 34 is based on the subject matter of Example (s) 32-33 and further shows that the channel scan operation includes a listen before talk (LBT) operation.

Example 35 comprises the subject matter of Example (s) 32-34 and further includes the one or more processors configured to assign the one or more 5G or NR downlink channels in one or more sub-bands of the plurality of sub-bands encode.

Example 36 comprises the subject matter of Example (s) 35 and further includes the one or more processors configured to use the one or more 5G or NR Downlink channels encoded only in the sub-band (s) determined to be available by the channel scan (s).

Example 37 is based on the subject matter of Example (s) 32-36 and further includes the one or more processors configured to encode the one or more 5G or NR downlink channels within a channel occupancy time (COT).

Example 38 includes the subject matter of Example (s) 37 and further includes the one or more processors configured to encode the 5G or NR downlink channels at the beginning of the COT.

Example 39 has the subject matter of Example (s) 37 and further includes the one or more processors configured to encode the 5G or NR downlink channels in a central portion of the COT / encode.

Example 40 exhibits the subject matter of Example (s) 37 and further includes one or more processors configured to multiple encode the 5G or NR downlink channels within the COT.

Example 41 carries the subject matter of Example (s) 37 and further includes the one or more processors configured to subdivide the one or more 5G or NR downlink channels for transmission during a first portion of the COT Encoding use of the entire bandwidth.

Example 42 carries the subject matter of Example (s) 41 and further includes the one or more processors configured to pass through the one or more 5G or NR downlink channels for transmission during a second portion of the COT Rate match to the 5G or NR downlink channels encode on one or more subbands indicated as available based on the channel scan operation.

Example 43 has the subject matter of example (s) 32-42 and further includes a control unit in the downlink providing information about the plurality of subbands in the bandwidth.

Example 44 comprises the subject matter of example (s) 43 and further includes wherein the downlink control unit provides the information about the plurality of subbands in the bandwidth as a BITMAP of N bits, where N is a number of the plurality of subbands is.

Example 45 comprises the subject matter of Example (s) 44 and further comprises wherein each bit of the N bits indicates the result of the channel scan operation for a respective sub-band of the plurality of sub-bands.

Example 46 includes the subject matter of Example (s) 32-45 and further includes that the one or more 5G or NR downlink channels are a physical downlink shared channel (PDSCH ) exhibit.

Example 47 is the subject matter of Example (s) 46 and further includes the PDSCH having a common group PDSCH.

Example 48 is subject to the subject matter of Example (s) 47 and further includes that a candidate position for the group-shared PDSCH is positioned in each of the plurality of sub-bands.

Example 49 includes the subject matter of Example (s) 47-48 and further includes the one or more processor (s) configured to set up a cluster-based control unit (CORESET) to control the one or more specify the multiple sub-bands for the transmission of the common group PDSCH.

Example 50 carries the subject matter of Example (s) 32-49 and further includes the one or more processors configured to use the one or more 5G or NR downlink channels for transmission in encode a licensed tape.

Example 51 has the subject matter of example (s) 32 and further includes that the one or more 5G or NR downlink channels are transmitted in the licensed band in order to increase the reliability of the transmission of the one or more 5G or Provide NR downlink channels.

Example 52 features a method of wireless communication in a fifth generation (5G) or new radio (NR) system, the method comprising: selecting a bandwidth in the unlicensed spectrum for communication over the 5G or NR -System; Performing a channel scan for a plurality of sub-bands in the bandwidth; and transmitting one or more 5G or NR downlink channels, the transmission of the 5G or NR downlink channels depending on a result of the channel scan.

Example 53 has the subject matter of Example (s) 52 and further shows that the channel scan process includes a Clear Channel Assessment (CCA) operation.

Example 54 includes the subject matter of Example (s) 52-53 and further shows that the channel scan operation includes a Listen Before Talk (LBT) operation.

Example 55 comprises the subject matter of Example (s) 52-54 and further includes the transmission of one or more 5G or NR downlink channels in one or more sub-bands of the plurality of sub-bands.

Example 56 exhibits the subject matter of Example (s) 55 and further includes the transmission of the one or more 5G or NR downlink channels only in the one of the one or more sub-bands identified by the channel scan as available was determined.

Example 57 incorporates the subject matter of Example (s) 52-56 and further includes transmitting the one or more 5G or NR downlink channels within a channel occupancy time (COT).

Example 58 is based on the subject matter of Example (s) 57 and further includes the transmission of the 5G or NR downlink channel or the 5G or NR downlink channels at the start of the channel occupancy time (COT).

Example 59 exhibits the subject matter of Example (s) 57 and further includes the transmission of the 5G or NR downlink channels in a central portion of the COT.

Example 60 carries the subject matter of example (s) 57 and further includes the multiple transmission of the 5G or NR downlink channels within the COT.

Example 61 replicates the subject matter of Example (s) 57 and further includes encoding one or more 5G or NR downlink channels for transmission using the full bandwidth during a first part of the COT.

Example 62 embodies the subject matter of example (s) 61 and further includes, during a second part of the COT, encoding the one or more 5G or NR downlink channels for transmission by rate matching to the 5G or NR downlink channels on one or more multiple sub-bands indicated as available due to the channel scan operation.

Example 63 is the subject matter of Example (s) 52-62 and further includes a control unit in the downlink providing information about the plurality of sub-bands in the bandwidth.

Example 64 comprises the subject matter of example (s) 63 and further includes wherein the downlink control unit provides the information about the plurality of subbands in the bandwidth as a BITMAP of N bits, where N is a number of the plurality of subbands is.

Example 65 comprises the subject matter of Example (s) 64 and further comprises wherein each bit of the N bits indicates the result of the channel scan operation for a respective sub-band of the plurality of sub-bands.

Example 66 is based on the subject matter of Example (s) 52-64 and further includes the one or more 5G or NR downlink channels comprising a physical downlink shared channel (PDSCH).

Example 67 has the subject matter of Example (s) 65 and further includes the PDSCH having a common group PDSCH.

Example 68 comprises the subject matter of Example (s) 66 and further includes a candidate position for the common group PDSCH being positioned in each of the plurality of subbands.

Example 69 is the subject of example (s) 66-67 and further includes the establishment of a cluster based control unit (CORESET) to indicate one or more sub-bands for the transmission of the common group PDSCH.

Example 70 carries the subject matter of Example (s) 52-69 and further includes the transmission of one or more 5G or NR downlink channels in a licensed band.

Example 71 has the subject matter of Example (s) 70 and further includes that the one or more 5G or NR downlink channels are transmitted in the licensed band in order to increase the reliability of the transmission of the one or more 5G downlink channels. or to provide NR downlink channels.

Example 72 may include an apparatus that has means for performing one or more elements of a method or for realizing a facility as described in any of Examples 1-71 or in connection therewith, or another method or process described herein includes. This can for example comprise a communication device for carrying out communications in a system of the fifth generation (5G) or a new radio system (NR), wherein the communication device comprises means for selecting a bandwidth in the unlicensed spectrum for communication via the 5G or NR System; Means for performing a channel scan for a plurality of sub-bands in the bandwidth; and means for transmitting one or more 5G or NR downlink channels, wherein the transmission of the 5G or NR downlink channels depends on a result of the channel scanning process and may optionally include other elements that are described in one of Examples 1-71 or thus in Relationship.

Example 73 may include one or more non-transitory computer-readable media that contain instructions to cause an electronic device to execute one or more elements of a method or to implement a device when the instructions are executed by one or more processors of the electronic device, such as described in or related to any of Examples 1-71, or another method or process described herein.

Example 74 may include a device that includes logic, modules or circuits for executing one or more elements of a method for realizing a device, as described in one of Examples 1-71 or according to one of Examples 1-71 or according to another method described herein or any other method or process described herein.

Example 75 may include a method, technique, or process as described or related to any of Examples 1-71, or parts thereof.

Example 76 may include an apparatus comprising: one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method that Techniques or to carry out the process or to realize a device as described in one of Examples 1-71 or in connection therewith, or parts thereof.

Example 77 may have a signal as described in any of Examples 1-71 or relates to any of Examples 1-71, or parts thereof.

Example 78 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or in connection with any of Examples 1-71, or parts or portions thereof, or otherwise in present disclosure.

Example 79 may include a signal encoded with data as described in or related to any of Examples 1-71, or parts or portions thereof, or otherwise described in the present disclosure.

Example Z80 may have a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message, as described in or in connection with Examples 1-71, or parts or parts thereof, or otherwise described in the present disclosure.

Example 81 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors is intended to cause the one or more processors to perform the method, techniques, or processing or implementation of a device as described in one of Examples 1-71 described or associated therewith, or parts thereof.

Example 82 may have a computer program with instructions, wherein the execution of the program by a processing element is intended to cause the processing element to use the method, the techniques or the processing or implementation of a device as described in one of Examples 1-71 or in connection therewith, execute parts of it.

Example 83 may comprise a signal on a wireless network as shown and described herein.

Example 84 may include a method of communicating on a wireless network as illustrated and described herein.

Example 85 may include a system for providing wireless communication as shown and described herein.

Example 86 may include a device for providing wireless communication as shown and described herein.

Each of the examples described above can be combined with any other example (or a combination of examples), unless expressly stated otherwise. The foregoing description of one or more implementations is provided for the purpose of illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise form indicated. Modifications and variations are possible in light of the above teachings or can be learned from practice of various aspects.

QUOTES INCLUDED IN THE DESCRIPTION

This list of the documents listed by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 62/888283 [0001]

Claims (10)

A communication device comprising: a memory; and one or more processors operatively coupled to the memory and set up: select a bandwidth in an unlicensed spectrum for communication via a fifth generation system (5G) or a new radio system (NR); perform a channel scan for a plurality of sub-bands in the bandwidth; and encoding one or more 5G or NR downlink channels for transmission, the coding of the 5G or NR downlink channels for transmission being based on a result of the channel scan; wherein the channel scanning process optionally comprises a clear channel assessment (CCA) process and / or a listen-to-speak (LBT) operation. The communication device according to Claim 1 , the one or more processors configured to encode the one or more 5G or NR downlink channels in one or more sub-bands of the plurality of sub-bands; the one or more processors are optionally configured to encode the one or more 5G or NR downlink channels only in the one of the one or more sub-bands determined to be available by the channel scan. The communication device according to one of the Claims 1 or 2 wherein the one or more processors are configured to encode one or more 5G or NR downlink channels within a channel occupancy time (COT); wherein the one or more processors are optionally arranged to encode the one or more 5G or NR downlink channels for transmission using the entire bandwidth during a first portion of the COT; wherein the one or more processors are further optionally configured, during a second part of the COT, to transmit the one or more 5G or NR downlink channels for transmission by rate matching the 5G or NR downlink channels on one or more sub-bands based on of the channel scan are indicated as available. The communication device according to one of the Claims 1 to 3 wherein a downlink control unit provides information about the plurality of sub-bands in the bandwidth; wherein optionally the downlink control information provides the information about the plurality of sub-bands in the bandwidth as a BITMAP of N bits, where N is equal to a number of the plurality of sub-bands. The communication device according to one of the Claims 1 to 4th wherein the one or more 5G or NR downlink channels comprise a physical downlink shared channel (PDSCH); wherein the PDSCH optionally comprises a group-shared PDSCH, a candidate position for the group-shared PDSCH being positioned in each of the plurality of sub-bands; wherein the one or more processors are further optionally set up to set up a cluster-based control unit (CORESET) in order to display the one or more sub-bands for transmission of the group-shared PDSCH. A communication device for performing communications in a fifth generation (5G) or a new radio (NR) system, the communication device comprising: Means for selecting a bandwidth in the unlicensed spectrum for communication over the 5G or NR system; Means for performing a channel scan operation for a plurality of sub-bands in the bandwidth; and Means for transmitting one or more 5G or NR downlink channels, the transmission of the 5G or NR downlink channels depending on a result of the channel scan; optionally wherein the channel scanning process comprises a clear channel assessment (CCA) process and / or a listen-to-speak (LBT) operation. The communication device according to Claim 6 , wherein the one or more 5G or NR downlink channels are transmitted in one or more sub-bands of the plurality of sub-bands; optionally, the one or more 5G or NR downlink channels being transmitted only in the one of the one or more sub-bands determined to be available by the channel scan. The communication device according to one of the Claims 6 or 7th , wherein the one or more 5G or NR downlink channels are transmitted within a channel occupancy time (COT). The communication device according to Claim 8 , further comprising, during a first portion of the COT, means for encoding the one or more 5G or NR downlink channels for transmission using the entire bandwidth; optionally the communication device further comprises, during a second part of the COT, means to select the one or more 5G or NR downlink channels for transmission by rate matching the 5G or NR downlink channels on one or more sub-bands that are deemed available based on the channel scanning operation are specified to be coded. A method of wireless communication for a fifth generation system (5G) or a new radio system (NR), the method comprising: transmitting or causing a base station to transmit downward channels using unlicensed spectrum, wherein the transmitting of PDSCH depends on the LBT results of each LBT bandwidth.

Images