Method and apparatus for SSB measurement time configuration in communication network
By adjusting the configuration and offset configuration of SSB measurement time in the communication network, the problem of propagation delay caused by mobile base stations/relays affecting SSB measurement time is solved, and the accuracy and quality of SSB measurements are improved.
Patent Information
- Application Number
- CN202380033076.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-14
- Filing Date
- 2023-02-09
- Publication Date
- 2024-11-19
AI Technical Summary
In a communication network, the propagation delay caused by the mobile base station/relay affects the accuracy of the SSB measurement time, causing the terminal device to lose the portion of the SSB within the predetermined measurement time window, thereby affecting the accuracy of the measurement results.
By determining and sending configurations of SSB measurement time and related offset configurations in the communication network, adjusting the SSB measurement time to adapt to propagation delays, ensuring that the terminal device can perform SSB measurements within the time window that starts earlier or ends later, reducing The effect of time alignment.
Improves the quality and accuracy of SSB measurements and enhances the communication network performance in the mobile base station/relay situation.
Smart Images

Figure CN118985106A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to wireless communication technology, and more particularly to a method and apparatus for enhancing SSB measurement time configuration (SMTC) in a communication network. SSB may refer to a synchronization signal block, which in an exemplary scenario may specifically be a combination of a synchronization signal (SS) and a physical broadcast channel (PBCH) in a communication network. Background Art
[0002] As the demand for communication services develops, many other technologies need to be used to supplement the mobile communication network on the ground. For example, for some underserved areas where it is difficult to deploy fixed base stations, mobile base stations / relays will be a favorable choice. An example of such a mobile base station / relay is a satellite communication network.
[0003] For example, satellite communications are experiencing a resurgence. Several satellite network plans have been announced over the past few years. Satellite networks can complement terrestrial mobile networks by providing connectivity and multicast / broadcast services to underserved areas.
[0004] To benefit from a strong mobile ecosystem and economies of scale, there is significant interest in adapting terrestrial radio access technologies including LTE and NR to satellite networks, which is reflected in the 3GPP standardization work.
[0005] In 3GPP Release 15, the first version of the 5G System (5GS) was specified. This is a new generation of radio access technology designed to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and mMTC. 5G includes the New Radio (NR) access layer interface and the 5G Core network (5GC). The NR physical layer and upper layers are reusing parts of the LTE specifications and adding required components driven by new use cases. One of the components is the introduction of a sophisticated beamforming and beam management framework to extend the support of 3GPP technologies to frequency ranges above 6GHz.
[0006] In Release 15, 3GPP began preparing for NR operation in non-terrestrial networks (NTN). This work was carried out within the study project "NR support for non-terrestrial networks" and resulted in 3GPP TR 38.811[1]. In Release 16, preparations for NR operation in NTN networks continued under the study project "NR support solutions for non-terrestrial networks"[2]. Summary of the invention
[0007] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0008] The movement of base stations / relays in the network may cause some problems, such as moving cells or switching cells, or propagation delays, etc. This delay will also affect the SSB sent to the terminal device served by the network. When the terminal device tries to measure the SSB within the predetermined measurement time window / gap, some parts of the SSB may be lost due to the time offset of the SSB caused by propagation delays, etc. The measurement results obtained by the terminal device will be disturbed.
[0009] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Specific methods and apparatus are provided for enhancing SMTC in a communication network.
[0010] A first aspect of the present disclosure provides a method performed by a network node in a communication network. The method may include: determining a first configuration for an SSB measurement time; determining a second configuration for indicating an offset associated with the SSB measurement time; and sending the first configuration and the second configuration to a wireless device to instruct the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration. SSB refers to a combination of a synchronization signal and a physical broadcast channel.
[0011] In an embodiment of the present disclosure, the first configuration may include: periodicity, and duration of the SSB measurement time. In addition, the second configuration may include: a timing offset window associated with the duration of the SSB measurement time.
[0012] In an embodiment of the present disclosure, the duration of the SSB measurement time may be extended by the timing offset window to start earlier than the first configuration; and / or the duration of the SSB measurement time may be extended by the timing offset window to end later than the first configuration.
[0013] In an embodiment of the present disclosure, the duration of the SSB measurement time may be shifted by the timing offset window to start earlier than the first configuration; or, the duration of the SSB measurement time may be shifted by the timing offset window to end later than the first configuration.
[0014] In an embodiment of the present disclosure, the timing offset window may be constant; or the timing offset window may be periodically changed at an update rate.
[0015] In an embodiment of the present disclosure, the second configuration may be enabled or disabled based at least on an instruction from the network node, and / or a report from the wireless device, and / or a predefined rule.
[0016] In an embodiment of the present disclosure, the second configuration may be determined based on at least the first configuration.
[0017] In an embodiment of the present disclosure, the second configuration may be determined by the wireless device and / or by a network node providing service for the wireless device based at least on measurements of SSBs and / or cells.
[0018] In an embodiment of the present disclosure, the second configuration may be determined based at least on a location of the wireless device.
[0019] In an embodiment of the present disclosure, the second configuration may include a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
[0020] In an embodiment of the present disclosure, the first configuration may include at least a first SSB measurement time and a second SSB measurement time; and the second configuration may include at least a first timing offset window for a first duration of the first SSB measurement time and a second timing offset window for a second duration of the second SSB measurement time.
[0021] In an embodiment of the present disclosure, when the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window may be disabled.
[0022] In an embodiment of the present disclosure, it may be determined whether the first timing offset window or the second timing offset window is disabled based on the priority of the first timing offset window and / or the priority of the second timing offset window.
[0023] In an embodiment of the present disclosure, the first configuration and the second configuration may be provided to the wireless device from a satellite; and the second configuration may be determined based on at least a location of the wireless device, ephemeris data of the satellite and / or a feeder link delay.
[0024] In an embodiment of the present disclosure, the second configuration may be enabled or disabled for the wireless device based on a change in at least one of the following: the validity or invalidity of the ephemeris data, the validity or invalidity of the position of the wireless device, the type of the satellite, the position of at least one neighboring satellite, or the time to be covered by at least one neighboring satellite. Alternatively, the second configuration may be enabled or disabled for the wireless device based on at least one of the following: the capability of the wireless device; or the first configuration.
[0025] In an embodiment of the present disclosure, the measurement process and requirements for measuring the SSB during the SSB measurement time may be based on the first configuration and / or the second configuration.
[0026] In an embodiment of the present disclosure, the requirements for measuring SSB may include at least one of the following: measurement time, measurement accuracy, the number of identified cells to be measured per carrier, and / or the number of beams to be measured.
[0027] In an embodiment of the present disclosure, scheduling restrictions may be applied to the SSB measurement time based on the first configuration and / or the second configuration.
[0028] In an embodiment of the present disclosure, when the duration of the SSB measurement time is close to or conflicts with a paging occasion, the duration and / or the second configuration may be disabled.
[0029] In an embodiment of the present disclosure, the first configuration and the second configuration may be sent to a plurality of wireless devices including the wireless device through broadcasting. Alternatively, the first configuration and the second configuration may be sent to the wireless device through a dedicated message.
[0030] In an embodiment of the present disclosure, the network node may include a satellite or a base station relayed by the satellite.
[0031] In an embodiment of the present disclosure, the wireless device may be in an idle mode, an inactive mode, or a connected mode.
[0032] A second aspect of the present disclosure provides a method performed by a terminal device in a communication network. The method may include: receiving a first configuration and a second configuration from a network node in the communication network; and performing SSB measurement based on at least the first configuration and / or the second configuration. The first configuration is used for SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time.
[0033] In an embodiment of the present disclosure, the first configuration may include: periodicity, and duration of the SSB measurement time. In addition, the second configuration may include: a timing offset window associated with the duration of the SSB measurement time.
[0034] In an embodiment of the present disclosure, the duration of the SSB measurement time may be extended by the timing offset window to start earlier than the first configuration; and / or the duration of the SSB measurement time may be extended by the timing offset window to end later than the first configuration.
[0035] In an embodiment of the present disclosure, the duration of the SSB measurement time may be shifted by the timing offset window to start earlier than the first configuration; or, the duration of the SSB measurement time may be shifted by the timing offset window to end later than the first configuration.
[0036] In an embodiment of the present disclosure, the timing offset window may be constant; or the timing offset window may be periodically changed at an update rate.
[0037] In an embodiment of the present disclosure, the second configuration may be enabled or disabled based at least on an instruction from the network node, and / or a report from the wireless device, and / or a predefined rule.
[0038] In an embodiment of the present disclosure, the second configuration may be determined based on at least the first configuration.
[0039] In an embodiment of the present disclosure, the second configuration may be determined by the wireless device and / or by a network node providing service for the wireless device based at least on measurements of SSBs and / or cells.
[0040] In an embodiment of the present disclosure, the second configuration may be determined based at least on a location of the wireless device.
[0041] In an embodiment of the present disclosure, the second configuration may include a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
[0042] In an embodiment of the present disclosure, the first configuration may include at least a first SSB measurement time and a second SSB measurement time; and the second configuration may include at least a first timing offset window for a first duration of the first SSB measurement time and a second timing offset window for a second duration of the second SSB measurement time.
[0043] In an embodiment of the present disclosure, when the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window may be disabled.
[0044] In an embodiment of the present disclosure, it may be determined whether the first timing offset window or the second timing offset window is disabled based on the priority of the first timing offset window and / or the priority of the second timing offset window.
[0045] In an embodiment of the present disclosure, the first configuration and the second configuration may be provided to the wireless device from a satellite; and the second configuration may be determined based on at least a location of the wireless device, ephemeris data of the satellite and / or a feeder link delay.
[0046] In an embodiment of the present disclosure, the second configuration may be enabled or disabled for the wireless device based on a change in at least one of the following: validity or invalidity of the ephemeris data, validity or invalidity of the position of the wireless device, the type of the satellite, the position of at least one neighboring satellite, or the time to be covered by at least one neighboring satellite. Alternatively, the second configuration may be enabled or disabled for the wireless device based on at least one of the following: capability of the wireless device; or the first configuration.
[0047] In an embodiment of the present disclosure, the measurement process and requirements for measuring the SSB during the SSB measurement time may be based on the first configuration and / or the second configuration.
[0048] In an embodiment of the present disclosure, the requirements for measuring SSB may include at least one of the following: measurement time, measurement accuracy, the number of identified cells to be measured per carrier, and / or the number of beams to be measured.
[0049] In an embodiment of the present disclosure, scheduling restrictions may be applied to the SSB measurement time based on the first configuration and / or the second configuration.
[0050] In an embodiment of the present disclosure, when the duration of the SSB measurement time is close to or conflicts with a paging occasion, the duration and / or the second configuration may be disabled.
[0051] In an embodiment of the present disclosure, the first configuration and the second configuration may be sent to a plurality of wireless devices including the wireless device through broadcasting. Alternatively, the first configuration and the second configuration may be sent to the wireless device through a dedicated message.
[0052] In an embodiment of the present disclosure, the network node may include a satellite or a base station relayed by the satellite.
[0053] In an embodiment of the present disclosure, the wireless device may be in an idle mode, an inactive mode, or a connected mode.
[0054] A third aspect of the present disclosure provides an apparatus for a network node in a communication network. The apparatus may include: a processor; and a memory containing instructions executable by the processor. The apparatus for the network node is operated to: determine a first configuration for an SSB measurement time; determine a second configuration for indicating an offset associated with the SSB measurement time; and send the first configuration and the second configuration to a wireless device to instruct the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration. The SSB refers to a combination of a synchronization signal and a physical broadcast channel.
[0055] In an embodiment of the present disclosure, the device may further be operated to execute the method according to any of the above embodiments.
[0056] A fourth aspect of the present disclosure provides an apparatus for a wireless device. The apparatus for the wireless device may include: a processor; and a memory containing instructions executable by the processor. The apparatus for the wireless device operates to: receive a first configuration and a second configuration from a network node in a communication network; and perform SSB measurement based on at least the first configuration and / or the second configuration. The first configuration is used for SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time.
[0057] In an embodiment of the present disclosure, the device may further be operated to execute the method according to any of the above embodiments.
[0058] A fifth aspect of the present disclosure provides a computer-readable storage medium, which stores instructions. When the instructions are executed by at least one processor, the at least one processor executes the method according to any of the above embodiments.
[0059] Embodiments herein have many advantages. According to embodiments of the present disclosure, a method for enhancing SMTC in a communication network may be provided.
[0060] Specifically, an offset associated with the SSB measurement time may be indicated. The specific SSB measurement may be adjusted accordingly. Thus, the impact of a mobile base station / relay (e.g., a mobile satellite) on the time alignment of the SSB may be reduced. The quality of the SSB measurement in such situations may be enhanced. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] The above and other aspects, features and advantages of various embodiments of the present disclosure will become more fully apparent through the following detailed description in conjunction with the accompanying drawings, in which like reference numerals or letters are used to represent similar or equivalent elements. In order to facilitate a better understanding of the embodiments of the present disclosure, the accompanying drawings are shown and are not necessarily drawn to scale, in which:
[0062] Figure 1A is a diagram illustrating an example architecture of a satellite network with bent pipe repeaters.
[0063] Figure 1B is a diagram showing an example illustration of an SSB, an SMTC window, and a measurement gap.
[0064] Figure 2 is a flow chart illustrating a method performed by a network node according to an embodiment of the present disclosure.
[0065] Figure 3 is a flow chart illustrating a method performed by a wireless device according to an embodiment of the present disclosure.
[0066] Figure 4 is a diagram showing an example of a signaling flow between a network node and a UE.
[0067] Figure 5A is a diagram showing multiple SMTCs signaled by a network node to a wireless device.
[0068] Figure 5B is a diagram showing a 4 ms SMTC window.
[0069] Figure 5C is a diagram showing SMTC configuration offset.
[0070] Figure 5D is a diagram depicting an example of an SMTC Timing Offset Window (STOW) on either side of the SMTC duration.
[0071] Figure 5E is a diagram depicting an example of STOW on one side of the SMTC duration.
[0072] Fig. 5F is a diagram showing time-shifted STOW.
[0073] Figure 5G It is shown that the STOW concept is used to solve Figure 5C Figure 1 shows the problem.
[0074] Figure 5H is a diagram showing exemplary parameters in a STOW configuration.
[0075] Fig.5I is a diagram showing exemplary multiple STOWs for multiple SMTCs.
[0076] Figure 6 is a diagram showing switching between different scenes.
[0077] Fig. 7A is a block diagram showing an exemplary apparatus for a network node suitable for executing a method according to an embodiment of the present disclosure.
[0078] Figure 7B is a block diagram illustrating an exemplary apparatus for a wireless device suitable for performing a method according to an embodiment of the present disclosure.
[0079] Figure 8 is a block diagram illustrating a device / computer-readable storage medium according to an embodiment of the present disclosure.
[0080] Fig. 9A is a schematic diagram showing units of an exemplary device of a network node according to an embodiment of the present disclosure.
[0081] Fig. 9B is a block diagram illustrating an exemplary apparatus for a second network node suitable for executing a method according to an embodiment of the present disclosure.
[0082] Fig.10 An example of a communication system 1000 is shown in accordance with some embodiments.
[0083] Fig.11 A UE 1100 is shown in accordance with some embodiments.
[0084] Fig.12 A network node 1200 is shown according to some embodiments.
[0085] Fig.13 is a block diagram of a host 1300, which may be a computer system according to various aspects described herein. Fig.10 An embodiment of host 1016.
[0086] Fig.14 is a block diagram illustrating a virtualization environment 1400 in which functionality implemented by some embodiments may be virtualized.
[0087] Fig.15 A communication diagram is shown in which a host 1502 communicates with a UE 1506 through a network node 1504 over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION
[0088] There is growing interest in applying NB-IoT and LTE-M to NTN. Therefore, 3GPP Release 17 includes both work items for NRNTN[3] and study items for NB-IoT and LTE-M support for NTN[4].
[0089] A satellite radio access network typically consists of the following components: a satellite, which refers to a space-borne platform; an earth-based gateway, which connects the satellite to a base station or core network, depending on the choice of architecture; a feeder link, which refers to the link between the gateway and the satellite; and an access link or service link, which refers to the link between the satellite and the UE.
[0090] Depending on the orbital altitude, satellites can be classified as low Earth orbit (LEO), medium Earth orbit (MEO) or geostationary orbit (GEO) satellites: LEO: typical altitude range is 250-1,500 km, orbital period range is 90-120 minutes; MEO: typical altitude range is 5,000-25,000 km, orbital period range is 3-15 hours; GEO: altitude is about 35,786 km, orbital period is 24 hours.
[0091] Satellite communication networks can be divided into two basic architectures based on the functions of the satellites in the system.
[0092] For the transparent payload architecture (also known as bent pipe architecture), the satellite forwards the received signal between the terminal and the network equipment on the ground, only amplifying and converting from the uplink frequency to the downlink frequency. When applied to the general 3GPP architecture and terminology, the transparent payload architecture means that the gNB is located on the ground and the satellite forwards the signal / data between the gNB and the UE.
[0093] For the regenerative payload architecture, the satellite includes onboard processing to demodulate and decode the received signal and regenerate the signal before sending it back to Earth. When applied to the general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite.
[0094] In the NR NTN work items in 3GPP Release 17, only the transparent payload architecture is considered.
[0095] Satellite networks or satellite-based mobile networks can also be called non-terrestrial networks (NTNs). On the other hand, mobile networks with ground-based base stations can also be called terrestrial networks (TNs) or non-NTN networks. Satellites within NTNs can be called NTN nodes, NTN satellites, or simply satellites.
[0096] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and implement the present invention, rather than to impose any limitation on the scope of the present invention. References to features, advantages or similar language throughout this specification do not mean that all features and advantages that can be implemented by the present disclosure should be in or present in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages is understood to mean that specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, the described features, advantages and characteristics of the present disclosure may be combined in one or more embodiments in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more specific features or advantages of a specific embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, which may not be present in all embodiments of the present disclosure.
[0097] Generally, unless different meanings are clearly given and / or implied in the context of using the term, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless clearly stated otherwise, all references to one / an / the element, equipment, assembly, device, step, etc. should be openly interpreted as referring to at least one instance of the element, equipment, assembly, device, step, etc. Unless a step is clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.
[0098] As used herein, the term "network" or "communication network" refers to a network that complies with any suitable wireless communication standard. For example, wireless communication standards may include New Radio (NR), Long Term Evolution (LTE), Advanced LTE, Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. In the following description, the terms "network" and "system" may be used interchangeably. In addition, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to wireless communication protocols defined by standards organizations such as the Third Generation Partnership Project (3GPP), or wired communication protocols.
[0099] The term "network node" used herein refers to a network device or network entity or network function or any other device (physical or virtual) in a communication network. For example, a network node in a network may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a server node / function (e.g., a service capability server / application server (SCS / AS), a group communication service application server (GCS AS), an application function (AF)), an open node / function (e.g., a service capability exposure function (SCEF), a network exposure function (NEF)), a unified data management (UDM), a home subscriber server (HSS), a session management function (SMF), an access and mobility management function (AMF), a mobility management entity (MME), a controller or any other suitable device in a wireless communication network. A BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as a femto, a micro, etc.).
[0100] Further examples of network nodes include a Multi-Standard Radio (MSR) radio such as an MSR BS, a network controller such as a Radio Network Controller (RNC) or a Base Station Controller (BSC), a Base Transceiver Station (BTS), a transmission point, a transmission node, a positioning node, etc.
[0101] In addition, the terms "network node", "network function", "network entity" in this document may also refer to any suitable node, function, entity that can be implemented (physically or virtually) in a communication network. For example, a 5G system (5GS) may include multiple NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), etc. In other embodiments, for example, depending on the specific network, the network function may include different types of NFs (such as PCRF (Policy and Charging Rules Function), etc.).
[0102] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom, while "wireless (terminal) device" may refer to any terminal device that can access a communication network in a wireless manner and receive services therefrom. As an example and not a limitation, a terminal device may refer to a mobile terminal, a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), etc. In the following description, the terms "wireless device", "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate in accordance with one or more communication standards promulgated by 3GPP (e.g., 3GPP's LTE and / or NR standards). As used herein, a "user equipment" or "UE" may not necessarily have a "user" in terms of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, a terminal device may be designed to send information to a network on a predetermined schedule when triggered by an internal or external event, or in response to a request from a communication network. In contrast, a UE may represent a device that is intended to be sold to a human user or operated by a human user but may not initially be associated with a specific human user.
[0103] As yet another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring, sensing and / or measurement, etc. and transmits the results of such monitoring, sensing and / or measurement, etc. to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (such as watches), etc. In other cases, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0104] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.
[0105] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the example embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0106] As used herein, the phrase "at least one of A and / or B" should be understood to mean "only A, only B, or both A and B". The phrase "A and / or B" should be understood to mean "only A, only B, or A and B".
[0107] The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms of "a", "an", and "the" are intended to also include the plural forms unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "include", "comprise", "have", and / or "contain" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0108] It should be noted that the terms used in this article are only used to facilitate the description and distinction of nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.
[0109] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0110] The following can be considered as the main challenges to be addressed in NTN: moving satellites (resulting in moving cells or switching cells), long propagation delays.
[0111] Moving satellites (resulting in moving or switching cells) introduce new challenges, as the default assumption in terrestrial network design (e.g. NR or LTE) is that cells are stationary. This is not the case for NTN, especially when LEO satellites are considered. A UE on the ground may only see a LEO satellite for a few seconds or minutes. There are two different options for LEO deployments. With earth-fixed beams, the beam / cell coverage is fixed relative to the geographic location, i.e. a steerable beam from the satellite ensures that a certain beam covers the same geographic area even if the satellite moves relative to the surface of the Earth. On the other hand, with mobile beams, LEO satellites have a fixed antenna pointing direction relative to the surface of the Earth, e.g. perpendicular to the surface of the Earth, so the cell / beam coverage sweeps across the Earth as the satellite moves. In this case, the spot beam serving the UE may switch every few seconds.
[0112] Longer propagation delays create new challenges, as propagation delays in land mobile systems are typically less than 1 millisecond. In contrast, propagation delays in NTNs can be much longer, ranging from a few milliseconds (LEO) to hundreds of milliseconds (GEO), depending on the altitude of the spaceborne or airborne platforms deployed in the NTN.
[0113] In a terrestrial network (TN), the relative time position of the SSB between the serving cell and the neighboring cells is fixed. The propagation delay within each cell depends on the cell size and the UE location, and from the UE's perspective, it only changes due to UE movement.
[0114] In contrast, in a low earth orbit (LEO) scenario, even the propagation delay between the UE and the serving cell varies with time due to the movement of the satellite. In addition, the propagation delay towards neighboring cells on neighboring satellites also varies with time. The situation becomes even worse when the feeder link delay is also considered and increases with the increase in satellite altitude.
[0115] When belonging to different satellites, the serving cell and the target cell may not necessarily be time and frame synchronized. For the SMTC window and gap configuration towards the UE, the time offset caused by the SSB transmission between different cells also needs to be considered.
[0116] Figure 1AAn exemplary architecture of a satellite network with bent pipe transponders (i.e., a transparent payload architecture) is shown. A base station (BS) 11 (e.g., a gNB) may be integrated in a gateway 16 or connected to the gateway 16 via a terrestrial connection (wired, optical fiber, wireless link). A communications satellite 10 typically generates multiple beams over a given area. The footprint of a beam is typically elliptical and is traditionally considered to be a cell, but 3GPP work does not exclude cells consisting of the footprints of multiple beams. The footprint of a beam is also often referred to as a spot beam 13. The footprint of a beam or spot beam 13 may move over the surface of the Earth as the satellite moves, or it may be fixed to the Earth by a beam pointing mechanism used by the satellite to compensate for satellite motion (the latter may be referred to as a quasi-Earth fixed beam or quasi-Earth fixed cell). The size of a spot beam depends on the system design and ranges from tens of kilometers to thousands of kilometers.
[0117] In LEO or MEO communication systems, a large number of satellites need to be deployed in a series of orbits to provide continuous coverage around the globe. Launching a giant satellite constellation is an expensive and time-consuming process. Therefore, it is expected that all LEO and MEO satellite constellations will only provide partial earth coverage for some time. For some constellations dedicated to large-scale IoT services with low latency requirements, it may not even be necessary to support full earth coverage. It may be sufficient to provide occasional or regular coverage depending on the orbital period of the constellation.
[0118] The wireless device 12 (e.g., a 3GPP UE in RRC_IDLE or RRC_INACTIVE state) needs to perform many procedures over the access link 14, including mobility measurement purposes, paging monitoring, logging of measurement results, tracking area updates, and searching for new PLMNs (Public Land Mobile Networks), to name a few. These procedures will consume power in the device, and the general trend of 3GPP is to allow relaxation of these procedures to extend device battery life. This trend is particularly evident for IoT devices supported by reduced functionality (redcap), NB IoT, and LTE-M.
[0119] Propagation delay is an important aspect of satellite communications, which is different from the delay expected in land mobile systems. For a bent-pipe satellite network, i.e. a network with an access link 14 and a feeder link 15 to a gateway 16, the round-trip delay may depend on the orbital altitude, ranging from tens of milliseconds for LEO satellites to hundreds of milliseconds for GEO satellites. In contrast, the round-trip delay in terrestrial cellular networks is typically less than 1 millisecond.
[0120] The distance between the UE (device) 12 and the satellite 10 can vary significantly, depending on the position of the satellite and the elevation angle ε seen by the UE. Assuming a circular orbit, the minimum distance is achieved when the satellite is directly above the UE (ε = 90°) and the maximum distance is achieved when the satellite is at the minimum possible elevation angle. Table 1 shows the distance between the satellite and the UE at different orbital altitudes and elevation angles, as well as the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay when ε = 90°). Note that this table assumes a regenerative payload architecture. For the case of a transparent payload, the propagation delay between the gateway and the satellite also needs to be considered, unless the base station corrects for this.
[0121] Table 1: Propagation delays for different orbit altitudes and elevation angles.
[0122]
[0123]
[0124] Due to the high speeds of LEO and MEO satellites, propagation delays can also vary widely and can vary by about 10-100μs per second, depending on orbital altitude and satellite speed.
[0125] This propagation delay will affect the transmission of signals (eg, SSB signals) between the satellite and the UE.
[0126] Figure 1B is a schematic diagram showing an example illustration of SSB, SMTC window and measurement gap.
[0127] The NR synchronization signal (SS) consists of the primary SS (PSS) and the secondary SS (SSS). The NR physical broadcast channel (PBCH) carries very basic system information. The combination of SS and PBCH is called SSB in NR. Multiple SSBs are transmitted in a local burst set. In an SS burst set, multiple SSBs can be transmitted in different beams. The transmission of SSBs within a local burst set is restricted to a 5ms window. The set of possible SSB time locations within an SS burst set depends on a set of parameters (numerology) that are uniquely identified by the frequency band in most cases. The SSB period can be configured from a value set {5, 10, 20, 40, 80, 160} ms (where the unit used in the configuration is a subframe, which has a duration of 1ms).
[0128] The UE is not required to perform measurements with the same period as the SSB period. Therefore, SSB Measurement Time Configuration (SMTC) has been introduced for NR. Signaling of the SMTC window informs the UE about the timing and period of the SSBs that the UE can use for measurements. The SMTC window period can be configured from the value set {5, 10, 20, 40, 80, 160} ms, matching the possible SSB period. The SMTC window duration can be configured from the value set {1, 2, 3, 4, 5} ms (where the unit used in the configuration is subframe and the duration is 1 ms).
[0129] The UE can use the same RF module for measuring neighboring cells and for data transmission in the serving cell. Measurement gaps allow the UE to suspend data transmission in the serving cell and perform measurements of neighboring cells. The measurement gap repetition period is configurable from the value set {20,40,80,160} ms, and the gap length is configurable from the value set {1.5,3,3.5,4,5.5,6,10,20} ms. Typically, the measurement gap length is configured to be greater than the SMTC window duration to allow time for RF retuning. A measurement gap time advance is also introduced to fine-tune the relative position of the measurement gap with respect to the SMTC window. The measurement gap timing advance is configurable from the value set {0,0.25,0.5} ms.
[0130] For Release 17 NTN, Release 17 NR operations (e.g., SMTC configuration and UE measurement gap configuration) may be enhanced by addressing issues associated with different / larger propagation delays and satellites (e.g., considering their deployment, mobility, altitude, minimum elevation angles, and prioritizing typical NTN scenarios).
[0131] In some examples, Release 17 NTN does not rely solely on network implementation to solve the above issues.
[0132] Enhancements to SMTC configuration may be supported for Release 17 NTN. In some examples, new UE assistance is defined in Release 17 NTN so that the network can correctly (re)configure SMTC and / or measurement gaps. In some examples, for Release 17 NTN, one or more SMTC configurations associated with a frequency may be configured. For example, an SMTC configuration may be associated with a set of cells (e.g., any other suitable set determined per satellite or per gNB). For example, multiple SMTC configurations may be enabled by additionally introducing different new offsets to the traditional SMTC configuration. For example, the following improvements may also be considered:
[0133] (a) Multiple SMTCs can be configured for each carrier for a UE and used in parallel.
[0134] (b) The NW can know which SMTC (including offset / periodicity, etc.) is associated with a specific UE.
[0135] (c) There may be multiple SMTC configurations only in time or for a specific location.
[0136] (d) The potential impact on signaling can be considered, assuming that the delay is a dynamic value.
[0137] (e) Feeder link delay can also be considered.
[0138] The configuration of one or more offsets may be based on network implementation. The network may update the UE's SMTC configuration to accommodate different propagation delays. Measurement gap enhancement may be supported.
[0139] The maximum number of SMTCs in one measurement object may be 4. Multiple SMTC configurations may be enabled by additionally introducing different new offsets for legacy SMTC configurations. Multiple SMTC configurations may be enabled by additionally introducing different new offsets for legacy SMTC configurations. The specific maximum number of SMTC configurations in one measurement object with the same ssbFrequency may be 4. Different UE capabilities may be considered to support measurements of multiple configured SMTCs.
[0140] Regarding the maximum number of SMTCs per frequency layer, for the same ssbFrequency, the maximum number of SMTCs configured per measurement object can be 4. The number of parallel SMTCs for requirement-defined configurations can be configured. Different UE capabilities may be required to support measurements of multiple configured SMTCs. The capability for the number of measurement cell groups may also be considered.
[0141] Figure 2 is a flow chart showing a method performed by a network node according to an embodiment of the present disclosure. Figure 2 As shown, the method 100 performed by a network node in a communication network may include: step S102, determining a first configuration for SSB measurement time; step S104, determining a second configuration for indicating an offset related to the SSB measurement time; step S106, sending the first configuration and the second configuration to the wireless device to instruct the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration. SSB refers to a combination of a synchronization signal and a physical broadcast channel.
[0142] According to an embodiment of the present disclosure, a method for enhancing SMTC in a communication network may be provided. Specifically, an offset associated with an SSB measurement time may be indicated. The specific SSB measurement may be adjusted accordingly. Thus, the impact of a mobile base station / relay (e.g., a mobile satellite) on the time alignment of the SSB may be reduced. The measurement quality of the SSB in such a case may be enhanced.
[0143] In an embodiment of the present disclosure, the first configuration may include: periodicity, and duration of the SSB measurement time. In addition, the second configuration may include: a timing offset window associated with the duration of the SSB measurement time. For example, the timing offset window may be an SMTC timing offset window (STOW).
[0144] In an embodiment of the present disclosure, the duration of the SSB measurement time may be extended by the timing offset window to start earlier than the first configuration; and / or the duration of the SSB measurement time may be extended by the timing offset window to end later than the first configuration.
[0145] In an embodiment of the present disclosure, the duration of the SSB measurement time may be shifted by the timing offset window to start earlier than the first configuration; or, the duration of the SSB measurement time may be shifted by the timing offset window to end later than the first configuration.
[0146] According to an embodiment of the present disclosure, the SSB measurement time may be adjusted (eg, extended and / or shifted) so that portions of the SSB signal not covered by the original SMTC may also be measured.
[0147] In an embodiment of the present disclosure, the timing offset window may be constant; or the timing offset window may be changed periodically at an update rate.
[0148] In an embodiment of the present disclosure, the second configuration may be enabled or disabled based at least on an instruction from a network node, and / or a report from a wireless device, and / or a predefined rule.
[0149] In an embodiment of the present disclosure, the second configuration may be determined based on at least the first configuration.
[0150] In an embodiment of the present disclosure, the second configuration may be determined by the wireless device and / or by a network node providing service for the wireless device based at least on measurements of SSBs and / or cells.
[0151] In an embodiment of the present disclosure, the second configuration may be determined based at least on a location of the wireless device.
[0152] In an embodiment of the present disclosure, the second configuration may include a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
[0153] In an embodiment of the present disclosure, the first configuration may include at least a first SSB measurement time and a second SSB measurement time; and the second configuration may include at least a first timing offset window for a first duration of the first SSB measurement time and a second timing offset window for a second duration of the second SSB measurement time.
[0154] In an embodiment of the present disclosure, when the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window may be disabled.
[0155] In an embodiment of the present disclosure, it may be determined whether the first timing offset window or the second timing offset window is disabled based on the priority of the first timing offset window and / or the priority of the second timing offset window.
[0156] In an embodiment of the present disclosure, the first configuration and the second configuration may be provided to the wireless device from a satellite; and the second configuration may be determined based on at least a location of the wireless device, ephemeris data of the satellite, and / or a feeder link delay.
[0157] In an embodiment of the present disclosure, the second configuration may be enabled or disabled for the wireless device based on a change in at least one of the following: validity or invalidity of ephemeris data, validity or invalidity of the location of the wireless device, the type of satellite, the location of at least one neighboring satellite, or the time to be covered by at least one neighboring satellite. Alternatively, the second configuration may be enabled or disabled for the wireless device based on at least one of the following: capabilities of the wireless device; or the first configuration.
[0158] According to an embodiment of the present disclosure, multiple criteria are provided for a network node or a wireless device to enable, disable or update a specific STOW.
[0159] In an embodiment of the present disclosure, the measurement process and requirement for measuring the SSB during the SSB measurement time may be based on the first configuration and / or the second configuration.
[0160] In an embodiment of the present disclosure, the requirements for measuring SSB may include at least one of the following: measurement time, measurement accuracy, the number of identified cells to be measured per carrier, and / or the number of beams to be measured.
[0161] According to an embodiment of the present disclosure, the second configuration may be applied to a case with multiple SMTCs.
[0162] In an embodiment of the present disclosure, scheduling restrictions may be applied to the SSB measurement time based on the first configuration and / or the second configuration.
[0163] In an embodiment of the present disclosure, when the duration of the SSB measurement time is close to or conflicts with the paging occasion, the duration and / or the second configuration may be disabled.
[0164] According to an embodiment of the present disclosure, STOW may be applied to a connected mode (with scheduling restrictions) or an idle mode (with paging occasions).
[0165] In an embodiment of the present disclosure, the first configuration and the second configuration may be transmitted to a plurality of wireless devices including a wireless device through broadcasting. Alternatively, the first configuration and the second configuration may be transmitted to the wireless device through a dedicated message.
[0166] In an embodiment of the present disclosure, the network node may include a satellite or a base station relayed by a satellite.
[0167] In an embodiment of the present disclosure, the wireless device may be in an idle mode, or an inactive mode, or a connected mode.
[0168] Figure 3 is a flow chart showing a method performed by a wireless device according to an embodiment of the present disclosure. Figure 3 As shown, the method 200 performed by the wireless device may include: step S202, receiving a first configuration and a second configuration from a network node in the communication network; step S204, performing SSB measurement based on at least the first configuration and / or the second configuration. The first configuration is used for the SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time.
[0169] In an embodiment of the present disclosure, the first configuration may include: periodicity, and duration of the SSB measurement time. In addition, the second configuration may include: a timing offset window related to the duration of the SSB measurement time.
[0170] In an embodiment of the present disclosure, the duration of the SSB measurement time may be extended by the timing offset window to start earlier than the first configuration; and / or the duration of the SSB measurement time may be extended by the timing offset window to end later than the first configuration.
[0171] In an embodiment of the present disclosure, the duration of the SSB measurement time may be shifted by the timing offset window to start earlier than the first configuration; or, the duration of the SSB measurement time may be shifted by the timing offset window to end later than the first configuration.
[0172] In an embodiment of the present disclosure, the timing offset window may be constant; or the timing offset window may be changed periodically at an update rate.
[0173] In an embodiment of the present disclosure, the second configuration may be enabled or disabled based at least on an instruction from a network node, and / or a report from a wireless device, and / or a predefined rule.
[0174] In an embodiment of the present disclosure, the second configuration may be determined based on at least the first configuration.
[0175] In an embodiment of the present disclosure, the second configuration may be determined by the wireless device and / or by a network node providing service to the wireless device based at least on measurements of SSBs and / or cells.
[0176] In an embodiment of the present disclosure, the second configuration may be determined based at least on the location of the wireless device.
[0177] In an embodiment of the present disclosure, the second configuration may include a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
[0178] In an embodiment of the present disclosure, the first configuration may include at least a first SSB measurement time and a second SSB measurement time; and the second configuration may include at least a first timing offset window for a first duration of the first SSB measurement time and a second timing offset window for a second duration of the second SSB measurement time.
[0179] In an embodiment of the present disclosure, when the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window may be disabled.
[0180] In an embodiment of the present disclosure, it may be determined whether the first timing offset window or the second timing offset window is disabled based on the priority of the first timing offset window and / or the priority of the second timing offset window.
[0181] In an embodiment of the present disclosure, the first configuration and the second configuration may be provided to the wireless device from a satellite; and the second configuration may be determined based on at least a location of the wireless device, ephemeris data of the satellite, and / or a feeder link delay.
[0182] In an embodiment of the present disclosure, the second configuration may be enabled or disabled for the wireless device based on a change in at least one of the following: validity or invalidity of ephemeris data, validity or invalidity of the location of the wireless device, the type of satellite, the location of at least one neighboring satellite, or the time to be covered by at least one neighboring satellite. Alternatively, the second configuration may be enabled or disabled for the wireless device based on at least one of the following: capabilities of the wireless device; or the first configuration.
[0183] In an embodiment of the present disclosure, the measurement process and requirement for measuring the SSB during the SSB measurement time may be based on the first configuration and / or the second configuration.
[0184] In an embodiment of the present disclosure, the requirements for measuring SSB may include at least one of the following: measurement time, measurement accuracy, the number of identified cells to be measured per carrier, and / or the number of beams to be measured.
[0185] In an embodiment of the present disclosure, scheduling restrictions may be applied to the SSB measurement time based on the first configuration and / or the second configuration.
[0186] In an embodiment of the present disclosure, when the duration of the SSB measurement time is close to or conflicts with the paging occasion, the duration and / or the second configuration may be disabled.
[0187] In an embodiment of the present disclosure, the first configuration and the second configuration may be transmitted to a plurality of wireless devices including a wireless device through broadcasting. Alternatively, the first configuration and the second configuration may be transmitted to the wireless device through a dedicated message.
[0188] In an embodiment of the present disclosure, the network node may include a satellite or a base station relayed by a satellite.
[0189] In an embodiment of the present disclosure, the wireless device may be in an idle mode, or an inactive mode, or a connected mode.
[0190] Figure 4 is a diagram showing an example of a signaling flow between a network node and a UE. The network node (e.g., BS11, satellite 12) shall provide a STOW configuration (second configuration) together with an existing measurement configuration (SMTC) to a UE (e.g., (wireless) device 2). The STOW configuration may include parameters {r1, tr1, s1}, or an exact one or more of the parameter sets {r1, tr1, s1}, {r2, tr2, s2}. More examples regarding specific r1, tr1, s1, etc. will be described below.
[0191] Furthermore, the network node may enable or disable the use of STOW. This may be done through explicit signaling, or through a null STOW configuration or setting the STOW duration (eg r1)=0 in RRC signaling.
[0192] For the movement of the target satellite, the network can update the STOW configuration by sending a new configuration again, or the network can provide multiple parameter sets {r1, tr1, s1}, {r2, tr2, s2} in the previous STOW configuration for the UE to select appropriate parameters to perform the STOW update by the UE itself if the UE determines that it is necessary.
[0193] According to an embodiment of the present disclosure, a network (e.g., a gNB) provides a SMTC for a UE, optionally associated with one or more neighboring cells. The configuration may include an SMTC timing offset window (STOW), and may also optionally include rules for how the STOW should be defined and updated to adapt to the effects of satellite movement in a predictable manner, which allows the UE and the network (e.g., a gNB) to remain synchronized in terms of the timing of the STOW, regardless of whether there is further signaling between the UE and the network.
[0194] According to a further embodiment of the present disclosure, each UE may report an SMTC timing offset window when performing measurements. Thereafter, the NW will provide the UE with a specific SMTC and STOW for each UE. Alternatively, the NW will provide the UE with an SMTC and STOW that is a collection of timing offset windows reported by all UEs in each cell.
[0195] According to a further embodiment of the present disclosure, the window constant duration of the STOW for SMTC is associated with the SMTC duration, SMTC periodicity and SMTC offset according to a predefined rule, a configuration of the network or a report of the UE.
[0196] According to a further embodiment of the present disclosure, the constant duration of the window of STOW for SMTC is associated with the cell / SSB-ID and / or satellite ID according to a predefined rule or a configuration of the network.
[0197] According to a further embodiment of the present disclosure, the window constant duration of the STOW for the SMTC can be changed periodically at a constant update rate.
[0198] According to a further embodiment of the present disclosure, the window variable duration of the STOW of the SMTC is associated with the SMTC duration, SMTC periodicity and SMTC offset according to a predefined rule or a configuration of the network or a report of the UE.
[0199] According to a further embodiment of the present disclosure, the variable duration of the window of the STOW of the SMTC is associated with the Cell / SSB-ID and / or the satellite ID according to a predefined rule or a configuration of the network.
[0200] According to a further embodiment of the present disclosure, the window variable duration of the STOW of the SMTC is periodically changed at a constant update rate.
[0201] According to a further embodiment of the present disclosure, if there are multiple SMTCs, multiple STOWs with associated variable window durations are configured with corresponding SMTC windows.
[0202] According to a further embodiment of the present disclosure, if multiple SMTCs overlap, the window variable duration of the STOW is configured with a corresponding collection of the overlapping SMTC windows.
[0203] According to a further embodiment of the present invention, in some configuration aspects of multiple SMTCs and associated STOWs, scheduling restrictions are imposed on symbols that can be used to send PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS (tracking reference signal) / CSI-RS for CQI (channel quality indication).
[0204] According to a further embodiment of the present disclosure, the network indicates to the UE whether to enable or disable STOW on all or part of the SMTCs and the configured constant duration of the STOW window. Symbols that do not need to occupy STOW can be used for other purposes.
[0205] According to a further embodiment of the present disclosure, the UE indicates to the network whether to enable or disable STOW on all or part of the SMTCs and the configured constant duration of the STOW window. Symbols that do not need to occupy STOW can be used for other purposes.
[0206] The network (e.g., gNB) preferably enables dynamic SMTC and / or measurement gap configuration to be based on knowledge of the UE's location and the ephemeris data and feeder link latency of the satellites serving the cell targeted by the configuration (e.g., the cell associated with the configuration).
[0207] To ensure that the configuration remains valid, the network may configure the UE to report its location when it moves more than a configured maximum distance from the location where the UE received the configuration. Alternatively, or in addition, the UE may be triggered to signal its location to the network when it detects that the configured SMTC window and / or measurement gap no longer completely covers the SSB transmissions of the relevant neighboring cell (as received by the UE). These mechanisms allow the network to provide a new configuration to the UE before the UE's movement results in the relevant SSB transmissions not being completely covered by the configured SMTC window and / or measurement gap (as seen by the UE).
[0208] Furthermore, some of the embodiment examples listed above are inherently limited in validity time, as they each contain a finite list of pre-configured updates that apply at a particular time.
[0209] In addition, the configuration in other embodiments may also be associated with a limited validity time, for example, by including an indication of the validity time in the configuration, i.e., the period of time for which the configuration is valid (or this validity time may be specified in the standard). When the configuration is no longer valid, the network preferably provides a new configuration to the UE.
[0210] According to an embodiment of the present disclosure, the proposed solution provides enhancement in the trade-off between flexibility and efficiency, as well as clear details or methods regarding the implementation of SMTC configuration, especially regarding STOW.
[0211] Further detailed application of the embodiments of the present disclosure in a scenario including a satellite will be described.
[0212] In this disclosure, the term "satellite" is often used even if a more appropriate term is "gNB associated with a satellite". The term "satellite" may also be referred to as a satellite node, an NTN node, a node in space, etc. Here, a gNB associated with a satellite may include a regenerative satellite (where the gNB is a satellite payload, i.e., the gNB is integrated with the satellite) or a transparent satellite (where the satellite payload is a relay and the gNB is on the ground (i.e., the satellite relays communications between the gNB on the ground and the UE)).
[0213] The period or duration of time that a UE can remain connected, camp on, or maintain communication with a satellite or gNB, etc. is referred to as the term "coverage time" or "service time" or "network availability" or "sojourn time" or "dwell time", etc. The term "non-coverage time", also known as "non-service time" or "network unavailability", or "non-dwell time" or "non-dwell time", refers to the period of time when the satellite or gNB is unable to serve, communicate, or provide coverage to the UE. Another way to explain availability is that it is not about the satellite / network being strictly unable to serve the UE due to lack of coverage, but rather that the UE does not need to measure certain "cells that are unlikely to be served (by the satellite that broadcasts the serving cell)". In this case, the terminology may still be like the no coverage case, or it may be different, such as "no measurement required".
[0214] The term node used may be a network node or a user equipment (UE). Examples of network nodes include NodeB, base station (BS), multi-standard radio (MSR) radio node (e.g., MSR BS, eNodeB, gNodeB, MeNB, SeNB), location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), central unit (e.g., in gNB), distributed unit (e.g., in gNB), baseband unit, centralized baseband, C-RAN, access point (AP), transmission point, transmission node, transmission reception point (TRP), RRU, RRH, node in distributed antenna system (DAS), core network node (e.g., MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g., E-SMLC), etc.
[0215] The non-limiting term UE refers to any type of wireless device that communicates with a network node and / or another UE in a cellular or mobile communication system. Examples of UE include a target device, a device-to-device (D2D) UE, a vehicle-to-vehicle (V2V), a machine type UE, an MTC UE or a UE supporting machine-to-machine (M2M) communication, a PDA, a tablet, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, etc.
[0216] The term radio access technology or RAT may refer to any RAT, such as UTRA, E-UTRA, Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT, New Radio (NR), 4G, 5G, NR NTN, IoT NTN, LTE NTN, etc. Any device denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.
[0217] The term signal or radio signal used in this article can be any physical signal or physical channel. Examples of DL physical signals are reference signals (RS), such as PSS, SSS, CSI-RS, DMRS signals in SS / PBCH blocks (SSBs), discovery reference signals (DRS), CRS, PRS, etc. RS can be periodic, for example, RS opportunities carrying one or more RSs may occur at a certain period, such as 20ms, 40ms, etc. RS can also be non-periodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 consecutive symbols. One or more SSBs are transmitted in an SSB burst that repeats at a certain period, such as 5ms, 10ms, 20ms, 40ms, 80ms and 160ms. The UE is configured with information about SSBs on a cell of a certain carrier frequency through one or more SS / PBCH block measurement timing configuration (SMTC) configurations. SMTC configurations include parameters such as SMTC period, time length or duration of SMTC opportunity, and SMTC time offset relative to a reference time (e.g., SFN of a serving cell). Therefore, SMTC opportunities may also occur with a certain period, such as 5ms, 10ms, 20ms, 40ms, 80ms and 160ms. Examples of UL physical signals are reference signals, such as SRS, DMRS, etc. The term physical channel refers to any channel that carries higher layer information (such as data, control, etc.). Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPUCCH, sPDSCH, sPUCCH, sPUSCH, MPDCCH, NPDCCH, NPDSCH, E-PDCCH, PUSCH, PUCCH, NPUSCH, etc.
[0218] Figure 5A is a diagram illustrating multiple SMTCs that a network node signals to a wireless device.
[0219] As shown in the example scenario, by introducing different new offsets, multiple SMTC / MG (measurement gap) configurations can be enabled. Figure 5A As shown, in one opportunity of NW broadcasting, there are a total of 4 SMTCs per MO (measurement object) or per frequency layer, of which SMTC#1 and SMTC#4 do not overlap, and SMTC#2 and SMTC#3 partially overlap due to different offsets.
[0220] SMTC#1, SMTC#2, SMTC#3, and SMTC#4 may indicate indexes of multiple SMTCs configured by the NW, which may also be referred to as exact RRC IE parameters.
[0221] Figure 5B is a diagram showing a 4 ms SMTC window.
[0222] The UE receives the configuration and applies the pre-configured updates according to the received configuration. Such SMTC window configuration may be referred to as a dynamic SMTC window configuration or a dynamic SMTC.
[0223] For example, the UE may be configured with a SMTC configuration per cell list: this is present in TS 38.331 version 17.4.0, up to 4 different SMTC periodicities may be enabled and the durations remain as {sf1,sf2,sf3,sf4,sf5}.
[0224] SSB-MTC3List-r16::= SEQUENCE(SIZE(1..4))OF SSB-MTC3-r16
[0225] SSB-MTC3-r16::= SEQUENCE{
[0226] periodicityAndOffset-r16 CHOICE{
[0227]
[0228] The proposed solution may include the network (e.g. gNB) providing the UE with an SMTC optionally associated with one or more neighboring cells, wherein the configuration includes the SMTC timing offset window (STOW), and also includes rules for how the STOW should be defined and updated to adapt to the effects of satellite movement in a predictable manner, which allows the UE to configure the STOW accordingly. The UE and the network (e.g. gNB) should remain synchronized in terms of the timing of the STOW, regardless of whether there is further signaling between the UE and the network.
[0229] Figure 5C is a diagram showing the offset of SMTC configuration. The network can configure the SMTC window based on an estimate of the propagation delay to the cell or UE, but not all UEs can accurately receive the SSB burst within the SMTC window. Figure 5C An example is shown in FIG. 1 , where SMTC is the same for UE1, UE2, and UE3. UE1 can receive SSB at the precise SMTC position, UE2's SMTC is a little earlier than the actual SSB arrival time, and UE3's SMTC is a little later than the actual SSB arrival time.
[0230] To alleviate this problem, the SMTC Timing Offset Window (STOW) is defined together with the SMTC duration to extend / shift the actual reception timing of the UE while reducing the impact on scheduling. According to the existing SMTC definition, STOW provides the UE with the possibility to perform measurements outside the SMTC duration configured by the network, which can be enabled or disabled. The enabling and disabling mechanism can be indicated by the NW or reported by the UE or based on predefined rules. In terms of the configuration of multiple SMTCs and associated STOWs, scheduling restrictions are imposed on the assignment of symbols that can be used to send PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS / CSI-RS for CQI. STOW may be located on both sides of the SMTC duration.
[0231] Figure 5D is a diagram depicting an example of STOW on both sides of the SMTC duration. If STOW is disabled, it will fall back to the existing SMTC. In contrast, if STOW is enabled, the UE should measure the SSB burst before and / or after the SMTC duration depending on the implementation of the UE itself, but if STOW is not specified, completely free search is allowed without any restrictions or rules are ambiguous. One of the advantages is that the network can configure STOW or set rules to configure STOW for each UE for different criteria, with implementation flexibility. Another advantage is that the network and UE have the same understanding of the STOW configuration, and scheduling restrictions can be less compared to a fixed SMTC with a longer duration.
[0232] In one specific example, STOW may be configured with a list of time shifts before and after SMTC, such as {0, 1, 2} symbols.
[0233] In another specific example, STOW may be configured with a list of N time shifts before and after SMTC, such as {0,1,2}μs. Scheduling constraints will be applied to symbols as an upper limit (N / NR symbol length).
[0234] In another specific example, STOW can be configured with one or two dedicated values {N1, N2} in a time shift list such as {-2, -1, 0, 1, 2} symbols. Wherein, if the STOW duration is before the SMTC, N is less than 0. If the STOW duration is after the SMTC, N is greater than 0. If the NW wants to configure STOW on both sides, the NW can configure N1 and N2.
[0235] As an option, when applicable, the network shall provide multiple dynamic SMTCs and / or measurement gap configurations for the UE, where each SMTC and / or measurement gap configuration is associated with a group of UEs or a group of cells served by the same satellite. In this case, the network can configure a reference SMTC corresponding to the shortest or longest propagation to the serving cell center or cell edge, and then the UE's STOW can be set to one side (left or right), which means that the propagation delay from the satellite to the UE is longer or shorter than the reference SMTC.
[0236] Figure 5E is a diagram depicting an example of STOW on one side of the SMTC duration. Figure 5E One aspect of the STOW shown in is that the STOW is not always located on both sides of the duration of the SMTC, and the one-sided STOW can also be used to extend the reception capability of a one-way UE.
[0237] As an option, the network can configure STOW for SMTC based on ephemeris data, UE position and UE feedback. The network may know that it does not need to keep one side of the SMTC duration as usual, and can cut off the same length of the duration of one side when STOW extends the duration of the other side.
[0238] Fig. 5F is a diagram showing a time-shifted STOW. Fig. 5F As shown, one aspect of STOW is that STOW is not always used to extend the duration of SMTC. A time-shifted STOW can also be used to shift the SMTC and keep the original duration length of the SMTC unchanged.
[0239] Figure 5G It is shown that the STOW concept is used to solve Figure 5C Graph of the problem in Figure 1. Therefore, Figure 5C The problem in can be solved by the STOW concept, such as Figure 5G As shown in the figure, once UE2 and UE3 are patched by the time-shifted STOW, it means that UE2 and UE3 can use the time in the STOW to make more measurements on the actual SSB. No part will be missed during the measurement.
[0240] Figure 5His a diagram showing exemplary parameters in a STOW configuration. Another aspect of STOW is that the range / duration / length of a STOW can be one or more symbols. In one example, a parameter may include a predefined list of range / duration / length of a STOW {r1, r2, r3...}, such as Figure 5H As shown. In addition, the selection among {r1, r2, r3...} can vary over time with respect to another parameter, which includes a predefined list of time durations {tr1, tr2, tr3...}. For example, r1 is valid for a predefined time duration tr1, r2 is valid for a predefined time duration tr2, and so on. In one example, the total time of tr1+tr2+tr3... may be less than the SMTC period.
[0241] From another perspective, r1, r2, r3... indicate the shift level allowed by SMTC. From another perspective, r1, r2, r3... and the corresponding valid time tr1, tr2, tr3... indicate the allowed shift rate of SMTC. In one example, other parameters s1=r1 / tr1, s2=r2 / tr2, s3=r3 / tr3 directly indicate the shift rate of SMTC. For example, {r1, r2, r3...}, {tr1, tr2, tr3...}, {s1, s2, s3...} can be predefined, configured by the network or determined by the UE.
[0242] One example is that the range of STOW should be related to the duration of SMTC {td1, td2, td3, ...}, for example, if the duration of SMTC is Td1, the allowed STOW should be r1. If the duration of SMTC is Td2, the allowed STOW should be r2.
[0243] Another example related to the scope of the STOW is that, based on the location of the UE and knowledge of the ephemeris data and feeder link delay of the satellite serving the cell targeted by the configuration (e.g., the cell associated with the configuration), the network can indicate a reference STOW to the UE instead of setting the rules for the duration of the STOW as described above. If the network does not have sufficiently recent or accurate information about the location of the UE when the configuration is to be created, the network can request the UE to signal the location of the UE to the network.
[0244] As an option, the STOW duration associated with a set of cells and SMTC configurations can be selectively associated with the configuration of the cell / SSB-ID and / or satellite ID. An example is as follows. If the cell / SSB-ID and / or satellite ID belongs to set 1 (ID1, ID2...), the allowed STOW parameters should be {r1, tr1, s1}. If the cell / SSB-ID and / or satellite ID belongs to set 2 (ID1, ID2...), the allowed STOW should be {r2, tr2, s2}, and so on.
[0245] The extended range of STOW duration allows the network (e.g., gNB) to configure some additional margin in the window. Therefore, the time of reception of SSB transmissions can "slide" within the STOW for a period of time due to satellite movement before the range of the STOW must be updated / moved / switched. If the {r1, r2} of the STOW does not cover the propagation delay variation, the SMTC duration can be changed from Td1 to Td2, etc., and the STOW should be updated according to the above embodiment.
[0246] Another possibility of this embodiment is that STOW may face a specific situation in the case of multiple SMTCs. STOW examples can also be applied to this multi-SMTC situation.
[0247] Fig.5I is a diagram showing exemplary multiple STOWs for multiple SMTCs.
[0248] by Fig.5I For example, in case 1, STOW1 of SMTC1 and STOW2 of SMTC2 do not overlap yet (there may be a partial conflict or they are close in time (for example, within a certain time margin), but they do not overlap in time). In case 2, STOW1 and STOW2 overlap, but SMTC1 and SMTC2 do not overlap (there may be a partial conflict or they are close in time (for example, within a certain time margin), but they do not overlap in time). In case 3, SMTC1 and SMTC2 overlap.
[0249] If the UE cannot measure the overlapping SMTCs at the same time, the network or the UE determines which of the two overlapping SMTC+STOW to retain and which of the two overlapping SMTCs to cancel.
[0250] There are some solutions to solve this problem, for example, at one time, STOW1 is used for SMTC1 and SMTC2 without STOW2 is measured. At another time, STOW2 is used for SMTC2 and SMT1 without STOW1 is measured. Alternatively, one of the STOWs can always be prioritized, such as STOW1 for SMTC1, and SMTC2 without STOW2 is measured. The specific priority can be based on the different characteristics or configurations of SMTC1 and SMTC2. In addition, a shorter STOW1 and / or STOW2 can be configured to avoid conflicts.
[0251] The difference between scenario 1 with STOW disabled and scenario 2 with STOW enabled may be related to parameters such as validity or invalidity of ephemeris data; validity or invalidity of UE position; satellite type; position of some neighboring satellites; time of coverage area of some neighboring satellites; capability of UE; SMTC configuration.
[0252] Figure 6 is a diagram showing switching between different scenes. Figure 6 As shown, the switch between scenario 1 with STOW disabled and scenario 2 with STOW enabled can be signaled by the network through explicit signaling. Alternatively, the switch can be implicitly / automatically triggered based on the change or update of the above parameters. To allow the network and UE to keep in sync on STOW validity and configuration, explicit signaling by the network is preferred. In addition, the assistance of the UE can support the network to configure the appropriate STOW for the UE.
[0253] In one example, the network configures one of the SMTCs with STOW for GEO and LEO. After the coverage of LEO expires, the network can update the SMTC without STOW to be reserved only for GEO.
[0254] In another example, when the UE cannot identify the SSB or detects a low signal strength / quality SSB in the SMTC without STOW, the UE may request a STOW from the network.
[0255] In another example, when the validity time of the SMTC without STOW expires, the UE may request a STOW from the network.
[0256] In another example, when the UE has invalid Global Navigation Satellite System (GNSS) location information, the UE may request a STOW from the network.
[0257] In another example, if the network is configured with only one SMTC, the network may enable STOW to ensure high robustness of the unique SMTC.
[0258] Alternatively, the UE may switch between scenario 1 in which STOW is disabled and scenario 2 in which STOW is enabled according to the change or update of the above parameters. To allow the network and the UE to be synchronized on STOW validity and configuration, the UE notifies the NW to enable or disable STOW and / or detailed STOW parameters, such as r1, r2, r3. In addition, the NW may provide UE assistance information to facilitate the UE to configure appropriate STOW.
[0259] In one example, the network configures one SMTC for GEO and LEO with STOW. After LEO's coverage expires, the UE may only perform SMTC without STOW to reserve only for GEO.
[0260] In another example, when the UE cannot identify the SSB or detects a low signal strength / quality SSB in the SMTC without STOW, the UE may perform STOW and notify the network to enable or disable STOW and / or detailed STOW parameters, such as r1, r2, r3.
[0261] In another example, if the SMTC validity time without STOW expires, the UE may perform STOW.
[0262] In another example, if the UE has invalid GNSS location information, the UE may perform STOW.
[0263] In another example, if the network configures only one SMTC, the UE may enable STOW to ensure high robustness of the unique SMTC.
[0264] like Figure 6 As shown in Figure 1, switching between scenario 1 with STOW disabled and scenario 2 with STOW enabled requires transition time, and also requires updating the parameters of STOW, such as {r1, r2, r3…} and {tr1, tr2, tr3…} or {s1, s2, s3…}. When only STOW is updated, transition time is also required.
[0265] When the UE switches between any two scenarios when STOW is enabled, STOW configuration is changed, or STOW is disabled, the UE shall abandon the measurement of the first (previous) scenario and is not expected to meet any measurement requirements. After the transition time interval, the UE must restart the measurement and meet the requirements corresponding to the second (new) state.
[0266] Another aspect of this embodiment is a set of measurement procedures and requirements, including P2 applied to the UE when STOW is enabled; and P1 applied to the UE when STOW is disabled. P1 or P2 can be used for L1-RSRP and / or SS-RSRP. In addition, depending on the duration of STOW {r1, r2}, there can be two different measurement procedures and requirements, such as P2-1 and P2-2.
[0267] Examples of requirements for the measurement process and requirements include measurement time, measurement accuracy, the number of identified cells to be measured per carrier, the number of beams (e.g., SSBs) to be measured, etc. Examples of measurement time are cell detection time, measurement period of measurement (e.g., synchronization signal reference signal received power (SS-RSRP), SS reference signal received quality (SS-RSRQ), SS signal interference and noise ratio (SS-SINR), etc.), SSB index acquisition time, measurement report delay, radio link monitoring (RLM) assessment period (e.g., desynchronization assessment period, synchronization assessment period, beam detection assessment period, candidate beam detection assessment period, measurement period of L1 measurement (e.g., L1-RSRP, L1-SINR, etc.), the number of SMTCs in one MO (measurement object) / frequency layer, the number of carriers / frequencies / cells to be measured, etc.
[0268] For example, the P2 requirement may be stricter than the P1 requirement. In addition, in P2, there may be P2-1 (corresponding to parameter r1), P2-2 (corresponding to parameter r2), and P2-3. When r2>r1, the P2-2 requirement may be stricter than the P2-1 requirement. The term "strict" may be interchangeably referred to as stricter, less lenient, tighter, more demanding, more difficult, etc.
[0269] Table 2: Measurement requirements
[0270]
[0271] To meet or satisfy more stringent requirements, the UE needs to allocate or assign more resources to perform and process measurements compared to the case where the UE has to meet less stringent requirements. Examples of resources include processor units, memory units, battery power, etc. Examples of requirements include measurement time, measurement rate, measurement accuracy for measurements such as SS-RSRQ, SS-RSRP, etc., the number of cells to be measured within the measurement time, the number of carriers to be monitored, signal levels such as SINR, SS-RSRP, etc., and other limitations that the requirements need to satisfy. Examples of measurement time include measurement period or L1 measurement period, evaluation period, cell detection time, etc. In one example, a shorter measurement time is more stringent (or less lenient) than a longer measurement time for the same type of measurement (e.g., measurement of SS-RSRP). In another example, a shorter cell detection time is more stringent than a longer cell detection time for the same type of cell (e.g., NR inter-frequency cell).
[0272] The differences between P1 and P2 are described by several examples below.
[0273] In P2, the UE measures on more beams (e.g., SSB) than in P1, or measures in the opposite manner or direction.
[0274] In P2, the UE performs measurements on one or more adjacent cells (or carriers, frequencies) faster than in P1. In one example, the UE measures fewer adjacent cells than in P1 in the opposite manner or direction.
[0275] In P2, the UE is allowed to perform measurements according to one or more of the following operation modes: The UE performs measurements while meeting shorter or longer requirements, e.g., the measurement time (Tms) is shorter or longer than the reference measurement time (Tmr), e.g., when Tms < Tmr or Tms > Tmr. In one example, K * Tms = Tmr; where K > 1. In another example, Tms = 400 ms, while for the same measurement (e.g., for SS-RSRP), Tmr = 1600 ms.
[0276] In addition, when using STOW in the RRC_CONNECTED (RRC - connected) state, one aspect is regarding the scheduling restrictions for STOW. In some cases, the scheduling restrictions should be applied to SSB symbols. For example, the UE is not expected to send PUCCH / PUSCH / SRS or receive PDSCH / PDCCH / TRS / CSI-RS for CQI on the SSB symbols to be measured, or on some symbols before and after each consecutive SSB symbol to be measured (possibly in SMTC or STOW) or on all symbols within the SMTC + STOW window duration.
[0277] Back to Fig.5I , in case 1, STOW1 of SMTC1 and STOW2 of SMTC2 do not overlap. Scheduling restrictions should be applied to each SMTC and STOW.
[0278] In case 2, when STOW1 and STOW2 overlap but SMTC1 and SMTC2 do not overlap, scheduling constraints should be applied to each SMTC and the set of STOWs between STOW1 and STOW2.
[0279] In case 3, when SMTC1 and SMTC2 overlap, scheduling restrictions should be applied to the set of SMTCs and STOW1 before SMTC1 and STOW2 after SMTC2.
[0280] When STOW is used in RRC_IDLE / INACTIVATED state, one aspect is that paging occasions should not be occupied by STOW.
[0281] One example is that STOW should be limited to avoid being too close to or colliding with a paging occasion.
[0282] Another example is that SMTCs with STOW that are too close to or conflict with paging occasions should be discarded to ensure paging activity and expect longer measurement delays.
[0283] Fig. 7A is a block diagram illustrating an exemplary apparatus for a network node suitable for executing a method according to an embodiment of the present disclosure.
[0284] like Fig. 7A As shown, the apparatus 10 for a network node in a communication network may include: a processor 101; and a memory 102. The memory contains instructions executable by the processor. The apparatus 10 for a network node is used to: determine a first configuration for an SSB measurement time; wherein SSB refers to a combination of a synchronization signal and a physical broadcast channel; determine a second configuration for indicating an offset related to the SSB measurement time; and send the first configuration and the second configuration to a wireless device, for instructing the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration.
[0285] In an embodiment of the present disclosure, the apparatus 10 is also used to execute the method according to any of the above embodiments, for example Figure 2 , 4 As shown in .
[0286] Figure 7B is a block diagram illustrating an exemplary apparatus for a wireless device, which is suitable for performing a method according to an embodiment of the present disclosure.
[0287] like Figure 7BAs shown, the apparatus 20 for a wireless device may include: a processor 201; and a memory 202. The memory contains instructions executable by the processor. The apparatus 20 for a wireless device is used to: receive a first configuration and a second configuration from a network node in a communication network; and perform SSB measurement based on at least the first configuration and / or the second configuration. The first configuration is used for SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time.
[0288] In the embodiments of the present disclosure, the apparatus 20 may also be used to execute the method according to any of the above embodiments, for example Figure 3 , 4 As shown in .
[0289] The processor 101, 201 may be any type of processing component, such as one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The memory 102, 202 may be any type of storage component, such as a read-only memory (ROM), a random access memory, a cache, a flash memory device, an optical storage device, etc.
[0290] Figure 8 is a block diagram illustrating a device / computer-readable storage medium according to an embodiment of the present disclosure.
[0291] like Figure 8 As shown, a computer-readable storage medium 80 or any other type of product stores instructions 801, and when the instructions 801 are executed by at least one processor, the at least one processor performs a method according to any of the above embodiments, for example Figure 2 , 3 , as shown in 4.
[0292] In addition, the present disclosure may also provide a carrier containing the computer program / instructions as described above, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disk or an electronic storage device, such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.
[0293] Fig. 9A is a schematic diagram showing units of an exemplary apparatus for a network node according to an embodiment of the present disclosure.
[0294] like Fig. 9AAs shown, an apparatus 10 for a network node may include: a first determination unit 12, configured to determine a first configuration for an SSB measurement time; wherein SSB refers to a combination of a synchronization signal and a physical broadcast channel; a second determination unit 14, configured to determine a second configuration for indicating an offset associated with the SSB measurement time; and a sending unit 16, configured to send the first configuration and the second configuration to a wireless device, for instructing the wireless device to perform SSB measurement based at least on the first configuration and / or the second configuration.
[0295] In the embodiments of the present disclosure, the device 10 may also execute the method according to any of the above embodiments, for example: Figure 2 , 4 As shown in .
[0296] Fig. 9B is a block diagram illustrating an exemplary apparatus for a second network node, which is suitable for performing the method according to an embodiment of the present disclosure.
[0297] like Fig. 9B As shown, an apparatus 20 for a second network node in a second communication network may include: a receiving unit 22, which is configured to receive a first configuration and a second configuration from a network node in the communication network; and an execution unit 24, which is configured to perform SSB measurement based on at least the first configuration and / or the second configuration. The first configuration is used for SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time.
[0298] In an embodiment of the present disclosure, the device 20 may also be operable to execute the method according to any of the above embodiments, for example Figure 3 , 4 As shown in .
[0299] The term "unit" may have its conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or distributed devices, computer programs or instructions for performing various tasks, processes, calculations, output and / or display functions, etc., such as those described herein.
[0300] By using these units, the device may not need a fixed processor or memory, and any computing resources and storage resources may be arranged from at least one network node / device / entity / device related to the communication system. Virtualization technology and network computing technology (such as cloud computing) may be further introduced to improve the efficiency of network resource utilization and network flexibility.
[0301] The techniques described herein may be implemented by various means, such that the device implementing one or more functions of the corresponding device described in the embodiment includes not only prior art components, but also components for implementing one or more functions of the corresponding device described in the embodiment, and may include separate components for each separate function, or may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, it may be implemented by modules (e.g., processes, functions, etc.) that perform the functions described herein.
[0302] In particular, these functional units may be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform (eg, a cloud infrastructure).
[0303] Fig.10 An example of a communication system 1000 is shown in accordance with some embodiments.
[0304] In this example, the communication system 1000 includes a telecommunications network 1002 including an access network 1004 such as a radio access network (RAN) and a core network 1006 including one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. The network node 1010 facilitates direct or indirect connection of user equipment (UE), such as by connecting UE 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UE 1012) to the core network 1006 via one or more wireless connections.
[0305] Example wireless communications over wireless connections include sending 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. Additionally, in various embodiments, the communication system 1000 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 or not via a wired or wireless connection. The communication system 1000 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.
[0306] UE 1012 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 1010 and other communication devices. Similarly, network node 1010 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1012 and / or with other network nodes or devices in telecommunication network 1002 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management in telecommunication network 1002.
[0307] In the depicted example, the core network 1006 connects the network node 1010 to one or more hosts, such as the host 1016. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1006 includes another core network node (e.g., core network node 1008) consisting of hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, network node, and / or host, so that the description is generally applicable to the corresponding components of the core network node 1008. The example core network node includes a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF) One or more functions.
[0308] The host 1016 may be under the ownership or control of a service provider other than the operator or provider of the access network 1004 and / or the telecommunications network 1002, and may be operated by or on behalf of the service provider. The host 1016 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions of an alarm and monitoring center, or any other such functions performed by a server.
[0309] on the whole, Fig.10The communication system 1000 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but 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 standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standards, such as 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.
[0310] In some examples, the telecommunication network 1002 is a cellular network implementing 3GPP standardized features. Therefore, the telecommunication network 1002 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 1002. For example, the telecommunication network 1002 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine type communication (mMTC) / massive IoT services to more UEs.
[0311] In some examples, UE 1012 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1004 on a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1004. In addition, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).
[0312] In this example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and / or 1012d) and a network node (e.g., network node 1010b). In some examples, the hub 1014 may be a controller, a router, a content source, and an analyzer, or any other communication device described herein with respect to the UE. For example, the hub 1014 may be a broadband router that enables the UE to access the core network 1006. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1010, or received by an executable code, a script, a process, or other instructions in the hub 1014. As another example, the hub 1014 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1014 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and the hub 1014 then provides it to the UE directly or after performing local processing and / or after adding additional local content. In another example, the hub 1014 acts as a proxy server or orchestrator for the UE, especially when one or more UEs are low-energy IoT devices.
[0313] Hub 1014 can have constant / persistent or intermittent connection to network node 1010b. Hub 1014 can also allow different communication schemes and / or scheduling between hub 1014 and UE (e.g., UE 1012c and / or 1012d) and hub 1014 and core network 1006. In other examples, hub 1014 is connected to core network 1006 and / or one or more UE via wired connection. In addition, hub 1014 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 1004. In some scenarios, UE can establish wireless connection with network node 1010, while still connected via hub 1014 via wired or wireless connection. In some embodiments, hub 1014 can be a dedicated hub-that is, its main function is to route the communication from network node 1010b to UE / route the communication from UE to network node 1010b. In other embodiments, the hub 1014 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 1010b, but which is also operable as a communications start and / or end point for certain data channels.
[0314] Fig.11 UE 1100 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.
[0315] The UE may support device-to-device (D2D) communications, such as by implementing 3GPP standards for sidelink communications, dedicated short-range communications (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 owning and / or operating the associated device. Instead, a UE may represent a device that is intended to be sold to or operated by a human user but may not, or may not initially, be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0316] UE 1100 includes processing circuitry 1102, which is operatively coupled to input / output interface 1106, power supply 1108, memory 1110, communication interface 1112, and / or any other components or any combination thereof via bus 1104. Some UEs may utilize Fig.11 All or a subset of the components shown. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0317] The processing circuit 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1110 as a machine-readable computer program. The processing circuit 1102 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 and appropriate firmware; one or more stored computer programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 1102 may include multiple central processing units (CPUs).
[0318] In this example, the input / output interface 1106 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1100. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, directional boards, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, 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 can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.
[0319] In some embodiments, the power supply 1108 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1108 may also include a power circuit for delivering power from the power supply 1108 itself and / or an external power supply to various parts of the UE 1100 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, for charging the power supply 1108. The power circuit may perform any formatting, conversion, or other modification to the power from the power supply 1108 so that the power is suitable for the various components of the UE 1100 to which it is powered.
[0320] The memory 1110 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 1110 includes one or more application programs 1114, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1116. The memory 1110 may store any of a variety of operating systems or a combination of operating systems for use by the UE 1100.
[0321] The memory 1110 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, a built-in hard disk drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more user identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a “SIM card”. The memory 1110 may allow the UE 1100 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1110 , which may be or include a device-readable storage medium.
[0322] The processing circuit 1102 may be configured to communicate with an access network or other network using a communication interface 1112. The communication interface 1112 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 may include one or more transceivers for communication, 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 1118 and / or a receiver 1120 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1118 and the receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software, or firmware, or may be implemented separately alternatively.
[0323] In the illustrated embodiment, the communication functionality of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication (e.g., using a global positioning system (GPS) to determine location), another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards (e.g., IEEE 802.11, code division multiple 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 network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.).
[0324] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 1112. The data captured by the UE's sensor may be transmitted to the network node via another UE via a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to balance the load of reports from multiple sensors), in response to a trigger event (e.g., sending an alert when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0325] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.
[0326] When in the form of an Internet of Things (IoT) device, a UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are or are embedded in: a connected refrigerator or freezer, a television, connected lighting, an electric meter, a robotic 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 / humidity sensor, an electronic door lock, a connected doorbell, an air conditioning system such as 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, an augmented reality (AR) or virtual reality (VR) head mounted display, a wearable device for tactile or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, the UE may be used to identify the user and the device in question. Fig.11 In addition to the other components depicted in the illustrated UE 1100 , a UE in the form of an IoT device may include circuitry and / or software depending on the intended application of the IoT device.
[0327] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0328] In fact, for a single use case, any number of UEs may be used together. For example, a first UE may be a drone or integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for 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 speed of the drone. The first and / or second UE may also include more than one of the above functions. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.
[0329] Fig.12A network node 1200 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications 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 Node Bs (gNBs)).
[0330] Base stations may be classified based on the amount of coverage they provide (or in other words, their transmit power level), and therefore, based on the amount of coverage provided, 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 that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0331] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device (e.g., an MSR BS), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT).
[0332] The network node 1200 includes a processing circuit 1202, a memory 1204, a communication interface 1206, and a power supply 1208. The network node 1200 may include multiple physically separated components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In certain scenarios where the network node 1200 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered to be a single separate network node in some cases. In some embodiments, the network node 1200 may be configured to support a variety of radio access technologies (RATs). In such an embodiment, some components may be duplicated (e.g., separate memories 1204 for different RATs) and some components may be reused (e.g., the same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of various components shown for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 1200. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1200.
[0333] The processing circuit 1202 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic, operable alone or in combination with other network node 1200 components (e.g., memory 1204) to provide network node 1200 functionality.
[0334] In some embodiments, the processing circuit 1202 includes a system on a chip (SOC). In some embodiments, the processing circuit 1202 includes one or more radio frequency (RF) transceiver circuits 1212 and baseband processing circuits 1214. In some embodiments, the radio frequency (RF) transceiver circuits 1212 and baseband processing circuits 1214 may be located on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of the RF transceiver circuits 1212 and baseband processing circuits 1214 may be located on the same chip or chipset, board, or unit.
[0335] The memory 1204 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, a persistent storage device, a solid-state memory, a remotely mounted memory, a magnetic medium, an optical medium, a random access memory (RAM), a read-only memory (ROM), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., 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 device that stores information, data, and / or instructions that can be used by the processing circuit 1202. The memory 1204 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 1202 and used by the network node 1200. The memory 1204 may be used to store any calculations performed by the processing circuit 1202 and / or any data received via the communication interface 1206. In some embodiments, the processing circuit 1202 and the memory 1204 are integrated.
[0336] The communication interface 1206 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1206 includes a port / terminal 1216 for sending data to the network and receiving data from the network, for example, via a wired connection. The communication interface 1206 also includes a radio front-end circuit 1218, which can be coupled to the antenna 1210, or can be a part of the antenna 1210 in some embodiments. The radio front-end circuit 1218 includes a filter 1220 and an amplifier 1222. The radio front-end circuit 1218 can be connected to the antenna 1210 and the processing circuit 1202. The radio front-end circuit can be configured to adjust the signal communicated between the antenna 1210 and the processing circuit 1202. The radio front-end circuit 1218 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1218 can use a combination of a filter 1220 and / or an amplifier 1222 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1210. Similarly, when receiving data, antenna 1210 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1218. The digital data may be passed to processing circuit 1202. In other embodiments, the communication interface may include different components and / or different combinations of components.
[0337] In some alternative embodiments, the network node 1200 does not include a separate radio front end circuit 1218, instead the processing circuit 1202 includes the radio front end circuit and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuit 1212 is part of the communication interface 1206. In yet another embodiment, the communication interface 1206 includes one or more ports or terminals 1216, the radio front end circuit 1218, and the RF transceiver circuit 1212 as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuit 1214, which is part of a digital unit (not shown).
[0338] Antenna 1210 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1210 may be coupled to radio front end circuit 1218 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1210 is separate from network node 1200 and may be connected to network node 1200 via an interface or port.
[0339] Antenna 1210, communication interface 1206 and / or processing circuit 1202 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1210, communication interface 1206 and / or processing circuit 1202 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.
[0340] The power supply 1208 provides power to the various components of the network node 1200 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1208 may also include or be coupled to a power management circuit to provide power to the components of the network node 1200 for performing the functions described herein. For example, the network node 1200 may be connected to an external power source (e.g., an electrical grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source supplies power to the power circuit of the power supply 1208. As a further example, the power supply 1208 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit. If the external power source fails, the battery can provide backup power.
[0341] Embodiments of network node 1200 may include Fig.12Additional components beyond those shown are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 1200 may include a user interface device to allow information to be input into the network node 1200 and to allow information to be output from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1200.
[0342] Fig.13 is a block diagram of a host 1300 according to various aspects described herein, and the host 1300 may be Fig.10 1016 of the embodiment of the host. As used herein, the host 1300 can be or include a combination of various hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a processing resource in a server farm. The host 1300 can provide one or more services to one or more UEs.
[0343] Host 1300 includes processing circuitry 1302, which is operably coupled to input / output interface 1306, network interface 1308, power supply 1310, and memory 1312 via bus 1304. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.11 and Fig.12 ) so that its description is generally applicable to the corresponding components of the host 1300.
[0344] The memory 1312 may include one or more computer programs, including one or more host applications 1314 and data 1316, which may include user data, such as data generated by a UE for the host 1300 or data generated by the host 1300 for the UE. An embodiment of the host 1300 may utilize only a subset or all of the components shown. The host application 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for a variety of different categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, heads-up display systems). The host application 1314 may also provide user authentication and permission checks, and may periodically report health, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1300 can select and / or instruct different hosts for over-the-top services for the UE. The host application 1314 can support various protocols, such as HTTP live streaming (HLS) protocol, real-time messaging protocol (RTMP), real-time streaming protocol (RTSP), dynamic adaptive streaming over HTTP (MPEG-DASH), etc.
[0345] Fig.14 1400 is a block diagram showing a virtualized environment 1400 in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more hardware nodes (e.g., hardware computing devices running as network nodes, UEs, core network nodes, or hosts). In addition, in an embodiment in which a virtual node does not require radio connectivity (e.g., a core network node or host), the node may be fully virtualized.
[0346] Application 1402 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some of the features, functions and / or advantages of some of the embodiments disclosed herein.
[0347] Hardware 1404 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, and the like. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. Virtualization layer 1406 may present a virtual operating platform that appears to be networked hardware to VMs 1408.
[0348] VM 1408 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 1406. Different embodiments of instances of virtual devices 1402 can be implemented on one or more of VM 1408 and can be implemented in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and client devices.
[0349] In the context of NFV, VMs 1408 can be software implementations of physical machines that run programs as if they were executed on physical, non-virtualized machines. Each VM 1408 and the portion of the hardware 1404 on which it executes (whether hardware dedicated to that VM and / or hardware shared by that VM with other VMs) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1408 on top of hardware 1404 and corresponds to an application 1402.
[0350] Hardware 1404 may be implemented in a standalone network node with general or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed through management and orchestration 1410, which in particular oversees the lifecycle management of application 1402. In some embodiments, hardware 1404 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities (e.g., radio access nodes or base stations) to virtual nodes. In some embodiments, a control system 1412 may be utilized to provide some signaling, which may be used alternatively for communication between hardware nodes and radio units.
[0351] Fig.15 A communication diagram is shown in which a host 1502 communicates with a UE 1506 via a network node 1504 over a partially wireless connection according to some embodiments. Fig.15 Describe the UE discussed in the previous paragraph (such as Fig.10 UE 1012a and / or Fig.11 UE 1100), network nodes (such as Fig.10 The network node 1010a and / or Fig.12 ), and a host (e.g. Fig.10 Host 1016 and / or Fig.13 Host 1300) according to various embodiments of the example implementation.
[0352] Similar to the host 1300, an embodiment of the host 1502 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1502 also includes software, which is stored in the host 1502 or accessible by the host 1502 and can be executed by the processing circuit. The software includes a host application, which can be used to provide services to a remote user (e.g., a UE 1506 connected via an over-the-top (OTT) connection 1550 extending between the UE 1506 and the host 1502). When providing services to a remote user, the host application can provide user data sent using the OTT connection 1550.
[0353] The network node 1504 includes hardware that enables it to communicate with the host 1502 and the UE 1506. The connection 1560 can be direct or through a core network (such as Fig.10The core network 1006 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.
[0354] UE 1506 includes hardware and software stored in or accessible by UE 1506 and executable by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "app", which is operable to provide services to human or non-human users via UE 1506 with the support of host 1502. In host 1502, the executed host application can communicate with the executed client application via an OTT connection 1550 terminated at UE 1506 and host 1502. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 1550 can transmit both the request data and the user data. The client application of the UE can interact with the user to generate the user data provided to the host application via the OTT connection 1550.
[0355] The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide connectivity between the host 1502 and the UE 1506. The connection 1560 and the wireless connection 1570 over which the OTT connection 1550 may be provided have been drawn abstractly to illustrate communications between the host 1502 and the UE 1506 via the network node 1504 without explicit reference to any intermediate devices and the precise routing of messages through those devices.
[0356] As an example of sending data via OTT connection 1550, in step 1508, host 1502 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1506. In other embodiments, the user data is associated with UE 1506 that shares data with host 1502 without explicit human interaction. In step 1510, host 1502 initiates a transmission carrying user data to UE 1506. Host 1502 may initiate the transmission in response to a request sent by UE 1506. The request may be caused by human interaction with UE 1506 or by an operation performed by a client application executed on UE 1506. According to the teachings of the embodiments described throughout this disclosure, the transmission may be delivered via network node 1504. Therefore, in step 1512, according to the teachings of the embodiments described throughout this disclosure, network node 1504 sends the user data carried in the transmission initiated by host 1502 to UE 1506. In step 1514 , UE 1506 receives the user data carried in the transmission, which may be performed by a client application executing on UE 1506 associated with a host application executed by host 1502 .
[0357] In some examples, UE 1506 executes a client application that provides user data to host 1502. The user data may be provided as a reaction to or in response to data received from host 1502. Thus, in step 1516, UE 1506 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may also take into account user input received from the user via the input / output interface of UE 1506. Regardless of the specific manner in which the user data is provided, UE 1506 initiates transmission of the user data to host 1502 via network node 1504 in step 1518. In step 1520, network node 1504 receives user data from UE 1506 and initiates transmission of the received user data to host 1502 in accordance with the teachings of the embodiments described throughout this disclosure. In step 1522, host 1502 receives the user data carried in the transmission initiated by UE 1506.
[0358] One or more of the various embodiments improves the performance of an OTT service provided to a UE 1506 using an OTT connection 1550 in which a wireless connection 1570 forms the last segment. According to an embodiment of the present disclosure, an offset associated with an SSB measurement time may be indicated. Specific SSB measurements may be adjusted accordingly. Thus, the impact of a mobile base station / relay (e.g., a mobile satellite) on the time alignment of the SSB may be reduced. The measurement quality of the SSB in such cases may be enhanced. More specifically, the teachings of these embodiments may improve the performance of a communication network, such as data rate, latency, power consumption, thereby providing benefits such as reduced user waiting time, relaxed file size restrictions, increased content resolution, improved responsiveness, and extended battery life.
[0359] In an example scenario, plant status information may be collected and analyzed by host 1502. As another example, host 1502 may process audio and video data that may have been retrieved from a UE for use in creating a map. As another example, host 1502 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, host 1502 may store surveillance videos uploaded by a UE. As another example, host 1502 may store media content such as video, audio, VR, or AR that it may broadcast, multicast, or unicast to a UE or control access to it. As other examples, host 1502 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function for collecting, retrieving, storing, analyzing, and / or sending data.
[0360] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments improve. There may also be an optional network function for reconfiguring the OTT connection 1550 between the host 1502 and the UE 1506 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 1550 may be implemented in software and hardware of the host 1502 and / or the UE 1506. In some embodiments, sensors (not shown) may be deployed in or associated with other communication devices through which the OTT connection 1550 passes; the sensors may participate in the measurement process by providing the values of the monitored quantities exemplified above or providing the values of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1550 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1504. Such processes and functions are known in the art and can be practiced. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1502 to measure throughput, propagation time, delay, etc. The measurement may be implemented as follows, where the software causes a message (particularly an empty or "dummy" message) to be sent using the OTT connection 1550 while monitoring propagation time, errors, etc.
[0361] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as being located in a single box within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components constituting a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between a processing circuit and a communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.
[0362] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some 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 functions may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium (e.g., in a hardwired manner). In any of those specific embodiments, the processing circuit may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.
[0363] Any embodiments of the present disclosure may be used as a supplement to 3GPP TS, such as 3GPP TS 38.133, Release 17 (eg, V17.4.0).
Claims
1. A method (100) performed by a network node in a communication network, comprising: Determining (S102) a first configuration for a synchronization signal block (SSB) measurement time; wherein SSB refers to a combination of a synchronization signal and a physical broadcast channel; determining (S104) a second configuration for indicating an offset associated with the SSB measurement time; and The first configuration and the second configuration are sent (S106) to a wireless device, for instructing the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration.
2. The method (100) according to claim 1, in, The first configuration includes: periodicity, and duration of the SSB measurement time; and The second configuration includes: a timing offset window associated with the duration of the SSB measurement time.
3. The method (100) according to claim 2, in, The duration of the SSB measurement time is extended by the timing offset window to start earlier than the first configuration; and / or Therein, the duration of the SSB measurement time is extended by the timing offset window to end later than the first configuration.
4. The method (100) according to claim 2, in, The duration of the SSB measurement time is shifted by the timing offset window to start earlier than the first configuration; or wherein the duration of the SSB measurement time is shifted by the timing offset window to end later than the first configuration.
5. The method (100) according to any one of claims 2 to 4, in, The timing offset window is constant; or Wherein, the timing offset window can be changed periodically at an update rate.
6. The method (100) according to any one of claims 1 to 5, in, The second configuration is enabled or disabled based at least on an instruction from the network node, and / or a report from the wireless device, and / or a predefined rule.
7. The method (100) according to any one of claims 1 to 6, in, The second configuration is determined based at least on the first configuration.
8. The method (100) according to any one of claims 1 to 6, in, The second configuration is determined by the wireless device and / or by a network node serving the wireless device based at least on measurements of SSBs and / or cells.
9. The method (100) according to any one of claims 1 to 6, in, The second configuration is determined based at least on a location of the wireless device.
10. The method (100) according to any one of claims 1 to 9, in, The second configuration includes a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
11. The method (100) according to any one of claims 1 to 10, in, The first configuration includes at least a first SSB measurement time and a second SSB measurement time; as well as The second configuration includes at least a first timing offset window for a first duration of the first SSB measurement time, and a second timing offset window for a second duration of the second SSB measurement time.
12. The method (100) according to claim 11, in, When the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window is disabled.
13. The method (100) according to claim 12, in, Based on the priority of the first timing offset window and / or the priority of the second timing offset window, it is determined whether the first timing offset window or the second timing offset window is disabled.
14. The method (100) according to any one of claims 1 to 13, in, The first configuration and the second configuration are provided to the wireless device from a satellite; as well as The second configuration is determined based at least on the location of the wireless device, the ephemeris data of the satellite and / or the feeder link delay.
15. The method (100) according to claim 14, in, The second configuration is enabled or disabled for the wireless device based on a change in at least one of the following: the validity or invalidity of the ephemeris data, the validity or invalidity of said location of said wireless device, the type of satellite, the position of at least one adjacent satellite, or The time at which coverage will be achieved by at least one adjacent satellite; or The second configuration is enabled or disabled for the wireless device based on at least one of the following: the capabilities of the wireless device; or The first configuration.
16. The method (100) according to any one of claims 1 to 15, in, The measurement process and requirements for measuring the SSB during the SSB measurement time are based on the first configuration and / or the second configuration.
17. The method (100) according to claim 16, in, The requirements for measuring SSB include at least one of the following: Measurement time, measurement accuracy, number of identified cells to be measured per carrier, and / or number of beams to be measured.
18. The method (100) according to any one of claims 1 to 17, in, Based on the first configuration and / or the second configuration, scheduling restrictions are applied to the SSB measurement time.
19. The method (100) according to any one of claims 1 to 17, in, When the duration of the SSB measurement time is close to or conflicts with a paging occasion, the duration and / or the second configuration is disabled.
20. The method (100) according to any one of claims 1 to 19, in, The first configuration and the second configuration are transmitted to a plurality of wireless devices including the wireless device by broadcasting; or The first configuration and the second configuration are sent to the wireless device via a dedicated message.
21. The method (100) according to any one of claims 1 to 20, in, The network node includes a satellite or a base station relayed by the satellite.
22. The method (100) according to any one of claims 1 to 21, in, The wireless device is in an idle mode, or an inactive mode, or a connected mode.
23. A method (200) performed by a wireless device, comprising: Receive (S202) a first configuration and a second configuration from a network node in a communication network; wherein the first configuration is used for a synchronization signal block SSB measurement time, and the second configuration is used to indicate an offset related to the SSB measurement time; and Based at least on the first configuration and / or the second configuration, performing (S204) SSB measurement.
24. The method (200) according to claim 23, in, The first configuration includes: periodicity, and duration of the SSB measurement time; and The second configuration includes: a timing offset window associated with the duration of the SSB measurement time.
25. The method (200) according to claim 24, in, The duration of the SSB measurement time is extended by the timing offset window to start earlier than the first configuration; and / or Therein, the duration of the SSB measurement time is extended by the timing offset window to end later than the first configuration.
26. The method (200) according to claim 24, in, the duration of the SSB measurement time being shifted by the timing offset window to start earlier compared to the first configuration; or wherein the duration of the SSB measurement time is shifted by the timing offset window to end later than the first configuration.
27. The method (200) according to any one of claims 24 to 26, in, The timing offset window is constant; or Wherein, the timing offset window can be changed periodically at an update rate.
28. The method (200) according to any one of claims 23 to 27, in, The second configuration is enabled or disabled based at least on an indication from the network node, and / or a report from the wireless device, and / or a predefined rule.
29. The method (200) according to any one of claims 23 to 28, in, The second configuration is determined based at least on the first configuration.
30. The method (200) according to any one of claims 23 to 28, in, The second configuration is determined by the wireless device and / or by a network node serving the wireless device based at least on measurements of SSBs and / or cells.
31. The method (200) according to any one of claims 23 to 28, in, The second configuration is determined based at least on a location of the wireless device.
32. The method (200) according to any one of claims 23 to 31, in, The second configuration includes a plurality of timing offset windows selectable by the wireless device for the SSB measurement time.
33. The method (200) according to any one of claims 23 to 32, in, The first configuration includes at least a first SSB measurement time and a second SSB measurement time; as well as The second configuration includes at least a first timing offset window for a first duration of the first SSB measurement time, and a second timing offset window for a second duration of the second SSB measurement time.
34. The method (200) according to claim 33, in, When the first duration is close to or conflicts with the second duration, the first timing offset window and / or the second timing offset window is disabled.
35. The method (200) according to claim 34, in, Based on the priority of the first timing offset window and / or the priority of the second timing offset window, it is determined whether the first timing offset window or the second timing offset window is disabled.
36. The method (200) according to any one of claims 23 to 35, in, The first configuration and the second configuration are provided to the wireless device from a satellite; as well as The second configuration is determined based at least on the position of the wireless device, the ephemeris data of the satellite and / or the feeder link delay.
37. The method (200) according to claim 36, in, The second configuration is enabled or disabled for the wireless device based on a change in at least one of the following: the validity or invalidity of the ephemeris data, the validity or invalidity of said location of said wireless device, the type of satellite, the position of at least one adjacent satellite, or The time at which at least one adjacent satellite will be captured; or The second configuration is enabled or disabled for the wireless device based on at least one of the following: the capabilities of the wireless device; or The first configuration.
38. The method (200) according to any one of claims 23 to 37, in, The measurement process and requirements for measuring the SSB during the SSB measurement time are based on the first configuration and / or the second configuration.
39. The method (200) according to any one of claims 38, in, The requirements for measuring SSB include at least one of the following: Measurement time, measurement accuracy, number of identified cells to be measured per carrier, and / or number of beams to be measured.
40. The method (200) according to any one of claims 23 to 39, in, Based on the first configuration and / or the second configuration, scheduling restrictions are applied to the SSB measurement time.
41. The method (200) according to any one of claims 23 to 40, in, When the duration of the SSB measurement time is close to or conflicts with a paging occasion, the duration and / or the second configuration is disabled.
42. The method (200) according to any one of claims 23 to 41, in, The first configuration and the second configuration are transmitted to a plurality of wireless devices including the wireless device by broadcasting; or The first configuration and the second configuration are sent to the wireless device via a dedicated message.
43. The method (200) according to any one of claims 23 to 42, in, The network node includes a satellite or a base station relayed by the satellite.
44. The method (200) according to any one of claims 23 to 43, in, The wireless device is in an idle mode, or an inactive mode, or a connected mode.
45. An apparatus (10) for a network node in a communication network, comprising: Processor (101); as well as a memory (102) containing instructions executable by the processor, whereby the apparatus (10) for the network node is operable to: Determining a first configuration for a synchronization signal block (SSB) measurement time; wherein SSB refers to a combination of a synchronization signal and a physical broadcast channel; determining a second configuration for indicating an offset associated with the SSB measurement time; as well as The first configuration and the second configuration are sent to a wireless device to instruct the wireless device to perform SSB measurement based on at least the first configuration and / or the second configuration.
46. The device (10) according to claim 45, wherein The apparatus (10) is further operable to perform a method according to any one of claims 2 to 22.
47. An apparatus (20) for a wireless device, comprising: Processor (201); as well as A memory (202) comprising instructions executable by a processor, whereby the apparatus (20) for the wireless device is operable to: Receiving a first configuration and a second configuration from a network node in a communication network; wherein the first configuration is used for a synchronization signal block (SSB) measurement time, and the second configuration is used to indicate an offset associated with the SSB measurement time; as well as Based at least on the first configuration and / or the second configuration, SSB measurement is performed.
48. The device (20) according to claim 47, wherein The apparatus (20) is further operable to perform a method according to any one of claims 24 to 44.
49. A computer readable storage medium (80) storing instructions (801) which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 44.
Citation Information
Cited By
Systems and methods for performing signal measurements
WO2026118284A1
