Methods, communications devices, and core network entities

Abstract

A request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server is received and used to determine a User Plane Function (UPF) to serve as a MoQ relay f

Description

BACKGROUND Field of Disclosure The present disclosure relates to communications devices and core network entities of wireless communications networks and methods of operating such communications devices and core network entities. Description of Related Art The “background” description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description which may not otherwise qualify as prior art at the time of filing, are neither expressly or impliedly admitted as prior art against the present invention. Previous generation mobile telecommunication systems, such as those based on the 3GPP defined UMTS and Long Term Evolution (LTE) architecture, are able to support a wider range of services than simple voice and messaging services offered by previous generations of mobile telecommunication systems. For example, with the improved radio interface and enhanced data rates provided by LTE systems, a user is able to enjoy high data rate applications such as mobile video streaming and mobile video conferencing that would previously only have been available via a fixed line data connection. The demand to deploy such networks is therefore strong and the coverage area of these networks, i.e. geographic locations where access to the networks is possible, is expected to continue to increase rapidly. Current and future wireless communications networks are expected to routinely and efficiently support communications with an ever-increasing range of devices associated with a wider range of data traffic profiles and types than existing systems are optimised to support. For example, it is expected future wireless communications networks will be expected to efficiently support communications with devices including reduced complexity devices, machine type communication (MTC) devices, high resolution video displays, virtual reality headsets, extended Reality (XR) and so on. Some of these different types of devices may be deployed in very large numbers, for example low complexity devices for supporting the “The Internet of Things”, and may typically be associated with the transmissions of relatively small amounts of data with relatively high latency tolerance. Other types of device, for example supporting high-definition video streaming, may be associated with transmissions of relatively large amounts of data with relatively low latency tolerance. Other types of device, for example used for autonomous vehicle communications and for other critical applications, may be characterised by data that should be transmitted through the network with low latency and high reliability. A single device type might also be associated with different traffic profiles / characteristics depending on the application(s) it is running. For example, different consideration may apply for efficiently supporting data exchange with a smartphone when it is running a video streaming application (high downlink data) as compared to when it is running an Internet browsing application (sporadic uplink and downlink data) or being used for voice communications by an emergency responder in an emergency scenario (data subject to stringent reliability and latency requirements). In view of this there is expected to be a desire for current wireless communications networks, for example those which may be referred to as 5G or new radio (NR) systems / new radio access technology (RAT) systems, or indeed future 6G wireless communications, as well as future iterations / releases of existing systems, to efficiently support connectivity for a wide range of devices associated with different applications and different characteristic data traffic profiles and requirements. One example of a new service is referred to as Ultra Reliable Low Latency Communications (URLLC) services which, as its name suggests, requires that a data unit or packet be communicated with a high reliability and with a low communications delay. Another example of a new service is extended Reality (XR), which may be provided by various user equipment such as wearable devices. XR combines real-world and virtual environments, incorporating aspects such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), and thus requires high quality and minimised interaction delay. Services such as URLLC and XR therefore represent a challenging example for both LTE type communications systems and 5G / NR communications systems, as well as future generation communications systems. 5G NR has continuously evolved and the current work plan includes 5G-NR-advanced in which some further enhancements are expected, especially to support new use-cases / scenarios with higher requirements. The desire to support these new use-cases and scenarios gives rise to new challenges for efficiently handling communications in wireless communications systems that need to be addressed. SUMMARY OF THE DISCLOSURE The present disclosure can help address or mitigate at least some of the issues discussed above. Some embodiments of the present technique can provide a method of operating a core network entity for communicating with a communications device is provided. The method comprises receiving, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; determining, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; and transmitting, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server. Some embodiments of the present technique can provide a method of operating a communications device for communicating with a core network entity. The method comprises transmitting, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; receiving, from the core network entity, a second signal, the second signal including an address of a MoQ relay for communicating with the MoQ server by relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) determined by the core network entity based on the request signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; and establishing connection with the UPF based on the address of the MoQ relay. Respective aspects and features of the present disclosure are defined in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary, but are not restrictive, of the present technology. The described embodiments, together with further advantages, will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS A more complete appreciation of the disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings wherein like reference numerals designate identical or corresponding parts throughout the several views, and wherein: Figure 1 schematically represents some aspects of an LTE-type wireless telecommunication system which may be configured to operate in accordance with certain embodiments of the present disclosure; Figure 2 schematically represents some aspects of an NR-type wireless telecommunications system which may be configured to operate in accordance with certain embodiments of the present disclosure; Figure 3 is a schematic block diagram of an example infrastructure equipment and communications device which may be configured to operate in accordance with certain embodiments of the present disclosure; Figure 4 is a schematic block diagram of an example wireless communications network which may be configured to operate in accordance with certain embodiments of the present disclosure; Figure 5 is reproduced from [8], and illustrates a traffic model for extended Reality (XR); Figure 6 illustrates a part schematic, part message flow diagram representation of an example wireless communications system comprising a communications device and a core network entity in accordance with embodiments of the present disclosure; Figure 7 is a schematic block diagram of an example wireless communications system in accordance with embodiments of the present disclosure; Figure 8 illustrates a message flow diagram representation of an example wireless communications system comprising a communications device and a core network entity in accordance with some embodiments of the present disclosure; Figure 9 illustrates a message flow diagram representation of an example wireless communications system comprising a communications device and a core network entity in accordance with some other embodiments of the present disclosure; Figure 10 is a flow diagram illustrating a method of operating a core network entity of a wireless communications network in accordance with example embodiments of the present disclosure; and Figure 11 is a flow diagram illustrating a method of operating a communications device in accordance with example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS Long Term Evolution Advanced Radio Access Technology (4G) Figure 1 provides a schematic diagram illustrating some basic functionality of a mobile telecommunications network / system 6 operating generally in accordance with LTE principles, but which may also support other radio access technologies, and which may be adapted to implement embodiments of the disclosure as described herein. Various elements of Figure 1 and certain aspects of their respective modes of operation are well-known and defined in the relevant standards administered by the 3GPP body, and also described in many books on the subject, for example, Holma H. and Toskala A [1], It will be appreciated that operational aspects of the telecommunications networks discussed herein which are not specifically described (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be implemented in accordance with any known techniques, for example according to the relevant standards and known proposed modifications and additions to the relevant standards. The network 6 includes a plurality of base stations 1 connected to a core network 2. Each base station provides a coverage area 3 (i.e., a cell) within which data can be communicated to and from communications devices 4. Although each base station 1 is shown in Figure 1 as a single entity, the skilled person will appreciate that some of the functions of the base station may be carried out by disparate, inter-connected elements, such as antennas (or antennae), remote radio heads, amplifiers, etc. Collectively, one or more base stations may form a radio access network. Data is transmitted from base stations 1 to communications devices 4 within their respective coverage areas 3 via a radio downlink (DL). Data is transmitted from communications devices 4 to the base stations 1 via a radio uplink (UL). The core network 2 routes data to and from the communications devices 4 via the respective base stations 1 and provides functions such as authentication, mobility management, charging and so on. Terminal devices may also be referred to as mobile stations, user equipment (UE), user terminal, mobile radio, communications device, and so forth. Services provided by the core network 2 may include connectivity to the internet or to external telephony services. The core network 2 may further track the location of the communications devices 4 so that it can efficiently contact (i.e., page) the communications devices 4 for transmitting downlink data towards the communications devices 4. Base stations, which are an example of network infrastructure equipment, may also be referred to as transceiver stations, nodeBs, e-nodeBs, eNB, g-nodeBs, gNB and so forth. In this regard different terminology is often associated with different generations of wireless telecommunications systems for elements providing broadly comparable functionality. However, certain embodiments of the disclosure may be equally implemented in different generations of wireless telecommunications systems, and for simplicity certain terminology may be used regardless of the underlying network architecture. That is to say, the use of a specific term in relation to certain example implementations is not intended to indicate these implementations are limited to a certain generation of network that may be most associated with that particular terminology. New Radio Access Technology (5G) An example configuration of a wireless communications network which uses some of the terminology proposed for and used in NR and 5G is shown in Figure 2. In Figure 2 a plurality of transmission and reception points (TRPs) 10 are connected to distributed control units (DUs) 41, 42 by a connection interface represented as a line 16. Each of the TRPs 10 is arranged to transmit and receive signals via a wireless access interface within a radio frequency bandwidth available to the wireless communications network. Thus, within a range for performing radio communications via the wireless access interface, each of the TRPs lOhas a coverage area as represented by a circle 12. As such, wireless communications devices 14 which are within the coverage area 12 of each of the TRPs 10 can transmit and receive signals to and from those TRPs 10 via the wireless access interface. Each of the distributed units 41, 42 are connected to a central unit (CU) 40 (which may be referred to as a controlling node) via an interface 46. The central unit 40 is then connected to the core network 20 which may contain all other functions required to transmit data for communicating to and from the wireless communications devices and the core network 20 may be connected to other networks 30. The elements of the wireless access network shown in Figure 2 may operate in a similar way to corresponding elements of an LTE network as described with regard to the example of Figure 1. It will be appreciated that operational aspects of the telecommunications network represented in Figure 2, and of other networks discussed herein in accordance with embodiments of the disclosure, which are not specifically described (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be implemented in accordance with any known techniques, for example according to currently used approaches for implementing such operational aspects of wireless telecommunications systems, e.g. in accordance with the relevant standards. The TRPs 10 of Figure 2 may in part have a corresponding functionality to a base station or eNodeB of an LTE network. Similarly, the communications devices 14 may have a functionality corresponding to the UE devices 4 known for operation with an LTE network. It will be appreciated therefore that operational aspects of a new RAT network (for example in relation to specific communication protocols and physical channels for communicating between different elements) may be different to those known from LTE or other known mobile telecommunications standards. However, it will also be appreciated that each of the core network component, base stations and communications devices of a new RAT network will be functionally similar to, respectively, the core network component, base stations and communications devices of an LTE wireless communications network. In terms of broad top-level functionality, the core network 20 connected to the new RAT telecommunications system represented in Figure 2 may be broadly considered to correspond with the core network 2 represented in Figure 1, and the respective central units 40 and their associated distributed units / TRPs 10 may be broadly considered to provide functionality corresponding to the base stations 1 of Figure 1. The term network infrastructure equipment / access node may be used to encompass these elements and more conventional base station type elements of wireless telecommunications systems. Depending on the application at hand the responsibility for scheduling transmissions which are scheduled on the radio interface between the respective distributed units and the communications devices may lie with the controlling node / central unit and / or the distributed units / TRPs. A communications device 14 is represented in Figure 2 within the coverage area of the first coverage area 12. This communications device 14 may thus exchange signalling with the first central unit 40 in the first coverage area 12 via one of the distributed units / TRPs 10 associated with the first coverage area 12. It will further be appreciated that Figure 2 represents merely one example of a proposed architecture for a new RAT based telecommunications system in which approaches in accordance with the principles described herein may be adopted, and the functionality disclosed herein may also be applied in respect of wireless telecommunications systems having different architectures. Thus, certain embodiments of the disclosure as discussed herein may be implemented in wireless telecommunication systems / networks according to various different architectures, such as the example architectures shown in Figures 1 and 2. It will thus be appreciated the specific wireless telecommunications architecture in any given implementation is not of primary significance to the principles described herein. In this regard, certain embodiments of the disclosure may be described generally in the context of communications between network infrastructure equipment / access nodes and a communications device, wherein the specific nature of the network infrastructure equipment / access node and the communications device will depend on the network infrastructure for the implementation at hand. For example, in some scenarios the network infrastructure equipment / access node may comprise a base station, such as an LTE-type base station 1 as shown in Figure 1 which is adapted to provide functionality in accordance with the principles described herein, and in other examples the network infrastructure equipment may comprise a control unit / controlling node 40 and / or a TRP 10 of the kind shown in Figure 2 which is adapted to provide functionality in accordance with the principles described herein. A more detailed diagram of some of the components of the network shown in Figure 2 is provided by Figure 3. In Figure 3, a TRP 10 as shown in Figure 2 comprises, as a simplified representation, a wireless transmitter 30, a wireless receiver 32 and a controller or controlling processor 34 which may operate to control the transmitter 30 and the wireless receiver 32 to transmit and receive radio signals to one or more UEs 14 within a coverage area 12 formed by the TRP 10. As shown in Figure 3, an example UE 14 is shown to include a corresponding transmitter 49, a receiver 48 and a controller 44 which is configured to control the transmitter 49 and the receiver 48 to transmit signals representing uplink data to the wireless communications network via the wireless access interface formed by the TRP 10 and to receive downlink data as signals transmitted by the transmitter 30 and received by the receiver 48 in accordance with the conventional operation. The transmitters 30, 49 and the receivers 32, 48 (as well as other transmitters, receivers and transceivers described in relation to examples and embodiments of the present disclosure) may include radio frequency filters and amplifiers as well as signal processing components and devices in order to transmit and receive radio signals in accordance for example with the 5G / NR standard. The controllers 34, 44 (as well as other controllers described in relation to examples and embodiments of the present disclosure) may be, for example, a microprocessor, a CPU, or a dedicated chipset, etc., configured to carry out instructions which are stored on a computer readable medium, such as a non-volatile memory. The processing steps described herein may be carried out by, for example, a microprocessor in conjunction with a random access memory, operating according to instructions stored on a computer readable medium. The transmitters, the receivers and the controllers are schematically shown in Figure 3 as separate elements for ease of representation. However, it will be appreciated that the functionality of these elements can be provided in various different ways, for example using one or more suitably programmed programmable computer(s), or one or more suitably configured application-specific integrated circuit(s) / circuitry / chip(s) / chipset(s). As will be appreciated the infrastructure equipment / TRP / base station as well as the UE / communications device will in general comprise various other elements associated with its operating functionality. As shown in Figure 3, the TRP 10 also includes a network interface 50 which connects to the DU 42 via a physical interface 16. The network interface 50 therefore provides a communication link for data and signalling traffic from the TRP 10 via the DU 42 and the CU 40 to the core network 20. The interface 46 between the DU 42 and the CU 40 is known as the Fl interface which can be a physical or a logical interface. The Fl interface 46 between CU and DU may operate in accordance with specifications 3GPP TS 38.470 and 3GPP TS 38.473, and may be formed from a fibre optic or other wired or wireless high bandwidth connection. In one example the connection 16 from the TRP 10 to the DU 42 is via fibre optic. The connection between a TRP 10 and the core network 20 can be generally referred to as a backhaul, which comprises the interface 16 from the network interface 50 of the TRP 10 to the DU 42 and the Fl interface 46 from the DU 42 to the CU 40. The core network 20 is connected to the CU 40 via the N2 (also called NG-C) interface for carrying control data and via the N3 (also called NG-U) interface for carrying user data. Figure 4 illustrates a communications network 51 which may be configured to operate in accordance with certain embodiments of the present disclosure, and in which the core network 20 (i.e. the core network 20 discussed with respect to Figures 2 and 3, for example) is shown in more detail. The communications network 51 of Figure 4 comprises a UE 14, an access node (AN) 10 which may in particular be a radio access node (RAN) such as a gNB, a core network 20, and an application function node (AF) 52. Here, as those skilled in the art would appreciate, the AF 52 controls applications though providing interaction between the application layer and various network functions and resources. The core network 20 here may be a 5G / NR core network as specified by the 3GPP such as a 5GC and as referred to above with respect to Figure 2, for example. The core network 20 as shown in Figure 4 may comprise several core network nodes, in particular a policy control function and / or network exposure function node (PCF / NEF) 54 which control some aspects related to security and capacity, a session management function node (SMF) 55 that handles calls and sessions, an access and mobility management function node (AMF) 56 that provides access for the UE 14 and the AN / RAN 10, and / or a user plane function node (UPF) 53 which handles user data. The AF may, for example, interact with the NEF / PCT 54 and / or the UPF 53. Those skilled in the art would appreciate that the core network 20 may comprise other functions to those that are shown in Figure 4, which include but are not limited to: a unified data management function node (UDM), a network repository function node (NRF), a network slice selection function node (NSSF), and a charging function node (CHF), which allows charging functions to be provided to network functions. Services Supported by NR Networks Systems incorporating NR technology support a number of different services (or types of services), which may be characterised by different requirements for latency, data rate and / or reliability. For example, Enhanced Mobile Broadband (eMBB) services are characterised by high capacity with a requirement to support up to 20 Gb / s. A requirement for Ultra Reliable and Low Latency Communications (URLLC) services is that one transmission of a 32 byte packet is required to be transmitted from the radio protocol layer 2 / 3 SDU ingress point to the radio protocol layer 2 / 3 SDU egress point of the radio interface within 1 ms with a reliability of 1—10’5 (99.999 %) or higher (99.9999 %) [2], Massive Machine Type Communications (mMTC) is another example of a service which may be supported by NR-based communications networks. In addition, systems may be expected to support further enhancements related to Industrial Internet of Things (IIoT) in order to support services with new requirements of high availability, high reliability, low latency, and in some cases, high-accuracy positioning. Enhanced URLLC (eURLLC) [3] [4] specifies features that require high reliability and low latency, such as factory automation, transport industry, electrical power distribution, etc. It should be appreciated that the Uplink Control Information (UCI) for URLLC and eMBB will have different requirements. Another such service incorporating NR technology is 5GNR in Unlicensed Spectrum (NR-U) [5], which enable devices to make use of shared and unlicensed spectrum bandwidth. Such features as Listen Before Talk (LBT), as specified by [5], is incorporated into the NR frame structure for NR-U operation in unlicensed bands. extended Reality (XR), which covers a number of different types of application such as as augmented reality (AR), mixed reality (MR), and virtual reality (VR), and cloud gaming (CG), refers generally to various types of augmented, virtual, and mixed environments, where human-to-machine and human-to-human communications are performed with the assistance of handheld and wearable end user devices (UEs). XR applications are considered important for NR Rei-18 and beyond (also known as 5G Advanced) [6], XR applications may require both a relatively high data rates and low latency. As 5G NR was not designed to support the combination of the aforementioned requirements, XR applications may not be supported optimally in 5G NR networks and user experience may suffer because the required data rate / latency may not be reached and UE power consumption may be high. XR applications may have the unique characteristic that the associated traffic pattern is deterministic (i.e., have a certain periodicity and certain number of traffic flows). There may be further relevant other applications with multiple data streams having different characteristics, like factory automation, remote machine operation, and unmanned aerial vehicle (UAV) operation, or applications requiring a differentiation between video and audio. XR traffic is rich in video, especially in the downlink, with a typical frame rate of 60 Hz [7], which leads to a data transmission with non-integer periodicity in NR, i.e. the periodicity is not an integer number of subframes and in this example, the periodicity is 16.67 ms. Due to varying frame encoding delay and network transfer time, the packet arrival at the gNB may experience random jitter. The non-integer and jitter characteristics of XR traffic is known as quasi-periodic traffic. In addition to jitter, the packet size also varies within a range; that is the packet size in each period is random. The jitter and random packet size of UL traffic is illustrated in Figure 5, which is based on a similar figure (figure 5.1.1-1) in [8], Figure 5 illustrates a single stream traffic model for XR. A first packet k 61 is transmitted, representing Internet Protocol (IP) packets belonging to video frame k. At a later point in time -which, on average, is the inverse of the frame generation rate (i.e., 1 / fps) as denoted by arrow 65 - a second packet k+1 62 is transmitted, representing IP packets belonging to video frame k+1. The variable packet size which follows a probability distribution is shown by arrow 63, while the variable jitter which also follows a probability distribution is denoted by arrow 64. Media over QUIC (MoQ) XR media can be provided by means of Media Over QUIC (MoQ) technology to benefit from the quick connection establishment time of QUIC, which further leads to faster media delivery. MoQ further provides the advantages of enabling multiplexing and combining data from multiple services over one connection, for example, parallel independent streams. In addition, it is considered that arranging an MoQ Relay between the client (e.g. UE) and the MoQ Server has potential benefits for hiding network details behind the relay. The terms “MoQ Relay”, “MoQ Proxy”, and variations thereof, are used interchangeably herein, and generally refer to entities that relays the traffic between the client and the MoQ server. Encrypted traffic may also be supported by using a MoQ Relay in the network (e.g. UPF). Other benefits provided by MoQ Relay include improved load balancing, speeding up content delivery, security and privacy, enhanced congestion control and low latency of media delivery. Nevertheless, there is a need for improved methods to allow the client to discover the MoQ Relay in the network. Embodiments of the present technique allow the client to discover the MoQ Relay so that the client can be provided with, inter alia, security and privacy for the media delivery. In addition, embodiments of the present technique further enable capability negotiation, thus allowing the network to assign an appropriate UPF that supports the MoQ Relay functionality as a MoQ Relay for the client. Compared to using QUIC directly, in MoQ each element is divided into payload and metadata (metadata not encrypted). Since MoQ in edge of local network (i.e. traffic via relay) goes into a single entry point, the relay can decide which server will serve the content. Accordingly, a mechanism is needed to determine how which server behind the relay is selected. Technical Problem It has been discussed that Edge Application Server Discovery Function (EASDF) can be used by the client (UE) to retrieve an IP-address to the MoQ Relay. However, the solution is about how to support encrypted traffic. If an EASDF based solution is used to retrieve an IP-address to the MoQ Relay, then there is a practical problem with encrypted traffic. To be able to support that, then all MoQ Relays that use the same certificate must share the same private certificate with all other MoQ Relays. However, an XR Content provider will most likely not share their private certificate (which is owned by the owner of the domain name) to the operator. The same problem occurs when using the same FQDN (the complete domain name for a specific computer, or host, on the internet) between operators, as they will not share it with each other. If only the IP address to the MoQ Relay is used, then security using TLS / SSL is not possible based on this EASDF solution since IP addresses not valid anymore. In addition, there is a problem when the UE does not use an FQDN that is intended for the “real” server on the internet, and instead delivers an IP-address that is not owned by the XR Content provider but owned by the operator. Doing so then the UE uses that IP address regardless of if it uses 3GPP access or non-integrated, non-3GPP access, i.e. WiFi direct via local access point not connected to the operator. This will poison the domain name system (DNS) cache in the UE and therefore undesirable. There is therefore a need for improved methods, communications devices and core network entities which can address at least some of the problems identified above. Accessing MoQ Server via MoQ Relay Embodiments of the present technique provide a MoQ based solution where the network acts as a MoQ Relay. The issues with certificate can be avoided if the UE is instead provided with the FQDN that is used to access the MoQ Relay so there is two different FQDN, one to the actual XR media server (MoQ Server) and another to the local MoQ Relay. In addition, embodiments of the present technique provide that the UE indicates the MoQ Relay capability support when setting up a data connection (PDU Session Establishment) or when modifying a data connection (PDU Session Modification). This allows the network to select an appropriate UPF that have the MoQ Relay functionality. That is, a UPF that supports the MoQ Relay functionality as a MoQ Relay for the client. Capability negotiation According to embodiments of the present technique, the UE indicates if it supports XR media using MoQ via a relay when connectivity is set up (e.g. by PDU Session Establishment procedure) or when connectivity is modified (e.g. by PDU Session Modification procedure), this allows the network to select an appropriate UPF supporting relay capability when the connectivity is set up. The indication could, for example, be provided in a PCO (Protocol Configuration Option) element that is sent by the UE during PDU Session Establishment / Modification procedure. As such, embodiments of the present technique allow capability negotiation, such that the network can assign an appropriate UPF that supports the MoQ Relay functionality as a MoQ Relay for the client. Providing FQDN of the MoQ Relay to UE Embodiments of the present technique provide various solutions for the UE to access the MoQ Relay: 1) According to some embodiments of the present technique, during PDU Session Establishment / Modification procedure, the UE receives from the network a FQDN of the MoQ Relay - located in the operator’s local UPF - in a PCO (Protocol Configuration Option) parameter. This could be done as a response to a PCO from the UE. For example, this could be a response to PCO where the UE indicates that it supports MoQ Relay (see above). The indication can be represented by a key value, encoded as a specific number of bits (e.g. one bit) or as a string. With this indication, the network can assign an UPF that supports MoQ Relay capabilities to the UE. 2) According to some other embodiments of the present technique, the UE performs a DNS lookup (similar to EASDF) of the FQDN of the MoQ Server or the MoQ Relay. If the DNS response is a C-NAME then the UE uses that as a FQDN to the MoQ Relay. C-Name is a way to configure alias in the DNS system when multiple FQDN should correspond to the same IP-address. However, it should be understood that the present disclosure is not so limited and any alias information such as a service (SRV) record may be used. With this then the UE will have two different FQDNs, one to the real XR media server and another FQDN to the operators MoQ Relay. This allows each operator to have its own unique FQDN to their MoQ Relay with their private certificate associated to it. Those skilled in the art would further appreciate that the solution is compatible with the Android application model. As will also be appreciated by one skilled in the art, capability signalling can be performed independently. Signalling for accessing MoQ Relay Figure 6 shows a part schematic, part message flow diagram representation of an example wireless communications system 103 comprising a communications device 101 (e.g. a UE 14) and a core network entity 102 (e.g. an SMF 10) in accordance with at least some embodiments of the present technique. The communications device 101 is configured to transmit signals to and / or receive signals from the core network, for example, to and from the core network entity 102, where the core network may be a core network such as that described above with reference to Figure 4. Such signals received by the communications device 101 may, for example, include data for applications such as XR. The communications device 101 comprises a transceiver (or transceiver circuitry) 101.1 and a controller (or controller circuitry) 101.2, while the core network entity 102 comprises interface circuitry 102.1 and a controller (or controller circuitry) 102.2. Each of the controllers 101.2, 102.2 may be, for example, a microprocessor, a CPU, or a dedicated chipset, etc. As shown in the example of Figure 6, the interface circuitry 102.1 and the controller circuitry 102.2 of the core network entity 102 are configured in combination to receive, from the communications device 101, a first (e.g. request) signal 111, the first signal 111 being (or comprising) a request for information to enable the communications device 101 to communicate with a MoQ server; to determine, based on the received first signal 111, a UPF to serve as a MoQ relay for the communications device 101 for communicating with the MoQ server, in which the MoQ relay relays traffic between the communications device 101 and the MoQ server; and to transmit, to the communications device 101, a second (e.g. response) signal 112 which includes an address of the MoQ relay for the communications device 101 to establish connection with the determined UPF. In particular, the address of the MoQ relay is different from an address of the MoQ server. As is appreciated by the skilled person, the MoQ relay and MoQ server are identified by their respective addresses, but the disclosure is not so limited and any identifier that can be used to identify the MoQ relay and MoQ server is envisaged. In some embodiments, the address of the MoQ relay may be a Full Quality Domain Name (FQDN). The address of the MoQ relay and the address of the MoQ server may also be associated with different private certificates. In some embodiments of the present technique, the first / request signal 111 received by the core network entity 102 may comprise an indication of a capability of the communications device 101 for supporting connections with the MoQ relay. Although embodiments of the present technique use a request signal to carry the indication of MoQ relay capability, it should be understood that the present disclosure is not so limited and any signalling for the communications device to indicate its MoQ relay capability to the network entity may be used. Such indication of the capability of the communications device 101 for supporting connections with a MoQ relay may be a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Establishment / Modification. Meanwhile, the second (e.g. response) signal 112 transmitted by the core network entity 102 may be a response for PDU Session Establishment / Modification, and the address of the MoQ relay may be a PCO parameter included in the response for PDU Session Establishment / Modification. However, it should be understood that the disclosure is not so limited and any signalling that can provide the address of the MoQ relay may be used. In some other embodiments of the present technique, however, the first / request signal 111 received by the core network entity 102 may comprise a Domain Name System (DNS) query requesting an information associated with an address of the MoQ server or the MoQ Relay indicated in the first / request signal 111. In particular, the requested information may be the address of the MoQ relay transmitted to the communications device 101 in the second / response signal 112. In some example embodiments, the core network entity 102 may transmit, to a local DNS server after (e.g. in response to) receiving the first (e.g. request) signal 111, a request for the alias information associated with the address of the MoQ server or the MoQ relay. Subsequently, the core network entity 102 may then receive, from the local DNS server in response to the request for the alias information, an indication of the alias information. Specifically, the requested alias information associated with the address of the MoQ server or the MoQ relay may a Canonical Name (C-NAME) or a DNS Service (SRV) record. Figure 7 illustrates a schematic block diagram of an example wireless communications system in accordance with embodiments of the present disclosure. In Figure 7, the example wireless communications system 700 includes a User Equipment (UE) 701, a Radio Access Network (RAN) 702, an Access and Mobility Management Function (AMF) 703, a Session Management Function (SMF) 704, a User Plane Function (UPF) MoQ relay 704, a MoQ server 705 and a Domain Name System (DNS) 706. In accordance with embodiments of the present technique, signal flow 711 includes a first (e.g.) request signal transmitted from the UE 701 to the SMF 704 in the core network. The first / request signal is a request for information to enable the UE 701 to communicate with a MoQ server 706. In some embodiments, the request may be a request for the UE 701 to communicate with the MoQ server 706. The SMF 704 receives the first / request signal and uses it to determine an appropriate UPF 704 which supports MoQ relay capability to act as a MoQ relay for the UE 701, so that the UE 701 communicates with the MoQ server 706 by the MoQ relaying the traffic between the UE 701 and the MoQ server 706. The signal flow 711 further includes a second (e.g. response) signal transmitted from the SMF 704 to the UE 701. The second / response signal comprises an address of the MoQ relay 705, which is different from an address of the MoQ server 706. In some embodiments, the address of the MoQ relay 705 may be a Full Quality Domain Name (FQDN). Additionally, the address of the MoQ relay 705 and the address of the MoQ server 706 are associated with different private certificates. Next, the UE 701 uses this FQDN of the MoQ relay 705 to set up a connection with the determined UPF 705 via signal flow 712. Furthermore, signal flow 713 between the UPF MoQ relay 705 and MoQ server 706 contains signalling for the MoQ server 706 to determine whether UE 701 is allowed to use the MoQ relay 705. Although embodiments of the present technique use UPF as a core network entity to act as a MoQ Relay, it should be understood that the disclosure is not so limited and any core network entity that can serve as a relay for the traffic between the UE and the MoQ server may be used. According to some embodiments of the present technique, the first (e.g. request) signal in the signal flow 711 may comprise an indication of a capability of the UE 701 for supporting connections with the MoQ relay 705. The indication of the MoQ relay capability of the UE 701 may be a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Establishment / Modification sent by the UE 701 to the SMF 704. On the other hand, the second / response signal transmitted by the SMF 704 in the signal flow 711 may be a PDU Session Establishment / Modification response, which contains a PCO parameter representing the FQDN of the MoQ relay 705. According to some other embodiments of the present technique, the first (e.g. request) signal in the signal flow 711 may comprise a Domain Name System (DNS) query which requests an information associated with an FQDN of the MoQ server 706 or the MoQ relay 705, as indicated in the first / request signal. Such requested information is provided to the UE 701 in the second (e.g. response) signal and may be the FQDN of the MoQ relay 705. In some example embodiments, the SMF 704, after (and in some arrangements, indeed, in response to) receiving the first / request signal, may transmit a DNS query to the local DNS server 707 via signal flow 714 in order to request alias information associated with the FQDN of the MoQ server 706 or the MoQ relay 705. The local DNS server 706, in response to the DNS query, returns an indication of the alias information such as DNS to the SMF 704 via signal flow 714. Specifically, the alias information associated with the FQDN of the MoQ server or the MoQ relay is a Canonical Name (C-NAME) or a DNS Service (SRV) record. Figure 8 illustrates a message flow diagram representation of an example wireless communications system comprising a communications device and a core network entity in accordance with some embodiments of the present disclosure. In Figure 8, the example wireless communication system 800 includes a UE 801, a SMF 802, and a UPF MoQ Relay 803. According to some embodiments of the present technique, the UE 801 transmits a PDU Session Establishment / Modification request to the SMF 802 containing a request for information to enable the UE 801 to communicate with a MoQ server. The request may contain a Protocol Configuration Option (PCO) parameter indicating a capability of the UE 801 for supporting connections with the MoQ relay 803, in which the MoQ relay 803 relays traffic between the UE 801 and the MoQ server. The SMF 802 receives the request in the PDU Session Establishment / Modification request and determines an appropriate UPF 803 which supports MoQ relay capability to act as a MoQ relay for the UE 801. The SMF 802 then returns a PDU Session Establishment / Modification response to the UE 801 containing a PCO parameter which represents an address, such as a FQDN, of the MoQ relay 803. In some embodiments, the SMF 802 may request the address from a local DNS server. Specifically, the MoQ relay and the MoQ server have different FQDNs, each of the FQDNs are associated with different private certificates. Subsequently, the UE 801 uses the FQDN of the MoQ relay to set up a connection with the UPF MoQ Relay 803 as determined by the SMF 802. Figure 9 illustrates a message flow diagram representation of an example wireless communications system comprising a communications device and a core network entity in accordance with some other embodiments of the present disclosure. In Figure 9, the example wireless communication system 900 includes a UE 901, a SMF 902, and a UPF MoQ Relay 903. According to some embodiments of the present technique, the UE 901 transmits a DNS Query message to the SMF 902 containing a request for a C-Name associated with the address, such as a FQDN, of the MoQ server or the MoQ Relay 903. The SMF 902 regards the DNS Query message as a request for the UE 901 to communicate with a MoQ server. According to some embodiments of the present technique, the SMF 902 then transmits, to a local DNS server after (or in response to) receiving the DNS Query message, a request for the alias information associated with the address of the MoQ server or the MoQ relay, for example, a Canonical Name (C-Name) or a DNS Service (SRV) record. In response to the request for the alias information, the local DNS server returns an indication of the alias information to the SMF 902. In addition, the SMF 902 determines an appropriate UPF 903 which supports MoQ relay capability to act as a MoQ relay for the UE 901. The SMF 902 then returns a DNS Response to the UE 801 containing the alias information, such as the C-Name, associated with the FQDN of the MoQ server or the MoQ relay. Specifically, the MoQ relay and the MoQ server have different FQDNs, each of the FQDNs are associated with different private certificates. Subsequently, the UE 901 uses the alias information associated with the FQDN of the MoQ server or the MoQ relay to set up a connection with the UPF MoQ Relay 903 as determined by the SMF 902. Figure 10 shows a flow diagram illustrating a method of operating a core network entity of a wireless communications network in accordance with example embodiments of the present technique. The process shown by Figure 10 is specifically a method of operating a core network entity (e.g. SMF) forming part of a wireless communications network configured to transmit signals to and / or to receive signals from a communications device (e.g. UE). The method begins in step SI. The method comprises, in step S2, receiving, from the communications device, a first (e.g. request) signal, the first signal being a request for information to enable the communications device to communicate with a MoQ server. Next, in step S3, the process comprises determining, based on the received first signal, a UPF to serve as a MoQ relay for the communications device, in which the MoQ relay relays traffic between the communication device and the MoQ server. In some embodiments, the selection of UPF which acts as a MoQ relay is optional. For example, if the UPF is already assigned before the core network entity receives the first signal, the UPF will not be selected based on the first signal. Then, in step S4, the process comprises transmitting, to the communications device, a response signal, the response signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF. Specifically, the address of the MoQ relay is different from an address of the MoQ server. The process ends in step S5. In some embodiments, the address of the MoQ relay may be a Full Quality Domain Name (FQDN). Furthermore, the address of the MoQ relay and the address of the MoQ server may be associated with different private certificates. According to some embodiments of the present technique, the first (e.g. request) signal may comprise an indication of a capability of the communications device for supporting connections with the MoQ relay. Such indication of the capability of the communications device for supporting connections with a MoQ relay may be a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Establishment / Modification. On the other hand, the second (e.g. response) signal may be a response for PDU Session Establishment / Modification, and the address of the MoQ relay may be a parameter contained in a PCO (that is, a PCO parameter) included in the response for PDU Session Establishment / Modification. According to some other embodiments of the present technique, the first / request signal may comprise a Domain Name System (DNS) query requesting an information associated with an address of the MoQ server indicated in the first signal. The requested information may be the address of the MoQ relay transmitted to the communications device in the second / response signal. In some example embodiments, the method may comprise transmitting, to a local DNS server after receiving the first (e.g. request) signal, a request for alias information associated with the address of the MoQ server or the MoQ relay, and subsequently receiving, from the local DNS server in response to the request for the alias information, an indication of the alias information. The alias information associated with the address of the MoQ server or the MoQ relay may be a Canonical Name (C-NAME) or a DNS Service (SRV) record. Figure 11 is a flow diagram illustrating a method of operating a communications device in accordance with example embodiments of the present technique. The process shown by Figure 11 is specifically a method of operating a communications device (e.g. UE) forming part of a wireless communications network configured to transmit signals to and / or to receive signals from a core network entity (e.g. SMF). The method begins in step SI 1. The method comprises, in step S12, transmitting, to the core network entity, a first (e.g. request) signal, the first signal being a request for information to enable the communications device to communicate with a MoQ server, for the core network entity to determine a UPF to serve as a MoQ relay for the communications device, in which the MoQ relay relays traffic between the communications device and the MoQ server. Next, in step S13, the method comprises receiving, from the core network entity, a second (e.g. response) signal, the second signal including an address of the MoQ relay, in which the address of the MoQ relay is different from an address of the MoQ server. Subsequently, in step S14, the method comprises establishing connection with the determined UPF based on the address of the MoQ relay. The process ends in step SI5. In some embodiments, the address of the MoQ relay may be a FQDN. Additionally, the address of the MoQ relay and the address of the MoQ server may be associated with different private certificates. According to some embodiments of the present technique, the first / request signal transmitted by the communications device may comprise an indication of a capability of the communications device for supporting connections with the MoQ relay. Such indication of the capability of the communications device for supporting connections with a MoQ relay may be a PCO parameter included in a request for PDU Session Establishment or a request for PDU Session Modification. On the other hand, the second / response signal may be a response for PDU Session Establishment or a response for PDU Session Modification, and the address of the MoQ relay may be a PCO parameter included in the response for PDU Session Establishment or the response for PDU Session Modification. According to some other embodiments of the present technique, the first / request signal transmitted by the communications device may comprise a DNS query requesting an information associated with an address of the MoQ server or the MoQ relay, as indicated in the first signal. The requested information may be the address of the MoQ relay transmitted to the communications device in the second / response signal. The requested information associated with the address of the MoQ server or the MoQ relay may be a C-NAME or a DNS SRV record. The following numbered paragraphs provide further example aspects and features of the present technique: Paragraph 1. A method for operating a core network entity for communicating with a communications device, the method comprising: receiving, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; determining, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; and transmitting, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server. Paragraph 2. A method according to paragraph 1, wherein the address of the MoQ relay is a Full Quality Domain Name (FQDN). Paragraph 3. A method according to paragraph 1 or paragraph 2, wherein the first signal comprises an indication of a capability of the communications device for supporting connections with the MoQ relay. Paragraph 4. A method according to paragraph 3, wherein the indication of the capability of the communications device for supporting connections with a MoQ relay is a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Estab li shment / Modifi cati on. Paragraph 5. A method according to paragraph 4, wherein the second signal is a response for PDU Session Establishment / Modification, and the address of the MoQ relay is a PCO parameter included in the response for PDU Session Establishment / Modification. Paragraph 6. A method according to paragraph 1 or paragraph 2, wherein the first signal comprises a Domain Name System (DNS) query requesting information associated with an address of the MoQ server or the MoQ Relay indicated in the first signal, and wherein the requested information is the address of the MoQ relay transmitted to the communications device in the second signal. Paragraph 7. A method according to paragraph 6, comprising transmitting, to a local DNS server after receiving the first signal, a request for alias information associated with the address of the MoQ server or the MoQ relay, and receiving, from the local DNS server in response to the request for the alias information, an indication of the alias information. Paragraph 8. A method according to paragraph 6 or paragraph 7, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a Canonical Name (C-NAME). Paragraph 9. A method according to paragraph 6 or paragraph 7, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a DNS Service (SRV) record. Paragraph 10. A method according to any of paragraphs 1 to 9, wherein the core network entity is a Session Management Function (SMF). Paragraph 11. A method of operating a communications device for communicating with a core network entity, the method comprising transmitting, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; receiving, from the core network entity, a second signal, the second signal including an address of a MoQ relay for communicating with the MoQ server by relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) determined by the core network entity based on the request signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; and establishing connection with the UPF based on the address of the MoQ relay. Paragraph 12. A method according to paragraph 11, wherein the address of the MoQ relay is a Full Quality Domain Name (FQDN). Paragraph 13. A method according to paragraph 11 or paragraph 12, wherein the first signal comprises an indication of a capability of the communications device for supporting connections with the MoQ relay. Paragraph 14. A method according to paragraph 13, wherein the indication of the capability of the communications device for supporting connections with a MoQ relay is a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Establishment / Modification. Paragraph 15. A method according to paragraph 14, wherein the second signal is a response for PDU Session Establishment / Modification, and the address of the MoQ relay is a PCO parameter included in the response for PDU Session Establishment / Modification. Paragraph 16. A method according to paragraph 11 or paragraph 12, wherein the first signal comprises a Domain Name System (DNS) query requesting information associated with an address of the MoQ server or the MoQ relay indicated in the first signal, and wherein the requested information is the address of the MoQ relay received by the communications device in the second signal. Paragraph 17. A method according to paragraph 16, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a Canonical Name (C-NAME). Paragraph 18. A method according to paragraph 16, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a DNS Service (SRV) record. Paragraph 19. A method according to any of paragraphs 11 to 18, wherein the core network entity is a Session Management Function (SMF). Paragraph 20. A core network entity of a wireless communications network for communicating with a communications device, the core network entity comprising interface circuitry configured to transmit signals and to receive signals, and a controller configured in combination with the interface circuitry to receive, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; determine, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; and transmit, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server. Paragraph 21. A communications device for communicating with core network entity of a wireless communications network, the communications device comprising a transceiver configured to transmit signals and to receive signals, and a controller configured in combination with the transceiver to transmit, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; receive, from the core network entity, a second signal, the second signal including an address of a MoQ relay for the communication device to communicate with the MoQ server by the MoQ relay relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) as determined by the core network entity based on the first signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; and establish connection with the UPF based on the address of the MoQ relay. Paragraph 22. Circuitry for core network entity of a wireless communications network for communicating with a communications device, the circuitry comprising transceiver circuitry configured to transmit signals and to receive signals, and controller circuitry configured in combination with the transceiver circuitry to receive, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; determine, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; and transmit, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server. Paragraph 23. Circuity for a communications device for communicating with a core network entity of a wireless communications network, the circuitry comprising transceiver circuitry configured to transmit signals and to receive signals, and controller circuitry configured in combination with the transceiver circuitry to transmit, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server; receive, from the core network entity, a second signal, the second signal including an address of a MoQ relay for the communication device to communicate with the MoQ server by the MoQ relay relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) as determined by the core network entity based on the first signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; and establish connection with the UPF based on the address of the MoQ relay. Paragraph 24. A wireless communications system comprising a core network entity according to paragraph 20 and a communications device according to paragraph 21. Paragraph 25. A computer program which, when the program is executed by a computer, cause the computer to perform the method of paragraph 1 or paragraph 11. Paragraph 26. A non-transitory computer-readable storage medium storing a computer program according to paragraph 25. It will be appreciated that the above description for clarity has described embodiments with reference to different functional units, circuitry and / or processors. However, it will be apparent that any suitable distribution of functionality between different functional units, circuitry and / or processors may be used without detracting from the embodiments. Described embodiments may be implemented in any suitable form including hardware, software, firmware or any combination of these. Described embodiments may optionally be implemented at least partly as computer software running on one or more data processors and / or digital signal processors. The elements and components of any embodiment may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units. As such, the disclosed embodiments may be implemented in a single unit or may be physically and functionally distributed between different units, circuitry and / or processors. Although the present disclosure has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognise that various features of the described embodiments may be combined in any manner suitable to implement the technique. References [1] Holma H. and Toskala A, “LTE for UMTS OFDMA and SC-FDMA based radio access”, John Wiley and Sons, 2009. [2] TR 38.913, “Study on Scenarios and Requirements for Next Generation Access 5 Technologies (Release 14)”, third Generation Partnership Project, V14.3.0. [3] RP-190726, “Physical layer enhancements for NR ultra-reliable and low latency communication (URLLC)”, Huawei, HiSilicon, RAN#83. [4] RP-201310, “Revised WID: Enhanced Industrial Internet of Things (loT) and ultra reliable and low latency communication (URLLC) support for NR,” Nokia, Nokia 10 Shanghai Bell, RAN#88e. [5] RP-191575, “NR-based Access to Unlicensed Spectrum”, Qualcomm, RAN#84. [6] RP-220285, “Revised SID: Study on XR Enhancements for NR”, Nokia, RAN#95e. [7] R2-2302309 (TR38.835), “Study on XR enhancements for NR”, vl.0.2. [8] TR 38.838, “Study on XR (Extended Reality) Evaluations for NR (Release 17)”, vl7.0.0.

Claims

What is claimed is:

1. A method for operating a core network entity for communicating with a communications device, the method comprising:receiving, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;determining, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; andtransmitting, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server.

2. A method according to claim 1, wherein the address of the MoQ relay is a Full Quality Domain Name (FQDN).

3. A method according to claim 1 or claim 2, wherein the first signal comprises an indication of a capability of the communications device for supporting connections with the MoQ relay.

4. A method according to claim 3, wherein the indication of the capability of the communications device for supporting connections with a MoQ relay is a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Estab li shment / Modifi cati on.

5. A method according to claim 4, wherein the second signal is a response for PDU Session Establishment / Modification, and the address of the MoQ relay is a PCO parameter included in the response for PDU Session Establishment / Modification.

6. A method according to claim 1 or claim 2, wherein the first signal comprises a Domain Name System (DNS) query requesting information associated with an address of the MoQ server or the MoQ Relay indicated in the first signal, and wherein the requested information is the address of the MoQ relay transmitted to the communications device in the second signal.

7. A method according to claim 6, comprisingtransmitting, to a local DNS server after receiving the first signal, a request for alias information associated with the address of the MoQ server or the MoQ relay, andreceiving, from the local DNS server in response to the request for the alias information, an indication of the alias information.

8. A method according to claim 6 or claim 7, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a Canonical Name (C-NAME).

9. A method according to claim 6 or claim 7, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a DNS Service (SRV) record.

10. A method according to any of claims 1 to 9, wherein the core network entity is a Session Management Function (SMF).

11. A method of operating a communications device for communicating with a core network entity, the method comprisingtransmitting, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;receiving, from the core network entity, a second signal, the second signal including an address of a MoQ relay for communicating with the MoQ server by relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) determined by the core network entity based on the request signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; and establishing connection with the UPF based on the address of the MoQ relay.

12. A method according to claim 11, wherein the address of the MoQ relay is a Full Quality Domain Name (FQDN).

13. A method according to claim 11 or claim 12, wherein the first signal comprises an indication of a capability of the communications device for supporting connections with the MoQ relay.

14. A method according to claim 13, wherein the indication of the capability of the communications device for supporting connections with a MoQ relay is a Protocol Configuration Option (PCO) parameter included in a request for Protocol Data Unit (PDU) Session Estab li shment / Modifi cati on.

15. A method according to claim 14, wherein the second signal is a response for PDU Session Establishment / Modification, and the address of the MoQ relay is a PCO parameter included in the response for PDU Session Establishment / Modification.

16. A method according to claim 11 or claim 12, wherein the first signal comprises a Domain Name System (DNS) query requesting information associated with an address of the MoQ server or the MoQ relay indicated in the first signal, and wherein the requested information is the address of the MoQ relay received by the communications device in the second signal.

17. A method according to claim 16, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a Canonical Name (C-NAME).

18. A method according to claim 16, wherein the requested information associated with the address of the MoQ server or the MoQ relay is a DNS Service (SRV) record.

19. A method according to any of claims 11 to 18, wherein the core network entity is a Session Management Function (SMF).

20. A core network entity of a wireless communications network for communicating with a communications device, the core network entity comprisinginterface circuitry configured to transmit signals and to receive signals, anda controller configured in combination with the interface circuitry toreceive, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;determine, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; andtransmit, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server.

21. A communications device for communicating with core network entity of a wireless communications network, the communications device comprisinga transceiver configured to transmit signals and to receive signals, anda controller configured in combination with the transceiver totransmit, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;receive, from the core network entity, a second signal, the second signal including an address of a MoQ relay for the communication device to communicate with the MoQ server by the MoQ relay relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) as determined by the core network entity based on the first signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; andestablish connection with the UPF based on the address of the MoQ relay.

22. Circuitry for core network entity of a wireless communications network for communicating with a communications device, the circuitry comprisingtransceiver circuitry configured to transmit signals and to receive signals, and controller circuitry configured in combination with the transceiver circuitry to receive, from the communications device, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;determine, based on the received first signal, a User Plane Function (UPF) to serve as a MoQ relay for the communications device to communicate with the MoQ server by relaying traffic between the communications device and the MoQ server; andtransmit, to the communications device, a second signal, the second signal including an address of the MoQ relay for the communications device to establish connection with the determined UPF, wherein the address of the MoQ relay is different from an address of the MoQ server.

23. Circuity for a communications device for communicating with a core network entity of a wireless communications network, the circuitry comprisingtransceiver circuitry configured to transmit signals and to receive signals, and controller circuitry configured in combination with the transceiver circuitry to transmit, to the core network entity, a first signal, the first signal being a request for information to enable the communications device to communicate with a Media over QUIC (MoQ) server;receive, from the core network entity, a second signal, the second signal including an address of a MoQ relay for the communication device to communicate with the MoQ server by the MoQ relay relaying traffic between the communications device and the MoQ server, wherein the MoQ relay is supported by a User Plane Function (UPF) as determined by the core network entity based on the first signal, and wherein the address of the MoQ relay is different from an address of the MoQ server; andestablish connection with the UPF based on the address of the MoQ relay.

24. A computer program which, when the program is executed by a computer, cause the computer to perform the method of claim 1 or claim 11.

25. A non-transitory computer-readable storage medium storing a computer program according to claim 24.26

Images