CN113678490A

CN113678490A - Mechanism for transmitting background data in uplink

Info

Publication number: CN113678490A
Application number: CN201980095166.7A
Authority: CN
Inventors: 沈洋; 王维兴
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2019-04-02
Filing date: 2019-04-02
Publication date: 2021-11-19
Also published as: WO2020199129A9; WO2020199129A1

Abstract

Embodiments of the present disclosure relate to mechanisms for transmitting background data in the uplink. According to an embodiment of the present invention, if a server device initiates a background data transfer negotiation process, the server device sends a request for sending information for sending background data to a terminal device in an uplink. And controlling the network equipment to send information for sending background data to the terminal equipment in an uplink. In this way, the transmission of the background in the uplink is managed and more efficient.

Description

Mechanism for transmitting background data in uplink

Technical Field

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

Background

In recent communication networks, the amount of data has increased dramatically. For example, in fifth generation (5G) communication systems, the capacity of the available Radio Access Nodes (RANs) is much larger than in fourth generation (4G) communication systems. Some data, such as background data, may not need to be transmitted immediately. It is expected that background data transfer will be used to utilize both radio resources and core network resources in an efficient manner.

Disclosure of Invention

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

In a first aspect, a controlling network device is provided. The control network device includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the control network device to receive a request from a server device at the control network device. The request includes identification information of the terminal device and an index associated with information for data transmission. The controlling network device is further caused to retrieve information for the data transmission based on the index. The control network device is further caused to generate further information for sending background data in the uplink based on the information for data transmission. The controlling network device is further caused to send further information to the terminal device.

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

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

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

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

In a sixth aspect, a method is provided. The method comprises receiving, at a terminal device, information from a controlling network device for transmitting background data in an uplink. The method also includes transmitting background data in an uplink to the 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 including identification information of a terminal device and an index associated with information for data transmission; means for retrieving information for data transmission based on the index; means for generating further information for sending background data in the 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 the terminal device is to transmit data in an uplink; means for sending, at the server device, a request to the controlling network device, the request comprising identification information of the terminal device and an index associated with information for data transmission; and means for receiving data in the uplink from the terminal device, the data being transmitted in the uplink based on the further information for data transmission, the further information for data transmission being 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 from a controlling network device for transmitting background data in an uplink; and means for sending background data to the server device in an uplink 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 a method according to any one of the fourth to sixth aspects described above.

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

Drawings

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

fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present disclosure;

FIG. 2 shows a schematic diagram of interactions between devices according to an embodiment of the present disclosure;

FIG. 3 shows a flow diagram of a method implemented at a controlling network device, according to an embodiment of the present disclosure;

FIG. 4 shows a flow diagram of a method implemented at a server device, in accordance with an embodiment of the present disclosure;

FIG. 5 shows a flow diagram of a method implemented at a terminal device in accordance with an embodiment of the disclosure;

FIG. 6 shows a schematic diagram of an apparatus according to an embodiment of the present disclosure; and

fig. 7 illustrates 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 numbers refer to the same or similar elements.

Detailed Description

The principles of the present disclosure will now be described with reference to a few exemplary embodiments. It is understood that these embodiments are described only for the purpose of illustration and to aid those skilled in the art in understanding and practicing the present disclosure, and do not set forth any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various other ways than those described below.

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

References in the present disclosure to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. 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 will be understood that, although the terms first, 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, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof.

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

(a) a purely hardware circuit implementation (such as an implementation in analog and/or digital circuitry only), and

(b) a combination of hardware circuitry and software, such as (as applicable):

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

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

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

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

As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), narrowband internet of things (NB-IoT), and so forth. Further, communication between user devices and network devices in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and/or any other protocol now known or later developed. Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will, of course, also be future types of communication technologies and systems that may be used to embody the present disclosure. The scope of the present disclosure should not be limited to the above-described systems.

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. A network device may refer to a Base Station (BS) or an Access Point (AP), e.g., a NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), relay, low power node (such as femto, pico), etc., depending on the terminology and technology applied.

The term "terminal device" refers to any terminal device capable of wireless communication. By way of example, and not limitation, a terminal device may also be referred to as a communication device, User Equipment (UE), Subscriber Station (SS), portable subscriber station, Mobile Station (MS), or Access Terminal (AT). The end devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable end devices, Personal Digital Assistants (PDAs), portable computers, desktop computers, image capture end devices (such as digital cameras), gaming end devices, music storage and playback devices, in-vehicle wireless end devices, wireless terminals, mobile stations, laptop embedded devices (LEEs), laptop installation devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), internet of things (loT) devices, watches or other wearable devices, Head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in industrial and/or automated processing chain environments), Consumer electronics devices, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

As described above, background data may not need to be transferred immediately. A core network in the third generation partnership project (3GPP) should support a third party service provider to request background data transfer for a group of terminal devices that are serviced by the third party service provider.

Furthermore, the third party application server should be able to indicate to the 3GPP system when background data delivery (a) exceeds the agreed maximum amount of data, or (b) continues to exceed the agreed time window, or (c) occurs outside the agreed area.

The 3GPP core network should be able to inform the third party service provider in a coordinated response based on locally available information (e.g., congestion level) over a geographical area about the following: one or more recommended time windows for data transfer, and for each time window, a maximum aggregate bit rate for a group of UEs in a geographic area indicated by the third party service provider.

Furthermore, if the data is delivered within the recommended time window and if the transmission rate remains below the limit of the respective maximum aggregated bit rate, the 3GPP core network should be able to inform the third party service provider of the charging policy to be applied to the third party service provider.

The purpose of providing a time window is to facilitate the delivery of more traffic at less busy times, and the reason for providing the maximum aggregate bit rate is to spread the traffic over that time. The purpose of the multiple time windows is to allow the third party provider to select an appropriate time window based on its preferences, such as the desired billing regime and bit rate.

In conventional techniques, a conventional UE routing policy (URSP) framework may be used to deliver policy information related to background data transfer from a 5G core network to a terminal device. The policy information content may define time window and location criteria that need to be met by the background data transfer.

There is a single dedicated Protocol Data Unit (PDU) session for background data transfer that is established and released based on a background data transfer policy. In conventional solutions, a network device (e.g., an application server) may connect with a Policy Control Function (PCF) via a Network Exposure Function (NEF) to request a time window and related conditions for future background data transfers.

The application server request may contain an automatic site location (ASP) identifier, an amount of data to be transmitted for each terminal device, an expected amount of terminal devices, a desired time window, and optionally network area information. The application server provides a geographical or area of interest as network area information, including a Time Advance (TA) list or a list of NG-RAN nodes and/or a list of cell identifiers. When the application server provides a geographical area, the NEF maps it based on local configuration into a short list of TA and/or NG-RAN nodes and/or cell identifiers provided to the PCF.

The PCF may first retrieve all existing delivery policies stored for any ASP from the UDR. The PCF should then determine one or more delivery policies based on the information provided by the AF and other available information (e.g., network policy, level information in S-NSSAI, and load state estimates for required time windows, network areas, and existing transmission policies). The PCF may be configured to map the ASP identifier into the target DNN and the slice information.

In some embodiments, the delivery policy may include a recommended time window for background data delivery, a reference to a charging rate for the time window, and optionally a maximum aggregated bit rate (indicating that charging according to the referenced charging rate is applicable only to aggregated traffic for all relevant UEs that remain below this value).

Finally, the PCF may provide the list of candidate transmission policies or the selected transmission policy to the application server via the NEF together with the background data transmission reference ID. If the application server receives more than one transmission policy, the application server may select one of them and notify the PCF of the selected transmission policy.

The selected transfer policy is ultimately stored by the PCF in a Unified Data Repository (UDR) along with the background data transfer reference ID and network area information. The same or a different PCF may take this transmission policy and corresponding network area information from the UDR and take them into account in future decisions regarding transmission policies for background data related to the same or other ASPs.

As background data transfer is about to begin, the AF provides the PCF with background data transfer reference IDs and AF session information for each UE (via the N5 interface). The PCF obtains the corresponding transmission policy from the UDR and derives PCC rules for background data transmission based on the transmission policy. However, current background data transfer strategies only include the attributes of downlink data transfers.

According to an embodiment of the present disclosure, if a server device initiates a process of background data transfer negotiation, the server device sends a request for sending information for transmitting background data to a terminal device in an uplink. And controlling the network equipment to send information for sending background data to the terminal equipment in an uplink. In this way, the transmission of the background in the uplink is managed and more efficient.

Fig. 1 shows a schematic diagram of a communication system 100 in which embodiments of the present disclosure may be implemented. Communication system 100, which is part of a communication network, includes terminal devices 110-1, 110-2, … …, 110-N (collectively, "terminal devices 110," where N is an integer). Communication system 100 includes one or more network devices, such as network device 120 (also referred to as "control network device 120") and network device 130 (also referred to as "server device 130"). It should be understood that communication system 100 may also include other elements that have been omitted for clarity. It should be understood that the number of terminal devices and network devices shown in fig. 1 is given for illustrative purposes and does not represent any limitation. Server device 130 and controlling network device 120 may communicate with terminal device 110.

It should be understood that the number of network devices and terminal devices is for illustration purposes only and does not represent any limitation. System 100 may include any suitable number of network devices and terminal devices suitable for implementing embodiments of the present disclosure.

Communications in communication system 100 may be implemented in accordance with any suitable communication protocol, including, but not limited to, first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), etc. cellular communication protocols, wireless local area network communication protocols, such as Institute of Electrical and Electronics Engineers (IEEE)802.11, etc., and/or any other protocol currently known or developed in the future. Further, the communication may use any suitable wireless communication technology, including but not limited to: code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and/or any other technique now known or later developed.

Fig. 2 shows a schematic diagram of an interaction 200 according to an embodiment of the present disclosure. The interaction 200 may be implemented at any suitable device. For purposes of illustration only, interaction 200 is described as being implemented at terminal device 110-1, controlling network device 120, and server device 130.

In some embodiments, the server device 130 may send 205 a request to generate information for data transmission. For example, the server device 130 may invoke a Nnef _ BDTP negotiation creation service. In some embodiments, the request may include one or more of the following: ASP identifier, amount of data to be transferred per terminal device, expected number of terminal devices, desired time window, network area information, identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographical area or area of interest as network area information, including a TA list or a list of NG-RAN nodes and/or a list of cell identifiers. The request may also include a trigger condition for sending further information to the terminal device. For example, the trigger condition may indicate that additional information needs to be sent to the terminal device if the terminal device registers with the network.

The controlling network device 120 may generate 210 information for data transmission. For example, based on the request, control network device 120 may invoke an Npcf _ BDT policy control Create (Npcf _ BDTPolicyControl Create) service to authorize creation of policies for background data transfers. In some embodiments, the PCF may determine information for the data transmission based on the request. In some embodiments, this information may also be determined based on other information, such as network policy, level information in single network slice selection assistance information (S-NSSAI), and load state estimates for required time windows, network areas, and current transmission policies. Control network device 120 may be configured to map the ASP identifier to the target DNN and the slice information (i.e., S-NSSAI).

In some embodiments, control network device 120 may generate a candidate information list and send the candidate information list to server device 130. If server device 130 receives more than one candidate information list, server device 130 may select one of them and notify the PCF of the selected information list. Control network device 120 may also generate an index of the information (e.g., background data transfer reference ID) and transmit 215 the index to server device 130.

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

In some embodiments, the server device 130 may send another request to update the information. Another request may include the ASP identifier, the information, and an index to the information. Alternatively, the further request may also include an indication for delivering the updated information to terminal device 110-1.

Server device 130 determines that terminal device 110-1 is to send background data in the uplink. In some embodiments, if terminal device 110-1 initiates sending background data in the uplink, server device 130 determines whether terminal device 110-1 is allowed to send background data in the uplink. In some embodiments, if terminal device 110-1 begins to register with server device 130, server device 130 determines whether terminal device 110-1 is allowed to send background data in the uplink.

The server device 130 sends 225 a request for information for data transfer. For example, if server device 130 determines that terminal device 110-1 is allowed to send background data in the uplink, server device 130 may send a request to control network device 120 for information for data transfer. Alternatively, if terminal device 110-1 starts registering with server device 130, server device 130 may send a request for information for data transmission to control network device 120. The server device 130 may send the index and AF session information to the controlling network device 120 via the N5 interface.

The request includes identification information of terminal device 110-1. For example, the request may include an identification of terminal device 110-1. Alternatively, the request may include an identification of a group of terminal devices to which terminal device 110-1 belongs. In some embodiments, the request may also include an identification of the application and/or an identification of the Operating System (OS).

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

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

Controlling network device 120 to send additional information to terminal device 110-1. In some embodiments, controlling network device 120 may generate routing and information for traffic transmission on the selected route (e.g., URSP) for terminal device 110-1. The controlling network device 120 may send additional information with the URSP. The controlling network device 120 may combine the URSP with additional information. Table 1 below shows an example of extending the URSP rule. It should be noted that table 1 is exemplary only and not limiting.

TABLE 1

Table 2 below shows an example of additional information. It should be noted that table 2 is merely exemplary and not limiting.

TABLE 2

In this way, since the further information only applies to sessions (e.g., AF sessions) of the server device 130 that may be identified by any of the traffic descriptors for the URSP, the URSP and the further information may share the same traffic description, and thus, extending the URSP to include more information may reduce the size of the UE policy when they are provided together, so that N1 signaling may be reduced. For application traffic affected by further information, the URSP and the further information policy are likely to be provided together, e.g. when the server device 130 is about to start traffic transmission, it will trigger the policy needed to control the delivery of the network device 120.

Furthermore, there is a single dedicated PDU session for transmitting background data in the uplink, which is established and released based on additional information. This means that both the URSP and further information need to be considered at the same time when associating an application with a PDU session, and it is easier for the terminal device to perform PDU session association.

In some embodiments, control network device 120 may generate a separate table for additional information. The additional information and the URSP may be sent separately. In this way, the additional information may be more backward compatible with conventional communication systems. Table 3 below shows an example of additional information. It should be noted that table 3 is merely exemplary and not limiting.

TABLE 3

Terminal device 110-1 may determine 245 a PDU for transmitting background data in the uplink to server device 130. Terminal device 110-1 transmits 250 background data in the uplink based on the additional information. In the exemplary embodiment, if terminal device 110-1 determines that there is a PDU session matching additional information. Terminal device 110-1 may determine an existing PDU session for transmitting background data in the uplink based on the additional information. In this way, the total number of PDU sessions per terminal device may be reduced.

Alternatively, if terminal device 110-1 determines that all PDU sessions do not match the further information, terminal device 110-1 may send a setup request to set up a further protocol data unit for transmitting background data in the uplink. The establishment request may include an indication to send background data in the uplink. For example only, the indication to transmit background data in the uplink may be a Background Data Transfer (BDT) indicator.

In some embodiments, there may be two PDU sessions, one for background data scrubbing and one for non-BDT, and terminal device 110-1 may only select a PDU session controlled by BDT if a BDT is needed for an AF session. In both uplink and downlink, the same AF session can be bound to 2 different PDU sessions. However, server device 130 may generally desire to have a single PDU session for both the uplink and downlink to reduce the complexity of its service logic. Thus, a BDT indication, referred to as a BDT indicator, is introduced as an attribute of the PDU session to allow terminal device 110-1 or control network device 120 to bind the AF session to the same PDU session.

When the establishment of a new PDU session is triggered by terminal device 110-1 and the new PDU is for BDT, a BDT indicator needs to be included in the request to establish the new PDU session and the BDT indicator is then passed to the Session Management Function (SMF) for session establishment. The SMF may establish the PDU and send the configuration of the PDU to the controlling network device 120. The configuration of the PDU may include an indication of background data (i.e., a BDT indicator). The configuration of the PDU may also include one or more of: access type, IPv4 address and/or IPv6 prefix, PEI, GPSI, user location information, UE time zone, serving network, RAT type, charging characteristics information, session AMBR, default QoS information for subscription, tracking requirements and internal group identifier (see section 5.9.7 of TS 23.501), NSI ID, DN authorization profile index, frame routing. Control network device 120 may combine the session of server device 130 with the session of the PDU including the BDT indicator.

For each newly detected application, terminal device 110-1 evaluates the combined URSP and BDT rules and determines whether the application matches the traffic descriptor of any combined URSP and BDT rules. When the combined URSP and BDT rule is determined to be applicable to a given application, terminal device 110-1 may select a routing descriptor within the rule in order of routing descriptor priority.

When a valid routing descriptor is found, end device 110-1 may determine whether there is an existing PDU session that matches all of the components in the selected routing descriptor. If a BDT policy is included, terminal device 110-1 selects an existing PDU session that may communicate data based on the BDT policy.

If none of the existing PDU sessions match, end device 110-1 may attempt to establish a new PDU session using the value specified by the selected routing descriptor. If the BDT policy is included, the UE requests establishment of a PDU session that may transfer data based on the BDT policy, the request including a BDT indicator. When the control network device 120 receives a configuration of new PDUs including an indication of the BDT indicator, the control network device 120 may bind the AF session to a PDU session, which may communicate data in view of the BDT indicator based on further information.

Fig. 3 shows a flow diagram of a method 300 according to an embodiment of the present disclosure. Method 300 may be implemented at any suitable device. For purposes of illustration only, method 300 is described as being implemented at controlling network device 120.

In some embodiments, control network device 120 may receive a request to generate information for data transmission. For example, the server device 130 may call the Nnef _ bdtpnotification _ Create service. In some embodiments, the request may include one or more of the following: ASP identifier, amount of data to be communicated per terminal device, expected number of terminal devices, desired time window, network area information, trigger conditions for transmitting further information, and identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographical area or area of interest as network area information, including a TA list or a list of NG-RAN nodes and/or a list of cell identifiers. In some embodiments, the trigger condition indicates that further information is to be sent to the terminal device in response to the terminal device registering with the network.

Control network device 120 may generate information for data transmission. For example, based on the request, control network device 120 may invoke the Npcf _ BDTPolicyControl _ Create service to authorize the creation of policies for background data transfers. In some embodiments, the PCF may determine information for the data transmission based on the request. In some embodiments, this information may also be determined based on other information, such as network policy, level information in single network slice selection assistance information (S-NSSAI), and load state estimates for required time windows, network areas, and current transmission policies. Control network device 120 may be configured to map the ASP identifier to the target DNN and the slice information.

In some embodiments, control network device 120 may generate a candidate information list and send the candidate information list to server device 130. If server device 130 receives more than one candidate information list, server device 130 may select one of them and notify the PCF of the selected information list. Control network device 120 may also generate an index of this information and send the index to server device 130.

In some embodiments, controlling network device 120 may send another request to update the information. Another request may include the ASP identifier, the information, and an index to the information. Alternatively, the further request may also include an indication for delivering the updated information to terminal device 110-1.

At block 310, control network device 120 receives a request from server device 130. The request includes identification information of terminal device 110-1. For example, the request may include an identification of terminal device 110-1. Alternatively, the request may include an identification of a group of terminal devices to which terminal device 110-1 belongs. In some embodiments, the request may also include an identification of the application and/or an identification of the Operating System (OS).

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

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

At block 330, the controlling network device 120 generates additional information for transmitting data in the uplink. The further information may comprise at least one of: an amount of data to be transmitted for each terminal device for the uplink, a desired time window for the uplink, or network area information for the uplink.

At block 340, network device 120 is controlled to send additional information to terminal device 110-1. In some embodiments, controlling network device 120 may generate routing and information for traffic transmission on the selected route (e.g., URSP) for terminal device 110-1. The controlling network device 120 may send additional information with the URSP. The controlling network device 120 may combine the URSP with additional information. Alternatively, control network device 120 may generate a separate table for the additional information. In some embodiments, controlling network device 120 may send additional information in response to terminal device 110-1 registering in the network.

Fig. 4 shows a flow diagram of a method 400 according to an embodiment of the present disclosure. Method 400 may be implemented at any suitable device. For purposes of illustration only, the method 400 is described as being implemented at the server device 130.

In some embodiments, server device 130 may send a request to generate information for data transmission. In some embodiments, the request may include one or more of the following: ASP identifier, amount of data to be transmitted per terminal device, expected amount of terminal devices, desired time window, network area information, trigger conditions for transmitting the second information, and identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographical area or area of interest as network area information, including a TA list or a list of NG-RAN nodes and/or a list of cell identifiers.

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

In some embodiments, the server device 130 may send another request to update the information. Another request may include the ASP identifier, the information, and an index to the information. Alternatively, the further request may also comprise an indication to transmit the updated information to terminal device 110-1.

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

At block 420, the server device 130 sends a request for information for data transfer. For example, if server device 130 determines that terminal device 110-1 is allowed to send background data in the uplink, server device 130 may send a request to control network device 120 for information for data transfer. Alternatively, if terminal device 110-1 starts registering with server device 130, server device 130 may send a request for information for data transmission to control network device 120. The server device 130 may send the index and AF session information to the controlling network device 120 via the N5 interface.

Fig. 5 shows a flow diagram of a method 500 according to an embodiment of the present disclosure. Method 500 may be implemented at any suitable device. Method 500 is described as being implemented at terminal device 110-1 for purposes of illustration only.

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

At block 520, terminal device 110-1 transmits background data in the uplink based on the additional information. Terminal device 110-1 may determine a PDU for transmitting background data in the uplink to server device 130. In the exemplary embodiment, if terminal device 110-1 determines that there is a PDU session matching additional information. Terminal device 110-1 may determine an existing PDU session for transmitting background data in the uplink based on the additional information. In this way, the total number of PDU sessions per terminal device may be reduced.

Alternatively, if terminal device 110-1 determines that all PDU sessions do not match the additional information, terminal device 110-1 may establish a new PDU session for transmitting background data in the uplink based on the additional information. Terminal device 110-1 may send a setup request to set up further protocol data units for transmitting background data in the uplink. The establishment request may include an indication to transmit background data in the uplink.

In some embodiments, an apparatus (e.g., controlling network device 120) for performing method 300 may include respective means for performing corresponding steps in method 300. These components may be implemented in any suitable manner. For example, it may 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 including identification information of a terminal device and an index associated with information for data transmission; means for obtaining information for data transmission based on the index; means for generating further information for transmitting background data in the uplink based on the information for data transmission; and means for transmitting the further information to the terminal device.

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

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

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

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

In some embodiments, the trigger condition indicates that further information is to be transmitted to the terminal device in response to the terminal device registering with the network.

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

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

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

In some embodiments, an apparatus (e.g., server device 130) for performing method 400 may include respective means for performing corresponding steps in method 400. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.

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

In some embodiments, the means for sending the request to the controlling network device comprises: means for sending a request to a controlling network device in response to determining that the terminal device is allowed to send data in the uplink.

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

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

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

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

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

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

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

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

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

Fig. 6 is a simplified block diagram of a device 600 suitable for implementing embodiments of the present disclosure. Device 600 may be used to implement a communication device, such as

network devices

120, 130 or terminal device 110-1 shown in fig. 1. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processors 610, and one or more communication modules (e.g., transmitters and/or receivers (TX/RX))640 coupled to the processors 610.

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

The processor 610 may be of any type suitable for a local technology network, and may include, by way of non-limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), and processors based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips that are time-dependent from a clock synchronized to the main processor.

The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, Read Only Memory (ROM)624, Electrically Programmable Read Only Memory (EPROM), flash memory, a hard disk, a Compact Disk (CD), a Digital Video Disk (DVD), and other magnetic storage and/or optical storage devices. Examples of volatile memory include, but are not limited to, Random Access Memory (RAM)622 and other volatile memory that does not persist for the duration of the power down.

The computer programs 630 include 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 processes by loading the program 630 into the RAM 622.

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

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

In general, the various embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the block diagrams, apparatus, systems, techniques or methods described herein may be implemented in 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, that execute in the device on the target real or virtual processor to perform the

methods

500 and 600 described above with reference to fig. 2-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data types, etc. 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 local or distributed devices. In a distributed facility, program modules may be located in both local and remote memory storage media.

Program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the execution of the program codes by the processor or controller causes the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the 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, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of a 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 is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of a computer-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

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 some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. A controlling network device, comprising:

at least one processor; and

at least one memory including computer program code;

the at least one memory and the computer program code configured to, with the at least one processor, cause the control network device to:

receiving, at the controlling network device, a request from a server device, the request including identification 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 sending background data in an uplink based on the information for data transmission; and

transmitting the further information to the terminal device.

2. The controlling network device of claim 1, wherein the further information for sending 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,

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

Information of a network area in which the terminal device is allowed to send the background data in uplink.

3. The controlling network device of claim 1, wherein the controlling network device is caused to transmit the further information by:

generating routing selection and information of service transmission on the selected route for the terminal equipment;

combining the routing and information of traffic transmission on the selected route with the further information; and

sending the combined routing and information of traffic transmission on the selected route together with the further information.

4. The controlling network device of claim 1, wherein the controlling network device is further caused to:

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

the amount of background data sent in the uplink,

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

identification of a group of terminal devices, or

A trigger condition for sending the further information;

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

generating the index associated with the information for data transmission;

sending the index to the network device; and

storing the information for data transmission with the index.

5. The controlling network device of claim 4, wherein the trigger condition indicates that the further information is sent to the terminal device in response to the terminal device registering with a network.

6. The controlling network device of claim 4, wherein the controlling network device is further caused to:

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

and storing the updated information for data transmission.

7. The controlling network device of claim 1, wherein the controlling network device is further caused to:

in response to the terminal device triggering establishment of a protocol data unit, receiving a configuration of the protocol data unit from a session management device that established the protocol data unit, the configuration including an indication for the background data.

8. 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, binding the session of the server device to a further session of the protocol data unit on which the background data is sent in an uplink based on the further information.

9. A server device, comprising:

at least one processor; and

at least one memory including computer program code;

the at least one memory and the computer program code configured to, with the at least one processor, cause the server apparatus to:

determining that the terminal equipment is to send data in an uplink;

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

receiving the data from the terminal device in an uplink, the data being transmitted in the uplink based on further information for data transmission, the further information for data transmission being generated based on the information for data transmission.

10. The server device of claim 9, wherein the server device is caused to send the request to the further network device by:

sending the request to the controlling network device in response to determining that the terminal device is allowed to send data in the uplink.

11. The server device of claim 9, wherein the server device is caused to send the request to the further network device by:

sending the request to the controlling network device in response to determining that the terminal device is allowed to send data in the uplink after the terminal device is registered in the network.

12. The server device of claim 9, wherein the server device is further caused to:

sending 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,

the amount of background data sent in the uplink,

information of a network area in which the background data is allowed to be transmitted in an uplink,

identification of a group of terminal devices, or

A trigger condition for sending the further information; and

receiving the index associated with the information for data transmission.

13. The server device of claim 9, wherein the trigger condition indicates that the further information is sent to the terminal device in response to the terminal device registering with a network.

14. The server device of claim 12, wherein the server device is further caused to:

sending an update request including the index of the information for data transmission.

15. A terminal device, comprising:

at least one processor; and

at least one memory including computer program code;

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

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

and sending the background data to a server device in an uplink based on the information.

16. The terminal device of claim 15, wherein the information for sending the background data in uplink comprises at least one of:

17. The terminal device of claim 15, wherein the terminal device is caused to send the background data in the uplink by:

determining whether a protocol data unit matches the information; and

in response to the protocol data unit matching the information, sending the background data in an uplink on the protocol data unit.

18. The terminal device of claim 15, wherein the terminal device is caused to send the background data in the uplink by:

determining whether a protocol data unit matches the information; and

in response to the protocol data unit not matching the information, sending a setup request for setting up a further protocol data unit for sending the background data in the uplink, the request comprising an indication for sending the background data in the uplink.

19. A method, comprising:

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

retrieving the information for data transmission based on the index;

transmitting the further information to the terminal device.

20. The method of claim 19, wherein the additional information for sending 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 the uplink,

21. The method of claim 19, wherein sending the additional information comprises:

22. The method of claim 19, further comprising:

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

identification of a group of terminal devices, or

A trigger condition for sending the further information;

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

generating the index associated with the information for data transmission;

sending the index to the control network device; and

storing the information for data transmission with the index.

23. The method of claim 22, wherein the trigger condition indicates that the further information is sent to the terminal device in response to the terminal device registering with a network.

24. The method of claim 19, further comprising:

and storing the updated information for data transmission.

25. The method of claim 19, further comprising:

26. The method of claim 25, further comprising:

27. A method, comprising:

determining that the terminal equipment is to send data in an uplink;

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

28. The method of claim 27, wherein sending the request to the control network device comprises:

29. The method of claim 27, wherein sending the request to the control network device comprises:

sending the request to the controlling network device in response to determining that the terminal device is allowed to send data in the uplink after the terminal device is registered in a network in which the terminal device is located.

30. The method of claim 27, further comprising:

a time window for transmitting the background data in uplink,

the amount of background data sent in the uplink,

identification of a group of terminal devices, or

A trigger condition for sending the second information; and

receiving the index associated with the information for data transmission.

31. The method of claim 30, wherein the trigger condition indicates that the further information is sent to the terminal device in response to the terminal device registering with a network.

32. The method of claim 30, further comprising:

33. A method, comprising:

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

34. The method of claim 33, wherein the information for sending the background data in uplink comprises at least one of:

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

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

And the information of the network area allows the terminal equipment to send the background data in the network area.

35. The method of claim 33, wherein sending the background data in uplink comprises:

determining whether a protocol data unit matches the information; and

36. The method of claim 33, wherein sending the background data in uplink comprises:

determining whether a protocol data unit matches the information; and

in response to the protocol data unit not matching the information, sending a request to establish a further protocol data unit for sending the background data in the uplink, the request comprising an indication for sending the background data in the uplink.

37. An apparatus, comprising:

means for receiving, at a controlling network device, a request from a server device, the request including identification 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 sending background data in an uplink based on the information for data transmission; and

means for transmitting the further information to the terminal device.

38. An apparatus, comprising:

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

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

means for receiving the data from the terminal device in uplink, the data being transmitted in uplink based on further information for data transmission, the further information for data transmission being generated based on the information for data transmission.

39. An apparatus, comprising:

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

means for transmitting the background data to a server device in an uplink based on the information.

40. A computer-readable medium having instructions stored thereon, which, when executed by at least one processing unit of a machine, cause the machine to perform the method of any one of claims 19 to 36.