WO2024037452A1 - Procédé et appareil de sélection de scénario acr - Google Patents

Procédé et appareil de sélection de scénario acr Download PDF

Info

Publication number
WO2024037452A1
WO2024037452A1 PCT/CN2023/112564 CN2023112564W WO2024037452A1 WO 2024037452 A1 WO2024037452 A1 WO 2024037452A1 CN 2023112564 W CN2023112564 W CN 2023112564W WO 2024037452 A1 WO2024037452 A1 WO 2024037452A1
Authority
WO
WIPO (PCT)
Prior art keywords
acr
ees
eas
network node
target
Prior art date
Application number
PCT/CN2023/112564
Other languages
English (en)
Inventor
Wenliang Xu
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 WO2024037452A1 publication Critical patent/WO2024037452A1/fr

Links

Classifications

    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for application context relocation (ACR) scenario selection.
  • ACR application context relocation
  • Edge computing is a concept that enables services to be hosted close to the service consumers and provides benefits such as efficient service delivery with significant reduction in end-to-end latency and decreased load on the transport network.
  • the benefits of edge computing will strengthen the promise of 5G (fifth generation) and expand the prospects for several new and enhanced use cases –including virtual and augmented reality, Internet of Things (IoT) , Industrial IoT, autonomous driving, real-time multiplayer gaming, etc.
  • IoT Internet of Things
  • Industrial IoT autonomous driving
  • real-time multiplayer gaming etc.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project (3GPP) TS 23.558 V17.4.0, the disclosure of which is incorporated by reference herein in its entirety, specifies application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures to enable the deployment of edge applications.
  • FIG. 1a shows a reference point representation of architecture for edge enabling applications according to an embodiment of the present disclosure.
  • FIG. 1a is same as Figure 6.2-4 of 3GPP TS 23.558 V17.4.0.
  • the Edge Data Network (EDN) is a local Data Network.
  • Edge Application Server (s) and the Edge Enabler Server are contained within the EDN.
  • the Edge Configuration Server provides configurations related to the EES, including details of the Edge Data Network hosting the (edge enabler server) .
  • the UE contains Application Client (s) (ACs) and the Edge Enabler Client (EEC) .
  • the Edge Application Server (s) , the Edge Enabler Server and the Edge Configuration Server may interact with the 3GPP core network.
  • the functional entities include:
  • EES Edge Enabler Server
  • EEC Edge Enabler Client
  • ECS Edge Configuration Server
  • AC Application Client
  • EAS Edge Application Server
  • EAS is the application server resident in the EDN, performing the server functions.
  • the AC connects to the EAS in order to avail the services of the application with the benefits of Edge Computing.
  • 3GPP TR 23.700-98 V1.1.1 the disclosure of which is incorporated by reference herein in its entirety, is a technical report capturing the study on enhanced architecture for enabling edge applications over 3GPP networks.
  • FIG. 1b shows a reference point representation of architecture for edge enabling applications according to another embodiment of the present disclosure.
  • FIG. 1b is same as Figure 6.2.1-1 of 3GPP TR 23.700-98 V1.1.1.
  • EDGEAPP Edge Applications
  • the ACR scenarios may include user equipment (UE) triggered ACR (e.g. triggered by EEC) and data network (DN) side triggered ACR scenarios (i.e. triggered by S-EAS (source EAS) or S-EES (source EES) ) .
  • UE user equipment
  • DN data network
  • S-EAS source EAS
  • S-EES source EES
  • multiple ACR scenarios can be supported by AC, EEC, EES and EAS and these ACR scenarios can be triggered simultaneously.
  • ACR scenario selection to narrow down the number of used ACR scenarios (e.g. only one ACR scenario is selected) to reduce the complexity.
  • ACR scenarios are specified in 3GPP TS 23.558 [2] clause 8.8.
  • Applications can utilize one or more ACR scenarios. Different combinations of utilizing ACR scenarios by Applications should be enabled by the Edge Enabler Layer (e.g. only one ACR scenario allowed or several ACR scenarios allowed) .
  • ACR scenarios made by EES was mentioned in Solution #19 of 3GPP TR 23.700-98 V1.1.1.
  • the selection of ACR scenario made by EEC was mentioned in Solution #35 of 3GPP TR 23.700-98 V1.1.1. They are suitable in EEC triggered initial EAS discovery and EEC triggered T-EAS discovery during ACR.
  • an improved solution for ACR scenario selection may be desirable.
  • the T-EAS service continuity support capability e.g. supported ACR scenarios
  • AC, EEC and EES service continuity support capability of AC, EEC and EES.
  • ACR scenario selection can be further decided between S-EAS and S-EES and final result needs to be notified to the EEC and T-EAS.
  • a method performed by a first network node may comprise deciding to perform application context relocation (ACR) .
  • the method may further comprise sending a first message to a second network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the at least one ACR scenario to be used in the next ACR may be supported by an application client (AC) , an edge enabler client (EEC) , a target edge application server (EAS) and a target edge enabler server (EES) .
  • AC application client
  • EEC edge enabler client
  • SAS target edge application server
  • EES target edge enabler server
  • the first network node may comprise a source EES and the second network node may comprise a target EES.
  • the method may further comprise sending a fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the fourth message may be a target information notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • a method performed by a second network node may comprise receiving a first message from a first network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the method may further comprise selecting the at least one ACR scenario to be used in the next ACR.
  • the at least one ACR scenario to be used in the next ACR may be supported by an AC, an EEC, a target EAS and a target EES.
  • the first network node may comprise a source EES and the second network node may comprise a target EES.
  • the method may further comprise sending a sixth message to an EEC.
  • the sixth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the method may further comprise sending a ninth message to a target EAS.
  • the ninth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the sixth message may be a target information notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • the method may further comprise sending a message comprising information about the at least one ACR scenario to be used in the next ACR to the first network node.
  • a method performed by a target EAS may comprise receiving an eighth message from a target EES.
  • the eighth message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the method may further comprise storing the information about the at least one ACR scenario to be used in the next ACR.
  • the at least one ACR scenario to be used in the next ACR may be supported by an AC, an EEC, the target EAS and the target EES.
  • the method may further comprise sending an ACR scenario selection subscription request to the target EES.
  • the method may further comprise receiving an ACR scenario selection subscription response from the target EES.
  • the eighth message may be an ACR selection notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • a method performed by an EEC may comprise receiving a message comprises information about at least one ACR scenario to be used in a next ACR from an EES in an ACR scenario.
  • the method further comprises storing the information about the at least one ACR scenario to be used in the next ACR.
  • the method may further comprise sending a message comprises information about at least one ACR scenario to be used in a next ACR to an AC.
  • the at least one ACR scenario to be used in the next ACR may be supported by an AC, the EEC, a target EAS and a target EES.
  • the message may be a target information notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • a first network node may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor.
  • the first network node is operative to decide to perform application context relocation (ACR) .
  • the first network node is further operative to send a first message to a second network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • a second network node comprising a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor.
  • the second network node is operative to receive a first message from a first network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the second network node is further operative to select the at least one ACR scenario to be used in the next ACR.
  • a target EAS comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor.
  • the target EAS is operative to receive an eighth message from a target EES.
  • the eighth message may comprise information about at least one ACR scenario to be used in a next ACR.
  • a EEC comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor.
  • the EEC is operative to receive a message comprising information about at least one ACR scenario to be used in a next ACR from an EES in an ACR scenario.
  • the EEC is further operative to store the information about the at least one ACR scenario to be used in the next ACR.
  • a first network node may comprise a deciding module configured to decide to perform application context relocation (ACR) .
  • the first network node may further comprise a first sending module configured to send a first message to a second network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the first network node may further comprise a second sending module configured to send a fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • a second network node may comprise a receiving module configured to receive a first message from a first network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the second network node may further comprise a selecting module configured to select the at least one ACR scenario to be used in the next ACR.
  • the second network node may further comprise a first sending module configured to send a sixth message to an EEC.
  • the sixth message may comprise the information about the at least one ACR scenario to be used in the next ACR
  • the second network node may further comprise a second sending module configured to send a ninth message to a target EAS.
  • the ninth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the second network node may further comprise a third sending module configured to send a message comprising information about the at least one ACR scenario to be used in the next ACR to the first network node.
  • the target EAS may comprise a first receiving module configured to receive an eighth message from a target EES.
  • the eighth message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the target EAS may further comprise a storing module configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • the target EAS may further comprise a sending module configured to send an ACR scenario selection subscription request to the target EES.
  • the target EAS may further comprise a second receiving module configured to receive an ACR scenario selection subscription response from the target EES.
  • an EEC may comprise a receiving module configured to receive a message from an EES in an ACR scenario.
  • the message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the EEC may further comprise a storing module configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • the EEC may further comprise a sending module configured to send a message comprising information about at least one ACR scenario to be used in a next ACR to an AC.
  • a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first, second, third or fourth aspects.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first, second, third or fourth aspects.
  • a communication system including a host computer.
  • the host computer includes processing circuitry configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device.
  • the cellular network includes a network node (such as the first network node or the second network node above mentioned) , and/or the terminal device (such as EEC above mentioned) .
  • the system further includes the terminal device.
  • the terminal device is configured to communicate with the network node.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the terminal device includes processing circuitry configured to execute a client application associated with the host application.
  • a communication system including a host computer and a network node.
  • the host computer includes a communication interface configured to receive user data originating from a transmission from a terminal device.
  • the transmission is from the terminal device to the network node.
  • the terminal device is above mentioned EEC.
  • the processing circuitry of the host computer is configured to execute a host application.
  • the terminal device is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • a method implemented in a communication system which may include a host computer, a network node and a terminal device.
  • the method may comprise providing user data at the host computer.
  • the method may comprise, at the host computer, initiating a transmission carrying the user data to the terminal device via a cellular network comprising the network node.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device.
  • the cellular network may comprise a network node having a radio interface and processing circuitry.
  • a method implemented in a communication system which may include a host computer, a network node and a terminal device.
  • the method may comprise providing user data at the host computer.
  • the method may comprise, at the host computer, initiating a transmission carrying the user data to the terminal device via a cellular network comprising the network node.
  • the terminal device may perform any step of the method according to the fifth and sixth aspects of the present disclosure.
  • a communication system including a host computer.
  • the host computer may comprise processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a terminal device.
  • the terminal device may comprise a radio interface and processing circuitry.
  • the terminal device’s processing circuitry may be configured to perform any step of the method according to the fifth and sixth aspects of the present disclosure.
  • a method implemented in a communication system which may include a host computer, a network node and a terminal device.
  • the method may comprise, at the host computer, receiving user data transmitted to the network node from the terminal device which may perform any step of the method according to the fifth and sixth aspects of the present disclosure.
  • a communication system including a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a terminal device to a network node.
  • the terminal device may comprise a radio interface and processing circuitry.
  • the terminal device’s processing circuitry may be configured to perform any step of the method according to the fifth and sixth aspects of the present disclosure.
  • a method implemented in a communication system which may include a host computer, a network node and a terminal device.
  • the method may comprise, at the host computer, receiving, from the network node, user data originating from a transmission which the network node has received from the terminal device.
  • a communication system which may include a host computer.
  • the host computer may comprise a communication interface configured to receive user data originating from a transmission from a terminal device to a network node.
  • the network node may comprise a radio interface and processing circuitry.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows.
  • it can address KI#19 of 3GPP TR 23.700-98 V1.1.1 in the S-EAS decided ACR scenario which allows the S-EAS to determine the ACR scenario (s) or request the S-EES to determine the ACR scenario (s) to be used.
  • it can address KI#19 of 3GPP TR 23.700-98 V1.1.1 in the S-EES executed ACR scenario which allows the S-EES to determine the ACR scenario (s) to be used.
  • the proposed solution provides a proactive way to decrease the system complexity for the subsequent ACR during Data network side triggered ACR.
  • FIG. 1a shows a reference point representation of architecture for edge enabling applications according to an embodiment of the present disclosure
  • FIG. 1b shows a reference point representation of architecture for edge enabling applications according to another embodiment of the present disclosure
  • FIG. 2a schematically shows a high level architecture in the fifth generation network according to an embodiment of the present disclosure
  • FIG. 2b schematically shows system architecture in a 4G network according to an embodiment of the present disclosure
  • FIG. 3a shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 3b shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 3c shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 3d shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 3e shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 3f shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 3g shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 4a shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 4b shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 4c shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 4d shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 5a shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 5b shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 5c shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 6a shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 6b shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 6c shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 7a shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 7b shows a flowchart of S-EAS decided ACR scenario selection according to an embodiment of the present disclosure
  • FIG. 7c shows a flowchart of S-EAS requested ACR scenario selection according to an embodiment of the present disclosure
  • FIG. 7d shows a flowchart of S-EES decided ACR scenario selection according to an embodiment of the present disclosure
  • FIG. 8a is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • FIG. 8b is a block diagram showing a first network node according to an embodiment of the disclosure.
  • FIG. 8c is a block diagram showing a second network node according to an embodiment of the disclosure.
  • FIG. 8d is a block diagram showing a target EES according to another embodiment of the disclosure.
  • FIG. 8e is a block diagram showing a target EAS according to another embodiment of the disclosure.
  • FIG. 8f is a block diagram showing an EEC according to another embodiment of the disclosure.
  • FIG. 8g is a block diagram showing an AC according to another embodiment of the disclosure.
  • FIG. 9 is a schematic showing a wireless network in accordance with some embodiments.
  • FIG. 10 is a schematic showing a user equipment in accordance with some embodiments.
  • FIG. 11 is a schematic showing a virtualization environment in accordance with some embodiments.
  • FIG. 12 is a schematic showing a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • FIG. 13 is a schematic showing a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;
  • FIG. 14 is a schematic showing 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 schematic showing methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;
  • FIG. 16 is a schematic showing methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG. 17 is a schematic showing methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • the term “network” refers to a network following any suitable communication standards such as new radio (NR) , long term evolution (LTE) , LTE-Advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • a CDMA network may implement a radio
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • Ad-hoc network wireless sensor network
  • the terms “network” and “system” can be used interchangeably.
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP.
  • the communication protocols may comprise the first generation (1G) , 2G
  • network node or “network node” refers to any suitable network function (NF) which can be implemented in a network element (physical or virtual) of a communication network.
  • NF network function
  • the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the 5G system may comprise a plurality of NFs such as AMF (Access and mobility Function) , SMF (Session Management Function) , AUSF (Authentication Service Function) , UDM (Unified Data Management) , PCF (Policy Control Function) , AF (Application Function) , NEF (Network Exposure Function) , UPF (User plane Function) and NRF (Network Repository Function) , RAN (radio access network) , SCP (service communication proxy) , NWDAF (network data analytics function) , NSSF (Network Slice Selection Function) , NSSAAF (Network Slice-Specific Authentication and Authorization Function) , etc.
  • AMF Access and mobility Function
  • SMF Session Management Function
  • AUSF Authentication Service Function
  • UDM Unified Data Management
  • PCF Policy Control Function
  • AF Application Function
  • NEF Network Exposure Function
  • UPF User plane Function
  • NRF Network Repository Function
  • RAN radio access network
  • the 4G system may include MME (Mobile Management Entity) , HSS (home subscriber server) , Policy and Charging Rules Function (PCRF) , Packet Data Network Gateway (PGW) , PGW control plane (PGW-C) , Serving gateway (SGW) , SGW control plane (SGW-C) , E-UTRAN Node B (eNB) , etc.
  • MME Mobile Management Entity
  • HSS home subscriber server
  • PCRF Policy and Charging Rules Function
  • PGW Packet Data Network Gateway
  • PGW-C PGW control plane
  • SGW Serving gateway
  • SGW-C SGW control plane
  • the network function may comprise different types of NFs for example depending on a specific network.
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE) , or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA) , a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • a portable computer an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance
  • a mobile phone a cellular phone, a smart phone, a voice over IP (VoIP) phone
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project) , such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3rd Generation Partnership Project
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean “only A, only B, or both A and B. ”
  • the phrase “A and/or B” should be understood to mean “only A, only B, or both A and B” .
  • a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device.
  • the communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and/or use of the services provided by, or via, the communication system.
  • FIG. 2a schematically shows a high level architecture in the fifth generation network according to an embodiment of the present disclosure.
  • the fifth generation network may be 5GS.
  • the architecture of FIG. 2a is same as Figure 4.2.3-2 as described in 3GPP TS 23.501 V17.2.0, the disclosure of which is incorporated by reference herein in its entirety.
  • 2a may comprise some exemplary elements such as AUSF, AMF, DN (data network) , NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN, SCP (Service Communication Proxy) , NSSAAF (Network Slice-Specific Authentication and Authorization Function) , NSACF (Network Slice Admission Control Function) , etc.
  • the UE can establish a signaling connection with the AMF over the reference point N1, as illustrated in FIG. 2a.
  • This signaling connection may enable NAS (Non-access stratum) signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R) AN and the N2 connection for this UE between the (R) AN and the AMF.
  • the (R) AN can communicate with the UPF over the reference point N3.
  • the UE can establish a protocol data unit (PDU) session to the DN (data network, e.g. an operator network or Internet) through the UPF over the reference point N6.
  • PDU protocol data unit
  • the exemplary system architecture also contains some reference points such as N1, N2, N3, N4, N6, N9, N15, etc., which can support the interactions between NF services in the NFs.
  • these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.
  • the AM related policy is provided by PCF to AMF for a registered UE via N15 interface. AMF can get AM policy during AM Policy Association Establishment/Modification procedure.
  • Various NFs shown in FIG. 2a may be responsible for functions such as session management, mobility management, authentication, security, etc.
  • the AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R) AN, SCP, NSACF may include the functionality for example as defined in clause 6.2 of 3GPP TS 23.501 V17.2.0.
  • FIG. 2b schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-1a of 3GPP TS 23.682 V17.2.0, the disclosure of which is incorporated by reference herein in its entirety.
  • SCS Services Capability Server
  • AS Application Server
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber System
  • UE User Equipment
  • RAN Radio Access Network
  • SGSN Serving GPRS (General Packet Radio Service) Support Node)
  • MME Mobile Switching Centre
  • S-GW Serving Gateway
  • GGSN/P-GW Gateway GPRS Support Node/PDN (Packet Data Network) Gateway
  • MTC-IWF Machine Type Communications-InterWorking Function
  • CDF/CGF Charging Data Function/Charging Gateway Function
  • MTC-AAA Mobileachine Type Communications-authentication, authorization and accounting
  • SMS-SC/GMSC/IWMSC Short Message Service-Service Centre/Gateway MSC/InterWorking MSC
  • IP-SM-GW Internet protocol Short Message Gateway
  • the system architecture shows the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN (Universal Terrestrial Radio Access Network) , E-UTRAN (Evolved UTRAN) , GERAN (GSM EDGE (Enhanced Data rates for GSM Evolution) Radio Access Network) , etc. ) via the Um/Uu/LTE-Uu interfaces.
  • the system architecture also shows the 3GPP network service capability exposure to SCS and AS.
  • the exemplary system architecture also contains various reference points.
  • Tsms Reference point used by an entity outside the 3GPP network to communicate with UEs used for MTC via SMS (Short Message Service) .
  • Tsp Reference point used by a SCS to communicate with the MTC-IWF related control plane signalling.
  • T4 Reference point used between MTC-IWF and the SMS-SC in the HPLMN.
  • T6a Reference point used between SCEF and serving MME.
  • T6b Reference point used between SCEF and serving SGSN.
  • T8 Reference point used between the SCEF and the SCS/AS.
  • S6m Reference point used by MTC-IWF to interrogate HSS/HLR (Home Location Register) .
  • S6n Reference point used by MTC-AAA to interrogate HSS/HLR.
  • S6t Reference point used between SCEF and HSS.
  • Gi/SGi Reference point used between GGSN/P-GW and application server and between GGSN/P-GW and SCS.
  • Rf/Ga Reference point used between MTC-IWF and CDF/CGF.
  • Gd Reference point used between SMS-SC/GMSC/IWMSC and SGSN.
  • SGd Reference point used between SMS-SC/GMSC/IWMSC and MME.
  • FIG. 3a shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 300 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the first network node may decide to perform application context relocation (ACR) .
  • ACR application context relocation
  • the ACR may be for an AC.
  • the first network node may be any suitable network node in an ACR scenario.
  • the first network node may be S-EES (source EES) or S-EAS (source EAS) .
  • the first network node may be S-EES.
  • the S-EES may decide to perform ACR.
  • the first network node may be S-EAS.
  • the S-EAS may decide to perform ACR.
  • the first network node may send a first message to a second network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the first network node may select at least one ACR scenario to be used in a next ACR.
  • the first message may be any suitable message such as an existing message or a new message.
  • the first message may be any suitable existing message in a corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.
  • the first message is a selected target EAS declaration message as described in 3GPP TS 23.558 V17.4.0.
  • the second network node may be any suitable network node in an ACR scenario.
  • the second network node may be S-EES (source EES) or T-EES (target EES) .
  • the first network node may select at least one ACR scenario to be used in a next ACR.
  • the first network node may send a first message to a second network node such as S-EES.
  • the first network node may send a first message to a second network node such as T-EES.
  • the at least one ACR scenario to be used in the next ACR is supported by an application client (AC) , an edge enabler client (EEC) , a target edge application server (EAS) and a target edge enabler server (EES) .
  • AC application client
  • EEC edge enabler client
  • SAS target edge application server
  • EES target edge enabler server
  • the first network node may obtain or know supported ACR scenarios in service continuity support capability among AC, EEC, T-EES (target EES) and T-EAS (target EAS) .
  • the S-EES may include the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the first network node such as S-EAS or S-EES may select one or more ACR scenario (s) based on the supported ACR scenarios by the selected T-EAS.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery (e.g., as described in clause 8.8.2.2 of 3GPP TS 23.558 V17.4.0) , an ACR executed by an EEC via a source EES (e.g., as described in clause 8.8.2.3 of 3GPP TS 23.558 V17.4.0) , an ACR decided by a source EAS (e.g., as described in clause 8.8.2.4 of 3GPP TS 23.558 V17.4.0) , an ACR executed by a source EES (e.g., as described in clause 8.8.2.5 of 3GPP TS 23.558 V17.4.0) , or an ACR executed by an EEC via a target EES (e.g., as described in clause 8.8.2.6 of 3GPP TS 23.558 V17.4.0) .
  • regular EAS discovery e.g., as described in clause 8.8.2.2 of 3GPP TS 23.558
  • the first network node may further perform the proposed method according to various embodiments.
  • first network node is a S-EES and the second network node is a T-EES
  • the T-EES may send a message to an EEC and a T-EAS.
  • the message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • FIG. 3b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 310 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the first network node may comprise a source edge application server (EAS) and the first network node may select the at least one ACR scenario to be used in the next ACR.
  • EAS source edge application server
  • the first network node may send a first EAS discovery request to a source edge enabler server (EES) .
  • EAS source edge enabler server
  • the EAS discovery request may be same as the EAS discovery request as described in 3GPP TS 23.558 V17.4.0.
  • the first network node may receive a first EAS discovery response from the source EES.
  • the first EAS discovery response may comprise information about at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among an AC, an EEC, a target EAS and a target EES.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the first network node may select a target EAS from the at least one candidate target EAS.
  • the first network node may select a target EAS from the at least one candidate target EAS in various ways and the present disclosure has no limit on it.
  • FIG. 3c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 320 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the first network node may comprise a source edge application server (EAS) and the first network node may select the at least one ACR scenario to be used in the next ACR.
  • EAS source edge application server
  • the first network node may send a second message to the second network node.
  • the second message may comprise information about the at least one ACR scenario to be used in the next ACR.
  • the second message may be any suitable message such as an existing message or a new message.
  • the second message may be any suitable existing message in a corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.
  • the second message is a selected target EAS declaration message as described in 3GPP TS 23.558 V17.4.0.
  • FIG. 3d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 330 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the first network node may comprise a source edge application server (EAS) and the first network node may send the first message to the second network node.
  • EAS source edge application server
  • the first network node may send a second EAS discovery request to a source EES.
  • the second EAS discovery request may be same as the EAS discovery request as described in 3GPP TS 23.558 V17.4.0.
  • the first network node may receive a second EAS discovery response from the source EES.
  • the second EAS discovery response may comprise information about at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among an AC, an EEC, a target EAS and a target EES.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the first network node may select a target EAS from the at least one candidate target EAS.
  • FIG. 3e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 340 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the first network node may comprise a source EES.
  • the source EES may select the at least one ACR scenario to be used in the next ACR and/or may send the first message to the second network node such as T-EES.
  • the first network node may send a third EAS discovery request to a target EES.
  • the third EAS discovery request may comprise AC service continuity support capability and EEC service continuity support capability.
  • the first network node may receive a third EAS discovery response from the target EES.
  • the third EAS discovery response may comprise information about at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among an AC, an EEC, a target EAS and the target EES.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the first network node may select a target EAS from the at least one candidate target EAS.
  • the first network node may select a target EAS from the at least one candidate target EAS in various ways and the present disclosure has no limit on it.
  • FIG. 3f shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 350 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the first network node may send a third message to a target EES.
  • the third message may comprise information about the at least one ACR scenario to be used in the next ACR.
  • the first network node such as S-EES may select at least one ACR scenario to be used in a next ACR, it may send the third message to a target EES.
  • the third message may be any suitable message such as an existing message or a new message.
  • the third message may be any suitable existing message in a corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.
  • the third message is a selected target EAS declaration message.
  • the first network node may send a fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the first network node such as S-EES may select at least one ACR scenario to be used in a next ACR, it may send the third message to the EEC.
  • the fourth message may be any suitable message such as an existing message or a new message.
  • the fourth message may be any suitable existing message in a corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.
  • the fourth message is a target information notification message as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.
  • FIG. 3g shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 360 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the second network node may comprise a target EES and the source EES may send the first message to the target EES.
  • the target EES may select the at least one ACR scenario to be used in the next AC.
  • the first network node may receive a message comprising information about the at least one ACR scenario to be used in the next ACR from the target EES.
  • the message may be the selected target EAS declaration response.
  • the first network node may send the fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • FIG. 4a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 400 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the second network node may receive a first message from a first network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the second network node may be S-EES and the first network node may be S-EAS.
  • the second network node may be T-EES and the first network node may be S-EES.
  • the first message is a selected target EAS declaration message.
  • the first network node may comprise a source edge application server (EAS) and the second network node may comprise a source EES.
  • EAS source edge application server
  • the second network node may select the at least one ACR scenario to be used in the next ACR.
  • the at least one ACR scenario to be used in the next ACR is supported by an application client (AC) , an edge enabler client (EEC) , a target edge application server (EAS) and a target edge enabler server (EES) .
  • AC application client
  • EEC edge enabler client
  • SAS target edge application server
  • EES target edge enabler server
  • the second network node may obtain or know supported ACR scenarios in service continuity support capability among AC, EEC, T-EES (target EES) and T-EAS (target EAS) .
  • the S-EES may include the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the second network node such as S-EES or T-EES may select one or more ACR scenario (s) based on the supported ACR scenarios by the selected T-EAS.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • FIG. 4b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 410 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the second network node may receive a second EAS discovery request from the first network node.
  • the second network node may send a fourth EAS discovery request to a target EES.
  • the fourth EAS discovery request may comprise AC service continuity support capability and EEC service continuity support capability.
  • the second network node receive a fourth EAS discovery response from the target EES.
  • the fourth EAS discovery response may comprise information about at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among an AC, an EEC, a target EAS and the target EES.
  • the second network node may send a second EAS discovery response to the first network node.
  • the second EAS discovery response may comprise the information about the at least one candidate target EAS.
  • blocks 412, 414, 416 and 418 may be performed.
  • the second EAS discovery request may comprise AC service continuity support capability and EEC service continuity support capability.
  • FIG. 4c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 420 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the second network node may send a fifth message to a target EES.
  • the fifth message may comprise information about the at least one ACR scenario to be used in the next ACR.
  • the second network node may send the fifth message to the target EES.
  • block 422 may be omitted and the T-EES may store the information about the at least one ACR scenario to be used in the next ACR.
  • the second network node may send a sixth message to an EEC.
  • the sixth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the EEC may notify the AC with the at least one ACR scenario to be used in the next ACR.
  • the second network node may send the sixth message to the EEC.
  • the first network node is S-EES and the second network node is T-EES
  • the second network node may send the sixth message to the EEC and store the information about the at least one ACR scenario to be used in the next ACR.
  • T-EES directly notify EEC without EEC subscription to T-EES, this is a possible method if using control plane based notification (e.g. Short Message Service or Non-IP Data Delivery) to UE.
  • control plane based notification e.g. Short Message Service or Non-IP Data Delivery
  • the fifth message is a selected target EAS declaration message and the sixth message is a target information notification message.
  • the second network node may send a ninth message to a target EAS.
  • the ninth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the second network node may send the ninth message to the EAS.
  • FIG. 4d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node.
  • the apparatus may provide means or modules for accomplishing various parts of the method 430 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the first network node may comprise a source EES.
  • the second network node may comprise a target EES.
  • the target EES may select the at least one ACR scenario to be used in the next AC.
  • the second network node may send a message comprising information about the at least one ACR scenario to be used in the next ACR to the first network node
  • the message may be the selected target EAS declaration response.
  • the first network node may send the fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the second network node send the ninth message to a target EAS.
  • the ninth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • FIG. 5a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a target EES or communicatively coupled to the target EES.
  • the apparatus may provide means or modules for accomplishing various parts of the method 500 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the target EES may receive a seventh message from a source EES.
  • the seventh message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the target EES may store the information about the at least one ACR scenario to be used in the next ACR.
  • the target EES may be as a source EES and knows which ACR scenario is to be used. Therefore the proposal method provides a proactive way to decrease the system complexity for the subsequent ACR during data network side triggered ACR.
  • the target EES may send an eighth message to a target EAS.
  • the eighth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the target EAS may be as a source EAS and knows which ACR scenario is to be used. Therefore the proposal method provides a proactive way to decrease the system complexity for the subsequent ACR during data network side triggered ACR.
  • the at least one ACR scenario to be used in the next ACR is supported by an AC, an EEC, the target EAS and the target EES.
  • the seventh message is a selected target EAS declaration message and the eighth message is an ACR selection notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • FIG. 5b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a target EES or communicatively coupled to the target EES.
  • the apparatus may provide means or modules for accomplishing various parts of the method 510 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the target EES may receive an EAS discovery request from the source EES.
  • the EAS discovery request may comprise AC service continuity support capability and EEC service continuity support capability.
  • the target EES may discover at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among AC, EEC, the target EAS and the target EES.
  • the target EES may send an EAS discovery response to the source EES.
  • the EAS discovery response may comprise information about at least one candidate target EAS.
  • FIG. 5c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a target EES or communicatively coupled to the target EES.
  • the apparatus may provide means or modules for accomplishing various parts of the method 520 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the target EES may receive an ACR scenario selection subscription request from the target EAS.
  • the target EES may send an ACR scenario selection subscription response to the target EAS.
  • the target EES may send the eighth message to the target EAS in response to receiving an ACR scenario selection subscription request from the target EAS.
  • FIG. 6a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a target EAS or communicatively coupled to the target EAS.
  • the apparatus may provide means or modules for accomplishing various parts of the method 600 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the target EAS may receive an eighth message from a target EES.
  • the eighth message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the target EAS may store the information about the at least one ACR scenario to be used in the next ACR.
  • the target EAS may be as a source EAS and knows which ACR scenario is to be used. Therefore the proposal method provides a proactive way to decrease the system complexity for the subsequent ACR during data network side triggered ACR.
  • the at least one ACR scenario to be used in the next ACR is supported by an AC, an EEC, the target EAS and the target EES.
  • the eighth message is an ACR selection notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • FIG. 6b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a target EAS or communicatively coupled to the target EAS.
  • the apparatus may provide means or modules for accomplishing various parts of the method 610 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the target EAS may send an ACR scenario selection subscription request to the target EES.
  • the target EAS may receive an ACR scenario selection subscription response from the target EES.
  • the target EAS may receive the eighth message from the target EES in response to sending the ACR scenario selection subscription request to the target EES.
  • FIG. 6c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an EEC or communicatively coupled to the EEC.
  • the apparatus may provide means or modules for accomplishing various parts of the method 620 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the EEC may receive a message from an EES in an ACR scenario.
  • the message may comprise information about at least one ACR scenario to be used in a next ACR.
  • a decision to perform ACR in the ACR scenario may be made by a source EES or a source EAS.
  • the EES may be a source EES or a target EES.
  • the EEC may store the information about the at least one ACR scenario to be used in the next ACR.
  • the EEC knows which ACR scenario is to be used. Therefore the proposal method provides a proactive way to decrease the system complexity for the subsequent ACR during data network side triggered ACR.
  • the EEC may send a message comprising the information about the at least one ACR scenario to be used in the next ACR to an AC.
  • the EEC may notify the AC with the at least one ACR scenario to be used in the next ACR.
  • the at least one ACR scenario to be used in the next ACR is supported by an AC, the EEC, a target EAS and a target EES.
  • the message is a target information notification message.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • FIG. 7a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an AC or communicatively coupled to the AC.
  • the apparatus may provide means or modules for accomplishing various parts of the method 700 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the description thereof is omitted here for brevity.
  • the AC may receive a message from a EEC in an ACR scenario.
  • the message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the AC may store the information about the at least one ACR scenario to be used in the next ACR.
  • a decision to perform ACR in the ACR scenario is made by a source EES or a source EAS.
  • the AC knows which ACR scenario is to be used. Therefore the proposal method provides a proactive way to decrease the system complexity for the subsequent ACR during data network side triggered ACR.
  • the at least one ACR scenario to be used in the next ACR is supported by an AC, the EEC, a target EAS and a target EES.
  • the at least one ACR scenario may comprise at least one of an ACR initiated by an EEC using regular EAS discovery, an ACR executed by an EEC via a source EES, an ACR decided by a source EAS, an ACR executed by a source EES, or an ACR executed by an EEC via a target EES.
  • the S-EAS discovers the candidate T-EAS (s) via the S-EES and may select a T-EAS.
  • the S-EAS can:
  • the EES After receiving a request for selecting ACR scenario (s) to be used from the S-EAS, the EES can select ACR scenario (s) to be used or ask T-EES to select ACR scenario (s) to be used. Then the T-EES may send information about the ACR scenario (s) to be used to the S-EES. Then the T-EAS and EEC are notified with the information about the ACR scenario (s) to be used.
  • the S-EES discovers the candidate T-EAS (s) and select a T-EAS.
  • the S-EES further selects ACR scenario (s) to be used or ask T-EES to select ACR scenario (s) to be used.
  • the T-EES may send information about the ACR scenario (s) to be used to the S-EES.
  • the T-EAS and EEC are notified with the information about the ACR scenario (s) to be used.
  • the selected ACR scenario (s) can be the same as or a subset of the common supported ACR scenarios by AC, EEC, EES and EAS.
  • FIG. 7b shows a flowchart of S-EAS decided ACR scenario selection according to an embodiment of the present disclosure.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the S-EAS Before sending Selected T-EAS declaration request to the S-EES in step 4, the S-EAS additionally selects one or more ACR scenario (s) based on the supported ACR scenarios by the selected T-EAS. Then the S-EAS includes the selected ACR scenario list in the Selected T-EAS declaration request to the S-EES.
  • the S-EES declares the selected T-EAS and selected ACR scenario list to the T-EES.
  • the T-EES stores the selected ACR scenarios to be used and notifies the selected T-EAS with the selected ACR scenario list.
  • T-EAS stores the selected ACR scenarios to be used and acknowledges the ACR selection notification and the T-EES in turn responds the S-EES for Selected T-EAS declaration.
  • step 4b is not executed and step 4c is executed between the S-EES and T-EAS.
  • T-EAS is supposed to subscribe to ACR selection notification in advance.
  • the S-EES additionally includes the selected ACR scenario list in the Target information notification sent to the EEC.
  • the EEC stores the selected ACR scenarios to be used.
  • FIG. 7b may be same as the corresponding steps as described in clause 8.8.2.4 of 3GPP TS 23.558 V17.4.0, the description thereof is omitted here for brevity.
  • FIG. 7c shows a flowchart of S-EAS requested ACR scenario selection according to an embodiment of the present disclosure.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) .
  • the discovered T-EAS (s) is a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, T-EES and T-EAS.
  • the S-EAS additionally request the S-EES to select one or more ACR scenario (s) . Then the S-EES, based on the selected T-EAS information received in the Selected T-EAS declaration request, selects one or more ACR scenario (s) from the supported ACR scenarios in service continuity support capability for the selected T-EAS.
  • the S-EES may also request the T-EES to select ACR scenarios to be used, in this case, the T-EES selects the ACR scenarios based on the selected T-EAS information received in the Selected T-EAS declaration request and responds the S-EES with the selected ACR scenario list. Then the T-EAS and EEC are notified with the selected ACR scenario list.
  • the S-EES declares the selected T-EAS and selected ACR scenario list to the T-EES.
  • the T-EES stores the selected ACR scenarios to be used and notifies the selected T-EAS with the selected ACR scenario list.
  • T-EAS stores the selected ACR scenarios to be used and acknowledges the ACR selection notification and the T-EES in turn responds the S-EES for Selected T-EAS declaration.
  • step 4b is not executed and step 4c is executed between the S-EES and T-EAS.
  • T-EAS is supposed to subscribe to ACR selection notification in advance.
  • the S-EES additionally includes the selected ACR scenario list in the Target information notification sent to the EEC.
  • the EEC stores the selected ACR scenarios to be used.
  • FIG. 7c may be same as the corresponding steps as described in clause 8.8.2.4 of 3GPP TS 23.558 V17.4.0, the description thereof is omitted here for brevity.
  • FIG. 7d shows a flowchart of S-EES decided ACR scenario selection according to an embodiment of the present disclosure.
  • the S-EES does not need to include its own service continuity support capability and S-EAS service continuity support capability. Instead, the S-EES includes the AC service continuity support capability (as part of AC profile) and EEC service continuity support capability in the T-EAS discovery request sent to T-EES (s) . Besides the common supported ACR scenarios, the discovered EASs may also support more ACR scenarios than the AC and EEC.
  • T-EES offered the discovered T-EASs to S-EAS are a filtered result which considers common supported ACR scenarios in service continuity support capability among AC, EEC, S-EES, T-EES and T-EAS as described in clause 8.8.3.2 of 3GPP TS 23.558 V17.4.0 and the selected T-EAS and T-EES cannot support more ACR scenarios than the S-EAS and S-EES, or the AC and EEC.
  • the S-EES additionally selects one or more ACR scenario (s) considering common supported ACR scenarios in AC, EEC, T-EES and T-EAS.
  • the S-EES knows the service continuity support capability in AC and EEC during initial EAS discovery, so it may select a T-EAS which supports more ACR scenarios than the AC and EEC but the selected one or more ACR scenario (s) need to be supported by the AC and EEC (and by T-EES and T-EAS too) .
  • the S-EES declares the selected T-EAS and selected ACR scenario list to the T-EES.
  • the T-EES stores the selected ACR scenarios to be used and notifies the selected T-EAS with the selected ACR scenario list.
  • T-EAS stores the selected ACR scenarios to be used and acknowledges the ACR selection notification and the T-EES in turn responds the S-EES for Selected T-EAS declaration.
  • the S-EES may also request the T-EES to select ACR scenarios to be used, in this case, the T-EES selects the ACR scenarios based on the selected T-EAS information received in the Selected T-EAS declaration request and responds the S-EES with the selected ACR scenario list. Then the T-EAS and EEC are notified with the selected ACR scenario list.
  • step 5b is not executed and step 5c is executed between the S-EES and T-EAS.
  • T-EAS is supposed to subscribe to ACR selection notification in advance.
  • the S-EES additionally includes the selected ACR scenario list in the Target information notification sent to the EEC.
  • the EEC stores the selected ACR scenarios to be used.
  • FIG. 7d may be same as the corresponding steps as described in clause 8.8.2.5 of 3GPP TS 23.558 V17.4.0, the description thereof is omitted here for brevity.
  • the following contents may be added into 3GPP TR 23.700-98 V1.1.1.
  • X. 2.4-1 describes the information elements for ACR information notification from the EES to the EEC.
  • X. 2.4-2 describes information elements for the selected target EAS declaration request sent from the S-EAS to the S-EES or from S-EES to T-EES.
  • X. 2.4-3 describes information elements for the selected target EAS declaration response sent from the T-EES to the S-EES.
  • Table 7. X. 2.3-4 describes the information elements for an ACR management event notification (to include ACR selection notification information) from the S-EES/T-EES to the T-EAS.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows.
  • it can address KI#19 of 3GPP TR 23.700-98 V1.1.1 in the S-EAS decided ACR scenario which allows the S-EAS to determine the ACR scenario (s) or request the S-EES to determine the ACR scenario (s) to be used.
  • it can address KI#19 of 3GPP TR 23.700-98 V1.1.1 in the S-EES executed ACR scenario which allows the S-EES to determine the ACR scenario (s) to be used.
  • the proposed solution provides a proactive way to decrease the system complexity for the subsequent ACR during Data network side triggered ACR.
  • FIG. 8a is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • any one of the first network node, the second network node, the target EES, the target EAS, the AC, or the EEC described above may be implemented as or through the apparatus 800.
  • the apparatus 800 comprises at least one processor 821, such as a digital processor (DP) , and at least one memory (MEM) 822 coupled to the processor 821.
  • the apparatus 800 may further comprise a transmitter TX and receiver RX 823 coupled to the processor 821.
  • the MEM 822 stores a program (PROG) 824.
  • the PROG 824 may include instructions that, when executed on the associated processor 821, enable the apparatus 800 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 821 and the at least one MEM 822 may form processing means 825 adapted to implement various embodiments of the present disclosure.
  • Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 821, software, firmware, hardware or in a combination thereof.
  • the MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.
  • the processor 821 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • general purpose computers special purpose computers
  • microprocessors microprocessors
  • DSPs digital signal processors
  • processors based on multicore processor architecture, as non-limiting examples.
  • the memory 822 contains instructions executable by the processor 821, whereby the first network node operates according to any of the methods related to the first network node as described above.
  • the memory 822 contains instructions executable by the processor 821, whereby the second network node operates according to any of the methods related to the second network node as described above.
  • the memory 822 contains instructions executable by the processor 821, whereby the target EES operates according to any of the methods related to the target EES as described above.
  • the memory 822 contains instructions executable by the processor 821, whereby the target EAS operates according to any of the methods related to the target EAS as described above.
  • the memory 822 contains instructions executable by the processor 821, whereby the EEC operates according to any of the methods related to the EEC as described above.
  • the memory 822 contains instructions executable by the processor 821, whereby the AC operates according to any of the methods related to the AC as described above.
  • FIG. 8b is a block diagram showing a first network node according to an embodiment of the disclosure.
  • the first network node 840 may comprise a deciding module 841 configured to decide to perform application context relocation (ACR) .
  • the first network node 840 may further comprise a first sending module 842 configured to send a first message to a second network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the first network node 840 may further comprise a second sending module 843 configured to send a fourth message to an EEC.
  • the fourth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • FIG. 8c is a block diagram showing a second network node 860 according to an embodiment of the disclosure.
  • the second network node 860 may comprise a receiving module 861 configured to receive a first message from a first network node.
  • the first message may comprise information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.
  • the second network node 860 may further comprise a selecting module 862 configured to select the at least one ACR scenario to be used in the next ACR.
  • the second network node 860 may further comprise a first sending module 863 configured to send a sixth message to an EEC.
  • the sixth message may comprise the information about the at least one ACR scenario to be used in the next ACR
  • the second network node 860 may further comprise a second sending module 864 configured to send a ninth message to a target EAS.
  • the ninth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the second network node 860 may further comprise a third sending module 865 configured to send a message comprising information about the at least one ACR scenario to be used in the next ACR to the first network node.
  • FIG. 8d is a block diagram showing a target EES according to another embodiment of the disclosure.
  • the target EES 870 may comprise a first receiving module 871 configured to receiving a seventh message from a source EES.
  • the seventh message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the target EES 870 may further comprise a storing module 872 configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • the target EES 870 may further comprise a first sending module 873 configured to sending an eighth message to a target EAS.
  • the eighth message may comprise the information about the at least one ACR scenario to be used in the next ACR.
  • the target EES 870 may further comprise a second receiving module 874 configured to receive an EAS discovery request from the source EES.
  • the EAS discovery request may comprise AC service continuity support capability and EEC service continuity support capability.
  • the target EES 870 may further comprise a discovering module 875 configured to discover at least one candidate target EAS.
  • the at least one candidate target EAS is a filtered result which considers at least one common supported ACR scenario in service continuity support capability among AC, EEC, the target EAS and the target EES.
  • the target EES 870 may further comprise a second sending module 876 configured to sending an EAS discovery response to the source EES.
  • the EAS discovery response may comprise information about at least one candidate target EAS.
  • the target EES 870 may further comprise a third receiving module 877 configured to receive an ACR scenario selection subscription request from the target EAS.
  • the target EES 870 may further comprise a third sending module 878 configured to send an ACR scenario selection subscription response to the target EAS.
  • FIG. 8e is a block diagram showing a target EAS according to another embodiment of the disclosure.
  • the target EAS 880 may comprise a first receiving module 881 configured to receive an eighth message from a target EES.
  • the eighth message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the target EAS 880 may further comprise a storing module 882 configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • the target EAS 880 may further comprise a sending module 883 configured to send an ACR scenario selection subscription request to the target EES.
  • the target EAS 880 may further comprise a second receiving module 884 configured to receive an ACR scenario selection subscription response from the target EES.
  • FIG. 8f is a block diagram showing an EEC according to another embodiment of the disclosure.
  • the EEC 890 may comprise a receiving module 891 configured to receive a message from an EES in an ACR scenario.
  • the message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the EEC 890 may further comprise a storing module 892 configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • the EEC 890 may further comprise a sending module 893 configured to send a message comprising information about at least one ACR scenario to be used in a next ACR to an AC.
  • FIG. 8g is a block diagram showing an AC according to another embodiment of the disclosure.
  • the AC 895 may comprise a receiving module 896 configured to receive a message from an EEC in an ACR scenario.
  • the message may comprise information about at least one ACR scenario to be used in a next ACR.
  • the AC 895 may further comprise a storing module 897 configured to store the information about the at least one ACR scenario to be used in the next ACR.
  • a decision to perform ACR in the ACR scenario is made by a source EES or a source EAS.
  • the EES, EEC, AC, or EAS may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the EES, EEC, AC, or EAS in the communication system.
  • the introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • Embodiments of the present disclosure provide a communication system including a host computer including: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device.
  • the cellular network includes a network node such as a base station, EES, EAS, etc., and/or the terminal device such as the AC or EEC above mentioned.
  • the system further includes the terminal device.
  • the terminal device is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the terminal device includes processing circuitry configured to execute a client application associated with the host application.
  • Embodiments of the present disclosure also provide a communication system including a host computer including: a communication interface configured to receive user data originating from a transmission from a terminal device; a base station. The transmission is from the terminal device to the base station.
  • the processing circuitry of the host computer is configured to execute a host application.
  • the terminal device is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • FIG. 9 is a schematic showing a wireless network in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIG. 9.
  • the wireless network of FIG. 9 only depicts network 1006, network nodes 1060 (corresponding to network side node) and 1060b, and WDs (corresponding to terminal device) 1010, 1010b, and 1010c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 1060 and wireless device (WD) 1010 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM) , Universal Mobile Telecommunications System (UMTS) , Long Term Evolution (LTE) , and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBe
  • Network 1006 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs) , packet data networks, optical networks, wide-area networks (WANs) , local area networks (LANs) , wireless local area networks (WLANs) , wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks
  • wireless networks metropolitan area networks, and other networks to enable communication between devices.
  • Network node 1060 and WD 1010 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points) , base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs) ) .
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs) , sometimes referred to as Remote Radio Heads (RRHs) .
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS) .
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs) , core network nodes (e.g., MSCs, MMEs) , O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs) , and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes
  • SON nodes e.g., SON nodes
  • positioning nodes e.g.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 1060 includes processing circuitry 1070, device readable medium 1080, interface 1090, auxiliary equipment 1084, power source 1086, power circuitry 1087, and antenna 1062.
  • network node 1060 illustrated in the example wireless network of FIG. 9 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 1060 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1080 may comprise multiple separate hard drives as well as multiple RAM modules) .
  • network node 1060 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc. ) , which may each have their own respective components.
  • network node 1060 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s .
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 1060 may be configured to support multiple radio access technologies (RATs) .
  • RATs radio access technologies
  • Network node 1060 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1060, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1060.
  • Processing circuitry 1070 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1070 may include processing information obtained by processing circuitry 1070 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 1070 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 1070 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1060 components, such as device readable medium 1080, network node 1060 functionality.
  • processing circuitry 1070 may execute instructions stored in device readable medium 1080 or in memory within processing circuitry 1070. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 1070 may include a system on a chip (SOC) .
  • SOC system on a chip
  • processing circuitry 1070 may include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074.
  • radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074 may be on separate chips (or sets of chips) , boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on the same chip or set of chips, boards, or units
  • processing circuitry 1070 executing instructions stored on device readable medium 1080 or memory within processing circuitry 1070.
  • some or all of the functionality may be provided by processing circuitry 1070 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 1070 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1070 alone or to other components of network node 1060, but are enjoyed by network node 1060 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 1080 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1070.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital
  • Device readable medium 1080 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1070 and, utilized by network node 1060.
  • Device readable medium 1080 may be used to store any calculations made by processing circuitry 1070 and/or any data received via interface 1090.
  • processing circuitry 1070 and device readable medium 1080 may be considered to be integrated.
  • Interface 1090 is used in the wired or wireless communication of signalling and/or data between network node 1060, network 1006, and/or WDs 1010. As illustrated, interface 1090 comprises port (s) /terminal (s) 1094 to send and receive data, for example to and from network 1006 over a wired connection. Interface 1090 also includes radio front end circuitry 1092 that may be coupled to, or in certain embodiments a part of, antenna 1062. Radio front end circuitry 1092 comprises filters 1098 and amplifiers 1096. Radio front end circuitry 1092 may be connected to antenna 1062 and processing circuitry 1070. Radio front end circuitry may be configured to condition signals communicated between antenna 1062 and processing circuitry 1070.
  • Radio front end circuitry 1092 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1092 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1098 and/or amplifiers 1096. The radio signal may then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 may collect radio signals which are then converted into digital data by radio front end circuitry 1092. The digital data may be passed to processing circuitry 1070. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 1060 may not include separate radio front end circuitry 1092, instead, processing circuitry 1070 may comprise radio front end circuitry and may be connected to antenna 1062 without separate radio front end circuitry 1092.
  • processing circuitry 1070 may comprise radio front end circuitry and may be connected to antenna 1062 without separate radio front end circuitry 1092.
  • all or some of RF transceiver circuitry 1072 may be considered a part of interface 1090.
  • interface 1090 may include one or more ports or terminals 1094, radio front end circuitry 1092, and RF transceiver circuitry 1072, as part of a radio unit (not shown) , and interface 1090 may communicate with baseband processing circuitry 1074, which is part of a digital unit (not shown) .
  • Antenna 1062 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1062 may be coupled to radio front end circuitry 1090 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1062 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1062 may be separate from network node 1060 and may be connectable to network node 1060 through an interface or port.
  • Antenna 1062, interface 1090, and/or processing circuitry 1070 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1062, interface 1090, and/or processing circuitry 1070 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 1087 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1060 with power for performing the functionality described herein. Power circuitry 1087 may receive power from power source 1086. Power source 1086 and/or power circuitry 1087 may be configured to provide power to the various components of network node 1060 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component) . Power source 1086 may either be included in, or external to, power circuitry 1087 and/or network node 1060.
  • network node 1060 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1087.
  • power source 1086 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1087. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node 1060 may include additional components beyond those shown in FIG. 9 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 1060 may include user interface equipment to allow input of information into network node 1060 and to allow output of information from network node 1060. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1060.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE) .
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA) , a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a smart device, a wireless customer-premise equipment (CPE) , a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • smart device a wireless customer-premise equipment (CPE)
  • CPE wireless customer-premise equipment
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V) , vehicle-to-infrastructure (V2I) , vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc. ) personal wearables (e.g., watches, fitness trackers, etc. ) .
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 1010 includes antenna 1011, interface 1014, processing circuitry 1020, device readable medium 1030, user interface equipment 1032, auxiliary equipment 1034, power source 1036 and power circuitry 1037.
  • WD 1010 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1010, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1010.
  • Antenna 1011 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1014.
  • antenna 1011 may be separate from WD 1010 and be connectable to WD 1010 through an interface or port.
  • Antenna 1011, interface 1014, and/or processing circuitry 1020 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna 1011 may be considered an interface.
  • interface 1014 comprises radio front end circuitry 1012 and antenna 1011.
  • Radio front end circuitry 1012 comprise one or more filters 1018 and amplifiers 1016.
  • Radio front end circuitry 1014 is connected to antenna 1011 and processing circuitry 1020, and is configured to condition signals communicated between antenna 1011 and processing circuitry 1020.
  • Radio front end circuitry 1012 may be coupled to or a part of antenna 1011.
  • WD 1010 may not include separate radio front end circuitry 1012; rather, processing circuitry 1020 may comprise radio front end circuitry and may be connected to antenna 1011.
  • some or all of RF transceiver circuitry 1022 may be considered a part of interface 1014.
  • Radio front end circuitry 1012 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1012 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1018 and/or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect radio signals which are then converted into digital data by radio front end circuitry 1012. The digital data may be passed to processing circuitry 1020. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 1020 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1010 components, such as device readable medium 1030, WD 1010 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry 1020 may execute instructions stored in device readable medium 1030 or in memory within processing circuitry 1020 to provide the functionality disclosed herein.
  • processing circuitry 1020 includes one or more of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 1020 of WD 1010 may comprise a SOC.
  • RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 1024 and application processing circuitry 1026 may be combined into one chip or set of chips, and RF transceiver circuitry 1022 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1022 and baseband processing circuitry 1024 may be on the same chip or set of chips, and application processing circuitry 1026 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 1022 may be a part of interface 1014.
  • RF transceiver circuitry 1022 may condition RF signals for processing circuitry 1020.
  • processing circuitry 1020 executing instructions stored on device readable medium 1030, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 1020 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 1020 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1020 alone or to other components of WD 1010, but are enjoyed by WD 1010 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 1020 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1020, may include processing information obtained by processing circuitry 1020 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1010, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 1020 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1010, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 1030 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1020.
  • Device readable medium 1030 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM) ) , mass storage media (e.g., a hard disk) , removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1020.
  • processing circuitry 1020 and device readable medium 1030 may be considered to be integrated.
  • User interface equipment 1032 may provide components that allow for a human user to interact with WD 1010. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1032 may be operable to produce output to the user and to allow the user to provide input to WD 1010. The type of interaction may vary depending on the type of user interface equipment 1032 installed in WD 1010. For example, if WD 1010 is a smart phone, the interaction may be via a touch screen; if WD 1010 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected) .
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 1032 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1032 is configured to allow input of information into WD 1010, and is connected to processing circuitry 1020 to allow processing circuitry 1020 to process the input information. User interface equipment 1032 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1032 is also configured to allow output of information from WD 1010, and to allow processing circuitry 1020 to output information from WD 1010. User interface equipment 1032 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1032, WD 1010 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 1034 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1034 may vary depending on the embodiment and/or scenario.
  • Power source 1036 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet) , photovoltaic devices or power cells, may also be used.
  • WD 1010 may further comprise power circuitry 1037 for delivering power from power source 1036 to the various parts of WD 1010 which need power from power source 1036 to carry out any functionality described or indicated herein.
  • Power circuitry 1037 may in certain embodiments comprise power management circuitry.
  • Power circuitry 1037 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1010 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 1037 may also in certain embodiments be operable to deliver power from an external power source to power source 1036. This may be, for example, for the charging of power source 1036. Power circuitry 1037 may perform any formatting, converting, or other modification to the power from power source 1036 to make the power suitable for the respective components of WD 1010 to which power is supplied.
  • FIG. 10 is a schematic showing a user equipment in accordance with some embodiments.
  • FIG. 10 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller) .
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter) .
  • UE 1100 may be any UE identified by the 3rd Generation Partnership Project (3GPP) , including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 1100 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP) , such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • UE 1100 includes processing circuitry 1101 that is operatively coupled to input/output interface 1105, radio frequency (RF) interface 1109, network connection interface 1111, memory 1115 including random access memory (RAM) 1117, read-only memory (ROM) 1119, and storage medium 1121 or the like, communication subsystem 1131, power source 1133, and/or any other component, or any combination thereof.
  • Storage medium 1121 includes operating system 1123, application program 1125, and data 1127. In other embodiments, storage medium 1121 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIG. 10, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 1101 may be configured to process computer instructions and data.
  • Processing circuitry 1101 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc. ) ; programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP) , together with appropriate software; or any combination of the above.
  • the processing circuitry 1101 may include two central processing units (CPUs) . Data may be information in a form suitable for use by a computer.
  • input/output interface 1105 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 1100 may be configured to use an output device via input/output interface 1105.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 1100.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 1100 may be configured to use an input device via input/output interface 1105 to allow a user to capture information into UE 1100.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc. ) , a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 1109 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 1111 may be configured to provide a communication interface to network 1143a.
  • Network 1143a may encompass wired and/or wireless networks such as a local-area network (LAN) , a wide-area network (WAN) , a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • LAN local-area network
  • WAN wide-area network
  • network 1143a may comprise a Wi-Fi network.
  • Network connection interface 1111 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 1111 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like) .
  • the transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 1117 may be configured to interface via bus 1102 to processing circuitry 1101 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 1119 may be configured to provide computer instructions or data to processing circuitry 1101.
  • ROM 1119 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O) , startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 1121 may be configured to include operating system 1123, application program 1125 such as a web browser application, a widget or gadget engine or another application, and data file 1127.
  • Storage medium 1121 may store, for use by UE 1100, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 1121 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID) , floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM) , synchronous dynamic random access memory (SDRAM) , external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 1121 may allow UE 1100 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1121, which may comprise a device readable medium.
  • processing circuitry 1101 may be configured to communicate with network 1143b using communication subsystem 1131.
  • Network 1143a and network 1143b may be the same network or networks or different network or networks.
  • Communication subsystem 1131 may be configured to include one or more transceivers used to communicate with network 1143b.
  • communication subsystem 1131 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 1133 and/or receiver 1135 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like) . Further, transmitter 1133 and receiver 1135 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 1143b may encompass wired and/or wireless networks such as a local-area network (LAN) , a wide-area network (WAN) , a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 1143b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 1113 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1100.
  • communication subsystem 1131 may be configured to include any of the components described herein.
  • processing circuitry 1101 may be configured to communicate with any of such components over bus 1102.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1101 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 1101 and communication subsystem 1131.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 11 is a schematic showing a virtualization environment in accordance with some embodiments.
  • FIG. 11 is a schematic block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks) .
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes 1230. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node) , then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 1220 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. ) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 1220 are run in virtualization environment 1200 which provides hardware 1230 comprising processing circuitry 1260 and memory 1290-1.
  • Memory 1290-1 contains instructions 1295 executable by processing circuitry 1260 whereby application 1220 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 1200 comprises general-purpose or special-purpose network hardware devices 1230 comprising a set of one or more processors or processing circuitry 1260, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs) , or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 1260 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs) , or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 1290-1 which may be non-persistent memory for temporarily storing instructions 1295 or software executed by processing circuitry 1260.
  • Each hardware device may comprise one or more network interface controllers (NICs) 1270, also known as network interface cards, which include physical network interface 1280.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 1290-2 having stored therein software 1295 and/or instructions executable by processing circuitry 1260.
  • Software 1295 may include any type of software including software for instantiating one or more virtualization layers 1250 (also referred to as hypervisors) , software to execute virtual machines 1240 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 1240 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of the instance of virtual appliance 1220 may be implemented on one or more of virtual machines 1240, and the implementations may be made in different ways.
  • processing circuitry 1260 executes software 1295 to instantiate the hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM) .
  • Virtualization layer 1250 may present a virtual operating platform that appears like networking hardware to virtual machine 1240.
  • hardware 1230 may be a standalone network node with generic or specific components. Hardware 1230 may comprise antenna 12225 and may implement some functions via virtualization. Alternatively, hardware 1230 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE) ) where many hardware nodes work together and are managed via management and orchestration (MANO) 12100, which, among others, oversees lifecycle management of applications 1220.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 1240 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 1240, and that part of hardware 1230 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1240, forms a separate virtual network elements (VNE) .
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 12200 that each include one or more transmitters 12220 and one or more receivers 12210 may be coupled to one or more antennas 12225.
  • Radio units 12200 may communicate directly with hardware nodes 1230 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 12230 which may alternatively be used for communication between the hardware nodes 1230 and radio units 12200.
  • FIG. 12 is a schematic showing a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network 1310, such as a 3GPP-type cellular network, which comprises access network 1311, such as a radio access network, and core network 1314.
  • Access network 1311 comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c.
  • Each base station 1312a, 1312b, 1312c is connectable to core network 1314 over a wired or wireless connection 1315.
  • a UE 1391 located in coverage area 1313c is configured to wirelessly connect to, or be paged by, the corresponding base station 1312c.
  • a relay UE 1392 in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a. While a plurality of UEs 1391, 1392 are illustrated in this example, 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 1312a or 1312b or 1312c .
  • Telecommunication network 1310 is itself connected to host computer 1330, 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 1330 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 1321 and 1322 between telecommunication network 1310 and host computer 1330 may extend directly from core network 1314 to host computer 1330 or may go via an optional intermediate network 1320.
  • Intermediate network 1320 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1320, if any, may be a backbone network or the Internet; in particular, intermediate network 1320 may comprise two or more sub-networks (not shown) .
  • the communication system of FIG. 12 as a whole enables connectivity between the connected UEs 1391, 1392 and host computer 1330.
  • the connectivity may be described as an over-the-top (OTT) connection 1350.
  • Host computer 1330 and the connected UEs 1391, 1392 are configured to communicate data and/or signalling via OTT connection 1350, using access network 1311, core network 1314, any intermediate network 1320 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 1350 may be transparent in the sense that the participating communication devices through which OTT connection 1350 passes are unaware of routing of uplink and downlink communications.
  • base station 1312a or 1312b or 1312c may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1330 to be forwarded (e.g., handed over) to a connected UE 1391.
  • base station 1312a or 1312b or 1312c need not be aware of the future routing of an outgoing uplink communication originating from the UE 1391 towards the host computer 1330.
  • FIG. 13 is a schematic showing a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 1410 comprises hardware 1415 including communication interface 1416 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1400.
  • Host computer 1410 further comprises processing circuitry 1418, which may have storage and/or processing capabilities.
  • processing circuitry 1418 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 1410 further comprises software 1411, which is stored in or accessible by host computer 1410 and executable by processing circuitry 1418.
  • Software 1411 includes host application 1412.
  • Host application 1412 may be operable to provide a service to a remote user, such as UE 1430 connecting via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the remote user, host application 1412 may provide user data which is transmitted using OTT connection 1450.
  • Communication system 1400 further includes base station 1420 provided in a telecommunication system and comprising hardware 1425 enabling it to communicate with host computer 1410 and with UE 1430.
  • Hardware 1425 may include communication interface 1426 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1400, as well as radio interface 1427 for setting up and maintaining at least wireless connection 1470 with UE 1430 located in a coverage area (not shown in FIG. 13) served by base station 1420.
  • Communication interface 1426 may be configured to facilitate connection 1460 to host computer 1410. Connection 1460 may be direct or it may pass through a core network (not shown in FIG. 13) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1425 of base station 1420 further includes processing circuitry 1428, 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 1420 further has software 1421 stored internally or accessible via an external connection.
  • Communication system 1400 further includes UE 1430 already referred to. Its hardware 1435 may include radio interface 1437 configured to set up and maintain wireless connection 1470 with a base station serving a coverage area in which UE 1430 is currently located. Hardware 1435 of UE 1430 further includes processing circuitry 1438, 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 1430 further comprises software 1431, which is stored in or accessible by UE 1430 and executable by processing circuitry 1438. Software 1431 includes client application 1432. Client application 1432 may be operable to provide a service to a human or non-human user via UE 1430, with the support of host computer 1410.
  • an executing host application 1412 may communicate with the executing client application 1432 via OTT connection 1450 terminating at UE 1430 and host computer 1410.
  • client application 1432 may receive request data from host application 1412 and provide user data in response to the request data.
  • OTT connection 1450 may transfer both the request data and the user data.
  • Client application 1432 may interact with the user to generate the user data that it provides.
  • host computer 1410, base station 1420 and UE 1430 illustrated in FIG. 13 may be similar or identical to host computer 1330, one of base stations 1312a, 1312b, 1312c and one of UEs 1391, 1392 of FIG. 12, respectively.
  • the inner workings of these entities may be as shown in FIG. 13 and independently, the surrounding network topology may be that of FIG. 12.
  • OTT connection 1450 has been drawn abstractly to illustrate the communication between host computer 1410 and UE 1430 via base station 1420, 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 1430 or from the service provider operating host computer 1410, or both. While OTT connection 1450 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 1470 between UE 1430 and base station 1420 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 1430 using OTT connection 1450, in which wireless connection 1470 forms the last segment. More precisely, in some embodiments herein, it can address KI#19 of 3GPP TR 23.700-98 V1.1.1 in the S-EAS decided ACR scenario which allows the S-EAS to determine the ACR scenario (s) or request the S-EES to determine the ACR scenario (s) to be used.
  • the proposed solution provides a proactive way to decrease the system complexity for the subsequent ACR during Data network side triggered ACR.
  • ideal situation would be that AC, EEC, EES and EAS support and only support exactly the same ACR scenarios. But in reality, it could be that a suitable T-EAS (satisfying AC’s KPI (Key Performance Indicator) requirement) supports more ACR scenarios than S-EAS and S-EES, or AC and EEC. Then the S-EES decided ACR scenario selection solution is useful to make ACR scenario selection for the suitable T-EAS and notify the corresponding entities about the selection.
  • 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 1450 may be implemented in software 1411 and hardware 1415 of host computer 1410 or in software 1431 and hardware 1435 of UE 1430, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1450 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 1411, 1431 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1450 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not affect base station 1420, and it may be unknown or imperceptible to base station 1420. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signalling facilitating host computer 1410’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 1411 and 1431 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1450 while it monitors propagation times, errors etc.
  • FIG. 14 is a schematic showing 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 FIGs. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 14 will be included in this section.
  • the host computer provides user data.
  • substep 1511 (which may be optional) of step 1510, 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.
  • step 1530 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 1540 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 15 is a schematic showing 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. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 15 will be included in this section.
  • 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 1630 (which may be optional) , the UE receives the user data carried in the transmission.
  • FIG. 16 is a schematic showing methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG. 16 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 FIGs. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 16 will be included in this section.
  • step 1710 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data.
  • substep 1721 (which may be optional) of step 1720, the UE provides the user data by executing a client application.
  • substep 1711 (which may be optional) of step 1710, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 1730 (which may be optional) , transmission of the user data to the host computer.
  • step 1740 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 17 is a schematic showing methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG. 17 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 FIGs. 12 and 13. For simplicity of the present disclosure, only drawing references to FIG. 17 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.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent un procédé et un appareil de sélection de scénario ACR. Un procédé mis en œuvre par un premier nœud de réseau consiste à décider d'effectuer une relocalisation de contexte d'application (ACR). Le procédé consiste également à envoyer un premier message à un second nœud de réseau. Le premier message comprend des informations pour demander au second nœud de réseau de sélectionner au moins un scénario ACR à utiliser dans une ACR suivante.
PCT/CN2023/112564 2022-08-16 2023-08-11 Procédé et appareil de sélection de scénario acr WO2024037452A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2022112698 2022-08-16
CNPCT/CN2022/112698 2022-08-16

Publications (1)

Publication Number Publication Date
WO2024037452A1 true WO2024037452A1 (fr) 2024-02-22

Family

ID=89940762

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112564 WO2024037452A1 (fr) 2022-08-16 2023-08-11 Procédé et appareil de sélection de scénario acr

Country Status (1)

Country Link
WO (1) WO2024037452A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852948A (zh) * 2021-07-07 2021-12-28 华为技术有限公司 发送应用上下文迁移信息的方法和装置
WO2022070042A1 (fr) * 2020-09-29 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Influence de la fonction d'application dans la relocalisation d'un contexte d'application

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022070042A1 (fr) * 2020-09-29 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Influence de la fonction d'application dans la relocalisation d'un contexte d'application
CN113852948A (zh) * 2021-07-07 2021-12-28 华为技术有限公司 发送应用上下文迁移信息的方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.558, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V17.4.0, 13 June 2022 (2022-06-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 167, XP052182852 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhanced architecture for enabling Edge Applications; (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-98, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.1.1, 15 July 2022 (2022-07-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 158, XP052183765 *
WENLIANG XU, ERICSSON: "ACR scenario selection in DN", 3GPP DRAFT; S6-222091; TYPE PCR; FS_EEDGEAPP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 6, no. Online; 20220822 - 20220831, 16 August 2022 (2022-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052186885 *

Similar Documents

Publication Publication Date Title
KR102554326B1 (ko) V2x 통신들을 위한 애플리케이션 서버 및/또는 서비스들의 발견을 위한 방법들, 장치 및 컴퓨터 판독가능한 매체
US20230421641A1 (en) Methods providing dynamic nef tunnel allocation and related network nodes/functions
WO2021227833A1 (fr) Procédé et appareil de fourniture de service périphérique
WO2022127867A1 (fr) Procédé et appareil de commande de données d'apprentissage
KR102445901B1 (ko) 지능형 교통 시스템(its) 메시지 분배를 위한 방법, 장치 및 컴퓨터 판독 가능 매체
WO2021164659A1 (fr) Procédé et appareil de protection de la confidentialité
WO2023274149A1 (fr) Procédé, appareil d'assurance d'accord sur le niveau de service dans un réseau mobile
US20230328677A1 (en) Handling registrations of a user equipment in different communication networks
WO2024037452A1 (fr) Procédé et appareil de sélection de scénario acr
US20210227382A1 (en) To Increase Security of Dual Connectivity
WO2023241470A1 (fr) Procédé et appareil de gestion d'informations de session d'application en informatique à la frontière
WO2023241294A1 (fr) Procédé et appareil de relocalisation de contexte d'application
WO2024022278A1 (fr) Procédé et appareil de gestion de mobilité
WO2023066286A1 (fr) Procédé et appareil de commande de service
WO2023179376A1 (fr) Procédé et appareil de découverte de nœud relais
WO2024037405A1 (fr) Procédé et appareil pour une continuité de service
WO2024022420A1 (fr) Procédé et appareil d'abonnement par défaut à des notifications
WO2023056788A1 (fr) Procédé, appareil de continuité de service d'exposition de réseau sur l'ensemble de réseaux de données périphériques
WO2024027630A1 (fr) Procédé et appareil d'alignement d'autorisation
WO2023227024A1 (fr) Procédé et appareil de sélection de trajet
WO2023083264A1 (fr) Procédé et appareil pour service de multidiffusion/diffusion
WO2023216193A1 (fr) Procédé et appareil de communication sur surface intelligente reconfigurable (ris)
WO2024012064A1 (fr) Procédé et appareil de rapport d'événement
US20240114444A1 (en) Network slice isolation via network slice lists
WO2023164888A1 (fr) Procédé et appareil pour la détermination d'un sinr mu-mimo dl

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: 23854353

Country of ref document: EP

Kind code of ref document: A1