Method and device for supporting IMS-DC service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, provided are a method and a device for transferring related information to a data channel application server in order to utilize IMS-related event information for a data channel service during a bootstrap data channel setup signaling or an application data channel setup signaling for an IMS-DC service connection.

Description

Method and device for supporting IMS-DC service in wireless communication system

[0001] The present disclosure relates to an IMS-DC (IP(internet protocol) Multimedia Subsystem Data Channel) service, and more particularly, to a method and device for transmitting related information to a data channel application server in order to utilize IMS-related event information for a data channel service during a bootstrap data channel setup signaling procedure or an application data channel setup signaling procedure for connecting an IMS-DC service.

[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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The IMS system is a system for transmitting IP-based multimedia. Various services, such as VoLTE and VoNR, are provided through existing IMS networks linked to LTE or 5G networks. The purpose of the IMS data channel is to provide various value-added services, such as user location information transmission and screen sharing, using separate applications, in addition to the basic voice or video-based services, by utilizing the IMS-DC service, a data channel linked to the IMS, in addition to existing RTP-based voice, video, and text services. To transmit these value-added services using the data channel within the IMS data network, the terminal transmits signaling information for the data channel-based service to the network through a bootstrap data channel connection process. The network then transmits application information to the terminal based on user or service provider settings and request information received from the terminal. This information allows the terminal to download the application for a specific service. The terminal can then request and receive the application based on this information. Furthermore, the network can allocate a separate media function entity within the network to receive data for the application and perform media resource management service operations that connect this entity to a data channel application server.

[0009] The present disclosure provides a method and device for transmitting related information to a data channel application server to provide an IMS data channel service utilizing IMS event-related information according to the service requirements of a terminal or service provider during a bootstrap or application data channel connection process for using an IMS data channel service.

[0010] According to one embodiment of the present disclosure, a method of a DCSF (Data Channel Signaling Function) entity in a wireless communication system includes the steps of receiving a request for transmission of IMS event-related information from a data channel application server based on data channel service request information, receiving subscription information for determining whether a service provider can receive IMS event-related information received from a corresponding data channel application server based on the transmission information of the IMS event-related information from an HSS (Home Subscriber Server) entity, the step of transmitting an IMS event-related information subscription message from an IMS-AS (Application server) entity to an IMS-AS based on the transmission request information of the IMS event-related information, and the step of receiving a response message.

[0011] The present disclosure provides a device and method capable of effectively providing a service in a wireless communication system.

[0012] Specifically, a method and device according to one embodiment of the present disclosure provide a method for generating IMS event-related information based on a service provider's service requirements and network information to provide an IMS data channel service utilizing IMS event-related information. Furthermore, a method for entity bootstrapping or application data channel setup for IMS event-related information is provided.

[0013] FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to an embodiment of the present disclosure.

[0014] FIG. 2 is an example of an IMS-DC (data channel) structure that provides a data channel service based on an IMS (IP (internet protocol) multimedia subsystem) service according to one embodiment of the present disclosure.

[0015] FIG. 3a is a flowchart illustrating an operation for providing IMS event subscription information to a data channel application server during a bootstrap data channel setup signaling procedure in response to an IMS-DC service connection request in a UE according to an embodiment of the present disclosure.

[0016] FIG. 3b is a flowchart illustrating an operation for providing IMS event subscription information to a data channel application server during a bootstrap data channel setup signaling process in response to an IMS-DC service connection request in a UE according to an embodiment of the present disclosure.

[0017] FIG. 4 is a flowchart illustrating information transfer and operations for requesting IMS event subscription information from a data channel application server to a DCSF according to one embodiment of the present disclosure.

[0018] FIG. 5 is a flowchart illustrating an application data channel setup signaling process using IMS event subscription information according to the connection type of the application data channel in an IMS-AS (application server) according to an embodiment of the disclosure.

[0019] FIG. 6 is a flowchart illustrating an application data channel setup signaling process using IMS event subscription information according to the connection type of the application data channel in IMS-AS according to one embodiment of the present disclosure.

[0020] FIG. 7 is a flowchart illustrating a process of transmitting and operating related information for application data channel connection based on a response message received from a remote network in IMS-AS according to one embodiment of the present disclosure.

[0021] FIG. 8 is a diagram illustrating an example configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure.

[0022] FIG. 9 is a diagram showing an example configuration of a base station in a wireless communication system according to various embodiments of the present disclosure.

[0023] FIG. 10 is a diagram showing an example configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.

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

[0025] In describing this disclosure, descriptions of technical details that are well-known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to avoid obscuring the gist of this disclosure by omitting unnecessary explanations and to convey it more clearly. Furthermore, the terms described below are defined based on their functions in this disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification as a whole.

[0026] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0027] Hereinafter, a base station (BS) is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B (or an xNode B (where x is an alphabet including g or e)), a wireless access unit, a base station controller, a satellite, an airborn, or a node on a network. A user equipment (UE) may include a mobile station (MS), a vehicle, a satellite, an airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) means a wireless transmission path of a signal transmitted from a terminal to an air station. Additionally, a sidelink (SL) may exist, which means a wireless transmission path of a signal transmitted from a terminal to another terminal.

[0028] In addition, although 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, this may include 5G-Advance or NR-Advance, or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR), and the 5G described below may also include existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0029] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0030] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0031] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0032] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. At this time, it should be noted that the same components in the attached drawings are represented by the same reference numerals as much as possible. In addition, it should be noted that the attached drawings of the present disclosure are provided to aid in understanding the present disclosure, and the present disclosure is not limited to the forms or arrangements illustrated in the drawings of the present disclosure. In addition, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted. It should be noted that in the following description, only the parts necessary for understanding the operation according to various embodiments of the present disclosure will be described, and the description of other parts will be omitted so as not to distract from the gist of the present disclosure. In addition, although the present disclosure describes various embodiments using terminology used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP)), this is merely an example for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0033] In this disclosure, phrases such as “A / B”, “A and / or B”, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B, or C”, “at least one of A, B, and C”, and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may be used simply to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0034] For convenience of explanation, this disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE (3rd Generation Partnership Project Long Term Evolution) standards and the 3GPP 5G standards. However, this disclosure is not limited to these terms and names and can be equally applied to systems conforming to other standards.

[0035] 3GPP, responsible for cellular mobile communications standards, is standardizing a new core network architecture called 5G Core (5GC) to facilitate the evolution of 4G LTE systems to 5G systems. Compared to the Evolved Packet Core (EPC), the network core for 4G, 5GC supports the following differentiated features:

[0036] Meanwhile, efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are also referred to as "Beyond 4G Network" or "Post-LTE" systems. The 5G communication system specified by 3GPP is called the New Radio (NR) system.

[0037] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies have been discussed and applied to NR systems in 5G communication systems.

[0038] Additionally, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.

[0039] In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0040] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technologies, wireless and wired communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (Information Technology) technologies with various industries.

[0041] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, 5G communication such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN), a big data processing technology described above, can also be considered an example of the convergence of 5G and IoT technologies.

[0042] 5GC introduces the Network Slice feature. As a requirement of 5G, 5GC must support a variety of terminal types and services, such as enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). These terminals and services each have different requirements for the core network. For example, eMBB services may require high data rates, while URLLC services may require high reliability and low latency. To meet these diverse service requirements, Network Slice technology has been proposed.

[0043] Network slicing can refer to a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An activated network slice can be called a network slice instance, and each network slice instance (NSI) can have different characteristics. By configuring a network function (NF) for each NSI according to its characteristics, mobile carriers can satisfy various service requirements according to terminals / services. For example, mobile carriers can efficiently support various 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI that matches the characteristics of the service required for each terminal.

[0044] 5GC can easily support the network virtualization paradigm by separating mobility management functions from 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. In 5G, the number of terminals (including MTC terminals) will explode, and the mobility and traffic / session characteristics that must be supported depending on the terminal type will become more specialized. Therefore, supporting all functions from a single entity (such as the MME) will inevitably reduce scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates mobility management and session management functions to improve scalability in terms of functional / implementation complexity and signaling load of the core entity responsible for the control plane.

[0045] Interactive services require very low latency to support two-way communication, and additional requirements arise when used for content transmission for interactive services to improve accessibility as mentioned above. In the present disclosure, in order to use a service utilizing a data channel-based application requiring very low latency, a terminal or a service provider server may provide a low latency value required for providing the service to the network when requesting a service connection, and the network may provide a function to search for and select an appropriate media function entity based on the required latency value when connecting a bootstrap data channel of a service utilizing the data channel-based application.

[0046] The present disclosure introduces a method for establishing a connection for a service utilizing a data channel-based application requiring very low latency, and a process for performing a connection operation between network entities to provide low latency through a boostslack data channel setup signaling process based on the related information by transmitting related parameters to a network. When the information is transmitted in the 3gpp-hint-qos field for low latency requirements within the SIP (session initiation protocol) or when an application server registers the data channel-related information with a data channel signaling function entity within a data channel server, low latency information required for using the application-related service can be registered together. The IMS-AS that receives the above information can utilize the related information when searching for a network function entity to select a media function entity that takes end-to-end delay into account based on service requirements. Additionally, when registering a network function within the NRF of a media function entity, related information can be additionally included in the media profile to support discovery of the network function entity based on the low latency requirement in IMS-AS, etc., and selection of the media function entity based on the information.

[0047] FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to an embodiment of the present disclosure.

[0048] A network entity included in the network structure of the 5G system of Fig. 1 may include a network function (NF) depending on the system implementation and may also be called a network node.

[0049] Referring to FIG. 1, the network structure of a 5G system may include various network entities. For example, the 5G system may include an authentication server function (AUSF) entity (108), an access and mobility management function (AMF) entity (103), a session management function (SMF) entity (105), a policy control function (PCF) entity (106), an application function (AF) entity (107), a unified data management (UDM) entity (109), a data network (DN) entity (110), a network exposure function (NEF) entity (111), a network slicing selection function (NSSF) entity (114), a network repository function (NRF) entity (115), a network data analytics function (NWDAF), and an edge application service domain repository (EDS). It may include a domain repository (EDR), an edge application server (EAS), an EAS discovery function (EASDF), a user plane function (UPF) entity (104), a (radio) access network ((R)AN) (102), and a terminal, for example, a user equipment (UE) (101).

[0050] Each NF entity in the 5G system supports the following functions:

[0051] AUSF (108) processes and stores data for authentication of UE (101).

[0052] AMF (103) provides functions for access and mobility management per UE, and one UE can be connected to one AMF by default. Specifically, the AMF (103) provides signaling between CN nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (e.g., N2 interface), termination of non-access stratum (NAS) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including, for example, control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (e.g., for AMF events and interfaces to the LI system), provision of forwarding of session management (SM) messages between UE and SMF, transparent proxy for SM message routing, access authentication, and roaming authorization. It supports functions such as access authorization including checks, provision of SMS message transmission between UE and SMSF, security anchor function (SAF) and / or security context management (SCM). Some or all of the functions of an AMF entity (103) may be supported within a single instance of an AMF entity.

[0053] DN (110) refers to, for example, an operator service, Internet access, or a third-party service. DN (110) transmits a downlink protocol data unit (PDU) to the UPF entity (104) or receives a PDU transmitted from the UE (101) from the UPF entity (104).

[0054] The PCF entity (106) receives information about packet flows from the application server and provides a function to determine policies such as mobility management and session management. Specifically, the PCF entity (106) supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function entity(ies) (e.g., AMF entity, SMF entity, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination within a user data repository (UDR).

[0055] The SMF entity (105) provides a session management function, and when the UE (101) has multiple sessions, each session can be managed by a different SMF entity. Specifically, the SMF entity (105) is responsible for session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF entity (104) and the (R)AN (102) node), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, setting up traffic steering to route traffic from the UPF entity (104) to the appropriate destination, termination of the interface to policy control functions, enforcement of the control portion of the policy and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the session management (SM) portion of NAS messages, downlink data notification, initiation of AN (access network) specific SM information (delivered to the (R)AN (102) via N2 via the AMF entity (103)), determination of the session and service continuity (SSC) mode of the session, and roaming. Supports functions such as functions, etc. Some or all functions of an SMF entity (105) can be supported within a single instance of an SMF entity.

[0056] The UDM entity (109) stores user subscription data, policy data, etc. The UDM entity (109) includes two parts: an application front end (FE) and a user data repository (UDR).

[0057] The FE (front end) includes the UDM FE, which is responsible for location management, subscription management, and credential processing, and the PCF entity, which is responsible for policy control. The UDR stores the data required for the functions provided by the UDM-FE and the policy profiles required by the PCF entity. The data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE accesses the subscription information stored in the UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.

[0058] The UPF entity (104) forwards the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102), and forwards the uplink PDU received from the UE (101) via the (R)AN (102) to the DN (110). Specifically, the UPF entity (104) supports functions such as an anchor point for intra / inter RAT mobility, an external PDU session point for interconnection to the Data Network, a user plane part of packet routing and forwarding, packet inspection and policy rule enforcement, an uplink classifier to support lawful intercept, traffic usage reporting, routing of traffic flows to the Data Network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering. Some or all of the functions of a UPF entity (104) may be supported within a single instance of a UPF.

[0059] The AF entity (107) interacts with the 3GPP core network to provide services (e.g., supporting functions such as application impact on traffic routing, access to network capability exposure, and interaction with the policy framework for policy control).

[0060] (R)AN(102) is a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB).

[0061] The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink / downlink (i.e., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon attachment of the UE if routing to the AMF is not determined from the information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from the AMF), scheduling and transmission of system broadcast information (originating from the AMF or operating and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, and QoS flows. It supports features such as mapping to management and data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

[0062] UE (101) refers to a user equipment. The user equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, the user equipment may be a portable device such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or may be a non-portable device such as a personal computer (PC) or vehicle-mounted device.

[0063] The NEF (111) provides a means to securely expose services and capabilities provided by 3GPP network functions, for example, for third parties, internal exposure / re-exposure, application functions, and edge computing. The NEF (111) receives information from other NF (s) (based on the exposed capability(s) of other NF (s)). The NEF (111) can store the received information as structured data using a standardized interface to a data storage network function. The stored information can be re-exposed to other NF entity(s) and AF entity(s) by the NEF entity (111) and used for other purposes, such as analysis.

[0064] EASDF is an NF that can add an ECS (EDNS (extension mechanisms for DNS) client subnet) option that can be expressed as the address of a DNS server to which a DNS (domain name system) request of a terminal will be forwarded, and an IP subnet address to be added when forwarding a DNS request of the terminal, for each FQDN (fully qualified domain name). EASDF receives EAS (exchange active sync) domain configuration information from EDR, and processes a DNS request message received from a terminal according to the received information. In addition, EASDF is an NF that receives a terminal IP address, location information of the terminal within 3GPP, DNS message processing rules, and DNS message reporting rules from the SMF (105), processes a DNS Query message received from the terminal, a DNS response message received from a DNS server, and transmits information in a DNS message and statistical information processed therefrom to the SMF (105) according to the DNS message reporting rules.

[0065] NRF (115) supports service discovery. It receives NF discovery requests from NF instances and provides information about discovered NF instances to the NF instances. It also maintains available NF instances and the services they support.

[0066] Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE (101) accesses one DN (110) using one PDU session, but the present disclosure is not limited thereto.

[0067] A UE (101) can access two (i.e., local and central) data networks simultaneously using multiple PDU sessions. In this case, two SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.

[0068] Additionally, the UE (101) may simultaneously access two (i.e., local and central) data networks provided within a single PDU session.

[0069] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. As an example, the reference point(s) included in the 5G system in Figure 1 are illustrated, and the 5G system architecture may define more reference points than those described below.

[0070] - N1: Reference point between UE (101) and AMF (103)

[0071] - N2: Reference point between (R)AN(102) and AMF(103)

[0072] - N3: Reference point between (R)AN(102) and UPF(104)

[0073] - N4: Reference point between SMF (105) and UPF (104)

[0074] - N5: Reference point between PCF (106) and AF (107)

[0075] - N6: Reference point between UPF (104) and DN (110)

[0076] - N7: Reference point between SMF (105) and PCF (106)

[0077] - N8: Reference point between UDM (109) and AMF (103)

[0078] - N10: Reference point between UDM (109) and SMF (105)

[0079] - N11: Reference point between AMF (103) and SMF (105)

[0080] - N12: Reference point between AMF (103) and AUSF (108)

[0081] - N13: Reference point between UDM (109) and AUSF (108)

[0082] - N14: Reference point between two AMFs (103)

[0083] - N15: Reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario.

[0084] - Nx: Reference point between SMF(105) and EASDF

[0085] - Ny: Reference point between NEF (EDF) (111) and EASDF

[0086] Hereinafter, the present disclosure describes a method for transmitting and / or receiving multiple applications and multiple streams transmitted from a data channel application server and a remote UE (user equipment) through a data stream using a single port in the UE. Specifically, the present disclosure may describe a media resource management service operation for supporting multiplexing of data streams through a media function entity or IMS-AGW within a network. In addition, the UE may transmit a request for application-related information supporting multiplexing to the network through a bootstrap data channel setup process, and the network receiving the request may transmit an application list including application information supporting multiplexing to the UE to support a service supporting multiplexing.

[0087] FIG. 2 is an example of an IMS-DC (IP (internet protocol) multimedia subsystem data channel) structure that provides a data channel service based on an IMS (IP (internet protocol) multimedia subsystem) service according to one embodiment of the present disclosure.

[0088] A terminal can transmit a SIP (session initiation protocol) INVITE message to an existing CSCF for a call session connection request (e.g., P-CSCF (proxy - call session control function) and S-SCSF (serving - call session control function)). The SIP INVITE message can include media-related parameters and multiplexing-related requirement information in the SDP (Session Description Protocol) and transmit them together to the network. In addition, the terminal can transmit an SDP offer including bootstrap information together with an SDP offer for connecting an existing video or audio session, etc., in the SIP INVITE message in order to use an IMS data channel service.

[0089] The S-CSCF, which has received the SIP INVITE including the above SDP information, can forward the contents of the bootstrap data channel SDP offer to 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. In addition, if both sides support the data channel, the S-CSCF can decide to forward the information for the bootstrap data channel connection for the data channel connection to IMS-AS.

[0090] The IMS-AS, which receives the bootstrap-related SDP offer message from the S-CSCF, can first check with the HSS (home subscriber server) whether the UE or subscriber can use the data channel service. If the user cannot use the data channel based on the user profile, the IMS-AS can perform the MMTel (multimedia telephony) session setup operation without connecting the data channel through the general IMS process. In addition, if the user cannot use the data channel-based service, the IMS-AS can update the SIP INVITE message received from the S-CSCF by deleting the DC (data channel)-related media information, and then forward the updated SIP INVITE message to the S-CSCF.

[0091] When a service user can use an IMS data channel-based service, the S-CSCF can perform data channel bootstrapping through a data channel call request to the Data Channel Signaling Function (DCSF). IMS-AS can select a DCSF by performing discovery and selection of a DCSF instance from NRF based on the network operator's local configuration or information transmitted from the UE. IMS-AS can forward a Session Event Control Notification (SessionEventControl_Notify) message containing at least one of the following information to the DCSF selected through the above process: SessionEstablishmentRequestEvent, Session ID, CallingID, CalledID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID.

[0092] Upon receiving a DC control request from IMS-AS, the DCSF can make policy decisions regarding how to create a bootstrap data channel based on the relevant parameters in the DC control request message. Furthermore, the DCSF can determine MDC1 media information to enable the UE to download applications via the MF or MRF.

[0093] Based on the above-determined MDC1 media information, DCSF can forward a MediaControl_MediaInstruction message containing at least one of the following information: SessionID or MediaInstructionSet, to IMS-AS. DCSF can also forward the MediaInstructionSet to IMS-AS, including at least one of the following information: MDC1 media endpoint address, DC stream ID, or alternative information for the URL of the application list transmitted on the MDC1 interface. Accordingly, DCSF can provide IMS-AS with a policy on how to create a bootstrap data channel using MF on the originating and terminating sides.

[0094] IMS-AS can select an MF through a process of searching and selecting an MF instance or enhanced MRF supporting local configuration or DC media capabilities using NRF.

[0095] IMS-AS can forward a list of Media Termination Descriptors to the MF selected in the above process via the Nmf_MRM_Create message. IMS-AS can request the creation of two different Media Terminations. One Media Termination may be local bootstrap media-related information, and the other may indicate remote bootstrap media-related information to be provided to a remote UE. Each Media Termination may include resource allocation request information for the Mb and MDC1 interfaces. The MF can forward the result of the negotiation of the corresponding data channel media resource information to IMS-AS.

[0096] IMS-AS may send a response to a MediaInstruction request from DCSF. The response message may include information regarding the result of the operation and MDC1 data channel media resource information negotiation information.

[0097] DCSF can store media resource information in a response message to a MediaInstruction request received from IMS-AS, and can forward a response message related to a data channel connection notification (SessionEventControl_Notify) request from IMS-AS to IMS-AS.

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

[0099] UE#2 and the terminating network can forward the SDP response related to the bootstrap data channel to the originating network in an 18X response message. Based on the received SDP response message, the MF or enhanced MRF can update the data channel media resource information of UE#2. Afterwards, UE#2 and the terminating network can send a 200 OK response message indicating that the request has been successfully completed.

[0100] IMS-AS can notify DCSF of successful session connection related event information by sending a SessionEventControl Notify message containing at least one of SessionEstablishmentSuccessEvent, SessionID, or MediaInfoList. Afterwards, IMS-AS, which receives a response message for successful session connection event notification from DCSF, can send UE#1 a 200 OK message indicating that a bootstrap data channel has been connected. Through the above-described operations, a bootstrap data channel connection can be established between UE#1 and UE#2 and the originating MF or enhanced MRF. Afterwards, UE#1 and UE#2 can request a data channel application by sending an application request message to the MF or enhanced MRF. If multiple 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 application-related URL information based on the replacement URL information received from DCSF. Afterwards, the MF can forward the 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 based on the data channel processing capability and selection of the UE. UE#1 and UE#2 can perform the above-described process through the terminating DCSF, if they use the terminating MF or MRF depending on the location of the MF, and can download the appropriate data channel application.

[0101] After the IMS session and bootstrap data channel connection and data channel application are downloaded to UE#1 and UE#2, UE#1 can send a SIP reINVITE message containing an updated SDP to IMS-AS. The updated SDP may include at least one of the application data channel request or related DC application binding information in addition to the bootstrap data channel information.

[0102] IMS-AS can determine whether to notify DCSF of a media change request event based on user subscription data information. If IMS-AS decides to notify DCSF of an event, it can forward a SessionEventControl_Notify message containing at least one of the following: MediaChangeRequest Event, Session ID, Event Direction, Event Initiator, or Media Info List.

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

[0104] DCSF can forward a response to the Session Event Notification message to IMS-AS. IMS-AS can then forward a SIP reINVITE message to the originating S-CSCF, which can then forward the SIP reINVITE message to the terminating network and UE#2.

[0105] UE#2 and the terminating network can forward the 200 OK response to the originating network within the SDP response related to the application data channel. Afterwards, the IMS-AS, which receives the SDP offer response message including the 200 OK response from the terminating network, can notify the DCSF of the successful data channel change. The DCSF will send a response to the notification to the IMS-AS, and the IMS-AS can then forward the 200 OK response to UE#1 through the originating S-CSCF and P-CSCF. At this time, the P-CSCF of the originating network can perform the QoS procedure of the application data channel media based on the SDP response information including the 200 OK response. UE#1 can send an ACK to the terminating network. Through the above process, the application data channel connection operation between UE#1 and UE#2 can be performed.

[0106] FIG. 3a and FIG. 3b are flowcharts illustrating an operation for providing IMS event subscription information to a data channel application server during an entity bootstrap data channel setup signaling procedure in response to an IMS-DC (IP (internet protocol) multimedia subsystem data channel) service connection request in a UE according to one embodiment of the present disclosure.

[0107] In step 301, the terminal may transmit a SIP INVITE message containing request information for a video or audio session connection to a CSCF, such as a P-CSCF and an S-SCSF. The terminal may include media-related parameters such as video or audio, and QoS-related requirement information in the SDP and transmit them to the network using the SIP INVITE message. In addition, bootstrap information for an IMS data channel session connection may be transmitted together in the SDP offer to request a service connection using additional data in addition to the existing video or audio-based session connection request.

[0108] The S-CSCF, which has received the SIP INVITE including the above SDP information, can forward the contents of the bootstrap data channel SDP offer for a data channel service connection request to the IMS-AS if the SIP INVITE includes a bootstrap data channel SDP offer. 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. In addition, the S-CSCF can decide to forward information for a bootstrap data channel connection for a data channel connection to the IMS-AS if both sides support a data channel.

[0109] In step 302, the IMS-AS, which has received the bootstrap-related SDP offer message from the S-CSCF, can check with the HSS whether the UE (e.g., UE#1) or subscriber can use the data channel service. If the user cannot use the data channel based on the user profile, the MMTel session setup operation can be performed without connecting the data channel through the general IMS process. In addition, if the user cannot use the data channel-based service, the IMS-AS can update the SIP INVITE message received from the S-CSCF by deleting the DC-related media information in the SIP INVITE message, and then forward the updated SIP INVITE message to the S-CSCF.

[0110] When a service user can utilize an IMS data channel-based service, data channel bootstrapping can be performed by requesting a data channel call to DCSF. IMS-AS can select a DCSF by performing discovery and selection of a DCSF instance from NRF based on the network operator's local configuration or information received from the UE.

[0111] In step 303, IMS-AS may forward a session event control notification (SessionEventControl_Notify) message containing at least one of SessionEstablishmentRequestEvent, Session ID, CallingID, CalledID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID to the DCSF selected according to the information forwarded from the UE in step 302 or the network operator policy.

[0112] In step 304, DCSF, which has received a DC control request for IMS-DC service connection from IMS-AS, may perform a policy decision related to the bootstrap data channel based on the relevant parameters in the DC control request message (e.g., including at least one of CallingID, CalledID, or DC Stream ID) and the DCSF service policy.

[0113] In step 305, DCSF may determine MDC1 media information (e.g., MDC1 Endpoint information on DCSF side) to enable each UE to download applications via MF or MRF.

[0114] In step 306, the DCSF may determine whether to provide the data channel application server with application-related information for supporting the data channel service and IMS event subscription information at the request of the data channel application service provider based on the relevant parameters in the DC control request message. In the embodiments of the present disclosure, in FIGS. 3A and 3B , it may be assumed that the data channel service provider has previously set application-related information for providing the IMS data channel service utilizing IMS event-related information based on at least one of terminal information (e.g., Calling ID and DC stream ID) or receiver information (e.g., Called ID) when registering the application and related information with the DCSF. As in the embodiment of FIG. 4 , when the data channel service provider provides application-related information to the DCSF, it may also transmit request information for subscribing to IMS event-related information of a specific application. Thereafter, the DCSF may check, through the HSS entity, information on whether the data channel service provider or a specific application can receive IMS event-related information, and it may be assumed that the setup for transmitting IMS event-related information between the data channel application server and the DCSF has already been completed.

[0115] In step 307, the DCSF may transmit IMS event information and related subscriber information (e.g., including at least one of a Calling ID, a DC stream ID, or a Called ID) to the IMS-AS to receive IMS event subscription information, including at least one of an IMS Communication Service Identifier (ICSI), an IMS Application Reference Identifier, or Subscribed Supplementary services information. The DCSF may request transmission of the information when the event is updated or information is changed. In addition, the DCSF may request separate IMS event subscription information for specific subscribers and subscriber groups.

[0116] In step 308, IMS-AS can filter IMS event-related information required by a specific application based on the IMS event information and related subscriber information received from DCSF in step 307, and can generate IMS event subscription information required by the data channel application server.

[0117] In step 309, IMS-AS may forward application-specific IMS event subscription information to DCSF based on the filtered IMS event-related information forwarded in step 307. Furthermore, IMS event subscription information may be provided differently for each user or specific user group. If IMS-AS provides separate event subscription information for each subscriber or subscriber group, the IMS event subscription information may include separate subscriber information or subscriber group information.

[0118] In steps 310 and 311, the DCSF may forward the IMS event subscription information received from the data channel application server to the NEF and / or DC-AS based on the IMS event subscription information and related information received from the IMS-AS. If the data channel application server is an application server of a trusted operator, the DCSF may forward the IMS event subscription information directly to the data channel application server via the DC4 interface without going through the NEF. If the data channel application server is not trusted or 3 rd In the case of a party application server, DCSF can pass IMS event subscription information to NEF via DC3 interface and can pass initial IMS event subscription information to data channel application server via N33 interface.

[0119] In step 312, DCSF may forward to IMS-AS a MediaControl_MediaInstruction message containing at least one of SessionID and MediaInstructionSet information based on information received from the data channel application server. DCSF may include at least one of the following substitute information in the MediaInstructionSet: an MDC1 media endpoint address, a DC stream ID, or a URL of an application list containing application information that supports multiplexing transmitted on the MDC1 interface. Through the above-described operations, DCSF may provide IMS-AS with a policy on how to create a bootstrap data channel using MF on the originating and terminating sides.

[0120] In step 313, IMS-AS can select MF or enhanced MRF based on the information received from DCSF. IMS-AS can forward NF Discovery Request (NFDiscovery_Request) message to NRF for discovery and selection of MF instance or enhanced MRF. NRF can select appropriate MF based on MF profile information in NF Discovery Request message transmitted from IMS-AS for MF selection. NRF can select MF that satisfies MF profile requirements received from IMS-AS and forward MF profile information to IMS-AS via NF Discovery Request Response message.

[0121] In steps 314 and 315, the IMS-AS may forward a list of Media Termination Descriptors to the MF selected in the above process (e.g., step 313) via an Nmf_MRM_Create message. The IMS-AS may request the creation of two different Media Terminations. One Media Termination may be local bootstrap media-related information, and the other Media Termination may indicate remote bootstrap media-related information to be provided to a remote UE. Each Media Termination may include resource allocation request information for the Mb and MDC1 interfaces. The MF may forward the result of the negotiation of data channel media resource information to the IMS-AS.

[0122] In step 316, after IMS-AS receives the data channel media resource allocation result from MF, IMS-AS may transmit a response to the MediaInstruction request (MediaControl_MediaInstruction) to DCSF. The response message may include the result information of the above operation (e.g., steps 314 and 315) and MDC1 data channel media resource information negotiation information.

[0123] In step 317, DCSF may store media resource information in a response message for a MediaInstruction request received from IMS-AS, and may forward a response message related to a data channel connection notification (SessionEventControl_Notify) request from IMS-AS to IMS-AS.

[0124] At step 318, the IMS-AS may send a SIP INVITE message to the S-CSCF containing at least one of an updated SDP offer with added media information of the MF or enhanced MRF or a request for IMS event subscription information related to the remote UE on the remote network.

[0125] In step 319, the S-CSCF may forward at least one of the updated SDP offers, including the media information of the received MF or enhanced MRF or the request for IMS event subscription information related to the remote UE on the remote network, to the remote network and UE#2 in a SIP INVITE message.

[0126] In step 320, the remote network and UE#2 may perform the negotiation process between the remote network and the terminal for a bootstrap data channel connection based on the updated SDP offer information received in step 319 in the same or similar manner as originating. If a request for IMS event subscription information related to a remote UE on the remote network is received, the remote network and UE#2 may receive the IMS event subscription information related to the remote UE on the remote network from the IMS-AS of the remote network and include it in a 200 OK response message.

[0127] In step 321, the remote network (Terminating) and the UE may forward an SDP response to the originating network in an 18X response message if there is a requirement for an update or change related to the bootstrap data channel. Based on the received SDP response message, the MF or enhanced MRF may update the data channel media resource information related to UE#2.

[0128] At step 322, the remote network and the UE (e.g., UE#2) may send a 200 OK response message containing the remote UE related IMS event subscription information on the remote network to the S-CSCF of the originating network.

[0129] In step 323, the S-CSCF, which has received a 200 OK response message including remote UE related IMS event subscription information on the remote network from the remote network and the UE (e.g., UE#2), may forward the remote UE related IMS event subscription information on the remote network in the 200 OK response message to the IMS-AS.

[0130] In step 324, the IMS-AS, which receives a 200 OK message from the S-CSCF containing IMS event subscription information related to the remote UE on the remote network, may forward a SessionEventControl_Notify message containing IMS event subscription information related to the remote UE on the remote network to the DCSF to inform it of event information related to a successful session connection. If the IMS event subscription information related to the remote UE on the remote network is received in step 324, the DCSF may forward the IMS event subscription information of the remote network to the data channel application server through steps 327 and 328.

[0131] In steps 325 and 326, IMS-AS may receive a response message for a successful session connection event notification from DCSF. IMS-AS may then forward a 200 OK message to UE#1 containing Bootstrap-related SDP answer information indicating that the Bootstrap Data Channel connection setup has been successfully completed.

[0132] If the IMS event subscription information is changed or updated, IMS-AS may transmit the updated or changed IMS event subscription information corresponding to a specific subscriber or subscriber group to DCSF in step 326.

[0133] In steps 327 and 328, the DCSF, which receives updated or changed IMS event subscription information from the IMS-AS, forwards the information to the data channel application server, which forwards the updated or changed IMS event subscription information to the data channel application server, thereby providing the IMS data channel service.

[0134] In steps 329 and 330, operations for bootstrap data channel connection can be performed between UE#1, UE#2, and originating MF or enhanced MRF. The terminal that has received the application list including application information supporting multiplexing can select an application supporting multiplexing according to the selection of the service user or the policy of the network operator. Thereafter, the UE can transmit an application request message to the DCSF through the MF or enhanced MRF to download an application supporting multiplexing. The MF or MRF can change the root URL of the application request message received from the UE to application-related URL information based on the replacement URL information received from the DCSF in step 314. Thereafter, the MF or MRF can transmit the application request message received from the UE to the DCSF through MDC1. The DCSF can provide the application list or appropriate data applications to UE#1 and UE#2 according to the data channel processing capability and selection of the UE. If the requested data channel application is not available in the DCSF, the DCSF can request the application from the data channel application server and transmit the requested data channel application to UE #1 and UE #2 via MDC1 and MDC3. Through the above process, the terminal can download the application transmitted through the IMS data channel, and at the same time, receive application-related information such as application binding information. The application-related information may include a Bootstrap DC stream ID, which indicates through which Bootstrap channel the transmitted application was transmitted.Application-related information may provide information on which data channel server (e.g., DCSF) the terminal received the application from through the Bootstrap DC stream ID or Bootstrap DC ID, and may then include the information in the application data channel setup signaling process to provide information for connecting to the appropriate data channel server.

[0135] In steps 331 and 332, an IMS data channel service may be provided through a bootstrap data channel connection using the MF or MRF on the terminating network, depending on the location of the MF or MRF. A terminal that has received an application list including application information supporting the multiplexing may select an application supporting the multiplexing according to the service user's choice or the network operator's policy. Thereafter, each UE may transmit an application request message to the terminating DCSF through the MF or enhanced MRF on the terminating network to download the corresponding application. The terminating DCSF may provide the application list or appropriate data applications to UE#1 and UE#2 according to the data channel processing capability and selection of the UE. If the requested data channel application is not available in the DCSF, the DCSF may request the corresponding application from the data channel application server and transmit the application to UE#1 and UE#2 through MDC1 and MDC3. The application-related information may include a Bootstrap DC stream ID, which indicates through which Bootstrap channel the corresponding application was transmitted. Application-related information may provide information on which data channel server (e.g., DCSF) the terminal received the application from through the Bootstrap DC stream ID or Bootstrap DC ID, and may then include the information in the application data channel setup signaling process to provide information for connecting to the appropriate data channel server.

[0136] FIG. 4 is a flowchart illustrating information transfer and operations for requesting IMS event subscription information from a data channel application server to a DCSF according to one embodiment of the present disclosure.

[0137] At step 401, the data channel application server may decide to request IMS event subscription information from the IMS network from the data channel application server of a specific application or a specific subscriber or subscriber group.

[0138] In steps 402 and 403, the data channel application server may forward an IMS event subscription information request message to the DCSF via NEF, the message including application-related information including at least one of a Called ID or an IMS Application Reference Identifier, IMS event subscription information including at least one of Subscribed Supplementary services, or an IMS Communication Service Identifier (ICSI).

[0139] In steps 404 and 405, the DCSF can check with the HSS whether the requested IMS event subscription information is available from the data channel application server based on the IMS event subscription information request message.

[0140] In steps 406 and 407, the DCSF may forward a response message of the IMS event subscription information request, including whether the IMS event subscription information request is accepted, to the data channel application server if the data channel application service provider can receive IMS event subscription information. Thereafter, if the DCSF receives the IMS event subscription information from the IMS-AS through the bootstrap data channel or application data channel setup signaling process, the DCSF may forward the IMS event subscription information to the data channel application server using steps 406 and 407.

[0141] DCSF can receive IMS event subscription information and application-related information from the data channel application server in advance through the embodiment of FIG. 4. Furthermore, DCSF can request IMS event subscription information from IMS-AS based on the application and specific subscriber information requested by the terminal during the bootstrap data channel or application data channel setup signaling process.

[0142] FIG. 5 is a flowchart illustrating an operation for providing IMS event subscription information to a data channel application server during an application data channel setup signaling process in response to an IMS-DC session connection request in a UE according to an embodiment of the present disclosure.

[0143] FIG. 5 is a flowchart illustrating a method of transmitting information for updating DCSF policies and updating related media resources within an MF entity to perform a connection operation of an application data channel considering a P2A (Person to Application) connection type according to one embodiment of the present disclosure.

[0144] In step 501, the IMS-AS may receive an SDP offer message related to an application data channel for an application data channel connection from the terminal through the S-CSCF. The IMS-AS may request the DCSF for an application data channel connection based on the application data channel connection request message including the SDP offer information and the bootstrap stream ID received from the S-CSCF. At this time, if the IMS-AS performs the application data channel connection through the local DCSF based on the bootstrap stream ID, the local IMS-AS may determine to generate a SessionEvent_Control_Notify message. In addition, if the IMS-AS performs the application data channel connection through the remote DCSF based on the bootstrap stream ID, the IMS-AS may retransmit the SDP offer information received from the S-CSCF through the S-CSCF to request that the SDP offer information be transmitted in the remote network. The S-CSCF in the remote network that has received the updated SDP offer may request to perform the application data channel connection. When a service user can use an IMS data channel-based service, IMS-AS can perform a media data channel connection operation for exchanging application data by sending a session connection request to DCSF for setting up an application data channel. IMS-AS can select a DCSF (e.g., a local DCSF or a remote DCSF) based on the Bootstrap DC ID received during the bootstrap data channel connection process. In this embodiment, it can be assumed that the application data channel connection operation is performed using a local DCSF and MF.

[0145] In step 502, IMS-AS may forward a SessionEventControl_Notify message containing at least one of MediaChangeRequest Event, Session ID, Event Direction, Event initiator, or Media Info List information for an application data channel connection request to DCSF.

[0146] In step 503, the DCSF, which has received information including the media change request event, can recognize, based on application-related binding information, that IMS event subscription information needs to be transmitted to the data channel application server when using the IMS data channel service via the data channel application. If the DCSF recognizes that IMS event subscription information needs to be transmitted, it can perform a data channel control policy update for the application data channel using the IMS event subscription information.

[0147] In step 504, the DCSF may generate related information for connecting to a data channel application server based on the media-related information received from the IMS-AS if the connection type of the application data channel is a P2A connection type. Based on the related information related to the application data channel, the DCSF may determine to generate data channel media resource information including information for connecting to a media data channel (MDC2 Endpoint) and update a data channel control policy if the connection type of the application data channel is an application data channel using a data channel application server.

[0148] In step 505, the DCSF may decide to request IMS event subscription information from the originating network side, considering the application data connection type and data channel application-related policies and requirements. The DCSF may determine whether to provide application-related information for supporting a data channel service and IMS event subscription information to the data channel application server based on the relevant parameters in the DC control request message and upon the request of the corresponding data channel application service provider. In an embodiment of the present disclosure, it may be assumed that the data channel service provider has previously transmitted application-related information to the DCSF, which provides an IMS data channel service utilizing IMS event-related information, based on at least one of terminal information (e.g., including at least one of a Calling ID or a DC stream ID) or receiver information (e.g., a Called ID). As in the embodiment of FIG. 4, when the data channel service provider provides application-related information to the DCSF, it may also transmit request information for subscribing to IMS event-related information of a specific application.

[0149] In step 506, the DCSF may include information related to the MF and the data channel application server for application data channel connection in the data channel media resource information and transmit the information to the IMS-AS through media-related instruction (MediaInstruction) information for media control. The media resource information may include information for updating or adding data channel media resources within the MF entity. The IMS-AS may transmit packets in the data channel on the user plane from each UE to the MF or enMRF. The MF or enMRF may receive media resource information from the DCSF, including media instruction information for transmitting packets in the data channel on the user plane received from the IMS-AS to the data channel application server using the MDC2 interface. The IMS-AS may transmit the allocation of media resource information and a request for MDC2 media information to the MF. Using the MDC2 media information request, the MF may allocate data channel media resources for transmitting application data transmitted from the UE to the data channel application server.

[0150] In step 507, the DCSF may transmit to the IMS-AS at least one of the IMS event information or related subscriber information (e.g., including at least one of the Calling ID, DC stream ID, or Called ID) including at least one of the IMS Communication Service Identifier (ICSI), the IMS Application Reference Identifier, or the Subscribed Supplementary services information to receive the IMS event subscription information. The DCSF may request transmission of updated or changed information when the event is updated or the information is changed. In addition, the DCSF may request separate IMS event subscription information for specific subscribers and subscriber groups.

[0151] In step 508, the IMS-AS can filter IMS event-related information required by a specific application based on at least one of the IMS event information or related subscriber information received from the DCSF in step 507, and generate IMS event subscription information required by the data channel application server.

[0152] In step 509, IMS-AS may transmit application-specific IMS event subscription information based on the filtered IMS event-related information transmitted in step 507. Furthermore, IMS event subscription information may be provided differently for each user or specific user group. If separate event subscription information is provided for each subscriber or subscriber group, IMS-AS may provide separate subscriber information or subscriber group information within the IMS event subscription information.

[0153] In steps 510 and 511, the DCSF may forward the IMS event subscription information received from the IMS-AS to the corresponding data channel application server based on at least one of the IMS event subscription information or related information. If the data channel application server is an application server of a trusted operator, the DCSF may forward the IMS event subscription information directly to the data channel application server through the DC4 interface without going through the NEF. If the data channel application server is not trusted or 3 rd In the case of a party application server, DCSF can pass IMS event subscription information to NEF via DC3 interface and can pass initial IMS event subscription information to data channel application server via N33 interface.

[0154] In step 512, the IMS-AS, which has received the data channel media resource including the MDC2 media information and the updated SDP information, can forward the media resource information for the application data channel connection considering the P2A connection type to the MF or enMRF via a media resource management request (Nmf_MRM_Create Request) message. If the UE's application data is to be forwarded to the data channel application server using the MRF, the UE can request the MRF to allocate the relevant data channel media resource via the Mr' / Cr interface.

[0155] In step 513, the MF may forward the MDC2 media information and media resource allocation result information of the MF to the IMS-AS via a media resource management request response (Nmf_MRM_Create Request Response) message, taking into account the P2A connection type.

[0156] At step 514, IMS-AS may forward media resource information of MF entity for P2A connection including MDC2 media information received from MF or enMRF to DCSF.

[0157] In steps 515 and 516, DCSF may store media resource information and then forward a P2A application data channel establishment request to the data channel application server via DC3 or DC4. If the data channel application server accepts the application data channel establishment request forwarded through the above process, the data channel application server may forward MDC2-related SDP response information (MDC2 media endpoint information) to DCSF.

[0158] In step 517, the DCSF may perform a data channel media resource update based on the MDC2 media endpoint information of the data channel application server received from the data channel application server, and then transmit the updated data channel media resource information to IMS-AS based on the MDC2 related SDP response information (MDC2 media endpoint information).

[0159] In steps 518 and 519, IMS-AS may request resource update of media function entity based on updated data channel media resource information and receive the update result value from MF.

[0160] In step 520, IMS-AS may notify DCSF of response information for a media control related instruction including the result of a successful data channel related media resource update after receiving the update result value from MF.

[0161] In step 521, after the DCSF is notified of the response information for the media control related instruction, the DCSF may transmit a response message including an updated SDP answer based on the MDC2 related information for application data channel connection considering the P2A connection for the media control related instruction to the IMS-AS. When the IMS-AS receives the data channel related response message from the DCSF for application data channel connection based on the P2A connection type, the IMS-AS may add the response message transmitted from the remote network to a 200 OK response message and transmit it to UE #1. In addition, when transmitting a SIP re-INVITE to the remote network, the IMS-AS may delete the application data channel related SDP offer information and transmit only the video or audio related SDP offer.

[0162] Through the above process, IMS-AS can perform an application data channel connection operation utilizing IMS event subscription information considering the P2A connection type and an operation for allocating media resources within the MF entity for the application data channel connection between the data channel application server and the terminal. Based on the result of the above operation, IMS-AS can forward a SIP re-INVITE message containing an updated SDP offer to the remote network through the S-CSCF.

[0163] FIG. 6 is a flowchart illustrating an application data channel setup signaling process according to a connection type of an application data channel in IMS-AS according to an embodiment of the present disclosure.

[0164] FIG. 6 is a flowchart illustrating a method for transmitting information for updating DCSF policies and updating related media resources within an MF entity to perform a connection operation of an application data channel considering a P2A2P (Person to Application to Person) connection type according to one embodiment of the present disclosure.

[0165] In step 601, the IMS-AS may receive an SDP offer message related to an application data channel for an application data channel connection from the terminal through the S-CSCF. The IMS-AS may request the DCSF for an application data channel connection based on the application data channel connection request message including the SDP offer information and the bootstrap stream ID received from the S-CSCF. At this time, the IMS-AS may determine to generate a SessionEvent_Control_Notify message in the local IMS-AS if the application data channel connection is performed through the local DCSF based on the bootstrap stream ID. If the application data channel connection is performed through the remote DCSF based on the bootstrap stream ID, the IMS-AS may retransmit the SDP offer information received from the S-CSCF through the S-CSCF to request that the SDP offer information be transmitted in the remote network. The S-CSCF in the remote network that has received the updated SDP offer may request to perform an application data channel connection. When a service user can utilize an IMS data channel-based service, IMS-AS can perform a media data channel connection operation for exchanging application data by requesting a session connection for setting up an application data channel with DCSF. IMS-AS can select a DCSF (e.g., a local DCSF or a remote DCSF) based on the Bootstrap DC ID received during the bootstrap data channel connection process. In this embodiment, it can be assumed that the application data channel connection operation is performed using a local DCSF and MF.

[0166] In step 602, IMS-AS may forward a SessionEventControl_Notify message containing at least one of a MediaChangeRequest Event, a Session ID, an Event Direction, an Event initiator, or a Media Info List for an application data channel connection request to DCSF.

[0167] In step 603, the DCSF, having received information including a media change request event, can recognize, based on application-related binding information, that IMS event subscription information needs to be transmitted to the data channel application server when using the IMS data channel service via the data channel application. Furthermore, the DCSF can update the data channel control policy for the application data channel using the IMS event subscription information.

[0168] In step 604, the DCSF may generate related information for connecting to a data channel application server based on the media-related information received from the IMS-AS if the connection type of the application data channel is a P2A2P connection type. If the connection type of the application data channel is an application data channel using a data channel application server, the DCSF may determine to generate data channel media resource information including information for connecting to a media data channel (MDC2 Endpoint) and update a data channel control policy based on the related information related to the application data channel.

[0169] In step 605, the DCSF may decide to request IMS event subscription information from the originating and remote (terminating) network side, considering the application data connection type, data channel application-related policies and requirements. The DCSF may determine whether to provide application-related information for supporting the data channel service and IMS event subscription information at the request of the corresponding data channel application service provider to the data channel application server based on the relevant parameters in the DC control request message. In an embodiment of the present disclosure, it may be assumed that the data channel service provider has previously transmitted application-related information to the DCSF, which provides an IMS data channel service utilizing IMS event-related information, based on information such as terminal information (e.g., including at least one of a Calling ID or a DC stream ID) and receiver-side information (e.g., a Called ID). As in the embodiment of FIG. 4, when the data channel service provider provides application-related information to the DCSF, request information for subscribing to IMS event-related information of a specific application may be transmitted together.

[0170] In step 606, the DCSF may include information related to the MF and the data channel application server for application data channel connection in the data channel media resource information and transmit the information to the IMS-AS through the media-related instruction (MediaInstruction) information for media control. The media resource information may include information for updating or adding data channel media resources within the MF entity. The IMS-AS may transmit packets in the data channel on the user plane from each UE to the MF or enMRF. The MF or enMRF may receive media resource information including media instruction information for transmitting packets in the data channel on the user plane to the data channel application server using the MDC2 interface from the DCSF. The IMS-AS may transmit the allocation of media resource information and a request for MDC2 media information to the MF. Using the MDC2 media information request, the MF may allocate data channel media resources for transmitting application data transmitted from the UE to the data channel application server.

[0171] In step 607, the DCSF may transmit to the IMS-AS at least one of the IMS event information or related subscriber information (e.g., at least one of the Calling ID, the DC stream ID, or the Called ID) including at least one of the IMS Communication Service Identifier (ICSI), the IMS Application Reference Identifier, or the Subscribed Supplementary services information to receive the IMS event subscription information. The DCSF may request the IMS-AS to transmit the updated or changed information when the event is updated or the information is changed. In addition, the DCSF may request the IMS-AS to provide separate IMS event subscription information for a specific subscriber or subscriber group.

[0172] In step 608, IMS-AS can filter IMS event-related information required by a specific application based on the IMS event information and related subscriber information received from DCSF in step 607, and generate IMS event subscription information required by the data channel application server.

[0173] In step 609, IMS-AS may forward application-specific IMS event subscription information to DCSF based on the filtered IMS event-related information transmitted in step 607. Furthermore, IMS event subscription information may be provided differently for each user or specific user group. When providing event subscription information for each subscriber or subscriber group, separate subscriber information or subscriber group information may be provided within the IMS event subscription information.

[0174] In steps 610 and 611, the DCSF can forward the IMS event subscription information received from the IMS-AS to the data channel application server based on the IMS event subscription information and related information. If the data channel application server is an application server of a trusted operator, the DCSF can forward the IMS event subscription information directly to the data channel application server through the DC4 interface without going through the NEF. If the data channel application server is not trusted or 3 rd In the case of a party application server, DCSF can pass IMS event subscription information to NEF via DC3 interface and initial IMS event subscription information to data channel application server via N33 interface.

[0175] In step 612, the IMS-AS, which has received the data channel media resource including the MDC2 media information and the updated SDP information, can forward the media resource information for the application data channel connection considering the P2A2P connection type to the MF or enMRF via a media resource management request (Nmf_MRM_Create Request) message. If the UE's application data is to be forwarded to the data channel application server using the MRF, the UE can request the MRF to allocate the relevant data channel media resource via the Mr' / Cr interface.

[0176] In step 613, the MF may forward the MDC2 media information and media resource allocation result information of the MF to the IMS-AS via a media resource management request response (Nmf_MRM_Create Request Response) message, taking into account the P2A2P connection type.

[0177] At step 614, IMS-AS may forward media resource information of MF entity for P2A2P connection including MDC2 media information received from MF or enMRF to DCSF.

[0178] In steps 615 and 616, DCSF may store media resource information and then forward a P2A2P application data channel establishment request to the data channel application server via DC3 or DC4. If the data channel application server accepts the application data channel establishment request forwarded through the above process, the data channel application server may forward MDC2-related SDP response information (MDC2 media endpoint information) to DCSF.

[0179] In step 617, the DCSF may update the data channel media resource based on the MDC2 media endpoint information of the data channel application server received from the data channel application server. Furthermore, the DCSF may forward the updated data channel media resource information to IMS-AS based on the MDC2-related SDP response information (MDC2 media endpoint information).

[0180] In steps 618 and 619, IMS-AS may request resource update of media function entity based on updated data channel media resource information and may receive update result value from MF.

[0181] In step 620, after the IMS-AS receives the update result value from the MF, it can notify the DCSF of the response information for the media control related instruction including the result of the successful data channel related media resource update.

[0182] In step 621, after receiving response information for a media control related instruction, the DCSF may forward a response message for a session event control notification, which includes at least one of MDC2 related information for application data channel connection considering a P2A2P connection for the media control related instruction, or a request for IMS event subscription information of a remote network, to the IMS-AS. The IMS-AS, which has received the information, may forward an updated SIP re-INVITE message, which includes at least one of MDC2 related information or a request for IMS event subscription information of a remote network, to the remote network.

[0183] Through the above process, IMS-AS can perform an application data channel connection operation utilizing IMS event subscription information considering the P2A2P connection type and an operation for allocating media resources within the MF entity for the application data channel connection between the data channel application server and the terminal. Based on the result of the above operation, IMS-AS can forward a SIP re-INVITE message containing an updated SDP offer to the remote network through the S-CSCF.

[0184] FIG. 7 is a flowchart illustrating a process of transmitting and operating related information for application data channel connection based on a response message received from a remote network in IMS-AS according to one embodiment of the present disclosure.

[0185] In steps 701 and 702, IMS-AS may receive from DCSF at least one of data channel resource allocation (MDC2 Endpoint) or IMS event subscription request-related information according to the connection type of the application data channel in FIGS. 5 and 6. IMS-AS may forward a SIP re-INVITE message containing updated SDP offer information to the remote network based on the information received from DCSF. If the connection type is P2A, the re-INVITE message may not include an SDP offer related to the application data channel.

[0186] In step 703, a negotiation process for an application data channel connection between the remote network and the terminal may be performed based on the SIP re-INVITE information including the updated SDP offer information received in step 702. At this time, the remote network and the terminal may determine an application data channel connection based on IMS event subscription information depending on whether the remote network supports IMS-AS.

[0187] In steps 704 and 705, if the remote UE and network support provision of IMS event subscription information, the remote network and the terminal may forward updated SDP answer information including the IMS event subscription information of the IMS-AS within the remote network to the Originating Network via a 200 OK response message. The S-CSCF may forward the information within the 200 OK response message forwarded from the remote network and the UE to the IMS-AS.

[0188] If the updated SDP answer information is in response to an application data channel connection request using a P2A connection type, the audio and video related SDP responses can be included in a 200 OK response message and passed to IMS-AS via S-CSCF. S-CSCF can forward the 200 OK response message to IMS-AS, and IMS-AS can notify DCSF of the result of a successful media change request event.

[0189] Based on the SDP Answer information including the remote network's IMS event subscription information received from the remote network and the UE in step 706, the IMS-AS can notify the DCSF that the application data channel connection has been successfully completed.

[0190] In steps 707 and 708, the DCSF may forward the IMS event subscription information of the remote network received from the IMS-AS to the data channel application server based on the IMS event subscription information and related information of the remote network. If the data channel application server is an application server of a trusted operator, the DCSF may forward the IMS event subscription information of the remote network directly to the data channel application server through the DC4 interface without going through the NEF. If the data channel application server is an untrusted or third-party application server, the DCSF may forward the IMS event subscription information of the remote network to the NEF through the DC3 interface, and may forward the initial IMS event subscription information of the remote network to the data channel application server through the N33 interface.

[0191] In step 709, the DCSF, which received the session event control notification message in step 706, may forward a response to the notification message to IMS-AS.

[0192] In steps 710 and 711, the IMS-AS may forward a 200 OK message containing SDP Answer information received from the remote network and UE to the P-CSCF via the S-CSCF. In the case of an application data channel using a P2A connection type, the IMS-AS may add a response message (SDP answer for P2A connection between UE#1 and DC-AS) regarding the connection request information between UE#1 and the data channel application server to the 200 OK response message containing audio and video related SDP responses received from the remote network and UE#2, and forward the message to the S-CSCF and P-CSCF.

[0193] In step 712, the P-CSCF may forward application data channel information in the SDP Answer for QoS allocation to the PCF based on the information in the 200 OK message so that an appropriate QoS can be allocated.

[0194] In step 713, the P-CSCF, which has received QoS information based on the application data channel information, can finally transmit 200 OK information to the UE.

[0195] At step 714, UE#1 can finally transmit to the remote network and UE#2 via an ACK message that successful application data channel establishment has been completed based on information from the remote network and the UE.

[0196] Step 715a is an application data channel connection considering the P2A connection type, where UE #1 can use an audio or video related IMS call session with UE #2, while simultaneously using an IMS data channel related service by using the data channel application server, MDC2, and the application data channel.

[0197] Steps 715b and 715c are application data channel connections considering the P2A2P connection type, where UE #1 and UE #2 can exchange application data through a data channel application server via MF or enMRF.

[0198] FIG. 8 is a diagram illustrating an example configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure.

[0199] The network entity of FIG. 8 may be one of the network entities described in the embodiments of FIGS. 1 to 7.

[0200] A network entity according to one embodiment of the present disclosure may include a processor (810) that controls the overall operation of the network entity, a transceiver (820) including a transmitter and a receiver, and a memory (830). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 8.

[0201] According to one embodiment of the present disclosure, the transceiver (820) can transmit and receive signals with at least one of other network entities or terminals. The transmitted and received signals may include at least one of control information and data. If the network entity of FIG. 8 is a core network entity (NF), the signals transmitted and received between the network entity and the terminal may be transmitted and received via the RAN.

[0202] According to one embodiment of the present disclosure, the processor (810) may control the overall operation of the corresponding network entity to perform an operation according to one or a combination of two or more of the embodiments of FIGS. 1 to 7 described above. Meanwhile, the processor (810), the transceiver (820), and the memory (830) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (810) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (820) may include at least one communication interface for transmitting and receiving signals with another network entity via wired / wireless.

[0203] According to one embodiment of the present disclosure, the memory (830) can store data such as basic programs, application programs, and setting information for the operation of the corresponding network entity. In addition, the memory (830) provides the stored data upon request of the processor (810). The memory (830) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (830). In addition, the processor (810) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (830).

[0204] FIG. 9 is a diagram illustrating an example configuration of a base station in a wireless communication system according to various embodiments of the present disclosure. The base station of FIG. 9 may refer to the RAN node described in the embodiments of FIGS. 1 to 7.

[0205] A base station according to one embodiment of the present disclosure may include a processor (910) that controls the overall operation of the base station, a transceiver (920) including a transmitter and a receiver, and a memory (930). Of course, the present invention is not limited to the above example, and the base station may include more or fewer components than those illustrated in FIG. 9.

[0206] According to one embodiment of the present disclosure, a transceiver (920) can transmit and receive signals with at least one of a terminal, another base station, or a network entity. The transmitted and received signals can include at least one of control information and data.

[0207] According to one embodiment of the present disclosure, the processor (910) may control the overall operation of the base station to perform operations according to one or a combination of two or more of the embodiments of FIGS. 1 to 7 described above. Meanwhile, the processor (910), the transceiver (920), and the memory (930) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (910) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (920) may include at least one communication interface for transmitting and receiving signals wired / wirelessly to and from a terminal, another base station, or a network entity.

[0208] According to one embodiment of the present disclosure, the memory (930) can store data such as basic programs, application programs, and setting information for the operation of the corresponding base station. In addition, the memory (930) provides the stored data upon request of the processor (910). The memory (930) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (930). In addition, the processor (910) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (930).

[0209] FIG. 10 is a diagram showing an example configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.

[0210] A terminal according to one embodiment of the present disclosure may include a processor (1010) that controls the overall operation of the terminal, a transceiver (1020) including a transmitter and a receiver, and a memory (1030). Of course, the present invention is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 10.

[0211] According to one embodiment of the present disclosure, a transceiver (1020) can transmit and receive signals with at least one other terminal, base station, or network entity. The transmitted and received signals can include at least one of control information and data.

[0212] According to one embodiment of the present disclosure, the processor (1010) may control the overall operation of the terminal to perform an operation according to one or a combination of two or more of the embodiments of FIGS. 1 to 7 described above. Meanwhile, the processor (1010), the transceiver (1020), and the memory (1030) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (1010) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (1020) may include at least one communication interface for transmitting and receiving signals with another terminal, a base station, or a network entity via wired / wireless.

[0213] According to one embodiment of the present disclosure, the memory (1030) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In addition, the memory (1030) provides the stored data upon request of the processor (1010). The memory (1030) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (1030). In addition, the processor (1010) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (1030).

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

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

[0216] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0217] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0218] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0219] Meanwhile, a part or all of one or more embodiments proposed in the present disclosure may be applied in combination with a part or all of one or more other embodiments, and such combination forms are also included within the scope of the present disclosure.

[0220] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below but also by equivalents thereof. Furthermore, the above-described embodiments may be combined and operated as needed, as long as there is no technical contradiction.

Claims

1. The method of DC-SF (data channel signaling function) entity in a wireless communication system is as follows: A step of receiving a first request message including first information for subscribing to an IMS (IP (internet protocol) multimedia subsystem) event from a DC-AS (data channel application server); and A step of transmitting a response message to the first request message to the DC-AS, A method, wherein the first information includes at least one of application related information or IMS event subscription information.

2. In paragraph 1, the method, A step of receiving a second request message including second information from IMS-AS (application server); and A method further comprising a step of identifying whether to transmit the first information to the DC-AS based on the second information.

3. In paragraph 1, The above application-related information includes at least one of a Called ID (identifier) ​​or an IMS application reference ID, A method, wherein the IMS event subscription information includes at least one of a subscribed supplementary service or an IMS communication service identifier (ICSI).

4. In paragraph 1, A method, wherein the second information includes at least one of SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID.

5. The method of IMS-AS (IP (internet protocol) multimedia subsystem application server) entity in a wireless communication system is as follows: A step for identifying whether a terminal can use a service based on IMS-DC (data channel); A method comprising the step of transmitting a first request message including first information using DC-SF (data channel signaling function) when the terminal can use the IMS DC-based service.

6. In paragraph 5, The second information for subscribing to an IMS event is transmitted to the DC-AS (data channel application server) based on the first information. A method, wherein the second information includes at least one of application related information or IMS event subscription information.

7. In paragraph 6, The above application-related information includes at least one of a Called ID (identifier) ​​or an IMS application reference ID, A method, wherein the IMS event subscription information includes at least one of a subscribed supplementary service or an IMS communication service identifier (ICSI).

8. In paragraph 5, A method, wherein the first information includes at least one of SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID.

9. In a wireless communication system, the DC-SF (data channel signaling function) entity is Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one of the above control units: Receive a first request message including first information for subscribing to an IMS (IP (internet protocol) multimedia subsystem) event from a DC-AS (data channel application server), and It is set to transmit a response message to the above first request message to the DC-AS, A DC-SF entity, wherein the first information comprises at least one of application related information or IMS event subscription information.

10. In paragraph 9, at least one control unit: Receive a second request message including second information from IMS-AS (application server), and A DC-SF entity further configured to identify whether to transmit the first information to the DC-AS based on the second information.

11. In paragraph 9, The above application-related information includes at least one of a Called ID (identifier) ​​or an IMS application reference ID, A DC-SF entity, wherein the IMS event subscription information includes at least one of a subscribed supplementary service or an IMS communication service identifier (ICSI).

12. In paragraph 9, A DC-SF entity, wherein the second information includes at least one of SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID.

13. In a wireless communication system, the IMS-AS (IP (internet protocol) multimedia subsystem application server) entity, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one of the above control units: Identify whether the terminal can use IMS-DC (data channel)-based services, and An IMS-AS entity configured to transmit a first request message including first information using DC-SF (data channel signaling function) when the terminal can use the IMS DC-based service.

14. In paragraph 13, The second information for subscribing to an IMS event is transmitted to the DC-AS (data channel application server) based on the first information. The second information includes at least one of application-related information or IMS event subscription information, The above application-related information includes at least one of a Called ID (identifier) ​​or an IMS application reference ID, An IMS-AS entity, wherein the above IMS event subscription information includes at least one of a subscribed supplementary service or an IMS communication service identifier (ICSI).

15. In paragraph 13, An IMS-AS entity, wherein the first information includes at least one of SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, SessionCase, Event initiator, MediaInfoList, or DC Stream ID.

Images