System and method for mib extension and reinterpretation

Abstract

A method, system, and apparatus are disclosed. According to one or more embodiments, a wireless device (22) is provided that is configured to communicate with a network node (16). The wireless device (22) includes processing circuitry (84) configured to: receive a master information block, MIB, and use a bit of the MIB as an indication of the presence of a MIB extension and / or as an instruction to interpret at least a portion of the content of the MIB in a predefined manner.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and in particular, to methods and apparatus for interpreting the contents of a Master Information Block (MIB). Background Technology

[0002] System information in the 3GPP New Radio (NR) is delivered via the Master Information Block (MIB) and the System Information Block (SIB). The MIB is transmitted on a physical channel separate from the SIB, such as the Physical Broadcast Channel (PBCH). The MIB contains a small amount of information necessary for the radio device (WD) to receive the remaining system information in the SIB. Among other information segments, the MIB contains the configuration of Control Resource Set 0 (CORESET#0), which describes the structure used to receive the Physical Downlink Control Channel (PDCCH). The structure of the MIB can be specified in standards such as 3GPP wireless communication standards (e.g., 3GPP Technical Specification (TS) 38.211 V15.4.0, Section 7.4.3; 3GPP TS 38.331 V15.4.0, Section 6.2.2), and the format cannot be changed between versions of the standard without potentially adversely interfering with backward compatibility. For example, the smallest possible CORESET#0 size in the frequency domain could be 24 resource blocks (RBs), meaning that supporting bandwidths smaller than that is impossible, even though the MIB occupies 20 RBs. Other expected enhancements in the future could also benefit from changes to the MIB. However, currently, most bits carried by the PBCH have specific meanings defined in 3GPP wireless communication standards, such as the 3GPP New Radio (NR) standard. Summary of the Invention

[0003] Some embodiments advantageously provide methods, systems, and apparatus for using reserved bits of the MIB as flags indicating the presence of an "extended MIB" (eMIB, also known as an additional MIB and / or MIB extension) or as instructions for interpreting at least a portion of the MIB's content. Embodiments also provide for replacing at least a portion of the MIB with content encoded according to a second standard, which may differ from the MIB's first standard, such as a wireless communication standard. The eMIB or content to be interpreted can be transmitted in a manner that would prevent conventional WDs operating under previous / currently known versions of wireless communication standards (e.g., currently known versions of 3GPP wireless communication standards) from detecting the eMIB. In various embodiments, this can be achieved by using at least one of a PBCH scrambling sequence different from the MIB's or a PBCH cyclic redundancy check (CRC) different from the current MIB. Embodiments may also use at least one of a primary synchronization signal (PSS) or secondary synchronization signal (SSS) having values ​​that do not represent valid combinations according to the MIB's specification to avoid detection by conventional WDs. By extending or interpreting the MIB's content, new features requiring additional system information can be supported in a backward-compatible manner. For example, using the described methods and systems, it is possible to configure a CORESET#0 of a different size than that provided by currently applicable standards.

[0004] According to one aspect of this disclosure, a wireless device configured to communicate with a network node is provided. The wireless device includes processing circuitry configured to: receive a Master Information Block (MIB); and use bits of the MIB as an indication of the presence of MIB extensions and / or as instructions to interpret at least a portion of the contents of the MIB in a predefined manner.

[0005] According to one or more embodiments of this aspect, the bit is a reserved bit in the MIB. According to one or more embodiments of this aspect, the processing circuitry is configured to: use the bit of the MIB as an indication of the presence of a MIB extension; and receive the MIB extension. According to one or more embodiments of this aspect, the processing circuitry is configured to receive the MIB extension in response to a bit of the MIB having a predefined value. According to one or more embodiments of this aspect, the MIB extension is an additional MIB.

[0006] According to one or more embodiments of this aspect, the MIB extension is received via the Physical Broadcast Channel (PBCH). According to one or more embodiments of this aspect, the processing circuitry is configured to determine, at least based on the MIB extension, the configuration for receiving the Physical Downlink Control Channel. According to one or more embodiments of this aspect, the MIB defines a CORESET#0, wherein the MIB extension defines a different CORESET#0 with a bandwidth smaller than that of the CORESET#0 defined by the MIB. According to one or more embodiments of this aspect, the size of the MIB extension is smaller than the size of the MIB.

[0007] According to one or more embodiments of this aspect, a different scrambling sequence is used for MIB expansion compared to a scrambling sequence used for MIB. According to one or more embodiments of this aspect, a different CRC is used for MIB expansion compared to a CRC used for MIB. According to one or more embodiments of this aspect, interpreting at least a portion of the content of the MIB in a predefined manner includes at least one of the following: interpreting at least a portion of the content of the MIB in a first predefined manner in response to a bit of the MIB having a first value; and interpreting at least a portion of the content of the MIB in a second predefined manner in response to a bit of the MIB having a second value.

[0008] According to another aspect of this disclosure, a method implemented by a wireless device configured to communicate with a network node is provided. A Master Information Block (MIB) is received. Bits of the MIB are used as indications of the presence of MIB extensions and / or as instructions to interpret at least a portion of the MIB's contents in a predefined manner.

[0009] According to one or more embodiments of this aspect, the bit is a reserved bit in the MIB. According to one or more embodiments of this aspect, the bit of the MIB is used as an indication of the presence of a MIB extension, and the MIB extension is received. According to one or more embodiments of this aspect, the MIB extension is received in response to a bit of the MIB having a predefined value. According to one or more embodiments of this aspect, the MIB extension is an additional MIB.

[0010] According to one or more embodiments of this aspect, the MIB extension is received via the Physical Broadcast Channel (PBCH). According to one or more embodiments of this aspect, the configuration for receiving the Physical Downlink Control Channel is determined at least based on the MIB extension. According to one or more embodiments of this aspect, the MIB defines a CORESET#0, and the MIB extension defines a different CORESET#0 with a smaller bandwidth than the CORESET#0 defined by the MIB. According to one or more embodiments of this aspect, the size of the MIB extension is smaller than the size of the MIB.

[0011] According to one or more embodiments of this aspect, a different scrambling sequence is used for MIB expansion compared to a scrambling sequence used for MIB. According to one or more embodiments of this aspect, a different CRC is used for MIB expansion compared to a CRC used for MIB. According to one or more embodiments of this aspect, interpreting at least a portion of the content of the MIB in a predefined manner includes at least one of the following: interpreting at least a portion of the content of the MIB in a first predefined manner in response to bits of the MIB having a first value, and interpreting at least a portion of the content of the MIB in a second predefined manner in response to bits of the MIB having a second value.

[0012] According to another aspect of this disclosure, a network node configured to communicate with a wireless device is provided. The network node includes processing circuitry configured to induce the transmission of a Master Information Block (MIB), wherein bits of the MIB provide indications of the presence of MIB extensions and / or instructions to interpret at least a portion of the MIB's contents in a predefined manner.

[0013] According to one or more embodiments of this aspect, the bit is a reserved bit in the MIB. According to one or more embodiments of this aspect, the bit in the MIB provides an indication of the presence of a MIB extension, and the processing circuitry is further configured to induce the transmission of the MIB extension. According to one or more embodiments of this aspect, the processing circuitry is configured to induce the transmission of the MIB extension in response to a bit in the MIB having a predefined value.

[0014] According to one or more embodiments of this aspect, the MIB extension is an additional MIB. According to one or more embodiments of this aspect, the MIB extension is transmitted via the Physical Broadcast Channel (PBCH). According to one or more embodiments of this aspect, the processing circuitry is configured to facilitate the transmission of the Physical Downlink Control Channel, the configuration of which is indicated by the MIB extension. According to one or more embodiments of this aspect, the MIB defines a CORESET#0, and wherein the MIB extension defines a different CORESET#0 having a smaller bandwidth than the CORESET#0 defined by the MIB.

[0015] According to one or more embodiments of this aspect, the size of the MIB extension is smaller than the size of the MIB. According to one or more embodiments of this aspect, a different scrambling sequence is used for the MIB extension compared to the scrambling sequence used for the MIB. According to one or more embodiments of this aspect, a different CRC is used for the MIB extension compared to the CRC used for the MIB. According to one or more embodiments of this aspect, interpreting at least a portion of the MIB content in a predefined manner includes at least one of the following: interpreting at least a portion of the MIB content in a first predefined manner in response to bits of the MIB having a first value, and interpreting at least a portion of the MIB content in a second predefined manner in response to bits of the MIB having a second value.

[0016] According to another aspect of this disclosure, a method is provided implemented by a network node configured to communicate with a wireless device. This method facilitates the transmission of a Master Information Block (MIB), wherein bits of the MIB provide indications of the presence of MIB extensions and / or instructions to interpret at least a portion of the MIB's contents in a predefined manner.

[0017] According to one or more embodiments of this aspect, the bit is a reserved bit in the MIB. According to one or more embodiments of this aspect, the bit in the MIB provides an indication of the presence of a MIB extension, and wherein the transmission of the MIB extension is prompted. According to one or more embodiments of this aspect, the transmission of the MIB extension is prompted in response to a bit in the MIB having a predefined value. According to one or more embodiments of this aspect, the MIB extension is an additional MIB.

[0018] According to one or more embodiments of this aspect, the MIB extension is transmitted via the Physical Broadcast Channel (PBCH). According to one or more embodiments of this aspect, it facilitates the transmission of the Physical Downlink Control Channel, wherein the configuration of the Physical Downlink Control Channel is indicated by the MIB extension. According to one or more embodiments of this aspect, the MIB defines a CORESET#0, and wherein the MIB extension defines a different CORESET#0 having a smaller bandwidth than the CORESET#0 defined by the MIB.

[0019] According to one or more embodiments of this aspect, the size of the MIB extension is smaller than the size of the MIB. According to one or more embodiments of this aspect, a different scrambling sequence is used for the MIB extension compared to the scrambling sequence used for the MIB. According to one or more embodiments of this aspect, a different CRC is used for the MIB extension compared to the CRC used for the MIB. According to one or more embodiments of this aspect, interpreting at least a portion of the MIB content in a predefined manner includes at least one of the following: interpreting at least a portion of the MIB content in a first predefined manner in response to bits of the MIB having a first value, and interpreting at least a portion of the MIB content in a second predefined manner in response to bits of the MIB having a second value.

[0020] According to another aspect of this disclosure, a wireless device configured to communicate with a network node is provided. The wireless device includes processing circuitry configured to receive a Master Information Block (MIB) and decode at least a portion of the contents of the MIB using a first configuration different from a second configuration previously stored for decoding the MIB.

[0021] According to one or more embodiments of this aspect, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments of this aspect, the first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments of this aspect, the first configuration corresponds to a first version of a wireless communication standard, and the second configuration corresponds to a second version of a wireless communication standard that is different from the first version.

[0022] According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a CRC different from the cyclic redundancy check (CRC) associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments of this aspect, the processing circuitry is further configured to receive signaling indicating the first configuration, wherein the first configuration replaces the second configuration.

[0023] According to another aspect of this disclosure, a method implemented by a wireless device configured to communicate with a network node is provided. A Master Information Block (MIB) is received. At least a portion of the contents of the MIB is decoded using a first configuration, which is different from a second configuration previously stored for decoding the MIB.

[0024] According to one or more embodiments of this aspect, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments of this aspect, the first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments of this aspect, the first configuration corresponds to a first version of a wireless communication standard, and the second configuration corresponds to a second version of a wireless communication standard that is different from the first version.

[0025] According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a CRC different from the cyclic redundancy check (CRC) associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments of this aspect, the processing circuitry is further configured to receive signaling indicating the first configuration, whereby the first configuration replaces the second configuration.

[0026] According to another aspect of this disclosure, a network node configured to communicate with a wireless device is provided. The network node includes processing circuitry configured to facilitate the transmission of a Master Information Block (MIB), wherein at least a portion of the contents of the MIB is decipherable using a first configuration different from a second configuration previously stored at the wireless device for deciphering the MIB.

[0027] According to one or more embodiments of this aspect, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments of this aspect, the first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments of this aspect, the first configuration corresponds to a first version of a wireless communication standard, and the second configuration corresponds to a second version of a wireless communication standard that is different from the first version.

[0028] According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a CRC different from the cyclic redundancy check (CRC) associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments of this aspect, the processing circuitry is further configured to cause the transmission of signaling indicating the first configuration, which is configured to replace the second configuration.

[0029] According to another aspect of this disclosure, a method is provided implemented by a network node configured to communicate with a wireless device. The transmission of a Master Information Block (MIB) is provided, wherein at least a portion of the content of the MIB is decipherable using a first configuration, which differs from a second configuration previously stored at the wireless device for deciphering the MIB.

[0030] According to one or more embodiments of this aspect, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments of this aspect, the first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments of this aspect, the first configuration corresponds to a first version of a wireless communication standard; and the second configuration corresponds to a second version of a wireless communication standard that is different from the first version. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration.

[0031] According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a CRC different from the CRC associated with the second configuration. According to one or more embodiments of this aspect, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments of this aspect, the transmission of signaling indicative of the first configuration is triggered, wherein the first configuration is configured to replace the second configuration. Attached Figure Description

[0032] A more complete understanding of this embodiment and its accompanying advantages and features will be more readily understood by referring to the following detailed description taken in conjunction with the accompanying drawings, in which: Figure 1This is a schematic diagram of an exemplary network architecture based on the principles of this disclosure, illustrating a communication system connected to a host computer via an intermediate network; Figure 2 This is a block diagram illustrating how a host computer communicates with a wireless device via a network node through at least a partial wireless connection, according to some embodiments of the present disclosure. Figure 3 This is a flowchart illustrating an exemplary method for executing a client application at a wireless device, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure. Figure 4 This is a flowchart illustrating an exemplary method for receiving user data at a wireless device, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure. Figure 5 This is a flowchart illustrating an exemplary method for receiving user data from a wireless device at a host computer, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure. Figure 6 This is a flowchart illustrating an exemplary method for receiving user data at a host computer, implemented in a communication system including a host computer, a network node, and a wireless device, according to some embodiments of the present disclosure. Figure 7 This is a flowchart of an exemplary process in a network node according to some embodiments of this disclosure; Figure 8 This is a flowchart of another exemplary process in a network node according to some embodiments of the present disclosure; Figure 9 This is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure; Figure 10 This is a flowchart of another exemplary process in a wireless device according to some embodiments of the present disclosure; Figure 11 This is a flowchart of another exemplary process in a wireless device according to some embodiments of the present disclosure; and Figure 12 This is a flowchart of an exemplary process in a wireless device according to some embodiments of the present disclosure. Detailed Implementation

[0033] Before describing the exemplary embodiments in detail, note that the embodiments primarily concern a combination of apparatus components and processing steps relating to using reserved bits of the MIB as a flag indicating the presence of an eMIB or as an indication of interpreting at least a portion of the MIB's content in a predefined manner and / or replacing at least a portion of the MIB with content encoded according to a second standard, which differs from the first standard of the MIB. In other words, in one or more embodiments, the MIB can be interpreted in a predefined manner / path different from the predefined manner / path by which conventional wireless devices would interpret the same MIB. Specifically, in some existing wireless communication standards, all bits on the PBCH, except for one or more reserved bits, have specific meanings defined in the wireless communication standard, where these one or more reserved bits have not yet been defined, i.e., they may lack any associated functions and / or functionalities defined by the existing wireless communication standard. For example, a reserved bit under an existing wireless communication standard may refer to a bit reserved for future use. In 3GPP Technical Specification (TS) 38.331 V15.4.0, a reserved bit is referred to as a "spare" bit, where the spare bit may not have any defined functionality within the MIB other than being a spare, as follows: In one or more embodiments, this disclosure adds functionality to one or more reserved (i.e., “spare”) bits such that one or more reserved bits in an existing wireless communication standard now have one or more of the functions and / or features described herein, such as functionality relating to the MIB, i.e., the “spare” bits are no longer spare. Furthermore, for clarity, one or more bits having the new functionality described herein are still referred to as one or more “reserved” bits, although these one or more bits correspond to one or more previously reserved bits, since those previously reserved bits now have the new functionality described herein. Therefore, in the drawings, components have been indicated by conventional symbols where appropriate, thus showing only those specific details relevant to understanding the embodiments, so as not to obscure this disclosure with details that would be readily apparent to those skilled in the art who benefit from the description herein. Throughout the specification, similar numbers indicate similar elements.

[0034] As used herein, relational terms such as “first” and “second” may be used only to distinguish one entity or element from another, without necessarily requiring or implying any physical or logical relationship or order between these entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the concepts described herein. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms “comprises,” “comprising,” and / or “includes,” as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0035] In the embodiments described herein, connection terms such as "communicate with" can be used to indicate electrical or data communication, which can be achieved through, for example, physical contact, induction, electromagnetic radiation, radio signals, infrared signals, or optical signals. Those skilled in the art will understand that multiple components can interoperate, and modifications and variations are possible to achieve electrical and data communication.

[0036] In some embodiments described herein, the term "connection" and the like may be used herein to indicate a connection, although not necessarily a direct one, and may include wired and / or wireless connections.

[0037] As used herein, the term "network node" can refer to any type of network node included in a radio network, which may also include any of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB) node, donor node of control relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio headend (RRH), core network node (e.g., mobility management entity (MME), ad hoc network (SON) node, coordination node, location node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS) node, etc. Network nodes may also include test equipment. The term “radio node” as used in this article can also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0038] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. WD as used herein can be any type of wireless device capable of communicating with a network node or another WD via radio signals, such as a wireless device (WD). A WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0039] Furthermore, in some embodiments, the generic term "radio network node" is used. It can be any kind of radio network node, which may include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), (IAB) node, relay node, access point, radio access point, remote radio unit (RRU), remote radio headend (RRH).

[0040] In one or more embodiments, a reserved bit may refer to a bit that is reserved for future use under one or more communication standards. In one example, a reserved bit under one or more communication standards is a spare bit and does not have predefined functionality associated with, for example, a MIB. In one or more embodiments described herein, reserved bits are provided with new functionality.

[0041] In one or more embodiments, CORESET may refer to a set of resources in a specific and / or predefined region of a downlink (DL) resource grid.

[0042] Indications can typically be explicit and / or implicit in indicating the information they represent and / or indicate. Implicit indications can be based, for example, on the location and / or resources used for transmission. Explicit indications can be based, for example, on parameterization using one or more parameters, and / or one or more indices, and / or one or more bit patterns representing the information.

[0043] Transmissions in the downlink can involve transmissions from the network or network node to a terminal. Transmissions in the uplink can involve transmissions from a terminal to the network or network node. Transmissions in the sidelink can involve (direct) transmissions from one terminal to another. Uplink, downlink, and sidelink (e.g., sidelink transmission and reception) can be considered as directions of communication. In some variations, uplink and downlink can also be used to describe wireless communication between network nodes, such as wireless backhaul and / or relay communication and / or (wireless) network communication between base stations or similar network nodes, particularly communication terminated therein. Backhaul and / or relay communication and / or network communication can be considered as implemented as sidelink or uplink communication or similar forms.

[0044] Configuring a terminal, wireless device, or node may involve instructing and / or causing the wireless device or node to change its configuration, for example, setting and / or registering at least one entry and / or operating mode. The terminal, wireless device, or node may be adapted to configure itself, for example, based on information or data in the terminal or wireless device's memory. Configuring a node, terminal, or wireless device by another device, node, or network may refer to and / or include the transmission of information and / or data and / or instructions, such as data (which may also be and / or include configuration data) and / or scheduling data and / or scheduling permission, to the wireless device or node by the other device, node, or network. Configuring a terminal may include sending allocation / configuration data to the terminal, thereby instructing how to interpret the MIB. The terminal may be configured with and / or used for scheduling data and / or using, for example, uplink resources for transmission, scheduling, and / or allocation, and / or downlink resources for, for example, reception, scheduling, and / or allocation. Uplink resources and / or downlink resources may be scheduled and / or provided with allocation or configuration data.

[0045] Note that although terms from a particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be construed as limiting the scope of this disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Global Microwave Interconnection Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas covered in this disclosure.

[0046] It should also be noted that the functions described herein as being performed by wireless devices or network nodes can be distributed across multiple wireless devices and / or network nodes. In other words, one should expect that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, and can actually be distributed among several physical devices.

[0047] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It should also be understood that the terms used herein shall be interpreted as having the same meaning as they have in the context of this specification and in the relevant art, and shall not be interpreted as having an idealized or overly formal meaning unless expressly defined herein.

[0048] Using existing systems and methods, it is difficult to introduce more signaling options into the MIB, such as the possibility of supporting a CORESET#0 size of less than 24 RBs. In the current MIB standard, only a single reserved bit exists, i.e., a spare bit, for future use, while multiple extensions may be needed. Therefore, embodiments provide the use of reserved bits in the MIB as a flag indicating the presence of an eMIB or as an instruction to interpret at least a portion of the MIB's content in a predefined manner, and / or to replace at least a portion of the MIB with content encoded according to a second communication standard different from the first communication standard of the MIB. Thus, reserved bits can be used as a flag indicating the presence of an eMIB. The eMIB can be transmitted in a manner that a conventional WD would not detect and that would not interfere with the functionality of conventional devices.

[0049] Therefore, in various embodiments, new features requiring additional system information can be supported in a backward-compatible manner. For example, CORESET#0 can be configured to have a different size compared to that possible in existing wireless communication standards.

[0050] Referring now to the accompanying drawings, in which similar elements are indicated by similar reference numerals, Figure 1The diagram illustrates a communication system 10 according to an embodiment, which may support 3GPP-type cellular networks such as LTE and / or NR (5G) standards. This cellular network includes an access network 12, such as a radio access network, and a core network 14. The access network 12 includes multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of radio access points, each with a defined corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to or be paged by a corresponding network node 16a. A second WD 22b in coverage area 18b can wirelessly connect to a corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is in the coverage area or where a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0051] Furthermore, it is anticipated that WD 22 can communicate simultaneously and / or be configured to communicate with more than one network node 16 and more than one type of network node 16, respectively. For example, WD 22 can have dual connectivity with both LTE-enabled network nodes 16 and the same or different NR-enabled network nodes 16. As an example, WD 22 can communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0052] The communication system 10 may be directly connected to the host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 26, 28 between the communication network 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend via an optional intermediate network 30. The intermediate network 30 may be one or more of a public, private, or hosted network. The intermediate network 30, if present, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0053] Figure 1The communication system as a whole enables connectivity between one of the connected WDs 22a and 22b and the host computer 24. This connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a and 22b are configured to use access network 12, core network 14, any intermediate networks 30, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that the participating communication devices traversing it are unaware of the routes of uplink and downlink communications. For example, it may not be necessary to inform network node 16 of the past routes of incoming downlink communications containing data originating from host computer 24 to be forwarded (e.g., transferred) to connected WD 22a. Similarly, network node 16 does not need to know the future routes of outgoing uplink communications originating from WD 22a toward host computer 24.

[0054] Network node 16 is configured to include MIB unit 32, which is configured to perform one or more network node 16 functions described herein, such as those relating to MIB interpretation. As used herein, “interpreting” a MIB can mean interpreting a received MIB in a manner different from that defined in existing standards, for example, in a manner / path different from that in which conventional wireless devices can interpret the same MIB. For example, WD 22 receiving the MIB may be able to interpret the MIB in a predefined manner according to existing wireless communication standards, such as 3GPP TS 38.331V15.4.0; however, the same MIB can be interpreted differently, i.e., reinterpreted as described herein, wherein the interpretation of the MIB may be based on flags and / or values ​​associated with one or more reserved bits, or may be based on an additional MIB, and / or may be based on a different definition of one or more fields assigned to the MIB (from existing wireless communication standards), and / or based on a new configuration table.

[0055] In one or more embodiments, the MIB unit 32 is configured to use reserved bits of the MIB transmitted to the WD as an indication of the presence of an eMIB (extended MIB) or an instruction to re-decode at least a portion of the MIB content and / or an indication to replace at least a portion of the MIB content with content encoded according to a second communication standard (i.e., using a different interpretation), the content encoded according to the second communication standard being different from the content encoded according to a first communication standard of the MIB. In one or more embodiments, the eMIB generally refers to additional MIB data / information, wherein the size of the eMIB can be equal to, less than, or greater than the size of the MIB. The wireless device 22 is configured to include a MIB decoding unit 34, which is configured to use reserved bits of the received MIB as an indication of the presence of an eMIB and an instruction to re-decode at least a portion of the MIB content and / or an indication to decode at least a portion of the MIB content according to a second communication standard, the second communication standard being different from the first communication standard of at least a portion of the MIB content.

[0056] According to the embodiments, reference will now be made to Figure 2 Describing an example implementation of the WD 22, network node 16, and host computer 24 discussed in the preceding paragraphs, in the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain wired or wireless connections to various communication devices of the communication system 10. The host computer 24 also includes processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or replacing a processor and memory such as a central processing unit, the processing circuitry 42 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits), adapted to execute instructions. The processor 44 may be configured to access (e.g., write and / or read) memory 46, which may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0057] Processing circuitry 42 may be configured to control any and / or cause such methods and / or processes to be executed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46 configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.

[0058] Software 48 may be executable by processing circuitry 42. Software 48 includes a host application 50. Host application 50 may operate to provide services to remote users, such as WD 22 connected via an OTT connection 52 terminating between WD 22 and host computer 24. In providing services to remote users, host application 50 may provide user data transmitted using OTT connection 52, “user data” which may be data and information described herein as enabling the aforementioned functionality. In one embodiment, host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. Processing circuitry 42 of host computer 24 may enable host computer 24 to observe, monitor, control, transmit to and / or receive from network node 16 and / or wireless device 22. Processing circuitry 42 of host computer 24 may include a monitoring unit 54 configured to enable the service provider to monitor network node 16 and / or wireless device 22. Processing circuitry 42 of host computer 24 may also include a control unit 56 configured to enable the service provider to control network node 16 and / or wireless device 22.

[0059] The communication system 10 also includes a network node 16, which is provided within the communication system 10 and includes hardware 58 that enables it to communicate with the host computer 24 and with the WD 22. Hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located within a coverage area 18 served by the network node 16. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. Connection 66 may be direct, or it may be via the core network 14 of the communication system 10 and / or via one or more intermediate networks 30 outside the communication system 10.

[0060] In the illustrated embodiment, the hardware 58 of network node 16 also includes processing circuitry 68. Processing circuitry 68 may include processor 70 and memory 72. Specifically, in addition to or replacing processors and memory such as a central processing unit, processing circuitry 68 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits), adapted to execute instructions. Processor 70 may be configured to access (e.g., write to and / or read from) memory 72, which may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0061] Therefore, network node 16 also has software 74, which is internally stored, for example, in memory 72, or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 can be executed by processing circuitry 68. Processing circuitry 68 can be configured to control any and / or cause such methods and / or processes described herein to be executed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. Memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuitry 68, cause the processor 70 and / or the processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, the processing circuitry 68 of network node 16 may include a MIB unit 32 configured to use reserved bits of the MIB transmitted to the WD as the presence of an eMIB and / or to interpret at least a portion of the content of the MIB in a predefined manner and / or to replace at least a portion of the MIB with content encoded according to a second communication standard, which is different from the content encoded according to a first communication standard of the MIB.

[0062] The communication system 10 also includes the previously mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 where the WD 22 is currently located. The radio interface 82 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0063] The hardware 80 of the WD 22 also includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. Specifically, in addition to or replacing a processor and memory such as a central processing unit, processing circuitry 84 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits), adapted to execute instructions. Processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0064] Therefore, WD 22 may also include software 90, which is stored, for example, in memory 88 at WD 22 or in external memory accessible to WD 22 (e.g., a database, storage array, network storage device, etc.). Software 90 is executable by processing circuitry 84. Software 90 may include a client application 92. Client application 92 may be operable to provide services to human or non-human users via WD 22 with the support of host computer 24. In host computer 24, host application 50, executing, can communicate with client application 92 via an OTT connection 52 terminated at WD 22 and host computer 24. When providing services to a user, client application 92 can receive request data from host application 50 and provide user data in response to the request data. OTT connection 52 can transmit both request data and user data. Client application 92 can interact with the user to generate the user data it provides.

[0065] Processing circuitry 84 may be configured to control any of the methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD 22 described herein. WD 22 includes memory 88 configured to store data, programming software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, processing circuitry 84 of wireless device 22 may include an MIB decoding unit 34 configured to use reserved bits of received MIBs as the presence of eMIBs and / or to re-decode at least a portion of the content of the MIBs in a predefined manner and / or to decode at least a portion of the content of the MIBs according to a second communication standard different from a first communication standard for at least a portion of the MIB content.

[0066] In some embodiments, the internal operations of network node 16, WD 22, and host computer 24 can be as follows: Figure 2 As shown, and independently, the surrounding network topology can be Figure 1 The network topology.

[0067] exist Figure 2 In this diagram, OTT connection 52 is abstractly depicted to illustrate communication between host computer 24 and wireless device 22 via network node 16, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to hide the routing from WD 22, the service provider operating host computer 24, or both. When OTT connection 52 is active, the network infrastructure can also make decisions to dynamically change the routing (e.g., based on network load balancing considerations or reconfiguration).

[0068] The wireless connection 64 between WD 22 and network node 16 is based on the teachings of embodiments described throughout this disclosure. One or more embodiments in various embodiments improve the performance of OTT services provided to WD 22 using OTT connection 52, wherein wireless connection 64 can form the final segment. More precisely, the teachings of some embodiments in these embodiments can improve data rates, latency, and / or power consumption, and thus provide benefits such as reduced user wait times, relaxed file size limits, better responsiveness, and extended battery life.

[0069] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 52 between host computer 24 and WD 22 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 52 may be implemented in software 48 of host computer 24 or software 90 of WD 22, or both. In embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 52 passes; sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that software 48, 90 may calculate or estimate based on. Reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect network node 16 and may be unknown or imperceptible to network node 16. Such procedures and functionality may be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, thereby facilitating measurements of throughput, propagation time, latency, etc., by host computer 24. In some embodiments, the measurement can be achieved by software 48, 90 using OTT connection 52 to cause a message to be transmitted, particularly an empty message or a "dummy" message, while it monitors propagation time, errors, etc.

[0070] Therefore, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward user data to a cellular network for transmission to WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, network node 16 is configured and / or processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22, and / or preparing / terminating / maintaining / supporting / terminating transmissions received from WD 22.

[0071] In some embodiments, host computer 24 includes processing circuitry 42 and a communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / terminating transmissions received from network node 16.

[0072] although Figure 1 and Figure 2Various “units” such as MIB unit 32 and MIB decoding unit 34 are shown within the respective processors, but it is conceivable that these units can be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the unit can be implemented within the processing circuitry in hardware or a combination of hardware and software.

[0073] Figure 3 This is a flowchart illustrating an exemplary method implemented in a communication system according to one embodiment, such as, for example, Figure 1 and Figure 2 The communication system may include a host computer 24, a network node 16, and a WD22, which may be reference... Figure 2 The methods described herein are as follows. In the first step, host computer 24 provides user data (block S100). In an optional sub-step of the first step, host computer 24 provides user data by executing a host application, such as, for example, host application 50 (block S102). In the second step, host computer 24 initiates a transmission carrying user data to WD 22 (block S104). In an optional third step, in accordance with the teachings of the embodiments described herein, network node 16 transmits the user data carried in the transmission initiated by host computer 24 to WD 22 (block S106). In an optional fourth step, WD 22 executes a client application, such as client application 92, associated with host application 50 executed by host computer 24 (block S108).

[0074] Figure 4 This is a flowchart illustrating an exemplary method implemented in a communication system according to one embodiment, such as, for example, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced. Figure 1 and Figure 2 The methods described herein. In the first step, host computer 24 provides user data (block S110). In an optional sub-step (not shown), host computer 24 provides user data by executing a host application, such as, for example, host application 50. In the second step, host computer 24 initiates a transmission carrying the user data to WD 22 (block S112). According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried via network node 16. In an optional third step, WD 22 receives the user data carried in the transmission (block S114).

[0075] Figure 5 This is a flowchart illustrating an exemplary method implemented in a communication system according to one embodiment, such as, for example, Figure 1The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced. Figure 1 and Figure 2 The methods described herein. In an optional first step, WD 22 receives input data provided by host computer 24 (block S116). In an optional sub-step of the first step, WD 22 executes client application 92, which provides user data in response to the received input data provided by host computer 24 (block S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (block S120). In an optional sub-step of the second step, WD provides user data by executing a client application, such as, for example, client application 92 (block S122). When providing user data, the executed client application 92 may also consider user input received from the user. Regardless of the specific manner in which user data is provided, in an optional third sub-step, WD 22 may initiate the transmission of user data to host computer 24 (block S124). In a fourth step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, host computer 24 receives user data transmitted from WD 22 (block S126).

[0076] Figure 6 This is a flowchart illustrating an exemplary method implemented in a communication system according to one embodiment, such as, for example, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be referenced. Figure 1 and Figure 2 The methods described herein. In an optional first step, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, network node 16 initiates the transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0077] Figure 7This is a flowchart of an exemplary process in network node 16. One or more blocks and / or functions performed by network node 16 may be performed by one or more elements of network node 16, such as MIB unit 32, processor 70, communication interface 60, radio interface 62, etc. in processing circuitry 68. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to perform at least one of the following: (A) using (block S134) a reserved bit of the master information block (MIB) transmitted to WD as an indication of at least one of an instruction for the existence of an extended MIB (eMIB) and an instruction to interpret at least a portion of the contents of the MIB in a predefined manner; and (B) replacing (block S136) at least a portion of the MIB with content encoded according to a second communication standard, which is different from the content encoded according to a first communication standard of the MIB.

[0078] In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60, to transmit the eMIB such that the eMIB cannot be detected by conventional WD 22. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60, to use at least one of a Physical Broadcast Channel (PBCH) scrambling sequence different from that used for the eMIB and a PBCH Cyclic Redundancy Check (CRC) different from that used for the current eMIB, such that the eMIB cannot be detected by conventional WD 22 and / or decoded by conventional WD 22. In one or more embodiments, network node 16 is configured, for example via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60, to use at least one of a primary synchronization signal (PSS) and secondary synchronization signal (SSS) having values ​​that do not represent a valid combination according to the MIB specification if the synchronization signal block (SSB) structure is reused.

[0079] In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to define the transmission timing of the eMIB in relation to the MIB. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to use the next possible MIB timing relative to a MIB in which the eMIB is marked, for example, by one or more reserved bits. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to repurpose resource elements occupied by at least one of PSS or SSS. For example, PSS / SSS may not be required for eMIB transmission, allowing network node 16 to use resource elements otherwise occupied by PSS / SSS for other purposes, such as carrying other data, information, and / or signaling. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to transmit eMIB using fewer orthogonal frequency division multiplexing (OFDM) symbols than those used for SSB.

[0080] Figure 8 This is a flowchart of another exemplary process in network node 16 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by network node 16 may be performed by one or more elements of network node 16, such as MIB unit 32, processor 70, communication interface 60, radio interface 62, etc., in processing circuitry 68. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to cause (block S138) the transmission of bits of the Master Information Block (MIB), the bits of which provide an indication of the presence of MIB extensions and / or instructions to interpret at least a portion of the contents of the MIB in a predefined manner, as described herein.

[0081] According to one or more embodiments, the bit is a reserved bit in the MIB. According to one or more embodiments, the bit in the MIB provides an indication of the presence of a MIB extension, and the processing circuit 68 is further configured to induce the transmission of the MIB extension. According to one or more embodiments, the processing circuit 68 is configured to induce the transmission of the MIB extension in response to a bit in the MIB having a predefined value.

[0082] According to one or more embodiments, the MIB extension is an additional MIB. According to one or more embodiments, the MIB extension is transmitted via the Physical Broadcast Channel (PBCH). According to one or more embodiments, processing circuitry 68 is configured to facilitate the transmission of the Physical Downlink Control Channel, the configuration of which is indicated by the MIB extension. According to one or more embodiments, the MIB defines a CORESET#0, and the MIB extension defines a different CORESET#0 with a smaller bandwidth than the CORESET#0 defined by the MIB.

[0083] According to one or more embodiments, the size of the MIB extension is smaller than the size of the MIB. According to one or more embodiments, a different scrambling sequence is used for the MIB extension compared to the scrambling sequence used for the MIB. According to one or more embodiments, a different CRC is used for the MIB extension compared to the CRC used for the MIB. According to one or more embodiments, interpreting at least a portion of the content of the MIB in a predefined manner includes at least one of the following: interpreting at least a portion of the content of the MIB in a first predefined manner in response to bits of the MIB having a first value, and interpreting at least a portion of the content of the MIB in a second predefined manner in response to bits of the MIB having a second value.

[0084] Figure 9 This is a flowchart of another exemplary process in network node 16 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by network node 16 may be performed by one or more elements of network node 16, such as MIB unit 32, processor 70, communication interface 60, radio interface 62, etc., in processing circuitry 68. In one or more embodiments, network node 16 is configured, for example, via one or more of processing circuitry 68, processor 70, radio interface 62, and communication interface 60 to facilitate (block S140) the transmission of a Master Information Block (MIB), wherein at least a portion of the contents of the MIB is decipherable using a first configuration, which differs from a second configuration previously stored at wireless device 22 for deciphering the MIB, as described herein.

[0085] According to one or more embodiments, a first configuration corresponds to a first table of at least a first CORESET configuration, and a second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments, a first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments, a first configuration corresponds to a first version of a wireless communication standard; and a second configuration corresponds to a second version of a wireless communication standard that is different from the first version.

[0086] According to one or more embodiments, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration. According to one or more embodiments, the MIB associated with the first configuration uses a CRC different from the cyclic redundancy check (CRC) associated with the second configuration. According to one or more embodiments, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments, the processing circuitry is further configured to cause the transmission of signaling indicating the first configuration, which is configured to replace the second configuration.

[0087] Figure 10 This is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as the MIB decoding unit 34, processor 86, radio interface 82, etc. in the processing circuitry 84. In one or more embodiments, the wireless device 22 is configured, for example, via one or more of the processing circuitry 84, processor 86, and radio interface 82 to perform at least one of the following: (A) using reserved bits of the received Master Information Block (MIB) as an indication of the presence of an Extended MIB (eMIB) and an instruction to decode at least a portion of the content of the MIB in a predefined manner; and (B) decoding at least a portion of the MIB content according to a second communication standard (block S144), which is different from the first communication standard used for decoding at least a portion of the MIB content, as described herein.

[0088] In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to receive and decode eMIB. In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to use at least one of a Physical Broadcast Channel (PBCH) scrambling sequence different from the MIB and a PBCH Cyclic Redundancy Check (CRC) different from the MIB. In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to use at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) having values ​​that do not represent a valid combination according to the MIB specification if the Synchronization Signal Block (SSB) structure is reused.

[0089] In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to decode the reception timing of an eMIB associated with a MIB. In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to interpret subsequently received MIBs as eMIBs, i.e., interpreting MIBs received after a MIB tag as eMIBs, allowing WD 22 to interpret MIBs together with any accompanying MIBs (i.e., eMIBs). In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to interpret resource elements occupied by at least one of a PSS or SSS. In one or more embodiments of WD 22, WD 22 is configured to and / or include a radio interface and / or processing circuitry configured to receive eMIBs using a fewer number of Orthogonal Frequency Division Multiplexing (OFDM) symbols than those used for an SSB.

[0090] Figure 11 This is a flowchart of exemplary processes in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as the MIB decoding unit 34, processor 86, radio interface 82, etc., in the processing circuitry 84. In one or more embodiments, the wireless device 22 is configured, for example, via one or more of the processing circuitry 84, processor 86, and radio interface 82 to receive (block S146) the Master Information Block (MIB), as described herein. In one or more embodiments, the wireless device 22 is configured, for example, via one or more of the processing circuitry 84, processor 86, and radio interface 82 to use (block S148) bits of the MIB as an indication of the presence of a MIB extension and / or as instructions to decode at least a portion of the contents of the MIB in a predefined manner, as described herein.

[0091] According to one or more embodiments, the bit is a reserved bit in the MIB. According to one or more embodiments, the processing circuit 84 is configured to use the bit of the MIB as an indication of the presence of a MIB extension and to receive the MIB extension. According to one or more embodiments, the processing circuit 84 is configured to receive the MIB extension in response to a bit of the MIB having a predefined value.

[0092] According to one or more embodiments, the MIB extension is an additional MIB. According to one or more embodiments, the MIB extension is received via the Physical Broadcast Channel (PBCH). According to one or more embodiments, the processing circuitry 84 is configured to determine the configuration for receiving the Physical Downlink Control Channel based at least on the MIB extension.

[0093] According to one or more embodiments, the MIB defines a CORESET#0, and the MIB extension defines a different CORESET#0 with a smaller bandwidth than the CORESET#0 defined by the MIB. According to one or more embodiments, the size of the MIB extension is smaller than the size of the MIB. According to one or more embodiments, a different scrambling sequence is used for the MIB extension compared to the scrambling sequence used for the MIB. According to one or more embodiments, a different CRC is used for the MIB extension compared to the CRC used for the MIB. According to one or more embodiments, interpreting at least a portion of the content of the MIB in a predefined manner includes at least one of the following: interpreting at least a portion of the content of the MIB in a first predefined manner in response to a bit of the MIB having a first value, and interpreting at least a portion of the content of the MIB in a second predefined manner in response to a bit of the MIB having a second value.

[0094] Figure 12 This is a flowchart of exemplary processes in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as the MIB decoding unit 34, processor 86, radio interface 82, etc., in the processing circuitry 84. In one or more embodiments, the wireless device 22 is configured, for example, via one or more of the processing circuitry 84, processor 86, and radio interface 82 to receive (block S150) a Master Information Block (MIB). In one or more embodiments, the wireless device 22 is configured, for example, via one or more of the processing circuitry 84, processor 86, and radio interface 82 to decode (block S152) at least a portion of the contents of the MIB using a first configuration, which differs from a second configuration previously stored for decoding the MIB.

[0095] According to one or more embodiments, a first configuration corresponds to a first table of at least a first CORESET configuration, and a second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. According to one or more embodiments, a first CORESET configuration corresponds to CORESET#0 having a bandwidth smaller than that of the second CORESET configuration. According to one or more embodiments, a first configuration corresponds to a first version of a wireless communication standard, wherein the second configuration corresponds to a second version of the wireless communication standard that is different from the first version.

[0096] According to one or more embodiments, the MIB associated with the first configuration uses a scrambling sequence different from the scrambling sequence associated with the second configuration. According to one or more embodiments, the MIB associated with the first configuration uses a CRC different from the cyclic redundancy check (CRC) associated with the second configuration. According to one or more embodiments, the MIB associated with the first configuration uses a PSS / SSS structure different from the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration. According to one or more embodiments, the processing circuitry is further configured to receive signaling indicating the first configuration, whereby the first configuration replaces the second configuration.

[0097] The general process flow of the arrangements of this disclosure has been described, and examples of hardware and software arrangements for implementing the processes and functions of this disclosure have been provided. The following sections provide details and examples of arrangements for extending, reusing, and reinterpreting MIB content.

[0098] In some embodiments, information can be added to the SIB in a backward-compatible manner. The SIB is scheduled in a manner similar to that performed in data transmission according to existing wireless communication protocols. In some embodiments, the PDCCH can indicate to the WD22 that it wants to receive the Physical Downlink Shared Channel (PDSCH), and the PDSCH contains one or more SIBs. Since the payload size and structure can be indicated on the PDCCH and are not mandated by known communication standards (e.g., known 3GPP communication standards), it is possible to add information to the SIB in a backward-compatible manner.

[0099] Some embodiments provide reserved bits in the MIB to indicate the presence of an "extended MIB" (eMIB, also known as an additional MIB and / or MIB extension). This bit is reserved for existing 3GPP Rel-15 WD 22 and / or legacy WD 22, and WD 22 does not expect any specific value in the reserved bits. For future 3GPP Rel-X implementations as defined at least in part herein, the reserved bits are used to indicate the presence / absence of the "extended MIB," for example, a 0 in the reserved bits indicates no eMIB, such that WD 22 reinterprets / deprecates the MIB in a predefined manner according to existing wireless communication standards such as the 3GPP Rel-15 specification, and a 1 in the reserved bits indicates the presence of the eMIB as described herein. As used herein, 3GPP Rel-X can refer to one or more future versions of the 3GPP wireless communication standard as defined at least in part according to the teachings described herein.

[0100] The eMIB can be transmitted in a manner invisible to the conventional WD 22, for example via one or more of the processing circuitry 68, processor 70, radio interface 62, MIB unit 32, etc. To avoid specifying additional physical channel structures, it is preferable to reuse the existing PBCH structure or even the entire Synchronization Signal Block (SSB) structure. For example, the eMIB can be made invisible to the conventional WD 22 by using a different scrambling sequence than the current MIB, or by using a different Cyclic Redundancy Check (CRC) than the current MIB, such as via one or more of the processing circuitry 68, processor 70, radio interface 62, MIB unit 32, etc., to ensure that the conventional WD 22 cannot incorrectly decode the eMIB as a regular MIB. If the SSB structure is reused, different primary synchronization signals (PSS) and / or secondary synchronization signals (SSS) with values ​​that do not represent valid combinations according to current specifications can be used to avoid the conventional WD 22 detecting and / or decoding the eMIB.

[0101] For eMIBs, PSS / SSS may not be necessary, and therefore the resource elements occupied by these signals can be reused for other purposes. Specifically, if an eMIB is transmitted in an SS block similar to the SS block in which the MIB is transmitted, then the PSS / SSS will be the same SS block as the eMIB. Alternatively, the eMIB can be transmitted using fewer OFDM symbols than currently used for the SSB, such as via one or more of processing circuitry 68, processor 70, radio interface 62, MIB unit 32, etc. The transmission timing of the eMIB can be defined relative to the current MIB, for example, the next possible MIB timing when the eMIB is used.

[0102] In another embodiment, reserved bits in the MIB can be used to indicate the reinterpretation of one or more existing fields in the MIB, or the interpretation of one or more existing fields in the MIB in a predefined manner, such as a predefined manner different from a predefined manner / path if the reserved bits do not indicate such a way. In such an embodiment, for 3GPP MIB 22, the bits are reserved, and WD 22 does not expect any particular value; that is, WD 22 operates in a predefined "normal" manner, for example, according to the current (i.e., known) 3GPP MIB specification.

[0103] For future 3GPP Rel-X WD 22 (i.e., WD 22 implementing future 3GPP Rel-X), reserved bits are used to indicate whether one or more existing fields in the MIB will be reinterpreted and / or reinterpreted in a predefined manner. For example, a 0 in the reserved bits indicates no reinterpretation and operation, otherwise, according to existing wireless communication standards such as the 3GPP Rel-15 specification as a case for a "normal" MIB, and a 1 in the reserved bits indicates that the MIB is reinterpreted and / or reinterpreted in a manner different from the predefined method for interpreting a "normal" MIB. For example, pdcch-ConfigSIB1 in existing communication standards can be configured to indicate CORESET (i.e., CORESET#0) and PDCCH time-domain location / monitoring timing (i.e., search space#0), where this indication can be redefined for 3GPP Rel-X WD22. In such an embodiment, if the reserved bit in the MIB is 0, then pdcch-ConfigSIB1 carries the same meaning for 3GPP Rel-X WD 22 as it does for 3GPP Rel-15 WD 22 (i.e., interpreted in a first predefined manner), such that WD 22 uses, for example, CORESET#0 and search space #0 as defined in existing communication standards (e.g., 3GPP Rel-15). If the reserved bit in the MIB is 1, then pdcch-Config1 can carry a different meaning for 3GPP Rel-X WD 22 compared to 3GPP Rel-15 WD 22 (i.e., interpreted and / or defined in a second predefined manner different from the first predefined manner). For example, where the reserved bit in the MIB is equal to 1, pdcch-ConfigSIB1 can indicate another CORESET#0 configuration (e.g., with reduced bandwidth, such as when compared to CORESET #0 which can be defined in existing communication standards) and a new search space #0 configuration (e.g., a new monitoring timing) for use with WD 22, that is, to interpret the MIB in a predefined way that is different from another interpretation that can be applied to the MIB.

[0104] For backward capability, the network may need to transmit PDCCH scheduling SIB1 for 3GPP Rel-15 WD 22 according to the configuration signaled in pdcch-ConfigSIB1. In practice, network node 16 needs to configure two CORESET #0s (corresponding search space #0s) for scheduling SIBs, such as via processing circuitry 68, processor 70, radio interface 62, MIB unit 32, etc. This two CORESET #0 configuration helps accommodate the reduced capability of the WD 22, which has reduced bandwidth capabilities compared to the 3GPP Rel-15 WD 22. For example, the 3GPP Rel-15 WD 22 can interpret this field to receive a first CORESET #0 as performed in the existing WD 22. However, the 3GPP Rel-X WD 22 can reinterpret this field as described herein to receive a second CORESET #0 with reduced bandwidth compared to the first CORESET #0. In other words, in one or more embodiments, 3GPP Rel-X WD 22 may apply different definitions, for example, based on the values ​​of reserved bits in the MIB, to interpret one or more fields in the MIB.

[0105] In the third embodiment, no eMIB is used, but the MIB content is interpreted in a predefined manner and / or reinterpreted compared to existing (i.e., known) versions of the 3GPP specification (without involving new functionality of the aforementioned reserved bits). For example, the table configured in CORESET#0 may be replaced by a new table defined for a future version of the NR specification. In one or more embodiments, one or more tables, configurations, etc., may be stored by WD 22 in a memory such as memory 88 and / or received from network node 16 via signaling. To avoid the conventional WD 22 potentially finding and using the MIB, several possibilities exist in the event of a potential misinterpretation of the content. For example, in some embodiments, a different PBCH scrambling sequence, a different PBCH CRC, or a different PSS / SSS structure may be used than the current SSB.

[0106] Some examples Example A1. A network node 16 configured to communicate with a wireless device 22 (WD 22), the network node 16 being configured to and / or include a radio interface 62 and / or include processing circuitry 68, which is configured to perform at least one of the following: The reserved bits of the Master Information Block (MIB) transmitted to the WD 22 are used as an indication of at least one of the instructions for the existence of the Extended MIB (eMIB) and the reinterpretation of at least a portion of the MIB's contents; and At least a portion of the MIB is replaced with content encoded according to a second communication standard, wherein the content encoded according to the second communication standard is different from the content encoded according to a first communication standard of the MIB.

[0107] Example A2. The network node 16 according to Example A1 is configured to and / or include a radio interface 62 and / or include processing circuitry 68, which is configured to transmit an eMIB such that the eMIB cannot be detected by the conventional WD 22.

[0108] Example A3. The network node 16 according to any one of Examples A1 and A2 is configured to and / or include a radio interface 62 and / or include processing circuitry 68 configured to use at least one of a Physical Broadcast Channel (PBCH) scrambling sequence different from the MIB and a PBCH Cyclic Redundancy Check (CRC) different from the current MIB.

[0109] Example A4. The network node 16 according to any of Examples A1-A3 is configured to and / or include a radio interface 62 and / or include processing circuitry 68, which is configured to use at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) having values ​​that do not represent a valid combination according to the MIB specification if the synchronization signal block (SSB) structure is reused.

[0110] Example A5. The network node 16 according to any of Examples A1-A4 is configured to and / or include a radio interface 62 and / or include processing circuitry 68 configured to define the transmission timing of the eMIB in relation to the MIB.

[0111] Example A6. The network node 16 according to any of Examples A1-A5 is configured to and / or include a radio interface 62 and / or include processing circuitry 68 configured to use the next possible MIB opportunity for eMIB.

[0112] Example A7. The network node 16 according to any one of Examples A1-A6 is configured to and / or include a radio interface 62 and / or include processing circuitry 68 configured to reuse resource elements occupied by at least one of the PSS and SSS.

[0113] Example A8. The network node 16 according to any of Examples A1-A7 is configured to and / or include a radio interface 62 and / or include processing circuitry 68 configured to transmit the eMIB using fewer orthogonal frequency division multiplexing (OFDM) symbols than those used for the SSB associated with the MIB.

[0114] Example B1. A method implemented in network node 16, the method comprising at least one of the following: The reserved bits of the Master Information Block (MIB) transmitted to the WD 22 serve as an indication of at least one of the instructions for the existence of the Extended MIB (eMIB) and the reinterpretation of at least a portion of the MIB's contents; and At least a portion of the MIB is replaced with content encoded according to a second communication standard, wherein the content encoded according to the second communication standard is different from the content encoded according to a first communication standard of the MIB.

[0115] Example B2. The method according to Example B1 includes transmitting an eMIB such that the eMIB cannot be detected by a conventional WD 22.

[0116] Example B3. The method according to any one of Examples B1 and B2 includes at least one of using a physical broadcast channel (PBCH) scrambling sequence different from the MIB and a PBCH cyclic redundancy check (CRC) different from the MIB.

[0117] Example B4. The method according to any one of Examples B1-B3 includes, if the synchronization signal block (SSB) structure is reused, using at least one of the primary synchronization signal (PSS) and secondary synchronization signal (SSS) that have values ​​that do not represent a valid combination according to the MIB specification.

[0118] Example B5. The method according to any one of Examples B1-B4 includes defining the transmission timing of the eMIB in relation to the MIB.

[0119] Example B6. The method according to any one of Examples B1-B5 includes using the next possible MIB timing for the eMIB.

[0120] Example B7. The method according to any one of Examples B1-B6 includes reusing a resource element occupied by at least one of PSS or SSS.

[0121] Example B8. The method according to any of Examples B1-B7 includes transmitting the eMIB using fewer orthogonal frequency division multiplexing (OFDM) symbols than the number of orthogonal frequency division multiplexing (OFDM) symbols used for the SSB associated with the MIB.

[0122] Example C1. A wireless device 22 (WD 22) configured to communicate with a network node 16e, the WD 22 being configured to and / or include a radio interface 82 and / or processing circuitry 84, which is configured to perform at least one of the following operations: Using the reserved bits of the received Master Information Block (MIB) as an indication of at least one of the instructions for the existence of the Extended MIB (eMIB) and for reinterpreting at least a portion of the MIB's contents; and Decode at least a portion of the MIB content according to a second communication standard, which is different from a first communication standard used to decode at least a portion of the MIB content.

[0123] Example C2. According to WD 22 of Example C1, it is configured to and / or include a radio interface 82 and / or processing circuitry 84, which is configured to receive and decode eMIB.

[0124] Example C3. The WD 22 according to any one of Examples C1 and C2 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to use at least one of a Physical Broadcast Channel (PBCH) scrambling sequence different from the MIB and a PBCH Cyclic Redundancy Check (CRC) different from the MIB.

[0125] Example C4. The WD 22 according to any one of Examples C1-C3 is configured to and / or include a radio interface 82 and / or processing circuitry 84, which is configured to use at least one of the different primary synchronization signal (PSS) or secondary synchronization signal (SSS) having values ​​that do not represent valid combinations according to the MIB specification if the synchronization signal block (SSB) structure is reused.

[0126] Example C5. The WD 22 according to any one of Examples C1-C4 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to receive timing decoding of the eMIB associated with the MIB.

[0127] Example C6. The WD 22 according to any one of Examples C1-C5 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to interpret subsequently received MIBs as eMIBs.

[0128] Example C7. The WD 22 according to any one of Examples C1-C6 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to interpret resource elements occupied by at least one of the PSS or SSS.

[0129] Example C8. The WD 22 according to any of Examples C1-C7 is configured to and / or include a radio interface 82 and / or processing circuitry 84 configured to receive the eMIB using fewer orthogonal frequency division multiplexing (OFDM) symbols than the number of orthogonal frequency division multiplexing (OFDM) symbols used for the SSB associated with the MIB.

[0130] Example D1. A method implemented in a wireless device 22 (WD 22), the method comprising at least one of the following: The reserved bits of the Master Information Block (MIB) received by WD 22 are used as an indication of at least one of the instructions for the existence of the Extended MIB (eMIB) and the reinterpretation of at least a portion of the MIB's contents; and Decode at least a portion of the MIB content according to a second communication standard, which is different from the first communication standard of the MIB.

[0131] Example D2. The method described according to Example D1 includes receiving and decoding eMIB.

[0132] Example D3. The method according to any one of Examples D1 and D2 includes at least one of using a scrambling sequence of a Physical Broadcast Channel (PBCH) different from the MIB and a PBCH Cyclic Redundancy Check (CRC) different from the MIB.

[0133] Example D4. The method according to any one of Examples D1-D3 includes, if the synchronization signal block (SSB) structure is reused, using at least one of the primary synchronization signal (PSS) and secondary synchronization signal (SSS) that have values ​​that do not represent a valid combination according to the MIB specification.

[0134] Example D5. The method according to any one of Examples D1-D4 includes receiving timing decoding of the eMIB associated with the MIB.

[0135] Example D6. The method according to any one of Examples D1-D5 includes interpreting the subsequently received MIB as an eMIB.

[0136] Example D7. The method according to any one of Examples D1-D6 includes interpreting a resource element occupied by at least one of PSS or SSS.

[0137] Example D8. The method according to any of Examples D1-D7 includes receiving the eMIB using fewer orthogonal frequency division multiplexing (OFDM) symbols than the number of orthogonal frequency division multiplexing (OFDM) symbols used for the SSB associated with the MIB.

[0138] As those skilled in the art will understand, the concepts described herein can be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects, all of which are generally referred to herein as “circuit” or “module.” Any process, step, action, and / or functionality described herein can be performed by and / or associated with a corresponding module, which can be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can take the form of a computer program product on a tangible computer-readable storage medium having computer program code embodied in that medium that is executable by a computer. Any suitable tangible computer-readable medium can be utilized, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0139] This document describes some embodiments with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thus creating a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executable via the processor of the computer or other programmable data processing apparatus, create components for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0140] These computer program instructions may also be stored in a computer-readable storage medium or storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of writing comprising instruction components that implement the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0141] Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0142] It should be understood that the functions / actions indicated in the boxes may not occur in the order shown in the operation diagram. For example, depending on the functions / actions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Although some of the diagrams include arrows on the communication path to indicate the main direction of communication, it should be understood that communication may occur in the opposite direction to the arrows depicted.

[0143] Computer program code used to perform the operations of the concepts described herein can be written in an object-oriented programming language, such as Java® or C++. However, computer program code used to perform the operations of this disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (e.g., via the Internet using an Internet service provider).

[0144] This document has disclosed numerous different embodiments in conjunction with the foregoing description and accompanying drawings. It will be understood that a literal description and illustration of every combination and sub-combination of these embodiments would be excessively repetitive and confusing. Therefore, all embodiments can be combined in any manner and / or combination, and this specification, including the accompanying drawings, should be interpreted as a complete written description of all combinations and sub-combinations constituting the embodiments described herein, as well as the ways and processes of making and using them, and should support the claims for any such combinations or sub-combinations.

[0145] Those skilled in the art will understand that the embodiments described herein are not limited to those specifically shown and described above. Furthermore, unless stated to the contrary above, it should be noted that all drawings are not to scale. Various modifications and variations are possible in accordance with the foregoing teachings without departing from the scope of the following claims.

Claims

1. A wireless device (22) configured to communicate with a network node (16), the wireless device comprising: Processing circuit (84), the processing circuit (84) being configured to: Receive the master information block (MIB), wherein the MIB defines CORESET#0; as well as The bits of the MIB are used as an indication of the presence of a MIB extension, wherein the MIB extension is an additional MIB and defines a different CORESET#0 with a bandwidth smaller than that defined by the MIB.

2. The wireless device of claim 1, wherein, The bit is a reserved bit in the MIB.

3. The wireless device according to any one of claims 1-2, wherein, The processing circuit is configured to: Receive the MIB extension.

4. The wireless device according to claim 3, wherein, The processing circuitry is configured to receive the MIB extension in response to the MIB having a predefined value.

5. The wireless device according to claim 3, wherein, The MIB extension is received via the Physical Broadcast Channel (PBCH).

6. The wireless device according to claim 3, wherein, The bandwidth of CORESET#0 defined by the MIB is at least 24 resource blocks, and the bandwidth of CORESET#0 defined by the MIB extension is less than 24 resource blocks.

7. The wireless device according to claim 3, wherein, The size of the MIB extension is smaller than the size of the MIB.

8. The wireless device according to claim 3, wherein, A different scrambling sequence was used for the MIB expansion compared to the scrambling sequence used for the MIB.

9. The wireless device according to claim 3, wherein, A different CRC is used for the MIB extension compared to the CRC used for the MIB.

10. The wireless device according to any one of claims 1-2, wherein, The processing circuitry is configured to further use bits of the MIB as instructions to interpret at least a portion of the MIB's content in a predefined manner, and interpreting at least a portion of the MIB's content in a predefined manner includes at least one of the following: In response to the bit of the MIB having a first value, at least a portion of the content of the MIB is interpreted in a first predefined manner; and In response to the bit of the MIB having a second value, at least a portion of the content of the MIB is interpreted in a second predefined manner.

11. The wireless device according to claim 10, wherein, The bit is a reserved bit in the MIB, wherein the portion of the MIB content includes pdcch-ConfigSIB1, and wherein if the reserved bit in the MIB is 1, pdcch-ConfigSIB1 indicates a different CORESET#0 and a different search space#0 than if the reserved bit in the MIB is 0.

12. A method implemented by a wireless device (22) configured to communicate with a network node (16), the method comprising: Receive (S146) Master information block MIB, wherein the MIB defines CORESET#0; as well as The bits of the MIB (S148) are used as an indication of the presence of a MIB extension, wherein the MIB extension is an additional MIB and defines a different CORESET#0 having a smaller bandwidth than that defined by the MIB.

13. The method according to claim 12, wherein, The bit is a reserved bit in the MIB.

14. The method according to any one of claims 12-13, further comprising: Receive the MIB extension.

15. The method of claim 14, further comprising receiving the MIB extension in response to the MIB having a predefined value.

16. The method of claim 14, wherein, The MIB extension is received via the Physical Broadcast Channel (PBCH).

17. The method according to claim 14, wherein, The bandwidth of CORESET#0 defined by the MIB is at least 24 resource blocks, and the bandwidth of CORESET#0 defined by the MIB extension is less than 24 resource blocks.

18. The method according to claim 14, wherein, The size of the MIB extension is smaller than the size of the MIB.

19. The method of claim 14, wherein, A different scrambling sequence was used for the MIB expansion compared to the scrambling sequence used for the MIB.

20. The method of claim 14, wherein, A different CRC is used for the MIB extension compared to the CRC used for the MIB.

21. The method according to any one of claims 12-13, wherein, The method includes further using bits of the MIB as instructions to interpret at least a portion of the content of the MIB in a predefined manner, and interpreting at least a portion of the content of the MIB in a predefined manner includes at least one of the following: In response to the bit of the MIB having a first value, at least a portion of the content of the MIB is interpreted in a first predefined manner; and In response to the bit of the MIB having a second value, at least a portion of the content of the MIB is interpreted in a second predefined manner.

22. The method according to claim 21, wherein, The bit is a reserved bit in the MIB, wherein the portion of the MIB content includes pdcch-ConfigSIB1, and wherein if the reserved bit in the MIB is 1, pdcch-ConfigSIB1 indicates a different CORESET#0 and a different search space#0 than if the reserved bit in the MIB is 0.

23. A network node (16) configured to communicate with a wireless device (22), the network node comprising: Processing circuit (68) configured to cause transmission of a main information block (MIB), wherein the MIB defines CORESET#0, and bits of the MIB provide an indication of the presence of a MIB extension, wherein the MIB extension is an additional MIB and defines a different CORESET#0 having a smaller bandwidth than the CORESET#0 defined by the MIB.

24. The network node according to claim 23, wherein, The bit is a reserved bit in the MIB.

25. The network node according to any one of claims 23-24, wherein, The processing circuitry is also configured to enable transmission for MIB extension.

26. The network node according to claim 25, wherein, The processing circuitry is configured to cause the transmission of the MIB extension in response to the MIB having a predefined value.

27. The network node according to claim 25, wherein, The MIB extension is transmitted via the Physical Broadcast Channel (PBCH).

28. The network node according to claim 25, wherein, The bandwidth of CORESET#0 defined by the MIB is at least 24 resource blocks, and the bandwidth of CORESET#0 defined by the MIB extension is less than 24 resource blocks.

29. The network node according to claim 25, wherein, The size of the MIB extension is smaller than the size of the MIB.

30. The network node according to claim 25, wherein, A different scrambling sequence was used for the MIB expansion compared to the scrambling sequence used for the MIB.

31. The network node according to claim 25, wherein, A different CRC is used for the MIB extension compared to the CRC used for the MIB.

32. The network node according to claim 25, wherein, The bits of the MIB further provide instructions for interpreting at least a portion of the contents of the MIB in a predefined manner, and interpreting at least a portion of the contents of the MIB in a predefined manner includes at least one of the following: In response to the bit of the MIB having a first value, at least a portion of the content of the MIB is interpreted in a first predefined manner; and In response to the bit of the MIB having a second value, at least a portion of the content of the MIB is interpreted in a second predefined manner.

33. The network node according to claim 32, wherein, The bit is a reserved bit in the MIB, wherein the portion of the MIB content includes pdcch-ConfigSIB1, and wherein if the reserved bit in the MIB is 1, pdcch-ConfigSIB1 indicates a different CORESET#0 and a different search space#0 than if the reserved bit in the MIB is 0.

34. A method implemented by a network node (16) configured to communicate with a wireless device (22), the method comprising causing (S138) the transmission of a main information block (MIB), wherein the MIB defines a CORESET#0, bits of the MIB provide an indication of the presence of a MIB extension, wherein the MIB extension is an additional MIB and defines a different CORESET#0 having a smaller bandwidth than the CORESET#0 defined by the MIB.

35. The method according to claim 34, wherein, The bit is a reserved bit in the MIB.

36. The method according to any one of claims 34-35, wherein, The method also includes a transmission that enables the MIB to expand.

37. The method of claim 36, wherein, It also includes a transmission that causes the MIB to expand in response to the MIB having a predefined value.

38. The method according to claim 36, wherein, The MIB extension is transmitted via the Physical Broadcast Channel (PBCH).

39. The method according to claim 36, wherein, The bandwidth of CORESET#0 defined by the MIB is at least 24 resource blocks, and the bandwidth of CORESET#0 defined by the MIB extension is less than 24 resource blocks.

40. The method of claim 36, wherein, The size of the MIB extension is smaller than the size of the MIB.

41. The method according to claim 36, wherein, A different scrambling sequence was used for the MIB expansion compared to the scrambling sequence used for the MIB.

42. The method according to claim 36, wherein, A different CRC is used for the MIB extension compared to the CRC used for the MIB.

43. The method according to claim 36, wherein, The bits of the MIB further provide instructions for interpreting at least a portion of the contents of the MIB in a predefined manner, and interpreting at least a portion of the contents of the MIB in a predefined manner includes at least one of the following: In response to the bit of the MIB having a first value, at least a portion of the content of the MIB is interpreted in a first predefined manner; and In response to the bit of the MIB having a second value, at least a portion of the content of the MIB is interpreted in a second predefined manner.

44. The method according to claim 43, wherein, The bit is a reserved bit in the MIB, wherein the portion of the MIB content includes pdcch-ConfigSIB1, and wherein if the reserved bit in the MIB is 1, pdcch-ConfigSIB1 indicates a different CORESET#0 and a different search space#0 than if the reserved bit in the MIB is 0.

45. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) comprising: Processing circuit (84), the processing circuit (84) being configured to: Receive Master Information Block (MIB); as well as At least a portion of the contents of the MIB is interpreted using a first configuration that differs from the second configuration previously stored for interpreting the MIB. Wherein, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. Wherein, the first CORESET configuration corresponds to CORESET#0, which has a smaller bandwidth than the second CORESET configuration.

46. ​​The wireless device (22) according to claim 45, wherein, The first configuration corresponds to the first version of the wireless communication standard; and The second configuration corresponds to a second version of the wireless communication standard that is different from the first version.

47. The wireless device (22) according to any one of claims 45-46, wherein, The MIB associated with the first configuration uses a different scrambling sequence than the scrambling sequence associated with the second configuration.

48. The wireless device (22) according to any one of claims 45-46, wherein, The MIB associated with the first configuration uses a different CRC than the cyclic redundancy check (CRC) associated with the second configuration.

49. The wireless device (22) according to any one of claims 45-46, wherein, The MIB associated with the first configuration uses a different PSS / SSS structure than the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration.

50. The wireless device (22) according to any one of claims 45-46, wherein, The processing circuitry is further configured to receive signaling indicating the first configuration, which replaces the second configuration.

51. A method implemented by a wireless device (22) configured to communicate with a network node (16), the method comprising: Receive (S150) Master Information Block (MIB); as well as At least a portion of the contents of the MIB is interpreted (S152) using a first configuration that differs from the second configuration previously stored for interpreting the MIB. Wherein, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. Wherein, the first CORESET configuration corresponds to CORESET#0, which has a smaller bandwidth than the second CORESET configuration.

52. The method according to claim 51, wherein, The first configuration corresponds to the first version of the wireless communication standard; and The second configuration corresponds to a second version of the wireless communication standard that is different from the first version.

53. The method according to any one of claims 51-52, wherein, The MIB associated with the first configuration uses a different scrambling sequence than the scrambling sequence associated with the second configuration.

54. The method according to any one of claims 51-52, wherein, The MIB associated with the first configuration uses a different CRC than the cyclic redundancy check (CRC) associated with the second configuration.

55. The method according to any one of claims 51-52, wherein, The MIB associated with the first configuration uses a different PSS / SSS structure than the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration.

56. The method according to any one of claims 51-52, further comprising signaling instructing the first configuration to replace the second configuration.

57. A network node (16) configured to communicate with a wireless device (22), the network node (16) comprising: A processing circuit (68) is configured to facilitate the transmission of a main information block (MIB), at least a portion of the contents of which is decipherable using a first configuration different from a second configuration previously stored at the wireless device (22) for deciphering the MIB. Wherein, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. Wherein, the first CORESET configuration corresponds to CORESET#0, which has a smaller bandwidth than the second CORESET configuration.

58. The network node (16) according to claim 57, wherein, The first configuration corresponds to the first version of the wireless communication standard; and The second configuration corresponds to a second version of the wireless communication standard that is different from the first version.

59. The network node (16) according to any one of claims 57-58, wherein, The MIB associated with the first configuration uses a different scrambling sequence than the scrambling sequence associated with the second configuration.

60. The network node (16) according to any one of claims 57-58, wherein, The MIB associated with the first configuration uses a different CRC than the cyclic redundancy check (CRC) associated with the second configuration.

61. The network node (16) according to any one of claims 57-58, wherein, The MIB associated with the first configuration uses a different PSS / SSS structure than the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration.

62. The network node (16) according to any one of claims 57-58, wherein, The processing circuit (68) is also configured to cause the transmission of signaling indicative of the first configuration, which is configured to replace the second configuration.

63. A method implemented by a network node (16) configured to communicate with a wireless device (22), the method comprising: This prompts (S140) the transmission of the Master Information Block (MIB), at least a portion of the content of which is decipherable using a first configuration, which differs from a second configuration previously stored at the wireless device (22) for deciphering the MIB. Wherein, the first configuration corresponds to a first table of at least a first CORESET configuration, and the second configuration corresponds to a second table of at least a second CORESET configuration that is different from at least the first CORESET. Wherein, the first CORESET configuration corresponds to CORESET#0, which has a smaller bandwidth than the second CORESET configuration.

64. The method according to claim 63, wherein, The first configuration corresponds to the first version of the wireless communication standard; and The second configuration corresponds to a second version of the wireless communication standard that is different from the first version.

65. The method according to any one of claims 63-64, wherein, The MIB associated with the first configuration uses a different scrambling sequence than the scrambling sequence associated with the second configuration.

66. The method according to any one of claims 63-64, wherein, The MIB associated with the first configuration uses a different CRC than the cyclic redundancy check (CRC) associated with the second configuration.

67. The method according to any one of claims 63-64, wherein, The MIB associated with the first configuration uses a different PSS / SSS structure than the primary synchronization signal / secondary synchronization signal PSS / SSS structure associated with the second configuration.

68. The method of any one of claims 63-64, further comprising causing the transmission of signaling instructing the first configuration, the first configuration being configured to replace the second configuration.

Images