Multiple types of synchronization signal blocks in a communication network

Abstract

The disclosure relates to a method performed by a communication device. The device monitors for multiple types of synchronization signal blocks (SSBs) in a communication network. The multiple types of SSBs include a first type of SSB that includes one or more synchronization signals and a broadcast channel from which to acquire a first MIB. The first MIB comprises parameters for acquiring a first type of SIB which indicates scheduling information for one or more other SIBs. A second type of SSB that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a second MIB is also included in the multiple types of SSBs. The second MIB comprises information indicating a beam, carrier, or TRP with which the second type of SSB is associated.

Description

[0001] MULTIPLE TYPES OF SYNCHRONIZATION SIGNAL BLOCKS IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to transmission and monitoring of multiple types of synchronization signal blocks in a communication network.

[0004] BACKGROUND

[0005] A communication device in a communication network traditionally uses a synchronization signal block (SSB) to acquire time and frequency synchronization and to acquire System Information for initial access. A communication device can also use an SSB for channel estimation, automatic neighbor relation (ANR), and mobility measurements, as well as use an SSB as a quasi colocation (QCL) root for other channels or signals. An SSB for these purposes includes synchronization signals and a broadcast channel transmitted together on a block of transmission resources. The block of transmission resources may for example consist of transmission resources that are consecutive in time and frequency, e.g., a block of resource elements in four Orthogonal Frequency Division Multiplex (OFDM) symbols across 240 subcarriers. A communication device reads the broadcast channel in order to receive basic System Information (SI) required for initial access to the communication network. A communication device in this regard can acquire a Master Information Block (MIB) from the broadcast channel. The MIB, among other things, indicates the System Frame Number (SFN) as well as parameters for the communication device to acquire a System Information Block (SIB) Type#1 (SIB1). SIB1 carries information relevant to evaluating if the communication device is allowed to access a cell with which the SSB is associated, carries a cell global identity (CGI), and also carries scheduling information for acquiring other SIBs. See, e.g., 3GPP TS 38.331 v17.6.0 for further details. The above SSB may also be referred to as a cell-defining (CD) SSB. This is because the SSB in this case is associated with a CGI.

[0006] A so-called non-CD (NCD) SSB may be defined as well, to be used for other purposes. For example, an NCD-SSB advantageously facilitates deployment of multiple bandwidth parts (BWPs) for a cell and / or non-standalone cells for dual connectivity. For this purpose, SIB1 is not needed. Accordingly, the MIB acquired from an NCD-SSB does not convey parameters for a communication device to acquire SIB1. If a communication device looking for a CD-SSB finds an NCD-SSB, the NCD-SSB contains a pointer to a CD-SSB so as to assist the communication device in finding a CD-SSB.

[0007] Although NCD-SSBs prove helpful for some purposes, challenges nonetheless exist in providing for SSB transmission that is efficient, especially from an energy perspective. Some embodiments in this regard recognize inefficiencies attributed to a CD-SSB serving multiple purposes, including initial access, ANR, and mobility measurements. Because a CD-SSB supports initial access, the CD-SSB must be transmitted more frequently and / or with more System Information content than would otherwise be required for the CD-SSB to just support ANR and / or mobility measurements. Over-dimensioning of a CD-SSB in terms of the purposes it serves thereby introduces inefficiencies in SSB transmission.

[0008] SUMMARY

[0009] To address this and / or other problems, some embodiments herein provide multiple different types of SSBs to enable more efficient SSB transmission. One type of SSB may for instance be transmitted with a timing and / or System Information content that supports initial access, whereas at least one other type of SSB may be transmitted with a timing and / or System Information Content that supports ANR and / or mobility measurements. Some embodiments thereby enable improved efficiency for the latter type(s) of SSBs that target ANR and / or mobility measurements. The latter type(s) of SSBs may for instance be transmitted with less frequency and / or with less System Information content than the type of SSB that supports initial access.

[0010] More particularly, embodiments herein include a method performed by a communication device. The method comprises monitoring for multiple types of synchronization signal blocks, SSBs, in a communication network. The multiple types of SSBs include at least a first type of SSB that is on a synchronization raster, that includes one or more synchronization signals, and that includes a broadcast channel from which to acquire a first Master Information Block, MIB. The first MIB comprises parameters for acquiring a first type of System Information Block, SIB, which indicates scheduling information for one or more other SIBs. The multiple types of SSBs include at least a second type of SSB that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a second MIB. The second MIB comprises information indicating a beam, carrier, or transmission reception point, TRP, with which the second type of SSB is associated.

[0011] Other embodiments herein include a method performed by a radio network node configured for use in a communication network. The method comprises transmitting multiple types of synchronization signal blocks, SSBs. The multiple types of SSBs include at least a first type of SSB that is on a synchronization raster, that includes one or more synchronization signals, and that includes a broadcast channel from which to acquire a first Master Information Block, MIB. The first MIB comprises parameters for acquiring a first type of System Information Block, SIB, which indicates scheduling information for one or more other SIBs. The multiple types of SSBs include at least a second type of SSB that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a second MIB. The second MIB comprises information indicating a beam, carrier, or transmission reception point, TRP, with which the second type of SSB is associated.

[0012] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0013] BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0015] Figure 1 illustrates a communication network according to some embodiments.

[0016] Figure 2 illustrates a third type of SSB used for QCL indication which excludes any broadcast channel from which to acquire a MIB.

[0017] Figure 3 illustrates the signal structure of the first type of SSB according to embodiments.

[0018] Figure 4 illustrates the placement in time of SSB candidates within an SSB period.

[0019] Figure 5 illustrates channels that are QCLed with an SSB.

[0020] Figure 6 illustrates multiple types of SSBs in accordance with embodiments of the present disclosure.

[0021] Figure 7 illustrates two radio network nodes that may be turned on / off in an area covered by a third node transmitting idle mode SSB.

[0022] Figure 8 is a flow chart that illustrates a method performed by the communication device in accordance with particular embodiments.

[0023] Figure 9 is a flow chart that illustrates a method performed by the communication device in accordance with particular embodiments.

[0024] Figure 10 is a flow chart that illustrates a method performed by the communication device in accordance with particular embodiments.

[0025] Figure 11 is a flow chart that illustrates a method performed by the network node in accordance with particular embodiments.

[0026] Figure 12 is a flow chart that illustrates a method performed by the network node in accordance with particular embodiments.

[0027] Figure 13 is a flow chart that illustrates a method performed by the network node in accordance with particular embodiments.

[0028] Figure 14 illustrates a communication device as implemented in accordance with one or more embodiments.

[0029] Figure 15 illustrates a radio network node as implemented in accordance with one or more embodiments. Figure 16 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0030] Figure 17 illustrates a communication system according to embodiments.

[0031] Figure 18 is a block diagram illustrating a UE according to embodiments.

[0032] Figure 19 is a block diagram illustrating a network node according to embodiments.

[0033] DETAILED DESCRIPTION

[0034] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0035] Certain challenges exist with regards to inefficiencies in SSB transmission as described in the background section. Apparatus and methods are disclosed that address the aforementioned and / or other challenges.

[0036] Figure 1 shows a communication network 10 according to some embodiments. The communication network 10 provides communication service to one or more communication devices 12, e.g., user equipment(s) (UEs). The communication network 10 in this regard includes one or more radio network nodes 14 that provide radio access to the communication network 10. The radio network node(s) 14 may for instance provide one or more cells on which to transmit and / or receive, e.g., where a cell may correspond to a carrier frequency.

[0037] The radio network node(s) 14 as shown in this regard are configurable to transmit multiple different types of synchronization signal blocks (SSBs), e.g., that are for and / or associated with the same cell or cell global identity (CGI). In some embodiments, any given radio network node 14 may be configurable to transmit one or more of the multiple different types of SSBs, e.g., some radio network nodes 14 may transmit all of the multiple different types of SSBs whereas other radio network nodes 14 may transmit only one of the multiple different types of SSBs.

[0038] The multiple different types of SSBs as shown in Figure 1 include at least a first type of SSB 16-1 and a second type of SSB 16-2. The first type of SSB 16-1 as shown includes one or more synchronization (sync) signals 18-1 and a broadcast channel 20-1. The synchronization signal(s) 18-1 may include a Primary Synchronization Signal (PSS) and / or a Secondary Synchronization Signal (SSS). On the broadcast channel 20-1 is transmitted a first Master Information Block (MIB) 22-1 , e.g., as defined in 3GPP TS 38.331 v17.6.0 except as otherwise specified herein. The broadcast channel 20-1 is thereby a channel from which to acquire the first MIB 22-1. The first MIB 22-1 as shown comprises parameters 24-1 for acquiring a first type of System Information Block (SIB) 26-1. The parameters 24-1 may for example include a subcarrier spacing for the first type of SIB 26-1 and / or a configuration for a downlink control channel for acquiring the first type of SIB 26-1 (e.g., a common control resource set (CORESET), a common search space, etc.).

[0039] The first type of SIB 26-1 indicates scheduling information (info) 28-1 for one or more other SIBs 30-1. The scheduling information 28-1 may for example indicate a mapping of SIB(s) 30-1 to System Information (SI) messages, a periodicity of SIB(s) 30-1 , an SI window size, etc. In some embodiments, the first type of SIB 26-1 may also indicate a cell global identity (CGI) 32 of a cell with which the first type of SSB 16-1 is associated. The first type of SIB 26-1 in this case may for example indicate a Public Land Mobile Network (PLMN) identity and a cell identity, which may be concatenated together to form the CGI. In some embodiments, the first type of SIB 26-1 may be a SIB Type#1 (SIB1), e.g., as defined in 3GPP TS 38.331 V17.6.0 except as otherwise specified herein.

[0040] In some embodiments, the transmission timing and / or content of the first type of SSB 16-1 is tailored for certain purpose(s), e.g., initial access to the communication network 10 and / or a cell search procedure. In these and other embodiments, the first type of SSB 16-1 may be transmitted on a synchronization (sync) raster 15, e.g., to facilitate communication device(s) 12 finding the first type of SSB 16-1 during initial access and / or cell search. Here, the synchronization raster 15 may define a limited set of possible frequency positions at which the first type of SSB 16-1 is allowed to be transmitted.

[0041] Alternatively or additionally, the transmission timing and / or content of the first type of SSB 16-1 is tailored for use by communication device(s) 12 in a certain radio resource control (RRC) mode, e.g., an RRC idle mode. For example, in some embodiments, the first type of SSB 16-1 is transmitted periodically, e.g., with a period that provides a desired, regular availability of the first type of SSB 16-1. As another example, at least some of the content of the first MIB 22-1 may be specific to an RRC idle mode. In these and other embodiments, the first type of SSB 16-1 may be denoted as an l-SSB, e.g., to indicate that the first type of SSB 16-1 is associated with and / or specific for RRC idle mode.

[0042] Contrasted with the first type of SSB 16-1, the second type of SSB 16-2 also includes one or more synchronization signal(s) 18-2 and a broadcast channel 20-2. However, the broadcast channel 20-2 is a channel from which to acquire a second MIB 22-2.

[0043] In some embodiments, this second MIB 22-2 includes parameters 24-2 for acquiring a second type of SIB 26-2. This second type of SIB 26-2 indicates at least a cell global identity (CGI) 32, e.g., associated with the second type of SSB 16-2, which may for instance be the same CGI 32 as that with which the first type of SSB 16-1 is associated. However, in some embodiments, unlike the first type of SIB 26-1 acquirable from the first type of SSB 16-1, this second type of SIB 26-2 does not indicate scheduling information 28-2 for any other SIB(s) 30-2. In fact, in one embodiment, the second type of SIB 26-2 only indicates the CGI 32. Either way, in some embodiments, the second type of SIB 26-2 may also be denoted as SIB1 , similarly to the first type of SIB 26-1, because the second MIB 22-2 includes parameters 24-2 for acquiring the second type of SIB 26-2. However, because the second type of SIB 26-2 may have different content, timing, and / or purpose, the second type of SIB 26-2 may more particularly be denoted as SIB1

[0044] In these and other embodiments, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for certain purpose(s) different than those for which the first type of SSB 16-1 is tailored. For example, the transmission timing and / or content of the second type of SSB 16-2 may not be tailored for initial access or cell search. In such a case, the second type of SSB 16-2 may be deployable off the synchronization (sync) raster 15. Instead, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for supporting ANR relations in the communication network 10. For example, the second type of SIB 26-2 may be tailored to include the CGI 32 in order to support ANR relations. A communication device 12 may accordingly receive the second type of SSB 16-2, acquire the second MIB 22-2 from the broadcast channel 20-2 included in the second type of SSB 16-2, acquire the second type of SIB 26-2 using the parameters 24-2 comprised in the acquired second MIB 22-2, and report to the communication network 10 the CGI 32 indicated by the second type of SIB 26-2 as part of an ANR procedure. The second type of SSB 16-2 may alternatively or additionally be transmitted less often in time than the first type of SSB 16-2, to reflect the less frequency need of SSB for ANR as compared to initial access. For example, the second type of SSB 16-2 may be transmitted with a longer (i.e. , extended) periodicity than the periodicity with which the first type of SSB 16-1 is transmitted. In these and other embodiments, the second type of SSB 16-2 may be denoted as an E-SSB, e.g., to reflect the extended periodicity with which it is transmitted.

[0045] Alternatively or additionally, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in RRC mode(s) different than that for which the transmission timing and / or content of the first type of SSB 16-1 is tailored. For example, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in RRC connected mode. As such, a communication device 12 may monitor for the first type of SSB 16-1 while in RRC idle mode but monitor for the second type of SSB 16-2 while in RRC connected mode. Or, as another example, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in either RRC connected mode or RRC inactive mode. In this case, a communication device 12 may monitor for the first type of SSB 16-1 while in RRC idle mode but monitor for the second type of SSB 16-2 while in either RRC connected mode or RRC inactive mode.

[0046] In other embodiments shown in Figure 1 , the second MIB 22-2 alternatively or additionally comprises information 34 indicating a beam, carrier, or transmission reception point (TRP) with which the second type of SSB 16-2 is associated. The information indicating the beam, carrier or TRP may in embodiments comprise at least a portion 34 of an identity of the beam, carrier or TRP. As one example, the second MIB 22-2 may include an identity field that explicitly indicates at least a portion 34 of the identity of a beam, carrier, or TRP with which the second type of SSB 16-2 is associated. In another example, the synchronization signal(s) 18-2 may convey one portion of the identity of the beam, carrier, or TRP, and the second MIB 22-2 may include an identity field that explicitly indicates another portion of the identity of the beam, carrier, or TRP. Either way, these embodiments may support associating different transmissions of the second type of SSB 16-2 to different beams or carriers and / or to different TRPs.

[0047] According to these embodiments, then, the content of the second MIB 22-2 may differ from the content of the first MIB 22-1 , e.g., the first MIB 22-1 includes at least one field that is not included in the second MIB 22-2 and / or the second MIB 22-2 includes at least one field that is not included in the first MIB 22-1. For example, the first MIB 22-1 may lack any indication of or any identity of a beam, carrier, or TRP with which the first type of SSB 16-1 is associated (it may even not be associated with any specific beam, carrier, or TRP). This may be the case even though the first and second MIBs 22-1 , 22-2 are associated with the same cell. In fact, in some embodiments, the first and second MIBs 22-1 , 22-2 are considered to be different types of MIBs.

[0048] In these embodiments too, then, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for certain purpose(s) different than those for which the first type of SSB 16-1 is tailored. For example, instead of being tailored for initial access or cell search, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for supporting mobility measurements, e.g., in RRC connected mode. For example, the second type of SSB 16-1 may be tailored to indicate the beam, carrier, or TRP, or at least a portion of the identity of the beam, carrier, or TRP, precisely in order to support mobility measurements. A communication device 12 may accordingly receive the second type of SSB 16-2, acquire the second MIB 22-2 from the broadcast channel 20-2 included in the second type of SSB 16-2, and perform mobility measurement(s) using the second type of SSB 16-2. The communication device 12 may then determine, from the indication or identity portion comprised in the acquired second MIB 22-2, the identity of the beam, carrier, or TRP with which the second type of SSB 16-2 is associated. The communication device 12 can then associate the mobility measurement(s) with the determined identity, and report the mobility measurement(s) associated with the determined identity to the network, or make a mobility decision (e.g., handover decision) based on the mobility measurement(s) being associated with the determined identity. By having information indicating the beam, carrier or TRP in the MIB, there is no uncertainty for the communication device with regards to what the second type of SSB is associated with. This can be an advantage e.g. when a communication device combines more than one SSB measurement, as there is no risk that the communication device combines measurements from different TRPs or beams. In these and other embodiments, the second type of SSB 16-2 may be denoted as an M-SSB, e.g., to reflect the purpose of the second type of SSB 16-2 as being for mobility measurements.

[0049] Furthermore, in these embodiments as well, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in RRC mode(s) different than that for which the transmission timing and / or content of the first type of SSB 16-1 is tailored. For example, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in RRC connected mode, e.g., at least some of the content of the second MIB 22-2 (such as the beam, carrier, or TRP identity) may be specific for RRC connected mode. As such, a communication device 12 may monitor for the first type of SSB 16-1 while in RRC idle mode but monitor for the second type of SSB 16-2 while in RRC connected mode. Or, as another example, the transmission timing and / or content of the second type of SSB 16-2 may be tailored for use by communication device(s) 12 in either RRC connected mode or RRC inactive mode. In this case, a communication device 12 may monitor for the first type of SSB 16-1 while in RRC idle mode but monitor for the second type of SSB 16-2 while in either RRC connected mode or RRC inactive mode.

[0050] Given the different types of SSBs 16-1 , 16-2, some embodiments enable a communication device 12 to differentiate between those different SSB types. Some embodiments for example exploit the synchronization signal(s) 18-1, 18-2 and / or the broadcast channels 20-1 , 20-2 for this purpose.

[0051] For example, in embodiments where the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), the first type of SSB 16-1 includes a PSS in a first set of possible PSSs and the second type of SSB 16-2 includes a PSS in a second set of possible PSSs. The first and second sets of possible PSSs are mutually exclusive in this case. A communication device 12 may therefore monitor for the first type of SSB 16-1 , e.g., while in a RRC idle mode, by attempting to detect a PSS included in the first set of possible PSSs. Similarly, a communication device 12 may monitor for the second type of SSB 16-2, e.g., while in an RRC connected mode, by attempting to detect a PSS included in the second set of possible PSSs.

[0052] In another embodiment, the first type of SSB 16-1 includes a SSS in a first set of possible SSSs and the second type of SSB 16-2 includes a SSS in a second set of possible SSSs. The first and second sets of possible SSSs are mutually exclusive in this case. A communication device 12 may therefore monitor for the first type of SSB 16-1, e.g., while in a RRC idle mode, by attempting to detect a SSS included in the first set of possible SSSs. Similarly, a communication device 12 may monitor for the second type of SSB 16-2, e.g., while in an RRC connected mode, by attempting to detect a SSS included in the second set of possible SSSs.

[0053] A combination of the above PSS and SSS embodiments is possible as well. In this case, the first type of SSB 16-1 includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB 16-2 includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs. Here, the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive.

[0054] In other embodiments that exploit the broadcast channels 20-1 , 20-2 for differentiating the different types of SSBs 16-1, 16-2, the broadcast channel 20-1 included in the first type of SSB 16-1 may be encoded differently than the broadcast channel 20-2 included in the second type of SSB 16-2. For example, one or more transmission parameters may govern transmission of the broadcast channel 20-1 included in the first type of SSB 16-1 and transmission of the broadcast channel 20-2 included in the second type of SSB 16-2. The parameter(s) may include a channelization code parameter, a scrambling sequence parameter, and / or a cyclic redundancy check parameter. Regardless, the one or more transmission parameters may have one or more first values for the broadcast channel 20-1 included in the first type of SSB 16-1 and have one or more second values for the broadcast channel 20-2 included in the second type of SSB 16-2. Here, the one or more first values are different than the one or more second values.

[0055] In still other embodiments, the first MIB 22-1 and the second MIB 22-2 each includes a type field (not shown in Figure 1). The type field in the first MIB 22-1 has a first value indicating that the first MIB 22-1 is associated with the first type of SSB 16-1, and the type field in the second MIB 22-2 has a second value indicating that the second MIB 22-2 is associated with the second type of SSB 16-2. A communication device 12 may therefore monitor for the first type of SSB 16-1 , e.g., while in a RRC idle mode, by attempting to detect the first value of the type field in the MIB. Similarly, a communication device 12 may monitor for the second type of SSB 16-2, e.g., while in an RRC connected mode, by attempting to detect the second value of the type field in the MIB.

[0056] No matter how the different types of SSBs 16-1, 16-2 are distinguished to a communication device 12, in some embodiments the second type of SSB 16-2 is used as a QCL root for one or more other signals or channels. The communication device 12 may do so while in RRC connected mode. In this case, a communication device 12 may use the second type of SSB 16-2 as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-colocated with the received second type of SSB 16-2.

[0057] Other embodiments, by contrast, define yet a third type of SSB 16-3 for this purpose (i.e., the purpose of QCL indication) as shown in Figure 2. As shown, this third type of SSB 16-3 includes one or more synchronization signals 18-3 but excludes any broadcast channel 20-3 from which to acquire a MIB. Any of the above schemes for differentiating between types of SSBs may be extended to differentiate this third type of SSB 16-3 as well. In this case, then, a communication device 12 use the third type of SSB 16-3 as a QCL root by assuming that one or more other received signals or channels are quasi-colocated with the received third type of SSB 16-3.

[0058] Note that, with types of SSBs defined as described herein, the radio network node 14 may advantageously transmit SSB signaling less frequently and / or with less content than known approaches. For example, in some embodiments, the second and / or third type of SSB 16-2, 16- 3 may be transmitted less frequent or, at times, not at all, without jeopardizing initial access, since initial access is supported by the first type of SSB 16-1. As another example embodiment, if the radio network node 14 has not instructed any communication device 12 to read the CGI 34 that may be included in the second type of SSB 16-2 , the radio network node 14 may even decide not to transmit the second type of SIB 26-2 at all.

[0059] Consider now some embodiments herein as applicable in the following context where a communication device 12 is exemplified as a UE, and the communication network 10 is exemplified as a 5G or New Radio (NR) network.

[0060] NR state machine

[0061] Some embodiments herein are applicable to RRC modes or states as defined for New Radio (NR). In NR, a UE can be in different states or modes. Three different states are defined from a radio-network perspective: RRCJDLE (RRC idle mode), RRC_CONNECTED (RRC connected mode), and RRCJNACTIVE (RRC inactive mode).

[0062] In RRCJDLE, there is no RRC context - that is, the parameters necessary for communication between the device and the network - in the radio-access network and the device does not belong to a specific cell. No data transfer may take place as the device sleeps most of the time to reduce battery consumption.

[0063] In RRC_CONNECTED, the RRC context is established and all parameters necessary for communication between the device and the radio-access network are known to both entities. The cell to which the device belongs is known and data transfer to / from the device may take place.

[0064] In RRCJNACTIVE, the RRC context is kept, but the UE is not connected to a specific cell, and data transmission cannot take place (except for the small-data transmission enhancements introduced in a later NR release). It can thus be seen as something between idle and connected modes.

[0065] SSB composition

[0066] In some embodiments, the first type of SSB 16-1 is, or is based on, an NR SSB. In this regard, when an NR UE is switched on or searches for a new cell in handover, the UE tries to detect the first type of SSB 16-1. Figure 3 shows the signal structure of the first type of SSB 16- 1 according to some embodiments. It consists of synchronization signals in the form of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS), as well as a broadcast channel in the form of a Physical Broadcast Channel (PBCH). To reduce the cell search time (the procedure to detect and synchronize to a new cell), the SSB can only be transmitted on certain frequencies, given by the synchronization raster 15. Instead of searching for all possible frequency locations, a UE only needs to try to find an SSB at the frequency locations given by the search raster.

[0067] The UE searches for the PSS (typically with a time-domain filter) and performs rough time- and frequency synchronization based on PSS. Once it finds the PSS, it can process the next three symbols to detect the SSS. Since the UE is already time- and frequency synchronized, this step may happen in the frequency-domain, i.e. , the UE transforms each symbol into the frequency-domain and correlates the received SSS symbols with SSS candidates. The found PSS (in total three PSS sequences exist) together with the found SSS sequence (in total 336 SSS sequences exist) define the physical layer cell ID (in total 3 x 336 = 1008), which may be non-unique globally. After successful detection of PSS and SSS, the UE can demodulate and decode the PBCH, which contains the MIB as well as some physical layer created payload, which together enable the UE to proceed in accessing the cell.

[0068] The NR PSS is based on a cyclic-shifted (in frequency-domain) m-sequence of length 127 subcarriers, and the NR SSS is based on a Gold sequence of length 127 subcarriers. Both synchronization signals are Binary Phase Shift Key (BPSK) modulated.

[0069] Especially during initial access, the UE has no notion about the timing of the cell. The SSB is therefore periodically transmitted so that a UE - irrespective when it is switched on - always finds a first type of SSB 16-1. The first type of SSB 16-1 may be repeated with the SSB periodicity which can vary in NR from 5 to 160 ms and is assumed to be 20 ms for initial access.

[0070] Especially at higher frequencies, the coverage of SSB may be insufficient to cover the complete desired cell area. It is therefore possible to perform multiple transmissions of the first type of SSB 16-1 within an SSB period. For example, perform multiple transmissions of the first type of SSB 16-1 within an SSB period with different beams (i.e., spatial precoders) to cover the desired cell area. Figure 4 shows the placement in time of SSB candidates within an SSB period. This is sometimes called SSB composition. Figure 4 shows the symbols within two slots that can carry SSB candidates, depending on the SSB composition pattern A to E. Since two slots are not sufficient to carry the maximum number of SSB candidates, more than two slots per SSB period can carry SSBs.

[0071] Since coverage is worse at higher frequencies, narrower beams are needed at higher frequencies to achieve the desired coverage. Therefore, SSB compositions may contain more SSB candidates at higher frequencies than at lower frequencies, see Table 2. Depending on the carrier frequency, with numerology = 0 or = 1, up to 4 or 8 SSB candidates are supported per SSB period, respectively.

[0072] Table 2: Number of possible SSB candidates per SSB period

[0073] Initial access

[0074] In some embodiments, during initial access, the UE searches for the first type of SSB 16-1 , e.g., located in the frequency domain on the synchronization raster 15, also referred to as a search raster. Once a PSS and an SSS have been found, the UE reads the PBCH to obtain the MIB. The MIB contains information where in the frequency domain to find the initial CORESET, which is used to transmit Physical Downlink Control Channel (PDCCH) control signaling to the UE. The control is used to inform the UE where to find the remaining system information and how to access the system. Mobility

[0075] Some embodiments exploit the second type of SSB 16-2 for mobility. To handle mobility, a UE connected to the system regularly performs a cell search to find new candidate cells to connect to. This cell search in embodiments herein is based on the second type of SSB 16-2. Once the second type of SSB 16-2 is measured with a “good quality”, the UE reports the physical layer cell ID (derived from the PSS+SSS combination as described previously) along with the received signal quality to the network 10. There are configurable rules for determining what a measurement of “good quality” is, where one example is that the measured signal strength is higher than the signal strength measured in the current cell. The network 10 can then make a decision whether to move the UE to the new cell with the reported physical layer cell ID or not.

[0076] Occasionally, the network may not recognize the physical layer cell ID. In such cases it can request the UE to read the second type of SIB 26-2 and report the cell global ID 32. This helps the network to build a list of neighbor relations, i.e. , which physical cell IDs are used next to each other. QCL root

[0077] Some embodiments herein exploit the second type of SSB 16-2 and / or the third type of SSB 16-3 for QCL. In this regard, signals in NR are associated with an antenna port. An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna portis conveyed. A communication device 12 can assume that two transmitted signals have experienced the same radio channel if and only if they are transmitted from the same antenna port. This is useful to the receiver, for example to perform channel estimation.

[0078] Even if two signals have been transmitted from two different antennas or antenna ports, the channels experienced by the two signals may still have many large-scale properties in common. As an example, the channels experienced by two signals transmitted from two different antenna ports corresponding to different physical antennas at the same site will, even if being different in the details, typically have the same or at least similar large-scale properties, for example, in terms of Doppler spread / shift, average delay spread, and average gain. It can also be expected that the channels will introduce similar average delay. Knowing that the radio channels corresponding to two different antenna ports have similar large-scale properties can be used by the device receiver, for example, in the setting of parameters for channel estimation.

[0079] For this reason, the concept of quasi-colocation (QCL) with respect to antenna ports is part of NR. A device receiver can assume that the radio channels corresponding to two different antenna ports have the same large-scale properties in terms of specific parameters such as average delay spread, Doppler spread / shift, average delay, and spatial Rx parameters if, and only if, the antenna ports are specified as being quasi-collocated.

[0080] There are four different QCL types defined in NR:

[0081] • QCL-TypeA - QCL with respect to Doppler shift, Doppler spread, average delay, and delay spread;

[0082] • QCL-TypeB - QCL with respect to Doppler shift and Doppler spread;

[0083] • QCL-TypeC - QCL with respect to Doppler shift and average delay;

[0084] • QCL-TypeD - QCL with respect to spatial Rx parameters.

[0085] Thus, the QCL relations help the device to prepare for receiving a signal or channel where properties estimated from one signal can be used in the channel estimation for another channel or signal. According to some embodiments, the second type of SSB 16-2 and / or the third type of SSB 16-3 is a QCL root. This means that the UE can assume that many other signals or channels transmitted to the UE are QCL:ed with this SSB, e.g., as illustrated in the example in Figure 5. As seen in the figure, the Doppler shift and the average delay obtained from the SSB (of the second or third type herein) can be used for improving the TRS-based estimate of time and frequency drift and, in the next step, for improving the DM-RS-based channel estimate for the PDCCH and Physical Downlink Shared Channel (PDSCH). Cell-defining and non-cell-defining SSBs

[0086] In some embodiments, the first and / or second types of SSBs 16-1 , 16-2 are each a cell- defining SSB. Such a cell-defining SSB may be associated with a specific cell and / or convey a CGI.

[0087] In some embodiments, one or more other SSBs may be transmitted in the communication network 10 that are non-cell defining (NCD) SSBs. An NCD SSB in this regard is associated with a MIB which indicates that no SIB1 is present (the MIB will, in this case, also contain a pointer to the relevant CD-SSB). Idle mode devices finding an NCD-SSB will simply continue the cell search until an CD-SSB is found, while a device in connected or inactive mode can be told to use an NCD-SSB through RRC signaling. Energy Performance

[0088] Some embodiments herein improve energy performance in the communication network 10. Indeed, one of the most important energy performance enablers is to maximize the idle or sleep time of radio and baseband components, such as digital signal processors and power amplifiers. During times without user data transmission, as few signals as possible should be transmitted. It is also advantageous to concentrate signals in time, i.e. , when one signal is transmitted in a symbol, it is advantageous to transmit other needed signals in the same or adjacent symbols. Some embodiments herein provide SSB transmission based on these energy performance principles.

[0089] Some embodiments for example recognize that, in NR, the legacy SSB is heretofore used for both idle mode and connected mode. Thus, for a TRP (or a node or a beam) to transmit data there has to be a corresponding SSB and that SSB can also be found in idle mode. A legacy NR UE expects to be able to measure on the SSB corresponding to a TRP (or a node or a beam) for some duration prior to receiving data from it. Although it is possible to activate and deactivate SSB transmissions in a legacy NR system it cannot be done on a traffic burst timescale. This is not preferable from an energy efficiency perspective as this means that the TRP cannot be rapidly switched on only for the duration of the data transfer.

[0090] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments, in particular, define separate SSB types 16-1 and 16-2 / 16-3 for idle and connected modes, e.g., with different MIB content. In some embodiments, the PSS, SSS, and / or PBCH is used to indicate the SSB type and / or how the MIB should be interpreted. That is, some embodiments differentiate between these SSB types using one or more of different PSS, SSS, or PBCH structure.

[0091] Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments allow nodes that are deployed for capacity / data rate purposes to be rapidly switched on only for the duration of the transmission without affecting idle mode UEs, thereby enabling significantly improved network energy efficiency.

[0092] More particularly, to simplify UE implementation, it is beneficial if the signals used for idle and connected mode follow a similar structure. This can be achieved by defining multiple types of SSBs, including one or more of those shown in Figure 6.

[0093] One type of SSB is an l-SSB. An l-SSB is one example of the first type of SSB 16-1 in Figure 1. An l-SSB is used in idle mode. It is transmitted on the idle mode search grid (which can be identical to the one used in NR or a sparser one). The MIB provides information to receive system information for a UE in idle mode.

[0094] Another type of SSB is an E-SSB. An E-SSB is one example of the second type of SSB 16-2 in Figure 1. An E-SSB is used in connected mode. It is periodically transmitted with a long periodicity, that is a periodicity that is extended compared to the periodicity for l-SSB for example. The MIB can provide information to receive at least parts of the system information, in particular the global cell ID to assist ANR procedures in the network.

[0095] Yet another type of SSB is an M-SSB. An M-SSB is another example of the second type of SSB 16-2 in Figure 1. The M-SSB is used for mobility in connected mode. It is transmitted periodically, aperiodically, in bursts, or not at all, as dynamically decided by the network. This is the SSB used for mobility measurements in embodiments, unlike prior art where the SSB used in idle mode also forms the basis for mobility measurements. For M-SSB, the MIB does not point to any system information, but preferably contains an identity associated with a specific beam or TRP in the network.

[0096] Yet a further type of SSB is a D-SSB. A D-SSB is an example of the third type of SSB 16-3 in Figure 2. A D-SSB is used as QCL root in connected mode (unless some other signal is used as QCL root, such as E-SSB or M-SSB).

[0097] The exact set of SSBs may differ, but as a minimum the l-SSB used in idle mode in some embodiments is separate from the other SSB(s) not used in idle mode. For example, it is possible to operate without the D-SSB and use the M-SSB as the QCL root instead.

[0098] In some embodiments, both the l-SSB and the E-SSB may point to additional system information, denoted SIB1 and SIBT, respectively, in the figures. The content of SIB1 and SIBT may or may not be identical. The information needed typically differs between a UE in idle mode and a UE in connected mode. For ANR purposes, which is the main reason for the E-SSB, the global cell ID needed and the SIBT should thus at least include this piece of information. However, no additional information is necessary in SIBT, unlike SIB1 in l-SSB where information how to access the system is required.

[0099] Since the same basic structure is used for all these signals or types of SSBs, the UE needs to have a way to differentiate between the different types of SSBs in order to know how to process them. This can be achieved in multiple ways.

[0100] One way is to define different sets of PSS that can be used for the different SSB types respectively. This does not affect the complexity as the UE is searching for one SSB type at a time. For example, a UE in idle mode performing a cell search uses the l-SSB only. Having a different PSS for the l-SSB compared to the other types of SSBs is beneficial as an idle mode UE would - at an early stage - stop the procedure from detecting another type of SSB. In connected mode, the UE can be provided with assistance information, e.g., knowledge that all neighboring TRPs are roughly time synchronized. Indeed, if the UE in connected mode knows at least a rough timing of the cell or TRP from which it is receiving the SSB it can simplify the receiver-side processing by detecting PSS and SSS in the frequency domain, unlike the case with unknown timing where the PSS is processed in the time domain. Processing PSS in the time domain is more costly from a processing perspective than processing it in the frequency domain.

[0101] Another way is to define different sets of SSS that can be used for the different SSB types respectively in a similar way as for the PSS.

[0102] Another alternative is to encode the PBCH containing the M IB differently depending on the SSB type, e.g., using different channel codes, different scrambling sequences, or different cyclic redundancy checks (CRCs). Alternatively, a header in the MIB can include information indicating which SSB type the rest of the MIB belongs to. In all these approaches of encoding the PBCH differently, an idle mode UE would need to process both PSS, SSS, and PBCH before it can conclude whether it was an l-SSB or not, thereby prolonging the cell search time in idle mode compared to using PSS to separate the different SSB types.

[0103] Combinations of the above are also possible, for example using some PSS+SSS combinations for the l-SSB and the rest for the other SSB types.

[0104] In the description above, the focus has been on idle and connected modes, but the same fundamental principle can be used also when the inactive mode is included. Which SSB types that are valid for inactive mode depends on the desired properties of the resulting system. One possibility is to treat the inactive mode in the same way as the connected mode from an SSB type perspective, but other possibilities exist.

[0105] Note that, in some embodiments, a radio network node may transmit only one type of SSB or at least transmit a subset of all types of SSBs. A radio network node may for example transmit M-SSB only. This could be the case for a radio network node deployed for capacity / data rate purposes only, which is thus turned on / off depending on whether a UE is using that node or not. In Figure 7, this would be the nodes 14-2 and 14-3, where 14-3 is turned on and used by the UE 12, and node 14-2 is turned off. There is no need to transmit idle mode signals / SSBs from these nodes as the area is already covered by the node 14-1 which transmits idle mode SSB periodically.

[0106] In another example, a node may transmit both l-SSB and M-SSB. Such a node would be visible to idle mode UEs (using l-SSB) but could also be used for connected mode mobility (using M-SSB).

[0107] In view of the modifications and variations herein, Figure 8 depicts a method performed by a communication device 12 in accordance with particular embodiments. The method includes monitoring for multiple types of synchronization signal blocks, SSBs, 16-1, 16-2 in a communication network 10 (Block 800). In some embodiments, the multiple types of SSBs 16-1, 16-2 include at least a first type of SSB 16-1 that is on a synchronization raster 15, that includes one or more synchronization signals 18-1, and that includes a broadcast channel 20-1 from which to acquire a first Master Information Block, MIB, 22-1 wherein the first MIB 22-1 comprises parameters 24-1 for acquiring a first type of System Information Block, SIB, 26-1 which indicates scheduling information 28-1 for one or more other SIBs 30-1 (Block 805). In some embodiments, the multiple types of SSBs 16-1 , 16-2 include at least a second type of SSB 16-2 that includes one or more synchronization signals 18-2 and that includes a broadcast channel 20-2 from which to acquire a second MIB 22-2 (Block 810). In some embodiments, the second MIB 22-2 comprises parameters 24-2 for acquiring a second type of SIB 26-2 which indicates at least a cell global identity 32 (Block 815). In other embodiments, the second MIB 22-2 alternatively or additionally comprises at least a portion 34 of an identity of a beam, carrier, or transmission reception point, TRP, with which the second type of SSB 16-2 is associated (Block 820).

[0108] In some embodiments, said monitoring comprises monitoring for the first type of SSB 16- 1 while the communication device 12 is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB 16-2 while the communication device 12 is in an RRC connected mode.

[0109] In some embodiments, said monitoring comprises monitoring for the first type of SSB 16- 1 while the communication device 12 is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB 16-2 while the communication device 12 is in either an RRC connected mode or an RRC inactive mode.

[0110] In some embodiments, monitoring for the first type of SSB 16-1 is performed as part of a cell search procedure.

[0111] In some embodiments, said monitoring comprises monitoring for multiple types of SSBs 16-1 , 16-2 that are associated with the same cell.

[0112] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a PSS in a first set of possible PSSs and the second type of SSB 16-2 includes a PSS in a second set of possible PSSs. In some embodiments, the first and second sets of possible PSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a PSS in the first set of possible PSSs, and monitoring for the second type of SSB 16-2 comprises monitoring for an SSB that includes a PSS in the second set of possible PSSs. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in an RRC idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a PSS in the received SSB is included in the first set of possible PSSs, and aborting processing of the received SSB if the received SSB is not of the first type. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a PSS in the received SSB is included in the second set of possible PSSs, and aborting processing of the received SSB if the received SSB is not of the second type. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in a radio resource control idle mode, attempting to detect an SSB of the first type by attempting to detect a PSS included in the first set of possible PSSs. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, attempting to detect an SSB of the second type by attempting to detect a PSS included in the second set of possible PSSs.

[0113] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a SSS in a first set of possible SSSs and the second type of SSB 16-2 includes a SSS in a second set of possible SSSs. In some embodiments, the first and second sets of possible SSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a SSS in the first set of possible SSSs, and monitoring for the second type of SSB 16-2 comprises monitoring for an SSB that includes a SSS in the second set of possible SSSs. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in a radio resource control idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a SSS in the received SSB is included in the first set of possible SSSs, and aborting processing of the received SSB if the received SSB is not of the first type. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a SSS in the received SSB is included in the second set of possible SSSs, and aborting processing of the received SSB if the received SSB is not of the second type.

[0114] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB 16-2 includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs. In some embodiments, the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the first set of possible combinations of PSSs and SSSs, and monitoring for the second type of SSB 16- 2 comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the second set of possible combinations of PSSs and SSSs. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in a radio resource control idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a combination of a PSS and a SSS in the received SSB is included in the first set of possible combinations of PSSs and SSSs, and aborting processing of the received SSB if the received SSB is not of the first type. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a combination of a PSS and a SSS in the received SSB is included in the second set of possible combinations of PSSs and SSSs, and aborting processing of the received SSB if the received SSB is not of the second type.

[0115] In some embodiments, the broadcast channel 20-1 included in the first type of SSB 16-1 is encoded differently than the broadcast channel 20-2 included in the second type of SSB 16-2.

[0116] In some embodiments, one or more transmission parameters govern transmission of the broadcast channel 20-1 included in the first type of SSB 16-1 and transmission of the broadcast channel 20-2 included in the second type of SSB 16-2. In some embodiments, the one or more transmission parameters have one or more first values for the broadcast channel 20-1 included in the first type of SSB 16-1 and have one or more second values for the broadcast channel 20- 2 included in the second type of SSB 16-2. In some embodiments, the one or more first values are different than the one or more second values. In some embodiments, the one or more parameters include at least a channelization code parameter. In other embodiments, the one or more parameters include at least a scrambling sequence parameter. In yet other embodiments, the one or more parameters include at least a cyclic redundancy check parameter. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in a radio resource control idle mode, receiving an SSB and attempting to detect a broadcast channel 20-1 included in the received SSB using the one or more first values for the one or more parameters. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, receiving an SSB, receiving an SSB and attempting to detect a broadcast channel 20-2 included in the received SSB using the one or more second values for the one or more parameters.

[0117] In some embodiments, the first MIB 22-1 and the second MIB 22-2 each includes a type field. In some embodiments, the type field in the first MIB 22-1 has a first value indicating that the first MIB 22-1 is associated with the first type of SSB 16-1 , and the type field in the second MIB 22-2 has a second value indicating that the second MIB 22-2 is associated with the second type of SSB 16-2. In some embodiments, monitoring for the first type of SSB 16-1 comprises, while in a radio resource control idle mode, receiving an SSB that includes an MIB 22-1 with the type field, detecting whether the received SSB is of the first type by detecting whether the type field in the MIB has the first value, and aborting processing of the received SSB if the received SSB is not of the first type. In other alternative or additional embodiments, monitoring for the second type of SSB 16-2 comprises, while in an RRC connected mode, receiving an SSB that includes an MIB 22-2 with the type field, detecting whether the received SSB is of the second type by detecting whether the type field in the MIB has the second value, and aborting processing of the received SSB if the received SSB is not of the second type.

[0118] In some embodiments, the first MIB 22-1 and the second MIB 22-2 are different types of MIBs. In other alternative or additional embodiments, the first MIB 22-1 includes at least one field that is not included in the second MIB 22-2 and / or the second MIB 22-2 includes at least one field that is not included in the first MIB 22-1.

[0119] In some embodiments, the first MIB 22-1 and the second MIB 22-2 are associated with the same cell, and a content of the first MIB 22-1 is different than a content of the second MIB 22-2. In some embodiments, at least some of the content of the first MIB 22-1 is specific to an RRC idle mode and wherein at least some of the content of the second MIB 22-2 is specific to an RRC connected mode.

[0120] In some embodiments, the second MIB 22-2 comprises the parameters 24-2 for acquiring the second type of SIB 26-2.

[0121] In some embodiments, the second type of SIB 26-2 does not indicate scheduling information any other SIB.

[0122] In some embodiments, the second MIB 22-2 comprises the at least a portion 34 of the identity of the beam, carrier, or TRP with which the second type of SSB 16-2 is associated.

[0123] In some embodiments, the second type of SSB 16-2 has a longer transmission periodicity than the first type of SSB 16-1.

[0124] In some embodiments, the method further comprises, from said monitoring, receiving the second type of SSB 16-2 (Block 825). In some embodiments, the method further comprises acquiring the second MIB 22-2 from the broadcast channel 20-2 included in the received second type of SSB 16-2 (Block 825). In some embodiments, the second MIB 22-2 comprises the parameters 24-2 for acquiring the second type of SIB 26-2, and the method further comprises acquiring the second type of SIB 26-2 using the parameters 24-2 comprised in the acquired second MIB 22-2 (Block 830). In some embodiments, the method further comprises reporting the cell global identity 32 indicated by the acquired second type of SIB 26-2 as part of an automatic neighbor relation, ANR, procedure (Block 830). In some embodiments, the second MIB 22-2 comprises the at least a portion 34 of the identity of the beam, carrier, or TRP with which the second type of SSB 16-2 is associated (Block 835). In some embodiments, the method further comprises performing one or more mobility measurements using the received second type of SSB 16-2 (Block 835). In some embodiments, the method further comprises determining, from the at least a portion 34 of the identity comprised in the acquired second MIB 22-, the identity of the beam, carrier, or TRP with which the second type of SSB 16-2 is associated (Block 835). In some embodiments, the method further comprises associating the one or more mobility measurements with the determined identity (Block 835). In some embodiments, the method further comprises making a mobility decision based on the one or more mobility measurements being associated with the determined identity (Block 835). In some embodiments, the second type of SSB 16-2 is received during an RRC connected mode.

[0125] In some embodiments, the second type of SSB 16-2 is deployable off the synchronization raster 15.

[0126] In some embodiments, the first type of SSB 16-1 is an l-SSB and the second type of SSB 16-2 is an E-SSB or an M-SSB.

[0127] In some embodiments, the multiple types of SSBs 16-1 , 16-2 further include a third type of SSB 16-3, wherein the third type of SSB 16-3 includes one or more synchronization signals but excludes any broadcast channel 20-1, 20-2 from which to acquire an MIB 22-1 , 22-2 (Block 840). In some embodiments, said monitoring comprises monitoring for the first type of SSB 16-1 while the communication device 12 is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB 16-2 and the third type of SSB 16-3 while the communication device 12 is in an RRC connected mode. In some embodiments, said monitoring comprises monitoring for the first type of SSB 16-1 while the communication device 12 is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB 16-2 and the third type of SSB 16-3 while the communication device 12 is in either an RRC connected mode or an RRC inactive mode. In some embodiments, the first type of SSB 16-1, the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a PSS in a first set of possible PSSs, the second type of SSB 16-2 includes a PSS in a second set of possible PSSs, and the third type of SSB 16-3 includes a PSS in a third set of possible PSSs. In some embodiments, the first, second, and third sets of possible PSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a PSS in the first set of possible PSSs. In some embodiments, monitoring for the second type of SSB 16- 2 comprises monitoring for an SSB that includes a PSS in the second set of possible PSSs, and monitoring for the third type of SSB 16-3 comprises monitoring for an SSB that includes a PSS in the third set of possible PSSs. In some embodiments, the first type of SSB 16-1 , the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a SSS in a first set of possible SSSs, the second type of SSB 16-2 includes a SSS in a second set of possible SSSs, and the third type of SSB 16-3 includes a SSS in a third set of possible SSSs. In some embodiments, the first, second and third sets of possible SSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a SSS in the first set of possible SSSs. In some embodiments, monitoring for the second type of SSB 16-2 comprises monitoring for an SSB that includes a SSS in the second set of possible SSSs, and monitoring for the third type of SSB 16-3 comprises monitoring for an SSB that includes a SSS in the third set of possible SSSs. In some embodiments, the first type of SSB 16-1, the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, the second type of SSB 16-2 includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs and the third type of SSB 16-3 includes a combination of a PSS and a SSS in a third set of possible combinations of PSSs and SSSs. In some embodiments, the first, second, and third sets of possible combinations of PSSs and SSSs are mutually exclusive. In some embodiments, monitoring for the first type of SSB 16-1 comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the first set of possible combinations of PSSs and SSSs. In some embodiments, monitoring for the second type of SSB 16-2 comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the second set of possible combinations of PSSs and SSSs, and monitoring for the third type of SSB 16-3 comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the third set of possible combinations of PSSs and SSSs. In some embodiments, the method further comprises, from said monitoring, receiving the third type of SSB 16-3 (Block 845). In some embodiments, the method further comprises using the received third type of SSB 16-3 as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-colocated with the received third type of SSB 16-3 (Block 845). In some embodiments, the third type of SSB 16-3 is received during an RRC connected mode. In some embodiments, the third type of SSB 16-3 is deployable off the synchronization raster 15. In some embodiments, the first type of SSB 16-1 is an l-SSB, the second type of SSB 16-2 is an E-SSB or an M-SSB, and the third type of SSB 16-3 is a D-SSB.

[0128] In some embodiments, the method further comprises, from said monitoring, receiving the second type of SSB 16-2. In some embodiments, the method further comprises using the received second type of SSB 16-2 as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-collocated with the received second type of SSB 16-2.

[0129] Figure 9 depicts a method performed by a communication device 12 in accordance with other particular embodiments. The method includes monitoring for a first type of synchronization signal block, SSB, while the communication device 12 is in a first radio resource control, RRC, mode (Block 900). The method also comprises monitoring for a second type of SSB 16-2 while the communication device 12 is in a second RRC mode (Block 910).

[0130] In some embodiments, the first RRC mode is RRC idle mode and the second RRC mode is RRC connected mode.

[0131] In some embodiments, the first RRC mode is RRC idle mode and the second RRC mode is RRC inactive mode.

[0132] In some embodiments, the first and second types of SSBs 16-1, 16-2 are the first and second types of SSBs 16-1 , 16-2 according to any of the embodiments above described with respect to Figure 8.

[0133] In some embodiments, the method further comprises any of the steps described with respect to Figure 8.

[0134] Figure 10 depicts a method performed by a communication device 12 in accordance with other particular embodiments. The method includes receiving a synchronization signal block, SSB, that includes one or more synchronization signals 18-1 , 18-2 and that includes a broadcast channel 20-1 , 20-2 from which to acquire a Master Information Block, MIB 22-1 , 22-2 (Block 1000). In some embodiments, the MIB 22-1 , 22-2 comprises parameters 24-1, 24-2 for acquiring an SIB 26-1, 26-2 that indicates a cell global identity 32 but that does not indicate scheduling information for acquiring any other SIB (Block 1010). In other alternative or additional embodiments, the MIB 22-1 , 22-2 lacks parameters for acquiring any SIB and includes at least a portion 34 of an identity of a beam, carrier, or transmission reception point, TRP, with which the SSB is associated (Block 1020).

[0135] In some embodiments, the SSB is the second type of SSB 16-2 according to any of the embodiments above. In some embodiments, the method further comprises any of the steps described with respect to Figure 8

[0136] Figure 11 depicts a method performed by a radio network node configured for use in a communication network 10. The method includes transmitting multiple types of synchronization signal blocks, SSBs 16-1 , 16-2 (Block 1110). In some embodiments, the multiple types of SSBs 16-1 , 16-2 include at least a first type of SSB 16-1 that is on a synchronization raster 15, that includes one or more synchronization signals 18-1, 18-2, and that includes a broadcast channel 20-1 , 20-2 from which to acquire a first Master Information Block, MIB, 22-1 wherein the first MIB 22-1 comprises parameters 24-1 for acquiring a first type of System Information Block, SIB, 26-1 which indicates scheduling information 28-1 for one or more other SIBs 30-1 (Block 1120). In some embodiments, the multiple types of SSBs 16-1, 16-2 include at least a second type of SSB 16-2 that includes one or more synchronization signals 18-2 and that includes a broadcast channel 20-2 from which to acquire a second MIB 22-2 (Block 1130). In some embodiments, the second MIB 22-2 comprises parameters 24-2 for acquiring a second type of SIB 26-2 which indicates at least a cell global identity 32 (Block 1140). In other embodiments, the second MIB 22-2 alternatively or additionally comprises information indicating a beam, carrier, or TRP with which the second type of SSB 16-2 is associated (Block 1150). In embodiments, the information indicating the beam, carrier, or TRP comprises at least a portion 34 of an identity of the beam, carrier, or transmission reception point, TRP, 11

[0137] In some embodiments, the first type of SSB 16-1 is specific for and / or targets communication devices 12 in a radio resource control, RRC, idle mode, and the second type of SSB 16-2 is specific for and / or targets communication devices 12 in an RRC connected mode.

[0138] In some embodiments, the first type of SSB 16-1 is specific for and / or targets communication devices 12 in a radio resource control, RRC, idle mode, and the second type of SSB 16-2 is specific for and / or targets communication devices 12 in either an RRC inactive mode or an RRC connected mode.

[0139] In some embodiments, said transmitting comprises transmitting multiple types of SSBs 16-1 , 16-2 that are associated with the same cell.

[0140] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a PSS in a first set of possible PSSs and the second type of SSB 16-2 includes a PSS in a second set of possible PSSs. In some embodiments, the first and second sets of possible PSSs are mutually exclusive.

[0141] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a SSS in a first set of possible SSSs and the second type of SSB 16-2 includes a SSS in a second set of possible SSSs. In some embodiments, the first and second sets of possible SSSs are mutually exclusive.

[0142] In some embodiments, the first type of SSB 16-1 and the second type of SSB 16-2 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB 16-2 includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs. In some embodiments, the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive.

[0143] In some embodiments, the method further comprises encoding the broadcast channel 20-1 included in the first type of SSB 16-1 differently than the broadcast channel 20-2 included in the second type of SSB 16-2 (Block 1100).

[0144] In some embodiments, said transmitting comprises transmitting the broadcast channel 20-1 included in the first type of SSB 16-1 using one or more first values for one or more transmission parameters, and transmitting the broadcast channel 20-2 included in the second type of SSB 16-2 using one or more second values for the one or more transmission parameters, wherein the one or more first values are different than the one or more second values. In some embodiments, the one or more parameters include at least a channelization code parameter. In other embodiments, the one or more parameters include at least a scrambling sequence parameter. In yet other embodiments, the one or more parameters include at least a cyclic redundancy check parameter.

[0145] In some embodiments, the first MIB 22-1 and the second MIB 22-2 each includes a type field. In some embodiments, the type field in the first MIB 22-1 has a first value indicating that the first MIB 22-1 is associated with the first type of SSB 16-1 , and the type field in the second MIB 22-2 has a second value indicating that the second MIB 22-2 is associated with the second type of SSB 16-2.

[0146] In some embodiments, the first MIB 22-1 and the second MIB 22-2 are different types of MIBs. In other alternative or additional embodiments, the first MIB 22-1 includes at least one field that is not included in the second MIB 22-2 and / or the second MIB 22-2 includes at least one field that is not included in the first MIB 22-1.

[0147] In some embodiments, the first MIB 22-1 and the second MIB 22-2 are associated with the same cell, and a content of the first MIB 22-1 is different than a content of the second MIB 22-2. In some embodiments, at least some of the content of the first MIB 22-1 is specific to an RRC idle mode and wherein at least some of the content of the second MIB 22-2 is specific to an RRC connected mode.

[0148] In some embodiments, the second MIB 22-2 comprises the parameters 24-2 for acquiring the second type of SIB 26-2.

[0149] In some embodiments, the second type of SIB 26-2 does not indicate scheduling information for any other SIB.

[0150] In some embodiments, the second MIB 22-2 comprises the at least a portion 34 of the identity of the beam, carrier, or TRP with which the second type of SSB 16-2 is associated.

[0151] In some embodiments, said transmitting comprises transmitting the first type of SSB 16- 1 with a first periodicity in time and transmitting the second type of SSB 16-2 with a second periodicity in time. In some embodiments, the second periodicity is longer than the first periodicity.

[0152] In some embodiments, said transmitting comprises periodically transmitting the first type of SSB 16-1 and aperiodically transmitting the second type of SSB 16-2.

[0153] In some embodiments, said transmitting comprises periodically transmitting the first type of SSB 16-1 and selectively transmitting the second type of SSB 16-2 on demand as needed.

[0154] In some embodiments, the first and second types of SSBs 16-1, 16-2 are each associated with a certain cell. In some embodiments, said transmitting comprises periodically transmitting the first type of SSB 16-1 irrespective of whether any communication device 12 is in RRC connected mode with respect to the certain cell and selectively transmitting the second type of SSB 16-2 only when at least one communication device 12 is in RRC connected mode with respect to the certain cell.

[0155] In some embodiments, said transmitting comprises periodically transmitting the first type of SSB 16-1 irrespective of whether any communication device 12 has an ongoing data transmission and selectively transmitting the second type of SSB 16-2 only while at least one communication device 12 has an ongoing data transmission.

[0156] In some embodiments, the method comprises transmitting the second type of SSB 16-2 off the synchronization raster 15.

[0157] In some embodiments, the first type of SSB 16-1 is an l-SSB and the second type of SSB 16-2 is an E-SSB or an M-SSB.

[0158] In some embodiments, the multiple types of SSBs 16-1 , 16-2 further include a third type of SSB 16-3. In some embodiments, the third type of SSB 16-3 includes one or more synchronization signals but excludes any broadcast channel 20-1 , 20-2 from which to acquire an MIB 22-1 , 22-2. In some embodiments, the first type of SSB 16-1 is specific for and / or targets communication devices 12 in a radio resource control, RRC, idle mode, and each of the second and third types of SSBs 16-1 , 16-3 is specific for and / or targets communication devices 12 in an RRC connected mode. In some embodiments, the first type of SSB 16-1 is specific for and / or targets communication devices 12 in a radio resource control, RRC, idle mode, and each of the second and third types of SSBs 16-1, 16-3 is specific for and / or targets communication devices 12 in either an RRC inactive mode or an RRC connected mode.

[0159] In some embodiments, the first type of SSB 16-1, the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a PSS in a first set of possible PSSs, the second type of SSB 16-2 includes a PSS in a second set of possible PSSs, and the third type of SSB 16-3 includes a PSS in a third set of possible PSSs. In some embodiments, the first, second, and third sets of possible PSSs are mutually exclusive. In some embodiments, the first type of SSB 16-1, the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a SSS in a first set of possible SSSs, the second type of SSB 16-2 includes a SSS in a second set of possible SSSs, and the third type of SSB 16-3 includes a SSS in a third set of possible SSSs. In some embodiments, the first, second and third sets of possible SSSs are mutually exclusive. In some embodiments, the first type of SSB 16-1, the second type of SSB 16-2, and the third type of SSB 16-3 each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS. In some embodiments, the first type of SSB 16-1 includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, the second type of SSB 16-2 includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs and the third type of SSB 16-3 includes a combination of a PSS and a SSS in a third set of possible combinations of PSSs and SSSs. In some embodiments, the first, second, and third sets of possible combinations of PSSs and SSSs are mutually exclusive. In some embodiments, the third type of SSB 16-3 is a quasicolocation, QCL, root for one or more other signals or channels. In some embodiments, the method comprises transmitting the third type of SSB 16-3 off the synchronization raster 15. In some embodiments, the first type of SSB 16-1 is an l-SSB, the second type of SSB 16-2 is an E-SSB or an M-SSB, and the third type of SSB 16-3 is a D-SSB.

[0160] In some embodiments, the second type of SSB 16-2 is a quasi-colocation, QCL, root for one or more other signals or channels.

[0161] Figure 12 depicts a method performed by a radio network node configured for use in a communication network 10 in accordance with other particular embodiments. The method includes transmitting a first type of synchronization signal block, SSB, for communication devices 12 in a first radio resource control, RRC, mode (Block 1200). The method also comprises transmitting a second type of SSB 16-2 for communication devices 12 in a second RRC mode (Block 1210).

[0162] In some embodiments, the first RRC mode is RRC idle mode and the second RRC mode is RRC connected mode.

[0163] In some embodiments, the first RRC mode is RRC idle mode and the second RRC mode is RRC inactive mode.

[0164] In some embodiments, the first and second types of SSBs 16-1, 16-2 are the first and second types of SSBs 16-1 , 16-2 according to any of the embodiments above described with respect to Figure 11. In some embodiments, the method further comprises any of the steps of any of the embodiments above described with respect to Figure 11.

[0165] Figure 13 depicts a method performed by a radio network node configured for use in a communication network 10 in accordance with other particular embodiments. The method includes transmitting a synchronization signal block, SSB, that includes one or more synchronization signals 18-1, 18-2 and that includes a broadcast channel 20-1 , 20-2 from which to acquire a Master Information Block, MIB 22-1 , 22-2 (Block 1300). In some embodiments, the MIB 22-1, 22-2 comprises parameters 24-1, 24-2 for acquiring an SIB 26-1, 26-2 that indicates a cell global identity 32 but that does not indicate scheduling information for acquiring any other SIB (Block 1310). In other alternative or additional embodiments, the MIB 22-1, 22-2 lacks parameters for acquiring any SIB and includes at least a portion 34 of an identity of a beam, carrier, or transmission reception point, TRP, with which the SSB is associated (Block 1320).

[0166] In some embodiments, the SSB is the second type of SSB 16-2 according to any of the embodiments above. In some embodiments, the method further comprises any of the steps of any of the embodiments above described with respect to Figure 11. Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0167] Embodiments also include a communication device 12 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. The power supply circuitry is configured to supply power to the communication device 12.

[0168] Embodiments further include a communication device 12 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the communication device 12 further comprises communication circuitry.

[0169] Embodiments further include a communication device 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 12 is configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0170] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[0171] Embodiments herein also include a radio network node 14 configured to perform any of the steps of any of the embodiments described above for the radio network node 14.

[0172] Embodiments also include a radio network node 14 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node 14. The power supply circuitry is configured to supply power to the radio network node 14.

[0173] Embodiments further include a radio network node 14 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node 14. In some embodiments, the radio network node 14 further comprises communication circuitry. Embodiments further include a radio network node 14 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the radio network node 14 is configured to perform any of the steps of any of the embodiments described above for the radio network node 14.

[0174] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0175] Figure 14 for example illustrates a communication device 12 as implemented in accordance with one or more embodiments. As shown, the communication device 12 includes processing circuitry 1410 and communication circuitry 1420. The communication circuitry 1420 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication device 12. The processing circuitry 1410 is configured to perform processing described above, e.g., in Figure 8, 9, and / or 10, such as by executing instructions stored in memory 1430. The processing circuitry 1410 in this regard may implement certain functional means, units, or modules.

[0176] Figure 15 illustrates a radio network node 14 as implemented in accordance with one or more embodiments. As shown, the radio network node 14 includes processing circuitry 1510 and communication circuitry 1520. The communication circuitry 1520 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1510 is configured to perform processing described above, e.g., in Figure 11, 12, and / or 13, such as by executing instructions stored in memory 1530. The processing circuitry 1510 in this regard may implement certain functional means, units, or modules. Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0177] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0178] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0179] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0180] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0181] Figure 17 shows an example of a communication system 1700 in accordance with some embodiments.

[0182] In the example, the communication system 1700 includes a telecommunication network 1702 that includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more core network nodes 1708. The access network 1704 includes one or more access network nodes, such as network nodes 1710a and 1710b (one or more of which may be generally referred to as network nodes 1710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1702, including one or more network nodes 1710 and / or core network nodes 1708.

[0183] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1712a, 1712b, 1712c, and 1712d (one or more of which may be generally referred to as UEs 1712) to the core network 1706 over one or more wireless connections.

[0184] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0185] The UEs 1712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1710 and other communication devices. Similarly, the network nodes 1710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1712 and / or with other network nodes or equipment in the telecommunication network 1702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1702.

[0186] In the depicted example, the core network 1706 connects the network nodes 1710 to one or more hosts, such as host 1716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1706 includes one more core network nodes (e.g., core network node 1708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1708. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0187] The host 1716 may be under the ownership or control of a service provider other than an operator or provider of the access network 1704 and / or the telecommunication network 1702, and may be operated by the service provider or on behalf of the service provider. The host 1716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0188] As a whole, the communication system 1700 of Figure 17 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0189] In some examples, the telecommunication network 1702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1702. For example, the telecommunications network 1702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0190] In some examples, the UEs 1712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0191] In the example, the hub 1714 communicates with the access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712c and / or 1712d) and network nodes (e.g., network node 1710b). In some examples, the hub 1714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1714 may be a broadband router enabling access to the core network 1706 for the UEs. As another example, the hub 1714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1710, or by executable code, script, process, or other instructions in the hub 1714. As another example, the hub 1714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0192] The hub 1714 may have a constant / persistent or intermittent connection to the network node 1710b. The hub 1714 may also allow for a different communication scheme and / or schedule between the hub 1714 and UEs (e.g., UE 1712c and / or 1712d), and between the hub 1714 and the core network 1706. In other examples, the hub 1714 is connected to the core network 1706 and / or one or more UEs via a wired connection. Moreover, the hub 1714 may be configured to connect to an M2M service provider over the access network 1704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1710 while still connected via the hub 1714 via a wired or wireless connection. In some embodiments, the hub 1714 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1710b. In other embodiments, the hub 1714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1710b, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Figure 18 shows a UE 1800 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integ rated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0193] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0194] The UE 1800 includes processing circuitry 1802 that is operatively coupled via a bus 1804 to an input / output interface 1806, a power source 1808, a memory 1810, a communication interface 1812, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 18. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0195] The processing circuitry 1802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1810. The processing circuitry 1802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1802 may include multiple central processing units (CPUs). In the example, the input / output interface 1806 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1800. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0196] In some embodiments, the power source 1808 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1808 may further include power circuitry for delivering power from the power source 1808 itself, and / or an external power source, to the various parts of the UE 1800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1808. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1808 to make the power suitable for the respective components of the UE 1800 to which power is supplied.

[0197] The memory 1810 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1810 includes one or more application programs 1814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1816. The memory 1810 may store, for use by the UE 1800, any of a variety of various operating systems or combinations of operating systems.

[0198] The memory 1810 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1810 may allow the UE 1800 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1810, which may be or comprise a device-readable storage medium.

[0199] The processing circuitry 1802 may be configured to communicate with an access network or other network using the communication interface 1812. The communication interface 1812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1822. The communication interface 1812 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1818 and / or a receiver 1820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1818 and receiver 1820 may be coupled to one or more antennas (e.g., antenna 1822) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0200] In the illustrated embodiment, communication functions of the communication interface 1812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0201] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1812, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0202] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0203] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1800 shown in Figure 18.

[0204] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0205] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0206] Figure 19 shows a network node 1900 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0207] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0208] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0209] The network node 1900 includes a processing circuitry 1902, a memory 1904, a communication interface 1906, and a power source 1908. The network node 1900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1900 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1904 for different RATs) and some components may be reused (e.g., a same antenna 1910 may be shared by different RATs). The network node 1900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1900.

[0210] The processing circuitry 1902 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1900 components, such as the memory 1904, to provide network node 1900 functionality.

[0211] In some embodiments, the processing circuitry 1902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1902 includes one or more of radio frequency (RF) transceiver circuitry 1912 and baseband processing circuitry 1914. In some embodiments, the radio frequency (RF) transceiver circuitry 1912 and the baseband processing circuitry 1914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1912 and baseband processing circuitry 1914 may be on the same chip or set of chips, boards, or units.

[0212] The memory 1904 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1902. The memory 1904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1902 and utilized by the network node 1900. The memory 1904 may be used to store any calculations made by the processing circuitry 1902 and / or any data received via the communication interface 1906. In some embodiments, the processing circuitry 1902 and memory 1904 is integrated.

[0213] The communication interface 1906 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1906 comprises port(s) / terminal(s) 1916 to send and receive data, for example to and from a network over a wired connection. The communication interface 1906 also includes radio front-end circuitry 1918 that may be coupled to, or in certain embodiments a part of, the antenna 1910. Radio front-end circuitry 1918 comprises filters 1920 and amplifiers 1922. The radio front-end circuitry 1918 may be connected to an antenna 1910 and processing circuitry 1902. The radio front-end circuitry may be configured to condition signals communicated between antenna 1910 and processing circuitry 1902. The radio front-end circuitry 1918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1920 and / or amplifiers 1922. The radio signal may then be transmitted via the antenna 1910. Similarly, when receiving data, the antenna 1910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1918. The digital data may be passed to the processing circuitry 1902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0214] In certain alternative embodiments, the network node 1900 does not include separate radio front-end circuitry 1918, instead, the processing circuitry 1902 includes radio front-end circuitry and is connected to the antenna 1910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1912 is part of the communication interface 1906. In still other embodiments, the communication interface 1906 includes one or more ports or terminals 1916, the radio front-end circuitry 1918, and the RF transceiver circuitry 1912, as part of a radio unit (not shown), and the communication interface 1906 communicates with the baseband processing circuitry 1914, which is part of a digital unit (not shown).

[0215] The antenna 1910 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1910 may be coupled to the radio front-end circuitry 1918 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1910 is separate from the network node 1900 and connectable to the network node 1900 through an interface or port.

[0216] The antenna 1910, communication interface 1906, and / or the processing circuitry 1902 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1910, the communication interface 1906, and / or the processing circuitry 1902 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0217] The power source 1908 provides power to the various components of network node 1900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1900 with power for performing the functionality described herein. For example, the network node 1900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1908. As a further example, the power source 1908 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0218] Embodiments of the network node 1900 may include additional components beyond those shown in Figure 19 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1900 may include user interface equipment to allow input of information into the network node 1900 and to allow output of information from the network node 1900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1900.

[0219] Figure 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0220] Applications 1602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0221] Hardware 1604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs 1608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.

[0222] The VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0223] In the context of NFV, a VM 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1608, and that part of hardware 1604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1608 on top of the hardware 1604 and corresponds to the application 1602.

[0224] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.

[0225] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0226] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0227] List of embodiments:

[0228] Group A Embodiments

[0229] A1. A method performed by a communication device (12), the method comprising: monitoring for multiple types of synchronization signal blocks, SSBs (16-1 , 16-2), in a communication network (10), wherein the multiple types of SSBs (16-1, 16-2) include at least: a first type of SSB (16-1) that is on a synchronization raster (15), that includes one or more synchronization signals (18-1), and that includes a broadcast channel (20-1) from which to acquire a first Master Information Block, MIB (22-1), wherein the first MIB (22-1) comprises parameters for acquiring a first type of System Information Block, SIB, (26-1) which indicates scheduling information (28-1) for one or more other SIBs (30-1); and a second type of SSB (16-2) that includes one or more synchronization signals (18-2) and that includes a broadcast channel (20-2) from which to acquire a second MIB (22-2), wherein the second MIB (22-2) comprises: parameters (24-2) for acquiring a second type of SIB (26-2) which indicates at least a cell global identity (32); and / or at least a portion (34) of an identity of a beam, carrier, or transmission reception point, TRP, with which the second type of SSB (16-2) is associated.

[0230] A2. The method of embodiment A1 , wherein said monitoring comprises monitoring for the first type of SSB while the communication device is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB while the communication device is in an RRC connected mode.

[0231] A3. The method of embodiment A1 , wherein said monitoring comprises monitoring for the first type of SSB while the communication device is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB while the communication device is in either an RRC connected mode or an RRC inactive mode.

[0232] A4. The method of any of embodiments A1-A3, wherein monitoring for the first type of SSB is performed as part of a cell search procedure.

[0233] A5. The method of any of embodiments A1-A4, wherein said monitoring comprises monitoring for multiple types of SSBs that are associated with the same cell.

[0234] A6. The method of any of embodiments A1-A5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs and the second type of SSB includes a PSS in a second set of possible PSSs, wherein the first and second sets of possible PSSs are mutually exclusive.

[0235] A7. The method of embodiment A6, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a PSS in the first set of possible PSSs, and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a PSS in the second set of possible PSSs. A8-1. The method of embodiment A7, wherein: monitoring for the first type of SSB comprises, while in an RRC idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a PSS in the received SSB is included in the first set of possible PSSs, and aborting processing of the received SSB if the received SSB is not of the first type; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a PSS in the received SSB is included in the second set of possible PSSs, and aborting processing of the received SSB if the received SSB is not of the second type.

[0236] A8-2. The method of embodiment A7, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, attempting to detect an SSB of the first type by attempting to detect a PSS included in the first set of possible PSSs; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, attempting to detect an SSB of the second type by attempting to detect a PSS included in the second set of possible PSSs.

[0237] A9. The method of any of embodiments A1-A5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs and the second type of SSB includes a SSS in a second set of possible SSSs, wherein the first and second sets of possible SSSs are mutually exclusive.

[0238] A10. The method of embodiment A9, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a SSS in the first set of possible SSSs, and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a SSS in the second set of possible SSSs.

[0239] A11-1. The method of embodiment A10, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a SSS in the received SSB is included in the first set of possible SSSs, and aborting processing of the received SSB if the received SSB is not of the first type; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a SSS in the received SSB is included in the second set of possible SSSs, and aborting processing of the received SSB if the received SSB is not of the second type.

[0240] A11-2. The method of embodiment A10, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, attempting to detect an SSB of the first type by attempting to detect a SSS included in the first set of possible SSSs; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, attempting to detect an SSB of the second type by attempting to detect a SSS included in the second set of possible SSSs.

[0241] A12. The method of any of embodiments A1-A5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs, wherein the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive.

[0242] A13. The method of embodiment A12, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the first set of possible combinations of PSSs and SSSs, and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the second set of possible combinations of PSSs and SSSs.

[0243] A14-1. The method of embodiment A13, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, receiving an SSB, detecting whether the received SSB is of the first type by detecting whether a combination of a PSS and a SSS in the received SSB is included in the first set of possible combinations of PSSs and SSSs, and aborting processing of the received SSB if the received SSB is not of the first type; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, receiving an SSB, detecting whether the received SSB is of the second type by detecting whether a combination of a PSS and a SSS in the received SSB is included in the second set of possible combinations of PSSs and SSSs, and aborting processing of the received SSB if the received SSB is not of the second type.

[0244] A14-2. The method of embodiment A13, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, attempting to detect an SSB of the first type by attempting to detect a combination of a PSS and SS included in the first set of possible combinations of PSSs and SSSs; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, attempting to detect an SSB of the second type by attempting to detect a combination of a PSS and SSS included in the second set of possible combinations of PSSs and SSSs.

[0245] A15. The method of any of embodiments A1-A5, wherein the broadcast channel included in the first type of SSB is encoded differently than the broadcast channel included in the second type of SSB.

[0246] A16. The method of any of embodiments A1-A5, wherein one or more transmission parameters govern transmission of the broadcast channel included in the first type of SSB and transmission of the broadcast channel included in the second type of SSB, wherein the one or more transmission parameters have one or more first values for the broadcast channel included in the first type of SSB and have one or more second values for the broadcast channel included in the second type of SSB, wherein the one or more first values are different than the one or more second values.

[0247] A17. The method of embodiment A16, wherein the one or more parameters include one or more of: a channelization code parameter; a scrambling sequence parameter; or a cyclic redundancy check parameter.

[0248] A18. The method of any of embodiments A16-A17, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, receiving an SSB and attempting to detect a broadcast channel included in the received SSB using the one or more first values for the one or more parameters; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, receiving an SSB, receiving an SSB and attempting to detect a broadcast channel included in the received SSB using the one or more second values for the one or more parameters.

[0249] A19. The method of any of embodiments A1-A5, wherein the first MIB and the second MIB each includes a type field, wherein the type field in the first MIB has a first value indicating that the first MIB is associated with the first type of SSB, and wherein the type field in the second MIB has a second value indicating that the second MIB is associated with the second type of SSB.

[0250] A20. The method of embodiment A19, wherein: monitoring for the first type of SSB comprises, while in a radio resource control idle mode, receiving an SSB that includes an MIB with the type field, detecting whether the received SSB is of the first type by detecting whether the type field in the MIB has the first value, and aborting processing of the received SSB if the received SSB is not of the first type; and / or monitoring for the second type of SSB comprises, while in an RRC connected mode, receiving an SSB that includes an MIB with the type field, detecting whether the received SSB is of the second type by detecting whether the type field in the MIB has the second value, and aborting processing of the received SSB if the received SSB is not of the second type.

[0251] A21. The method of any of embodiments A1-A20, wherein: the first MIB and the second MIB are different types of MIBs; and / or the first MIB includes at least one field that is not included in the second MIB and / or the second MIB includes at least one field that is not included in the first MIB.

[0252] A22. The method of any of embodiments A1-A21 , wherein the first MIB and the second MIB are associated with the same cell, and wherein a content of the first MIB is different than a content of the second MIB.

[0253] A23. The method of embodiment A22, wherein at least some of the content of the first MIB is specific to an RRC idle mode and wherein at least some of the content of the second MIB is specific to an RRC connected mode.

[0254] A24. The method of any of embodiments A1-A23, wherein the second MIB comprises the parameters for acquiring the second type of SIB.

[0255] A25. The method of any of embodiments A1-A24, wherein the second type of SIB does not indicate scheduling information for any other SIB.

[0256] A26. The method of any of embodiments A1-A25, wherein the second MIB comprises the at least a portion of the identity of the beam, carrier, or TRP with which the second type of SSB is associated.

[0257] A27. The method of any of embodiments A1-A26, wherein the second type of SSB has a longer transmission periodicity than the first type of SSB.

[0258] A28. The method of any of embodiments A1-A27, further comprising: from said monitoring, receiving the second type of SSB; and acquiring the second MIB from the broadcast channel included in the received second type of SSB.

[0259] A29. The method of embodiment A28, wherein the second MIB comprises the parameters for acquiring the second type of SIB, and wherein the method further comprises acquiring the second type of SIB using the parameters comprised in the acquired second MIB.

[0260] A30. The method of embodiment A29, further comprising reporting the cell global identity indicated by the acquired second type of SIB as part of an automatic neighbor relation, ANR, procedure.

[0261] A31. The method of embodiment A28, wherein the second MIB comprises the at least a portion of the identity of the beam, carrier, or TRP with which the second type of SSB is associated, and wherein the method further comprises: performing one or more mobility measurements using the received second type of SSB; determining, from the at least a portion of the identity comprised in the acquired second MIB, the identity of the beam, carrier, or TRP with which the second type of SSB is associated; associating the one or more mobility measurements with the determined identity; and making a mobility decision based on the one or more mobility measurements being associated with the determined identity.

[0262] A32. The method of any of embodiments A28-A31 , wherein the second type of SSB is received during an RRC connected mode.

[0263] A33. The method of any of embodiments A1-A32, wherein the second type of SSB is deployable off the synchronization raster.

[0264] A34. The method of any of embodiments A1-A33, wherein the first type of SSB is an l-SSB and the second type of SSB is an E-SSB or an M-SSB.

[0265] A35. The method of any of embodiments A1-A34, wherein the multiple types of SSB further include a third type of SSB, wherein the third type of SSB includes one or more synchronization signals but excludes any broadcast channel from which to acquire an MIB.

[0266] A36. The method of embodiment A35, wherein said monitoring comprises monitoring for the first type of SSB while the communication device is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB and the third type of SSB while the communication device is in an RRC connected mode.

[0267] A37. The method of embodiment A35, wherein said monitoring comprises monitoring for the first type of SSB while the communication device is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB and the third type of SSB while the communication device is in either an RRC connected mode or an RRC inactive mode.

[0268] A38. The method of any of embodiments A35-A37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs, the second type of SSB includes a PSS in a second set of possible PSSs, and the third type of SSB includes a PSS in a third set of possible PSSs, wherein the first, second, and third sets of possible PSSs are mutually exclusive, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a PSS in the first set of possible PSSs, wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a PSS in the second set of possible PSSs, and wherein monitoring for the third type of SSB comprises monitoring for an SSB that includes a PSS in the third set of possible PSSs.

[0269] A39. The method of any of embodiments A35-A37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs, the second type of SSB includes a SSS in a second set of possible SSSs, and the third type of SSB includes a SSS in a third set of possible SSSs, wherein the first, second and third sets of possible SSSs are mutually exclusive, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a SSS in the first set of possible SSSs, wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a SSS in the second set of possible SSSs, and wherein monitoring for the third type of SSB comprises monitoring for an SSB that includes a SSS in the third set of possible SSSs.

[0270] A40. The method of any of embodiments A35-A37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs and the third type of SSB includes a combination of a PSS and a SSS in a third set of possible combinations of PSSs and SSSs, wherein the first, second, and third sets of possible combinations of PSSs and SSSs are mutually exclusive, wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the first set of possible combinations of PSSs and SSSs, wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the second set of possible combinations of PSSs and SSSs, and wherein monitoring for the third type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the third set of possible combinations of PSSs and SSSs.

[0271] A41. The method of any of embodiments A35-A40, further comprising: from said monitoring, receiving the third type of SSB; and using the received third type of SSB as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-colocated with the received third type of SSB.

[0272] A42. The method of embodiment A41 , wherein the third type of SSB is received during an RRC connected mode.

[0273] A43. The method of any of embodiments A35-A42, wherein the third type of SSB is deployable off the synchronization raster.

[0274] A44. The method of any of embodiments A35-A43, wherein the first type of SSB is an l-SSB, the second type of SSB is an E-SSB or an M-SSB, and the third type of SSB is a D-SSB. A45. The method of any of embodiments A1-A34, further comprising: from said monitoring, receiving the second type of SSB; and using the received second type of SSB as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-colocated with the received second type of SSB.

[0275] AA1. A method performed by a communication device, the method comprising: monitoring for a first type of synchronization signal block, SSB, while the communication device is in a first radio resource control, RRC, mode; and monitoring for a second type of SSB while the communication device is in a second RRC mode.

[0276] AA2. The method of embodiment AA1, wherein the first RRC mode is RRC idle mode and the second RRC mode is RRC connected mode.

[0277] AA3. The method of embodiment AA1 , wherein the first RRC mode is RRC idle mode and the second RRC mode is RRC inactive mode.

[0278] AA4. The method of any of embodiments AA1-AA3, wherein the first and second types of SSBs are the first and second types of SSBs according to any of embodiments A1-A45.

[0279] AA5. The method of embodiment AA4, further comprising any of the steps of any of embodiments A1-A45.

[0280] AAA1. A method performed by a communication device, the method comprising: receiving a synchronization signal block, SSB, that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a Master Information Block, MIB, wherein: the MIB comprises parameters for acquiring an SIB that indicates a cell global identity but that does not indicate scheduling information for acquiring any other SIB; and / or the MIB lacks parameters for acquiring any SIB and includes at least a portion of an identity of a beam, carrier, or transmission reception point, TRP, with which the SSB is associated.

[0281] AAA2. The method of embodiment AAA1 , wherein the SSB is the second type of SSB according to any of embodiments A1-A45. AAA3. The method of embodiment AAA2, further comprising any of the steps of any of embodiments A1-A45.

[0282] Group B Embodiments

[0283] B1. A method performed by a radio network node configured for use in a communication network, the method comprising: transmitting multiple types of synchronization signal blocks, SSBs, wherein the multiple types of SSBs include at least: a first type of SSB that is on a synchronization raster, that includes one or more synchronization signals, and that includes a broadcast channel from which to acquire a first Master Information Block, MIB, wherein the first MIB comprises parameters for acquiring a first type of System Information Block, SIB, which indicates scheduling information for one or more other SIBs; and a second type of SSB that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a second MIB, wherein the second MIB comprises: parameters for acquiring a second type of SIB which indicates at least a cell global identity; and / or at least a portion of an identity of a beam, carrier, or transmission reception point, TRP, with which the second type of SSB is associated.

[0284] B2. The method of embodiment B1 , wherein the first type of SSB is specific for and / or targets communication devices in a radio resource control, RRC, idle mode, and wherein the second type of SSB is specific for and / or targets communication devices in an RRC connected mode.

[0285] B3. The method of embodiment B1 , wherein the first type of SSB is specific for and / or targets communication devices in a radio resource control, RRC, idle mode, and wherein the second type of SSB is specific for and / or targets communication devices in either an RRC inactive mode or an RRC connected mode.

[0286] B5. The method of any of embodiments B1-B4, wherein said transmitting comprises transmitting multiple types of SSBs that are associated with the same cell.

[0287] B6. The method of any of embodiments B1-B5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs and the second type of SSB includes a PSS in a second set of possible PSSs, wherein the first and second sets of possible PSSs are mutually exclusive.

[0288] B9. The method of any of embodiments B1-B5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs and the second type of SSB includes a SSS in a second set of possible SSSs, wherein the first and second sets of possible SSSs are mutually exclusive.

[0289] B12. The method of any of embodiments B1-B5, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs, wherein the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive.

[0290] B15. The method of any of embodiments B1-B5, further comprising encoding the broadcast channel included in the first type of SSB differently than the broadcast channel included in the second type of SSB.

[0291] B16. The method of any of embodiments B1-B5, wherein said transmitting comprises transmitting the broadcast channel included in the first type of SSB using one or more first values for one or more transmission parameters, and transmitting the broadcast channel included in the second type of SSB using one or more second values for the one or more transmission parameters, wherein the one or more first values are different than the one or more second values.

[0292] B17. The method of embodiment B16, wherein the one or more parameters include one or more of: a channelization code parameter; a scrambling sequence parameter; or a cyclic redundancy check parameter.

[0293] B19. The method of any of embodiments B1-B5, wherein the first MIB and the second MIB each includes a type field, wherein the type field in the first MIB has a first value indicating that the first MIB is associated with the first type of SSB, and wherein the type field in the second MIB has a second value indicating that the second MIB is associated with the second type of SSB.

[0294] B21. The method of any of embodiments B1-B20, wherein: the first MIB and the second MIB are different types of MIBs; and / or the first MIB includes at least one field that is not included in the second MIB and / or the second MIB includes at least one field that is not included in the first MIB.

[0295] B22. The method of any of embodiments B1-B21 , wherein the first MIB and the second MIB are associated with the same cell, and wherein a content of the first MIB is different than a content of the second MIB.

[0296] B23. The method of embodiment B22, wherein at least some of the content of the first MIB is specific to an RRC idle mode and wherein at least some of the content of the second MIB is specific to an RRC connected mode.

[0297] B24. The method of any of embodiments B1-B23, wherein the second MIB comprises the parameters for acquiring the second type of SIB.

[0298] B25. The method of any of embodiments B1-B24, wherein the second type of SIB does not indicate scheduling information for any other SIB.

[0299] B26. The method of any of embodiments B1-B25, wherein the second MIB comprises the at least a portion of the identity of the beam, carrier, or TRP with which the second type of SSB is associated.

[0300] B27. The method of any of embodiments B1-B26, wherein said transmitting comprises transmitting the first type of SSB with a first periodicity in time and transmitting the second type of SSB with a second periodicity in time, wherein the second periodicity is longer than the first periodicity.

[0301] B28. The method of any of embodiments B1-B26, wherein said transmitting comprises periodically transmitting the first type of SSB and aperiodically transmitting the second type of SSB. B29. The method of any of embodiments B1-B26, wherein said transmitting comprises periodically transmitting the first type of SSB and selectively transmitting the second type of SSB on demand as needed.

[0302] B30. The method of any of embodiments B1-B26, wherein the first and second types of SSBs are each associated with a certain cell, wherein said transmitting comprises periodically transmitting the first type of SSB irrespective of whether any communication device is in RRC connected mode with respect to the certain cell and selectively transmitting the second type of SSB only when at least one communication device is in RRC connected mode with respect to the certain cell.

[0303] B31. The method of any of embodiments B1-B26, wherein said transmitting comprises periodically transmitting the first type of SSB irrespective of whether any communication device has an ongoing data transmission and selectively transmitting the second type of SSB only while at least one communication device has an ongoing data transmission.

[0304] B33. The method of any of embodiments B1-B32, comprising transmitting the second type of SSB off the synchronization raster.

[0305] B34. The method of any of embodiments B1-B33, wherein the first type of SSB is an l-SSB and the second type of SSB is an E-SSB or an M-SSB.

[0306] B35. The method of any of embodiments B1-B34, wherein the multiple types of SSB further include a third type of SSB, wherein the third type of SSB includes one or more synchronization signals but excludes any broadcast channel from which to acquire an MIB.

[0307] B36. The method of embodiment B35, wherein the first type of SSB is specific for and / or targets communication devices in a radio resource control, RRC, idle mode, and wherein each of the second and third types of SSBs is specific for and / or targets communication devices in an RRC connected mode.

[0308] B37. The method of embodiment B35, wherein the first type of SSB is specific for and / or targets communication devices in a radio resource control, RRC, idle mode, and wherein each of the second and third types of SSBs is specific for and / or targets communication devices in either an RRC inactive mode or an RRC connected mode.

[0309] B38. The method of any of embodiments B35-B37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs, the second type of SSB includes a PSS in a second set of possible PSSs, and the third type of SSB includes a PSS in a third set of possible PSSs, wherein the first, second, and third sets of possible PSSs are mutually exclusive.

[0310] B39. The method of any of embodiments B35-B37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs, the second type of SSB includes a SSS in a second set of possible SSSs, and the third type of SSB includes a SSS in a third set of possible SSSs, wherein the first, second and third sets of possible SSSs are mutually exclusive.

[0311] B40. The method of any of embodiments B35-B37, wherein the first type of SSB, the second type of SSB, and the third type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs and the third type of SSB includes a combination of a PSS and a SSS in a third set of possible combinations of PSSs and SSSs, wherein the first, second, and third sets of possible combinations of PSSs and SSSs are mutually exclusive.

[0312] B41. The method of any of embodiments B35-B40, wherein the third type of SSB is a quasicolocation, QCL, root for one or more other signals or channels.

[0313] B43. The method of any of embodiments B35-B42, comprising transmitting the third type of SSB off the synchronization raster.

[0314] B44. The method of any of embodiments B35-B43, wherein the first type of SSB is an l-SSB, the second type of SSB is an E-SSB or an M-SSB, and the third type of SSB is a D-SSB.

[0315] B45. The method of any of embodiments B1-B34, wherein the second type of SSB is a quasicolocation, QCL, root for one or more other signals or channels.

[0316] BB1. A method performed by a radio network node configured for use in a communication network, the method comprising: transmitting a first type of synchronization signal block, SSB, for communication devices in a first radio resource control, RRC, mode; and transmitting a second type of SSB for communication devices in a second RRC mode.

[0317] BB2. The method of embodiment BB1 , wherein the first RRC mode is RRC idle mode and the second RRC mode is RRC connected mode.

[0318] BB3. The method of embodiment BB1 , wherein the first RRC mode is RRC idle mode and the second RRC mode is RRC inactive mode.

[0319] BB4. The method of any of embodiments BB1-BB3, wherein the first and second types of SSBs are the first and second types of SSBs according to any of embodiments B1-B45.

[0320] BB5. The method of embodiment BB4, further comprising any of the steps of any of embodiments A1-A45.

[0321] BBB1. A method performed by a radio network node configured for use in a communication network, the method comprising: transmitting a synchronization signal block, SSB, that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a Master Information Block, MIB, wherein: the MIB comprises parameters for acquiring an SIB that indicates a cell global identity but that does not indicate scheduling information for acquiring any other SIB; and / or the MIB lacks parameters for acquiring any SIB and includes at least a portion of an identity of a beam, carrier, or transmission reception point, TRP, with which the SSB is associated.

[0322] BBB2. The method of embodiment BBB1 , wherein the SSB is the second type of SSB according to any of embodiments B1-B45.

[0323] BBB3. The method of embodiment BBB2, further comprising any of the steps of any of embodiments B1-B45.

[0324] Group C Embodiments

[0325] C1. A communication device configured to perform the method of any of the Group A embodiments. C2. A communication device comprising processing circuitry configured to perform the method of any of the Group A embodiments.

[0326] C3. A communication device comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group A embodiments.

[0327] C4. A communication device comprising: processing circuitry configured to perform the method of any of the Group A embodiments; and power supply circuitry configured to supply power to the communication device.

[0328] 05. A communication device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication device is configured to perform the method of any of the Group A embodiments.

[0329] C6. The communication device of any of embodiments C1-C5, wherein the communication device is a wireless communication device.

[0330] C7. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform the method of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0331] C8. A computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the method of any of the Group A embodiments.

[0332] C9. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0333] C10. A network node configured to perform the method of any of the Group B embodiments.

[0334] C11. A network node comprising processing circuitry configured to perform the method of any of the Group B embodiments.

[0335] C12. A network node comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group B embodiments.

[0336] C13. A network node comprising: processing circuitry configured to perform the method of any of the Group B embodiments; power supply circuitry configured to supply power to the network node.

[0337] C14. A network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform the method of any of the Group B embodiments.

[0338] C15. The network node of any of embodiments C10-C14, wherein the network node is a base station.

[0339] C16. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the method of any of the Group B embodiments.

[0340] C17. The computer program of embodiment C16, wherein the network node is a base station.

[0341] C18. A carrier containing the computer program of any of embodiments C16-C17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Claims

CLAIMS1. A method performed by a communication device (12), the method comprising: monitoring for multiple types of synchronization signal blocks, SSBs (16-1 , 16-2), in a communication network (10), wherein the multiple types of SSBs (16-1, 16-2) include at least: a first type of SSB (16-1) that is on a synchronization raster (15), that includes one or more synchronization signals (18-1), and that includes a broadcast channel (20-1) from which to acquire a first Master Information Block, MIB (22-1), wherein the first MIB (22-1) comprises parameters for acquiring a first type of System Information Block, SIB, (26-1) which indicates scheduling information (28-1) for one or more other SIBs (30-1); and a second type of SSB (16-2) that includes one or more synchronization signals (18-2) and that includes a broadcast channel (20-2) from which to acquire a second MIB (22-2), wherein the second MIB (22-2) comprises information indicating a beam, carrier, or transmission reception point, TRP, with which the second type of SSB (16-2) is associated.

2. The method of claim 1 , wherein said monitoring comprises monitoring for the first type of SSB while the communication device is in a radio resource control, RRC, idle mode, and monitoring for the second type of SSB while the communication device is in an RRC connected mode.

3. The method of any of claims 1-2, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs and the second type of SSB includes a PSS in a second set of possible PSSs, wherein the first and second sets of possible PSSs are mutually exclusive, and wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a PSS in the first set of possible PSSs, and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a PSS in the second set of possible PSSs.

4. The method of any of claims 1-2, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs and the second type of SSB includes a SSS in a second set of possible SSSs, wherein the first and second sets of possible SSSs are mutually exclusive, and wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a SSS in the first set of possible SSSs,and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a SSS in the second set of possible SSSs.

5. The method of any of claims 1-2, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs, wherein the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive, and wherein monitoring for the first type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the first set of possible combinations of PSSs and SSSs, and wherein monitoring for the second type of SSB comprises monitoring for an SSB that includes a combination of a PSS and a SSS in the second set of possible combinations of PSSs and SSSs.

6. The method of any of claims 1-2, wherein the broadcast channel included in the first type of SSB is encoded differently than the broadcast channel included in the second type of SSB.

7. The method of any of claims 1-2, wherein one or more transmission parameters govern transmission of the broadcast channel included in the first type of SSB and transmission of the broadcast channel included in the second type of SSB, wherein the one or more transmission parameters have one or more first values for the broadcast channel included in the first type of SSB and have one or more second values for the broadcast channel included in the second type of SSB, wherein the one or more first values are different than the one or more second values.

8. The method of any of claims 1-2, wherein the first MIB and the second MIB each includes a type field, wherein the type field in the first MIB has a first value indicating that the first MIB is associated with the first type of SSB, and wherein the type field in the second MIB has a second value indicating that the second MIB is associated with the second type of SSB.

9. The method of any of claims 1-8, wherein: the first MIB and the second MIB are different types of MIBs; and / or the first MIB includes at least one field that is not included in the second MIB and / or the second MIB includes at least one field that is not included in the first MIB.

10. The method of any of claims 1-9, wherein the first MIB and the second MIB are associatedwith the same cell, and wherein a content of the first MIB is different than a content of the second MIB.

11. The method of any of claims 1-10, wherein the second type of SIB does not indicate scheduling information for any other SIB.

12. The method of any of claims 1-11, wherein the second type of SSB has a longer transmission periodicity than the first type of SSB, and / or wherein the second type of SSB is deployable off the synchronization raster.

13. The method of any of claims 1-12, further comprising: from said monitoring, receiving the second type of SSB; and acquiring the second MIB from the broadcast channel included in the received second type of SSB.

14. The method of claim 13, further comprising: performing one or more mobility measurements using the received second type of SSB; determining, from the information indicating a beam, carrier, or TRP comprised in the acquired second MIB, an identity of the beam, carrier, or TRP; associating the one or more mobility measurements with the determined identity; and reporting the one or more mobility measurements to the communication network.

15. The method of any of the preceding claims, further comprising: from said monitoring, receiving the second type of SSB; and using the received second type of SSB as a quasi-colocation, QCL, root by assuming that one or more other received signals or channels are quasi-colocated with the received second type of SSB.

16. The method of any of the preceding claims, wherein the information indicating the beam, carrier, or TRP comprises at least a portion (34) of an identity of the beam, carrier, or TRP.

17. A method performed by a radio network node configured for use in a communication network, the method comprising: transmitting multiple types of synchronization signal blocks, SSBs, wherein the multiple types of SSBs include at least: a first type of SSB that is on a synchronization raster, that includes one or more synchronization signals, and that includes a broadcast channel fromwhich to acquire a first Master Information Block, MIB, wherein the first MIB comprises parameters for acquiring a first type of System Information Block, SIB, which indicates scheduling information for one or more other SIBs; and a second type of SSB that includes one or more synchronization signals and that includes a broadcast channel from which to acquire a second MIB, wherein the second MIB comprises: information indicating a beam, carrier, or transmission reception point, TRP, with which the second type of SSB is associated.

18. The method of claim 17, wherein the first type of SSB is specific for and / or targets communication devices in a radio resource control, RRC, idle mode, and wherein the second type of SSB is specific for and / or targets communication devices in an RRC connected mode.

19. The method of any of claims 17-18, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a PSS in a first set of possible PSSs and the second type of SSB includes a PSS in a second set of possible PSSs, wherein the first and second sets of possible PSSs are mutually exclusive.

20. The method of any of claims 17-18, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a SSS in a first set of possible SSSs and the second type of SSB includes a SSS in a second set of possible SSSs, wherein the first and second sets of possible SSSs are mutually exclusive.

21. The method of any of claims 17-18, wherein the first type of SSB and the second type of SSB each include a primary synchronization signal, PSS, and a secondary synchronization signal, SSS, wherein the first type of SSB includes a combination of a PSS and a SSS in a first set of possible combinations of PSSs and SSSs, and the second type of SSB includes a combination of a PSS and a SSS in a second set of possible combinations of PSSs and SSSs, wherein the first and second sets of possible combinations of PSSs and SSSs are mutually exclusive.

22. The method of any of claims 17-18, further comprising encoding the broadcast channel included in the first type of SSB differently than the broadcast channel included in the second type of SSB.

23. The method of any of claims 17-18, wherein said transmitting comprises transmitting the broadcast channel included in the first type of SSB using one or more first values for one or more transmission parameters, and transmitting the broadcast channel included in the second type of SSB using one or more second values for the one or more transmission parameters, wherein the one or more first values are different than the one or more second values.

24. The method of any of claims 17-18, wherein the first MIB and the second MIB each includes a type field, wherein the type field in the first MIB has a first value indicating that the first MIB is associated with the first type of SSB, and wherein the type field in the second MIB has a second value indicating that the second MIB is associated with the second type of SSB.

25. The method of any of claims 17-24, wherein: the first MIB and the second MIB are different types of MIBs; and / or the first MIB includes at least one field that is not included in the second MIB and / or the second MIB includes at least one field that is not included in the first MIB.

26. The method of any of claims 17-25, wherein the first MIB and the second MIB are associated with the same cell, and wherein a content of the first MIB is different than a content of the second MIB.

27. The method of any of claims 17-26, wherein the second type of SIB does not indicate scheduling information for any other SIB.

28. The method of any of claims 17-27, wherein said transmitting comprises one of: transmitting the first type of SSB with a first periodicity in time and transmitting the second type of SSB with a second periodicity in time, wherein the second periodicity is longer than the first periodicity; periodically transmitting the first type of SSB and aperiodically transmitting the second type of SSB; periodically transmitting the first type of SSB and selectively transmitting the second type of SSB on demand as needed.

29. The method of any of claims 17-28, comprising transmitting the second type of SSB off the synchronization raster.

30. The method of any of claims 17-29, wherein the second type of SSB is a quasicolocation, QCL, root for one or more other signals or channels.31 The method of any of claims 17-30, information indicating the beam, carrier, or TRP comprises at least a portion (34) of an identity of the beam, carrier, or TRP.32 A communication device configured to perform the method of any of claims 1-1633 A communication device comprising: communication circuitry; and processing circuitry configured to perform the method of any of claims 1-16. 34 A network node configured to perform the method of any of claims 17-31 .35 A network node comprising: communication circuitry; and processing circuitry configured to perform the method of any of claims 17-31.

Images