Method and device for providing data service in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a first network entity in a wireless communication system according to one embodiment of the present disclosure may comprise the steps of: storing Internet protocol multimedia subsystem (IMS) application server (AS)-related information; and if an application function (AF) request message is authenticated, receiving, from a second network entity, a terminal subscription information request message, wherein the AF request message may include transmission from a data channel (DC) AS to the second network entity.

Description

Method and device for providing data services in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method for subscribing to and receiving notifications of IMS events in order to provide data channel services in an IMS framework of a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in 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] An object of the present invention is to provide, according to one embodiment of the disclosure, a method and apparatus for subscribing to and receiving notification of an IMS event provided in a wireless communication system.

[0009] The present invention for solving the above problems is characterized in that the method performed by a first network entity in a wireless communication system includes the steps of storing information related to an Internet Protocol Multimedia Subsystem (IMS) AS (Application Server); and, when an Application Function (AF) request message is authenticated, receiving a terminal subscription information request message from a second network entity, wherein the AF request message is transmitted from a Data channel (DC) AS to the second network entity.

[0010] In one embodiment, the method further comprises the step of transmitting a message including a list of user subscription services including a terminal ID or group ID to the second network entity.

[0011] In one embodiment, the method further comprises the step of transmitting an event subscription message to an IMS AS.

[0012] In one embodiment, the IMS AS related information is characterized in that it is registered with the first network entity and allocated by the terminal.

[0013] In addition, in another embodiment of the present invention, a method performed in a second network entity in a wireless communication system comprises the steps of: receiving an AF (Application Function) request message from a DC (Data channel) AS (Application Server); authenticating the AF request message; and transmitting a terminal subscription information request message to a first network entity when the AF request message is authenticated, characterized in that information related to an IMS (Internet Protocol Multimedia Subsystem) AS is stored in the first network entity.

[0014] In addition, in another embodiment of the present invention, in a wireless communication system, a first network entity includes a transceiver capable of transmitting and receiving at least one signal; and a control unit coupled to the transceiver, wherein the control unit is configured to store IMS (Internet Protocol Multimedia Subsystem) AS (Application Server) related information, and, when an AF (Application Function) request message is authenticated, receive a terminal subscription information request message from a second network entity, and the AF request message is characterized in that it is transmitted from a DC (Data channel) AS to the second network entity.

[0015] In addition, in another embodiment of the present invention, in a wireless communication system, a second network entity includes a transceiver capable of transmitting and receiving at least one signal; and a control unit coupled to the transceiver, wherein the control unit is configured to: receive an AF (Application Function) request message from a DC (Data channel) AS (Application Server), authenticate the AF request message, and, when the AF request message is authenticated, transmit a terminal subscription information request message to a first network entity, and IMS (Internet Protocol Multimedia Subsystem) AS related information is characterized in that it is stored in the first network entity.

[0016] According to one embodiment of the present invention, it is possible to subscribe to and receive notifications for IMS events more effectively.

[0017] FIG. 1 is a diagram illustrating a mobile communication system structure according to one embodiment of the present disclosure.

[0018] FIG. 2 is a diagram illustrating an IMS structure for providing a data channel in a mobile communication system according to an embodiment of the present disclosure.

[0019] FIG. 3 is a diagram illustrating a method and procedure for managing IMS AS information in a wireless communication system according to an embodiment of the present disclosure.

[0020] FIG. 4 is a diagram illustrating a method and procedure for managing IMS AS information in a wireless communication system according to an embodiment of the present disclosure.

[0021] FIG. 5 is a diagram illustrating an IMS data channel setup procedure according to an embodiment of the present invention.

[0022] FIG. 6 is a diagram illustrating an IMS event subscription chain procedure according to an embodiment of the present invention.

[0023] FIG. 7 is a diagram illustrating the structure of a terminal according to one embodiment of the present invention.

[0024] FIG. 8 is a diagram illustrating the structure of a network entity according to one embodiment of the present invention.

[0025] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Furthermore, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Furthermore, the terms described below are defined based on their functions within the present invention and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0026] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0027] The present disclosure relates to a device and method for providing data services in a wireless communication system. Specifically, the present disclosure describes a technique for subscribing to and receiving notifications of IMS events in order to provide data channel services within the IMS (Internet Protocol Multimedia Subsystem) framework of a wireless communication system.

[0028]

[0029] FIG. 1 is a diagram illustrating a mobile communication system structure according to one embodiment of the present disclosure.

[0030] 5GS (5G System) can be composed of a terminal (UE), a New Radio (NR) base station (NG-RAN), and a 5G core network. Referring to FIG. 1, the 5G core network can be composed of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), a Unified Data Management (UDM), a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), and a Unified Data Repository (UDR). A terminal (UE) can access a 5G core network through a base station ((R)AN). Hereinafter, the UE may be referred to as a terminal, and the (R)AN may be referred to as a base station. In addition, the 5G core network may further include an Application Function (AF) and a Data Network (DN).

[0031] In one embodiment, AMF is a Network Function (NF) that manages wireless network access and mobility for a terminal.

[0032] SMF is an NF that manages sessions for terminals, and session information includes QoS (Quality of Service) information, charging information, and packet processing information.

[0033] UPF is an NF that handles user traffic (e.g., User Plane traffic) and is controlled by SMF.

[0034] The PCF is an NF that manages operator policy (PLMN policy) for providing services in a wireless communication system. Additionally, the PCF can be divided into a PCF responsible for AM (Access and Mobility) policy and UE policy, and a PCF responsible for SM (Session Management) policy. The PCF responsible for AM / UE policy and the PCF responsible for SM policy can be logically or physically separate NFs, or they can be a single NF.

[0035] UDM is an NF that stores and manages subscriber information (UE subscription) of terminals.

[0036] A UDR is a network function (NF) or database (DB) that stores and manages data. It stores terminal subscription information and can provide it to the UDM. Additionally, it can store operator policy information and provide it to the PCF.

[0037] NSSF may be an NF that performs the function of selecting network slice instances that serve a terminal or determining Network Slice Selection Assistance Information (NSSAI).

[0038] AUSF may be an NF that performs functions to support authentication for 3GPP access and non-3GPP access.

[0039] An AF may be an NF that provides functions for a service according to the present disclosure.

[0040] DN may refer to a data network that can provide business services, Internet access, or third-party services.

[0041]

[0042] FIG. 2 is a diagram illustrating an IMS structure for providing a data channel in a mobile communication system according to an embodiment of the present disclosure.

[0043] The Proxy-Call Session Control Function (P-CSCF) is the primary contact point for IMS. Messages transmitted by terminals first reach the P-CSCF. When interacting with the PCF, the P-CSCF acts as an Application Function (AF).

[0044] The Interrogating-CSCF (I-CSCF) is the contact point within the operator's network for all connections to users. During the registration process, the I-CSCF allocates a Serving-CSCF (S-CSCF) for the terminal to process Session Initiation Protocol (SIP) registration. During session-related procedures, the I-CSCF obtains the address of the S-CSCF from the Home Subscriber Server (HSS). It forwards received SIP request messages to the S-CSCF. It also generates a Charging Data Record (CDR) related to billing and resource usage.

[0045] The S-CSCF (Serving-CSCF) performs session control services for terminals. It manages session states. It acts as a register for registration. That is, it accepts registration request messages and stores related information in a location server (e.g., HSS). If the HSS contains policy information for the terminal's Public User Identity, it provides the information to the P-CSCF and / or the terminal. In session-related procedures, the S-CSCF performs session control. It accepts or forwards session requests. It handles interactions with the service platform for the provided services. It provides service event-related information to endpoints. It generates CDRs related to billing and resource usage.

[0046] HSS (or UDM) is a server that stores user subscription information and service information.

[0047] The IMS Application Server (AS) interacts with the Data Communication Signaling Functions (DCSF) for event notification. The IMS AS receives data channel control instructions from the DCSF and interacts with the Data Channel Media Function (DCMF) to manage data channel media resources accordingly.

[0048] IMS-AGW is an IMS access gateway.

[0049] The Media Resource Function (MRF) controls media stream resources. It interprets information from the AS and S-CSCF, controls resource control and allocation, and generates CDRs.

[0050] DCSF is a control function that provides data channel control. DCSF does not participate in SIP signaling. The DSCF receives event reports from the IMS AS and determines whether to provide data services. DCSF manages application data channel resources in the DCMF or MRF via the bootstrap data channel and the IMS AS. It downloads data channel applications from the data channel application repository. It interacts with the Network Exposure Function (NEF) to expose data channel capabilities. It interacts with the DC AS to control DC resources and forward traffic.

[0051] DCAR (Data Channel Application Repository) stores verified data channel applications and provides them to DCSF upon request.

[0052] The MRF controls media stream resources. It interprets information from the AS and S-CSCF, controls resource control and allocation, and generates CDRs.

[0053] The DCMF and MRF provide media resource management and forwarding of data channel media traffic. Under the control of the IMS AS, the DCMF and MRF manage data channel media resources, including bootstrap and application data channel resources. The DCMF and MRF terminate the bootstrap data channel from the UE and forward HTTP (HyperText Transfer Protocol) traffic between the UE and the DCSF. In peer-to-peer (P2P) scenarios, the DCMF and MRF anchor the application data channel and, if necessary, forward application data traffic to and from the UE. The DCMF and MRF forward traffic on the A2P / P2A application data channel between the UE and the DCAS.

[0054] DC Application Server is a server that provides data channel application-related services.

[0055] NEF is an NF that supports communication between the 5G core network and external entities (e.g., DC AS).

[0056] Remote IMS can refer to the IMS to which the other terminal is connected.

[0057]

[0058] The present invention proposes a method for finding an IMS AS to provide data channel services, and a method for a DCSF to subscribe to an IMS AS for notification of IMS events for data channel service provision. In describing embodiments of the present invention, the terms "user," "subscriber," and "terminal" may be used interchangeably.

[0059]

[0060] FIG. 3 is a diagram illustrating a method and procedure for managing IMS AS information in a wireless communication system according to an embodiment of the present disclosure. A Network Repository Function (NRF) according to an embodiment of the present invention can receive and manage IMS AS-related information and provide IMS AS-related information to other NFs through the procedure illustrated in FIG. 3.

[0061] An IMS AS according to an embodiment of the present invention can provide IMS session-related event subscription functions and media control functions. Table 1 shows examples of NF services provided by the IMS AS.

[0062] Service NameService OperationsOperation SemanticsExample Consumer(s)Nimsas_SessionEventControlSubscribeSubscribe / NotifyDCSFNotifySubscribe / NotifyDCSFNimsas_MediaControlMediaInstructionRequest / ResponseDCSF

[0063] Regarding the IMS Session Event Control service, Table 2 shows examples of events that can be subscribed to in an IMS AS. An NF can subscribe to the event notifications shown in Table 2 using the Session Event Control service shown in Table 1. Table 2 shows examples of events that can be subscribed to in an IMS AS.

[0064] EventIDParametersSessionEstablishmentRequestEventCalling ID, Called ID, Session case, Media info listSessionEstablishmentProgressEventMedia info listSessionEstablishmentAlertingEventMedia info listSessionEstablishmentSuccessEventMedia info listSessionEstablishmentFailureEventMediaChangeRequestEvent.Event initiator, Media info listMediaChangeSuccessEventMedia info listMediaChangeFailureEventMedia info listSessionTerminationEventSession case

[0065] Referring to FIG. 3, at step 320, the IMS AS (300) may transmit an NF registration message to the NRF (302). The IMS AS (300) may transmit the NF registration message after performing terminal registration. The NF registration request message may be for the IMS AS (300) to register with the NRF (302) and for other NFs to find the IMS AS from the NRF (302). The NF registration request message may include information related to the IMS AS. For example, at least one of an IMS AS name, an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., an IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a user's Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.) may be included. In step 322, the NRF (302) may register the IMS AS (300) and store the received IMS AS-related information. The stored IMS AS information may be used for NF discovery in a subsequent procedure.

[0066] At step 324, the DC AS (310) may transmit an AF request message to the NEF (308). The AF request message may be a message that the DC AS (310) transmits to the IMS AS (300) to subscribe to an event as shown in Table 2. The AF request message may include at least one of an indicator representing a service (e.g., IMS Communication Service Identifier, ICSI), an event ID to subscribe to, information about a user making and / or receiving a call (e.g., a user's external ID, a user's Public User Identities, a user's Private User Identities, an IMPU, an IMPI, etc.), and group information (e.g., an external group ID, etc.).

[0067] The event ID to subscribe to may represent an event as shown in Table 2. Additionally, the AF request message may include one or more event IDs.

[0068] The user's external ID is not the ID used within the IMS or mobile operator network, but rather from outside, for example, 3 rd It may be an identifier of a user managed by a party service provider.

[0069] An external group ID may be an identifier representing a group containing one or more users. The users identified by the group ID may be users who use / subscribe to the same service. The same service may be a service identified by a service identifier included in the AF request message in step 324.

[0070] User information included in an AF request message may include one or more user identifiers.

[0071] The group information included in the AF request message may include one or more external group identifiers.

[0072] The service provided by the IMS AS or the indicator indicating the service provided by the IMS AS may be an NF service supported by the IMS AS shown in Table 1. Alternatively, the service provided by the IMS AS or the indicator indicating the service provided by the IMS AS may be an IMS Communication Service (ICS Identifier (ICSI)) provided by the IMS AS. Table 3 shows examples of ICSI values.

[0073] URN-valueBrief overview of the functionality associated with this NSS.urn:urn-7:3gpp-service.ims.icsi.mmtelThis URN indicates that the device supports the IMS Multimedia Telephony Communication Service framework, and specifically indicates that the terminal has the capabilities of multimedia telephonyurn:urn-7:3gpp-service.ims.icsi.iptvExtract from TS 183 063 clause 5.6.1: " This URN indicates that the device supports the IMS IPTV Service"urn:urn-7:3gpp-service.ims.icsi.raExtract from TS 185 010 (draft only) clause A.3: " This URN indicates that the device supports the IMS Remote Access Service"urn:3gpp-service.ims.icsi.omapushThis ICSI value is associated with OMA Push services. The OMA Push 2.2 enabler release, which is in Candidate status in the OMA, includes support for SIP Push. SIP Push extends the OMA Push enabler, which is widely deployed and fundamental to many mobile data services, with the ability to operate over SIP-based networks such as 3GPP IMS.The OMA Push ICSI enables SIP transactions that are related to the OMA Push service to be identified, so that messages can be properly handled by the SIP / IP Core Network functions and OMA Push service entities. Support for SIP Push will be fundamental to the evolution of mobile data services in an LTE environment, as OMA Push service entities can provide seamless evolution for OMA service enablers from dependence upon the SMS-based WAP Push transport, transparently delivering the same service-specific data over SIP Push.urn:urn-7:3gpp-service.ims.icsi.oma.cpm.msgOMA CPM Pager Mode CPM Message : Uniquely identifies in a SIP MESSAGE a Pager Mode CPM Standalone Message.urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsgOMA CPM Large Mode CPM Message: Uniquely identifies in SIP INVITE a request for Large Message Mode CPM Standalone Message.urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransferOMA CPM File Transfer: Uniquely identifies in SIP INVITE a request for CPM File Transferurn:urn-7:3gpp-service.ims.icsi.oma.cpm.sessionOMA CPM Chat: Uniquely identifies in SIP INVITE a request for CPM chat.urn:urn-7:3gpp-service.ims.icsi.oma.cpm.deferredOMA CPM Deferred Messageurn:urn-7:3gpp-service.ims.icsi.oma.cpm.systemmsgOMA CPM System Message: Uniquely identifies in SIP INVITE a request for a CPM System message.urn:urn-7:3gpp-service.ims.icsi.oma.cab_1.0Used to identify and route message notifications specific for OMA CAB and OMA S-CAB, such as notifications to a user that he / she was added as a new contact by another user.3gpp-service.ims.icsi.oma.cab_1.1Used to identify and route contact subscription invitation requests, using a SIP MESSAGE between two network entities (e.g. cross-domain OMA CAB 1.1 Servers) as defined in OMA CAB 1.1.+g.oma.sip-imIM feature tag used in the Contact header of the SIP REGISTER request to indicate support for OMA SIMPLE IM, and in the Accept-Contact header of:· SIP INVITE for SIMPLE IM chat sessions, file transfer, Large Message Mode and deferred delivery of messages, and of· SIP MESSAGE containing a SIMPLE IM Pager Mode Message.+g.oma.sip-im.system-messageIM feature tag used in the Contact header of the SIP REGISTER request to indicate that a IM client supports System Message, and in the SIP MESSAGE requests to distinguish system messages from normal user message.+g.oma.sip-im.large-messageIM feature tag used in the Contact header of the SIP REGISTER request to indicate that a IM client supports Large Message session, and in SIP INVITE to determine that the request is a Large IM Message.urn:urn-7:3gpp-service.ims.icsi.mcpttThis URN indicates that the device has the capabilities to support the mission critical push to talk (MCPTT) service.urn:urn-7:3gpp-service.ims.icsi.mcdataThis URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) service.urn:urn-7:3gpp-service.ims.icsi.mcdata.sdsThis URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service.urn:urn-7:3gpp-service.ims.icsi.mcdata.fdThis URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) File Distribution (FD) IMS communication service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) File Distribution (FD) IMS communication service.urn:urn-7:3gpp-service.ims.icsi.mcvideoThis URN indicates that the device has the capabilities to support the mission critical video (MCVideo) service.

[0074] In step 326, the NEF (308) can authenticate the AF request message. The NEF (308) can verify whether the NF or AF can subscribe to the event requested by the DC AS (310). The NEF (308) can verify whether the terminal corresponding to the user ID included in the AF request message is a terminal that can use the requested service, i.e., a terminal that is subscribed to the corresponding service. The NEF (308) can verify whether the user group corresponding to the group ID included in the AF request message or the terminal corresponding to the group ID is a group or terminal that can use the requested service, i.e., a group or terminal that is subscribed to the corresponding service. The NEF (308) can verify whether the requested service is a service related to / corresponding to a data channel. If terminal subscription information is required for the above verification / authentication procedure, the NEF (308) can also obtain terminal subscription information from the UDM / HSS (304) (steps 328 to 330). In step 328, the NEF (308) may transmit a terminal subscription information request message to the UDM / HSS (304). The terminal subscription information request message may include a terminal ID. The terminal ID may be determined based on user information received from the DC AS (300) in step 324. For example, the NEF (308) may include the terminal ID received in step 324 in the message of step 328. Alternatively, for example, the NEF (308) may change the terminal ID (e.g., external ID, etc.) received in step 324 to a terminal ID used in an IMS or mobile communication operator network (e.g., Public User Identity, Private User Identity, etc.) and include the changed terminal ID in the message of step 328.Alternatively, for example, NEF (308) may change the group ID received in step 324 to a group ID or terminal ID (e.g., Public User Identity, Private User Identity, etc.) used in the IMS or mobile communication operator network, and include the changed group ID or terminal ID in the message in step 328.

[0075] At step 330, the UDM (304) can reply to the NEF (308) with a list of services to which the user is subscribed, referred to by terminal ID or group ID.

[0076] NEF (308) can determine the DCSF (306) to which the AF request message will be forwarded. DCSF information may be set in NEF (308). For example, DCSF information supporting service-specific services may be set. Alternatively, DCSF information supporting user-specific users may be set.

[0077] If authentication for the AF request is successful, in step 332, the NEF (308) can transmit an AF request message to the selected DCSF (306) based on the configuration information.

[0078] Depending on the network deployment option, the DC AS (300) may transmit an AF request message to the DSCF (306) via the NEF (308) according to the procedure illustrated in steps 324 to 332. Alternatively, the DC AS (300) may transmit the AF request message directly to the DCSF (306) without going through the NEF (308). In the case of a direct request, the NEF operation described in the embodiment of the present invention may be performed in the DCSF (306).

[0079] In step 334, the DCSF (306) may transmit an NF discovery request message to the NRF (302) to find an IMS AS to be subscribed to an event in order to process an event subscription request received from the DC AS (300). The NF discovery request message may include information related to the IMS AS to be discovered. For example, the NF discovery request message may include at least one of an IMS AS name, an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., an IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a user's Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.).

[0080] NRF (302) can determine an IMS AS that satisfies the conditions of the IMS AS that the DCSF (306) requested to discover in step 334 wants to discover based on the IMS AS information stored in step 322.

[0081] At step 336, the NRF (302) may reply an NF discovery response message to the DCSF (306). The NF discovery response message may include IMS AS information determined by the NRF (302). The IMS AS information may include at least one of an IMS AS name discovered by the NRF (302), an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., an IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a user's Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.).

[0082] In step 338, the DCSF (306) may transmit an event subscription message to the IMS AS (300) received in step 336. The event subscription message may include at least one of service-related information for which an event subscription is desired, determined based on the AF request message, such as an event ID, a calling user ID, a called user ID, a session case, and a media information list.

[0083] The event subscription message of step 338 may not include an event ID. Alternatively, the event subscription message of step 338 may indicate a subscription to all IMS events (e.g., data channel-related IMS events) associated with a user (e.g., a user identified by a calling user ID, a called user ID, etc.). For example, the IMS AS (300) may determine that the subscription is to all IMS events if the event subscription message does not include an event ID. Alternatively, the event subscription message may include information indicating a subscription to all IMS events (e.g., an indicator indicating a subscription to all IMS events, an event ID indicating a subscription to all IMS events, etc.). All IMS events may include at least one or all of the events that can be subscribed to by the IMS AS shown in Table 2.

[0084] IMS AS (300) can store the received event subscription and, when the requested event occurs, send a notification message to DCSF (step 512 of FIG. 5).

[0085] FIG. 4 is a diagram illustrating a method and procedure for managing IMS AS information in a wireless communication system according to an embodiment of the present disclosure. An HSS (or UDM) according to an embodiment of the present invention can manage IMS AS-related information through the procedure illustrated in FIG. 4 and provide IMS AS-related information to other NFs.

[0086] In step 420, the HSS / UDM (304) can store IMS AS related information. The mobile communication service provider can set IMS AS related information in the HSS / UDM (304). The IMS AS related information may include at least one of an IMS AS name, an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered in the IMS AS (e.g., user Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered in the IMS AS (e.g., group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.).

[0087] Steps 422 to 430 may correspond to steps 324 to 332 of FIG. 3.

[0088] In step 432, the DCSF (306) may transmit a request message to the HSS / UDM (304) to discover the IMS AS that is the target of the event subscription request. The request message may include IMS AS related information. The IMS AS related information may include at least one of an IMS AS name, an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., an IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a user's Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.).

[0089] HSS / UDM (304) can determine an IMS AS that satisfies the conditions of the IMS AS that the DCSF requested to discover in step 432 based on the IMS AS information stored in step 420.

[0090] At step 434, the HSS / UDM (304) may reply a response message to the DCSF (306). The response message may include IMS AS information determined by the HSS / UDM (304). The IMS AS information may include at least one of an IMS AS name, an IMS AS address, a service provided by the IMS AS, an indicator indicating a service provided by the IMS AS (e.g., an IMS Communication Service Identifier, ICSI), user information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a user's Public User Identities, Private User Identities, IMPU, IMPI, etc.), group information for which the IMS AS provides a service or is registered with the IMS AS (e.g., a group ID, etc.), and capabilities of the IMS AS (e.g., whether Data Channel support is available, etc.).

[0091] According to another embodiment, the NEF (308) may include IMS AS related information in the request message of step 426 to discover the IMS AS that is the target of the event subscription request along with other information described in the embodiment of the present invention. Accordingly, the HSS / UDM (304) may include the IMS AS related information determined by the HSS / UDM (304) along with other information described in the embodiment of the present invention in the response message of step 428. The NEF (308) may include the IMS AS information received from the HSS / UDM (304) along with other information described in the embodiment of the present invention in the message sent to the DCSF (306) in step 430. The DCSF (306) may transmit the event subscription message of step 436 to the IMS AS (300) received from the NEF (308) based on the information received from the NEF (308). In this case, steps 432 to 434 may be omitted.

[0092] Step 436 may correspond to step 338 of Fig. 3.

[0093]

[0094] FIG. 5 is a diagram illustrating an IMS data channel setup procedure according to an embodiment of the present invention. Referring to FIG. 5, a method for establishing a DC (Data Channel) is illustrated in a procedure in which a first terminal establishes a session for communication with a second terminal.

[0095] In step 510, the first terminal (500) can transmit a SIP INVITE message and a Session Description Protocol (SDP). The INVITE message can be received by the IMS AS (300) via the CSCF (502). The SDP can include a bootstrap offer for establishing a data channel. Based on the received information, the IMS AS (300) can determine that a DC is required for the session established with the received INVIATE, for example, if the SDP includes information for establishing a data channel.

[0096] At step 512, the IMS AS (300) can check whether there is an NF that has subscribed to an IMS event through the procedure illustrated in FIG. 3 or 4. For example, the IMS AS (300) can determine the DCSF (306) that has subscribed to an IMS event related to a call connection request for a received data channel. The DCSF (306) according to an embodiment of the present invention may subscribe to the IMS AS for a Session Establishment Request Event related to a user (e.g., a first terminal or a second terminal) referred to by a user ID or a group ID through the procedure illustrated in FIG. 3 or 4. Alternatively, the DCSF (306) according to an embodiment of the present invention may subscribe to the IMS AS (300) for all IMS events (including a Session Establishment Request Event event) related to a user (e.g., a first terminal or a second terminal) referred to by a user ID or a group ID through the procedure illustrated in FIG. 3 or 4.

[0097] In step 514, the IMS AS (300) may transmit a notification message to the DCSF (306) that is subscribed to the IMS event. The notification message may be a message notifying that a session establishment event related to the first terminal or the second terminal has occurred. The notification message may include at least one of a session ID, a sending user ID, a receiving user ID, a session case (e.g., receiving, sending, etc.), an event initiator (e.g., a served IMS subscriber, a remote IMS subscriber, etc.), and media information (e.g., a data channel, audio, video, etc.). The IMS AS (300) may suspend the session establishment procedure until it receives the notification response message of step 522.

[0098] At step 516, the DCSF (306) may transmit media instruction information for bootstrap setup of the DC to the IMS AS (300).

[0099] At step 518, the IMS AS (300) can perform media resource allocation by communicating with the DCMF (or enMRF) (504) based on the received media indication information.

[0100] After completing the media resource allocation, the IMS AS (300) can transmit a response message to the DCSF (306) at step 520 indicating that the media control request received at step 516 has been completed.

[0101] Since the media resource allocation is complete, the DCSF (306) can send a notification response message to the IMS AS (300) in step 522. The notification response message in step 522 may be a response to the notification message received in step 514.

[0102] The IMS AS (300) that receives the notification response message can resume the session establishment procedure. In steps 524 to 526, the IMS AS (300) can transmit an INVITE message to the second terminal (506) via the CSCF (502).

[0103] The second terminal (506), which has received the INVITE message sent by the first terminal (500), may decide to establish a call and transmit a 200 OK message at step 528. The 200 OK message may be transmitted to the IMS AS (300) at step 530 via the CSCF (502).

[0104] The IMS AS (300) that receives the 200 OK can check whether there is an NF subscribed to the IMS event related to the session. For example, the IMS AS (300) can determine the DCSF (306) that is subscribed to the IMS event related to the call connection for the received data channel. The DCSF (306) according to an embodiment of the present invention may subscribe to the IMS AS for a Session Establishment Success Event related to a user (e.g., a first terminal or a second terminal) referred to by a user ID or a group ID through the procedure illustrated in FIG. 3 or 4. Alternatively, the DCSF (306) according to an embodiment of the present invention may subscribe to the IMS AS (300) for all IMS events (including a Session Establishment Success Event event) related to a user (e.g., a first terminal or a second terminal) referred to by a user ID or a group ID through the procedure illustrated in FIG. 3 or 4.

[0105] In step 532, the IMS AS (300) may send a notification message to the DCSF (306) that subscribes to the IMS event. The notification message may include at least one of a session ID and media information. The session ID may be the same value as the session ID included in the session establishment event in step 514. The IMS AS (300) may suspend the session establishment procedure until it receives the notification response message in step 534.

[0106] DCSF (306), which has received a notification message from IMS AS (300), can determine that the session indicated by the session ID received in step 514 has been successfully established. In step 534, DCSF (306) can transmit a response message to the notification message to IMS AS (300).

[0107] At step 536, the IMS AS (300) can transmit a 200 OK message to the first terminal (500) via the CSCF (502). Upon receiving the 200 OK, the first terminal (500) can establish a session connection with the second terminal (506) and transmit and receive data.

[0108]

[0109] There may be various embodiments of how the DCSF (306) according to an embodiment of the present invention subscribes to IMS events from the IMS AS (300). The DCSF (306) may subscribe to events related to IMS sessions associated with Data Channel media from the IMS AS (300) through the procedure illustrated in FIG. 3 or FIG. 4. The event subscription may be a subscription to events related to specific media (e.g., Data Channel) within the IMS session, rather than the IMS session itself.

[0110] For example, DCSF (306) may subscribe to one or more IMS events of interest to DCSF in step 338 of FIG. 3 or step 436 of FIG. 4. To subscribe to one or more IMS events, the event subscription message in step 338 of FIG. 3 or step 436 of FIG. 4 may include one or more event IDs.

[0111] Alternatively, the event subscription message may include at most one event ID. In this case, to subscribe to one or more IMS events, the DCSF (306) may transmit to the IMS AS (300) as many event subscription messages as the number of event IDs. That is, the message in step 338 of FIG. 3 or step 436 of FIG. 4 may be transmitted to the IMS AS (300) as many event IDs as the number of events to subscribe to.

[0112] Alternatively, the event subscription message may not include an event ID or may include information indicating a subscription to all IMS events. To subscribe to all IMS events, the event subscription message in step 338 of FIG. 3 or step 436 of FIG. 4 may not include an event ID or may include information indicating a subscription to all IMS events. The DSCF (306) may subscribe to all IMS events by sending a single event subscription message.

[0113] DCSF may subscribe to at least one of the IMS events shown in Table 2 before the IMS session establishment procedure shown in FIG. 5 occurs. For example, DCSF (306) may subscribe to Session Establishment Request Event, Session Establishment Success Event, and Session Establishment Failure Event before the procedure shown in FIG. 5 occurs. Accordingly, based on the events subscribed to before FIG. 5, IMS AS (300) may transmit a notification message of step 514 of FIG. 5 and / or step 532 of FIG. 5 to DSCF.

[0114]

[0115] According to another embodiment of the present invention, the DSCF and the IMS AS can sequentially subscribe to IMS events.

[0116] FIG. 6 is a diagram illustrating an IMS event subscription chain procedure according to an embodiment of the present invention.

[0117] Referring to FIG. 6, at step 610, the DCSF (306) may receive an AF request message from the AF. Step 610 may correspond to steps 324 to 332 of FIG. 3 or steps 422 to 430 of FIG. 4.

[0118] In step 612, the DCSF (306) may transmit an event subscription message to the IMS AS (300). Step 612 may correspond to step 338 of FIG. 3 or step 436 of FIG. 4. In addition, the event subscription message of step 612 may include an Event ID indicating a Session Establishment Request Event. That is, the event subscription message of step 612 may only include events for session establishment requests. In addition, the event subscription message of step 612 may include an indicator indicating that the event subscription is a subscription request that continues until an (explicit) cancellation request is made. The IMS AS (300) may store and manage event subscriptions for received session establishment requests.

[0119] A DC establishment related procedure may be triggered at step 614. Step 612 may correspond to steps 510 to 512 of FIG. 5.

[0120] In step 616, the IMS AS (300) may transmit a notification message to the DCSF (306) notifying that a session establishment request event has occurred. The notification message in step 616 may be a notification message transmitted based on the event subscription received in step 612. Step 616 may correspond to step 514 of FIG. 5 .

[0121] In step 618, the IMS AS (300) may perform a resource allocation procedure. Step 618 may correspond to steps 516 to 520 of FIG. 5.

[0122] In step 620, the DCSF (306) may transmit an event notification response message to the IMS AS (300). Step 620 may correspond to step 522 of FIG. 5. In addition, the notification response message of step 620 may include information about the next event that the DCSF wishes to subscribe to. For example, the DCSF (306) may wish to subscribe to an event related to the session for which the establishment request notification was received in step 616. Accordingly, the DCSF (306) may include (piggyback) an event subscription request in the notification response message of step 620. The event subscription request may include information related to the session to be subscribed to (e.g., a session ID), event information (e.g., an event ID indicating at least one of the events Session Establishment Progress, Session Establishment Alert, Session Establishment Success, and Session Establishment Failure shown in Table 2, etc.). Additionally, the event subscription request may include an indicator indicating that the event subscription is a one-time subscription request that can be automatically canceled when a single notification occurs. For example, if a Session Establishment Success event occurs and the IMS AS (300) sends a notification message to the DCSF (306), the IMS AS (300) may send the notification message and cancel the Session Establishment Success event subscription. This may be because if the session establishment is successful, the establishment success event will not occur again for that session. Alternatively, the subscription request may indicate that if a notification occurs for at least one of the events for which the subscription was requested, the subscription will be canceled for the remaining events as well.That is, for example, when a successful session establishment event, referred to as a session ID, occurs and a notification message is sent to the DCSF, subscriptions for both the successful session establishment event and the failed session establishment event may be canceled. This may be because, if the session establishment is successful, no failed session establishment event will occur for that session. The IMS AS (300) may store and manage the received session-related event subscriptions.

[0123] In step 622, the IMS AS (300) may continue the session establishment procedure. Step 622 may correspond to steps 524 to 530.

[0124] In step 624, the IMS AS (300) may transmit a notification message to the DCSF (306) notifying that a session establishment success event has occurred. The notification message in step 624 may be a notification message transmitted according to the event subscription received in step 620. Step 624 may correspond to step 532 of FIG. 5. In addition, if the session establishment success event subscription is a one-time event, the IMS AS (300) may cancel the session establishment success event subscription. In addition, if there is a session establishment failure event subscription for the corresponding session, the IMS AS (300) may also cancel the session establishment failure event subscription.

[0125] In step 626, DCSF (306) may transmit an event notification response message to IMS AS (300). Step 626 may correspond to step 534 of FIG. 5. In addition, the notification response message of step 626 may include information about the next event that DCSF (306) wishes to subscribe to. For example, DCSF (306) may wish to subscribe to an event related to a session for which establishment success notification was received in step 624. Accordingly, DCSF (306) may include (piggyback) an event subscription request in the notification response message of step 626. The event subscription request may include information related to the session to be subscribed to (e.g., session ID), event information (e.g., an event ID indicating at least one of the events Media Change Request and Session Termination shown in Table 2, etc.). Additionally, an event subscription request may include information indicating whether the event subscription is a persistent request that persists until an explicit termination request is made, a request that can be implicitly terminated under certain conditions, or a one-time subscription request that can be automatically terminated upon a single notification. For example, a Media Change Request event may be an explicit termination request or a persistent event subscription that persists until a certain condition is met. This may be because changes related to a specific media (e.g., a data channel) may be requested / occurred multiple times during an IMS session. Furthermore, this may be because when an IMS session is terminated or a specific media (e.g., a data channel) is no longer used in an IMS session, i.e., when a specific media is terminated, no further media-related changes occur, and thus event subscriptions for it are no longer necessary. In other words, when the conditions of an IMS session termination or the termination of a data channel during an IMS session are met, the IMS AS may terminate the subscription to the Media Change Request event.The difference between managing subscriptions to Media Change Request events and Session Establishment Request events performed on IMS AS is that Media Change Request events are event subscriptions that are no longer valid when the corresponding session ends, whereas Session Establishment Request events are not associated with a specific session but rather are related to a new session request, so the event subscription remains valid even when the session ends or there are no sessions for the terminal.

[0126] Additionally, for example, when a Session Termination event occurs and the IMS AS (300) sends a notification message to the DCSF (306), the IMS AS (300) may send the notification message and cancel the subscription to the Session Termination event. This may be because when a session is terminated or a specific medium (e.g., a data channel) is terminated during a session, the Session Termination event will not occur again for that session.

[0127] IMS AS (300) can store and manage received session-related event subscriptions.

[0128] At step 628, a media (e.g., data channel) change request may occur during an IMS session. This may occur when the first or second terminal sends a reINVITE message containing a new SDP. When the IMS AS (300) receives the reINVITE message sent by the first terminal, the IMS AS (300) can confirm that a media change request has occurred.

[0129] In step 630, the IMS AS (300) may transmit a notification message to the DCSF (306) notifying that a media change request event has occurred. The notification message in step 630 may be a notification message transmitted based on the event subscription received in step 626.

[0130] IMS AS (300) may also perform media change (e.g., data channel) through an instruction from DSCF (306).

[0131] In step 632, DCSF (306) may transmit an event notification response message to IMS AS (300). This may be a response message indicating that the event notification in step 630 has been successfully received. The notification response message in step 632 may include information about the next event that DCSF wishes to subscribe to. For example, DCSF (306) may wish to subscribe to an event related to the media for which a media change request notification was received in step 630. Accordingly, DCSF (306) may include (piggyback) an event subscription request in the notification response message in step 632. The event subscription request may include information related to the session to be subscribed to (e.g., a session ID) and event information (e.g., an event ID indicating at least one of the media-related events Media Change Success and Media Change Failure shown in Table 2). In addition, the event subscription request may include an indicator indicating that the event subscription is a one-time subscription request that may be automatically canceled when a single notification occurs. For example, when a Media Change Success event occurs and the IMS AS sends a notification message to the DCSF, the IMS AS (300) may send the notification message and cancel the subscription to the Media Change Success event. This may be because, if the requested media change is successful, the change success event will not occur again for the corresponding media change request. Alternatively, if a notification occurs for at least one of the subscription-requested events, it may indicate that the subscription will be canceled for the remaining events as well. That is, for example, when a media change success event for a session referred to by a session ID occurs and a notification message is sent to the DCSF, the subscription for not only the media change success event but also the media change failure event may be canceled.This may be because, if a media change is successful, no media change failure event will be generated for the media change request. The IMS AS (300) may store and manage event subscriptions related to the received session (and / or media change).

[0132] At step 634, the IMS AS (300) can continue the media change procedure.

[0133] In step 636, the IMS AS (300) may transmit a notification message to the DCSF (306) notifying that a media change success (or failure) event has occurred. The notification message in step 636 may be a notification message transmitted according to the event subscription received in step 632. If the media change success event subscription is a one-time event, the IMS AS (300) may cancel the media change success event subscription. In addition, if there is a media change failure event subscription for the corresponding session, the IMS AS (300) may also cancel the media change failure event subscription.

[0134] In step 638, DCSF (306) may transmit an event notification response message to IMS AS (300). This may be a response message indicating that the event notification in step 636 has been successfully received.

[0135] At step 640, the IMS AS (300) may be notified that an IMS session or a specific media (e.g., data channel) termination event has occurred during an IMS session.

[0136] In step 642, the IMS AS (300) may transmit a notification message indicating that a DSCF session termination event has occurred. The notification message in step 642 may be a notification message transmitted according to the event subscription received in step 626.

[0137] In step 644, the DCSF (306) may transmit an event notification response message to the IMS AS (300). This may be a response message indicating that the event notification in step 642 has been successfully received. The DCSF (306) may be aware that a specific medium (e.g., a data channel) has been terminated or that an IMS session providing a specific medium has been terminated. The IMS AS (300) may cancel all event subscriptions associated with the terminated session. For example, the subscription to at least one of the events shown in Table 2, excluding the Session Establishment Request Event, may be canceled.

[0138] Figure 6 illustrates a procedure for sequentially subscribing to and canceling events related to an IMS session, according to an embodiment of the present invention. Figure 6 also illustrates examples of event subscriptions that should persist regardless of the session, event subscriptions that should persist until a specific condition related to the session is met, and one-time subscriptions that should be canceled upon the occurrence of a single event, according to an embodiment of the present invention.

[0139] Additionally, although FIG. 6 illustrates a method in which DCSF (306) piggybacks a subsequent event subscription request on a response message to an event notification (e.g., steps 620, 626, and 632) according to an embodiment of the present invention, the event subscription request may be transmitted as a separate message from the response message after receiving the response message.

[0140] In addition, although FIG. 6 describes implicit cancellation of event subscription, DCSF (306) may also explicitly include an event cancellation request in the event response message. For example, DCSF may include cancellation of subscription for at least one of Session Establishment Success, Session Establishment Failure, Session Establishment Progress, and Session Establishment Alerting events in the response message of step 626. DSCF may include cancellation of subscription for at least one of Media Change Success and Media Change Failure events in the response message of step 638. DSCF may include cancellation of subscription for at least one of the events shown in Table 2 except for the Session Establishment Request event in the response message of step 638.

[0141] According to another embodiment of the present invention, the DSCF (306) may be subscribed to the IMS AS (300) for all IMS events. In this case, the message in step 612 of FIG. 6 may indicate subscription to all IMS events. Accordingly, when an IMS event occurs, the IMS AS (300) may transmit event notification messages in steps 616, 624, 630, 636, and 642 to the DCSF (306). In addition, since the message in step 612 includes subscription to all IMS events, the messages in steps 620, 626, and 632 may not include additional event subscription request messages.

[0142] The present invention has described a method for receiving an event notification message by sending an event subscription request to an IMS AS (300) based on a request received from a DC AS by a DCSF (306), according to one embodiment. In addition, according to one embodiment, the DC AS may also receive an event notification message.

[0143] For example, in step 338 of FIG. 3 or step 436 of FIG. 4, the DCSF (306) may include information indicating that the consumer for the event subscription request is a DC AS and / or a DC AS address (e.g., an IP address of the DC AS, etc.). Accordingly, the IMS AS (300) may transmit an event notification message to the DC AS when an event for which a subscription request has been made occurs. The DC AS may receive the event notification message directly from the IMS AS (300).

[0144] Alternatively, for example, the DCSF (306) may transmit event notification information received from the IMS AS (300) to the DC AS. Accordingly, when the DCSF (306) receives an event notification according to the procedure illustrated in FIG. 5 or FIG. 6, the DCSF (306) may transmit the corresponding event information to the DC AS. The DCSF (306) may transmit the event information directly to the DC AS or to the DC AS via the NEF. The DC AS may receive an event notification message generated from the IMS AS (300) directly or indirectly via the DCSF and / or the NEF.

[0145]

[0146] FIG. 7 is a diagram illustrating the structure of a terminal according to one embodiment of the present invention.

[0147] Referring to FIG. 7, the terminal may include a transceiver (710), a control unit (720), and a storage unit (730). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0148] The transceiver (710) can transmit and receive signals with other network entities. The transceiver (710) can receive system information from a base station, for example, and can receive a synchronization signal or a reference signal.

[0149] The control unit (720) can control the overall operation of the terminal according to the embodiment proposed in the present invention.

[0150] The storage unit (730) can store at least one of the information transmitted and received through the transmission and reception unit (710) and the information generated through the control unit (720).

[0151] FIG. 8 is a diagram illustrating the structure of a network entity according to one embodiment of the present invention.

[0152] Referring to FIG. 8, the terminal may include a transceiver (810), a control unit (820), and a storage unit (830). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0153] The transceiver (810) can transmit and receive signals with other network entities. The transceiver (810) can receive system information from a base station, for example, and can receive a synchronization signal or a reference signal.

[0154] The control unit (820) can control the overall operation of the terminal according to the embodiment proposed in the present invention.

[0155] The storage unit (830) can store at least one of the information transmitted and received through the transmission and reception unit (810) and the information generated through the control unit (820).

[0156] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading and executing the program code stored in the memory device through a processor or a CPU (Central Processing Unit).

[0157] The various components and modules of the entity or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software, and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

[0158] 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.

[0159] 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 embodiments described in the claims or specification of the present disclosure.

[0160] These programs (software modules, software) may be stored in random access memory, non-volatile memory including 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 memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0161] 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 area network (WAN), 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.

[0162] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, 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 plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0163] 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.

Claims

1. A method performed in a first network entity in a wireless communication system, Step for storing information related to IMS (Internet Protocol Multimedia Subsystem) AS (Application Server); and Including a step of receiving a terminal subscription information request message from a second network entity when the AF (Application Function) request message is authenticated, A method characterized in that the AF request message is transmitted from a DC (Data channel) AS to the second network entity.

2. In paragraph 1, A method further comprising the step of transmitting a message including a list of user subscription services including a terminal ID or a group ID to the second network entity.

3. In paragraph 1, A method further comprising the step of transmitting an event subscription message to an IMS AS.

4. In paragraph 1, A method, characterized in that the above IMS AS related information is registered with the first network entity and allocated by the terminal.

5. In a method performed in a second network entity in a wireless communication system, A step of receiving an AF (Application Function) request message from a DC (Data channel) AS (Application Server); a step of authenticating the above AF request message; and If the above AF request message is authenticated, the step of transmitting a terminal subscription information request message to the first network entity is included, A method characterized in that information related to an IMS (Internet Protocol Multimedia Subsystem) AS is stored in a first network entity.

6. In paragraph 5, A method further comprising the step of receiving, from the first network entity, a message including a list of user subscription services including a terminal ID or a group ID, to the second network entity.

7. In paragraph 5, A method, characterized in that an event subscription message is transmitted from the first network entity to the IMS AS.

8. In paragraph 5, A method, characterized in that the above IMS AS related information is registered in the first network enterer and allocated by the terminal.

9. In a first network entity in a wireless communication system, A transceiver capable of transmitting and receiving at least one signal; and Including a control unit coupled with the above transmitter and receiver, The above control unit: Stores information related to IMS (Internet Protocol Multimedia Subsystem) AS (Application Server), and When the AF (Application Function) request message is authenticated, it is configured to receive a terminal subscription information request message from a second network entity, A first network entity, characterized in that the AF request message is transmitted from a DC (Data channel) AS to the second network entity.

10. In paragraph 9, the control unit: A first network entity further configured to transmit a message including a list of user subscription services including a terminal ID or group ID to the second network entity.

11. In paragraph 9, the control unit: A first network entity further configured to transmit an event subscription message to an IMS AS.

12. In paragraph 9, A first network entity, characterized in that the above IMS AS related information is registered with the first network entity and allocated by the terminal.

13. In a second network entity in a wireless communication system, A transceiver capable of transmitting and receiving at least one signal; and Including a control unit coupled with the above transmitter and receiver, The above control unit: Receives an AF (Application Function) request message from the DC (Data channel) AS (Application Server), Authenticate the above AF request message, and If the above AF request message is authenticated, it is configured to transmit a terminal subscription information request message to the first network entity, A second network entity, characterized in that information related to an IMS (Internet Protocol Multimedia Subsystem) AS is stored in the first network entity.

14. In paragraph 13, the control unit: A second network entity configured to receive, from the first network entity, a message including a list of user subscription services including a terminal ID or a group ID, the second network entity.

15. In paragraph 13, An event subscription message is transmitted from the first network entity to the IMS AS, and A second network entity, characterized in that the above IMS AS related information is registered in the first network entity and allocated by the terminal.

Images