CN116508361A

CN116508361A - Transmission of periodic data in inactive state

Info

Publication number: CN116508361A
Application number: CN202080107435.XA
Authority: CN
Inventors: 刘建国; 陶涛; 孟艳; 刘勇
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2020-11-25
Filing date: 2020-11-25
Publication date: 2023-07-28
Also published as: WO2022109864A1

Abstract

Embodiments of the present disclosure relate to transmission of periodic data in an inactive state. The first device receives control information for transmission of periodic data from at least one of the second device, the third device or the core network element, and based on the control information, obtains periodic data from the third device in an inactive state. In this way, paging overhead may be reduced and power savings at the first device may be achieved.

Description

Transmission of periodic data in inactive state

Technical Field

Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to the transmission of periodic data in an inactive state.

Background

For positioning operations in a New Radio (NR), sometimes a location server such as a Location Management Function (LMF) or the last serving cell needs to send periodic positioning assistance data to the positioning device. Typically, if the positioning device is in an inactive state, the positioning device must move to a connected state for receiving periodic positioning assistance data. This may result in increased power consumption, additional signaling overhead, and positioning delay.

Currently, NR version 17 grants small data transmissions in the inactive state. In this case, it is important to keep the positioning device in an inactive state to receive periodic positioning assistance data from the network side.

Disclosure of Invention

In general, example embodiments of the present disclosure provide a scheme for transmission of periodic data in an inactive state.

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, with the at least one processor, cause the first device to: receiving control information for transmission of periodic data from at least one of the second device, the third device or the core network element; and based on the control information, acquiring the periodic data from the third device in an inactive state.

In a second aspect, a second device is provided. The second 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, with the at least one processor, cause the second device to: determining control information for transmission of periodic data; and transmitting the control information to the first device for acquiring the periodic data from the third device in the inactive state.

In a third 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, with the at least one processor, cause the third device to: receiving a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and transmitting the periodic data to the first device in a response to the random access request.

In a fourth aspect, a core network element is provided. The core network element comprises: 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, with the at least one processor, cause the core network element to: generating control information for transmission of the periodic data; and transmitting the control information to a first device, the control information being used by the first device to acquire the periodic data from a third device in an inactive state.

In a fifth aspect, a method for communication is provided. The method comprises the following steps: at the first device, receiving control information for transmission of periodic data from at least one of the second device, the third device, or the core network element; and based on the control information, acquiring the periodic data from the third device in an inactive state.

In a sixth aspect, a method for communication is provided. The method comprises the following steps: determining, at the second device, control information for transmission of periodic data; and transmitting the control information to the first device for acquiring the periodic data from the third device in the inactive state.

In a seventh aspect, a method for communication is provided. The method comprises the following steps: at a third device, receiving a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and transmitting the periodic data to the first device in a response to the random access request.

In an eighth aspect, a method for communication is provided. The method comprises the following steps: generating, at a core network element, control information for transmission of periodic data; and transmitting the control information to a first device, the control information being used by the first device to acquire the periodic data from a third device in an inactive state.

In a ninth aspect, an apparatus for communication is provided. The device comprises: means for receiving, at the first device, control information for transmission of periodic data from at least one of the second device, the third device, or the core network element; and means for acquiring the periodic data from the third device in an inactive state based on the control information.

In a tenth aspect, an apparatus for communication is provided. The device comprises: means for determining, at the second device, control information for transmission of periodic data; and means for transmitting the control information to the first device for obtaining the periodic data from the third device in an inactive state.

In an eleventh aspect, an apparatus for communication is provided. The device comprises: means for receiving, at a third device, a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and means for transmitting the periodic data to the first device in a response to the random access request.

In a twelfth aspect, an apparatus for communication is provided. The device comprises: means for generating control information for transmission of periodic data at a core network element; and means for transmitting the control information to a first device, the control information being used by the first device to obtain the periodic data from a third device in an inactive state.

In a thirteenth aspect, a non-transitory computer-readable medium is provided. The non-transitory computer readable medium comprises program instructions for causing an apparatus to perform the method according to the fifth aspect.

In a fourteenth aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable medium includes program instructions for causing an apparatus to perform the method according to the sixth aspect.

In a fifteenth aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable medium includes program instructions for causing an apparatus to perform the method according to the seventh aspect.

In a sixteenth aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable medium includes program instructions for causing an apparatus to perform the method according to the eighth aspect.

It should be understood that the summary is not intended to identify key or essential features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

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

FIG. 1 illustrates an example communication network in which example embodiments of the present disclosure may be implemented;

fig. 2 shows a flow chart illustrating a transmission process of periodic data in an inactive state according to some embodiments of the present disclosure;

fig. 3 shows a flow chart illustrating a configuration process of control information for transmission of periodic data according to some embodiments of the present disclosure;

fig. 4 shows a flow chart illustrating another configuration process of control information for transmission of periodic data in accordance with some embodiments of the present disclosure;

fig. 5 shows a flow chart illustrating yet another configuration process of control information for transmission of periodic data in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates a flowchart of an example communication method implemented at a first device, according to an example embodiment of the disclosure;

FIG. 7 illustrates a flowchart of an example communication method implemented at a second device, according to an example embodiment of the disclosure;

FIG. 8 illustrates a flowchart of an example communication method implemented at a third device, according to an example embodiment of the disclosure;

fig. 9 illustrates a flowchart of an example communication method implemented at a core network element according to an example embodiment of the present disclosure;

FIG. 10 illustrates a simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure; and

fig. 11 illustrates a block diagram of an example computer-readable medium, according to an example embodiment of the present disclosure.

The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements.

Detailed Description

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 to assist those skilled in the art in understanding and practicing the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein may be implemented in various ways other than those described below.

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

References in the specification to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It will be understood that, although the terms "first" and "second," etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, 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 items.

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," "including," and/or "containing" when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof.

As used in this application, the term "circuitry" may refer to one or more or all of the following:

(a) Hardware-only circuit implementations (e.g., implementations in analog and/or digital circuitry only) and

(b) A combination of hardware circuitry and software, for example (as applicable):

(i) Combination of analog and/or digital hardware circuitry and software/firmware

(ii) Any portion of a hardware processor having software (including a digital signal processor, software, and memory that work together to cause a device such as a mobile phone or server to perform various functions), and

(c) Hardware circuitry and/or a processor, such as a microprocessor or a portion of a microprocessor, that requires software for operation (e.g., firmware), but may not exist when software is not required for operation.

This definition of circuitry applies to all uses of this term in this application, including all uses in any claims. As another example, as used in this application, the term circuitry also encompasses implementations of only hardware circuitry or processor (or multiple processors) or a portion of hardware circuitry or processor and its (or their) accompanying software and/or firmware. For example, if applicable to particular claim elements, the term circuitry also encompasses baseband integrated circuits or processor integrated circuits for a server, a cellular network device, or a mobile device in another computing or network device, or similar integrated circuit.

As used herein, the term "communication network" refers to a network that conforms to 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 the like. Furthermore, the communication between the terminal device and the network device in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, a first generation (1G), a second generation (2G), 2.5G, 2.75G, a third generation (3G), a fourth generation (4G), 4.5G, a future fifth generation (5G) New Radio (NR) communication protocol, and/or any other protocol now known or later developed. The embodiment of the invention can be applied to various communication systems. In view of the rapid development of communications, there will of course be future types of communication technologies and systems in which the present invention may be implemented. The scope of the present disclosure should not be considered limited to only the systems described above.

As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services therefrom. Depending on the terminology and technology applied, a network device may refer to a Base Station (BS) or Access Point (AP) such as a node B (NodeB or NB), an evolved node B (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, a low power node such as a femto node, a pico node, etc.

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, voice over IP (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, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless terminals, mobile stations, notebook computer embedded devices (LEEs), notebook computer embedded devices (LMEs), USB dongles, smart devices, wireless customer premise devices (CPE), internet of things (loT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (such as tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronics devices, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

In NR version 16, local NR positioning support is standardized. Thus, NR version 16 specifies the following positioning scheme: downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), downlink angle of departure (DL-AoD), uplink angle of arrival (UL-AoA), and Multi-cell round trip time (Multi-RTT).

In NR release 16, radio Access Technology (RAT) -dependent positioning techniques are limited to terminal devices in Radio Resource Control (RRC) connected mode. In this case, the number of terminal devices that can be located simultaneously is limited. For example, in internet of things (IoT) scenarios and other use cases, a large number of terminal devices may need location services at the same time. Requiring all terminal devices to move to the connected state would result in a large signaling overhead. Furthermore, when requesting positioning, if the terminal device is not in a connected state, an additional time delay may occur before positioning the terminal device. Furthermore, power consumption is increased because the terminal device needs to be moved to a connected state before positioning. Thus, 3GPP release 17 approves the enhancement of the positioning of the terminal device in RRC idle state and RRC inactive state.

When the terminal device is in the RRC connected state, it can communicate with the network device using typical NR physical channels and procedures. When the terminal device is in RRC idle and RRC inactive states, power may be saved compared to in RRC connected states.

The RRC inactive state does not support data transmission until release 16. Therefore, the terminal device must resume the connection for any downlink and uplink data (i.e., move to RRC connected state). Connection establishment and subsequent release to the RRC inactive state occurs for each data transmission, however, data packets are small and infrequent. This means that, for example, when a packet arrives at the downlink of a terminal device in RRC inactive state, the network will initiate a paging procedure for the terminal device, and then the terminal device will start a 2-step or 4-step Random Access (RA) procedure to resume the connection before data transfer. This results in unnecessary power consumption and signaling overhead. In this case, in NR version 17, small Data Transmission (SDT) in the RRC inactive state is supported. This means that the NR supports an RRC inactive state and that terminal devices with infrequent (periodic and/or aperiodic) data transmissions are typically maintained by network devices in the RRC inactive state.

As described above, for positioning operations in NR, a location server such as an LMF sometimes needs to send periodic positioning assistance data to a positioning device. Typically, if the positioning device is in an inactive state, the positioning device must move to a connected state for receiving periodic positioning assistance data. This may result in increased power consumption, additional signaling overhead, and positioning delay. In case NR version 17 currently approves small data transmission in the inactive state, it is important to keep the positioning device in the inactive state to receive periodic positioning assistance data from the network side.

In one conventional approach, it is proposed to support location measurement reporting in RRC inactive state based on SDT. It would be beneficial for a positioning device to reduce power consumption and end-to-end latency for positioning operations. In another conventional approach, it is proposed to send positioning assistance data to the positioning device according to a RACH based procedure in RRC inactive state, e.g. using Msg4 for 4-step RA and MsgB for 2-step RA with flexible payload size to carry positioning assistance data in RRC inactive state. However, the corresponding mechanisms as to how the positioning assistance data transmission is implemented have not been discussed.

In the event that the positioning device in the RRC inactive state begins to initiate an RRC connection recovery procedure for UL SDT, the network device may send positioning assistance data with an RRC release message (i.e., a suspension indication) in the DL MAC PDU to the positioning device. However, the terminal device in NR typically initiates the RRC connection recovery procedure only when UL data needs to be transmitted. If the terminal device does not initiate the RRC connection recovery procedure for UL SDT, the network device should first page the terminal device. For periodic positioning assistance data transmissions, the network device should page the positioning device periodically in an RRC inactive state for positioning assistance data transmissions. In order to achieve fast assistance data updates, the network device needs to configure a small paging cycle for the positioning device. This operation will increase the power consumption of the positioning device due to paging monitoring, which is very sensitive for low power positioning devices.

To address the above and other potential problems, embodiments of the present disclosure provide an improved scheme for transmitting periodic data, such as periodic positioning assistance data, in an inactive state. In this scheme, the network device instructs a terminal device such as a positioning device to periodically initiate an RRC connection recovery procedure for transmission of periodic data in an RRC inactive state, even though it does not need to transmit uplink data. Upon receiving an RRC connection restoration request for periodic data transmission, an anchor cell of the terminal device requests periodic data from a last serving cell of the terminal device, and transmits the periodic data as downlink small data to the terminal device in an RRC inactive state. This will benefit the terminal device to save power and will also benefit the network device to reduce paging overhead for periodic data transmissions.

Some example embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the disclosure extends beyond these limited embodiments.

Fig. 1 illustrates an example communication network 100 in which embodiments of the present disclosure may be implemented. As shown in fig. 1, the network 100 includes a first device 110, a second device 120, and a third device 130. Each of the second device 120 and the third device 130 may serve the first device 110. The first device 110 may access the core network 140 via any one of the second device 120 and the third device 130 and receive services from the core network element 141 in the core network 140. In some embodiments, the core network element 141 may be a location server such as an LMF. Of course, the core network element 141 may have any other suitable functionality. For illustration, the first device 110 is shown as a terminal device, and the second device 120 and the third device 130 are shown as network devices.

For purposes of illustration only, and not to imply any limitation on the scope of the disclosure, some embodiments will be described in the context of the first device 110 being a terminal device and the second device 120 and the third device 130 each being a network device. It should be appreciated that in other embodiments, the first device 110 may be a network device and the second device 120 and/or the third device 130 may be terminal devices. In other words, the principles and spirit of the present disclosure may be applied to uplink and downlink transmissions.

It should also be understood that the number of first, second and third devices and the number of core network elements shown in fig. 1 are for illustration purposes only and are not meant to be limiting in any way. The network 100 may include any suitable number of first, second, and third devices and core network elements suitable for implementing embodiments of the present disclosure.

As shown in fig. 1, each of the first device 110 and the second and third devices 120 and 130 may communicate with each other via a channel, such as a wireless communication channel. The second device 120 and the third device 130 may communicate with each other via an air interface. Communications in network 100 may conform to any suitable standard including, but not limited to, LTE evolution, LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), code Division Multiple Access (CDMA), global system for mobile communications (GSM), and the like. Further, the communication may be performed according to any generation communication protocol currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.

In some scenarios, the core network element 141 or the second device 120 needs to send periodic data to the first device 110. For example, the core network element 141 or the second device 120 may send periodic positioning assistance data to the first device 110. It should be noted that embodiments of the present invention are also applicable to any other type of periodic data.

Assume that the first device 110 is in a connected state (e.g., RRC connected state) with the second device 120 and then the second device 120 instructs the first device 110 to enter an inactive state (e.g., RRC inactive state). In some embodiments, the first device 110 in the inactive state may perform cell reselection from the second device 120 to the third device 130 for paging reception. In this case, the third device 130 acts as an anchor cell for the first device 110, while the second device 120 acts as a last serving cell for the first device 110. In some alternative embodiments, the first device 110 in the inactive state may not perform cell reselection. In this case, the second device 120 acts as both an anchor cell and a last serving cell for the first device 110. In other words, the second device 120 and the third device 130 are the same device.

For convenience, the following description will be made in connection with the case where the third device 130 serves as an anchor cell for the first device 110 and the second device 120 serves as a last serving cell for the first device 110.

Fig. 2 illustrates a flow chart of a transmission process 200 of periodic data in an inactive state according to some embodiments of the present disclosure. For convenience, the following description will be made in connection with the context of fig. 1.

According to an embodiment of the present disclosure, the core network element 141 or the second device 120 generates control information for transmission of periodic data and configures the control information to the first device 110. Based on the control information, the first device 110 acquires periodic data in an inactive state.

In some embodiments, the control information may include an indication that the random access request needs to be periodically transmitted (also referred to herein as an RRC connection recovery request indication). This field may specify that the first device 110 should periodically initiate an RRC connection recovery procedure for periodic data transmissions.

In some embodiments, the control information may include a number of random access requests (also referred to herein as a request amount). This field may specify the number of periodic RRC connection recovery requests for periodic data transmission. For example, the field may be defined as an integer value N. The integer n=1 … 31 corresponds to an amount of 2N. The integer value n=32 represents an "unlimited/indefinite" amount, which means that the RRC connection resume request should continue until an LTE Positioning Protocol (LPP) suspension message is received. It should be understood that the above values of N are merely examples and are not limiting of the present disclosure. Any other suitable value is also possible.

In some embodiments, the control information may include a period of random access requests (also referred to herein as a request interval). This field may specify an interval between RRC connection resume requests.

In some embodiments, the control information may include resources configured to transmit the random access request. For example, the control information may include an identification of the resource. This field may specify the resources for the RRC connection resume request. In some embodiments, the resources may be resources configured for a 2-step RACH procedure. In some embodiments, the resources may be resources configured for a 4-step RACH procedure. In some embodiments, the resource may be a Configuration Grant (CG) resource for SDT.

Referring to fig. 2, in some embodiments, the core network element 141 may generate 211 control information in the user plane interface and send 212 the control information to the first device 110, e.g., based on the LET location protocol (LPP). For example, upon receiving a periodic data request from the first device 110, the core network element 141 may configure control information in an Information Element (IE). As an example, the LMF may configure control information for transmission of periodic positioning assistance data in positioning method specific assistance data (e.g., IEA-GNSS-provideasistancedata). In this way, the transmission of control information to the first device 110 is transparent to the second device 120 and the third device 130.

Control information about the RRC connection resume request indication (i.e., rrcrumerequest indication) may be indicated in the GNSS-periodic control param of IEA-GNSS-providesstastatadata. Other control information such as the amount of requests and the request interval may be implicitly configured by GNSS PeriodicControlParam. For example, the request amount may be implicitly determined by reliveryAmount, and the request interval may be implicitly determined by reliveryInterval. An example of a GNSS-Periodacontrol Param is as follows.

GNSS-PeriodicControlParam

The IE GNSS-PeriodicControlParam is used to specify control parameters for a periodic assistance data delivery.

--ASN1START

GNSS-PeriodicControlParam-r15::＝SEQUENCE{

RRCResumeRequestIndication INTERGER(0..1)

deliveryAmount-r15 INTEGER(1..32),

deliveryInterval-r15 INTEGER(1..64),

...

}

--ASN1STOP

In some alternative embodiments, the core network element 141 may send 213 at least a portion of the control information to the serving cell of the first device 110 (i.e., the second device 120), and the second device 120 may configure 215 the control information to the first device 110. In some alternative embodiments, the second device 120 may itself generate 214 the control information and configure 215 the control information to the first device 110. The configuration 215 of the control information from the second device 120 to the first device 110 will be described below with reference to fig. 3 to 5.

Fig. 3 illustrates a flow chart of a configuration process 300 of control information for periodic data transmission according to some embodiments of the present disclosure. For convenience, the following description will be made in connection with the context of fig. 1 and 2. In this example, the first device 110 is in an RRC connected state, and the second device 120 acts as a serving cell for the first device 110.

As shown in fig. 3, the second device 120 may send 310 control information to the first device 110 before the first device 110 enters the inactive state. In some embodiments, the second device 120 may configure the control information to the first device 110 in higher layer RRC signaling. In some embodiments, the second device 120 may configure the control information to the first device 110 in L1 signaling.

Fig. 4 shows a flow chart illustrating another configuration process 400 of control information for periodic data transmissions according to some embodiments of the present disclosure. For convenience, the following description will be made in connection with the context of fig. 1 and 2. In this example, the first device 110 is in an RRC inactive state, the second device 120 acts as the last serving cell for the first device 110, and the third device 130 acts as the anchor cell for the first device 110.

As shown in fig. 4, the second device 120, which is the last serving cell, may initiate 410 a paging procedure in a Radio Access Network (RAN) -based notification area (RNA) and instruct cells in the RNA to configure control information by paging messages. In this case, the third device 130, which is an anchor cell, may receive 420 the configuration of the control information from the second device 120 and send 430 a paging message including the control information to the first device 110. In this way, control information for the transmission of periodic data may be configured to the first device 110 based on the paging procedure.

Fig. 5 illustrates a flow chart of yet another configuration process 500 of control information for periodic data transmissions according to some embodiments of the present disclosure. For convenience, the following description will be made in connection with the context of fig. 1 and 2. In this example, the first device 110 is in an RRC inactive state, the second device 120 acts as the last serving cell for the first device 110, and the third device 130 acts as the anchor cell for the first device 110.

As shown in fig. 5, the second device 120, which is the last serving cell, may initiate 510 a paging procedure in the RNA and instruct the anchor cell to transmit control information to the first device 110 based on the RACH or CG-SDT procedure upon receiving an RRC connection recovery request from the first device 110. In this case, the second device 120 may transmit 520 control information to the third device 130 as an anchor cell. The third device 130 may send 530 a paging message to the first device 110.

In response to the paging message, the first device 110 may send 540 an RRC connection resume request to the third device 130. In some embodiments, the first device 110 may send the RRC connection recovery request in message a (MsgA) for the 2-step RACH procedure. The MsgA may also include a PRACH preamble. In some alternative embodiments, the first device 110 may send the RRC connection resume request in message 3 (Msg 3) for the 4-step RACH procedure.

The third device 130 may send 550 a response to the RRC connection resume request, the response including control information. In some embodiments in which the first device 110 sends a message a (MsgA) for a 2-step RACH procedure, the third device 130 may send a message B (MsgB) for a 2-step RACH procedure with control information to the first device 110. The MsgB may also include a successful Random Access Response (RAR) and an RRC release message. In some embodiments in which the first device 110 sends message 3 (Msg 3) for the 4-step RACH procedure, the third device 130 may send message 4 (Msg 4) for the 4-step RACH procedure with control information to the first device 110. In this way, the control information for the transmission of periodic data may be configured to the first device 110 based on the random access procedure.

Returning to fig. 2, upon receiving the configuration of the control information for the periodic data transmission, the first device 110 acquires the periodic data from the third device 130 in the inactive state. In some embodiments, the first device 110 may periodically initiate an RRC connection recovery procedure for periodic data transmissions based on the configuration of the control information. In some embodiments, the first device 110 may periodically send 221 a random access request with an indication to the third device 130 for acquiring periodic data.

In some embodiments where resources (e.g., 2-or 4-step RACH resources or CG-SDT resources) are configured in the control information, the first device 110 may send an RRC connection recovery request using the resources configured in the control information. In some alternative embodiments, the first device 110 may send the RRC connection recovery request in the CG PUSCH resources for the 2-step RACH procedure, the Msg3 for the 4-step RACH procedure, or the SDT based on the configuration of the anchor cell.

Regarding the indication for acquiring periodic data, in some embodiments, a recovery reason for acquiring periodic data may be carried in the UL MAC PDU along with the RRC connection recovery request. For example, the recovery reasons may indicate that periodic positioning assistance data is desired to be acquired. Of course, the restoration reason may indicate any other type of periodic data.

Upon receiving an RRC connection recovery request with an indication to acquire periodic data from the first device 110, the third device 130, which is an anchor cell, may request 222 periodic data of the first device 110 from the second device 120, which is a last serving cell.

Upon receiving the request for periodic data, the second device 120 may determine the periodic data. In some embodiments, the second device 120 may generate 223 periodic data. In some embodiments, the core network element 141 may generate 223 'periodic data and send 224' periodic data to the second device 120. In this case, the second device 120 may acquire periodic data from the core network element 141.

In some embodiments, the periodic data may include periodic positioning assistance data. In some embodiments, the periodic positioning assistance data may include positioning assistance data for high accuracy global navigation satellite system positioning (HA GNSS). In some embodiments, where DL-TDOA and UL-TDOA are used in combination, the periodic positioning assistance data may include uplink positioning measurements for synchronization error cancellation. In some embodiments, the periodic positioning assistance data may include a configuration of positioning reference signaling, such as uplink power control parameters of positioning Sounding Reference Signals (SRS). For example, the uplink power control parameters may include a configuration of a no-path reference RS and spatial relationship information or correlation rules. Of course, the periodic positioning assistance data may also comprise any other suitable information.

After determining the periodic data, the second device 120 may send 224 the periodic data to the third device 130. The third device 130 may send 225 periodic data to the first device 110. In some embodiments, the third device 130 may send periodic data to the first device 110 in DL MAC PDUs along with an RRC release message (i.e., a suspension indication).

In some embodiments, periodic data may be sent over MsgB for a 2-step RACH procedure. In some alternative embodiments, periodic data may be sent over Msg4 for a 4-step RACH procedure. In some alternative embodiments, periodic data may be transmitted through the DL PDSCH in response to receiving an RRC connection resume request through CG resources configured for SDT or periodic data transmission.

It should be noted that the acts illustrated in fig. 2-5 are not always necessary to implement embodiments of the present disclosure, and that more or fewer acts may be adapted as desired. The first device 110 in the RRC inactive state is enabled to periodically initiate an RRC connection recovery procedure for periodic data transfer in the RRC inactive state through the procedure described in connection with fig. 2 to 5. Furthermore, there is no need to perform a transition from the RRC inactive state to the RRC connected state. Furthermore, no paging procedure is required for periodic data transmission. Thus, power savings at the first device 110 may be achieved and paging overhead may also be reduced.

It should be appreciated that the process according to embodiments of the present disclosure may be applied to other application scenarios for DL SDT besides positioning assistance data transmission.

Corresponding to the procedure described in connection with fig. 2 to 5, embodiments of the present disclosure provide a communication method implemented at a first device, a second device, a third device and a core network element. These methods will be described below with reference to fig. 6 to 9.

Fig. 6 illustrates a flow chart of a communication method 600 implemented at a first device according to an example embodiment of the disclosure. The method 600 may be implemented at the first device 110 shown in fig. 1. For discussion purposes, the method 600 will be described with reference to FIG. 1. It should be understood that method 600 may also include additional blocks not shown and/or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

As shown in fig. 6, at block 610, the first device 110 receives control information for transmission of periodic data from at least one of the second device 120, the third device 130, or the core network element 141. In some embodiments, the first device 110 may receive control information in a signaling message from the second device 120 before entering the inactive state. In some embodiments, the first device 110 may receive control information from the third device 130 in an inactive state based on the paging procedure. In some embodiments, the first device 110 may receive control information from the third device 130 in an inactive state based on a random access procedure. In some embodiments, the first device 110 may receive control information from the core network element 141 in a user plane interface.

In some embodiments, the control information may include at least one of: an indication that the random access request needs to be periodically transmitted; the number of random access requests; a period of the random access request; or resources configured for transmitting the random access request. Of course, the control information may include any other suitable information.

At block 620, the first device 110 obtains periodic data from the third device 130 based on the control information in the inactive state. In some embodiments, the first device 110 may periodically send a random access request with an indication to the third device 130 to obtain periodic data based on the control information, and receive periodic data from the third device 130 in a response to the random access request.

In some embodiments, the periodic data may include periodic positioning assistance data. In some embodiments, the periodic positioning assistance data may include at least one of: positioning assistance data for HA GNSS; uplink positioning measurements for synchronization error cancellation in case of DL-TDOA and UL-TDOA combined use; or configuration of positioning reference signaling including uplink power control parameters of positioning SRS. For example, the uplink power control parameters may include a configuration of a no-path reference RS and spatial relationship information or correlation rules. Of course, the periodic positioning assistance data may comprise any other suitable information.

With the scheme of fig. 6, the first device in the inactive state is enabled to periodically initiate a random access procedure for acquiring periodic data in the inactive state without transitioning to the connected state. In contrast to conventional schemes, no paging procedure is required for periodic data transmission. Thus, power savings at the first device may be achieved and paging overhead at the network side may also be reduced.

Fig. 7 illustrates a flowchart of a communication method 700 implemented at a second device according to an example embodiment of the present disclosure. The method 700 may be implemented at the second device 120 shown in fig. 1. For discussion purposes, the method 700 will be described with reference to FIG. 1. It should be understood that method 700 may also include additional blocks not shown and/or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

As shown in fig. 7, at block 710, the second device 120 determines control information for transmission of periodic data. In some embodiments, the second device 120 may generate the control information. In some embodiments, the second device 120 may receive control information from the core network element 141.

At block 720, the second device 120 sends control information to the first device 110. The control information may be used by the first device 110 to obtain periodic data from the third device 130 in an inactive state. In some embodiments, the second device 120 may send control information to the first device 110 in a signaling message before entering the inactive state. In some embodiments, the second device 120 may send control information to the third device 130 for transmission to the first device 110 in the inactive state based on at least one of a paging procedure or a random access procedure.

In some embodiments, the second device 120 may receive a request from the third device 130 to obtain periodic data and send the periodic data to the third device 130. In some embodiments, the second device 120 may obtain periodic data from the core network element 141 and send the periodic data to the third device 130.

With the scheme of fig. 7, the second device can determine control information for transmitting periodic data to the first device, which facilitates the first device periodically initiating a random access procedure to acquire periodic data in an inactive state without transitioning to a connected state. In this case, the paging procedure is not required for periodic data transmission. Thus, power savings at the first device may be achieved and paging overhead at the network side may also be reduced.

Fig. 8 illustrates a flowchart of a communication method 800 implemented at a third device according to an example embodiment of the present disclosure. The method 800 may be implemented at the third device 130 shown in fig. 1. For discussion purposes, the method 800 will be described with reference to FIG. 1. It should be understood that method 800 may also include additional blocks not shown and/or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

As shown in fig. 8, at block 810, the third device 130 receives a random access request with an indication to acquire periodic data. The random access request is transmitted by the first device 110 in the inactive state based on control information for the transmission of periodic data, which is received from at least one of the second device 120, the third device 130 or the core network element 141. In some embodiments, the third device 130 may receive control information from the second device 120 and transmit the control information to the first device 110 in the inactive state.

In some embodiments, the third device 130 may send control information during the paging process (e.g., in a paging message). In some embodiments, the third device 130 may send the control information through an SDT procedure (e.g., CG-based SDT or RACH-based SDT).

At block 820, the third device 130 sends periodic data to the first device 110 in a response to the random access request. In some embodiments, the third device 130 may generate periodic data. In some embodiments, the third device 130 may send a request to the second device 120 to acquire periodic data and receive periodic data from the second device 120.

With the scheme of fig. 8, the third device may be configured to transmit control information of the periodic data to the first device, which facilitates the first device periodically initiating a random access procedure for acquiring the periodic data in the inactive state without transitioning to the connected state. In this case, the paging procedure is not required for periodic data transmission. Thus, power savings at the first device may be achieved and paging overhead at the network side may also be reduced.

Fig. 9 shows a flow chart of a communication method 900 implemented at a core network element according to an example embodiment of the present disclosure. The method 900 may be implemented at the core network element 141 shown in fig. 1. For discussion purposes, the method 900 will be described with reference to FIG. 1. It is to be appreciated that method 900 may also include additional blocks not shown and/or omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect.

As shown in fig. 9, at block 910, the core network element 141 generates control information for transmission of periodic data. In some embodiments, the control information may include at least one of: an indication that the random access request needs to be periodically transmitted; the number of random access requests; a period of the random access request; or resources configured for transmitting the random access request. Of course, the control information may include any other suitable information.

At block 920, the core network element 141 sends control information to the first device 110. In some embodiments, the core network element 141 may send control information to the first device 110 in a user plane interface. In some embodiments, the core network element 141 may send control information to the second device 120 for forwarding to the first device 110. The control information will be used by the first device 110 to obtain periodic data from the third device 130 in the inactive state.

In some embodiments, the core network element 141 may also generate periodic data and transmit the periodic data to the second device 120. In some embodiments, the periodic data may include periodic positioning assistance data. In some embodiments, the periodic positioning assistance data may include at least one of: positioning assistance data for HA GNSS; uplink positioning measurements for synchronization error cancellation in case of DL-TDOA and UL-TDOA combined use; or configuration of positioning reference signaling including uplink power control parameters of positioning SRS. For example, the uplink power control parameters may include a configuration of a no-path reference RS and spatial relationship information or correlation rules. Of course, the periodic positioning assistance data may comprise any other suitable information.

With the scheme of fig. 9, the core network device may generate control information for the transmission of periodic data, which facilitates the first device periodically initiating a random access procedure for acquiring periodic data in an inactive state without transitioning to a connected state. In this case, the paging procedure is not required for periodic data transmission. Thus, power savings at the first device may be achieved and paging overhead at the network side may also be reduced.

In some embodiments, an apparatus (e.g., first device 110) capable of performing any of the methods 600 may include means for performing the steps of the methods 600. The component may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

In some embodiments, the apparatus includes means for receiving, at a first device, control information for transmission of periodic data from at least one of a second device, a third device, or a core network element; and means for acquiring the periodic data from the third device in an inactive state based on the control information.

In some embodiments, the means for receiving control information comprises at least one of: means for receiving control information in a signaling message from the second device before entering the inactive state, means for receiving the control information from the third device in the inactive state based on at least one of a paging procedure or a random access procedure, or means for receiving the control information from the core network element in a user plane interface.

In some embodiments, the means for acquiring may include: means for periodically transmitting a random access request having an indication for acquiring the periodic data to the third device based on the control information; and means for receiving the periodic data from the third device in a response to the random access request.

In some embodiments, an apparatus (e.g., second device 120) capable of performing any of method 700 may include means for performing the various steps of method 700. The component may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

In some embodiments, the apparatus comprises: means for determining, at the second device, control information for transmission of periodic data; and means for transmitting the control information to the first device for obtaining the periodic data from the third device in an inactive state.

In some embodiments, the means for determining may include means for generating control information. In some embodiments, the means for determining may comprise means for receiving control information from a core network element.

In some embodiments, the means for transmitting may include at least one of: means for transmitting the control information to the first device in a signaling message prior to entering the inactive state, or means for transmitting the control information to the third device for transmission to the first device in the inactive state based on at least one of a paging procedure or a random access procedure.

In some embodiments, the apparatus may further comprise: means for receiving a request from the third device to acquire the periodic data; and means for transmitting the periodic data to the third device. In some embodiments, the means for transmitting periodic data may further comprise means for obtaining periodic data from a core network element; and means for transmitting the periodic data to the third device.

In some embodiments, an apparatus (e.g., third device 130) capable of performing any of method 800 may include means for performing the various steps of method 800. The component may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

In some embodiments, the apparatus includes means for receiving, at a third device, a random access request with an indication to acquire periodic data, the random access request sent by a first device in an inactive state based on control information for transmission of the periodic data, the control information received from at least one of a second device, the third device, or a core network element; and means for transmitting the periodic data to the first device in a response to the random access request.

In some embodiments, the apparatus may further comprise means for receiving control information from the second device; and means for transmitting the control information to the first device in the inactive state based on at least one of a paging procedure or a random access procedure.

In some embodiments, the apparatus may further comprise: means for sending a request to the second device to acquire the periodic data; and means for receiving the periodic data from the second device. In some embodiments, the periodic data may include periodic positioning assistance data. In some embodiments, the periodic positioning assistance data may include at least one of: positioning assistance data for HA GNSS; uplink positioning measurements for synchronization error cancellation in case of DL-TDOA and UL-TDOA combined use; or configuration of positioning reference signaling including uplink power control parameters of positioning SRS. For example, the uplink power control parameters may include a configuration of a no-path reference RS and spatial relationship information or correlation rules. Of course, the periodic positioning assistance data may comprise any other suitable information.

In some embodiments, an apparatus (e.g., core network element 141) capable of performing any of the methods 900 may include means for performing the various steps of the methods 900. The components may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules.

In some embodiments, the apparatus comprises: means for generating control information for transmission of periodic data at a core network element; and means for transmitting the control information to a second device, the control information forwarded by the second device to the first device for obtaining the periodic data from a third device in an inactive state.

In some embodiments, the apparatus may further comprise: means for generating the periodic data; and means for transmitting the periodic data to a second device. In some embodiments, the periodic data may include periodic positioning assistance data. In some embodiments, the periodic positioning assistance data may include at least one of: positioning assistance data for HA GNSS; uplink positioning measurements for synchronization error cancellation in case of DL-TDOA and UL-TDOA combined use; or configuration of positioning reference signaling including uplink power control parameters of positioning SRS. For example, the uplink power control parameters may include a configuration of a no-path reference RS and spatial relationship information or correlation rules. Of course, the periodic positioning assistance data may comprise any other suitable information.

Fig. 10 is a simplified block diagram of an apparatus 1000 suitable for implementing embodiments of the disclosure. The device 1000 may be provided to implement a first device, a second device, a third device or a core network element, such as the first device 110, the second device 120, the third device 130 or the core network element 141 shown in fig. 1. As shown, the apparatus 1000 includes: one or more processors 1010, one or more memories 1020 coupled to the processors 1010, and one or more communication modules 1040 (e.g., a transmitter and/or a receiver) coupled to the processors 1010.

The communication module 1040 is for bi-directional communication. The communication module 1040 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

The processor 1010 may be of any type suitable to the local technology network and may include, as non-limiting examples, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs), and processors based on a multi-core processor architecture. The device 1000 may have multiple processors, such as application specific integrated circuit chips, which are slaved in time to a clock that is synchronized to the master processor.

Memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact Disks (CD), digital Video Disks (DVD), and other magnetic and/or optical memory. Examples of volatile memory include, but are not limited to, random Access Memory (RAM) 1022 and other volatile memory that does not last during periods of power failure.

The computer program 1030 includes computer-executable instructions that are executed by the associated processor 1010. Program 1030 may be stored in ROM 1024. Processor 1010 may perform any suitable actions and processes by loading program 1030 into RAM 1022.

Embodiments of the present disclosure may be implemented by program 1030 such that device 1000 may perform any of the processes of the present disclosure discussed with reference to fig. 2-5. Embodiments of the present disclosure may also be implemented in hardware or by a combination of software and hardware.

In some embodiments, program 1030 may be tangibly embodied in a computer-readable medium that may be included in device 1000 (e.g., memory 1020) or other storage device accessible to device 1000. Device 1000 may load program 1030 from the computer readable medium into RAM 1022 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, etc. Fig. 11 shows an example of a computer readable medium 600 in the form of a CD or DVD. The computer-readable medium has stored thereon the program 1030.

In general, the various embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the disclosed embodiments are shown and described as block diagrams, flowcharts, or using some other illustration, it is to be understood that the block diagrams, apparatus, systems, techniques, or methods described herein may be implemented, as non-limiting examples, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers, or other computing devices, or some combination thereof.

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 comprises computer executable instructions, such as instructions included in program modules, that are executed in a device on a target real or virtual processor to perform the methods 600-900 described above with reference to fig. 6-9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions of program modules may be executed within local or distributed devices. In distributed devices, program modules may be located in both local and remote memory storage media.

Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These 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, results in the implementation of the functions/operations specified in the flowchart and/or block diagram block or blocks. The program code may execute entirely on the machine, partly on the machine and partly on a remote machine, or entirely on the remote machine or server as a stand-alone software package.

In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations described above. Examples of carriers include signals, computer readable media, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is 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 a computer-readable storage medium 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.

Moreover, although operations are described in a particular order, this should not be understood as requiring that such operations be performed in the particular order or sequence illustrated, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while in the foregoing discussion contains several specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the 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, comprising:

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, with the at least one processor, cause the first device to:

receiving control information for transmission of periodic data from at least one of the second device, the third device or the core network element; and

based on the control information, the periodic data is acquired from the third device in an inactive state.

2. The first device of claim 1, wherein the first device is caused to obtain the periodic data by:

periodically transmitting a random access request to the third device based on the control information, the random access request having an indication for acquiring the periodic data; and

in a response to the random access request, the periodic data from the third device is received.

3. The first device of claim 1, wherein the control information comprises at least one of:

an indication that the random access request needs to be periodically transmitted;

the number of random access requests;

A period of the random access request; or (b)

Resources configured for transmitting the random access request.

4. The first device of claim 1, wherein the periodic data comprises periodic positioning assistance data.

5. The first device of claim 4, wherein the periodic positioning assistance data comprises at least one of:

positioning assistance data for high-precision global navigation satellite system positioning;

uplink positioning measurements for synchronization error cancellation in case the downlink arrival time difference and the uplink arrival time difference are used in combination; or (b)

Configuration of positioning reference signaling includes uplink power control parameters of positioning sounding reference signals.

6. The first device of claim 1, wherein the first device is caused to receive the control information by at least one of:

before entering the inactive state, receiving the control information in a signaling message from the second device,

receiving the control information from the third device in the inactive state based on at least one of a paging procedure or a random access procedure, or

In a user plane interface, the control information is received from the core network element.

7. The first device of claim 1, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

8. A second device, comprising:

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, with the at least one processor, cause the second device to:

determining control information for transmission of periodic data; and

and sending the control information to the first device for acquiring the periodic data from the third device in the inactive state.

9. The second device of claim 8, wherein the control information comprises at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

10. The second device of claim 8, wherein the periodic data comprises periodic positioning assistance data.

11. The second device of claim 10, wherein the periodic positioning assistance data comprises at least one of:

12. The second device of claim 8, wherein the second device is caused to determine the control information by:

the control information is received from a core network element.

13. The second device of claim 8, wherein the second device is caused to transmit the control information by at least one of:

transmitting the control information to the first device in a signaling message, or

The control information is sent to the third device for transmission to the first device in the inactive state based on at least one of a paging procedure or a random access procedure.

14. The second device of claim 8, wherein the second device is further caused to:

receiving a request from the third device to acquire the periodic data; and

and sending the periodic data to the third device.

15. A second device according to claim 14, wherein the second device is caused to transmit the periodic data by:

acquiring the periodic data from a core network element; and

and sending the periodic data to the third device.

16. The second device of claim 8, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

17. A third device, comprising:

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, with the at least one processor, cause the third device to:

receiving a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and

In a response to the random access request, the periodic data is sent to the first device.

18. The third device of claim 17, wherein the control information includes at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

19. The third apparatus of claim 17, wherein the periodic data comprises periodic positioning assistance data.

20. The first device of claim 19, wherein the periodic positioning assistance data comprises at least one of:

21. The third device of claim 17, wherein the third device is further caused to:

Receiving the control information from the second device; and

the control information is transmitted to the first device in the inactive state based on at least one of a paging procedure or a random access procedure.

22. The third device of claim 17, wherein the third device is further caused to:

transmitting a request to the second device for acquiring the periodic data; and

the periodic data is received from the second device.

23. The third device of claim 17, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

24. A core network element comprising:

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, with the at least one processor, cause the core network element to:

generating control information for transmission of the periodic data; and

25. A core network element according to claim 24, wherein the core network device is caused to send the control information by:

and sending the control information to a second device for forwarding to the first device.

26. The core network element of claim 24, wherein the control information comprises at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

27. The core network element of claim 24, wherein the periodic data comprises periodic positioning assistance data.

28. The core network element of claim 26, wherein the periodic positioning assistance data comprises at least one of:

29. The core network element of claim 24, wherein the core network element is further caused to:

generating the periodic data; and

and sending the periodic data to a second device.

30. The core network element of claim 25 or 29, wherein the first device is a terminal device, the second device is a network device acting as a last serving cell for the first device, and the third device is a network device acting as an anchor cell for the first device.

31. A method for communication, comprising:

at the first device, receiving control information for transmission of periodic data from at least one of the second device, the third device, or the core network element; and

32. The method of claim 31, wherein obtaining the periodic data comprises:

periodically transmitting a random access request with an indication for acquiring the periodic data to the third device based on the control information; and

33. The method of claim 31, wherein the control information comprises at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

34. The method of claim 31, wherein the periodic data comprises periodic positioning assistance data.

35. The method of claim 34, wherein the periodic positioning assistance data comprises at least one of:

uplink positioning measurements for synchronization error cancellation in case of a downlink arrival time difference and an uplink arrival time difference used in combination; or (b)

36. The method of claim 31, wherein receiving the control information comprises at least one of:

37. The method of claim 31, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

38. A method for communication, comprising:

determining, at the second device, control information for transmission of periodic data; and

39. The method of claim 38, wherein the control information comprises at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

40. The method of claim 38, wherein the periodic data comprises periodic positioning assistance data.

41. The method as recited in claim 40, wherein said periodic positioning assistance data comprises at least one of:

42. The method of claim 38, wherein determining the control information comprises:

the control information is received from a core network element.

43. The method of claim 38, wherein transmitting the control information comprises at least one of:

44. The method of claim 38, further comprising:

receiving a request from the third device to acquire the periodic data; and

And sending the periodic data to the third device.

45. The method of claim 44, wherein transmitting the periodic data comprises:

acquiring the periodic data from a core network element; and

and sending the periodic data to the third device.

46. The method of claim 38, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

47. A method for communication, comprising:

at a third device, receiving a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and

48. The method of claim 47, wherein the control information comprises at least one of:

the number of random access requests;

a period of the random access request; or (b)

Resources configured for transmitting the random access request.

49. The method of claim 47, wherein the periodic data comprises periodic positioning assistance data.

50. The method as recited in claim 49, wherein said periodic positioning assistance data comprises at least one of:

51. The method of claim 47, further comprising:

receiving the control information from the second device; and

52. The method of claim 47, further comprising:

the periodic data is received from the second device.

53. The method of claim 47, wherein the first device is a terminal device, the second device is a network device that acts as a last serving cell for the first device, and the third device is a network device that acts as an anchor cell for the first device.

54. A method for communication, comprising:

generating, at a core network element, control information for transmission of periodic data; and

and transmitting the control information to a first device, wherein the control information is used by the first device to acquire the periodic data from a third device in an inactive state.

55. The method of claim 54, wherein transmitting the control information comprises:

56. The method of claim 54, wherein the control information includes at least one of:

the number of random access requests;

A period of the random access request; or (b)

Resources configured for transmitting the random access request.

57. The method of claim 54, wherein the periodic data comprises periodic positioning assistance data.

58. The method as recited in claim 57, wherein said periodic positioning assistance data comprises at least one of:

59. The method of claim 54, further comprising:

generating the periodic data; and

and sending the periodic data to a second device.

60. The method of claim 55 or 59, wherein the first device is a terminal device, the second device is a network device acting as a last serving cell for the first device, and the third device is a network device acting as an anchor cell for the first device.

61. An apparatus for communication, comprising:

means for receiving, at the first device, control information for transmission of periodic data from at least one of the second device, the third device, or the core network element; and

means for acquiring the periodic data from the third device in an inactive state based on the control information.

62. An apparatus for communication, comprising:

means for determining, at the second device, control information for transmission of periodic data; and

and means for transmitting the control information to the first device for acquiring the periodic data from the third device in the inactive state.

63. An apparatus for communication, comprising:

means for receiving, at a third device, a random access request with an indication for acquiring periodic data, the random access request being sent by a first device in an inactive state based on control information for transmission of periodic data, the control information being received from at least one of a second device, the third device or a core network element; and

means for transmitting the periodic data to the first device in a response to the random access request.

64. An apparatus for communication, comprising:

means for generating control information for transmission of periodic data at a core network element; and

means for transmitting the control information to a first device, the control information being used by the first device to obtain the periodic data from a third device in an inactive state.

65. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method of any one of claims 31 to 37.

66. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method of any one of claims 38 to 46.

67. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method of any one of claims 47 to 53.

68. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method of any one of claims 54 to 60.