Method and apparatus for supporting call session update in wireless communication system

The method and apparatus for managing IMS call session updates through a data channel application server address scalability and complexity issues in 5G systems by enabling efficient data channel-based service support for video or voice sessions, enhancing network resource utilization and user experience.

WO2026240580A1PCT designated stage Publication Date: 2026-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096865
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-05-12
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in managing IMS call session updates efficiently, particularly in supporting data channel-based services for video or voice-based sessions, as they struggle with scalability and complexity due to the increasing number of connected devices and diverse service requirements.

Method used

A method and apparatus are introduced to manage IMS call session updates through a data channel application server (DC AS), enabling terminals to transmit update requests via a data channel, with mechanisms for determining session updates, establishing bootstrap data channels, and supporting various application data channel connections.

Benefits of technology

This approach enhances the ability to manage and update IMS call sessions efficiently, supporting diverse services and improving scalability by utilizing data channels for additional services beyond traditional voice or video, thereby optimizing network resources and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096865_19112026_PF_FP_ABST
    Figure KR2026096865_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure relates to a 5G or 6G communication system for supporting an IMS data channel session management operation via a DC AS during use of an IMS-based service. Specifically, the present disclosure relates to a method and apparatus for managing information for supporting an IMS data channel session management operation via a DC AS, such as IMS session ID information being used by a specific terminal or terminals at the DC AS.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for supporting call session updates in a wireless communication system

[0001] The present disclosure relates to a method and apparatus for supporting a data channel service-based IMS session update operation using a data channel application server (DC AS) for a video or voice-based IMS session in use by a terminal or terminals in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present disclosure may provide a method and apparatus for managing IMS call session information to transmit an update request for a terminal or a call session being used by terminals to an IMS network via a data channel application server through various embodiments.

[0009] According to one embodiment of the present disclosure, a method of an MMTEL (Multi-Media Telephony) Enabler Server entity comprises: receiving a DC AS initiated IMS DC session establishment or modification service request message via the MMTEL Enabler client of UE #2, the message including a session ID, information of UE #1 (IMPU of UE #1 in target application or service, Calling ID), p-early-media support indication, application binding info, and other IMS DC-related information to be added by UE #2; transmitting the DC AS initiated IMS DC session establishment or modification service request and related information received from UE #2 to a VAL server (Application Server); receiving an IMS DC session management service request message from the VAL server (Application Server), the message including relevant policies and information for performing an IMS session update operation in the MMTEL Enabler Server, such as an Ims Session Management Policy, operation type, and ADC type (A2P / P2P / P2A2P); and the Ims Session Management Policy received from the VAL server (Application Server) and / or UE #2. A step for determining whether the IMS session to be updated based on the Session ID is a Standalone session, andA step of determining whether to check, through IMS session event monitoring, whether a bootstrap data channel has been established within the IMS session of a terminal or terminals to be updated based on IMS Session Management policy information received from the VAL server (Application Server); if it is decided to check, through IMS session event monitoring, whether a bootstrap data channel has been established within the IMS session of a terminal or terminals, a step of requesting the IMS network (IMS AS) to transmit information regarding whether a bootstrap data channel has been established within the IMS session of a specific terminal or terminals using the IMS session through an IMS session event monitoring subscription request; a step of receiving information regarding whether a bootstrap data channel has been established within the IMS session of a specific terminal or terminals using the IMS network (IMS AS) through the IMS network (IMS AS); and an IMS data channel including a request to establish a bootstrap data channel for the establishment of a bootstrap data channel and a data channel application download operation for the specific terminal or terminals if, through the IMS session event monitoring operation, a bootstrap data channel has not been established within the IMS session of the specific terminal or terminals. A step of transmitting a session management create request message (IMS DC session management create request) to the IMS network (IMS AS), and based on the response message of the IMS network based on the IMS data channel session management create request message including an IMS session event monitoring notification message or a bootstrap data channel establishment request, Session ID and p-early-media support indication, session timer, operation type, BDC & ADC type (A2P / P2P / P2A2P),The method may include the step of transmitting a data session connection request message to the IMS network (IMS AS), which includes an IMS data channel session management update request message (IMS DC session management update request) containing information such as application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, IMS Session management event subscription request, MDC2 media resource info in DC AS or MMTEL server), an application data channel establishment request message between specific terminals, and information such as application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, IMS Session management event subscription request, MDC2 media resource info in DC AS or MMTEL server).

[0010] According to one embodiment of the present disclosure, a method of an MMTEL (Multi-Media Telephony) Enabler Server entity comprises: receiving an IMS DC session management service request message from a VAL server (Application Server) that includes relevant policies and information for performing an IMS session update operation in the MMTEL Enabler Server, such as (IMS Session Management Policy, p-early-media support indication, operation type, ADC type (A2P / P2P / P2A2P), application binding information), Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, Notification Target, MDC2 media resource info in DC AS), etc.; and, when an IMS session management or IMS DC session management service request is received from the VAL server (Application Server) but a separate Session ID is not included in the service request message, determining a terminal to request IMS DC session management configuration information based on Target UE information (e.g., UE #1 or UE #2) received from the VAL server (Application Server); and the determined terminal (MMTEL Enabler Client) Session ID request indication, UE #1 info (egA step of transmitting an IMS DC session management configuration request message including IMPU of UE #1 in target application or service), Application binding info, and a step of receiving an IMS DC session management configuration response message from a terminal (MMTEL Enabler Client) that includes information related to the IMS session currently being serviced by the terminal, including Session ID, Calling ID, Called ID, Indicator of supporting Application binding info including Application ID, and Session ID and p-early-media support indication, session timer, operation type, BDC & ADC type (A2P / P2P / P2A2P), application binding information, Target UE info (e.g.The method may include the steps of: transmitting an IMS DC session management create / update request message to an IMS network (IMS AS) that includes information such as IMPU of UE #1 and / or UE #2 in target application or service, an IMS session management event subscription request of the terminal or terminals, and MDC2 media resource info in DC AS or MMTEL server according to the application data channel type; receiving an IMS DC session management create / update response or IMS DC session management Notify Request message from the IMS network that includes information such as MDC2 media resource info in MF, Session ID, Service ID or Application ID according to the application data channel type; and transmitting information within the IMS DC session management response message or notification message received from the IMS network (IMS AS) to the VAL Server (Application Server) when the VAL Server (Application Server) supports data channel services according to the Ims Session Management Policy.

[0011] According to one embodiment of the present disclosure, an IMS call session update operation currently being used by terminals or terminals can be supported through a data channel application channel.

[0012] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0013] FIG. 1 illustrates a network structure and interface using an MMTEL Enabler server and an MMTEL enabler client according to one embodiment of the present disclosure.

[0014] FIG. 2 is an example of an IMS-DC (IP (Internet Protocol) Multimedia Subsystem Data Channel) structure providing an IMS (IP (Internet Protocol) Multimedia Subsystem) service-based data channel service according to one embodiment of the present disclosure.

[0015] FIG. 3 is an example of a network operation structure for supporting an IMS call session update operation using a DC AS according to one embodiment of the present disclosure.

[0016] FIG. 4 is an example of a network operation structure for supporting an IMS call session update operation using a DC AS according to one embodiment of the present disclosure.

[0017] FIG. 5 shows the structure of a network entity according to one embodiment of the present disclosure.

[0018] FIG. 6 shows the structure of a terminal according to one embodiment of the present disclosure.

[0019] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings.

[0020] In describing the present disclosure, technical details that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure are omitted. This is intended to convey the essence of the present disclosure more clearly without obscuring it by omitting unnecessary explanations. Furthermore, the terms described below are defined considering their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0021] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0022] Hereinafter, a base station (BS) is an entity that performs resource allocation for terminals and may be at least one of gNode B, eNode B, Node B (or xNode B (where x is an alphabet including g and e)), a radio access unit, a base station controller, a satellite, an airborn, or a node on a network. A terminal (user equipment: UE) may include a Mobile Station (MS), a Vehicular, a satellite, an airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a radio transmission path for a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a radio transmission path for a signal transmitted by a terminal to a base station. Additionally, a sidelink (SL) may exist, which refers to a radio transmission path for a signal transmitted by a terminal to another terminal.

[0023] In addition, while LTE, LTE-A, or 5G systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5G-Advance or NR-Advance or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR) may be included, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0024] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0025] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0026] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0027] 3GPP, responsible for cellular mobile communication standards, has named a new core network structure "5G Core" (5GC) and is proceeding with standardization to facilitate the evolution from 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), the network core for 4G, 5GC supports the following differentiated features.

[0028] Network Slice functionality is introduced in 5GC. As a requirement for 5G, 5GC must support various types of terminals and services; e.g., enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLC), and Massive Machine Type Communications (mMTC). Each of these terminals / services has different requirements for the core network. For instance, eMBB services may require high data rates, while URLLC services may require high stability and low latency. Network Slice technology has been proposed to satisfy these diverse service requirements.

[0029] Network slicing refers to a method of creating multiple logical networks (e.g., network slices) by virtualizing a single physical network. An active network slice can be referred to as a network slice instance, and each network slice instance (NSI) can have different characteristics. Mobile operators can satisfy various service requirements for terminals / services by configuring network functions (NFs) suited to the characteristics of each NSI. For example, mobile operators can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required by each terminal.

[0030] 5GC facilitates support for network virtualization paradigms by separating mobility management functions and session management functions. In 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core entity called the Mobility Management Entity (MME), which is responsible for registration, authentication, mobility management, and session management functions. In 5G, as the number of terminals (e.g., MTC terminals) increases explosively and the mobility and traffic / session characteristics that must be supported vary depending on the terminal type, having a single entity (e.g., MME) support all functions inevitably leads to reduced scalability, which requires adding entities for specific functions. Therefore, to improve scalability in terms of the functional / implementation complexity and signaling load of the core entity responsible for the control plane, various functions are being developed based on a structure that separates mobility management functions and session management functions.

[0031] The IMS system (IP (Internet Protocol) Multimedia Subsystem) is a system for transmitting IP-based multimedia, and various services such as VoLTE and VoNR are provided through existing IMS networks linked with LTE or 5G networks. The purpose of the IMS data channel service is to provide various additional services, such as user location information transmission and screen sharing using separate applications, in addition to existing voice or video-based services, by utilizing data channel services linked with IMS in addition to existing RTP (Real-Time Transport Protocol)-based services such as voice, video, and text. The data channel service linked with IMS may be an IMS-DC (IP (Internet Protocol) Multimedia Subsystem-Data Channel) service.

[0032] In order to use an additional service or a standalone IMS data channel service using an IMS data channel within the IMS data network, the terminal may transmit a signaling message to the network that includes a request for a data channel application and related configuration information for a data channel-based service through a bootstrap data channel setup signaling process. Upon receiving the signaling message, the IMS data channel network may transmit the application or application list information to the terminal based on the settings of the user or service provider and the request information received from the terminal, thereby enabling the download of an application for the data channel service.

[0033] Based on application or application list information received from the network, the terminal can select an appropriate data channel application according to the terminal's performance and user selection, and request the corresponding data channel application. Additionally, the network may allocate a separate media function entity within the network during the bootstrap data channel setup process to support the download of a specific application requested by the terminal. The media function entity may receive data channel application-related information (Replacement HTTP URL representing the application list offered via the MDC1 interface) that can be converted into data channel application information through the operation of a media resource management service during the bootstrap data channel setup process.

[0034] Subsequently, the media function entity receives specific data channel application information selected and requested by the terminal through the Mb interface, converts the data channel application download request information into HTTP URL information recognizable by the IMS data channel network (e.g., DSCF), and performs the terminal's application download support operation.

[0035] The terminal can receive each data channel application through a bootstrap connection process and can receive information related to the data channel application simultaneously with the reception of the data channel application. Subsequently, the terminal can perform an application data channel setup signaling operation to request a data channel connection for the received data channel application. The application data channel setup signaling message may also transmit application binding information containing configuration information to support a specific application. Based on the application binding information received from the terminal, the network can perform at least one of three types of application data channel connections: a connection between terminals (P2P (peer-to-peer) Application Data Channel Setup), a connection between terminals and an application server (P2A (peer-to-application) Application Data Channel Setup), or a connection between terminals through an application server (P2A2P (peer-to-application to peer) Application Data Channel Setup).

[0036] When connecting to an IMS DC service, the terminal may request and execute bootstrap or application data channel connection operations for a standalone IMS data channel service, rather than an IMS data channel service in the form of an add-on service based on existing IMS sessions (e.g., audio / video / messaging). Additionally, when using a standalone IMS data channel service, a bootstrap data channel session connection is performed first, and the bootstrap data channel session may not always be open when using the IMS data channel service. For example, the terminal may request an application data channel connection over the network using a data channel application (e.g., a native application) pre-configured by service providers. In this case, the terminal may not proceed with the process of downloading the data channel application and related configuration information through a separate bootstrap data channel session connection. Furthermore, even if a terminal supports IMS DC services, if it lacks data channel service subscription information to use the service, the terminal may proceed with a data channel session negotiation procedure to utilize the IMS data channel service.

[0037] During the use of the IMS DC service, an update operation for a terminal or a call session being used by terminals can be performed by the terminal directly requesting an update request to the IMS network or by transmitting it to the IMS network through a data channel application server.

[0038] Figure 1 is a diagram illustrating the network structure and interface using an MMTEL Enabler server and an MMTEL enabler client.

[0039] A network entity included in the network structure of the wireless communication system of Fig. 1 may include a network function (NF) depending on the system implementation.

[0040] Referring to FIG. 1, the network structure of a wireless communication system may include various network entities. For example, a wireless communication system includes the authentication server function (AUSF) entity, the (core) access and mobility management function (AMF) entity, the session management function (SMF) entity, the policy control function (PCF) entity, the application function (AF) entity, the unified data management (UDM) entity, the data network (DN), the network exposure function (NEF) entity, the network slicing selection function (NSSF) entity, the network repository function (NRF) entity, the network data analytics function (NWDAF), the edge application service domain repository (EDR), the edge application server (EAS), the EAS discovery function (EASDF), and the user plane function: It may include a UPF entity, a (radio) access network ((R)AN), a data channel signaling function (DCSF), and a terminal, for example, a user device (UE).

[0041] In 3GPP systems, a conceptual link connecting NFs within a wireless communication system is defined as a reference point. For example, the reference point(s) included in the wireless communication system and IMS system of FIG. 1 are as follows.

[0042] - N33: Reference point between AF and NEF

[0043] - DC4: Reference point between DCSF and DC Application Server

[0044] -MDC2: Reference point for data channel media transmission between the MF (media function) and the DC Application Server

[0045] -MDC3: Reference point for data channel media transmission between DCSF and DC Application Server

[0046] Referring to FIG. 1, the network structure of the MMTEL Enabler system may include various network entities. For example, it may include an MMTel Enabler Server entity, an MMTel Enabler Client entity, an Application Server entity, a Controlling Application Server entity, an Application Client entity, a SEAL Client entity, and a SEAL server entity.

[0047] A conceptual link connecting entities within an MMTEL Enabler system is defined as a reference point. For example, the reference point(s) included in the MMTEL Enabler system of FIG. 1 are as follows.

[0048] -MMTel-1: Reference point between MMTEL Enabler Client and MMTEL Enabler Server

[0049] -MMTel-2: Reference point between MMTEL Enabler Server and Application Server

[0050] -MMTel-3: Reference point between MMTEL Enabler Server and Controlling Application Server

[0051] -MMTel-4: Reference point between MMTEL Enabler Client and DCMTSI client

[0052] -App-1: Reference point between Application Client and Application Server

[0053] -SEAL-C: Reference point between MMTEL Enabler Client and SEAL Client

[0054] -SEAL-S: Reference point between MMTEL Enabler Server and SEAL Server

[0055] -SEAL-UU: Reference point between SEAL Client and SEAL Server

[0056] FIG. 2 is an example of an IMS-DC (IP (Internet Protocol) Multimedia Subsystem Data Channel) structure providing an IMS (IP (Internet Protocol) Multimedia Subsystem) service-based data channel service according to one embodiment of the present disclosure.

[0057] The terminal can transmit a SIP (session initiation protocol) INVITE message to an existing CSCF (proxy-call session control function) to request a call session connection, such as to a P-CSCF (proxy-call session control function) or S-SCSF (serving-call session control function). The SIP INVITE message may include SDP (Session Description Protocol) information, and information regarding media-related parameters and multiplexing requirements may be included within the SDP information and transmitted to the network. Additionally, to utilize IMS data channel services, the terminal may include an SDP offer containing bootstrap information within the SIP INVITE message, along with an existing SDP offer for a video or audio session connection, and transmit it.

[0058] In the following examples, the UE #1 side network may be referred to as the Originating Network, and the network entity of the UE #1 side network may be referred to as the Originating IMS AS, Originating MF, or Originating DCSF, etc. Also, in the following examples, the UE #2 side network may be referred to as the Terminating Network, and the network entity of the UE #2 side network may be referred to as the Terminating IMS AS, Terminating MF, or Terminating DCSF, etc.

[0059] The S-CSCF (serving-call session control function), upon receiving a SIP INVITE containing SDP information, can forward the contents of the bootstrap-related SDP offer to the IMS AS if the SIP INVITE includes a bootstrap data channel SDP offer for a data channel service connection request. At this time, the S-CSCF can check whether the terminal or network supports IMS-DC based on the contents of the received bootstrap-related SDP offer; if both parties support the data channel, it can decide to forward the information for the bootstrap data channel connection to the IMS AS. Upon receiving the bootstrap-related SDP offer message from the S-CSCF, the IMS AS can first verify with the HSS (home subscriber server) whether the relevant UE or subscriber can use the data channel service. If it is determined based on the user profile that the user cannot use the data channel, the IMS AS can perform a multimedia telephony (MMTel) session setup operation without a data channel connection through the standard IMS process. In addition, if the user is unable to use data channel-based services, the IMS AS can update the SIP INVITE message by deleting the DC (data channel) related media information within the SIP INVITE message received from the S-CSCF, and then forward the updated SIP INVITE message to the S-CSCF.

[0060] If the service user can use a service based on the IMS data channel, data channel bootstrapping can be performed through a data channel call request to the DCSF (data channel signaling function). The IMS AS can select a DCSF by performing discovery and selection of a DCSF instance from the NRF based on the network operator's local configuration or information transmitted from the UE. The IMS AS can deliver a Session Event Control Notification (SessionEventControl_Notify) message containing information such as SessionEstablishmentRequestEvent, Session ID, CallingID, CalledID, SessionCase, Event initiator, MediaInfoList, and DC Stream ID to the selected DCSF.

[0061] Upon receiving a DC control request from the IMS AS, the DCSF can make policy decisions regarding how to create bootstrap data channels based on relevant parameters within the DC control request message. Additionally, the DCSF can determine MDC1 media information to enable the UE to download applications via the media function (MF) or multimedia resource function (MRF).

[0062] Based on the determined information, the DCSF can send a MediaControl_MediaInstruction message containing information such as SessionID and MediaInstructionSet to the IMS AS. The DCSF can include the MDC1 media endpoint address, DC stream ID, and alternative information for the URLs of the application list delivered from the MDC1 interface within the MediaInstructionSet and send it to the IMS AS. Based on this, the DCSF can provide the IMS AS with policies regarding how the originating and terminating sides can create bootstrap data channels using MF.

[0063] IMS AS can select an MF by using NRF to search for and select an MF instance or enhanced MRF that supports local settings or DC media functions.

[0064] The IMS AS can transmit a list of Media Termination Descriptors to the selected MF via the Nmf_MRM_Create message. The IMS AS may request the creation of two different Media Terminations. One Media Termination information may be information related to local bootstrap media, and the other Media Termination information may represent information related to remote bootstrap media to be provided to the remote UE. Each Media Termination information may include information regarding resource allocation requests for the Mb and MDC1 interfaces. The MF may transmit the negotiation results of the corresponding data channel media resource information to the IMS AS.

[0065] In the above step, the IMS AS may transmit a response to the DCSF regarding the request from the DCSF to transmit a MediaInstruction to the MF for the allocation of media resources within the MF. The response message may include information regarding the result of the operation and information regarding the negotiation of MDC1 data channel media resource information. That is, the DCSF may transmit media resource allocation information within the MF to the MF via the IMS AS as a MediaInstructionSet, and the MF may transmit the media resource allocation result within the MF and additional resource information (e.g., MDC1 interface information) to the DCSF via the IMS AS to receive the media resource allocation result within the MF and additional resource allocation information requested by the DCSF.

[0066] DCSF can store media resource information within the response message to the MediaInstruction request received from the IMS AS and forward the response message related to the data channel connection notification (SessionEventControl_Notify) request from the IMS AS to the IMS AS.

[0067] IMS AS can send a SIP INVITE message to S-CSCF containing an updated SDP offer with media information added from an MF or enhanced MRF. S-CSCF can forward the received SIP INVITE message containing the updated SDP offer to the remote network and UE#2.

[0068] UE#2 and the terminating network may include the bootstrap data channel-related SDP response in an 18X response message and forward it to the originating network. Based on the received SDP response message, the MF or enhanced MRF may update UE#2's data channel media resource information. Subsequently, UE#2 and the terminating network may send a 200 OK response message indicating that the request has been successfully completed.

[0069] The IMS AS can notify the DCSF of event information regarding a successful session connection by forwarding a SessionEventControl Notify message containing SessionEstablishmentSuccessEvent, SessionID, and MediaInfoList. Subsequently, upon receiving a response message from the DCSF regarding the notification of the successful session connection event, the IMS AS can forward a 200 OK message to UE#1 indicating that the bootstrap data channel has been established. This enables the establishment of a bootstrap data channel between UE#1, UE#2, and the originating MF or enhanced MRF. Afterward, UE#1 and UE#2 can request data channel applications by forwarding application request messages to the MF or enhanced MRF. If multi-DC applications are supported, UE#1 and UE#2 can request an application list from the MF or enhanced MRF. The MF or MRF can change the root URL to the application-related URL information based on the replacement URL information received from the DCSF. Subsequently, the MF can forward the corresponding application request message received from the UE to the DCSF. The DCSF can provide an application list or appropriate data applications to UE#1 and UE#2 depending on the UE's data channel processing capability and selection. If a terminating MF or MRF is used depending on the location of the MF, the terminal can perform the aforementioned process through the terminating DCSF and download appropriate data channel applications.

[0070] After the IMS session and bootstrap data channel connections and data channel applications have been downloaded to UE#1 and UE#2, UE#1 may send a SIP reINVITE message containing an updated SDP to the IMS AS. The updated SDP may include not only bootstrap data channel information but also application data channel request information and related DC application binding information.

[0071] The IMS AS can determine whether to notify the DCSF of a media change request event based on user subscription data information. If the IMS AS decides to notify the DCSF of the event, it can send a SessionEventControl_Notify message to the DCSF containing the MediaChangeRequest Event, Session ID, Event Direction, Event initiator, and Media Info List.

[0072] After receiving a session event notification message, the DCSF can determine a policy regarding how to execute an application data channel connection request based on the relevant parameters received through the notification message and the network operator's policy. If UE#2 is the target endpoint and an anchor for a local MF or enhanced MRF is not required, the DCSF may decide to add an application data channel media descriptor to the SDP offer. If an MF or enhanced MRF is required as an anchor for the application data channel, the DCSF may forward a Nimsas_MediaControl message to the IMS AS to instruct the IMS AS to perform the allocation of data channel media resources for the MF or enhanced MRF.

[0073] DCSF can forward a response to a session event notification message to IMS AS. Subsequently, IMS AS can forward a SIP reINVITE message to the originating S-CSCF, and S-CSCF can forward it to the terminating network and UE#2.

[0074] UE#2 and the terminating network can include a 200 OK response within the SDP response related to the application data channel and forward it to the originating network. Subsequently, the IMS AS, upon receiving an SDP offer response message containing 200 OK from the terminating network, can notify the DCSF of information regarding the successful data channel change. The DCSF sends a response to the notification to the IMS AS, and the IMS AS can then forward the 200 OK response to UE#1 via the originating S-CSCF and P-CSCF. At this time, the P-CSCF of the originating network can perform QoS procedures for the application data channel media based on the SDP response information containing the 200 OK response. UE#1 can send an ACK to the terminating network. Through the aforementioned process, the application data channel connection operation between UE#1 and UE#2 can be performed.

[0075] FIG. 3 is an example of a network operation structure for supporting an IMS session update operation using DC AS based on request information of a terminal according to one embodiment of the present disclosure.

[0076] In order to perform IMS DC service updates (adding / removing / changing data channel sessions) via the DC AS for IMS sessions currently in use by a terminal or between terminals, the DC AS must be aware of the IMS session IDs currently in use between the terminals. Based on the corresponding IMS session IDs between the terminals, the DC AS can request the IMS network (e.g., IMS AS) to perform operations related to IMS data channel services (adding / removing / changing data channel services) by transmitting an update request message for the IMS service currently in use between the terminals.

[0077] While using an IMS service (e.g., Voice or Video Call) with the Originating terminal (UE #1), the Terminating side terminal (UE #2) may transmit a request message for establishing or changing an IMS data channel session using a DC AS to the DC AS, which includes the IMS session ID currently in use with UE #1, information about UE #1, and application information related to the IMS data channel. The request message for establishing or changing an IMS data channel session using the DC AS may be transmitted from the MMTEL Enabler Client within the Terminating side terminal (UE #2) to the VAL server (Application Server) via the MMTEL Enabler Server. The VAL server (Application Server) determines whether to accept the service request for establishing or modifying an IMS data channel session using the DC AS received through the MMTEL Enabler Server; if it accepts the service request for establishing or modifying an IMS data channel session received from the MMTEL Enabler Client within the terminating terminal (UE #2), the VAL server (Application Server) determines the IMS Session Management Policy, Session ID and p-early-media support indication, operation type, ADC type (A2P / P2P / P2A2P), application binding information), and Target UE info (e.g.Relevant information to support IMS data channel session creation or update services using DC AS, such as IMPU of UE #1 and / or UE #2 in target application or service, and Notification Target, can be transmitted to the MMTEL Enabler Server.

[0078] In Step 1, the Terminating side terminal (UE #2) may determine to establish an additional data channel service connection with UE #1 while using an IMS service (e.g., Voice or Video Call) with the Originating side terminal (UE #1). After determining to perform an IMS session update operation using DC AS through the MMTEL Enabler client within the Terminating side terminal (UE #2), a request message for establishing or changing an IMS data channel session using DC AS, which includes the IMS session ID currently in use with UE #1, information about UE #1 (e.g., IMPU of UE #1 in target application or service, Calling ID), p-early-media support indication, and IMS data channel related application information (application binding info), may be transmitted to the MMTEL enabler server.

[0079] In Step 2, the MMTEL Enabler Server can check whether a separate IMS session management policy for performing IMS session update operations using DC AS is already configured or supported by receiving it from the VAL server (Application Server). If there is an IMS session management policy configured within the MMTEL Enabler Server or received from the VAL server (Application Server), Steps 3 and 4 may be omitted. If there is no separate IMS session management policy, the MMTEL Enabler Server can forward a service request message (DC AS initiated IMS DC session establishment or modification service request) to the VAL server (Application Server) for performing IMS session update operations using DC AS. The service request for performing IMS session update operations using DC AS may include the Session ID received from UE #2, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, Calling ID), p-early-media support indication, application binding info, etc.

[0080] In step 3, the VAL server (Application Server) can determine whether to support an IMS session update operation using a DC AS based on a service request message for performing an IMS session update operation using a DC AS received through the MMTEL Enabler server.

[0081] In Step 4, if the VAL server (Application Server) has determined in Step 3 to support the IMS session update operation using DC AS, it may forward an IMS session management policy service request message to the MMTEL Enabler Server. The IMS session management policy service request message may include information such as the IMS Session Management Policy to support the IMS session update operation using DC AS, UE #2's Session ID and p-early-media support indication, operation type, ADC type (A2P / P2P / P2A2P), application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, Notification Target, etc.).

[0082] In Step 5, the MMTEL Enabler Server can determine whether the IMS session requested by UE #2 is a session that supports Standalone DC services based on the IMS Session Management Policy and / or the Session ID of UE #2 within the IMS Session Management Policy service request message received from the VAL server (Application Server) in Step 4. If there is no separate Session ID associated with UE #2, the MMTEL Server can recognize that the IMS session associated with UE #2 requires support for an IMS session update operation using a DC AS that supports Standalone DC services. Based on the IMS Session Management Policy, the MMTEL Enabler Server can decide to perform an IMS session update operation based on a Standalone IMS DC if support for the Standalone IMS DC service is permitted in relation to the IMS session update operation using the corresponding DC AS.

[0083] In Step 6, the MMTEL Enabler Server can determine an action to check whether to establish a bootstrap data channel related to UE #2 in the IMS network (IMS AS) based on UE #2's Session ID. The MMTEL Enabler Server can determine whether to perform the action to check whether to establish a bootstrap data channel based on the IMS Session Management Policy.

[0084] In Step 7, the MMTEL Enabler Server can check, based on UE #2's information and UE #2's session ID, whether a bootstrap data channel has been established within the IMS session currently being used by UE #2 with UE #1 using an IMS event monitoring subscription request message to the IMS AS registered by UE #2. This IMS event monitoring subscription request message can be delivered to the HSS via the NEF. The HSS can locate the IMS AS to which UE #2 is registered via the NRF. The HSS can request the information of UE #2 and the session ID being used by UE #2 from the IMS AS selected via the NRF to be delivered, and to receive information regarding whether a bootstrap data channel has been established within the specific IMS session being used by UE #2. If a bootstrap data channel has been established within the specific IMS session being used by UE #2, the IMS AS can deliver this information to the NEF via an IMS event monitoring notification (Nimsas_ImsEE_Notify) message. NEF can transmit the IMS event monitoring result value to the AF (MMTEL Enabler Server) that requested the corresponding IMS event monitoring using the Nnef_ImsEE_Notify Request message, based on the Notification Correlation ID information of the IMS event monitoring notification (Nimsas_ImsEE_Notify) message received from IMS AS.

[0085] In Step 8, the MMTEL Enabler Server can determine the Bootstrap Data Channel (BDC) type based on the IMS event monitoring result value received from the IMS network and the application data channel type information. If the application data channel type is an Application to Person (A2P) connection between the data channel application server and a specific terminal, it can generate a P2A-based BDC connection request. If the application data channel type is a connection between terminals, it can generate a Person to Person (P2P)-based connection request and transmit it to the IMS network (IMS AS). Upon receiving an IMS session update request from the MMTEL Enabler Server that includes a Bootstrap Data Channel connection request between a specific terminal or terminals, the IMS AS can perform the steps of Step 8a and / or 8b according to the application data channel type and the information of the Target UE for establishing the application data channel. Through steps 8a and / or 8b, a bootstrap data channel establishment operation within an IMS session used by a specific terminal or terminals may be performed, and an appropriate data channel application download or update operation may be performed through the bootstrap data channel.

[0086] In Step 9, the MMTEL Enabler Server may forward an IMS Session Management Update Request Message to the NEF to perform operations to establish, remove, or modify an application data channel within an IMS session used by a specific terminal or terminals using an IMS AS. The IMS Session Management Update Request Message may include at least one of the following: IMS session information (Session ID) used by UE #2, operation type, BDC & ADC type (A2P / P2P / P2A2P), application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, IMS Session management event subscription request, MDC2 media resource info in DC AS or MMTEL server). Based on the Target UE info within the IMS Session Management Update Request Message, the NEF can find an IMS AS supporting the target UE through the HSS. Subsequently, the NEF can perform the procedure to establish an application data channel by forwarding the IMS Session Management Update Request Message received from the MMTEL Enabler Server to the specific terminal or the IMS AS supporting the terminals.

[0087] If an IMS session management operation supporting Standalone is determined in Step 5, Step 8, which is a separate bootstrap data channel establishment procedure, may be omitted. If a Standalone-based bootstrap and / or application data channel establishment procedure is performed without a separate bootstrap data channel establishment procedure and verification process, the MMTEL Enabler server may forward an IMS session management update request message to the IMS AS that additionally includes at least one of the information of a p-early-media support indication and a session timer.

[0088] In Step 10, the IMS AS may perform an action to establish an application data channel using the application data channel type and target UE information within the IMS session management update request message. If the application data channel type is a connection request for establishing an application data channel between a specific UE and a DC AS, either Step 10a or Step 10b may be performed. If the application data channel connection type is a connection between UEs (P2P or P2A2P), Steps 10a and 10b may be performed. If the data channel application requested by the DC AS is not present on the terminal, each terminal may perform a data channel application download action during the application data channel establishment procedure. If a Standalone-based bootstrap and / or application data channel establishment procedure is requested without a separate bootstrap data channel establishment procedure and verification process, a specific terminal or each terminal may simultaneously perform the bootstrap data channel establishment procedure and the data channel application download action.

[0089] In step 11, the IMS AS may transmit the result of an IMS session management update operation to the NEF via an IMS session management Notify Request message. The IMS session management Notify Request message may include at least one of the following: MDC2 media resource info in MF, Session ID, Service ID, or Application ID. The result information of the IMS session management update operation may instead be transmitted via an IMS event notification request message (Nimsas_ImsEE_Notify Request) according to the event or event category information within the IMS event monitoring subscription request message (Nnef_imsEE_Subscribe Request) requested by the MMTEL Enabler Server.

[0090] In Step 12, the NEF that has been notified of the result of the IMS session management update operation from the IMS AS may forward it to the appropriate AF (MMTEL Enabler Server). If the MMTEL Enabler Server performs the role of the DC AS in accordance with the IMS session management policy, etc., Step 12 may be omitted.

[0091] FIG. 4 is an example of a network operation structure for supporting an IMS session update operation using a DC AS according to an embodiment of the present disclosure.

[0092] In one embodiment of the present invention, in order to perform an IMS DC service update operation (adding / removing / changing a data channel session) through a DC AS regarding an IMS session currently in use between terminals or between terminals, the DC AS must recognize the IMS session ID currently in use between the terminals. Based on the IMS session ID between the terminals or between terminals, the DC AS can request the IMS network (e.g., IMS AS) to perform an operation related to the IMS data channel service (adding / removing / changing the data channel service) by transmitting an update request message for the IMS service currently in use between the terminals or between terminals.

[0093] In one embodiment of the present invention, a VAL server (Application Server) can determine an IMS data channel session creation or update service using a DC AS between specific terminals or terminals. To request an IMS session management operation service using a DC AS, the VAL server (Application Server) can transmit relevant information to an MMTEL Enabler Server to support an IMS data channel session creation or update service using a DC AS, such as an IMS Session Management Policy, Session ID and p-early-media support indication, operation type, ADC type (A2P / P2P / P2A2P), application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, Notification Target).

[0094] If the MMTEL Enabler Server does not include the IMS session ID information of a specific UE or UEs within the IMS session management operation service request message using DC AS, it may request the IMS session ID information of a specific UE or UEs from the MMTEL Enabler Client of the corresponding UE.

[0095] The MMTEL Enabler Server can forward requests for IMS session management creation or update operations using the DC AS to the IMS network (IMS AS) based on the IMS session ID information received from the MMTEL Enabler Client.

[0096] In Step 1, the VAL server (Application Server) can determine support for an IMS session update operation using the DC AS of a specific terminal or specific terminals using the service.

[0097] In Step 2, the VAL server (Application Server) may transmit an IMS session management policy service request message to the MMTEL Enabler Server based on the decision of Step 1. The IMS session management policy service request message may include information such as an IMS session management policy to support IMS session update operations using DC AS, a p-early-media support indication, an operation type, an ADC type (A2P / P2P / P2A2P), application binding information, and Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, Notification Target).

[0098] In Step 3, the MMTEL Enabler Server can check whether a separate terminal or the session ID of terminals is transmitted within the IMS session management policy service request (IMS DC session management service request) message. If the MMTEL Enabler Server has transmitted the session ID of a specific terminal or terminals to the VAL server (Application Server), it may not perform a separate request for the transmission of the IMS session ID in Steps 4 and 5. However, if the MMTEL Enabler Server has not transmitted the session ID of a specific terminal or terminals to the VAL server (Application Server), the MMTEL Enabler Server may perform a request to the MMTEL Enabler Client within the terminal to transmit the terminal-related IMS session ID.

[0099] In step 4, the MMTEL Enabler Server may transmit an IMS session management configuration request message to the MMTEL Enabler Client (e.g., MMTEL Enabler Client in UE #2) that includes at least one of the following: an IMS session ID request indication, information of the counterpart terminal connected to the current terminal for performing IMS session management updates between terminals (e.g., UE #1 info such as IMPU of UE #1 in target application or service from UE #2 case), and application binding info.

[0100] In step 5, the MMTEL Enabler Client may transmit an IMS session management configuration response message to the MMTEL Enabler Server, which includes at least one of the following: an IMS session ID currently in use by the terminal, terminal information related to the session (e.g., Calling ID, Called ID), and an indicator of supporting application binding info including Application ID.

[0101] In Step 6, the MMTEL Enabler Server can determine whether the IMS session requested by UE #2 is a session that supports Standalone DC services based on the IMS Session Management Policy within the IMS Session Management Policy service request message received from the VAL server (Application Server) in Step 2 and / or the Session ID of UE #2 received in Step 5. If no separate Session ID related to UE #2 is received from Step 5, the MMTEL Server can recognize that the IMS session related to UE #2 requires support for an IMS session update operation using a DC AS that supports Standalone DC services. In one embodiment of the present invention, the MMTEL Enabler Server can determine to perform an IMS session update operation based on a Standalone IMS DC if the support for Standalone IMS DC services is allowed for an IMS session update operation using the corresponding DC AS based on the IMS Session Management Policy.

[0102] In step 7a, the MMTEL Enabler Server can determine whether UE #2 supports the data channel application required by the DC AS based on the indicator of supporting application binding info (including Application ID) within the MS session management configuration response received from the MMTEL Enabler Client of UE #2. If UE #2 does not support the data channel application, the MMTEL Enabler Server can perform the download operation of the data channel application required by the DC AS through the operation in step 9a.

[0103] In step 7b, the MMTEL Enabler Server may determine an action to check whether to establish a bootstrap data channel related to UE #1 and / or UE #2 in the IMS network (IMS AS) based on the IMS Session IDs of UE #1 and / or UE #2. The MMTEL Enabler Server may determine whether to perform the action to check whether to establish the bootstrap data channel based on an IMS Session Management Policy.

[0104] In Step 8, the MMTEL Enabler Server can check, based on UE #2's information and UE #2's session ID, whether a bootstrap data channel has been established within the IMS session used by UE #2 using an IMS event monitoring subscription request message to the IMS AS registered by UE #2. This IMS event monitoring subscription request message can be delivered to the HSS via the NEF. The HSS can locate the IMS AS to which UE #2 is registered via the NRF. The HSS can request the information of UE #2 and the session ID used by UE #2 from the IMS AS selected via the NRF to be delivered, and to receive information on whether a bootstrap data channel has been established within the specific IMS session used by UE #2. If a bootstrap data channel has been established within the specific IMS session used by UE #2, the IMS AS can deliver this information to the NEF via an IMS event monitoring notification (Nimsas_ImsEE_Notify) message. NEF can transmit the IMS event monitoring result value to the AF (MMTEL Enabler Server) that requested the corresponding IMS event monitoring using the Nnef_ImsEE_Notify Request message, based on the Notification Correlation ID information of the IMS event monitoring notification (Nimsas_ImsEE_Notify) message received from IMS AS.

[0105] In Step 9, the MMTEL Enabler Server can determine the BDC type based on the IMS event monitoring result value received from the IMS network and the application data channel type information. If the application data channel type is an Application to Person (A2P) connection between the data channel application server and a specific terminal, it can generate a P2A-based BDC connection request. If the application data channel type is a connection between terminals, it can generate a Person to Person (P2P)-based connection request and transmit it to the IMS network (IMS AS). Upon receiving an IMS session update request from the MMTEL Enabler Server that includes a bootstrap data channel connection request between a specific terminal or terminals, the IMS AS can perform steps 9a and / or 9b according to the application data channel type and the information of the Target UE for establishing the application data channel. Through steps 9a and / or 9b, the operation to establish a bootstrap data channel within the IMS session being used by the specific terminal or terminals can be performed, and an appropriate data channel application download or update operation can be performed through the bootstrap data channel.

[0106] In Step 9, the MMTEL Enabler Server may forward an IMS Session Management Update Request Message to the NEF to perform operations to establish, remove, or modify an application data channel within an IMS session used by a specific terminal or terminals using an IMS AS. The IMS Session Management Update Request Message may include at least one of the following: IMS session information (Session ID) used by UE #2, operation type, BDC & ADC type (A2P / P2P / P2A2P), application binding information, Target UE info (e.g., IMPU of UE #1 and / or UE #2 in target application or service, IMS Session management event subscription request, MDC2 media resource info in DC AS or MMTEL server). Based on the Target UE info information within the IMS Session Management Update Request Message, the NEF can find an IMS AS supporting the target UE through the HSS. Subsequently, the NEF can perform the procedure to establish an application data channel by forwarding the IMS Session Management Update Request Message received from the MMTEL Enabler Server to the specific terminal or the IMS AS supporting the terminals.

[0107] If an IMS session management operation supporting Standalone is determined in Step 6, Step 8, which is a separate bootstrap data channel establishment procedure, may be omitted. If a Standalone-based bootstrap and / or application data channel establishment procedure is performed without a separate bootstrap data channel establishment procedure and verification process, the MMTEL Enabler server may forward an IMS session management update request message to the IMS AS that additionally includes at least one of the information of a p-early-media support indication and a session timer.

[0108] In Step 10, the IMS AS may perform an operation to establish an application data channel based on the application data channel type and target UE information within the IMS session management update request message. If the application data channel type is a connection request for establishing an application data channel between a specific UE and a DC AS, either Step 10a or Step 10b may be performed. If the application data channel connection type is a connection between UEs (P2P or P2A2P), Steps 10a and 10b may be performed. If the data channel application requested by the DC AS is not present on the terminal, each terminal may perform a data channel application download operation during the application data channel establishment procedure. If a Standalone-based bootstrap and / or application data channel establishment procedure is requested without a separate bootstrap data channel establishment procedure and verification process, a specific terminal or each terminal may simultaneously perform the bootstrap data channel establishment procedure and the data channel application download operation.

[0109] In Step 11, the IMS AS may transmit the result of an IMS session management update operation to the NEF via an IMS session management Notify Request message. The IMS session management Notify Request message may include at least one of the following: MDC2 media resource info in MF, Session ID, Service ID, or Application ID. The result information of the IMS session management update operation may instead be transmitted via an IMS event notification request message (Nimsas_ImsEE_Notify Request) according to the event or event category information within the IMS event monitoring subscription request message (Nnef_imsEE_Subscribe Request) requested by the MMTEL Enabler Server.

[0110] In Step 12, the NEF that has been notified of the result of the IMS session management update operation from the IMS AS may forward it to the appropriate AF (MMTEL Enabler Server). If the MMTEL Enabler Server performs the role of the DC AS in accordance with the IMS session management policy, etc., Step 12 may be omitted.

[0111] FIG. 5 shows the structure of a network entity according to one embodiment of the present disclosure.

[0112] The network entity of FIG. 5 can correspond to the network entity or network function described in FIG. 1 to FIG. 4.

[0113] Referring to FIG. 5, a network entity according to one embodiment of the present disclosure may be configured to include a transmitting and receiving unit (510), a memory (520), and a processor (530).

[0114] The transceiver (510) may provide an interface for performing communication with other devices within the network. That is, the transceiver (510) may convert a bit sequence transmitted from a network entity to another device into a physical signal, and convert a physical signal received from another device into a bit sequence. That is, the transceiver (510) may transmit and receive signals. Accordingly, the transceiver (510) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the transceiver (510) may be configured so that the network entity can communicate with other devices or systems via a backhaul connection (e.g., wired backhaul or wireless backhaul) or via the network.

[0115] The memory (520) can store data such as basic programs, applications, and configuration information for the operation of the core network object. The memory (520) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Additionally, the memory (520) can provide the stored data upon request from the processor (530).

[0116] The processor (530) can control the overall operations of the network entity. For example, the processor (530) can transmit and receive signals through the transceiver (510). Additionally, the processor (530) can write and read data to and from memory (520). The processor (530) may be referred to as a control unit (e.g., a controller).

[0117] FIG. 6 shows the structure of a terminal according to one embodiment of the present disclosure. The terminal of FIG. 6 can correspond to the user equipment (UE) depicted in FIG. 1 to FIG. 4.

[0118] Referring to FIG. 6, the terminal may include a transceiver (610), a memory (620), and a processor (630).

[0119] The transceiver (610) can perform functions for transmitting and receiving signals through a wireless channel. For example, the transceiver (610) can perform conversion functions between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the transceiver (610) can generate complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the transceiver (610) can restore the received bit sequence by demodulating and decoding the baseband signal. Additionally, the transceiver (610) can up-convert the baseband signal into an RF band signal and transmit it through an antenna, and down-convert the RF band signal received through the antenna into a baseband signal.

[0120] All or part of the transmitting and receiving unit (610) may be referred to as the 'transmitting unit', 'receiving unit', or 'transmitting and receiving unit'. Additionally, in the following description, transmission and reception performed via a wireless channel may be used to mean that processing as described above is performed by the transmitting and receiving unit (610).

[0121] The memory (620) can store data such as basic programs, application programs, and setting information for the operation of the terminal. The memory (620) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Additionally, the memory (620) can provide the stored data upon request from the processor (630).

[0122] The processor (630) can control the overall operations of the terminal. For example, the processor (630) can transmit and receive signals through the transceiver (610). Additionally, the processor (630) writes and reads data to and from memory (620). Furthermore, the processor (630) can perform the functions of the protocol stack required by the communication standard. To this end, the processor (630) may include at least one processor or microprocessor, or be part of a processor. Additionally, part of the communication unit (605) and the processor (630) may be referred to as a communication processor (CP).

[0123] Meanwhile, the order of description in the drawings illustrating the method proposed in this disclosure does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel. Alternatively, the drawings illustrating the method proposed in this disclosure may omit some components and include only some components to the extent that the essence of this disclosure is not compromised.

[0124] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0125] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments described in the specification of this disclosure.

[0126] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0127] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure. Terms used in the description of an embodiment of the present disclosure, such as terms for identifying a connection node, terms for designating network entities, terms for designating messages, terms for designating interfaces between network entities, and terms for designating various identification information, are provided as examples for convenience of explanation. Accordingly, the present disclosure is not limited to these terms, and other terms may be used to designate objects having equivalent technical meanings.

[0128] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0129] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by an MMTel (Multi-Media Telephony) Enabler server in a wireless communication system, A step of receiving a first request message from an application server for an IMS (Internet Protocol Multimedia Subsystem) session management service associated with a data channel; A step of obtaining an IMS session identifier based on the first request message above; and A method comprising the step of transmitting the IMS session identifier to the application server.

2. In Paragraph 1, A method further comprising the step of sending a second request message for an IMS session management update to a Network exposure function (NEF) entity.

3. In Paragraph 2, A method in which the second request message comprises at least one of the IMS session identifier, operation type, application binding information, and information about the user terminal (user equipment, UE).

4. In Paragraph 2, A method further comprising the step of receiving a response message from the above NEF entity that includes a result corresponding to the second request message.

5. In Paragraph 1, A method further comprising the step of identifying that the first request message is valid based on the above IMS session identifier.

6. In Paragraph 1, A method in which the first request message includes information about a terminal associated with the IMS session and information about an application.

7. A method performed by an application server of a wireless communication system, A step of sending a request message to an MMTel (Multi-Media Telephony) Enabler server for an IMS (Internet Protocol Multimedia Subsystem) session management service associated with a data channel; and A method comprising the step of receiving an IMS session identifier associated with the request message from the MMTel Enabler server.

8. In Paragraph 7, A method in which the first request message includes information about a terminal associated with the IMS session and information about an application.

9. Regarding the MMTel (Multi-Media Telephony) Enabler server: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the MMTel Enabler server: Receive a first request message from an application server for an IMS (Internet Protocol Multimedia Subsystem) session management service associated with a data channel, and Based on the first request message above, obtain an IMS session identifier, and An MMTel Enabler server that causes the application server to transmit the IMS session identifier.

10. In Paragraph 9, the above commands are for the MMTel Enabler server: An MMTel Enabler server that causes a Network exposure function (NEF) entity to send a second request message for an IMS session management update.

11. In Paragraph 10, The above second request message is an MMTel Enabler server comprising at least one of the above IMS session identifier, operation type, application binding information, and information about the user terminal (user equipment, UE).

12. In Paragraph 10, the above commands are for the MMTel Enabler server: An MMTel Enabler server that receives a response message containing a result corresponding to the second request message from the above NEF entity.

13. In Paragraph 9, the above commands are for the MMTel Enabler server: Identifying that the first request message is valid based on the above IMS session identifier, and The above first request message is an MMTel Enabler server that includes information about a terminal associated with the IMS session and information about an application.

14. Regarding application servers: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the application server: Send a request message to the MMTel (Multi-Media Telephony) Enabler server for an IMS (Internet Protocol Multimedia Subsystem) session management service associated with the data channel, and An application server that receives an IMS session identifier associated with the request message from the MMTel Enabler server.

15. In Paragraph 14, The above first request message is an application server that includes information about a terminal associated with the IMS session and information about an application.