Mechanism for sending background data in uplink
By negotiating and generating backend data transmission strategies for uplink in the 5G communication system, the problem of low backend data transmission efficiency in the 5G system is solved, efficient utilization of radio resources and core network resources is achieved, and resource management and services are optimized. Transmission efficiency.
Patent Information
- Application Number
- CN201980095166.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-04-02
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-04-02
AI Technical Summary
In 5G communication systems, the transmission efficiency of backend data is low, and it is difficult for the existing technology to effectively utilize radio resources and core network resources. Especially in the uplink, the traditional backend data transmission strategy is not efficient, resulting in waste of resources and dispersion of services. Uneven.
By negotiating between the control network device and the server device, a background data transmission policy for uplink is generated and transmitted, including the identification information, data volume, time window and network area information of the terminal device, ensuring efficient in non-busy times. Transfer backend data, reduce signaling and improve resource utilization.
It realizes efficient background data transmission in the uplink, optimizes resource utilization, reduces the number of PDU sessions of terminal devices, and improves service transmission efficiency and resource management flexibility.
Smart Images

Figure CN113678490B_ABST
Abstract
Description
Technical Field
[0001] 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 sending background data in an uplink. Background Art
[0002] In recent communication networks, the amount of data has increased dramatically. For example, in the fifth generation (5G) communication system, the capacity of the available radio access node (RAN) is much larger than that in the fourth generation (4G) communication system. 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. Summary of the invention
[0003] In general, embodiments of the present disclosure relate to a method for sending background data in an uplink and a corresponding communication device.
[0004] In a first aspect, a control 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, together 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 a terminal device and an index associated with information for data transmission. The control network device is further caused to retrieve information for data transmission based on the index. The control network device is further caused to generate additional information for sending background data in an uplink based on the information for data transmission. The control network device is further caused to send additional information to the terminal device.
[0005] In a second aspect, a server device is provided. The server 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, together with the at least one processor, cause the server device to determine that the terminal device is to send data in an uplink. The server device is also caused to send a request including identification information of the terminal device and an index associated with information for data transmission to a control network device at the server device. The server device is also caused to receive data from the terminal device in the uplink, the data being sent in the uplink based on additional information for data transmission, the additional information for data transmission being generated based on the information for data transmission.
[0006] In a third aspect, a terminal device is provided. The terminal 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 cause the terminal device to receive information for sending background data in an uplink from a network device together with the at least one processor. The terminal device is also caused to send background data to a server device in an uplink based on the information.
[0007] In a fourth aspect, a method is provided. The method includes receiving a request from a server device at a control network device. The request includes identification information of a terminal device and an index associated with information for data transmission. The method also includes obtaining information for data transmission based on the index. The method also includes generating additional information for sending background data in an uplink based on the information for data transmission. The method also includes sending the additional information to the terminal device.
[0008] In a fifth aspect, a method is provided. The method includes determining that a terminal device is to send data in an uplink. The method also includes transmitting, at a server device, a request to a control network device including identification information of the terminal device and an index associated with information for data transmission. The method also includes receiving data from the terminal device in the uplink, the data being sent in the uplink based on additional information for data transmission, the additional information for data transmission being generated based on the information for data transmission.
[0009] In a sixth aspect, a method is provided. The method includes receiving information for sending background data in an uplink from a control network device at a terminal device. The method also includes sending the background data to a server device in an uplink based on the information.
[0010] In a seventh aspect, a device is provided, comprising: a component for receiving a request from a server device at a control network device, the request comprising identification information of a terminal device and an index associated with information for data transmission; a component for obtaining information for data transmission based on the index; a component for generating additional information for sending background data in an uplink based on the information for data transmission; and a component for transmitting the additional information to the terminal device.
[0011] In an eighth aspect, a device is provided, comprising: a component for determining that a terminal device is to send data in an uplink; a component for sending a request to a control network device at a server device, the request comprising identification information of the terminal device and an index associated with information for data transmission; and a component for receiving data from the terminal device in an uplink, the data being sent in the uplink based on additional information for data transmission, the additional information for data transmission being generated based on the information for data transmission.
[0012] In a ninth aspect, an apparatus is provided, comprising: a component for receiving information for sending background data in an uplink from a control network device at a terminal device; and a component for sending background data to a server device in an uplink based on the information.
[0013] In a tenth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least execute a method according to any one of the fourth to sixth aspects above.
[0014] It should be understood that the summary is not intended to identify the key or essential features of the 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 readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Some example embodiments will now be described with reference to the accompanying drawings, in which:
[0016] Figure 1 A schematic diagram of a communication system according to an embodiment of the present disclosure is shown;
[0017] Figure 2 A schematic diagram showing interactions between devices according to an embodiment of the present disclosure;
[0018] Figure 3 A flowchart of a method implemented at a control network device according to an embodiment of the present disclosure is shown;
[0019] Figure 4 A flowchart of a method implemented at a server device according to an embodiment of the present disclosure is shown;
[0020] Figure 5 A flowchart of a method implemented at a terminal device according to an embodiment of the present disclosure is shown;
[0021] Figure 6 A schematic diagram showing an apparatus according to an embodiment of the present disclosure; and
[0022] Figure 7A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.
[0023] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0024] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for the purpose of illustrating and helping those skilled in the art to understand and realize the present disclosure, without any limitation to the scope of the present disclosure. The disclosure described herein can be realized in various other ways except as described below.
[0025] 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.
[0026] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).
[0027] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiment, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0028] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "including", "having", "having", "including" and / or "comprising" when used herein specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0029] As used in this application, the term "circuitry" may refer to one, more, or all of the following:
[0030] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only), and
[0031] (b) a combination of hardware circuitry and software such as (where applicable):
[0032] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and
[0033] (ii) any portion of a hardware processor (including a digital signal processor) with software, software and memory that work together to cause a device (such as a mobile phone or server) to perform various functions, and
[0034] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but which may not be present when not required for operation.
[0035] This 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 covers an implementation of only a hardware circuit or processor (or multiple processors) or a 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 a particular claim element) a baseband integrated circuit or processor integrated circuit of a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0036] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the user equipment and the network equipment in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, of course, there will also be communication technologies and systems that can be used to embody future types of the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned systems.
[0037] 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), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as a femto, a pico), etc., depending on the terminology and technology applied.
[0038] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image acquisition terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless terminal, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
[0039] As mentioned above, background data may not need to be transmitted immediately.The core network in the 3rd Generation Partnership Project (3GPP) shall support a third party service provider requesting background data delivery for a group of terminal devices that are served by the third party service provider.
[0040] In addition, the third-party application server should be able to indicate to the 3GPP system when background data transfer (a) exceeds the agreed maximum data amount, or (b) continues beyond the agreed time window, or (c) occurs outside the agreed area.
[0041] The 3GPP Core Network should be able to inform the third party service provider in a coordinated response, based on locally available information over the geographical area (e.g. congestion levels), of the following: one or more recommended time windows for data transfer and, for each time window, the maximum aggregate bit rate for a group of UEs in the geographical area indicated by the third party service provider.
[0042] Furthermore, 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 if the data is delivered within the recommended time window and if the transmission rate remains below the limit of the corresponding maximum aggregate bit rate.
[0043] The purpose of providing time windows is to facilitate the delivery of more traffic during non-peak hours, and the reason for providing a maximum aggregate bit rate is to spread the traffic during that time. The purpose of multiple time windows is to allow a third party provider to select an appropriate time window based on its preferences (such as expected billing system and bit rate).
[0044] In traditional technology, the traditional UE routing policy (URSP) framework can be used to deliver policy information related to background data delivery from the 5G core network to the terminal device. The policy information content can define the time window and location criteria that the background data delivery needs to meet.
[0045] There is a single dedicated protocol data unit (PDU) session for background data delivery that is established and released based on the background data delivery policy. In traditional solutions, a network device (e.g., an application server) can connect to a policy control function (PCF) via a network exposure function (NEF) to request a time window and related conditions for future background data delivery.
[0046] The application server request may contain an automatic site positioning (ASP) identifier, the amount of data to be transmitted for each terminal device, the expected amount of terminal devices, the expected time window, and optional network area information. The application server provides a geographic area 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 geographic area, the NEF maps it to a short list of TAs and / or NG-RAN nodes and / or cell identifiers provided to the PCF based on local configuration.
[0047] The PCF may first retrieve all existing delivery strategies stored for any ASP from the UDR. Afterwards, the PCF shall determine one or more delivery strategies based on the information provided by the AF and other available information (e.g., network strategy, level information in S-NSSAI, and load state estimates of the required time window, network area, and existing transmission strategies). The PCF may be configured to map the ASP identifier to the target DNN and slice information.
[0048] In some embodiments, the delivery policy may include a recommended time window for background data delivery, a reference to a charging rate for that time window, and an optional maximum aggregate bit rate (indicating that charging according to the referenced charging rate applies only to aggregate traffic of all relevant UEs that remains below that value).
[0049] Finally, the PCF may provide the candidate transmission strategy list or the selected transmission strategy to the application server via the NEF together with the background data transmission reference ID. If the application server receives more than one transmission strategy, the application server may select one of them and notify the PCF of the selected transmission strategy.
[0050] The selected transmission strategy is finally stored by the PCF in the Unified Data Repository (UDR) together with the background data transmission reference ID and network region information. The same or different PCF can obtain the transmission strategy and corresponding network region information from the UDR and take them into account in future decisions about the transmission strategy of background data related to the same or other ASPs.
[0051] When background data transmission is about to start, AF provides background data transmission reference ID and AF session information to PCF for each UE (via N5 interface). PCF obtains the corresponding transmission policy from UDR and derives PCC rules for background data transmission according to the transmission policy. However, the current background data transmission policy only includes the attributes of downlink data transmission.
[0052] According to an embodiment of the present disclosure, if a server device initiates a background data delivery negotiation process, the server device sends a request to the terminal device in an uplink for sending information for transmitting background data. The control network device sends information for sending background data to the terminal device in an uplink. In this way, the background transmission in the uplink is managed and more efficient.
[0053] Figure 1A schematic diagram of a communication system 100 in which embodiments of the present disclosure may be implemented is shown. The communication system 100, as part of a communication network, includes terminal devices 110-1, 110-2, ..., 110-N (collectively referred to as "terminal devices 110", where N is an integer). The communication system 100 includes one or more network devices, such as a network device 120 (also referred to as a "control network device 120") and a network device 130 (also referred to as a "server device 130"). It should be understood that the communication system 100 may also include other elements that are omitted for clarity. It should be understood that Figure 1 The number of terminal devices and network devices shown is given for illustrative purposes and does not represent any limitation. The server device 130 and the control network device 120 can communicate with the terminal device 110.
[0054] It should be understood that the number of network devices and terminal devices is only for illustration purposes and does not represent any limitation. System 100 may include any suitable number of network devices and terminal devices suitable for implementing the embodiments of the present disclosure.
[0055] The communication in the communication system 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G), wireless local area network communication protocols (such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and / or any other protocol currently known or developed in the future. In addition, the communication can use any appropriate 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 technology currently known or developed in the future.
[0056] Figure 2 A schematic diagram of an interaction 200 according to an embodiment of the present disclosure is shown. The interaction 200 may be implemented at any suitable device. For illustrative purposes only, the interaction 200 is described as being implemented at the terminal device 110 - 1 , the control network device 120 , and the server device 130 .
[0057] 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 call the Nnef_BDTP Negotiation_Create service. In some embodiments, the request may include one or more of the following: an ASP identifier, an amount of data to be transferred for each terminal device, an expected number of terminal devices, an expected time window, network area information, an identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographic area or an area of interest as network area information, including a TA list or a NG-RAN node list and / or a cell identifier list. The request may also include a trigger condition for sending additional information to the terminal device. For example, the trigger condition may indicate that if the terminal device is registered with the network, additional information needs to be sent to the terminal device.
[0058] The controlling network device 120 may generate 210 information for data transmission. For example, based on the request, the controlling network device 120 may call the Npcf_BDTPolicyControl_Create service to authorize the creation of a policy regarding background data delivery. In some embodiments, the PCF may determine information for data transmission based on the request. In some embodiments, the information may also be determined based on other information, such as a network policy, level information in a single network slice selection auxiliary information (S-NSSAI), and a required time window, network area, and load state estimate of the current transmission policy. The controlling network device 120 may be configured to map an ASP identifier to a target DNN and slice information (i.e., S-NSSAI).
[0059] In some embodiments, the control network device 120 may generate a candidate information list and send the candidate information list to the server device 130. If the server device 130 receives more than one candidate information list, the server device 130 may select one of them and notify the PCF of the selected information list. The control network device 120 may also generate an index of the information (e.g., a background data transmission reference ID) and transmit 215 the index to the server device 130.
[0060] The control network device 120 may store information with an index. For example, the information with an index may be stored in a UDR. The same or different PCFs may obtain the information and corresponding network area information from the UDR.
[0061] In some embodiments, server device 130 may send another request for updating the information. The another request may include an ASP identifier, the information, and an index of the information. Alternatively, the another request may also include an instruction for delivering the updated information to terminal device 110-1.
[0062] The server device 130 determines that the terminal device 110-1 is to send background data in the uplink. In some embodiments, if the terminal device 110-1 initiates the sending of background data in the uplink, the server device 130 determines whether the terminal device 110-1 is allowed to send background data in the 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 send background data in the uplink.
[0063] Server device 130 sends 225 a request for information for data transmission. 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 for information for data transmission to control network device 120. Alternatively, if terminal device 110-1 begins to register with server device 130, server device 130 may send a request for information for data transmission to control network device 120. Server device 130 may send an index and AF session information to control network device 120 via the N5 interface.
[0064] The request includes identification information of the terminal device 110-1. For example, the request may include the identification of the terminal device 110-1. Alternatively, the request may include the identification of a group of terminal devices, and the terminal device 110-1 belongs to the group of terminal devices. In some embodiments, the request may also include the identification of an application and / or the identification of an operating system (OS).
[0065] The request also includes an index to information for data transmission. The request may also include one or more of the following: a time window in which the 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 information of a network area in which the terminal device is allowed to transmit background data in the uplink.
[0066] The controlling network device 120 retrieves 230 information for data transmission based on the index. For example, the controlling 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 sending data in the uplink. The further information may include at least one of the following: an amount of data to be sent for each terminal device of the uplink, an expected time window for the uplink, or network area information for the uplink.
[0067] The control network device 120 sends the additional information to the terminal device 110-1. In some embodiments, the control network device 120 can generate information (e.g., URSP) for the terminal device 110-1 on the route selection and the traffic transmission on the selected route. The control network device 120 can send the additional information together with the URSP. The control network device 120 can combine the URSP with the additional information. Table 1 below shows an example of an extended URSP rule. It should be noted that Table 1 is only an example and not a limitation.
[0068] Table 1
[0069]
[0070]
[0071] The following Table 2 shows an example of the additional information. It should be noted that Table 2 is only an example and not a limitation.
[0072] Table 2
[0073]
[0074]
[0075] In this way, since the additional information only applies to the session of the server device 130 that can be identified by any one of the service descriptors used for the URSP (e.g., AF session), the URSP and the additional information can share the same service description, and therefore, extending the URSP to include more information can reduce the size of the UE policy when they are provided together, thereby reducing N1 signaling. For application services affected by the additional information, the URSP and the additional information policy are likely to be provided together, for example, when the server device 130 is about to start service transmission, it triggers the control network device 120 to deliver the required policy.
[0076] In addition, there is a single dedicated PDU session for sending background data in the uplink, which is established and released based on the additional information. This means that when associating an application with a PDU session, both the URSP and the additional information need to be considered, and it is easier for the terminal device to perform PDU session association.
[0077] In some embodiments, the control network device 120 can generate a separate table for the additional information. The additional information and the URSP can be sent separately. In this way, the additional information can be more backward compatible with conventional communication systems. Table 3 below shows an example of the additional information. It should be noted that Table 3 is only an example and not a limitation.
[0078] Table 3
[0079]
[0080]
[0081]
[0082] Terminal device 110-1 may determine 245 a PDU for sending background data in an uplink to server device 130. Terminal device 110-1 sends 250 the background data in an uplink based on the further information. In an example embodiment, if terminal device 110-1 determines that there is a PDU session that matches the further information. Terminal device 110-1 may determine an existing PDU session for sending background data in an uplink based on the further information. In this way, the total number of PDU sessions per terminal device may be reduced.
[0083] Alternatively, if the terminal device 110-1 determines that all PDU sessions do not match the additional information, the terminal device 110-1 may send a setup request to establish an additional protocol data unit for sending background data in the uplink. The setup request may include an indication for sending background data in the uplink. By way of example only, the indication for sending background data in the uplink may be a background data transfer (BDT) indicator.
[0084] In some embodiments, there can be two PDU sessions, one PDU session for background data and one PDU session for non-BDT, and if the AF session requires BDT, the terminal device 110-1 can only select the PDU session controlled by BDT. In the uplink and downlink, the same AF session can be bound to 2 different PDU sessions. However, the server device 130 may generally desire to have a single PDU session for both uplink and downlink to reduce the complexity of its service logic. Therefore, a BDT indication, referred to as a BDT indicator, is introduced as an attribute of the PDU session to allow the terminal device 110-1 or the controlling network device 120 to bind the AF session to the same PDU session.
[0085] When the 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 included in the request to establish the new PDU session, and the BDT indicator is then transmitted to the session management function (SMF) for session establishment. The SMF can establish the PDU and send the configuration of the PDU to the control 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 the following: access type, IPv4 address and / or IPv6 prefix, PEI, GPSI, user location information, UE time zone, service network, RAT type, charging characteristic information, session AMBR, subscribed default QoS information, tracking requirements and internal group identifier (see Section 5.9.7 of TS 23.501), NSI ID, DN authorization profile index, frame routing. The control network device 120 can combine the session of the server device 130 with the session of the PDU including the BDT indicator.
[0086] For each newly detected application, terminal device 110-1 evaluates the combined URSP and BDT rules and determines whether the application matches the service descriptor of any combined URSP and BDT rules. When the combined URSP and BDT rules are 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.
[0087] When a valid routing descriptor is found, the terminal device 110-1 may determine whether there is an existing PDU session that matches all components in the selected routing descriptor. If a BDT policy is included, the terminal device 110-1 selects an existing PDU session that can deliver data based on the BDT policy.
[0088] If none of the existing PDU sessions match, the terminal device 110-1 may attempt to establish a new PDU session using the value specified by the selected routing descriptor. If a BDT policy is included, the UE requests to establish a PDU session that can transmit data based on the BDT policy, and the request includes a BDT indicator. When the control network device 120 receives the configuration of a new PDU including an indication of the BDT indicator, the control network device 120 may bind the AF session to the PDU session that can transmit data based on the additional information taking into account the BDT indicator.
[0089] Figure 3 1 is a flow chart of a method 300 according to an embodiment of the present disclosure. The method 300 may be implemented at any suitable device. For illustration purposes only, the method 300 is described as being implemented at the control network device 120.
[0090] In some embodiments, the control network device 120 may receive a request to generate information for data transmission. For example, the server device 130 may call the Nnef_BDTPNegotiation_Create service. In some embodiments, the request may include one or more of the following: an ASP identifier, an amount of data to be transmitted for each terminal device, an expected number of terminal devices, an expected time window, network area information, a trigger condition for transmitting additional information, and an identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographic area or an area of interest as network area information, including a TA list or a NG-RAN node list and / or a cell identifier list. In some embodiments, the trigger condition indicates that additional information is sent to the terminal device in response to the terminal device registering with the network.
[0091] The control network device 120 may generate information for data transmission. For example, based on the request, the control network device 120 may call the Npcf_BDTPolicyControl_Create service to authorize the creation of a policy regarding background data delivery. In some embodiments, the PCF may determine information for data transmission based on the request. In some embodiments, the information may also be determined based on other information, such as network policy, level information in single network slice selection auxiliary information (S-NSSAI), and required time windows, network areas, and load state estimates of the current transmission policy. The control network device 120 may be configured to map the ASP identifier to the target DNN and slice information.
[0092] In some embodiments, the control network device 120 may generate a candidate information list and send the candidate information list to the server device 130. If the server device 130 receives more than one candidate information list, the server device 130 may select one of them and notify the PCF of the selected information list. The control network device 120 may also generate an index of the information and send the index to the server device 130.
[0093] The control network device 120 may store information with an index. For example, the information with an index may be stored in a UDR. The same or different PCFs may obtain the information and corresponding network area information from the UDR.
[0094] In some embodiments, the control network device 120 may send another request for updating the information. The another request may include the ASP identifier, the information, and an index of the information. Alternatively, the another request may also include an instruction for delivering the updated information to the terminal device 110-1.
[0095] 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 the identification of terminal device 110-1. Alternatively, the request may include the identification of a group of terminal devices to which terminal device 110-1 belongs. In some embodiments, the request may also include the identification of an application and / or an identification of an operating system (OS).
[0096] The request also includes an index to information for data transmission. The request may also include one or more of the following: a time window in which the terminal device 110-1 is allowed to send 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 area in which the terminal device is allowed to send background data in the uplink.
[0097] At block 320, the controlling network device 120 retrieves information for data transmission based on the index. For example, the controlling network device 120 may retrieve all information stored in the UDR to obtain the information.
[0098] At block 330, the control network device 120 generates further information for sending data in uplink. The further information may include at least one of: the amount of data to be sent for each terminal device for uplink, the desired time window for uplink, or network area information for uplink.
[0099] At block 340, control network device 120 sends additional information to terminal device 110-1. In some embodiments, control network device 120 may generate information (e.g., URSP) for terminal device 110-1 on route selection and traffic transmission on the selected route. Control network device 120 may send the additional information together with the URSP. Control network device 120 may combine the URSP with the additional information. Alternatively, control network device 120 may generate a separate table for the additional information. In some embodiments, control network device 120 may send the additional information in response to terminal device 110-1 registering in the network.
[0100] Figure 4 4 is a flow chart of a method 400 according to an embodiment of the present disclosure. The method 400 may be implemented at any suitable device. For illustration purposes only, the method 400 is described as being implemented at the server device 130.
[0101] In some embodiments, the 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: an ASP identifier, an amount of data to be sent for each terminal device, an expected amount of the terminal device, an expected time window, network area information, a trigger condition for sending the second information, and an identification of a group of terminal devices. In some embodiments, the server device 130 may provide a geographical area or an area of interest as the network area information, including a TA list or a NG-RAN node list and / or a cell identifier list.
[0102] In some embodiments, server device 130 may send a candidate information list. 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.
[0103] In some embodiments, server device 130 may send another request for updating the information. The other request may include an ASP identifier, the information, and an index of the information. Alternatively, the other request may also include an instruction to transmit the updated information to terminal device 110-1.
[0104] At block 410, server device 130 determines that terminal device 110-1 is to send background data in an uplink. In some embodiments, if terminal device 110-1 initiates sending background data in an uplink, server device 130 determines whether terminal device 110-1 is allowed to send background data in an 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 an uplink.
[0105] At block 420, server device 130 sends a request for information for data transmission. 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 for information for data transmission to control network device 120. Alternatively, if terminal device 110-1 begins to register with server device 130, server device 130 may send a request for information for data transmission to control network device 120. Server device 130 may send the index and AF session information to control network device 120 via the N5 interface.
[0106] The request includes identification information of the terminal device 110-1. For example, the request may include the identification of the terminal device 110-1. Alternatively, the request may include the identification of a group of terminal devices to which the terminal device 110-1 belongs. In some embodiments, the request may also include the identification of an application and / or an identification of an operating system (OS).
[0107] The request also includes an index to information for data transmission. The request may also include one or more of the following: a time window in which the terminal device 110-1 is allowed to send 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 area in which the terminal device is allowed to send background data in the uplink.
[0108] Figure 5 1 is a flow chart of a method 500 according to an embodiment of the present disclosure. The method 500 may be implemented at any suitable device. For illustration purposes only, the method 500 is described as being implemented at the terminal device 110 - 1 .
[0109] At block 510, the terminal device 110-1 receives from the server device 130-1 further information for sending background data in uplink.In some embodiments, the terminal device 110-1 may receive the further information together with the URSP.
[0110] At block 520, terminal device 110-1 sends background data in an uplink based on the additional information. Terminal device 110-1 may determine a PDU for sending background data in an uplink to server device 130. In an example embodiment, if terminal device 110-1 determines that there is a PDU session that matches the additional information. Terminal device 110-1 may determine an existing PDU session for sending background data in an uplink based on the additional information. In this way, the total number of PDU sessions for each terminal device may be reduced.
[0111] Alternatively, if the terminal device 110-1 determines that all PDU sessions do not match the additional information, the terminal device 110-1 may establish a new PDU session for sending background data in the uplink based on the additional information. The terminal device 110-1 may send a setup request to establish an additional protocol data unit for transmitting background data in the uplink. The setup request may include an indication for sending background data in the uplink.
[0112] In some embodiments, an apparatus for performing method 300 (e.g., controlling network device 120) may include corresponding components for performing corresponding steps in method 300. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit system or a software module.
[0113] In some embodiments, the apparatus includes: a component for receiving a request from a server device at a control network device, the request including identification information of a terminal device and an index associated with information for data transmission; a component for obtaining information for data transmission based on the index; a component for generating additional information for transmitting background data in an uplink based on the information for data transmission; and a component for sending additional information to the terminal device.
[0114] In some embodiments, the additional information for sending background data in the uplink includes at least one of: a time window in which the terminal device is allowed to transmit background data in the uplink, the 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 background data in the uplink.
[0115] In some embodiments, the component for sending additional information includes: a component for generating information about route selection and service transmission on the selected route for a terminal device; a component for combining the information about route selection and service transmission on the selected route with additional information; and a component for sending the combined information about route selection and service transmission on the selected route with the additional information.
[0116] In some embodiments, the apparatus further comprises: a component for generating information on route selection and service transmission on the selected route for a terminal device; a component for sending information on route selection and service transmission on the selected route to the terminal device; and a component for sending additional information.
[0117] In some embodiments, the apparatus includes a component for receiving an additional request for generating information for data transmission, the additional request including at least one of: a time window in which the terminal device is allowed to send background data in an uplink, an amount of background data sent in an uplink, information about a network area in which the terminal device is allowed to send background data in an uplink, an identification of a group of terminal devices, or a trigger condition for sending additional information; a component for generating first information for data transmission based on the additional request; a component for generating an index associated with the information for data transmission; a component for sending the index to a control network device; and a component for storing the first information for data transmission together with the index.
[0118] In some embodiments, the triggering condition indicates that further information is transmitted to the terminal device in response to the terminal device registering with the network.
[0119] In some embodiments, the apparatus includes: means for updating the information for data transmission in response to receiving an update request including an index of the information for data transmission; and means for storing the updated information for data transmission.
[0120] In some embodiments, the apparatus comprises means for receiving, in response to the terminal device triggering establishment of the protocol data unit, a configuration of the protocol data unit from a session management device establishing the protocol data unit, the configuration comprising an indication of the background data.
[0121] In some embodiments, the apparatus comprises means for binding the session of the server device to a further session of protocol data units over which background data is transmitted in an uplink based on the further information in response to the request comprising an index to the information.
[0122] In some embodiments, an apparatus for executing method 400 (e.g., server device 130) may include corresponding components for executing corresponding steps in method 400. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit system or a software module.
[0123] In some embodiments, the apparatus includes: a component for determining that a terminal device is to send data in an uplink; a component for sending a request to a control network device at a server device, the request including identification information of the terminal device and an index associated with information for data transmission; and a component for receiving data from the terminal device in an uplink, the data being sent in the uplink based on additional information for data transmission, the additional information for data transmission being generated based on the information for data transmission.
[0124] In some embodiments, the means for sending the request to the controlling network device comprises means for sending the request to the controlling network device in response to determining that the terminal device is allowed to send data in the uplink.
[0125] In some embodiments, the means for sending the request to the controlling network device comprises means for sending the request to the further network device in response to determining that the terminal device is allowed to send data in an uplink after the terminal device registers in the network.
[0126] In some embodiments, the apparatus includes a component for sending an additional request for generating information for data transmission, the additional request including at least one of: a time window for sending background data in an uplink, an amount of background data to be sent in an uplink, information of a network area in which background data is allowed to be sent in an uplink, an identification of a group of terminal devices, or a trigger condition for sending second information; and a component for receiving an index associated with the information for data transmission.
[0127] In some embodiments, the triggering condition indicates that further information is transmitted to the terminal device in response to the terminal device registering with the network.
[0128] In some embodiments, the apparatus comprises: means for transmitting an update request comprising an index of information for data transmission.
[0129] In some embodiments, an apparatus for executing method 500 (e.g., terminal device 110-1) may include corresponding components for executing corresponding steps in method 500. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit system or a software module.
[0130] In some embodiments, the apparatus comprises: a component for receiving information for sending background data in an uplink from a control network device at a terminal device; and a component for sending background data to a server device in an uplink based on the information.
[0131] In some embodiments, the information for sending background data in the uplink includes at least one of: a time window in which the terminal device is allowed to send background data in the uplink, the 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.
[0132] In some embodiments, the means for receiving information includes means for receiving routing information updated with the information.
[0133] In some embodiments, means for sending background data in the uplink includes means for determining whether the protocol data unit matches the information; and means for sending the background data in the uplink on the protocol data unit in response to the protocol data unit matching the information.
[0134] In some embodiments, the means for sending background data in an uplink comprises: means for determining whether a protocol data unit matches the information; and means for sending a request to establish an additional protocol data unit for transmitting background data in an uplink in response to the protocol data unit not matching the information, the request comprising an indication for sending background data in the uplink.
[0135] Figure 6 600 is a simplified block diagram of a device 600 suitable for implementing an embodiment of the present disclosure. The device 600 may be used to implement a communication device, such as Figure 1 The network devices 120, 130 or the terminal device 110-1 are shown. 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.
[0136] The communication module 640 is used for two-way 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.
[0137] Processor 610 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.
[0138] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic storage and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist over the duration of a power outage.
[0139] Computer program 630 includes computer executable instructions that are executed by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any suitable actions and processes by loading program 630 into RAM 622.
[0140] The embodiments of the present disclosure may be implemented by a program 630, so that the device 600 may execute the Figures 2 to 5 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.
[0141] In some embodiments, the program 630 may be tangibly embodied in a computer-readable medium, which may be included in the device 600 (such as in the memory 620) or in other storage devices accessible to 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 type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 7 An example of a computer readable medium 700 in the form of a CD or DVD is shown. The computer readable medium has a program 630 stored thereon.
[0142] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the block diagrams, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.
[0143] 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 computer executable instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above reference Figure 2-6 Methods 500 and 600 described herein. Typically, program modules include routines, programs, libraries, objects, classes, components, data types, etc. that perform specific tasks or implement specific abstract data structures. The functions of program modules can be combined or split between program modules as needed in various embodiments. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.
[0144] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that these program codes cause the functions / operations specified in the flow chart and / or block diagram to be implemented when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, executed as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.
[0145] In the context of the present disclosure, computer program codes 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 carriers include signals, computer readable media, etc.
[0146] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination thereof. More specific examples of computer readable storage media include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0147] In addition, although the operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in a continuous order or to perform all the operations shown to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes several specific implementation details, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively.
[0148] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should 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 control network device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the controlling network device to: receiving, at the control 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; Retrieve the information for data transmission based on the index; Generating additional information for the terminal device to send background data in an uplink based on the information for data transmission, wherein the additional information for the terminal device to send the background data in an uplink includes at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as The additional information is sent to the terminal device.
2. The control network device according to claim 1, wherein the control network device is caused to send the further information by: Generating information on route selection and service transmission on the selected route for the terminal device; combining information of the route selection and traffic transmission over the selected route with the further information; and The combined information of the route selection and the traffic transmission on the selected route is sent together with the further information.
3. The control network device according to claim 1, wherein the control 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 time window in which the terminal device is allowed to send the background data in the uplink, the amount of said background data sent in uplink, the information of the network area, the terminal device is allowed to send the background data in uplink in the network area, The identifier 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; as well as The information for data transmission is stored together with the index.
4. A control network device according to claim 3, 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.
5. The control network device according to claim 3, wherein the control network device is further caused to: updating the information for data transmission in response to receiving an update request including the index of the information for data transmission; and Stores updated information for data transmission.
6. The control network device according to claim 1, wherein the control network device is further caused to: In response to the terminal device triggering the establishment of a protocol data unit, receiving a configuration of the protocol data unit from a session management device that establishes the protocol data unit, the configuration including an indication for the background data.
7. The control network device according to claim 6, wherein the control network device is further caused to: In response to the request comprising the index to the information, the session of the server device is bound to a further session of the protocol data units on which the background data is sent in uplink based on the further information.
8. A server device, comprising: at least one processor; as well as 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: Determining that the terminal device is to send data in an uplink; sending, at the server device, a request to a control network device, the request including identification information of a terminal device and an index associated with information for data transmission; as well as receiving the data from the terminal device in an uplink, the data being sent in an uplink based on further information for data transmission, the further information for data transmission being generated based on the information for data transmission, wherein the further information for data transmission comprises at least one of the following: a time window in which the terminal device is allowed to send background data in the uplink, the amount of background data allowed to be sent by the terminal device in uplink, or The terminal device may also be configured to transmit the background data in the uplink in the network area in which the terminal device is allowed to transmit the background data.
9. The server device according to claim 8, wherein the server device is caused to send the request to another network device by: In response to determining that the terminal device is allowed to send data in the uplink, the request is sent to the controlling network device.
10. The server device of claim 8, wherein the server device is caused to send the request to another network device by: In response to determining that the terminal device is allowed to send data in an uplink after the terminal device is registered in the network, the request is sent to the controlling network device.
11. The server device according to claim 8, 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 the following: the time window for sending the background data in an uplink, the amount of said background data sent in uplink, the information of the network area allowing the background data to be sent in uplink in the network area, The identifier of a group of terminal devices, or a triggering condition for sending the further information; and The index is received in association with the information for data transmission.
12. A server device according to claim 11, 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.
13. The server device according to claim 11, wherein the server device is further caused to: An update request for the index including the information for data transmission is sent.
14. A terminal device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: Receiving information used by the terminal device to send background data in an uplink from a control network device, wherein the information used by the terminal device to send the background data in an uplink is generated by the control network device in the following manner: receiving, at the control network device, a request from a server device, the request including identification information of the terminal device and an index associated with information for data transmission; Retrieve the information for data transmission based on the index; Generating additional information for the terminal device to send the background data in an uplink based on the information for data transmission, wherein the additional information for the terminal device to send the background data in an uplink includes at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as The background data is sent in an uplink to the server device based on the information.
15. The terminal device according to claim 14, wherein the terminal device is caused to send the background data in uplink by: determining whether the protocol data unit matches the information; and In response to the protocol data unit matching the information, the background data is sent in an uplink on the protocol data unit.
16. The terminal device according to claim 14, wherein the terminal device is caused to send the background data in uplink by: determining whether the protocol data unit matches the information; and In response to the protocol data unit not matching the information, a setup request for establishing a further protocol data unit for sending the background data in uplink is sent, the request comprising an indication for sending the background data in uplink.
17. A method for communication, comprising: receiving, at a control 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; Retrieve the information for data transmission based on the index; Generating additional information for the terminal device to send background data in an uplink based on the information for data transmission, wherein the additional information for the terminal device to send the background data in an uplink includes at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as The additional information is sent to the terminal device.
18. The method of claim 17, wherein sending the additional information comprises: Generating information on route selection and service transmission on the selected route for the terminal device; combining the information of the route selection and the traffic transmission on the selected route with the further information; as well as The combined information of the route selection and the traffic transmission on the selected route is sent together with the further information.
19. The method according to claim 17, further comprising: receiving a further request for generating the information for data transmission, the further request comprising at least one of: the time window in which the terminal device is allowed to send the background data in the uplink, the amount of the background data allowed to be transmitted by the terminal device in uplink, the information of the network area, the terminal device is allowed to send the background data in uplink in the network area, The identifier 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; as well as The information for data transmission is stored together with the index.
20. A method according to claim 19, 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.
21. The method of claim 17, further comprising: updating the information for data transmission in response to receiving an update request including the index of the information for data transmission; as well as Stores updated information for data transmission.
22. The method of claim 17, further comprising: In response to the terminal device triggering the establishment of a protocol data unit, receiving a configuration of the protocol data unit from a session management device that establishes the protocol data unit, the configuration including an indication for the background data.
23. The method according to claim 22, further comprising: In response to the request comprising the index to the information, the session of the server device is bound to a further session of the protocol data units on which the background data is sent in uplink based on the further information.
24. A method for communication, comprising: Determining that the terminal device is to send data in an uplink; Sending a request at a server device to a control network device, the request including identification information of the terminal device and an index associated with information for data transmission; as well as receiving the data from the terminal device in an uplink, the data being sent in an uplink based on further information for data transmission, the further information for data transmission being generated based on the information for data transmission, wherein the further information for data transmission comprises at least one of the following: a time window in which the terminal device is allowed to send background data in the uplink, the amount of background data allowed to be sent by the terminal device in uplink, or The terminal device may also be configured to transmit the background data in the uplink in the network area in which the terminal device is allowed to transmit the background data.
25. The method of claim 24, wherein sending the request to the control network device comprises: In response to determining that the terminal device is allowed to send data in the uplink, the request is sent to the controlling network device.
26. The method of claim 24, wherein sending the request to the control network device comprises: In response to determining that the terminal device is allowed to send data in an uplink after registering in the network where the terminal device is located, the request is sent to the controlling network device.
27. The method of claim 24, further comprising: Sending a further request to generate the information for data transmission, the further request comprising at least one of the following: the time window for sending the background data in an uplink, the amount of said background data sent in uplink, the information of the network area allowing the background data to be sent in uplink in the network area, The identifier of a group of terminal devices, or a trigger condition for sending the further information; as well as The index is received in association with the information for data transmission.
28. A method according to claim 27, 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.
29. The method of claim 27, further comprising: An update request for the index including the information for data transmission is sent.
30. A method for communication, comprising: Receiving, at a terminal device, information for the terminal device to send background data in an uplink from a control network device, wherein the information for the terminal device to send the background data in an uplink is generated by the control network device in the following manner: receiving, at the control network device, a request from a server device, the request including identification information of the terminal device and an index associated with information for data transmission; Retrieve the information for data transmission based on the index; Generating additional information for the terminal device to send the background data in an uplink based on the information for data transmission, wherein the additional information for the terminal device to send the background data in an uplink includes at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as The background data is sent to the server device in an uplink at the terminal device based on the information.
31. The method of claim 30, wherein sending the background data in an uplink comprises: determining whether the protocol data unit matches the information; as well as In response to the protocol data unit matching the information, the background data is sent in an uplink on the protocol data unit.
32. The method of claim 30, wherein sending the background data in an uplink comprises: determining whether the protocol data unit matches the information; as well as In response to the protocol data unit not matching the information, a request for creating a further protocol data unit for sending the background data in uplink is sent, the request comprising an indication for sending the background data in uplink.
33. An apparatus for communication, comprising: means for receiving, at the control network device, a request from a server device, the request comprising identification information of the terminal device and an index associated with information for data transmission; means for obtaining the information for data transmission based on the index; A means for generating further information for the terminal device to send background data in an uplink based on the information for data transmission, wherein the further information for the terminal device to send the background data in an uplink comprises at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as Means for sending said further information to said terminal device.
34. An apparatus for communication, comprising: A component for determining that a terminal device is to send data in an uplink; means for sending, at the server device, a request to the control network device, the request comprising identification information of the terminal device and an index associated with information for data transmission; as well as means for 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, wherein the further information for data transmission comprises at least one of the following: a time window in which the terminal device is allowed to send background data in the uplink, the amount of background data allowed to be sent by the terminal device in uplink, or The terminal device may also be configured to transmit the background data in the uplink in the network area in which the terminal device is allowed to transmit the background data.
35. An apparatus for communication, comprising: A component for receiving, at a terminal device, information for the terminal device to send background data in an uplink from a control network device, wherein the information for the terminal device to send the background data in an uplink is generated by the control network device in the following manner: receiving, at the control network device, a request from a server device, the request including identification information of the terminal device and an index associated with information for data transmission; Retrieve the information for data transmission based on the index; Generating additional information for the terminal device to send the background data in an uplink based on the information for data transmission, wherein the additional information for the terminal device to send the background data in an uplink includes at least one of the following: a time window in which the terminal device is allowed to send the background data in an uplink, the amount of background data allowed to be sent by the terminal device in uplink, or information of a network area in which the terminal device is allowed to send the background data in an uplink; as well as Means for sending the background data to a server device in an uplink based on the information at the terminal device.
36. 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 17 to 32.
