Setting a system frame number counter
By setting the SFN counter to zero during specific handover events, the synchronization issues in non-integer DRX cycles are resolved, ensuring consistent DRX operation across cells during handovers.
Patent Information
- Application Number
- PCT/CN2024/111273
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2026-02-12
AI Technical Summary
In the context of 3GPP release 18 eXtended Reality (XR) discussions, non-integer discontinuous reception (DRX) cycles introduce challenges with SFN wrap around, particularly during handover procedures where source and target cells may have different SFN numbering, leading to synchronization issues and outdated drx-TimeReferenceSFN values.
The SFN counter (DRX_SFN_COUNTER) is set to zero upon specific events during handover, such as transmission of a response message, reception of a contention resolution message, or reception of a random access response, ensuring synchronization and correct DRX cycle continuation.
This approach ensures accurate DRX_SFN_COUNTER maintenance during handovers, even when RRC reconfiguration timing differs from actual handover execution, maintaining consistent DRX operation across cells.
Smart Images

Figure CN2024111273_12022026_PF_FP_ABST
Abstract
Description
SETTING A SYSTEM FRAME NUMBER COUNTER
[0001] FIELDS
[0002] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for setting a system frame number (SFN) counter.BACKGROUND
[0003] Non-integer discontinuous reception (DRX) cycle has been introduced in the context of 3rd Generation Partnership Project (3GPP) release18 eXtended Reality (XR) discussions since the XR traffic periodicities are typically non-integer values. To avoid glitches at SFN wrap around, DRX_SFN_COUNTER was introduced to ensure the DRX cycle continues after the SFN wrap around.SUMMARY
[0004] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a network apparatus, a first message for a handover associated with a first cell; and set a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access; or reception of a random access response from the first cell.
[0005] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: determine that a first apparatus is to switch to a first cell; and set a system frame number (SFN) counter to zero upon one of the following: a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command; transmission of a contention resolution message for random access from the first cell, ; transmission of a random access response from the first cell; or reception of a response message to a first message comprising a handover command.
[0006] In a third aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a network apparatus, a first message for a handover associated with a first cell; and setting a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access; or reception of a random access response from the first cell.
[0007] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: determining that a first apparatus is to switch to a first cell; and setting a system frame number (SFN) counter to zero upon one of the following: a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command; transmission of a contention resolution message for random access from the first cell, ; transmission of a random access response from the first cell; or reception of a response message to a first message comprising a handover command.
[0008] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a network apparatus, a first message for a handover associated with a first cell; and means for setting a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access; or reception of a random access response from the first cell.
[0009] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for determining that a first apparatus is to switch to a first cell; and means for setting a system frame number (SFN) counter to zero upon one of the following: a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command; transmission of a contention resolution message for random access from the first cell, ; transmission of a random access response from the first cell; or reception of a response message to a first message comprising a handover command.
[0010] In a seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.
[0011] In an eighth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
[0012] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0014] FIG. 1 illustrates an example signaling flow of handover procedure;
[0015] FIG. 2 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0016] FIG. 3 illustrates a signaling flow of communication in accordance with some embodiments of the present disclosure;
[0017] FIG. 4 illustrates a flowchart of a method implemented at a first apparatus according to some example embodiments of the present disclosure;
[0018] FIG. 5 illustrates a flowchart of a method implemented at a second apparatus according to some example embodiments of the present disclosure;
[0019] FIG. 6 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0020] FIG. 7 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0021] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0022] Principle of the present disclosure will now be described with reference to some example 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 limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0023] 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.
[0024] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0025] It shall be understood that although the terms “first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0026] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0027] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0029] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[0030] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0031] (b) combinations of hardware circuits and software, such as (as applicable) :
[0032] (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and
[0033] (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0034] (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0035] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0036] 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) communication protocols, 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.
[0037] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0038] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0039] As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
[0040] As discussed above, in the wireless communications, the non-integer DRX cycle has been introduced in the context of 3GPP release18 XR discussions since the XR traffic periodicities are typically non-integer values. To avoid glitches at SFN wrap around, DRX_SFN_COUNTER was introduced to ensure the DRX cycle continues after the SFN wrap around.
[0041] Radio resource control (RRC) controls DRX operation by configuring the parameters such as: drx-onDurationTimer: the duration of UE staying active at the beginning of a DRX cycle; drx-SlotOffset: the delay before starting the drx-onDurationTimer; drx-TimeReferenceSFN: the configuration to indicate how UE initializes DRX_SFN_COUNTER and so on.
[0042] DRX_SFN_COUNTER may be used for the DRX operation, where the DRX_SFN_COUNTER is a counter that increments when SFN changes to 0 and the maximum value of this counter is at least 65535.
[0043] Example operations about how to set the value of DRX_SFN_COUNTER are discussed as below. As one example, if the drx-NonIntegerLongCycleStartOffset is configured, DRX_SFN_COUNTER is incremented by 1 in the first symbol of a slot in which SFN changes to 0. When DRX is configured or reconfigured by RRC signaling, if drx-TimeReferenceSFN is included in the RRC (re-) configuration which is received during the first half of a hyper frame (i.e., SFN is between 0 and 511) , DRX_SFN_COUNTER is set to 1, else DRX_SFN_COUNTER is set to 0.
[0044] So far, there are still open issues whether, during handover (HO) procedures, source cell, target cell and UE will be synchronized to apply the same drx-TimeReferenceSFN to initialize their DRX_SFN_COUNTER when UE receives RRC (re-) configuration that includes drx-TimeReferenceSFN.
[0045] Reference is now made to FIG. 1, which an example signaling flow of handover procedure.
[0046] In some cases, the source gNB and target gNB might have different SFN numbering for asynchronies system, and thus SFN timing offset is exchanged between the source gNB and target gNB.
[0047] IE SFN Offset contains the time offset between an absolute time reference and the SFN0 start. The IE is calculated assuming that the SFN transmission started at the absolute time reference. The absolute time reference chosen is 1980-01-06 T00: 00: 19 International Atomic Time (TAI) . Below Table illustrates details about the IE SFN Offset.
[0048] Table IE SFN Time Offset
[0049] In FIG. 1, the RRC reconfiguration with HO command (4) from source gNB includes the drx-TimeReferenceSFN set by the target gNB. The SFN timing offset is exchanged between the gNBs and the target gNB might be able to take the SFN difference into account when setting the drx-TimeReferenceSFN value.
[0050] The UE sets the SFN counter according to reception time of HO command of source SFN (RRCReconfiguration in step 4) .
[0051] If it is assumed the HO procedure may be completed within an SFN frame (e.g., 10s) , it seems to be no issue with current procedure based on the reception timing of RRC reconfiguration from the source gNB as the target gNB could take the SFN time offset into account.
[0052] However, the duration of HO procedure may be unpredictable due to, for example, complicated communication condition. For example, in a case of conditional handover (CHO) / layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) , for which cases HO execution is only done when the configured condition is met, the time point that the CHO / LTM condition is met might be much later than the reception of the RRC reconfiguration message with CHO / LTM configuration. Thus, the drx-TimeReferenceSFN and the receiving time of the HO command would become irrelevant for DRX_SFN_COUNTER settting. That is, HO execution might be done much later than RRC reconfiguration with CHO / LTM, and therefore, the drx-TimeReferenceSFN and the receiving time of the HO command would become out-dated.
[0053] Besides, the RRC configurations are applied upon reception of RRC reconfiguration message for non-HO case, while for HO case, the configuration of target cell only happens after the HO is completed, i.e., after RRC reconfiguration complete is sent. For example, DRX RRC (re) configuration for non-HO case is applied upon reception of the RRC (re) configuration message (after the RRC processing) while DRX (re) configuration for HO case is applied upon transmission of RRC reconfiguration complete message to target cell.
[0054] It may be concluded that the HO case has many differences compared with the non-HO case, such as, the drx-TimeReferenceSFN might become outdated if the actual HO execution comes much later than the RRC reconfiguration; the timing for applying the DRX configuration is different for normal RRC reconfiguration (without HO) and HO case, where for the former, the DRX configuration is applied after the processing of the RRC reconfiguration, i.e., before sending the RRC complete message, while for the latter, it is only applied after the HO completion.
[0055] According to the example of the present discourse, the SFN counter (DRX_SFN_COUNTER) may be maintained correctly in HO case. In this solution, a first apparatus (such as, a terminal device) receives, from a network apparatus, a first message for a handover associated with a first cell; and sets a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access; or reception of a random access response from the first cell.
[0056] In the context of the present disclosure, “non-integer cycle” is used as an example application scenario for describing some specific example embodiments of the present disclosure. It is noted that such example embodiments described are only for the purpose of illustration without suggesting any limitations. In fact, the operation of SFN counter setting may be needed in other application scenarios, and the solution for setting SFN counter discussed herein may also be applicable to the other application scenarios.
[0057] In the context of the present disclosure, “DRX non-integer cycle” is used as an example application procedure for describing some specific example embodiments of the present disclosure. It is noted that such example embodiments described are only for the purpose of illustration without suggesting any limitations. In fact, the non-integer cycle operation may be applied in other procedures, such as, a discontinuous transmission (DTX) procedure, a configured grant procedure and so on.
[0058] Further, CHO-based HO and LTM-based HO are used as examples of assistance information for describing some specific example embodiments of the present disclosure. It is noted that such example embodiments described are only for the purpose of illustration without suggesting any limitations. CHO / LTM-based HO may be replaced by any HO procedure (the execution of which takes longer than 10 s, the execution of which is not completed within a SFN space, or the execution of which is not completed within a hyper frame ) .
[0059] Moreover, the term “transmission of X” may refer to a starting transmission of X, an ending transmission of X, reception feedback / acknowledgment of transmission of X and so on. The term may refer to “areception of X” may refer to a starting reception of X, an ending reception of X, correct decoding of X, correct processing of X and so on. In summary, transmission / reception used herein may refer to any suitable time points that is related with the transmitting / receiving behavior.
[0060] Example Environment
[0061] FIG. 2 shows an example communication environment 200 in which example embodiments of the present disclosure may be implemented. The network communication 200 includes a first apparatus 210, a second apparatus 220-1 and optional second apparatuses 220-2. In the following text, the second apparatuses 220-1 and 220-2 are collectively referred to as the second apparatuses 220 or individually referred to as the second apparatus 220. Additionally, the second apparatuses 220 may provide one or more coverage areas, also called as cells.
[0062] The communication environment 200 comprises cell 230-1 and 230-2. In some embodiments, different cells may be provided by different second apparatus 220. Alternatively, in some embodiments, a same second apparatus 220 may provide more than one cell. For example, in some embodiments, the cell 230-1 and 230-2 may be provided by the second apparatus 220-1 / 220-2. In some other embodiments, cell 230-1 and 230-2 may be provided by the second apparatus 220-2 and the second apparatus 220-1, respectively.
[0063] Further, in the actual communication scenario, the first apparatus 210 may move over time, which cause a cell switch. In the example of FIG. 2, as moving, the first apparatus 210 may switch from the cell 230-2 to the cell 230-1. In case that the cells 230-1 and 230-2 are provided by a same second apparatus 220, the cell switch is referred to as an intra-gNB HO, and in case that the cells 230-1 and 230-2 are provided by different second apparatuses 220, the cell switch is referred to as an inter-gNB HO. It is noted that, the solution proposed in this present disclosure may be applicable to both intra-gNB HO and inter-gNB HO.
[0064] In some example embodiments, the first apparatus 210 may be comprised in a terminal device / apparatus, e.g., UE, and the second apparatus 220 may be comprised in a network device / apparatus serving the terminal device / apparatus. The network device may be e.g., gNB, for example, source gNB or target gNB.
[0065] In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 210 operating as a terminal apparatus and the second apparatus 220 operating as a network apparatus. However, in some example embodiments, operations described in connection with a terminal apparatus may be implemented at a network apparatus or other apparatus, and operations described in connection with a network apparatus may be implemented at a terminal apparatus or other apparatus.
[0066] In some example embodiments, if the first apparatus 210 is a terminal apparatus and the second apparatus 220 is a network apparatus, a link from the second apparatus 220 to the first apparatus 210 is referred to as a downlink (DL) , while a link from the first apparatus 210 to the second apparatus 220 is referred to as an uplink (UL) . In DL, the second apparatus 220 is a transmitting (TX) apparatus (or a transmitter) and the first apparatus 210 is a receiving (RX) apparatus (or a receiver) . In UL, the first apparatus 210 is a TX apparatus (or a transmitter) and the second apparatus 220 is a RX apparatus (or a receiver) .
[0067] It is to be understood that the number of devices and their connections shown in first apparatus 210 are only for the purpose of illustration without suggesting any limitation. The communication environment 200 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell, and one or more additional cells may be deployed in the communication environment 200. It is noted that although illustrated as a network device, the second apparatus 220 may be another device than a network device. Although illustrated as a terminal device, the first apparatus 210 may be another device than a terminal device.
[0068] Communications in the communication environment 200 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , 5.5G, the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0069] Work Principle and Example Signaling for Communication
[0070] Details will be discussed with reference to FIG. 3, which illustrates a signaling flow 300 of communication in accordance with some embodiments of the present disclosure. For the purposes of discussion, the signaling flow 300 will be discussed with reference to FIG. 2, for example, by using the first apparatus 210 and the second apparatus 220, where the first apparatus 210 may function as a terminal apparatus and the second apparatus 220 may function as a network apparatus. Further, the first apparatus 210 is served by the second cell 230-2 and is to switch to the first cell 230-1.
[0071] It is to be understood that the operations at the first apparatus 210 and the second apparatus 220 should be coordinated. In other words, the second apparatus 220 and the first apparatus 210 should have a common understanding about configurations, parameters and so on. Such a common understanding may be implemented by any suitable interactions between the second apparatus 220 and the first apparatus 210 or both the second apparatus 220 and the first apparatus 210 applying the same rule, policy, and / or the like.
[0072] In the following, although some operations are described from a perspective of the first apparatus 210, it is to be understood that the corresponding operations should be performed by the second apparatus 220. Similarly, although some operations are described from a perspective of the second apparatus 220, it is to be understood that the corresponding operations should be performed by the first apparatus 210. For example, if the second apparatus 220 transmits a message to the first apparatus 210, it is considered that the first apparatus 210 receives the message. As another example, if the first apparatus 210 receives a message from the second apparatus 220, it is considered that the second apparatus 220 transmits the message. Merely for brevity, some of the same or similar contents are omitted here.
[0073] Example processes at the first apparatus 210 will be discussed first. As illustrated in FIG. 3, in operation, the first apparatus 210 receives (330-2) a first message for a handover associated with a first cell 230-1 (such as, an RRC reconfiguration message) from a network apparatus providing the source cell (second cell 230-2) . The first message may include HO command. In the example of FIG. 3, the second apparatus 220-1 transmits (330-1) the first message to the first apparatus 210. The first apparatus 210 may initiate or perform the handover or cell switch according to the configuration provided in the first message.
[0074] In some example embodiments, the first cell 230-1 (target cell) may be provided by the network apparatus providing the source cell or by a second apparatus 220 different from the network apparatus providing the source cell. That is, both intra-gNB HO and inter-gNB HO are applicable.
[0075] In some example embodiments, the first apparatus 210 may be configured with a non-integer cycle configuration.
[0076] In some example embodiments, the non-integer cycle configuration may be one of the following: a DRX non-integer cycle configuration (such as, drx-NonIntegerLongCycleStartOffset) , a discontinuous transmission, DTX, non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0077] Then, the first apparatus 210 sets the SFN counter according to the communication 340 on the first cell 230-1. SFN counter may be referred to as DRX_SFN_COUNTER or DRX SFN COUNTER. DRX_SFN_COUNTER may be referred to as SFN counter. According to the example embodiments of the present discourse, example communication may be one of: transmission of a second message comprising a response to the first message (such as, RRC reconfiguration complete (RRCReconfigurationcomplete) message) , or a random access channel (RACH) procedure including both contention-based random access (CBRA) and contention-free random access (CFRA) .
[0078] Specifically, in some cases, the first apparatus 210 sets SFN counter to zero upon transmission of a second message to the first cell 230-1, where the second message comprise a response to the first message. The second message may comprise, e.g., RRC reconfiguration complete message. Alternatively, in some other cases, the first apparatus 210 sets SFN counter to zero upon reception of a contention resolution message (Msg B or Msg 4) for random access from the first cell 230-1, such as, for CBRA case. Alternatively, in some other cases, the first apparatus 210 sets SFN counter to zero upon reception of a random access response from the first cell 230, such as, for CFRA case.
[0079] Alternatibely, or in addition, in some embodiments, the first apparatus 210 may ignore a parameter for initializing the SFN counter that is comprised in the first message, such as, drx-TimeReferenceSFN.
[0080] In some example embodiments, the first message may be an RRC reconfiguration message with a HO configuration. Alternatively, in some example embodiments, the first message may be an RRC reconfiguration message with a CHO configuration. Alternatively, in some example embodiments, the first message may be an RRC reconfiguration message with an LTM configuration.
[0081] Example embodiments for non-HO case are discussed below. In operation, the first apparatus 210 receives from the network apparatus 220-1 a third message without comprising a handover-related configuration (such as, without comprising a CHO configuration, or an LTM configuration, or other HO configurations) . Examples of handover-related configuration messages comprise conditionalReconfiguration and ltm-Config.
[0082] In this event, the first apparatus 210 may set the SFN counter to one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter.
[0083] Alternatively, the first apparatus 210 may set the SFN counter to zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0084] Example processes at the second apparatus 220 will be discussed in the following. In operation, the second apparatus 220 determines that a first apparatus 210 is to switch to a first cell 230-1. The second apparatus 220 provides the first cell 230-1. In a case of intra-gNB, the second apparatus 220 is the second apparatus 220-1, and in a case of inter-gNB, the second apparatus 220 is the second apparatus 220-2.
[0085] In some example embodiments, the first apparatus 210 may be configured with a non-integer cycle configuration. In some example embodiments, the non-integer cycle configuration may be one of the following: a discontinuous reception, DRX, non-integer cycle configuration, a discontinuous transmission, DTX, non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0086] Similar with the example processes at the first apparatus 210, the second apparatus 220 also sets the SFN counter according to the communication 340 on the first cell 230-1. It should be noted that, the SFN setting operation at the second apparatus 220 should be consistent with or correspond with that at the first apparatus 210.
[0087] In some cases, the second apparatus 220 sets the SFN counter to zero upon a scheduled time for transmitting a second message from the first apparatus 210 to the second apparatus 220, where a second message comprises a response of a first message and the first message comprises a handover command. Alternatively, in some other cases, the second apparatus 220 sets the SFN counter to zero upon reception of a response message to a first message comprising a handover command.
[0088] Alternatively, in some other cases, the second apparatus 220 sets the SFN counter to zero upon transmission of a contention resolution message for random access from the first cell 230-1. Alternatively, in some other cases, the second apparatus 220 sets the SFN counter to zero upon transmission of a random access response from the first cell 230-1.
[0089] In some example embodiments, the first message may be an RRC reconfiguration message with a HO configuration. Alternatively, in some example embodiments, the first message may be an RRC reconfiguration message with a CHO configuration. Alternatively, in some example embodiments, the first message may be an RRC reconfiguration message with an LTM configuration.
[0090] In a case of inter-gNB HO (the source cell is provided by the second apparatus 220-1 and the target cell is provided by the second apparatus 220-2) , additional signalling interactions are needed. Specifically, the second apparatus 220-1 may transmit (310-1) a handover request for the first apparatus 210 to the second apparatus 220-2, and the second apparatus 220-2 may receive (310-2) the handover request accordingly.
[0091] Then the second apparatus 220-2 may transmit (320-1) an acknowledge message for the handover request to the second apparatus 210-1 (such as, for indicating the admission control for the first apparatus 210 is allowed) , and the second apparatus 220-1 may receive (320-2) the acknowledge message accordingly. Based on the acknowledge message, an RRC reconfiguration may be transmitted to the first apparatus 210. In some example embodiments, in a case that the acknowledge message comprises a parameter for initializing the SFN counter, the second apparatus 220-2 may ignore the parameter for initializing the SFN counter comprised in the acknowledge message when setting the SFN counter.
[0092] Example embodiments for non-HO case are discussed below. In this event, the second apparatus 220-1 may transmit a third message without comprising a handover-related configuration (such as, without comprising a CHO configuration, an LTM configuration, or other HO configurations) to the first apparatus 210.
[0093] Then, the second apparatus 220-1 may set the SFN counter to be one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter. Alternatively, the second apparatus 220-1 may set the SFN counter to be zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0094] An example operation of the above example processes is described below.
[0095] 1> if the drx-NonIntegerLongCycleStartOffset is configured:
[0096] 2> increment DRX_SFN_COUNTER by 1 in the first symbol of a slot in which SFN changes to 0;
[0097] 2> if DRX is (re-) configured by RRC without conditionalReconfiguration nor ltm-Config:
[0098] 3> if drx-TimeReferenceSFN is included in the RRC (re-) configuration which is received during the first half of a hyper frame (i.e., SFN is between 0 and 511) :
[0099] 4> set DRX_SFN_COUNTER to 1.
[0100] 3> else:
[0101] 4> set DRX_SFN_COUNTER to 0.
[0102] 2> else:
[0103] 3> set DRX_SFN_COUNTER to 0 upon transmission of RRCReconfigurationcomplete message.
[0104] According to the above example processes, it may be ensured that DRX_SFN_COUNTER is set correctly even if the RRC reconfiguration comes much earlier than the actual HO execution for such as CHO-based HO and LTM-based HO.
[0105] As an example, for CHO / LTM, DRX_SFN_COUNTER is initiated to 0 upon HO complete regardless of the drx-TimeReferenceSFN.
[0106] As an example, for CHO-based HO and / or LTM-based HO, DRX_SFN_COUNTER is initiated or set to 0 upon HO complete regardless of the drx-TimeReferenceSFN.
[0107] As an example, for CHO-based HO, DRX_SFN_COUNTER is set to 0 upon HO complete regardless of the drx-TimeReferenceSFN.
[0108] As an example, for LTM-based HO, DRX_SFN_COUNTER is set to 0 upon HO complete regardless of the drx-TimeReferenceSFN.
[0109] Example Method
[0110] FIG. 4 shows a flowchart of an example method 400 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the first apparatus 210 in FIG. 2.
[0111] At block 410, the first apparatus 210 receives, from a network apparatus, a first message for a handover associated with a first cell.
[0112] At block 420, the first apparatus 210 sets a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access, or reception of a random access response from the first cell.
[0113] In some example embodiments, the first apparatus may be configured with a non-integer cycle configuration.
[0114] In some example embodiments, the non-integer cycle configuration may be one of the following: a discontinuous reception, DRX, non-integer cycle configuration, a discontinuous transmission, DTX, non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0115] In some example embodiments, the first message may be one of the following: a radio resource control, RRC, reconfiguration message with a conditional handover, CHO, configuration, an RRC reconfiguration message with a handover configuration or an RRC reconfiguration message with a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.
[0116] In some example embodiments, the first apparatus may comprise: ignore a parameter for initializing the SFN counter that is comprised in the first message.
[0117] In some example embodiments, the first apparatus may receive, from the network apparatus, a third message without comprising a handover-related configuration; set the SFN counter to one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; and set the SFN counter to zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0118] In some example embodiments, the handover-related configuration may be one of the following: a handover configuration, a conditional handover, CHO, configuration, or a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.
[0119] In some example embodiments, the first cell may be provided by the network apparatus or by a second apparatus different from the network apparatus.
[0120] In some example embodiments, the first apparatus is a terminal apparatus.
[0121] The first apparatus may comprise one or more entities of any of protocol layers, such as a medium access control (MAC) entity, an RRC entity, a radio link control (RLC) entity, a packet data convergence protocol (PDCP) entity or a physical (PHY) entity. In some embodiments, the entity is configured to perform at least the method of FIG. 4, and / or any one or more of the embodiments described.
[0122] FIG. 5 shows a flowchart of an example method 500 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the second apparatus 220 in FIG. 2.
[0123] At block 510, the second apparatus determines that a first apparatus is to switch to a first cell.
[0124] At block 520, the second apparatus sets a system frame number (SFN) counter to zero upon one of the following: a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command; transmission of a contention resolution message for random access from the first cell; transmission of a random access response from the first cell; reception of a response message to a first message comprising a handover command.
[0125] In some example embodiments, the second apparatus may be configured with a non-integer cycle configuration.
[0126] In some example embodiments, the non-integer cycle configuration may be one of the following: a discontinuous reception (DRX) non-integer cycle configuration, a discontinuous transmission (DTX) non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0127] In some example embodiments, the first message may be one of the following: a radio resource control (RRC) reconfiguration message with a conditional handover (CHO) configuration, or an RRC reconfiguration message with a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) configuration.
[0128] In some example embodiments, the second apparatus may transmit, to the first apparatus, a third message without comprising a handover-related configuration; set the SFN counter to be one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; and set the SFN counter to be zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0129] In some example embodiments, the handover-related configuration may be one of the following: a handover configuration, a conditional handover (CHO) configuration, or a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) configuration.
[0130] In some example embodiments, the second apparatus may receive, from the network apparatus, a handover request for the first apparatus; transmit, to the network apparatus, an acknowledge message for the handover request. The acknowledge message comprises a parameter for initializing the SFN counter, the second apparatus may ignore the parameter for initializing the SFN counter comprised in the acknowledge message.
[0131] In some example embodiments, the first apparatus is a terminal apparatus and the second apparatus is a network apparatus.
[0132] Example Apparatus, Device and Medium
[0133] In some example embodiments, a first apparatus capable of performing any of the method 400 (for example, the first apparatus 210 in FIG. 2) may comprise means for performing the respective operations of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 210 in FIG. 2.
[0134] In some example embodiments, the first apparatus comprises means for receiving, from a network apparatus, a first message for a handover associated with a first cell; and means for setting a system frame number, SFN, counter to zero upon one of the following: transmission of a second message to the first cell, the second message comprising a response to the first message; reception of a contention resolution message from the first cell for random access; or reception of a random access response from the first cell.
[0135] In some example embodiments, the first apparatus is configured with a non-integer cycle configuration.
[0136] In some example embodiments, the non-integer cycle configuration may be one of the following: a discontinuous reception, DRX, non-integer cycle configuration, a discontinuous transmission, DTX, non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0137] In some example embodiments, the first message may be one of the following: a radio resource control, RRC, reconfiguration message with a conditional handover, CHO, configuration, an RRC reconfiguration message with a handover configuration or an RRC reconfiguration message with a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.
[0138] In some example embodiments, the first apparatus further comprises: ignore a parameter for initializing the SFN counter that is comprised in the first message.
[0139] In some example embodiments, the first apparatus further comprises: means for receiving, from the network apparatus, a third message without comprising a handover-related configuration; means for setting the SFN counter to one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; and means for setting the SFN counter to zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0140] In some example embodiments, the handover-related configuration may be one of the following: a handover configuration, a conditional handover, CHO, configuration, or a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.
[0141] In some example embodiments, the first cell is provided by the network apparatus or by a second apparatus different from the network apparatus.
[0142] In some example embodiments, the first apparatus is a terminal apparatus.
[0143] In some example embodiments, a second apparatus capable of performing any of the method 500 (for example, the second apparatus 220 in FIG. 2) may comprise means for performing the respective operations of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 220 in FIG. 2.
[0144] In some example embodiments, the second apparatus comprises means for determining that a first apparatus is to switch to a first cell; and means for setting a system frame number (SFN) counter to zero upon one of the following: a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command; transmission of a contention resolution message for random access from the first cell, ; transmission of a random access response from the first cell; or reception of a response message to a first message comprising a handover command.
[0145] In some example embodiments, the first apparatus is configured with a non-integer cycle configuration.
[0146] In some example embodiments, the non-integer cycle configuration may be one of the following: a discontinuous reception (DRX) non-integer cycle configuration, a discontinuous transmission (DTX) non-integer cycle configuration, or a configured grant non-integer cycle configuration.
[0147] In some example embodiments, the first message may be one of the following: a radio resource control (RRC) reconfiguration message with a conditional handover (CHO) configuration, or an RRC reconfiguration message with a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) configuration.
[0148] In some example embodiments, the second apparatus further comprises: means for transmitting, to the first apparatus, a third message without comprising a handover- related configuration; means for setting the SFN counter to be one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; and means for setting the SFN counter to be zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.
[0149] In some example embodiments, the handover-related configuration may be one of the following: a handover configuration, a conditional handover (CHO) configuration, or a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) configuration.
[0150] In some example embodiments, the second apparatus further comprises: means for receiving, from the network apparatus, a handover request for the first apparatus; means for transmitting, to the network apparatus, an acknowledge message for the handover request, wherein the acknowledge message comprises a parameter for initializing the SFN counter, and the second apparatus is further caused to: means for ignoring the parameter for initializing the SFN counter comprised in the acknowledge message.
[0151] In some example embodiments, the first apparatus is a terminal apparatus and the second apparatus is a network apparatus.
[0152] FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing example embodiments of the present disclosure. The device 600 may be provided to implement a communication device, for example, the first apparatus 210 or the second apparatus 220 as shown in FIG. 2. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.
[0153] The communication module 640 is for bidirectional communications. The communication module 640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 640 may include at least one antenna.
[0154] The processor 610 may be of any type suitable to the local technical network and may include one or more of the following: 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.
[0155] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.
[0156] A computer program 630 includes computer executable instructions that are executed by the associated processor 610. The instructions of the program 630 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 630 may be stored in the memory, e.g., the ROM 624. The processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 622.
[0157] The example embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 5. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0158] In some example embodiments, the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600. The device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0159] FIG. 7 shows an example of the computer readable medium 700 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 700 has the program 630 stored thereon.
[0160] 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, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method 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.
[0161] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. 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.
[0162] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code 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 code, 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.
[0163] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0164] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer 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 computer 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.
[0165] Further, although 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, although 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. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0166] Although the present disclosure has been described in languages 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
A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:receive, from a network apparatus, a first message for a handover associated with a first cell; andset a system frame number, SFN, counter to zero upon one of the following:- transmission of a second message to the first cell, the second message comprising a response to the first message;- reception of a contention resolution message from the first cell for random access; or- reception of a random access response from the first cell.The first apparatus of claim 1, wherein the first apparatus is configured with a non-integer cycle configuration.The first apparatus of claim 1 or 2, wherein the non-integer cycle configuration is one of the following:a discontinuous reception, DRX, non-integer cycle configuration,a discontinuous transmission, DTX, non-integer cycle configuration, ora configured grant non-integer cycle configuration.The first apparatus of any of claims 1 to 3, wherein the first message is one of the following:a radio resource control, RRC, reconfiguration message with a conditional handover, CHO, configuration,an RRC reconfiguration message with a handover configuration, oran RRC reconfiguration message with a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.The first apparatus of any of claims 1 to 4, wherein the first apparatus is further caused to: ignore a parameter for initializing the SFN counter that is comprised in the first message.The first apparatus of any of claims 1 to 5, wherein the first apparatus is further caused to:receive, from the network apparatus, a third message without comprising a handover-related configuration;set the SFN counter to one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; andset the SFN counter to zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.The first apparatus of claim 6, wherein the handover-related configuration is one of the following:a handover configuration,a conditional handover, CHO, configuration, ora layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.The first apparatus of any of claims 1 to 7, wherein the first cell is provided by the network apparatus or by a second apparatus different from the network apparatus.The first apparatus of any of claims 1 to 8, wherein the first apparatus is a terminal apparatus.A second apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:determine that a first apparatus is to switch to a first cell; andset a system frame number, SFN, counter to zero upon one of the following:- a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command;- transmission of a contention resolution message for random access from the first cell;- transmission of a random access response from the first cell; or- reception of a response message to a first message comprising a handover command.The second apparatus of claim 10, wherein the first apparatus is configured with a non-integer cycle configuration.The second apparatus of claim 10 or 11, wherein the non-integer cycle configuration is one of the following:a discontinuous reception, DRX, non-integer cycle configuration,a discontinuous transmission, DTX, non-integer cycle configuration, ora configured grant non-integer cycle configuration.The second apparatus of any of claims 10 to 12, wherein the first message is one of the following:a radio resource control, RRC, reconfiguration message with a conditional handover, CHO, configuration,an RRC reconfiguration message with a handover configuration, oran RRC reconfiguration message with a layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.The second apparatus of any of claims 10 to 13, wherein the first cell is provided by the second apparatus, and the second apparatus is further caused to:transmit, to the first apparatus, a third message without comprising a handover-related configuration;set the SFN counter to be one in accordance with a determination that the third message is received during a first half of a hyper frame and comprises a parameter for initializing the SFN counter; andset the SFN counter to be zero in accordance with a determination that the third message does not comprise the parameter for initializing the SFN counter or the third message is received during a second half of a hyper frame.The second apparatus of claim 14, wherein the handover-related configuration is one of the following:a handover configuration,a conditional handover, CHO, configuration, ora layer 1 / layer 2, L1 / L2, triggered mobility, LTM, configuration.The second apparatus of any of claims 10 to 13, wherein the first cell is provided by a network apparatus different from the second apparatus, and the second apparatus is further caused to:receive, from the network apparatus, a handover request for the first apparatus;transmit, to the network apparatus, an acknowledge message for the handover request, wherein the acknowledge message comprises a parameter for initializing the SFN counter, and the second apparatus is further caused to:ignore the parameter for initializing the SFN counter comprised in the acknowledge message.The second apparatus of any of claims 10 to 16, wherein the first apparatus is a terminal apparatus and the second apparatus is a network apparatus.A method comprising:receiving, from a network apparatus, a first message for a handover associated with a first cell; andsetting a system frame number, SFN, counter to zero upon one of the following:- transmission of a second message to the first cell, the second message comprising a response to the first message;- reception of a contention resolution message from the first cell for random access; or- reception of a random access response from the first cell.A method comprising:determining that a first apparatus is to switch to a first cell; andsetting a system frame number, SFN, counter to zero upon one of the following:- a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command;- transmission of a contention resolution message for random access from the first cell;- transmission of a random access response from the first cell; or- reception of a response message to a first message comprising a handover command.A first apparatus comprising:means for receiving, from a network apparatus, a first message for a handover associated with a first cell; andmeans for setting a system frame number, SFN, counter to zero upon one of the following:- transmission of a second message to the first cell, the second message comprising a response to the first message;- reception of a contention resolution message from the first cell for random access; or- reception of a random access response from the first cell.A second apparatus comprising:means for determining that a first apparatus is to switch to a first cell; andmeans for setting a system frame number, SFN, counter to zero upon one of the following:- a scheduled time for transmitting a second message from the first apparatus to the second apparatus, wherein a second message comprises a response of a first message, wherein the first message comprises a handover command;- transmission of a contention resolution message for random access from the first cell;- transmission of a random access response from the first cell; or- reception of a response message to a first message comprising a handover command.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 19 or the method of claim 20.
Citation Information
Patent Citations
Mobility management method, device and system
CN104854908A
Data forwarding and retransmission method and device
CN113840342A
Method and device for adjusting discontinuous reception in connected state
CN117793863A
Handoff for satellite communication
US20170230104A1
Communication method, base station and user equipment
WO2013086677A1