Methods, apparatus and computer programs
By introducing a UDP proxy into the 5G system, the problem of intermediate networks being unable to read application data metadata caused by end-to-end encryption was solved, enabling effective application data management and quality of service processing, and improving data transmission efficiency and quality.
Patent Information
- Application Number
- CN202580029168.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-23
- Filing Date
- 2025-02-19
- Publication Date
- 2026-11-17
AI Technical Summary
In communication networks, especially in 5G systems, end-to-end encrypted application data transmission prevents intermediate network nodes from reading the metadata of the application data, resulting in an inability to effectively manage the transmission of application data. For example, it is impossible to provide quality of service processing based on PDU sets and the detection of data burst termination.
By introducing a UDP proxy between user equipment and application servers, application data is transmitted using an encrypted channel, and application metadata, including PDU set information and data burst end information, is provided at the intermediate proxy, so that the network can understand and manage application data.
It enables the network to effectively manage the transmission of application data under end-to-end encryption, provides quality of service processing based on PDU sets and detection of data burst termination, and improves the efficiency and quality of data transmission.
Smart Images

Figure CN123125845A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to methods, apparatuses, and computer programs, and specifically, but not exclusively, to methods, apparatuses, and computer programs relating to providing metadata for application data. Background Technology
[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides access to a data network. Mobile communication networks or wireless communication networks are examples of communication networks. Communication devices may be served by application servers.
[0003] This type of communication network operates according to standards provided by organizations such as the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of these standards are the so-called fourth-generation (4G) and fifth-generation (5G) standards provided by 3GPP. Summary of the Invention
[0004] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of embodiments of this disclosure, nor are they intended to be used to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure.
[0005] According to a first aspect, a method is provided, the method comprising: controlling an application to send application data to a user equipment via an encrypted channel; sending application metadata that can be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; generating a message including at least one of application metadata semantic information for reading the application metadata and application access rules; and sending the message to a core network entity.
[0006] Based on some examples, application metadata semantic information includes instructions on how an application controlled by a device can send application metadata to an intermediate agent.
[0007] According to some examples, application access rules include at least one of the following: application identifier, application addressing information, and proxy information used to reach the application.
[0008] According to some examples, application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide application metadata; and information indicating the type of transmission for the type of transport used for the application metadata.
[0009] According to some examples, information indicating at least one protocol that can be used to provide application metadata is associated with a context identifier.
[0010] According to some examples, information indicating the type of transport used indicates that the UDP proxy is being used as an intermediary proxy.
[0011] According to some examples, application data sent to a user device via an encrypted channel includes Extended Reality and Media Services (XRM) data, which includes one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with application metadata used for their delivery to the user device.
[0012] According to some examples, the intermediate proxy includes a UDP proxy, and application data is sent to the user device via the UDP proxy through an encrypted channel.
[0013] This method can be performed by a device.
[0014] The apparatus may include components for implementing the method.
[0015] The apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least one of the methods discussed in the first aspect.
[0016] This device can implement application functions and / or application servers.
[0017] According to a second aspect, a method is provided, the method comprising: receiving a message from a network entity, the message including at least one of application metadata semantic information for reading application metadata and application access rules, wherein application data and application metadata are transmitted together via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage application data transmitted via the encrypted channel; determining, based on operator policies, that the network entity is authorized to provide application metadata semantic information; generating a message including at least one of application metadata semantic information for reading application metadata and application access rules; and sending the message to a core network entity.
[0018] Based on some examples, core network entities include the Unified Data Repository (UDR).
[0019] According to some examples, the method includes: receiving a subscription request from a session management function (SMF) for application access rules and / or application metadata semantic information; and sending the application metadata semantic information to the SMF.
[0020] Based on some examples, application metadata semantic information includes instructions on how device-controlled applications can send application metadata to an intermediate agent.
[0021] According to some examples, application access rules include at least one of the following: application identifier, application addressing information, and proxy information used to reach the application.
[0022] According to some examples, application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide application metadata; and information indicating the type of transmission for the type of transport used for the application metadata.
[0023] According to some examples, information indicating at least one protocol that can be used to provide application metadata is associated with a context identifier.
[0024] Based on some examples, information indicating the type of transport used indicates that a UDP proxy is being used.
[0025] According to some examples, application data transmitted over encrypted channels includes Extended Reality and Media Services (XRM) data, which includes one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with application metadata for their delivery to the user device.
[0026] According to some examples, application data is sent via a UDP proxy through an encrypted channel.
[0027] This method can be performed by a device.
[0028] The apparatus may include components for implementing the method.
[0029] This device can enable network access functionality.
[0030] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least one of the methods discussed in the second aspect.
[0031] According to a third aspect, a method is provided, the method comprising: receiving a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein application data is transmitted together with application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage application data transmitted via the encrypted channel; generating a request for the application data transmitted via the encrypted channel by a User Datagram Protocol (UDP) agent, wherein the request is generated based on the application access rules and / or application metadata semantic information; and sending the request to a User Plane Function (UPF).
[0032] According to some examples, the method includes: receiving parameters for a UDP proxy from a UPF; sending an application access rule and parameters for a UDP proxy to a user equipment, wherein the user equipment is configured to connect to the UDP proxy to receive application data when a filtering condition in the application access rule is met.
[0033] According to some examples, core network entities include Network Open Function (NEF) or Policy Control Function (PCF).
[0034] Based on some examples, application metadata semantic information includes instructions on how an application controlled by a device can send application metadata to an intermediate agent.
[0035] According to some examples, application access rules include at least one of the following: application identifier, application addressing information, and proxy information used to reach the application.
[0036] According to some examples, application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide application metadata; and information indicating the type of transmission for the type of transport used for the application metadata.
[0037] According to some examples, information indicating at least one protocol that can be used to provide application metadata is associated with a context identifier.
[0038] Based on some examples, information indicating the type of transport used indicates that a UDP proxy is being used.
[0039] According to some examples, application data transmitted over encrypted channels includes Extended Reality and Media Services (XRM) data, which includes one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with application metadata for their delivery to the user device.
[0040] This method can be performed by a device.
[0041] The apparatus may include components for implementing the method.
[0042] This device can perform session management functions.
[0043] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least one of the methods discussed in relation to the third aspect.
[0044] According to the fourth aspect, a method is provided, the method comprising: receiving a message from a network entity, the message including at least one of application metadata semantic information for reading application metadata and application access rules, wherein application data is transmitted together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate proxy, wherein the application metadata can be used to manage application data transmitted via the encrypted channel; allocating resources for a User Datagram Protocol (UDP) proxy to be used as an intermediate proxy; and sending parameters for the UDP proxy to the network entity.
[0045] According to some examples, the method includes: using metadata semantic information to negotiate how application metadata will be received from the application server; sending application data to the user equipment, wherein the application metadata is used to map the application data to a specific Quality of Service (QoS) process in the network; and determining metadata to be sent to the access network along with the application data, wherein the application data is mapped to the QoS process by applying a specific QoS threshold level or selecting a specific QoS enforcement rule.
[0046] Based on some examples, network entities include SMFs.
[0047] Based on some examples, application metadata semantic information includes instructions on how an application controlled by a device can send application metadata to an intermediate agent.
[0048] According to some examples, application access rules include at least one of the following: application identifier, application addressing information, and proxy information used to reach the application.
[0049] According to some examples, application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide application metadata; and information indicating the type of transmission for the type of transport used for the application metadata.
[0050] According to some examples, information indicating at least one protocol that can be used to provide application metadata is associated with a context identifier.
[0051] Based on some examples, the type of transport used to transmit information indicating the type of data used for application metadata indicates that a UDP proxy is being used.
[0052] According to some examples, application data transmitted over encrypted channels includes Extended Reality and Media Services (XRM) data, which includes one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with application metadata for their delivery to the user device.
[0053] This method can be performed by a device.
[0054] The apparatus may include components for implementing the method.
[0055] This device can enable user-facing functionality.
[0056] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least one of the methods discussed in the fourth aspect.
[0057] According to the fifth aspect, a method is provided, the method comprising: receiving application access rules and information for UDP proxy from a core network entity; determining whether conditions in the application access rules are met; connecting to the UDP proxy when the conditions in the application access rules are met; and receiving application data using the UDP proxy.
[0058] According to some examples, application access rules and UDP information are received during the non-access stratum NAS protocol data unit (PDU) session establishment acceptance or in the NAS PDU session modification request.
[0059] Based on some examples, determining whether the conditions in the application access rule are met includes: determining whether the uplink data sent from the user equipment matches the description in the application access rule.
[0060] According to some examples, application access rules include at least one of the following: application identifier, application addressing information, and proxy information used to reach the application.
[0061] Based on some examples, application access rules indicate that a UDP proxy will be used.
[0062] According to some examples, application data includes extended reality and media service XRM data, which includes one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each media stream and each application data unit in the one or more real-time media streams is associated with application metadata for their delivery to the user device.
[0063] According to some examples, the method involves communicating with the application server via a UDP proxy.
[0064] This method can be performed by a device.
[0065] The apparatus may include components for implementing the method.
[0066] The device may include user equipment.
[0067] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least one of the methods discussed in the fifth aspect.
[0068] According to one aspect, a computer-readable medium is provided, the computer-readable medium including program instructions stored thereon for performing at least one of the methods described above.
[0069] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions stored thereon for performing at least one of the methods described above.
[0070] According to one aspect, a non-volatile tangible storage medium is provided, the non-volatile tangible storage medium including program instructions stored thereon for performing at least one of the methods described above.
[0071] Many different aspects have been described above. It should be understood that additional aspects can be provided through any combination of two or more of the aspects mentioned above.
[0072] Various other aspects are also described in the following detailed description and the appended claims.
[0073] Many different embodiments have been described above. It should be understood that other embodiments can be provided by combining any two or more of the embodiments described above. Attached Figure Description
[0074] Some exemplary embodiments will now be described with reference to the accompanying drawings, which are non-limiting and illustrative, in which:
[0075] Figure 1 A representation of a communication network including a fifth-generation communication network is shown;
[0076] Figure 2 An example network architecture is shown;
[0077] Figure 3A An example datagram payload is shown;
[0078] Figure 3B An example datagram payload is shown;
[0079] Figure 4 An example message stream is shown;
[0080] Figure 5 An example message stream is shown;
[0081] Figure 6 An example message stream is shown;
[0082] Figure 7 An example message stream is shown;
[0083] Figure 8 Example methods executed by application functions or application servers are shown;
[0084] Figure 9 An example method executed by the Network Open Function is shown;
[0085] Figure 10 An example method executed by the session management function is shown;
[0086] Figure 11 Example methods executed by user-face functions are shown;
[0087] Figure 12 An example method executed by a user device is shown;
[0088] Figure 13 The illustration shows a method for using some example embodiments. Figure 1 The representation of a communication system device;
[0089] Figure 14 A representation of an apparatus according to some example embodiments is shown; and
[0090] Figure 15 A schematic representation of a non-volatile storage medium is shown, which, when executed by a processor, causes the processor to perform one or more steps of the methods disclosed herein. Detailed Implementation
[0091] When application data is sent between application endpoints via an encrypted channel (e.g., an end-to-end (E2E) encrypted channel), the intermediate network cannot read the application data. However, the application endpoints can share metadata about the application data with the network, allowing the network to better manage the delivery of the application data (e.g., its application-specific Quality of Service processing).
[0092] An example of data that can be transmitted over encrypted channels is video services, which constitute a significant part of overall internet traffic. Video encoders generate a set of different types of frames (such as I-frames or P-frames) or slices, which are transmitted over the network using media transport protocols (e.g., Real-time Transport Protocol, RTP). For Extended Reality and Media Services (XRM), 3GPP Release 18 has specified a mechanism called Application-Aware QoS for handling video (or other similar) services. Typically, frames or slices are large, so they are segmented into many Internet Protocol (IP) packets and transmitted over the network; these IP packets are treated as PDUs (Protocol Data Units) in 5G systems. PDUs carrying the same frames or slices can be identified as a set of PDUs, rather than processing individual PDUs.
[0093] Using this approach, 5G systems (core network and especially access network) can provide service quality (QoS) processing based on PDU sets. This can be based on PDU set-specific QoS parameters (e.g., PDU set latency budget (PSDB), PDU set error rate (PSER), PDU set integrated processing indicator (PSIHI), which are provided to the access network (e.g., radio access network (RAN)) via the control plane upon request from application functions or application servers. Service processing can also be based on other PDU set information, such as PDU set importance or size, which is carried as metadata along with the PDU itself via the user plane. For downlink services, the User Plane Function (UPF) detects IP packet sets belonging to the PDU set and provides corresponding information to the 3GPP access network (e.g., RAN) via the 3GPP User Plane Protocol (GTP-U), which can then apply PDU set-based QoS accordingly.
[0094] PDU set detection using RTP is possible based on specific RTP headers used in the media stream between the AS (Application Server) and UE, which include information related to the PDU set. However, this is challenged when the media is transmitted via a transport protocol that encrypts all relevant header information. For example, with Fast UDP Internet Connection QUIC, where the QUIC payload is encrypted end-to-end, the UPF cannot detect or read the PDU set information.
[0095] When application endpoints use E2E encrypted channels over a network, it is advantageous (and in some use cases, necessary) to develop architectures, protocols, and mechanisms to allow, enable, or otherwise facilitate the system (e.g., a 5G system) to receive metadata (e.g., identification metadata) from the application to apply the PDU set concept within the system. An example provides a system (e.g., a system as part of a 5G system) that does not access end-to-end protected application data, and the metadata used for the application data remains protected between the application and the 5G system. Thus, application data can be protected between the UE and AF / AS via a UDP proxy in the UPF.
[0096] In addition to PDU-based QoS processing for services, similar issues apply to the detection of data burst termination (the last packet within a packet burst). The UPF should perform this detection in the downlink (DL) direction to provide the RAN with a data burst termination indicator. This detection also relies on reading information from packet headers such as RTP.
[0097] In the following explanation, various example embodiments are described with reference to a communication device (e.g., a UE) capable of communicating with a communication network. Before explaining in detail embodiments of the methods and apparatus of this disclosure, please refer to... Figure 1 A brief explanation of a communication network that includes the fifth-generation communication system (5GS), the radio access network, and its core network (5GC).
[0098] Figure 1 A schematic representation of a communication network is shown, comprising a cellular or mobile communication system (e.g., a 5G communication system (5GS)) and a data network. The 5GS may include a radio access network (such as a 5G radio access network (5G-RAN) or a next-generation radio access network (NG-RAN)) and a 5G core network (5GC). Application functions may be deployed in the 5GS as trusted application functions, or they may be deployed or hosted on one or more application servers in the data network. Such application functions are untrusted application functions. The 5GS connects the UE to the data network via the access network and the 5GC (e.g., the 5GC's UPF).
[0099] 5GC can include the following network functions: Network Slice Selection Function (NSSF); Network Open Function; Network Repository Function (NRF); Policy Control Function (PCF); UDM; Application Function (AF); Authentication Server Function (AUSF); AMF; Session Management Function (SMF); and User Plane Function (UPF). Figure 1 It also shows the various interfaces (N1, N2, etc.) that can be implemented between the various elements of the system.
[0100] Some examples described herein provide a method for AF or AS requests to instantiate a proxy in certain UPFs to serve a specific service. Other examples provide a method for configuring one or more UEs in a system to use a proxy when connecting to a specific service. Some examples provide a method for providing configuration information to associated UPF(s) and / or UE(s) in a system. Some examples provide information to the UEs indicating when to use a proxy and for which service the proxy should be used.
[0101] Some examples also provide a method for UPF and AF / AS to negotiate what metadata each side supports and how that metadata can be carried in the HTTP tunnel.
[0102] When media and related protocol header information that can be used for PDU set identification is end-to-end encrypted (e.g., information within the QUIC protocol payload), relay nodes on any path in the network cannot access the PDU set information. Taking a 5G network as an example, this means that the UPF cannot detect the PDU set information or the data burst end indication. Therefore, XRM applications will not receive optimized processing from the network because the network cannot apply PDU set-based QoS or data burst end-based UE power saving to media services.
[0103] XRM services may include one or more real-time media streams for video, audio, sensory, and / or tactile information, wherein each media stream comprises a series of application data units. Each media stream and each application data unit in the one or more real-time media streams is associated with application metadata for their delivery over the network (e.g., for delivery to a user device).
[0104] Application metadata is a general container that provides useful information about application data (e.g., UDP payload). This information is useful for UPF to detect UDP payloads and process them accordingly. Application metadata can be used to manage application data, for example, to detect application data and apply QoS thresholds to the detected application data.
[0105] In the XRM context, application metadata can contain PDU set information and data burst end information. Semantics and encoding are specified in 3GPP TS 26.522. In some examples, the total size of application metadata is 64 bits. However, application metadata can have any amount of data and encoding, and this can be determined by the implementer of the AS and / or UPF.
[0106] Application metadata semantic information specifies the header fields and encodings used by the AS to create application metadata. This information can be provided to the UPF by the AS / AF via in-band signaling or control plane methods. Application metadata semantic information may include instructions on how an application controlled by the AS / AF can send application metadata to an intermediate agent. Application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide application metadata; and information indicating the type of transport used for the application metadata. The information indicating at least one protocol that can be used to provide application metadata is associated with a context identifier. The information indicating the type of transport used for the application metadata may indicate that a UDP proxy is used.
[0107] Application metadata semantic identifiers are defined to provide an identifier for specific application metadata semantics. This identifier is provided along with the ContextId when the Context ID is registered with the AS. For example, an application metadata semantic identifier could resemble [3gpp-defined-ts26.522-v18]. In this case, when the AS sends application metadata, the PDU set information, data burst end information, and encoding specified in 3GPP TS 26.522 will be followed.
[0108] Application Access Rules (AARs) can be provided to the system (e.g., 5GS) to create User Datagram Protocol (UDP) proxies and for use by the UE via the UDP proxy. An AAR can be provided to one or more core network entities of the 5GS. The AAR can be provided by the Application Front-End (AF) or Application Support System (AS). An AAR can include at least one of the following: an application identifier; application addressing information; and proxy information for reaching the application. An example skeleton of an AAR might correspond to: • Application identifiers for UEs, for example, application identifier for OS X = xrm.app.example.com, application identifier for OS Y = xrm.Osy-app.example.com, [different application identifiers will be used if different UE OSes]; 5GX application identifier: xyz [if 5GC, for example for PCF, CHF, a different application identifier will be used than that of (multiple) UEs]; • Protocol: UDP • Transport descriptor: UDP proxy
[0109] According to some examples, when the SMF receives an AAR, the SMF requests the UPF (e.g., via the N4 interface) to configure a UDP proxy with the connect-UDP option (e.g., in a Packet Forwarding Control Protocol (PFCP) Session Modification Request message or a PFCP Session Establishment Request message). User data can then be sent using the UDP protocol with the UPF acting as a UDP proxy. The UPF can send the UDP proxy IP address and port number to the SMF that will be used for the application and PDU session. This can be done via the N4 in (multiple) PFCP Session Establishment / Modification Response messages. Based on this information, the SMF can provide the updated AAR to the UE via a NAS message. The updated AAR may have the following example skeleton: • Application identifier used for the UE, for example, application identifier xrm.app.example.com, application identifier • Protocol: UDP • Transport descriptor: UDP proxy • UDP proxy IP address and port number
[0110] AAR can be provided to the UE by the SMF, for example, in the NAS PDU session establishment accept message or in the NAS PDU session modification request message.
[0111] As described above, when application endpoints communicate over the network using an E2E encrypted channel such as QUIC, it is useful for the application to provide the UPF with PDU set, data burst end identification related metadata, or other metadata. In the case of XRM, the application metadata semantics can include PDU set information and data burst end, but can also include the type of PDU (to distinguish, for example, Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP), and NAT Session Traversal Utility (STUN) streams). PDU set detection using RTP is possible based on specific RTP headers used in the media stream between the AS (Application Server) and UE, which include PDU set related information. However, this presents challenges when the media is transmitted via a transport protocol that encrypts all relevant header information. For example, with QUIC, where the QUIC payload is end-to-end encrypted, the UPF cannot detect or read the PDU set information. Currently, the IETF is working to standardize two methods for real-time media on QUIC: Media on QUIC (MoQ) and RTP on QUIC, both of which will utilize special solutions to provide PDU set information to the UPF.
[0112] Some examples described herein allow, enable, or otherwise facilitate the instantiation of agents in certain UPFs to serve one or more services requested by their associated AFs, and configure (multiple) UEs to use the instantiated agents. This can be done as follows: • AF provides AAR (Application Access Rule) information to the 5G system (e.g., to one or more core network entities of the 5G system) via extending existing APIs or via new APIs, as described in the following alternative process. Alternatively, information indicating AAR information may be provided to the 5G system via another method. • Information indicating that an AAR (Aspect-Based Argument) is provided by the AF (Agency Advisory) or other means can be further provided to the SMF (Small and Medium-sized Enterprise). Based on the AAR information, the SMF can: - Request the UPF to instantiate (UDP) proxies for one or more requested services, begin proxying UE services to any application servers (AS) of these services, and report the addressing information of the (UDP) proxies back to the SMF; - AAR rules are provided to the UE via NAS, where the AAR rules are generated based on AAR information received from AF and (UDP) proxy addressing information provided by the managed (UDP) proxy UPF; - The AAR rules sent to the UE via NAS ensure that the UE will use the UDP proxy when it is relevant in the network, that is, only when the UDP proxy is used for services identified in the contact rules (and will not use the UDP proxy when it is not relevant, that is, when the UDP proxy is used for services not included in any rules).
[0113] Several examples describe proxy operations utilizing the HTTP connect method for negotiating what metadata each end (UPF / proxy at one end and AS at the other) supports and how that metadata is carried in the HTTP tunnel. The first example mechanism is based on an Application Programming Interface (API), where the AF provides "application metadata semantics," which can ultimately be used by the UPF to appropriately read metadata sent from the AS in-band to the proxy in the UPF. This information can be service-wide (applicable to all proxied UE connections to all ASs of the service) or limited to a specific UE's proxied connection to an AS. The second example mechanism may include in-band negotiation. The AS / AF can negotiate using HTTP headers, using a UPF application metadata semantic ID, which is used to in-band identify a specific semantic when multiple metadata semantics are available.
[0114] Figure 2An example method for providing a UDP proxy is shown. As discussed in RFC 9298, the UDP payload can be augmented with additional data. A zero (0) context ID value is reserved for the UDP payload. Non-zero context IDs can be dynamically generated and registered between peers. The context ID registration process can be performed using HTTP header fields or the Capsule protocol [RFC 9297]. This context ID can be used to extend CONNECT-UDP as defined in RFC 9298.
[0115] Leveraging the flexibility provided by RFC 9298, at point 201, UE 202 sends a request to UPF 204 (i.e., the UDP proxy) to initiate a tunnel using a “connect-udp” upgrade token, specifying the target AS 206 information in “target_host” and “target_port”. DNS resolution for the request sent at point 201 can be performed at point 203 to address AS 206 (e.g., if needed).
[0116] UPF 204 understands the request received at 201 for session establishment (e.g., XRM media session establishment) and sends an HTTP request with a "connect-udp" upgrade token to AS 206 at 205, where target_port is the expected port number (which defaults to 443). When AS receives a tunnel request from UPF with a "target_host" corresponding to localhost, AS understands that the request is intended to create a tunnel to reach the local application.
[0117] Figure 2 The diagram (at point 201) shows that UE 202 initiates an HTTP / 3 tunnel to AS 206 via UPF 204. UE 202 can act as an HTTP client. UPF 204 acts as a UDP proxy, and AS 206 acts as an HTTP server.
[0118] When UE 202 sends a CONNECT request to UPF 204 at 201, UPF 204 will therefore create another HTTP tunnel toward AS 206 to forward UE 202's UDP payload. UPF 204 selects a non-zero context ID for this tunnel toward AS 206 and registers it via an HTTP header field (or via the capsule protocol). This context ID can be selected dynamically.
[0119] UPF 204 uses an HTTP header (“Application Metadata”) to register the selected context ID. The HTTP header is a structured field of the Item [as discussed in RFC 8941]. The presence of the “Application-metadata” HTTP header in the request indicates UPF 204's support for application metadata. The HTTP header value will contain the selected context ID. If the selected context ID is 20, an example of an “Application-metadata” HTTP header could be as follows: Application-metadata: 20;
[0120] When receiving a connect request with an "Application-metadata" HTTP header from UPF 204, AS 206 understands that the request uses the proposed method, and in its response at 207, AS 206 replies using the context ID it selected for that communication. For example, it could respond with: Application-metadata: 20;
[0121] Upon receiving the response from AS 206, UPF 204 understands that the use of the proposed HTTP datagram payload with metadata in this context has been completed and agreed upon. From this point onward, AS 206 tunnels the UDP payload into the HTTP datagram to UPF 204. The response sent from AS 206 at 207 can be forwarded from UPF 204 to UE 202 at 209.
[0122] Application metadata can be included in the HTTP datagram and sent to UPF 204 at position 211. Figure 3A and Figure 3B Two options for including metadata in the HTTP datagram payload of a UDP proxy with metadata are shown.
[0123] exist Figure 3A In the first option shown, the UDP proxy HTTP datagram payload includes a context ID, metadata, and the UDP proxy payload. In this example, the content and length of the metadata can be known in advance between UPF 204 and AS 206.
[0124] exist Figure 3BIn the second option shown, the metadata length is provided as a separate structural element in the HTTP datagram, and the application-layer metadata is encoded in the tunneled UDP payload (e.g., at the beginning or end of the UDP payload). UPF 204 then reads the information from the tunneled UDP payload according to the specified length. This extension can be extended because the application-layer metadata length determines how much metadata is encoded.
[0125] return Figure 2 Regardless of the first option ( Figure 3A Is it used or the second option? Figure 3B At 211, metadata is sent from AS 206 to UPF 204 along with the UDP proxy HTTP datagram. At 213, the UDP proxy HTTP datagram payload is then sent from UPF 204 to UE 202 without metadata.
[0126] When multiple encoding formats or different versions of application metadata are defined, the HTTP header sent from the UPF to the AS can be used to indicate which application metadata encoding version and / or format was used in the data session. An example of such an HTTP header is: Application-metadata : context-id=42; encoding=Application LayerSemantic Identifier; r
[0127] Therefore, in-band signaling can be used to indicate which application metadata encoding version and / or format is used in the data session.
[0128] Another approach is to use a control plane method, where the AF informs the 5G system what types of application metadata are supported in user plane services (i.e., the HTTP datagram tunnel from AS to UPF), and this is executed by the AF via NEF. The name (similar to the 3gpp-defined-encoding-number interpreted in in-band signaling) can be shared from the AF. This information is ultimately delivered to the UPF. Therefore, the UPF can understand what types of application metadata are present in the HTTP datagram.
[0129] Figure 4 and Figure 5 A first example method for providing rules such as the AAR described above to SMF is shown. This first example method can also be used to synchronize user-plane entities to use UPF proxies. Figure 6 A second example method is shown for providing rules such as the AAR mentioned above to the PCF (the PCF can then then...) Figure 7(As shown, rules are provided to SMF). The second example method can also be used to synchronize user-plane entities to use UPF proxies.
[0130] Note that while the provision of application metadata semantics from AF to 5GS can be applied to any application-aware situation, the special case of XRM applications is considered below as an example, namely, XRM semantics or XRM metadata semantics (used interchangeably) and their provision are taken into account.
[0131] exist Figure 4 and Figure 5 In the first example method shown, XRM semantics, along with AAR, are independent of QoS information and are provided before the PDU session is established. A dedicated (QoS-agnostic) API is used by AF to provide AAR and XRM metadata semantics to 5GS.
[0132] exist Figure 6 In the second example method shown, XRM semantics, along with AAR and QoS information, are provided before the PDU session is established.
[0133] Then, Figure 7 The first and second example methods are shown to enter the PDU session establishment process and the modifications used to allow, enable, or otherwise facilitate the instantiation of a proxy in certain UPFs to serve one or more services requested by their associated AFs and to configure UE(s) to use the instantiated proxy.
[0134] Note that AS and UPF can transmit XRM semantics via an HTTP connection as described above.
[0135] exist Figure 4 and Figure 5 In the first example method shown, a dedicated (QoS-agnostic) API is used by AF to provide AAR and XDRM metadata semantics to 5GS.
[0136] At 417, AF 412 uses a service to send AAR and XRM metadata semantics to NEF 410. This service may include Create / Update / Delete request messages. This service may include the Nnef_AARManagement_Create / Update / Delete service. This information can then be updated to the SMF that has already subscribed to the AAR management service using the Nnef_AARManagement_Subscribe service operation (hereinafter referred to as...). Figure 5 discuss).
[0137] The AAR and XRM metadata semantics provided by AF 412 can correspond to: • Application identifiers used for OS X, such as xrm.app.example.com; application identifiers used for OS Y, such as xrm.OSY-app.example.com; • 5GX application identifier: xyz [If it is for 5GC, such as PCF, CHF, a different application identifier will be used than that of (multiple) UEs]; • Protocol: UDP; • Transport descriptor: UDP proxy.
[0138] At 417, AF 412 calls the Nnef_AARManagement_Create / Update / Delete service.
[0139] At 419, NEF 410 can check whether AF 412 is authorized to execute the request, and NEF 410 checks whether AF 412 is authorized to supply the AAR data based on operator policy. In addition to the information from AF 412, NEF 410 can also determine the affected Data Network Name (DNN) and multiple sets of Single Network Slice Selection Auxiliary Information (S-NSSAI).
[0140] At position 421, NEF 410 stores the information received at position 417 in UDR 408. This can be done by sending Nudr_DM_Create / Update / Delete(DNN+S-NSSAI, one or more AAR sets) to the UDR to store the corresponding information in the UDR.
[0141] At position 423, UDR 408 updates its data storage.
[0142] At position 425, UDR 408 sends a response to NEF 410 to acknowledge that the data has been stored. This can be sent as a Nudr_DM_Create / Update / Delete response message.
[0143] At position 427, NEF 410 sends a response to AF 412 to acknowledge that the data has been stored. This can be sent as an Nnef_AARManagement_Create / Update / Delete response message.
[0144] Figure 5 Example methods are shown for providing, modifying, or removing AARs and / or application metadata semantic information for reading application metadata to SMF 508. NEF 510 may correspond to NEF 410.
[0145] At position 529, the SMF 508 subscribes to the NEF 510 to receive AAR and / or XRM metadata semantic notifications. This can be done by sending an Nnef_AARManagement_Subscribe message with subscription filtering information corresponding to the set(s) of DNN+S-NSSAI supported by the SMF 508.
[0146] At 531, the process for semantic management of AAR and / or XRM metadata is triggered by AF (e.g., AF 412).
[0147] At point 533, for affected DNN+S-NSSAI that have already subscribed to this information, the NEF 510 sends AAR and / or XRM metadata semantic information. The NEF 510 can call Nnef_AAR_Management_Notify(AAR, Affected DNN+S-NSSAI) to the SMF 508 that has already subscribed to this information. The NEF 510 can decide to delay the distribution of AAR or XRM semantics to (multiple) SMF 508s for a period of time to optimize signaling load.
[0148] At 535, SMF 508 stores the received information for use in the affected PDU session.
[0149] A second example method for providing ARM semantics and / or AAR is in Figure 6 The example is shown below. In this example, XRM metadata semantics and / or AAR are provided along with QoS information before the PDU session is established.
[0150] The NEF API (e.g., Nnef_AF_Request_for_QoS as defined by 3GPP) for requesting QoS for UEs or UE groups not identified by their UE addresses can be used. Since a UE or UE group can be identified without an IP address, this means that the affected UE has not yet established a PDU session with the AF.
[0151] In this example, Nnef_AF_Request_for_QoS points to all UEs for a specific DNN / S-NSSAI combination. AAR and XRM metadata semantics are passed to the 5GC / UE via Nnef_AF_Request_for_QoS.
[0152] At position 637, PCF 614 subscribes to application data from UDR 608.
[0153] At 639, AF 612 sends a request to NEF 610 for reserving resources (e.g., in the Nnef_AF_Request_QoS_Create request message). This request may include at least one of the following: (multiple) flow descriptions or external application identifiers; QoS references or individual QoS parameters; alternative service requirements (as described in Clause 6.1.3.22 of TS 23.503); all UEs accessing DNN / S-NSSAI; XRM metadata semantics; and application access rules.
[0154] At position 641, NEF 610 authorizes the AF request using the new context.
[0155] At 643, NEF 610 stores the received information in UDR 608. NEF 610 uses the Nudr_DM service to store this information in UDR 608. This information is stored in UDR 608 as appropriately extended application data. If AF 612 requests notification of resource allocation status or other events, NEF 610 includes information for reporting the event (e.g., the requested information), including a notification target address pointing to NEF 610 or AF 612 and a notification-related ID containing the AF transaction internal ID.
[0156] At 645, UDR 608 uses the data received at 643 to notify the (multiple) PCFs 614 that have been subscribed.
[0157] At position 647, NEF 610 responds to AF 612.
[0158] At 639, (multiple) PCF 614 identifiers are active PDU sessions associated with data received from UDR 608.
[0159] Figure 7 The modified PDU session establishment process is shown. Once a PDU session is established, XRM metadata semantics and AAR are provided per PDU session.
[0160] At position 751, UE 702 requests to establish a PDU session.
[0161] At 753, the standard PDU session establishment procedure can be performed as described in 3GPP TS 23.502 4.3.2.2.
[0162] At 755, PCF 714 generates Policy and Charging Control (PCC) and sends it to SMF 708. (If the above is about...) Figure 4 and Figure 5If the first example method described is used, then the PCC rule does not need to include AAR and / or XRM semantics, because SMF708 already has this information based on its subscription to NEF. If the above regarding... Figure 6 If the second example method described (at 757) is used, then the PCC rule includes application access rules and / or XRM metadata semantics.
[0163] At 759, steps 8 and 9 of the PDU session establishment procedure described in Section 4.3.2.2 of TS 23.502 are performed.
[0164] 767 illustrates the establishment of the UDP proxy. At 761, based on the AAR from the PCC or locally available information, the SMF 708 uses UDP proxy control information to instruct the UPF 704 to activate the UDP proxy function for this PFCP session. The SMF 708 also sends XRM metadata semantics to the UPF in the PFCP session establishment request.
[0165] At 763, UPF 704 allocates resources for the UDP proxy, and at 765, the corresponding UDP proxy parameters (the parameters of the UDP proxy, i.e., the IP address and port number) are returned to SMF 708 in a response message (e.g., the PFCP session establishment response).
[0166] At 769 and 771, SMF 708 can send an AAR containing newly received UDP proxy server information from UPF 704 to UE 702, for example, in a NAS PDU session establishment acceptance or in a NAS PDU session modification request.
[0167] At 773, when the filtering conditions received in the AAR match, UE 702 initiates a UDP connection to the UDP proxy in UPF 704 based on the application access rules received from SMF 708. At 775, the connection terminates at the established UDP proxy. At 777, UPF 704 initiates a UDP connection to AS 706. The UE is now able to use UDP proxy technology to send uplink data to the UDP proxy in UPF 704. At 777, the UDP proxy in the UPF sends UL user plane data to AS 706 (e.g., which may include a media server).
[0168] At 779, AS 706 sends downlink data (e.g., application data) to the UDP proxy in UPF 704. AS 706 sends the PDU along with XRM metadata (e.g., in an HTTP datagram). Downlink data can be transmitted over an encrypted channel. Downlink data can be transmitted to the user equipment via the UDP proxy in UPF 704 over an encrypted channel.
[0169] At 781, UPF 704 receives the UDP proxy payload and the XRM metadata container. The UDP proxy in UPF 704 is able to understand application metadata by using AAR and application metadata semantic information. Then, before forwarding the UDP proxy payload to UE 702 via access network 718 (e.g., 5G AN / RAN at 785 utilizing PDU set information to provide appropriate QoS to PDUs), UPF 704 extracts the PDU set information from the XRM metadata container encapsulated in the HTTP datagram according to the supplied XRM metadata semantics, and generates a GTP-U header based on the received PDU set information.
[0170] Figure 8 An example method flow is shown. This method can be executed by an AF such as AF 412 or AF 612, or by an AS such as AS 706 or AS 206.
[0171] At 800, the method includes controlling the application to send application data to the user equipment via an encrypted channel.
[0172] At 802, the method includes sending application metadata that can be understood by an intermediate agent, wherein the application metadata can be used to manage application data sent through an encrypted channel.
[0173] At 804, the method includes generating a message that includes at least one of application metadata semantic information for reading application metadata and application access rules.
[0174] At point 806, the method includes sending the message to the core network entity.
[0175] Figure 9 An example method flow is shown. For example, this method can be executed by a NEF such as NEF 410, 510, or 610.
[0176] At 900, the method includes receiving a message from a network entity, the message including at least one of application metadata semantic information for reading application metadata and application access rules, wherein application data is sent together with application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage application data sent via the encrypted channel.
[0177] At 902, the method includes determining, based on operator policies, that network entities are authorized to provide application metadata semantic information.
[0178] At 904, the method includes generating a message that includes at least one of application metadata semantic information for reading application metadata and application access rules.
[0179] At position 906, the method includes sending the message to the core network entity.
[0180] Figure 10 An example method flow is shown. For example, this method can be executed by an SMF such as an SMF 508 or an SMF 708.
[0181] At 1000, the method includes receiving a message from a network entity, the message including at least one of application metadata semantic information for reading application metadata and application access rules, wherein application data is sent together with application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage application data sent via the encrypted channel.
[0182] At 1000, the method includes generating a request for application data that a User Datagram Protocol (UDP) proxy is used to send over an encrypted channel, wherein the request is generated based on application access rules and / or application metadata semantic information.
[0183] At 1000, the method includes sending the request to the User Face Function (UPF).
[0184] Figure 11 An example method flow is shown. For example, this method can be executed by a UPF such as UPF 204 or 704.
[0185] At 1100, the method includes receiving a message from a network entity, the message including at least one of application metadata semantic information for reading application metadata and application access rules, wherein application data is sent together with application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage application data sent via the encrypted channel.
[0186] At 1100, the method includes allocating resources for a User Datagram Protocol (UDP) proxy that will be used as an intermediary proxy.
[0187] At 1100, the method includes sending parameters for UDP proxy to the network entity.
[0188] Figure 12 An example method flow is shown. For example, this method can be executed by a UE such as UE 202 or 702.
[0189] At 1200, the method includes receiving application access rules and information for UDP proxy from the core network entity.
[0190] At 1202, the method includes determining whether the conditions in the application access rule are met.
[0191] At 1204, the method includes connecting to the UDP proxy when the conditions in the application access rules are met.
[0192] At 1206, the method includes receiving application data using a UDP proxy.
[0193] Figure 13 The illustration shows the implementation or includes at least Figure 1 The illustrated example is a session management device 1300 for the core network of a communication network. Device 1300 may include at least one random access memory (RAM) 1311a, at least one read-only memory (ROM) 1311b, at least one processor 1312, 1313, and a network interface 1314. At least one processor 1312, 1313 may be coupled to RAM 1311a and ROM 1311b. At least one processor 1312, 1313 may be configured to execute appropriate software code 1315 of the network entity described herein. Execution of the software code 1315 of the network entity described herein (or execution of the instructions of the software code 1315) may, for example, cause the device to perform… Figures 8 to 12 The method shown is illustrated. Software code 1315 can be stored in ROM 1311b. Device 1300 can be interconnected with another device 1300 for controlling other network functions of the 5GC. In some embodiments, one or more network functions of the 5GC are deployed or hosted on device 1300. In alternative embodiments, the device may include software code for additional network functions of the core network of a communication network. Device 1300 may include computing devices (e.g., servers), computing systems such as distributed computing systems, or virtual machines provided by cloud computing systems. In some examples, device 1300 may include a cloud computing system (e.g., a cloud core network) that includes session management functions and Figure 1 Other network functions of the core network shown.
[0194] Figure 14 The illustration shows an example of a communication device 1400, such as... Figure 1The terminal illustrated. Communication device 1400 can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples of communication device 1400 include user equipment, mobile station (MS) or mobile device (such as a mobile phone or so-called "smartphone"), computer equipped with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or tablet device equipped with wireless communication capabilities, machine-type communication (MTC) device, Internet of Things (IoT) type communication device, or any combination of these devices or similar devices. Communication device 1400 may include a transceiver for transmitting and / or receiving, for example, wireless signals carrying communication (e.g., radio signals). Communication can be one or more of voice, email, text messages, multimedia data, machine data, etc.
[0195] Communication equipment 1400 can receive wireless signals (e.g., radio signals) via air or radio interface 1407 through suitable means for receiving, and can transmit wireless signals via suitable means for transmitting radio signals. Figure 14 In the diagram, the transceiver is schematically represented by block 1406. Transceiver 1406 may include, for example, a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the mobile device and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna.
[0196] The communication device 1400 may include at least one processor 1301, at least one ROM 1402a, at least one RAM 1402b, and other possible components 1403 for performing tasks configured to be performed with software and hardware assistance, including controlling access to a radio access network (e.g., Figure 1 The device accesses and communicates with 5G-RAN (or NG-RAN) and other communication devices as illustrated. At least one processor 1401 is coupled to RAM 1402b and ROM 1402a. At least one processor 1401 can be configured to execute appropriate software code 1408 (e.g., at least one processor can execute instructions of software code 1408). Execution of software code 1408 can, for example, allow the communication device to perform one or more operations, including those described herein. Software code 1408 can be stored in ROM 1402a.
[0197] The processor, ROM and RAM, transceiver, and other circuitry (e.g., modem) of the communication device can be provided on a circuit board, in a chipset, or in a system-on-a-chip. The circuit board, chipset, or system-on-a-chip is indicated by reference numeral 1404. The communication device 1400 may optionally have a user interface, such as a keypad 1405, a touch-sensitive screen or touchpad, or a combination thereof. Optionally, depending on the type of communication device, one or more of a display, speaker, and microphone may be provided.
[0198] Figure 15 A schematic representation of non-volatile storage media 1500a (e.g., a computer disk (CD) or digital universal disk (DVD)) and 1500b (e.g., a universal serial bus (USB) memory stick) is shown, which stores instructions and / or parameters 1502 that, when executed by a processor, allow the processor to perform one or more steps of any method flow described herein.
[0199] It should be understood that the above references to various network functions (e.g., AMF, AF, PCF, etc.) may include means for performing at least some of the functions associated with these network functions. Furthermore, means including a network function may include a virtual network function instance of that network function.
[0200] It should be understood that the device may include or be coupled to other units or modules, such as radio sections or radio heads used for transmission and / or reception or in transmission and / or reception. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.
[0201] Note that while some embodiments have been described with respect to 5G networks, similar principles can be applied to other networks and communication systems. Therefore, although some embodiments have been described above by way of example with reference to certain example architectures, technologies, and standards for wireless networks, these embodiments can be applied to any other suitable form of communication system other than those illustrated and described herein.
[0202] This document also notes that while various exemplary embodiments have been described above, several variations and modifications may be made to the various exemplary embodiments without departing from the scope of this disclosure.
[0203] As used herein, “at least one of the following: ”, “at least one of ”, and similar wording, wherein the list of two or more elements is connected by “and” or “or”, means at least one of these elements, or at least any two or more of these elements, or at least all of these elements.
[0204] In general, various embodiments can be implemented in hardware or dedicated circuit systems, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. Although various aspects of this disclosure may be illustrated and described as block diagrams, flowcharts, or represented using some other illustration, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein are non-limiting examples that can be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0205] As used herein, the term "circuit system" may refer to one or more, or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any portion of a hardware processor (including a digital signal processor), software, and a memory (including a plurality of other processors), which work together to enable a device (such as a mobile phone or a server) to perform various functions; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when software is not required to operate.
[0206] This definition of a circuit system applies to all uses of the term "component" herein, including its use in any claim. As another example, as used herein, the term "circuit system" also covers only hardware circuitry or a processor (or processors), or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. For example, if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0207] Embodiments of this disclosure can be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) can be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components that are configured to implement the embodiments when the program is run. The one or more computer-executable components may be at least one piece of software code or a portion thereof.
[0208] Furthermore, it should be noted in this regard that any block in the logic flow shown in the accompanying drawings may represent a program step, or an interconnected logic circuit, block and function, or a combination of a program step and a logic circuit, block and function. Software may be stored on physical media such as memory blocks implemented within memory chips or processors, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, CDs, etc. The physical medium is a non-transitory medium.
[0209] As used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).
[0210] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, gate-level circuits, and processors based on multi-core processor architectures.
[0211] The various example embodiments of this disclosure can be practiced in a variety of components, such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready to be etched and formed on a semiconductor substrate.
[0212] The scope of protection sought with respect to the various exemplary embodiments of this disclosure is set forth in the independent claims. Exemplary embodiments and features (if any) described in this disclosure that do not fall within the scope of the independent claims should be interpreted as examples useful for understanding the various exemplary embodiments of this disclosure.
[0213] The foregoing description provides a complete and informative description of various exemplary embodiments of the present disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the art when the foregoing description is read in conjunction with the accompanying drawings and claims. Nevertheless, all such and similar modifications to the teachings will still fall within the various exemplary embodiments of the present disclosure set forth in the claims. As a non-limiting and illustrative example, further exemplary embodiments exist that include combinations of one or more exemplary embodiments with any of the other exemplary embodiments discussed above.
Claims
1. An apparatus comprising: Components used to control applications to send application data to user equipment through encrypted channels; A component for sending application metadata that can be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent through the encrypted channel; The component for generating a message, the message including at least one of application metadata semantic information for reading the application metadata and application access rules; A component used to send the message to core network entities.
2. The apparatus of claim 1, wherein the application metadata semantic information includes instructions on how an application controlled by the apparatus can send application metadata to the intermediate agent.
3. The apparatus according to claim 1 or claim 2, wherein the application access rule includes at least one of the following: application identifier, application addressing information, and proxy information for reaching the application.
4. The apparatus according to any of the preceding claims, wherein the application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide the application metadata; and information indicating the type of transmission used for the application metadata.
5. The apparatus of claim 4, wherein the information indicating at least one protocol that can be used to provide the application metadata is associated with a context identifier.
6. The apparatus according to claim 4 or claim 5, wherein: The information indicating the type of transmission used indicates that a UDP proxy is used as the intermediate proxy.
7. The apparatus according to any of the preceding claims, wherein the application data transmitted to the user device via the encrypted channel includes Extended Reality and Media Services (XRM) data, the XRM data including one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with the application metadata for their transmission to the user device.
8. The apparatus according to any of the preceding claims, wherein the intermediate proxy includes a UDP proxy, and the application data is transmitted to the user equipment via the UDP proxy and through the encrypted channel.
9. A method comprising: The control application sends application data to the user equipment through an encrypted channel; Send application metadata that can be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent through the encrypted channel; Generate a message, the message including at least one of application metadata semantic information for reading the application metadata and application access rules; Send the message to the core network entity.
10. A computer program comprising instructions that, when executed by at least one processor of a device, cause the device to perform: The control application sends application data to the user equipment through an encrypted channel; Send application metadata that can be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent through the encrypted channel; Generate a message, the message including at least one of application metadata semantic information for reading the application metadata and application access rules; Send the message to the core network entity.
11. An apparatus comprising: A component for receiving messages from network entities, the messages including at least one of application metadata semantic information and application access rules for reading application metadata, wherein application data is sent together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel. Components used to determine, based on operator policies, whether the network entity is authorized to provide the application metadata semantic information; A component for generating a message, the message including at least one of the application metadata semantic information for reading the application metadata and the application access rules; A component used to send the message to core network entities.
12. The apparatus of claim 11, wherein the core network entity includes a unified data repository (UDR).
13. The apparatus according to claim 11 or claim 12, comprising: A component for receiving subscription requests from the Session Management Function (SMF) for the application access rules and / or application metadata semantic information; A component used to send the application metadata semantic information to the SMF.
14. The apparatus according to any one of claims 11 to 13, wherein the application metadata semantic information includes instructions on how an application controlled by the apparatus can send application metadata to the intermediate agent.
15. The apparatus according to any one of claims 11 to 14, wherein the application access rule includes at least one of the following: an application identifier, application addressing information, and proxy information for reaching the application.
16. The apparatus according to any one of claims 11 to 15, wherein the application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide the application metadata; and information indicating the type of transmission used for the application metadata.
17. The apparatus of claim 16, wherein the information indicating at least one protocol that can be used to provide the application metadata is associated with a context identifier.
18. The apparatus according to claim 16 or claim 17, wherein: The information indicating the type of transmission used indicates that a UDP proxy is being used.
19. The apparatus of any one of claims 16 to 18, wherein the application data transmitted via the encrypted channel includes Extended Reality and Media Services (XRM) data, the XRM data including one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with the application metadata for their transmission to a user device.
20. The apparatus according to any one of claims 16 to 19, wherein the application data is transmitted via a UDP proxy through the encrypted channel.
21. A method comprising: Receive a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein application data is sent together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; Based on the operator's policy, it is determined that the network entity is authorized to provide the application metadata semantic information; Generate a message, the message including at least one of the application metadata semantic information and application access rules used to read the application metadata; Send the message to the core network entity.
22. A computer program comprising instructions that, when executed by at least one processor of a device, cause the device to perform: Receive a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein application data is sent together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; Based on the operator's policy, it is determined that the network entity is authorized to provide the application metadata semantic information; Generate a message, the message including at least one of the application metadata semantic information for reading the application metadata and the application access rule; Send the message to the core network entity.
23. An apparatus comprising: A component for receiving messages from network entities, the messages including at least one of application metadata semantic information and application access rules for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel. The component for generating a request, which is application data sent via the encrypted channel by the User Datagram Protocol (UDP) proxy, wherein the request is generated based on the application access rules and / or the application metadata semantic information; A component used to send the request to the User Plane Function (UPF).
24. The apparatus of claim 23, wherein the apparatus comprises: A component for receiving parameters for the UDP proxy from the UPF; A component for sending the application access rules and the parameters for the UDP proxy to a user equipment, wherein the user equipment is configured to connect to the UDP proxy to receive the application data when the filtering conditions in the application access rules are met.
25. The apparatus of claim 23 or claim 24, wherein the core network entity includes a Network Open Function (NEF) or a Policy Control Function (PCF).
26. The apparatus according to any one of claims 23 to 25, wherein the application metadata semantic information includes instructions on how an application controlled by the apparatus can send application metadata to the intermediate agent.
27. The apparatus according to any one of claims 23 to 26, wherein the application access rule includes at least one of the following: an application identifier, application addressing information, and proxy information for reaching the application.
28. The apparatus of any one of claims 23 to 27, wherein the application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide the application metadata; and information indicating the type of transmission used for the application metadata.
29. The apparatus of claim 28, wherein the information indicating at least one protocol that can be used to provide the application metadata is associated with a context identifier.
30. The apparatus according to claim 28 or claim 29, wherein: The information indicating the type of transmission used indicates that a UDP proxy is being used.
31. The apparatus of any one of claims 24 to 30, wherein the application data transmitted via the encrypted channel includes Extended Reality and Media Services (XRM) data, the XRM data including one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with the application metadata for their transmission to a user device.
32. A method comprising: Receive a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel, such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; A request is generated, which is application data that is sent through the encrypted channel by a User Datagram Protocol (UDP) proxy, wherein the request is generated based on the application access rules and / or the application metadata semantic information; Send the request to the User Face Function (UPF).
33. A computer program comprising instructions that, when executed by at least one processor of a device, cause the device to perform: Receive a message from a network entity, the message including at least one of application access rules and application metadata semantic information for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel, such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; A request is generated, wherein the request is used by the User Datagram Protocol (UDP) proxy to send the application data through the encrypted channel, and wherein the request is generated based on the application access rules and / or the application metadata semantic information; Send the request to the User Face Function (UPF).
34. An apparatus comprising: A component for receiving messages from network entities, the messages including at least one of application metadata semantic information and application access rules for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel. Components for allocating resources for a User Datagram Protocol (UDP) proxy that will be used as the intermediate proxy; A component used to send parameters for the UDP proxy to the network entity.
35. The apparatus of claim 34, wherein the apparatus comprises: A component used to negotiate how the application metadata will be received from the application server using the metadata semantic information; Components for sending the application data to a user equipment, wherein the application metadata is used to map the application data to a specific Quality of Service (QoS) process in the network, and determining metadata to be sent to the access network along with the application data, wherein the application data is mapped to the QoS process by applying a specific QoS threshold level or selecting a specific QoS enforcement rule.
36. The apparatus of claim 34 or 35, wherein the network entity comprises an SMF.
37. The apparatus according to any one of claims 34 to 36, wherein the application metadata semantic information includes instructions on how an application controlled by the apparatus can send application metadata to the intermediate agent.
38. The apparatus according to any one of claims 34 to 37, wherein the application access rule includes at least one of the following: an application identifier, application addressing information, and proxy information for reaching the application.
39. The apparatus according to any one of claims 34 to 38, wherein the application metadata semantic information includes at least one of the following: an application identifier; information indicating at least one protocol that can be used to provide the application metadata; and information indicating the type of transmission used for the application metadata.
40. The apparatus of claim 39, wherein the information indicating at least one protocol that can be used to provide the application metadata is associated with a context identifier.
41. The apparatus according to claim 39 or claim 40, wherein: The information indicating the type of transmission used indicates that a UDP proxy is being used.
42. The apparatus of any one of claims 37 to 41, wherein the application data transmitted via the encrypted channel includes Extended Reality and Media Services (XRM) data, the XRM data including one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with the application metadata for their transmission to a user device.
43. A method comprising: Receive a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel, such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; Allocate resources for the User Datagram Protocol (UDP) proxy that will be used as the intermediate proxy; Send parameters for the UDP proxy to the network entity.
44. A computer program comprising instructions that, when executed by at least one processor of a device, cause the device to perform: Receive a message from a network entity, the message including at least one of application metadata semantic information and application access rules for reading application metadata, wherein the application data is sent together with the application metadata via an encrypted channel, such that the application metadata can only be understood by an intermediate agent, wherein the application metadata can be used to manage the application data sent via the encrypted channel; Allocate resources for the User Datagram Protocol (UDP) proxy that will be used as the intermediate proxy; Send parameters for the UDP proxy to the network entity.
45. A user equipment, comprising: Components used to receive application access rules and information for UDP proxying from core network entities; A component used to determine whether the conditions in the application access rules are met; A component for connecting to the UDP proxy when the conditions in the application access rules are met; Components used to receive application data using the UDP proxy.
46. The user equipment of claim 45, wherein the application access rules and UDP information are received during the non-access stratum NAS protocol data unit (PDU) session establishment acceptance or during the NAS PDU session modification request.
47. The user equipment according to claim 45 or claim 46, wherein determining whether the condition in the application access rule is satisfied includes: Determine whether the uplink data to be sent from the user equipment matches the description in the application access rule.
48. The user equipment according to any one of claims 45 to 47, wherein the application access rule includes at least one of the following: application identifier, application addressing information, and proxy information for reaching the application.
49. The user equipment according to claim 48, wherein: The application access rule indicates that the UDP proxy will be used.
50. The user equipment according to any one of claims 45 to 49, wherein the application data includes extended reality and media service XRM data, the XRM data including one or more real-time media streams for video, audio, sensory and / or haptic information, wherein the media streams include a series of application data units, and each of the one or more real-time media streams and each application data unit is associated with application metadata for their transmission to the user equipment.
51. The user equipment according to claim 49, comprising: Components used for communicating with the application server via the UDP proxy.
52. A method comprising: Receive application access rules and information for UDP proxy from the core network entity; Determine whether the conditions in the application access rules are met; When the conditions in the application access rules are met, connect to the UDP proxy; Use the UDP proxy to receive application data.
53. A computer program comprising instructions that, when executed by at least one processor of a device, cause the device to perform: Receive application access rules and information for UDP proxy from the core network entity; Determine whether the conditions in the application access rules are met; When the conditions in the application access rules are met, connect to the UDP proxy; Use the UDP proxy to receive application data.
