KR20220143563A - Wireless communication method and apparatus for supporting rcs - Google Patents

Abstract

According to the present invention, a wireless communication method supporting a rich communication suite (RCS) service may comprise: a step of performing an RCS provision operation for an OEM application through an IP multimedia subsystem (IMS) native service module by responding to an RCS service request from the OEM application; a step of, when the RCS provision operation is completed, requesting for an RCS function connection to a session initiation protocol (SIP) transport layer through an SIP transport adapter and an SIP transport interface; a step of controlling a session for an RCS function by the SIP transport layer based on a control method for each RCS function; and a step of exchanging the RCS media data with a network through a dedicated bearer. The present invention is able to provide an improved quality of service.

Description

WIRELESS COMMUNICATION METHOD AND APPARATUS FOR SUPPORTING RCS

The technical idea of the present disclosure relates to a method and an apparatus for supporting a Rich Communication Suite (RCS) service, and specifically includes a SIP transport layer and a SIP transport adapter connected by a Session Initiation Protocol (SIP) transport interface, and To a wireless communication device and method, through which an OEM application directly uses a SIP transport layer and a media-only bearer.

In order to meet the increasing demand for wireless data traffic after the commercialization of the 4G communication system, an improved 5G communication system is being developed. In recent mobile communication, the introduction of mobile terminals that can access the communication network and use data services is accelerating due to the growth of the LTE (Long Term Evolution) network and the introduction of the 5G NR (New Radio) network. Voice over Long Term Evolution (VoLTE) supporting voice calls using LTE networks and Voice over New Radio (VoNR) supporting voice calls using 5G NR networks are being introduced and developed.

Moreover, with the development of mobile communication, users of mobile terminals are simply using the mobile terminal for various purposes other than voice calls. Accordingly, the Global System for Mobile Communications Association (GSMA) has proposed a Rich Communication Suite (RCS) that provides various communication functions to users of mobile terminals through a communication network. The RCS service is an IP Multimedia Subsystem (IMS)-based unified messaging service, and allows not only voice, but also video, SMS (Short Message Service), chatting, and file sharing to be integrated and used through a communication network. As a specific example, the RCS service provides a call function that shares multimedia files such as videos or photos during a call (Enriched Call), an address book function that can acquire information about the other party registered in the address book in real time (Enhanced Phonebook), and during chatting A message function (Enriched Messaging) for sharing files, etc. may be provided.

IMS, which forms the basis of RCS service, is a standard of a network framework adopted by 3GPP to provide multimedia services in an IP network. The IMS standard defines signal connection processing between target terminals that want to use a service, media processing for transmitting actual service data, quality, and billing method. A representative protocol used in IMS is SIP (Session Initiation Protocol), which is a protocol for multimedia communication for establishing, changing, and terminating a session.

As the performance of a terminal and a wireless network is greatly improved, research on a wireless communication device and a wireless communication method capable of providing an RCS service together with a VoLTE/VoNR service has been recently expanded.

It is an object of the present disclosure to include a SIP transport interface and a SIP transport layer and a SIP transport adapter configured to directly access the SIP transport layer of a modem processor from an application processor performing RCS service of an OEM application, including IMS single registration (Single Registration) and to propose a wireless communication device and method for enabling the use of a dedicated bearer.

In order to achieve the above object, a wireless communication method supporting a Rich Communication Suite (RCS) service according to an aspect of the technical idea of the present disclosure responds to an RCS service request of an OEM application, and an IP Multimedia Subsystem (IMS) native performing an RCS provisioning operation for the OEM application through a native service module, when the RCS provisioning operation is completed, through a SIP (Session Initiation Protocol) transport adapter and a SIP transport interface Sending an RCS function connection request to the SIP transport layer, controlling a session for the RCS function by the SIP transport layer based on the SIP transaction control for the RCS service, and the dedicated bearer exchanging RCS media data with the network.

A wireless communication device supporting an RCS service according to an aspect of the technical concept of the present disclosure includes a SIP transport adapter configured to be directly connected to a Session Initiation Protocol (SIP) transport layer to support an RCS function of an OEM application, the An application processor including an IP multimedia subsystem (IMS) native service module configured to perform an RCS provisioning operation for an OEM application, an application processor interface; a modem processor comprising a SIP transaction layer and a SIP transaction user layer for native provisioning operations and native services, and a SIP transport layer configured to be connected through a SIP transport interface with a SIP transport adapter of the application processor; have.

A modem processor supporting an RCS service according to an aspect of the technical concept of the present disclosure is a modem processor supporting a Rich Communication Suite (RCS) service, and provides RCS provision for the OEM application in response to an RCS service request of the OEM application. (provision) A provisioning module performing an operation, after the RCS provisioning operation is completed by the provisioning module, an RCS function connection request through a SIP (Session Initiation Protocol) transport adapter in response to an RCS service request of an OEM application and a SIP transport layer configured to control a session for the RCS function based on the RCS function.

According to the wireless communication device and the wireless communication method according to an embodiment of the present disclosure, by providing an interface for accessing the SIP transport layer, the RCS-based OEM application provides native level provisioning performance in a single registration environment. and RCS function conforming to each operator's standard, thereby supporting the integrated RCS service in OEM applications.

In addition, it is possible to provide improved quality of service (QoS) in signaling data, user data, or media data.

1 is a functional block diagram of a wireless communication device supporting an RCS service according to an embodiment of the present disclosure.
2 is a diagram illustrating an internal structure of a SIP stack of a modem processor and peripheral devices according to an embodiment of the present disclosure.
3 is a flowchart schematically illustrating a method of operating a SIP transport layer using a SIP stack according to an embodiment of the present disclosure.
4 is a flowchart illustrating a synchronization method for initialization of a SIP transport layer and IMS single registration according to an embodiment of the present disclosure.
5 is a flowchart illustrating a method of selecting a path through which a SIP message is transmitted and received according to an embodiment of the present disclosure.
6 is a schematic flowchart illustrating a method of performing IMS single registration.
7 is a flowchart illustrating a method of operating a SIP transport layer using a dedicated bearer after performing IMS single registration.
8 is a flowchart schematically illustrating a method of providing a bearer independent protocol (BIP) service in a SIM toolkit using a SIP transport layer according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

1 is a functional block diagram of a wireless communication device supporting an RCS service according to an embodiment of the present disclosure.

The wireless communication device 100 may be fixed or mobile, and may refer to any device capable of transmitting and receiving data and/or control information through wireless communication with a plurality of networks. For example, the wireless communication device 100 includes a terminal, a terminal equipment, a terminal device, a mobile station (MS), a mobile terminal (MT), a user terminal (UT), and an SS ( Subscribe Station), a wireless device, a handheld device, and the like.

Referring to FIG. 1 , the wireless communication device 100 may include an application processor 120 and a modem processor 140 .

The application processor 120 may include an RCS-based OEM application 122 and an RCS-based native application 124 . A native application means an app developed for use on a specific platform or device, and it is optimized for a device using a specific platform, so it is advantageous in accessing system resources and has the advantage of not limiting access to native services. In contrast, an original equipment manufacturer (OEM) application means an app developed to be downloaded and used regardless of platform or device, and access to native services is limited and can only be accessed through the platform standard API (application programming interface). . The OEM application 122 may have a session initiation protocol (SIP) stack therein.

The application processor 120 may include a native service module 126 and a SIP transport adapter 128 .

The native service module 126 may be a module that provides an application program interface (API) to an upper application level to implement an IMS function. For example, the OEM application 122 may be connected to the native service module 126 to support single registration, and through this connection, the OEM application may receive provisioning service support.

The provisioning service is a service related to the preparation to service the RCS function, and may include, as a non-limiting example, one of IMS Registration, GBA Authentication, Presence using Address book, User Capability Discovery, Contact List, and Auto-Configuration. have. In particular, the provisioning service may include a presence function related to user management capable of RCS. The presence function provides information contained in the SIP message header related to the presence according to the requirements of the operator, and error handling. Contents may be different.

The SIP transport adapter 128 is defined as a module that connects and manages the OEM application 122 and the SIP transport layer 144 when SIP signaling is used to control the SIP session. The SIP session may be a session for supporting the RCS function.

The modem processor 140 may include a SIP stack 142 and a SIP transport interface 148 .

The SIP stack 142 may be a module including the SIP transport layer 144 . The SIP transport layer 144 may handle transmission of a transaction message in the SIP stack 142 and may support functions related to syntax conversion, packet encryption, and tunneling for the SIP message. In some embodiments of the present disclosure, the SIP transport layer 144 of the modem processor may have a structure that cooperates with the SIP transaction layer of the OEM application 122 .

The SIP transport interface 148 may provide a path from the OEM application 122 to the SIP transport layer 144 so that the OEM application 122 can selectively open a session for the RCS function. That is, the SIP transport interface 148 allows the OEM application 122 to initiate SIP signaling for the RCS function by itself.

According to an embodiment, data transmitted through this path may include a SIP transaction layer message generated by the OEM application 122 . In addition, data transmitted through this path may include a session description protocol (SDP) body encoded as needed. The RCS function that the OEM application 122 wants to replace with this path is, as a non-limiting example, Standalone Message, Enriched call, Chatbot, Group-Chat, File Transfer using a base protocol such as SIP, MSRP, RTP, HTTP/HTTPS, etc. , may correspond to one of GBA Authentication.

In some embodiments of the present disclosure, the SIP transport adapter 128 of the application processor 120 and the Native SIP Stack 142 of the modem processor 140 are dual SIM dual standby supporting a multi stack. - It can work with either a SIM Dual-Standby: DSDS device or a Dual-SIM Dual-Active (DSDA) device. For multiple activated applications considering dual SIM, the SIP transport layer 144 can process SIP messages simultaneously and in parallel through unique classification of stack ID, call-ID, branch-value, etc. .

2 is a diagram illustrating an internal structure of a SIP stack of a modem processor and peripheral devices according to an embodiment of the present disclosure.

Specifically, the SIP stack 200 included in the modem processor includes a SIP transaction user layer 202, a SIP transaction layer 204, and a SIP transport layer 206. It may be a module including For example, the SIP-TransactionUser-Handler 146 defined as the sum of the SIP transaction user layer and the SIP transaction layer is interfaced with the application processor, and various requests interlocked with the modem in relation to the IMS network framework. ) can be dealt with. The SIP-TransactionUser-Handler 146 may include a small module (SIP API) 201 that connects the SIP message of the application, the SIP transaction user layer 202 and the SIP transaction layer 204, and the small module is the application's It can handle database reuse and validate messages according to operator requirements. The message may be transmitted transparently through the SIP transaction user layer 202 , the SIP transaction layer 204 , the SIP transport layer 206 and the TCP/IP layer 209 .

According to an embodiment of the present disclosure, as a result of IMS single registration to be described later, the encryption protocol between the server, system, and application operating over the network is SSL (secure sockets layers) or TLS (transport layer security) If it is determined whether or not it is recognized, the OEM application may be provided with an appropriate Secured IMS service by the library 208 inside the SIP transport layer.

In addition, when the SIP transport layer 206 detects that the newly opened session is related to the RCS service, the SIP transport layer 206 may transmit the message to the OEM application without modifying the downlink path.

The modem processor may include several devices around the SIP stack 200 .

Specifically, the modem processor may include a PDN Manager 210 for managing IMS packet data network (PDN) activation around the SIP stack 200 . For example, the PDN Manager 210 can distinguish a stack in a dual-SIM environment through PDN information passed through a message. A method using a capability-based setting table and a method using message ID history to select whether a received SIP message is a path from the OEM application to the SIP transport layer 206 in a multi-activated dual SIM environment All of these can be supported. To this end, the SIP transport layer 206 classifies the categories for messages delivered from the SIP transaction layer 204 (eg, creating a capability list), and the SIP message history (eg, call ID, transaction ID (branch value)) can be stored and managed.

The modem processor may also include a GBA controller 220 in charge of a Generic Bootstrapping Architecture (GBA) function around the SIP stack 200 . For GBA authentication, the authentication value through the SIM may be required when accessing the HTTP server in common for the application processor and the modem processor, and an API may be provided through the SIP transport adapter 128 to share the GBA authentication with OEM applications. According to an embodiment, the GBA controller 220 may be located in the application processor.

Additionally, the modem processor may include an XML configuration access protocol (XCAP) controller 230 around the SIP stack 200 .

The XCAP Controller 230 is an essential device in the IMS service and may be used to access the configuration server and additional services using the HTTP protocol.

3 is a flowchart schematically illustrating a method of operating a SIP transport layer using a SIP stack according to an embodiment of the present disclosure.

Specifically, FIG. 3 shows an application processor 120 including an OEM application 122 and a native service module 126 , a modem processor 140 including a SIP transaction user layer 202 and a SIP transport layer 206 . and a flow diagram 300 illustrating an example of operation of a 3GPP network 324 including a server 326 . Hereinafter, an operation method according to an embodiment using the SIP stack will be described.

The wireless communication device 100 including the application processor 120 and the modem processor 140 may communicate with the 3GPP network 324 . For example, the wireless communication device 100 is a non-limiting example of a 5th Generator (5G) system, a 5G New Radio (NR) system, a Long Term Evolution (LTE) system, a Code Division Multiple Access (CDMA) system, and a GSM system. It may communicate with the IMS-based 3GPP network 324 according to a (Global System for Mobile Communications) system, a Wireless Local Area Network (WLAN) system, or any other RAT. The 3GPP network 324 may include a server 326 that communicates with the wireless communication device 100 .

When an input for a user of the wireless communication device 100 to initiate an RCS service using the OEM application 122 is given to the wireless communication device 100 , the OEM application 122 natively generates the necessary information for initiating the RCS service. A request is made to the service module 126 (S302). As an example, matters necessary for RCS service initiation may include whether a multi-SIP stack is used. The native service module 126 that has received the request of the OEM application 122 performs IMS Single Registration while performing IMS single registration. As UE capability, the function required by the OEM application 122 and the native service module 126 are The function is reflected at the same time (S304).

The native service module 126 transmits the request for registration through the SIP transaction user layer 202 and the SIP transport layer 206 of the modem processor 140 , and normally from the server 326 of the 3GPP network 324 . A response indicating registration is received (S306).

The native service module 126 is ready to be used, so that the native application 328 can use the RCS service for its intended purpose of using the native service.

The native service module 126 shares SIP configuration parameter information with the OEM application 122 based on the performed IMS single registration (S310). The SIP configuration parameter information may include SIP header tag information to be used by the application-side SIP stack.

The native application 328 may open a session for the original purpose and exchange media data using a dedicated bearer 330 (S312).

As a result of IMS single registration, the OEM application 122 may similarly open a session and exchange media data using the dedicated bearer 330 (S314). In this case, the media data may be RCS media data for the RCS function.

The OEM application 122 may use the provisioning service through a separate RCS device API (S316). Also, unlike the conventional method described above, the OEM application 122 may directly control the session for the RCS function through SIP signaling through the SIP transport adapter and the SIP transport interface (S318). Thereafter, the router controller 130 adjusts the router table to access the open dedicated bearer (S320), and the OEM application 122 may exchange RCS media data with the server 326 through the dedicated bearer (S322). .

4 is a flowchart illustrating a synchronization method for initialization of a SIP transport layer and IMS single registration according to an embodiment of the present disclosure.

The wireless communication device 100 according to an embodiment of the present disclosure needs initialization for SIP-based SIP transmission at the time of first booting. Specifically, FIG. 4 shows that when the SIP stack of the OEM application 122 and the SIP stack of the modem processor 140 exist, the SIP stack of the modem processor 140 is initialized to the role of the native SIP stack and at the same time the OEM application 122 is It shows the process of synchronizing two SIP stacks with each other to perform IMS single registration with the SIP transaction layer in the SIP stack. Hereinafter, an operation method according to an embodiment of inducing IMS single registration will be described.

When the wireless communication device 100 is booted by the user, the OEM application 122 transmits parameters related to the category On/Off condition for each RCS function that the OEM application 122 wants to set to the native service module 126 . to perform (S402). The native service module 126, which has received parameters related to category On/Off conditions for each RCS function, maintains capability information through a capability operation, which is one of the provisioning services. Through this series of processes, the native service module 126 may retain both the information on the RCS function to be set by the OEM application 122 and the information on the RCS function performed by the native application 124 . Thereafter, the application processor 120 sets a default PDN and an IMS PDN. Here, the default PDN generally means an IP network allocated from the P-GW of the core for a service using the Internet network, and the IMS PDN means an IP network for using an IMS service such as HD Voice. If the application processor 120 succeeds in setting the PDN, the native service module 126 activates the set PDN (S404). According to an embodiment, the activated PDN may be a default PDN for Internet, an IMS PDN for single registration, or another PDN.

The native service module 126 transmits the capability information included in the parameter information received from the OEM application 122 together with the PDN setup related message to the SIP-TransactionUser-Handler 146 of the modem processor, and IMS Single Registration is requested (S406). Based on the received information, the modem processor 140 performs IMS single registration and at the same time the SIP message in the SIP transport layer 144 is a path transmitted from the OEM application 122 or a path transmitted from the native application 124 . You can create a table that determines cognition. As an embodiment, whether the SIP message is a path transmitted from the OEM application 122 or a path transmitted from the native application 124 may be divided into RCS functional units of the application. As another embodiment, even for the same RCS function, a path may be selected by classifying a forwarding path of the SIP message in real time. When the SIP message is transmitted from the OEM application 122 in the SIP transport layer 144 , it may be referred to as an App Path, and in the SIP transport layer 144 , the SIP message is transmitted from the native application 124 . In the case of , it may be referred to as a Native Path.

Table 1 shows an example of information on a combination of a 64-bit mask value for capability for each RCS function and a forwarding path of a SIP message for each function.

Field Length Description featureMap 10(Array of size 2) Map of clientId and featureBitmask
typedef struct
{
U8 clientId; // RCS_APP=1, NATIVE_APP=2
U64 featureBitMask;
}sitAimsfeatureMap;

In an embodiment of the present disclosure, the combination of the 64 bit mask value for the capability of each RCS function and the delivery path of the SIP message for each function can be informed by delivering the information as shown in [Table 1], and based on this, IMS Single Registration and The delivery route can be determined. For example, among RCS functions, Chatbot may be used as an App Path, and among RCS functions, it may be declared that an enriched call is used as a Native Path.

Table 2 shows an example of a method for classifying an RCS function according to the GSMA standard at the SIP message receiving side.

RCS function SIP OPTIONS Tag SIP Message Tag IM +g.3gpp.iariref ="urn%3Aurn-%3A3gpp-application.ims.iari.rcse.im" Standalone Messaging
SIP
MESSAGE (in case of Pager Mode CPM Standalone Messages)
· P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.oma.cpm.msg or urn:urn-7:3gpp-service.ims.icsi.oma.cpm.msg.group and not carrying content of the type “message/imdn+xml”; or
INVITE (in case of Large Message Mode CPM Standalone Messages)
· P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg or urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg.group Group Chat
SIP
· INVITE, SUBSCRIBE and REFER (in case of chat sessions)
· P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group Chatbot +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.gsma.rcs.extension" SIP INVITE
· Accept-Contact header field containing feature tag +g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.chatbot". FT +g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft" HTTP File Transfer
A Chat Message with application/vnd.gsma.rcs-ft-http+xml as the CPIM content-type property is sent in an MSRP session (identified as in 1-to-1 Chat and Group Chat). VoLTE (VoNR)
/ViLTE(ViNR) Call +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";
video IP Voice Call
SIP INVITE
· P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
· Accept-Contact and Contact header fields containing the feature tag +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel” and
· only audio media in SDP in 200 OK response
IP Video Call
SIP INVITE
· P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
· Accept-Contact and Contact header fields containing the feature tag +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel”
· Accept-Contact and Contact header fields containing the “video” capability indication and
· audio and video media in SDP in 200 OK response

Referring to Table 2, for example, when the SIP message receiving side checks the capability, it can be divided into Accept-Contact and Contact header included in SIP OPTIONS Tag, and in case of RCS function, P- included in SIP Message Tag It can be identified by the Asserted-Service field. Also, the SIP Message Tag may be, for example, INVITE or MESSAGE.

When SIP single registration is completed (S408), the native service module 126 transmits configuration parameters to the OEM application 122 to be used by the SIP stack of the OEM application 122 (S410).

When a situation occurs in which the SIP transmission profile of the OEM application is changed in an environment using multiple RCS applications, as in S402, the OEM application 122 performs the category On/Off condition for each RCS function that the OEM application 122 wants to set. An initialization process of transmitting related parameters to the native service module 126 is newly performed (S412). According to an embodiment, the situation in which the SIP transport profile of the OEM application is changed in an environment using multiple RCS applications is when the RCS function to be used in the OEM application is changed or when another OEM application is executed or the running OEM application is terminated. etc. may apply.

After the new initialization process is performed (S412), IMS Registration is executed again through the operations of S404-S410.

5 is a flowchart illustrating a method of selecting a path through which a SIP message is transmitted and received according to an embodiment of the present disclosure.

Specifically, FIG. 5A shows a case in which a SIP message is received from the SIP transport adapter 128 or a case in which a SIP message transmission request is received from the native service module 126 in the SIP transport layer 144, and according to a path A method of transmitting a SIP message to a server is described, and FIG. 5B shows that when a SIP message is received from the server, the received SIP message is selected from a path through the SIP transport adapter 128 or a path through the native service module 126 and how to transmit it.

In the embodiment of FIG. 5A , the SIP transport layer 144 may initialize to store a route for each category of the RCS function that the OEM application 122 intends to use.

When a SIP message is received (502) from the SIP transport adapter 128 at the SIP transport layer 144, the SIP transport layer 144 provides a route history (eg, call ID and transaction) for returning a response. ID (branch value)) and save the path as "APP-WAY" (504). Thereafter, the SIP transport layer 144 transmits the SIP message to the server 326 ( 512 ).

On the other hand, when the SIP transport layer 144 receives the SIP message transmission request from the native service module 126 (506), the SIP transaction layer 204 prepares to transmit the SIP message (508). At this time, the SIP transport layer 144 stores the path history (eg, call ID and transaction ID (branch value)) for returning a response, and stores the path as "NATIVE-WAY" (510). Thereafter, the SIP transport layer 144 transmits the SIP message to the server 326 ( 512 ).

According to an embodiment, the SIP transport layer 144 may set both "APP-WAY" and "NATIVE-WAY" routes for the case where the category of the RCS function to be used by the OEM application 122 is the same.

In the embodiment of FIG. 5B, upon receiving the SIP message from the server (514), the SIP transport layer 144 checks the P-Asserted-Service included in the SIP header to classify the category of the RCS function of the SIP message. (516).

By determining whether the SIP message transmission history (eg, call ID and transaction ID (branch value)) exists (518), if the history (eg, call ID and transaction ID (branch value)) exists, it is stored in the stored history. Accordingly, the SIP message is transmitted to the application processor 120 by selecting a path ( 520 ).

When the path according to the stored history is “APP-WAY” ( 522 ), the SIP transport layer 144 transmits a SIP message to the application processor 120 through the SIP transport adapter 128 ( 524 ).

Determining whether a SIP message transmission history (eg, call ID and transaction ID (branch value)) exists (518) so that the history (eg, call ID and transaction ID (branch value)) does not exist and the stored history If the path according to the method is "APP-WAY" ( 526 ), the SIP transport layer 144 transmits a SIP message to the application processor 120 through the SIP transport adapter 128 ( 524 ).

Determining whether a SIP message transmission history (eg, call ID and transaction ID (branch value)) exists (518) so that the history (eg, call ID and transaction ID (branch value)) does not exist and the stored history When the path according to 'APP-WAY' is not "APP-WAY", that is, "NATIVE-WAY", the SIP transport layer 144 transmits a SIP message to the application processor 120 through the native service module 126 ( 528).

According to an embodiment, the SIP transport layer 144 may set both "APP-WAY" and "NATIVE-WAY" routes for the case where the category of the RCS function to be used by the OEM application 122 is the same.

In this way, according to the embodiment of FIG. 5 , the modem processor 140 of the wireless communication device 100 uses the same RCS function at the same time in an environment using multiple RCS applications by first identifying a path with the SIP message transmission history. In case there is no history, it is determined as a newly received case, and a path can be selected based on a setting table according to the RCS function category.

6 is a schematic flowchart illustrating a method of performing VoLTE/RCS integrated IMS single registration.

Specifically, FIG. 6 is an IMS single registration performed after the initialization of the SIP transport layer of FIG. 4 for inducing IMS single registration and the synchronization method for IMS single registration. As a diagram illustrating an example of a method, the operation from a network point of view rather than an internal operation of the wireless communication device 100 will be described.

Referring to FIG. 6 , the wireless communication device 100 transmits a SIP registration message to a Home Subscriber Server (HSS) 620 through a call session control function (CSCF) 610 for IMS registration (S602). The IMS registration information included in the SIP registration message may include at least one of an International Mobile Subscriber Persistent Identity (IMPI) and an IP Multimedia Public identity (IMPU). The CSCF is a session control function block and may include a proxy call session control function (P-CSCF), a serving call session control function (S-CSCF), and an interrogating call session control function (I-CSCF). Here, the P-CSCF may correspond to an IMS service proxy server for each communication service provider.

The HSS 620 transmits a SIP 401 (Unauthorized) message to the wireless communication device 100 through the CSCF 610 in response to the registration request of the wireless communication device 100 . The wireless communication device 100 retransmits the SIP registration message including information necessary for the RCS service to the home subscriber server (HSS) 620 through a call session control function (CSCF) 610 ( S606 ). The HSS 620 transmits a SIP 200 OK message to the wireless communication device 100 through the CSCF 610 in response to the re-registration request of the wireless communication device 100, and the IMS single registration is completed.

Table 3 shows an example of a SIP registration message flow transmitted by the wireless communication device 100 in steps S602 and S608.

18:33:21.951 18:34:17.004053 ST1 SIP UL.Request REGISTER
18:33:22.706 18:34:17.756891 ST1 SIP DL.Response 401 Unauthorized
18:33:22.811 18:34:17.892237 ST1 SIP UL.Request REGISTER
18:33:23.533 18:34:18.598810 ST1 SIP DL.Response 200 OK
18:33:23.534 18:34:18.611841 ST1 SIP UL.Request SUBSCRIBE
18:33:23.877 18:34:18.942621 ST1 SIP DL.Response 200 OK
18:33:25.232 18:34:20.311396 ST1 SIP DL.Request NOTIFY
18:33:25.235 18:34:20.317743 ST1 SIP UL.Response 200 OK
18:33:26.683 18:34:21.737970 ST1 SIP UL.Request PUBLISH
18:33:26.935 18:34:22.016748 ST1 SIP DL.Response 200 OK

Table 4 shows an example of partial contents of the SIP registration message transmitted by the wireless communication device 100 in steps S602 and S608.

REGISTER sip:msg.pc.t-mobile.com SIP/2.0
From: <sip:310260123456789@ims.mnc260.mcc310.3gppnetwork.org>;tag=b3a8594f
To: <sip:310260123456789@ims.mnc260.mcc310.3gppnetwork.org>
Contact: <sip:310260123456789@[fc01:bbbb:cdcd:efe1::1]:49155>;audio;video;+g.3gpp.smsip;+g.3gpp.icsi-ref="urn%3Aurn-7% 3A3gpp-service.ims.icsi.mmtel,urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session,urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.msg, urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.largemsg,urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.filetransfer";+g.3gpp.iari-ref= "urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geopush,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geosms";reg-id=1;+sip.instance="<urn:gsma:imei:35069520-012395-0>"
Call-ID: 90166a13d1de4dc@fc01:bbbb:cdcd:efe1::1\

The SIP registration message is prepared according to the multipurpose internet mail extensions (MIME) type standard in ANSI (American national standards institute) text format and transmitted. Referring to Table 4, the header part of Contact in the content of the SIP registration message may mean a combination of RCS functions requested by the wireless communication device 100, according to an embodiment.

Table 5 shows an exemplary list of some of the values included in Contact among the contents of the SIP registration message.

Mobile Communication Device services Capability Tags AUDIO CALL
VIDEO CALL audio
video SMS +g.3gpp.smsip VoLTE FUNCTION +g.3gpp.cs-voice,
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel,
+g.gsma.callcomposer,
+g.3gpp.srvcc-alerting,
+g.3gpp.mid-call,
+g.3gpp.cs2ps-srvcc,
?? RCS FUNCTIONS
in +g.3gpp.icsi-ref +g.3gpp.icsi-ref=
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session,
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.msg,
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.largemsg,
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.filetransfer,
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.systemmsg'
3gpp-service.ims.icsi.oma.cpm.msg.group,
3gpp-service.ims.icsi.oma.cpm.largemsg.group,
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.botspam,
urn:urn-7:3gpp-service.ims.icsi.gsma.callcomposer,
urn%3Aurn-7%3A3gpp-service.ims.icsi.gsma.callunanswered,
urn%3Aurn-7%3A3gpp-service.ims.icsi.gsma.sharedmap,
urn%3Aurn-7%3A3gpp-service.ims.icsi.gsma.sharedsketch,
?? RCS FUNCTIONS
in +g.3gpp.iari-ref +g.3gpp.iari-ref=urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fthttp,
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.ftthumb,
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geopush,
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geosms
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.mnc000.mcc460.offlinemsg
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.chatbot
urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.chatbot.sa
urn%3Aurn-7%3A3gppapplication.ims.iari.rcs.ftsms
org.3gpp.urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.closedgroupchat,
?? IMEI +sip.instance="<urn:gsma:imei:35069520-012395-0>"

The SIP registration message transmitted by the wireless communication device 100 at S602 and S608 may include information related to capability as shown in Table 5 according to whether IMS single registration is supported.

7 is a flowchart illustrating a method of operating a SIP transport layer using a dedicated bearer after IMS single registration.

Specifically, FIG. 7 is a view showing a specific embodiment of FIG. 3 , and in the method of operating the SIP transport layer of FIG. 3 , an operation of connecting a network and a session using a dedicated bearer is described in detail.

When an input for a user of the wireless communication device 100 to initiate an RCS service using the OEM application 122 is given to the wireless communication device 100 , the OEM application 122 natively generates the necessary information for initiating the RCS service. An initialization process for requesting the service module 126 is performed (S702). In S702, for example, the initialization parameters transmitted by the OEM application 122 to the native service module 126 include a value of "RCS_FeatureSupport_t 64bit" including information on an RCS function that the OEM application 122 wants to use and an OEM application ( 122) issued ID information may be included. Specifically, the ID information issued by the OEM application 122 may be a universally unique identifier (UUID) or any type of ID information corresponding to a UUID.

After the initialization process, although not shown in FIG. 7 , the native service module 126 activates the PDN through the PDN Manager of the modem processor 140 for IMS single registration. In an embodiment, the native service module 126 may request PDN activation from a telephony data connection tracker (DCT) if the IMS PDN has not yet been activated after confirming that the state of the wireless communication device is LTE Camp On. . When the PDN is activated, for example, after recognizing that the IMS PDN is normally activated, IMS single registration is triggered. According to an embodiment, the activated PDN may be a default PDN for Internet, an IMS PDN for single registration, or another PDN.

The application processor 120 combines the information obtained in S702, for example, the items necessary for the OEM application 122 to initiate the RCS service, IMS PDN selection information, and the like, and sends a request for IMS single registration to the modem processor 140 transmit (S704). The process of performing IMS single registration has been described in detail with reference to FIG. 6, and thus will be omitted here. When the IMS single registration is completed, the OEM application 122 receives SIP configuration parameter information (S706). As an embodiment, the SIP configuration parameter information may include information received from the 3GPP network 324 as a result of IMS single registration. For example, the information received from the 3GPP network 324 may include synchronization information when operating in multiple SIP stacks.

The OEM application 122 requests session establishment in the form of a SIP INVITE message to use the RCS function (S708). In this case, the OEM application 122 may directly use the SIP transport layer 206 of the modem processor 140 . Although not shown in FIG. 7 , an operation of confirming RCS compatibility with a remote user connected through a server using a presence function may be preceded. Since the presence function corresponds to a provisioning service, it can be supported through a separate RCS device API.

The SIP transport layer 206 of the modem processor 140 transmits the SIP message to the server 326 in cooperation with the SIP transaction layer of the OEM application 122 (S710). The OEM application 122 receives information about a session for exchanging RCS function data (S712), and the server 326 establishes a dedicated bearer (S714). In case of IMS single registration, the IMS PDN may use multiple dedicated bearers for QoS support. The application processor 120 adjusts or sets IP packet routing characteristics through 5-tuple information including Source address/Source Port/Destination Address/Destination Port/Network type, and the modem processor 140 sends the dedicated bearer 330 to You can control the session based on it. When the OEM application 122 uses the SIP transport adapter to access the dedicated bearer 330 and transmits information corresponding to the dedicated bearer 330 to the router controller 130, TCP/IP that can be used in response thereto Receives a socket context ID. This allows the OEM application 122 to communicate with the network through the socket.

The OEM application 122 exchanges media data corresponding to the RCS function with the server 326 (S716).

When the media data exchange is terminated, a SIP signaling request and response for terminating the session are exchanged between the OEM application 122 and the server 326 (S718 and S720). At this time, the setup of the dedicated bearer 330 by the server 326 is terminated (S722).

When a separate SIP stack is used in different RCS applications, it may be considered as multiple registration. Specifically, multiple registration corresponds to a case where registration is performed individually without integrating VoLTE service and RCS service without single registration. In this case, the OEM application can operate as a general Internet network. and compatible in the structure of the present invention. For example, the OEM application may inform the native service module 126 of a single registration requirement excluding the RCS function that it wants to register separately, and the separately registered native service and the OEM application do not interfere with each other. does not That is, depending on the network situation, for example, when the IMS network cannot be used and only the Internet network can be used, under the condition that some functions cannot be integrated into a single registration, it is divided into multiple Registration is possible, and the present invention is considered unhindered under these conditions.

8 is a flowchart schematically illustrating a method of providing a bearer independent protocol (BIP) service in the SIM toolkit using the SIP transport layer 144 according to an embodiment of the present disclosure.

When there is a request for IMS SIP signaling from the SIM through the SIM-Toolkit 150 that supports the IMS-based protocol, the OEM application 122 establishes an IMS session to communicate with the network using the SIP transport layer 144. have. Specifically, referring to the embodiment of FIG. 8 , a universal integrated circuit card (UICC) transmits data in the form of an IP packet to the IMS network through a dedicated bearer ( S812 ), and when a response is received from the IMS network, the SIP transport The layer 144 may recognize that a response has been received by utilizing the "Call ID" and the "branch value", and returns the received response to the SIM-Toolkit 150 (S814).

Exemplary embodiments have been disclosed in the drawings and specification as described above. Although embodiments have been described using specific terms in the present specification, these are only used for the purpose of explaining the technical spirit of the present disclosure, and are not used to limit the meaning or the scope of the present disclosure described in the claims. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. Accordingly, the true technical protection scope of the present disclosure should be defined by the technical spirit of the appended claims.

Claims (10)

As a wireless communication method for supporting RCS (Rich Communication Suite) service,
performing an RCS provisioning operation for the OEM application through an IP multimedia subsystem (IMS) native service module in response to an RCS service request of the OEM application;
transmitting an RCS function connection request to a SIP transport layer through a SIP (session initiation protocol) transport adapter and a SIP transport interface when the RCS provisioning operation is completed;
controlling a session for an RCS function by a SIP transport layer based on the RCS function connection request; and
Including; exchanging RCS media data with the network through a dedicated bearer (dedicated bearer)
wireless communication method. According to claim 1,
The step of performing the RCS provisioning operation for the OEM application comprises:
Synchronizing the native SIP stack of the modem processor and the SIP stack of the application processor to enable IP Multimedia Subsystem (IMS) single registration;
wireless communication method. According to claim 1,
The RCS provisioning operation includes at least one of IMS Registration, GBA Authentication, Presence using Address book, User Capability Discovery, Contact List, and Auto-Configuration for the RCS function,
wireless communication method. According to claim 1,
The RCS function connection request includes data related to at least one of Standalone Message, Enriched call, Chatbot, Group-Chat, File Transfer, and GBA Authentication using SIP,
wireless communication method. According to claim 1,
The step of controlling the session for the RCS function,
determining whether a SIP message is forwarded from the IMS native service module or the SIP transport adapter according to the RCS function over a TCP/IP session;
wireless communication method. A wireless communication device comprising an application processor and a modem processor supporting a Rich Communication Suite (RCS) service, the wireless communication device comprising:
The application processor is
a SIP transport adapter configured to directly connect with a session initiation protocol (SIP) transport layer to support the RCS function of an OEM application; and
and an IMS (IP multimedia subsystem) native service module configured to perform an RCS provisioning operation for the OEM application,
The modem processor,
application processor interface;
SIP transaction layer and SIP transaction user layer for native provisioning operation and native service; and
a SIP transport layer configured to be connected to a SIP transport adapter of the application processor through a SIP transport interface;
wireless communication device. 7. The method of claim 6,
The modem processor,
A native SIP stack configured to synchronize with the SIP stack of the application processor to enable IMS (IP Multimedia Subsystem) single registration;
wireless communication device. 7. The method of claim 6,
The application processor is
configured to exchange media data according to the RCS function with the network through a dedicated bearer,
wireless communication device. 7. The method of claim 6,
The SIP transport layer of the modem processor,
and determine whether a SIP message is forwarded from the IMS native service module or the SIP transport adapter according to the RCS function over a TCP/IP session;
wireless communication device. A modem processor supporting RCS (Rich Communication Suite) services, comprising:
a provisioning module for performing an RCS provisioning operation for the OEM application in response to an RCS service request of the OEM application; and
After the RCS provisioning operation is completed by the provisioning module, an RCS function connection request is received through a session initiation protocol (SIP) transport adapter in response to an RCS service request of an OEM application, and based on the RCS function, the RCS function Including; SIP transport layer configured to control the session for the function;
modem processor.

Images