Method and network node for port management

Abstract

This disclosure provides a method and network node for port management. This disclosure provides a method (100) in a Network Open Function (NEF). The method (100) includes: receiving (110) a request from an Application Function (AF) for dynamically reserving a Reliable Data Service (RDS) port resource associated with a Non-Internet Protocol (IP) Data Delivery (NIDD) configuration, the request including an indication of whether the reservation of the RDS port resource requires confirmation with an end device; and sending (120) a response to the request to the AF.

Description

[0001] Case Analysis

[0002] This application is a divisional application of the invention patent application filed on May 17, 2021, with application number 202180037817.4 and invention title "Method for Port Management and Network Node". Technical Field

[0003] This disclosure relates to communication technologies, and more specifically, to a method for port management and a network node. Background Technology

[0004] This section is intended to provide background on various embodiments of the technology described in this disclosure. The descriptions in this section may include protectable concepts, but are not necessarily concepts that have been previously conceived or sought protection. Therefore, unless otherwise stated herein, the content described in this section is not prior art to the specification and / or claims of this disclosure, and should not be considered prior art simply because it is included in this section.

[0005] Non-Internet Protocol (IP) data is considered unstructured and is therefore also referred to as unstructured data in the 3rd Generation Partnership Project (3GPP) specifications. Non-IP Data Delivery (NIDD) is defined in 3GPP Technical Specifications (TS) 23.682, V16.6.0 or TS 23.501, V16.4.0, each of which is incorporated herein by reference in its entirety. NIDD functionality can be used to handle Mobile Initiation (MO) and Mobile Termination (MT) communications with terminal equipment (or user equipment (UE)).

[0006] An association needs to be established between the Application Function (AF) (or Service Capability Server / Application Server (SCS / AS)) and the Packet Data Network (PDN) connection to the Network Open Function (NEF) (or Service Capability Open Function (SCEF)) to enable the transmission of non-IP data between the end device and the AF. When Reliable Data Service (RDS) is enabled, the NEF determines this association based on the port number and a defined policy that can be used to map SCS / AS identifiers and end device identifiers to Data Network Names (DNNs) or Single Network Slice Selection Auxiliary Information (S-NSSAI) (or Access Point Names (APNs)).

[0007] When using a PDN connection of type "Non-IP", RDS can be used between the end device and the NEF. RDS provides mechanisms to determine, for the NEF, whether data has been successfully delivered to the end device, and for the end device, whether data has been successfully delivered to the NEF. RDS retransmits data if the requested acknowledgment is not received. This service is enabled or disabled based on the APN configuration according to the Service Level Agreement (SLA). When RDS is enabled, a protocol is used between endpoints of a non-IP PDN connection. This protocol uses packet headers to identify whether a packet does not require acknowledgment, requires acknowledgment, or is acknowledged, and allows duplicate Protocol Data Units (PDUs) to be detected and eliminated at the receiving endpoint. RDS supports single and multiple applications within the end device. The port number in the header identifies the application at the initiating end and the application at the receiving end.

[0008] Referring to 3GPP TS24.250, V16.2.0, which is incorporated herein by reference in its entirety, RDS ports can be dynamically managed by the end device and / or NEF. The end device and / or NEF can support the reservation of source and destination port numbers and the subsequent release of reserved port numbers. Summary of the Invention

[0009] For example, in the dynamic management of RDS ports, the AF might expect to retain or release a pair of RDS ports, including one at the NEF and one at the terminal device, and this retention or release might fail because, for example, the terminal device might be in a dormant state and therefore unresponsive. This retention or release might also fail due to Hypertext Transfer Protocol (HTTP) timeouts, as the processing time for RDS protocol messages is much longer than typical HTTP client timers. In another example, in some cases where such retention or release fails, or in some other cases where the terminal device requests to retain and release an RDS port at the NEF or notifies the NEF of a retained RDS port at the terminal device, it is expected that the corresponding AF will be correctly notified. In yet another example, the AF or UE might request the release of an RDS port that was not created by itself, which could be problematic.

[0010] The purpose of this disclosure is to provide a method and network node capable of solving at least one of the above-mentioned problems.

[0011] According to a first aspect of this disclosure, a method in a NEF is provided. The method includes: receiving from an AF a request for dynamically reserving RDS port resources associated with an NIDD configuration. The request includes an indication of whether the reservation of the RDS port resources requires confirmation with an end device. The method further includes: sending a response to the request to the AF.

[0012] In this embodiment, the request may include a Uniform Resource Identifier (URI) for the RDS port resource. The URI indicates the first port at the NEF and the second port at the terminal device.

[0013] In an embodiment, the method may further include: reserving the RDS port resources at the NEF when the indication indicates that the reservation of the RDS port resources does not require confirmation with the terminal device, and when the first port and / or the second port does not exist in any NIDD configuration. The response may indicate that the RDS port resources have already been reserved at the NEF.

[0014] In an embodiment, the method may further include: after the reservation operation, notifying the terminal device that the RDS port resource has been reserved at NEF.

[0015] In an embodiment, the method may further include: when the indication indicates that the reservation of RDS port resources needs to be confirmed with the terminal device, and when the first port and / or the second port does not exist in any NIDD configuration, initiating an interaction with the terminal device to reserve the RDS port resources at the terminal device.

[0016] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0017] In an embodiment, the method may further include: after sending a response, receiving an RDS response from a terminal device, the RDS response confirming the reservation of RDS port resources; reserving the RDS port resources at the NEF; and notifying the AF of one or more RDS ports currently reserved at the NEF.

[0018] In an embodiment, the method may further include: after the retention operation, maintaining a record at the NEF that the RDS port resources are retained by the AF.

[0019] In an embodiment, the method may further include: receiving an RDS response indicating confirmation failure from a terminal device after the initiated operation; and notifying the AF of one or more RDS ports currently reserved at the NEF.

[0020] In an embodiment, when the indication indicates that the reservation of RDS port resources needs to be confirmed with the terminal device, and when NEF is unable to interact with the terminal device because a packet data network (PDN) connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0021] In an embodiment, when the first port and / or the second port already exist in any NIDD configuration, the response may indicate that reserving the RDS port resource at NEF has failed.

[0022] According to a second aspect of this disclosure, a method in NEF is provided. The method includes: receiving from an AF a request for dynamically releasing RDS port resources associated with an NIDD configuration. The request includes an indication of whether confirmation with an end device is required for the release of the RDS port resources. The method further includes: sending a response to the request to the AF.

[0023] In an embodiment, the method may further include: when the indication indicates that the release of the RDS port resource does not require confirmation with the terminal device, and when the RDS port resource exists in the NIDD configuration and is reserved by the AF, releasing the RDS port resource at the NEF. The response may indicate that the RDS port resource has been released at the NEF.

[0024] In an embodiment, the method may further include: notifying the terminal device that the RDS port resource has been released at NEF.

[0025] In an embodiment, the method may further include: when the indication indicates that the release of the RDS port resource requires confirmation with the terminal device: when the RDS port resource exists in the NIDD configuration and the RDS port resource is reserved by AF, initiating an interaction with the terminal device to release the RDS port resource at the terminal device.

[0026] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0027] In an embodiment, the method may further include: after sending a response, receiving an RDS response from a terminal device, the RDS response confirming the release of RDS port resources or indicating a failure to release RDS port resources; releasing the RDS port resources at the NEF; and notifying the AF of one or more RDS ports currently reserved at the NEF.

[0028] In an embodiment, when the RDS port resource is not present in the NIDD configuration or is not reserved by the AF, the response may indicate a failure to release the RDS port resource at the NEF.

[0029] In an embodiment, when the indication requires confirmation with the terminal device for the release of RDS port resources, and when NEF is unable to interact with the terminal device because a PDN connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0030] According to a third aspect of this disclosure, a method in NEF is provided. The method includes: receiving an RDS request associated with RDS port resources from an end device during a MONIDD process associated with an NIDD configuration; and notifying an AF associated with the NIDD configuration of one or more RDS ports currently reserved at the NEF.

[0031] In this embodiment, the RDS request may be used to reserve RDS port resources and includes a URI of the RDS port resources. The URI indicates a first port at the NEF and a second port at the terminal device. The method may further include: reserving the RDS port resources at the NEF when the first port and / or the second port does not exist in any NIDD configuration; and during the MTNIDD process, sending an RDS response to the terminal device indicating that the RDS port resources have been reserved at the NEF.

[0032] In an embodiment, the method may further include: maintaining an indication at the NEF that the RDS port resources are reserved by the terminal device.

[0033] In an embodiment, an RDS request can be used to release RDS port resources, and the method may further include: releasing the RDS port resources at NEF when the RDS port resources exist in the NIDD configuration and are reserved by the terminal device; and sending an RDS response to the terminal device during the MTNIDD process, indicating that the RDS port resources have been released at NEF.

[0034] In an embodiment, an RDS request may be used to notify the NEF of RDS port resources reserved at the terminal device. The RDS port resources have URIs indicating a first port at the NEF and a second port at the terminal device. The method may further include reserving the RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration.

[0035] In an embodiment, the method may further include: maintaining a record at the NEF that the RDS port resources are retained by the terminal device.

[0036] According to a fourth aspect of this disclosure, a network node is provided. The network node includes a processor and a memory. The memory contains instructions enabling the network node to implement NEF. The network node is configured to, when implementing NEF, execute the methods described in accordance with the first, second, and / or third aspects described above.

[0037] According to a fifth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer-readable instructions. When executed by a processor of a network node, the computer-readable instructions configure the network node to perform the methods described in accordance with the first, second, and / or third aspects described above.

[0038] According to a sixth aspect of this disclosure, a method in an AF is provided. The method includes: sending a request to a NEF to dynamically retain or release RDS port resources associated with an NIDD configuration. The request includes an indication of whether confirmation with an end device is required for the retention or release of the RDS port resources. The method further includes: receiving a response to the request from the NEF.

[0039] In an embodiment, when the indication indicates that the retention or release of RDS port resources does not require confirmation with the terminal device, the response may indicate that the RDS port resources have been retained or released at the NEF, or indicate the failure to retain or release the RDS port resources at the NEF.

[0040] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate that confirmation is still in progress before the timer associated with the request expires.

[0041] In an embodiment, the method may further include: after receiving a response, receiving a notification from the NEF of one or more RDS ports currently reserved at the NEF.

[0042] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate a failure to reserve RDS port resources at NEF, or indicate that a PDN connection has not yet been established with the terminal device.

[0043] According to a seventh aspect of this disclosure, a network node is provided. The network node includes a processor and a memory. The memory contains instructions enabling the network node to implement AF (Automatic Function). The network node is configured to, when implementing AF, execute the method described in the sixth aspect above.

[0044] According to an eighth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer-readable instructions. When executed by a processor of a network node, the computer-readable instructions configure the network node to perform the method described in the sixth aspect above.

[0045] Through embodiments of this disclosure, an indication of whether confirmation with the terminal device is required can be included in a request from the AF for dynamically reserving or releasing RDS port resources, allowing the NEF to dynamically reserve or release RDS port resources according to this indication. Additionally, upon receiving an RDS request from the terminal device for dynamically reserving or releasing RDS port resources or notifying the RDS port resources reserved at the terminal device, the NEF can notify the associated AF of the RDS ports currently reserved at the NEF. Embodiments of this disclosure allow dynamic RDS management (e.g., RDS port reservation, release, and notification) to be performed more efficiently, flexibly, or appropriately. Attached Figure Description

[0046] The above and other objects, features and advantages will become more apparent from the following description of embodiments with reference to the accompanying drawings, in which:

[0047] Figure 1 This is a flowchart illustrating a method in NEF according to an embodiment of the present disclosure;

[0048] Figure 2 This is a flowchart illustrating a method in NEF according to another embodiment of the present disclosure;

[0049] Figure 3 This is a flowchart illustrating a method in NEF according to yet another embodiment of the present disclosure;

[0050] Figure 4 This is a flowchart illustrating a method in AF according to an embodiment of the present disclosure;

[0051] Figure 5 This is a sequence diagram illustrating a process for reserving RDS port resources according to an embodiment of the present disclosure;

[0052] Figure 6 This is a sequence diagram illustrating a process for releasing RDS port resources according to an embodiment of the present disclosure;

[0053] Figure 7 This is a sequence diagram illustrating a UE-initiated process for reserving, releasing, or notifying RDS port resources according to embodiments of the present disclosure;

[0054] Figure 8 This is a sequence diagram illustrating a process for reserving RDS port resources according to another embodiment of the present disclosure;

[0055] Figure 9 This is a sequence diagram illustrating a process for releasing RDS port resources according to another embodiment of the present disclosure;

[0056] Figure 10This is a sequence diagram illustrating a UE-initiated process for reserving, releasing, or notifying RDS port resources according to another embodiment of this disclosure;

[0057] Figure 11 This is a block diagram of a network node for implementing NEF according to embodiments of the present disclosure;

[0058] Figure 12 This is a block diagram of a network node for implementing NEF according to another embodiment of the present disclosure;

[0059] Figure 13 This is a block diagram of a network node for implementing NEF according to yet another embodiment of the present disclosure;

[0060] Figure 14 This is a block diagram of a network node for implementing AF according to embodiments of the present disclosure; and

[0061] Figure 15 This is a block diagram of a network node for implementing AF according to another embodiment of the present disclosure. Detailed Implementation

[0062] The use of terms such as "an embodiment," "embodiment," or "example embodiment" in the specification indicates that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be assumed that implementing such a feature, structure, or characteristic in conjunction with other embodiments (whether explicitly described or not) is within the knowledge of someone skilled in the art.

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

[0064] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” as used herein are intended to also include the plural forms unless the context explicitly indicates otherwise. It should be further understood that, when used herein, the terms “comprising,” “having,” “including,” etc., indicate the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0065] In the context of this disclosure, the terms "terminal device" or "UE" refer to any end device that can access and receive services from a wireless communication network. By way of example and not limitation, a terminal device or UE can refer to a mobile terminal or any other suitable device. As an example, a terminal device or UE can be configured to communicate according to one or more communication standards published by 3GPP (e.g., 3GPP's Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 4G or Long Term Evolution (LTE) and / or 5G standards). A terminal device or UE as used herein may not necessarily be a "user" in the sense of a human user who owns and / or operates the associated device. In some embodiments, a terminal device or UE can be configured to send and / or receive information without direct human interaction. For example, a terminal device or UE can be designed to send information to the network according to a predetermined schedule when triggered by an internal or external event or in response to a request from the wireless communication network. A terminal device or UE can refer to a device intended for sale to or operated by a human user but which may not initially be associated with a particular human user. Terminal devices or UEs can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, and in this case, can be referred to as D2D communication devices. As another example, in Internet of Things (IoT) scenarios, a terminal device or UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of these monitoring and / or measurements to another UE and / or network device. In this case, the terminal device or UE can be a machine-to-machine (M2M) device, and in the 3GPP context, can be referred to as a machine-type communication (MTC) device. As a specific example, a terminal device or UE can implement the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machines, or household or personal appliances (e.g., refrigerators, televisions, personal wearable devices such as watches, etc.). In other scenarios, a terminal device or UE can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0066] As used in this document, "network node" refers to any physical or virtual node configured to implement network functions, including but not limited to those specified by 3GPP. Network nodes can be implemented in physical devices or virtualized environments (e.g., cloud environments).

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

[0068] Figure 1 This is a flowchart illustrating a method 100 according to an embodiment of the present disclosure. Method 100 can be performed at NEF. Although method 100 will be described below primarily with reference to 5G systems, it should be noted that the method can also be applied to 4G systems, in which case it can be performed at SCEF.

[0069] At box 110, a request is received from the AF (or SCS / AS in a 4G system) to dynamically reserve RDS port resources associated with the NIDD configuration. The NIDD configuration may have been created by the AF according to section 4.25.3 of TS 23.502, V16.4.0 (or by the SCS / AS according to section 5.13.2 of TS 23.682), which is incorporated herein by reference in its entirety. The request includes an indication of whether confirmation with the terminal device is required for the reservation of the RDS port resources.

[0070] Here, the request may include the URI of an RDS port resource, such as the resource URI defined in Table 4, which is described later. The URI indicates the first port at the NEF and the second port at the terminal device. In other words, an RDS port resource may include a pair of ports, namely, the first port at the NEF and the second port at the terminal device.

[0071] At box 120, send a response to the request to AF.

[0072] In the example, when the indication states that the reservation of RDS port resources does not require confirmation with the terminal device, the RDS port resources can be reserved at the NEF without interaction with the terminal device for confirmation, even if the first port and / or the second port are not present in any NIDD configuration (e.g., in any NIDD configuration of the same DNN or S-NSSAI (or the same APN in a 4G system) as the NIDD configuration). In this case, the response sent to the AF in box 120 can indicate that the RDS port resources have been reserved at the NEF.

[0073] In the example, NEF can also notify the end device that the RDS port resource has been reserved at NEF. In the example, NEF can maintain a record of whether the RDS port resource is reserved by AF.

[0074] On the other hand, when the indication requires confirmation with the terminal device to reserve RDS port resources, NEF can initiate an interaction with the terminal device to reserve RDS port resources at the terminal device when the first port and / or the second port do not exist in any NIDD configuration (e.g., in any NIDD configuration of the same DNN or S-NSSAI).

[0075] In the example, when the NEF is unable to interact with the end device because a PDN connection has not yet been established with the end device (e.g., an unstructured PDN connection), the response sent to the AF in box 120 can indicate that a PDN connection has not yet been established with the end device.

[0076] In another example, for instance, after successfully initiating an interaction with the end device, before the timer associated with the request expires, the response sent to the AF in box 120 can indicate that the acknowledgment is still in progress, so that the AF does not consider the request to have failed due to timer expiration. The NEF can then receive an RDS response from the end device (which confirms the reservation of the RDS port resource), reserve the RDS port resource at the NEF, and notify the AF of one or more RDS ports currently reserved at the NEF. In this case, the NEF can maintain a record of the RDS port resources being reserved by the AF. Alternatively, the NEF can receive an RDS response from the end device indicating a failed acknowledgment and notify the AF of one or more RDS ports currently reserved at the NEF.

[0077] Regardless of whether the indication indicates that the reservation of RDS port resources requires confirmation with the end device, the response sent to the AF in box 120 may indicate a failure to reserve RDS port resources at the NEF when the first port and / or the second port already exist in any NIDD configuration (e.g., in any NIDD configuration of the same DNN or S-NSSAI).

[0078] Figure 2 This is a flowchart illustrating a method 200 according to an embodiment of the present disclosure. Method 200 can be performed at the NEF. Although method 200 will be described below primarily with reference to 5G systems, it should be noted that the method can also be applied to 4G systems, in which case it can be performed at the SCEF.

[0079] At box 210, a request is received from the AF (or SCS / AS in a 4G system) to dynamically release RDS port resources associated with the NIDD configuration. The NIDD configuration may have been created by the AF according to section 4.25.3 of TS 23.502 (or by the SCS / AS according to section 5.13.2 of TS 23.682). The request includes an indication of whether confirmation with the terminal device is required for the release of the RDS port resources.

[0080] At box 220, send a response to the request to AF.

[0081] When the indication states that the release of RDS port resources does not require confirmation with the end device, and when the RDS port resources exist in the NIDD configuration and are reserved by the AF, the RDS port resources can be released at the NEF without interaction with the end device for confirmation. In this case, the response sent to the AF in box 220 can indicate that the RDS port resources have been released at the NEF.

[0082] In the example, NEF can also notify the end device that the RDS port resource has been released at NEF.

[0083] On the other hand, when the indication requires confirmation with the terminal device to release the RDS port resource, and when the RDS port resource exists in the NIDD configuration and is reserved by the AF (e.g., when the record maintained at the NEF indicates that the RDS port resource is reserved by the AF), the NEF can initiate an interaction with the terminal device to release the RDS port resource at the terminal device.

[0084] In the example, when the NEF is unable to interact with the end device because a PDN connection has not yet been established with the end device (e.g., an unstructured PDN connection), the response sent to the AF in box 220 can indicate that a PDN connection has not yet been established with the end device.

[0085] In another example, for instance, after successfully initiating an interaction with the end device, before the timer associated with the request expires, the response sent to the AF in box 220 can indicate that the process is still in progress, so that the AF does not consider the request to have failed due to a timer expiration. The NEF can then receive an RDS response from the end device (which confirms the release of the RDS port resource or indicates a failure to release the RDS port resource), release the RDS port resource at the NEF, and notify the AF of one or more RDS ports currently reserved at the NEF.

[0086] Regardless of whether the indication indicates that the release of the RDS port resource requires confirmation with the end device, the response sent to the AF in box 220 may indicate the failure to release the RDS port resource at the NEF when the RDS port resource does not exist in the NIDD configuration or is not reserved by the AF (e.g., when the record maintained at the NEF indicates that the RDS port resource is reserved by the end device).

[0087] Figure 3This is a flowchart illustrating method 300 according to an embodiment of the present disclosure. Method 300 can be performed at NEF. Although method 300 will be described below primarily with reference to 5G systems, it should be noted here that the method can also be applied to 4G systems, in which case it can be performed at SCEF.

[0088] At box 310, during the MO NIDD process associated with the NIDD configuration, an RDS request associated with the RDS port resource is received from the end device. The NIDD configuration may, for example, have been created by the AF according to section 4.25.3 of TS 23.502 (or by the SCS / AS according to section 5.13.2 of TS 23.682).

[0089] At box 320, notify the AF (or SCS / AS in a 4G system) associated with the NIDD configuration of one or more RDS ports currently reserved at the NEF.

[0090] In the example, an RDS request can be used to reserve an RDS port resource. This request can contain the URI of the RDS port resource, such as the resource URI defined in Table 4, described later. The URI indicates a first port at the NEF and a second port at the terminal device. In other words, an RDS port resource can include a pair of ports, namely, a first port at the NEF and a second port at the terminal device. In this case, when the first port and / or the second port do not exist in any NIDD configuration (e.g., in any NIDD configuration with the same DNN or S-NSSAI (or the same APN) as the NIDD configuration), the NEF can reserve the RDS port resource and send an RDS response to the terminal device during the MT NIDD process indicating that the RDS port resource has been reserved at the NEF. Here, the NEF can maintain an indication that the RDS port resource is reserved by the terminal device.

[0091] In another example, an RDS request can be used to release RDS port resources. In this case, when the RDS port resource exists in the NIDD configuration and is reserved by the end device (e.g., when a record maintained at NEF indicates that the RDS port resource is reserved by the end device), NEF can release the RDS port resource. NEF can then send an RDS response to the end device indicating that the RDS port resource has been released at NEF.

[0092] In another example, an RDS request can be used to notify the NEF of RDS port resources reserved at the end device. The RDS port resources can have URIs indicating a first port at the NEF and a second port at the end device. In this case, the NEF can reserve the RDS port resources at the NEF if the first port and / or the second port do not exist in any NIDD configuration (e.g., in any NIDD configuration with the same DNN or S-NSSAI (or the same APN) as the NIDD configuration). Here, the NEF can maintain an indication that the RDS port resources are reserved by the end device.

[0093] Figure 4 This is a flowchart illustrating method 400 according to an embodiment of the present disclosure. Method 400 can be performed at the AF. Although method 300 will be described below primarily with reference to 5G systems, it should be noted here that the method can also be applied to 4G systems, in which case it can be performed at the SCS / AS.

[0094] At box 410, a request is sent to the NEF (or SCEF in a 4G system) to dynamically reserve or release RDS port resources associated with the NIDD configuration. This request includes an indication of whether confirmation with the terminal device is required for the reservation or release of the RDS port resources.

[0095] At box 420, receive the response to the request from NEF.

[0096] When the indication indicates that the reservation or release of RDS port resources does not require confirmation with the terminal device, the response received from the NEF in box 420 may indicate that the RDS port resources have been reserved or released at the NEF, or indicate the failure to reserve or release the RDS port resources at the NEF.

[0097] On the other hand, when the indication requires confirmation with the end device for the reservation or release of RDS port resources, in step 420, a response can be received from the NEF before the timer associated with the request expires. This response indicates that the confirmation is still in progress, preventing the AF from considering the request to have failed due to timer expiration. The AF can then receive notification from the NEF of one or more RDS ports currently reserved at the NEF. In another example, the response received from the NEF in block 420 could indicate a failure to reserve RDS port resources at the NEF, or indicate that a connected PDN connection (e.g., an unstructured PDN connection) has not yet been established with the end device.

[0098] The following is for reference. Figures 5 to 10 The sequence diagrams illustrate the above methods in more detail 100 to 400. Figures 5 to 7 It is a sequence diagram for 5G systems, and Figures 8 to 10This is a sequence diagram for 4G systems. Tables 1 through 8 below will be used in the description below. For some details in these tables, please refer to TS 29.122, V16.5.0, the entire contents of which are incorporated herein by reference.

[0099] Table 1: Definition of Type ManagePort

[0100]

[0101] Table 2: Enumerated Management Entities

[0102] Enumeration value describe applicability UE Indicates UE AS This refers to the application server (AF, SCS / AS).

[0103] Table 3: Overview of Resources and Methods

[0104]

[0105] Table 4: Resource URI Variables for Resource "Individual ManagePort Configuration"

[0106]

[0107] Table 5: Data structures supported by resource PUT requests / responses

[0108]

[0109] Table 6: Data Structures Supported by DELETE Requests / Responses for Resources

[0110]

[0111] Table 7: Data Structures Supported by POST Requests / Responses to Resources

[0112]

[0113] Table 8: Application Errors

[0114]

[0115]

[0116] Figure 5 This is a sequence diagram illustrating a process for dynamically reserving RDS port resources according to an embodiment of the present disclosure.

[0117] As shown in the figure, at 5.1, the AF requests the NEF to dynamically reserve RDS port resources (including the NEF port and UE port) at the NEF via an HTTP PUT request. This request includes the indication "skipUeInquiry" (see Table 1). At 5.2a, the NEF processes this request. If the "skipUeInquiry" indication is set to "false", it means that the RDS port resources will be reserved with the UE's confirmation or consent. Then, if the RDS port resources ("individual ManagePortConfiguration" resources), i.e., the NEF port and / or the UE port, already exist in any NIDD configuration within the same DNN / S-NSSAI, at 5.2b, the NEF responds with a "403 Forbidden" response with a cause value "PORT_NOT_FREE" in the "cause" attribute of the "ProblemDetails" structure; otherwise, the NEF interacts with the UE using the RDS protocol as specified in TS 24.250 to reserve the RDS port resources, and this process continues at 5.3. If the NEF is unable to interact with the UE because the PDN connection (between the Session Management Function (SMF) and the NEF) has not been established, then at 5.2b, the NEF rejects the HTTP PUT request and responds with a "500 Internal Server Error" with the reason value "NO_PDN_CONNECTION".

[0118] If the “skipUeInquiry” indication is set to “true”, it means that the RDS port resource will be reserved without UE confirmation or consent. Then, if the requested NEF port and / or UE port already exist in any NIDD configuration within the same DNN / S-NSSAI, at 5.2b, the NEF responds with a “403 Forbidden” response with a cause value “PORT_NOT_FREE” in the “cause” attribute of the “ProblemDetails” structure; otherwise, the NEF creates the “individual ManagePort Configuration” resource and sends an HTTP “201 Created” response to the AF at 5.2b. The NEF also marks the resource as created by the AF (manageEntity in Table 1) and notifies the UE using the RDS protocol as specified in TS 24.250, and this process continues at 5.3.

[0119] If the "skipUeInquiry" indication is set to "false", the NEF prepares an NIDD packet containing an RDS message (i.e., reserving the RDS port). If the "skipUeInquiry" indication is set to "true", the NEF prepares an NIDD packet containing an RDS message (i.e., notifying the RDS port). At 5.3, the NEF sends the prepared NIDD packet with the RDS message to the UE according to steps 3 to 16 of the NEF-anchored mobile termination data transmission procedure as specified in Clause 4.25.2 of TS 23.502. If the NEF receives a successful transmission response from the SMF, at 5.4 the NEF returns a "202 Accept" to the AF to indicate that processing is still in progress, and the processing continues at 5.5; otherwise, at 5.4 the NEF replies to the AF with a "500 Internal Server Error" and an appropriate reason value indicating the reason for the transmission failure.

[0120] At 5.5, the UE initiates the MO NIDD procedure to include an RDS reserved port response message for port reservation, according to steps 1 through 3 of the MO data transmission procedure anchored by the NEF as specified in TS 23.502. If the "skipUeInquiry" indication is set to "false" and the NEF receives a successful UE RDS reserved port response, the NEF creates an "individualManagePort Configuration" resource and notifies the AF of the reserved port at 5.6 (see below). Figure 7 The NEF, as described above, marks the resource as created by the AF (manageEntity in Table 1); otherwise, at 5.6, the NEF notifies the AF of the currently reserved ports (see below). Figure 7 (As stated above). At 5.7, AF acknowledges the RDS port notification from NEF. At 5.8, NEF acknowledges the MO NIDD request from SMF.

[0121] Figure 6 This is a sequence diagram illustrating a process for dynamically releasing RDS port resources according to an embodiment of the present disclosure.

[0122] As shown in the figure, at 6.1, the AF requests the NEF to dynamically release RDS port resources (including the NEF port and the UE port) at the NEF via an HTTP DELETE request. This request includes the instruction "skipUeInquiry" (see Table 1). At 6.2a, the NEF processes this request. If the RDS port resource (the "individual ManagePort Configuration" resource) does not exist in the same NIDD configuration, at 6.2b, the NEF responds with a "404 Not Found" error with the cause value "PORT_NOT_ASSOC_WITH_APP" in the "cause" attribute of the "ProblemDetails" structure; otherwise, if an HTTP DELETE request is received for an "Individual NIDD downlink data delivery" resource created by the UE (referencing the manageEntity of the resource), at 6.2b, the NEF rejects the message with a "403 Forbidden" response with the cause value "OPERATION_PROHIBITED" in the "cause" attribute of the "ProblemDetails" structure. Then, if the "individualManagePortConfiguration" resource was created by AF:

[0123] - If the "skipUeInquiry" instruction is set to "false", it means that the RDS port resources will be released upon UE confirmation or consent, and the NEF will interact with the UE using the RDS protocol as specified in TS 24.250 to release the RDS port resources, and this process continues at 6.3. If the NEF is unable to interact with the UE due to the failure to establish a PDN connection (between the Session Management Function (SMF) and the NEF), then at 6.2b, the NEF rejects the HTTP DELETE request and responds with a "500 Internal Server Error" with the reason value "NO_PDN_CONNECTION".

[0124] - If the “skipUeInquiry” instruction is set to “true”, it means that the RDS port resource will be released without UE confirmation or consent. At 6.2b, the NEF deletes the individual ManagePort Configuration resource and responds to the AF with an HTTP “204 No Content” response, notifying the UE using the RDS protocol as specified in TS 24.250, and the process continues at 6.3.

[0125] If the "skipUeInquiry" indication is set to "false", the NEF prepares an NIDD packet containing an RDS message (i.e., releasing the RDS port). If the "skipUeInquiry" indication is set to "true", the NEF prepares an NIDD packet containing an RDS message (i.e., notifying the RDS port). At 6.3, the NEF sends the prepared NIDD packet with the RDS message to the UE according to steps 3 to 16 of the NEF-anchored mobile termination data transmission procedure as specified in Clause 4.25.2 of TS 23.502. If the NEF receives a successful transmission response from the SMF, at 5.4 the NEF returns a "202 Accept" to the AF to indicate that processing is still in progress, and the processing continues at 6.5; otherwise, at 6.4 the NEF replies to the AF with a "500 Internal Server Error" and an appropriate reason value indicating the reason for the transmission failure.

[0126] At 6.5, the UE initiates the MO NIDD procedure according to steps 1 to 3 of the MO data transmission procedure anchored by the NEF as specified in TS 23.502, to include an RDS release port response message for port reservation. If the "skipUeInquiry" indication is set to "false" and the NEF receives a response from the UE (whether successful or failed (e.g., a failure due to the RDS port resource already being released at the UE)), the NEF deletes the "individual ManagePort Configuration" resource and notifies the AF of the reserved port at 6.6 (see below). Figure 7 (As stated above). At 6.7, AF acknowledges the RDS port notification from NEF. At 6.8, NEF acknowledges the MO NIDD request from SMF.

[0127] Figure 7 This is a sequence diagram illustrating a UE-initiated process for dynamically reserving, releasing, or notifying RDS port resources according to embodiments of the present disclosure.

[0128] As shown in the figure, at point 7.1, the UE sends MO NIDD data to the NEF. This MO NIDD data carries an RDS request, which can be a request to reserve, release, or notify the RDS port resources.

[0129] If the RDS request is a request to reserve RDS port resources (including NEF ports and UE ports), then when the NEF port and / or UE port do not exist in any NIDD configuration in the same DNN / S-NSSAI, the NEF reserves the RDS port resources (“individual ManagePort Configuration” resources) and marks the RDS port resources as created by the UE (manageEntity in Table 1).

[0130] If the RDS request is a request to release RDS port resources, then NEF releases the RDS port resources (“individualManagePort Configuration” resources) when the RDS port resources exist in the same NIDD configuration and the RDS port resources are reserved by the UE (refer to the manageEntity of the resource).

[0131] If the RDS request is a request for RDS port resources (including NEF ports and UE ports) reserved at the UE, then when the NEF port and / or UE port do not exist in any NIDD configuration in the same DNN / S-NSSAI, the NEF reserves the RDS port resources (“individual ManagePort Configuration” resources) and marks the RDS port resources as created by the UE (manageEntity in Table 1).

[0132] Then, at 7.2, the NEF notifies the AF of an HTTP POST request including the currently reserved RDS port, and at 7.3, the AF acknowledges the POST request. At 7.4, the NEF acknowledges the MO NIDD message from the SMF. At 7.5, if the RDS request is a request to reserve / release RDS port resources, the NEF sends a response to the UE according to steps 3 to 16 of the NEF-anchored mobile termination data transmission procedure as specified in Clause 4.25.2 of TS 23.502.

[0133] Figure 8 This is a sequence diagram illustrating a process for dynamically reserving RDS port resources according to another embodiment of the present disclosure.

[0134] As shown in the figure, at 8.1, the SCS / AS requests the SCEF to dynamically reserve RDS port resources (including the SCEF port and the UE port) at the SCEF via an HTTP PUT request. This request includes the indication "skipUeInquiry" (see Table 1). At 8.2a, the SCEF processes this request. If the "skipUeInquiry" indication is set to "false", it means that the RDS port resources will be reserved with the UE's confirmation or consent. Then, if the RDS port resources ("individual ManagePortConfiguration" resources), i.e., the SCEF port and / or the UE port, already exist in any NIDD configuration within the same APN, at 8.2b, the SCEF responds with a "403 Forbidden" response with the cause value "PORT_NOT_FREE" in the "cause" attribute of the "ProblemDetails" structure; otherwise, the SCEF interacts with the UE using the RDS protocol as specified in TS 24.250 to reserve the RDS port resources, and this process continues at 8.3. If the SCEF is unable to interact with the UE due to the PDN connection not being established, then at 8.2b, the SCEF rejects the HTTP PUT request and responds with a "500 Internal Server Error" with the reason value "NO-PDN_CONNECTION".

[0135] If the “skipUeInquiry” indication is set to “true”, it means that the RDS port resource will be reserved without UE confirmation or consent. Then, if the requested SCEF port and / or UE port already exist in any NIDD configuration within the same APN, at 8.2b, the SCEF responds with a “403 Forbidden” response with a cause value “PORT_NOT_FREE” in the “cause” attribute of the “ProblemDetails” structure; otherwise, the SCEF creates the “individualManagePort Configuration” resource and sends an HTTP “201 Created” response to the SCS / AS at 8.2b. The SCEF also marks the resource as created by the SCS / AS and notifies the UE using the RDS protocol as specified in 3GPP TS 24.250 (refer to 8.3, 8.6, and 8.7).

[0136] If the "skipUeInquiry" indication is set to "false", the SCEF prepares a NIDD packet containing an RDS message (i.e., reserving the RDS port) and sends the NIDD packet to the Mobility Management Entity (MME) / Serving GPRS (General Packet Radio Service) Support Node (SGSN) at 8.3. If the "skipUeInquiry" indication is set to "true", the SCEF prepares a NIDD packet containing an RDS message (i.e., notifying the RDS port) and sends the NIDD packet to the MME / SGSN at 8.3.

[0137] If the MME / SGSN is able to immediately transmit non-IP data to the UE, for example, when the UE is already in Evolved Packet System (EPS) Connection Management (ECM)_CONNECTED mode, or when the UE is in ECM_IDLE and the MME / SGSN is able to initiate a paging procedure, then the procedure continues at 8.6.

[0138] If the MME / SGSN knows that the UE is temporarily unreachable while using power-saving features (e.g., UE power-saving mode or extended idle mode DRX), or if the MME / SGSN knows that the UE has not been scheduled to be reachable during the SCEF waiting time, then at 8.4, the MME / SGSN may send an NIDD submission response (reason, requested retransmission time) message to the SCEF.

[0139] If the "skipUeInquiry" indication is set to "false" and the SCEF receives a negative response from the MME / SGSN, then at 8.5, the SCEF rejects the HTTP PUT request and responds with a "500 Internal Server Error" with an appropriate reason value, for example, "UE Temporarily Unreachable" received from the MME / SGSN is mapped to the reason value "TEMPORARILY_NOT_REACHABLE". This response may include the requested retransmission time to indicate to the SCS / AS the expected time when the UE is reachable, allowing the SCS / AS to prepare for any reconfiguration for the RDS port resources.

[0140] At 8.6, if necessary, the MME / SGSN pagees the UE and transmits non-IP data to the UE via data transmission through the MME / SGSN procedure. If the MME / SGSN is able to initiate NIDD transmission at 8.6, then at 8.7, the MME / SGSN sends an "NIDD Submission Response (Reason)" message to the SCEF, acknowledging the "NIDD Submission Request" received from the SCEF at 8.3.

[0141] If the SCEF receives a successful transmission response from the MME / SGSN, at 8.8 the SCEF returns a "202 Accept" to the SCS / AS to indicate that processing is still in progress, and the process continues at 8.9; otherwise, at 8.8 the SCEF replies to the SCS / AS with a "500 Internal Server Error" and an appropriate reason value indicating the reason for the transmission failure. At 8.9, the UE initiates the MO NIDD procedure to include an RDS response for port reservation.

[0142] If the "skipUeInquiry" indication is set to "false" and the SCEF receives a successful UE response, the SCEF creates an "individual ManagePort Configuration" resource and notifies the SCS / AS of the reserved ports at 8.10 (see below for reference). Figure 10 The resource is marked as created by SCS / AS (manageEntity in Table 1); otherwise, at 8.10, SCEF notifies SCS / AS of the currently reserved ports (see below). Figure 10 (as described above). At 8.11, SCS / AS acknowledges the notification sent from SCEF.

[0143] Figure 9 This is a sequence diagram illustrating a process for dynamically releasing RDS port resources according to another embodiment of the present disclosure.

[0144] As shown in the figure, at 9.1, the SCS / AS requests the SCEF to dynamically release RDS port resources (including the SCEF port and the UE port) at the SCEF via an HTTP DELETE request. This request includes the indication "skipUeInquiry" (see Table 1). At 9.2a, the SCEF processes this request. If the RDS port resource (the "individual ManagePortConfiguration" resource) does not exist in the same NIDD configuration, then at 9.2b, the SCEF responds with a "404 Not Found" error with the cause value "PORT_NOT_ASSOC_WITH_APP" in the "casue" attribute of the "ProblemDetails" structure; otherwise, if an HTTP DELETE request is received for an "Individual NIDDdownlink data delivery" resource created by the UE (referencing the manageEntity of the resource), then at 9.2b, the SCEF rejects the message with a "403 Forbidden" response with the cause value "OPERATION_PROHIBITED" in the "cause" attribute of the "ProblemDetails" structure. Then, if the "individual ManagePort Configuration" resource was created by SCS / AS:

[0145] - If the "skipUeInquiry" instruction is set to "false", it means that the RDS port resources will be released upon UE confirmation or consent, and the SCEF will interact with the UE using the RDS protocol as specified in TS 24.250 to release the RDS port resources, and this process continues at 9.3. If the SCEF is unable to interact with the UE due to the PDN connection not being established, at 9.2b, the SCEF rejects the HTTP DELETE request and responds with a "500 Internal Server Error" with the reason value "NO_PDN_CONNECTION".

[0146] - If the “skipUeInquiry” instruction is set to “true”, it means that the RDS port resource will be released without UE confirmation or consent. At 9.2b, the SCEF deletes the individual ManagePort Configuration resource and responds to the SCS / AS with an HTTP “204 No Content” response, and notifies the UE using the RDS protocol as specified in TS 24.250 (refer to 9.3, 9.6 and 9.7).

[0147] If the "skipUeInquiry" indicator is set to "false", the SCEF prepares a NIDD packet containing an RDS message (i.e., releasing the RDS port) and sends the NIDD packet to the MME / SGSN at 9.3. If the "skipUeInquiry" indicator is set to "true", the SCEF prepares a NIDD packet containing an RDS message (i.e., notifying the RDS port) and sends the NIDD packet to the MME / SGSN.

[0148] If the MME / SGSN can immediately transmit non-IP data to the UE, for example, when the UE is already in ECM_CONNECTED mode, or when the UE is in ECM_IDLE and the MME / SGSN can initiate a paging procedure, then the procedure continues at 9.6.

[0149] If the MME / SGSN knows that the UE is temporarily unreachable while using power-saving features (e.g., UE power-saving mode or extended idle mode DRX), or if the MME / SGSN knows that the UE has not been scheduled to be reachable during the SCEF waiting time, then at 9.4, the MME / SGSN may send an NIDD submission response (reason, requested retransmission time) message to the SCEF.

[0150] If the "skipUeInquiry" indication is set to "false" and the SCEF receives a negative response from the MME / SGSN, then at 9.5, the SCEF rejects the HTTP DELETE request and responds with a "500 Internal Server Error" with an appropriate reason value, for example, "UE Temporarily Unreachable" received from the MME / SGSN is mapped to the reason value "TEMPORARILY_NOT_REACHABLE". This response may include the requested retransmission time to indicate to the SCS / AS the expected time when the UE is reachable, allowing the SCS / AS to prepare for any reconfiguration for the RDS port resources.

[0151] At 9.6, if necessary, the MME / SGSN pagees the UE and transmits non-IP data to the UE via data transmission through the MME / SGSN procedure. If the MME / SGSN is able to initiate NIDD transmission at 9.6, then at 9.7, the MME / SGSN sends an "NIDD Submission Response (Reason)" message to the SCEF, acknowledging the "NIDD Submission Request" received from the SCEF at 9.3.

[0152] If the SCEF receives a successful transmission response from the MME / SGSN, at 9.8 the SCEF should return a "202 Accept" to the SCS / AS to indicate that processing is still in progress, and the process continues at 9.9; otherwise, at 9.8 the SCEF should reply to the SCS / AS with a "500 Internal Server Error" and an appropriate reason value indicating the cause of the transmission failure. At 9.9, the UE initiates the MO NIDD procedure to include an RDS response for port release.

[0153] If the "skipUeInquiry" indication is set to "false" and the SCEF receives a response from the UE (whether successful or failed (e.g., a failure due to the RDS port resource already being released at the UE)), the SCEF releases the "individual ManagePort configuration" resource and notifies the SCS / AS of the currently reserved port at 9.10 (see below for reference). Figure 10 (As stated above). At 9.11, SCS / AS acknowledges the notification sent from SCEF.

[0154] Figure 10 This is a sequence diagram illustrating a UE-initiated process for dynamically reserving, releasing, or notifying RDS port resources according to another embodiment of this disclosure.

[0155] As shown in the figure, at point 10.1, the UE sends MO non-IP data to the MME / SGSN. This MO non-IP data carries an RDS request, which can be a request to reserve, release, or notify RDS port resources. At point 10.2, the MME / SGSN sends a "NIDD Submit Request" message carrying the RDS request to the SCEF. At point 10.3, the SCEF replies to the MME / SGSN with a "NIDD Submit Response" message (manageEntity in Table 1).

[0156] If the RDS request is a request to reserve RDS port resources (including NEF ports and UE ports), then when the SCEF port and / or UE port do not exist in any NIDD configuration in the same APN, the SCEF reserves the RDS port resources (“individual ManagePort Configuration” resources) and marks the RDS port resources as created by the UE.

[0157] If the RDS request is a request to release RDS port resources, then SCEF releases the RDS port resources (“individualManagePort Configuration” resources) when the RDS port resources exist in the same NIDD configuration and the RDS port resources are reserved by the UE (refer to the manageEntity of the resource).

[0158] If the RDS request is a request for RDS port resources (including NEF port and UE port) reserved at the UE, then when the SCEF port and / or UE port do not exist in any NIDD configuration in the same APN, the SCEF reserves the RDS port resources (“individual ManagePort Configuration” resources) and marks the RDS port resources as created by the UE (manageEntity in Table 1).

[0159] Then, at 10.4, the SCEF notifies the SCS / AS of an HTTP POST request including the currently reserved RDS port, and at 10.5, the SCS / AS acknowledges the POST request. At 10.6, if the RDS request is a request to reserve / release RDS port resources, the SCEF sends a response to the UE according to the MT NIDD procedure.

[0160] Corresponding to method 100 or 200 as described above, a network node is provided. Figure 11 This is a block diagram of a network node 1100 for implementing NEF according to an embodiment of the present disclosure.

[0161] When NEF is implemented, network node 1100 can be operated to perform actions such as Figure 1 Method 100 is shown. (For example...) Figure 11 As shown, network node 1100 includes a receiving unit 1110 configured to receive from the AF a request for dynamically reserving RDS port resources associated with the NIDD configuration. The request includes an indication of whether confirmation with the terminal device is required for the reservation of the RDS port resources. Network node 1100 also includes a sending unit 1120 configured to send a response to the request to the AF.

[0162] In this embodiment, the request may include a Uniform Resource Identifier (URI) for the RDS port resource. The URI indicates the first port at the NEF and the second port at the terminal device.

[0163] In an embodiment, network node 1100 may further include an RDS port management unit 1130. When the indication indicates that the reservation of RDS port resources does not require confirmation with the terminal device, the RDS port management unit 1130 may be configured to reserve RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration. In this case, the response may indicate that the RDS port resources have already been reserved at the NEF.

[0164] In an embodiment, the sending unit 1120 can also be configured to notify the terminal device that the RDS port resources have been reserved at NEF.

[0165] In an embodiment, when the indication indicates that the reservation of RDS port resources needs to be confirmed with the terminal device, the RDS port management unit 1130 can also be configured to: initiate an interaction with the terminal device to reserve RDS port resources at the terminal device when the first port and / or the second port does not exist in any NIDD configuration.

[0166] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0167] In this embodiment, the receiving unit 1110 may also be configured to receive an RDS response from the terminal device, the RDS response confirming the reservation of RDS port resources. The RDS port management unit 1130 may also be configured to reserve RDS port resources at the NEF. The sending unit 1120 may also be configured to notify the AF of one or more RDS ports currently reserved at the NEF.

[0168] In an embodiment, the RDS port management unit 1130 can also be configured to maintain a record at the NEF that the RDS port resources are retained by the AF.

[0169] In an embodiment, the receiving unit 1110 may also be configured to receive an RDS response indicating a failed confirmation from the terminal device, and the sending unit 1120 may also be configured to notify the AFN of one or more RDS ports currently reserved at the NEF.

[0170] In an embodiment, when the indication indicates that the reservation of RDS port resources needs to be confirmed with the terminal device, and when NEF is unable to interact with the terminal device because a packet data network (PDN) connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0171] In an embodiment, when the first port and / or the second port already exist in any NIDD configuration, the response may indicate that the RDS end-day resource reservation at NEF has failed.

[0172] Alternatively, when NEF is implemented, network node 1100 can be operational to perform actions such as Figure 2 Method 200 is shown. (e.g.) Figure 11 As shown, network node 1100 includes a receiving unit 1110 configured to receive from the AF a request for dynamically releasing RDS port resources associated with the NIDD configuration. The request includes an indication of whether confirmation with the terminal device is required for the release of the RDS port resources. Network node 1100 also includes a sending unit 1120 configured to send a response to the request to the AF.

[0173] In an embodiment, network node 1100 may further include an RDS port management unit 1130. When the indication indicates that the release of RDS port resources does not require confirmation with the terminal device, the RDS port management unit 1130 may be configured to: release the RDS port resources at the NEF when the RDS port resources exist in the NIDD configuration and are reserved by the AF, and the response may indicate that the RDS port resources have been released at the NEF.

[0174] In an embodiment, the sending unit 1120 can also be configured to notify the terminal device that the RDS port resources have been released at NEF.

[0175] In an embodiment, when the indication requires confirmation with the terminal device for the release of RDS port resources, the RDS port management unit 1130 can also be configured to: when the RDS port resources exist in the NIDD configuration and the RDS port resources are reserved by AF, initiate an interaction with the terminal device to release the RDS port resources at the terminal device.

[0176] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0177] In this embodiment, the receiving unit 1110 may also be configured to receive an RDS response from the terminal device, the RDS response confirming the release of RDS port resources or indicating a failure to release RDS port resources. The RDS port management unit 1130 may also be configured to release RDS port resources at the NEF. The sending unit 1120 may also be configured to notify the AF of one or more RDS ports currently reserved at the NEF.

[0178] In an embodiment, when the RDS port resource is not present in the NIDD configuration or is not reserved by the AF, the response may indicate a failure to release the RDS port resource at the NEF.

[0179] In an embodiment, when the indication requires confirmation with the terminal device for the release of RDS port resources, and when NEF is unable to interact with the terminal device because a PDN connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0180] Units 1110 and 1120, and optional unit 1130, can be implemented as a purely hardware solution or a combination of software and hardware, for example, by one or more of the following: a processor or microprocessor and suitable software, and a memory, programmable logic device (PLD) or other electronic component or processing circuitry for storing the software, configured to perform the above and, for example, in Figure 1 or Figure 2 The actions shown in the image.

[0181] Corresponding to method 300 as described above, a network node is provided. Figure 12 This is a block diagram of a network node 1200 for implementing NEF according to an embodiment of the present disclosure.

[0182] When NEF is implemented, network node 1200 can be operated to perform actions such as Figure 3 Method 300 is shown. (For example...) Figure 12 As shown, network node 1200 includes a receiving unit 1210 configured to receive RDS requests associated with RDS port resources from an end device during the MONIDD process associated with the NIDD configuration. Network node 1200 also includes a sending unit 1220 configured to notify the AF associated with the NIDD configuration of one or more RDS ports currently reserved at the NEF.

[0183] In this embodiment, the RDS request can be used to reserve RDS port resources and includes a URI of the RDS port resources. The URI indicates a first port at the NEF and a second port at the terminal device. Network node 1200 may also include an RDS port management unit 1230 configured to reserve RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration. Sending unit 1220 may also be configured to send an RDS response to the terminal device during the MT NIDD process, indicating that the RDS port resources have been reserved at the NEF.

[0184] In an embodiment, the RDS port management unit can also be configured to maintain an indication at the NEF that the RDS port resources are reserved by the terminal device.

[0185] In this embodiment, an RDS request can be used to release RDS port resources. Network node 1200 may also include an RDS port management unit 1230 configured to release the RDS port resources at NEF when the RDS port resources exist in the NIDD configuration and are reserved by the terminal device. Sending unit 1220 may also be configured to send an RDS response indicating that the RDS port resources have been released at NEF to the terminal device during the MT NIDD process.

[0186] In this embodiment, an RDS request can be used to notify the NEF of RDS port resources reserved at the terminal device. The RDS port resources have URIs indicating a first port at the NEF and a second port at the terminal device. Network node 1200 may also include an RDS port management unit 1230 configured to reserve RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration.

[0187] In an embodiment, the RDS port management unit 1230 can also be configured to maintain a record at the NEF that the RDS port resources are retained by the terminal device.

[0188] Units 1210 and 1220, and optional unit 1230, can be implemented as a purely hardware solution or a combination of software and hardware, for example, by one or more of the following: a processor or microprocessor and suitable software, and a memory, programmable logic device (PLD) or other electronic component or processing circuitry for storing the software, configured to perform the above and, for example, in Figure 3 The actions shown in the image.

[0189] Figure 13 This is a block diagram of a network node 1300 for implementing NEF according to another embodiment of the present disclosure.

[0190] Network node 1300 includes processor 1310 and memory 1320. Memory 1320 may contain instructions executable by processor 1310, thereby enabling network node 1300 to perform, for example, the aforementioned instructions when implementing NEF. Figure 1 The described process involves actions. Specifically, memory 1320 contains instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: receive a request from AF for dynamically reserving RDS port resources associated with the NIDD configuration. This request includes an indication of whether confirmation with the end device is required for the reservation of the RDS port resources. Memory 1320 also contains instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: send a response to the request to AF.

[0191] In this embodiment, the request may include a URI for an RDS port resource. The URI indicates a first port at the NEF and a second port at the terminal device.

[0192] In an embodiment, memory 1320 may further contain instructions executable by processor 1310, thereby enabling network node 1300 to: reserve RDS port resources at NEF when implementing NEF: when the indication indicates that the reservation of RDS port resources requires confirmation with the end device; and when the first port and / or the second port is not present in any NIDD configuration. A response may indicate that the RDS port resources have already been reserved at NEF.

[0193] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF, notify terminal devices that RDS port resources have been reserved at NEF after the reservation operation.

[0194] In an embodiment, the memory 1320 may also contain instructions executable by the processor 1310, thereby enabling the network node 1300 to, when implementing NEF, initiate interaction with the terminal device to reserve the RDS port resources at the terminal device when the instruction indicates that the reservation of RDS port resources requires confirmation with the terminal device, and when the first port and / or the second port is not present in any NIDD configuration.

[0195] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0196] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: receive an RDS response from an end device after sending a response, the RDS response confirming the reservation of RDS port resources; reserve RDS port resources at NEF; and notify AF of one or more RDS ports currently reserved at NEF.

[0197] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: maintain a record at NEF that the RDS port resources are retained by AF after the retention operation.

[0198] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF,: receive an RDS response indicating confirmation failure from the terminal device after an initiated operation; and notify AF of one or more RDS ports currently reserved at NEF.

[0199] In an embodiment, when the indication indicates that the reservation of RDS port resources needs to be confirmed with the terminal device, and when NEF is unable to interact with the terminal device because a PDN connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0200] In an embodiment, when the first port and / or the second port already exist in any NIDD configuration, the response may indicate that reserving the RDS port resource at NEF has failed.

[0201] Alternatively, network node 1300 includes processor 1310 and memory 1320. Memory 1320 may contain instructions executable by processor 1310, thereby enabling network node 1300 to perform, for example, the aforementioned instructions when implementing NEF. Figure 2 The described process involves actions. Specifically, memory 1320 contains instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: receive from AF a request for the dynamic release of RDS port resources associated with the NIDD configuration. This request includes an indication of whether confirmation with the end device is required for the release of the RDS port resources. Memory 1320 also contains instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: send a response to the request to AF.

[0202] In an embodiment, memory 1320 may further contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF: release the RDS port resource at NEF when the instruction indicates that the release of the RDS port resource does not require confirmation with the end device, and when the RDS port resource exists in the NIDD configuration and is reserved by AF. A response may indicate that the RDS port resource has been released at NEF.

[0203] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to: notify end devices that RDS port resources have been released at NEF when implementing NEF.

[0204] In an embodiment, the memory 1320 may also contain instructions executable by the processor 1310, thereby enabling the network node 1300 to, when implementing NEF, initiate an interaction with the terminal device to release the RDS port resources at the terminal device when the instruction indicates that the release of the RDS port resources requires confirmation with the terminal device, or when the RDS port resources exist in the NIDD configuration and are reserved by the AF.

[0205] In one embodiment, the response may indicate that the process is still in progress before the timer associated with the request expires.

[0206] In an embodiment, the memory 1320 may also contain instructions executable by the processor 1310, thereby enabling the network node 1300 to, when implementing NEF: receive an RDS response from the terminal device after sending a response, the RDS response confirming the release of RDS port resources or indicating a failure to release RDS port resources; release RDS port resources at NEF; and notify the AF of one or more RDS ports currently reserved at NEF.

[0207] In an embodiment, when the RDS port resource is not present in the NIDD configuration or is not reserved by the AF, the response may indicate a failure to release the RDS port resource at the NEF.

[0208] In an embodiment, when the indication requires confirmation with the terminal device for the release of RDS port resources, and when NEF is unable to interact with the terminal device because a PDN connection has not yet been established with the terminal device, the response may indicate that a PDN connection has not yet been established with the terminal device.

[0209] Alternatively, network node 1300 includes processor 1310 and memory 1320. Memory 1320 may contain instructions executable by processor 1310, thereby enabling network node 1300 to perform, for example, the aforementioned instructions when implementing NEF. Figure 3 The described process involves actions. Specifically, memory 1320 contains instructions executable by processor 1310, thereby enabling network node 1300 to: receive RDS requests associated with RDS port resources from end devices during the MO NIDD process associated with NIDD configuration, and notify the AF associated with NIDD configuration of one or more RDS ports currently reserved at NEF.

[0210] In this embodiment, an RDS request may be used to reserve RDS port resources and includes a URI of the RDS port resources. The URI indicates a first port at the NEF and a second port at the terminal device. The memory 1320 may also contain instructions executable by the processor 1310, thereby enabling the network node 1300 to: reserve RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration, and to send an RDS response to the terminal device indicating that the RDS port resources have been reserved at the NEF during the MT NIDD process.

[0211] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to, when implementing NEF, indicate that the RDS port resources maintained by NEF are reserved by the terminal device.

[0212] In an embodiment, an RDS request can be used to release RDS port resources, and memory 1320 can also contain instructions executable by processor 1310, thereby enabling network node 1300 to: release RDS port resources at NEF when the RDS port resources exist in the NIDD configuration and are reserved by the end device; and send an RDS response to the end device indicating that the RDS port resources have been released at NEF during MT NIDD.

[0213] In an embodiment, an RDS request can be used to notify the NEF of RDS port resources reserved at the terminal device. The RDS port resources have URIs indicating a first port at the NEF and a second port at the terminal device. The memory 1320 may also contain instructions executable by the processor 1310, thereby enabling the network node 1300 to, when implementing the NEF, reserve RDS port resources at the NEF when the first port and / or the second port are not present in any NIDD configuration.

[0214] In an embodiment, memory 1320 may also contain instructions executable by processor 1310, thereby enabling network node 1300 to operate in implementing NEF to maintain a record at NEF that RDS port resources are retained by the terminal device.

[0215] Corresponding to method 400 as described above, a network node is provided. Figure 14 This is a block diagram of a network node 1400 for implementing AF according to an embodiment of the present disclosure.

[0216] When AF is implemented, network node 1400 becomes operable to perform actions such as Figure 4 Method 400 is shown. (For example...) Figure 14As shown, network node 1400 includes a sending unit 1410 configured to send a request to NEF to dynamically reserve or release RDS port resources associated with NIDD configuration. The request includes an indication of whether confirmation with the end device is required for the reservation or release of the RDS port resources. Network node 1400 also includes a receiving unit 1420 configured to receive a response to the request from NEF.

[0217] In an embodiment, when the indication indicates that the retention or release of RDS port resources does not require confirmation with the terminal device, the response may indicate that the RDS port resources have been retained or released at the NEF, or indicate the failure to retain or release the RDS port resources at the NEF.

[0218] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate that confirmation is still in progress before the timer associated with the request expires.

[0219] In an embodiment, the receiving unit 1420 may also be configured to receive, after receiving a response, a notification from the NEF of one or more RDS ports currently reserved at the NEF.

[0220] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate a failure to reserve RDS port resources at NEF, or indicate that a PDN connection has not yet been established with the terminal device.

[0221] Units 1410 and 1420 may be implemented as a purely hardware solution or a combination of software and hardware, for example, by one or more of the following: a processor or microprocessor and suitable software, and a memory, programmable logic device (PLD) or other electronic component or processing circuitry for storing the software, configured to perform the above and, for example, in Figure 4 The actions shown in the image.

[0222] Figure 15 is a block diagram of a network node 1500 for implementing AF according to another embodiment of the present disclosure.

[0223] Network node 1500 includes processor 1510 and memory 1520. Memory 1520 may contain instructions executable by processor 1510, thereby enabling network node 1500 to perform, for example, the instructions mentioned above when implementing AF. Figure 4The described process involves actions. Specifically, memory 1520 contains instructions executable by processor 1510, thereby enabling network node 1500 to, upon implementing AF,: send a request to NEF for dynamically reserving or releasing RDS port resources associated with the NIDD configuration. This request includes an indication of whether confirmation with the end device is required for the reservation or release of the RDS port resources. Memory 1520 also contains instructions executable by processor 1510, thereby enabling network node 1500 to, upon implementing AF, receive a response to this request from NEF.

[0224] In an embodiment, when the indication indicates that the retention or release of RDS port resources does not require confirmation with the terminal device, the response may indicate that the RDS port resources have been retained or released at the NEF, or indicate the failure to retain or release the RDS port resources at the NEF.

[0225] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate that confirmation is still in progress before the timer associated with the request expires.

[0226] In an embodiment, memory 1520 may also contain instructions executable by processor 1510, thereby enabling network node 1500 to, when implementing AF: receive notification from NEF of one or more RDS ports currently reserved at NEF after receiving a response.

[0227] In an embodiment, when the indication requires confirmation with the terminal device for the reservation or release of RDS port resources, the response may indicate a failure to reserve RDS port resources at NEF, or indicate that a PDN connection has not yet been established with the terminal device.

[0228] This disclosure also provides at least one computer program product in the form of non-volatile or volatile memory (e.g., non-transitory computer-readable storage media, electrically erasable programmable read-only memory (EEPROM), flash memory, and hard disk drives). The computer program product includes a computer program. The computer program includes: code / computer-readable instructions that, when executed by processor 1310, cause network node 1300 to perform, for example, the aforementioned... Figure 1 , Figure 2 or Figure 3 The described process of action; or code / computer-readable instructions, which, when executed by processor 1510, cause network node 1500 to perform, for example, in conjunction with the preceding... Figure 4 The actions described in the process.

[0229] Computer program products can be configured as computer program code constructed from computer program modules. Computer program modules can substantially execute... Figure 1 , Figure 2 , Figure 3 or Figure 4 The actions of the process shown.

[0230] The processor may be a single CPU (Central Processing Unit), but may also include two or more processing units. For example, the processor may include a general-purpose microprocessor; an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor, such as an application-specific integrated circuit (ASIC). The processor may also include onboard memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may include a non-transitory computer-readable storage medium storing the computer program. For example, the computer program product may be flash memory, random access memory (RAM), read-only memory (ROM), or EEPROM, and in alternative embodiments, the aforementioned computer program modules may be distributed across different computer program products in the form of memory.

[0231] The present disclosure has been described above with reference to its embodiments. It should be understood that various modifications, substitutions, and additions can be made by those skilled in the art without departing from the spirit and scope of the present disclosure. Therefore, the scope of the present disclosure is not limited to the specific embodiments described above, but is defined only by the appended claims.

Claims

1. A method (100) in Network Open Functions (NEF), comprising: The application function AF receives (110) a request for dynamically reserving a reliable data service RDS port resource associated with a non-Internet Protocol "IP" data transfer NIDD configuration, the request including an indication of whether the reservation of the RDS port resource needs to be confirmed with the terminal device; as well as Send (120) a response to the request to the AF.

2. The method (100) according to claim 1, wherein, The request includes a Uniform Resource Identifier (URI) for the RDS port resource, the URI indicating a first port at the NEF and a second port at the terminal device.

3. The method (100) according to claim 2, wherein, When the indication indicates that the reservation of the RDS port resource does not require confirmation with the terminal device: When the first port and / or the second port are not present in any NIDD configuration, the RDS port resource is reserved at the NEF. The response indicates that the RDS port resource has been reserved at the NEF.

4. The method (100) according to claim 3, further comprising: After the retention, The terminal device is notified that the RDS port resource has been reserved at the NEF.

5. The method (100) according to claim 2, further comprising: When the indication requires confirmation with the terminal device to reserve the RDS port resources. When the first port and / or the second port are not present in any NIDD configuration, an interaction with the terminal device is initiated to reserve the RDS port resources at the terminal device.

6. The method (100) according to claim 5, wherein, The response indicates that the confirmation is still in progress before the timer associated with the request expires.

7. The method (100) according to claim 6, further comprising: After sending the response Receive an RDS response from the terminal device, the RDS response confirming the reservation of the RDS port resources; The RDS port resources are reserved at the NEF. as well as Notify the AF of one or more RDS ports currently reserved at the NEF.

8. The method (100) according to claim 3 or 7, further comprising: After the retention, The RDS port resources maintained at the NEF are records retained by the AF.

9. The method (100) according to claim 5, further comprising: After the initiation, Receive from the terminal device an RDS response indicating the failure of the confirmation; as well as Notify the AF of one or more RDS ports currently reserved at the NEF.

10. The method (100) according to claim 1 or 2, wherein, The response indicates that a PDN connection has not been established with the terminal device when the indication indicates that the reservation of the RDS port resources needs to be confirmed with the terminal device, and when the NEF is unable to interact with the terminal device because a Packet Data Network (PDN) connection has not yet been established with the terminal device.

11. The method (100) according to claim 2, wherein, The response indicates that reserving the RDS port resource at NEF failed when the first port and / or the second port already exist in any NIDD configuration.

12. A method (200) in Network Open Functions (NEF), comprising: The application function AF receives (210) a request for dynamically releasing a reliable data service RDS port resource associated with a non-Internet Protocol "IP" data transfer NIDD configuration, the request including an indication of whether the release of the RDS port resource requires confirmation with the terminal device; as well as Send (220) a response to the request to the AF.

13. The method (200) according to claim 12, further comprising: When the indication indicates that the release of the RDS port resources does not require confirmation with the terminal device. When the RDS port resource exists in the NIDD configuration and is reserved by the AF, the RDS port resource is released at the NEF. The response indicates that the RDS port resource has been released at the NEF.

14. The method (200) according to claim 13, further comprising: The terminal device is notified that the RDS port resource has been released at the NEF.

15. The method (200) according to claim 12, further comprising: When the instruction indicates that the release of the RDS port resources requires confirmation with the terminal device. When the RDS port resource exists in the NIDD configuration and is reserved by the AF, an interaction with the terminal device is initiated to release the RDS port resource at the terminal device.

16. The method (200) according to claim 15, wherein, The response indicates that the confirmation is still in progress before the timer associated with the request expires.

17. The method (200) according to claim 16, further comprising: After sending the response Receive an RDS response from the terminal device, the RDS response confirming the release of the RDS port resources or indicating the failure to release the RDS port resources; Release the RDS port resources at the NEF; as well as Notify the AF of one or more RDS ports currently reserved at the NEF.

18. The method (200) according to claim 12, wherein, The response indicates a failure to release the RDS port resource at the NEF when the RDS port resource is not present in the NIDD configuration or is not reserved by the AF.

19. The method (200) according to claim 12, wherein, When the indication indicates that the release of the RDS port resources requires confirmation with the terminal device, and when the NEF is unable to interact with the terminal device because a Packet Data Network (PDN) connection has not yet been established with the terminal device, the response indicates that a PDN connection has not yet been established with the terminal device.

20. A network node (1300) including a processor (1310) and a memory (1320), the memory (1320) including instructions that enable the network node (1300) to implement a Network Open Function (NEF), the network node being configured to: when implementing the NEF, perform the method according to any one of claims 1 to 19.

21. A computer-readable storage medium having computer-readable instructions, wherein, When the computer-readable instructions are executed by the processor of the network node, the computer-readable instructions configure the network node to perform the method according to any one of claims 1 to 19.

22. A method (400) for applying function AF, comprising: Send (410) to the Network Open Function (NEF) a request to dynamically retain or release Reliable Data Service (RDS) port resources associated with a Non-Internet Protocol "IP" data transfer (NIDD) configuration, the request including an indication of whether the retention or release of the RDS port resources requires confirmation with the terminal device. as well as Receive (420) a response to the request from the NEF.

23. The method (400) according to claim 22, wherein, When the indication indicates that the retention or release of the RDS port resource does not require confirmation with the terminal device, the response indicates that the RDS port resource has been retained or released at the NEF, or indicates a failure to retain or release the RDS port resource at the NEF.

24. The method (400) according to claim 22, wherein, When the indication requires confirmation with the terminal device for the reservation or release of the RDS port resources, the response indicates that the confirmation is still in progress until the timer associated with the request expires.

25. The method (400) according to claim 24, further comprising: After receiving the response Receive notifications from the NEF regarding one or more RDS ports currently reserved at the NEF.

26. The method (400) according to claim 22, wherein, When the indication requires confirmation with the terminal device for the reservation or release of the RDS port resource, the response indicates a failure to reserve the RDS port resource at the NEF, or indicates that a connection to the Packet Data Network (PDN) has not yet been established with the terminal device.

27. A network node (1500) including a processor (1510) and a memory (1520), the memory (1520) including instructions enabling the network node (1500) to implement an application function AF, the network node being configured to: when implementing the AF, perform the method according to any one of claims 22 to 26.

28. A computer-readable storage medium having computer-readable instructions, wherein, When the computer-readable instructions are executed by the processor of the network node, the computer-readable instructions configure the network node to perform the method according to any one of claims 22 to 26.

Images