WO2025200027A1 - Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet - Google Patents

Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet

Info

Publication number
WO2025200027A1
WO2025200027A1 PCT/CN2024/085068 CN2024085068W WO2025200027A1 WO 2025200027 A1 WO2025200027 A1 WO 2025200027A1 CN 2024085068 W CN2024085068 W CN 2024085068W WO 2025200027 A1 WO2025200027 A1 WO 2025200027A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
communication
ims
service
service associated
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.)
Pending
Application number
PCT/CN2024/085068
Other languages
English (en)
Inventor
Jing PING
Shi Wen Liu
Saurabh Khare
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.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/085068 priority Critical patent/WO2025200027A1/fr
Publication of WO2025200027A1 publication Critical patent/WO2025200027A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security

Definitions

  • Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for access control on internet protocol multimedia subsystem (IMS) data channel (DC) service exposure.
  • IMS internet protocol multimedia subsystem
  • DC data channel
  • the study aims at investigating the security impacts of the new features of the Next Generation Real Time Communication (RTC) has been discussed. More specifically the study aims at IMS third party identity security handling, the security handling of the enhancements to IMS media plane to support the use cases of IMS based Metaverse services and IMS data channel service exposure security.
  • RTC Real Time Communication
  • an apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a request of a service associated with a DC communication in an IMS; determine whether the request of the service associated with the DC communication is allowed at least based on an authorization decision received from at least one network function or one or more DC authorization policies retrieved from the at least one network function; and cause, based on the determination, the service associated with the DC communication to be exposed to a DC application server.
  • a method comprises: receiving a request of a service associated with a DC communication in an IMS; determining whether the request of the service associated with the DC communication is allowed at least based on an authorization decision received from at least one network function or one or more DC authorization policies retrieved from the at least one network function; and causing, based on the determination, the service associated with the DC communication to be exposed to a DC application server.
  • a method comprises: receiving, from one of a NEF or an IMS AS or a DCSF, information associated with a request of a service associated with a DC communication in an IMS or a request for retrieving at least one or more DC authorization policies corresponding to the request of the service; and transmitting, to one of the NEF or the IMS AS or the DCSF, an indication indicating whether the request of the service is authorized or the one or more DC authorization policies.
  • an apparatus comprising means for receiving, from one of a NEF or an IMS AS or a DCSF, information associated with a request of a service associated with a DC communication in an IMS or a request for retrieving at least one or more DC authorization policies corresponding to the request of the service; and means for transmitting, to one of the NEF or the IMS AS or the DCSF, an indication indicating whether the request of the service is authorized or the one or more DC authorization policies.
  • a computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.
  • a computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
  • aDC authorization policy , “the DC authorization policy” , “DC authorization policies” and/or “one or more DC authorization policies” used hereinafter may be considered as a DC specific authorization policy for the DC communication in IMS DC.
  • the one or more DC authorization policies comprises at least one subscription-based DC authorization policy.
  • the NEF 110 receives (202) a request of a DC communication service, e.g., a DC event subscription, from DC AS 140.
  • a DC communication service e.g., a DC event subscription
  • the NEF 110 may determine whether the request of the service associated with the DC communication is allowed based on one or more DC authorization policies retrieved from the at least one network function, e.g., from HSS/UDM 120. It is to be understood that the one or more DC authorization policies may also be retrieved from other network function such as PCF, PCRF, IMS AS/DCSF 130.
  • one or more DC authorization policies and/or the corresponding user consent are used for the NEF 110 to authorize the request from the DC AS 140.
  • the NEF 110 may determine whether the request of the service associated with the DC communication is allowed based on an authorization decision received from at least one network function e.g., from HSS/UDM 120.
  • the NEF 110 may transmit (206) related information extracted from the request of the service associated with the DC communication. If the NEF 110 receives an indication indicating the request is authorized, the NEF 110 may determine that the service associated with the DC communication is to be exposed to the DC application server.
  • an application function e.g., associated with the DC AS 140
  • the NEF 110 may check the authorization policy and consent flag for the UE. If policy and consent are allowed, then only provide the data or block the data.
  • the NEF 110 After determining the request of the service associated with the DC communication is allowed, for both options 1 and 2, the NEF 110 sends (208) the DC event subscription request to IMS AS/DSCF 130 indicating that the request of the service associated with the DC communication is allowed. Then the NEF 110 may receive (212) response from IMS AS/DSCF 130.
  • the NEF 110 may transmit (214) a response to the DC AS 140 indicating that the service request associated with the DC communication is proceeded.
  • the NEF 110 may receive (216) a DC event notification from a network function, e.g., an IMS AS/DSCF 130. If the NEF 110 determines a DC event notification is received from the IMS AS/DSCF 130, the NEF 110 may retrieve (218) DC AS property and one or more privacy policies from the locally or the at least one network function, such as PCF/PCRF/UDM/HSS/DCSF. The NEF 110 may anonymize (220) the DC event data based on the DC application server property and the one or more privacy policies and transmit (222) the anonymized DC event data as a part of notification to the DC application server. More specifically, the NEF 110 may anonymize personal data in the notification if required according to privacy policy and AF properties.
  • a network function e.g., an IMS AS/DSCF 130.
  • the NEF 110 may retrieve (218) DC AS property and one or more privacy policies from the locally or the at least one network function, such as PCF/PCRF/UDM/HSS/DCSF.
  • option 3 whether the request of the service associated with the DC communication is allowed may be determined by the IMS AS/DSCF 130. That is, the IMS AS/DSCF 130 may make authorization decision and grant permission for the request.
  • the NEF 110 may forward (208) the request to the IMS AS/DSCF 130.
  • the IMS AS/DSCF 130 may request to retrieve (210) one or more DC authorization policies and corresponding user consent retrieved from HSS/UDM 120 and obtain the requested one or more DC authorization policies and corresponding user consent from HSS/UDM 120. If the IMS AS/DSCF 130 determines, based on the one or more DC authorization policies and/or the corresponding user consent retrieved from the HSS/UDM 120, that the request of the service associated with the DC communication is authorized, the IMS AS/DSCF 130 may determine that the service is to be exposed to the DC application server.
  • one or more DC authorization policies and/or the corresponding user consent are used for the IMS AS/DSCF 130 to authorize the request from the DC AS 140. It is to be understood that the one or more DC authorization policies may also be retrieved from other network function such as PCF or PCRF.
  • the IMS AS/DSCF 130 may determine whether the request of the service associated with the DC communication is allowed based on based on an authorization decision received from at least one network function e.g., from HSS/UDM 120.
  • the IMS AS/DSCF 130 may transmit related information extracted from the request of the service associated with the DC communication. If the IMS AS/DSCF 130 receives an indication indicating the request is authorized, the IMS AS/DSCF 130 may determine that the service associated with the DC communication is to be exposed to the DC application server.
  • the NEF 110 may receive (212) response from IMS AS/DSCF 130 indicating that the service associated with the DC communication is authorized to be exposed to the DC AS 140.
  • NEF 110 may expose all information to the AF as raw data.
  • NEF 110 may mask calling and called number, but still share downloaded applications, in specific region and/or period.
  • AF property shows its application client on UE on behalf of the subscriber
  • all DC related information collected by IMS system for the subscriber can be exposed to the AF to allow the user to monitor the status of application DC.
  • the privacy policy can be part of user consent.
  • the signaling flow 300 in FIG. 3 refers to a scenario in which authorization and privacy protection for IMS DC event exposure may be based on AF-based authorization policy.
  • DC authorization policies may be provisioned in NEF/PCF/PCRF/DCSF/IMS AS according to operator's polices
  • privacy policies may be preconfigured in NEF or PCF/PCRF/UDM/HSS and user consent specific to IMS DC is preconfigured in UDM/HSS.
  • aDC authorization policy , “the DC authorization policy” , “DC authorization policies” and/or “one or more DC authorization policies” used hereinafter may be considered as a DC specific authorization policy for the DC communication in IMS DC.
  • the one or more DC authorization policies comprises at least one application function-based DC authorization policies.
  • the NEF 110 receives (302) a request of a DC communication service, e.g., a DC event subscription, from the DC AS 140.
  • a DC communication service e.g., a DC event subscription
  • the solution of the present disclosure proposes a mechanism for authorizing the AF/AS based on authorization policies when an AF/AS access IMS data DC services. It is to be understood that the solution of the present disclosure may also be reused for non-DC IMS service exposure protection, in that case, the authorization policies are DC agnostic.
  • the subject may refer to, e.g., application function/server (identified by AF/AS ID, optionally with AF type for subscription-based polices) .
  • the conditions may refer to, e.g., location: if subscriber is in certain location, then only AF is allowed to access the event; and time or time duration: Only in certain time duration, events are exposed to AF.
  • privacy data may be, e.g. caller and called id, downloaded applications, time create/terminate DC, etc.
  • the AF property may be, e.g. operator AF, 3rd party AF on behalf of subscriber (e.g. for session control) , 3rd party AF for application usage or performance analytics/survey/statistic, etc.
  • the NEF or the IMS AS/DCSF causes, based on the determination, the service associated with the DC communication to be exposed to a DC application server.
  • the method 500 further comprises: in accordance with the determination that the request of the service associated with the DC communication is received from the DC application server, transmitting to the at least one network function, a request for retrieving at least one of the following: one or more DC authorization policies, or corresponding user consent; and in accordance with the determination, based on the one or more DC authorization policies and/or the corresponding user consent retrieved from the at least one network function, that the request is authorized, determine that the service is to be exposed to the DC application server.
  • the method 500 further comprises: in accordance with the determination that the request of the service associated with the DC communication is received from the DC application server, forwarding the request to an IMS application server or a data channel signaling function, DCSF; and in accordance with a determination that a response to the request indicating that the service associated with the DC communication is allowed to be exposed to the DC application server, determining that the service associated with the DC communication is to be exposed to the DC application server.
  • the service associated with the DC communication comprises a service of a DC event subscription
  • the method 500 further comprises: in accordance with the determination that a DC event notification , retrieving DC application server property and one or more privacy policies from the apparatus or the at least one network function; anonymizing the DC event data based on the DC application server property and the one or more privacy policies; and transmitting the anonymized DC event data as a part of notification to the DC application server.
  • the service associated with the DC communication comprises a DC session control
  • the method 500 further comprises: checking if the DC application server is matched to an application corresponding to a target application DC associated with the service based on the one or more DC authorization policies; and in accordance with the determination that the DC application server is matched to the application corresponding to the target application DC, determining that the DC session control is allowed.
  • the method 500 further comprises: in accordance with the determination that the request of the service associated with the DC communication is received from a Network Exposure Function, NEF, transmitting, to the at least one network function, information extracted from the request; and in accordance with the determination that an indication received from the at least one network function indicating the request is authorized, transmitting a response to the request indicating that the service associated with the DC communication is allowed to be exposed to the DC application server.
  • NEF Network Exposure Function
  • the service associated with the DC communication comprises at least one of the following: a DC event subscription, a DC initiation, a DC release, a DC communication update, or a DC download.
  • the at least one function comprises at least one of the following: a policy control function, PCF, a policy and charging rules function, PCRF, a unified data management, UDM, a home subscriber server, HSS, a DCSF, or an IMS application server, IMS AS.
  • the one or more DC authorization policies comprises at least one subscription-based DC authorization policy and/or at least one application function-based DC authorization policies.
  • the apparatus comprises an NEF or an IMS AS or a DCSF.
  • FIG. 6 shows a flowchart of an example method 600 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the UDM/HSS 120 in FIG. 1.
  • the UDM/HSS 120 receives, from one of a NEF or an IMS AS or a DCSF, information associated with a request of a service associated with a DC communication in an IMS or a request for retrieving at least one or more DC authorization policies corresponding to the request of the service.
  • the UDM/HSS 120 transmits, to one of the NEF or the IMS AS or the DCSF, an indication indicating whether the request of the service is authorized or the one or more DC authorization policies.
  • the method 600 further comprises: obtaining the one or more DC authorization policies from the apparatus or at least one further network function; and determining whether the request of the service is authorized based on the one or more DC authorization policies.
  • the method 600 further comprises: in accordance with the determination that the request is received from the NEF, or an IMS AS or a DCSF for retrieving the one or more DC authorization policies and corresponding user consent, transmitting the one or more DC authorization policies and corresponding user consent to the NEF.
  • the service associated with the DC communication comprises at least one of the following: a DC event subscription, a DC initiation, a DC release, a DC communication update, or a DC download.
  • the at least one function comprises at least one of the following: a PCF, a PCRF, a DCSF, or an IMS AS.
  • the one or more DC authorization policies comprises at least one subscription-based DC authorization policy and/or at least one application function-based DC authorization policies.
  • the apparatus comprises a UDM or an HSS.
  • an apparatus capable of performing any of the method 500 may comprise means for performing the respective operations of the method 500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus may be implemented as or included in the NEF 110 or the IMS AS/DCSF 130 in FIG. 1.
  • the apparatus comprises means for receiving a request of a service associated with a DC communication in an IMS; means for determining whether the request of the service associated with the DC communication is allowed at least based on an authorization decision received from at least one network function or one or more DC authorization policies retrieved from the at least one network function; and means for causing, based on the determination, the service associated with the DC communication to be exposed to a DC application server.
  • the apparatus is caused to: means for in accordance with the determination that the request of the service associated with the DC communication is received from the DC application server, transmitting to the at least one network function, a request for retrieving at least one of the following: one or more DC authorization policies, or corresponding user consent; and means for in accordance with the determination, means for determining on the one or more DC authorization policies and/or the corresponding user consent retrieved from the at least one network function, that the request is authorized, determine that the service is to be exposed to the DC application server.
  • the apparatus is caused to: means for in accordance with the determination that the request of the service associated with the DC communication is received from the DC application server, transmitting to the at least one network function, information extracted from the request; and means for in accordance with the determination that an indication received from the at least one network function indicating the request is authorized, determining that the service associated with the DC communication is to be exposed to the DC application server.
  • the apparatus is caused to: means for transmitting, to the DC application server, a response indicating that the service request associated with the DC communication is proceeded.
  • the service associated with the DC communication comprises a service of a DC event subscription
  • the apparatus is caused to: means for in accordance with the determination that a DC event notification , retrieving DC application server property and one or more privacy policies from the apparatus or the at least one network function; means for anonymizing the DC event data based on the DC application server property and the one or more privacy policies; and means for transmitting the anonymized DC event data as a part of notification to the DC application server.
  • the apparatus is caused to: means for in accordance with the determination that the request of the service associated with the DC communication is received from a Network Exposure Function, NEF, transmitting, to the at least one network function, information extracted from the request; and means for in accordance with the determination that an indication received from the at least one network function indicating the request is authorized, transmitting a response to the request indicating that the service associated with the DC communication is allowed to be exposed to the DC application server.
  • NEF Network Exposure Function
  • the service associated with the DC communication comprises at least one of the following: a DC event subscription, a DC initiation, a DC release, a DC communication update, or a DC download.
  • the at least one function comprises at least one of the following: a policy control function, PCF, a policy and charging rules function, PCRF, a unified data management, UDM, a home subscriber server, HSS, a DCSF, or an IMS application server, IMS AS.
  • the one or more DC authorization policies comprises at least one subscription-based DC authorization policy and/or at least one application function-based DC authorization policies.
  • the apparatus comprises an NEF or an IMS AS or a DCSF.
  • an apparatus capable of performing any of the method 600 may comprise means for performing the respective operations of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus may be implemented as or included in the HSS/UDM 120 in FIG. 1.
  • the apparatus comprises means for receiving, from one of a NEF or an IMS AS or a DCSF, information associated with a request of a service associated with a DC communication in an IMS or a request for retrieving at least one or more DC authorization policies corresponding to the request of the service; and means for transmitting, to one of the NEF or the IMS AS or the DCSF, an indication indicating whether the request of the service is authorized or the one or more DC authorization policies.
  • the apparatus is caused to: means for obtaining the one or more DC authorization policies from the apparatus or at least one further network function; and means for determining whether the request of the service is authorized based on the one or more DC authorization policies.
  • the apparatus is caused to: means for in accordance with the determination that the request is received from the NEF, or an IMS AS or a DCSF for retrieving the one or more DC authorization policies and corresponding user consent, transmitting the one or more DC authorization policies and corresponding user consent to the NEF.
  • the service associated with the DC communication comprises at least one of the following: a DC event subscription, a DC initiation, a DC release, a DC communication update, or a DC download.
  • the at least one function comprises at least one of the following: a PCF, a PCRF, a DCSF, or an IMS AS.
  • the one or more DC authorization policies comprises at least one subscription-based DC authorization policy and/or at least one application function-based DC authorization policies.
  • the apparatus comprises a UDM or an HSS.
  • FIG. 7 is a simplified block diagram of a device 700 that is suitable for implementing example embodiments of the present disclosure.
  • the device 700 may be provided to implement a communication device, for example, the NEF 110 or the IMS AS/DCSF 130 or the UDM/HSS 120 as shown in FIG. 1.
  • the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
  • the communication module 740 is for bidirectional communications.
  • the communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices.
  • the communication interfaces may represent any interface that is necessary for communication with other network elements.
  • the communication module 740 may include at least one antenna.
  • the processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a computer program 730 includes computer executable instructions that are executed by the associated processor 710.
  • the instructions of the program 730 may include instructions for performing operations/acts of some example embodiments of the present disclosure.
  • the program 730 may be stored in the memory, e.g., the ROM 724.
  • the processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.
  • the example embodiments of the present disclosure may be implemented by means of the program 730 so that the device 700 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 6.
  • the example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 730 may be tangibly contained in a computer readable medium which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700.
  • the device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution.
  • the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • the term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
  • FIG. 8 shows an example of the computer readable medium 800 which may be in form of CD, DVD or other optical storage disk.
  • the computer readable medium 800 has the program 730 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages.
  • the program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

Landscapes

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

Abstract

Des exemples de modes de réalisation de la présente divulgation concernent un contrôle d'accès sur le service d'exposition du canal de données (DC) du sous-système multimédia du protocole Internet (IMS). Un procédé consiste à : recevoir une demande d'un service associé à une communication par canal de données (DC) dans un IMS; déterminer si la demande du service associé à la communication par DC est autorisée au moins sur la base d'une décision d'autorisation reçue en provenance d'au moins une fonction de réseau ou d'une ou de plusieurs politiques d'autorisation DC récupérées à partir de la ou des fonctions de réseau ; et amener, sur la base de la détermination, le service associé à la communication par DC à être exposé à un serveur d'application DC.
PCT/CN2024/085068 2024-03-29 2024-03-29 Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet Pending WO2025200027A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085068 WO2025200027A1 (fr) 2024-03-29 2024-03-29 Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/085068 WO2025200027A1 (fr) 2024-03-29 2024-03-29 Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet

Publications (1)

Publication Number Publication Date
WO2025200027A1 true WO2025200027A1 (fr) 2025-10-02

Family

ID=97218676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/085068 Pending WO2025200027A1 (fr) 2024-03-29 2024-03-29 Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet

Country Status (1)

Country Link
WO (1) WO2025200027A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557744A (zh) * 2018-05-31 2019-12-10 华为技术有限公司 订阅事件的方法与网络功能网元
WO2023004697A1 (fr) * 2021-07-29 2023-02-02 Nokia Shanghai Bell Co., Ltd. Acheminement de plan d'utilisateur entre une fonction de plan d'utilisateur et une fonction d'application
WO2023142676A1 (fr) * 2022-01-26 2023-08-03 Telefonaktiebolaget Lm Ericsson (Publ) Élimination d'autorisation spécifique à un service dans un cœur de réseau 5g (5gc)
WO2023185854A1 (fr) * 2022-03-29 2023-10-05 中国移动通信有限公司研究院 Procédé et appareil de traitement d'informations, dispositif de communication et support de stockage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557744A (zh) * 2018-05-31 2019-12-10 华为技术有限公司 订阅事件的方法与网络功能网元
WO2023004697A1 (fr) * 2021-07-29 2023-02-02 Nokia Shanghai Bell Co., Ltd. Acheminement de plan d'utilisateur entre une fonction de plan d'utilisateur et une fonction d'application
WO2023142676A1 (fr) * 2022-01-26 2023-08-03 Telefonaktiebolaget Lm Ericsson (Publ) Élimination d'autorisation spécifique à un service dans un cœur de réseau 5g (5gc)
WO2023185854A1 (fr) * 2022-03-29 2023-10-05 中国移动通信有限公司研究院 Procédé et appareil de traitement d'informations, dispositif de communication et support de stockage

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Subscription status notification for Event Exposure service", 3GPP DRAFT; S2-183998_3451_SUBSCRIPTION STATUS NOTIFICATION FOR EVENT EXPOSURE SERVICE(23.502)_V1.1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sanya, China; 20180416 - 20180420, 20 April 2018 (2018-04-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051432879 *

Similar Documents

Publication Publication Date Title
US12401690B2 (en) Mechanism for dynamic authorization
US12477337B2 (en) Access token revocation in security management
US12495095B2 (en) Network function validation
US20240381091A1 (en) Consent Data Scheduling Method and Network-Side Device
WO2022094995A1 (fr) Anonymisation de données permettant la minimisation "drive-test"
EP4274161A1 (fr) Appareil, procédés et programmes informatiques
WO2025200027A1 (fr) Contrôle d'accès sur le service d'exposition de canal de données du sous-système multimédia de protocole internet
US20230345251A1 (en) Method, device and computer readable medium for communications
WO2023015482A1 (fr) Isolement de données de gestion
WO2025231876A1 (fr) Protection de réseau mobile terrestre public
US20260058956A1 (en) Resource owner authorization for api invoker
WO2025217818A1 (fr) Partage de données de consommation d'énergie
WO2026031218A1 (fr) Synchronisation de paramètres d'abonnement
WO2024234176A1 (fr) Amélioration de services de gestion de réseau
WO2025030344A1 (fr) Mise en vigueur d'isolement pour orientation de trafic d'application
US20240064512A1 (en) Usage of access token in service based architecture
US20240340772A1 (en) Steering of roaming enhancement during registration reject
WO2024077582A1 (fr) Contre-mesure de sécurité pour contrôle d'admission de tranche de réseau distribué
WO2024098177A1 (fr) Procédure d'authentification pour tranche de réseau
WO2026065013A1 (fr) Autorisation de demande de service
WO2025175539A1 (fr) Authentification akma avec des informations de dispositif
US20260067680A1 (en) Authentication for device with non-cellular access
WO2025112008A1 (fr) Communication sécurisée dans un système d'enregistrement et retransmission de réseau non terrestre
WO2023236093A1 (fr) Dispositifs, procédés, appareils, et supports lisibles par ordinateur pour isolation de tranche de réseau
US20250274358A1 (en) Network repository function policy control for different public land mobile networks

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

Country of ref document: EP

Kind code of ref document: A1