WO2025002402A1 - Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application - Google Patents

Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application Download PDF

Info

Publication number
WO2025002402A1
WO2025002402A1 PCT/CN2024/102554 CN2024102554W WO2025002402A1 WO 2025002402 A1 WO2025002402 A1 WO 2025002402A1 CN 2024102554 W CN2024102554 W CN 2024102554W WO 2025002402 A1 WO2025002402 A1 WO 2025002402A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
network
subscription
response
domain
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2024/102554
Other languages
English (en)
Inventor
Junjun Wang
Hao Zeng
Jingrui TAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to CN202480042879.8A priority Critical patent/CN121399986A/zh
Priority to EP24831029.4A priority patent/EP4710583A1/fr
Publication of WO2025002402A1 publication Critical patent/WO2025002402A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/086—Access security using security domains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

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 User Equipment (UE) domain information exposure to application function.
  • UE User Equipment
  • 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 V17.7.0 specifies system architecture for the 5th Generation Mobile Communication Technology (5G) System (5GS) .
  • Figure 1 shows the non-roaming architecture for Service Exposure for Evolved Packet Core (EPC) -5th Generation Core (5GC) Interworking.
  • EPC Evolved Packet Core
  • 5GC 5th Generation Core
  • 3GPP TS29.503 V17.9.0 specifies Unified Data Management Services.
  • Network Exposure Function can subscribe Core Network (CN) Type Change from Unified Data Management (UDM) .
  • a 5th Generation Mobile Communication Technology (5G) subscriber has 5G/4th Generation Mobile Communication Technology (4G) switching capability when UE moves between 5GC and EPC. This improves the UE-Side user experience.
  • SCEF/NEF Service Capability Exposure Function/Network Exposure Function
  • AF Application Function
  • APIs programmable Application Programming Interfaces
  • NEF can subscribe Core Network (CN) Type Change from Unified Data Management (UDM) .
  • CN Core Network
  • UDM Unified Data Management
  • AF doesn’ t know the Core Network Type for a UE.
  • 3GPP does not define a solution for NEF/SCEF/SCEF+NEF to distinguish subscription domain to know if the UE is 4G subscription or 5G subscription, the consequent is that SCEF+NEF cannot return valid subscription domain information to AF.
  • SCEF+NEF cannot return valid subscription domain information to AF.
  • SCEF+NEF it doesn’ t know if it need to interact with 4GC or 5GC.
  • the core network type is a kind of network domain information.
  • the core network type and subscription domain mentioned above belong to UE domain information.
  • the embodiments of the present disclosure propose an solution for exposing UE domain information to an application function.
  • a method performed by a first network node in Communication Network may comprise receiving a first request from a second network node.
  • the first request it may comprise a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • the method may further comprise determining a UE domain information according to the received UE ID.
  • the method may further comprise sending a first response to the second network node.
  • the first response may comprise the determined UE domain information.
  • the UE domain information may comprise core network type and subscription domain.
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • the subscription domain may comprise at least one of 4th Generation Mobile Communication Technology subscription (4G subscription) , and 5th Generation Mobile Communication Technology subscription (5G subscription) .
  • the first network node may comprise a Network Exposure Function (NEF) , or a Service Capability Exposure Function (SCEF) , or a combination of NEF and SCEF.
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • the second network node may comprise an Application Function (AF) .
  • AF Application Function
  • the third network node may comprise a Network Repository Function (NRF) .
  • NRF Network Repository Function
  • the fourth network node may comprise a Unified Data Management (UDM) , or a combination of UDM and Home Subscriber Server (HSS) .
  • UDM Unified Data Management
  • HSS Home Subscriber Server
  • a method performed by a second network node in Communication Network may comprise sending a first request to a first network node.
  • the first request may comprise a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • the method may further comprise receiving a first response, from the first network node.
  • the first response may comprise a UE domain information according to the UE ID.
  • the UE domain information may comprise core network type and subscription domain.
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • the subscription domain may comprise at least one of 4th Generation Mobile Communication Technology subscription (4G subscription) , and 5th Generation Mobile Communication Technology subscription (5G subscription) .
  • the first network node may comprise a Network Exposure Function (NEF) , or a Service Capability Exposure Function (SCEF) , or a combination of NEF and SCEF.
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • the second network node may comprise an Application Function (AF) .
  • AF Application Function
  • an apparatus which may be implemented as a network entity.
  • the apparatus may comprise one or more processors and one or more memories storing computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the first aspect of the present disclosure.
  • an apparatus which may be implemented as a network entity.
  • the apparatus may comprise one or more processors and one or more memories storing computer program codes.
  • the one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the second aspect of the present disclosure.
  • a computer-readable medium having computer program codes embodied thereon which, when executed on a computer, cause the computer to perform any step of the method according to the first aspect or the second aspect of the present disclosure.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. It proposes a solution for exposing UE domain information to an application function. Through the proposed method, AF can provide the fine-grained granularity service, based on the exposure of the UE domain information.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 1 shows a Service Exposure Architecture for EPC-5GC Interworking
  • FIG. 2 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 3 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 4 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 5 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 6 shows an example of a communication system according to an embodiment of the disclosure
  • FIG. 7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • FIG. 8 is a block diagram showing a network function according to an embodiment of the disclosure.
  • FIG. 9 is a block diagram showing a network function according to an embodiment of the disclosure.
  • FIG. 10 is a block diagram of a host according to an embodiment of the disclosure.
  • FIG. 11 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection according to an embodiment of the disclosure.
  • the term “network” refers to a network following any suitable communication standards such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, 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
  • 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 technology such as Universal Terrestrial Radio Access (UTRA) , etc.
  • 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 device or “network node” refers to any suitable network function (NF) which can be implemented in a network function (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 node may comprise different types of NFs for example depending on a specific network.
  • terminal device or “user equipment (UE) ” refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal 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 Universal Serial Bus (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
  • 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 5G subscriber has 5G/4G switching capability when UE moves between 5GC and EPC. This improves the UE-Side user experience.
  • SCEF/NEF Service Capability Exposure Function, Network Exposure Function
  • AF Application Function
  • APIs programmable Application Programming Interfaces
  • MonitoringType is given in below table 1.
  • NEF can subscribe Core Network (CN) Type Change from Unified Data Management (UDM) .
  • CN Core Network
  • UDM Unified Data Management
  • AF doesn’ t know the Core Network Type for a UE. There is no mechanism and data model between NEF and AF to let AF get the Core Network Type for a UE.
  • 3GPP does not define a solution for SCEF+NEF/NEF/SCEF to distinguish subscription domain to know if the UE is 4G subscription or 5G subscription, the consequent is that SCEF+NEF/NEF/SCEF cannot return valid subscription domain information to AF.
  • SCEF+NEF it doesn’ t know if it need to interact with 4GC or 5GC.
  • the core network type and subscription domain mentioned above belong to UE domain information.
  • the core network type is a kind of network domain information.
  • the UE domain information may comprise at least one of subscription domain, and network domain information (core network type) .
  • the UE domain information may comprise at least one of subscription domain, and core network type.
  • the embodiments of the present disclosure propose an solution for exposing UE domain information to an application function according to a UE ID.
  • Fig. 1 shows an architecture for Service Exposure for EPC-5GC Interworking, which is defined in 3GPP TS 23.501 v17.7.0. If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF node for Service Capability Exposure.
  • EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc.
  • 5GC Interface represents southbound interfaces between NEF and 5GC Network Functions e.g.N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc.
  • the north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node.
  • FIG. 2 shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in/as or communicatively coupled to a first network node.
  • the apparatus may provide means for accomplishing various parts of the method 200 as well as means for accomplishing other processes in conjunction with other components.
  • the first network node may receive a first request from a second network node.
  • the first request may comprise a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • UE ID User Equipment Identifier
  • the first network node may determine a UE domain information according to the received UE ID.
  • the first network node may send a first response to the second network node.
  • the first response may comprise the determined UE domain information.
  • the first request may be any suitable message, such as a HTTP Post request, a HTTP Get request, etc.
  • the first response may be any suitable message, such as a HTTP post response, a HTTP Get response, etc.
  • the UE ID may be any suitable information which can be used to identify the one or more user equipment devices, such as it may comprise at least one of UE address (such as IP address or MAC (Media Access Control) address) , Generic Public Subscription Identifier (GPSI) , Subscription Permanent Identifier (SUPI) , MobileStationIntegratedServicesDigitalNetwork (MSISDN) , external identifier (ID) .
  • UE address such as IP address or MAC (Media Access Control) address
  • GPSI Generic Public Subscription Identifier
  • SUPI Subscription Permanent Identifier
  • MSISDN MobileStationIntegratedServicesDigitalNetwork
  • ID external identifier
  • the first network node may be a physical entity or a virtualized network function.
  • the first network node may be any suitable network device or node or entity or function (physical or virtual) which can provide a network exposure function or service capability exposure function.
  • the first network node may provide a means to securely expose the services and capabilities provided by the network interfaces.
  • the first network node may provide a means for the discovery of the exposed services and capabilities.
  • the first network node may provide access to network capabilities through homogenous network application programming interfaces (e.g.Network APIs) .
  • the first network node may abstract the services from the underlying network interfaces and protocols.
  • the first network node may be NEF as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the first network node may be SCEF. In another embodiment, the first network node may comprise a combination of NEF and SCEF.
  • the second network node may be a physical entity or a virtualized network function.
  • the network node may be any suitable network device or node or entity or function (physical or virtual) which can provide an application function.
  • the second network node may be Application Function (AF) as described in 3GPP TS 23.501 V17.7.0.
  • the second network node may be service capability server (SCS) /application server (AS) as described in 3GPP TS 23.682 V17.3.0.
  • CN Type Core Network Type
  • cnType Core network Type
  • CnType Core network Type
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • the CnType may comprise three different kinds of core network types of a UE: EPC, 5GC, Dual EPC and 5GC.
  • the three different types of CnType may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the core network type may comprise at least one of SINGLE_4G, SINGLE_5G, DUAL_4G5G. The enumeration of it is shown in Table 2b.
  • EPC corresponds to “SINGLE_4G”
  • 5GC corresponds to “SINGLE_5G”
  • 5GC corresponds to “DUAL_4G5G” .
  • the three different types of core network type may take any suitable names to denote the three kinds of registration type in core network.
  • Table 3 shows an enumeration example of subscription domain.
  • the subscription domain may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the method may further comprise determining the subscription domain as 4G subscription and the first core network type as EPC.
  • the method may further comprise sending a third request, to the fourth network node, to subscribe the core network type change according to the UE ID.
  • the method may further comprise receiving a third response from the fourth network node, wherein the third response indicating the core network type according to the UE ID, determining the core network type comprised in the UE domain information as the received core network type in the third response according to the UE ID and the subscription domain as 5G subscription.
  • the method may further comprise receiving a first message from the fourth network node, wherein the first message comprises an updated core network type according to the UE ID, determining the core network type comprised in the UE domain information as the updated core network type received in the first message and the subscription domain as 5G subscription.
  • the method may further comprise sending a second message to the second network node.
  • the second message may comprise an updated UE domain information.
  • the updated UE domain information may comprise the updated core network type and subscription domain.
  • the first request may be a network exposure function event exposure subscribe request.
  • the first request is a Nnef_EventExposure_Subscribe request.
  • the first response may be a network exposure function event exposure subscribe response.
  • the first response is a Nnef_EventExposure_Subscribe response.
  • the first message may be a notification message.
  • the first message is a Nudm_EventExposure_Notify message.
  • the second message may be a notification message.
  • the first message is a Nnef_EventExposure Notification.
  • the third network node may comprise a Network Repository Function (NRF) .
  • NRF Network Repository Function
  • the fourth network node may comprise a Unified Data Management (UDM) , or a combination of UDM and Home Subscriber Server (HSS) .
  • UDM Unified Data Management
  • HSS Home Subscriber Server
  • FIG. 3 shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in/as or communicatively coupled to a first network node.
  • the apparatus may provide means for accomplishing various parts of the method 300 as well as means for accomplishing other processes in conjunction with other components.
  • the first request may be any suitable message, such as a HTTP Post request, a HTTP Get request, etc.
  • the UE ID may be any suitable information which can be used to identify the one or more user equipment devices, such as it may comprise at least one of UE address (such as IP address or MAC (Media Access Control) address) , Generic Public Subscription Identifier (GPSI) , Subscription Permanent Identifier (SUPI) , MobileStationIntegratedServicesDigitalNetwork (MSISDN) , external identifier (ID) .
  • UE address such as IP address or MAC (Media Access Control) address
  • GPSI Generic Public Subscription Identifier
  • SUPI Subscription Permanent Identifier
  • MSISDN MobileStationIntegratedServicesDigitalNetwork
  • ID external identifier
  • the first network node may further comprising determining a core network type and/or a subscription domain according to the received UE ID.
  • the first network node may be a physical entity or a virtualized network function.
  • the first network node may be any suitable network device or node or entity or function (physical or virtual) which can provide a network exposure function or service capability exposure function.
  • the first network node may provide a means to securely expose the services and capabilities provided by the network interfaces.
  • the first network node may provide a means for the discovery of the exposed services and capabilities.
  • the first network node may provide access to network capabilities through homogenous network application programming interfaces (e.g.Network APIs) .
  • the first network node may abstract the services from the underlying network interfaces and protocols.
  • the first network node may be NEF as described in 3GPP TS 23.501 V17.7.0. In another embodiment, the first network node may be SCEF. In another embodiment, the first network node may comprise a combination of NEF and SCEF.
  • the second network node may be a physical entity or a virtualized network function.
  • the network node may be any suitable network device or node or entity or function (physical or virtual) which can provide an application function.
  • the second network node may be Application Function (AF) as described in 3GPP TS 23.501 V17.7.0.
  • the second network node may be service capability server (SCS) /application server (AS) as described in 3GPP TS 23.682 V17.3.0.
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • CN Type Core Network Type
  • cnType Core network Type
  • CnType Core network Type
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • the CnType may comprise three different kinds of core network types of a UE: EPC, 5GC, Dual EPC and 5GC.
  • the three different types of CnType may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the core network type may comprise at least one of SINGLE_4G, SINGLE_5G, DUAL_4G5G. The enumeration of it is shown in Table 2b.
  • EPC corresponds to “SINGLE_4G”
  • 5GC corresponds to “SINGLE_5G”
  • 5GC corresponds to “DUAL_4G5G” .
  • the three different types of core network type may take any suitable names to denote the three kinds of registration type in core network.
  • the subscription domain for a UE may comprise 4th Generation Mobile Communication Technology subscription (4G subscription) , 5th Generation Mobile Communication Technology subscription (5G subscription) .
  • Table 3 shows an enumeration example of subscription domain.
  • the subscription domain may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the method may further comprise determining a core network type and a subscription domain according to the received UE ID comprises sending a second request to a third network node to discover if there exist a fourth network node service instance for the UE ID,receiving a second response from the third network node. The second response indicating whether there exist a fourth network node service instance for the UE ID.
  • the method may further comprise determining the subscription domain as 4G subscription an d the first core network type as “EPC” .
  • the method may further comprise sending a third request, to the fourth network node, to subscribe the core network type change according to the UE ID.
  • the method further may further comprise receiving a third response from the fourth network node, wherein the third response indicating the core network type according to the UE ID, determining the core network type as the received core network type in the third response according to the UE ID and the subscription domain as 5G subscription.
  • the method may further comprise receiving a first message from the fourth network node.
  • the first message may comprise a current core network type according to the UE ID.
  • the method further comprise determining the core network type as the updated core network type received in the first message and the subscription domain as 5G subscription, and sending a second message to the second network node.
  • the second message may comprise the determined core network type and the determined subscriber domain.
  • the first request may be a network exposure function event exposure subscribe request.
  • the first request is a Nnef_EventExposure_Subscribe request.
  • the first response may be a network exposure function event exposure subscribe response.
  • the first response is a Nnef_EventExposure_Subscribe response.
  • the first message may be a notification message.
  • the first message is a Nudm_EventExposure_Notify message.
  • the second message may be a notification message.
  • the first message is a Nnef_EventExposure Notification.
  • the third network node may comprise a Network Repository Function (NRF) .
  • NRF Network Repository Function
  • the fourth network node may comprise a Unified Data Management (UDM) , or a combination of UDM and Home Subscriber Server (HSS) .
  • UDM Unified Data Management
  • HSS Home Subscriber Server
  • FIG. 4 shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in/as or communicatively coupled to a second network node.
  • the apparatus may provide means for accomplishing various parts of the method 400 as well as means for accomplishing other processes in conjunction with other components.
  • the second network node may send a first request to a first network node.
  • the first request may comprise a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • UE ID User Equipment Identifier
  • the second network node may receive a first response, from the first network node.
  • the first response may comprise a UE domain information according to the UE ID.
  • the first request may be any suitable message, such as a HTTP Post request, a HTTP Get request, etc.
  • the first response may be any suitable message, such as a HTTP post response, a HTTP Get response, etc.
  • the UE ID may be any suitable information which can be used to identify the one or more user equipment devices, such as it may comprise at least one of UE address (such as IP address or MAC (Media Access Control) address) , Generic Public Subscription Identifier (GPSI) , Subscription Permanent Identifier (SUPI) , MobileStationIntegratedServicesDigitalNetwork (MSISDN) , external identifier (ID) .
  • UE address such as IP address or MAC (Media Access Control) address
  • GPSI Generic Public Subscription Identifier
  • SUPI Subscription Permanent Identifier
  • MSISDN MobileStationIntegratedServicesDigitalNetwork
  • ID external identifier
  • the second network node may be a physical entity or a virtualized network function.
  • the second network node may be any suitable network device or node or entity or function (physical or virtual) which can provide a network exposure function or service capability exposure function.
  • the second network node may be a physical entity or a virtualized network function.
  • the network node may be any suitable network device or node or entity or function (physical or virtual) which can provide an application function.
  • the second network node may be Application Function (AF) as described in 3GPP TS 23.501 V17.7.0.
  • the second network node may be service capability server (SCS) /application server (AS) as described in 3GPP TS 23.682 V17.3.0.
  • the first network node may comprise a Network Exposure Function (NEF) , or a Service Capability Exposure Function (SCEF) , or a combination of NEF and SCEF.
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • the UE domain information may comprise at least one of core network type, subscription domain.
  • the CnType may comprise three different kinds of core network types of a UE: EPC, 5GC, Dual EPC and 5GC.
  • the three different types of CnType may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the core network type may comprise at least one of SINGLE_4G, SINGLE_5G, DUAL_4G5G. The enumeration of it is shown in Table 2b.
  • EPC corresponds to “SINGLE_4G”
  • 5GC corresponds to “SINGLE_5G”
  • 5GC corresponds to “DUAL_4G5G” .
  • the three different types of core network type may take any suitable names to denote the three kinds of registration type in core network.
  • the subscription domain may comprise at least one of 4th Generation Mobile Communication Technology subscription (4G subscription) , 5th Generation Mobile Communication Technology subscription (5G subscription) .
  • 4G subscription 4th Generation Mobile Communication Technology subscription
  • 5G subscription 5th Generation Mobile Communication Technology subscription
  • the first request may be a network exposure function event exposure subscribe request.
  • the first request is a Nnef_EventExposure_Subscribe request.
  • the first response may be a network exposure function event exposure subscribe response.
  • the first response is a Nnef_EventExposure_Subscribe message.
  • the second message may be a notification message.
  • the first message is a Nnef_EventExposure Notification.
  • the method may further comprise receiving a second message from the first network node.
  • the second message may comprise an updated UE domain information core network type and the according to the UE ID.
  • the updated UE domain information may comprise an updated core network type and a subscription domain.
  • the first network node may comprise a Network Exposure Function (NEF) , or a Service Capability Exposure Function (SCEF) , or a combination of NEF and SCEF.
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • the second network node may comprise an Application Function (AF) .
  • AF Application Function
  • Fig. 5 shows an example of a communication system according to an embodiment of the disclosure. There are four network nodes.
  • the first network node may be a NEF, SCEF, or a combination of NEF+SCEF.
  • the second network node may be an Application Function (AF) .
  • AF Application Function
  • the third network node may be an NRF.
  • the fourth network node may be a UDM, or a combination of UDM + HSS.
  • each NF producer registers its own services to NRF, the other NF consumers discovers the registered services via NRF through input specific parameters.
  • the procedure is described in 3GPP TS23.502 v17.7.0 section 4.17.4.
  • UDM is dedicated for 5G subscriptions’ management. It registers its services to NRF. Each UDM instance is responsible for a specific UE segmentation. The UE segmentation uses different UE ID range, such as GPSI range.
  • the second network node may send a subscribe request to the first network node (NEF/SCEF/NEF+SCEF) to subscribe Nnef_APISupportCapability service for a User Equipment (UE) .
  • a UE ID is used to indicate the UE.
  • the request may be a Nnef_EventExposure Subscribe Request, with parameters UE ID, Event Type (API_Support_Capability) , callback URI in the request message.
  • the request may be a Nnef_EventExposure Subscribe (UE ID, Event Type (API_Support_Capability) , callback URI) message.
  • the first network node may discover EventExposure service of the fourth network node (UDM/HSS) by sending a Nnrf_NFDiscovery_Request to the third network (NRF) .
  • the service discovery procedure is detailed described in 3GPP TS23.502 section 4.17.4.
  • the first network node sends a request to NRF.
  • the first network node may determine a subscription domain for the UE according to UDM discovery response from NRF.
  • the core network type may comprise at least one of Evolved Packet Core (EPC) , Fifth Generation Core network (5GC) , Dual EPC and 5GC.
  • EPC Evolved Packet Core
  • 5GC Fifth Generation Core network
  • Dual EPC Dual EPC and 5GC.
  • the CnType may comprise three different kinds of registration type in core network for a UE: EPC, 5GC, Dual EPC and 5GC.
  • the three different types of CnType may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the three different types of CnType may take any suitable name, such as SINGLE_4G, SINGLE_5G, DUAL_4G5G can also be used to denote the three kinds of CnType, which is shown in Table 2b.
  • the subscription domain for a UE may comprise 4th Generation Mobile Communication Technology subscription (4G subscription) , 5th Generation Mobile Communication Technology subscription (5G subscription) .
  • Table 3 shows an Enumeration example of subscription domain.
  • the subscription domain may take any suitable form, such as an array, an indication, or a bit, or a flag, etc.
  • the first network node may determine this is a 5G subscription. Then it may execute steps from 3b to 5b for subscribing core network type change event to UDM, and may execute steps from 6b to 7b for getting a core network type change event notification from UDM.
  • Step 3a (This is a 4G subscription)
  • the first network node may determine the availability or expected level of support of common APIs for the received UE ID.
  • the first network node may determine the UE domain information.
  • the CnType “SIGNLE_4G” or “EPC”
  • the subscription domain ”4G” .
  • the first network node may immediately send a MonitoringEventReport with parameters CnType, subscription domain in a Nnef_EventExposure_Subscribe Response message. Meanwhile, the availability or expected level of support of common APIs are also comprised in the Nnef_EventExposure_Subscribe Response. Then the first network node may send the response to the AF.
  • Step 3b (This is a 5G subscription)
  • the first network node may subscribe the core network type change event to UDM by sending Nudm_EventExposure_Subscribe Request (CN Type Change, Report Type, UE ID, Duration of Reporting) message.
  • Nudm_EventExposure_Subscribe Request CN Type Change, Report Type, UE ID, Duration of Reporting
  • Step 4b (This is a 5G subscription)
  • the UDM may determine the CnType for the indicated UE based on the registered MME or AMF.
  • the UDM may send a Nudm_EventExposure_Subscribe Response to the first network node to inform the new CnType for the UE.
  • the new CnType may be comprised in a CnTypeChangeReport.
  • Table 4 shows a definition of the Report, which is described in 3GPP TS29.503 v17.9.0. Table 4 Report
  • Step 5b (This is a 5G subscription) According to the received CnType from UDM/HSS and the determined subscription domain.
  • the subscription domain “5G” subscription.
  • the first network node may determine the availability of support of APIs for the indicated UE.
  • the first network node may send a Nnef_EventExposure Subscribe Response to the second network node.
  • a MonitoringEventReport API support capabilities are included in it.
  • the MonitoringEventReport may comprise the CnType and the subscription domain in the report.
  • Step 6b When the fourth network node (UDM or HSS) detects that the indicated UE is switching between EPC and 5GC, the UDM may determine the CnType for the indicated UE.
  • the fourth network node (UDM/HSS) may inform the first network node of the CnType by sending Nudm_EventExposure_Notify (CN type) .
  • the first network node may send a Nnef_EventExposure Notification to the second network node.
  • a MonitoringEventReport API support capabilities are included in it.
  • the MonitoringEventReport may comprise the updated CnType and subscription domain in it.
  • the subscription domain “5G” .
  • MonitoringEventReport may comprise API support capabilities in it.
  • the first network node may send a Nnef_EventExposure Notif to the second network node.
  • the subscription domain could be included in the MonitoringEventReport to indicate the subscriber type, such as 4G subscription or 5G subscription.
  • steps 6b –7b are omitted.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. It proposes a solution for exposing UE domain information to an application function. Through the proposed method, AF can provide the fine-grained granularity service, based on the exposure of the UE domain information. E. g. AF gives the higher video quality if UE registered with 5GS.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 6 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • the first network node described above may be implemented as or through the apparatus 600.
  • the apparatus 600 comprises at least one processor 601, such as a digital processor (DP) , and at least one memory (MEM) 602 coupled to the processor 601.
  • the apparatus 600 may further comprise a transmitter TX and receiver RX 603 coupled to the processor 601.
  • the MEM 602 stores a program (PROG) 604.
  • the PROG 604 may include instructions that, when executed on the associated processor 601, enable the apparatus 600 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 601 and the at least one MEM 602 may form processing means 605 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 601, software, firmware, hardware or in a combination thereof.
  • the MEM 602 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 601 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 602 contains instructions executable by the processor 601, whereby the network node operates according to any of the methods related to the network node as described above.
  • the memory 602 contains instructions executable by the processor 601, whereby the application node operates according to any of the methods related to the application node as described above.
  • FIG. 7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • the second network node described above may be implemented as or through the apparatus 700.
  • the apparatus 700 comprises at least one processor 701, such as a digital processor (DP) , and at least one memory (MEM) 702 coupled to the processor 701.
  • the apparatus 700 may further comprise a transmitter TX and receiver RX 703 coupled to the processor 701.
  • the MEM 702 stores a program (PROG) 704.
  • the PROG 704 may include instructions that, when executed on the associated processor 701, enable the apparatus 700 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 801 and the at least one MEM 702 may form processing means 705 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 701, software, firmware, hardware or in a combination thereof.
  • the MEM 702 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 701 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 702 contains instructions executable by the processor 701, whereby the network node operates according to any of the methods related to the network node as described above.
  • the memory 702 contains instructions executable by the processor 701, whereby the application node operates according to any of the methods related to the application node as described above.
  • FIG. 8 is a block diagram showing a network node according to an embodiment of the disclosure.
  • the first network node 800 may comprise a first receiving module 801 configured to receive a first request from a second network node, wherein the first request comprises a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • UE ID User Equipment Identifier
  • UE User Equipment
  • the first network node 800 further comprises a first determining module 807 configured to determine a UE domain information according to the received UE ID.
  • the first network node 800 may further comprise a first sending module 802 configured to send a first response to the second network node.
  • the first response may comprise the determined UE domain information.
  • the first network node 800 may further comprise a second sending module 804 configured to send a second request to a third network node to discover if there exist a fourth network node service instance for the UE ID.
  • the first network node 800 may further comprise a second receiving module 803 configured to receive a second response from the third network node, wherein the second response indicating whether there exist a fourth network node service instance for the UE ID.
  • the first network node 800 may further comprise a third sending module 806 configured to send a third request, to the fourth network node, to subscribe the core network type change according to the UE ID, when the second response indicates there exist a fourth network node service instance for the UE ID.
  • a third sending module 806 configured to send a third request, to the fourth network node, to subscribe the core network type change according to the UE ID, when the second response indicates there exist a fourth network node service instance for the UE ID.
  • the first network node 800 may further comprise a third receiving module 805 configured to receive response or message from the fourth network node.
  • FIG. 9 is a block diagram showing a network node according to an embodiment of the disclosure.
  • the second network node 900 may comprise a sending module 901 configured to send a first request to a first network node.
  • the first request may comprise a User Equipment Identifier (UE ID) to indicate a User Equipment (UE) .
  • UE ID User Equipment Identifier
  • the second network node 900 may further comprise a first receiving module 902 configured to receive a first response, from the first network node.
  • the first response may comprise a UE domain information according to the UE ID.
  • the second network node 900 may further comprise a second receiving module 903 configured to receive a second message from the first network node.
  • the second message may comprise an updated UE domain information according to the UE ID.
  • FIG. 10 shows an example of a communication system QQ1000 in accordance with some embodiments.
  • the communication system QQ1000 includes a telecommunication network QQ1002 that includes an access network QQ1004, such as a radio access network (RAN) , a core network QQ1006, which includes one or more core network nodes QQ1008.
  • the access network QQ1004 includes one or more access network nodes, such as network nodes QQ1010a and QQ1010b (one or more of which may be generally referred to as network nodes QQ1010) , or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes QQ1010 facilitate direct or indirect connection of user equipment (UE) , such as by connecting UEs QQ1012a, QQ1012b, QQ1012c, and QQ1012d (one or more of which may be generally referred to as UEs QQ1012) to the core network QQ1006 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system QQ1000 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system QQ1000 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs QQ1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ1010 and other communication devices.
  • the network nodes QQ1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ1012 and/or with other network nodes or equipment in the telecommunication network QQ1002 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ1002.
  • the core network QQ1006 connects the network nodes QQ1010 to one or more hosts, such as host QQ1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network QQ1006 includes one more core network nodes (e.g., core network node QQ1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ1008.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC) , Mobility Management Entity (MME) , Home Subscriber Server (HSS) , Access and Mobility Management Function (AMF) , Session Management Function (SMF) , Authentication Server Function (AUSF) , Subscription Identifier De-concealing function (SIDF) , Unified Data Management (UDM) , Security Edge Protection Proxy (SEPP) , Network Exposure Function (NEF) , and/or a User Plane Function (UPF) , Control Function (PCF) , Unified Data Management (UDM) , etc.
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • the host QQ1016 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ1004 and/or the telecommunication network QQ1002, and may be operated by the service provider or on behalf of the service provider.
  • the host QQ1016 may host a variety of applications or application functions (AFs) to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • AFs application functions
  • the communication system QQ1000 of FIG. 10 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM) ; Universal Mobile Telecommunications System (UMTS) ; Long Term Evolution (LTE) , and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G) ; wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi) ; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal
  • the telecommunication network QQ1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC) /Massive IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs QQ1012 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network QQ1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ1004.
  • a UE may be configured for operating in single-or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i. e. being configured for multi-radio dual connectivity (MR-DC) , such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio –Dual Connectivity (EN-DC) .
  • MR-DC multi-radio dual connectivity
  • the hub QQ1014 communicates with the access network QQ1004 to facilitate indirect communication between one or more UEs (e.g., UE QQ1012c and/or QQ1012d) and network nodes (e.g., network node QQ1010b) .
  • the hub QQ1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub QQ1014 may be a broadband router enabling access to the core network QQ1006 for the UEs.
  • the hub QQ1014 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub QQ1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub QQ1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub QQ1014 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub QQ1014 may have a constant/persistent or intermittent connection to the network node QQ1010b.
  • the hub QQ1014 may also allow for a different communication scheme and/or schedule between the hub QQ1014 and UEs (e.g., UE QQ1012c and/or QQ1012d) , and between the hub QQ1014 and the core network QQ1006.
  • the hub QQ1014 is connected to the core network QQ1006 and/or one or more UEs via a wired connection.
  • the hub QQ1014 may be configured to connect to an M2M service provider over the access network QQ1004 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes QQ1010 while still connected via the hub QQ1014 via a wired or wireless connection.
  • the hub QQ1014 may be a dedicated hub –that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ1010b.
  • the hub QQ1014 may be a non-dedicated hub –that is, a device which is capable of operating to route communications between the UEs and network node QQ1010b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 11 is a block diagram of a host QQ100, which may be an embodiment of the host QQ1016 of FIG. 10, in accordance with various aspects described herein.
  • the host QQ1100 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host QQ1100 may provide one or more services to one or more UEs.
  • the host QQ1100 includes processing circuitry QQ1102 that is operatively coupled via a bus QQ1104 to an input/output interface QQ1106, a network interface QQ1108, a power source QQ1110, and a memory QQ1112.
  • the memory QQ1112 may include one or more computer programs including one or more host application programs QQ1114 and data QQ1116, which may include user data, e.g., data generated by a UE for the host QQ1100 or data generated by the host QQ1100 for a UE.
  • Embodiments of the host QQ1100 may utilize only a subset or all of the components shown.
  • the host application programs QQ1114 may be implemented in a container-based architecture and may provide support for edge applications, video codecs (e.g., Versatile Video Coding (VVC) , High Efficiency Video Coding (HEVC) , Advanced Video Coding (AVC) , MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G. 711) , including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems) .
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG MPEG
  • VP9 MPEG, VP9
  • audio codecs e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G. 711
  • UEs e.g., handsets, desktop computers, wearable display systems, heads-up
  • the host application programs QQ1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ1100 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs QQ1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP) , Real-Time Streaming Protocol (RTSP) , Dynamic Adaptive Streaming over HTTP (MPEG-DASH) , etc.
  • FIG. 12 shows a communication diagram of a host QQ1202 communicating via a network node QQ1204 with a UE QQ1206 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ1012a of FIG. 10) , network node (such as network node QQ1010a of FIG. 10) , and host (such as host QQ1016 of FIG. 10 and/or host QQ1100 of FIG. 11) discussed in the preceding paragraphs will now be described with reference to FIG. 12.
  • host QQ1202 Like host QQ1100, embodiments of host QQ1202 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host QQ1202 also includes software, which is stored in or accessible by the host QQ1202 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ1206 connecting via an over-the-top (OTT) connection QQ1250 extending between the UE QQ1206 and host QQ1202.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection QQ1250.
  • the network node QQ1204 includes hardware enabling it to communicate with the host QQ1202 and UE QQ1206.
  • the connection QQ1260 may be direct or pass through a core network (like core network QQ1006 of FIG. 10) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE QQ1206 includes hardware and software, which is stored in or accessible by UE QQ1206 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ1206 with the support of the host QQ1202.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ1206 with the support of the host QQ1202.
  • an executing host application may communicate with the executing client application via the OTT connection QQ1250 terminating at the UE QQ1206 and host QQ1202.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection QQ1250 may transfer both the request data and the user data.
  • the UE's client application may
  • the OTT connection QQ1250 may extend via a connection QQ1260 between the host QQ1202 and the network node QQ1204 and via a wireless connection QQ1270 between the network node QQ1204 and the UE QQ1206 to provide the connection between the host QQ1202 and the UE QQ1206.
  • the connection QQ1260 and wireless connection QQ1270, over which the OTT connection QQ1250 may be provided, have been drawn abstractly to illustrate the communication between the host QQ1202 and the UE QQ1206 via the network node QQ1204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host QQ1202 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE QQ1206.
  • the user data is associated with a UE QQ1206 that shares data with the host QQ1202 without explicit human interaction.
  • the host QQ1202 initiates a transmission carrying the user data towards the UE QQ1206.
  • the host QQ1202 may initiate the transmission responsive to a request transmitted by the UE QQ1206.
  • the request may be caused by human interaction with the UE QQ1206 or by operation of the client application executing on the UE QQ1206.
  • the transmission may pass via the network node QQ1204, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ1212, the network node QQ1204 transmits to the UE QQ1206 the user data that was carried in the transmission that the host QQ1202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ1214, the UE QQ1206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ1206 associated with the host application executed by the host QQ1202.
  • the UE QQ1206 executes a client application which provides user data to the host QQ1202.
  • the user data may be provided in reaction or response to the data received from the host QQ1202.
  • the UE QQ1206 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE QQ1206. Regardless of the specific manner in which the user data was provided, the UE QQ1206 initiates, in step QQ1218, transmission of the user data towards the host QQ1202 via the network node QQ1204.
  • step QQ1220 in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ1204 receives user data from the UE QQ1206 and initiates transmission of the received user data towards the host QQ1202. In step QQ1222, the host QQ1202 receives the user data carried in the transmission initiated by the UE QQ1206.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE QQ1206 using the OTT connection QQ1250, in which the wireless connection QQ1270 forms the last segment. More precisely, the teachings of these embodiments some embodiments herein can optimize the current solution. Some embodiments herein can consider two development cases. In some embodiments herein, it proposed a method to distribute the key of application function in case the VPLMN support or not support AKMA service in AKMA roaming scenario. In some embodiments herein, the key of application function is bound with SN ID, which can resist key leakage attack. In some embodiments herein, when the UE moves to another network, the key KAF used in VPLMN can be deleted both in the UE and VPLMN and cannot be used in HPLMN again, which can resist key leakage attack.
  • factory status information may be collected and analyzed by the host QQ1202.
  • the host QQ1202 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host QQ1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights) .
  • the host QQ1202 may store surveillance video uploaded by a UE.As another example, the host QQ1202 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host QQ1202 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices) , or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • 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 the OTT connection may be implemented in software and hardware of the host QQ1202 and/or UE QQ1206.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ1250 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 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection QQ1250 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not directly alter the operation of the network node QQ1204. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ1202.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ1250 while monitoring propagation times, errors, etc.
  • Embodiment 1 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE) , the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the operations related to the wireless device as described above to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 2 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Embodiment 3 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE) , the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs the operations related to the wireless device as described above to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 4 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 5 The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 6 A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE) , the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the operations related to the wireless device as described above to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 7 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • Embodiment 8 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 9 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the operations related to the wireless device as described above to receive the user data from the UE for the host.
  • OTT over-the-top
  • Embodiment 10 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 11 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 12 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE) , the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs the operations related to the wireless device as described above to receive the user data from the UE for the host.
  • UE user equipment
  • Embodiment 13 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.
  • Embodiment 14 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE) , wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the operations related to the wireless device as described above to receive the user data from the host.
  • OTT over-the-top
  • Embodiment 15 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Embodiment 16 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 17 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE) , the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs the operations related to the wireless device as described above to receive the user data from the host.
  • UE user equipment
  • Embodiment 18 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 19 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 20 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to utilize user data; and a network interface configured to receipt of transmission of the user data to a cellular network for transmission to a user equipment (UE) , wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the operations related to the wireless device as described above to transmit the user data to the host.
  • OTT over-the-top
  • Embodiment 21 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Embodiment 22 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 23 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE) , the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs the operations related to the wireless device as described above to transmit the user data to the host.
  • UE user equipment
  • Embodiment 24 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 25 The method of the previous embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent un procédé et un appareil d'exposition d'informations de domaine d'UE à une fonction d'application. Un procédé mis en œuvre par un premier nœud de réseau dans un réseau de communication comprend la réception d'une première requête en provenance d'un second nœud de réseau, la première requête comprenant un identifiant d'équipement utilisateur (UE ID) pour indiquer un équipement utilisateur (UE), la détermination d'informations de domaine d'UE selon l'ID d'UE reçu, et l'envoi d'une première réponse au second nœud de réseau. La première réponse comprend les informations de domaine d'UE déterminées. Les informations de domaine d'UE comprennent un type de réseau central et un domaine d'abonnement.
PCT/CN2024/102554 2023-06-29 2024-06-28 Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application Ceased WO2025002402A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202480042879.8A CN121399986A (zh) 2023-06-29 2024-06-28 用于向应用功能的用户设备域信息开放的方法和装置
EP24831029.4A EP4710583A1 (fr) 2023-06-29 2024-06-28 Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2023/103656 2023-06-29
CN2023103656 2023-06-29

Publications (1)

Publication Number Publication Date
WO2025002402A1 true WO2025002402A1 (fr) 2025-01-02

Family

ID=93937482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/102554 Ceased WO2025002402A1 (fr) 2023-06-29 2024-06-28 Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application

Country Status (3)

Country Link
EP (1) EP4710583A1 (fr)
CN (1) CN121399986A (fr)
WO (1) WO2025002402A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190141518A1 (en) * 2016-07-04 2019-05-09 Huawei Technologies Co., Ltd. Method, apparatus, and system for managing imsi status of terminal device
CN115989717A (zh) * 2020-06-22 2023-04-18 诺基亚技术有限公司 用户设备中的多个订阅实体
US20230156453A1 (en) * 2020-04-08 2023-05-18 Telefonaktiebolaget Lm Ericsson (Publ) Common event exposure in network domains

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190141518A1 (en) * 2016-07-04 2019-05-09 Huawei Technologies Co., Ltd. Method, apparatus, and system for managing imsi status of terminal device
US20230156453A1 (en) * 2020-04-08 2023-05-18 Telefonaktiebolaget Lm Ericsson (Publ) Common event exposure in network domains
CN115989717A (zh) * 2020-06-22 2023-04-18 诺基亚技术有限公司 用户设备中的多个订阅实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Slice privacy protection in NSSAA related procedure", 3GPP DRAFT; S3-203022, vol. SA WG3, 30 October 2020 (2020-10-30), FR, XP052469194 *

Also Published As

Publication number Publication date
EP4710583A1 (fr) 2026-03-18
CN121399986A (zh) 2026-01-23

Similar Documents

Publication Publication Date Title
WO2023058009A1 (fr) Indication d'itinérance en cas de catastrophe pour session et politique
WO2020088594A1 (fr) Procédé et appareil de transmission de données
US20250193663A1 (en) Method and Apparatus for Performing Secondary Authentication/Authorization for Terminal Device in Communication Network
US20240155334A1 (en) Method and Apparatus for Exposing User Equipment Address Information
WO2023198733A1 (fr) Détermination efficace d'informations d'abonnement d'utilisateur dans un réseau multi-domaine
WO2025002402A1 (fr) Procédé et appareil d'exposition d'informations de domaine d'équipement utilisateur à une fonction d'application
US20260129561A1 (en) Method and apparatus for session management
WO2024067680A9 (fr) Procédé et appareil de gestion de session
WO2024169845A1 (fr) Procédé et appareil de facturation
WO2024169727A1 (fr) Procédé et appareil de stockage de données spécifiques à une application
WO2024169729A1 (fr) Procédé et appareil de gestion de session
WO2024159987A1 (fr) Procédés et appareils pour mise à jour de mappage ebi et arp
WO2024126146A1 (fr) Procédé et appareil de gestion de session de qualité de service de réseau de données de bord
WO2024083103A1 (fr) Procédé et appareil d'authentification
WO2024227388A1 (fr) Procédés et dispositifs d'indication d'informations
WO2024217298A1 (fr) Procédés et appareils de commande de tranche de réseau
WO2024146809A1 (fr) Procédé et appareil pour services différenciés
WO2024138618A1 (fr) Procédé et appareil de gestion de session d'échange de clé internet (ike)
WO2025123311A1 (fr) Procédé et appareil d'extension de durée de vie d'association de sécurité enfant de sécurité ip
WO2025214285A1 (fr) Procédé et appareil pour une continuité de service
WO2024083105A1 (fr) Procédé et appareil de sécurité de plan utilisateur d'un groupe de réseaux virtuels
WO2023143097A1 (fr) Procédé et appareil destinés à un service de multidiffusion/diffusion
WO2024146596A1 (fr) Procédé et appareil d'abonnement et de notification
US20260122725A1 (en) Wireless Device, First Network Node, and Methods Performed Thereby for Handling a Configuration
US20250081257A1 (en) Device-to-Network Relaying for an Emergency Service

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024831029

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

ENP Entry into the national phase

Ref document number: 2024831029

Country of ref document: EP

Effective date: 20251210

WWP Wipo information: published in national office

Ref document number: 2024831029

Country of ref document: EP