Method and apparatus for handling of service reception

Abstract

Embodiments of the present disclosure provide method and apparatus for handling of service reception in a network A method performed by a wireless communication device may comprise, when the wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing a reception of the broadcast / groupcast transmission.

Description

METHOD AND APPARATUS FOR HANDLING OF SERVICE RECEPTIONTECHNICAL FIELD

[0001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for handling of service reception in a network, e.g. broadcast / groupcast transmission reception in Non-Terrestrial Network (NTN).BACKGROUND

[0002] This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

[0003] To benefit from strong mobile ecosystem and economy of scale, a satellite network based on terrestrial wireless access technologies including new radio (NR) and long term evolution (LTE) for satellite networks, is being specified in 3rd Generation Partnership Project (3 GPP) standard.

[0004] In 3GPP Release 15, the first release of the fifth generation (5G) system (5GS) was specified. This is a

[0005] new generation’s radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC) and massive machine type communication (mMTC). 5G includes the NR access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the LTE specification, and additional components are introduced when motivated by the new use cases.

[0006] In Release 15, 3GPP also started the work to prepare NR for operation in an NTN. The work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in 3GPP TR 38.811 V15.4.0. In Release 16, the work to prepare NR for operation in an NTN network continues with the study item “Solutions for NR to support Non-Terrestrial Network” in 3GPP TR 38.821 V16.2.0. In parallel the interest to adapt LTE for operation in NTN is growing. As a consequence, 3GPP introduced support for NTN in both LTE and NR in Release 17. After the basic functionality was established, NTN enhancements continued in Release 18 for both LTE and NR.

[0007] Public Warning System (PWS) is an umbrella term covering the Earthquake and Tsunami Warning System (ETWS), the Commercial Mobile Alert System (CMAS), the European Public Warning System (EU-ALERT), and the Korean Public Alert System (KPAS).

[0008] ETWS primary / secondary notification and CMAS notification are delivered in System Information Blocks (SIBs) while indication of ETWS / CMAS notification delivery is indicated in paging message or DCI using direct indication. Before acquiring the SIBs delivering ETWS / CMAS notification, the user equipment (UE) first needs to read SIB1 to obtain the scheduling information of those SIBs.

[0009] Segmentation can be applied for the delivery of message e.g. an ETWS secondary notification and CMAS notification. The segmentation is fixed for transmission of e.g. a given ETWS secondary notification and CMAS notification within a cell (i.e. the same segment size for a given segment with the same messageidentifier, serialNumber and wamingMessageSegmentNumber), Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) does not interleave transmissions of CMAS notifications, i.e. all segments of e.g. a given CMAS notification transmission are transmitted prior to those of another CMAS notification.

[0010] Upon entering a cell during Radio Resource Control (RRC) IDLE (RRC IDLE), following successful handover or upon connection re-establishment, the UE discards any previously buffered wamingMessageSegment and wamingAreaCoordinatesSegment (if any). If either the received value of messageidentifier or of serialNumber or of both are different from the current (stored) values of messageidentifier and serialNumber, the UE also discards any previously buffered wamingMessageSegment and wamingAreaCoordinatesSegment (if any).SUMMARY

[0011] 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.

[0012] It has been decided that narrow band internet of things (NB-IoT) UEs in RRC connected cannot receive PWS indication / notifications. This will lead to PWS notification reception is interrupted when the NB-IoT UE is triggered to enter RRC connected when e.g., receiving paging from the network (NW).

[0013] Besides, for some NW e.g. NTN, the time that a network node (e.g. satellite) or cell serves a certain area is fairly short especially for earth-moving cell and cell resel ection / switch occurs quite frequently, it proposed that a UE does not discard previously buffered message segments (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) when switching serving cell. However, the cell switch may be due to either movement of network node (e.g. satellite) or UE, for the latter case it may not be suitable to keep the buffered messagesegments, i.e., wamingMessageSegment and wamingAreaCoordinatesSegment (if any). Besides if the new network node (e.g. satellite) delivers a message segment (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) with different delivery information or configuration (e.g. different messageidentifiers or serialNumbers (e.g. in the same SIB), the UE (e.g. NB-IoT UE) will still discard it.

[0014] To overcome or mitigate at least one of above mentioned problems or other problems, the embodiments of the present disclosure propose a solution for handling of service reception in a network.

[0015] In a first aspect of the disclosure, there is provided a method performed by a wireless communication device. The method may comprise, when the wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing a reception of the broadcast / groupcast transmission.

[0016] In a second aspect of the disclosure, there is provided a method performed by a network node. The method may comprise, when a wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing a reception of the broadcast / groupcast transmission.

[0017] In a third aspect of the disclosure, there is provided a wireless communication device. The wireless communication device may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said wireless communication device is operative to, when a wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritize a reception of the broadcast / groupcast transmission.

[0018] In a fourth aspect of the disclosure, there is provided a network node. The network node may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said network node is operative to, when a wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritize a reception of the broadcast / groupcast transmission.

[0019] In a fifth aspect of the disclosure, there is provided a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second aspect.

[0020] In a sixth aspect of the disclosure, there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second aspect.

[0021] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, with the proposed solutions, the impact of RRC state switch can be avoided which ensures the broadcast / groupcast transmission (e.g. PWS notification) can be received in time. In some embodiments herein, unnecessary discarding of stored segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) is avoided which improves the delivery efficiency, saves UE energy and reduces the delivery time. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, by way of example, from the following detailed description with reference to the accompanying drawings, in which like reference numerals or letters are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and not necessarily drawn to scale, in which:

[0023] FIG. la shows example architecture of a satellite network with bent pipe transponders;

[0024] FIG. lb shows an example of store and forward operation for an NTN pay load;

[0025] FIG.1c shows an example of NTN Architecture Types;

[0026] FIGs.2, 3a, 3b, 3c, 3d, 3e, 4a, 4b, 5a, 5b, 6, 7a, 7b and 7c show flowcharts of methods according to embodiments of the present disclosure;

[0027] FIG.8 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure;

[0028] FIG.9 shows an example of a communication system in accordance with some embodiments;

[0029] FIG.10 shows a UE in accordance with some embodiments;

[0030] FIG.11 shows a network node in accordance with some embodiments; and

[0031] FIG.12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0032] The 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 for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

[0033] As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA), Non-Terrestrial Network (NTN) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc. UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future.

[0034] The term “network device” or “network node” or “network function” refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure. For example, the 5G system (5GS) may comprise a plurality of NFs such as Access and Mobility Management Function (AMF), Charging Function(CHF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), radio access network (RAN), service communication proxy (SCP), network data analytics function (NWDAF), network slice selection function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), an Ambient Internet of Things Function (AIOTF), Unified Data Repository (UDR), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network. For example, the 4G system (such as Long Term Evolution (LTE)) may include Mobile Management Entity (MME), home subscriber server (HSS), PCRF (Policy and Charging Rules Function), PGW (Packet Data Network Gateway), PGW control plane (PGW-C), PGW user plane (PGW-U) Serving gateway (SGW), application server (AS), SGW control plane (SGW-C), SGW user plane (SGW-U), E-UTRAN Node B (eNB), etc. For example, the NTN may include satellite based network node. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network.

[0035] The network device may be an access network device with accessing function in a communication network via which a terminal device accesses to the network and receives services therefrom. The access network device may include a base station (BS), satellite based access network device, an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller or any other suitable device in a wireless communication network. The 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 header (RH), an Integrated Access and Backhaul (IAB) node, a remote radio head (RRH), a relay, a low power node such as a femto, a pico, Wireless Access Backhaul (WAB) node, and so forth.

[0036] Yet further examples of the access network device comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, positioning nodes and / or the like. More generally, however, the networknode may represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

[0037] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. The UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), zero-energy (ZE) loT (ZE-IoT) devices, Passive-IoT device, Ambient power-enabled loT, or Ambient loT devices, or an Access Terminal (AT). The terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, 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 equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device”, “terminal”, “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project), such as 3GPP LTE standard or NR standard. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and / or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.

[0038] As yet another example, in an loT scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another terminal device and / or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3 GPP narrow band internet ofthings (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0039] It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar / same meanings may also be used.

[0040] 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 skills in the art to which this disclosure belongs.

[0041] In 3GPP, 5G system (5GS) is a new generation’s radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), narrow band internet of things (NB-IoT) and Massive Machine-Type Communications (mMTC). 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the Long Term Evolution (LTE) specification, and to that add needed components when motivated by new use cases. There have been a lot of discussions in 3GPP in the last few years on how to specify technologies to cover / address use cases for Machine-to-Machine (M2M) and / or Internet of Things (loT). In Release 13 enhancements to support Machine-Type Communications (MTC) were specified introducing new UE categories Ml (Cat-Mi) and NB1 (Cat-NBl) to support reduced maximum bandwidth of up to 6 physical resource blocks (PRBs) in enhanced Machine Type Communication (eMTC) work item and narrowband carrier in NB-IoT work item specifying a new radio interface, respectively.

[0042] At the 3GPP RAN#70 meeting, a new Release 13 work item named NB-IoT was approved. The objective of the new loT related work items approved for release 13 was to specify a radio access for cellular internet of things (loT) that addresses improved indoor coverage, support for massive number of low throughput devices, not sensitive to delay, ultra-low device cost, low device energy consumption and (optimized) network architecture.

[0043] NB-IoT can be described as a narrowband version of LTE. Similar to eMTC, NB-IoT makes use of increased acquisition times and time repetitions to extend the system coverage. The repetitions can be seen as a third level of retransmissions added at the physical layer as a complement to those at Medium Access Control (MAC) Hybrid Automatic Repeat Request (HARQ) and Radio Link Control (RLC) Automatic Repeat Request (ARQ). A NB-IoT downlink carrier is defined by 12 Orthogonal Frequency Division Multiplexing (OFDM) sub-carriers,each of 15 kHz, giving a total baseband bandwidth of 180 kHz. When multiple carriers are configured, several 180 kHz carriers can be used, e.g., for increasing the system capacity, inter-cell interference coordination, load balancing, etc. This design gives NB-IoT high deployment flexibility. When receiving RRCConnectionRelease message, NB-IoT UE delays releasing the RRC connection for 10 seconds.

[0044] Satellite Communications

[0045] A satellite radio access network usually includes the following components:

[0046] • A satellite that refers to a space-home platform.

[0047] • An earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture.

[0048] • Feeder link that refers to the link between a gateway and a satellite

[0049] • Access link that refers to the link between a satellite and a UE.

[0050] A communication satellite typically generates several beams over a given area. The footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell (but a cell consisting of multiple beams is not precluded). The footprint of a beam is also often referred to as a spotbeam. Three types of beams or cells are supported in NTN:

[0051] • Earth-fixed beams / cells: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., in the case of Geostationary Earth Orbit (GEO) satellites).

[0052] • Quasi-Earth-fixed beams / cells: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., in the case of Non-geostationary orbit (NGSO) satellites generating steerable beams).

[0053] • Earth-moving beams / cells: provisioned by beam(s) whose coverage area slides over the earth surface (e.g., in the case of NGSO satellites generating fixed or non-steerable beams).

[0054] NTN-specific information in the system information

[0055] Due to the special operating conditions in an NTN, the system information broadcasted in an NTN cell has to include NTN-specific information. To serve this purpose, a new SIB (SIB 19) is introduced in NR NTN which contains NTN-specific information. In loT NTN, the NTN-specific information is provided in SIB31 and SIB32, while t-Service is indicated in SIB3(SIB3-NB in NB-IoT) in 3GPP TS 36.331 vl 8.4.0. t-Service indicates time information on when a NTN quasi-Earth fixed cell is going to stop serving the area it is currently covering, while t-ServiceStart indicates time information on when the incoming satellite is going to start serving the area for quasi-earth fixed cell. tle-EphemerisParameters provides the satellite orbital parameters based on the TLE set format for estimating in-coverage and out-of-coverage periods for a satellite with earth moving cell(s).

[0056] 3GPP Release 19 NTN enhancements

[0057] The standardization of NTN technologies continues in 3GPP with another two work items: RP-234077 in 3GPP TSG RAN Meeting #102 and RP-234078 in 3GPP TSG RAN Meeting #102 for LTE and NR, respectively. The justification for these enhancements is the necessities of the commercial deployments that are ongoing at the moment of writing. Based on real deployment or deployment plans, further evolution of NR and loT NTN is required.

[0058] Among the objectives included in the loT NTN Release 19 Work Item Description (WID), this invention is related to Support broadcast of PWS messages for NB-IoT re-using the LTE mechanisms, for NB-IoT UE in RRC connected, not support PWS indication / notifications in paging, direct indication, and system information.

[0059] Architecture

[0060] Two basic architectures can be distinguished for satellite communication networks, depending on the functionality of the satellites in the system:

[0061] • Transparent payload (also referred to as bent pipe architecture). The satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency. When applied to general 3GPP architecture and terminology, the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals / data between the gNB and the UE

[0062] • Regenerative payload. The satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth. When applied to general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite.

[0063] In the work item for NR NTN and loT NTN in 3GPP Release 17 and Release 18, only the transparent payload architecture is considered.

[0064] FIG. la shows example architecture of a satellite network with bent pipe transponders (i.e. , the transparent pay load architecture).

[0065] The base station (BS)(e.g. gNB, eNB, RAN node, etc.) may be integrated in the gateway or connected to the gateway via a terrestrial connection (wire, optic fiber, wireless link). A satellite radio access network may usually include the following components:A satellite that refers to a space-home platform,An earth-based gateway (GW) that connects the satellite to a base station or a core network, depending on the choice of architecture,A feeder link that refers to the link between a gateway and a satellite,An access link, or service link, that refers to the link between a satellite and a device (e.g. UE).

[0066] FIG. lb shows an example of store and forward operation for an NTN pay load.

[0067] The store and forward architecture for NTN involves the use of network nodes as satellites or high-altitude platforms (HAPS) to relay communication signals between terrestrial device (e.g. UE) and the core network. This architecture is designed to extend the coverage and capacity of traditional terrestrial networks, particularly in remote or underserved areas.

[0068] The store and forward mechanism allows the NTN to temporarily store incoming data before transmitting it to the next hop in the network, which could be another relay node (e.g., thanks to inter-satellite links) or the core network itself. This enables the NTN to overcome the inherent latency and intermittent connectivity associated with non-terrestrial communication links.

[0069] The store and forward architecture is particularly useful in scenarios where the NTN is used to provide connectivity in areas with limited terrestrial infrastructure, such as remote rural or maritime environments. This mechanism, the NTN can efficiently manage the transmission of data between UEs and the core network, even in challenging communication conditions, i.e., areas where satellites cannot be connected to ground stations. From a business perspective, this architecture improves ground segment affordability by enabling operation with fewer ground-stations and a more robust operation of the satellite under intermittent feeder link operation. This is specifically well-suited for delay tolerant loT applications that do not require continuous connectivity.

[0070] FIG.1c shows an example of NTN Architecture Types.

[0071] Although the Transparent Architecture is the one most used in deployments today, the semi-transparent architecture, where the RU is on-board the satellite, shows some promise of providing improved network scalability and performance. An eNB (or gNB) refers to the satellite telecom functions of the Satellite Access Node (SAN) which can vary depending on the regenerative deployment architecture. Examples of a satellite telecom function may include at least one of an Advanced Aerial / Antenna Services (AAS), a radio unit (RU), a distributed unit (DU), a central unit (CU). For example, for the semi-transparent RU-on-board, the satellite telecom function may include an AAS and a RU. For the regenerative: DU-on-board, the satellite telecom function may include an AAS, a RU, and a DU. For the regenerative: gNB-on-board, the satellite telecom function may include an AAS, a RU, a DU and a CU. The potential for different SAN configurations rather than a complete eNB being referred to as the entity performing the main steps. Any of the regenerative architectures could apply and then the invention may be implemented in one or more of CU, DU, RU or AAS

[0072] Although the subject matter described herein may be implemented in any appropriate type of system (e.g. LTE, 5GS, 6GS, etc.) using any suitable components, the embodiments disclosed herein are described in relation to a communication system complied with the exemplary system architecture illustrated in FIGs.la, lb and 1c. For simplicity, the system architecture of FIGs.la, lb and 1c only depicts some exemplary elements. In practice, a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and / or use of the services provided by, or via, the communication system.

[0073] The message names in the procedures / methods of the embodiments are descriptive. It is assumed that the names may be updated e.g. with corresponding Service Based Interface (SBI) based names where applicable during the normative phase.

[0074] The term NTN may, depending on the context, refer to either or both of NR NTN and loT NTN, and sometimes the term is used to refer to only loT NTN.

[0075] The embodiments outlined below are described mainly in terms of LTE based NB-IoT NTNs, but they are equally applicable in an NTN based on LTE-M or NR technology.

[0076] The term “network” is used in the solution description to refer to a network node, which typically will be a gNB (e.g. in a NR based NTN) or an eNB (e.g. in an LTE based NTN, such as an loT NTN), but which may also be a base station or an access point in another type of network based on communication via satellites or HAPS, or any other network node (in a network involving satellites or HAPS) with the ability to directly or indirectly communicate with a UE. More specifically, when the term “network” is used in the solution description, and the network is said to do something in relation to a UE, e.g. receive something from a UE or transmit something to a UE or configure a UE with some configuration, this refers to a network node, typically a gNB.

[0077] The terms information element (IE), parameter, field parameter, and field may be used interchangeably in this document.

[0078] Parameters / IEs / fields used in Abstract Syntax Notation One(ASN.l) code as well as in procedural text in the 3GPP RRC specification for 5G / NR, i.e., 3GPP TS 38.331 version 18.0.0, are often named with a suffix indicating the number of the release of the 3 GPP standard the parameter / IE / field was introduced in (e.g. the suffix “-r!7” for a parameter / IE / field introduced in release 17 of the 3GPP standard). Parameters / IEs / fields following this naming convention are typically referred to both with and without the suffix, where the name including the suffix isused in the ASN.l code (and thus defines the formal name from the ASN.l compiler’s perspective), while the name without the suffix is used in running text, e.g. in field descriptions and procedural text. Relevant examples in the context of this document include the parameters / IEs / fields tl-Threshold-rl7 / tl -Threshold and t-Service-rl7 / t-Service. In this document, both name variants may occur for various parameters / IEs / fields.

[0079] In below embodiments, (NB-IoT) SIB for delivering ETWS primary notification is denoted ETWS primary SIB(-NB), (NB-IoT) SIB for delivering ETWS secondary notification is denoted ETWS secondary SIB(-NB), (NB-IoT) SIB for delivering CMAS notification is denoted CMAS SIB(-NB).

[0080] In below embodiments, PWS notification refers to ETWS primary notification and / or ETWS secondary notification and / or CMAS notification. The embodiments are equally applied to other kinds of PWS notification such as EU-ALERT, the Korean Public Alert System (KPAS), etc, and in general (higher layer) info delivered in SIB.

[0081] FIGs.2, 3a, 3b, 3c, 3d, 3e, 4a, 4b, 5a and 5b show flowcharts of methods according to embodiments of the present disclosure, which may be performed by an apparatus implemented in or at or as a wireless communication device or communicatively coupled to the wireless communication device. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the methods as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in an embodiment, the description thereof is omitted in other embodiment for brevity.

[0082] FIG.2 shows a flowchart of a method 200 according to an embodiment of the present disclosure.

[0083] At block 202, when the wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, the wireless communication device may prioritize a reception of the broadcast / groupcast transmission.

[0084] The broadcast / groupcast transmission may be any suitable broadcast / groupcast transmission. In an embodiment, the broadcast / groupcast transmission may comprise at least one of time critical PWS notification (e.g. ETWS primary notification), non-time critical PWS notification^, g. ETWS secondary notification), or a Multicast / Broadcast Services (MBS) service.

[0085] Segmentation can be applied for the delivery of the broadcast / groupcast transmission e.g. ETWS secondary notification and CMAS notification. The segmentation may be fixed for transmission of a given broadcast / groupcast transmission within a cell (i.e. the same segmentsize for a given segment with the same messageidentifier, serialNumber and wamingMessageSegmentNumber), BS or satellite based network node does not interleave transmissions of the broadcast / groupcast transmission, i.e. all segments of a given broadcast / groupcast transmission are transmitted prior to those of another broadcast / groupcast transmission.

[0086] The wireless communication device may prioritize a reception of the broadcast / groupcast transmission in various ways. For example, the wireless communication device may ignore or delay any other action, instruction, RRC state change, etc. until the wireless communication device has received the broadcast / groupcast transmission, or all segments or a part of segments of the broadcast / groupcast transmission.

[0087] For example, the wireless communication device may delay performing a random access procedure, delay entering an RRC connected state, not discard at least one buffered segment of the broadcast / groupcast transmission, not reacquiring multicast control channel (MCCH), etc.

[0088] The wireless communication device may be any suitable node, device, function, or entity with the radio function, such as terminal device, UE, NB-IoT UE, etc. For example, the wireless communication device may comprise any suitable terminal device of any suitable network, e.g. 4GS, 5GS, 6GS orNTN.

[0089] In an embodiment, the wireless communication device may comprise any suitable NTN terminal device. For example, the wireless communication device in RRC connected state cannot receive some broadcast / groupcast transmission e.g. PWS indication / notification if a dedicated signaling is not used.

[0090] In an embodiment, the wireless communication device may comprise a Narrowband Internet of Things (NB-IoT) user equipment.

[0091] The network may comprise any suitable network which can deliver the broadcast / groupcast transmission. For example, the network may comprise LTE, 5GS, 6GS or NTN.

[0092] In an embodiment, the wireless communication device may be served by a network node (e.g. gNB, satellite based gNB, eNB, satellite based eNB) in the network. In an embodiment, the wireless communication device may be served by a satellite based network node in the NTN. In an embodiment, the satellite based network node may comprise a satellite based radio access network node.

[0093] The network node may be comprised in any suitable network. For example, the network node may be comprised in 3 GPP network or NTN. In an embodiment, the 3 GPP network may comprise EPS, a fifth generation system (5GS) or a sixth generation system (6GS).

[0094] The network node may be any suitable network node, e.g. access network device (such as eNB, gNB, satellite, etc.), which can deliver broadcast / groupcast transmission. In an embodiment, the network node may comprise a satellite based radio access network node.

[0095] In an embodiment, when the wireless communication device in a radio resource control (RRC) idle state or an RRC inactive state is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered, the wireless communication device may perform at least one of steps of methods 300, 320, 330, 340 and 350 of FIGs.3a, 3b, 3c, 3d and 3e.

[0096] FIG.3a shows a flowchart of a method 300 according to an embodiment of the present disclosure.

[0097] At block 302, optionally, the wireless communication device may ignore an instruction in a paging message which informs the wireless communication device to enter an RRC connected state. For example, the paging message may be from the satellite based radio access network node.

[0098] At block 304, optionally, the wireless communication device may delay entering an RRC connected state when the wireless communication device is triggered to enter the RRC connected state.

[0099] At block 306, optionally, the wireless communication device may delay entering an RRC connected state until the wireless communication device has received the broadcast / groupcast transmission or for a time period when the wireless communication device is triggered to enter the RRC connected state. For example, the time period may be any suitable time period which can be (pre)determined by the wireless communication device or be (pre)configured by the network.

[0100] At block 308, optionally, the wireless communication device may delay performing a random access procedure when the wireless communication device is triggered to perform the random access procedure;

[0101] At block 310, optionally, the wireless communication device may delay performing a random access procedure until the wireless communication device has received the broadcast / groupcast transmission or for a time period when the wireless communication device is triggered to perform the random access procedure. For example, the time period may be any suitable time period which can be (pre)determined by the wireless communication device or be (pre)configured by the network.

[0102] In an embodiment, when receiving time critical PWS notification (e.g. ETWS primary notification) in RRC idle or RRC inactive, the wireless communication device e.g. UE mayprioritize the time critical PWS notification reception and delay performing delay random access when triggered.

[0103] In an embodiment, when a (NB-IoT) UE in RRC idle or RRC inactive is receiving time critical PWS notification (e.g., ETWS primary notification) or is indicated there are time critical PWS notification being delivered, the UE (is allowed to) ignore the instruction in the paging message which informs the UE to enter RRC connected and / or delay random access for e.g., tracking area update (TAC) or sending UE originated traffic or sending UL service request until it receives the time critical PWS notification. In one option, the UE is allowed to take such action for at most a (pre)configured time period since it receives the paging message or is triggered to perform random access. In one option, if the paging message triggering the UE to enter RRC connected indicates the UE shall not ignore it even the UE is receiving time critical PWS notification, the UE shall follow the instruction in the paging message.

[0104] FIG.3b shows a flowchart of a method 320 according to an embodiment of the present disclosure.

[0105] At block 322, optionally, the wireless communication device may indicate to the network that the wireless communication device is receiving or going to receive a type of the broadcast / groupcast transmission and following an instruction of the network.

[0106] The type of the broadcast / groupcast transmission may be any suitable type of broadcast / groupcast transmission.

[0107] The instruction of the network may comprise any suitable instruction. In an embodiment, the instruction of the network may comprise at least one of instructing the wireless communication device to terminate a random access procedure and continue receiving the broadcast / groupcast transmission in RRC idle or RRC inactive until the broadcast / groupcast transmission is received or for a time period or until the wireless communication device is paged by the network to enter a RRC connected state, or delivering the type of the broadcast / groupcast transmission to the wireless communication device using a dedicated signaling after the wireless communication device enters a RRC connected state.

[0108] For example, when receiving non-time critical PWS notification in RRC idle or RRC inactive, the wireless communication device e.g. UE indicates this to the NW and follows the NW instruction.

[0109] In an embodiment, when a (NB-IoT) UE in RRC idle or RRC inactive is receiving non-time critical PWS notification (e.g., ETWS secondary notification and / or CMAS notification) or is indicated there is non-time critical PWS notification being delivered and is triggered to enter RRC connected, the UE may indicate to the NW (e.g., in Msg3 in case of 4 step random access or MsgB in case of 2 step random access) that it is receiving (or going toreceive) certain type(s) of non-time critical PWS notification. The type information may be an indicator (e.g. two bits indicator) indicating whether it is ETWS secondary notification or CMAS notification or both, or represented by the messageidentifier and optionally also the serialNumber of the notification. Correspondingly the NW may take any of the any suitable actions.

[0110] In an embodiment, the NW may instruct the UE to terminate the random access procedure and continue receiving non-time critical PWS notification in RRC idle or RRC inactive until the non-time critical PWS notification is received or for at most a (preconfigured) time period or until the UE is paged by the NW (again) to enter RRC connected where the paging message may indicate that the UE shall follow the instruction in the paging message even it is receiving the non-time critical PWS notification.

[0111] In an embodiment, the NW may deliver the indicated type(s) of non-time critical PWS notification to the UE using a dedicated signaling (e.g., a MAC control element (CE) identified by a specific Logical Channel (LCH) identifier (ID) or RRC signaling) after the UE enters RRC connected.

[0112] At block 324, optionally, the wireless communication device may inform the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states.

[0113] The RRC states may comprise any suitable RRC states, e.g. RRC idle state, RRC inactive state, or RRC connected state.

[0114] In an embodiment, the wireless communication device e.g. UE may inform the NW it is able to assemble segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and warning AreaCoordinates Segment (if any)) received in different RRC states. Correspondingly the NW may deliver the (subsequent) segments of the broadcast / groupcast transmission to the UE with the same deliver configuration adopted in different RRC states. In this case, the UE does not discard previously buffered segments (e.g. wamingMessageSegment and warning AreaCoordinates Segment (if any)) unless other discarding condition(s) are met.

[0115] In an embodiment, the UE may inform the NW in Msg3 / MsgB or in a uplink (UL) message (e.g., UEAssistancelnformation) after entering RRC connected that it is able to assemble segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any), etc.) received in different RRC states and segments of the broadcast / groupcast transmission (e.g. the PWS notification segments, etc.) it has already received or buffered in RRC idle or RRC inactive. The NW then only delivers the segments (e.g. PWS notification segments, etc.) that the UE has not received or buffered yet with the samedelivery information, e.g., the same messageidentifier, serialNumber, and the same delivery configuration, e.g., the same segment size, as used in delivering the segments (e.g. the wamingMessageSegment and wamingAreaCoordinates Segment (if any), etc.) in the corresponding SIB(-NB), and informs the UE how it will deliver the segments. The UE then does not discard previously buffered segments if the NW adopts the same delivery information / configuration unless the other condition(s) leading to the UE to discard the stored segments are met.

[0116] At block 326, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if a same delivery information or configuration for the broadcast / groupcast transmission is applied in different RRC states.

[0117] At block 328, optionally, the wireless communication device may discard at least one buffered segment of the broadcast / groupcast transmission if different delivery information or configuration for the broadcast / groupcast transmission is applied in different RRC states.

[0118] FIG.3c shows a flowchart of a method 330 according to an embodiment of the present disclosure.

[0119] At block 332, optionally, the wireless communication device may assemble at least one buffered segment and / or the at least one received segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment.

[0120] At block 334, optionally, the wireless communication device may discard at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is different from delivery information or configuration associated with the at least one received segment.

[0121] At block 336, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment.

[0122] At block 338, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if cell or network node switch or reselection is due to a movement of a cell or a network node in the network.

[0123] FIG.3d shows a flowchart of a method 340 according to an embodiment of the present disclosure.

[0124] At block 342, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission when the wireless communicationdevice is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and the new cell or the new network node in the network.

[0125] At block 344, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission when the wireless communication device is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that the new cell or the new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device.

[0126] At block 346, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission when per area broadcast / groupcast transmission delivery information or configuration for the broadcast / groupcast transmission is adopted and the wireless communication device is still staying in an area associated with the broadcast / groupcast transmission.

[0127] FIG.3e shows a flowchart of a method 350 according to an embodiment of the present disclosure.

[0128] At block 352, optionally, the wireless communication device may not reacquire multicast control channel (MCCH) when the wireless communication device is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that multicast traffic channel (MTCH) configuration does not change or a same MTCH configuration is adopted in different cells or network nodes in the network.

[0129] At block 354, optionally, the wireless communication device may not reacquire MCCH if cell or network node switch or reselection is due to a movement of a cell or a network node in the network.

[0130] At block 356, optionally, the wireless communication device may not reacquire MCCH if the wireless communication device is still staying in an area associated with the broadcast / groupcast transmission and a same delivery information or configuration for the broadcast / groupcast transmission is applied in the area.

[0131] At block 358, optionally, the wireless communication device may reacquire MCCH if a reacquisition condition is met.

[0132] At block 360, optionally, the wireless communication device may discard at least one buffered segment of the broadcast / groupcast transmission if a discarding condition is met.

[0133] In an embodiment, when the wireless communication device is in a RRC connected state, the wireless communication device may perform at least one of steps of methods 400 and 410 of FIGs.4a and 4b.

[0134] FIG.4a shows a flowchart of a method 400 according to an embodiment of the present disclosure.

[0135] At block 402, optionally, the wireless communication device may inform the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states.

[0136] At block 404, optionally, the wireless communication device may assemble at least one buffered segment and / or the at least one received segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment.

[0137] FIG.4b shows a flowchart of a method 410 according to an embodiment of the present disclosure.

[0138] At block 412, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if a same delivery information or configuration for the broadcast / groupcast transmission is applied in different RRC states.

[0139] At block 414, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if different delivery information or configuration for the broadcast / groupcast transmission are applied in different RRC states.

[0140] At block 416, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is different from delivery information or configuration associated with the at least one received segment.

[0141] At block 418, optionally, the wireless communication device may not discard at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment.

[0142] Embodiments

[0143] In an embodiment, the wireless communication device e.g. UE does not discard previously buffered segment(s) of the broadcast / groupcast transmission (e.g. wamingMessageSegment and warning AreaCoordinates Segment (if any)) upon cell / network node (e.g. satellite) switch / reselection due to cell / network node (e.g. satellite) movement, which the wireless communication device could determine based on existing parameters or explicitindication from the NW. The network node (e.g. eNB, gNB, satellite) makes sure the different cells / network nodes serving the same area deliver the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) with the same configuration.

[0144] In an embodiment, the UE does not discard previously buffered segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) when switching / reselecting another cell / network node (e.g. satellite) if it was indicated that the same delivery information / configuration is applied in the old and new cell / node (e.g. satellite).

[0145] In an embodiment, the same delivery information / configuration is applied for a certain broadcast / groupcast transmission (e.g. PWS notification) delivered in a geographic area. The UE does not discard previously buffered segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) if it is still staying in the area associated with the broadcast / groupcast transmission (e.g. PWS notification).

[0146] In an embodiment, the optimization on delivery information / configuration for broadcast / groupcast transmission (e.g. PWS notification) may also be applied to other broadcasted / groupcasted transmission. For instance, for MBS, the UE does not reacquire MCCH when switching / reselecting serving cell / network node (e.g. satellite) if the MTCH configuration included in MCCH does not change unless other MCCH reacquisition condition(s) are met.

[0147] In an embodiment, in case the broadcasted / groupcasted transmission (e.g. PWS notification) occurs when the UE is already in RRC connected state, the NW may deliver the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) with the same delivery information / configuration as used in delivering the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) in the corresponding SIB(-NB) if the UE is able to assemble the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) received in different RRC states, and informs the UE how it delivers the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)). The UE then does not discard the buffered segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) when later enters RRC idle or RRC inactive if the NW adopts the same delivery information / configuration unless the other condition(s) leading to the UE to discard the stored segments of the broadcast / groupcast transmission are met.

[0148] In an embodiment, the UE does not discard previously buffered segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) upon cell / network node (e.g. satellite) switch / reselection if it determines that the cell / network node (e.g. satellite) switch / reselection is due to the movement of the cell / network node (e.g. satellite). The UE could make the determination in one or more of the following ways:• The original serving cell / network node (e.g. satellite) is a Quasi-Earth-fixed cell and no more providing service to the UE. For example, the UE could deduce the original serving cell / network node (e.g. satellite) is a Quasi-Earth-fixed cell in case e.g., none of Earth-moving cell dedicated parameters such as EphemerisParameters (e.g. contle-EphemerisParameters), elevationAngles and movingReferenceLocation are present in the relevant SIB(s). For example, the UE could know the original serving cell / satellite is no more providing service to it if e.g., the cell / satellite switch / reselection occurs after t-Service (indicating the time when the satellite is out of service) of the original serving cell / satellite.• The new serving cell / network node (e.g. satellite) indicates it replaces another cell / network node (e.g. satellite) to provide service in the area originally served by that other cell / network node (e.g. satellite), and the UE is originally served by that other cell / network node (e.g. satellite) and now switches to / reselects the new serving cell / network node (e.g. satellite). This may only apply to Quasi-Earth-fixed cell / network node (e.g. satellite), i.e., Earth-moving cell / satellite will not send such indication.

[0149] Meanwhile, the network node (e.g. satellite, eNB, gNB) makes sure the different cells / network nodes (e.g. satellite) serving the same area deliver the segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) with the same delivery information or configurations, e.g., the same messageidentifier, serialNumber, and the same configuration, e.g., the same segment size. Besides, if one cell / network node (e.g. satellite) has completed delivery of the Nth segment before replacing, the replaced cell / network node (e.g. satellite) may start the delivery from the (N+l)th segment (which is the first segment if Nth segment is the last segment). In this way the UE receives the broadcast / groupcast transmission (e.g. PWS notification) as if the broadcast / groupcast transmission (e.g. PWS notification) is delivered from the same cell / network node (e.g. satellite) unless it switches to / reselects another cell / network node (e.g. satellite) due to its own movement.

[0150] Such mechanism could also be applied to other broadcasted / groupcasted transmission. For instance, for MBS, the network node (e.g. satellite, eNB, gNB) makes sure the different cells / the network nodes (e.g. satellites, eNBs, gNBs) serving the same area deliver the sameMBS service with the same MTCH configuration. The UE does not reacquire MCCH containing MTCH configuration upon cell / network node (e.g. satellite, eNB, gNB) switch / reselection caused by serving cell / network node (e.g. satellite, eNB, gNB) movement unless other MCCH reacquisition condition(s) are met.

[0151] In an embodiment, the cell / network node (e.g. satellite, eNB, gNB) may indicate whether it adopts the same broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) delivery information / configuration (e.g. for a certain PWS notification) as that adopted in another cell / network node (e.g. satellite, eNB, gNB) (which it just replaces to provide service), or it only indicates it replaces another cell / network node (e.g. satellite, eNB, gNB) to provide service in case it adopts the same broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) delivery information / configuration as that adopted in the other cell / network node (e.g. satellite, eNB, gNB). The UE does not discard previously buffered segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) (e.g. for the indicated PWS notification) when switching / reselecting serving cell / network node (e.g. satellite, eNB, gNB) if when receiving such indication.

[0152] Also such mechanism could be applied to other broadcasted / groupcasted transmission. For instance, for MBS, the UE does not reacquire MCCH containing MTCH configuration upon cell / network node (e.g. satellite, eNB, gNB) switch / reselection if it was indicated that the same MTCH configuration is adopted in the different cells / network nodes (e.g. satellites, eNBs, gNBs) unless other MCCH reacquisition condition(s) are met. For mbs-NeighbourCellList included in MCCH which indicates list of neighbour cells providing one or more MBS services that are provided by the current serving cell, a cell / network node (e.g. satellite, eNB, gNB) may indicate whether mbs-NeighbourCellList is updated compared to that indicated in another cell / network node (e.g. satellite, eNB, gNB) (which it just replaces to provide service) or after how long time period / at which time mbs-NeighbourCellList will be updated, the UE does not reacquire MCCH upon cell / network node (e.g. satellite, eNB, gNB) switch / reselection if it determines that mbs-NeighbourCellList does not change unless other MCCH reacquisition condition(s) are met.

[0153] In an embodiment, the broadcasted / groupcasted transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) delivery information / configuration for a certain service (e.g. PWS notification) is kept the same in the geographic area associated with the certain service (e.g. PWS notification). In this way the UE receives the certain service (e.g. PWS notification) as if there is no cell / network node (e.g. satellite, eNB, gNB) movement as long as the UE stays in the geographic area associated with the certain service (e.g. PWS notification). Note that this can work even with earth-movingcell / satellite in which case the geographic area associated with the certain service (e.g. PWS notification) may sometimes be served by more than one cell / network node (e.g. satellite, eNB, gNB), during that period all the relevant cells / network nodes (e.g. satellites, eNBs, gNBs) may deliver the same segment in the geographic area with the same delivery information / configuration.

[0154] The cell / network node (e.g. satellite, eNB, gNB) may indicate whether it adopts per area broadcasted / groupcasted transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) delivery information / configuration for a certain service (e.g. PWS notification). The UE does not discard previously buffered segments of the broadcasted / groupcasted transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) for the indicated certain service (e.g. PWS notification) if receiving such indication and still staying in the area associated with the indicated certain service (e.g. PWS notification) (even the UE switches / reselects serving cell / network node (e.g. satellite, eNB, gNB)).

[0155] Similarly such mechanism could also be applied to other broadcasted / groupcasted transmission. For instance, for MBS the MTCH configuration for delivering a MBS service in that MTCH may be kept the same in the geographic area associated with the MBS service. The UE does not reacquire MCCH if it is indicated per area MTCH configuration for some MBS services is applied and it is not staying in the service area associated with a MBS service it is interested in or receiving and not belonging to the indicated service areas unless other MCCH reacquisition condition(s) are met.

[0156] In an embodiment, after switching RRC state or switching / reselecting serving cell / network node (e.g. satellite, eNB, gNB), the UE first tries to receive a segment of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) without discarding the stored segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) if the delivery information (e.g. messageidentifier, serialNumber, etc.) and the configuration (e.g. the segment size) associated with the received segments (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) is different from that associated with the stored ones, the UE discards the stored segments (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)).

[0157] FIG.5a shows a flowchart of a method 500 according to an embodiment of the present disclosure.

[0158] At block 502, optionally, the wireless communication device may determine cell or network node switch or reselection is due to a movement of a cell or a network node in the network.

[0159] In an embodiment, said determining may be based on at least one of:• a cell or a network node in the network is a Quasi-Earth-fixed cell and no more providing service to the wireless communication device, or• a new cell or a new network node in the network indicates that it replaces the old cell or the old network node in an area originally served by the old cell or the old network node.

[0160] At block 504, optionally, the wireless communication device may receive, from the network, an instruction of the network.

[0161] At block 506, optionally, the wireless communication device may receive, from the network, a message informing the wireless communication device whether cell or network node switch or reselection is due to a movement of a cell or a network node in the network.

[0162] At block 508, optionally, the wireless communication device may receive, from the network, a message informing the wireless communication device that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and the new cell or the new network node in the network.

[0163] FIG.5b shows a flowchart of a method 510 according to an embodiment of the present disclosure.

[0164] At block 512, optionally, the wireless communication device may receive, from the network, a message informing the wireless communication device that the new cell or the new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device.

[0165] At block 514, optionally, the wireless communication device may receive, from the network, a message informing the wireless communication device that the MTCH configuration does not change or the same MTCH configuration is adopted in different cells or network nodes in the network.

[0166] At block 516, optionally, the wireless communication device may receive, from the network, a message informing the wireless communication device how the network delivers the broadcast / groupcast transmission.

[0167] FIGs.6, 7a, 7b and 7c show flowcharts of methods according to embodiments of the present disclosure, which may be performed by an apparatus implemented in or at or as a network node or communicatively coupled to the network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the methods as well asmeans or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in an embodiment, the description thereof is omitted in other embodiment for brevity.

[0168] FIG.6 shows a flowchart of a method 600 according to an embodiment of the present disclosure.

[0169] At block 602, when a wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing a reception of the broadcast / groupcast transmission, the network node may prioritize a reception of the broadcast / groupcast transmission.

[0170] The network node may prioritize a reception of the broadcast / groupcast transmission in various ways. For example, the network node may ignore or delay any other action, instruction, RRC state change, etc. to be sent to the wireless communication device until the wireless communication device has received the broadcast / groupcast transmission, or all segments or a part of segments of the broadcast / groupcast transmission.

[0171] For example, the network node may delay at least one of indicating the wireless communication device to perform a random access procedure, indicating the wireless communication device to enter an RRC connected state, indicating the wireless communication device to not discard at least one buffered segment of the broadcast / groupcast transmission, indicating the wireless communication device to not reacquire multicast control channel (MCCH), indicating the wireless communication device that the new cell or the new network node adopts the same delivery information or configuration for the broadcast / groupcast transmission as that adopted in the old cell or the old network node etc.

[0172] In an embodiment, when the wireless communication device in a radio resource control (RRC) idle state or an RRC inactive state is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered, the network node may perform at least one of steps of methods 700 and 710 of FIGs.7a and 7b.

[0173] FIG.7a shows a flowchart of a method 700 according to an embodiment of the present disclosure.

[0174] At block 702, optionally, the network node may receive, from the wireless communication device, a message indicating that the wireless communication device is receiving or going to receive a type of the broadcast / groupcast transmission and send, to the wireless communication device, an instruction of the network.

[0175] In an embodiment, the instruction of the network may comprise at least one of:• instruct the wireless communication device to terminate a random access procedure and continue receiving the broadcast / groupcast transmission in RRC idle or RRC inactive until thebroadcast / groupcast transmission is received or for a time period or until the wireless communication device is paged by the network to enter a RRC connected state, or• deliver the type of the broadcast / groupcast transmission to the wireless communication device using a dedicated signaling after the wireless communication device enters a RRC connected state.

[0176] At block 704, optionally, the network node may receive, from the wireless communication device, a message informing the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states and deliver, to the wireless communication device, at least one segment of the broadcast / groupcast transmission with a same delivery information or configuration in different RRC states.

[0177] At block 706, optionally, the network node may send, to the wireless communication device, a message informing the wireless communication device whether cell or network node switch or reselection is due to a movement of a cell or a network node in the network.

[0178] At block 708, optionally, the network node may send, to the wireless communication device, a message informing the wireless communication device that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and a new cell or a new network node in the network.

[0179] FIG.7b shows a flowchart of a method 710 according to an embodiment of the present disclosure.

[0180] At block 712, optionally, the network node may send, to the wireless communication device, a message informing the wireless communication device that a new cell or a new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device in case the new cell or the new network node adopts the same delivery information or configuration for the broadcast / groupcast transmission as that adopted in the old cell or the old network node.

[0181] At block 714, optionally, the network node may send, to the wireless communication device, a message informing the wireless communication device that the multicast traffic channel (MTCH) configuration does not change or the same MTCH configuration is adopted in different cells or network nodes in the network.

[0182] At block 716, optionally, the network node may send, to the wireless communication device, a message informing the wireless communication device how the network delivers the broadcast / groupcast transmission.

[0183] In an embodiment, when the wireless communication device is in a RRC connected state, the network node may perform at least one of steps of methods 720 of FIG.7c.

[0184] FIG.7c shows a flowchart of a method 720 according to an embodiment of the present disclosure.

[0185] At block 722, optionally, the network node may receive, from the wireless communication device, a message informing the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states.

[0186] At block 724, optionally, the network node may deliver, to the wireless communication device, at least one segment of the broadcast / groupcast transmission with a same delivery information or configuration in different RRC states and / or an area associated with the broadcast / groupcast transmission.

[0187] According to various embodiments, it proposes methods to properly receive broadcast / groupcast transmission (e.g. PWS notification, MBS service) in different RRC states (e.g. RRC idle or RRC inactive or RRC connected state) and avoid the negative impact from RRC state switch. Meanwhile, methods are proposed to avoid UE discarding previously stored segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) when the UE switches RRC state and / or switches / reselects serving cell / network node as long as the UE can assemble the newly received segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) with the stored ones.

[0188] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, with the proposed solutions, the impact of RRC state switch can be avoided which ensures the broadcast / groupcast transmission (e.g. PWS notification) can be received in time. In some embodiments herein, unnecessary discarding of stored segments of the broadcast / groupcast transmission (e.g. wamingMessageSegment and wamingAreaCoordinatesSegment (if any)) is avoided which improves the delivery efficiency, saves UE energy and reduces the delivery time. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0189] FIG.8 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure. For example, the network node, or wireless communication device described above may be implemented as or through the apparatus 800.

[0190] The apparatus 800 comprises at least one processor 821, such as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The apparatus 800 may comprise a transmitter TX and receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executedon the associated processor 821, enable the apparatus 800 to operate in accordance with the embodiments of the present disclosure. A combination of the at least one processor 821 and the at least one MEM 822 may form processing means 825 adapted to implement various embodiments of the present disclosure.

[0191] Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 821, software, firmware, hardware or in a combination thereof.

[0192] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.

[0193] The processor 821 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.

[0194] In an embodiment where the apparatus is implemented as or at the network node, the memory 822 contains instructions executable by the processor 821, whereby the network node operates according to any of the methods performed by the network node as described above.

[0195] In an embodiment where the apparatus is implemented as or at the wireless communication device, the memory 822 contains instructions executable by the processor 821, whereby the wireless communication device operates according to any of the methods performed by the wireless communication device as described above.

[0196] With function units, the network node or the wireless communication device may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the network node or the wireless communication device in the communication system. The introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.

[0197] Further, the exemplary overall commutation system including the terminal device (e.g. wireless communication device described above) and the network node (e.g. the network node described above) will be introduced as below.

[0198] FIG.9 shows an example of a communication system 9100 in accordance with some embodiments.

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

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

[0201] In some embodiments, the telecommunication network includes a non-terrestrial network, NTN. Unless otherwise described herein, embodiments applicable for NTN may be implanted according to the following clauses. An NTN is telecommunication network where the radio access payload is conveyed via satellite to a ground station. E-UTRAN supports radio access over non-terrestrial networks for BL UEs, UEs in enhanced coverage and NB-IoT UEs.Support for non-terrestrial networks encompasses platforms that provide radio access through Geosynchronous orbits (GSO), Non-Geosynchronous Orbit (NGSO), which includes Low-Earth Orbit (LEO) and Medium Earth Orbit (MEO) or High Altitude Platform Systems (HAPS). Another example of a Non-Terrestrial Network (NTN) provides non-terrestrial NR access to the UE by means of an NTN payload and an NTN Gateway, a service link between the NTN pay load and a UE, and a feeder link between the NTN Gateway and the NTN payload exists. An access network may include an NTN access network such as the 3GPP Satellite Access Node (SAN) which comprises Non-NTN infrastructure base station functions (e.g. eNB / gNB) a terrestrial Gateway which provides the interface to the feeder link to an NTN payload RF node. In some embodiments a network node comprises a SAN, wherein the location of base station functions for a network node (described above for the general terrestrial access) vary between residing in the terrestrial access network node part of the SAN and the NTN Payload RF node functions depending on the supported architecture. One example of NTN architecture is called bent pipe or transparent architecture where the radio frequency processing function (transceiver) on a satellite platform is interconnected with a terrestrial base station, also known as transparent architecture, and the NTN payload is passed transparently, no unpacking. Another example of NTN architecture is called regenerative architecture, where part or all of the eNB / gNB can be in the satellite.

[0202] In some examples a SAN includes an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).

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

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

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

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

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

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

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

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

[0211] The hub 9114 may have a constant / persistent or intermitent connection to the network node 9110b. The hub 9114 may also allow for a different communication scheme and / or schedule between the hub 9114 and UEs (e.g., UE 9112c and / or 9112d), and between the hub 9114 and the core network 9106. In other examples, the hub 9114 is connected to the core network 9106 and / or one or more UEs via a wired connection. Moreover, the hub 9114 may be configured to connect to an M2M service provider over the access network 9104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 9110 while still connected via the hub 9114 via a wired or wireless connection. In some embodiments, the hub 9114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 9110b. In other embodiments, the hub 9114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 9110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0212] FIG.10 shows a UE 1000 in accordance with some embodiments. The UE 1000 presents additional details of some embodiments of the UE 9112 of FIG.9. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0214] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG.10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0215] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1002 may include multiple central processing units (CPUs).

[0216] In the example, the input / output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

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

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

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

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

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

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

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

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

[0227] FIG.11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU), components of a satellite access network (SAN) (e.g, terrestrial base station, gateway, NTN payload RF function).

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

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

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

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

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

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

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

[0235] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

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

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

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

[0239] Embodiments of the network node 1100 may include additional components beyond those shown in FIG.11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100. In some embodiments providing a core network node, such as core network node 9108 of FIG. 9, some components, such as the radio front-end circuitry 1118 and the RF transceiver circuitry 1112 may be omitted.

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

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

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

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

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

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

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

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

[0248] The term unit or module may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / orelectronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0249] According to an aspect of the disclosure it is provided a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0250] According to an aspect of the disclosure it is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0251] In addition, the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. The computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.

[0252] The techniques described herein may be implemented by various means so that an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software, implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

[0253] Exemplary embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatuses. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.

[0254] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0255] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any implementation or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular implementations. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[0256] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The above described embodiments are given for describing rather than limiting the disclosure, and it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the disclosure as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the disclosure and the appended claims. The protection scope of the disclosure is defined by the accompanying claims.References1. 3GPP TR 38.811 V15.4.0, Study on New Radio (NR) to support non-terrestrial networks 2. 3GPP TR 38.821 V16.2.0, Solutions for NR to support non-terrestrial networks3. RP-221806, Revised WID on loT NTN enhancements.4. RP-220208, Solutions for NR to support non-terrestrial networks (NTN).5. RP-223519, Revised WID on loT NTN enhancements

Claims

1. WHAT IS CLAIMED IS:

1. A method (200) performed by a wireless communication device, the method comprising: when the wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing (202) a reception of the broadcast / groupcast transmission.

2. The method according to claim 1, further comprising:when the wireless communication device in a radio resource control (RRC) idle state or an RRC inactive state is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered, performing at least one of:ignoring (302) an instruction in a paging message which informs the wireless communication device to enter an RRC connected state;delaying (304) entering an RRC connected state when the wireless communication device is triggered to enter the RRC connected state;delaying (306) entering an RRC connected state until the wireless communication device has received the broadcast / groupcast transmission or for a time period when the wireless communication device is triggered to enter the RRC connected state;delaying (308) performing a random access procedure when the wireless communication device is triggered to perform the random access procedure;delaying (310) performing a random access procedure until the wireless communication device has received the broadcast / groupcast transmission or for a time period when the wireless communication device is triggered to perform the random access procedure;indicating (322) to the network that the wireless communication device is receiving or going to receive a type of the broadcast / groupcast transmission and following an instruction of the network;informing (324) the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states;not discarding (326) at least one buffered segment of the broadcast / groupcast transmission if a same delivery information or configuration for the broadcast / groupcast transmission is applied in different RRC states;discarding (328) at least one buffered segment of the broadcast / groupcast transmission if different delivery information or configuration for the broadcast / groupcast transmission are applied in different RRC states;assembling (332) at least one buffered segment and / or the at least one receivedsegment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment;discarding (334) at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is different from delivery information or configuration associated with the at least one received segment;not discarding (336) at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment;not discarding (338) at least one buffered segment of the broadcast / groupcast transmission if cell or network node switch or reselection is due to a movement of a cell or a network node in the network;not discarding (342) at least one buffered segment of the broadcast / groupcast transmission when the wireless communication device is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and the new cell or the new network node in the network;not discarding (344) at least one buffered segment of the broadcast / groupcast transmission when the wireless communication device is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that the new cell or the new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device;not discarding (346) at least one buffered segment of the broadcast / groupcast transmission when per area broadcast / groupcast transmission delivery information or configuration for the broadcast / groupcast transmission is adopted and the wireless communication device is still staying in an area associated with the broadcast / groupcast transmission;not reacquiring (352) multicast control channel (MCCH) when the wireless communication device is switched to or reselects a new cell or a new network node in the network if the wireless communication device was indicated that multicast traffic channel (MTCH) configuration does not change or a same MTCH configuration is adopted in different cells or network nodes in the network;49not reacquiring (354) MCCH if cell or network node switch or reselection is due to a movement of a cell or a network node in the network;not reacquiring (356) MCCH if the wireless communication device is still staying in an area associated with the broadcast / groupcast transmission and a same delivery information or configuration for the broadcast / groupcast transmission is applied in the area;reacquiring (358) MCCH if a reacquisition condition is met; ordiscarding (360) at least one buffered segment of the broadcast / groupcast transmission if a discarding condition is met.

3. The method according to any of claims 2, wherein the instruction of the network comprises at least one of:instructing the wireless communication device to terminate a random access procedure and continue receiving the broadcast / groupcast transmission in RRC idle or RRC inactive until the broadcast / groupcast transmission is received or for a time period or until the wireless communication device is paged by the network to enter a RRC connected state, ordelivering the type of the broadcast / groupcast transmission to the wireless communication device using a dedicated signaling after the wireless communication device enters a RRC connected state.

4. The method according to any of claims 1-3, further comprising:when the wireless communication device is in a RRC connected state, performing at least one of:informing (402) the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states;assembling (404) at least one buffered segment and / or the at least one received segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment;not discarding (412) at least one buffered segment of the broadcast / groupcast transmission if a same delivery information or configuration for the broadcast / groupcast transmission is applied in different RRC states;discarding (414) at least one buffered segment of the broadcast / groupcast transmission if different delivery information or configuration for the broadcast / groupcast transmission are applied in different RRC states;discarding (416) at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is different from delivery information or configuration associated with the at least50one received segment; ornot discarding (418) at least one buffered segment of the broadcast / groupcast transmission if delivery information or configuration associated with the at least one buffered segment is same as delivery information or configuration associated with the at least one received segment.

5. The method according to any of claims 1-4, further comprising at least one of: determining (502) cell or network node switch or reselection is due to a movement of a cell or a network node in the network;receiving (504), from the network, an instruction of the network;receiving (506), from the network, a message informing the wireless communication device whether cell or network node switch or reselection is due to a movement of a cell or a network node in the network;receiving (508), from the network, a message informing the wireless communication device that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and the new cell or the new network node in the network;receiving (512), from the network, a message informing the wireless communication device that the new cell or the new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device;receiving (514), from the network, a message informing the wireless communication device that the MTCH configuration does not change or the same MTCH configuration is adopted in different cells or network nodes in the network; orreceiving (516), from the network, a message informing the wireless communication device how the network delivers the broadcast / groupcast transmission.

6. The method according to claim 5, wherein said determining is based on at least one of: a cell or a network node in the network is a Quasi-Earth-fixed cell and no more providing service to the wireless communication device, ora new cell or a new network node in the network indicates that it replaces the old cell or the old network node in an area originally served by the old cell or the old network node.

7. The method according to any of claims 1-6, wherein the broadcast / groupcast transmission comprises at least one of:time critical Public Warning System (PWS) notification,non-time critical PWS notification, ora Multicast / Broadcast Services (MBS) service.

8. The method according to any of claims 1-7, wherein51the network node comprises a satellite based radio access network node, and / or the wireless communication device comprises a Narrowband Internet of Things (NB-IoT) user equipment, and / orthe network comprises a non-terrestrial network (NTN) , and / orthe wireless communication device is served by a satellite based network node in the NTN.

9. A method (600) performed by a network node, the method comprising:when a wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritizing (602) a reception of the broadcast / groupcast transmission.

10. The method according to claim 9, further comprising:when the wireless communication device in a radio resource control (RRC) idle state or an RRC inactive state is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered, performing at least one of:receiving (702), from the wireless communication device, a message indicating that the wireless communication device is receiving or going to receive a type of the broadcast / groupcast transmission and sending, to the wireless communication device, an instruction of the network;receiving (704), from the wireless communication device, a message informing the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states and delivering, to the wireless communication device, at least one segment of the broadcast / groupcast transmission with a same delivery information or configuration in different RRC states;sending (706), to the wireless communication device, a message informing the wireless communication device whether cell or network node switch or reselection is due to a movement of a cell or a network node in the network;sending (708), to the wireless communication device, a message informing the wireless communication device that a same delivery information or configuration for the broadcast / groupcast transmission is applied in both an old cell or an old network node in the network and a new cell or a new network node in the network;sending (712), to the wireless communication device, a message informing the wireless communication device that a new cell or a new network node replaces an old cell or an old network node in the network to provide a service to the wireless communication device in case the new cell or the new network node adopts the same delivery information or configuration for the broadcast / groupcast transmission as that adopted in the old cell or the old network node;sending (714), to the wireless communication device, a message informing the wireless communication device that the multicast traffic channel (MTCH) configuration does not change or the same MTCH configuration is adopted in different cells or network nodes in the network; orsending (716), to the wireless communication device, a message informing the wireless communication device how the network delivers the broadcast / groupcast transmission.

11. The method according to claim 10, wherein the instruction of the network comprises at least one of:instructing the wireless communication device to terminate a random access procedure and continue receiving the broadcast / groupcast transmission in RRC idle or RRC inactive until the broadcast / groupcast transmission is received or for a time period or until the wireless communication device is paged by the network to enter a RRC connected state, ordelivering the type of the broadcast / groupcast transmission to the wireless communication device using a dedicated signaling after the wireless communication device enters a RRC connected state.

12. The method according to any of claims 9-11, wherein when the wireless communication device is in a RRC connected state, the method further comprises:receiving (722), from the wireless communication device, a message informing the network that the wireless communication device is able to assemble segments of the broadcast / groupcast transmission received in different RRC states; and / ordelivering (724), to the wireless communication device, at least one segment of the broadcast / groupcast transmission with a same delivery information or configuration in different RRC states and / or an area associated with the broadcast / groupcast transmission.

13. The method according to any of claims 9-12, wherein the broadcast / groupcast transmission comprises at least one of:time critical Public Warning System (PWS) notification,non-time critical PWS notification, ora Multicast / Broadcast Services (MBS) service.

14. The method according to any of claims 9-13, whereinthe network node comprises a satellite based radio access network node, and / or the wireless communication device comprises a Narrowband Internet of Things (NB-IoT) user equipment, and / orthe network comprises a non-terrestrial network (NTN), and / orthe wireless communication device is served by a satellite based network node in the NTN.

15. A wireless communication device (800), comprising:a processor (821); anda memory (822) coupled to the processor (821), said memory (822) containing instructions executable by said processor (821), whereby said wireless communication device (800) is operative to:when the wireless communication device is receiving a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritize a reception of the broadcast / groupcast transmission.

16. The wireless communication device according to claim 15, wherein the wireless communication device is further operative to perform the method of any one of claims 2 to 8.

17. A network node (800), comprising:a processor (821); anda memory (822) coupled to the processor (821), said memory (822) containing instructions executable by said processor (821), whereby said network node (800) is operative to:when a wireless communication device is receive a broadcast / groupcast transmission or is indicated there is a broadcast / groupcast transmission being delivered or to be delivered in a network, prioritize a reception of the broadcast / groupcast transmission.

18. The network node according to claim 17, wherein the network node is further operative to perform the method of any one of claims 10 to 14.

19. A computer-readable storage medium storing instructions 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 14.

20. A computer program product comprising instructions 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 14.54

Images