KR20220006766A - Method and apparatus for providing interworking between MCPTX network and service server in communication system - Google Patents

Abstract

The present disclosure relates to a communication technique for merging IoT technology with a 5G communication system for supporting a data transmission rate higher than that of a 4G system, and a system therefor. The present disclosure can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security-and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. The present invention provides a method and a device for providing a gateway function for linkage with another service network through a service mash-up function (SMF) and more efficiently linking an MCPTX network and a separate network.

Description

Method and apparatus for providing interworking between MCPTX network and service server in a communication system {Method and apparatus for providing interworking between MCPTX network and service server in communication system}

An embodiment of the present specification is a MCPTX (Mission Critical Push To Talk/Video/Data) related technology.

Specifically, the interaction between PS-LTE (Public Safety - Long Term Evolution) network, IoT solution providing IoT (Internet of Thing) service, and video analysis solution that provides intelligent monitoring service by detecting specific events by analyzing real-time video streams It relates to a method and apparatus for providing an interworking service.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE system after (Post LTE) system.

In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation Technology development is underway.

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

Meanwhile, the PS-LTE network, a public safety service network using MCPTX technology defined in the 3GPP standard as one of the technologies in the wireless communication system, uses the PS-LTE network to provide group communication and message transmission/reception to users belonging to the service network. , recording/recording, location and status information confirmation services can be provided.

However, using the interface and protocol defined in the 3GPP MCPTX standard, the service provided by the Video Surveillance network is provided to the PS-LTE network subscribers through interworking with the Video Surveillance network, or the service provided by the IoT Platform is provided to the PS-LTE network subscribers. There is no concrete way to do it.

That is, in the prior art, the PS-LTE network cannot provide various services provided by other service networks to PS-LTE network subscribers through interworking with other service networks using the interfaces and protocols defined in the 3GPP MCPTX standard.

The invention according to the present disclosure was derived to solve the above problems. According to an embodiment of the present invention, a gateway function for interworking with other service networks is provided through SMF (Service Mash-up Function), and MCPTX It is possible to efficiently link the network with a separate network.

A method of an apparatus for performing a service mash-up function (SMF) for MCPTX-AS (Mission Critical Push To Everything - Application Server) server interworking in a wireless communication system according to an embodiment of the present invention is at least one Receiving at least one event message from any one of the service servers of Generating a Session Initiation Protocol (SIP) related message corresponding to the parameter information and the data information and transmitting the generated SIP related message to the MCPTX service control server to be linked with the service server characterized in that

In addition, the present invention is a device for performing a service integration function (Service Mash-up Function: SMF) for interworking with MCPTX-AS (Mission Critical Push To Everything - Application Server) server in a wireless communication system, which transmits and receives signals with the server Receives at least one event message from any one service server among the transceiver and at least one service server, and checks parameter information and data information of the service server based on the at least one event message, and the service A server, generating a Session Initiation Protocol (SIP) related message corresponding to the parameter information and the data information, and controlling to transmit the generated SIP related message to the MCPTX service control server to be linked with the service server It is characterized in that it includes a control unit.

According to an embodiment of the present invention, a gateway function for interworking with other service networks can be provided through SMF (Service Mash-up Function), and the MCPTX network and a separate network can be interlocked more efficiently.

1 is a diagram illustrating an operation of an entire network for establishing a group communication session using a PS-LTE network.
2 is a diagram illustrating a network structure for performing an interworking service between a PS-LTE network and another service network through SMF according to an embodiment of the present invention.
3 is a flowchart illustrating an operation when an SMF receives an event message from a VMS according to an embodiment of the present invention.
4 is a diagram illustrating the overall operation of the network when the SMF receives an event message from the VMS according to an embodiment of the present invention.
5 is a flowchart illustrating an operation when the SMF receives an event message from the IoT Platform according to an embodiment of the present invention.
6 is a diagram showing the overall operation of the network when the SMF receives an event message from the IoT Platform according to an embodiment of the present invention.
7 is a flowchart illustrating an operation when an SMF receives an event message from a VMS according to another embodiment of the present invention.
8 is a diagram showing the overall operation of the network when the SMF receives an event message from the VMS according to another embodiment of the present invention.
9 is a flowchart illustrating an operation when the SMF receives an event message from the IoT Platform according to another embodiment of the present invention.
10 is a diagram illustrating the overall operation of the network when the SMF receives an event message from the IoT Platform according to another embodiment of the present invention.
11 is a flowchart illustrating an operation when an SMF receives an event message according to an embodiment of the present invention.
12 is a flowchart illustrating that the SMF operates in a cooperate mode when receiving an event message according to an embodiment of the present invention.
13 is a diagram illustrating an overall operation of a network when an SMF receives a message regarding resource change information according to an embodiment of the present invention.
14 is a structural diagram showing the structure of an SMF according to an embodiment of the present invention.
15 is a structural diagram showing the structure of the MCPTX-AS according to an embodiment of the present invention.

Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, a term referring to various identification information and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described later, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards.

Advantages and features of the present disclosure, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the disclosure of the present disclosure to be complete, and common knowledge in the technical field to which the present disclosure belongs It is provided to fully inform the possessor of the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory which may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~ unit' performs certain roles do. However, '-part' is not limited to software or hardware. '~' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, '~' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings.

A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, a term referring to various identification information and the like are exemplified for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description below, in the present invention, terms and names defined in LTE and NR standards, which are the latest standards defined by the 3rd Generation Partnership Project (3GPP) organization among existing communication standards, are used. However, the present invention is not limited by the terms and names, and may be equally applied to systems conforming to other standards. In particular, the present invention can be applied to 3GPP NR (5th generation mobile communication standard).

According to an embodiment of the invention MCPTT (Mission Critical Push To Talk) or MCPTX (Mission Critical Push To Talk / Video / Data) may be the information on the standard defined by the ^{3GPP (3 rd Generation Partnership Project)} . In addition, PS-LTE (Public Safety - Long Term Evolution) network built using MCPTX may be a communication technology necessary for communication between people involved in public safety when performing disaster prevention, preparedness, response, and recovery. have. The main functions of the PS-LTE network may include group communication, message transmission/reception, recording/recording, and a location information-based verification function that enables location information of related devices and persons to be checked in real time.

According to an embodiment of the present invention, a video management system (VMS) monitors real-time video from a plurality of video devices such as CCTV installed for a video management service, analyzes a video stream received from the video device, and provides a video stream After the event information detected as a result of the analysis is created as a message, the message can be transmitted to related parties. For example, the video management system operates the Video Surveillance service, and when a specific event occurs after video analysis, the event details are notified to the relevant parties through a commercial network, etc. have.

According to an embodiment of the present invention, the IoT (Internet of Things) platform analyzes the data for each sensor received from the installed sensors using various sensor information, and when the value of the data satisfies the set condition, the condition is satisfied for the concerned parties. You can send a message indicating that it has been done. For example, an IoT gateway that receives data from sensors collects data, converts it, transmits sensor data to the IoT platform, and analyzes it through real-time monitoring. After notifying you, you can provide a service that can handle the case by the person concerned.

According to an embodiment of the present invention, a Service Mash-up Function (SMF) may be a device that functions as a gateway for interworking with other service networks. The SMF may, for example, perform configuration management, resource management, media processing, notification management, group communication service control, and the like.

Dispatcher Manager for MCPTX service control (MCPTX Client function) Geographical Information Server (GIS) Device or terminal location information and status information management MCPTX-AS (Mission Critical Push To Talk/Video/Data-Application Server) MCPTX service control CSCF (Call Session Control Function) Call Session Control UE (User Equipment) Terminal (MCPTX Client function) Evolved Packet Core (EPC) Core Network device in LTE network eNB (evolved NodeB) Base station device in LTE network VMS (Video Management System) Real-time event monitoring after transmitting the video stream for CCTV real-time video information storage and control and video analytics to the VA Engine (e.g., performing the processing procedure after detecting the event derived from the video stream analysis result) IoT Platform Real-time sensor data monitoring received from sensors in conjunction with IoT Gateway (e.g., event handling procedures are performed when threshold is exceeded)

According to Table 1, descriptions of terms related to components for facilitating description in the present invention are shown. A detailed description of each component will be described later. FIG. 1 is a diagram illustrating an operation of an entire network for establishing a group communication session using a PS-LTE network.

According to an embodiment of the present invention, the first terminal (User Equipment: UE) 100 is a terminal that wants to request session establishment for group communication, and the second terminal 110 is a terminal that receives session establishment in group communication. have. The call session control function (CSCF) 120 may control a group communication session, and may play a role in controlling the session by receiving a Session Initiation Protocol (SIP) message delivered from the first terminal. The CSCF 120 transmits a SIP message on the network to the MCPTX service control server (Mission Critical Push To Audio/Video/Data-Application Server: MCPTX-AS) and MCPTX service control to provide a service as requested by the first terminal 100 It is transmitted to the application manager, for example, the Dispatcher 140, so that the session is completed.

Referring to FIG. 1 to describe the above process in detail, the first UE 100 transmits the received SIP related message to the MCPTX-AS 130 to request session establishment for group communication in step S101. can For example, the SIP-related message may be a SIP INVITE message including at least one of an MCPTT ID and a Group ID to create a group session. Alternatively, the first UE 100 may transmit a SIP-related message to the CSCF 120 to request session establishment for group communication in step S101. The CSCF 120 may transmit the received SIP-related message to the MCPTX-AS 130 when receiving a SIP-related message for a session establishment request for group communication in step S103 .

When the MCPTX-AS 130 receives a SIP-related message for a session establishment request for group communication, in step S105, the session establishment from the first terminal 100 to the second terminal 110, which is a member of the group, is A SIP-related message for indicating that the request has been made may be transmitted to the second terminal 110 . For example, the SIP related message for indicating to the second terminal 110 that the first terminal has requested session establishment may be a SIP INVITE message. Alternatively, when the MCPTX-AS 130 receives a SIP-related message for a session establishment request for group communication, in step S105, a session is established from the first terminal 100 to the second terminal 110, which is a member of the group. A SIP-related message for indicating that this has been requested may be transmitted to the CSCF 120 . The CSCF 120 may transmit the SIP-related message received from the MCPTX-AS 130 to the second terminal 110 in step S107 .

When the second terminal 110 receives the SIP-related message for the session establishment request, in step S109, the SIP-related message is sent to the MCPTX-AS 130 to inform the MCPTX-AS 130 that it has been accepted by the end user agent. can be transmitted For example, the SIP related message may be a SIP 200 OK message to inform the MCPTX-AS 130 that it has been accepted by the end user agent. Alternatively, when the second terminal 110 receives the SIP-related message for the session establishment request, in step S109, the SIP-related message is transmitted to the CSCF 120 to inform the MCPTX-AS 130 that it has been accepted by the end user agent. can The CSCF 120 may transmit to the MCPTX-AS 130 a SIP-related message indicating that it has been accepted by the end user agent received from the second terminal 110 in step S111 .

The MCPTX-AS 130 may transmit a SIP-related message for informing the first terminal 100 that the second terminal 110 has accepted the session establishment request to the first terminal 100 in step S113 . For example, the SIP related message for notifying the first terminal 100 that the second terminal 110 has accepted the session establishment request may be a SIP 200 OK message. Alternatively, the MCPTX-AS 130 may transmit a SIP-related message to the CSCF 120 to inform the first terminal 100 that the second terminal 110 has accepted the session establishment request in step S113. The CSCF 120 may transmit to the first terminal 100 a SIP-related message for notifying the received terminal 1 that the second terminal 110 has accepted the session establishment request in step S 115 .

When the first terminal 100 receives a SIP-related message for notifying that the second terminal 110 has accepted the session establishment request, in step S117, a SIP message related to call confirmation is transmitted to the MCPTX-AS 130 can For example, the SIP message related to call acknowledgment may be a SIP ACK message. Alternatively, when the first terminal 100 receives a SIP-related message for notifying that the second terminal 110 has accepted the session establishment request, in step S117, a SIP message related to call confirmation may be transmitted to the CSCF 120. have. When receiving the SIP message related to the call confirmation, the CSCF 120 may transmit a SIP message related to the call confirmation to the MCPTX-AS 130 in step S119.

The MCPTX-AS 130 may transmit to the second terminal 110 a SIP message related to a call confirmation for transmission to the second terminal 110 in step S121 . For example, the SIP message related to the call confirmation to be transmitted to the second terminal 110 may be a SIP ACK message. Alternatively, the MCPTX-AS 130 may transmit a SIP message related to call confirmation for transmission to the second terminal 110 to the CSCF 120 in step S121 . When the CSCF 120 receives the SIP message related to the call confirmation to be transmitted to the second terminal 110 , the CSCF 120 may transmit the received message to the second terminal 110 in step S123 .

The MCPTX-AS 130 may perform the MCPTX Client role in step S125 and transmit a SIP related message for a session establishment request to the Dispatcher 140 that is an MCPTX service control manager to the Dispatcher 140 . For example, the SIP related message for requesting session establishment to the dispatcher 140 may be a SIP INVITE message. Alternatively, the MCPTX-AS 130 may perform the MCPTX Client role in step S125 and transmit a SIP-related message for a session establishment request to the Dispatcher 140 that is an MCPTX service control manager to the CSCF 120 . When the CSCF 120 receives the SIP-related message for the session establishment request from the Dispatcher 140 , in step S127 , the CSCF 120 may transmit the SIP-related message to the Dispatcher 140 .

Dispatcher 140 receives the SIP-related message for the session establishment request, and when accepting the session establishment request, in step S129, a SIP-related message for notifying the MCPTX-AS 130 that the session establishment request has been accepted. - Can be transmitted to the AS (130). For example, the SIP-related message for informing the MCPTX-AS 130 that the session establishment request has been accepted may be a SIP 200 OK message. Alternatively, the Dispatcher 140 receives the SIP-related message for the session establishment request, and when accepting the session establishment request, in step S129, a SIP-related message for notifying the MCPTX-AS 130 that the session establishment request has been accepted. It can be transmitted to the CSCF (120). When the CSCF 120 receives a SIP-related message for notifying the MCPTX-AS 130 that the session establishment request has been accepted, in step S131 , the SIP-related message may be transmitted to the MCPTX-AS 130 .

The MCPTX-AS 130 may transmit to the Dispatcher 140 a SIP message related to call confirmation for transmission to the Dispatcher 140 in step S133. For example, the SIP message related to call confirmation to be transmitted to the dispatcher 140 may be a SIP ACK message. Alternatively, the MCPTX-AS 130 may transmit a SIP message related to a call confirmation for transmission to the Dispatcher 140 to the CSCF 120 in step S133. When the CSCF 120 receives the SIP message related to the call confirmation for transmission to the dispatcher 140 , the CSCF 120 may transmit the received message to the dispatcher 140 in step S135 .

Through the above process, the PATH Established between the first terminal 100 and the MCPTX-AS 130, the second terminal 110 and the MCPTX-AS 130, the Dispatcher 140 and the MCPTX-AS 130 is established, and MCPTX -AS 130 may receive Audio/Video/Data information transmitted by a terminal having the right to speak and transmit Audio/Video/Data information to a terminal in the group.

2 is a diagram illustrating a network structure for performing an interworking service between a PS-LTE network and another service network through SMF according to an embodiment of the present invention.

According to an embodiment of the present invention, the VMS 201 monitors real-time video received from multiple CCTVs, analyzes a video stream received from CCTV, detects an event as a result of video stream analysis, and generates the detected event information as a message. After that, you can send a message to the stakeholders. In addition, it is possible to detect an event related to a change to a resource managed by the VMS, generate the detected event information, and then send a message to the person concerned. For example, changes to managed resources may correspond to CCTV additions, deletions, status information, and the like.

According to an embodiment of the present invention, the IoT Platform 203 analyzes the data for each sensor received from the installed sensors using various sensor information, and when the value of the data satisfies a set condition (eg, the data received from the fire sensor) If the temperature information is ^{above 100 o} , it is recognized as a topic event) and a message indicating that the condition has been satisfied can be sent to the relevant parties. In addition, it is possible to detect an event for a change to a resource managed by the IoT Platform, generate the detected event information, and then send a message to the person concerned. For example, changes to managed resources may correspond to sensor additions, deletions, status information, and the like.

According to an embodiment of the present invention, the SMF 205 may be a device that functions as a gateway for interworking with other service networks. The SMF 205 may perform, for example, configuration management, resource management, media processing, notification management, group communication service control, and the like.

Referring to FIG. 2 , the SMF 205 may receive an event related message from the VMS 201 or the IoT Platform 203 . The SMF 205 may check the message transmission server and the message, and determine whether to perform the VMS 201 interworking or the IoT Platform 203 interworking. In this case, the SMF 205 may determine parameters and data related to an interworking network, and may determine a message for interworking. Also, the SMF 205 may transmit a group message to at least one terminal 219 , 221 , and 223 through interworking with a wireless communication network. An example of the interworking method with the wireless communication network may be a direct interworking or an interworking method through the dispatcher 211, and the SMF 205 may determine the interworking method according to an interworking environment or input.

In addition, the SMF 205 may simultaneously receive an event-related message from a plurality of VMSs 201 , a plurality of IoT Platforms 203 , or a plurality of VMSs 201 and IoT Platform 203 . The SMF 205 may check the message transmission server and the message and determine whether to perform the cooperative mode.

The above operations for the SMF will be described in detail later.

3 is a flowchart illustrating an operation when an SMF receives an event message from a VMS according to an embodiment of the present invention.

Referring to FIG. 3 , in step S300 , the SMF receives an event message and data from the VMS. The event message received from the VMS may correspond to event information detected as a result of video stream analysis, and may include at least one of group-related information, data to be transmitted information, and server-related information.

In step S310, the SMF checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include identifier information for the user and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of an MCPTT ID, a group ID, and a GIS address, and the data information may be information related to whether session establishment is required data. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID distinguishes the MCPTT group in the MCPTT system, and the MCPTT system and the MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server.

The SMF may generate a SIP related message based on the parameter and data related information identified in step S320 or based on the VMS server. In this case, the SIP-related message is a message for requesting session establishment for group communication and may include the parameter. For example, the SIP-related message may be a SIP INVITE message including at least one of MCPTT ID and Group ID. In addition, if the server that has transmitted the event information is a VMS or the data related information is data requiring session establishment, the SMF may be generated in step S320, and the generated SIP related message may be a message for a call request. Specifically, data requiring session establishment may be streaming data or data requiring continuous data transmission and reception. The message for the call request may be a SIP INVITE message.

The SMF may transmit a SIP-related message to the MCPTX-AS in step S330. Alternatively, the SMF may transmit a SIP-related message to the MCPTX-AS via the CSCF in step S330.

The SMF may receive a response message related to the SIP-related message transmitted from the MCPTX-AS. The response message is a message for informing the SMF that the session establishment has been accepted in the MCPTX-AS, and may be, for example, a SIP 200 OK message. Alternatively, the SMF may receive a response message regarding the transmitted SIP-related message from the MCPTX-AS via the CSCF. When the SMF receives a response message related to the SIP-related message, it can know that the session establishment has been successful. Thereafter, the SMF may transmit a message indicating that the call is confirmed to the MCPTX-AS. Alternatively, the SMF may transmit a message indicating that the call is acknowledged to the MCPTX-AS via the CSCF. For example, the message indicating that the SMF call is acknowledged may be a SIP ACK message.

The SMF may transmit data to the MCPTX-AS in step S340 after the session establishment is completed. Alternatively, data may be transmitted to the MCPTX-AS via the CSCF. In this case, the data is transmitted to at least one terminal belonging to a specific group through the MCPTX service control server, and the at least one terminal may be determined based on the parameter information included in the SIP-related message.

4 is a diagram showing the overall operation of the network when the SMF 403 receives an event message from the VMS according to an embodiment of the present invention.

Referring to FIG. 4 , in step S401 , the VMS 401 may monitor real-time video, analyze a video stream received from CCTV, and generate an event message including event information detected as a result of video stream analysis. In this case, the event message may include at least one of group-related information, contextual information about data to be transmitted, and server-related information. For example, the contextual information may be information on fire, emergency, and real-time disaster. The information about the group is information about the group to which the situation is to be communicated, such as firefighters, police officers, and other persons concerned with the situation. The VMS 401 may transmit the event message and data to the SMF 403 in step S403 .

The SMF 403 checks the parameter information and data information of the service server based on the event message in step S405. In this case, the parameter information may include identifier information for the user and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of an MCPTT ID, a group ID, and a GIS address, and the data information may be information related to whether session establishment is required data. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID distinguishes the MCPTT group in the MCPTT system, and the MCPTT system and the MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server. In addition, the SMF 403 may generate a SIP related message based on the checked parameter and data related information or based on the VMS 401 server. In this case, the SIP-related message is a message for requesting session establishment for group communication and may include the parameter. For example, the SIP-related message may be a SIP INVITE message including at least one of MCPTT ID and Group ID. In addition, when the server that has transmitted the event information is the VMS 401 or the data related information is data requiring session establishment, the generated SIP related message may be a message for a call request. Specifically, data requiring session establishment may be streaming data or data requiring continuous data transmission and reception. The message for the call request may be a SIP INVITE message.

The SMF 403 may transmit a SIP-related message to the MCPTX-AS 407 based on the determined parameter and data-related information in step S407. Alternatively, the SIP-related message may be transmitted to the MCPTX-AS 407 via the CSCF 405 . In the embodiment of the present invention, the entire operation via the CSCF 405 will be mainly described, but this is only one embodiment, and a message, data or signal is transmitted via the CSCF 405 or the CSCF 405 There may be cases where it is not transmitted via the .

When the MCPTX-AS 407 receives a SIP-related message for a session establishment request for group communication, it may determine a transmission terminal 411 for a message transmission group and a member belonging to the group based on the SIP-related message. Specifically, the terminal 411 may be determined based on the parameter information included in the SIP-related message. The MCPTX-AS 407 may transmit a SIP-related message for indicating that session establishment has been requested from the SMF 403 to the determined transmission terminal 411 in step S411 . For example, the SIP related message for indicating to the terminal 411 that session establishment is requested from the SMF 403 may be a SIP INVITE message. Alternatively, the MCPTX-AS 407 may transmit a SIP-related message for indicating that the session establishment is requested to the CSCF 405 . The CSCF 405 may transmit the SIP-related message received from the MCPTX-AS 407 to the terminal 411 in step S413 .

When the terminal 411 receives the SIP-related message for the session establishment request, in step S415, to notify the MCPTX-AS 407 that it has been accepted by the terminal 411, a SIP-related message is transmitted to the MCPTX-AS 407. can For example, in order to inform the MCPTX-AS 407 that it has been accepted by the terminal 411, the SIP-related message may be a SIP 200 OK message. Alternatively, when the terminal 411 receives the SIP-related message for the session establishment request, in step S415, the terminal 411 transmits a SIP-related message to the CSCF 405 to inform the MCPTX-AS 407 that it has been accepted. . The CSCF 405 may transmit to the MCPTX-AS 407 a SIP-related message indicating that it has been accepted by the end user agent received from the terminal 411 in step S417 .

The MCPTX-AS 407 may transmit a SIP-related message to the SMF 403 for informing the SMF 403 that the terminal 411 has accepted the session establishment request in step S419 . For example, the SIP-related message for notifying the SMF 403 that the terminal 411 has accepted the session establishment request may be a SIP 200 OK message. Alternatively, the MCPTX-AS 407 may transmit a SIP-related message to the CSCF 405 for informing the SMF 403 that the terminal 411 has accepted the session establishment request in step S419 . The CSCF 405 may transmit to the SMF 403 a SIP-related message for notifying that the terminal 411 has accepted the session establishment request to the SMF 403 in step S421. Path established between MXPTX-AS (407) and SMF (403) through the above process.

When the SMF 403 receives a SIP-related message for notifying that the terminal 411 has accepted the session establishment request, in step S423 , the SMF 403 may transmit a call confirmation-related SIP message to the MCPTX-AS 407 . For example, the SIP message related to call acknowledgment may be a SIP ACK message. Alternatively, when the SMF 403 receives a SIP related message for notifying that the terminal 411 has accepted the session establishment request, in step S423 , the SMF 403 may transmit a call confirmation related SIP message to the CSCF 405 . When receiving the SIP message related to the call confirmation, the CSCF 405 may transmit a SIP message related to the call confirmation to the MCPTX-AS 407 in step S425.

The MCPTX-AS 407 may transmit to the terminal 411 a SIP message related to call confirmation for transmission to the terminal 411 in step S427 . For example, the SIP message related to the call confirmation to be transmitted to the terminal 411 may be a SIP ACK message. Alternatively, the MCPTX-AS 407 may transmit a SIP message related to call confirmation to be transmitted to the terminal 411 to the CSCF 405 in step S427 . When receiving the SIP message related to call confirmation to be transmitted to the terminal 411 , the CSCF 405 may transmit the received message to the terminal 411 in step S429 . Path established between the MXPTX-AS (407) and the terminal (411) through the above process.

The MCPTX-AS 407 may perform the MCPTX Client role in step S431 and transmit a SIP-related message for a session establishment request to the Dispatcher 409, which is an MCPTX service control manager, to the Dispatcher 409 . For example, the SIP-related message for requesting session establishment to the dispatcher 409 may be a SIP INVITE message including at least one of MCPTT ID and Group ID. Alternatively, the MCPTX-AS 407 may transmit a SIP-related message for a session establishment request to the Dispatcher 409, which performs the MCPTX Client role and is an MCPTX service control manager, to the CSCF 405 in step S431. When the CSCF 405 receives the SIP-related message for the session establishment request from the Dispatcher 409, in step S433, the CSCF 405 may transmit the SIP-related message to the Dispatcher 409.

Dispatcher 409 receives the SIP-related message for the session establishment request, and when accepting the session establishment request, in step S435, a SIP-related message for notifying the MCPTX-AS 407 that the session establishment request has been accepted. - Can be transmitted to the AS (407). For example, the SIP-related message for informing the MCPTX-AS 407 that the session establishment request has been accepted may be a SIP 200 OK message. Alternatively, the Dispatcher 409 receives the SIP-related message for the session establishment request, and when accepting the session establishment request, in step S435, a SIP-related message for notifying the MCPTX-AS 407 that the session establishment request has been accepted. It can be transmitted to the CSCF (405). When the CSCF 405 receives a SIP-related message for notifying the MCPTX-AS 407 that the session establishment request has been accepted, in step S437, the SIP-related message may be transmitted to the MCPTX-AS 407.

The MCPTX-AS 407 may transmit to the Dispatcher 409 a SIP message related to call confirmation for transmission to the Dispatcher 409 in step S439 . For example, the SIP message related to call acknowledgment to be transmitted to the dispatcher 409 may be a SIP ACK message. Alternatively, the MCPTX-AS 407 may transmit a SIP message related to call confirmation for transmission to the Dispatcher 409 to the CSCF 405 in step S439 . When the CSCF 405 receives the SIP message related to the call confirmation for transmission to the Dispatcher 409, the CSCF 405 may transmit the received message to the Dispatcher 409 in step S441.

Through the above process, PATH established between SMF (403) and MCPTX-AS (407), terminal (411) and MCPTX-AS (407), Dispatcher (409) and MCPTX-AS (407), and MCPTX-AS (407) ) may receive Audio/Video/Data information transmitted by the SMF 403 and transmit Audio/Video/Data information to the terminal 411 in the group. Specifically, the SMF 403 may transmit data to the MCPTX-AS 407 after the session establishment is completed. Alternatively, data may be transmitted to the MCPTX-AS 407 via the CSCF 405 . At this time, the data is transmitted to at least one terminal 411 belonging to a specific group through the MCPTX service control server, and the at least one terminal 411 is determined based on the parameter information included in the SIP-related message. can

5 is a flowchart illustrating an operation when the SMF 403 receives an event message from the IoT Platform according to an embodiment of the present invention.

Referring to FIG. 5 , in step S500 , the SMF receives an event message and data from the IoT Platform. The event message received from the IoT Platform analyzes the sensor-specific data received from the installed sensors using various sensor information, and when the data value satisfies a set condition (eg, the temperature information received from the fire sensor is 100 ^o If it is above, it is recognized as a topical event) and may correspond to a message indicating that the conditions have been satisfied to the relevant parties.

In step S510, the SMF checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include public service identifier information, user identifier information, and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a Public Service Identity (PSI), an MCPTT ID, a Group ID, and a PSI, and the data information may be information related to whether or not an instance message can be transmitted. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID distinguishes the MCPTT group in the MCPTT system, and the MCPTT system and the MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server.

The SMF may generate a SIP related message based on the parameter and data related information identified in step S520 or based on the IoT Platform server. In this case, the SIP-related message may include the parameter as a message for transmitting instance data. For example, the SIP-related message may be a SIP MESSAGE message including at least one of MCPTT ID, Group ID, PSI, and instance data. In addition, when the server that transmitted the event information is the IoT Platform or the data related information is sensor data, the SIP related message generated in step S520 may be a message for transmitting instance data. Specifically, instance data may include SMS and the like.

The SMF may transmit a SIP-related message to the MCPTX-AS in step S530. Alternatively, the SMF may transmit a SIP-related message to the MCPTX-AS via the CSCF in step S530. In this case, the SMF may transmit a SIP-related message including data to the MCPTX-AS without session establishment.

The SMF may receive a response message related to the SIP-related message transmitted from the MCPTX-AS. The response message is a message for informing the SMF that the instance message has been received in the MCPTX-AS, and may be, for example, a SIP 200 OK message. Alternatively, the SMF may receive a response message regarding the transmitted SIP-related message from the MCPTX-AS via the CSCF.

6 is a diagram illustrating the overall operation of the network when the SMF receives an event message from the IoT Platform according to an embodiment of the present invention.

Referring to FIG. 6 , in step S601, the IoT Platform analyzes the data for each sensor received from the installed sensors using various sensor information, and when the value of the data satisfies a set condition (eg, the temperature received from the fire sensor) If the information is ^{more than 100 o} , it is recognized as a topical event) and an event message can be generated to indicate that the condition is satisfied to the relevant parties. In this case, the event message may include at least one of group-related information, contextual information about data to be transmitted, and server-related information. For example, the contextual information may be information on fire, emergency, and real-time disaster. The information about the group is information about the group to which the situation is to be communicated, such as firefighters, police officers, and other persons concerned with the situation. The IoT Platform may transmit an event message and data to the SMF 603 in step S603 .

In step S605 , the SMF 603 checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include public service identifier information, user identifier information, and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a Public Service Identity (PSI), an MCPTT ID, and a Group ID, and the information about the data may be information related to whether data can transmit an instance message. . At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID distinguishes the MCPTT group in the MCPTT system, and the MCPTT system and the MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server. The SMF 603 may generate a SIP related message based on the checked parameter and data related information or based on the IoT Platform server. In this case, the SIP-related message may include the parameter as a message for transmitting instance data. For example, the SIP-related message may be a SIP MESSAGE message including at least one of MCPTT ID, Group ID, PSI, and instance data. In addition, when the server that transmitted the event information is the IoT Platform or the data-related information is instance data, the SMF 603 generated in step S520 may be a message for transmitting instance data. Specifically, instance data may include SMS and the like. The SMF 603 may transmit a SIP-related message to the MCPTX-AS 607 in step S607. Alternatively, the SMF 603 may transmit a SIP-related message to the MCPTX-AS 607 via the CSCF 605 in step S607. In this case, the SMF 603 may transmit a SIP-related message including data to the MCPTX-AS 607 without session establishment.

When the MCPTX-AS 607 receives a SIP-related message for transmitting instance data for group communication, it may transmit a SIP-related message for notifying that the instance data has been received to the SMF 603 in step S611. For example, the SIP-related message for notifying that the instance data has been received may be a SIP 202 ACCEPTED message. Alternatively, the MCPTX-AS 607 may transmit a SIP-related message for informing that the instance data has been received to the CSCF 605 in step S611. The CSCF may transmit a SIP-related message for notifying that the instance data has been received to the SMF 603 in step S613 .

When the MCPTX-AS 607 receives a SIP-related message for transmitting instance data for group communication, it may determine a message transmission group and the transmission terminal 611 based on the SIP-related message. Specifically, the terminal 611 may be determined based on the parameter information included in the SIP-related message. The MCPTX-AS 607 may transmit a message for transmitting the instance data received from the SMF 603 to the determined transmitting terminal 611 in step S615 . For example, the SIP-related message for transmitting instance data may be SIP MESSAGE. Alternatively, the SMF 603 may transmit a SIP related message for transmitting instance data to the CSCF 605 . The CSCF 605 may transmit the SIP-related message received from the MCPTX-AS 607 to the terminal 611 in step S617 .

When the terminal 611 receives a SIP-related message to transmit instance data, in step S619, to notify the MCPTX-AS 607 that the terminal 611 has accepted the SIP-related message to the MCPTX-AS 607. can For example, in order to inform the MCPTX-AS 607 that it has been received by the terminal 611, the SIP-related message may be a SIP 200 OK message. Alternatively, when the terminal 611 receives a SIP-related message for transmitting instance data, in step S619, to notify the MCPTX-AS 607 that it has been accepted by the terminal 611, a SIP-related message may be transmitted to the CSCF 605. have. The CSCF 605 may transmit to the MCPTX-AS 607 a SIP-related message indicating that it has been accepted by the end user agent received from the terminal 611 in step S621 .

The MCPTX-AS 607 may transmit, to the Dispatcher 609, a SIP-related message for transmitting instance data to the Dispatcher 609 serving as an MCPTX Client and serving as an MCPTX service control manager in step S623. For example, a SIP-related message for transmitting instance data to the dispatcher 609 may be a SIP MESSAGE message. Alternatively, the MCPTX-AS 607 may transmit a SIP-related message for transmitting instance data to the Dispatcher 609 serving as an MCPTX Client and transmitting the MCPTX service control manager to the CSCF 605 in step S623. When receiving the SIP-related message for transmitting instance data from the Dispatcher 609, the CSCF 605 may transmit the SIP-related message to the Dispatcher 609 in step S625.

When the Dispatcher 609 receives the SIP-related message for transmitting the instance data, in step S627, a SIP-related message for notifying the MCPTX-AS 607 that the SIP-related message for transmitting the instance data has been received. - Can be transmitted to the AS (607). For example, the SIP-related message for notifying the MCPTX-AS 607 that the message has been received may be a SIP 200 OK message. Alternatively, when the Dispatcher 609 receives a SIP-related message for transmitting instance data, in step S627, a SIP-related message to inform the MCPTX-AS 607 that it has received a SIP-related message for transmitting instance data. It can be transmitted to the CSCF (605). When receiving the SIP-related message from the MCPTX-AS 607 , the CSCF 605 may transmit the SIP-related message to the MCPTX-AS 607 in step S629 .

7 is a flowchart illustrating an operation when an SMF receives an event message from a VMS according to another embodiment of the present invention.

SMF can interwork with VMS and MCPTX-AS not only through direct interworking with wireless communication network, but also through interworking through Dispatcher. In this case, the SMF may determine the interworking method according to the interworking environment or input.

Referring to FIG. 7 , in step S700 , the SMF receives an event message and data from the VMS. The event message received from the VMS may correspond to event information detected as a result of video stream analysis, and may include at least one of group-related information, data to be transmitted information, and server-related information.

In step S710, the SMF checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include identifier information for the user and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a CCTV ID and a group ID, and the data information may be information related to whether or not session establishment is required data. At this time, the CCTV ID identifies the CCTV inside the CCTV VMS network, and the Group ID identifies the MCPTT group in the MCPTT system, and may refer to the MCPTT system referred to by the MCPTT group and the MCPTT server in the MCPTT system where the group is defined.

The SMF may determine the group call generation related API message based on the parameter and data related information identified in step S720 or based on the VMS server. In this case, the group call creation related API message is a message for requesting session establishment for group communication and may include the parameter. For example, an API message related to group call creation may be a CreateGroupCall message based on Dispatcher's Open API. In addition, if the server that transmitted the event information is a VMS or the data related information is data requiring session establishment, the group call generation related API message generated in step S720 may be a message for a call request. Specifically, data requiring session establishment may be streaming data or data requiring continuous data transmission and reception. The message for the call request may be a CreateGroupCall message based on Dispatcher's Open API.

The SMF may transmit an API message related to group call generation to the dispatcher in step S730. The dispatcher may generate a SIP-related message based on the parameters included in the group call generation-related API message. In this case, the SIP-related message is a message for requesting session establishment for group communication and may include the parameter. For example, the SIP related message may be a SIP INVITE message.

The SMF may receive a response message to the group call creation related API message from the dispatcher. For example, the response message may be a 200 OK message based on Dispatcher's Open API. The SMF may receive a Real Time Streaming Protocol (RTSP) related information message from the dispatcher in step S740. For example, the RTSP-related information message may be at least one of OPTIONS, PAUSE, DESCRIBE, GET_PARAMETER, SET_PARAMETER, SETUP, PLAY, and TEARDOWN.

When receiving the RTSP-related information message, the SMF may transmit an RTSP response message in step S750. For example, the RTSP response message may be an RTSP 200 OK message.

SMF can transmit data to Dispatcher after session establishment is completed. In this case, the data is transmitted to at least one terminal belonging to a specific group through the Dispatcher and the MCPTX service control server, and the at least one terminal may be determined based on parameter information included in the group call generation related API message. .

8 is a diagram showing the overall operation of the network when the SMF receives an event message from the VMS according to another embodiment of the present invention.

Referring to FIG. 8 , in step S801 , the VMS 801 may monitor real-time video, analyze a video stream received from CCTV, and generate an event message including event information detected as a result of video stream analysis. In this case, the event message may include at least one of group-related information, contextual information about data to be transmitted, and server-related information. For example, the contextual information may be information on fire, emergency, and real-time disaster. The information about the group is information about the group to which the situation is to be communicated, such as firefighters, police officers, and other persons concerned with the situation. The VMS 801 may transmit the event message and data to the SMF 803 in step S803 .

The SMF 803 receives an event message and data from the VMS 801 in step S803. The event message received from the VMS 801 may correspond to event information detected as a result of video stream analysis, and may include at least one of group information, data to be transmitted, and server-related information. In step S805 , the SMF 803 checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include identifier information for the user and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a CCTV ID and a group ID, and the information about data may be information related to whether or not session establishment is required data. At this time, the CCTV ID distinguishes the CCTV inside the VMS 801 network, and the Group ID identifies the MCPTT group in the MCPTT system, and the MCPTT system referred to by the MCPTT group and the MCPTT server in the MCPTT system in which the group is defined may refer to. The SMF 803 may determine the group call creation related API message based on the identified parameter and data related information or based on the VMS 801 server. In this case, the group call creation related API message is a message for requesting session establishment for group communication and may include the parameter. For example, the group call creation related API message may be a CreateGroupCall message based on the Open API of the Dispatcher 809 . In addition, when the server that has transmitted the event information is the VMS 801 or the data related information is data requiring session establishment, the generated group call generation related API message may be a message for a call request. Specifically, data requiring session establishment may be streaming data or data requiring continuous data transmission/reception. The message for the call request may be a CreateGroupCall message based on the Open API of the Dispatcher 809 .

The SMF 803 may transmit a group call generation related API message to the dispatcher 809 in step S807.

When the dispatcher 809 receives the group call generation related API message, the dispatcher 809 may check identifier information about the user based on the group call generation related API message. For example, the identifier information for the user may be an MCPTT ID. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user. Thereafter, the dispatcher 809 may generate a SIP-related message based on the checked parameter and the group call generation-related API message. In this case, the generated SIP-related message may be a message for a call request. Specifically, the message for the call request may be a SIP INVITE message including at least one of MCPTT ID and Group ID.

Dispatcher 809 may transmit a SIP-related message to the MCPTX-AS 807 in step S809. Alternatively, the SMF 803 may transmit a SIP-related message to the MCPTX-AS 807 via the CSCF 805 in step S809. At this time, the CSCF 805 may transmit a SIP-related message to the MCPTX-AS 807 in step S811.

When the MCPTX-AS 807 receives a SIP-related message for a session establishment request for group communication, it may determine a message transmission group and the transmission terminal 811 based on the SIP-related message. Specifically, the terminal 811 may be determined based on the parameter information included in the SIP-related message. The MCPTX-AS 807 may transmit a SIP-related message for indicating that session establishment has been requested from the Dispatcher 809 to the determined transmitting terminal 811 in step S813 . For example, the SIP related message for indicating to the terminal 811 that the dispatcher 809 has requested session establishment may be a SIP INVITE message. Alternatively, the MCPTX-AS 807 may transmit a SIP-related message to the CSCF 805 for indicating that session establishment has been requested. The CSCF 805 may transmit the SIP-related message received from the MCPTX-AS 807 to the terminal 811 in step S815 .

The terminal 811 transmits a SIP-related message to the MCPTX-AS 807 to inform the MCPTX-AS 807 that it has been accepted by the terminal 811 in step S817 when receiving the SIP-related message for the session establishment request. can For example, in order to inform the MCPTX-AS 807 that it has been accepted by the terminal 811, the SIP-related message may be a SIP 200 OK message. Alternatively, when the terminal 811 receives the SIP-related message for the session establishment request, in step S817, to inform the MCPTX-AS 807 that it has been accepted by the terminal 811, a SIP-related message may be transmitted to the CSCF 805. . The CSCF 805 may transmit to the MCPTX-AS 807 a SIP-related message indicating that it has been accepted by the end user agent received from the terminal 811 in step S819 .

The MCPTX-AS 807 may transmit a SIP-related message to the Dispatcher 809 to inform the Dispatcher 809 that the terminal 811 has accepted the session establishment request in step S821. For example, the SIP related message for notifying the dispatcher 809 that the terminal 811 has accepted the session establishment request may be a SIP 200 OK message. Alternatively, the MCPTX-AS 807 may transmit a SIP-related message to the CSCF 805 for informing the Dispatcher 809 that the terminal 811 has accepted the session establishment request in step S821. The CSCF 805 may transmit a SIP-related message to the dispatcher 809 to inform the dispatcher 809 that the terminal 811 has accepted the session establishment request in step S823.

Dispatcher 809 may transmit a SIP message related to call confirmation to the MCPTX-AS 807 in step S825 when receiving a SIP-related message for notifying that the terminal 811 has accepted the session establishment request. For example, the SIP message related to call acknowledgment may be a SIP ACK message. Alternatively, when the Dispatcher 809 receives a SIP-related message for notifying that the UE 811 has accepted the session establishment request, in step S825 , the Dispatcher 809 may transmit a call confirmation related SIP message to the CSCF 805 . When receiving the SIP message related to the call confirmation, the CSCF 805 may transmit a SIP message related to the call confirmation to the MCPTX-AS 807 in step S827.

The MCPTX-AS 807 may transmit a SIP message related to a call confirmation for transmission to the terminal 811 to the terminal 811 in step S829. For example, the SIP message related to the call confirmation to be transmitted to the terminal 811 may be a SIP ACK message. Alternatively, the MCPTX-AS 807 may transmit a SIP message related to call confirmation for transmission to the terminal 811 to the CSCF 805 in step S829. When receiving the SIP message related to call confirmation to be transmitted to the terminal 811 , the CSCF 805 may transmit the received message to the terminal 811 in step S831 . Through this, Path Established between the MXPTX-AS (807) and the terminal (811)

When the Dispatcher 809 receives a SIP-related message for notifying that the terminal 811 has accepted the session establishment request to the Dispatcher 809 in step S823, group call generation related to the SMF 803 in step S833 A response message to an API message can be transmitted. For example, the response message may be a 200 OK message based on the Open API of the Dispatcher 809 . The dispatcher 809 may transmit a Real Time Streaming Protocol (RTSP) related information message to the SMF 803 in step S835 . For example, the RTSP-related information message may be at least one of RTSP OPTIONS, RTSP DESCRIBE, and RTSP SETUP.

When receiving the RTSP-related information message, the SMF 803 may transmit an RTSP response message in step S837. For example, the RTSP response message may be an RTSP 200 OK message. Through this, Path Established between MXPTX-AS (807) and SMF (803).

Through the above process, PATH established between SMF (803) and MCPTX-AS (807), terminal (811) and MCPTX-AS (807), Dispatcher (809) and MCPTX-AS (807), and MCPTX-AS (807) ) may receive Audio/Video/Data information transmitted by the SMF 803 and transmit Audio/Video/Data information to the terminal 811 in the group. Specifically, the SMF 803 may transmit data to the Dispatcher 809 after the session establishment is completed. At this time, the data is transmitted to at least one terminal 811 belonging to a specific group through the MCPTX service control server, and the at least one terminal 811 is determined based on the parameter information included in the SIP-related message. can

9 is a flowchart illustrating an operation when the SMF receives an event message from the IoT Platform according to another embodiment of the present invention.

SMF can link IoT Platform and MCPTX-AS through the method of direct interworking with wireless communication network as well as the interworking method through Dispatcher. In this case, the SMF may determine the interworking method according to the interworking environment or input.

Referring to FIG. 9 , in step S900 , the SMF receives an event message and data from the IoT Platform. The event message received from the IoT Platform analyzes the sensor-specific data received from the installed sensors using various sensor information, and when the data value satisfies a set condition (eg, the temperature information received from the fire sensor is 100 ^o If it is above, it is recognized as a topical event) and may correspond to a message indicating that the conditions have been satisfied to the relevant parties.

In step S910, the SMF checks parameter information and data information of the service server based on the event message. In this case, the parameter information may include at least one of sensor identifier information and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a group ID and a sensor ID, and the data information may be information related to whether or not an instance message can be transmitted. At this time, the Sensor ID identifies the sensor inside the IoT Platform and can identify the user profile for MCPTT application layer users. It may refer to the MCPTT server in the system.

The SMF may determine the notification related API message based on the parameter and data related information identified in step S920 or based on the IoT platform. In this case, the notification-related API message may include the parameter as a message for transmitting an instance message. For example, the notification-related API message may be NotifyMessage based on Dispatcher's Open API. In addition, if the server that transmitted the event information is the IoT Platform or the data related information is instance data, the notification related API message generated in step S920 may be a message for transmitting the instance message. Specifically, instance data may include SMS and the like.

The SMF may transmit a notification-related API message to the dispatcher in step S930. The Dispatcher may generate a SIP-related message based on parameters included in the notification-related API message. In this case, the SIP-related message is a message for transmitting the instance message and may include the parameters and instance data. For example, the SIP-related message may be a SIP MESSAGE message including at least one of MCPTT ID, Group ID, PSI, and instance data.

The SMF may receive a response message to the notification-related API message from the Dispatcher. For example, the response message may be a 200 OK message based on Dispatcher's Open API.

10 is a diagram showing the overall operation of the network when the SMF receives an event message from the IoT Platform according to another embodiment of the present invention.

Referring to FIG. 10 , the IoT Platform 1001 analyzes the data for each sensor received from the installed sensors using various sensor information in step S1001, and when the value of the data satisfies a set condition (eg, from a fire sensor) If the received temperature information is 100 ^{o or} higher, it is recognized as a hot topic event), and an event message can be generated to indicate that the conditions have been satisfied. In this case, the event message may include at least one of group-related information, contextual information about data to be transmitted, and server-related information. For example, the contextual information may be information on fire, emergency, and real-time disaster. The information about the group is information about the group to which the situation is to be communicated, such as firefighters, police officers, and other persons concerned with the situation. The IoT Platform 1001 may transmit an event message and data to the SMF in step S1003.

In step S1005, the SMF checks parameter information and data information of the service server, based on the event message. In this case, the parameter information may include at least one of sensor identifier information and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a group ID and a sensor ID, and the data information may be information related to whether or not an instance message can be transmitted. At this time, the Sensor ID identifies the sensor inside the IoT Platform 1001 and can identify the user profile for the MCPTT application layer user. The Group ID identifies the MCPTT group in the MCPTT system, and the MCPTT system and group referred to by the MCPTT group It may refer to the MCPTT server in the defined MCPTT system. The SMF may determine the notification related API message based on the identified parameter and data related information or based on the IoT Platform 1001 . In this case, the notification-related API message may include the parameter as a message for transmitting an instance message. For example, the notification-related API message may be NotifyMessage based on Dispatcher's Open API. In addition, when the server that transmitted the event information is the IoT Platform 1001 or the data related information is instance data, the generated notification related API message may be a message for transmitting the instance message. Specifically, instance data may include SMS and the like.

SMF may transmit notification related API message to Dispatcher in step S1007.

When the dispatcher receives a notification-related API message, the dispatcher may transmit an API-related message to the SMF for notifying the SMF that the notification-related API message has been received in step S1009. For example, the API related message for notifying the SMF may be an API 200 OK message.

Based on the parameters included in the dispatcher notification related API message, public service identifier information and user identifier information can be checked. For example, public service identifier information may include PSI, and user identifier information may include MCPTT ID. In this case, MCPTT ID identifies MCPTT users and identifies user profiles for MCPTT application layer users. Thereafter, the Dispatcher may generate a SIP-related message based on the identified identifier information and notification-related API message. Specifically, the SIP-related message may be a SIP MESSAGE for instance data transmission. In this case, the SIP MESSAGE may include at least one of MCPTT ID, Group ID, PSI, and instance data.

Dispatcher 1009 may transmit a SIP-related message to the MCPTX-AS 1007 in step S1011. Alternatively, the SMF 1003 may transmit a SIP-related message to the MCPTX-AS 1007 via the CSCF 1005 in step S1011. In this case, the CSCF 1005 may transmit a SIP-related message to the MCPTX-AS 1007 in step S1013.

The MCPTX-AS may transmit a SIP-related message to the Dispatcher for notifying that the instance message has been received in step S1015. For example, the SIP-related message for notifying that the instance message has been received may be a SIP 202 ACCEPTED message. Alternatively, the MCPTX-AS may transmit a SIP-related message to the CSCF for notifying that the instance message has been received in step S1015. After CSCF, in step S1017, a SIP-related message for notifying that the instance message has been received may be transmitted to the dispatcher.

When the MCPTX-AS receives a message for transmitting instance data, it may determine the message transmission group and the transmission terminal 811 based on the SIP-related message. Specifically, the terminal 811 may be determined based on the parameter information included in the SIP-related message. The MCPTX-AS 807 may transmit a message for transmitting instance data to the determined transmission terminal 811 in step S1019. In this case, the message for transmitting instance data may be SIP MESSAGE. Alternatively, the MCPTX-AS 807 may transmit a message for transmitting instance data to the CSCF in step S1019. In this case, a message for transmitting instance data may be transmitted to the terminal 1011 in step S1021 of CSCF.

When the terminal receives the SIP-related message, it may transmit a message to the MCPTX-AS to inform that the SIP-related message has been received in step S1023. For example, a message for notifying that a SIP-related message has been received may be a SIP 200 OK message. Alternatively, when the terminal receives the SIP-related message, it may transmit a message to the CSCF to inform that the SIP-related message has been received in step S1023. In this case, the CSCF may transmit a message to the MCPTX-AS to inform that the SIP-related message has been received.

11 is a flowchart illustrating an operation when an SMF receives an event message according to an embodiment of the present invention.

The SMF may have a different configuration and interworking method depending on the event message. 11 illustrates that the SMF selects the interworking configuration centering on the direct interworking method among the direct interworking method Dispatcher interworking methods for convenience of explanation, but this is not intended to limit the technical features of the present invention. That is, the SMF may determine the interworking method according to the interworking environment or input.

Referring to FIG. 11 , the SMF may receive at least one event message from at least one service server in step S1101.

The SMF checks parameter information and data information based on the at least one event message and the service server in step S1103.

a) When the at least one service server is a VMS,

b) When the at least one event message is a message to the concerned parties after analyzing the video stream received from the CCTV and generating the event information detected as a result of the video stream analysis as a message,

c) When the data transmitted from the service server is data that requires session establishment

When at least one of conditions a, b, and c is satisfied, the parameter information may be identified as parameter information that is determined based on the event message and may include user identifier information and group identifier information for the user. For example, the parameter information may include at least one of an MCPTT ID, a group ID, and a GIS address, and the data information may be information related to whether session establishment is required data. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID identifies the MCPTT group in the MCPTT system, and the MCPTT system and MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server.

Thereafter, the SMF checks parameter information and data information based on the at least one event message and the service server, and if at least one of a, b, c is satisfied, proceeds to step S1107 and configures the service server and MCPTX through the VMS interworking configuration. The server can be linked. The VMS interworking configuration has been described in detail with reference to FIGS. 3 and 4 above.

d) when the at least one service server is SMF,

e) When the at least one event message is a message indicating that the condition is satisfied to the concerned parties because the value analyzed for each sensor data received from the installed sensors using various sensor information satisfies the set condition,

f) When the data transmitted from the service server is instance data

If it corresponds to at least one of d, e, and f, it will be confirmed that the parameter information includes public service identifier information, identifier information for a user, and group identifier information for the user, determined based on the event message. can For example, the parameter information may include at least one of an MCPTT ID, a Group ID, and a PSI, and the data information may be information related to whether or not an instance message can be transmitted.

Thereafter, the SMF checks parameter information and data information based on the at least one event message and the service server, and if at least one of the conditions d, e, and f is satisfied, proceeds to step S1105 and communicates with the service server through the IoT Platform interworking configuration. MCPTX server can be linked. The IoT Platform interworking configuration has been described in detail with reference to FIGS. 5 and 6 above.

12 is a flowchart illustrating that the SMF operates in a cooperate mode when receiving an event message according to an embodiment of the present invention.

The SMF may receive at least one event message from at least one service server in step S1201.

The SMF may check whether the at least one service server is a plurality of service servers in step S1203.

If it is not the case that the SMF receives at least one message from a plurality of servers, the process proceeds to step S1209 to perform an SMF operation corresponding to the received message. When the SMF receives at least one message from a plurality of servers, it proceeds to step S1205. The SMF may determine whether the received message is a message related to the same event in step S1205. For example, the event message may include at least one of an event type (eg, fire, smoke, invasion, cluster, etc.), group information, situation information about data to be transmitted, and server-related information. This may mean a case in which the event recognized by the VMS and the event recognized by the IoT Platform are the same at a specific location and at a specific point in time.

If the received message is not a message related to the same event, the process proceeds to step S1209 to perform an SMF operation corresponding to the received message. If the received message is a message related to the same event, the SMF proceeds to S1207.

The SMF checks the parameter information and data information of the service server based on the event message in step S1207. In this case, the parameter information may include public service identifier information, user identifier information, and group identifier information for the user, determined based on the event message. For example, the parameter information may include at least one of a Public Service Identity (PSI), an MCPTT ID, a Group ID, and a PSI, and the data information may be information related to whether or not an instance message can be transmitted. At this time, the MCPTT ID identifies the MCPTT user and can identify the user profile for the MCPTT application layer user, and the Group ID identifies the MCPTT group in the MCPTT system, and the MCPTT system and MCPTT system in the MCPTT system that the MCPTT group refers to. It can refer to a server.

The SMF may generate a SIP related message based on the checked parameter and data related information or based on the IoT Platform server. In this case, the SIP-related message may include the parameter as a message for transmitting instance data. For example, the SIP-related message may be a SIP MESSAGE message including at least one of MCPTT ID, Group ID, PSI, and instance data. In addition, if the server that transmitted the event information is the IoT Platform or the data related information is instance data, the SIP related message generated in step S520 may be a message for transmitting instance data. Specifically, instance data may include SMS and the like.

The SMF may transmit a SIP-related message to the MCPTX-AS. Alternatively, the SMF may transmit a SIP-related message to the MCPTX-AS via the CSCF. In this case, the SMF may transmit a SIP-related message including data to the MCPTX-AS without session establishment.

The SMF may receive a response message related to the SIP-related message transmitted from the MCPTX-AS. The response message is a message for informing the SMF that the instance message has been received in the MCPTX-AS, and may be, for example, a SIP 200 OK message. Alternatively, the SMF may receive a response message regarding the transmitted SIP-related message from the MCPTX-AS via the CSCF.

13 is a diagram illustrating an overall operation of a network when an SMF receives a message regarding resource change information according to an embodiment of the present invention.

SMF receives resource change information from various service servers such as VMS or IoT Platform and delivers it to GIS of PS-LTE network. can Specifically, referring to FIG. 13 , the service server may detect a change in CCTV or a change in Sensor, which is resource information configured in the network, in step S1301. For example, resource changes can include additions, deletions, and state changes of resources.

Thereafter, the service server may transmit a resource information message regarding the resource change to the SMF in step S1303.

The SMF receives the resource information message regarding the resource change from the service server in step S1303. The resource information about the resource change received from the service server may include at least one of information about the change and a resource identifier. In step S1303, the SMF checks the parameter information of the service server, based on the resource information message. In this case, the parameter information may include at least one of CCTV ID and Sensor ID. The SMF may determine an API message related to device information based on the checked parameter and context information. For example, it can be a CreateDeviceInfo message for adding a resource, DeleteDeviceInfo for deleting a resource, ChangeDeviceInfo for a resource information change, and ChangeDeviceStatus message for a resource status change. In this case, the API message related to the device information may include the parameter.

The SMF may transmit the API message regarding the device information determined in step S1305 to the GIS.

When the GIS receives an API message about device information in step S1307, the GIS may transmit an API-related message to the SMF to inform the SMF that the GIS has accepted the message. To inform the SMF that it has been accepted by the GIS, the API related message may be an API 200 OK message.

14 is a structural diagram showing the structure of an SMF according to an embodiment of the present invention.

The SMF includes a transceiver 1400 and a control unit 1410 . The transceiver 1400 may transmit or receive data from another device (eg, a base station, VMS, IoT Platform, GIS, MCPTX-AS, etc.).

The controller 1410 performs various operations of the SMF according to embodiments of the present invention by controlling the states and operations of all components included in the SMF. Specifically, the control unit receives at least one event message from any one service server among at least one service server, and checks parameter information and data information of the service server based on the at least one event message, and Control to generate a Session Initiation Protocol (SIP) related message corresponding to the service server, the parameter information and the data information, and transmit the generated SIP related message to the MCPTX service control server to be linked with the service server can do.

In addition, the control unit receives at least one resource change information message from any one service server among at least one service server, and based on the at least one resource change information message, parameter information including the GIS address of the service server control to generate a Session Initiation Protocol (SIP) related message corresponding to the service server and the parameter information, and transmit the generated SIP related message to the GIS server to be linked with the service server can

15 is a structural diagram showing the structure of the MCPTX-AS according to an embodiment of the present invention.

The MCPTX-AS includes a transceiver 1500 and a control unit 1510 . The transceiver 1500 may transmit or receive data from another device (eg, a base station, a CSCF, a terminal, an SMF, etc.).

When receiving a message for requesting a session establishment for group communication and a message for transmitting instance data, the controller 1510 may determine a message transmission group and a transmission terminal based on the received message.

According to an embodiment of the present invention, a gateway function for interworking with other service networks is provided through SMF, and MCPTX and a separate service server can be interlocked more efficiently.

Embodiments disclosed in the present specification and drawings are merely provided for specific examples to easily explain technical content and help understanding, and are not intended to limit the scope of the present invention. It will be apparent to those of ordinary skill in the art to which the present invention pertains that other modifications based on the technical spirit of the present invention can be implemented in addition to the embodiments disclosed herein.

On the other hand, in the present specification and drawings, preferred embodiments of the present invention have been disclosed, and although specific terms are used, these are only used in a general sense to easily explain the technical content of the present invention and to help the understanding of the present invention, It is not intended to limit the scope of the invention. In addition to the embodiments disclosed herein, it is apparent to those of ordinary skill in the art that other modifications based on the technical spirit of the present invention can be implemented.

Claims (18)

In the method of a device performing a service integration function (Service Mash-up Function: SMF) for interworking with MCPTX-AS (Mission Critical Push To Everything - Application Server) server in a wireless communication system,
Receiving at least one event message from any one of the at least one service server;
checking parameter information and data information of the service server based on the at least one event message;
generating a Session Initiation Protocol (SIP) related message corresponding to the service server, the parameter information, and the data information; and
Method of a device for performing SMF, comprising the step of transmitting the generated SIP-related message to the MCPTX service control server to be interlocked with the service server. The method of claim 1,
When the at least one service server is a video management system, the parameter information includes:
It includes identifier information for the user and group identifier information for the user, determined based on the event message,
The method of the apparatus for performing SMF, characterized in that the SIP-related message is an INVITE message for a call request.
3. The method of claim 2,
The method of the apparatus for performing SMF, characterized in that the event message includes at least one of information on the condition information, event transmission target information, and data type analyzed from the video management system.

The method of claim 1,
The data information is confirmed as either streaming data or instance data based on the event message,
When the data information is confirmed as the streaming data, the SIP-related message is determined as an INVITE message for a call request,
When the data information is identified as the instance data, the SIP-related message is determined as a MESSAGE message for transmitting an instant message.
The method of claim 1,
When the at least one service server is an IoT platform server, the parameter information is
including public service identifier information, identifier information for a user, and group identifier information for the user, determined based on the event message;
The method of the apparatus for performing SMF, characterized in that the SIP-related message is a MESSAGE message for transmitting an instant message.

According to claim 1, wherein the receiving step,
characterized in that it receives more data,
When the at least one service server is a video management system,
The data is delivered to the MCPTT server through a session created based on the SIP-related message,
When the at least one service server is an IoT platform server,
The data is included in the SIP-related message, the method of the device for performing SMF, characterized in that delivered to the MCPTX service control server.

7. The method of claim 6,
The data is transmitted to at least one terminal belonging to a specific group through the MCPTX service control server,
The method of the apparatus for performing SMF, characterized in that the at least one terminal is determined based on the parameter information included in the SIP-related message.

The method of claim 1,
When at least one service server is a plurality of service servers,
receiving an event message from each service server;
determining whether the received message is a message related to the same event;
If the received message is a message related to the same event, the determining may include: determining parameter information including a PSI ID, an MCPTT ID, and a Group ID corresponding to the event message; and
determining data information including content corresponding to the event message;
The method of the apparatus for performing SMF, characterized in that the SIP-related message is a MESSAGE message for transmitting an instant message.
In the method of the service integration function device (Service Mash-up Function: SMF) for interworking with MCPTX-AS (Mission Critical Push To Everything - Application Server) server in a wireless communication system,
Receiving at least one resource change information message from any one of the at least one service server;
checking parameter information including a GIS address of the service server based on the at least one resource change information message;
generating a Session Initiation Protocol (SIP) related message corresponding to the service server and the parameter information; and
and transmitting the generated SIP-related message to a GIS server to be linked with the service server.


In a device for performing a service integration function (Service Mash-up Function: SMF) for interworking with MCPTX-AS (Mission Critical Push To Everything - Application Server) server in a wireless communication system,
a transceiver for transmitting and receiving a signal to and from the server; and
Receive at least one event message from any one service server among at least one service server, and check parameter information and data information of the service server based on the at least one event message, the service server, the It includes a control unit for generating a Session Initiation Protocol (SIP) related message corresponding to the parameter information and the data information, and controlling to transmit the generated SIP related message to the MCPTX service control server to be linked with the service server A device for performing SMF, characterized in that.

The method according to claim 10, wherein when the at least one service server is a video management system, the parameter information comprises:
It includes identifier information for the user and group identifier information for the user, determined based on the event message,
The SIP-related message is an apparatus for performing SMF, characterized in that it is an INVITE message for a call request.
12. The method of claim 11,
The method of the apparatus for performing SMF, characterized in that the event message includes at least one of information on the condition information, event transmission target information, and data type analyzed from the video management system.

11. The method of claim 10,
The data information is confirmed as either streaming data or instance data based on the event message,
When the data information is confirmed as the streaming data, the SIP-related message is determined as an INVITE message for a call request,
When the data information is identified as the instance data, the SIP-related message is determined as a MESSAGE message for transmitting an instance message.
11. The method of claim 10,
When the at least one service server is an IoT platform server, the parameter information is
including public service identifier information, identifier information for a user, and group identifier information for the user, determined based on the event message;
The method of the apparatus for performing SMF, characterized in that the SIP-related message is a MESSAGE message for transmitting an instant message.

The method of claim 10, wherein the transceiver comprises:
receive more data,
The control unit is
When the at least one service server is a video management system, the data is controlled to be transmitted to the MCPTX service control server through a session created based on the SIP-related message, and the at least one service server is an IoT platform server In the case of , the data is included in the SIP-related message and is controlled to be transmitted to the MCPTX service control server.

16. The method of claim 15,
The data is transmitted to at least one terminal belonging to a specific group through the MCPTX service control server,
The at least one terminal is an apparatus for performing SMF, characterized in that it is determined based on the parameter information included in the SIP-related message.

11. The method of claim 10, wherein the control unit,
When at least one service server is a plurality of service servers,
Receives an event message from each service server, determines whether the received message is a message related to the same event, and if the received message is a message related to the same event, PSI ID and MCPTT ID corresponding to the event message and determining parameter information including Group ID, determining data information including content corresponding to the event message, and performing SMF, wherein the SIP-related message is a MESSAGE message for transmitting an instant message Device.
In a service integration function device (Service Mash-up Function: SMF) for interworking with MCPTX-AS (Mission Critical Push To Everything - Application Server) server in a wireless communication system,
a transceiver for transmitting and receiving a signal to and from the server; and
Receive at least one resource change information message from any one service server among at least one service server, and check parameter information including the GIS address of the service server based on the at least one resource change information message, , a control unit for generating a Session Initiation Protocol (SIP) related message corresponding to the service server and the parameter information, and controlling to transmit the generated SIP related message to a GIS server to be linked with the service server A device for performing SMF, characterized in that.

Images