Method, apparatus, system and computer program to determine packet delay budget

Abstract

There is provided a method for use in a network node, comprising: obtaining first information indicating a value of a delay between a first network entity and a second network entity and second information indicating a location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and a value of the delay between the network node and a second network entity whose location is indicated by the second information.

Description

Technical Field

[0001] The various example embodiments of this disclosure relate to a method, apparatus, system, and computer program, and particularly, but not limited to, determining packet delay budget (PDB) in a non-terrestrial network (NTN) architecture. Background Technology

[0002] A communication network can be used as a facility to enable communication between two or more communication devices or to provide communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Communication devices can be provided with services through an application server.

[0003] Communication networks can operate according to standards, such as those provided by the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3GPP are the so-called 3GPP standards for different generations of cellular technology, such as the 3GPP standards for 4G, 5G, 6G, etc. Summary of the Invention

[0004] Some exemplary embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure. Nor are these aspects intended to be used to limit its scope. In view of this disclosure, other related features, aspects, and elements will be apparent to those skilled in the art. For example, it should be understood that additional aspects may be provided by combination of any two or more aspects described below.

[0005] According to one aspect, a method for use in a network node is provided, comprising: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and the value of the delay between the network node and the second network entity, the location of the second network entity being indicated by the second information.

[0006] After the method provided in this embodiment is used, the network node can accurately determine the CN PDB based on the first information and the second information to support the configuration of scheduling and link layer functions.

[0007] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0008] In some embodiments, the method further includes: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0009] In some embodiments, the network node is a gNodeB (gNB).

[0010] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0011] In some embodiments, the first network entity is a user plane function (UPF).

[0012] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0013] In some embodiments, first information and / or second information are obtained from a third network entity.

[0014] In some embodiments, the third network entity is a Session Management Function (SMF).

[0015] In some embodiments, the method further includes: obtaining a value for the packet delay budget (PDB); and determining a value for the access network packet delay budget (AN PDB) based on the value of the PDB and the value of the CN PDB.

[0016] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0017] In some embodiments, the location of a network node is its current location.

[0018] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0019] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0020] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0021] According to one aspect, a method for use in a third network entity is provided, comprising: obtaining first information and second information, the first information indicating a value of delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of core network packet delay budget (CNPDB); and providing the first information and the second information to network nodes.

[0022] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0023] In some embodiments, the network node is a gNodeB (gNB).

[0024] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0025] In some embodiments, the first network entity is a user plane function (UPF).

[0026] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0027] In some embodiments, the third network entity is a Session Management Function (SMF).

[0028] In some embodiments, the method further includes: obtaining the value of the packet delay budget (PDB); and providing the value of the PDB to the network node.

[0029] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0030] In some embodiments, the location of a network node is its current location.

[0031] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0032] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0033] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0034] According to one aspect, an apparatus is provided, comprising components for performing: obtaining first information and second information, the first information indicating a value of delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of delay indicated by the first information and the value of delay between a network node and the second network entity, the location of the second network entity being indicated by the second information.

[0035] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0036] In some embodiments, the system further includes a component for performing the following: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0037] In some embodiments, the network node is a gNodeB (gNB).

[0038] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0039] In some embodiments, the first network entity is a user plane function (UPF).

[0040] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0041] In some embodiments, first information and / or second information are obtained from a third network entity.

[0042] In some embodiments, the third network entity is a Session Management Function (SMF).

[0043] In some embodiments, the system further includes components for performing the following: obtaining a value for the packet delay budget (PDB); and determining a value for the access network packet delay budget (AN PDB) based on the value of the PDB and the value of the CN PDB.

[0044] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0045] In some embodiments, the location of a network node is its current location.

[0046] In some embodiments, the system further includes a component for performing the following: obtaining third information indicating the identity of the first network entity.

[0047] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0048] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0049] According to one aspect, an apparatus including application functions is provided, wherein the apparatus includes components for performing: obtaining first information and second information, the first information indicating a value of delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of core network packet delay budget (CN PDB); and providing the first information and the second information to network nodes.

[0050] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0051] In some embodiments, the network node is a gNodeB (gNB).

[0052] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0053] In some embodiments, the first network entity is a user plane function (UPF).

[0054] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0055] In some embodiments, the third network entity is a Session Management Function (SMF).

[0056] In some embodiments, the method further includes: obtaining the value of the packet delay budget (PDB); and providing the value of the PDB to the network node.

[0057] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0058] In some embodiments, the location of a network node is its current location.

[0059] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0060] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0061] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0062] According to one aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: obtain first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determine a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and the value of the delay between a network node and the second network entity, the location of the second network entity being indicated by the second information.

[0063] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0064] In some embodiments, the apparatus is configured to: determine a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0065] In some embodiments, the network node is a gNodeB (gNB).

[0066] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0067] In some embodiments, the first network entity is a user plane function (UPF).

[0068] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0069] In some embodiments, first information and / or second information are obtained from a third network entity.

[0070] In some embodiments, the third network entity is a Session Management Function (SMF).

[0071] In some embodiments, the apparatus is configured to: obtain a value of the packet delay budget (PDB); and, based on the value of the PDB and the value of the CN PDB, determine a value of the access network packet delay budget (AN PDB).

[0072] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0073] In some embodiments, the location of a network node is its current location.

[0074] In some embodiments, the device is configured to: obtain third information indicating the identity of the first network entity.

[0075] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0076] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0077] According to one aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: obtain first information and second information, the first information indicating a value of delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of core network packet delay budget (CN PDB); and provide the first information and the second information to network nodes.

[0078] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0079] In some embodiments, the network node is a gNodeB (gNB).

[0080] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0081] In some embodiments, the first network entity is a user plane function (UPF).

[0082] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0083] In some embodiments, the third network entity is a Session Management Function (SMF).

[0084] In some embodiments, the apparatus is configured to: obtain the value of the packet delay budget (PDB); and provide the value of the PDB to the network node.

[0085] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0086] In some embodiments, the location of a network node is its current location.

[0087] In some embodiments, the device is configured to: obtain third information indicating the identity of the first network entity.

[0088] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0089] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0090] According to one aspect, a computer-readable medium is provided, the computer-readable medium including instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and the value of the delay between a network node and the second network entity, the location of the second network entity being indicated by the second information.

[0091] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0092] In some embodiments, the system further includes a component for performing the following: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0093] In some embodiments, the network node is a gNodeB (gNB).

[0094] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0095] In some embodiments, the first network entity is a user plane function (UPF).

[0096] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0097] In some embodiments, first information and / or second information are obtained from a third network entity.

[0098] In some embodiments, the third network entity is a Session Management Function (SMF).

[0099] In some embodiments, the system further includes components for performing the following: obtaining a value for the packet delay budget (PDB); and determining a value for the access network packet delay budget (AN PDB) based on the value of the PDB and the value of the CN PDB.

[0100] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0101] In some embodiments, the location of a network node is its current location.

[0102] In some embodiments, the system further includes a component for performing the following: obtaining third information indicating the identity of the first network entity.

[0103] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0104] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0105] According to one aspect, a computer-readable medium is provided, the computer-readable medium including instructions that, when executed by a device, cause the device to perform at least the following: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of a core network packet delay budget (CN PDB); and providing the first information and the second information to network nodes.

[0106] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0107] In some embodiments, the network node is a gNodeB (gNB).

[0108] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0109] In some embodiments, the first network entity is a user plane function (UPF).

[0110] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0111] In some embodiments, the third network entity is a Session Management Function (SMF).

[0112] In some embodiments, the method further includes: obtaining the value of the packet delay budget (PDB); and providing the value of the PDB to the network node.

[0113] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0114] In some embodiments, the location of a network node is its current location.

[0115] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0116] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0117] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0118] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor being configured, together with the at least one memory and the computer program code, to cause the apparatus to at least perform: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and the value of the delay between a network node and the second network entity, the location of the second network entity being indicated by the second information.

[0119] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0120] In some embodiments, the system further includes a component for performing the following: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0121] In some embodiments, the network node is a gNodeB (gNB).

[0122] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0123] In some embodiments, the first network entity is a user plane function (UPF).

[0124] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0125] In some embodiments, first information and / or second information are obtained from a third network entity.

[0126] In some embodiments, the third network entity is a Session Management Function (SMF).

[0127] In some embodiments, the system further includes components for performing the following: obtaining a value for the packet delay budget (PDB); and determining a value for the access network packet delay budget (AN PDB) based on the value of the PDB and the value of the CN PDB.

[0128] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0129] In some embodiments, the location of a network node is its current location.

[0130] In some embodiments, the system further includes a component for performing the following: obtaining third information indicating the identity of the first network entity.

[0131] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0132] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0133] According to one aspect, an apparatus is provided, comprising: at least one processor, at least one memory including computer program code, and at least one interface configured to communicate with at least another apparatus, the at least one processor being configured, together with the at least one memory and the computer program code, to cause the apparatus to perform at least the following: obtaining first information and second information, the first information indicating a value of delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of core network packet delay budget (CN PDB); and providing the first information and the second information to network nodes.

[0134] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0135] In some embodiments, the network node is a gNodeB (gNB).

[0136] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0137] In some embodiments, the first network entity is a user plane function (UPF).

[0138] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0139] In some embodiments, the third network entity is a Session Management Function (SMF).

[0140] In some embodiments, the method further includes: obtaining the value of the packet delay budget (PDB); and providing the value of the PDB to the network node.

[0141] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0142] In some embodiments, the location of a network node is its current location.

[0143] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0144] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0145] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0146] According to one aspect, a computer-readable medium is provided, the computer-readable medium including instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity; and determining a value of a core network packet delay budget (CN PDB) based on the value of the delay indicated by the first information and the value of the delay between a network node and the second network entity, the location of the second network entity being indicated by the second information.

[0147] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0148] In some embodiments, the system further includes a component for performing the following: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0149] In some embodiments, the network node is a gNodeB (gNB).

[0150] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0151] In some embodiments, the first network entity is a user plane function (UPF).

[0152] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0153] In some embodiments, first information and / or second information are obtained from a third network entity.

[0154] In some embodiments, the third network entity is a Session Management Function (SMF).

[0155] In some embodiments, the system further includes components for performing the following: obtaining a value for the packet delay budget (PDB); and determining a value for the access network packet delay budget (AN PDB) based on the value of the PDB and the value of the CN PDB.

[0156] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0157] In some embodiments, the location of a network node is its current location.

[0158] In some embodiments, the system further includes a component for performing the following: obtaining third information indicating the identity of the first network entity.

[0159] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0160] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0161] According to one aspect, a computer-readable medium is provided, the computer-readable medium including instructions that, when executed by a device, cause the device to perform at least the following: obtaining first information and second information, the first information indicating a value of a delay between a first network entity and a second network entity, the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine a value of a core network packet delay budget (CN PDB); and providing the first information and the second information to network nodes.

[0162] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0163] In some embodiments, the method further includes: determining a value of the delay between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0164] In some embodiments, the network node is a gNodeB (gNB).

[0165] In some embodiments, the gNB is included in a satellite, or an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0166] In some embodiments, the first network entity is a user plane function (UPF).

[0167] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0168] In some embodiments, the third network entity is a Session Management Function (SMF).

[0169] In some embodiments, the method further includes: obtaining the value of the packet delay budget (PDB); and providing the value of the PDB to the network node.

[0170] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0171] In some embodiments, the location of a network node is its current location.

[0172] In some embodiments, the method further includes: obtaining third information that indicates the identity of the first network entity.

[0173] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0174] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0175] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions that, when executed by a device, cause the device to perform at least the method according to any of the foregoing aspects.

[0176] Many different aspects have been described above. As previously mentioned, it should be understood that additional aspects can be provided through any combination of two or more of the aforementioned aspects. Other features, aspects, and elements will become apparent below. Attached Figure Description

[0177] Some exemplary embodiments will now be described by way of non-limiting and illustrative example only with reference to the accompanying drawings, in which:

[0178] Figure 1 This illustrates a representation of a fifth-generation communication system;

[0179] Figure 2 The illustration shows a method for using some example embodiments. Figure 1 The representation of a communication system device;

[0180] Figure 3 A representation of an apparatus according to some example embodiments is shown;

[0181] Figure 4 The composition of a PDB according to some example embodiments is shown;

[0182] Figure 5A A regenerated NTN architecture according to some example embodiments is shown;

[0183] Figure 5B An example composition of a PDB in a 5G NTN regenerative architecture according to an embodiment of the present disclosure is shown;

[0184] Figure 6 The PDU session establishment process according to an embodiment of the present disclosure is illustrated;

[0185] Figure 7A A scheme for obtaining the distance between the NTN-GW and the gNB according to an embodiment of the present disclosure is shown;

[0186] Figure 7B A scheme for obtaining the distance between the NTN-GW and the gNB according to an embodiment of the present disclosure is shown;

[0187] Figure 8 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0188] Figure 9 A flowchart of a method according to an embodiment of the present disclosure is shown; and

[0189] Figure 10 A schematic representation of an apparatus according to some example embodiments is shown.

[0190] Figure 11A flowchart of a method according to an embodiment of the present disclosure is shown.

[0191] Figure 12 A schematic representation of a non-volatile memory medium storing instructions and / or parameters is shown. Detailed Implementation

[0192] The following example embodiments will be described with reference to communication devices capable of communicating with a communication system. To aid in a better understanding of the example embodiments in the context, a fifth-generation communication system (5GS), its access network and 5G core network (5GC), and the communication devices will be referred to... Figure 1 , Figure 2 and Figure 3 This is described for illustrative purposes. It should be noted that the methods and apparatus in each embodiment of this disclosure are not limited to applications in 5G, but can also be applied to 6G and later communication systems.

[0193] Figure 1 A schematic representation of a 5GS is shown. The 5GS may include a user equipment (UE) 100 (or terminal), an access network (such as a (Radio) Access Network ((R)AN) 101 or a Next Generation Radio Access Network (NG-RAN)), a core network (CN) 102 or 5GC, and one or more application functions (AFs) 103. AFs 103 may be deployed in the 5GS as trusted AFs (or, in this example, untrusted AFs). In addition, AFs 103 may be deployed or hosted on one or more application servers in a data network (DN) 104. The 5GS connects the UE 100 to the data network 104 via the access network and 5GC 102.

[0194] (R)AN 101 may include one or more radio access nodes, such as gNBs. A gNB may include one or more gNB distributed units (DUs) connected to one or more gNB centralized units (CUs).

[0195] 5GC 102 may include the following network functions: Network Slice Selection Function (NSSF), not shown; Network Exposure Function (NEF) 105; Network Repository Function (NRF), not shown; Policy Control Function (PCF), not shown; Unified Data Management (UDM) 106; (multiple) AFs 103; Authentication Server Function (AUSF) 107; Access and Mobility Management Function (AMF) 108; Session Management Function (SMF) 109; and User Plane Function (UPF) 110. Figure 1 The various interfaces (N1, N2, etc.) implemented between the various elements of the system are also shown.

[0196] Figure 2 The diagram illustrates the control / implementation process. Figure 1 Access network 102 (for example, Figure 1 The illustration shows an example of a control device 200 for a (network) function or network entity of (RAN) 101 or Next Generation RAN (NG-RAN). The control device 200 may include: at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, one or more processors 212, 213, and a network interface 214. Processors 212 and 213 may be coupled to RAM 211a and ROM 211b. Processors 212 and 213 may be configured to execute software code 215 that may be stored in ROM 211b. Execution of software code 215 may, for example, cause device 200 to perform operations for controlling the (network) functions of access network 102. Control device 200 may interconnect with another control device 200 for controlling another (network) function or another network entity of access network 102. In some embodiments, each (network) function or each network entity of access network 102 is deployed or hosted on a corresponding control device 200. In an alternative embodiment, two or more (network functions) or network entities of access network 102 may share the same control device.

[0197] Figure 3 An example of a communication device 300 is illustrated, such as Figure 1 UE 100. Communication device 300 may be part of another device capable of transmitting and receiving radio signals. Non-limiting examples of communication device 300 include mobile stations (MS) or mobile devices, such as mobile phones or so-called "smartphones," computers provided with wireless interface cards or other wireless interface facilities (e.g., USB (Universal Serial Bus) dongles), personal data assistants (PDAs) or tablet computers provided with wireless communication capabilities, machine-type communication (MTC) devices, Internet of Things (IoT) type communication devices, or any combination thereof. Communication device 300 may include transceivers for transmitting and / or receiving wireless signals carrying, for example, communications (e.g., radio signals). Communications may be one or more of voice, email, text messages, multimedia data, machine data, etc.

[0198] The communication device 300, via appropriate means for receiving and transmitting wireless signals, can receive and transmit wireless signals through an air interface or radio interface 307. Figure 3In the diagram, the transceiver is schematically designated as block 306. Transceiver 306 may include, for example, a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the communication device 300 and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna.

[0199] The communication device 300 may be implemented using at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for use in the software and hardware-assisted execution of the tasks it is designed to perform, including access to the access network 102 (e.g., Figure 1 The processor 301 controls access to and communication with (R)AN 101 and other communication devices. The processor 301 is coupled to RAM 302b and ROM 302a. The processor 301 can be configured to execute software code 308, which can be stored in ROM 302a. The software code 308 can, for example, allow the execution of one or more operations of the communication device 300.

[0200] Processor 301, ROM 302a and RAM 302b, transceiver 306, and other circuitry of the communication device (e.g., modem) may be provided on a circuit board, in a chipset, or on a system-on-a-chip. The circuit board, chipset, or system-on-a-chip is designated by the number 304. The communication device 300 may optionally have a user interface, such as a keyboard 305, a touchscreen or touchpad, or a combination thereof. Depending on the type of communication device 300, one or more of a display, speaker, and microphone may optionally be provided.

[0201] The value of the Packet Delay Budget (PDB) defines: the time a packet spends in a given period of time. Figure 1 The PDB value represents the upper bound or maximum value of the possible delay between UE 100 and CN 102 (e.g., see 3GPP TS23.501: Delay time of packets between UE 100 and the N6 termination point or interface at UPF 110 in CN 102). In the case of 3GPP access, the PDB value is used to configure scheduling and link layer functions (e.g., setting scheduling priority weights and Hybrid Automatic Repeat Request (HARQ) target operating point). The PDB value applies to downlink (DL) packets transmitted from CN 102 (e.g., UPF 110) through the N6 interface, and uplink (UL) packets transmitted by UE 100 to CN 102. For a given 5G Quality of Service (QoS) identifier (5QI), the PDB value is the same for both UL and DL.

[0202] Figure 4The composition of the PDB value in this disclosure is illustrated. In 3GPP, the PDB value comprises two parts: the Access Network Packet Delay Budget (AN PDB) value and the Core Network Packet Delay Budget (CN PDB) value. The AN PDB value defines the upper bound or maximum value of the time that packets may be delayed between UE 100 and (R)AN 101. The CN PDB value defines the upper bound or maximum value of the time that packets may be delayed between CN 102 and (R)AN 101. The AN PDB value is determined by subtracting the CN PDB value from the PDB value (e.g., AN PDB = PDB - CN PDB). The CN PDB value is static / fixed or dynamically provided to (R)AN 101 when a Packet Data Unit (PDU) session or QoS flow needs to be created or modified. For Guaranteed Stream Bit Rate (GBR) QoS flows using the Delay-Critical Resource type, a dynamic value for the CN PDB can be used to obtain a more accurate delay budget available to (R)AN 101. This dynamic value for the CN PDB represents the delay between the UPF110 termination N6 for the QoS flow and (R)AN 101. If the CN PDB is used for the QoS flow, (R)AN 101 can apply a dynamic value to the CN PDB instead of a static value. Different or the same dynamic values ​​can be configured accordingly for the CN PDB in the uplink direction and for the CN PDB in the downlink direction. The dynamic value of the CN PDB can be configured for (R)AN 101, or it can be provided, for example, by SMF 109 during the PDU session creation process, PDU session modification process, or Xn / N2 handover and service request process.

[0203] Optionally, the evaluation of the PDB value may also take into account at least one processing latency, such as that from each node (e.g., Figure 4 The internal time delays of UE 100, (R)AN 101, and CN 102 in the dataset. Optionally, the evaluation of the CN PDB may also consider at least one processing delay, such as that from each node (e.g., Figure 4 The internal time delays of (R)AN 101 and CN 102 in the evaluation of AN PDB can also be considered at least one processing delay, such as that from each node (e.g., Figure 4 The internal time delay of (R)AN 101 and UE 100. However, because the internal time delay of each node is typically much smaller than that of UE 100. Figure 1 The transmission time delay between nodes in the network is negligible, so the processing delay can be ignored when evaluating PDB / AN PDB / CNPDB.

[0204] Non-terrestrial networks (NTNs) include wireless communication systems that provide non-terrestrial radio access to UEs via NTN payloads integrated into airborne platforms (e.g., high-altitude platforms (HAPs)) or spaceborne NTN vehicles (e.g., satellites) and NTN gateways (NTN gateways or NTN-GWs). NTN vehicles operate above the Earth's surface, using airborne platforms in Earth orbit. These platforms can include satellites in low Earth orbit (LEO), medium Earth orbit (MEO), geostationary orbit (GEO), and high-elliptical orbit (HEO), as well as HAPs and drones. Satellites can be in geosynchronous orbit (GSO) or non-geosynchronous orbit (NGSO). Here are some details about the different orbits used for NTNs:

[0205] LEO is a circular orbit located at altitudes typically ranging from 500 km to 2,000 km. Compared to MEO and HEO, LEO offers lower latency and better link budgets, but requires a larger number of satellites for global coverage.

[0206] MEO: A circular orbit located at an altitude of approximately 8,000 km to 20,000 km. Compared to LEO, MEO provides wider coverage but has longer latency / delay due to higher propagation delay.

[0207] HEOs have highly elliptical orbits, which makes them much farther from the Earth's surface, at altitudes exceeding 36,000 km.

[0208] GEO (also known as geosynchronous equatorial orbit) is a circular orbit located 35,786 km above the Earth's equator and follows the direction of the Earth's rotation. GEO satellites appear stationary relative to fixed points on Earth, but there is still a slight orbital movement.

[0209] A geostationary orbit (GSO) is a circular orbit approximately 35,786 kilometers above the Earth's surface. At any inclination, a geostationary orbit is synchronized with the Earth's rotation. More specifically, the time it takes for the Earth to complete one rotation around its axis is 23 hours, 56 minutes, and 4.09 seconds, the same as a satellite in geostationary orbit. A GSO can have any inclination, and therefore, a key difference from a GEO is that a GEO is always located in the same plane as the Earth's equator.

[0210] NGSO refers to a type of satellite orbit in which the satellite is not stationary relative to the Earth's surface. Unlike geostationary satellites, which remain fixed at an altitude of 36,000 kilometers above the Earth, NGSO satellite orbits are at lower elevations. There are two main types of NGSO orbits: MEO and LEO.

[0211] Figure 5AThis illustrates a 5G NTN regenerative architecture where complete base station functionality (e.g., gNB / (R)AN functionality) is integrated into the satellite. gNB 500 (in this example) Figure 5A The satellite (in the image) can connect to CN 102 on the ground via the Non-Terrestrial Network Gateway (NTN-GW) 502. Figure 5A In this configuration, UE 100 can connect to gNB 500 via the Uu interface. gNB 500 can connect to NTN-GW 502 (e.g., gNB 500 connects to NTN-GW 502A and / or NTN-GW 502B via route 1 and / or route 2). NTN-GW 502 (e.g., NTN-GW 502A and / or NTN-GW 502B) can connect to CN 102. When gNB 500 connects to NTN-GW 502, gNB 500 is assigned one or more IP addresses registered in NTN-GW 502. This ensures that control plane (CP) / user plane (UP) traffic from CN 102 (with destination IP addresses set to the gNB's IP address) is routed to the correct NTN-GW and then further forwarded to gNB 500. The gNB 500 can be assigned as a separate IP address for both the CP (Content Provider) and UP (User Provider).

[0212] Figure 5B This illustrates an example composition of PDB values ​​in a 5G NTN regenerative architecture. (Compared to...) Figure 4 Similarly, PDB = AN PDB + CNPDB, and Figure 5B The CN PDB value is dynamic: the CN PDB value includes a first CN PDB value (Delay1 in the following embodiment) and a second CN PDB value (Delay2 in the following embodiment). Delay1 defines the upper bound or maximum value of the time that the packet may be delayed between NTN-GW 502 and CN 102 (specifically, UPF 110 in CN 102). Delay2 defines the upper bound or maximum value of the time that the packet may be delayed between NTN-GW 502 and gNB 500. It should be noted that the distance between NTN-GW 502 and CN 102 in Delay1 is relatively stable / constant, therefore the value of Delay1 can be set to a static / fixed value. However, since the position of gNB 500 in the NGSO satellite, which is integrated in the NTN and whose position is relative to a fixed point on Earth (e.g., the position of NTN-GW 502), is dynamic or changes over time, Delay2, which depends on the distance between NTN-GW 502 and gNB 500, is dynamic.

[0213] It is foreseeable that the composition of the CN PDB values ​​(i.e., Delay1 and Delay2) can be changed to achieve the same result as... Figure 5B The same result for the PDB. For example, it can be anticipated that a portion of Delay2 will be assigned to Delay1, resulting in the same sum, i.e., CNPDB. In this scenario, for example, Delay1 may include the delay budget between CN 102 and the reference position of gNB 500, while Delay2 includes the delay budget between the reference position of gNB 500 and the current position of gNB 500.

[0214] Optionally, the reference position of gNB 500 can be any position of the satellite in orbit, that is, the reference position of gNB 500 is directly above NTN-GW 502.

[0215] The gNB 500 can also connect to different NTN-GWs. For example, in Figure 5B In this context, when the position of gNB 500 changes (e.g., the satellite moves in its orbit), gNB 500 can switch from NTN-GW 502A to NTN-GW 502B; or gNB 500 can maintain its connection with NTN-GW 502A and simultaneously initiate a connection with NTN-GW 502B. Because the land locations of NTN-GW 502A and NTN-GW 502B are different, the distances between gNB 500 and NTN-GW 502A and NTN-GW 502B are different. The Delay2 between gNB 500 and NTN-GW 502A is different from the Delay2 between gNB 500 and NTN-GW 502B. Similarly, because the positions of NTN-GW 502A and NTN-GW 502B are different, the distances between CN 102 and NTN-GW 502A and NTN-GW 502B are different. The delay 1 between CN 102 and NTN-GW 502A is different from the delay 1 between CN 102 and NTN-GW 502B.

[0216] Optionally, in some embodiments, the real-time location of other types of gNB 500 (e.g., airborne telecommunications equipment) may also change over time, not limited to satellites. All of these types of gNB 500 are described in the embodiments of this disclosure.

[0217] exist Figure 5A and Figure 5BIn the NTN regeneration architecture, because the distance between gNB 500 and NTN-GW 502 changes, it is impossible to provide gNB 500 with a static / fixed value for the CN PDB. It is also difficult to provide a dynamic value for the CN PDB from CN 102 to gNB 500, because CN 102 (e.g., SMF 109) will not know the real-time / current location of gNB 500, and the distance between gNB 500 and NTN-GW 502 changes. To obtain a more accurate CN PDB, some embodiments in this disclosure take into account the change in the location of gNB 500 during the creation of the data path between UE 100 and CN 102.

[0218] Figure 6 The PDU session creation process according to an embodiment of this disclosure is illustrated. Figure 6 During the PDU session creation process, the change in the location of gNB 500 is taken into account to determine the value of CN PDB / AN PDB.

[0219] This process assumes that UE 100 is already registered on AMF 108; therefore, unless UE 100 is registered urgently, AMF108 has already retrieved the user subscription data from UDM 106. This is presented as an example, not a limitation. Figure 6 The PDU session creation process is illustrated with the following steps:

[0220] Step 601: UE 100 sends a PDU session creation request to AMF 108;

[0221] In this disclosure, prior to step 601, gNB 500 is connected to CN 100 via NTN-GW 502, as follows: Figure 5A As shown.

[0222] Step 602: AMF 108 selects SMF 109 based on the PDU session establishment request;

[0223] Step 603: AMF 108 sends an Nsmf_PDUSession_CreateSMContext request to SMF 109;

[0224] Step 604: SMF 109 performs subscription retrieval / subscription for update between UDM 106 and SMF 109;

[0225] Step 605: SMF 109, depending on step 603, sends an Nsmf_PDUSession_CreateSMContext response or an Nsmf_PDUSession_UpdateSMContext response to AMF 108;

[0226] Step 606: SMF 109 optionally performs auxiliary PDU session authentication / authorization;

[0227] Step 607a: If the dynamic primary component carrier (PCC) will be used for the PDU session, then SMF 109 performs PCF selection;

[0228] Step 607b: SMF 109 performs the SM policy association creation process to create a session management (SM) policy association with the policy control function (PCF) and obtain the default PCC rule for the PDU session.

[0229] Step 608: SMF 109 performs UPF selection;

[0230] Step 609: SMF 109 initiates SM policy association with PCF;

[0231] Step 610a: SMF 109 sends an N4 session creation / modification request to UPF 110;

[0232] Step 610b: UPF 110 sends an N4 session creation / modification response to SMF 109;

[0233] Step 611: Namf_Communication_N1N2MessageTransfer is executed between AMF 108 and SMF 109;

[0234] In step 611, SMF 109 can send CN PDB related information to AMF 108.

[0235] Alternatively, CN PDB-related information can be sent in step 605.

[0236] CN PDB related information may include a list of the following information:

[0237] • Delayed budget information (e.g., Figure 5B (Delay1 in the middle).

[0238] • Information about the NTN-GW (e.g., the ID for NTN-GW 502, the location information of NTN-GW 502).

[0239] The delay budget information includes the static portion of the CN PDB. Since the location of the NTN-GW 502 or the reference location of the gNB 500 cannot be changed, the delay budget information (e.g., delay 1) is also static. In step 611, the delay budget information is not mandatory, and it can be pre-stored in the gNB 500 prior to step 611. For example, in Figure 6 This occurs before the PDU session creation process or in step 611 of another PDU session creation process.

[0240] The information from the NTN-GW is used by the gNB 500 to determine the CN PDB in subsequent steps. The function of the ID used for the NTN-GW 502 is: when the gNB 500 is different from a different NTN-GW 502 (e.g., ...), Figure 5A When connecting NTN-GW 502A and NTN-GW 502B, in such cases... Figure 5A The system identifies different NTN-GWs. The ID used for NTN-GW 502 is optional in the NTN-GW information.

[0241] The location information for NTN-GW 502 can refer to any form of location information. For example, in 3GPP, the format of the location information for NTN-GW 502 can refer to the format of the NG-RAN Access Point Location (IE) as defined in TS38.455 9.2.10:

[0242] The NG-RAN Access Point Location (IE) is used to identify the geographical location of the NG-RAN access point. This NG-RAN Access Point Location (IE) can also be used to identify the geographical location of NTN-GW 502. According to TS23.032 in Table 1, the NG-RAN Access Point Location (IE) is represented as an ellipsoidal point with elevation and an indeterminate ellipsoid.

[0243] Table 1:

[0244]

[0245]

[0246] In some embodiments, the location of NTN-GW 502 can be defined using geocentric-fixed (ECEF) coordinates, and the location of the reference point can be defined using ECEF coordinates or orbital coordinates. For example, Table 2:

[0247]

[0248]

[0249]

[0250]

[0251]

[0252] Optionally, delay budget information (e.g., Delay1) applies to downlink (DL) packet delay information transmitted from CN 102 (e.g., UPF 110) to UE 100 via NTN-GW 502, and to uplink (UL) packets transmitted from UE 100 to CN 102 (e.g., UPF 110) via NTN-GW 502.

[0253] Alternatively, if Delay1 includes the delay budget between the reference location of CN 102 and gNB 500CN, and Delay2 includes the delay budget between the reference location of gNB 500 and the current location of gNB 500. In this scenario, the CN PDB related information provided by SMF 109 in step 611 may also include reference location information (e.g., reference location ID, reference location location information), and the information of NTN-GW 502 is optional or can be ignored. Step 612: AMF108 sends an N2 PDU session request (NAS message) to gNB 500;

[0254] In this step, AMF 108 can forward the CN PDB related information from step 611 along with other SMF related information to gNB 500, and gNB 500 can locally store the CN PDB related information. In addition, gNB 500 can use the CN PDB related information to determine the value of the CN PDB. For example, if the NTN-GW information includes the location information of NTN-GW 502, gNB 500 first obtains its own location information (e.g., satellite ephemeris information), and gNB 500 determines the distance between gNB 500 and the connected NTN-GW 502 based on the location information of gNB 500 and NTN-GW 502. This distance between gNB 500 and NTN-GW 502 is further used to determine the Delay2 between gNB 500 and NTN-GW 502 (e.g., ...). Figure 5B (Delay2 in the equation). Delay2 = distance between gNB 500 and NTN-GW / signal speed.

[0255] Alternatively, the signal speed is the speed of light.

[0256] Optionally, the location information of gNB 500 can be used as the location information of NTN-GW 502 in the format of Table 1 or Table 2.

[0257] Optionally, the IE type and reference for the altitude of gNB 500 in Table 1 can be adjusted according to different orbit types (e.g., LEO). <MEO<HEO)。

[0258] In some embodiments, gNB 500 can determine Delay2 based on CN PDB related information (e.g., NTN-GW information) and gNB 500 location information. For example, gNB 500 can determine Delay2 by searching for the value of Delay2 in a pre-stored table in gNB 500 (e.g., Table 3 below), or by determining Delay2 from a preset formula.

[0259] Table 3 below shows how to obtain Delay2 from a pre-stored table:

[0260] Table 3:

[0261]

[0262] For example, in Table 3, gNB 500 can use the location of NTN-GW502 with at least one IE / group name from Table 1 / Table 2, along with the location of gNB 500, to search for the value of Delay2. For example, (A1, B1, C1...) is (latitude symbol, latitude, longitude...).

[0263] Figure 7A and Figure 7B Two other different schemes are shown to obtain the distance between the NTN-GW 502 and the gNB 500. Figure 7A and Figure 7B Based on the location information of NTN-GW 502 and gNB 500, gNB 500 can calculate the distance between NTN-GW 502 and gNB 500 by setting up the ECEF system. For example, in Figure 7A In the diagram, NTN-GW 502 is located at point O, and gNB 500 is located at point B'. After obtaining the distances to AO, OC, and OD' based on the latitude / longitude / altitude / delta value between the location information of gNB 500 and NTN-GW 502, gNB can be calculated using formula OB'. 2 =AO 2 +OC 2 +OD' 2 Determine the distance between gNB 500 and NTN-GW 502. Therefore, gNB 500 can calculate the transmission delay (e.g., Delay2) between gNB 500 and NTN-GW 502 based on the value of OB' (Delay2 = OB' / signal speed). Finally, gNB 500 can further determine CN PDB = Delay1 + Delay2.

[0264] Alternatively, the signal speed is the speed of light.

[0265] Figure 7B Another method for obtaining the distance between gNB 500 and NTN-GW 502 is shown. First, gNB 500 can obtain a reference position of gNB 500 (e.g., the position of a satellite directly above NTN-GW 502), which is the minimum distance between gNB 500 and NTN-GW 502 (e.g., ...). Figure 7B First, gNB 500 can obtain the current / real-time offset between gNB 500 and NTN-GW 502 (e.g., after the satellite moves from D' to B', the satellite can obtain the value of angle B'OD' or the distance between D'B' based on the change in the satellite's position information). Finally, gNB 500 can determine the distance between gNB 500 and NTN-GW 502 based on the offset of gNB 500's position, the reference position of gNB 500, and the position information of NTN-GW 502. After obtaining the distance between NTN-GW 502 and gNB 500, gNB 500 can further determine Delay2 based on the signal speed (e.g., Delay2 = distance between NTN-GW 502 and gNB 500 / signal speed).

[0266] Alternatively, the reference position of gNB 500 can be any position of the satellite in orbit.

[0267] Alternatively, the signal speed is the speed of light.

[0268] Optionally, Delay2 applies to downlink (DL) Delay2 received by NTN-GW 500 from UE 100, and uplink (UL) Delay2 transmitted by UE 100 to NTN-GW 500. If Delay1 is DL Delay1, then Delay2 can be DL Delay2; and if Delay1 is UL Delay1, then Delay2 can be UL Delay2. The value of UL Delay2 and the value of DL Delay2 can be the same or different, and the value of UL Delay1 and the value of DL Delay1 can be the same or different.

[0269] In some embodiments, gNB 500 may determine CN PDB based on Delay2 in step 612 and Delay1 in step 611 (e.g., CN PDB = Delay1 + Delay2).

[0270] Alternatively, if the delay budget information in step 611 is Delay1, this delay budget information includes the delay budget between CN 102 (e.g., UPF 110) and the reference position associated with gNB 500. In step 612, gNB 500 can obtain the delay budget between its reference position and its current / real-time position. For example, the reference position of gNB 500 is the position of a satellite directly above the position of NTN-GW 502, where the distance between NTN-GW 502 and gNB 500 is the shortest (e.g., ...). Figure 7B (Position D' in the middle). gNB 500 has obtained Delay1 between CN102 and the reference position of gNB 502 from the delay budget information in step 611, and then gNB 500 can obtain the distance between gNB 500's current / real-time position and gNB 500's reference position (e.g., position D' in the middle). Figure 7B The distance to D'B' in the signal is used to determine the value of Delay2 (Delay2 = distance to D'B' / signal speed). Finally, the gNB500 can determine the CN PDB by adding Delay1 between CN 102 and the reference position of the gNB500, and Delay2 between the current position of the gNB500 and the reference position of the gNB500.

[0271] Alternatively, the reference position of gNB 500 can be any position of gNB 500 in the track.

[0272] Optionally, to obtain a more accurate CN PDB, the gNB 500 can remove the processing latency of each node in the network system, such as the processing latency of CN 102 (e.g., SMF 109, UPF 110, NTN-GW 502, etc.) and the processing latency of the gNB 500. This is because the value of the processing latency is much smaller than the values ​​of Delay1 and Delay2. In some embodiments, the processing latency can be ignored to save processing time for the gNB 500.

[0273] Optionally, the gNB 500 can store timestamps based on Delay2 or CN PDB for resource allocation / scheduling.

[0274] In step 612, the determination of Delay2 by gNB 500 will be of great significance for gNB 500 to determine CN PDB in order to perform more accurate scheduling and resource allocation between gNB 500 and UE 100.

[0275] Step 613: AN-specific resource establishment (PDU session creation acceptance) is performed between gNB 500 and UE 100;

[0276] Step 614: gNB 500 sends an N2 PDU session response to AMF 108;

[0277] Step 615: AMF 108 sends an Nsmf_PDUSession_UpdateSMContext request to SMF 109;

[0278] Step 616a: SMF 109 sends an N4 session modification request to UPF 110;

[0279] Step 616b: UPF 120 sends an N4 session modification response to SMF 109;

[0280] Step 616c: Registration is performed between SMF 109 and UDM 106;

[0281] Step 617: SMF 109 sends Nsmf_PDUSession_UpdateSMContext to AMF 108;

[0282] Step 618: SMF 109 sends Nsmf_PDUSession_SMContextStatusNotify to AMF 108;

[0283] Step 619: SMF 109 sends IPv6 address configuration to UE 100;

[0284] Step 620: SMF 109 initiates SM policy association;

[0285] Step 621: Unsubscription is performed between SMF 109 and UDM 106.

[0286] It should be noted that in actual implementation, the steps illustrated can be selectively executed.

[0287] The dynamic / real-time CN PDB in this disclosure serves to enable better resource allocation by the gNB 500. For example, the dynamic / real-time CN PDB can be used to reserve resources accordingly for Guaranteed Bit Rate Data Radio Bearers (GBR DRBs). Another function of the dynamic CN PDB is that the gNB 500 can predict potential changes to the CN PDN from when the gNB begins serving UE 100 (e.g., when a satellite enters the area) until the gNB 500 ceases service (e.g., when a satellite leaves the area). Based on this accurate value of the CN PDB, the gNB 500 can perform better scheduling and resource allocation. Furthermore, in this disclosure, CN 102 (e.g., SMF 109) does not need to obtain detailed information about the gNB 500 (e.g., satellite location information).

[0288] After the PDU session is established, the UE 100 can receive DL packets for the gNB 500. The gNB 500 can also determine a dynamic / real-time CN PDB and use the dynamic CN PDB to schedule (multiple) specific DL packets. For example, the gNB 500 determines the CN PDB for each received DL packet (or for packets received during a timing window, such as a 5-ms timing window).

[0289] After the gNB 500 obtains the dynamic / real-time CN PDB, the accurate AN PDB can be determined based on this dynamic / real-time CN PDB. For example, after obtaining the total PDB associated with the QoS flow from UE 100 to CN 102 (e.g., SMF 109), the gNB 500 can subtract the CN PDB value from the total PDB to determine the AN PDB value (e.g., ANPDB = PDB - CN PDB). The gNB 500 can also use the AN PDB value to schedule the delivery of DL packets to UE 100, and / or schedule resources for UL packets sent from UE 100.

[0290] Optionally, if CN PDB is used for DL, then DL AN PDB = DL total PDB - DL CN PDB. If CN PDB is used for UL, then UL AN PDB = UL total PDB - UL CN PDB. The value of DL AN PDB can be the same as or different from UL AN PDB.

[0291] For example, in one embodiment, UE1 and UE2 have the same QoS, but are in different locations referenced by satellites. For UE1, the CN PDB obtained by the satellite will change from 150ms to 120ms from 10:00 to 10:03, and then change back to 150ms from 10:03 to 10:06; for UE2, the CN PDB obtained by the gNB will change from 120ms to 150ms from 10:00 to 10:03, and then change back to 120ms from 10:03 to 10:06.

[0292] In another embodiment, UE3 and UE4 have the same QoS, but in similar locations referenced by the satellite: for both UE3 and UE4, the CN PDB obtained by the satellite will change from 150ms to 120ms from 10:00 to 10:03, and then from 120ms to 150ms from 10:03 to 10:06.

[0293] The satellite can perform scheduling and resource allocation accordingly for UE1 and UE2, UE3 and UE4. For example, radio resource blocks can be shared for UE1 and UE2, but there is no possibility of sharing resources for UE3 and UE4.

[0294] Figure 8 A flowchart of a method according to an embodiment of the present disclosure is shown. Figure 8 The method shown can be used / applied in a network node (e.g., gNB 500) and includes the following steps:

[0295] Step 801: Obtain first location information, which is used to indicate the location of the second network entity or the reference location of the network node;

[0296] Optionally, the first location information is sent to the network node by other network entities (e.g., SMF) or is pre-stored in the network node.

[0297] Step 802: Obtain second location information, which is used to indicate the current location of the network node;

[0298] Step 803: Determine the value of the core network packet delay budget (CN PDB) based on the first location information and the second location information.

[0299] exist Figure 8 In this system, the gNB 500 can determine the value of the CN PDB based on its current location information. After determining the CN PDB value, the gNB 500 can allocate resources more accurately based on the CN PDB.

[0300] In some embodiments, the method further includes:

[0301] Step 804: Obtain the network delay budget value between the reference position of the second network entity or network node and the first network entity;

[0302] Step 805: Determine the value of the core network packet delay budget (CN PDB) based on the first location information, the second location information, and the network delay budget.

[0303] In some embodiments, the network delay budget value between the reference location of the second network entity or network node and the first network entity is received from the third network entity.

[0304] In some embodiments, first location information is received from a third network entity, which is used to indicate the location of a second network entity or a reference location of a network node.

[0305] In some embodiments, the method further includes:

[0306] Step 806: Obtain the value of the Packet Delay Budget (PDB) from the third network entity. The value of the Packet Delay Budget (PDB) is used to indicate the delay budget between the user equipment connected to the network node and the first network entity.

[0307] In some embodiments, the value of the packet delay budget (PDB) is sent to the network node by other network entities (e.g., SMF 109) or is pre-stored in the network node.

[0308] Step 807: Determine the value of the access network packet delay budget (AN PDB) based on the values ​​of the PDB and CN PDB.

[0309] In some embodiments, the second location information is the current location of the network node or the offset location of the network node.

[0310] In some embodiments, the first location information further includes at least one of the following: the identity information of the second network entity, or the identity information of the reference location of the network node.

[0311] In some embodiments, the value of CN PDB is related to the uplink direction from the network node to the first network entity; or, the value of CN PDB is related to the downlink direction from the first network entity to the network node.

[0312] In some embodiments, a network node is a radio access network (RAN) node on an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0313] In some embodiments, the first network entity is a user plane function (UPF).

[0314] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0315] In some embodiments, the third network entity is a Session Management Function (SMF).

[0316] In some embodiments, the network latency budget between the first network entity and the second network entity is the latency of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0317] In some embodiments, the first location information is obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0318] Figure 9 A flowchart of a method according to an embodiment of the present disclosure is shown. Figure 9 The method shown can be used / applied to third network entities and includes the following steps:

[0319] Step 901: Obtain first location information, which is used to indicate the location of the second network entity or the reference location of the network node;

[0320] Step 902: Provide the network node with first location information; wherein the first location information is used together with second location information to determine the value of the core network packet delay budget (CN PDB); wherein the second location information is used to indicate the current location of the network node.

[0321] In this embodiment, CN 102 (e.g., SMF 109) can provide gNB 500 with the location information of NTN-GW 502, which is used to determine a more accurate value of CN PDB for resource allocation.

[0322] In some embodiments, the method further includes:

[0323] Step 903: Obtain the network delay budget value between the reference position of the second network entity or network node and the first network entity;

[0324] Step 904: Provide the network delay value to the network node; wherein the network delay value is used together with the first location information and the second location information to determine the core network packet delay budget value.

[0325] In some embodiments, the first location information further includes: the identity information of the second network entity, or the identity information of the reference location of the network node.

[0326] In some embodiments, the value of CN PDB is related to the uplink direction from the network node to the second network entity; or the value of CN PDB is related to the downlink direction from the second network entity to the network node.

[0327] In some embodiments, a network node is a radio access network (RAN) node on an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0328] In some embodiments, the first network entity is a user plane function (UPF).

[0329] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0330] In some embodiments, the third network entity is a Session Management Function (SMF).

[0331] In some embodiments, the network latency budget between the first network entity and the second network entity is the latency of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0332] In some embodiments, the first location information is received during a Packet Data Unit (PDU) session establishment process or a PDU session modification process.

[0333] Figure 10 A flowchart of a method according to an embodiment of the present disclosure is shown. Figure 10 The method shown can be used / applied to network nodes (e.g., gNB 500) and includes the following steps:

[0334] Step 1001: Obtain first information and second information, wherein the first information indicates the value of the delay between the first network entity and the second network entity, and the second information indicates the location of the second network entity;

[0335] Step 1002: Determine the value of the core network packet delay budget (CN PDB) based on the delay value indicated by the first information and the delay value between the network node and the second network entity, the location of which is indicated by the second information.

[0336] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0337] In some embodiments, the method further includes:

[0338] Step 1003: Determine the delay value between the network node and the second network entity based on the location of the second network entity and the location of the network node.

[0339] In some embodiments, the network node is a gNodeB (gNB).

[0340] In some embodiments, the gNB is included in a satellite, airborne, or spaceborne non-terrestrial network (NTN) vehicle.

[0341] In some embodiments, the first network entity is a user plane function (UPF).

[0342] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0343] In some embodiments, first information and / or second information are obtained from a third network entity.

[0344] In some embodiments, the third network entity is a Session Management Function (SMF).

[0345] In some embodiments, the method further includes:

[0346] Step 1004: Obtain the value of the Packet Delay Budget (PDB);

[0347] Step 1005: Determine the value of the access network packet delay budget (AN PDB) based on the values ​​of the PDB and CN PDB.

[0348] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0349] In some embodiments, the location of a network node is its current location.

[0350] In some embodiments, the method further includes:

[0351] Step 1006: Obtain third information, which indicates the identity of the first network entity.

[0352] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0353] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0354] Figure 11 A flowchart of a method according to an embodiment of the present disclosure is shown. Figure 11 The method shown can be used / applied to a third network entity (e.g., SMF 109) and includes the following steps:

[0355] Step 1101: Obtain first information and second information, the first information indicating the value of the delay between the first network entity and the second network entity, and the second information indicating the location of the second network entity, wherein the first information and the second information are used to determine the value of the core network packet delay budget (CN PDB);

[0356] Step 1102: Provide the first and second information to the network nodes.

[0357] In some embodiments, the value of CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

[0358] In some embodiments, the network node is a gNodeB (gNB).

[0359] In some embodiments, the gNB is included in a satellite, airborne, or spaceborne non-terrestrial network (NTN) vehicle.

[0360] In some embodiments, the first network entity is a user plane function (UPF).

[0361] In some embodiments, the second network entity is a non-terrestrial network gateway (NTN-GW).

[0362] In some embodiments, the third network entity is a Session Management Function (SMF).

[0363] In some embodiments, the method further includes:

[0364] Step 1103: Obtain the value of the Packet Delay Budget (PDB); and provide the PDB value to the network nodes.

[0365] In some embodiments, the CN PDB is an uplink CN PDB or a downlink CN PDB.

[0366] In some embodiments, the location of a network node is its current location.

[0367] In some embodiments, the method further includes:

[0368] Step 1104: Obtain third information, which indicates the identity of the first network entity.

[0369] In some embodiments, the delay value between the first network entity and the second network entity is the delay value of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

[0370] In some embodiments, the first information and the second information are obtained during the Packet Data Unit (PDU) session establishment process or the PDU session modification process.

[0371] Figure 12 A schematic representation of a non-volatile memory medium 1200a (e.g., a computer optical disc (CD) or a digital versatile optical disc (DVD)) and a non-volatile memory medium 1200b (e.g., a Universal Serial Bus (USB) Memory Stick) is shown, which stores instructions and / or parameters 1202, which, when executed by the processor, allow the processor to perform... Figure 8 , Figure 9 , Figure 10 and Figure 11 One or more steps of the method.

[0372] It should be understood that the references to various network functions (e.g., AMF, SMF, TNF, etc.) in the foregoing can be implemented by means of at least some of the functions associated with those network functions. Furthermore, means configured to implement network functions can also be configured as virtual network function instances that implement those network functions.

[0373] In some examples, the apparatus may be a network function / includes a network function / is configured to implement a network function, such as AF, NEF, UDM / UDR, AMF, etc. In this disclosure, the term "apparatus as a network function / includes a network function / is configured to implement a network function" may refer to an apparatus / device configured to provide / perform at least a portion of the functions of that network function.

[0374] It should be understood that the device may include or be coupled to other units or modules, such as radio components or radio heads, that are used in or used for transmission and / or reception. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0375] It should be noted that while some example embodiments have been described with respect to 5G networks, similar example embodiments can be applied to other networks and communication systems. Therefore, although some example embodiments have been described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, other example embodiments can be applied to any other suitable form of communication system besides the communication systems illustrated and described herein.

[0376] It should also be noted in this document that various variations and modifications may be made to the various exemplary embodiments described herein without departing from the scope of this disclosure.

[0377] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one element, or at least any two or more elements, or at least all elements. As used herein, the expression “and / or” includes any and all combinations of the listed terms, including at least any one element, at least any two or more elements, or at least all elements.

[0378] As used herein, the term “or” refers to a non-exclusive “or” unless otherwise stated (e.g., “otherwise” or “or alternatively”).

[0379] As used herein, unless explicitly stated otherwise, “perform a step in response to A” does not indicate that the step is performed immediately after “A” appears, and one or more intermediate steps may be included. Similarly, “perform a step or function based on A” does not indicate that the step or function is performed solely based on “A”, as one or more additional conditions may be included.

[0380] In general, various embodiments can be implemented in hardware or dedicated circuitry systems, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this disclosure is not limited thereto. While various aspects of this disclosure may be illustrated and described as block diagrams, flowcharts, or other graphical representations, it is well known, as a non-limiting and illustrative example, that such blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0381] As used herein, the term "circuit system" may refer to one or more, or all of the following:

[0382] (a) Implementation only in hardware circuitry (e.g., implementation only in analog and / or digital circuitry systems); and

[0383] (b) A combination of hardware circuitry and software, such as (if applicable):

[0384] (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and

[0385] (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and

[0386] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which utilize software (e.g., firmware) for operation, but may not exist when the software is not used for operation.

[0387] This definition of "circuit system" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or processors) or a portion thereof and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0388] Embodiments of this disclosure can be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products), including software routines, applets, and / or macros, can be stored in any device-readable data storage medium, and they include program instructions for performing a specific task. A computer program product may include one or more computer-executable components that, when the program is run, are configured to perform the embodiments. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0389] Furthermore, it should be noted that any box in the logical flow shown in the diagram may represent a program step, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. Software may be stored on physical media, such as memory chips, memory blocks implemented within a processor, magnetic media (such as hard disks or floppy disks), and optical media (such as DVDs and their data variants, CDs). The physical media is non-transitory.

[0390] As used herein, the term “non-transient” refers to the limitations of the medium itself (e.g., tangible, not signal-based), rather than limitations on the persistence of data storage (e.g., RAM vs. ROM).

[0391] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, as a non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures.

[0392] The various exemplary embodiments of this disclosure can be practiced in a variety of components, such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready to be etched and formed on a semiconductor substrate.

[0393] The scope of protection sought by the various exemplary embodiments of this disclosure is set forth in the independent claims. Exemplary embodiments and features (if any) described in this disclosure that do not fall within the scope of the independent claims should be interpreted as examples that aid in understanding the various exemplary embodiments of this disclosure.

[0394] The foregoing description has provided a complete and detailed description of various exemplary embodiments of the present disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, in view of the present disclosure. Nevertheless, all such and similar modifications will still fall within the various exemplary embodiments of the present disclosure. Further exemplary embodiments exist by way of non-limiting and illustrative examples, including combinations of one or more exemplary embodiments with any other exemplary embodiments discussed above.

Claims

1. A method for use in a network node, comprising: Obtain first information and second information, wherein the first information indicates the value of the delay between the first network entity and the second network entity, and the second information indicates the location of the second network entity; as well as The value of the core network packet delay budget (CN PDB) is determined based on the value of the delay indicated by the first information and the value of the delay between the network node and the second network entity, the location of the second network entity being indicated by the second information.

2. The method of claim 1, wherein the value of the CN PDB is determined by adding the value of the delay indicated by the first information to the value of the delay between the network node and the second network entity.

3. The method according to claim 1 or claim 2, further comprising: Based on the location of the second network entity and the location of the network node, the value of the delay between the network node and the second network entity is determined.

4. The method according to any one of claims 1 to 3, wherein the network node is a gNodeB (gNB).

5. The method of claim 4, wherein the gNB is included in a satellite, airborne, or spaceborne non-terrestrial network (NTN) vehicle.

6. The method according to any one of claims 1 to 5, wherein the first network entity is a user plane function (UPF).

7. The method according to any one of claims 1 to 6, wherein the second network entity is a non-terrestrial network gateway (NTN-GW).

8. The method according to any one of claims 1 to 7, wherein the first information and / or the second information are obtained from a third network entity.

9. The method of claim 8, wherein the third network entity is a Session Management Function (SMF).

10. The method according to any one of claims 1 to 9, further comprising: Obtain the value of the Packet Delay Budget (PDB); as well as The value of the access network packet delay budget (AN PDB) is determined based on the value of the PDB and the value of the CN PDB.

11. The method according to any one of claims 1 to 10, wherein the CN PDB is an uplink CN PDB or a downlink CN PDB.

12. The method according to any one of claims 1 to 11, wherein the location of the network node is the current location of the network node.

13. The method according to any one of claims 1 to 12, further comprising: Obtain third information, which indicates the identity of the first network entity.

14. The method according to any one of claims 1 to 13, wherein the value of the delay between the first network entity and the second network entity is the value of the delay of the Quality of Service (QoS) flow at the N6 termination point of the user plane function.

15. The method according to any one of claims 1 to 14, wherein the first information and the second information are obtained during a Packet Data Unit (PDU) session establishment process or a PDU session modification process.

16. A method for use in a third network entity, comprising: Obtain first information and second information, wherein the first information indicates a delay value between a first network entity and a second network entity, and the second information indicates the location of the second network entity, wherein the first information and the second information are used to determine a core network packet delay budget (CN PDB) value; and Provide the first information and the second information to the network nodes.

17. An apparatus comprising components for performing the following: Obtain first information and second information, wherein the first information indicates the value of the delay between a first network entity and a second network entity, and the second information indicates the location of the second network entity; and The value of the core network packet delay budget (CN PDB) is determined based on the value of the delay indicated by the first information and the value of the delay between the network node and the second network entity, the location of the second network entity being indicated by the second information.

18. An apparatus including application functions, wherein the apparatus includes components for performing the following: Obtain first information and second information, wherein the first information indicates a delay value between a first network entity and a second network entity, and the second information indicates the location of the second network entity, wherein the first information and the second information are used to determine a core network packet delay budget (CN PDB) value; and Provide the first information and the second information to the network nodes.

19. A computer program comprising instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 16.

20. An apparatus comprising: At least one processor, At least one memory, said at least one memory including computer program code, and At least one interface, said at least one interface being configured to communicate with at least another device, The at least one processor is configured, together with the at least one memory and the computer program code, to cause the apparatus to perform the method according to any one of claims 1 to 16.

21. A computer program product comprising computer-executable computer program code, wherein the computer-executable computer program code, when the program is run on a computer, is configured to cause the computer to perform the method according to any one of claims 1 to 16.

22. The computer program product of claim 21, wherein the computer program product includes a computer-readable medium on which computer-executable computer program code is stored; and / or wherein the program can be directly loaded into the internal memory of the computer or its processor.

Images