Devices and methods of communication
Patent Information
- Application Number
- PCT/CN2024/080151
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-03-05
- Publication Date
- 2025-10-02
Smart Images

Figure CN2024080151_02102025_PF_FP_ABST
Abstract
Description
DEVICES AND METHODS OF COMMUNICATIONFIELD
[0001] Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication for mobility management.BACKGROUND
[0002] Currently, a communication of aerial user equipment (UE) such as unmanned aerial vehicle (UAV) is highly concerned. Mobility management of the aerial UE is still incomplete and needs to be further developed.SUMMARY
[0003] In general, embodiments of the present disclosure provide methods, devices and computer storage media of communication for mobility management.
[0004] In a first aspect, there is provided a terminal device. The terminal device comprises a processor configured to cause the terminal device to: receive, from a network device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device; determine a first configuration in the set of configurations based on a location of the terminal device; and perform the conditional cell change or the idle or inactive measurement based on the first configuration.
[0005] In a second aspect, there is provided a network device. The network device comprises a processor configured to cause the network device to: transmit, to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device.
[0006] In a third aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device and from a network device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device; determining a first configuration in the set of configurations based on a location of the terminal device; and performing the conditional cell change or the idle or inactive measurement based on the first configuration.
[0007] In a fourth aspect, there is provided a method of communication. The method comprises: transmitting, at a network device and to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device.
[0008] In a fifth aspect, there is provided a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to the third or fourth aspect of the present disclosure.
[0009] Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:
[0011] Fig. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented;
[0012] Fig. 2 illustrates a schematic diagram illustrating a process for communication according to some embodiments of the present disclosure;
[0013] Fig. 3 illustrates a schematic diagram illustrating an example of configuration release according to some embodiments of the present disclosure;
[0014] Fig. 4 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure;
[0015] Fig. 5 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure; and
[0016] Fig. 6 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
[0017] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0018] Principle of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0019] 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.
[0020] As used herein, the term ‘communication network’ refers to a network following any suitable communication standards, such as new radio (NR) , long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band Internet of things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5.5G, 5G-Advanced networks, or the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0021] As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, Internet of things (IoT) devices, ultra-reliable and low latency communications (URLLC) devices, Internet of everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure / network, devices for integrated access and backhaul (IAB) , small data transmission (SDT) , mobility, multicast and broadcast services (MBS) , positioning, dynamic / flexible duplex in commercial networks, reduced capability (RedCap) , space borne vehicles or air borne vehicles in non-terrestrial networks (NTN) including Satellites and high altitude platforms (HAPs) encompassing unmanned aircraft systems (UAS) , extended reality (XR) devices including different types of realities such as augmented reality (AR) , mixed reality (MR) and virtual reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast / broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple subscriber identity module (SIM) as known as multi-SIM. The term ‘terminal device’ can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
[0022] The term ‘network device’ refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , network-controlled repeaters, and the like.
[0023] The terminal device or the network device may have artificial intelligence (AI) or machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
[0024] The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed / unlicensed / shared spectrum. The terminal device may have more than one connections with the network devices under MR-DC application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
[0025] The network device may have the function of network energy saving (NES) , SON or minimization of drive tests (MDT) . The terminal may have the function of power saving.
[0026] The embodiments of the present disclosure may be performed in test equipment, e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
[0027] In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
[0028] As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
[0029] In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0030] In the context of the present disclosure, the term ‘a connected state’ may be interchangeably used with ‘an RRC_CONNECTED state’ or ‘a connected mode’ , the term ‘an idle state’ may be interchangeably used with ‘an RRC_IDLE state’ or ‘an idle mode’ , and the term ‘an inactive state’ may be interchangeably used with ‘an RRC_INACTIVE state’ or ‘an inactive mode’ .
[0031] In the context of the present disclosure, the term ‘waypoint’ may refer to a time or location point on a flightpath of a terminal device. The term ‘a time stamp’ may refer to a planned arriving time or actual arrived time. The term ‘a time indicated by a time stamp’ may refer to a timing or a period of time related to the timing (e.g., a period of time before or after the timing) . In the context of the present disclosure, a suffix ‘-enh’ refers to enhancements on existing information.
[0032] Embodiments of the present disclosure provide a solution of communication for mobility management. The solution may be applied for mobility management of any terminal devices, especially for aerial UE such as UAV. In the solution, a network device may transmit, to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement. A configuration in the set of configurations is associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device. The terminal device may determine a first configuration in the set of configurations based on a location of the terminal device and perform the conditional cell change or the idle or inactive measurement based on the first configuration. In this way, mobility management may be enhanced, especially for aerial UE such as UAV.
[0033] Principle and example embodiments of the present disclosure will be described in details below with reference to the accompanying drawings.
[0034] EXAMPLE OF COMMUNICATION NETWORK
[0035] Fig. 1 shows an example communication network 100 in which example embodiments of the present disclosure can be implemented. The communication network 100 may include terminal device 110 and network devices 120 and 130. Each of the network devices 120 and 130 may provide one or more cells to serve the terminal device 110 or any other terminal devices not shown. In the example of Fig. 1, the network device 120 provides a serving cell 121 at an altitude above the network device 120, and the network device 130 provides a serving cell 131 at an altitude above the network device 130.
[0036] For convenience, the following description will be given by assuming that the terminal device 110 is within the serving cell 121 of the network device 120. In the example of Fig. 1, the terminal device 110 is shown as an aerial terminal device. It is to be understood that embodiments of the present disclosure also apply to terrestrial terminal device.
[0037] In case that the terminal device 110 is within the serving cell 121 of the network device 120, the terminal device 110 may communicate with the network device 120 via a Uu interface such as a service link or radio link. Communication in a direction from a terminal device 110 towards the network device 120 is referred to as UL communication, while communication in a reverse direction from the network device 120 towards the terminal device 110 is referred to as DL communication. The network device 120 and the network device 130 may communicate with each other via a Xn interface.
[0038] The communications in the communication network 100 may conform to any suitable standards including, but not limited to, global system for mobile communications (GSM) , long term evolution (LTE) , LTE-evolution, LTE-advanced (LTE-A) , new radio (NR) , wideband code division multiple access (WCDMA) , code division multiple access (CDMA) , GSM EDGE radio access network (GERAN) , machine type communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-advanced networks, or the sixth generation (6G) networks.
[0039] It is to be understood that the numbers and connections of network devices, terminal devices and serving cells are only for the purpose of illustration without suggesting any limitations. The communication network 100 may include any suitable network devices, terminal devices and serving cells adapted for implementing embodiments of the present disclosure.
[0040] In some embodiments, the terminal device 110 may establish a dual connection (i.e., simultaneous connection) with two network devices. For example, the network device 120 may serve as a master node (MN) , and the network device 130 may serve as a secondary node (SN) . Although only the serving cell 121 is shown, the network device 120 (i.e., MN) may provide multiple serving cells, and these serving cells may form a master cell group (MCG) for the terminal device 110. For example, the serving cell 121 is a primary cell (i.e., PCell) in the MCG. Although only the serving cell 131 is shown, the network device 130 (i.e., SN) may provide multiple serving cells, and these serving cells may form a secondary cell group (SCG) for the terminal device 110. For example, the serving cell 131 is a primary cell (i.e., PSCell) in the SCG. The MN or SN may communicate with the terminal device 120 via a channel such as a wireless communication channel. The MN may communicate with the SN via a Xn interface.
[0041] In some embodiments, upon determination that an execution condition for a cell change is fulfilled, the terminal device 110 may perform the cell change. This procedure may be called as a conditional cell change. For example, upon determination that an execution condition for a PCell change from the MN to a further MN (not shown) is fulfilled, the terminal device 110 may perform the PCell change. This procedure may be called as a conditional SpCell change, conditional PCell change or conditional handover (CHO) . In another example, upon determination that an execution condition for a PSCell change from the SN to a further SN (not shown) is fulfilled, the terminal device 110 may perform the PSCell change. This procedure may be called as a conditional PSCell change.
[0042] In some embodiments, the terminal device 110 in an idle or inactive state may perform an idle or inactive measurement, and report, to a network (NW) upon entering a connected state, results of the idle or inactive measurement if needed.
[0043] Embodiments of the present disclosure provide solutions of enhancing the conditional cell change and the idle or inactive measurement. The solutions will be described in detail with reference to Figs. 2 to 3B.
[0044] EXAMPLE IMPLEMENTATION OF MOBILITY MANAGEMENT
[0045] Fig. 2 illustrates a schematic diagram illustrating a process 200 for communication according to embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to Fig. 1. The process 200 may involve the terminal device 110 and the network device 120 as illustrated in Fig. 1. It is assumed that the terminal device 110 is served by the network device 120.
[0046] As shown in Fig. 2, the terminal device 110 may transmit 210, to the network device 120, information of waypoints in a flightpath of the terminal device 110. In some embodiments, information of a waypoint may comprise at least one of the following: an index of the waypoint, a location of the waypoint, or a time stamp of the waypoint.
[0047] In some embodiments, the terminal device 110 may transmit available information of the flightpath (i.e., availability notification) to the network device 120, e.g., by a RRC message such as a RRC reconfiguration complete message, a RRC reestablishment complete message, or a UE assistance information (UAI) message. The network device 120 may request the terminal device 110 for the flightpath, for example, based on the available information. In some embodiments, the transmission of the available information of flightpath in UAI may be trigged by a 1 second mechanism. That is, the terminal device 110 may initiate the transmission of UAI again to a target cell if a UAI transmission was initiated during the last 1 second before receiving a reconfiguration with sync.
[0048] In some embodiments, the terminal device 110 may exclude the available information of the flightpath in a RRC reconfiguration complete message or a RRC reestablishment complete message if a UAI transmission indicating the available information of the flightpath was initiated during the last T time period before receiving the reconfiguration with sync. That is, the terminal device 110 may only indicate availability of the flightpath information in a RRC reconfiguration complete message or a RRC reestablishment complete message if no UAI transmission indicating the available information of the flightpath has been initiated during the last T time period (for example, T may be 0.5s, 1s, or 2s) before receiving the reconfiguration with sync.
[0049] For illustration, an example flightpath information report may be described as below.
[0050] 2> if the UE has (updated) flight path information available:
[0051] 3> if the UE had not provided a flight path information since last entering RRC_CONNECTED state; or
[0052] 3> if at least one waypoint or a timestamp corresponding to a waypoint location that was not previously provided since last entering RRC_CONNECTED state is available; or
[0053] 3> if at least one upcoming waypoint or a timestamp corresponding to a waypoint location that was previously provided since last entering RRC_CONNECTED state is being removed; or
[0054] 3> if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than the distance threshold configured by flightPathUpdateDistanceThr; or
[0055] 3> if flightPathUpdateTimeThr is configured and for at least one waypoint, the time difference between the previously provided timestamp and the new timestamp, if available, is more than the time threshold configured by flightPathUpdateTimeThr: or
[0056] 3> if the UE had not indicated availability of flight path information in UAI transmission during the last T time period;
[0057] 4> include flightPathInfoAvailable in RRCReconfigurationComplete message.
[0058] In this example, an information element (IE) ‘flightPathUpdateDistanceThr’ denotes a distance threshold for flightpath update, an IE ‘flightPathUpdateTimeThr’ denotes a time threshold for flightpath update, and an IE ‘flightPathInfoAvailable’ denotes availability of flightpath information.
[0059] For illustration, another example flightpath information report may be described as below.
[0060] In this example, an IE ‘WayPoint’ denotes a waypoint in a flightpath, an IE ‘wayPointIndex’ denotes an index of the waypoint, an IE ‘wayPointLocation’ denotes a location of the waypoint, and an IE ‘timeStamp’ denotes a time stamp of the waypoint.
[0061] In some embodiments, the terminal device 110 may report an addition or modification or cancel of a waypoint in the flightpath, e.g., by indicating an index of the waypoint. With a setting of an index of a waypoint, delta update of flightpath information may be supported. For example, the terminal device 110 may update part of the flightpath information by indicating the index of the waypoint which is different from that last reported.
[0062] Continuing to refer to Fig. 2, the network device 120 may transmit 220, to the terminal device 110, a set of configurations for a mobility related operation. In some embodiments, the mobility related operation may be a conditional cell change, e.g., conditional SPCell change, conditional PCell change or conditional PSCell change. In some embodiments, the mobility related operation may be an idle or inactive measurement. It is to be understood that any other suitable mobility related operations may also be feasible.
[0063] In some embodiments, a configuration in the set of configurations may be associated with a waypoint in a flightpath of the terminal device 110. In some embodiments, the network device 120 may transmit, to the terminal device 110, information of the waypoint comprising at least one of an index, location or time stamp of the waypoint. In some embodiments, the configuration may be mapped to the at least one of the index, location or time stamp of the waypoint.
[0064] In some embodiments, a configuration in the set of configurations may be associated with a waypoint group in a flightpath of the terminal device 110. The waypoint group may comprise one or multiple waypoints (i.e., a set of waypoints) . In some embodiments, the network device 120 may transmit information of the waypoint group to the terminal device 110. In some embodiments, the configuration may be mapped to the information of the waypoint group.
[0065] In some embodiments, the information of the waypoint group may comprise an index of the waypoint group. For example, the waypoint group may be indicated by a set of indexes of waypoints. For example, the waypoint group may be predefined and may be indicated by the index of the waypoint group.
[0066] In some embodiments, the information of the waypoint group may comprise an index of a first waypoint as a starting point of the waypoint group. In some embodiments, the waypoint group may comprise a set of waypoints within a first time duration since a time indicated by a time stamp of the first waypoint. In some embodiments, the information of the waypoint group may further comprise the first time duration. Alternatively, the first time duration may be predefined.
[0067] In some embodiments, the waypoint group may comprise a set of waypoints within a first distance from a location of the first waypoint. In some embodiments, the information of the waypoint group may further comprise the first distance. Alternatively, the first distance may be predefined.
[0068] In some embodiments, the information of the waypoint group may comprise an index of a second waypoint as an ending point of the waypoint group. In some embodiments, the waypoint group may comprise a set of waypoints within a second time duration before a time indicated by a time stamp of the second waypoint. In some embodiments, the information of the waypoint group may further comprise the second time duration. Alternatively, the second time duration may be predefined.
[0069] In some embodiments, the waypoint group may comprise a set of waypoints within a second distance before a location of the second waypoint. In some embodiments, the information of the waypoint group may further comprise the second distance. Alternatively, the second distance may be predefined.
[0070] In some embodiments, the information of the waypoint group may comprise both the index of the first waypoint and the index of the second waypoint. In some embodiments, the waypoint group may comprise a set of waypoints between the first waypoint and the second waypoint. For example, the set of waypoints may be within a time duration between the time indicated the time stamp of the first waypoint and the time indicated by the time stamp of the second waypoint. Alternatively or additionally, the set of waypoints may be within a distance between the location of the first waypoint and the location of the second waypoint.
[0071] For illustration, an example configuration of a waypoint group may be described as below.
[0072] In this example, an IE ‘wayPointRange’ denotes a waypoint group, an IE ‘RangeIndex-enh’ denotes an index of the waypoint group, an IE ‘startPoint’ denotes a starting point of the waypoint group, and an IE ‘endPoint’ denotes an ending point of the waypoint group.
[0073] In some embodiments, a configuration in the set of configurations may be associated with an altitude of the terminal device 110. In some embodiments, the configuration may be mapped to an altitude value.
[0074] In some embodiments, a configuration in the set of configurations may be associated with an altitude range of the terminal device 110. In some embodiments, the network device 120 may transmit information of the altitude range to the terminal device 110. In some embodiments, the information of the altitude range may comprise at least one of an index of the altitude range, a minimum altitude value, a maximum altitude value, or a hysteresis value.
[0075] In some embodiments, the altitude range may de predefined and may be indicated by the index of the altitude range.
[0076] In some embodiments, the altitude range may comprise altitude values within a first range above the minimum altitude value or above the minimum altitude value minus the hysteresis value. In some embodiments, the information of the altitude range may further comprise the first range. Alternatively, the first range may be predefined.
[0077] In some embodiments, the altitude range may comprise altitude values within a second range below the maximum altitude value or below the maximum altitude value plus the hysteresis value. In some embodiments, the information of the altitude range may further comprise the second range. Alternatively, the second range may be predefined.
[0078] In the context of the present disclosure, if a distance between a location of the terminal device 110 and a location of a waypoint is smaller than or equal to a distance threshold (e.g., at any previous time) , the terminal device 110 may consider that the terminal device 110 arrives at the location of the waypoint. If the terminal device 110 arrives at a location of a waypoint or the terminal device 110 arrives at the location of the waypoint at a time indicated by a time stamp of the waypoint, the terminal device 110 may consider that the terminal device 110 is located at the waypoint or arrives at the waypoint or enters the waypoint. For example, if the terminal device 110 arrives at the location of the waypoint no earlier than a first time before a time stamp of the waypoint, or no later than a second time after the time stamp of the waypoint, the terminal device 110 may consider that the terminal device 110 is located at the waypoint or arrives at the waypoint or enters the waypoint. For another example, if the terminal device 110 arrives at the location of the waypoint at a third time and the time difference between the third time and the time indicated by the time stamp is not larger than a time threshold, the terminal device 110 may consider that the terminal device 110 is located at the waypoint or arrives at the waypoint or enters the waypoint.
[0079] In the context of the present disclosure, if the terminal device 110 has passed a starting point of a waypoint group and not arrived at an ending point of the waypoint group, the terminal device 110 may consider that the terminal device 110 is located at the waypoint group or arrived at the waypoint group or enters the waypoint group.
[0080] In the context of the present disclosure, if a difference between an altitude of the terminal device 110 and a certain altitude is smaller than or equal to a threshold value, the terminal device 110 may consider that the terminal device 110 is located at the certain altitude or arrives at the certain altitude or enters the altitude.
[0081] In the context of the present disclosure, if the terminal device 110 has arrived at an altitude within an altitude range, the terminal device 110 may consider that the terminal device 110 is located at the altitude range or arrived at the altitude range or enters the altitude range.
[0082] In some embodiments where the set of configurations are for the conditional cell change, the set of configurations may comprise a set of conditional reconfigurations, and a configuration in the set of configurations may comprise a conditional reconfiguration in the set of conditional reconfigurations. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with an identity (ID) of a conditional reconfiguration in a configuration for a conditional cell change. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a report configuration. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a conditional reconfiguration in a list of conditional reconfigurations. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a RRC reconfiguration in a list of RRC reconfigurations.
[0083] In some embodiments where the set of configurations are for the idle or inactive measurement, the set of configurations may comprise a set of idle or inactive measurement configurations. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with an idle or inactive measurement configuration in a list of idle or inactive measurement configurations. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a carrier configuration in an idle or inactive measurement configuration. In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a synchronization signal block (SSB) measurement configuration in an idle or inactive measurement configuration.
[0084] Continuing to refer to Fig. 2, the terminal device 110 may determine 230 a first configuration in the set of configurations based on a location of the terminal device 110.
[0085] In some embodiments, if the terminal device 110 arrives at a location of a third waypoint, the terminal device 110 may determine, as the first configuration, a configuration in the set of configurations that is associated with the third waypoint or a waypoint group associated with the third waypoint. In some alternative embodiments, if the terminal device 110 arrives at the location of the third waypoint at a time indicated by a time stamp of the third waypoint, the terminal device 110 may determine, as the first configuration, a configuration in the set of configurations that is associated with the third waypoint or a waypoint group associated with the third waypoint.
[0086] In some embodiments, the terminal device 110 may consider it has arrived at the third waypoint or arrived at the location of the third waypoint if a distance between the terminal device 110 and the third waypoint is smaller than or equal to a distance threshold (e.g., at any previous time) . In some embodiments, after arriving at the third waypoint, the terminal device 110 may consider it has left the third waypoint if the distance between the terminal device 110 and the third waypoint is larger than or equal to the distance threshold plus a hysteresis value (if configured) .
[0087] In some embodiments, if the terminal device 110 arrives at a first altitude, the terminal device 110 may determine, as the first configuration, a configuration in the set of configurations that is associated with the first altitude or an altitude range associated with the first altitude.
[0088] In some embodiments, the terminal device 110 may consider it has arrived at the first altitude if a distance between an altitude of the terminal device 110 and the first altitude is smaller than or equal to an altitude threshold. In some embodiments, after arriving at the first altitude, the terminal device 110 may consider it has left the first altitude if the distance between the altitude of the terminal device 110 and the first altitude is larger than or equal to the altitude threshold plus a hysteresis value (if configured) .
[0089] In some scenarios, there may be overlapping among the multiple altitude ranges, and multiple configurations associated with multiple altitude ranges may be triggered simultaneously. In other words, multiple configurations may be applicable simultaneously, and more than one events may be simultaneously triggered to execute the conditional cell change or the idle or inactive measurement. In this case, the terminal device 110 may select one of the multiple configurations as the first configuration.
[0090] In some embodiments, the terminal device 110 may determine multiple difference values between an altitude of the terminal device 110 and multiple altitude thresholds associated with the multiple configurations. The terminal device 110 may select a first difference value in the multiple difference values, and determine, as the first configuration, one of the multiple configurations that is associated with the first difference value.
[0091] In some embodiments, the terminal device 110 may receive, from the network device 120, an indication of selecting the first difference value in the multiple difference values. Based on the indication, the terminal device 110 may determine or select the first difference value from the multiple difference values. In some embodiments, the first difference value may be a smallest value among the multiple difference values. For example, the network device 120 may provide an indication to apply a configuration of conditional cell change or idle / inactive measurement associated with the smallest value.
[0092] In some embodiments, the first difference value may be a largest value among the multiple difference values. For example, the network device 120 may provide an indication to apply a configuration of conditional cell change or idle / inactive measurement associated with the largest value.
[0093] In some embodiments, the terminal device 110 may receive, from the network device 120, information of priority values of the multiple configurations, and select one of the multiple configurations that has a priority value higher than or equal to a threshold priority value. In other words, the network device 120 may provide priority values of the multiple configurations for the terminal device 110 to determine which configuration is to be applied. In this example, a target cell associated with an ID of a conditional reconfiguration with a higher priority may be considered as a triggered cell.
[0094] In some embodiments, for conditional reconfiguration evaluation when multiple altitude range-based configurations are configured, it is up to implementation of the terminal device 110 regarding whether to reset filtering upon entering a different altitude range with a different configuration.
[0095] Continuing to refer to Fig. 2, the terminal device 110 may perform 240 the mobility related operation based on the first configuration. With reference to Fig. 2, in some embodiments, the terminal device 110 may perform 241 the conditional cell change based on the first configuration for the conditional cell change.
[0096] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with an identity of a conditional reconfiguration in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may determine that a set of cells associated with the conditional reconfiguration are applicable cells. In some embodiments, if the terminal device 110 is located outside of the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may determine that the set of cells are inapplicable cells. In some embodiments, if an execution condition for an applicable cell is fulfilled (e.g., all events configured for the applicable cell are fulfilled) and the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may determine the applicable cell as a triggered cell for conditional reconfiguration execution. Then the terminal device 110 may initiate the conditional reconfiguration execution for the triggered cell.
[0097] For illustration, an example configuration may be described as below.
[0098] In this example configuration, an IE ‘CondReconfigToAddMod’ denotes a conditional reconfiguration, an IE ‘condReconfigId’ denotes an ID of the conditional reconfiguration, an IE ‘wayPointRange’ denotes a waypoint group associated with the ID of the conditional reconfiguration.
[0099] For this example configuration, an example procedure may be described as below.
[0100] · Cell applicable aspect: UE may consider the cell to be applicable cell when the UE is located between the range for evaluation (i.e., if a condExecutionRange is associated to the condReconfigId, UE may consider the cell to be applicable cell when the UE locates in the range) ; UE may consider the cell to be applicable cell from the start point indicated in the range for evaluation; UE may consider the cell to be not applicable after the end point indicated in the range for evaluation.
[0101] · Trigger cell aspect: if event (s) associated to all measId (s) within condTriggerConfig for the applicable cell is fulfilled, a condExecutionRange is associated to the condReconfigId, and UE locates in the range, the UE may consider the applicable cell associated to that condReconfigId as a triggered cell, and initiate the conditional reconfiguration execution.
[0102] In this example procedure, an IE ‘condExecutionRange’ denotes a range for condition execution, an IE ‘condReconfigId’ denotes an ID of a conditional reconfiguration, an IE ‘measId (s) ’ denotes one or more measurement configuration ID, and an IE ‘condTriggerConfig’ denotes a configuration of an execution condition in the conditional reconfiguration.
[0103] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a report configuration in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may evaluate an event in the report configuration. For example, an ID of an event configuration is associated with an event X, and an entry condition applicable for the event X is fulfilled for the applicable cell during a corresponding time to trigger (TTT) defined for the event X. Alternatively or additionally, the terminal device 110 may also determine whether a report configuration associated with an ID of a measurement configuration within a RRC reconfiguration includes the waypoint or waypoint group or altitude or altitude range and the terminal device 110 locates in the waypoint or waypoint group or altitude or altitude range. If the report configuration includes the waypoint or waypoint group or altitude or altitude range, and the terminal device 110 locates in the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may consider an event associated with the measurement configuration ID to be fulfilled.
[0104] For illustration, an example configuration may be described as below.
[0105] In this example configuration, an IE ‘CondTriggerConfig’ denotes a configuration of an execution condition in a conditional reconfiguration, an IE ‘condEventId’ denotes an ID of an event associated with a report configuration, and an IE ‘wayPointRange’ denotes a waypoint group associated with the report configuration.
[0106] For this example configuration, an example procedure may be described as below.
[0107] · Condition evaluation aspect: if the condEventId is associated with condEventX, and if the entry conditions applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId (s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig,
[0108] · If the reportConfig associate to the measId within the condRRCReconfig includes a range and UE locates in the range,
[0109] · consider the event associated to that measId to be fulfilled.
[0110] In this example procedure, an IE ‘reportConfig’ denotes a report configuration, an IE ‘condEventId’ denotes an ID of an event associated with the report configuration, an IE ‘condEventX’ denotes an event X, an IE ‘condReconfigId’ denotes an ID of a conditional reconfiguration, an IE ‘VarConditionalReconfig’ denotes a variable for the conditional reconfiguration, an IE ‘condTriggerConfig’ denotes a configuration of an execution condition in the conditional reconfiguration, an IE ‘timeToTrigger’ denotes a time to trigger, an IE ‘condRRCReconfig’ denotes a RRC reconfiguration, and an IE ‘measId’ denotes an ID of a measurement configuration.
[0111] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a conditional reconfiguration in a list of conditional reconfigurations in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, the terminal device 110 may apply the conditional reconfiguration.
[0112] For illustration, an example configuration may be described as below.
[0113] In this example configuration, an IE ‘ConditionalReconfigflightPathBasedLsit’ denotes a list of conditional reconfigurations based on a flightpath, an IE ‘ConditionalReconfigflightPathBased’ denotes a conditional reconfiguration in the list of conditional reconfigurations, and an IE ‘wayPointRange’ denotes a waypoint group associated with the conditional reconfiguration.
[0114] For this example configuration, an example procedure may be described as below.
[0115] · List of flightpath-dependent ConditionalReconfig: When UE is within a range indicated by wayPointRange, it applies the corresponding CondReconfigToAddMod-enh, if present (and ignores the CondReconfigToAddMod) . Otherwise CondReconfigToAddModList if CondReconfigToAddMod-enh is absent. When the UE is outside all ranges indicated by wayPointRange (if any) , it applies CondReconfigToAddModList.
[0116] In this example procedure, an IE ‘ConditionalReconfig’ denotes a conditional reconfiguration, an IE ‘wayPointRange’ denotes a waypoint group, an IE ‘CondReconfigToAddMod-enh’ denotes a flightpath-dependent conditional reconfiguration, an IE ‘condEventX’ denotes an event X, an IE ‘CondReconfigToAddMod’ denotes a flightpath-independent conditional reconfiguration, an IE ‘CondReconfigToAddModList’ denotes a list of flightpath-independent conditional reconfigurations.
[0117] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a RRC reconfiguration in a list of RRC reconfigurations in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range and an execution condition for the RRC reconfiguration is fulfilled, the terminal device 110 may apply the RRC reconfiguration.
[0118] For illustration, an example configuration may be described as below.
[0119] In this example, an IE ‘condRRCReconfigflightPathBasedLsit’ denotes a list of RRC reconfigurations, an IE ‘condRRCReconfigflightPathBased’ denotes a RRC reconfiguration in the list of RRC reconfigurations, and an IE ‘wayPointRange’ denotes a waypoint group associated with the RRC reconfiguration.
[0120] For this example configuration, an example procedure may be described as below.
[0121] · List of flightpath-dependent condRRCReconfig: When the UE is within a range indicated by wayPointRange, and the execution condition is fulfilled, it applies the corresponding condRRCReconfig.
[0122] In this example procedure, an IE ‘wayPointRange’ denotes a waypoint group, an IE ‘condRRCReconfig’ denotes a RRC reconfiguration.
[0123] In some embodiments for the conditional cell change, the terminal device 110 may determine whether a set of events (i.e., one or more events) for a cell are fulfilled. If the set of events for the cell are fulfilled, the terminal device 110 may consider the cell as a triggered cell, and initiate an execution of a conditional reconfiguration in the first configuration.
[0124] In some embodiments, the set of events may comprise that a distance between the terminal device 110 and a first reference waypoint is smaller than or equal to a distance threshold, i.e., the terminal device 110 arrives at the first reference waypoint.
[0125] For illustration, an example procedure may be described as below.
[0126] UE shall:
[0127] 1>consider an entering condition for this event to be satisfied when both condition D1 is fulfilled;
[0128] 1>consider a leaving condition for this event to be satisfied when condition D2 is fulfilled; Inequality D1 (the entering condition)
[0129] Ml+Hys < Thresh
[0130] Inequality D2 (the leaving condition)
[0131] Ml-Hys >Thresh
[0132] Variables in the inequalities are defined as follows:
[0133] Ml denotes a distance between the UE and the first reference waypoint for this event, not taking into account any offsets, Hys denotes a hysteresis parameter for this event, and Thresh denotes the threshold for this event defined as a distance. Ml is expressed in meters. Hys / Thresh is expressed in the same unit as Ml.
[0134] In some embodiments, the set of events may comprise that the distance between the terminal device 110 and the first reference waypoint is larger than or equal to the distance threshold, i.e., the terminal device 110 has passed the first reference waypoint.
[0135] For illustration, an example procedure may be described as below.
[0136] UE shall:
[0137] 1>consider an entering condition for this event to be satisfied when both condition D1 is fulfilled;
[0138] 1>consider a leaving condition for this event to be satisfied when condition D2 is fulfilled; Inequality D1 (Entering condition)
[0139] Ml+Hys > Thresh
[0140] Inequality D2 (Leaving condition)
[0141] Ml-Hys < Thresh
[0142] Variables in the inequalities are defined as follows:
[0143] Ml denotes a distance between the UE and the first reference waypoint for this event, Hys denotes a hysteresis parameter for this event, and Thresh denotes the threshold for this event defined as a distance. Ml is expressed in meters. Hys / Thresh is expressed in the same unit as Ml.
[0144] In some embodiments, the set of events may comprise that the distance between the terminal device 110 and the first reference waypoint is larger than or equal to a first distance threshold and a distance between the terminal device 110 and a second reference waypoint is smaller than or equal to a second distance threshold. That is, the terminal device 110 has passed the first reference waypoint and has not arrived at the second reference waypoint. In some embodiments, the first reference waypoint may be the same as the second reference waypoint.
[0145] For illustration, an example procedure may be described as below.
[0146] UE shall:
[0147] 1> consider an entering condition for this event to be satisfied when both condition D2-1 and condition D2-2, as specified below, are fulfilled;
[0148] 1> consider a leaving condition for this event to be satisfied when at least one of condition D2-3 or condition D2-4, as specified below, is fulfilled;
[0149] Inequality D2-1 (Entering condition 1)
[0150] Ml1-Hys>Thresh1
[0151] Inequality D2-2 (entering condition 2)
[0152] Ml2+Hys<Thresh2
[0153] Inequality D2-3 (Leaving condition 1)
[0154] Ml1+Hys<Thresh1
[0155] Inequality D2-4 (Leaving condition 2)
[0156] Ml2-Hys>Thresh2
[0157] Variables in the inequalities are defined as follows:
[0158] Ml1 denotes a distance between the UE and the first reference waypoint, Ml2 denotes a distance between the UE and the second reference waypoint, Hys denotes a hysteresis parameter for this event, Thresh1 denotes a threshold for this event defined as a distance, and Thresh2 denotes another threshold for this event defined as a distance. Ml1 is expressed in meters. Ml2 / Hys / Thresh1 / Thresh2 is expressed in the same unit as Ml1. This also apply to a case that the first reference waypoint is the same as the second reference waypoint.
[0159] In some embodiments, the set of events may comprise that time measured at the terminal device 110 is within a time duration indicated by a set of reference time stamps. For example, the time measured at the terminal device 110 may be more than a time threshold t1 but is less than a time threshold t2. The time thresholds t1 and t2 may be indicated by a timestamp of a waypoint in the flightpath.
[0160] For illustration, an example procedure may be described as below.
[0161] UE shall:
[0162] 1>consider an entering condition for this event to be satisfied when condition T1-1, as specified below, is fulfilled;
[0163] 1>consider a leaving condition for this event to be satisfied when condition T1-2, as specified below, is fulfilled;
[0164] Inequality T1-1 (Entering condition)
[0165] Mt >Thresh1
[0166] Inequality T1-2 (Leaving condition)
[0167] Mt >Thresh2 or Mt >Thresh1+Duration
[0168] Variables in the inequalities are defined as follows:
[0169] Mt denotes a time measured at the UE, Thresh1 denotes a threshold parameter for this event (i.e., t1, as defined by a time stamp of a starting waypoint indicated within a report configuration for this event) , Thresh2 (if present) denotes a threshold parameter for this event (i.e., t2, as defined by a time stamp of an ending waypoint indicated within a report configuration for this event) , Duration (if present) denotes a duration parameter for this event (i.e., a time duration as defined within a report configuration for this event) . Thresh1 and Thresh2 is expressed in the same unit as Mt. Duration is expressed in the same unit as Mt.
[0170] In some embodiments, the set of events may comprise that the distance between the terminal device 110 and the first reference waypoint is smaller than or equal to the first distance threshold and a time difference between the time measured at the terminal device 110 and a time stamp of the first reference waypoint is smaller than or equal to a time difference threshold.
[0171] For illustration, an example procedure may be described as below.
[0172] UE shall:
[0173] 1> consider an entering condition for this event to be satisfied when both condition D2-1 and condition D2-2, as specified below, are fulfilled;
[0174] 1> consider a leaving condition for this event to be satisfied when at least one of condition D2-3 or condition D2-4, as specified below, is fulfilled;
[0175] Inequality D2-1 (Entering condition 1)
[0176] Ml-Hys>Thresh1
[0177] Inequality D2-2 (Entering condition 2)
[0178] Mt>Thresh2a
[0179] Inequality D2-3 (Leaving condition 1)
[0180] Ml1+Hys<Thresh1
[0181] Inequality D2-4 (Leaving condition 2)
[0182] Mt>Thresh2b or Mt >Thresh2a+Duration
[0183] Variables in the inequalities are defined as follows:
[0184] Ml denotes a distance between the UE and the first reference waypoint, Mt denotes a time measured at the UE, Hys denotes a hysteresis parameter for this event, Thresh1 denotes a threshold for this event defined as a distance, Thresh2a and Thresh2b denote threshold parameters for this event (i.e., for UAV, Thresh2a is t1 as defined by a time stamp of the first reference waypoint indicated within a report configuration for this event, Thresh2b is t2 as defined by a time stamp of the second reference waypoint indicated within the report configuration for this event) . Ml is expressed in meters. Ml2 / Hys / Thresh1 / Thresh2 is expressed in the same unit as Ml1. This also apply to a case that the first reference waypoint is the same as the second reference waypoint.
[0185] In some embodiments, the terminal device 110 may receive, from the network device 120, an indication of the first or second reference waypoint or the set of reference time stamps. That is, the first or second reference waypoint or the set of reference time stamps may be indicated by the network device 120 in the first configuration. In some embodiments, the first or second reference waypoint may be indicated by the network device 120 as one or more locations.
[0186] In some embodiments, the terminal device 110 may determine a nearest waypoint which has passed as the first or second reference waypoint. In some embodiments, the terminal device 110 may determine a waypoint to be arrived in the flightpath as the first or second reference waypoint. For example, the first or second reference waypoint may be the next N arriving waypoints in the flightpath, where N ≥ 1.
[0187] For illustration, an example procedure of the conditional cell change may be described as below.
[0188] If event (s) associated to all measId (s) are fulfilled:
[0189] · consider the target candidate cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell;
[0190] · initiate the conditional reconfiguration execution;
[0191] Determine one of the triggered cells as the selected cell, for the selected cell (s) of conditional reconfiguration execution:
[0192] · if the subsequentCondReconfig is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message for the selected cell
[0193] · perform Subsequent CPAC execution
[0194] · else
[0195] · apply the stored condRRCReconfig of the selected cell and perform the actions of Reception of an RRCReconfiguration by the UE.
[0196] In this example, an IE ‘measId’ denotes an ID of a measurement configuration, an IE ‘condRRCReconfig’ denotes a RRC reconfiguration, an IE ‘condReconfigId’ denotes an ID of the RRC reconfiguration, an IE ‘subsequentCondReconfig’ denotes subsequent conditional reconfiguration, and an IE ‘VarConditionalReconfig’ denotes a variable for a conditional reconfiguration.
[0197] With reference to Fig. 2, in some embodiments, the terminal device 110 may perform 242 the idle or inactive measurement based on the first configuration for the idle or inactive measurement.
[0198] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with an idle or inactive measurement configuration in a list of idle or inactive measurement configurations in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or the altitude or altitude range, the terminal device 110 may apply the idle or inactive measurement configuration.
[0199] For illustration, an example configuration may be described as below.
[0200] In this example configuration, an IE ‘MeasIdleConfigDedicatedflightPathBasedLsit’ denotes a list of idle or inactive measurement configurations, an IE ‘MeasIdleConfigDedicatedflightPathBased’ denotes an idle or inactive measurement configuration in the list of idle or inactive measurement configurations, and an IE ‘wayPointRange’ denotes a waypoint group associated with the idle or inactive measurement configuration.
[0201] For this example configuration, an example procedure may be described as below.
[0202] · List of flightpath-dependent MeasIdleConfig: When the UE is within a range indicated by wayPointRange, it applies the corresponding MeasIdleConfigDedicated-enh, if present (and ignores the MeasIdleConfigDedicated) . Otherwise MeasIdleConfigDedicated if MeasIdleConfigDedicated-enh is absent. When the UE is outside all ranges indicated by wayPointRange (if any) , it applies MeasIdleConfigDedicated-enh.
[0203] In this example procedure, an IE ‘MeasIdleConfig’ denotes an idle or inactive measurement configuration, an IE ‘wayPointRange’ denotes a waypoint group, an IE ‘MeasIdleConfigDedicated-enh’ denotes a flightpath-dependent idle or inactive measurement configuration, and an IE ‘MeasIdleConfigDedicated’ denotes a flightpath-independent idle or inactive measurement configuration.
[0204] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a carrier configuration in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or the altitude or altitude range, the terminal device 110 may apply the carrier configuration.
[0205] For illustration, an example configuration may be described as below.
[0206] In this example, an IE ‘measIdleCarrierListNRflightPathBasedLsit’ denotes a list of carrier configurations, an IE ‘MeasIdleCarrierListNRflightPathBased’ denotes a carrier configuration in the list of carrier configurations, and an IE ‘wayPointRange’ denotes a waypoint group associated with the carrier configuration.
[0207] For this example configuration, an example procedure may be described as below.
[0208] · List of flightpath-dependent measIdleCarrierListNR: When the UE is within an range indicated by wayPointRange, it applies the corresponding MeasIdleCarrierListNR-enh, if present (and ignores the measIdleCarrierListNR) . Otherwise MeasIdleConfigDedicated if MeasIdleCarrierListNR-enh is absent. When the UE is outside all ranges indicated by wayPointRange (if any) , MeasIdleCarrierListNR-enh applies.
[0209] In this example procedure, an IE ‘measIdleCarrierListNR’ denotes a list of carrier configurations for an idle or inactive measurement, an IE ‘wayPointRange’ denotes a waypoint group, an IE ‘MeasIdleCarrierListNR-enh’ denotes a flightpath-dependent carrier configuration, and an IE ‘MeasIdleCarrierListNR’ denotes a flightpath-independent carrier configuration.
[0210] In some embodiments, a waypoint or waypoint group or altitude or altitude range may be associated with a SSB measurement configuration in the first configuration. In this case, if the terminal device 110 is located in the waypoint or waypoint group or the altitude or altitude range, the terminal device 110 may apply the SSB measurement configuration.
[0211] For illustration, an example configuration may be described as below.
[0212] In this example, an IE ‘SSB-ToMeasureAltitudeBasedList-enh’ denotes a list of SSB measurement configurations, an IE ‘SSB-ToMeasureAltitudeBased-enh’ denotes a SSB measurement configuration in the list of SSB measurement configurations, and an IE ‘altitudeRange-enh’ denotes an altitude range associated with the SSB measurement configuration.
[0213] For this example configuration, an example procedure may be described as below.
[0214] · List of altitude-dependent ssb-ToMeasure: When the UE is within an altitude range indicated by altitudeRange, it ignores the ssb-ToMeasure (without suffix) , and applies the corresponding ssb-ToMeasure-enh if present, otherwise measures on all SS-blocks if ssb-ToMeasure is absent. When the UE is outside all the altitude ranges indicated by altitudeRange (if any) , ssb-ToMeasure (without suffix) applies.
[0215] · For each altitude range, altitudeMin indicates the minimum altitude in meters, altitudeMax indicates the maximum altitude in meters relative to sea level, and if included, altitudeHyst indicates hysteresis in meters for determination of the altitude range. I. e., when altitudeHyst is configured for an altitude range, the UE considers itself to have entered the range if altitudeMin ≤ UE altitude ≤ altitudeMax and after entering the range considers itself to be in the range while (altitudeMin –altitudeHyst) ≤ UE altitude ≤ (altitudeMax + altitudeHyst) .
[0216] · For each altitudeRange, if altitudeMin is absent, value minAltitude-enh is used and if altitudeMax is absent, value maxAltitude-enh is used.
[0217] In this example procedure, an IE ‘ssb-ToMeasure’ denotes a SSB measurement configuration, an IE ‘altitudeRange’ denotes an altitude range, an IE ‘ssb-ToMeasure-enh’ denotes an altitude-dependent SSB measurement configuration, an IE ‘ssb-ToMeasure’ denotes an altitude-independent SSB measurement configuration, an IE ‘minAltitude-enh’ denotes a newly defined minimum altitude, and an IE ‘maxAltitude-enh’ denotes a newly defined maximum altitude.
[0218] Continuing to refer to Fig. 2, the terminal device 110 may transmit 243, to the network device 120, results of the idle or inactive measurement associated with waypoints or waypoint groups or altitudes or altitude ranges.
[0219] In some embodiments, the terminal device 110 may store the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges, e.g., in a variable for an idle or inactive measurement report. In some embodiments, the terminal device 110 may set the results of the idle or inactive measurement with corresponding altitude or waypoint information (e.g., waypoint or waypoint group or altitude or altitude range) by setting the results of the idle or inactive measurement to a value in the variable for the idle or inactive measurement report. In some embodiments, upon arriving at a waypoint or waypoint group or altitude or altitude range with a different SSB measurement configuration, the terminal device 110 may include a new entry in the variable for the idle or inactive measurement report and set the corresponding altitude or waypoint information.
[0220] In some embodiments, the terminal device 110 may transmit the results of the idle or inactive measurement via a signaling similar as that for measurement results per carrier or measurement results per cell.
[0221] For illustration, an example report of the idle or inactive measurement results may be described as below.
[0222] In this example report, an IE ‘MeasResultIdleNR’ denotes idle or inactive measurement results, an IE ‘measResultServingCellAltitudeBasedList-enh’ denotes a list of serving cell altitude based measurement results, an IE ‘MeasResultServingCellAltitudeBased-enh’ denotes a serving cell altitude based measurement result, an IE ‘altitudeRange-enh’ denotes an altitude range, and IE ‘measResultServingCell-enh’ denotes a measurement result for a serving cell. It is to be understood that although this procedure is shown in connection with altitude information, it also applies to a waypoint or waypoint group.
[0223] In some embodiments, the terminal device 110 may transmit at least part of the results of the idle or inactive measurement. In some embodiments, the at least part of the results of the idle or inactive measurement may be associated with a set of cells that remain detectable when the terminal device 110 enters a connected state. In other words, if a result of the idle or inactive measurement is for a cell that remains detectable when the terminal device 110 enters the connected state, the terminal device 110 may transmit the result to the network device 120. In some embodiments, the at least part of the results of the idle or inactive measurement may be associated with the waypoints or waypoint groups or altitudes or altitude ranges indicated by the network device 120. In other words, if a result of the idle or inactive measurement is associated with a waypoint or waypoint group or altitude or altitude range indicated by the network device 120, the terminal device 110 may transmit the result to the network device 120.
[0224] For illustration, an example procedure may be described as below.
[0225] UE transmits a result of an idle or inactive measurement to NW, provided that the following conditions are met:
[0226] · When the UE enters the altitude range indicated in altitudeRange, if has been provided.
[0227] · When the UE arrives at the waypoint or enters the waypoint range indicated in waypointRange, if has been provided.
[0228] · The detected cell and SSBs remains detectable when the UE reconnects to the network.
[0229] In this example procedure, an IE ‘altitudeRange’ denotes an altitude range, and an IE ‘waypointRange’ denotes a waypoint group.
[0230] In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of reporting the at least part of the results of the idle or inactive measurement for waypoints or waypoint groups or altitudes or altitude ranges. For example, the network device 120 may indicate altitude or waypoint information for reporting idle or inactive measurement results. Based on the indication, the terminal device 110 may transmit at least part of the results of the idle or inactive measurement associated with the altitude or waypoint information.
[0231] In some embodiments, the network device 120 may transmit the indication via a signaling for an idle or inactive measurement configuration, system information for an idle or inactive measurement configuration, a signaling dedicated for an idle or inactive measurement configuration, or a list of carrier configurations.
[0232] Continuing to refer to Fig. 2, the terminal device 110 may decide to restart 244 the idle or inactive measurement.
[0233] In some embodiments, if a timer (e.g., T331) for the idle or inactive measurement expires after the terminal device 110 changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to a further waypoint or waypoint group or altitude or altitude range associated with a further configuration for the idle or inactive measurement, the terminal device 110 may restart the idle or inactive measurement.
[0234] For example, upon expiration of T331 after entering an altitude range with a different SSB measurement configuration, it is up to UE implementation to continue to perform the idle or inactive measurement. In another example, upon expiration of T331 after entering a waypoint group with a different idle or inactive measurement configuration, it is up to UE implementation to continue to perform the idle or inactive measurement.
[0235] In some embodiments, if the terminal device 110 changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to the further waypoint or waypoint group or altitude or altitude range associated with the further configuration for the idle or inactive measurement, the terminal device 110 may restart the idle or inactive measurement.
[0236] For example, upon entering an altitude range with a different SSB measurement configuration, or switching between different altitude ranges, it is up to UE implementation to continue to perform the idle or inactive measurement. In another example, upon entering a waypoint group with a different idle or inactive measurement configuration, or switching between different waypoint groups, it is up to UE implementation to continue to perform the idle or inactive measurement.
[0237] In some embodiments, the terminal device 110 may restart the idle or inactive measurement by restarting the timer for the idle or inactive measurement (e.g., T311) with a value of a configured time duration or with another extended measurement duration pre-configured. In some embodiments, the terminal device 110 may restart the idle or inactive measurement by restarting the timer for the idle or inactive measurement (e.g., T311) with a value of a configured time duration corresponding to an applied idle or inactive measurement configuration. In some embodiments, whether to reset filtering may base on implementation of the terminal device 110. In some embodiments, whether to reset or discard an old variable for an idle or inactive measurement report may be based on implementation of the terminal device 110. In some embodiments, the terminal device 110 may determine whether to reset filtering based on an indication from NW. In some embodiments, the terminal device 110 may determine whether to reset / discard the old variable for the idle or inactive measurement report based on an indication from NW.
[0238] In some embodiments, upon T331 expires or is stopped, the terminal device 110 may release the local idle or inactive measurement configuration based on the waypoint or waypoint group or altitude or altitude range information. In some embodiments, the terminal device 110 may release the local idle or inactive measurement configuration if altitude or flightpath based idle / inactive measurement is not configured. In some embodiments, the terminal device 110 may release the local idle or inactive measurement configuration associated with the passed waypoint or waypoint group, or associated with the altitude or altitude range which the terminal device 110 is not located in.
[0239] For illustration, an example procedure of releasing the local idle or inactive measurement configuration may be described as below.if T331 expires or is stopped:
[0240] · if altitude or flightpath based idle / inactive measurement is not configured,
[0241] · release the VarMeasIdleConfig.
[0242] In this example procedure, an IE ‘VarMeasIdleConfig’ denotes a variable for an idle or inactive measurement configuration.
[0243] For illustration, another example procedure of releasing the local idle or inactive measurement configuration may be described as below.if T331 expires or is stopped:
[0244] · if altitude or flightpath based idle / inactive measurement is configured,
[0245] · release the configurations corresponding to the passed waypoint or waypoint group;
[0246] · else
[0247] · release the VarMeasIdleConfig.
[0248] In this example procedure, an IE ‘VarMeasIdleConfig’ denotes a local variable for an idle or inactive measurement configuration.
[0249] Continuing to refer to Fig. 2, the terminal device 110 may release 250 a configuration in the set of configurations for the mobility related operation. In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of removing a configuration associated with a passed waypoint or waypoint group. The terminal device 110 may release the configuration based on reception of the indication. In some alternative embodiments, the terminal device 110 may autonomously release the configuration associated with the passed waypoint or waypoint group. In other words, the terminal device 110 may release the configuration associated with waypoints or waypoint ranges which do not belong to upcoming or future waypoints.
[0250] With reference to Fig. 2, in some embodiments, if the terminal device 110 passes a waypoint or waypoint group, the terminal device 110 may release 251 a configuration associated with the waypoint or waypoint group in the set of configurations. This procedure may be called as a release after pass.
[0251] For illustration, an example procedure of the release after pass may be described as below.
[0252] · if the ConditionalReconfiguration contains the condReconfigToRemoveList or releasePassedPoints:
[0253] · perform conditional reconfiguration removal procedure;
[0254] The UE shall:
[0255] · For each condReconfigId associated to flightpath waypoint which does not belong to the upcoming / future waypoint, remove the entry in condExecutionCondToAddModList within VarConditionalReconfig with a value for this condReconfigId.
[0256] In this example procedure, an IE ‘ConditionalReconfiguration’ denotes a conditional reconfiguration, an IE ‘condReconfigToRemoveList’ denotes a list of conditional reconfigurations to be removed, an IE ‘condExecutionCondToAddModList’ denotes a list of execution condition configurations, an IE ‘releasePassedPoints’ denotes an indication of releasing configurations associated with passed waypoints, an IE ‘VarConditionalReconfig’ denotes a variable for the conditional reconfiguration, and an IE ‘condReconfigId’ denotes an ID of the conditional reconfiguration.
[0257] With reference to Fig. 2, in some embodiments, if one or more waypoints or waypoint groups in the flightpath are updated, the terminal device 110 may release 252 one or more configurations associated with the one or more waypoints or waypoint groups. This procedure may be called as a release upon flightpath update.
[0258] In some embodiments, if a waypoint or waypoint group associated with a configuration has been added or removed or updated or changed or changed more than a threshold, the terminal device 110 may consider the configuration to be released upon update of the flightpath or upon flightpath update / availability notification.
[0259] In some embodiments, if a flightpath is updated and there is a configuration (e.g., conditional cell change configuration) associated with the flightpath, the configuration associated with the flightpath may also need to be updated or released.
[0260] In some embodiments, if a flightpath is updated and there is a configuration (e.g., conditional cell change configuration) associated with an updated waypoint, the configuration associated with the updated waypoint may also need to be updated or released.
[0261] In some embodiments, if a waypoint locates in a waypoint range associated with a configuration (e.g., conditional cell change configuration) has been added, removed or updated (based on a distance / time threshold) , the configuration may need to be updated or released.
[0262] In some embodiments, if a flightpath updated notification is triggered by addition, remove or update of a waypoint associated with a configuration (e.g., CHO configuration) , the configuration associated with the updated waypoint may need to be updated or released.
[0263] In some embodiments, if a flightpath updated notification is triggered by addition, remove or update of a waypoint that locates in a waypoint range associated with a configuration (e.g., CHO configuration) , the configuration associated to the updated waypoint may need to be updated or released.
[0264] In some embodiments, if number of added or removed or updated waypoints that locate in a waypoint range associated with a configuration (e.g., conditional cell change configuration) exceeds a number threshold, the configuration associated with the updated waypoints may also need to be updated or released.
[0265] For illustration, an example procedure of the release upon flightpath update may be described as below.
[0266] if UE has flight path information available:
[0267] · <conditions are fulfilled>
[0268] · include flightPathInfoAvailable;
[0269] · If the added / removed / changed waypoint is in the waypoint range associated with CHO configurations, remove the entry in condExecutionCondToAddModList within VarConditionalReconfig with the value for this condReconfigId.
[0270] In this example procedure, an IE ‘flightPathInfoAvailable’ denotes an indication that flight path information is available, an IE ‘condExecutionCondToAddModList’ denotes a list of execution condition configurations, an IE ‘VarConditionalReconfig’ denotes a variable of a conditional reconfiguration, and an IE ‘condReconfigId’ denotes an ID of the conditional reconfiguration.
[0271] For illustration, an example of a configuration release will be described in connection with Fig. 3. Fig. 3 illustrates a schematic diagram 300 illustrating an example of configuration release according to some embodiments of the present disclosure. For convenience, this example will be described in connection with the terminal device 110 of Fig. 1. It is assumed that flightpath 1 has waypoints 1, 2 and 3, and flightpath 2 has waypoints 1, 2 and 4. The waypoint 1 is associated with configuration 1, the waypoint 2 is associated with configuration 2, the waypoint 3 is associated with configuration 3, and the waypoint 4 is associated with configuration 4.
[0272] As shown in Fig. 3, when the terminal device 110 arrives at the waypoint 2 along the flightpath 1, as the terminal device 110 has passed the waypoint 1, the configuration 1 associated with the waypoint 1 is released.
[0273] Continuing to refer to Fig. 3, when the terminal device 110 arrives at the waypoint 2, the terminal device 110 may find out the planned flightpath 1 will be updated to the flightpath 2. In this case, the waypoint 3 is no longer the future waypoint, and the waypoint 4 becomes the future waypoint. Thus, the configuration 3 associated with the waypoint 3 is released. It is to be understood that all configurations associated with the future waypoints in the flightpath 1 since the change point are released.
[0274] So far, mobility enhancement is described. With the process 200, a conditional cell change based on flightpath or altitude information may be achieved, and thus mobility performance may be improved, especially for aerial UE such as UAV. In addition, an idle or inactive measurement based on flightpath or altitude information may be achieved, and more detailed measurement report may be provided to NW.
[0275] It is to be understood that operations in the process 200 described with reference to Figs. 2 and 3 may be carried out separately or in any suitable combination.
[0276] EXAMPLE IMPLEMENTATION OF METHODS
[0277] Accordingly, embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to Figs. 4 and 5.
[0278] Fig. 4 illustrates an example method 400 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 400 may be performed at the terminal device 110 as shown in Fig. 1. For the purpose of discussion, in the following, the method 400 will be described with reference to Fig. 1. It is to be understood that the method 400 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. It is assumed that the terminal device 110 is served by the network device 120.
[0279] At block 410, the terminal device 110 may receive, from the network device 120, a set of configurations for a conditional cell change or an idle or inactive measurement. In some embodiments, a configuration in the set of configurations may be associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device 110, or an altitude or altitude range of the terminal device 110.
[0280] In some embodiments, the terminal device 110 may receive, from the network device 120, information of the waypoint of the flightpath comprising at least one of the following: an index of the waypoint, a location of the waypoint, or a time stamp of the waypoint. In some embodiments, the terminal device 110 may receive, from the network device 120, information of the waypoint group of the flightpath comprising at least one of the following: an index of the waypoint group, an index of a first waypoint as a starting point of the waypoint group, or an index of a second waypoint as an ending point of the waypoint group.
[0281] At block 420, the terminal device 110 may determine a first configuration in the set of configurations based on a location of the terminal device 110.
[0282] In some embodiments, if the terminal device 110 arrives at a location of a third waypoint or arrives at the location of the third waypoint at a time indicated by a time stamp of the third waypoint, the terminal device 110 may determine, as the first configuration, a configuration in the set of configurations that is associated with the third waypoint or a waypoint group associated with the third waypoint.
[0283] In some embodiments, if multiple configurations associated with multiple altitude ranges are triggered simultaneously, the terminal device 110 may select one of the multiple configurations as the first configuration.
[0284] In some embodiments, the terminal device 110 may select the one of the multiple configurations by: determining multiple difference values between an altitude of the terminal device and multiple altitude thresholds associated with the multiple configurations; selecting a first difference value in the multiple difference values; and determining, as the first configuration, one of the multiple configurations that is associated with the first difference value. In some embodiments, the terminal device 110 may select the first difference value by: receiving, from the network device 120, an indication of selecting the first difference value in the multiple difference values; and selecting the first difference value based on the indication.
[0285] In some embodiments, the terminal device 110 may select the one of the multiple configurations by: receiving, from the network device 120, information of priority values of the multiple configurations; and selecting the one of the multiple configurations that has a priority value higher than or equal to a threshold priority value.
[0286] At block 430, the terminal device 110 may perform the conditional cell change or the idle or inactive measurement based on the first configuration.
[0287] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with an identity of a conditional reconfiguration in the configuration. In some embodiments, the terminal device 110 may perform the conditional cell change by at least one of the following: if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, determining that a set of cells associated with the conditional reconfiguration are applicable cells; if the terminal device 110 is located outside of the waypoint or waypoint group or altitude or altitude range, determining that the set of cells are inapplicable cells; if an execution condition for an applicable cell is fulfilled and the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, determining the applicable cell as a triggered cell for conditional reconfiguration execution.
[0288] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with a report configuration. In some embodiments, the terminal device 110 may perform the conditional cell change by: if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, evaluating an event in the report configuration.
[0289] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with a conditional reconfiguration in a list of conditional reconfigurations. In some embodiments, the terminal device 110 may perform the conditional cell change by: if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range, applying the conditional reconfiguration.
[0290] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with a RRC reconfiguration in a list of RRC reconfigurations. In some embodiments, the terminal device 110 may perform the conditional cell change by: if the terminal device 110 is located in the waypoint or waypoint group or altitude or altitude range and an execution condition for the RRC reconfiguration is fulfilled, applying the RRC reconfiguration.
[0291] In some embodiments, the terminal device 110 may perform the conditional cell change by: determining that a set of events for a cell are fulfilled; considering the cell as a triggered cell; and initiating an execution of a conditional reconfiguration in the configuration.
[0292] In some embodiments, the set of events may comprise at least one of the following: a distance between the terminal device 110 and a first reference waypoint is smaller than or equal to a distance threshold; the distance between the terminal device 110 and the first reference waypoint is larger than or equal to the distance threshold; the distance between the terminal device 110 and the first reference waypoint is larger than or equal to a first distance threshold and a distance between the terminal device 110 and a second reference waypoint is smaller than or equal to a second distance threshold; time measured at the terminal device 110 is within a time duration indicated by a set of reference time stamps; or the distance between the terminal device 110 and the first reference waypoint is smaller than or equal to the first distance threshold and a time difference between the time measured at the terminal device 110 and a time stamp of the first reference waypoint is smaller than or equal to a time difference threshold.
[0293] In some embodiments, the terminal device 110 may receive, from the network device 120, an indication of the first or second reference waypoint. In some embodiments, the terminal device 110 may determine, as the first or second reference waypoint, a nearest waypoint which has passed. In some embodiments, the terminal device 110 may determine, as the first or second reference waypoint, a waypoint to be arrived in the flightpath.
[0294] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with an idle or inactive measurement configuration in a list of idle or inactive measurement configurations, or a carrier configuration in the idle or inactive measurement configuration, or a SSB measurement configuration in the idle or inactive measurement configuration. In some embodiments, if the terminal device 110 is located in the waypoint or waypoint group or the altitude or altitude range, the terminal device 110 may apply the idle or inactive measurement configuration or the carrier configuration or the SSB measurement configuration.
[0295] In some embodiments, the terminal device 110 may receive, from the network device 120, an indication of reporting results of the idle or inactive measurement for waypoints or waypoint groups or altitudes or altitude ranges. The terminal device 110 may store the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges, and transmit, to the network device, at least part of the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges.
[0296] In some embodiments, the at least part of the results of the idle or inactive measurement may be associated with a set of cells that remain detectable when the terminal device 110 enters a connected state. In some embodiments, the at least part of the results of the idle or inactive measurement may be associated with the waypoints or waypoint groups or altitudes or altitude ranges indicated by the network device 120. In some embodiments, the at least part of the results of the idle or inactive measurement may be associated with the waypoints or waypoint groups or altitudes or altitude ranges belong to the future flightpath (for example, the upcoming N waypoints, N >= 1s) .
[0297] In some embodiments, if a timer for the idle or inactive measurement expires after the terminal device 110 changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to a further waypoint or waypoint group or altitude or altitude range associated with a further configuration for the idle or inactive measurement, the terminal device 110 may restart the idle or inactive measurement. In some embodiments, if the terminal device 110 changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to the further waypoint or waypoint group or altitude or altitude range associated with the further configuration for the idle or inactive measurement, the terminal device 110 may restart the idle or inactive measurement.
[0298] In some embodiments, if the terminal device 110 passes the waypoint or waypoint group, the terminal device 110 may release the configuration associated with the waypoint or waypoint group. In some embodiments, if one or more waypoints or waypoint groups in the flightpath are updated, the terminal device 110 may release one or more configurations associated with the one or more waypoints or waypoint groups.
[0299] In some embodiments, the terminal device 110 may receive, from the network device 120, an indication of removing a configuration associated with a passed waypoint or waypoint group. Based on reception of the indication, the terminal device 110 may release the configuration.
[0300] With the method 400, a conditional cell change and / or an idle or inactive measurement may be enhanced, especially for aerial UE such as UAV.
[0301] Fig. 5 illustrates an example method 500 of communication implemented at a network device in accordance with some embodiments of the present disclosure. For example, the method 500 may be performed at the network device 120 or 130 as shown in Fig. 1. For the purpose of discussion, in the following, the method 500 will be described with reference to Fig. 1. It is to be understood that the method 500 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. It is assumed that the terminal device 110 is served by the network device 120.
[0302] At block 510, the network device 120 may transmit, to the terminal device 110, a set of configurations for a conditional cell change or an idle or inactive measurement. In some embodiments, a configuration in the set of configurations may be associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device 110, or an altitude or altitude range of the terminal device 110.
[0303] In some embodiments, the network device 120 may transmit, to the terminal device 110, information of the waypoint of the flightpath comprising at least one of the following: an index of the waypoint, a location of the waypoint, or a time stamp of the waypoint. In some embodiments, the information of the waypoint may be associated with the configuration in the set of configurations.
[0304] In some embodiments, the network device 120 may transmit, to the terminal device 110, information of the waypoint group of the flightpath comprising at least one of the following: an index of the waypoint group, an index of a first waypoint as a starting point of the waypoint group, or an index of a second waypoint as an ending point of the waypoint group. In some embodiments, the information of the waypoint group may be associated with the configuration in the set of configurations.
[0305] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with at least one of the following: an identity of a conditional reconfiguration for the conditional cell change, a report configuration of the conditional reconfiguration, a conditional reconfiguration in a list of conditional reconfigurations for the conditional cell change, or a RRC reconfiguration in a list of RRC reconfigurations for the conditional cell change.
[0306] In some embodiments, the waypoint or waypoint group or altitude or altitude range may be associated with at least one of the following: an idle or inactive measurement configuration in a list of idle or inactive measurement configurations, a carrier configuration in the idle or inactive measurement configuration, or a SSB measurement configuration in the idle or inactive measurement configuration.
[0307] In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of reporting results of the idle or inactive measurement for waypoints or waypoint groups or altitudes or altitude ranges. In some embodiments, the network device 120 may receive, from the terminal device 110, at least part of the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges.
[0308] In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of a reference waypoint. In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of removing a configuration associated with a passed waypoint or waypoint group. In some embodiments, the network device 120 may transmit, to the terminal device 110, an indication of selecting a first difference value in multiple difference values. In some embodiments, the network device 120 may transmit, to the terminal device 110, information of priority values of multiple configurations associated with multiple altitude ranges.
[0309] With the method 500, enhancement of a conditional cell change and / or an idle or inactive measurement may be facilitated, especially for aerial UE such as UAV.
[0310] It is to be understood that operations of the methods 400 and 500 correspond to that described with reference to Figs. 2 and 3, and thus other details are not repeated here for conciseness.
[0311] EXAMPLE IMPLEMENTATION OF DEVICES
[0312] Fig. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure. The device 600 can be considered as a further example implementation of the terminal device 110 or the network device 120 as shown in Fig. 1. Accordingly, the device 600 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
[0313] As shown, the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a suitable transceiver 640 coupled to the processor 610, and a communication interface coupled to the transceiver 640. The memory 610 stores at least a part of a program 630. The transceiver 640 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 640 may include at least one of a transmitter 642 or a receiver 644. The transmitter 642 and the receiver 644 may be functional modules or physical entities. The transceiver 640 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 / Xn interface for bidirectional communications between eNBs / gNBs, S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, Un interface for communication between the eNB / gNB and a relay node (RN) , or Uu interface for communication between the eNB / gNB and a terminal device.
[0314] The program 630 is assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 1 to 5. The embodiments herein may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 610 and memory 620 may form processing means 650 adapted to implement various embodiments of the present disclosure.
[0315] The memory 620 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 620 is shown in the device 600, there may be several physically distinct memory modules in the device 600. The processor 610 may be of any type suitable to the local technical network, 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. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0316] In some embodiments, a terminal device comprises a circuitry configured to: receive, from a network device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device; determine a first configuration in the set of configurations based on a location of the terminal device; and perform the conditional cell change or the idle or inactive measurement based on the first configuration.
[0317] In some embodiments, a network device comprises a circuitry configured to: transmit, to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of: a waypoint or waypoint group in a flightpath of the terminal device, or an altitude or altitude range of the terminal device.
[0318] The term ‘circuitry’ used herein may refer to hardware circuits and / or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and / or digital hardware circuits with software / firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and / or firmware.
[0319] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0320] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to Figs. 1 to 5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0321] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0322] The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0323] 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 present disclosure, 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.
[0324] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A terminal device, comprising:a processor configured to cause the terminal device to:receive, from a network device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, oran altitude or altitude range of the terminal device;determine a first configuration in the set of configurations based on a location of the terminal device; andperform the conditional cell change or the idle or inactive measurement based on the first configuration.2.The terminal device of claim 1, wherein the terminal device is caused to receive the set of configurations by at least one of the following:receiving, from the network device, information of the waypoint of the flightpath comprising at least one of the following:an index of the waypoint,a location of the waypoint, ora time stamp of the waypoint; orreceiving, from the network device, information of the waypoint group of the flightpath comprising at least one of the following:an index of the waypoint group,an index of a first waypoint as a starting point of the waypoint group, oran index of a second waypoint as an ending point of the waypoint group.3.The terminal device of claim 1, wherein the terminal device is caused to determine the first configuration by:in accordance with a determination that the terminal device arrives at a location of a third waypoint or arrives at the location of the third waypoint at a time indicated by a time stamp of the third waypoint, determining, as the first configuration, a configuration in the set of configurations that is associated with the third waypoint or a waypoint group associated with the third waypoint.4.The terminal device of claim 1, wherein the waypoint or waypoint group or altitude or altitude range is associated with an identity of a conditional reconfiguration in the configuration, and the terminal device is caused to perform the conditional cell change by at least one of the following:in accordance with a determination that the terminal device is located in the waypoint or waypoint group or altitude or altitude range, determining that a set of cells associated with the conditional reconfiguration are applicable cells;in accordance with a determination that the terminal device is located outside of the waypoint or waypoint group or altitude or altitude range, determining that the set of cells are inapplicable cells; orin accordance with a determination that an execution condition for an applicable cell is fulfilled and the terminal device is located in the waypoint or waypoint group or altitude or altitude range, determining the applicable cell as a triggered cell for conditional reconfiguration execution.5.The terminal device of claim 1, wherein the waypoint or waypoint group or altitude or altitude range is associated with a report configuration, and the terminal device is caused to perform the conditional cell change by:in accordance with a determination that the terminal device is located in the waypoint or waypoint group or altitude or altitude range, evaluating an event in the report configuration.6.The terminal device of claim 1, wherein the waypoint or waypoint group or altitude or altitude range is associated with a conditional reconfiguration in a list of conditional reconfigurations, and the terminal device is caused to perform the conditional cell change by:in accordance with a determination that the terminal device is located in the waypoint or waypoint group or altitude or altitude range, applying the conditional reconfiguration.7.The terminal device of claim 1, wherein the waypoint or waypoint group or altitude or altitude range is associated with a radio resource control (RRC) reconfiguration in a list of RRC reconfigurations, and the terminal device is caused to perform the conditional cell change by:in accordance with a determination that the terminal device is located in the waypoint or waypoint group or altitude or altitude range and an execution condition for the RRC reconfiguration is fulfilled, applying the RRC reconfiguration.8.The terminal device of claim 1, wherein the terminal device is caused to perform the conditional cell change by:determining that a set of events for a cell are fulfilled;considering the cell as a triggered cell; andinitiating an execution of a conditional reconfiguration in the configuration.9.The terminal device of claim 8, wherein the set of events comprise at least one of the following:a distance between the terminal device and a first reference waypoint is smaller than or equal to a distance threshold;the distance between the terminal device and the first reference waypoint is larger than or equal to the distance threshold;the distance between the terminal device and the first reference waypoint is larger than or equal to a first distance threshold and a distance between the terminal device and a second reference waypoint is smaller than or equal to a second distance threshold;time measured at the terminal device is within a time duration indicated by a set of reference time stamps; orthe distance between the terminal device and the first reference waypoint is smaller than or equal to the first distance threshold and a time difference between the time measured at the terminal device and a time stamp of the first reference waypoint is smaller than or equal to a time difference threshold.10.The terminal device of claim 9, wherein the terminal device is further caused to:receive, from the network device, an indication of the first or second reference waypoint; ordetermine, as the first or second reference waypoint, a nearest waypoint which has passed; ordetermine, as the first or second reference waypoint, a waypoint to be arrived in the flightpath.11.The terminal device of claim 1, wherein the terminal device is further caused to:in accordance with a determination that the terminal device passes the waypoint or waypoint group, release the configuration associated with the waypoint or waypoint group, orin accordance with a determination that one or more waypoints or waypoint groups in the flightpath are updated, release one or more configurations associated with the one or more waypoints or waypoint groups.12.The terminal device of claim 11, wherein the terminal device is caused to release the configuration by:receiving, from the network device, an indication of removing a configuration associated with a passed waypoint or waypoint group; andreleasing the configuration based on reception of the indication.13.The terminal device of claim 1, wherein the terminal device is caused to determine the first configuration by:in accordance with a determination that multiple configurations associated with multiple altitude ranges are triggered simultaneously, selecting one of the multiple configurations as the first configuration.14.The terminal device of claim 13, wherein the terminal device is caused to select the one of the multiple configurations by:determining multiple difference values between an altitude of the terminal device and multiple altitude thresholds associated with the multiple configurations;selecting a first difference value in the multiple difference values; anddetermining, as the first configuration, one of the multiple configurations that is associated with the first difference value.15.The terminal device of claim 14, wherein the terminal device is caused to select the first difference value by:receiving, from the network device, an indication of selecting the first difference value in the multiple difference values; andselecting the first difference value based on the indication.16.The terminal device of claim 13, wherein the terminal device is caused to select the one of the multiple configurations by:receiving, from the network device, information of priority values of the multiple configurations; andselecting the one of the multiple configurations that has a priority value higher than or equal to a threshold priority value.17.The terminal device of claim 1, wherein the waypoint or waypoint group or altitude or altitude range is associated with an idle or inactive measurement configuration in a list of idle or inactive measurement configurations, or a carrier configuration in the idle or inactive measurement configuration, or a synchronization signal block (SSB) measurement configuration in the idle or inactive measurement configuration, and the terminal device is caused to perform the idle or inactive measurement by:in accordance with a determination that the terminal device is located in the waypoint or waypoint group or the altitude or altitude range, applying the idle or inactive measurement configuration or the carrier configuration or the SSB measurement configuration.18.The terminal device of claim 1, wherein the terminal device is further caused to:receive, from the network device, an indication of reporting results of the idle or inactive measurement for waypoints or waypoint groups or altitudes or altitude ranges;store the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges; andtransmit, to the network device, at least part of the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges.19.The terminal device of claim 18, wherein the terminal device is caused to transmit the at least part of the results of the idle or inactive measurement by:transmitting the at least part of the results of the idle or inactive measurement based on at least one of the following:the at least part of the results of the idle or inactive measurement are associated with a set of cells that remain detectable when the terminal device enters a connected state, orthe at least part of the results of the idle or inactive measurement are associated with the waypoints or waypoint groups or altitudes or altitude ranges indicated by the network device.20.The terminal device of claim 1, wherein the terminal device is further caused to:restart the idle or inactive measurement based on one of the following:a timer for the idle or inactive measurement expires after the terminal device changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to a further waypoint or waypoint group or altitude or altitude range associated with a further configuration for the idle or inactive measurement; orthe terminal device changes from the waypoint or waypoint group or altitude or altitude range associated with the configuration for the idle or inactive measurement to the further waypoint or waypoint group or altitude or altitude range associated with the further configuration for the idle or inactive measurement.21.A network device, comprising:a processor configured to cause the network device to:transmit, to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, oran altitude or altitude range of the terminal device.22.The network device of claim 21, wherein the network device is caused to transmit the set of configurations by at least one of the following:transmitting, to the terminal device, information of the waypoint of the flightpath comprising at least one of the following:an index of the waypoint,a location of the waypoint, ora time stamp of the waypoint; ortransmitting, to the terminal device, information of the waypoint group of the flightpath comprising at least one of the following:an index of the waypoint group,an index of a first waypoint as a starting point of the waypoint group, oran index of a second waypoint as an ending point of the waypoint group.23.The network device of claim 21, wherein the waypoint or waypoint group or altitude or altitude range is associated with at least one of the following:an identity of a conditional reconfiguration for the conditional cell change,a report configuration of the conditional reconfiguration,a conditional reconfiguration in a list of conditional reconfigurations for the conditional cell change, ora radio resource control (RRC) reconfiguration in a list of RRC reconfigurations for the conditional cell change.24.The network device of claim 21, wherein the network device is further caused to at least one of the following:transmit, to the terminal device, an indication of a reference waypoint;transmit, to the terminal device, an indication of removing a configuration associated with a passed waypoint or waypoint group;transmit, to the terminal device, an indication of selecting a first difference value in multiple difference values; ortransmit, to the terminal device, information of priority values of multiple configurations associated with multiple altitude ranges.25.The network device of claim 21, wherein the waypoint or waypoint group or altitude or altitude range is associated with at least one of the following:an idle or inactive measurement configuration in a list of idle or inactive measurement configurations,a carrier configuration in the idle or inactive measurement configuration, ora synchronization signal block (SSB) measurement configuration in the idle or inactive measurement configuration.26.The network device of claim 21, wherein the network device is further caused to:transmit, to the terminal device, an indication of reporting results of the idle or inactive measurement for waypoints or waypoint groups or altitudes or altitude ranges; andreceive, from the terminal device, at least part of the results of the idle or inactive measurement associated with the waypoints or waypoint groups or altitudes or altitude ranges.27.A method of communication, comprising:receiving, at a terminal device and from a network device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, oran altitude or altitude range of the terminal device;determining a first configuration in the set of configurations based on a location of the terminal device; andperforming the conditional cell change or the idle or inactive measurement based on the first configuration.28.A method of communication, comprising:transmitting, at a network device and to a terminal device, a set of configurations for a conditional cell change or an idle or inactive measurement, a configuration in the set of configurations being associated with at least one of:a waypoint or waypoint group in a flightpath of the terminal device, oran altitude or altitude range of the terminal device.