RRC State Transition Report

Abstract

Embodiments of the present disclosure relate to an apparatus, a method, a device, and a computer-readable storage medium for status transition reporting. The method includes: at a first device, determining a DRX configuration for a second device in an inactive state, the second device being located in an area served by one or more devices including the first device; determining configuration information at least partially based on the DRX configuration; and sending the configuration information to a third device in a core network to cause the third device to adjust downlink transmissions for the second device. In this way, the core network can determine when a UE is reachable and accordingly adjust transmissions associated with paging. Therefore, a longer eDRX cycle can be achieved without increasing the buffering burden at the RAN.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for radio resource control (RRC) state transition reporting. Background Art

[0002] In a traditional communication network, such as in an LTE system, a terminal device (e.g., a UE) may utilize extended discontinuous reception (eDRX) in the RRC idle state. During a paging transmission window (PTW) of each eDRX cycle, the UE monitors a paging channel for a paging message that includes the UE identity. Since the mobility management entity (MME) on the core network (CN) side knows the eDRX configuration of the UE, such as the paging hyperframe (PH) number and the start of the PTW, the MME can send a paging request to a base station (e.g., an eNB) of the radio access network (RAN) just before the start of the PTW or during the PTW, so that the eNB can prevent storing paging messages and excessive data transmission.

[0003] As communication technology evolves to the fifth generation (5G) new radio (NR), an RRC inactivity state is introduced. A UE in the RRC inactivity state can operate in a state where it can utilize eDRX while moving within a radio access network (RAN)-based notification area (RNA) without notifying the RAN. The RNA may cover more than one cell provided by multiple base stations (e.g., gNBs), which includes an anchor gNB that communicates with the access and mobility management function (AMF) at the CN and can perform an RRC connection recovery process for the UE, and the previous gNB serving the UE may retain the UE context data. When the previous serving gNB receives downlink (DL) data or a DL transmission from the AMF, the anchor gNB broadcasts a paging message in all cells of the RNA. The RAN node can notify the AMF of a state transition related to the inactivity state, i.e., the UE enters or leaves the inactivity state, through an RRC inactivity transition reporting process. From the perspective of the CN, limited knowledge about the eDRX configuration of the UE can be inferred from the RRC inactivity transition report. Summary of the Invention

[0004] Generally, example embodiments of the present disclosure provide a solution for RRC state transition reporting.

[0005] In a first aspect, a first device is provided. The first device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, by using the at least one processor, cause the first device to: determine an extended discontinuous reception configuration of a second device in an inactive state, the second device being located in an area served by one or more devices including the first device; determine configuration information at least partially based on the extended discontinuous reception configuration; and send the configuration information to a third device in a core network to cause the third device to adjust a downlink transmission for the second device.

[0006] In a second aspect, a third device is provided. The third device includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, by using the at least one processor, cause the third device to: receive configuration information from a first device in an access network, the configuration information being determined based on an extended discontinuous reception configuration of a second device in an inactive state, and the second device being located in an area served by one or more devices including the first device; and adjust a downlink transmission for the second device based on the configuration information.

[0007] In a third aspect, a method is provided. The method includes: at a first device, determining an extended discontinuous reception configuration of a second device in an inactive state, the second device being located in an area served by one or more devices including the first device; determining configuration information at least partially based on the extended discontinuous reception configuration; and sending the configuration information to a third device in a core network to cause the third device to adjust a downlink transmission for the second device.

[0008] In a fourth aspect, a method is provided. The method includes: at a third device, receiving configuration information from a first device in an access network, the configuration information being determined based on an extended discontinuous reception configuration of a second device in an inactive state, and the second device being located in an area served by one or more devices including the first device; and adjusting a downlink transmission for the second device based on the configuration information.

[0009] In a fifth aspect, a first apparatus is provided. The first apparatus includes: means for determining, at the first apparatus, an extended discontinuous reception configuration of a second apparatus in an inactive state, the second apparatus being located in an area served by one or more devices including the first apparatus; means for determining configuration information at least partially based on the extended discontinuous reception configuration; and means for sending the configuration information to a third apparatus in a core network to cause the third apparatus to adjust a downlink transmission of the second apparatus.

[0010] In a sixth aspect, a second device is provided. The second device includes: means for receiving, at a third device, configuration information from a first device of an access network, the configuration information being determined based on an extended discontinuous reception configuration for the second device in an inactive state, and the second device being located in an area served by one or more devices including the first device; and means for adjusting a downlink transmission of the second device based on the configuration information.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, including program instructions for causing a device to perform at least the method according to the third aspect above.

[0012] In an eighth aspect, a non-transitory computer-readable medium is provided, including program instructions for causing a device to perform at least the method according to the fourth aspect above.

[0013] It should 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 limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 An example communication environment in which embodiments of the present disclosure can be implemented is shown;

[0016] Figure 2 A signaling flow for state transition reporting related to the RRC inactive state according to some example embodiments of the present disclosure is shown;

[0017] Figure 3 A flowchart of a method implemented at a first device according to some example embodiments of the present disclosure is shown;

[0018] Figure 4 A flowchart of a method implemented at a second device according to some example embodiments of the present disclosure is shown;

[0019] Figure 5 A simplified block diagram of a device suitable for implementing embodiments of the present disclosure is shown; and

[0020] Figure 6 A block diagram of an example computer-readable medium according to some embodiments of the present disclosure is shown.

[0021] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. DETAILED DESCRIPTION

[0022] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and help those skilled in the art to understand and implement the present disclosure, without implying any limitation to the scope of the present disclosure. The present disclosure described herein can be implemented in various ways other than those described below.

[0023] In the following specification and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0024] In the present disclosure, references to "an embodiment", "embodiments", "example embodiments", etc. indicate that the described embodiments may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes that particular feature, structure, or characteristic. Further, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0025] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish elements. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0026] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms "comprises", "has", and / or "includes" are used herein, these terms specify the presence of the 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.

[0027] As used in this application, the term "circuit" may refer to one or more or all of the following:

[0028] (a) Only hardware circuit implementations (such as implementations with only analog and / or digital circuits) and

[0029] (b) Combinations of hardware circuits and software, such as (where applicable):

[0030] (i) Combinations of (multiple) analog and / or digital hardware circuits and software / firmware and

[0031] (ii) any part of a (plural) hardware processor with software (including a (plural) digital signal processor, software, and a (plural) memory, which work together to enable a device such as a mobile phone or a server to perform various functions) and

[0032] (c) a (plural) hardware circuit and / or a (plural) processor that requires software (e.g., firmware) to operate, such as a (plural) microprocessor or a part of a (plural) microprocessor, but the software may not be present when it is not required to operate.

[0033] This definition of a circuit applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuit also encompasses an implementation of only a hardware circuit or a processor (or plural processors) or a part of a hardware circuit or a processor and its (or their) attendant software and / or firmware. The term circuit also encompasses, for example and if applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0034] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), NarrowBand Internet of Things (NB-IoT), and so on. In addition, the communication between a terminal device and a network device in a communication network can be performed according to any suitable generation of 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 future fifth generation (5G) communication protocol, and / or any other protocol known currently or to be developed in the future. Embodiments of the present disclosure can be applied to various communication systems, including but not limited to terrestrial communication systems, non-terrestrial communication systems, or a combination thereof. Considering the rapid development in the communication field, of course, there will also be future types of communication technologies and systems that can be used to implement the present disclosure. It should not be regarded as limiting the scope of the present disclosure to only the foregoing systems.

[0035] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. Depending on the applied terms and technologies, the network device can refer to a base station (BS) or an access point (AP), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), relay, low-power nodes such as femto, pico, and so on.

[0036] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, IP voice (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premise equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automation processing chain environment), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and so on. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0037] In the LTE system, the MME knows when the UE is operating in the eDRX mode of the RRC idle state. The eDRX cycle is up to 10.24 s, and in some cases, the eDRX cycle is even extended to 2621.44 s. The hyper system frame number (H-SFN) is broadcast by the RAN node in the cell and is incremented by 1 when the SFN wraps around. The PH refers to the H-SFN at which the UE starts monitoring paging messages during the PTW used in ECM-IDLE. The PH can be determined as a function of the eDRX cycle and the UE identity based on rules known to the MME / AMF, the UE, and the RAN node. The UE can monitor paging messages during the NAS-configured PTW or until the UE receives a paging message including the NAS identity of the UE. The possible start offsets of the PTW are uniformly distributed within the PH. By using this rule to determine the PH and the start of the PTW, the MME / AMF can send the S1 paging request exactly before or during the start of the PTW, so the eNB can prevent storing paging messages and excessive data transmission.

[0038] UE complexity reduction, as one of the key features of NB-IoT in 5G NR, may involve reducing the number of UE receive (RX) / transmit (TX) antennas, reducing the UE bandwidth, half-duplex frequency division duplexing (FDD), relaxing the UE processing time and capabilities, etc., which also poses requirements on the power consumption of the UE. To balance power consumption and service latency, the UE can enter the RRC inactive state, in which the UE uses the eDRX mode. For the RRC inactive state, the eDRX period is extended to 10485.76 s.

[0039] The RAN node can notify the AMF via the RRC inactive transition report procedure when the UE enters or leaves the RRC inactive state. The RAN node can initiate this procedure by sending, for example, an RRC INACTIVE TRANSITION REPORT message to the AMF. Upon receiving the RRC INACTIVE TRANSITION REPORT message, the AMF takes appropriate actions based on the information indicated by the RRC state IE. Since the RRC INACTIVE configuration is handled by the RAN and due to its capabilities, the AMF cannot infer the UE's eDRX configuration from the RRC inactive transition report.

[0040] This challenges data buffering at the RAN node (e.g., the anchor node). The AMF can send a paging request and DL packets to the RAN node without knowing the eDRX period applied by the UE. However, at this point in time, the RAN node cannot send these packets to the UE because the RAN node needs to first page the UE and then can forward the DL packets at the next active occasion of the eDRX period, which may occur a long time in the future. Additionally, the NAS retransmission timer is quite short, such as around 10 s, so the eDRX period cannot be longer than the NAS retransmission timer.

[0041] To address the above and other potential issues, embodiments of the present disclosure provide a flexible state transition report of information regarding the eDRX configuration. Generally, when determining that the UE undergoes a state transition, including a first transition from the RRC connected state to the RRC inactive state and a second transition from the RRC inactive state to the RRC connected state, the RAN node can provide sufficient information related to the state transition to the CN node via the state transition report procedure. In this way, the CN node can determine when the UE is reachable based on the information related to the state transition and accordingly adjust the transmission of the paging request and the DL transmission. In this way, the buffering burden on the RAN node can be alleviated, and a longer eDRX period can be used.

[0042] Exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0043] Figure 1 An exemplary communication environment 100 in which embodiments of the present disclosure may be implemented is shown. The communication environment 100 includes a first device 110, a second device 120, a third device 130, and a fourth device 140.

[0044] The first device 110 and the fourth device 140 may be network devices in the RAN, such as base stations, and provide cells 102 and 104, respectively. In some exemplary embodiments, the overall coverage of cells 102 and 104 may be referred to as an RNA or a paging area. In the context of the exemplary embodiments, the first device 110 may act as an anchor network device or an anchor node, and the fourth device 140 may act as the previous node serving the second device 120. As described above, the anchor node (i.e., the first device 110) may communicate with the access and mobility management function (AMF) at the CN and perform an RRC connection restoration procedure with the second device 120, while the previous node (i.e., the fourth device 140) may maintain the context data of the second device 120.

[0045] The first device 110 may configure an eDRX configuration for the second device 120. The eDRX configuration may include, but is not limited to, an eDRX cycle, an H-SFN including PTW and PH, an on-duration timer, an inactivity timer, a DRX start offset, a DRX retransmission timer, etc. With the eDRX configuration, the second device 120 may determine when to enter the RRC inactive state and when to monitor the paging channel, which will be described in detail below.

[0046] The second device 120 may be a terminal device located within the RNA. For example, the second device 120 may move within the coverage of the RAN. As Figure 1 shown, the second device 120 is initially served by the first device 110 and then by the fourth device 140. In the exemplary embodiments, the second device 120 may switch between different states and thus undergo state transitions, including a first transition from the RRC connected state to the RRC inactive state and a second transition from the RRC inactive state to the RRC connected state.

[0047] In the RRC inactive state, the second device 120 may monitor paging messages in the paging channel during PTW on the H-SFN configured by the first device 110. Specifically, the PTW may include a set of paging opportunities (POs), and the second device 120 monitors the paging channel on each PO. When a paging message including the NAS identity of the second device 120 is received, the second device 120 may then establish an RRC connection to receive DL data transmissions.

[0048] The third device 130 may be a CN node responsible for access and mobility management. The third device 130 may communicate with the anchor node of the RNA (i.e., the first device 110). For example, the third device 130 may send a paging request and possible DL data or transmission to the first device 110. When receiving the paging request and possible DL transmission, the first device 110 may then perform paging within the RNA and then forward the possible DL data or transmission to the corresponding second device 120. For ease of discussion only, the third device 130 is shown as Figure 1 the AMF in, and any other device or node for implementing similar functions is also applicable to the embodiments of the present disclosure.

[0049] In the case where the second device 120 is to perform a state transition related to the inactive state, the third device 130 may receive a state transition report from the first device 110, which indicates whether to perform the first transition or the second transition. In the above case and in the case where the second device 120 is in the extended discontinuous reception mode, the third device 130 may also receive configuration information from the first device 110. Using the configuration information, the third device 130 may determine the reachability of the second device 120 and accordingly adjust the transmission of the paging request and the DL transmission, which will be discussed below in conjunction with Figures 2 to 4 is discussed.

[0050] It should be understood that the number of network devices, terminal devices, and / or cells is given for illustrative purposes and does not imply any limitation to the present disclosure. The communication environment 100 may include any suitable number of network devices, terminal devices, and / or cells suitable for implementing the implementations of the present disclosure. Although not shown, it can be understood that one or more additional devices may be located in cells 102 and 104, and one or more additional cells may be deployed in the environment 100.

[0051] For ease of discussion only, the first device 110 and the fourth device 140 are shown as base stations, while the second device 120 is shown as a UE. It should be understood that the base station and the UE are only example implementations of the first device 110, the fourth device 140, and the second device 120 respectively, and do not imply any limitation to the scope of the present application. Any other suitable implementation is also possible.

[0052] Communications in the communication network 100 can be implemented according to any suitable communication protocol(s), including but not limited to, cellular communication protocols such as the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local area network communication protocols such as those of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol known currently or to be developed in the future. Additionally, the communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), and / or any other technology known currently or to be developed in the future.

[0053] To better understand the state transition reporting process proposed in this disclosure, reference is now made to Figure 2 . Figure 2 A signaling flow 200 for RRC inactive transition reporting according to some example embodiments of the present disclosure is shown. The signaling flow 200 can involve Figure 1 the first device 110, the second device 120, and the third device 130 shown. For the purpose of discussion, the signaling flow 200 will be described with reference to Figure 1 .

[0054] In the signaling flow 200, the first device 110 determines 205 that the second device 120 is in the eDRX mode or that a state transition related to the inactive state is to be performed at the second device 120. As used herein, a state transition related to the inactive state refers to either a first transition from the RRC connected state to the RRC inactive state or a second transition from the RRC inactive state to the RRC connected state.

[0055] By way of example, in the case of the second transition, the second device 120 can initiate an RRC connection restoration process by sending 210 an RRC connection restoration request to the anchor node (i.e., the first device 110). The RRC connection restoration request can include the I-RNTI allocated by the previous RAN node (i.e., the fourth device 140) serving the second device 120.

[0056] In the above case, the first device 110 can obtain the data context of the second device 120 from the fourth device 140. Then, the first device 110 can perform 215 the RRC connection restoration process, and the second transition is completed.

[0057] In the case where the first device 110 determines to perform a state transition, the first device 110 determines 220 the eDRX configuration for the second device 120 in an inactive state. For example, the eDRX configuration may include, but is not limited to, the duration of the eDRX cycle, PTW, paging superframe number, and H-SFN information configured for the second device 120.

[0058] The first device 110 determines 225 the configuration information at least in part based on the eDRX configuration. The configuration information may include, for example, one or more of the following: the duration of the eDRX cycle, PTW, the paging superframe number of the second device 120, H-SFN, the buffer state of the first device 110, the possible DL transmission timing and delay duration of the DL transmission of the third device 130, and the like.

[0059] In some example embodiments, the eDRX configuration may include the duration of the eDRX cycle of the second device 120. In this case, the first device 110 may determine whether the duration of the eDRX cycle exceeds a duration threshold, which is a configurable parameter or specified by a mobile network operator. If the duration of the eDRX cycle exceeds the duration threshold, it may indicate that the second device 120 may not receive DL transmissions frequently. Additionally or alternatively, the first device 110 may not want to buffer too many DL transmissions to be forwarded to the second device 120. In this case, the first device 110 may determine the configuration information based on the duration of the eDRX cycle, and the configuration information may be sent to the third device 130 to indicate this fact.

[0060] Otherwise, if the duration of the eDRX cycle does not exceed the duration threshold, it may indicate that there is no need to notify the third device 130 of the state transition related to the inactive state. In this case, the first device 110 may not determine the configuration information and send it to the third device 130.

[0061] In some example embodiments, the first device 110 may determine the configuration information based on the eDRX configuration and the duration of the retransmission timer of the third device 130. By way of example, if the next PO of the eDRX cycle arrives after the expiration of the retransmission timer of the third device 130, it may result in too much data transmission being buffered at the first device 110. In this case, the first device 110 may determine the configuration information to cause the third device to increase the duration of the retransmission timer. In some examples, the retransmission timer may be a NAS retransmission timer.

[0062] In some example embodiments, the first device 110 may determine configuration information based on the eDRX configuration and buffer status of the first device 110. By way of example, if the first device 110 determines, based on the duration of the eDRX cycle and the buffer status of the first device 110, that the buffer of the first device 110 will be filled by DL transmissions from the third device 110, the first device 110 may determine configuration information indicating the maximum buffer size of the first device 110, or alternatively, determine a size threshold for the DL transmissions. Using such configuration information, the third device 130 may determine the size of the allowed DL transmissions.

[0063] When determining the configuration information, the first device 110 sends 230 the configuration information to the third device 130 so that the third device 130 adjusts the DL transmissions for the second device 120. The configuration information may be sent via an RRC inactivity transition report message. It should be understood that any other message or signal may also be used for the transmission of the configuration information, and thus the scope of the present disclosure is not limited thereto.

[0064] In the above case where the duration of the eDRX cycle exceeds a duration threshold, it may be indicated that the third device 130 needs to adjust the DL transmissions to be forwarded to the second device 120, for example, by increasing the duration of the retransmission timer of the third device 130. The first device 110 may cause the third device 130 to increase the duration of the retransmission timer in an implicit manner or an explicit manner.

[0065] As an example of the implicit manner, when receiving configuration information indicating, for example, the duration of the eDRX cycle, the third device 130 may determine a new duration of the retransmission timer based on the duration of the eDRX cycle. As a result, the retransmission of DL data may be reduced or avoided until the next PO arrives.

[0066] The first device 110 may also provide additional information or an indication to the third device 130 in a dynamic and flexible manner. As an example of the explicit manner, the first device 110 may send 230 an indication of the possible delay of the retransmission timer to the third device 130. Alternatively, the first device 110 may send 230 an indication of the proposed new duration of the retransmission timer.

[0067] In some example embodiments, the first device 130 may determine whether DL transmissions from the third device 130 are allowed based on the eDRX cycle of the second device 120. If the DL transmissions are allowed, the first device 110 may send 235 a first indication that the DL transmissions are allowed to the third device 130. Otherwise, if the DL transmissions are not allowed, the first device 110 may send 240 a second indication that the DL transmissions are not allowed to the third device 130.

[0068] In some example embodiments, the second device 120 may send a UL transmission to the first device 110, which may implicitly indicate that the second device 120 is also capable of receiving DL transmissions. In this case, the first device 110 may determine that DL transmissions are also allowed and send a first indication to the third device 130.

[0069] Additionally or alternatively, upon receiving a UL transmission, a user plane function (UPF) in the core network may determine that DL transmissions are also allowed. In this case, the UPF may send a first indication to the third device 130. In some examples, in this case, the first device 110 may not send a first indication to the third device 130.

[0070] When receiving configuration information and selectively receiving additional information and indications, the third device 130 adjusts 245 the DL transmissions for the second device 120 accordingly.

[0071] For example, in response to receiving a first indication from the first device 110, the third device 130 may then send 250 a DL transmission to the first device 110. The DL transmission may include at least one of a paging request, data transmission, or data retransmission. In some example embodiments, the third device 130 may determine the reachability of the second device 120 based on an eDRX configuration, and subsequent DL transmissions may be sent based on the reachability of the second device 120.

[0072] In some example embodiments, the configuration information may include a DL transmission timing for the third device 130. In this case, the third device 130 may send a DL transmission at the DL transmission timing.

[0073] In some example embodiments, the configuration information may include the buffer state of the first device 110. In this case, the third device 130 may determine the buffer size of the first device 110 based on the buffer state and send a DL transmission of a first size that is lower than the buffer size.

[0074] In some example embodiments, the third device 130 may receive 255 an indication to discard a DL transmission from the first device 110. In this case, the third device 130 may determine that the DL transmission is not allowed and stop further data transmission to the second device 120.

[0075] It should be understood that the example implementation manners are provided for illustrative purposes without any limitation. For example, the configuration information and the additional information and indications as described above can be sent via a single signal or message (e.g., the RRC Inactive Transition Report message). Such information and indications can also be sent separately, or part of them can be sent via the RRC Inactive Transition Report message while the remaining part can be sent via another message or signal. The scope of the present disclosure is not limited thereto.

[0076] The example embodiments of the present disclosure provide a flexible state transition reporting process. Once it is determined to perform a state transition related to the RRC Inactive state, the RAN node (e.g., the anchor gNB of the RNA) can notify the AMF of the CN of this fact in a dynamic and flexible manner by using the configuration information and additional indications. In this way, a longer eDRX cycle can be achieved, thereby meeting the power saving requirements of the UE. In addition, such a dynamic and flexible reporting process can eliminate the data buffering problem at the RAN.

[0077] Figure 3 A flowchart of an example method 300 according to some example embodiments of the present disclosure is shown. The method 300 can be implemented at a device such as the first device 110 as shown. For the purpose of discussion, the method 300 will be described with reference to Figure 1 shown. Figure 1 to describe the method 300.

[0078] At 310, the first device 110 determines an eDRX configuration for a second device 120 in an inactive state. The second device 120 can be located within the RNA served by the first device 110 and the fourth device 140, that is, within the coverage areas of cells 102 and 104. The first device 110 can act as an anchor node of the RAN, and the fourth device 140 can act as a node that currently serves the second device 120 and maintains the context data of the second device 120.

[0079] In some example embodiments, the first device 110 can determine whether to perform a state transition related to the inactive state (e.g., the RRC Inactive state) at the second device 120. The state transition related to the inactive state can include a first transition from the connected state to the inactive state or a second transition from the inactive state to the connected state. If a state transition related to the inactive state is to be performed at the second device 120, or alternatively, the second device 120 is in the eDRX mode, it may be necessary to adjust the DL transmission to be forwarded to the second device 120 by the first device 110.

[0080] At 320, the first device 110 determines configuration information at least partially based on the eDRX configuration. In some example embodiments, the configuration information may include at least one of the following: the duration of the eDRX cycle of the second device 120, the PTW of the second device 120, the PH number of the second device 120, the SFN associated with the first device 110, the buffer status of the first device 110, the DL transmission opportunity of the third device 130, the delay duration of the DL transmission, etc.

[0081] In some example embodiments, the eDRX configuration determined in 310 may include the duration of the eDRX cycle of the second device 120. In these embodiments, the first device 110 may determine whether the duration of the eDRX cycle exceeds a duration threshold, e.g., a pre-configured duration threshold or a configurable parameter configured by a mobile network operator. If the first device 110 determines that the duration of the eDRX cycle exceeds the duration threshold, it may indicate that the second device 120 may not receive DL transmissions frequently. Additionally or alternatively, the first device 110 may not want to buffer too many DL transmissions to be forwarded to the second device 120. In this case, at 320, the first device 110 may determine the configuration information based on the duration of the eDRX cycle.

[0082] Otherwise, if the duration of the eDRX cycle does not exceed the duration threshold, it may indicate that there is no need to notify the third device 130 of the state transition related to the inactive state. In this case, the first device 110 may not determine the configuration information and send it to the third device 130.

[0083] In some example embodiments, at 320, the first device 110 may determine the configuration information based on the eDRX configuration and the duration of the retransmission timer of the third device 130. For example, the eDRX configuration determined in 310 may include the duration of the eDRX cycle of the second device 120. In these embodiments, the first device may determine whether the next paging opportunity of the eDRX cycle arrives after the expiration of the retransmission timer of the third device 130. If the first device 110 determines that the next paging opportunity of the eDRX cycle arrives after the expiration of the retransmission timer, then at 320, the first device 110 may determine the configuration information.

[0084] In some example embodiments, at 320, the first device 110 may determine configuration information based on the eDRX configuration and the buffer status of the first device 110. For example, the eDRX configuration determined at 310 may include the duration of the eDRX cycle of the second device 120. In these embodiments, the first device may determine whether the buffer of the first device 110 will be filled by DL transmissions from the third device 130. If the first device 110 determines that the buffer of the first device 110 will be filled by DL transmissions from the third device 130, then at 320, the first device 110 may determine the configuration information.

[0085] At 330, the first device 110 sends the configuration information to the third device 130 so that the third device 130 adjusts the DL transmission of the second device 120. In some example embodiments, the configuration information may be sent to the third device 130 via an RRC inactivity transition report message.

[0086] The first device 110 may provide additional information or an indication to the third device 130 for notifying the third device 130 when data transmissions of the second device 120 can be sent to the first device 110. In some example embodiments, the first device 110 may determine whether the duration of the eDRX cycle exceeds a duration threshold. If the duration of the eDRX cycle exceeds the duration threshold, then the first device 110 may cause the third device 130 to increase the duration of the retransmission timer of the third device 130. For example, the first device 110 may send an indication of a possible retransmission delay or an increase in the duration of the retransmission timer, and thus the third device 130 may increase the duration of the retransmission timer based on such an indication.

[0087] In some example embodiments, the first device 110 may determine whether DL transmissions from the third device 130 are allowed based on the eDRX cycle of the second device 120. If the DL transmission is allowed, then the first device 110 may send a first indication that the DL transmission is allowed to the third device 130. If the DL transmission is not allowed, then the first device 110 may send a second indication that the DL transmission is not allowed to the third device 130.

[0088] In some example embodiments, a UPF (not shown) may receive an uplink transmission from the second device 120, which implicitly indicates that the DL transmission is allowed. In this case, the first device 110, or alternatively, the UPF may send a first indication that the DL transmission is allowed to the third device 130.

[0089] In some example embodiments, when a DL transmission from a third device 130 arrives at a first device 110, the first device 110 may reject data forwarding or further data forwarding. For example, the first device 110 may discard the DL transmission based on the buffer state of the first device 110. Additionally, the first device 110 may send an indication to a fourth device to discard the DL transmission.

[0090] In some example embodiments, the first device 110 may receive a DL transmission from the third device 130, including at least one of a paging request, a data transmission, or a data retransmission. In these embodiments, the third device 130 may send the DL transmission to the second device 120 based on a state transition.

[0091] In some example embodiments, the first device 110 may be an anchor node of a region (e.g., RNA), the second device 120 may be a terminal device, e.g., a low-complexity UE moving within the RNA, and the third device 130 may be a CN node configured with an AMF.

[0092] In some example embodiments, the first device 110 may determine that the next PO of the second device 120 is very close such that the retransmission timer does not expire before the next PO arrives. Alternatively, the first device 110 may determine that its buffer has sufficient free capacity. In the above cases, the first device 110 may determine not to send configuration information or additional information and an indication to the third device 130. In embodiments where any of the above cases change, e.g., the first device 110 may not receive any paging response from the second device 120, or the buffer state changes, the first device 110 may determine whether to send the configuration information or additional information and an indication to the third device 130 again.

[0093] It should be understood that the configuration information and the additional information and indication as described above may be sent via a single signal or message (such as an RRC inactive transition report message). Such information and indication may also be sent separately, or a part thereof may be sent via an RRC inactive transition report message while the remaining part may be sent via another message or signal. The scope of the present disclosure is not limited thereto.

[0094] Figure 4 A flowchart of an example method 400 according to some example embodiments of the present disclosure is shown. The method 400 may be implemented at a device of the third device 130 as shown, for example. For purposes of discussion, the method 400 will be described with reference to Figure 1 shown. Figure 1 to describe the method 400.

[0095] At block 410, a third device 130 receives configuration information from a first device 110 of the RAN. In some example embodiments, the configuration information may be determined based on an eDRX configuration for a second device 120 in an inactive state. In these embodiments, the second device 120 is located within an area served by one or more devices including the first device 110. For example, the area may be an RNA corresponding to the coverage of cells 102 and 104.

[0096] In some example embodiments, the configuration information may be received from the first device 110 in an RRC inactive transition report message for indicating a state transition related to the inactive state performed at the second device 120. The state transition related to the inactive state may include one of a first transition from a connected state to an inactive state or a second transition from an inactive state to a connected state. It should be understood that the RRC inactive transition report message is given only as one of various implementations for transmitting the configuration information. The configuration information may also be transmitted via any other suitable message or signal.

[0097] In some example embodiments, the configuration information may include at least one of the following: the duration of the eDRX cycle of the second device 120, the PTW of the second device 120, the PH number of the second device 120, the SFN associated with the first device 110, the buffer status of the first device 110, the DL transmission opportunity of the third device 130, the delay duration of the DL transmission, etc.

[0098] At 420, the third device 130 adjusts the DL transmission of the second device 120 based on the configuration information. In some example embodiments, the configuration information received at 410 may include the eDRX configuration of the second device. In these embodiments, at 420, the third device 130 may determine the reachability of the second device 120 based on the eDRX configuration. Then, the third device 130 may send a DL transmission based on the reachability of the second device 120.

[0099] In some example embodiments, the configuration information received at 410 may include the DL transmission opportunity of the third device 130. In these embodiments, as a result of the adjustment at 420, the third device 130 may send a DL transmission at the DL transmission opportunity.

[0100] In some example embodiments, the configuration information received at 410 may include the buffer status of the first device 110. In these embodiments, at 420, the third device 130 may determine the buffer size of the first device 110 based on the buffer status. Further, as a result of the adjustment at 420, the third device 130 may send a DL transmission of a first size that is less than the buffer size.

[0101] The third device 130 may receive additional information or an indication from the first device 110 for notifying the third device 130 when it may transmit the data transmission of the second device 120 to the first device 110. In some example embodiments, the third device 130 may receive an indication from the first device 110, and the indication may indicate to increase the duration of the retransmission timer of the third device 130.

[0102] In some example embodiments, the third device 130 may receive either a first indication that DL transmission is allowed or a second indication that downlink transmission is not allowed from the first device 110.

[0103] In a case where the third device 130 receives the second indication, or alternatively, when the third device 130 determines that DL transmission is not allowed based on the configuration information and the additional information or indication received from the first device 110, the third device 130 may reject all paging requests that occur during a period when the second device 120 does not accept paging requests and data transmissions.

[0104] In some example embodiments, the third device 130 may send a DL transmission to be forwarded to the second device 120 to the first device 110. If the first device 110 discards the DL transmission, the third device 130 may then receive an indication of discarding the DL transmission from the first device 110.

[0105] In some example embodiments, the first device 100 may be an anchor node of a region (e.g., RNA), the second device 120 may be a terminal device, e.g., a low-complexity UE moving within the RNA, and the third device 130 may be a CN node configured with an AMF.

[0106] It should be understood that the above-described configuration information and additional information and indications may be received via a single signal or message (such as an RRC invalid transition report message). Such information and indications may also be received in separate messages or signals, or alternatively, a part of such information and indications may be received via an RRC inactive transition report message, while the remaining part may be received via one or more other messages or signals. The scope of the present disclosure is not limited thereto.

[0107] Example embodiments of the present disclosure provide a flexible state transition reporting process. Once it is determined that a state transition related to the RRC inactive state is to be performed, a RAN node (e.g., an anchor gNB of an RNA) may notify the AMF of the CN of this fact in a dynamic and flexible manner. In this way, the AMF may adjust the paging process and data transmission to be forwarded to the UE by considering the eDRX configuration and the buffer state of the RAN node.

[0108] In some example embodiments, a first apparatus capable of performing method 300 may include components for performing the respective steps of method 300. These components may be implemented in any suitable form. For example, these components may be implemented in circuitry or software modules.

[0109] In some example embodiments, the first apparatus includes: components for determining, at the first apparatus, an extended discontinuous reception configuration of a second apparatus in an inactive state, the second apparatus being located within an area served by one or more devices including the first apparatus; components for determining configuration information based at least in part on the extended discontinuous reception configuration; and components for sending the configuration information to a third apparatus in a core network to cause the third apparatus to adjust a downlink transmission of the second apparatus.

[0110] In some example embodiments, the components for determining configuration information include: components for determining the configuration information if it is determined that the second apparatus is in an extended discontinuous reception mode or is to perform a state transition related to the inactive state, the state transition related to the inactive state including one of: a first transition from a connected state to an inactive state, or a second transition from an inactive state to a connected state.

[0111] In some example embodiments, the configuration information is sent to the third apparatus via a radio resource control inactive transition report message.

[0112] In some example embodiments, the configuration information includes at least one of: a duration of an extended discontinuous reception period of the second apparatus, a paging transmission window of the second apparatus, a paging superframe number of the second apparatus, a system frame number associated with the first apparatus, a buffer state of the first apparatus, a downlink transmission timing of the third apparatus, or a delay duration of the downlink transmission.

[0113] In some example embodiments, the extended discontinuous reception configuration includes a duration of an extended discontinuous reception period of the second apparatus, and the components for determining configuration information include: components for determining the configuration information based on the duration of the extended discontinuous reception period if it is determined that the duration of the extended discontinuous reception period exceeds a duration threshold.

[0114] In some example embodiments, the apparatus for determining configuration information includes: components for determining the configuration information based on the extended discontinuous reception configuration and a duration of a retransmission timer of the third apparatus.

[0115] In some example embodiments, the extended discontinuous reception configuration includes a duration of an extended discontinuous reception period of the second apparatus, and the components for determining configuration information include: components for determining the configuration information if it is determined that a buffer of the first apparatus will be filled by a downlink transmission from the third apparatus.

[0116] In some example embodiments, the first device further includes: a component for causing a third device to increase the duration of a retransmission timer of the third device if it is determined that the duration of an extended discontinuous reception period exceeds a duration threshold.

[0117] In some example embodiments, the first device further includes: a component for determining whether a downlink transmission is allowed based on an extended discontinuous reception period of a second device; a component for sending a first indication that the downlink transmission is allowed to a third device if it is determined that the downlink transmission is allowed; and a component for sending a second indication that the downlink transmission is not allowed to the third device if it is determined that the downlink transmission is not allowed.

[0118] In some example embodiments, the first device further includes: a component for determining that a downlink transmission is allowed in response to receiving an uplink transmission from a second device; and a component for sending a first indication that the downlink transmission is allowed to a third device.

[0119] In some example embodiments, the first device further includes: a component for discarding a downlink transmission from a third device based on a buffer state of the first device; and a component for sending an indication of discarding the downlink transmission to the third device.

[0120] In some example embodiments, the first device further includes: a component for receiving a downlink transmission from a third device, the downlink transmission including at least one of a paging request, a data transmission, or a data retransmission; and a component for sending the downlink transmission to a second device.

[0121] In some example embodiments, the first device includes an anchor node for a region, the second device includes a terminal device, and the third device includes a network device configured with an access and mobility management function.

[0122] In some example embodiments, the second device capable of performing method 400 may include components for performing the respective steps of method 400. These components may be implemented in any suitable form. For example, these components may be implemented in a circuit or a software module.

[0123] In some example embodiments, the second device includes: a component for receiving, at a third device, configuration information from a first device of an access network, the configuration information being determined based on an extended discontinuous reception configuration for the second device in an inactive state, and the second device being located in a region served by one or more devices including the first device; and a component for adjusting a downlink transmission of the second device based on the configuration information.

[0124] In some example embodiments, the configuration information is received from a first device in a radio resource control inactivity transition report message, which is used to indicate a state transition related to the inactivity state performed at a second device, and the state transition related to the inactivity state includes one of the following: a first transition from a connected state to an inactivity state, or a second transition from an inactivity state to a connected state.

[0125] In some example embodiments, the configuration information includes at least one of the following: the duration of the extended discontinuous reception period of the second device, the paging transmission window of the second device, the paging superframe number of the second device, the system frame number associated with the first device, the buffer status of the first device, the downlink transmission timing of a third device, or the delay duration of the downlink transmission.

[0126] In some example embodiments, the configuration information includes the extended discontinuous reception configuration of the second device, and the components for adjusting the downlink transmission include: a component for determining the reachability of the second device based on the extended discontinuous reception configuration; and a component for sending a downlink transmission based on the reachability of the second device.

[0127] In some example embodiments, the configuration information includes the downlink transmission timing of a third device, and the components for adjusting the downlink transmission include: a component for sending a downlink transmission at the downlink transmission timing.

[0128] In some example embodiments, the configuration information includes the buffer status of the first device, and the components for adjusting the downlink transmission include: a component for determining the buffer size of the first device based on the buffer status; and a component for sending a downlink transmission of a first size that is less than the buffer size.

[0129] In some example embodiments, the second device further includes: a component for receiving an indication from the first device to increase the duration of the retransmission timer of a third device.

[0130] In some example embodiments, the second device further includes: a component for receiving a first indication from the first device that downlink transmission is allowed; or a component for receiving a second indication from the first device that downlink transmission is not allowed.

[0131] In some example embodiments, the second device further includes: a component for sending a downlink transmission to the first device; and a component for receiving an indication from the first device to discard the downlink transmission.

[0132] In some example embodiments, the first device includes an anchor node of a region, the second device includes a terminal device, and the third device includes a network device configured with an access and mobility management function.

[0133] Figure 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. The device 500 can be provided to implement a communication device, such as Figure 1 the first device 110, the second device 120, the third device 130, and the fourth device 140 shown. As shown, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processors 510, and one or more communication modules 540 coupled to the processors 510.

[0134] The communication module 540 is used for two-way communication. The communication module 540 has at least one antenna to facilitate communication. The communication interface can represent any interface required to communicate with other network elements.

[0135] The processor 510 can be of any type suitable for the local technical network and can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. The device 500 can have multiple processors, such as an application-specific integrated circuit chip that is subordinate to a clock synchronized with the main processor in time.

[0136] The memory 520 can include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that will not persist during a power outage.

[0137] The computer program 530 includes computer-executable instructions executed by the associated processor 510. The program 530 can be stored in the ROM 524. The processor 510 can perform any suitable actions and processes by loading the program 530 into the RAM 522.

[0138] Embodiments of the present disclosure can be implemented by means of the program 530, such that the device 500 can execute any process of the present disclosure discussed with reference to Figure 3 and 4 Embodiments of the present disclosure can also be implemented by hardware or by a combination of software and hardware.

[0139] In some embodiments, program 530 may be tangibly embodied in a computer-readable medium, which may be included in device 500 (such as in memory 520) or other storage devices accessible to device 500. Device 500 may load program 530 from the computer-readable medium into RAM 522 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, and so on. Figure 6 An example of a computer-readable medium 600 in the form of a CD or DVD is shown. Program 530 is stored on the computer-readable medium.

[0140] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although the various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it is understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0141] 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 to be executed in a device on a target real or virtual processor, such as those included in program modules, to perform the methods 300 or 400 described above with reference to Figures 3 - 4 Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, and so on that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of program modules may be combined or split as needed among program modules. The machine-executable instructions for program modules may be executed locally or within a distributed device. In a distributed device, program modules may be located both locally and in remote storage media.

[0142] The program code for performing the 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, a special-purpose computer, or other programmable data processing device, such that when the program codes are executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0143] In the context of the present disclosure, computer program code or related data can be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and the like.

[0144] A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium will include an electrical connection having one or more wires, a portable computer disk, 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.

[0145] Furthermore, although the operations have been described in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the operations shown be performed, to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, 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 described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

[0146] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the 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 first device for communication, comprising: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, using the at least one processor, cause the first device to at least: determine an extended discontinuous reception configuration for a second device in an inactive state, the second device being located in an area served by one or more devices including the first device, wherein the extended discontinuous reception configuration includes a duration of an extended discontinuous reception period of the second device; based on determining that the second device is to perform a state transition from a connected state to the inactive state and based on determining that the duration of the extended discontinuous reception period exceeds a duration threshold, determine configuration information based on the duration of the extended discontinuous reception period; and send the configuration information to a third device in a core network to cause the third device to adjust downlink transmissions for the second device.

2. The first device according to claim 1, wherein the configuration information is sent to the third device via a radio resource control inactive transition report message.

3. The first device according to claim 1, wherein the configuration information includes at least one of the following: the duration of the extended discontinuous reception period of the second device, a paging transmission window of the second device, a paging superframe number of the second device, a system frame number associated with the first device, a buffer status of the first device, a downlink transmission timing of the third device, or a delay duration of the downlink transmission.

4. The first device according to claim 1, wherein the first device determines the configuration information by: determining the configuration information based on the extended discontinuous reception configuration and a duration of a retransmission timer of the third device.

5. The first device according to claim 4, wherein the first device determines the configuration information by: if it is determined that the next paging occasion of the extended discontinuous reception period arrives after the retransmission timer of the third device expires, determining the configuration information.

6. The first device according to claim 1, wherein the first device determines the configuration information by: determining the configuration information based on the extended discontinuous reception configuration and a buffer status of the first device.

7. The first device according to claim 6, wherein the first device determines the configuration information by: if it is determined that the buffer of the first device will be filled by a downlink transmission from the third device, determining the configuration information.

8. The first device according to any one of claims 1 to 7, wherein the first device is further caused to: if it is determined that the duration of the extended discontinuous reception period exceeds the duration threshold, cause the third device to increase the duration of the third device's retransmission timer.

9. The first device according to any one of claims 1 to 7, wherein the first device is further caused to: Determine whether the downlink transmission is allowed based on the extended discontinuous reception period of the second device; If it is determined that the downlink transmission is allowed, send a first indication that the downlink transmission is allowed to the third device; And If it is determined that the downlink transmission is not allowed, send a second indication that the downlink transmission is not allowed to the third device.

10. The first device according to any one of claims 1 to 9, wherein the first device is further caused to: Determine that the downlink transmission is allowed in response to receiving an uplink transmission from the second device; and Send a first indication that the downlink transmission is allowed to the third device.

11. The first device according to any one of claims 1 to 7, wherein the first device is further caused to: Discard a downlink transmission from the third device based on the buffer state of the first device; and Send an indication to the third device to discard the downlink transmission.

12. The first device according to any one of claims 1 to 7, wherein the first device is further caused to: Receive the downlink transmission from the third device, the downlink transmission including at least one of a paging request, a data transmission, or a data retransmission; and Send the downlink transmission to the second device.

13. The first device according to any one of claims 1 to 7, wherein the first device includes an anchor node for the area, the second device includes a terminal device, and the third device includes a network device configured with an access and mobility management function.

14. A method for communication, Comprising: At a first device, determine an extended discontinuous reception configuration for a second device in an inactive state, the second device being located in an area served by one or more devices including the first device, wherein the extended discontinuous reception configuration includes a duration of an extended discontinuous reception period of the second device; Based on the duration of the extended discontinuous reception period, determine configuration information according to determining that the second device is to perform a state transition from a connected state to the inactive state and according to determining that the duration of the extended discontinuous reception period exceeds a duration threshold; And Send the configuration information to a third device of a core network to cause the third device to adjust a downlink transmission for the second device.

15. The method according to claim 14, wherein the configuration information is sent to the third device via a radio resource control inactive transition report message.

16. The method according to claim 14, wherein the configuration information includes at least one of the following: The duration of the extended discontinuous reception period of the second device, The paging transmission window of the second device, The paging superframe number of the second device, The system frame number associated with the first device, The buffer state of the first device, The downlink transmission timing of the third device, or The delay duration of the downlink transmission.

17. The method according to claim 14, wherein determining the configuration information comprises: determining the configuration information based on the extended discontinuous reception configuration and the duration of the retransmission timer of the third device.

18. The method according to claim 17, wherein determining the configuration information comprises: determining the configuration information if it is determined that the next paging occasion of the extended discontinuous reception period arrives after the retransmission timer of the third device expires.

19. The method according to claim 14, wherein, determining the configuration information comprises: determining the configuration information based on the extended discontinuous reception configuration and the buffer state of the first device.

20. The method according to claim 19, wherein determining the configuration information comprises: determining the configuration information if it is determined that the buffer of the first device will be filled by the downlink transmission from the third device.

21. The method according to any one of claims 14 to 20, further comprises: if it is determined that the duration of the extended discontinuous reception period exceeds the duration threshold, causing the third device to increase the duration of the retransmission timer of the third device.

22. The method according to any one of claims 14 to 20, further comprises: determining whether the downlink transmission is allowed based on the extended discontinuous reception period of the second device; if it is determined that the downlink transmission is allowed, sending a first indication that the downlink transmission is allowed to the third device; and if it is determined that the downlink transmission is not allowed, the third device sending a second indication that the downlink transmission is not allowed.

23. The method according to any one of claims 14 to 20, further comprises: determining that the downlink transmission is allowed in response to receiving an uplink transmission from the second device; and sending a first indication that the downlink transmission is allowed to the third device.

24. The method according to any one of claims 14 to 20, further comprises: discarding the downlink transmission from the third device based on the buffer state of the first device; and sending an indication to the third device to discard the downlink transmission.

25. The method according to any one of claims 14 to 20, further comprises: receiving the downlink transmission from the third device, the downlink transmission including at least one of a paging request, a data transmission, or a data retransmission; and sending the downlink transmission to the second device.

26. The method according to any one of claims 14 to 20, wherein the first device includes an anchor node for the area, the second device includes a terminal device, and the third device includes a network device configured with an access and mobility management function.

27. A non-transitory computer-readable medium, comprising program instructions for causing a device to at least execute the method according to any one of claims 14 - 26.

Images