WO2025002862A1

WO2025002862A1 - System configured to manage data transmission in or with a telecommunications network and shared PDU session data structure

Info

Publication number: WO2025002862A1
Application number: PCT/EP2024/066690
Authority: WO
Inventors: Nassima TOUMI; Toni Dimitrovski; José Luis Almodóvar Chico
Original assignee: Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO; Koninklijke KPN NV
Current assignee: Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO; Koninklijke KPN NV
Priority date: 2023-06-26
Filing date: 2024-06-14
Publication date: 2025-01-02
Anticipated expiration: 2025-12-26

Abstract

The disclosure pertains to a system that is configured to manage data transmission in or with a telecommunications network using a shared protocol data unit, PDU, session, to convey data from a set of devices. The system may be configured to apply a selection filter to select the set of devices from a plurality of devices. The selection filter may be configurable in accordance with selection information applicable to the set of devices. Furthermore, the system is configured to manage the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter. The configurable selection filter of the system allows the single PDU session to be shared by different sets of devices. This provides for dynamic use of the PDU session, since the selection information can be configured, for example changed, to configure the set of devices using the shared PDU session dynamically.

Description

P2308PC00

System configured to manage data transmission in or with a telecommunications network and shared PDU session data structure

TECHNICAL FIELD

The present disclosure relates to a system configured to manage data transmission in or with a telecommunications network and a shared PDU session data structure. In particular, the disclosure pertains to a system configured to manage data transmission using a shared protocol data unit, PDU, session, established to convey data from a set of devices and to a shared PDU session data structure for use in such a system.

BACKGROUND

Future networks are expected to host a significant number of devices that store and/or collect data that should be uploaded via a telecommunications network infrequently or in small amounts and delivered to a data collecting entity. Such data transmissions should be managed efficiently in a telecommunications network.

For example, 3GPP recently issued a study on ambient power-enabled Internet of Things, loT, devices in Technical Recommendation 3GPP TR 22.840. The document discloses use cases and requirements for ambient power-enabled loT devices, hereinafter also referred to as ambient loT devices, being battery-less devices with limited energy storage capability (a capacitor may be included) wherein the energy is provided through the harvesting of radio waves, light, motion, heat or any other power source that could be suitable. Thus, energy is a very scarce resource in this context, and its usage is preferably optimized by limiting computations and/or the number and size of exchanged messages. Additionally, an ambient loT device may remain passive for extended periods of time before receiving a wake-up signal and starting to send data.

The telecommunications network should efficiently host large numbers of non-powered ambient loT devices, that can perform simple tasks and communicate only when receiving a power signal. Ambient loT devices would normally only perform necessary tasks and send useful data. Hence, establishing a PDU session in or with the telecommunications network for each ambient loT device, for example, is energy consuming because this requires the exchange of multiple messages. It is also impractical to reserve a PDU session for each ambient loT device and for each communication flow due to the expected large number of devices, as well as their activity pattern (for example, passive for extended periods of time and/or sending small amounts of data at a time). Furthermore, establishing a new PDU session each time an individual ambient loT device is activated is not energy efficient since PDU session establishment requires the exchange of multiple messages.

SUMMARY

The inventors have realized that it may be beneficial for a telecommunications operator to allow multiple ambient loT devices to use a limited number of PDU sessions. To that end, a system is disclosed that is configured to manage data transmission in or with a telecommunications network using a shared protocol data unit, PDU, session, to convey data from a set of devices. The system may be configured to apply a selection filter to select the set of devices from a plurality of devices. The selection filter may be configurable in accordance with selection information applicable to the set of devices. Furthermore, the system is configured to manage the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter.

It should be appreciated that the system may be a single component but may also be distributed over several devices, network nodes or locations. In one embodiment, the system is comprised in a user equipment or other device configured to establish a PDU session with the telecommunications network.

The selection filter of the system allows the single PDU session to be shared by different sets of devices. This provides for dynamic use of the PDU session, since the selection information can be configured, for example changed, to configure the set of devices using the shared PDU session dynamically. For example, the devices making use of an existing shared PDU session may change without requiring the shared PDU session to be (re-)established.

It should be appreciated that the selection filter may apply the selection information itself to perform a filter action or may apply filter information associated with or derivable from the selection information. A mapping table may be used to this end. For example, if the selection information relates to a list of device identifiers and responses from these devices include device identifiers, this information may be used to filter data for the shared PDU session. If the selection information pertains to devices in a certain area covered by selection sources, the system may use selection source identifiers known to cover this area and use a mapping table to map device identifiers to selection source identifiers.

Another aspect of this disclosure involves a shared PDU session data structure for exchanging data of a set of devices from a plurality of devices. The data structure comprises a shared PDU session identifier and, optionally, associated information identifying the selected set of devices, such as the selection information. The set of devices may comprise at least two devices. It is noted that the information identifying the selected set of devices may be included instead of the identifier of a particular device, such as a UE, that is normally included in the PDU session data structure. Such identifying information may include at least one of a device identifier(s) of at least one set of devices, a device group identifier of at least one set of devices, a location identifier of at least a part of one set of devices, a service type identifier of devices of at least one set of devices, a data type identifier of data from devices of at least one set of devices, a data characteristic identifier of data from devices of at least one set of devices, etc. This identifying information will be explained in further detail below, for example the location identifier may identify an area where at least one device is present or expected to be present.

It should be noted that shared PDU sessions as such are known from personal loT networks (PIN), as disclosed in 3GPP TS 23.700-88, version 18.0.0. In such a PIN, a PIN element with gateway capabilities (PEGC) is registered in the network as a user equipment, UE, and can be used for data transmission over a PDU session for all devices of the PIN. However, such PEGC only maps devices in the PIN to a shared PDU session in a static fashion. A PEGC may support multiple PINs.

In an embodiment, the system comprises at least one selection source configured to transmit a selection signal to the plurality of devices. The selection information relates to at least one of a selected radio resource of the selection signal, such as timing of transmission of the selection signal, and selection information in the selection signal. In this manner, the responding devices can be tied to the data transmitted over the shared PDU session. The system provides granularity as to the devices from which data are to be collected.

For example, the selection signal may be transmitted at a certain time by one or more selection sources, e.g. base stations, and responses from all devices within the coverage area of the selection source resulting from this selection signal are accepted by the selection filter to use the shared PDU session, for example within a certain time interval, starting, for example, at or sometime after the transmission of the selection signal.

Another example pertains to targeting certain devices by including the selection information associated with the selection filter in the selection signal and receive responses from the set of devices corresponding to the selection information for transmission over the shared PDU session.

In one embodiment, the selection source may contain at least one power source configured to transmit a power signal for wirelessly powering the set of devices. The selection information may involve at least one of timing of the transmission of the power signal and selection information embedded in the power signal, to select the set of devices to provide the data to the system. By binding the power signal transmitted in accordance with the selection information with the routing of the collected data in the system (e.g. via a mapping table comprised in the selection filter), a granular selection of ambient loT devices can be combined with a dynamically shared PDU session.

It is noted that, as an example, various embodiments for embedding selection information in a power signal are described in co-pending European patent application EP22210972.0.

Briefly, an ambient loT device may comprise at least a power harvesting part, a processing part and a storage part configured to store selection information. The power harvesting part may be configured to harvest power from the power signal of a power source connected to the system to operate the processing part. The processing part that is powered by the power signal may be configured to determine its selection from the received selection information and stored selection information, if any, and to perform communication only when its selection is determined.

The system enables to target specific ambient loT devices out of a large number of ambient loT devices in an area for data collection. The selection of the ambient loT devices is performed efficiently by using the power signal that is needed to provide power to the ambient loT device for activation. While all ambient loT devices in the area receive power from the power signal, the system and ambient loT devices enable that only selected ambient loT devices may respond to the selection signal in the embodiment wherein selection information is embedded in the power signal.

The system and ambient loT device may, for example, be configured such that the power signal comprises or consists of a single power pulse wherein the selection information is modulated in/demodulated from the single power pulse. The power pulse is a transmission or burst of energy that, at least in part, fluctuates in amplitude, frequency and/or phase to represent the selection information. One example includes a signal that starts from zero to form a preamble (e.g. a sine wave) and then embeds the signaling information as a frequency, amplitude, and/or phase variation (e.g. of the sine wave), possibly terminated by a postamble at the original (carrier) frequency before the amplitude is back to zero.

In one embodiment, the system is configured to process a data collection request to collect data from the set of devices, such as ambient loT devices. It should be appreciated that the data collection request may or may not originate from a data collecting entity participating in the shared PDU session to collect the data.

In one embodiment, the data collection request causes the system to perform establishing at least one shared PDU session. The data collection request may contain data collection information to configure the selection filter to manage the data transmission over the shared PDU session to be established.

In another embodiment, the data collection request causes the system to perform modifying at least one shared PDU session. The data collection request may contain data collection information to configure the selection filter to manage the data transmission over the shared PDU session to be modified.

The embodiment allows a third party, such as a data collection entity or another entity, to request data collection from a set of devices using data collection information. The system operator may translate that data collection information to the selection information in accordance to which the selection filter is configured and, hence, to target and/or define devices that are allowed to have data transmitted over the shared PDU session.

In one embodiment, the system is configured to generate a shared PDU session identifier associated with the shared PDU session. The shared PDU session identifier can be suitably used in the telecommunications system to identify the shared PDU session. The shared PDU session identifier may be used for establishing or modifying a shared PDU session, e.g. to identify a setting for the configurable selection filter.

Optionally, the system may be configured to process a request for a management PDU session. The management PDU session may be used for a third party to initialize and/or control the system, such as the configurable selection filter.

It should be appreciated that access to the system for third parties may also be configured in other manners, for example by providing an application programming interface, API, allowing access for a third party to the system to initialize and/or control the system, such as the configurable selection filter.

The shared PDU session identifier may, for example, be received in a data collection request from a party to establish or modify the shared PDU session, that was previously obtained from the system.

In one embodiment, the request for a management PDU session and the data collection request to establish or modify the shared PDU session constitute a single request. The combination of both reduces the amount of signaling in the telecommunications network. In one embodiment, the system contains a control parameter to control data transmission to a data collecting entity. The embodiment improves control over the use of shared PDU sessions for a third party.

For example, the control parameter may contain a repetition parameter for controlling repetition(s) of data transmissions from a set of devices to the collecting entity. The repetition parameter may control repeated data transmission over the established shared PDU session. The repetition control parameter may control re-establishment of the shared PDU session and/or may control modification of the shared PDU session. The repetition parameter may, for example, indicate a number of times data can be transmitted over the established shared PDU session, the time intervals wherein data can be transmitted over the shared PDU session, the number of times the shared PDU session should be established, a time interval between successive establishments of the shared PDU session, a number of modifications allowed for the shared PDU session etc. The embodiment avoids sending multiple data collection requests and/or repeatedly establishing management PDU sessions and, therefore, reduces communication over the telecommunications network. Advantageously, the same shared PDU identifier is used for repeated data transmission over a shared PDU session and/or for re-established shared PDU sessions. Tracking repetitions may be facilitated in this manner and/or re-establishment of the shared PDU session may be quicker in this manner.

The system may be configured to receive the control parameter, such as the repetition parameter, in a data collection request or over a management PDU session.

In one embodiment, the system is configured with a timer to control a time interval during which data received from devices is allowed to be transmitted over the shared PDU session when in accordance with the applicable selection filter. The timer provides for some flexibility on the timing of acceptance of data in the shared PDU session. This may be beneficial in case of slowly responding devices or when it is not even known whether devices are within reach of the system. In one embodiment, the system gathers the data collected from the devices and conveys the data corresponding to the selection filter over the shared PDU session upon expiry of the timer.

In one embodiment, the system is configured to use a plurality of shared PDU sessions for data transmission. The selection filter may be configured in accordance with selection information for different sets of devices to manage data transmission such that data is sent over a shared PDU session in accordance with the applicable selection information.

The system comprises an aggregation point for the data of various sets of devices and for establishing PDU sessions, wherein each PDU session will be shared between the devices of a particular set corresponding to a filter setting. The system enables differentiation between data received from the devices and determine with which PDU session the received data is associated in order to manage the data transmission.

In one embodiment, the selection filter is configurable with selection information. The selection information may be provided by or be derived from data collection information received from a third party such as an operator of devices, a data collecting party, or another party. The selection information serves to target devices from which data should be collected, which data may be conveyed using a particular associated shared PDU session. Examples of such selection information include one or more of the following, including derivatives of such examples.

For example, the selection information may include one or more device identifiers of at least one set of devices. Such information may comprise a list of devices. The device identifiers may be provided by a third party or may already be accessible in the system, such as in a register in the telecommunications network. This information enables the system to collect data of devices corresponding to the device identifier(s) and to route the collected data over a shared PDU session associated with these identified devices.

The selection information may also comprise a device group identifier for at least one set of devices. An operator of the devices may have pre-allocated one or more group identifiers to some or all of the devices from which data may be collected. This information enables the system to collect data regarding one or more devices belonging to a particular group and to route the collected data over a shared PDU session for devices associated with the group.

The selection information may also comprise a location identifier of at least a part of one set of devices. The location identifier may, for example, point or relate to a certain area wherein data is to be collected from devices in that area. The location identifier may comprise geographic coordinates. A derivative of a location information identifier includes particular, stationary, selection sources, such as radio base stations, that have a coverage area covering devices from which data is to be collected. This information enables the system to collect data regarding devices in a particular location and to route the collected data over a shared PDU session associated with devices at that location. As such, the location identifier may comprise one or more base station identifiers, cell identifiers, or sector identifiers.

Yet another example of selection information involves a service type identifier of services of devices relating to, for example, one or more particular applications for which the devices are tailored. This information enables the system to collect data relating to a particular service or services and to route the collected data over a shared PDU session associated with a particular service of a device.

A still further example involves a data type and/or data characteristic identifier of data for devices from a set of devices. Data may be collected from devices corresponding to the data type and/or data characteristic and may be routed over a shared PDU session associated with the data type or data characteristic.

In one embodiment, the system comprises at least a PDU gateway and a device gateway. The PDU gateway may be configured to manage the shared PDU session using the configurable selection filter. The device gateway may be configured to transmit a selection signal to the plurality of devices. Optionally, the selection information may be associated with a radio resource selected for the selection signal and/or selection information in the selection signal.

The PDU gateway and device gateway may be included in one component. However, distributing the system over a PDU gateway and a device gateway enables deployment of each of the gateways at an appropriate place. For example, the PDU gateway can be deployed centrally, for example in a telecommunications network, whereas the device gateway can be located close to devices from which data may need to be collected. For example, when the devices comprise ambient loT devices, the device gateway may comprise a power source to transmit a power signal for wirelessly powering the set of ambient loT devices and can be placed close to the ambient loT device. The power signal may have embedded selection information to select the set of devices to provide the data to the PDU gateway.

In one embodiment, the PDU gateway is configured to process mapping information of device gateways and devices, such as ambient loT devices, in a coverage area of the device gateways. This embodiment allows the PDU gateway, when having received a data collection request, to only send a selection signal to one or more device gateways to collect the data, based on, e.g. data collection information obtained from a data collecting party, e.g. a third party. The device gateway or device gateways do not need to know the devices from which data should be collected. Also, a data collection party does not need to know which device gateway covers which of the devices. In this embodiment, for example, ambient loT devices only need a power signal without further selection information to be included in the power signal to collect data from all devices receiving the power signal.

In one embodiment, the PDU gateway is configured to receive device information from the device gateway to enable selection of device gateways to collect data from the devices in accordance with the selection filter. This enables the PDU gateway to obtain information regarding mapping device gateways to devices reachable by the respective device gateways. The device information may be obtained on request of the PDU gateway or by receiving advertise messages from the device gateway having collected this information from devices within reach of the respective device gateways.

In one embodiment, the PDU gateway is configured to broadcast the selection signal to a plurality of device gateways. This embodiment is beneficial when the PDU gateway has no or only limited information on the devices within reach of the device gateways. The device gateways may have this information stored locally and may be triggered by the broadcast selection signal from the PDU gateway to collect data from the devices within their reach and forward the data to the PDU gateway, when received, immediately or afterwards.

In one embodiment, the PDU gateway is configured to instruct a network node, for example a core network node, of the telecommunications network to select the set of devices to which the selection signal should be sent via the device gateway. In this embodiment, the system comprises a further network node, e.g. a system having access to a register with device information on devices within reach of device gateways, so that individual devices or groups of devices are known within the system.

In one embodiment, the system comprises at least a PDU gateway and a device gateway. The device gateway may be configured to advertise device information to the PDU gateway of devices within a wireless coverage area of the device gateway. This embodiment may assist the PDU gateway to acquire information on the devices associated with each device gateway for subsequent collection of data.

In one embodiment, the device gateway is configured to gather device information of devices within a wireless coverage area of the device gateway. To that end, the device gateway may optionally send discovery requests. The embodiment assists the device gateway to obtain the device information for either local use by applying the gathered device information to select the set of devices from which data should be collected (for example, when receiving the broadcast trigger to collect data from the PDU gateway) or to forward to the PDU gateway (e.g. to populate a mapping table in the PDU gateway).

In one embodiment, the device gateway is configured to select a subset of the set of devices and join a shared PDU session of the PDU gateway for data transmission of the subset of devices over the joined shared PDU session. This embodiment is beneficial when the device gateway is aware of the shared PDU session and of the setting of the selection filter so that it can apply the selection filter.

In one embodiment, the PDU gateway is a core network node in the telecommunications network and the device gateway is contained in a base station of the telecommunications network. The embodiment is beneficial for using existing network infrastructure and allows telecom operators to provide a service in a controlled and efficient manner.

In one embodiment, the PDU gateway is a core network node in the telecommunications network and the device gateway is a device registered and wirelessly connectable to the telecommunications network. The registration of the device gateway in the network enables the network to directly identify and target the set of devices to collect data from and send the selection signal to only the relevant device gateways.

In one embodiment, the PDU gateway is contained in a device registered in and wirelessly connectable to the telecommunications network. The device may be a wearable device, such as a UE. Optionally, the device also comprises the device gateway.

In one embodiment, the PDU gateway may be configured to only establish and/or modify a shared PDU session between a device gateway and a data collecting entity. The PDU gateway transmits a shared PDU session identifier to the device gateway. In one embodiment, the device gateway is configured to direct the data transmissions from responding devices over a shared PDU session established between the device gateway and a data collecting entity over the telecommunications network. The selection filter configured with the selection information for responses from devices is then applied in the device gateway.

Another aspect of the disclosure pertains to a method for managing data transmission in or with a telecommunications network using a shared protocol data unit, PDU, session, to convey data from a set of devices. The method involves the step of applying a selection filter to select the set of devices from a plurality of devices, wherein the selection filter is configurable in accordance with selection information applicable to the set of devices. The method may also involve the step of managing the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter.

Embodiments of this method involve performing one or more steps in the system as claimed in the dependent claims.

Yet another aspect of the disclosure involves a computer program or suite of computer programs comprising one or more software code portions configured, when run in the system, to perform one or more steps of the above-identified method. Another aspect of the disclosure comprises a combination of a system as claimed with a plurality of devices for data transmission over the shared PDU session compliant with the selection information. In particular, such a combined system involves a combined system comprising a system configured to manage data transmission in or with a telecommunications network using a shared protocol data unit, PDU, session, to convey data from a set of devices, wherein the system is configured to apply a selection filter to select the set of devices from a plurality of devices, wherein the selection filter is configurable in accordance with selection information applicable to the set of devices, and wherein the system is configured to manage the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter. The combined system further comprises a plurality of devices configured to transmit data to the system for transmission over the shared PDU session in accordance with the configurable selection filter.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, a method or a computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Functions described in this disclosure may be implemented as an algorithm executed by a processor/microprocessor of a computer. Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied, e.g., stored, thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer readable storage medium may include, but are not limited to, the following: 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. In the context of the present invention, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber, cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the person's computer, partly on the person's computer, as a stand-alone software package, partly on the person's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the person's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor, in particular a microprocessor or a central processing unit (CPU), of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer, other programmable data processing apparatus, or other devices create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Moreover, a computer program for carrying out the methods described herein, as well as a non- transitory computer readable storage-medium storing the computer program are provided.

Elements and aspects discussed for or in relation with a particular embodiment may be suitably combined with elements and aspects of other embodiments, unless explicitly stated otherwise. Embodiments of the present invention will be further illustrated with reference to the attached drawings, which schematically will show embodiments according to the invention. It will be understood that the present invention is not in any way restricted to these specific embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the invention will be explained in greater detail by reference to exemplary embodiments shown in the drawings, in which:

FIGS. 1A and 1 B are schematic illustrations of systems configured to manage data transmission over a shared protocol data unit, PDU, session from one or more sets of a plurality of devices;

FIGS. 2A - 2C are schematic illustrations of further embodiments of the system configured to manage data transmission over a shared protocol data unit, PDU, session and a plurality of devices, including a selection source;

FIGS. 3A-3C are schematic illustrations of an embodiment of an ambient loT device configured to respond to a selection signal triggering a data transmission;

FIG. 4 is a schematic illustration of an implementation of (a part of) the system configured to manage data transmission over a shared PDU in a telecommunications network;

FIG. 5 is a message flow diagram showing a series of steps for managing and executing data transmission over a shared PDU session;

FIGS. 6A-6C are schematic illustrations of different implementations of the system with respect to the telecommunications network;

FIGS. 7 A - 7C show the implementations of a selection system in a 5G telecommunications network, and

FIG. 8 depicts an example of a processing system according to an embodiment of a system or a part thereof.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic illustration of a combination 100 of a system 10 configured to manage data transmission of a plurality of devices D1-D9 over a shared protocol data unit, sPDU, session. The data transmission is sent to a data collecting entity DCE over the sPDU session to convey data from a set of the plurality of devices D1-D9. The set S1 of devices may, for example, consist of devices D2, D3, D5, D8 and D9 as shown in FIG. 1A.

The system 10 comprises a selection filter 11 to select the set S1 of devices from the plurality of devices D1-D9 to be eligible for transmission over the sPDU session. The selection filter 11 is configurable in accordance with selection information that is applicable to the set S1 of devices. The system 10 is configured to manage the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter. The selection filter may, for example, apply the selection information to decide which devices are eligible for data transmission over the sPDU session.

The configurable selection filter of the system allows the single PDU session to be shared by different sets of devices, such as set S1 . This provides for dynamic use of the shared PDU session, since the selection information can be configured, for example changed, to select the set S1 of devices using the shared PDU session dynamically. For example, the devices D2, D3, D5, D8, D9 making use of the shared PDU session may change without requiring the PDU session to be (reestablished. The configuration of the selection filter 11 may be performed from a filter configuration entity FCE. The filter configuration entity FCE may or may not be operated by the same party as the data collection entity DCE. The data collecting entity DCE may control or instruct the filter configuration entity FCE to set the selection information. The FCE, or a part thereof, may be part of the system 10.

The shared PDU session is described by a data structure comprising a shared PDU session identifier sPDUJD and associated information identifying the selected set S of devices, such as the selection information as shown in FIG. 1A. The set S1 of devices may comprise at least two devices. Such identifying information may include at least one of device identifiers of at least one set of devices, a device group identifier of at least one set of devices, a location identifier of devices of at least one set of devices, a service type identifier of devices of at least one set of devices, a data type identifier of data from devices of at least one set of devices, a data characteristic identifier of data from devices of at least one set of devices, etc. This identifying information will be explained in further detail below.

FIG. 1 B is a schematic illustration of another embodiment, wherein the system 10 is configured to use a plurality of shared PDU sessions, sPDU1 and sPDU2, for data transmission. The shared PDU sessions can be distinguished using different shared PDU session identifiers sPDUJD, sPDUJDI for sPDU1 and sPDU_ID2 for SPDU2, and may further have different selection information as shown, for example different device identifiers, different device group identifiers and/or different data type identifiers. The selection filter 11 may be configured in accordance with selection information for different sets S1 , S2 of devices to manage data transmission such that data is sent over a sPDU session in accordance with the applicable selection information. In FIG. 1 B, devices D2, D3, D5, D8, D9 are selected to be part of set S1 , whereas devices D1 , D4, D6 and D7 are selected to be part of set S2.

The system 10 comprises an aggregation point for the data of various sets S1 , S2 of devices and is configured to establish or modify a sPDU session. Each PDU session will be shared between the devices D2, D3, D5, D8 and D9 resp. D1 , D4, D6 and D7 of a particular set S1 resp. S2 corresponding to a filter setting of selection filter 11. The system 10 enables differentiation between data received from the set of devices and determination with which PDU session the received data is associated in order to manage the data transmission over the respective sPDU sessions.

It is noted that in FIG. 1 B, device D4 is allocated to set S2 because the device matches the selection information (for example, the same group identifiers as devices D1 , D6 and D7) but does not participate in the data transmission. This may be due to local circumstances, such as lack of transmission power or because the device D4 is not in reach of the system.

FIG. 2A is a schematic illustration of a further embodiment of the combination of the system 10 and a plurality of devices D1-D9. The system 10 comprises at least one selection source 12. The selection source 12 is configured to transmit a selection signal PS to the plurality of devices D1-D9.

The selection information in the selection signal PS may relate to a selected radio resource of the selection signal, such as timing of transmission of the selection signal PS or a code or frequency selected for the selection signal PS. The selection information may also relate to information in the selection signal PS, such as device identifiers, device group identifiers, location identifiers, device type identifiers, data type identifiers, etc. as will be set out below in further detail. By applying the selection information or a derivative thereof, in the selection filter 11 , the responding devices can be tied to the data transmitted over the shared PDU session. The system provides granularity as to the devices from which data are to be collected.

With regard to using the radio resource as selection information, the selection signal PS may for example be transmitted at a certain time or in a certain time slot from one or more selection sources, e.g. base stations, and responses from all devices within the coverage area of the selection source resulting from this selection signal are accepted by the selection filter 11 to use the shared PDU session sPDU, for example within a certain time interval, starting, for example, at or some time after the transmission of the selection signal.

Sets of devices may be targeted by including the selection information associated with the selection filter 11 in the selection signal PS and receive responses from the set S1 of devices corresponding to the selection information for transmission over the shared PDU session sPDU1.

The selection filter 11 is configurable in accordance with the selection information. It should be appreciated that the selection filter 11 may apply the selection information itself to perform a filter action or may apply filter information associated with or derivable from the selection information used to select the set of devices. A mapping table MT, see FIGS. 2A and FIG. 2B, may be used for translation of selection information embedded in the selection signal PS to selection information applied by the filter for deciding which data to allow on the sPDU session. For example, if the selection information relates to a list of device identifiers and responses from these devices include device identifiers, this information may be used directly to filter data for the shared PDU session sPDU. If the selection information pertains to devices in a certain area covered by selection sources, the system may use selection source identifiers, e.g. base station identifiers, known to cover this area and use a mapping table to map device identifiers to selection source identifiers. This situation is shown in FIG. 2B. In FIG. 2B, the mapping table may translate area information provided by the FCE to selection source identifiers associated with the area. The responses from the devices may be accepted for the sPDU session because the responses arrive within a particular time interval after transmitting the selection information from the appropriate selection sources 12. Alternatively, the devices may transmit location information as selection information. When a device, such as device D4, moves to a location within the area at a later point in time (see arrow) and the selection signal PS is still transmitted or retransmitted, data from the device D4 will be sent over the sPDU session when this sPDU session is still in place.

The selection information may be provided by or be derived from data collection information received from a third party such as an operator of devices, a data collecting entity DCE, or another party, for example filter configuration entity FCE. The selection information serves to target devices, for example set S1 , from which data should be collected, which data may be conveyed using a particular associated sPDU session.

For example, the selection information may include device identifiers of at least one set S1 of devices. Such information may comprise a list of device identifiers. The device identifiers may be provided by a third party, for example filter configuration entity FCE, or may already be accessible in the system, such as in a register, for example a HSS of a 4G telecommunications network or a UDM function in a 5G or 6G telecommunications network. A dedicated register may also be provided in the telecommunications network. This information enables the system 10 to collect data of devices corresponding to the device identifiers of the set S1 and to route the collected data over a shared PDU session sPDU associated with these identified devices. The device identifiers may be included in the selection signal PS so that devices of the set S1 respond, preferably including the device identifier in the response, so that the selection filter can use the device identifier when filtering data from the sPDU session.

The selection information may comprise a device group identifier for at least one set S1 of devices. An operator of the devices may have pre-allocated one or more group identifiers to some or all of the devices from which data may be collected. For example, set S1 of devices in FIG. 1 B of FIG. 2A may have allocated group identifier GRI1 and set S2 of the devices may have been allocated group identifier GRI2. This information enables the system to collect data regarding one or more devices belonging to a particular group and to route the collected data over a shared PDU session for devices associated with the group. In FIG. 2A, only group identifier GRI1 is used so that only devices of this group respond and are admitted to the sPDU session.

The selection information may also comprise a location identifier of devices of at least one set of devices. The location identifier may, for example, point or relate to a certain area wherein data is to be collected from devices in that area. A derivative of a location information identifier includes particular, stationary, selection sources, such as radio base stations, that have a coverage area covering devices from which data is to be collected. This information enables the system to collect data regarding devices in a particular location and to route the collected data over an sPDU session associated with devices at that location. For example, a radio signal PS may be transmitted from base stations in a particular area and all devices in the area may respond, i.e. all devices in the area are associated with a set S of selected devices and may have their data transmitted over the sPDU session as shown in

FIG. 2B.

Yet another example of selection information involves a service type identifier of services of devices relating to, for example, one or more particular applications for which the devices are tailored. This information enables the system to collect data relating to a particular service or services and to route the collected data over a shared PDU session sPDU associated with a particular service of a device.

A still further example involves a data type and/or data characteristic identifier of data for devices from a set of devices. Data may be collected from devices corresponding to the data type and/or data characteristic and may be routed over a shared PDU session associated with the data type or data characteristic. Examples of such data type or characteristic may be temperature, humidity, light level etc.

The system 10 may be configured to process a data collection request to collect data from the set S1 , S2 of devices. It should be appreciated that the data collection request may or may not originate from a data collecting entity DCE participating in the sPDU session as the destination for the data. The data collection request may contain data collection information to configure the selection filter 20 to manage the data transmission over the sPDU session to be established. The data collection request may also cause the system 10 to perform modifying at least one existing sPDU session. Such modification may involve modifying the selection information in the sPDU data structure under the same sPDU identifier. The data collection request may contain data collection information to configure the selection filter 20 to manage the data transmission over the shared PDU session to be modified. This allows a third party, such as a data collection entity DCE or another entity, such as filter configuration entity FCE, to request data collection from a set of devices using data collection information. The system operator may translate that data collection information to the selection information in accordance to which the selection filter is configured and, hence, to target and/or define devices D1-D9 that are allowed to have data transmitted over the sPDU session.

The system 10 is configured to generate a shared PDU session identifier, sPDUJD, associated with the shared PDU session. The sPDUJD can be suitably used in the telecommunications system to identify the shared PDU session. The shared PDU session identifier may be used for establishing or modifying an sPDU session, e.g. to identify a setting for the configurable selection filter 20.

The system 10 may be configured to process a request for a management PDU session, mPDU. This is shown in FIG. 2C The mPDU session may be used for a third party to initialize and/or control the system 10, such as the configurable selection filter 11 , for example from DCE and/or FCE. It should be appreciated, however, that access to the system 10 for third parties may also be arranged for in other manners, for example by providing an application programming interface, API, allowing access for a third party to the system 10 to initialize and/or control the system 10, such as the configurable selection filter 11 .

The shared PDU session identifier, sPDUJD, may, for example, be received in a data collection request over mPDU session from a party to establish or modify the sPDU session, that was previously obtained from the system 10. The request for an mPDU session and the data collection request to establish or modify the shared PDU session may constitute a single request. The combination of both reduces the amount of signaling in the telecommunications network.

The system 10 may contain a control parameter to control data transmission to a data collecting entity, DCE. The control parameter improves control over the use of sPDU sessions for a third party. For example, the control parameter may contain a repetition parameter for controlling repetitions of data transmissions from a set S of devices to the data collecting entity, DCE. The repetition parameter may control repeated data transmission over the established sPDU session. The same shared PDU identifier is used for repeated data transmission over a shared PDU session. Tracking repetitions may be facilitated in this manner

The repetition control parameter may control re-establishment of the sPDU session and/or may control modification of the sPDU session. The repetition parameter may, for example, indicate a number of times data can be transmitted over the established sPDU session, the time intervals wherein data can be transmitted over the sPDU session, the number of times the sPDU session should be established, a time interval between successive establishments of the sPDU session, a number of modifications allowed for the sPDU session etc. The embodiment avoids sending multiple data collection requests and/or repeatedly establishing management PDU sessions and, therefore, reduces communication over the telecommunications network. The same shared PDU identifier is used for (re-)established PDU sessions. (Re-)establishment of the shared PDU session may be quicker in this manner.

To reduce signaling, if the data collecting entity DCE is expected to request data collection from the same set of devices or for the same selection information, instead of sending a data collection request each time, the DCE may send a single data collection request with an additional parameter indicating the periodic nature of the requested data collection procedure, and the time interval between each periodic data collection, and optionally the duration or number of times for which the procedure is repeated. To further reduce signaling on the sPDU session back to the data collecting entity DCE for periodic data collections, the system 10 may send data back only once, a limited number of times, or periodically using a different timer.

The system 10 may be configured to receive the control parameter, such as the repetition parameter, in a data collection request and/or over a mPDU session as shown in FIG. 2C and/or in a combined request.

In one embodiment, the system 10 is configured with a timer to control a time interval during which data received from devices of a set is allowed to be transmitted over the sPDU session when in accordance with the applicable selection filter 20. The timer provides for some flexibility on the timing of acceptance of data in the shared PDU session. This may be beneficial in the case of slowly responding devices, as may be the case for device D4 of set S2 in FIG. 1 B, or when it is not even known whether devices are within reach of the system, such as for device D4 in FIG. 2B. The system gathers the data collected from the devices and conveys the data corresponding to the selection filter over the sPDU session upon expiry of the timer.

Particularly, if more than one message is expected from certain devices, if certain devices are expected to take more time to respond, or if it is not known whether certain devices are still (active) in the network, a timer might be set for associating the received data with a sPDU session related to a selection signal. In that case, the system 10 may be configured to wait until the timer has expired to send the collected data back over the sPDU session.

Devices D1-D9 may be ambient Internet of Things, loT, devices. FIG. 3A is a schematic illustration of an ambient loT device 20 configured to receive and process power signal PS. The ambient loT device 20 comprises a power harvesting part 21 , a processing part 22 and a storage part 23 configured to store, at least, selection information. The ambient loT device 20 also comprises at least one of a communication part 24. The ambient loT device may comprise further parts or functions, such as at least one sensor 25 (or a connector therefore). It should be appreciated that ambient loT device 20 may comprise a plurality of sensors 25 or connectors therefore. Examples of sensors include a location sensor, a temperature sensor, a humidity sensor, a light sensor, a pressure sensor, a motion sensor etc..

The ambient loT device 20 is configured to harvest power from the power signal PS of the selection source 12 to activate at least the processing part 22 and, optionally, the other parts, such as at least one of the storage part 23, communication part 24 and sensor 25. Power supply lines to these parts are indicated by the solid lines in FIG. 3A.

The processing part 22 is configured to determine selection from the received selection information in the power signal PS and the selection information stored in storage part 23 and to perform an action only when its selection is determined. Signal lines for such action(s) are indicated by the dashed-dotted lines in FIG. 3A.

It is appreciated that ambient loT devices 20 may comprise more or fewer parts. Essentially, the ambient loT device 20 is a battery-less device with limited, if any, energy storage capability (one or more capacitors may be included) wherein the energy is provided through the harvesting of radio waves, light, motion, heat or any other power source that could be suitable. The ambient loT device 20 is not capable of storing any significant power provided to it in the power signal PS and uses the supplied power almost immediately in order to complete its desired actions.

FIG. 3B is a flow chart according to a disclosed embodiment for operating the ambient loT device 20. In a first step S1 , all ambient loT devices 20 in the area of the selection source 30 receive a power signal PS comprising, for example, embedded selection information and are powered accordingly. Each ambient loT device 20 receiving sufficient power from the power signal PS verifies in step S2 whether it is selected based on the selection information in the power signal PS. If it is not selected, step S3, no further actions are performed. If it is selected, step S4, the selected ambient loT device 20 may perform an action. The ambient loT device 20 may, for example, respond by communicating with an external network (for example by a simple “I am here” message sending, for example, its identifier or by communicating more elaborate information (for example with data from one or more sensors 25), to the system 10 for data transmission over sPDU associated with the selection information.

Ambient loT device 20 receives a power signal PS, such as a power pulse of duration T. The power pulse contains selection information by modulation of the pulse, as will be described in further detail with reference to FIG. 3C. From the power pulse, power harvesting part 21 collects energy and makes this energy available to other parts of the ambient loT device 20. It should be appreciated that the available energy is generally available for a slightly longer time than the duration T of the power pulse by the slowly decreasing slope for the available energy. The available energy is used for demodulating the power pulse, which may be performed by general processing part 22 or a dedicated demodulator (not shown in FIG. 3A). The demodulation provides the selection information and processing part 22 determines from the selection information whether or not the ambient loT device is selected (step S2 in FIG. 3B). This step may involve comparison of the selection information received in the power pulse with selection information obtained from storage part 23 that is also powered by the power pulse. If selected, processing part 22 determines whether it may transmit its data, if any. In particular, the processing part 22 may start running code from the storage part 23 in the ambient loT device 20 and can determine (e.g. compute) whether it needs to respond and how to respond. It can, for example, collect data from sensors, or from its storage part 23 and start communication with the telecommunications network to use the shared PDU session, sPDU.

In one embodiment, the selection system 10 is configured such that the power pulse has embedded further information relating to the action. The further information may pertain to sending particular data from the storage part 23 of the ambient loT device 20.

The further information may comprise a connection instruction, for example a parameter, for initiating a connection to an external network, such as a telecommunications network, or directly to another device that may or may not forward information to a network. An example of such another device includes another device D1-D9 or a device gateway as will be explained in further detail below with reference to FIGS. 6A-6C. Connecting to the external network may be triggered by a connection instruction in the power pulse or be the result of preprogrammed code executed by the processing part of the ambient loT device 20.

In one example, the ambient loT device 20 is powered by a power pulse having embedded selection information comprising a (group) identification by modulating the power pulse. For example, the power pulse could be amplitude, frequency or phase modulated with the (group)identification. The ambient loT device 20 may respond based on whether the power pulse contains the (group)identification relevant to (them) it or not. The response of the ambient loT device 20 can be a communication action, wherein the response includes, for example “Tag no.xyz present” or for instance comprises additional sensor data resulting in a response like “Tag no.xyz present; temp. 21deg.; humidity 65%”.

The selection information in the power pulse may also comprise or consist of a selection condition. For example, the power pulse may comprise a condition that only ambient loT devices 20 should respond that sense a temperature in a particular temperature range and/or sense a humidity above or below a particular humidity threshold. In such a situation, the ambient loT device 20 may comprise or be connected to a temperature or humidity sensor 25 and read the value directly from the sensor or from memory upon receiving the power signal PS and determine whether or not to respond based on the selection condition. In this case, the selection information also resides in the timing of the power pulse, that is used by the selection filter to put data on the shared PDU session, wherein the data originated from those devices matching the selection condition. In this manner, only devices with particular conditions (such as abnormal values, abnormal behavior, etc) respond, thereby reducing network load.

The power pulse is a transmission or burst of energy that, at least in part, fluctuates in amplitude, frequency and/or phase to represent the selection information and, optionally, further information. It should be appreciated that before receiving the power pulse, the ambient loT devices 20 have virtually no energy and cannot even maintain an idle state. Likewise, after the available energy harvested from the power pulse is consumed, the ambient loT devices are incapable of performing any action, like communication or storing (sensor) data. It should be appreciated that the power pulse duration T may be varied according to the circumstances. For example, a short pulse can be chosen when only selection information needs be transmitted, whereas a longer pulse can be chosen for actions requiring more power from the ambient loT devices 20 or when further information needs to be transmitted with the power pulse.

FIG. 3C is a single power pulse of a selection source 12 of duration T comprising selection information. Before t=0 and after t=T, the power pulse does not exist. The selection information is encoded in the power pulse by amplitude modulation for powering and selecting an ambient loT device. The amplitude of the signal should be sufficiently high to provide sufficient available energy to enable a selected ambient loT device to determine its selection and to perform one or more actions as desired. The amplitude modulation may not only represent the selection information but also further information, including instructions, as described above. In FIG. 3C, the selection information and, optionally, further information, is preceded by a preamble, wherein no information is contained. The preamble may be used to power up the ambient loT device 20 in order to prepare the ambient loT device to read the selection information appropriately.

The Ambient loT devices generate and send data on request (i.e. upon receiving and processing the wake-up power signal PS). The power signal PS for Ambient loT is targeted at a set S of ambient loT devices. The system 10 is capable of identifying the set of devices from which to collect data, and is aware of the associated service or application. The power signal is then received and processed only by the set of loT devices of interest for the service or application by including an identifier which only wakes up the devices in the targeted set, wherein an identifier may be encoded in the signal. In this manner, the paging of the devices to collect data is bound to the routing of the collected data to the destination entity on the appropriate sPDU session. For example, a mapping may be configured in the system 10 to associate each request with the set of devices to collect from, and to map the data received following a selection signal PS with a specific sPDU session to route the data to its destination.

FIG. 4 is a schematic illustration wherein the system 10 is distributed over multiple devices, such as a PDU gateway, PDU GW, and a device gateway DEV GW. The PDU gateway may be configured to manage the shared PDU session using the configurable selection filter 11 (not shown in FIG. 4). The device gateway may be configured to transmit a selection signal PS to the plurality of devices, such as ambient loT devices aloT. The selection information is associated with a radio resource selected for the selection signal and/or selection information in the selection signal. The PDU gateway and device gateway may be included in one component, as will be explained in further detail with reference to FIGS. 6A and 6C. Distributing the system over separate components enables deployment of each of the gateways at an appropriate place. For example, the PDU gateway can be deployed centrally, for example in a core network part of a telecommunications network, whereas the device gateway can be located close to devices from which data may need to be collected. For example, when the devices comprise ambient loT devices, the device gateway may comprise a power source to transmit a power signal PS for wirelessly powering the set of ambient loT devices and can be placed close to the ambient loT devices. Data communication of ambient loT devices from the PDU gateway is performed over an sPDU session, as indicated by the bold thick arrows. Data transmissions of ambient loT devices between the PDU gateway and the device gateway may or may not involve transmission over the sPDU session.

In the embodiment of FIG. 4, the data collecting entity DCE and filter configuration entity FCE are operated by the same party.

In an embodiment, the PDU gateway is configured to act as a relay/endpoint for collecting data from the ambient loT devices and forwarding the data to a data collecting entity DCE on an sPDU session. The device gateway is configured with energy wake-up signal generation capabilities and may be aware of the ambient loT devices within its reach, for example by sending discovery signals, for example on a regular basis. The device gateway may also be configured to advertise to the PDU gateway the capabilities and characteristics of the ambient loT devices that it can reach. In one embodiment, it may be assumed that when an ambient loT device is within reach of multiple device gateways, there is a unique association for each ambient device with only one device gateway.

When the PDU gateway receives a request to collect data for a certain sPDU session, the PDU gateway may select a set of device gateways that can collect the required data based on one or more selectin information items such as location, type of data (i.e. humidity, temperature...), or based on a group identifier or list of ambient loT devices.

The PDU gateway may instruct one or more device gateways to collect data from ambient loT devices matching the selection information items. The device gateways identify the ambient loT devices within reach from which data should be collected, generate the power signal PS and send it to the ambient loT devices. The ambient loT devices determine if they are targeted and may, if targeted, respond with data. The data is received by the device gateway and collected at the PDU gateway. The PDU gateway aggregates the collected data and sends the aggregated data on the sPDU session that was specified in the data collection request from the data collecting entity DCE.

In FIG. 4, the data collection request was transmitted over a management PDU session, mPDU, indicated by the dashed arrows. The management PUD session may be used to request establishment or modification of the sPDU session and/or to provide selection information or information from which selection information can be derived, i.e. the data collection request. The mPDU session may also be used to obtain the identifier, sPDUJD of a shared PDU session in advance of the data collection request.

In one embodiment, the PDU gateway is configured to keep track of the ambient loT devices currently associated with each sPDU session. The PDU gateway may instruct the device gateway(s) to transmit the selection signal PS and collect data from only the set of devices that is currently associated to the sPDU session specified in the data collection request from the data collecting entity DCE. The set of devices aloT may be defined by listing individual loT devices, by specifying the area to collect from, the type of devices, or by setting a number of devices to collect from. The set of loT devices for each PDU session can be dynamically changed by sending a data collection request to the PDU gateway.

As explained with reference to FIG. 1 B, there may be multiple sPDU sessions that are served by a single PDU gateway. This allows to make a distinction between the data collected for different services, or between different types of collected data. Additionally, an ambient loT device can be associated to and provide data to more than one sPDU session. For example, an ambient loT device collecting data in a certain area can provide different kinds of information to multiple services and applications. The ambient loT device would, in this example, receive a wake-up signal when data collection is requested for any of those applications.

The PDU gateway is configured to establish the sPDU sessions. PDU sessions can be created or deleted dynamically by sending a command to the PDU gateway to trigger the creation/deletion of the sPDU session. This can be done over the mPDU session. However, direct access to a device or function in the telecommunications system, such as the Session Management Function, SMF or the Access and Mobility Function, AMF, over an application programming interface, API, is also envisaged.

FIG. 5 shows an embodiment of a message flow to obtain data at the data collecting entity DCE. Dashed arrows show the communications on the mPDU session between the DCE/FCE and the PDU gateway, and solid arrows shows the communication on the sPDU session between the DCE and the ambient loT devices, aloT.

The data consumer sends an sPDU session creation request S1 to the PDU Gateway via the 5G core network, 5GC, for a new sPDU session. Optionally, the request S1 may include selection information, such as a list of devices, a device group identifier GRI, or selection criteria for determining the devices to collect data from forthat sPDU session.

Upon its receipt, the PDU gateway triggers a PDU session creation procedure and returns the sPDUJD of the newly created session to the data collecting entity DCE in step S2. The PDU gateway may keep in memory the mapping between the sPDUJD, the data collecting entity DCE, and the selection information, such as the list of ambient loT devices, group identifier GRI or selection criteria provided in the PDU session creation request of step S1 .

When the data consumer sends a data collection request in step S3 for a shared PDU session, it can provide selection information that is different from the selection information provided in step S1 . If the data collection request in step S3 does not contain selection information, the PDU gateway can apply the selection information obtained in step S1 .

The PDU gateway is aware of the ambient loT devices in the network and the corresponding device gateways. The PDU gateway uses the selection information to determine the set S of devices to collect data from and triggers the associated device gateway(s) in step S4 to send a power signal PS including selection information to the devices to obtain data in step S5. Step S4 may involve using Namf_Communication_N1 N2MessageTransfer service which allows 5G core network functions to transfer downlink N1/N2 messages to the UE or the Access Network via the AMF. It is noted that in step S4, the PDU-GW may add an identifier that can be used by the device gateway in a later step.

In an alternative, when the PDU gateway is not aware of the ambient loT devices and the corresponding device gateways, the device gateway(s) periodically advertise the capabilities of the ambient loT devices within their reach. The PDU gateway may identify the device gateway(s) that can reach ambient loT devices of interest. The optional discovery process is shown by the dashed box in FIG. 5. In that case, the PDU gateway may, for example, send a request to collect data with the selection information to each device, and each device gateway may determine the set of devices from which to collect data from.

Once the PDU gateway receives all of the collected data from the device gateway(s) in step S6. Step S6 may involve two separate steps in case the device gateway needs to process the response from the devices aloT. For example, the device gateway may use the identifier obtained in step S4 to inform the PDU gateway to which request the device gateway is responding. Alternatively, the steps S4 and S6 may include the sPDU session identifier sPDUJD for the scenario where the device gateway is aware of the PDU sessions.

The PDU gateway sends the data to the data collecting entity DCE over the sPDU session established for sPDUJD through the 5G Core step S7.

The data collecting entity DCE can also invoke a shared PDU session modification procedure when updating the list of device identifiers, group ID, or other selection information identifying a set of ambient loT devices that are associated with the shared PDU session.

FIGS. 6A-6C are schematic illustrations of different implementations of the system 10 with respect to the telecommunications network 30. In these implementations, the system comprises a PDU gateway and a device gateway.

The inventors have envisaged various modes of operation for such implementations, both for the PDU gateway and for the device gateway.

For example, the PDU gateway may be configured to process mapping information of device gateways and devices, such as ambient loT devices, in a coverage area of the device gateways. This embodiment allows the PDU gateway, when having received a data collection request from a DCE/FCE, to only send a selection signal to one or more device gateways to collect the data, based on, e.g. data collection information obtained from the DCE/FCE. The device gateway or device gateways do not need to know the ambient loT devices from which data should be collected. Also, a data collecting entity DCE/FCE does not need to know which device gateway covers which of the devices. In this embodiment, for example, ambient loT devices only need a power signal PS without further selection information to be included in the power signal to collect data from all devices receiving the power signal PS.

Another mode of operation involves the PDU gateway being configured to receive device information from the device gateway to enable selection of device gateways to collect data from the devices in accordance with the selection filter. This enables the PDU gateway to obtain information regarding mapping device gateways to ambient loT devices reachable by the respective device gateways. The device information may be obtained on request from the PDU gateway or by receiving advertising messages from the device gateway having collected this information from devices within reach of the respective device gateways. The device gateway may be configured to advertise device information to the PDU gateway of devices within a wireless coverage area of the device gateway. This embodiment may assist the PDU gateway to acquire information on the devices associated with each device gateway for subsequent collection of data.

Also, the PDU gateway may be configured to broadcast the selection signal to a plurality of device gateways. This embodiment is beneficial when the PDU gateway has no or only limited information on the ambient loT devices within reach of the device gateways. The device gateways may have this information stored locally and may be triggered by the broadcast selection signal from the PDU gateway to collect data from the devices within their reach and forward the data to the PDU gateway, when received, immediately or afterwards. The device gateway is configured to gather device information of devices within a wireless coverage area of the device gateway. To that end, the device gateway may optionally send discovery requests. The embodiment assists the device gateway to obtain the device information for either local use by applying the gathered device information to select the set of devices from which data should be collected (for example, when receiving the broadcast trigger to collect data from the PDU gateway) or to forward to the PDU gateway (e.g. to populate a mapping table MT in the PDU gateway).

In a different mode, the PDU gateway is configured to instruct a network node of the telecommunications network to select the set of devices to which the selection signal should be sent via the device gateway. In this embodiment, the system may comprise a further network node, e.g. a system having access to a register with device information on devices within reach of device gateways, so that individual devices or groups of devices are known within the system.

Also, the device gateway may be configured to select a subset of the set of devices and join a shared PDU session of the PDU gateway for data transmission of the subset of devices over the joined shared PDU session. This embodiment is beneficial when the device gateway is aware of the shared PDU session and of the setting of the selection filter so that it can apply the selection filter. When the device gateway is aware of the PDU session, it may send the data back to the data collecting entity DCE on the sPDU directly, without going through the PDU GW. This would have the advantage of reducing the load on the PDU GW.

In one embodiment, shown in FIG. 6A, both the PDU gateway(s) and the device gateway(s) are implemented in the telecommunications network 30. For example, the PDU gateway may be a core network node in the telecommunications network and the device gateway is contained in a base station of the telecommunications network. The PDU gateway may be implemented in an SMF of a 5G telecommunications network, for example. The embodiment is beneficial for using existing network infrastructure and allows telecom operators to provide a service in a controlled and efficient manner. FIG. 7 A is a schematic illustration of implementation in a 5G telecommunications network.

In particular, messages from the device gateway to the SMF can be transmitted via the access and mobility function, AMF, and its N1 N2 signaling transfer capabilities, where the AMF selects the appropriate SMF using 3GPP standardized procedures. The messages can also be sent directly to the SMF through direct or API access. In that case, the SMF uses "Ambient loT serving areas" (based on the area that the requestor application function, AF, can give to collect the data from, this can be done by the AF sending it directly to the SMF, or a mapping can be done by the NEF if the AF is going through the NEF) or some other selection criteria to select AMF.

In this embodiment, the sPDU session establishment process as defined in clause 4.3.2.2 in TS 23.502 may be enhanced to include a group identifier or other selection information to identify the ambient loT devices to collect data from instead of a UE identifier. To establish or update the sPDU session, the data collection entity DCE sends the shared PDU creation request to the SMF directly or through the network exposure function, NEF, to establish the sPDU session for collecting data from ambient loT devices, and the PDU modification request to update the selection information for selecting the target ambient loT devices. In addition to the parameters for sPDU session creation, the request includes selection information, such as a list of the IDs of the ambient loT devices to collect data from, a group ID referring to a set of ambient loT devices, or other selection information to determine the set of devices.

After receiving the shared PDU establishment or modification request, the SMF then triggers the sPDU session creation or modification procedure for those selected ambient loT devices and/or the associated device gateways. The PDU gateway may save the mapping between the sPDU identifier, sPDUJD, the data collecting entity and the selection information, such as the list of ambient loT device identifiers, group ID or other selection information provided in, for example, the PDU session creation request. This mapping is used for each data collection request to bind the data collection request with paging of the ambient loT devices with the routing of the collected data to the destination on the sPDU session.

To trigger data collection, the data collecting entity DCE sends a request to the SMF by indicating the sPDUJD and, optionally, selection information. On receiving the data collection request, the SMF then communicates with the AMF to identify the device gateway(s) (i.e. NG-RAN nodes), and instructs them to collect data to send it back on the sPDU session established between the PDU gateway and DCE. The data collection request can include a list of ambient loT devices to collect data from, or other selection information area, device characteristics or data type. Upon receiving the data collection request from the SMF, the NG-RAN nodes may identify the set of ambient loT devices to collect data from by the selection information with the list of ambient loT devices in its serving area if the request from the PDU gateway included such selection information. The NG-RAN then sends the wake-up signal to the ambient loT devices and collects the data received from the selected devices. Subsequently, the NG-RAN either sends back the collected data directly to the data collecting entity DCE on the sPDU session or sends it to the SMF through the AMF using for example the procedure for Mobile Originated Data Transport in Control Plane CloT 5GS. Forthe second option, the SMF collects all data received from the NG-RANs and sends it back to the data collecting entity DCE on the sPDU session through the UPF over the N3 interface or the NEF.

As mentioned above, to reduce the number of exchanged messages, the PDU session creation/update and data collection procedures can be coupled and triggered by a single message. In one embodiment, depicted in FIG. 6B, only the PDU gateway is located in the telecommunications network, whereas the device gateway is wirelessly connected to the network via a base station BS. The PDU gateway may be a core network node in the telecommunications network and the device gateway may be a device registered and wirelessly connectable to the telecommunications network 30. The registration of the device gateway in the network enables the network to directly identify and target the set of devices to collect data from and send the selection signal to only the relevant device gateways.

In particular, the device gateways may be separate devices that are registered in the telecommunications network 30 as UEs and advertise the characteristics to the SMF and the SMF selects the device gateway(s) accordingly. This may be beneficial in that the device gateway(s) may keep track of the ambient loT devices instead of the telecommunications network. The device gateway(s) may detect the ambient loT devices that are present in their coverage area by sending periodic discovery signals. The discovery signal to detect the ambient loT devices may be different from the selection signals used to collect data from the ambient loT devices.

Another scenario is where the device gateways do not advertise the ambient loT devices within their reach to reduce signaling. In that case, the PDU gateway may broadcast the selection signal to all device gateways and then each device gateway may select a list of ambient loT devices to collect data from.

Alternatively, the device gateway may not keep a record of the ambient loT devices within their coverage area to further reduce signaling. In that case, the PDU gateway may broadcast the selection signal to all device gateways. Subsequently, each device gateway may then be configured to send the discovery signal to detect the ambient loT devices that are associated with the sPDU session for this data collection request.

In yet another scenario, the ambient loT devices are registered and known in the telecommunications network 30, and the SMF may directly instruct the AMF to select the set of ambient loT devices to collect data from and identify the set of associated device gateways. Then, through the AMF, the SMF sends a selection signal to trigger the selected ambient loT devices. This allows a more targeted approach where the set of devices to collect data from is directly known by the telecommunications network 30. To track presence of the ambient loT devices in the network 30, the network instructs the device gateways to send periodic discovery signals and, if there is no response from an ambient loT device, the network considers that the device has left the network and is not associated to the sPDU session anymore. This also helps detecting the arrival of new devices and track their mobility between device gateways.

In one embodiment, shown in FIG. 6C, the PDU gateway is contained in a device registered in and wirelessly connectable to the telecommunications network. The device may be a wearable device, such as a User Equipment, UE. Optionally, the device also comprises the device gateway. FIG. 7B is a schematic illustration of this implementation for a 5G telecommunications network.

Particularly, the PDU gateway and device gateway can be configured as a UE with relay capabilities. The UE establishes PDU sessions with the telecommunications network 30 upon receiving data collection requests and send a selection signal to ambient loT devices using the device gateway to collect the data. The UE can also be a/the device configured to send the power signal PS and be aware of its surrounding ambient loT devices. The UE may, for example, use a mechanism for device-to-device, D2D, communication such as ProSe or another lightweight communication scheme) as described in a previous embodiment.

FIG. 7C is a schematic illustration of an implementation wherein the load of the PDU gateway (here, the SMF) can be reduced, the PDU gateway may be configured to only establish and/or modify a shared PDU session between a device gateway and a data collecting entity. The PDU gateway transmits a shared PDU session identifier to the device gateway. The device gateway is configured to direct the data transmissions from responding devices over a shared PDU session established between the device gateway and a data collecting entity over the telecommunications network. The selection filter configured with the selection information for responses from devices is then applied in the device gateway. In FIG. 7C, the NG-RAN, as device gateway may use the N3 interface for data transmission for the sPDU would be between the NG-RANs and the DCE. In that case, the NG-RAN may use a shared PDU session ID, sPDUJD, that may be obtained from the PDU gateway previously (e.g. in step S4 of FIG. 5). In other words, device gateways may be configured to send the data to the DCE over the shared PDU session directly through the 5GC, such as over the UPF.

FIG. 8 depicts a block diagram illustrating an exemplary processing system according to a disclosed embodiment, e.g. a wireless transmission device 20, 40 or a authentication system AUT as described above for use in a system 100. As shown in FIG. 8, the processing system 80 may include at least one processor 81 coupled to memory elements 82 through a system bus 83. As such, the processing system may store program code within memory elements 82. Further, the processor 81 may execute the program code accessed from the memory elements 82 via a system bus 83. In one aspect, the processing system may be implemented as a computer system that is suitable for storing and/or executing program code. It should be appreciated, however, that the processing system 80 may be implemented in the form of any system including a processor and a memory that is capable of performing the functions described within this specification.

The memory elements 82 may include one or more physical memory devices such as, for example, local memory 84 and one or more bulk storage devices 85. The local memory may refer to random access memory or other non-persistent memory device(s) generally used during actual execution of the program code. A bulk storage device may be implemented as a hard drive or other persistent data storage device. The processing system 80 may also include one or more cache memories (not shown) that provide temporary storage of at least some program code in order to reduce the number of times program code must be retrieved from the bulk storage device 85 during execution.

Input/output (I/O) devices depicted as an input device 86 and an output device 87 optionally can be coupled to the processing system. Examples of input devices may include, but are not limited to, a space access keyboard, a pointing device such as a mouse, or the like. Examples of output devices may include, but are not limited to, a monitor or a display, speakers, or the like. Input and/or output devices may be coupled to the processing system either directly or through intervening I/O controllers. In an embodiment, the input and the output devices may be implemented as a combined input/output device (illustrated in FIG. 8 with a dashed line surrounding the input device 86 and the output device 87). An example of such a combined device is a touch sensitive display, also sometimes referred to as a “touch screen display” or simply “touch screen” that may be provided with the UE. In such an embodiment, input to the device may be provided by a movement of a physical object, such as e.g. a stylus or a finger of a person, on or near the touch screen display.

A network adapter 88 may also be coupled to the processing system to enable it to become coupled to other systems, computer systems, remote network devices, and/or remote storage devices through intervening private or public networks. The network adapter may comprise a data receiver for receiving data that is transmitted by said systems, devices and/or networks to the processing system 80, and a data transmitter for transmitting data from the processing system 80 to said systems, devices and/or networks. Modems, cable modems, and Ethernet cards are examples of different types of network adapter that may be used with the processing system 80.

As pictured in FIG. 8, the memory elements 82 may store an application 89. In various embodiments, the application 89 may be stored in the local memory 84, the one or more bulk storage devices 85, or apart from the local memory and the bulk storage devices. It should be appreciated that the processing system 80 may further execute an operating system (not shown in FIG. 8) that can facilitate execution of the application 89. The application 89, being implemented in the form of executable program code, can be executed by the processing system 80, e.g., by the processor 81 . Responsive to executing the application, the processing system 80 may be configured to perform one or more operations or method steps described herein.

In one aspect of the present invention, one or more components of the system 10. as disclosed herein may represent processing system 80 as described herein.

Various embodiments of the invention may be implemented as a program product for use with a computer system, where the program(s) of the program product define functions of the embodiments (including the methods described herein). In one embodiment, the program(s) can be contained on a variety of non-transitory computer-readable storage media, where, as used herein, the expression “non-transitory computer readable storage media” comprises all computer-readable media, with the sole exception being a transitory, propagating signal. In another embodiment, the program(s) can be contained on a variety of transitory computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, ROM chips or any type of solid-state non-volatile semiconductor memory) on which information is permanently stored; and (ii) writable storage media (e.g., flash memory, floppy disks within a diskette drive or hard-disk drive or any type of solid-state random-access semiconductor memory) on which alterable information is stored. The computer program may be run on the processor 81 described herein.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. 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" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of embodiments of the present invention has been presented for purposes of illustration but is not intended to be exhaustive or limited to the implementations in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the claims. The embodiments were chosen and described in order to best explain the principles and some practical applications of the present invention, and to enable others of ordinary skill in the art to understand the present invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1 . A system configured to manage data transmission in or with a telecommunications network using a shared protocol data unit, PDU, session, to convey data from a set of devices, wherein the system is configured to apply a selection filter to select the set of devices from a plurality of devices, wherein the selection filter is configurable in accordance with selection information applicable to the set of devices, and wherein the system is configured to manage the data transmission over the shared PDU session for the selected set of devices in accordance with the selection information of the configurable selection filter.

2. The system according to claim 1 , wherein the system comprises at least one selection source configured to transmit a selection signal to the plurality of devices, wherein the selection information relates to at least one of timing of transmission of the selection signal and selection information in the selection signal.

3. The system according to claim 2, wherein the selection source comprises a power source configured to transmit a power signal for wirelessly powering the set of devices, wherein the selection information involves at least one of a selected radio resource for the power signal, such as timing of the transmission of the power signal, and selection information embedded in the power signal, to select the set of devices to provide the data to the system.

4. The system according to one or more of the preceding claims, wherein the system is configured to process a data collection request to collect data from the set of devices, such that the request causes the system to perform at least one of: establish the shared PDU session, wherein the data collection request contains data collection information to configure the selection filter to manage the data transmission over the shared PDU session to be established; and modify the shared PDU session, wherein the data collection request contains data collection information to configure or reconfigure the selection filter to manage the data transmission over the shared PDU session to be modified,

5. The system according to one or more of the preceding claims, wherein the system is configured to generate a shared PDU session identifier associated with the shared PDU session and wherein the system is, optionally, configured to process a request for a management PDU session, wherein the system is further configured to provide the shared PDU session identifier for transmission over the management PDU session, wherein the shared PDU session identifier is, optionally, received in the data collection request to establish or modify the shared PDU session according to claim 43.

6. The system according to claims 4 and 5, wherein the request for a management PDU session and the data collection request to establish or modify the shared PDU session constitute a single request.

7. The system according to one or more of the preceding claims, wherein the system contains a control parameter to control data transmission to a data collecting entity, wherein the control parameter, optionally contains a repetition parameter controlling repetition of data transmissions from a set of devices to the data collecting entity, the repetition parameter controlling at least one of:

- repeated data transmission over the established shared PDU session;

- re-establishment of the shared PDU session; and

- modification of the shared PDU session wherein the system is, optionally, configured to receive the control parameter in a data collection request according to claim 4 or a request for a management PDU session according to claim 5.

8. The system according to one or more of the preceding claims, wherein the system is configured with a timer to control a time interval during which data received from devices is transmitted over the shared PDU session when in accordance with the applicable selection filter.

9. The system according to one or more of the preceding claims, wherein the system is configured to use a plurality of shared PDU sessions for data transmission and wherein the selection filter is configured in accordance with different sets of devices and/or services thereof to manage data transmission such that data is sent over a shared PDU session in accordance with the applicable selection information.

10. The system according to one or more of the preceding claims, wherein the selection filter is configurable with at least one or more of the following selection information: device identifier(s) of at least one set of devices device group identifier of at least one set of devices location identifier of devices of at least one set of devices service type identifier of services of devices of at least one set of devices data type identifier of data from devices of at least one set of devices data characteristic(s) identifier(s) of data from devices of at least one set of devices

11 . The system according to one or more of the preceding claims, wherein the system comprises at least a PDU gateway and a device gateway, wherein the PDU gateway is configured to manage the shared PDU session using the configurable selection filter and wherein the device gateway is configured to transmit a selection signal to the plurality of devices, wherein the selection information relates to at least one of timing of transmission of the selection signal and selection information in the selection signal., such as a power source configured to transmit a power signal for wirelessly powering the set of devices, wherein the power signal has embedded selection information to select the set of devices to provide the data to the PDU gateway.

12. The system according to claim 11 , wherein the PDU gateway is configured to perform at least one of the following: process mapping information of device gateways and devices in a coverage area of the respective device gateways; receive device information from the device gateway to enable selection of device gateways to collect data from the devices in accordance with the selection information; broadcast the selection signal to a plurality of device gateways; instruct a core network node of the telecommunications network to select the set of devices to which the selection signal should be sent via the device gateway transmit a shared PDU session identifier to the device gateway.

13. The system according to one or more of the preceding claims, wherein the system comprises at least a PDU gateway and a device gateway, and wherein the device gateway is configured to perform at least one of the following: advertise device information to the PDU gateway of devices in a wireless coverage area of the device gateway; gather device information by receiving responses from devices within a wireless coverage area triggered by a discovery request, and, optionally, applying the gathered device information to select the set of devices; and select a subset of the set of devices and join a shared PDU session of the PDU gateway for data transmission of the subset over the joined shared PDU session direct the data transmission over a shared PDU session established between the device gateway and a data collecting entity over the telecommunications network.

14. The system according to one or more of the preceding claims 11-13, wherein the PDU gateway is a core network node in the telecommunications network and wherein the device gateway is contained in at least one of: a base station of the telecommunications network; and - a device registered and wirelessly connectable to the telecommunications network.

15. The system according to one or more of the claims 11-13, wherein the PDU gateway is contained in a device registered in and wirelessly connectable to the telecommunications network, and wherein, optionally, the device also comprises the device gateway.

16. A shared PDU session data structure for exchanging data of a set of devices from a plurality of devices, wherein the shared PDU session data structure comprises a shared PDU session identifier and information identifying the selected set of devices, wherein the selected set of devices comprises at least two devices.