Data retrieval and subscription optimization

Abstract

According to one aspect, a method is provided that is performed by a network function consumer (NFC), comprising sending (701) a request (401) to a network function producer (NFP), the request (401) being for context information for a first wireless device, the request (401) comprising one or more filter values ​​that identify a subset of context information for the first wireless device that is required by the NFC, the subset of context information for the first wireless device that is required by the NFC is associated with a particular protocol data unit (PDU) session.

Description

[Technical Field]

[0001] The present disclosure relates to Network Function (NF) Consumers (NFCs) and NF Producers (NFPs), and more particularly to requesting and retrieving data from an NFP by an NFC. [Background technology]

[0002] The present disclosure relates to a Network Function (NF) node, called an NF consumer (NFC), that consumes services provided by other NF nodes, called NF producers (NFPs).

[0003] The 3rd Generation Partnership Project (3GPP®) defines procedures to support Protocol Data Unit (PDU) session continuity during inter-system mobility procedures between 5th Generation Systems (5GS) and Evolved Packet Systems (EPS), or between 5GS and other types of systems, such as WiFi.

[0004] When a user equipment (UE) initially attaches to 5GS, a node called PGW-C+SMF (Control Plane Packet Data Network (PDN) Gateway (PGW-C) + Session Management Function (SMF)) stores the PGW-C+SMF Fully Qualified Domain Name (FQDN) and Network Function (NF) instance identification information for the connected data network name (DNN) / access point name (APN) in the Unified Data Management (UDM) node during the SMF registration procedure.

[0005] When the UE initially connects to the WiFi network, the PGW-C+SMF also stores the PGW-C+SMF FQDN and NF instance identification information for the connected DNN / APN in the UDM node during the SMF registration procedure if the PGW-C+SMF uses the N10 interface for WiFi access.

[0006] During mobility from WiFi to 5GS or from 5GS to WiFi, the Access and Mobility Management Function (AMF) reads the SMF instance identity from the UDM, or the Evolved Packet Data Gateway (ePDG) downloads the PGW-C+SMF FQDN from the Authentication, Authorization, and Accounting (AAA) server or the Home Subscriber Server (HSS). Note that the HSS queries this information from the UDM via the User Data Interworking, Coexistence, and Migration (UDICOM) interface so that the serving nodes (AMF and ePDG) can select the appropriate PGW-C+SMF node to support PDU session continuity. According to 3GPP® standard 3GPP® TS 29.503 “5G System; Unified Data Management Services; Stage 3 (Release 17),” v17.5.0 (2021-12), an NF service consumer (NFC), which may be, for example, an AMF or HSS, sends a request to a UDM to receive a UE’s “Context In SMF” data. This data is referred to herein as “UEContextInSmfData.” The request includes the UE’s identity / identifier (e.g., subscription persistent identifier (SUPI), / {supi}), the type of information requested ( / ue-context-in-smf-data), and query parameters (supported-features). This request is illustrated in Figure 1, which shows signaling between the NFC and the NFP in the form of a UDM. Signal 1 is a GET request from the NFC to the UDM, including the UE’s identifier and the type of information requested (ue-context-in-smf-data).

[0007] If successful, the UDM responds with "200 OK" (signal 2a) with a message body containing the context data in the SMF of the UE associated with the requesting NFC (UEContextInSmfData). If there is no valid subscription data for the UE identified in the request, the Hypertext Transfer Protocol (HTTP) status code "404 Not Found" is returned, including additional error information in the response body (e.g., in the "ProblemDetails" element).

[0008] As shown in Figure 2, an NF service consumer (e.g., AMF, HSS) can subscribe to notifications of data changes in UeContextInSmfData by sending a request to the UDM. The request (signal 1 in Figure 2) can include a callback uniform resource indicator (URI) and the URI of the monitored resource.

[0009] If successful (i.e., subscription created), the UDM responds with a "201 Created" message (signal 2a in Figure 2). If the UE does not have valid subscription data, the HTTP status code "404 Not Found" is returned (signal 2b in Figure 2). If the UE subscription data exists but the subscription to the requested data change notifications cannot be created, the HTTP status code "501 Not Implemented" is returned (signal 2c in Figure 2).

[0010] Once a subscription is created in the UDM, the UDM notifies the NF service consumer (which has subscribed to receive such notifications) about changes in the subscription data in the UeContextInSmfData received in SdmSubscription, as shown in Figure 3. Thus, signal 1 in Figure 3 shows the UDM sending a notification to the NFC, and signal 2 in Figure 3 is a "204 No Content" message from the NFC to the UDM.

[0011] Section 6.1.6.2.16 of 3GPP TS 29.503 defines UEContextInSmfData as follows:

[0012] [Table 1]

[0013] Section 4.2.2.2.2 "General registration" of 3GPP (registered trademark) TS 23.502 "Procedures for 5G System (5GS); Stage 2 (Release 17)" v17.3.0 (2021-12) states that the AMF can obtain UeContextInSmfData during the registration procedure and subscribe to UeContextInSmfData.

[0014] Section 4.3.2.2 "UE Request PDU Session Establishment" of 3GPP (registered trademark) TS 23.502, referring to 4.3.2.2.1 16c, states that when a PDU session is established, the SMF shall request the Nudm_UECM_Registration (SUPI, DNN, Single Network Slice Selection Assistance Information (S-NSSAI), PDU Session ID, SMF Identity, Serving ID) for a given PDU session. Public athletics The UE registers to the UDM using the mobile network (PLMN) ID (including the NID). As a result, the UDM stores the following information: SUPI, SMF identity, and the associated DNN, S-NSSAI, PDU session ID, and serving network. The UDM can further store this information in the UDR via Nudr_DM_Update (including the SUPI, subscription data, and UE context in the SMF data).

[0015] If the PDU session establishment is for emergency services, for an authenticated non-roaming UE, the SMF can register with the UDM using Nudm_UECM_Registration (including SUPI, PDU session ID, SMF identification information, and emergency service indication) for a given PDU session applicable to emergency services. As a result, the UDM stores the applicable PDU session for emergency services.

[0016] For an AMF that subscribes to UeContextInSmfData, the UDM sends a UeContextInSmfData notification to the AMF when the SMF / HSS registers the PDU session information or PGW information (pgw information) of a PDU session in the UDM.

[0017] Similarly, the procedures for GET and UeContextInSmfData subscribe / notify from the HSS to the UDM, and for GET and UeContextInPgwData subscribe / notify from the UDM to the HSS are defined in 3GPP TS 23.632, "User data interworking, coexistence and migration; Stage 2; (Release 17)", v17.0.0(2021-06), section 5.3.4.

[0018] Section 6.2.6.2.2 of 3GPP® TS 29.563 “5G System; Home Subscriber Server (HSS) services for interworking with Unified Data Management (UDM); Stage 3”, v17.3.0 (2021-12) defines UEContextInPgwData as shown in the table below.

[0019] [Table 2] Summary of the Invention

[0020] Currently, there is a specific challenge: Currently, when AMF or HSS retrieves or subscribes to UeContextInSmfData from UDM, the entire UeContextInSmfData is retrieved or subscribed to.

[0021] If the UE has multiple PDU sessions to be created, the UDM notifies the AMF or HSS of UeContextInSmfData when each PDU session is established if the AMF or HSS subscribes to UeContextInSmfData for the UDM. However, the AMF or HSS may only be interested in Internet Protocol (IP) Multimedia Subsystem (IMS)-related or emergency PDU sessions that may be handed over between WiFi and 5GS. In this case, notifying UeContextInSmfData of non-IMS-related PDU sessions that are not useful to the AMF or HSS increases unnecessary signaling in the network.

[0022] Therefore, when the AMF or HSS extracts UeContextInSmfData from the UDM, the UeContextInSmfData containing all PDU sessions is sent from the UDM to the AMF or HSS. Similarly, non-IMS related PDU sessions are unnecessary and useless for the AMF or HSS, but they increase the size of the data sent between the AMF or HSS and the UDM.

[0023] A similar issue occurs when an HSS looks up or subscribes to UeContextInSmfData or UeContextInAmfData (EpsInterworkingInfo) from a UDM, or when a UDM looks up or subscribes to UeContextInPgwData from an HSS.

[0024] Certain aspects of the present disclosure and their embodiments may provide solutions to these and other problems.

[0025] In certain embodiments of the present disclosure, a new query parameter may be specified when an NF consumer (e.g., an AMF) retrieves UeContextInSmfData using the GET method to indicate that the AMF only needs to obtain the pduSessions and pgwInfo in UeContextInSmfData for a specified DNN, e.g., an IMS DNN, or emergency services.

[0026] When an NF producer (e.g., UDM) receives a GET request for UeContextInSmfData, the NFP sends only pduSessions and pgwInfo for the specified DNN to the AMF (or other NFC), or sends only emergencyInfo to the AMF (or other NFC) according to the value of the query parameter.

[0027] Embodiments provide a new parameter to be added to "SdmSubscription" for the AMF (or other NFC) to indicate that the AMF (or other NFC) subscribes only to changes in pduSessions or pgwInfo in UeContextInSmfData for a specified DNN, such as an IMS DNN, or emergencyInfo for emergency services. In some embodiments of the present disclosure, this parameter is named "ueConSmfDataSubFilter," and in other embodiments, this parameter is named "ueContextInSmfDataSubscription."

[0028] The embodiment provides that a specified DNN can be configured in the AMF (or other NFC).

[0029] When a change in pduSessions or pgwInfo of a specified DNN occurs, the UDM (or other NFP) notifies the AMF (or other NFC) only of the corresponding pduSessions or pgwInfo in UeContextInSmfData. When a change in emergency service session occurs, the UDM (or other NFP) can notify the AMF (or other NFC) only of emergencyInfo.

[0030] The above solution refers to AMF, UDM, and UeContextInSmfData as examples of NF consumer, NF producer, and target resources, respectively. It will be appreciated that the same principles described above can also be used in the following scenarios: -HSS as NF consumer, UDM as NF producer, UeContextInSmfData or UeContextInAmfData(EpsInterworkingInfo) as target resource, UDM as NF consumer, HSS as NF producer, UeContextInPGwData as target resource.

[0031] Therefore, the present disclosure provides a method for the AMF or HSS to obtain and subscribe only to pduSession, pgwInfo, or emergencyInfo related to the IMS, which reduces the size of data transmission and reduces notification signaling between the AMF or HSS (or other NFC) and the UDM (or other NFP).

[0032] Certain embodiments may provide one or more of the following technical advantages: In these embodiments, PDU session or PGW information data that the AMF / HSS is not interested in is not sent from the UDM to the AMF / HSS, saving data transmission bandwidth between the AMF / HSS and the UDM.

[0033] Since the embodiments of the present disclosure provide a way for the AMF / HSS to subscribe only to specified DNN or emergencyInfo changes in UeContextInSmfData, notification signaling to the AMF / HSS for uninterested PDU session or PGW information changes can be avoided between the AMF / HSS and the UDM.

[0034] According to a first aspect, there is provided a method performed by an NFC. The method comprises sending a request for context information for a first wireless device to an NFP. The request comprises one or more filter values ​​that identify a subset of context information for the first wireless device required by the NFC. The subset of context information for the first wireless device required by the NFC may be associated with a particular PDU session.

[0035] According to a second aspect, a method is provided that is performed by an NFP. The method comprises receiving a request for context information for a first wireless device from an NFC. The request comprises one or more filter values ​​that identify a subset of context information for the first wireless device required by the NFC, and transmitting the wireless device context information to the NFC. The transmitted wireless device context information comprises the subset of context information for the first wireless device selected according to the one or more filter values. The subset of context information for the first wireless device required by the NF consumer may be associated with a particular PDU session. The context information may be stored by the NFP.

[0036] According to a third aspect, there is provided a network node configured to perform a method according to the first and / or second aspect, or any embodiment thereof.

[0037] According to a fourth aspect, there is provided an NFC configured to send a request to an NFP, the request being for context information for a first wireless device, the request comprising one or more filter values ​​that identify a subset of the context information for the first wireless device needed by the NFC, the subset of the context information for the first wireless device needed by the NFC may be associated with a particular PDU session.

[0038] According to a fifth aspect, an NFP configured to receive a request from an NF consumer is provided. The request is for context information for a first wireless device, and the request comprises one or more filter values ​​that identify a subset of the context information for the first wireless device needed by the NF consumer. The NFP is also configured to wirelessly transmit the device context information to the NF consumer. The transmitted wireless device context information comprises a subset of the context information for the first wireless device selected according to the one or more filter values. The subset of the context information for the first wireless device needed by the NF consumer may be associated with a particular PDU session. The context information may be stored by the NFP.

[0039] According to a sixth aspect, there is provided a network node comprising a processor and a memory, the memory comprising instructions executable by the processor, whereby the network node is operable to perform a method according to the first and / or second aspect, or any embodiment thereof.

[0040] According to a seventh aspect, there is provided an NFC comprising a processor and a memory, the memory including instructions executable by the processor, whereby the NFC is operable to send a request to an NFP. The request is for context information for a first wireless device, the request comprising one or more filter values ​​that identify a subset of the context information for the first wireless device required by the NFC. The subset of the context information for the first wireless device required by the NF consumer may be associated with a particular PDU session.

[0041] According to an eighth aspect, there is provided an NFP comprising a processor and a memory, the memory including instructions executable by the processor, the NFP operable to receive a request from an NFC for context information for a first wireless device, the request comprising one or more filter values ​​identifying a subset of the context information for the first wireless device required by the NFC, and transmit the wireless device context information to the NFC, the transmitted wireless device context information comprising the subset of the context information for the first wireless device selected according to the one or more filter values. The subset of the context information for the first wireless device required by the NF consumer may be associated with a particular PDU session. The context information may be stored by the NFP.

[0042] According to a ninth aspect, there is provided a network node comprising processing circuitry configured to cause the network node to perform any of the steps of the method according to the first and / or second aspect, or any embodiment thereof, and power supply circuitry configured to supply power to the processing circuitry.

[0043] According to a tenth aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured, when executed by a suitable computer or processor, to cause the computer or processor to perform a method according to the first and / or second aspect, or any embodiment thereof. [Brief explanation of the drawings]

[0044] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates the signaling involved in NFC requesting UEContextInSmfData from an NFP in the formation of a UDM. [Figure 2] FIG. 2 is a diagram illustrating the signaling involved in NFC subscribing to a change in UEContextInSmfData in the NFP in the form of a UDM. [Figure 3] FIG. 3 illustrates the signaling involved in the NFP in the form of a UDM, which notifies the NFC of changes to data to which the NFC has subscribed. [Figure 4] FIG. 4 is a diagram illustrating signaling between an NFC and an NFP, according to some embodiments. [Figure 5] FIG. 5 is a diagram illustrating signaling between an NFC and a UDM according to some embodiments. [Figure 6] FIG. 6 is a diagram illustrating signaling between an NFC and a UDM, according to some embodiments. [Figure 7] FIG. 7 is a flowchart illustrating a method performed by an NFC according to various embodiments. [Figure 8] FIG. 8 is a flowchart illustrating a method performed by an NFP, according to various embodiments. [Figure 9] FIG. 9 illustrates an example of a communication system according to some embodiments. [Figure 10]FIG. 10 illustrates a network node according to some embodiments. [Figure 11] FIG. 11 is a block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized. DETAILED DESCRIPTION OF THE INVENTION

[0045] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. Additional information can also be found in the documents listed in the appendix.

[0046] Briefly, embodiments of the techniques described herein relate to the operation of a network node or NF acting as an NFC to an NFP (i.e., the NFC requires services performed by the NFP), and the operation of a network node or NF acting as an NFP to an NFC. FIG. 4 illustrates signaling between an NFC and an NFP, according to some embodiments. The NFC sends a request 401 to the NFP for context information for a UE or other wireless device. Signal 402 indicates that the NFP will send filtered UE context information to the NFC. Request 401 comprises one or more filter values ​​that identify a subset of the context information for the UE that the NFC is interested in receiving. That is, the NFC may not need or want to receive all context information for the UE stored by the NFP, and the filter value in request 401 allows the NFC to signal or indicate to the NFP which portions of the context information should be sent to the NFC in signal 402.

[0047] Request 401 may be a subscription request that establishes a subscription for the UE's context information at the NFP. In this way, the NFP transmits the required context information when there is a change in the stored context information. Alternatively, request 401 may be a search request, in which case the NFP transmits the required context information after receiving the request.

[0048] The filter value may indicate whether the NFC requires context information for an IMS PDU session of an emergency PDU session. The filter value may indicate, for example, whether the NFC wants to receive context information only for the emergency service session, or for a specified network slice (e.g., S-NSSAI), a specified network (e.g., DNN), and / or a specified mobile network (e.g., PLMN).

[0049] The context information requested by signal 401 can be any of UEContextInSmfData, UEContextInAmfData, and UEContextInPgwData.

[0050] NFC can be either AMF, HSS, or UDM, and NFP can be either HSS or UDM.

[0051] In certain embodiments, the NFC is an AMF and the NFP is a UDM. In these embodiments, the context information may be UEContextInSmfData.

[0052] In certain embodiments, the NFC is an HSS and the NFP is a UDM. In these embodiments, the context information may be UEContextInSmfData and / or UEContextInAmfData.

[0053] In certain embodiments, the NFP is a UDM and the NFP is an HSS. In these embodiments, the context information may be UEContextInPgwData.

[0054] The following description section provides an exemplary implementation of the above solution for an NFC in the form of an AMF or HSS to request filtered UeContextInSmfData from an NFP in the form of a UDM. Those skilled in the art will understand from the above description and the following exemplary implementation how to adapt the implementation to a situation where the NFC is an HSS, the NFP is a UDM, and the target resource is UeContextInSmfData or UeContextInAmfData (EpsInterworkingInfo) as the target resource. Similarly, those skilled in the art will understand how to adapt the implementation to a situation where the NFC is a UDM, the NFP is an HSS, and the target resource is UeContextInPGwData.

[0055] Therefore, in the AMF / HSS → UDM scenario, one or more new parameters (filter values) can be added. The parameters can be selected from PLMN ID, singleNssai (sNssai), DNN, and emergencyServices. These parameters can be added to the query parameters in the GET method of UeContextInSmfData. This is shown in the following table, which is a modified version of Table 6.1.3.7.1-1 "URI query parameters supported by the GET method on this resource" in 3GPP TS 29.503 (Section 6.1.3.7 "Resource: UeContextInSmfData" → 6.1.3.7.3 "Resources Standard Methods" → 6.1.3.7.3.1 "GET"). While this example table shows all of the new parameters, it will be understood that a particular embodiment may include only one or a subset of these parameters. The new Information Elements (IEs) in the table below are "single-nssai", "Dnn", "emergencyServices", and "plmn-id".

[0056] [Table 3]

[0057] The corresponding procedure flow is shown in Figure 5, which shows that the NF service consumer (e.g., AMF, HSS) sends a GET request to the UDM to receive the UE's context-in-SMF data. The request includes the UE's identity ( / {supi}), the type of information requested ( / ue-context-in-smf-data), and (values) the new query parameters (supported capabilities, PLMN ID, singleNssai (sNssai), dnn, and emergencyServices). In a specific alternative implementation similar to the first SdmSubscription example below, the new parameters in Table 6.1.3.7.1-1 could instead be "dnnList" and "emergencyInd".

[0058] These query parameters can also be added to the subscription request message. In particular, new parameters dnnList and emergencyInd are added to indicate specific subscription information in UeContextInSmfData. This can be seen in the table below, which is a modified version of table 6.1.6.2.3-1 "Definition of type SdmSubscription" in section 6.1.6.2.3 Type: SdmSubscription of 3GPP TS 29.503. The new IE in the table below is the ueConSmfDataSubFilter entry.

[0059] [Table 4] TIFF0007823208000005.tif254155

[0060] A new subsection defining ueConSmfDataSubFilter is required, which may be found in section 6.1.6.2.x of 3GPP TS 29.503, as shown by the example table below.

[0061] [Table 5]

[0062] The optional features in Table 6.1.8-1 below are defined for the Nudm_SDM Application Programming Interface (API). They can be negotiated using the extension mechanism defined in Section 6.6 of 3GPP TS 29.500.

[0063] [Table 6] TIFF0007823208000008.tif233163TIFF0007823208000009.tif83165

[0064] The following presents an alternative embodiment of the query parameters added to the subscription request message. In particular, new parameters PLMN ID, singleNssai (sNssai), dnn, and emergencyServices are added to sdmSubscription to indicate specific subscription information for UeContextInSmfData. This can be seen in the table below, which is a modified version of table 6.1.6.2.3-1 in section 6.1.6.2.3 "Definition of type SdmSubscription" in section 6.1.6.2.3 "Type: SdmSubscription" of 3GPP TS 29.503. The new IE in the table below is the ueContextInSmfDataSubscription entry.

[0065] [Table 7] TIFF0007823208000011.tif237160TIFF0007823208000012.tif78164

[0066] As shown by the example table below, a new subsection defining ueContextInSmfDataSubscription is needed, which may be found in section 6.1.6.2.x of 3GPP TS 29.503.

[0067] [Table 8]

[0068] The corresponding procedure flow for a subscription embodiment is shown in Figure 6. The NF service consumer (e.g., AMF, HSS) sends a subscription request to the UDM to subscribe to notifications of data changes in UeContextInSmfData. The request includes the callback URI, the URI of the monitored resource, and the new subscription configuration data (filter values).

[0069] 7 is a flowchart illustrating a method performed by an NFC according to various embodiments. The method may be performed by a network node in a communication network. The network node / NFC may be an AMF, HSS, or UDM node. The NFC / network node may perform the method in response to executing appropriately formulated computer-readable code. The computer-readable code may be embodied on or stored on a computer-readable medium, such as a memory chip, an optical disk, or other storage medium. The computer-readable medium may be part of a computer program product.

[0070] In step 701, the NFC sends a request (e.g., request 401) to the NFP. The request is for context information for a first wireless device (e.g., a first UE), and the request comprises one or more filter values ​​that identify a subset of the context information for the first wireless device needed by the NFC. The NFP may be an HSS or a UDM node.

[0071] The request may be a subscription request for context information for the first wireless device such that the NFP transmits the context information to the NFC when the context information changes. Alternatively, the request may be a search request for context information for the first wireless device such that the NFP transmits the context information to the NFC in response to a search request.

[0072] The context information to which the subscription request relates may be any of UEContextInSmfData, UEContextInAmfData, and UEContextInPgwData.

[0073] The subset of context information for the first wireless device required by the NF consumer may be related to a particular PDU session. For example, in some embodiments, one or more filter values ​​included in the request may indicate whether the NFC requires context information for an IMS PDU session or an emergency PDU session.

[0074] In some embodiments, the filter value included in the request may relate to any one or more of: a network slice to which the subset of context information pertains; an S-NSSAI to which the subset of context information pertains; an identifier of a data network to which the subset of context information pertains; a DNN identifier to which the subset of context information pertains; a list of data networks to which the subset of context information pertains; a list of DNNs to which the subset of context information pertains; a network identifier of a network serving the first wireless device; a PLMN identifier of a PLMN serving the first wireless device; and the presence or absence of emergency services information.

[0075] In some embodiments, the NFC receives wireless device context information from the NFP (e.g., as illustrated by signal 402 in FIG. 4). The received wireless device context information may comprise a subset of context information for the first wireless device according to one or more filter values.

[0076] 8 is a flowchart illustrating a method performed by an NFP according to various embodiments. The method may be performed by a network node in a communications network. The NFP / network node may be an HSS or a UDM node. The NFP / network node may perform the method in response to executing appropriately formulated computer-readable code. The computer-readable code may be embodied on or stored on a computer-readable medium, such as a memory chip, an optical disk, or other storage medium. The computer-readable medium may be part of a computer program product.

[0077] In step 801, the NFP receives a request (e.g., request 401) from the NFC. The request is for context information for a first wireless device (e.g., a first UE), and the request comprises one or more filter values ​​that identify a subset of the context information for the first wireless device that is needed by the NFC.

[0078] In step 803, wireless device context information is transmitted to the NFC (e.g., as indicated by signal 402 in FIG. 4). The wireless device context information comprises a subset of context information for the first wireless device selected according to one or more filter values. This wireless device context information may be context information stored by the NFP.

[0079] The context information to which the subscription request relates may be any one of UEContextInSmfData, UEContextInAmfData, and UEContextInPgwData.

[0080] The received request may be a subscription request for context information for the first wireless device, and the NFP may send the wireless device context information to the NFC when there is a change to the context information stored by the NFP for the first wireless device. Alternatively, the received request may be a search request for context information of the first wireless device, such that the NFP sends the wireless device context information to the NFC in response to receiving the search request.

[0081] The subset of context information for the first wireless device required by the NF consumer may be related to a particular PDU session. For example, in some embodiments, one or more filter values ​​included in the request may indicate whether the NFC requires context information for an IMS PDU session or an emergency PDU session.

[0082] In some embodiments, the filter value included in the request may relate to any one or more of: a network slice to which the subset of context information pertains; an S-NSSAI to which the subset of context information pertains; an identifier of a data network to which the subset of context information pertains; a DNN identifier to which the subset of context information pertains; a list of data networks to which the subset of context information pertains; a list of DNNs to which the subset of context information pertains; a network identifier of a network serving the first wireless device; a PLMN identifier of a PLMN serving the first wireless device; and the presence or absence of emergency services information.

[0083] FIG. 9 illustrates an example of a communication system 900 in which some embodiments may be implemented.

[0084] In this example, communications system 900 includes a telecommunications network 902 including an access network 904, such as a radio access network (RAN), and a core network 906 including one or more core network nodes 908. Access network 904 includes one or more access network nodes, such as access network nodes 910a and 910b (one or more of which may be generally referred to as access network nodes 910), or any other similar Third Generation Partnership Project (3GPP®) access node or non-3GPP® access point. Access network node 910 facilitates direct or indirect connectivity of user equipment (UE), such as connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912), to the core network 906 over one or more wireless connections. The access network nodes 910 include, for example, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)), O-RAN nodes, and components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0085] Unless otherwise specified, the term "network node" as used herein refers to both access network nodes 910 and core network nodes 908.

[0086] Exemplary wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Moreover, in various embodiments, communications system 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. Communications system 900 may include and / or interface with any type of communications, telecommunications, data, cellular, wireless networks, and / or other similar types of systems.

[0087] The wireless device / UE 912 communicates with the network node 910 and other communication devices. wireless Arranged, configured, and / or operable to communicate wireless The access network node 910 may be any of a wide variety of communication devices, including a UE 912, a UE 912a, a UE 912b, a UE 912c, a UE 912d, a UE 912e, a UE 912f ...

[0088] In the illustrated example, the core network 906 connects the access network node 910 to one or more hosts, such as host 916. The connections may be direct or indirect through one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 906 includes one or more core network nodes (e.g., core network node 908) structured with hardware and software components. The functions of these components include: wireless The components of the core network node 908 may be substantially similar to those described with respect to the device / UE, access network node, and / or host, and therefore those descriptions are generally applicable to the corresponding components of the core network node 908. Exemplary core network nodes include a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), ... Node B (MSC), a Mobile Node C (MSC), a Mobile Node D (MSC), a Mobile Node E (MSC), a Mobile Node F (MS Integration The device includes one or more functions of a Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0089] The host 916 may be owned or controlled by, and operated by or on behalf of, a non-operator service provider or provider of the access network 904 and / or telecommunications network 902. The host 916 may host a variety of applications to provide one or more services. Examples of such applications include live preparation and pre-recorded audio / video content, data collection services such as acquiring and compiling data about various ambient conditions sensed by multiple UEs, analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

[0090] Overall, the communication system 900 of FIG. wirelessIn that sense, a communication system may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G), a wireless local area network (WLAN) standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standard, such as LoRa and Sigfox.

[0091] In some examples, the telecommunications network 902 is a cellular network that implements functions standardized by 3GPP. Thus, the telecommunications network 902 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 902. For example, the telecommunications network 902 may provide Ultra-Reliable Low Latency Communications (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and massive machine type communications (mMTC) / massive IoT services to still further UEs.

[0092] In some examples, the UE 912 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 904. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may be configured and operate in any one or combination of Wi-Fi, NR (New Radio), and LTE, i.e., for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0093] 9, a hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UEs 912c and / or 912d) and an access network node (e.g., access network node 910b). In some examples, the hub 914 may include controllers, routers, content sources, and analytics. node, or any of the other communications devices described herein with respect to a UE. For example, the hub 914 may be a broadband router that enables access to the core network 906 for the UE. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 910, or may be accepted by executable code, scripts, processes, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for data for the UE and, in some embodiments, may perform analysis or other processing of that data. As another example, the hub 914 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker, or other media delivery device, the hub 914 may obtain media or data related to VR assets, video, audio, or other sensory information via a network node, in which case the hub 914 provides it to the UE either directly, after performing local processing, and / or adding additional local content. In yet another example, the hub 914 acts as a proxy server or orchestrator for the UEs, especially if one or more of the UEs are low energy IoT devices.

[0094] Hub 914 may have a constant / permanent or intermittent connection to network node 910b. Hub 914 may also enable different communication schemes and / or schedules between hub 914 and UEs (UEs 912c and / or 912d) and between hub 914 and core network 906. In other examples, hub 914 is connected to core network 906 and / or one or more UEs via a wired connection. Moreover, hub 914 may be configured to connect to an M2M service provider over access network 904 and / or to other UEs over a direct connection. In some scenarios, a UE may establish a wireless connection with network node 910b while still being connected via hub 914 via a wired or wireless connection. In some embodiments, hub 914 may be a dedicated hub, i.e., a hub whose primary function is to route communications between UEs and network node 910b. In other embodiments, hub 914 may be a non-dedicated hub, i.e., a device that is operable to route communications between UEs and network node 910b, but that is also operable as a communications origination and / or termination point for any data channel.

[0095] 10 illustrates a network node 1000 according to some embodiments. As used herein, a network node refers to a device that is capable of, and is configured, arranged, and / or operable to communicate, directly or indirectly, with UEs and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access network nodes such as access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)), O-RAN nodes and components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs). Other examples of network nodes include exemplary core network nodes such as a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Mobile Node B (MSB), a Mobile Node B (MME ... Integration The core network may include a core network node (e.g., core network node 908 in core network 906) such as a node including functionality including one or more of the following functions: a data management (UDM), a security edge protection proxy (SEPP), a network publishing function (NEF), and / or a user plane function (UPF).

[0096] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power levels), and thus may be referred to as femto, pico, micro, or macro base stations, depending on the amount of coverage provided. A base station may also be a relay node or a relay donor node that controls a relay. An access network node may include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna, such as an antenna-integrated radio. Some distributed radio base stations may also be referred to as nodes in a distributed antenna system (DAS).

[0097] Other examples of access network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordinating entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC) and / or a minimized drive test (MDT).

[0098] The network node 1000 includes a processing circuit 1002, a memory 1004, a communication interface 1006, and a power source 1008, and / or any other components, or any combination thereof. The network node 1000 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios in which the network node 1000 comprises multiple separate components (e.g., a BTS and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique pair of a Node B and an RNC may, in some examples, be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be redundant (e.g., separate memories 1004 for different RATs) and some components may be reused (e.g., the same antenna 1010 may be shared by different RATs). Also, the network node 1000 may include multiple sets of the various illustrated components for different wireless technologies integrated into the network node 1000, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID (Radio Frequency Identification), or Bluetooth wireless technologies, which may be integrated into the same or different chips or chipsets and other components within the network node 1000.

[0099] The processing circuitry 1002 may include one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or other suitable computing device, resources, or combination of hardware, software, and / or coded logic operable, alone or in conjunction with other network node 1000 components, such as memory 1004, to provide the functionality of the network node 1000. For example, the processing circuitry 1002 may be configured to cause the network node to perform the methods described above or defined in the implementations below.

[0100] In some embodiments, the processing circuitry 1002 comprises a system-on-chip (SOC). In some embodiments, for example, when the network node 1000 is an access network node, the processing circuitry 1002 includes one or more of a radio frequency (RF) transceiver circuitry 1012 and a baseband processing circuitry 1014. In some embodiments, the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on the same chip or chipset, board, or unit. In embodiments in which the network node 1000 is in the form of a core network node, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 are not present in the network node 1000.

[0101] Memory 1004 may include any type of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuit 1002. Memory 1004 may store any suitable instructions, data, or information, including applications, including one or more of computer programs, software, logic, rules, code, tables, and / or other instructions, that are executable by processing circuit 1002 and usable by network node 1000. Memory 1004 may store any computational results produced by processing circuit 1002 and / or communication It may be used to store any data received via interface 1006. In some embodiments, processing circuit 1002 and memory 1004 are integrated.

[0102] The communication interface 1006 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, core networks, and / or UEs. As shown, the communication interface 1006 includes a port / terminal 1016 for transmitting and receiving data to and from a network, for example, over a wired connection.

[0103] In embodiments where the network node 1000 is an access network node, the communication interface 1006 also includes radio front-end circuitry 1018 which is coupled to, or in some embodiments may be part of, the antenna 1010. In embodiments where the network node 1000 is a core network node, the core network node includes radio front-end circuitry 1018.1018 The radio front-end circuit 1018 may not include the antenna 1010. The radio front-end circuit 1018 includes a filter 1020 and an amplifier 1022. The radio front-end circuit 1018 may be connected to the antenna 1010 and the processing circuit 1002. The radio front-end circuit may be configured to condition signals communicated between the antenna 1010 and the processing circuit 1002. The radio front-end circuit 1018 may accept digital data to be sent to another network node or UE via a wireless connection. The radio front-end circuit 1018 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of a filter 1020 and / or an amplifier 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when data is received, the antenna 1010 collects the radio signal, which may then be converted to digital data by the radio front-end circuit 1018. The digital data may be passed to the processing circuit 1002. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0104] In an alternative embodiment, the access network node 1000 may not include a separate radio front-end circuit 1018; rather, the processing circuit 1002 may include the radio front-end circuitry and may be connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communications interface 1006. In yet another embodiment, the communications interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012 as part of a radio unit (not shown), and the communications interface 1006 communicates with baseband processing circuitry 1014 that is part of a digital unit (not shown).

[0105] Antenna 1010 may include one or more antennas or an antenna array configured to transmit and / or receive wireless signals. Antenna 1010 may be coupled to radio front-end circuitry 1018 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1010 is separate from network node 1000 and connectable to network node 1000 through an interface or port.

[0106] The antenna 1010, the communication interface 1006, and / or the processing circuit 1002 may be configured to perform any receiving operation and / or any obtaining operation described herein as being performed by a network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuit 1002 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0107] The power source 1008 provides power to the various components of the network node 1000 in a format appropriate for each component (e.g., at the voltage and current levels required for each component). The power source 1008 may include or be coupled to power management circuitry for providing power to the components of the network node 1000 to perform the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuitry of the power source 1008. As a further example, the power source 1008 may include a source of power in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery may provide backup power in case of failure of the external power source.

[0108] Embodiments of network node 1000 may include additional components other than those shown in Figure 10 to provide certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1000 may include user interface devices that allow information to be input into and output from network node 1000. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions on network node 1000.

[0109] FIG. 11 is a block diagram illustrating a virtualization environment 1100 in which functionality implemented according to some embodiments may be virtualized. In this context, virtualization means for creating a virtual version of an apparatus or device may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may apply to any device or component thereof described herein and refers to an implementation in which at least a portion of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented within one or more virtual environments 1100 hosted by one or more hardware nodes, such as hardware computing devices operating as one or more core network nodes. In some embodiments, the nodes may be virtualized in their entirety.

[0110] An application 1102 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in the virtualized environment 1100 to implement some of the features, functionality and / or benefits of some of the embodiments disclosed herein.

[0111] The hardware 1104 may include processing circuitry, memory for storing software and / or instructions executable by the processing circuitry, and / or hardware devices as described herein, such as network interfaces and input / output interfaces. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 1108a and 1108b (one or more of which may be collectively referred to as VMs 1108), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears to the virtual machines 1108 as networking hardware.

[0112] The VMs 1108 may include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by a corresponding virtualization layer 1106. Various embodiments of instances of virtual appliances 1102 may be implemented in one or more of the VMs 1108, and the implementation may be done in various ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to aggregate many network equipment types into industry-standard, high-capacity server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0113] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each VM 1108 and the portion of the hardware 1104 on which it runs, whether the hardware is dedicated to that VM and / or shared by that VM with other VMs, forms a separate virtual network element. Also in the context of NFV, a virtual network function is responsible for handling specific network functions running in one or more VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.

[0114] The hardware 1104 may be implemented in a standalone network node with generic or proprietary components. The hardware 1104 may implement some functions via virtualization. Alternatively, the hardware 1104 may be part of a larger hardware cluster (e.g., in a data center or CPE) where multiple hardware nodes cooperate and are managed via a management and orchestration 1110, which oversees, among other things, the lifecycle management of the application 1102. In some embodiments, the hardware 1104 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces or may be used in combination with virtual components, such as radio access nodes or base stations, to provide wireless capabilities to virtual nodes. In some embodiments, some signaling may be provided with the use of a control system 1112, which may alternatively be used for communication between the hardware nodes and the radio units.

[0115] While the computing devices (e.g., network nodes) described herein may include a combination of the illustrated hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that the computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information into other information, comparing the obtained or transformed information with information stored at the network node, and / or performing one or more operations based on the obtained or transformed information, and making a decision as a result of that processing. Moreover, while components are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the computing device may include multiple different physical components that make up the illustrated single component, and functionality may be partitioned among the separate components. For example, a communication interface may be configured to include any of the components described herein, and the functionality of those components may be partitioned between the processing circuitry and the communication interface. In other examples, the computationally less intensive functions of any of these components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0116] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit, such as in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit can be configured to perform the described functionality regardless of whether it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to just the processing circuit or other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks in general.

[0117] The foregoing merely illustrates the principles of the present disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in light of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that are not explicitly shown or described herein, but which embody the principles of the present disclosure and therefore may be within the scope of the present disclosure. As will be understood by those skilled in the art, the various exemplary embodiments can be used in conjunction with, and interchangeably with, one another.

[0118] <Appendix>

[0119] TIFF0007823208000014.tif150167TIFF0007823208000015.tif124165TIFF0007823208000016.tif53168

[0120] ***First Change**** 6.1.6.1 Overview This section specifies the application data model supported by the API.

[0121] Table 6.1.6.1-1 shows the data types defined in the Nudm_SDM service API.

[0122] [Table 9] TIFF0007823208000018.tif247159TIFF0007823208000019.tif76159

[0123] Editor's Note: Airborne UE subscription data for UUAA-SM procedure is added after the request from Stage 2 is cleared. Table 6.1.6.1-2 specifies the data types that the Nudm_SDM Service API reuses from other specifications, including a reference to each specification and, where appropriate, a brief description of how they are used within the Nudm_SDM Service API.

[0124] [Table 10] TIFF0007823208000021.tif245156TIFF0007823208000022.tif21163

[0125] ***Next Change**** 6.1.6.2.3 Type: SdmSubscription

[0126] [Table 11] TIFF0007823208000024.tif254155

[0127] ***Next Change**** 6.1.6.2.xx Type: UeContextInSmfDataSubFilter

[0128] [Table 12]

[0129] ***Next Change**** 6.1.8 Capability Negotiation The optional features in Table 6.1.8-1 are defined in the Nudm_SDM API. They are negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].

[0130] [Table 14] TIFF0007823208000027.tif155166

[0131] ***Next Change**** A.2 Nudm_SDM API ****************Text omitted for clarity**************** SdmSubscription: type: object required: - nfInstanceId - callbackReference - monitoredResourceUris properties: nfInstanceId: $ref: 'TS29571_CommonData.yaml# / components / schemas / NfInstanceId' implicitUnsubscribe: type: boolean expires: $ref: 'TS29571_CommonData.yaml# / components / schemas / DateTime' callbackReference: $ref: 'TS29571_CommonData.yaml# / components / schemas / Uri' amfServiceName: $ref: 'TS29510_Nnrf_NFManagement.yaml# / components / schemas / ServiceName' monitoredResourceUris: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / Uri' minItems: 1 singleNssai: $ref: 'TS29571_CommonData.yaml# / components / schemas / Snssai' dnn: $ref: 'TS29571_CommonData.yaml# / components / schemas / Dnn' subscriptionId: type: string plmnId: $ref: 'TS29571_CommonData.yaml# / components / schemas / PlmnId' immediateReport: type: boolean default: false report: $ref: '# / components / schemas / ImmediateReport' supportedFeatures: $ref: 'TS29571_CommonData.yaml# / components / schemas / SupportedFeatures' contextInfo: $ref: '# / components / schemas / ContextInfo' nfChangeFilter: type: boolean default: false ueConSmfDataSubFilter: $ref: '# / components / schemas / UeContextInSmfDataSubFilter' **************** Omitted for clarity **************** MbsSubscriptionData: description: Contains the 5MBS Subscription Data. type: object properties: mbsAllowed: type: boolean default: false mbsSessionIdList: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / MbsSessionId' minItems: 1 UeContextInSmfDataSubFilter: description: UE Context In Smf Data Subscription Filter. type: object properties: dnnList: type: array items: $ref: 'TS29571_CommonData.yaml# / components / schemas / Dnn' minItems: 1 emergencyInd: type: boolean default: false ****************Text omitted for clarity**************** ***END OF CHANGES****

Claims

1. A method performed by a first Network Function (NF), comprising: transmitting (701) a request (401) for context information in a third NF for a first wireless device to a second NF, the request (401) further including one or more filter values ​​identifying the requested context information, the context information relating to at least one particular protocol data unit (PDU) session; receiving wireless device context information (402) from the second NF, the received wireless device context information (402) comprising the context information for the first wireless device according to the one or more filter values; Including, the request (401) is a subscription request to receive notifications of changes to context information for the first wireless device, and when the context information changes, the second NF sends the context information to the first NF; or the request (401) is a search request for context information for the first wireless device, and the second NF sends context information to the first NF in response to the search request; The context information is UEContextInAmfData or UEContextInPgwData, The one or more filter values ​​indicate whether the first NF requires context information for an emergency PDU session.

2. 2. The method of claim 1, wherein the filter value is: A list of Single Network Slice Selection Assistance Information (S-NSSAI) to which the context information relates; a list of DNNs to which the context information relates; or Indication of the presence of emergency services information; Related to, methods.

3. 2. The method of claim 1, wherein the first NF is one of an Access and Mobility Management Function (AMF), a Home Subscriber Server (HSS), and a Unified Data Management (UDM) node; The method, wherein the second NF is one of a Home Subscriber Server (HSS) and a Unified Data Management (UDM) node.

4. A method performed by a second Network Function (NF), comprising: receiving (801) a request for context information for a first wireless device from a first NF, the request (401) further including one or more filter values ​​identifying the requested context information, the context information relating to at least one particular protocol data unit (PDU) session; transmitting (803) wireless device context information (402) to the first NF, the transmitted wireless device context information (402) including context information for the first wireless device according to the one or more filter values; Including, the received request (401) is a subscription request to receive notifications of changes to context information for the first wireless device, and the second NF sends the wireless device context information (402) to the first NF when there is a change to the context information stored by the second NF for the first wireless device; or the received request (401) is a search request for context information for the first wireless device, and the second NF, in response to receiving the search request, sends the wireless device context information (402) to the first NF; The context information is UEContextInAmfData or UEContextInPgwData, The one or more filter values ​​indicate whether the first NF requires context information for an emergency PDU session.

5. The method of claim 4, wherein the filter value is: A list of Single Network Slice Selection Assistance Information (S-NSSAI) to which the context information relates; a list of Data Network Names (DNNs) to which the context information relates; or Indication of the presence of emergency services information; Related to, methods.

6. The method of claim 4, wherein the first NF is one of an Access and Mobility Management Function (AMF), a Home Subscriber Server (HSS), and a Unified Data Management (UDM) node; The method, wherein the second NF is one of a Home Subscriber Server (HSS) and a Unified Data Management (UDM) node.

7. A first network function (NF) node including a processor and a memory, the memory including instructions executable by the processor, whereby the first NF: sending (701) to a second NF a request (401) for context information in a third NF for a first wireless device, the request (401) further including one or more filter values ​​identifying the requested context information, the context information relating to at least one particular protocol data unit (PDU) session; receiving, from the second NF, wireless device context information (402), the received wireless device context information (402) including the context information for the first wireless device according to the one or more filter values; It works like this, the request (401) is a subscription request to receive notifications of changes to context information for the first wireless device, and when the context information changes, the second NF sends the context information to the first NF; or the request (401) is a search request for context information for the first wireless device, and the second NF sends context information to the first NF in response to the search request; The context information is UEContextInAmfData or UEContextInPgwData, A first NF node, wherein the one or more filter values ​​indicate whether the first NF requires context information for an emergency PDU session.

8. A first NF node as described in claim 7, further operating as described in claim 2 or 3.

9. a second network function (NF) node including a processor and a memory, the memory including instructions executable by the processor, whereby the second NF: receiving (801) from a first NF a request (401) for context information for a first wireless device, the request further including one or more filter values ​​identifying the requested context information, the context information relating to at least one particular protocol data unit (PDU) session; transmitting (803) wireless device context information (402) to the first NF, the transmitted wireless device context information (402) including context information for the first wireless device according to the one or more filter values; It works like this, the received request (401) is a subscription request to receive notifications of changes to context information for the first wireless device, and the second NF sends the wireless device context information (402) to the first NF when there is a change to the context information stored by the second NF for the first wireless device; or the received request (401) is a search request for context information for the first wireless device, and the second NF, in response to receiving the search request, sends the wireless device context information (402) to the first NF; The context information is UEContextInAmfData or UEContextInPgwData, A second NF node, wherein the one or more filter values ​​indicate whether the first NF requires context information for an emergency PDU session.

10. A second NF node as described in claim 9, further operating as described in claim 5 or 6.

Images