WO2021078936A1 - Nœuds périphériques, ue et procédés associés - Google Patents

Nœuds périphériques, ue et procédés associés Download PDF

Info

Publication number
WO2021078936A1
WO2021078936A1 PCT/EP2020/079877 EP2020079877W WO2021078936A1 WO 2021078936 A1 WO2021078936 A1 WO 2021078936A1 EP 2020079877 W EP2020079877 W EP 2020079877W WO 2021078936 A1 WO2021078936 A1 WO 2021078936A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge node
location
local
dns
central
Prior art date
Application number
PCT/EP2020/079877
Other languages
English (en)
Inventor
Attila MIHÁLY
Magnus HALLENSTÅL
Maria Luisa Mas Rosique
Wenliang Xu
Jan Backman
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2021078936A1 publication Critical patent/WO2021078936A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • Embodiments herein relate to a central, a local edge node, UE and methods performed therein regarding wireless communication.
  • embodiments herein relate to handling communication such as accessing an application server, and/or managing communication, in a wireless communications network.
  • UE user equipment
  • STA mobile stations, stations
  • CN core networks
  • the RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB.
  • RBS radio base station
  • the service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node.
  • the radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.
  • DL downlink
  • UL uplink
  • a Universal Mobile Telecommunications System is a third generation telecommunications network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment.
  • WCDMA wideband code division multiple access
  • HSPA High-Speed Packet Access
  • 3GPP Third Generation Partnership Project
  • telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity.
  • 3GPP Third Generation Partnership Project
  • radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNC radio network controller
  • BSC base station controller
  • the RNCs are typically connected to one or more core networks.
  • the Evolved Packet System comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN also known as the Long-Term Evolution (LTE) radio access network
  • EPC also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network.
  • the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.
  • Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions.
  • receive-side a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
  • 5G networks architecture is defined in the new 3GPP release (Rel)-16 see [1] A key issue that is being discussed for Rel 17 relates to architectural enhancements related to Edge Computing.
  • Edge Computing is a network architecture concept that enables cloud computing capabilities and service environments to be deployed at the edge of the cellular network. It promises several benefits such as lower latency, higher bandwidth, reduced backhaul traffic and prospects for several new services.
  • TR technical report [2] is being written identifying the key issues and proposing an application architecture and related solutions. The architecture proposed in this TR is shown in Fig. 1, where the interactions between the different entities are denoted by the different reference points EDGE-1 to EDGE-7.
  • EES Edge Enabler Server
  • a functional entity resident in the Edge Hosting Environment providing services for the Edge Application Servers and Edge Enabler Clients.
  • Functionalities of Edge Enabler Server :
  • Edge Data Network Configuration Server provides supporting functions needed for the UE to connect with an Edge Enabler Server. Functionalities of Edge Data Network Configuration Server:
  • the Edge Data Network configuration information includes the following:
  • URI Uniform Resource Identifier
  • Application Client Application software resident in the UE performing the client function.
  • Edge Application Server An Application Server resident in the Edge Hosting Environment (environment providing support required for Edge Application Server's execution).
  • Edge Data Network Local Data Network(s) that supports distributed deployment of Edge Hosting Environments (where Local Data Network is an access point geographically close to a UE's point of attachment).
  • Fig. 1 shows an Application layer architecture for enabling edge applications as proposed in [2]
  • Another advantage of such a DNS-based scheme is that the communication between UE (EEC) and EES can also be DNS-based as a natural means for AS server discovery in IP networks. This, on one hand, would make the usage of Edge Configuration Server, and related EDGE-4 interface, unnecessary. On the other hand, all DNS enhancements developed to ease AS server discovery developed for CDN networks could be used also here.
  • the 3GPP network could also snoop the DNS queries to insert additional information related to UE location and network capabilities (as described in IETF RFC 6891) to assist AS discovery and selection, and it could also snoop the DNS responses to infer the location of the selected AS, based on which the 3GPP network could provide proper routing of the UE traffic to/from the Edge AS.
  • Fig. 2 depicts the 5G reference architecture as defined by 3GPP TS 23. 501 v.15.0.0.
  • the User Plane Function (UPF)
  • the UPF is the Network Function that supports the handling of user plane traffic.
  • Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5G Core Network selects a UPF close to the UE and executes the traffic steering from the UPF to the local Data Network via a N6 interface. This may be based on the UE's subscription data, UE location, the information from Application Function (AF) as defined in TS 23.501 clause 5.6.7, policy or other related traffic rules.
  • AF Application Function
  • the service or session continuity may be required based on the requirements of the service or the 5G network.
  • the 5G Core Network may expose network information and capabilities to an Edge Computing Application Function.
  • Edge computing can be supported by one or a combination of a number of enablers: User plane (re)selection: the 5G Core Network (re)selects UPF to route the user traffic to the local Data Network, TS 23.501 clause 6.3.);
  • the 5G Core Network selects the traffic to be routed to the applications in the local Data Network;
  • An Application Function may influence UPF (re)selection and traffic routing via Policy Charging Function (PCF) or Network Exposure Function (NEF), TS 23.501 clause 5.6.7;
  • PCF Policy Charging Function
  • NEF Network Exposure Function
  • 5G Core Network and Application Function to provide information to each other via NEF as described in clause 5.20 or directly ( TS 23.502 [3] clause 4.15);
  • PCF Quality of service (QoS) and Charging: PCF provides rules for QoS Control and Charging for the traffic routed to the local Data Network.
  • DNS over HTTPS is a protocol for performing remote Domain Name System (DNS) resolution via the HTTPS protocol.
  • DNS remote Domain Name System
  • a goal of the method is to increase user privacy and security by preventing eavesdropping and manipulation of DNS data by man- in-the-middle attacks by using the HTTPS protocol to encrypt the data between the DoH client and the DoH-based DNS resolver.
  • the main problem with DoH is that the EEC cannot snoop the DNS request from the UE APP, and thus the present architecture is not applicable when DoH is used.
  • the 5GC is also not able to snoop DNS messages, so implicit traffic routing to the selected AS, in the local data network, is also not possible.
  • a solution is therefore needed that avoids using EEC in UE for AS discovery and selection.
  • Another problem with the solutions in the TR is that they assume that the UE needs to select and register in the Edge data network (DN) in advance.
  • the EEC creates and maintains a UE context in the EES and also an Edge DN context in the EEC.
  • This approach is inefficient: before the Application Client actually needs to connect to the Application Server the UE connects to the Edge DN, also, the architecture may consider and store information about applications that will not be used during the session, and the UE may need to select a new Edge AS if the network conditions change.
  • This solution is also complex, as there need to be mechanisms in place to maintain the mentioned contexts in EEC and EES.
  • Edge Data Network Configuration keeps the overview of the deployed Edge Data Networks, their services and service area, and their contact information. Sharing that information between different business domains (e.g. mobile network operator (MNO) and an external Service Edge Computing Provider) may not be acceptable.
  • MNO mobile network operator
  • Service Edge Computing Provider an external Service Edge Computing Provider
  • An object herein is to provide a mechanism to handle edge services in an efficient manner in the wireless communications network.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication of the UE in a wireless communications network.
  • the UE transmits a request related to DNS resolution, to a central edge node, for AS fully qualified domain name (FQDN) together with a location of the UE or an internal user identity of the UE indicating the location.
  • the UE receives from a local edge node or the central edge node, contact information to an AS, and/or receive, from the central edge node, a hypertext transfer protocol secure (HTTPS) redirect towards the local edge node for AS discovery and selection.
  • HTTPS hypertext transfer protocol secure
  • the object is achieved, according to embodiments herein, by providing a method performed by a central edge node for handling communication of a UE in a wireless communications network.
  • the central edge node receives a request related to DNS resolution, from the UE, for AS FQDN together with a location of the UE or an internal user identity of the UE indicating the location.
  • the central edge node selects an edge node, being a local edge node, based on the location of the UE, and initiates a communication for performing at the selected local edge node an AS discovery and selection process for the UE.
  • the object is achieved, according to embodiments herein, by providing a method performed by a local edge node for handling communication of a UE in a wireless communications network.
  • the local edge node receives, from a central edge node, a request related to DNS resolution for AS FQDN together with a location of the UE or a internal user identity of the UE indicating the location.
  • the local edge node selects an AS for the UE based on the location of the UE; and provides, to the UE or the central edge node, contact information to the selected AS.
  • the object is achieved, according to embodiments herein, by providing a central edge node, a local node and UE configured to perform the methods, respectively.
  • a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method above, as performed by the edge nodes and UE, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the method above, as performed by the UE or edge nodes, respectively.
  • Embodiments herein disclose a two-level hierarchy for the EES functionality. This hierarchy may replicate for the different Edge Computing Service providers available in that PLMN:
  • the central edge node denoted as a central EES entity that typically resides outside an Edge Data Network and acts as the authoritative name server for the ASes in a certain Edge Data Network. It receives the UE DNS request first. It may then authenticate the UE and authorize if the UE is allowed to use this application as an edge application. The central edge node then infers UE location, selects an optimal local EES, i.e. the local edge node, and mediates in the UE interaction with the local EES to identify the optimal AS the UE could connect to.
  • an optimal local EES i.e. the local edge node
  • the local edge node denoted as a local EES entity that is deployed in the Edge Data Network and keeps up-to-date information with the ASes in a certain Local Data network. It is responsible for selecting a proper AS, also referred to as Edge AS, for a certain UE and providing information to enable the exchange of Application Data Traffic with the Application Server.
  • Embodiments herein may be used for on-demand local AS discovery based on UE DNS trigger, when, for example, DoH is used instead of plain DNS. It offers a more efficient and simplified architecture compared to the state-of-art.
  • the proposal includes an architecture that can be deployed on top of the 3GPP network by MNO but also by other Edge Computing Service Providers. There is minimum information that needs to be shared. Embodiments herein may further include the Edge Computing Service Provider authorization to UE to access Edge Computing services. BRIEF DESCRIPTION OF THE DRAWINGS
  • Fig. 1 shows an application architecture according to prior art
  • Fig. 2 shows an architecture according to 5G
  • Fig. 3A shows a wireless communications network according embodiments herein;
  • Fig. 3B shows the split of the EES into a Central and a Local EES
  • Fig. 4A shows a combined signalling scheme and flowchart according to embodiments herein;
  • Fig. 4B shows a flowchart depicting a method performed by a UE according to embodiments herein;
  • Fig. 4C shows a flowchart depicting a method performed by a UE according to embodiments herein;
  • Fig. 4D shows a flowchart depicting a method performed by a UE according to embodiments herein;
  • Fig. 5 shows an example flow diagram showing the proposed logic for the central edge node for AS selection
  • Fig. 6 shows an example flow diagram showing the proposed logic for the local edge node for AS selection
  • Fig. 7A shows a signalling scheme depicting some embodiments herein
  • Fig. 7B shows a signalling scheme depicting some embodiments herein;
  • Fig. 8A shows a signalling scheme depicting some embodiments herein
  • Fig. 8B shows a signalling scheme depicting some embodiments herein;
  • Fig. 9A is a block diagram depicting a central edge node according to embodiments herein;
  • Fig. 9B is a block diagram depicting a local edge node according to embodiments herein
  • Fig. 9C is a block diagram depicting a UE according to embodiments herein;
  • Fig. 10 schematically illustrates a telecommunications network connected via an intermediate network to a host computer
  • Fig. 11 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection; and Figs. 12-15 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Embodiments herein relate to wireless communications networks in general.
  • Fig. 3 is a schematic overview depicting a wireless communications network 1.
  • the wireless communications network 1 comprises one or more RANs and one or more CNs.
  • the wireless communications network 1 may use one or a number of different technologies.
  • Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN).
  • AN e.g. radio access network
  • CN core networks
  • UE is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.
  • NB-loT narrowband internet of things
  • MTC Machine Type Communication
  • D2D Device to Device
  • the wireless communications network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11, of a first radio access technology (RAT), such as NR, LTE, or similar.
  • the radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g.
  • a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the radio network node depending e.g. on the first radio access technology and terminology used.
  • gNB gNodeB
  • eNB evolved Node B
  • eNode B evolved Node B
  • NodeB a NodeB
  • a base transceiver station such as a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a
  • the radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device.
  • a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.
  • Embodiments herein disclose a two-level hierarchy for the EES functionality, wherein the wireless communications network 1 further comprises one or more network nodes such as a central edge node 15 and a local edge node 16.
  • the central edge node 15 also denoted as a central EES entity or first network node, that typically resides outside an Edge Data Network and may act as the authoritative name server for the ASes in a certain Edge Data Network. It receives the UE DNS request first, also referred to as UE application (APP) DNS request. The central edge node 15 may then authenticate the UE 10 and may authorize that the UE 10 is allowed to use this application as an edge application. The firs edge node may then infer UE location, and selects an optimal local EES, i.e. the local edge node, and mediates in the UE 10 interaction with the local EES to identify the optimal AS the UE could connect to.
  • APP UE application
  • the local edge node 16 also denoted as a local EES entity or a second network node, that may be deployed in the Edge Data Network and may keep up-to-date information with the ASes, such as an application server (AS) 17, in a Local Data network. It is responsible for selecting a proper AS for the UE 10 and providing information to enable the exchange of Application Data Traffic with the Application Server.
  • AS application server
  • Embodiments herein may be used for on-demand local AS discovery based on UE DNS trigger, for example when DoH is used instead of plain DNS. It offers a more efficient and simplified architecture compared to the state-of-art.
  • the proposal includes an architecture that can be deployed on top of the 3GPP network by a mobile network operator (MNO) but also by other Edge Computing Service Providers and there is a minimum information that needs to be shared.
  • MNO mobile network operator
  • Edge Computing Service Providers there is a minimum information that needs to be shared.
  • Fig. 3B show the split of the EES into Central and Local EES. Two interfaces are proposed:
  • the Edge Enabler Client (EEC) in the UE 10 could be omitted, or its role substantially reduced to that of a DoH client, in case when the DoH client is implemented in the UEs operating system to convert all applications’ DNS requests to DoH.
  • EEC functions are either part of the application, e.g. provided in a library in a software development kit (SDK), or are provided by the operating system (OS) of the UE (also part of the SDK). This depends on OS.
  • SDK software development kit
  • OS operating system
  • Fig. 4A is a combined signalling scheme and flowchart depicting embodiments herein.
  • the UE 10 may first generate an DNS request such as a DoH request for an application.
  • the UE 10 transmits the DNS request to the central edge node 15, i.e. the central EES.
  • the central edge node 15 may then determine location of the UE 10. Action 404. The central edge node 15 then selects the local edge node based on the location of the UE 10.
  • the central edge node 15 then transmits a DNS request to the selected local edge node 16.
  • the central edge node 15 transmits to the UE 10, a HTTPS redirect indicating the selected local edge node for AS discovery and selection.
  • the UE 10 may transmit a DNS request, such as a
  • DoH request to the local edge node based on the received HTTPS redirect.
  • the local edge node 16 selects an (optimal e.g. closest) AS for the UE based on location of the UE.
  • the local edge node 16 transmits a DNS response to the central edge node 15 indicating the selected AS 17.
  • the central edge node 15 then transmits a DNS response back to the UE 10 indicating the selected AS 17.
  • Action 407b Alternatively, the local edge node 16 transmits a DNS response to the UE indicating the selected AS 17. Action 408. The UE 10 may then use the application and thereby communicate data with the selected AS 17.
  • the UE 10 transmits a request related to DNS resolution, to the central edge node 15, for AS FQDN together with a location of the UE or an internal user identity of the UE indicating the location.
  • the transmitted request may be a DNS request or a DoH request.
  • the internal user identity may comprise a UE internet protocol (IP) address, an IP domain and/or a generic public subscription identifier (GPSI) value.
  • IP internet protocol
  • GPSI generic public subscription identifier
  • the UE 10 receives, from the central edge node 15, contact information to the AS 17, and/or, from the central edge node 15, a hypertext transfer protocol secure (HTTPS) redirect towards the local edge node 16 for AS discovery and selection.
  • HTTPS hypertext transfer protocol secure
  • the UE 10 may then transmit a request to the local edge node 16 related to DNS resolution for AS FQDN together with the location of the UE or the internal user identity of the UE indicating the location.
  • the UE 10 may receive, from the local edge node 16, a DNS over HTTPS response indicating AS to connect to.
  • the central edge node 15 receives the request related to DNS resolution, from the UE 10, for AS FQDN, together with the location of the UE or an internal user identity of the UE indicating the location.
  • the central edge node 15 may determine location of the UE based on the received request.
  • the central edge node may for example determine location by retrieving a generic public subscription identifier, GPSI, value by using a UE IP address and/or an IP domain of the UE.
  • the central edge node 15 further selects edge node, being the local edge node, based on the location of the UE 10, e.g. selects an optimal edge node in terms of closeness or proximity.
  • the central edge node 15 then initiates a communication for performing at the selected local edge node 16 an AS discovery and selection process for the UE 10.
  • the central edge node 15 may for example initiate communication by transmitting, to the UE 10, the HTTP redirect towards the local edge node for AS discovery and selection for the UE 10.
  • the central edge node 15 may for example initiate communication by transmitting to the selected local edge node 16, a request related to DNS resolution for AS FQDN with the location of the UE or the internal user identity of the UE indicating the location.
  • the central edge node 15 may influence routing and/or QoS within the wireless communications network for a selected AS.
  • the local edge node 16 receives, from the central edge node 15, the request related to DNS resolution for AS FQDN together with a location of the UE or a internal user identity of the UE indicating the location.
  • the received request may be a DNS request from the central edge node 15.
  • the local edge node 16 selects the AS for the UE based on the location of the UE 10.
  • the local edge node 16 may influence routing and/or QoS within the wireless communications network for the selected AS.
  • the local edge node 16 provides, to the UE 10 or the central edge node 15, contact information to the selected AS.
  • the local edge node may transmit a DNS response to the central edge node or a DoH response to the UE, indicating an AS IP address.
  • the central edge node 15 may receive the DNS request for AS fully qualified domain name (FQDN).
  • the central EES may be a DoH server, i.e. , the server terminating the HTTPS connection, that is configured in the UE APP DoH client or an authoritative DNS name server the 3 rd party DoH server forwards the UE request to. In the first case it provides a standard HTTPS interface towards the UE 10, in the second case it provides a standard DNS interface towards the recursive DoH server.
  • the central edge node 15 may authenticate and authorize UE 10. This may be based on information received from the Edge configuration server through Edge 6 interface
  • the central edge node 15 may infer or determine location of the UE 10.
  • the central edge node 15 selects an optimal edge node such as the local edge node 16 based on a criterion e.g. the location of the UE 10. This may be based on selection criteria received from Edge configuration Server and UE location information received in Step 3. The selection itself could be based on Local DN/EES placement received from Edge configuration.
  • the central edge node 15 may then mediate or initiate communication with the local edge node 16 related to AS discovery and selection. This could be based on DNS communication or HTTPS redirect, as detailed in Sections below.
  • the local edge node 16 i.e. a local EES entity, is responsible of registering the different AS entities deployed in the Edge Data network through the EDGE-3 interface. (Note that EDGE-3 interface also allows for UE location exposure for the ASes serving them.) Based on this information, it performs AS selection for a UE request as described in Fig. 6:
  • the local edge node 16 may receive a DNS request for AS fully qualified domain name (FQDN) together with requesting UE location. More alternatives exist to receive the DNS request.
  • FQDN fully qualified domain name
  • the local edge node 16 selects optimal edge AS for the UE location.
  • Edge Network could e.g. be a multi-site, and therefore certain AS could be more optimal to serve a certain UE location than another.
  • the result of the selection is the contact information such as Edge AS contact information, for example, an IP address.
  • the local edge node 16 may provide provision for traffic routing towards the selected AS.
  • the Edge AS election may be paired with the routing of the application traffic in the Mobile Network.
  • the Local ESS may act as an
  • UPF User Plane Function
  • NEF Network-Enhanced Function
  • the local edge node 16 may influence the QoS treatment.
  • the Local EES may act as an Application Function to influence the QoS treatment for the given traffic.
  • the local edge node 16 responds with the selected AS contract information such as the IP address e.g. a DNS response to the request in 601 with the selected AS IP address.
  • the selected AS contract information such as the IP address e.g. a DNS response to the request in 601 with the selected AS IP address.
  • Figure 6 shows an example flow diagram showing the proposed logic for the local EES entity for AS selection.
  • the Local EEC influence on traffic routing and QoS treatment may be performed using the EES-X interface.
  • the Local EES can also have an EDGE-2 interface towards the 3GPP network.
  • Fig. 7 shows an example sequence diagram for AS discovery using DNS
  • UE 10 transmits a DoH request for AS FQDN.
  • the central edge node 15 may then receive an indication of the UE location.
  • the central edge node 15 selects the local edge node 16.
  • the central edge node 15 may then transmit a DNS request to the selected local edge node 16.
  • the local edge node 16 selects AS based on e.g. location of the UE 10.
  • the local edge node 16 and /or the central edge node 15 may then influence routing within the wireless communications network. 7. The local edge node 16 and /or the central edge node 15 may then influence QoS within the wireless communications network.
  • the local edge node 16 then transmits, to the central edge node 15, a response e.g. DNS response indicating address of the selected AS.
  • the central edge node 15 furthermore sends, to the UE, a DoH response indication e.g. the AS IP address.
  • the data traffic may be up and running.
  • Example edge AS discovery and selection using HTTP redirect This case assumes that the central edge node 15 acts as a DoH Server.
  • the alternative (DNS resolver) is not possible due to the redirect (Step 4) in Fig. 7B.
  • the central edge node 15 may get the UE location, for example receive an indication of the UE location, e.g. value or index value.
  • the central edge node 15 selects the local edge node 16.
  • the central edge node 15 furthermore transmits a HTTP redirect for the selected edged node.
  • UE 10 transmits a DoH request for AS FQDN.
  • the local edge node 16 selects AS based on e.g. location of the UE 10.
  • the local edge node 16 and /or the central edge node 15 may then influence routing within the wireless communications network.
  • the local edge node 16 and /or the central edge node 15 may then influence QoS within the wireless communications network.
  • the local edge node 16 furthermore sends a DoH response indication e.g. the AS IP address.
  • the data traffic may be up and running.
  • Embodiments herein enable applying cloud-native design principles for both the central and local edge node as well as the ASes. Furthermore, it is herein disclosed a system and method for DoH based on-demand Edge AS discovery and selection. It is based on splitting EES to central and a local EES components that may also interact via DNS.
  • Embodiments herein include User identities (UE IP address, IP domain, GPSI) in the requests such as DoH requests.
  • the GPSI may include Mobile Station International Subscriber Directory Number (MSISDN) or external identifier for the UE.
  • MSISDN Mobile Station International Subscriber Directory Number
  • the new Service by the Network Exposure Framework can be used to obtain at the central edge node one from the UE IP address and IP domain.
  • Fig. 8A shows a flowchart according to embodiments herein of an iterative DoH.
  • the "ipDomain" attribute is helpful in the following scenario.
  • SMF/UPF(s) that allocate Ipv4 IP addresses out of the same private address range to UE PDU Sessions.
  • the same IP address can thus be allocated to UE PDU sessions served by SMF/UPF(s) in different address domains.
  • the UE IP address is thus not sufficient for the session binding in the PCF/BSF.
  • An AF can serve UEs in different IP address domains, either by having direct IP interfaces to those domains, or by having interconnections via NATs in the user plane between the UPF and the AF.
  • UE resolves the central EES address (either locally or using the DNS)
  • the central EES after receiving the DoH request, if GPSI is not received, may query 3GPP network to retrieve the GPSI by using the UE IP address and optionally the IP domain:
  • the central EES then retrieves the UE location by using GPSI via NEF or using UE IP address and optionally IP domain via PCF and finds the closest EES for that location (local EES). e) The central EES responds the UE 10 with a DoH redirection towards the local EES.
  • the UE 10 send the DoH request to the local EES.
  • the local EES determines the local AS address and responds the UE.
  • the local EES further triggers traffic influence and QoS for the UE, so that traffic steering and QoS are according to the AS selection.
  • UE starts application traffic that UL-CL UPF steers to the edge AS.
  • Fig. 8B shows a flowchart according to Recursive DoH. The steps are omitted here which is similar with Fig. 8A with the differences that the central EES handles AS discovery via interaction with the local EES. Such interaction could be any protocol (e.g. HTTP or DNS).
  • the central EES sends a request to the local EES e.g. a get edge application server (EAS) address request such as a DNS request.
  • the local EES returns local EAS and sends a response such as a get EAS address response e.g. a DNS response to the central EES.
  • the central EES sends DoH response with the EAS address to the UE 10, and influences routing/QoS.
  • the UE 10 may then communicate with the EAS.
  • EAS edge application server
  • DoH Request is sent by UE to a central EES acting as DoH server. It redirects the request to the right local EES, and that one resolves the DoH request.
  • the DOH Request is sent by UE to a central EES acting as DoH server. It terminates the HTTPS, processes the DoH request and uses some other internal protocol (e.g. a DNS based protocol) to interact with the local EES to obtain the Edge AS address.
  • a DNS based protocol e.g. a DNS based protocol
  • EES central and/or local acting as an Application Functions (AF) interacts with the 3GPP Network and uses the 3GPP application programming interfaces (API) for Network Exposure functionality.
  • API application programming interfaces
  • the AF needs to include a User Identity that the Network exposure recognizes and translates (if needed) into the internal user identity that the 3GPP Network Functions recognize, to enforce the request.
  • DoH is basically an encapsulation of DNS and does not carry such User Identity.
  • the source IP address in the DoH request cannot be always used as User Identity since it may be NAT-ted by the 3GPP Network. Embodiments herein solve this.
  • Fig. 9a is a block diagram depicting the central edge node 15 for handling communication of the UE, e.g. selecting local edge node 16, in the wireless communications network 1 according to embodiments herein.
  • the central edge node 15 may comprise processing circuitry 901, e.g. one or more processors, configured to perform the methods herein.
  • processing circuitry 901 e.g. one or more processors, configured to perform the methods herein.
  • the central edge node may comprise a selecting unit 902.
  • the central edge node 15, the processing circuitry 901, and/or the selecting unit 902 is configured to receive the request related to DNS resolution, from the UE 10, for AS FQDN, together with the location of the UE or the internal user identity of the UE indicating the location, and to select the edge node, being the local edge node, based on the location of the UE. For example, configured to select optimal edge node based on location of the UE.
  • the central edge node may comprise an initiating unit 903.
  • the central edge node 15, the processing circuitry 901, and/or the initiating unit 903 is configured to initiate the communication for performing at the selected local edge node the AS discovery and selection process for the UE. For example, to initiate communication with the local edge node 16 related to AS discovery and selection.
  • the central edge node 15, the processing circuitry 901, and/or the initiating unit 903 may be configured to initiate communication by transmitting, to the UE 10, a HTTPS redirect towards the local edge node for AS discovery and selection for the UE.
  • the central edge node 15, the processing circuitry 901, and/or the initiating unit 903 may be configured to initiate communication by transmitting to the selected local edge node, a request related to DNS resolution for AS FQDN with the location of the UE or the internal user identity of the UE indicating the location.
  • the central edge node 15, the processing circuitry 901, and/or the selecting unit 902 may be configured to determine the location based on the received request.
  • the central edge node 15, the processing circuitry 901, and/or the selecting unit 902 may be configured to determine the location by retrieving a GPSI value by using a UE IP address and/or an IP domain of the UE 10.
  • the central edge node 15, the processing circuitry 901, and/or the initiating unit 903 may be configured to influence routing and/or QoS within the wireless communications network for a selected AS
  • the central edge node 15 further comprises a memory 905.
  • the memory 805 comprises one or more units to be used to store data on, such as data packets, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the central edge node 15 may comprise a communication interface such as comprising a transmitter, a receiver and/or a transceiver.
  • the methods according to the embodiments described herein for the central edge node 15 are respectively implemented by means of e.g. a computer program product 906 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the central edge node 15.
  • the computer program product 906 may be stored on a computer-readable storage medium 907, e g. a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 907, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the central edge node 15.
  • the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.
  • embodiments herein may disclose a central edge node 15 for handling communication in a wireless communications network, wherein the central edge node 15 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said central edge node 15 is operative to perform any of the methods herein.
  • Fig. 9b is a block diagram depicting the local edge node 16 for handling communication of the UE 10 in the wireless communications network 1 according to embodiments herein.
  • the local edge node 16 may comprise processing circuitry 1001, e.g. one or more processors, configured to perform the methods herein.
  • the local edge node 16 may comprise a receiving unit 1002.
  • the local edge node 16, the processing circuitry 1001 and/or the receiving unit 1002 is configured to receive, from the central edge node, a request related to DNS resolution for AS FQDN, together with the location of the UE or the internal user identity of the UE indicating the location.
  • the received request may be a DNS request from the central edge node.
  • the local edge node 16 may comprise a selecting unit 1003.
  • the local edge node 16, the processing circuitry 1001 and/or the selecting unit 1003 is configured to select an AS for the UE based on the location of the UE, for example, to select optimal edge AS for the UE location.
  • the local edge node 16 may comprise a providing unit 1004, e.g. a transmitter.
  • the local edge node 16, the processing circuitry 1001 and/or the providing unit 1003 is configured to provide, to the UE 10 or the central edge node 15, contact information to the selected AS.
  • the processing circuitry 1001 and/or the providing unit 1003 may be configured to influence routing and/or QoS within the wireless communications network for the selected AS.
  • the local edge node, the processing circuitry 1001 and/or the providing unit 1003 may be configured to transmit the DNS response to the central edge node or the DoH response to the UE, indicating an AS IP address.
  • the local edge node 16 may comprise a memory 1006.
  • the memory 906 comprises one or more units to be used to store data on, such as data packets, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the local edge node 16 may comprise a communication interface such as comprising a transmitter, a receiver and/or a transceiver.
  • the methods according to the embodiments described herein for the local edge node 16 are respectively implemented by means of e.g. a computer program product 1007 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the local edge node 16.
  • the computer program product 1007 may be stored on a computer-readable storage medium 1008, e.g. a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 1008, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the local edge node 16.
  • the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium.
  • embodiments herein may disclose a local edge node 16 for handling communication in a wireless communications network, wherein the local edge node 16 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said local edge node 16 is operative to perform any of the methods herein.
  • Fig. 9c is a block diagram depicting the UE 10 for handling communication of the UE 10 in the wireless communications network 1 according to embodiments herein.
  • the UE 10 may comprise processing circuitry 1101, e.g. one or more processors, configured to perform the methods herein.
  • processing circuitry 110 e.g. one or more processors, configured to perform the methods herein.
  • the UE 10 may comprise a transmitting unit 1102.
  • the UE 10, the processing circuitry 1101 and/or the transmitting unit 1102 may be configured to transmit the request related to DNS resolution, to the central edge node 15, for AS FQDN, together with the location of the UE or an internal user identity of the UE indicating the location. For example, transmit a DNS request to the local edge node or the central edge node for AS FQDN together with UE location.
  • the transmitted request may be a DNS request or a DoH request.
  • the internal user identity may comprise a UE IP address, an IP domain and/or a GPSI value.
  • the UE 10 may comprise a receiving unit 1103.
  • the UE 10, the processing circuitry 1101 and/or the receiving unit 1103 is configured to receive, from the local edge node or the central edge node, contact information to an AS, and/or, from the central edge node, receive the HTTPS redirect towards the local edge node for AS discovery and selection.
  • the UE 10, the processing circuitry 1101 and/or the receiving unit 1103 may be configured to receive a DoH response indicating AS to connect to.
  • the UE 10 may comprise a memory 1106.
  • the memory 1106 comprises one or more units to be used to store data on, such as data packets, events and applications to perform the methods disclosed herein when being executed, and similar.
  • the UE 10 may comprise a communication interface such as comprising a transmitter, a receiver and/or a transceiver.
  • the methods according to the embodiments described herein for the UE 10 are respectively implemented by means of e.g. a computer program product 1107 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer program product 1107 may be stored on a computer-readable storage medium 1108, e g. a disc, a universal serial bus (USB) stick or similar.
  • the computer-readable storage medium 1108, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10.
  • the computer-readable storage medium may be a transitory or a non-transitory computer- readable storage medium.
  • embodiments herein may disclose a UE 10 for handling communication in a wireless communications network, wherein the UE 10 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE 10 is operative to perform any of the methods herein.
  • the object is achieved, according to embodiments herein, by providing a method performed by a central edge node for handling communication of a UE.
  • the central edge node selects optimal edge node based on location of the UE, and initiates communication with selected edge node related to AS discovery and selection.
  • the object is achieved, according to embodiments herein, by providing a method performed by a local edge node for handling communication of a UE.
  • the local edge node may receive a DNS request, from the UE or a central edge node, for AS fully qualified domain name (FQDN) e.g. together with UE location.
  • the local edge node selects optimal edge AS for the UE location.
  • the local edge node provides to the UE 10 or the central edge node contact information to the selected AS.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication of the UE.
  • the UE transmits a DNS request to a local edge node or a central edge node for AS fully qualified domain name (FQDN) together e.g. with UE location.
  • the UE 10 receives contact information to the AS, and/or, from the central edge node, receive HTTPS redirect towards the local edge node.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication of the UE.
  • the UE transmits a request related to domain name, such as a DNS or DoH request, to a local edge node or a central edge node for AS fully qualified domain name (FQDN) together with a user identity of the UE.
  • the User Identity may be required by a API.
  • the user identity may be a UE IP address and optionally an IP domain and a GPSI value.
  • the UE may receive contact information to an AS, and/or, from the central edge node, receive HTTPS redirect towards the local edge node.
  • the object is achieved, according to embodiments herein, by providing a method performed by a central edge node such as a EES for handling communication of a UE.
  • the central edge node receives a request related to domain name from the UE for AS fully qualified domain name (FQDN) together with a user identity of the UE.
  • the central edge node gets location of a local edge node for a location of the UE based on the user identity of the UE e.g. selects optimal edge node based on location and identity of the UE, and may initiate communication with selected edge node related to AS discovery and selection.
  • This allows the central edge node to interact with the 3GPP network to solve the Edge AS Discovery and Selection when the UE request is based on DoH. It also allows the Application Architecture to request QoS and to influence the 3GPP connectivity and traffic steering to best match that Edge AS Selection.
  • the central edge node may get GPSI if not received from the UE.
  • the object is achieved, according to embodiments herein, by providing a method performed by a local edge node for handling communication of a UE.
  • the local edge node may receive a request, from the UE (or a central edge node), for AS fully qualified domain name (FQDN) together with user identity of the UE.
  • the User Identity may be required by an API.
  • the user identity may be a UE IP address and optionally an IP domain and a GPSI value.
  • the local edge node selects an optimal edge AS for the UE (based on location and ID).
  • the local edge node provides to the UE 10 or the central edge node contact information to the selected AS.
  • the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication of the UE.
  • the UE transmits a request related to domain name, such as a DNS or DoH request, to a local edge node or a central edge node for AS fully qualified domain name (FQDN) together with a user identity of the UE.
  • the User Identity may be required by a application programming interface (API).
  • the user identity may be a UE IP address and optionally an IP domain and a GPSI value.
  • the UE may receive contact information to an AS, and/or, from the central edge node, receive HTTP redirect towards the local edge node.
  • the object is achieved, according to embodiments herein, by providing a method performed by a central edge node such as a EES for handling communication of a UE.
  • the central edge node receives a request related to domain name from the UE for AS fully qualified domain name (FQDN) together with a user identity of the UE.
  • the central edge node gets location of a local edge node for a location of the UE based on the user identity of the UE e.g. selects optimal edge node based on location and identity of the UE, and may initiate communication with selected edge node related to AS discovery and selection.
  • This allows the central edge node to interact with the 3GPP network to solve the Edge AS Discovery and Selection when the UE request is based on DoH. It also allows the Application Architecture to request QoS and to influence the 3GPP connectivity and traffic steering to best match that Edge AS Selection.
  • the central edge node may get GPSI if not received from the UE.
  • the object is achieved, according to embodiments herein, by providing a method performed by a local edge node for handling communication of a UE.
  • the local edge node may receive a request, from the UE (or a central edge node), for AS fully qualified domain name (FQDN) together with user identity of the UE.
  • the User Identity may be required by a API.
  • the user identity may be a UE IP address and optionally an IP domain and a GPSI value.
  • the local edge node selects an optimal edge AS for the UE (based on location and ID).
  • the local edge node provides to the UE 10 or the central edge node contact information to the selected AS.
  • radio network node can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node.
  • network nodes are NodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.
  • MCG Master cell group
  • SCG Secondary cell group
  • MSR multi-standard radio
  • wireless device or user equipment refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system.
  • UE refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system.
  • Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.
  • D2D device to device
  • ProSe UE proximity capable UE
  • M2M machine to machine
  • Tablet tablet
  • smart phone smart phone
  • laptop embedded equipped (LEE) laptop mounted equipment
  • LME laptop mounted equipment
  • Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wdeband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • signals e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wdeband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • ASIC application-specific integrated circuit
  • Fig. 10 shows a Telecommunications network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunications network 3210, such as a 3GPP-type cellular network, which comprises access network 3211, such as a radio access network, and core network 3214.
  • Access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 above, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to core network 3214 over a wired or wireless connection 3215.
  • a first UE 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example being examples of the UE 10 above, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • Telecommunications network 3210 is itself connected to host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 3221 and 3222 between telecommunications network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230 or may go via an optional intermediate network 3220.
  • Intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 3220, if any, may be a backbone network or the Internet; in particular, intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Fig. 10 as a whole enables connectivity between the connected UEs 3291, 3292 and host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • Host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via OTT connection 3250, using access network 3211, core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 3250 may be transparent in the sense that the participating communication devices through which OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • Fig. 11 shows a host computer communicating via a base station and with a user equipment over a partially wireless connection in accordance with some embodiments
  • host computer 3310 comprises hardware 3315 including communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 3300.
  • Host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 3310 further comprises software 3311, which is stored in or accessible by host computer 3310 and executable by processing circuitry 3318.
  • Software 3311 includes host application 3312.
  • Host application 3312 may be operable to provide a service to a remote user, such as UE 3330 connecting via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the remote user, host application 3312 may provide user data which is transmitted using OTT connection 3350.
  • Communication system 3300 further includes base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with host computer 3310 and with UE 3330.
  • Hardware 3325 may include communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 3300, as well as radio interface 3327 for setting up and maintaining at least wireless connection 3370 with UE 3330 located in a coverage area (not shown in Fig. 11) served by base station 3320.
  • Communication interface 3326 may be configured to facilitate connection 3360 to host computer 3310. Connection 3360 may be direct or it may pass through a core network (not shown in Fig. 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 3325 of base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • Communication system 3300 further includes UE 3330 already referred to. Its hardware 3333 may include radio interface 3337 configured to set up and maintain wireless connection 3370 with a base station serving a coverage area in which UE 3330 is currently located. Hardware 3333 of UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 3330 further comprises software 3331, which is stored in or accessible by UE 3330 and executable by processing circuitry 3338.
  • Software 3331 includes client application 3332.
  • Client application 3332 may be operable to provide a service to a human or non-human user via UE 3330, with the support of host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via OTT connection 3350 terminating at UE 3330 and host computer 3310.
  • client application 3332 may receive request data from host application 3312 and provide user data in response to the request data.
  • OTT connection 3350 may transfer both the request data and the user data.
  • Client application 3332 may interact with the user to generate the user data that it provides.
  • host computer 3310, base station 3320 and UE 3330 illustrated in Fig. 11 may be similar or identical to host computer 3230, one of base stations 3212a, 3212b, 3212c and one of UEs 3291, 3292 of Fig. 10, respectively.
  • the inner workings of these entities may be as shown in Fig. 11 and independently, the surrounding network topology may be that of Fig. 10.
  • OTT connection 3350 has been drawn abstractly to illustrate the communication between host computer 3310 and UE 3330 via base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 3330 or from the service provider operating host computer 3310, or both. While OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 3370 between UE 3330 and base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 3330 using OTT connection 3350, in which wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments make it possible to enhance the CWS maintenance scheme for PUCCH transmission and/or a better fairness of channel accesses may be achieved.
  • Embodiments herein may e.g. enable the UE to more efficiently control communication by configuring the central and local edge nodes according to embodiments herein.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 3350 may be implemented in software 3311 and hardware 3315 of host computer 3310 or in software 3331 and hardware 3333 of UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 3320, and it may be unknown or imperceptible to base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 3310’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 3311 and 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig. 12 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Fig. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Fig.
  • step 3410 the host computer provides user data.
  • substep 3411 (which may be optional) of step 3410, the host computer provides the user data by executing a host application.
  • step 3420 the host computer initiates a transmission carrying the user data to the UE.
  • step 3430 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 3440 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
  • Fig. 13 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Fig. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Fig.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 3530 the UE receives the user data carried in the transmission.
  • Fig. 14 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Fig. 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Fig.
  • step 3610 the UE receives input data provided by the host computer. Additionally or alternatively, in step 3620, the UE provides user data. In substep 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application. In substep 3611 (which may be optional) of step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 3630 (which may be optional), transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Fig. 15 show methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Fig. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Fig. 10 and Fig. 11. For simplicity of the present disclosure, only drawing references to Fig. 15 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 3730 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • AUL Autonomous uplink BLER Block error rate BWP Bandwidth Part CAPC Channel access priority class
  • CBG Code block group CCA Clear channel assessment CO Channel occupancy COT Channel occupancy time
  • CWS Contention window size DL Downlink ED Energy detection eNB 4G base station gNB 5G base station HARQ Hybrid automatic repeat request IS In synch
  • MCOT Maximum channel occupancy time
  • PCell Primary cell
  • PCI Physical cell identity
  • PDCCH A downlink control channel
  • PDU Protocol data unit PHICH Physical channel Hybrid ARQ Indicator Channel
  • PLMN Public land mobile network
  • PSCell Primary SCG cell PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QCI QoS class identifier QoS Quality of service RAT Radio access technology
  • RLF Radio link failure
  • RLM Radio link monitoring
  • RLC Radio link control
  • RRC Radio resource control RS Reference signal
  • SCG Secondary cell group SDU Service data unit SMTC SSB — based measurement timing configuration
  • SPS Semi persistent scheduling TTI Transmission time interval
  • This pCR proposes a solution where the discovery of the optimal Edge Aplication server is done on a per need basis, that is at the moment the Application Client requires it.
  • the UE connects to the Edge DN only when the Edge DN applications servers are going to be used, and the Edge Application Server discovery can take into account the latest network status.
  • Kls #2 & #8 “Edge Data Network discovery and registration” and “Edge Data Network Selection”. They are Not Applicable. It is the optimal Edge Application Server that is selected. There is no Edge data network discovery and registration procedure as such that need to take place outside the actual Edge Application Server selection.
  • Kl #10 “Dynamic availability”. Does not apply since it is the network (5GC, EEC, and actual AS) that handles this.
  • Kl#1 “Service provisioning and configuration”.
  • Kl #4 Edge Application Server discovery
  • Kl #6 Edge Computing Service authorization
  • Kl #7 “Flexible deployment”
  • Kl#13 Provision of QoS information of the Edge Application Server For the solution to be solution, the selection of the Edge Application Server needs to be paired with the 3GPP 5GC connectivity and the steering of the traffic of that application. This aspect has also been included in this pCR.
  • This solution addresses Key Issues #1,#4, #6, #7 #13.
  • the key characteristics of this solution is that the Edge enabling server does not keep any registration state of the UE, thus no need to solve Kl #2.
  • the EDGE 4 as defined in the architecture does not apply. It is also assumed that it is the network side of the Edge Enabling Application Architecture that assigns a certain application server for a UE, and thus the UE does not need to do any selection among application servers, by this Kl #8 is not needed.
  • the user downloads an edge data network application. From the user’s perspective, this is like any other app.
  • the application itself contains necessary configuration data to run in an edge data network.
  • the typical case for this model is that the Edge Data Network service is provided over the Internet DNN and slice.
  • the UE is a specific device for edge data network services. Since it is a special device, it may already have the necessary application software and associated configurations, or the UE is configured to download the application software and associated configurations from a pre-configured site.
  • the typical case for this model is that the Edge Data Network service is provided over a dedicated DNN and slice.
  • URSP Rules in 5GC is used to configure the UE’s usage of DNNs and slices.
  • EEC functions are either part of the application (e.g. provided in a library in an SDK) or are provided by the operating system of the UE (also part of the SDK). This depends on OS.
  • Kl #7 is solved since each application will be tied to a certain edge data network.
  • the UE has the edge application SW according to 7.x.1.1 Since the application SWand the OS in the UE act as the EEC and the internals of the UE is not assumed to be standardized, the flow below uses the term EEC from the architecture, but EEC is not really a separate thing. The interplay between application and OS to realize the EEC is a UE internal matter and is not to be standardized in 3GPP..
  • An Edge Application Server deployed in the Edge Hosting environement either registers in the EES (Key Issue #3) using for example, solution #12, where the solution includes Edge Enabler Server authorization check to verify whether the Edge Application Server has the proper privileges to register as part of the priocess.
  • the EES is provitioned with the ASes by means of O&M. The latter has no impact on “existing” cloud applications
  • the AS is identified by a FQDN, the AS- FQDN.
  • the EEC does a discovery of an AS over EDGE-1 by sending a discovery request to the EES with the AS-FQDN as query parameter. There are examples how this is done in clause 7.X.1.2.1.
  • the EES authenticates and authorizes the UE for this application.
  • uplink classifier UL-CL
  • IPv6 multihoming IPv6 multihoming
  • the IP address may not be used to determine the Edge Application Server closest to the UE, this mean that the EES needs to get the UE location from the 5GC via e.g. NEF or PCF as per TS 23.502.
  • EES may initiate establishment of a QoS flow for this application as per TS 23.502. The EES may have gotten the QoS information when AS registers to EES
  • the UE may initiate a QoS flow establishment (see step 4)
  • the application/OS uses a HTTPS protocol (e.g. DNS over HTTPS) to discover the AS by using the AS-FQDN as a query parameter.
  • HTTPS protocol e.g. DNS over HTTPS
  • a HTTPS connection is set up to the EES.
  • the EES authenticates the UE and authorizes if UE is allowed to use this application as an edge application. How to authenticate (what client credentials to use) is an SA3 issue. There are several ways how route the HTTPS connection to the EES:
  • the EES has an anycast address known by the application/OS in the UE.
  • the IP network routes the request to the closest EES.
  • the EES has a FQDN, the EES-FQDN.
  • the DNS in the 5GC has knowledge of the location of the UE and returns to the UE the address of the local EES.
  • the EES has an EES-FQDN.
  • the EES-FQDN is resolved to any EES. This EES queries the location of the UE, and then:
  • the EES may have the address of the AS for the UE location
  • the EES may use HTTP re-direct to an EES that can respond with the address of the AS in the location of the UE.
  • the EES may use normal DNS to resolve the AS-FQDN. DNS is sent towards and EES that can respond with the address of the AS, using a pseudo UE address representing the UE location. Finally, it answers back to the UE using HTTPs with the address of the AS.
  • the EES may resolve the request and answer back with the AS for the UE Location
  • the EES may forward the request to the EES that can resolve it for the UE location
  • the EES cvan forwards it to the normal DNS Hierarchy fro nont-edge applications.
  • the EES authenticates the UE and authorizes if UE is allowed to use this application as an edge application. Since 5GC gives the UE an IP address and the connection between EES and UPF is secure, the EES can use the IP address to authenticate and authorize the UE. The EES can get location of the UE and directly query the site DNS for the address of the AS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne, par exemple, un procédé exécuté par un équipement utilisateur, UE, pour gérer la communication de l'UE dans un réseau de communication sans fil. L'UE transmet une requête relative à la résolution DNS, à un nœud périphérique central, pour AS FQDN, conjointement avec un emplacement de l'UE ou une identité utilisateur interne de l'UE indiquant l'emplacement. L'UE reçoit en outre, du nœud périphérique local ou du nœud périphérique central, des informations de contact à un AS, et/ou, à partir du nœud périphérique central, la réception d'une redirection HTTPS vers le nœud périphérique local pour la découverte et la sélection d'AS.
PCT/EP2020/079877 2019-10-23 2020-10-23 Nœuds périphériques, ue et procédés associés WO2021078936A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962924729P 2019-10-23 2019-10-23
US62/924,729 2019-10-23
CN2019116746 2019-11-08
CNPCT/CN2019/116746 2019-11-08

Publications (1)

Publication Number Publication Date
WO2021078936A1 true WO2021078936A1 (fr) 2021-04-29

Family

ID=73020201

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/079877 WO2021078936A1 (fr) 2019-10-23 2020-10-23 Nœuds périphériques, ue et procédés associés

Country Status (1)

Country Link
WO (1) WO2021078936A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113784371A (zh) * 2021-07-31 2021-12-10 华为技术有限公司 通信方法和装置
US20220255998A1 (en) * 2021-02-05 2022-08-11 Samsung Electronics Co., Ltd. Electronic device for performing edge computing service and a method for the same
WO2022237670A1 (fr) * 2021-05-14 2022-11-17 贵州白山云科技股份有限公司 Procédé et appareil de planification de nœud périphérique 5g, et support et dispositif
WO2023019381A1 (fr) * 2021-08-16 2023-02-23 Qualcomm Incorporated Interface de programmation d'application (api) d'alignement de liaison montante pour des applications basse puissance à faible latence
WO2023082856A1 (fr) * 2021-11-09 2023-05-19 Telefonaktiebolaget Lm Ericsson (Publ) Influence du trafic pour la sélection d'eas initial
WO2023123075A1 (fr) * 2021-12-29 2023-07-06 华为技术有限公司 Procédé et appareil de commande d'échange de données

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2810477A1 (fr) * 2012-01-31 2014-12-10 Telefonaktiebolaget L M Ericsson (publ) Sélection de serveur dans un réseau de communication relativement à un usager mobile

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2810477A1 (fr) * 2012-01-31 2014-12-10 Telefonaktiebolaget L M Ericsson (publ) Sélection de serveur dans un réseau de communication relativement à un usager mobile

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"Procedures for the 5G System", 3GPP TS 23.502
"Recursive DoH", 4 November 2019 (2019-11-04), XP051813182, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG6_MissionCritical/TSGS6_034_Reno/docs/S6-192117.zip pCR_Pictures v2.1.pptx> [retrieved on 20191104] *
"Study on application architecture for enabling Edge Applications", 3GPP TR 23.758
"System Architecture for the 5G System (5GS", 3GPP TS 23.501
ERICSSON: "Solution to KI#1, DNS over HTTP", vol. SA WG2, no. Incheon, Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), XP051842304, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_136AH_Incheon/Docs/S2-2000197.zip S2-2000197_pCR DoH solution.docx> [retrieved on 20200107] *
FUTUREWEI: "Architectural requirements and assumptions for the study on enhanced Edge Computing (FS_enh_EC)", vol. SA WG2, no. Split Croatia; 20191014 - 20191018, 4 October 2019 (2019-10-04), XP051801524, Retrieved from the Internet <URL:https://ftp.3gpp.org/Meetings_3GPP_SYNC/SA2/Docs/S2-1909322.zip S2-1909322_FS_enh_EC_assumption-V3_cl.doc> [retrieved on 20191004] *
SAMSUNG ET AL: "Edge Computing Deployment Scenarios", vol. SA WG6, no. Roma, Italia; 20190708 - 20190712, 12 July 2019 (2019-07-12), XP051758084, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG6_MissionCritical/TSGS6_032_Roma/docs/S6-191552.zip> [retrieved on 20190712] *
SAMSUNG: "Discussion on Edge Application Discovery", vol. SA WG6, no. Roma, Italia; 20190708 - 20190712, 5 July 2019 (2019-07-05), XP051757916, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG6_MissionCritical/TSGS6_032_Roma/docs/S6-191354.zip> [retrieved on 20190705] *
SAMSUNG: "New key issue proposal for Edge Application Server Discovery", vol. SA WG2, no. Split Croatia; 20191014 - 20191018, 4 October 2019 (2019-10-04), XP051801887, Retrieved from the Internet <URL:https://ftp.3gpp.org/Meetings_3GPP_SYNC/SA2/Docs/S2-1909691.zip S2-1909691_FS_enh_EC_key issue for application server discovery.docx> [retrieved on 20191004] *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220255998A1 (en) * 2021-02-05 2022-08-11 Samsung Electronics Co., Ltd. Electronic device for performing edge computing service and a method for the same
US11743342B2 (en) * 2021-02-05 2023-08-29 Samsung Electronics Co., Ltd. Electronic device for performing edge computing service and a method for the same
WO2022237670A1 (fr) * 2021-05-14 2022-11-17 贵州白山云科技股份有限公司 Procédé et appareil de planification de nœud périphérique 5g, et support et dispositif
CN113784371A (zh) * 2021-07-31 2021-12-10 华为技术有限公司 通信方法和装置
WO2023019381A1 (fr) * 2021-08-16 2023-02-23 Qualcomm Incorporated Interface de programmation d'application (api) d'alignement de liaison montante pour des applications basse puissance à faible latence
WO2023082856A1 (fr) * 2021-11-09 2023-05-19 Telefonaktiebolaget Lm Ericsson (Publ) Influence du trafic pour la sélection d'eas initial
WO2023123075A1 (fr) * 2021-12-29 2023-07-06 华为技术有限公司 Procédé et appareil de commande d'échange de données

Similar Documents

Publication Publication Date Title
US11784861B2 (en) Channel access related enhancements to New Radio Unlicensed (NR-U)
US20210168779A1 (en) Default pdsch beam setting and pdcch prioritization for multi panel reception
WO2021078936A1 (fr) Nœuds périphériques, ue et procédés associés
US11902963B2 (en) Coverage enhancement for physical uplink control channel transmissions in new radio
US20100103857A1 (en) Cell relay network attachment procedures
WO2022005917A1 (fr) Améliorations de réseau local sans fil pour une division de commutation de direction de trafic d&#39;accès
WO2022005918A1 (fr) Règles de répartition de trafic sensibles au ran et mesures de ran pour commutation et division améliorées d&#39;orientation de trafic d&#39;accès
US11716308B2 (en) Application triggered setup of distributed anchor for edge computing
EP3970414B1 (fr) Noeud de réseau et procédé mis en oeuvre pour fournir une application dans un réseau de communication
CN115997375A (zh) 在第五代（5g）系统中提供对本地化服务的接入（pals）
CN115997396A (zh) 在第五代（5g）系统中经由托管网络提供按需本地化服务
EP4255092A1 (fr) Communication d&#39;élément de réseau de l&#39;internet des objets personnel avec un système 5g et d&#39;autres éléments de réseau de l&#39;internet des objets personnel
US20220247623A1 (en) Network node and method performed therein for handling communication in a wireless communication network
KR20230153401A (ko) 차세대 셀룰러 네트워크들에서의 원격 직접 메모리 액세스(rdma)를 위한 혼잡 제어
JP2024519259A (ja) Ｍｓｇ３物理アップリンク共有チャネル（ＰＵＳＣＨ）繰り返し要求
US20230164623A1 (en) Application Function Node, Access and Mobility Management Function Node, System and Methods in a Communications Network
WO2022039835A1 (fr) Identification d&#39;un ue à l&#39;aide de son adresse ip source
WO2022015485A1 (fr) Techniques de transmission de canal de commande pour fonctionnement sans créneaux et ordonnancement de transmissions de données
CN115769615A (zh) 用于下一代蜂窝网络的计算服务实现
US20240154883A1 (en) Sixth generation (6g) system architecture and functions
US20240146473A1 (en) Enhanced frequency hopping for data transmissions
EP4376461A1 (fr) Procédé et dispositif pour faire fonctionner un terminal dans un système de communication sans fil
US20240147438A1 (en) Time domain resource allocation for data transmissions
US20230164745A1 (en) Inter-user equipment (ue) coordination information for new radio (nr) sidelink communication
US20240178945A1 (en) Time domain bundling of hybrid automatic repeat request-acknowledgement (harq-ack) feedback

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20797442

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20797442

Country of ref document: EP

Kind code of ref document: A1