WO2020199129A9

WO2020199129A9 - Mechanism for transmitting background data in uplink

Info

Publication number: WO2020199129A9
Application number: PCT/CN2019/081038
Authority: WO
Inventors: Yang Shen; Weixing Wang
Original assignee: Nokia Shanghai Bell Co., Ltd.; Nokia Solutions And Networks Oy; Nokia Technologies Oy
Priority date: 2019-04-02
Filing date: 2019-04-02
Publication date: 2021-10-07
Also published as: CN113678490A; WO2020199129A1

Abstract

Embodiments of the present disclosure relate to mechanism for transmitting background data in uplink. According to embodiments of the present disclosure, if the server device initiates the process of Background Data transfer negotiation, the server device transmits the request for transmitting information for transmitting background data in uplink to the terminal device. The controlling network device transmits information for transmitting background data in uplink to the terminal device. In this way, the transmission of background in uplink is managed and is more efficient.

Description

MECHANISM FOR TRANSMITTING BACKGROUND DATA IN UPLINK

FIELD

Embodiments of the present disclosure generally relate to the field of communications and in particular, to a method, device, apparatus and computer readable storage medium for transmitting background data in uplink.

BACKGROUND

In recent communication networks, volume of data has dramatically increased. For example, in the fifth generation (5G) communication systems, capacity of available radio access node (RAN) is much greater than the capacity in the fourth generation (4G) communication systems. Some data, for example background data, may not be necessary to be transmitted immediately. The background data transfer is expected to be used to utilize both the wireless resources and core network resources in an efficient manner.

SUMMARY

Generally, embodiments of the present disclosure relate to a method for transmitting background data in uplink and the corresponding communication devices.

In a first aspect, there is provided a controlling network device. The controlling network device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the controlling network device to receive, at the controlling network device, a request from a server device. The request comprises identity information of a terminal device and an index associated with information for data transmission. The controlling network device is also caused to retrieve the information for data transmission based on the index. The controlling network device is further caused to generate further information for transmitting background data in uplink based on the information for data transmission. The controlling network device is yet caused to transmit the further information to the terminal device.

In a second aspect, there is provided a server device. The server device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the server device to determine that a terminal device is to transmit data in uplink. The server device is also caused to transmit, to a controlling network device and at the server device, a request comprising identity information of a terminal device and an index associated with information for data transmission. The network device is further caused to receive the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.

In a third aspect, there is provided a terminal device. The terminal device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to receive information for transmitting background data in uplink from a network device. The terminal device is further caused to transmit the background data in uplink to a server device based on the information.

In a fourth aspect, there is provided a method. The method comprises receiving, at a controlling network device, a request from a server device. The request comprises identity information of a terminal device and an index associated with information for data transmission. The method also comprises retrieving the information for data transmission based on the index. The method further comprises generating further information for transmitting background data in uplink based on the information for data transmission. The method yet comprises transmitting the further information to the terminal device.

In a fifth aspect, there is provided a method. The method comprises determining that a terminal device is to transmit data in uplink. The method also comprises transmitting, to a controlling network device and at a server device, a request comprising identity information of a terminal device and an index associated with information for data transmission. The method also comprises receiving the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.

In a sixth aspect, there is provided a method. The method comprises receiving, at a terminal device, information for transmitting background data in uplink from a controlling network device. The method further comprises transmitting the background data in uplink to a server device based on the information.

In a seventh aspect, there is provided an apparatus comprising means for receiving, at a controlling network device, a request from a server device, the request comprising identity information of a terminal device and an index associated with information for data transmission; means for retrieving the information for data transmission based on the index; means for generating further information for transmitting background data in uplink based on the information for data transmission; and means for transmitting the further information to the terminal device.

In an eighth aspect, there is provided an apparatus comprising means for determining that a terminal device is to transmit data in uplink; means for transmitting, to a controlling network device and at a server device, a request comprising identity information of a terminal device and an index associated with information for data transmission; and means for receiving the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.

In a ninth aspect, there is provided an apparatus comprising means for receiving, at a terminal device, information for transmitting background data in uplink from a controlling network device; and means for transmitting the background data in uplink to a server device based on the information.

In a tenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above fourth to sixth aspects.

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

Fig. 1 illustrates a schematic diagram of a communication system according to embodiments of the present disclosure;

Fig. 2 illustrates a schematic diagram of interactions among devices according to embodiments of the present disclosure;

Fig. 3 illustrates a flow chart of a method implemented at a controlling network device according to embodiments of the present disclosure;

Fig. 4 illustrates a flow chart of a method implemented at a server device according to embodiments of the present disclosure;

Fig. 5 illustrates a flow chart of a method implemented at a terminal device according to embodiments of the present disclosure;

Fig. 6 illustrates a schematic diagram of a device according to embodiments of the present disclosure; and

Fig. 7 shows a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

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

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

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

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

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

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a user equipment and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “network device” refers to a node in a communication network via which a user equipment accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

As mentioned above, the background data may not be necessary to be transmitted immediately. The core network in third generation partnership project (3GPP) should support a 3rd party service provider request for background data transfer for a set of terminal devices that are served by the 3rd party service provider.

Additionally, the 3rd party application server should be able to indicate to the 3GPP System when the background data transfer (a) exceeds the agreed maximum data volume or (b) continues beyond the agreed time window or (c) happens outside the agreed areas.

The 3GPP Core Network should be able to inform the 3rd party service provider in one coordinated response, based on locally available information (e.g. congestion level) over the geographic area, about: one or more recommended time windows for the data transfer and for each time window the maximum aggregated bitrate for the set of UEs in the geographical area indicated by the 3rd party service provider.

Further, the 3GPP Core Network should be able to inform the 3rd party service provider about the charging policy that will be applied to the 3rd party service provider if the data are transferred within the recommended time window and if transmission rates stay below the limits of the respective maximum aggregated bitrate.

The aim of providing the time window is to favor transfer of more traffic during non-busy hours and reason for providing the maximum aggregate bitrate is to spread out traffic during that time. The aim of multiple time windows is to allow the 3rd party provider to choose one appropriate time window based on its preference like the expected charging regime and bitrate.

In conventional technologies, the convention UE Route Selection Policy (URSP) framework may be used for delivery of policy information related to background data transfer from 5G core network to the terminal device. The policy information content may define time window and location criteria that need to be met for background data transfer.

There is a single dedicated protocol data unit (PDU) session that is used for background data transfer which is established and released based on the background data transfer policies. In conventional solutions, the network device (for example, an application server) may connect with the policy control function (PCF) via the network exposure function (NEF) to request a time window and related conditions for future background data transfer.

The application server request may contain an automatic site positioning (ASP) identifier, the volume of data to be transferred per terminal device, the expected amount of terminal devices, the desired time window and optionally, network area information. The application server provides as Network Area Information either a geographical area, or an area of interest that includes a list of time advances (TAs) or list of NG-RAN nodes and/or a list of cell identifiers. When the application server provides a geographical area, then the NEF maps it based on local configuration into of a short list of TAs and/or NG-RAN nodes and/or cells identifiers that is provided to the PCF.

The PCF may first retrieve all existing transfer policies stored for any ASP from the UDR. Afterwards, the PCF shall determine, based on the information provided by the AF and other available information (e.g. network policy, level information in a S-NSSAI and load status estimation for the required time window, network area, and existing transfer policies) one or more transfer policies. The PCF may be configured to map the ASP identifier into a target DNN and slicing information.

In some embodiments, a transfer policy may comprise a recommended time window for the background data transfer, a reference to a charging rate for this time window and optionally a maximum aggregated bitrate (indicating that the charging according to the referenced charging rate is only applicable for the aggregated traffic of all involved UEs that stays below this value) .

Finally, the PCF may provide a list of candidate transfer policies or the selected transfer policy to the application server via NEF together with the Background Data Transfer reference ID. If the application server receives more than one transfer policy, the application server may select one of them and inform the PCF about the selected transfer policy.

The selected transfer policy is finally stored by the PCF in the unified data repository (UDR) together with the Background Data Transfer reference ID and the network area information. The same or a different PCF MAY retrieve this transfer policy and the corresponding network area information from the UDR and take them into account for future decisions about transfer policies for background data related to the same or other ASPs.

At the time the background data transfer is about to start, the AF provides for each UE the Background Data Transfer reference ID together with the AF session information to the PCF (via the N5 interface) . The PCF retrieves the corresponding transfer policy from the UDR and derives the PCC rules for the background data transfer according to this transfer policy. However, the current background data transfer policy only comprises the attributes for downlink data transfer.

According to embodiments of the present disclosure, if the server device initiates the process of Background Data transfer negotiation, the server device transmits the request for transmitting information for transmitting background data in uplink to the terminal device. The controlling network device transmits information for transmitting background data in uplink to the terminal device. In this way, the transmission of background in uplink is managed and is more efficient.

Fig. 1 illustrates a schematic diagram of a communication system 100 in which embodiments of the present disclosure can be implemented. The communication system 400, which is a part of a communication network, comprises terminal devices 110-1, 110-2, ..., 110-N (collectively referred to as “terminal device (s) 110” where N is an integer number) . The communication system 100 comprises one or more network devices, for example, a network device 120 (also referred to as “the controlling network device 120” ) and a network device 130 (also referred to as “the server device 130” ) . It should be understood that the communication system 100 may also comprise other elements which are omitted for the purpose of clarity. It is to be understood that the numbers of terminal devices and network devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations. The server device 130 and the controlling network device 120 may communicate with the terminal devices 110.

It is to be understood that the number of network devices and terminal devices is only for the purpose of illustration without suggesting any limitations. The system 100 may include any suitable number of network devices and terminal devices adapted for implementing embodiments of the present disclosure.

Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.

Fig. 2 illustrates a schematic diagram of interactions 200 in accordance with embodiments of the present disclosure. The interactions 200 may be implemented at any suitable devices. Only for the purpose of illustrations, the interactions 200 are described to be implemented at the terminal device 110-1, the controlling network device 120 and the server device 130.

In some embodiments, the server device 130 may transmit 205 a request to generate the information for data transmission. For example, the server device 130 may invoke the Nnef_BDTPNegotiation_Create service. In some embodiments, the request may comprise one or more of: an ASP identifier, the amount of data to be transferred per terminal device, the expected number of terminal devices, the desired time window, network area information, an identity of a group of terminal devices. In some embodiments, the server device 130 may provide as network area information either a geographical area, or an area of interest that includes a list of TAs or list of NG-RAN nodes and/or a list of cell identifiers. The request may also comprise the trigger condition for transmitting the further information to the terminal device. For example, the trigger condition may indicate that the further information needs to be transmitted to the terminal device if the terminal device registers with the network.

The controlling network device 120 may generate 210 the information for data transmission. For example, based on the request, the controlling network device 120 may invoke the Npcf_BDTPolicyControl_Create service to authorize the creation of the policy regarding the background data transfer. In some embodiments, the PCF may determine the information for data transmission based on the request. In some embodiments, the information may also be determined based on other information, for example, network policy, level information in a Single Network Slice Selection Assistance Information (S-NSSAI) and load status estimation for the required time window, network area, and current transfer policies. The controlling network device 120 may be configured to map the ASP identifier into a target DNN and slicing information, that is, S-NSSAI.

In some embodiments, the controlling network device 120 may generate the candidate lists of information and transmit the candidate list of information to the server device 130. If the server device 130 receives more than candidate lists of information, the server device 130 may select one of them and inform the PCF about the selected list of information. The controlling network device 120 may also generate the index (for example, Background Data Transfer Reference ID) of the information and transmit 215 the index to the server device 130.

The controlling network device 120 may store the information with the index. For example, the information with the index may be stored in the UDR. The same or a different PCF may retrieve this information and the corresponding network area information from the UDR.

In some embodiments, the server device 130 may transmit another request to update the information. The other request may comprise an ASP identifier, the information and the index of the information. Alternatively, the other request may also comprise an indication for delivering the updated information to the terminal device 110-1.

The server device 130 determines that the terminal device 110-1 is to transmit the background data in uplink. In some embodiments, if the terminal device 110-1 initiates to transmit the background data in uplink, the server device 130 determines whether the terminal device 110-1 is allowed to transmit the background data in uplink. In some embodiments, if the terminal device 110-1 starts to register with the server device 130, the server device 130 determines whether the terminal device 110-1 is allowed to transmit the background data in uplink.

The server device 130 transmits 225 the request for the information for data transmission. For example, if the server device 130 determines that the terminal device 110-1 is allowed to transmit the background data in uplink, the server device 130 may transmit the request to the controlling network device 120 for the information for data transmission. Alternatively, if the terminal device 110-1 starts to register with the server device 130, the server device 130 may transmit the request to the controlling network device 120 for the information for data transmission. The server device 130 may transmit the index together with the AF session information to the controlling network device 120 via an N5 interface.

The request comprises identity information of the terminal device 110-1. For example, the request may comprise an identity of the terminal device 110-1. Alternatively, the request may comprise an identity of a group of terminal devices to which the terminal device 110-1 belongs. In some embodiments, the request may also comprise identity of application and/or identity of operation system (OS) .

The request also comprises the index of the information for data transmission. The request may also comprise one or more of: a time window in which the terminal device 110-1 is allowed to transmit the background data in unlink, an amount of background data allowed to be transmitted by the terminal device in uplink or information of network area in which the terminal device is allowed to transmit the background data in uplink.

The controlling network device 120 retrieves 230 the information for data transmission based on the index. For example, the controlling network device 120 may retrieve the all information stored in the UDR to obtain the information. The controlling network device 120 generates 235 the further information for transmitting data in uplink. The further information may comprise at least one of: volume of data to be transferred per terminal device for uplink, desired time window for uplink or network area information for uplink.

The controlling network device 120 transmits the further information to the terminal device 110-1. In some embodiments, the controlling network device 120 may generate information of route selection and traffic transfer on a selected route for the terminal device 110-1, for example, the URSP. The controlling network device 120 may transmit the further information together with the URSP. The controlling network device 120 may combine the URSP with the further information. Table 1 below shows an example of extended URSP rule. It should be noted that Table 1 is only an example, not limitation.

Table 1

Table 2 below shows an example of the further information. It should be noted that Table 2 is only an example, not limitation.

Table 2

In this way, since the further information is only applied to the session of the server device 130 (for example, the AF session) that can be identified by any of the traffic descriptor used for URSP, the URSP and the further information may share the same traffic description, then extending URSP to include the further information can reduce the size of the UE policy when they are provided together, thus the N1 signaling can be reduced. For application traffic subject to the further information, quite likely the URSP and the further information policy are provided together, for example, when the server device 130 is about to start the traffic transfer, it triggers the controlling network device 120 to deliver the required policy.

In addition, there is a single dedicated PDU session that is used for transmitting background data in uplink which is established and released based on the further information. It means that when associating applications to PDU Sessions, it needs to consider both URSP and the further information and it is easier for the terminal device to perform PDU session association.

In some embodiments, the controlling network device 120 may generate a separate table for the further information. The further information and the URSP may be transmitted separately. In this way, the further information may be more backward compatible to the convention communication system. Table 3 below shows an example of the further information. It should be noted that Table 3 is only an example, not limitation.

Table 3

The terminal device 110-1 may determine 245 the PDU to transmit the background data in uplink to the server device 130. The terminal device 110-1 transmits 250 the background data in uplink based on the further information. In an example embodiment, if the terminal device 110-1 determines that there is a PDU session that matches the further information. The terminal device 110-1 may determine the existing PDU session to transmit the background data in uplink based on the further information. In that way, the total number of PDU sessions per terminal device can be reduced.

Alternatively, if the terminal device 110-1 determines that all PDU session mismatches with the further information, the terminal device 110-1 may transmit an establishing request to establish a further protocol data unit to transmit the background data in uplink. The establishing request may comprise an indication for transmitting the background data in uplink. Only as an example, the indication or transmitting the background data in uplink may be a background data transferring (BDT) indicator.

In some embodiments, there may be two PDU sessions, one for background data transferring and one for non-BDT, and the terminal device 110-1 may only select the one subject to BDT control ifBDT is required for the AF session. The same AF sessions may be bound to 2 different PDU sessions in uplink and in downlink. However, the server device 130 may usually expect to have a single PDU session for both uplink and in downlink to reduce the complexity of its service logic. Hence an indication of BDT, which is referred to as BDT indicator, is introduced as an attribute of the PDU session to allow either the terminal device 110-1 or the controlling network device 120 to bind the AF session to the same PDU session.

When an establishment of a new PDU session is triggered by the terminal device 110-1 and the new PDU is for BDT, the BDT indicator needs to be contained in the request to establish the new PDU session, and the BDT indicator is then passed to a Session Management Function (SMF) for session establishment. The SMF may establish the PDU and transmit the configuration of the PDU to the controlling network device 120. The configuration of the PDU may comprise the indication for the background data (namely, BDT indicator) . The configuration of the PDU may further comprise one or more of as Access Type, the IPv4 address and/or IPv6 prefix, PEI, GPSI, User Location Information, UE Time Zone, Serving Network, RAT type, Charging Characteristics information, Session AMBR, subscribed default QoS information, Trace Requirements and Internal Group Identifier (see TS 23.501 [2] , clause 5.9.7) , NSI ID, DN Authorization Profile Index, Frame Routes. The controlling network device 120 may combine the session of the server device 130 to the session of the PDU which comprises the BDT indicator.

For every newly detected application, the terminal device 110-1 evaluates the combined URSP and BDT rules and determines if the application is matching the Traffic descriptor of any combined URSP and BDT rule. When a combined URSP and BDT rule is determined to be applicable for a given application, the terminal device 110-1 may select a Route Selection Descriptor within this rule in the order of the Route Selection Descriptor Precedence.

When a valid Route Selection Descriptor is found, the terminal device 110-1 may determine if there is an existing PDU Session that matches all components in the selected Route Selection Descriptor. IfBDT policy is contained, the terminal device 110-1 selects an existing PDU session which can transfer data based on BDT policy.

If none of the existing PDU Sessions matches, the terminal device 110-1 may try to establish a new PDU Session using the values specified by the selected Route Selection Descriptor. If BDT policy is contained, the UE requests to establish a PDU session which can transfer data based on BDT policy, the request contains a BDT indicator. When the controlling network device 120 receives configuration of the new PDU which comprises the indication for the BDT indicator, the controlling network device 120 may bind the AF session to a PDU session which can transfer data based on the further information with the consideration of the BDT indicator.

Fig. 3 illustrates a flow chart of a method 300 in accordance with embodiments of the present disclosure. The method 300 may be implemented at any suitable devices. Only for the purpose of illustrations, the method 300 is described to be implemented at the controlling network device 120.

In some embodiments, the controlling network device 120 may receive a request to generate the information for data transmission. For example, the server device 130 may invoke the Nnef_BDTPNegotiation_Create service. In some embodiments, the request may comprise one or more of: an ASP identifier, the amount of data to be transferred per terminal device, the expected number of terminal devices, the desired time window, network area information, a trigger condition for transmitting the further information, and an identity of a group of terminal devices. In some embodiments, the server device 130 may provide as network area information either a geographical area, or an area of interest that includes a list of TAs or list of NG-RAN nodes and/or a list of cell identifiers. In some embodiments, the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.

The controlling network device 120 may generate the information for data transmission. For example, based on the request, the controlling network device 120 may invoke the Npcf_BDTPolicyControl_Create service to authorize the creation of the policy regarding the background data transfer. In some embodiments, the PCF may determine the information for data transmission based on the request. In some embodiments, the information may also be determined based on other information, for example, network policy, level information in a Single Network Slice Selection Assistance Information (S-NSSAI) and load status estimation for the required time window, network area, and current transfer policies. The controlling network device 120 may be configured to map the ASP identifier into a target DNN and slicing information.

In some embodiments, the controlling network device 120 may generate the candidate lists of information and transmit the candidate list of information to the server device 130. If the server device 130 receives more than candidate lists of information, the server device 130 may select one of them and inform the PCF about the selected list of information. The controlling network device 120 may also generate the index of the information and transmit the index to the server device 130.

In some embodiments, the controlling network device 120 may transmit another request to update the information. The other request may comprise an ASP identifier, the information and the index of the information. Alternatively, the other request may also comprise an indication for delivering the updated information to the terminal device 110-1.

At block 310, the controlling network device 120 receives the request from the server device 130. The request comprises identity information of the terminal device 110-1. For example, the request may comprise an identity of the terminal device 110-1. Alternatively, the request may comprise an identity of a group of terminal devices to which the terminal device 110-1 belongs. In some embodiments, the request may also comprise identity of application and/or identity of operation system (OS) .

At block 320, the controlling network device 120 retrieves the information for data transmission based on the index. For example, the controlling network device 120 may retrieve the all information stored in the UDR to obtain the information.

At block 330, the controlling network device 120 generates the further information for transmitting data in uplink. The further information may comprise at least one of: volume of data to be transferred per terminal device for uplink, desired time window for uplink or network area information for uplink.

At block 340, the controlling network device 120 transmits the further information to the terminal device 110-1. In some embodiments, the controlling network device 120 may generate information of route selection and traffic transfer on a selected route for the terminal device 110-1, for example, the URSP. The controlling network device 120 may transmit the further information together with the URSP. The controlling network device 120 may combine the URSP with the further information. Alternatively, the controlling network device 120 may generate a separate table for the further information. In some embodiments, the controlling network device 120 may transmit the further information in response to the terminal device 110-1 registering in the network.

Fig. 4 illustrates a flow chart of a method 400 in accordance with embodiments of the present disclosure. The method 400 may be implemented at any suitable devices. Only for the purpose of illustrations, the method 400 is described to be implemented at the server device 130.

In some embodiments, the server device 130 may transmit 205 a request to generate the information for data transmission. In some embodiments, the request may comprise one or more of: an ASP identifier, the amount of data to be transferred per terminal device, the expected number of terminal devices, the desired time window, network area information, a trigger condition for transmitting the second information, and an identity of a group of terminal devices. In some embodiments, the server device 130 may provide as network area information either a geographical area, or an area of interest that includes a list of TAs or list of NG-RAN nodes and/or a list of cell identifiers.

In some embodiments, the server device 130 may transmit the candidate list of information. If the server device 130 receives more than candidate lists of information, the server device 130 may select one of them and inform the PCF about the selected list of information.

At block 410, the server device 130 determines that the terminal device 110-1 is to transmit the background data in uplink. In some embodiments, if the terminal device 110-1 initiates to transmit the background data in uplink, the server device 130 determines whether the terminal device 110-1 is allowed to transmit the background data in uplink. In some embodiments, if the terminal device 110-1 starts to register with the server device 130, the server device 130 determines whether the terminal device 110-1 is allowed to transmit the background data in uplink.

At block 420, the server device 130 transmits the request for the information for data transmission. For example, if the server device 130 determines that the terminal device 110-1 is allowed to transmit the background data in uplink, the server device 130 may transmit the request to the controlling network device 120 for the information for data transmission. Alternatively, if the terminal device 110-1 starts to register with the server device 130, the server device 130 may transmit the request to the controlling network device 120 for the information for data transmission. The server device 130 may transmit the index together with the AF session information to the controlling network device 120 via an N5 interface.

Fig. 5 illustrates a flow chart of a method 500 in accordance with embodiments of the present disclosure. The method 500 may be implemented at any suitable devices. Only for the purpose of illustrations, the method 500 is described to be implemented at the terminal device 110-1.

At block 510, the terminal device 110-1 receives the further information for transmitting background data in uplink from the server device 130-1. In some embodiments, the terminal device 110-1 may receive the further information with the URSP.

At block 520, the terminal device 110-1 transmits the background data in uplink based on the further information. The terminal device 110-1 may determine the PDU to transmit the background data in uplink to the server device 130. In an example embodiment, if the terminal device 110-1 determines that there is a PDU session that matches the further information. The terminal device 110-1 may determine the existing PDU session to transmit the background data in uplink based on the further information. In that way, the total number of PDU sessions per terminal device can be reduced.

Alternatively, if the terminal device 110-1 determines that all PDU session mismatches with the further information, the terminal device 110-1 may establish a new PDU session to transmit the background data in uplink based on the further information. The terminal device 110-1 may transmit an establishing request to establish a further protocol data unit to transmit the background data in uplink. The establishing request may comprise an indication for transmitting the background data in uplink.

In some embodiments, an apparatus for performing the method 300 (for example, the controlling network device 120) may comprise respective means for performing the corresponding steps in the method 300. These means may be implemented in any suitable manners. For example, it can be implemented by circuitry or software modules.

In some embodiments, the apparatus comprises: means for receiving, at a controlling network device, a request from a server device, the request comprising identity information of a terminal device and an index associated with information for data transmission; means for retrieving the information for data transmission based on the index; means for generating further information for transmitting background data in uplink based on the information for data transmission; and means for transmitting the further information to the terminal device.

In some embodiments, the further information for transmitting the background data in uplink comprises at least one of: a time window in which the terminal device is allowed to transmit the background data in uplink, an amount of background data allowed to be transmitt320ed by the terminal device in uplink, or information of network area in which the terminal device is allowed to transmit the background data in uplink.

In some embodiments, the means for transmitting the further information comprises: means for generating information of route selection and traffic transfer on a selected route for the terminal device; means for combining the information of route selection and traffic transfer on the selected route with the further information; and means for transmitting the combined information of route selection and traffic transfer on the selected route and the further information.

In some embodiments, the apparatus further comprises: means for generating information of route selection and traffic transfer on a selected route for the terminal device; means for transmitting the information of route selection and traffic transfer on a selected route for the terminal device; and means for transmitting the further information.

In some embodiments, the apparatus comprises means for receiving a further request to generate the information for data transmission, the further request comprising at least one of: a time window in which the terminal device is allowed to transmit the background data in uplink, an amount of background data transmitting in uplink, information of network area in which the terminal device is allowed to transmit the background data in uplink, an identity of a group of terminal devices, or a trigger condition for transmitting the further information; means for generating the firs information for data transmission based on the further request; means for generating the index associated with the information for data transmission; means for transmitting the index to the controlling network device; and means for storing the firs information for data transmission with the index.

In some embodiments, the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.

In some embodiments, the apparatus comprises: means for in response to receiving an update request comprising the index of the information for data transmission, updating the information for data transmission; and means for storing the updated information for data transmission.

In some embodiments, the apparatus comprises: means for in response to the terminal device triggering an establishment of a protocol data unit, receiving configuration of the protocol data unit from a session management device which establishes the protocol data unit, the configuration comprising an indication for the background data.

In some embodiments, the apparatus comprises: means for in response to the request comprising the index of the information, binding a session of the server device to a further session of the protocol data unit on which the background data in uplink is transmitted based on the further information.

In some embodiments, an apparatus for performing the method 400 (for example, the server device 130) may comprise respective means for performing the corresponding steps in the method 400. These means may be implemented in any suitable manners. For example, it can be implemented by circuitry or software modules.

In some embodiments, the apparatus comprises: means for determining that a terminal device is to transmit data in uplink; means for transmitting, to a controlling network device and at a server device, a request comprising identity information of a terminal device and an index associated with information for data transmission; and means for receiving the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.

In some embodiments, the means for transmitting the request to the controlling network device comprises: means for in response to determining the terminal device is allowed to transmit data in uplink, transmitting the request to the controlling network device.

In some embodiments, the means for transmitting the request to the controlling network device comprises: means in response to determining the terminal device is allowed to transmit data in uplink after the terminal device being registered in a network, transmitting the request to the further network device.

In some embodiments, the apparatus comprises means for transmitting a further request to generate the information for data transmission, the further request comprising at least one of: a time window for transmitting the background data in uplink, an amount of background data transmitting in uplink, information of network area in which allowing to transmit the background data in uplink, an identity of a group of terminal devices, or a trigger condition for transmitting the second information; and means for receiving the index associated with the information for data transmission.

In some embodiments, the apparatus comprises: means for transmitting an update request comprising the index of the information for data transmission.

In some embodiments, an apparatus for performing the method 500 (for example, the terminal device 110-1) may comprise respective means for performing the corresponding steps in the method 500. These means may be implemented in any suitable manners. For example, it can be implemented by circuitry or software modules.

In some embodiments, the apparatus comprises: means for receiving, at a terminal device, information for transmitting background data in uplink from a controlling network device; and means for transmitting the background data in uplink to a server device based on the information.

In some embodiments, the information for transmitting the background data in uplink comprises at least one of: a time window in which allowing the terminal device to transmit the background data in uplink, an amount of background data allowed to be transmitted by the terminal device, or information of network area in which allowing the terminal device to transmit the background data.

In some embodiments, the means for receiving the information comprises: means for receiving information of route selection updated with the information.

In some embodiments, the means for transmitting the background data in uplink: means for determining whether a protocol data unit matches with the information; and means for in response to the protocol data unit matching with the information, transmitting the background data in uplink on the protocol data unit.

In some embodiments, the means for transmitting the background data in uplink comprises: means for determining whether a protocol data unit matches with the information; and means for in response to the protocol data unit mismatching with the information, transmitting a request to establish a further protocol data unit to transmit the background data in uplink, the request comprising an indication for transmitting the background data in uplink.

FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure. The device 600 may be provided to implement the communication device, for example the

network devices

120, 130 or the terminal device 110-1 as shown in Fig. 1. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication module (for example, transmitters and/or receivers (TX/RX) ) 640 coupled to the processor 610.

The communication module 640 is for bidirectional communications. The communication module 640 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.

The processor 610 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.

A computer program 630 includes computer executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 624. The processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 622.

The embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to Figs. 2 to 5. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

In some embodiments, the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600. The device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. Fig. 7 shows an example of the computer readable medium 700 in form of CD or DVD. The computer readable medium has the program 630 stored thereon.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the

methods

500 and 600 as described above with reference to Figs. 2-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A controlling network device comprising:

at least one processor; and

at least one memory including computer program codes;

the at least one memory and the computer program codes are configured to, with the at least one processor, cause the controlling network device to:

receive, at the controlling network device, a request from a server device, the request comprising identity information of a terminal device and an index associated with information for data transmission;

retrieve the information for data transmission based on the index;

generate further information for transmitting background data in uplink based on the information for data transmission; and

transmit the further information to the terminal device.
The controlling network device of claim 1, wherein the further information for transmitting the background data in uplink comprises at least one of:

a time window in which the terminal device is allowed to transmit the background data in uplink,

an amount of background data allowed to be transmitted by the terminal device in uplink, or

information of network area in which the terminal device is allowed to transmit the background data in uplink.
The controlling network device of claim 1, wherein the controlling network device is caused to transmit the further information by:

generating information of route selection and traffic transfer on a selected route for the terminal device;

combining the information of route selection and traffic transfer on the selected route with the further information; and

transmitting the combined information of route selection and traffic transfer on the selected route and the further information.
The controlling network device of claim 1, wherein the controlling network device is further caused to:

receive a further request to generate the information for data transmission, the further request comprising at least one of:

a time window in which the terminal device is allowed to transmit the background data in uplink,

an amount of background data transmitting in uplink,

information of network area in which the terminal device is allowed to transmit the background data in uplink,

an identity of a group of terminal devices, or

a trigger condition for transmitting the further information;

generate the information for data transmission based on the further request;

generate the index associated with the information for data transmission;

transmit the index to the network device; and

store the firs information for data transmission with the index.
The controlling network device of claim 4, wherein the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.
The controlling network device of claim 4, wherein the controlling network device is further caused to:

in response to receiving an update request comprising the index of the information for data transmission, update the information for data transmission; and

store the updated information for data transmission.
The controlling network device of claim 1, wherein the controlling network device is further caused to:

in response to the terminal device triggering an establishment of a protocol data unit, receive configuration of the protocol data unit from a session management device which establishes the protocol data unit, the configuration comprising an indication for the background data.
The controlling network device of claim 7, wherein the controlling network device is further caused to:

in response to the request comprising the index of the information, bind a session of the server device to a further session of the protocol data unit on which the background data in uplink is transmitted based on the further information.
A server device comprising:

at least one processor; and

at least one memory including computer program codes;

the at least one memory and the computer program codes are configured to, with the at least one processor, cause the server device to:

determine that a terminal device is to transmit data in uplink;

transmit, to a controlling network device and at the server device, a request comprising identity information of a terminal device and an index associated with information for data transmission; and

receive the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.
The server device of claim 9, wherein the server device is caused to transmit the request to the further network device by:

in response to determining the terminal device is allowed to transmit data in uplink, transmit the request to the controlling network device.
The server device of claim 9, wherein the server device is caused to transmit the request to the further network device by:

in response to determining the terminal device is allowed to transmit data in uplink after the terminal device being registered in a network, transmitting the request to the controlling network device.
The server device of claim 9, wherein the server device is further caused to:

transmit a further request to generate the information for data transmission, the further request comprising at least one of:

a time window for transmitting the background data in uplink,

an amount of background data transmitting in uplink,

information of network area in which allowing to transmit the background data in uplink,

an identity of a group of terminal devices, or

a trigger condition for transmitting the further information; and

receive the index associated with the information for data transmission.
The server device of claim 9, wherein the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.
The server device of claim 12, wherein the server device is further caused to:

transmit an update request comprising the index of the information for data transmission.
A terminal device comprising:

at least one processor; and

at least one memory including computer program codes;

the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to:

receive information for transmitting background data in uplink from a network device; and

transmit the background data in uplink to a server device based on the information.
The terminal device of claim 15, wherein the information for transmitting the background data in uplink comprises at least one of:

a time window in which the terminal device is allowed to transmit the background data in uplink,

an amount of background data allowed to be transmitted by the terminal device in uplink, or

information of network area in which the terminal device is allowed to transmit the background data in uplink.
The terminal device of claim 15, wherein the terminal device is caused to transmit the background data in uplink by:

determining whether a protocol data unit matches with the information; and

in response to the protocol data unit matching with the information, transmitting the background data in uplink on the protocol data unit.
The terminal device of claim 15, wherein the terminal device is caused to transmit the background data in uplink by:

determining whether a protocol data unit matches with the information; and

in response to the protocol data unit mismatching with the information, transmitting an establishing request to establish a further protocol data unit to transmit the background data in uplink, the request comprising an indication for transmitting the background data in uplink.
A method comprising:

receiving, at a controlling network device, a request from a server device, the request comprising identity information of a terminal device and an index associated with information for data transmission;

retrieving the information for data transmission based on the index;

generating further information for transmitting background data in uplink based on the information for data transmission; and

transmitting the further information to the terminal device.
The method of claim 19, wherein the further information for transmitting the background data in uplink comprises at least one of:

a time window in which the terminal device is allowed to transmit the background data in uplink,

an amount of background data allowed to be transmitted by the terminal device in uplink, or

information of network area in which the terminal device is allowed to transmit the background data in uplink.
The method of claim 19, wherein transmitting the further information comprises:

generating information of route selection and traffic transfer on a selected route for the terminal device;

combining the information of route selection and traffic transfer on the selected route with the further information; and

transmitting the combined information of route selection and traffic transfer on the selected route and the further information.
The method of claim 19, further comprising:

receiving a further request to generate the information for data transmission, the further request comprising at least one of:

a time window in which the terminal device is allowed to transmit the background data in uplink,

an amount of background data allowed to be transmitted by the terminal device in uplink,

information of network area in which the terminal device is allowed to transmit the background data in uplink,

an identity of a group of terminal devices, or

a trigger condition for transmitting the further information;

generating the firs information for data transmission based on the further request;

generating the index associated with the information for data transmission;

transmitting the index to the controlling network device; and

storing the information for data transmission with the index.
The method of claim 22, wherein the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.
The method of claim 19, further comprising:

in response to receiving an update request comprising the index of the information for data transmission, updating the information for data transmission; and

storing the updated information for data transmission.
The method of claim 19, further comprising:

in response to the terminal device triggering an establishment of a protocol data unit, receiving configuration of the protocol data unit from a session management device which establishes the protocol data unit, the configuration comprising an indication for the background data.
The method of claim 25, further comprising:

in response to the request comprising the index of the information, binding a session of the server device to a further session of the protocol data unit on which the background data in uplink is transmitted based on the further information.
A method comprising:

determining that a terminal device is to transmit data in uplink;

transmitting, to a controlling network device and at a server device, a request comprising identity information of a terminal device and an index associated with information for data transmission; and

receiving the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.
The method of claim 27, wherein transmitting the request to the controlling network device comprises:

in response to determining the terminal device is allowed to transmit data in uplink, transmitting the request to the controlling network device.
The method of claim 27, wherein transmitting the request to the controlling network device comprises:

in response to determining the terminal device is allowed to transmit data in uplink after the terminal device is registered in a network where the terminal device locates, transmitting the request to the controlling network device.
The method of claim 27, further comprising:

transmitting a further request to generate the information for data transmission, the further request comprising at least one of:

a time window for transmitting the background data in uplink,

an amount of background data transmitting in uplink,

information of network area in which allowing to transmit the background data in uplink,

an identity of a group of terminal devices, or

a trigger condition for transmitting the second information; and

receiving the index associated with the information for data transmission.
The method of claim 30, wherein the trigger condition indicates to transmit the further information to the terminal device in response to the terminal device being registering with a network.
The method of claim 30, further comprising:

transmitting an update request comprising the index of the information for data transmission.
A method comprising:

receiving, at a terminal device, information for transmitting background data in uplink from a controlling network device; and

transmitting the background data in uplink to a server device based on the information.
The method of claim 33, wherein the information for transmitting the background data in uplink comprises at least one of:

a time window in which allowing the terminal device to transmit the background data in uplink,

an amount of background data allowed to be transmitted by the terminal device, or

information of network area in which allowing the terminal device to transmit the background data.
The method of claim 33, wherein transmitting the background data in uplink:

determining whether a protocol data unit matches with the information; and

in response to the protocol data unit matching with the information, transmitting the background data in uplink on the protocol data unit.
The method of claim 33, wherein transmitting the background data in uplink comprises:

determining whether a protocol data unit matches with the information; and

in response to the protocol data unit mismatching with the information, transmitting a request to establish a further protocol data unit to transmit the background data in uplink, the request comprising an indication for transmitting the background data in uplink.
An apparatus comprising:

means for receiving, at a controlling network device, a request from a server device, the request comprising identity information of a terminal device and an index associated with information for data transmission;

means for retrieving the information for data transmission based on the index;

means for generating further information for transmitting background data in uplink based on the information for data transmission; and

means for transmitting the further information to the terminal device.
An apparatus comprising:

means for determining that a terminal device is to transmit data in uplink;

means for transmitting, to a controlling network device and at a server device, a request comprising identity information of a terminal device and an index associated with information for data transmission; and

means for receiving the data in uplink from the terminal device, the data being transmitted based on further information for transmitting data in uplink which is generated based on the information for data transmission.
An apparatus comprising:

means for receiving, at a terminal device, information for transmitting background data in uplink from a controlling network device; and

means for transmitting the background data in uplink to a server device based on the information.
A computer readable medium storing instructions thereon, the instructions, when executed by at least one processing unit of a machine, causing the machine to perform the method according to any one of claims 19-36.