[go: up one dir, main page]

WO2025107198A1 - Informations de capacité associées à des canaux de données - Google Patents

Informations de capacité associées à des canaux de données Download PDF

Info

Publication number
WO2025107198A1
WO2025107198A1 PCT/CN2023/133385 CN2023133385W WO2025107198A1 WO 2025107198 A1 WO2025107198 A1 WO 2025107198A1 CN 2023133385 W CN2023133385 W CN 2023133385W WO 2025107198 A1 WO2025107198 A1 WO 2025107198A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
capability information
data channel
network device
sip message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/133385
Other languages
English (en)
Inventor
Xu Chen
Jiongxuan CHEN
Zhi Wang
Xiao Cheng DU
Fan Shan HU
Qiang Li
Wei Lin
Yu Fang TIAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Investment China Co Ltd
Nokia Technologies Oy
Original Assignee
Nokia Solutions and Networks Investment China Co Ltd
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions and Networks Investment China Co Ltd, Nokia Technologies Oy filed Critical Nokia Solutions and Networks Investment China Co Ltd
Priority to PCT/CN2023/133385 priority Critical patent/WO2025107198A1/fr
Publication of WO2025107198A1 publication Critical patent/WO2025107198A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • Various example embodiments relate to the field of communications and in particular, to a terminal device, network devices, methods, apparatuses and a computer readable storage medium for indicating capability information associated with at least one data channel.
  • the Internet protocol multimedia subsystem (IMS) Data Channel is an extension of the IMS solution, and is designed to support conversational multimedia applications that are transported over protocols other than RTP (e.g., voice, video, SMS defined in GSMA IR. 92, GSMA IR. 94, and GSMA NG. 114) .
  • SIP/SDP is used in addition to audio/video/real-time text media streams.
  • a Data Channel Multimedia Telephony Service for IMS (DCMTSI) client can establish Bootstrap Data Channel with Data Channel Signalling Function (DCSF) and using HTTP protocol to retrieve root application first.
  • DCSF Data Channel Signalling Function
  • an Application Data Channel can be established with DCMF or another DCMTSI client.
  • the IMS Data Channel integrates internet connectivity and IMS connectivity, enhancing the ability of IMS to establish real-time communication between two endpoints for exchanging any form of data information in an action-oriented and multi-modal way.
  • example embodiments of the present disclosure provide a solution for indicating capability information associated with at least one data channel, especially for supporting data channel capability discovery and synchronization among participants of an IMS DC session.
  • a terminal device comprising at least one processor and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to transmit, to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • a first network device comprises at least one processor and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first network device to receive, from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel; and transmit, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • a second network device comprising at least one processor and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the second network device to receive, from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and construct, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • URL uniform resource locator
  • the third network device comprises at least one processor and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the third network device to receive, from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; generate a sixth SIP message by removing the header field from the first SIP message; and transmit the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • a method comprises: transmitting, at a terminal device and to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • a method comprises: receiving, at a first network device and from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel; and transmitting, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • a method comprises: receiving, at a second network device and from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and constructing, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • a uniform resource locator URL
  • a method comprises: receiving, at a third network device and from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; generating a sixth SIP message by removing the header field from the first SIP message; and transmitting the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • an apparatus comprising means for transmitting, at a terminal device and to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • an apparatus comprising means for receiving, at a first network device and from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel; and means for transmitting, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • an apparatus comprising means for receiving, at a second network device and from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and means for constructing, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • a uniform resource locator URL
  • an apparatus comprising means for receiving, at a third network device and from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; means for generating a sixth SIP message by removing the header field from the first SIP message; and means for transmitting the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above fifth to eighth aspect.
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: transmit, to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel; and transmit, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and construct, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • a uniform resource locator URL
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; generate a sixth SIP message by removing the header field from the first SIP message; and transmit the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • a terminal device comprising transmitting circuitry configured to transmit, to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • the first network device comprises receiving circuitry configured to receive, from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel; and transmitting circuitry configured to transmit, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • a second network device comprises receiving circuitry configured to receive, from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and constructing circuitry configured to construct, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • a uniform resource locator URL
  • a third network device comprises receiving circuitry configured to receive, from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; generating circuitry configured to generate a sixth SIP message by removing the header field from the first SIP message; and transmitting circuitry configured to transmit the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • Fig. 1 illustrates an example communication network in which embodiments of the present disclosure may be implemented
  • Fig. 2 illustrates a flowchart illustrating a process for capability discovery and synchronization according to some embodiments of the present disclosure
  • Fig. 3A illustrates a flowchart illustrating a process for capability discovery and synchronization according to some other embodiments of the present disclosure
  • Fig. 3B illustrates a flowchart illustrating a process for capability discovery and synchronization according to some further embodiments of the present disclosure
  • Fig. 4 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure
  • Fig. 5 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure
  • Fig. 6 illustrates a flowchart of a method implemented at a network device according to some other embodiments of the present disclosure
  • Fig. 7 illustrates a flowchart of a method implemented at a network device according to some further embodiments of the present disclosure
  • Fig. 8 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure.
  • Fig. 9 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • suitable generation communication protocols including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the a
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • BS base station
  • AP access point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • NR NB also referred to as a gNB
  • RRU Remote Radio Unit
  • RH radio header
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • the IMS Data Channel enhances the user experience by providing a smoother and more seamless experience for multimedia services. Moreover, the IMS Data Channel brings increased revenue and cost savings.
  • a solution for IMS Data Channel defined in 3GPP TS 26.114 and GSMA NG. 134, requires the establishment of a Bootstrap Data Channel first to provide a list of data channel applications. The list can be used in an IMS session between DCMTSI clients (e.g. a UE-1 and a UE-2) or between a DCMTSI client and a DCSF.
  • the DCSF is defined in TS 23.228 AC. 2.2.1. In TS 23.228 AC. 2.2.1, a network function for data channel management signalling, Data Channel Signalling Function (DCSF) , is specified.
  • DCSF Data Channel Signalling Function
  • the DCMTSI client is defined in TS 26.114, for example, in TS 26.114 version 16.6.1 Release 16, it is defined as below: DCMTSI client: a data channel capable MTSI client supporting data channel media as defined in clause 6.2.10.
  • DCMTSI client a data channel capable MTSI client supporting data channel media as defined in clause 6.2.10.
  • the bearer path is a connection between the UE and the DCMF to transfer data generated by a data channel (DC) application.
  • the SDP negotiation refers to SDP offer/answer exchanges (see RFC 3264) .
  • the DCMF may provide the media resource management and forwarding of data channel media traffic.
  • the usage of certain data channel application e.g., AR, MR, VR
  • the usage of certain data channel application depends on the detailed capabilities of both DCMTSI clients and that detailed capabilities would be relative to hardware condition, network condition, etc.
  • the capability of the DCMTSI client herein may refer to a capability associated with the data channel, i.e. a data channel (DC) capability, or referred to as an IMS DC capability.
  • DC data channel
  • IMS DC capability a capability associated with the data channel
  • the solution defined in GSMA NG. 134 and 3GPP TR 27.300 only provides a high-level capability discovery, that is, either “support IMS DC” or “not support IMS DC” is provided by the DCMTSI client.
  • This high-level capability discovery procedure is reflected in 3GPP TS 24.229 as summarized below:
  • Home network informs the DCMTSI client its capability of supporting IMS DC with a "+g. 3gpp. webrtc-datachannel” parameter in Feature-Caps header in the 200 OK response to REGISTER request.
  • Solution #5 in 3GPP TR 27.200 provides three options as listed below for the detailed capabilities discovery of DCMTSI clients but each has limitation in usage.
  • Option 1 proposes to use SIP REGISTER request to include the detailed capabilities and report the capabilities to the home IMS AS/DCSF via 3rd party registration.
  • Option 2 proposes to report the capabilities to DCSF by sending data channel application request via bootstrap data channel.
  • Option 3 proposes to report the capabilities to DCSF in bootstrap data channel request and carry the same in SIP INVITE/re-INVITE request.
  • Option 1 can only report the details capabilities to home IMS AS/DCSF, it cannot satisfy the need exchange the capabilities info among participants in one IMS DC session to figure out common DC application can be supported and downloaded.
  • Option 2 can only report the details capabilities to the served DCSF.
  • Option 1 So, it has the same limitation as Option 1. Furthermore, it’s transparent to IMS network. IMS has no influence on capability discovery per IMS local policy means lost revenue generation opportunity related to that. Option 3 also asks to report the details capabilities in bootstrap data channel request thus has the same limitation as Option 1. It adds INVITE/re-INVITE that carry the same capabilities but no specification on how to do (e.g., via SIP or SDP or other methods) and only consider the P2A2P scenario (Person-to-Application and Application-to-Person) (i.e., “both UEs use the same Data Channel Server” ) .
  • P2A2P scenario Person-to-Application and Application-to-Person
  • INVITE is heavy weight solution in IMS back-to-back user agent (B2BUA) network element that will result into more interaction between IMS signalling plane (e.g., P-CSCF) and IMS media plane (e.g., AGW) . That is unnecessary after bootstrap data channel has been established since the data channel application data payload shall be agnostic to IMS media plane.
  • IMS signalling plane e.g., P-CSCF
  • IMS media plane e.g., AGW
  • Using two paths to delivery capabilities info introduces potential synchronization issue between SIP signalling request and bootstrap data channel request. In addition, it doesn’t meet the needs of timely discovery or synchronization the details capability update of the DCMTSI client before establishment of bootstrap data channel.
  • the solutions above are either too high-level (e.g. the DCMTSI client only provides a high-level capability) to determine which kind of data channel applications are applicable to a DCMTSI client, or has the above limitation (s) in usage.
  • the mechanism to ensure that DCMTSI clients served by different DCSF participating in one IMS DC session can invoke a common data channel application is missing in the solutions above.
  • P2P person to person
  • both parties will download data channel applications from the DCSF/DCMF in their respective networks.
  • the data channel application available to the caller may not be available to the callee.
  • the IMS network it is necessary for the IMS network to be aware of the specific DC capabilities that are supported by the DCMTSI client (e.g. a UE) .
  • the capability of the DCMTSI client indicated by feature tag are static.
  • the 5G and IMS DC service is inherently flexible and environmentally aware.
  • the capabilities of DCMTSI clients could be dynamic and change depending on various factors such as type of access network, battery capacity, roaming condition, geographical location, accessories plug-in/plug out, etc.
  • the DCMTSI client may gain a VR capability (an example of a plurality of IMS DC capabilities) while plug-in an accessory or lose the IMS DC capability while fallback to 3G network during one in-progress IMS DC session. Therefore, timely discovery the capability changes and synchronization among participants of IMS DC session is required to provide users with the best experience.
  • Fig. 1 illustrates an example communication system (or referred to as communication network) 100 in which embodiments of the present disclosure may be implemented.
  • the system 100 includes a plurality of terminal devices, such as a terminal device 110 and a terminal device 120.
  • the system 100 may further include a plurality of network devices, in some examples, the plurality of network devices may comprise network device (s) in an Internet protocol multimedia system (IMS) 170.
  • Network devices 140, 150 and 160 are shown as examples of network devices in the IMS 170.
  • the network device 150 may be an IMS application server (AS) .
  • AS IMS application server
  • the network device 140 may be a proxy-call session control function (P-CSCF) .
  • the network device 150 may communicate with other network devices in the IMS 170, for example, the network device 150 may transmit information of the terminal devices 110, 120 to the network device 160.
  • the network device 160 may be a data channel signaling function (DCSF) .
  • the one or more network devices may further comprise one or more access network devices, as shown in Fig. 1, an access network device 130 is shown as an example.
  • the terminal devices 110, 120 may communicate with the network device (s) of the IMS 170 via the access network device 140.
  • the system 100 may include any suitable number of network devices and terminal devices adapted for implementing embodiments of the present disclosure.
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • MIMO Multiple-Input Multiple-Output
  • OFDM Orthogonal Frequency Division Multiple
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM
  • FIG. 2 shows a process 200 for capability discovery and synchronization according to some embodiments of the present disclosure.
  • a terminal device 210, a terminal device 220, a network device 230, a network device 240 and a network device 250 are shown in the process 200.
  • the terminal device 210 may be referred to as a first terminal device 210
  • the terminal device 220 may be referred to as a second terminal device 220.
  • the network device 230 may be referred to as a first network device 230, and in some examples it may be an Internet protocol multimedia system (IMS) application server (AS) .
  • IMS Internet protocol multimedia system
  • AS Internet protocol multimedia system
  • the network device 240 may be referred to as a second network device 240, and in some examples it may be a data channel signaling function (DCSF) .
  • the network device 250 may be referred to as a third network device 250, and in some examples it may be a proxy-call session control function (P-CSCF) .
  • P-CSCF proxy-call session control function
  • one of the terminal devices 210, 220 may the terminal device 110, and the other one of the terminal devices 210, 220 may the terminal device 120.
  • the network device 230 may be the same as the network device 150
  • the network device 240 may be the same as the network device 160
  • the network device 250 may be the same as the network device 140.
  • one of the terminal devices 210, 220 may be as a caller device (referred to as a caller for short)
  • other one may be as a callee device ( (referred to as a callee for short) in an IMS DC session.
  • the terminal devices 210, 220 may also be referred to as DCMTSI clients.
  • the IMS AS at an originating network (the network to which an originator of a telecommunication message is proximately connected to) and the IMS AS at a terminating network (the network to which a receiver of a telecommunication message is proximately connected to) may be different.
  • the originating network and the terminating network use one IMS AS as an example.
  • the terminal device 210 may transmit (201) , to the network device 230 (i.e. the first network device 230) , a session initiation protocol (SIP) message 202 comprising a header field indicating capability information 204 of the terminal device 210.
  • the SIP message 202 may be referred to as the first SIP message 202.
  • the header field comprised in the SIP message 202 may be referred to a first header field.
  • An example of the header field is “P-DC-Cap” , and it is a created new SIP header which is used to carry DCMTSI client’s real-time capability within SIP request/response messages.
  • the new SIP header carrying caller’s real-time capabilities may go through originating IMS AS/DCSF then to terminating IMS AS/DCSF.
  • the new SIP header carrying callee’s real-time capabilities will go through terminating IMS AS/DCSF then to originating IMS AS/DCSF. It may be removed by Session Border Controller (SBC) towards untrusted domain (e.g., towards DCMTSI client) for privacy consideration, the SBC may act as a P-CSCF in some embodiments. Consequently, each IMS AS/DCSF will be aware of the real-time capabilities of all participants in an IMS DC session. The details will be further described in subsequent steps below.
  • SBC Session Border Controller
  • the capability information 204 of the first terminal device 210 may be referred to as first capability information 204.
  • the capability information 204 is associated with at least one data channel, that is, the capability information 204 is associated with capability (ies) of supporting data channel (DC) of the terminal device 210.
  • the capability information 204 comprises a set of capabilities (referred to as a first set of capabilities) associated with at least one data channel.
  • the first set of capabilities may be indicated by a set of capability tags comprised in the header field.
  • the capability information 204 comprises an indicator that the terminal device 210 has no capability associated with at least one data channel.
  • the indicator may be provided by an empty header field without a capability tag.
  • P-DC-Cap: indicates that the terminal device 210 has no capability associated with at least one data channel.
  • the first SIP message 202 may be transmitted to the network device 230 via a proxy-call session control function (P-CSCF) , and the P-CSCF may be referred to as a first P-CSCF (not shown in Fig. 2) .
  • P-CSCF proxy-call session control function
  • the first P-CSCF receives the first SIP message 202 from the first terminal device 210, and transmits the SIP message 202 to the network device 230 (i.e. the first network device 230) .
  • the first network device 230 receives (203) from the terminal device 210, the session initiation protocol (SIP) message 202.
  • the first network device 230 may receive the SIP message 202 from the terminal device 210 via a P-CSCF (e.g. the first P-CSCF) .
  • the first network device 230 may transmit a response to the SIP message 202 to the terminal device 210.
  • the first network device 230 may transmit (205) , to the second network device 240, the capability information 204 of the terminal device 210 (i.e. the first terminal device 210) .
  • the first network device 230 may transmit the capability information 204 by transmitting a Nimsas_SessionEventControl_Notify request to the second network device 240, and the Nimsas_SessionEventControl_Notify request comprises the capability information 204.
  • the second network device 240 may transmit a response (e.g. a Nimsas_SessionEventControl_Notify response) to the Nimsas_SessionEventControl_Notify request to the first network device 230.
  • the second network device 240 may be a first data channel signaling function (DCSF) serving the first terminal device 210.
  • the first network device 230 may further transmit, to a second DCSF (not shown in Fig.
  • the first network device 230 may further transmit an identity of the first terminal device 210.
  • An example of the identity may be an Internet protocol multimedia public identity (IMPU) .
  • the first network device 230 may transmit the identity (e.g. the IMPU) of the first terminal device 210 to the first DCSF and/or the second DCSF.
  • the first DCSF i.e. the second network device 240
  • the first DCSF may receive from the first network device 230, the identity of the first terminal device 210 and/or the identity of the second terminal device 220.
  • the second network device 240 receives (207) the capability information 204 of the terminal device 210 served by the second network device 240, and may construct (209) , based on the capability information 204, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device 210 (i.e. the first terminal device 210) .
  • a uniform resource locator URL
  • the details of the step of constructing the URL will be further described below.
  • the first network device 230 may transmit (211) the SIP message 202 (i.e., the first SIP message 202) to the third network device 250.
  • the third network device 250 may be associated with the second terminal device 220, for example the third network device 250 may be a P-CSCF associated with the second terminal device 220.
  • the third network device 250 receives (213) the first SIP message 202, and generates (215) a SIP message 206 (may be referred to as a sixth SIP message 206) by removing the header field from the first SIP message 202. Then the third network device 250 may transmit (217) the sixth SIP message 206 to the second terminal device 220.
  • the second terminal device 220 receives (219) the sixth SIP message 206, and then may transmit, to the third network device 250, a SIP message (referred to as a fourth SIP message) comprising a second header field indicating second capability information of the second terminal device 220.
  • the second capability information is associated with at least one data channel.
  • the first SIP message 202 is a SIP request (referred to as a first SIP request) for initiating an IMS data channel session between the first terminal device 210 and the second terminal device 220.
  • the SIP request for initiating the IMS data channel session may be a SIP INVITE request.
  • the fourth SIP message is a response to the first SIP request, e.g. an 18x message with a P-DC-Cap header.
  • the sixth SIP message 206 may be a SIP INVITE request without the “P-DC-Cap” header.
  • the first SIP message 202 is a response to the fourth SIP message, e.g. an 18x message with a P-DC-Cap header.
  • the fourth SIP message is a SIP request (referred to as a second SIP request) for initiating the IMS data channel session, e.g. a SIP INVITE request with a “P-DC-Cap” header.
  • the sixth SIP message 206 may be an 18x message without the “P-DC-Cap” header.
  • the third network device 250 receives the fourth SIP message from the second terminal device 220) .
  • the third network device 250 may transmit, to the first network device 230, the second capability information.
  • the third network device 250 may transmit, to first network device 230, the second capability information by transmitting the fourth SIP message to the first network device 230.
  • the first network device 230 receives the fourth SIP message from the second terminal device 220.
  • the first network device 230 may transmit the second capability information to the second network device (e.g. the first DCSF) and/or the second DCSF.
  • the second network device 240 may receive, from the first network device 230, the second capability information of the second terminal device 220.
  • the second terminal device 220 may be a terminal device participating an IMS data channel session with the first terminal device 210.
  • the first network device 230 may also transmit an identity of the second terminal device 220 to the first DCSF and/or the second DCSF.
  • the DCSF (s) such as the first DCSF and/or the second DCSF, may obtain capability information from both the first terminal device 210 and the second terminal device 220.
  • the second network device 240 may construct the URL based on the capability information 204. Specifically, if the first capability information 204 and the second capability information have at least one common capability, the second network device 240 may construct the URL based on the at least one common capability. If the first capability information 204 and the second capability information have no common capability, the second network device 240 may construct the URL based on the set of data channel applications configured by the first network device 230. If at least one of the first capability information or the second capability information comprises an indicator indicating that the corresponding terminal device has no capability associated with at least one data channel, the second network device 240 may construct the URL based on the set of data channel applications configured by the first network device 230. The indicator comprised in the first capability information 204 indicates that the first terminal device 210 has no capability associated with at least one data channel, and the indicator comprised in the second capability information indicates that the second terminal device 220 has no capability associated with at least one data channel.
  • the data channel application may be initiated by the network (e.g., the first network device 230)
  • the second network device 240 may only utilize the received capability information of one participant (for example the first terminal device 210) as input to construct a URL that will be provided to DCMF (in some examples, Media Resource Function (MRF) may be used to implement a function of the DCMF) to allow for the downloading of a graphical user interface that contains data channel applications matching the capabilities of the first terminal device 210. Therefore, constructing the URL based on the capability information 204 means constructing the URL based capability information of one terminal device (e.g. the first terminal device) .
  • a caller and a callee are served by different DCSFs in different network.
  • the second network device 220 may construct the URL based on the first capability information 204 of the first terminal device 210 and second capability information of the second terminal device 220.
  • the second capability information indicates that the second terminal device 220 has a third set of capabilities associated with at least one data channel.
  • the second network device 240 constructs the URL based on capability information of both terminal devices (e.g. the caller and the callee) .
  • the second network device 240 may construct the URL based on the at least one common capability of the first terminal device 210 and the second terminal device 220.
  • the terminal device 210 does not indicate its capability information, then the URL may be constructed based on the capability of the network, for example, the first network device 230 determine a set of data channel applications for constructing the URL. Alternatively, there is no common capability between the first capability information 204 and the second capability information, then the URL may also be constructed based on the set of data channel applications configured by the network. In such examples above, the second network device 220 may construct the URL based on a set of data channel applications configured by the first network device 230.
  • the terminal device may establish a bootstrap data channel with a data channel media function (DCMF) for obtaining a data channel application list for the terminal device 210.
  • DCMF data channel media function
  • the data channel application list is based on the first capability information of the first terminal device 210.
  • the data channel application list is based on the first capability information of the first terminal device 210.
  • the data channel application list is based on the first capability information of the first terminal device 210 and the second capability information of the second terminal device 220, as mentioned in the P2P scenario above, the data channel application list is based on capability information of both the first terminal device 210 and the second terminal device 220, specifically, the data channel application list is based on common capability information of the both terminal devices.
  • the terminal device 210 may transmit the first SIP message 202 comprising a header field indicating (e.g.
  • the network e.g., the first network device, may use a default data channel application list comprising a set of data channel applications configured by the network device.
  • the second terminal device 220 may transmit, to the third network device 250, a fourth SIP message comprising a second header field indicating second capability information of the second terminal device 220.
  • the fourth SIP message is transmitted, via some devices, such as the first network device 230, the first P-CSCF (not shown in Fig. 2) associated with the first terminal device 210, to the first terminal device 210.
  • the SIP message received (e.g. via the first P-CSCF) by the first terminal device 210 is a SIP message (referred to as a second SIP message) without the second header field.
  • the first P-CSCF may remove the second header field from the fourth SIP message to obtain the second SIP message, and then transmit the second SIP message to the first terminal device 210.
  • the first terminal device 210 may receive, from the network device 230, the second SIP message without the second header field.
  • the first SIP message 202 is a first SIP request for initiating the IMS data channel session, and the second SIP message is determined based on a response to the first SIP request, specifically, the second SIP message is generated by removing a header field from the response to the first SIP request.
  • the first SIP message 202 is a response to the second SIP message, and the second SIP message is determined based on a second SIP request for initiating the IMS data channel session, specifically, the second SIP message is generated by removing a header field from the second SIP request.
  • the SIP message 202 (i.e. the first SIP message 202) is used for updating previous capability information of the terminal device 210.
  • the first SIP message 202 may be a SIP INFO request.
  • the capability information 204 comprises the first set of capabilities
  • a second set of capabilities of the terminal device 210 indicated by the previous capability information may be updated based on the first set of capabilities.
  • the capability information 204 indicating a set of updated capabilities of the terminal device 210.
  • the second set of capabilities may be terminated.
  • the second set of capabilities of the terminal device 210 being terminated means that the terminal device 210 loses the second set of capabilities.
  • the terminal device 210 may further terminate unavailable data channel application associated with the terminal device 210 to release at least one media resource of the data channel application.
  • the second network device 240 may terminate unavailable data channel application associated with the terminal device 210 to release at least one media resource of the data channel application. That is, terminating the unavailable data channel application may be performed by the terminal device 210 and/or the second network device 240.
  • the first network device 230 may transmit, to the terminal device 210, a SIP message (referred to as a third SIP message) for informing the terminal device 210 to obtain a data channel application list for the terminal device.
  • the third SIP message may be a SIP REFER request. If the SIP message 202 (i.e. the first SIP message 202) is used for updating previous capability information of the terminal device 210, the third SIP message is for informing the terminal device 210 to obtain an updated data channel application list.
  • the terminal device 210 receives, from the network device 230, the third SIP message, and transmits a request (e.g.
  • the terminal device 210 may further transmit, to the network device 230, a response to the third SIP message.
  • the third SIP message may be received from the network device 230 via the P-CSCF (e.g. the first P-CSCF) .
  • the terminal device 210 may transmit to the first network device 230, and the first network device may receive from the terminal device 210, a response to the third SIP message.
  • the first network device 230 may also transmit, to the second terminal device 220, a fifth SIP message for informing the second terminal device 220 to obtain a data channel application list for the second terminal device 220. If the SIP message 202 (i.e. the first SIP message 202) is used for updating previous capability information of the terminal device 210, the fifth SIP message is for informing the terminal device 220 to obtain an updated data channel application list.
  • the second terminal device 220 may transmit to the first network device 230, and the first network device may receive from the second terminal device 220, a response to the fifth SIP message.
  • An example of the third network device 250 may be a second P-CSCF (different from the first P-CSCF above) .
  • the fifth SIP message may be transmitted to the terminal device via the third network device 250, specifically, the third network device 250 receives the fifth SIP message from the first network device 230, and transmits the fifth SIP message to the second terminal device 220.
  • the third SIP message may also be transmitted to the first terminal device 210 via a P-CSCF, for example, via the first P-CSCF.
  • the UE may be an example of the first terminal device 210 or the second terminal device 220. As an example, the UE may be described as the first terminal device 210 below.
  • IMS AS may be an example of the first network device 230
  • DCSF may be an example of the second network device (the first DCSF) or the second DCSF.
  • Table 1 summarizes the technical effects of the solution in some embodiments on the UE, the IMS AS and the DCSF in typically scenarios that to ensure detailed data channel capability discovery and synchronization among participants (e.g. the UEs, etc. ) of IMS DC session.
  • the step 1 shows an example in which the SIP message 202 is for initiating the IMS data channel session, and the SIP message 202 comprises the first set of capabilities.
  • the case 1 in step 1 shows an example in which a second set of capabilities of the terminal device 210 indicated by the previous capability information is updated based on the first set of capabilities.
  • the case 2 in step 1 shows an example in which the second set of capabilities of the terminal device 210 is terminated.
  • the step 1 shows an example in which the SIP message 202 is for initiating the IMS data channel session, and the SIP message 202 comprises an indicator that the terminal device 210 has no capability associated with at least one data channel.
  • the step 1 shows an example in which the terminal device 210 having no capability is updated based on the first set of capabilities.
  • Fig. 3A illustrates a flowchart illustrating a process 300-1 for capability discovery and synchronization according to some other embodiments of the present disclosure.
  • the process 300-1 may be applied to IMS DC P2P (person to person) scenario. To simplify the presentation, irrelevant signaling steps are omitted from the process 300-1. In addition, some network elements (e.g., I-CSCF/S-CSCF) that not impacted by this solution of the process 300-1 are also omitted.
  • the process 300-1 and the process 300-2 below are based on TS 23.228 AC. 7.2.1.
  • the process 300-1 may also be applied to an IMS DC P2A2P scenario, in which the DCSF-1 340 and DCSF-2 350 below may be same DCSF.
  • a UE-1 310, a UE-2 320, an IMS AS 330, a DCSF-1 340, a DCSF-2 350, a P-CSCF-1 360 and a P-CSCF-2 370 are involved.
  • the UE-1 310 and UE-2 320 may be as DCMTSI clients, and may be examples of terminal devices (the first terminal device 210 and the second terminal device 220) .
  • the IMS AS 330 may be an example of the first network device 210.
  • the DCSF-1 340 or the DCSF-2 350 may be an example of the second network device 220.
  • the P-CSCF-1 360 or the P-CSCF-2 370 may be an example of the third network device 250.
  • the UE-1 310 is an example of the first terminal device 210
  • the DCSF-1 340 is an example of the second network device 240
  • the P-CSCF-2 370 is an example of the third network device 250
  • the UE-2 320 is an example of the second terminal device 220.
  • the UE-2 320 is an example of the first terminal device 210
  • the DCSF-2 350 is an example of the second network device 240
  • the P-CSCF-1 360 is an example of the third network device 250
  • the UE-1 310 is an example of the second terminal device 220.
  • the UE-1 310 transmits, to the P-CSCF-1 360, a SIP message comprising a header field indicating capability information of the UE-1 310.
  • the SIP message may be a SIP INVITE request.
  • the capability information may comprise a header field.
  • the header field may be a P-DC-Cap header, and the P-DC-Cap header contains capability information of the UE-1 310.
  • the capability information is associated with at least one data channel (DC) , and may be referred to as DC capability information.
  • the capability information indicates a set of capabilities, such as augmented reality and positioning capabilities (shown as AR&Pos) .
  • AR and Pos may be examples of the capability tags.
  • One capability tag may indicate one capability of a UE.
  • the P-CSCF-1 360 may be as an originating network.
  • step 303 the P-CSCF-1 360 transmits the SIP INVITE request with the P-DC-Cap header to the IMS AS 330.
  • the IMS AS 330 may transmit, to the DCSF-1 340, the capability information of the UE-1 310.
  • the IMS AS 330 may transmit a Nimsas_SessionEventControl_Notify request to the DCSF-1 340, and the Nimsas_SessionEventControl_Notify request comprises the capability information of the UE-1 310.
  • the Nimsas_SessionEventControl_Notify request may further comprise user information of the UE-1 310, for example, an Internet protocol multimedia public identity (IMPU) of the UE-1 310.
  • the IMPU is an example of the identity of the UE-1 310.
  • the DCSF-1 340 may transmit, to the IMS AS 330, a response to the Nimsas_SessionEventControl_Notify request.
  • This response may be referred to as Nimsas_SessionEventControl_Notify response.
  • the IMS AS 330 may transmit the capability information of the UE-1 310 to the DCSF-2 350, for example, the IMS AS 330 may transmit the Nimsas_SessionEventControl_Notify request with the user information and the capability information of the UE-1 310.
  • the DCSF-2 350 may transmit a Nimsas_SessionEventControl_Notify response to the IMS AS 330.
  • the IMS AS 330 may transmit, to the P-CSCF-2 370, the SIP message comprising the header field indicating capability information of the UE-1 310, for example, as shown in Fig. 3A, the IMS AS 330 transmits the SIP INVITE request with the P-DC-Cap header “P-DC-Cap: AR, Pos” to the P-CSCF-2 370.
  • the IMS AS 330 notifies the DCSFs the call event by sending the Nimsas_SessionEventControl_Notify request to both the DCSF-1 340 serving the UE-1 310 and the DCSF-2 350 serving the UE-2 320. Further, the IMS AS 330 provides information such as the IMPU and the capability information of UE-1 310 to both DCSFs (i.e. the DCSF-1 340 and the DCSF-2 350) .
  • the P-CSCF-2 370 may transmit, to the UE-2 320, the SIP message (e.g. the SIP INVITE request with the P-DC-Cap header) received from the IMS AS 330.
  • the P-CSCF-2 370 may generate a further SIP message by removing the header field from the SIP message received from the IMS AS 330, in other words, prior to transmitting the SIP message received from the IMS AS 330, the P-CSCF-2 370 may remove the header field (e.g. the P-DC-Cap header) from the SIP message received from the IMS AS 330.
  • the P-CSCF-2 370 may transmit, to the UE-2 320, a SIP INVITE request without the P-DC-Cap header.
  • the P-CSCF-2 370 may be as a terminating network. Based on the steps 309 and 311 above, the IMS AS 330 sends the SIP INVITE request to the UE-2 320 through the terminating network. The P-CSCF-2 370 may, based on local policy and for the cause of privacy consideration, remove the P-DC-Cap header.
  • the UE-2 320 may transmit, to the P-CSCF-2 370, a SIP message (different from a SIP message transmitted by the UE-1 310) comprising a header field indicating capability information of the UE-2 320.
  • the SIP message transmitted by the UE-2 320 is a response to the SIP message transmitted by the UE-1 310, and in some examples, the response to the SIP message transmitted by the UE-1 310 may be a 18x message.
  • the UE-2 320 may transmit a 18x message with a P-DC-Cap header indicating the capability information of the UE-2 320.
  • the capability information of the UE-2 320 may be indicated by a set of capability tags comprised in the header field, for example, the set of capability tags: AR, virtual reality (VR) , AI, Pos indicate the corresponding capabilities of augmented reality, virtual reality, artificial intelligence, and positioning, respectively.
  • the P-CSCF-2 370 may transmit, to the IMS AS 330, the SIP message comprising the header field indicating capability information of the UE-2 320, for example, P-CSCF-2 370 may transmit the 18x message with the P-DC-Cap header indicating the capability information of the UE-2 320 to the IMS AS 330.
  • the UE-2 320 responds with 18x with the P-DC-Cap header containing capability information (AR&VR&AI&Pos) of the UE-2 320 through the terminating network to the IMS AS 330.
  • AR&VR&AI&Pos capability information
  • the IMS AS 330 may transmit the capability information of the UE-2 320 to the DCSF-1 340, for example, the IMS AS 330 may transmit the Nimsas_SessionEventControl_Notify request with the user information and the capability information of the UE-2 320.
  • the DCSF-1 340 may transmit a Nimsas_SessionEventControl_Notify response to the IMS AS 330.
  • the IMS AS 330 may transmit, to the DCSF-2 350, the capability information of the UE-2 320.
  • the IMS AS 330 may transmit a Nimsas_SessionEventControl_Notify request to the DCSF-2 350, and the Nimsas_SessionEventControl_Notify request comprises the capability information of the UE-2 320.
  • the Nimsas_SessionEventControl_Notify request may further comprise user information of the UE-2 320, for example, an Internet protocol multimedia public identity (IMPU) of the UE-2 320. This IMPU is an example of the identity of the UE-2 310.
  • IMPU Internet protocol multimedia public identity
  • the DCSF-2 350 may transmit, to the IMS AS 330, a response to the Nimsas_SessionEventControl_Notify request.
  • This response may be referred to as Nimsas_SessionEventControl_Notify response.
  • the IMS AS 330 Based on the steps 317a and 319a, the IMS AS 330 notifies the DCSFs the call event by sending Nimsas_SessionEventControl_Notify requests to both DCSF-1 340 serving the UE-1 310 and the DCSF-2 350 serving the UE-2 320. Further, the IMS AS 330 provides information such as the IMPU and the capability information of the UE-2 320 to both DCSFs, such as the DCSF-1 340 and the DCSF-2 350.
  • the DCSF (the DCSF-1 340 or the DCSF-2 350) shall utilize the capabilities indicated in the capability information of both participants (e.g., the UE-1 310 and the UE-2 320) as an input to construct a URL, and the URL will be provided to a DCMF to allow for the downloading of a graphical user interface.
  • the graphical user interface contains data channel applications applicable to both participants.
  • the IMS AS 330 may transmit, to the P-CSCF-1 360, the SIP message comprising the header field indicating capability information of the UE-2 320, for example, as shown in Fig. 3A, the IMS AS 330 transmits the 18x message with the P-DC-Cap header “P-DC-Cap: AR, VR, AI, Pos” to the P-CSCF-2 370.
  • the P-CSCF-1 360 may transmit, to the UE-1 310, the SIP message (e.g. the SIP INVITE request with the P-DC-Cap header) received from the IMS AS 330.
  • the P-CSCF-1 360 may generate a further SIP message by removing the header field from the SIP message received from the IMS AS 330, in other words, prior to transmitting the SIP message received from the IMS AS 330, the P-CSCF-1 360 may remove the header field (e.g. the P-DC-Cap header) from the SIP message received from the IMS AS 330.
  • the P-CSCF-1 360 may transmit, to the UE-1 310, a 18x message without the P-DC-Cap header.
  • the IMS AS 330 sends the 18x response to the UE-1 310 through the originating network.
  • the P-CSCF-1 360 optionally can remove the P-DC-Cap header per local policy for privacy consideration.
  • step 325 the PRACK and UPDATE exchange between the originating network and the terminating network.
  • step 327 the bootstrap data channels are established between the UE-1 310 and originating DCMF (not shown in Fig. 3A) , and between the UE-2 320 and terminating DCMF (not shown in Fig. 3A) .
  • the DCMTSI Clients such as the UE-1 310 and the UE-2 320 can then initiate an HTTP GET request on the root ( "/" ) URL through the bootstrap data channel to retrieve a data channel (DC) application list.
  • the URL is constructed based on common capability (capabilities) between the capability (capabilities) of the UE-1 310 and the capability (capabilities) of the UE-2 320, thus, this DC application list only contains applications that support AR&Pos capabilities which are shared by both the UE-1 310 and the UE-2 320.
  • the DCMTSI client e.g. a UE
  • the DCMTSI client shall use a SIP INFO request to notify IMS AS/DCSF of the capability update.
  • IMS AS/DCSF shall then use a SIP REFER request to inform other participants (other UEs) to refresh data channel application list if the capability change would affect data channel application available to them.
  • the process may refer to Fig. 3B.
  • Fig. 3B illustrates a flowchart illustrating a process 300-2 for capability discovery and synchronization according to some further embodiments of the present disclosure.
  • the process 300-2 may be used for a scenario that the capability information of the UE-1 310 and/or the UE-2 320 changes. Accordingly, the UE-1 310 and/or the UE-2 320 need to update its (their) capability information and inform the updated capability information to the network (e.g., the IMS AS 330) .
  • the process 300-2 may be a continuation of the process 300-1. The steps below are described based on a case that the capability information of the UE-1 310 changes.
  • the UE-1 310 transmits, to the P-CSCF-1 360, a SIP message comprising a header field indicating updated capability information of the UE-1 310.
  • the SIP message may be a SIP INFO request.
  • the updated capability information may comprise a header field, for example, a P-DC-Cap header.
  • the P-DC-Cap header contains capability information of the UE-1 310, and the capability information indicates a set of updated capabilities of the UE-1 310, such as augmented reality, virtual reality, artificial intelligence, and positioning (indicated by a set of capability tags: AR, VR, AI, and Pos) .
  • step 331 the P-CSCF-1 360 transmits the SIP INFO request with the P-DC-Cap header indicating updated capability information of the UE-1 310 to the IMS AS 330.
  • the UE-1 310 Based on the steps 329 and 331, take an example that the capability information of the UE-1 310 changes, in this example, upon the capability of the UE-1 310 change (e.g., due to access network change or hardware change) , the UE-1 310 sends a SIP INFO request with the P-DC-Cap header containing new (i.e., updated) DC capability information (AR&VR&AI&Pos) of the UE-1 310 through the originating network to the IMS AS 350.
  • the P-DC-Cap header containing new (i.e., updated) DC capability information (AR&VR&AI&Pos) of the UE-1 310 through the originating network to the IMS AS 350.
  • the IMS AS 330 may transmit, to the DCSF-1 340, the updated capability information of the UE-1 310.
  • the IMS AS 330 may transmit a Nimsas_SessionEventControl_Notify request to the DCSF-1 340, and the Nimsas_SessionEventControl_Notify request comprises the updated capability information of the UE-1 310.
  • the Nimsas_SessionEventControl_Notify request may further comprise user information (e.g. the IMPU) of the UE-1 310.
  • the DCSF-1 340 may transmit, to the IMS AS 330, a Nimsas_SessionEventControl_Notify response to the Nimsas_SessionEventControl_Notify request.
  • the IMS AS 330 may transmit the updated capability information of the UE-1 310 to the DCSF-2 350, for example, the IMS AS 330 may transmit the Nimsas_SessionEventControl_Notify request with the user information and the updated capability information of the UE-1 310.
  • the DCSF-2 350 may transmit a Nimsas_SessionEventControl_Notify response to the IMS AS 330.
  • the IMS AS 330 notifies the DCSFs the call event by sending Nimsas_SessionEventControl_Notify requests to both the DCSF-1 340 serving the UE-1 310 and the DCSF-2 350 serving the UE-2 320. Further the IMS AS 330 provides information such as the IMPU and updated capability information of the UE-1 310 to both DCSFs. Similarly, in other examples (not show in Fig. 3B) , for example, if the capabilities (or capability) of the UE-2 320 changes, the UE-2 320 may also transmit the updated capability information of the UE-2 320 to both the DCSF-1 340 and the DCSF-2 350.
  • the DCSFs may utilize the updated capability information of the participants (the UE-1 310 and the UE-2 320) as input to construct a new URL (i.e. an updated URL) .
  • the new URL will be provided to DCMF to allow for the downloading of a graphical user interface that contains data channel applications applicable to both participants, that is, the UE-1 310 or the UE-2 320 may download the graphical user interface via an associated DCMF, and the graphical user interface comprise the data channel applications applicable to the UE (the UE-1 310 or the UE-2 320) .
  • the IMS AS 330 sends a 200 OK response for the SIP INFO request to the UE-1 310 through the originating network P-CSCF-1 360.
  • the IMS AS 330 may transmit a SIP message for informing the UE-1 310 to obtain a data channel application list for the UE-1 310.
  • the SIP message for informing the UE-1 310 to obtain a data channel application list for the UE-1 310 may be a SIP REFER request.
  • the IMS AS 330 transmits the SIP REFER request to the P-CSCF-1 360
  • the P-CSCF-1 360 transmits the SIP REFER request to the UE-1 310.
  • the IMS AS 330 may transmit a SIP message for informing the UE-2 320 to obtain a data channel application list for the UE-2 320.
  • the SIP REFER request transmitted to the UE-1 310 or the UE-2 320 may comprises a SIP header “Refer-To: URL” , and the UE-1 310 or the UE-2 320 may obtain the updated data channel application list via the URL.
  • the IMS AS 330 sends separate SIP REFER requests to both UEs to inform the UEs to retrieve updated URL with updated DC application list as result of capabilities update on the UE-1 310.
  • steps 345a and 347a the UE-1 310 sends a 200 OK response for the SIP REFER request to the IMS AS 330 via the P-CSCF-1 360.
  • steps 345b and 347b the UE-2 320 sends a 200 OK response for the SIP REFER request to the IMS AS 330 via the P-CSCF-2 370.
  • the bootstrap data channel is updated.
  • the DCMTSI clients (the UE-1 310 and the UE-2 320) initiate an HTTP GET request on the root ( "/" ) URL through the updated data channel to retrieve a new DC application list.
  • This DC application list contains data channel applications that support updated common capabilities which are shared by both the UE-1 310 and the UE-2 320.
  • a set of previous capability tags of the UE-1 310 comprises: AR and Pos
  • a set of capability tags of the UE-2 320 comprises: AR, VR, AI, and Pos
  • a previous DC application list contains data channel applications supporting common capabilities of the UE-1 310 and the UE-2 320, i.e. AR and Pos.
  • a set of updated capability tags of the UE-1 310 comprises: AR, VR, AI, and Pos
  • an updated DC application list contains data channel applications supporting updated common capabilities of the UE-1 310 and the UE-2 320, i.e. AR, VR, AI, and Pos.
  • the SIP message transmitted by the UE comprises a header field indicating capability information of the UE, and the header field may be a P-DC-Cap header.
  • the header field e.g. the P-DC-Cap header “P-DC-Cap” is defined to carry the capabilities for data channel applications of a given DCMTSI client (e.g. the UE-1 310 or the UE-2 320 above) . It can be used either during establishing Bootstrap data channel or before establishing Bootstrap data channel in the SIP request/response messages (e.g. the SIP INVITE request or the 18x message) .
  • P-DC-Cap "P-DC-Cap” HCOLON [cap-tag * (COMMA cap-tag) ]
  • cap-tag token # token is defined in RFC3261
  • header field is as below:
  • P-DC-Cap is an example of a capability tag (cap-tag for short) .
  • Cap-tags such as AR/MR/VR/XR/AI, where ‘AR’ means AR capability’ , ‘MR’ means MR capability’ , ‘VR’ means VR capability’ , ‘XR’ means AR&MR&VR capability’ , ‘AI’ means AI capability’ , ‘Pos’ means positioning capability’ .
  • the SIP message transmitted by the UE may indicates capability information comprising an indicator, and the indicator indicates the UE has no capability associated the data channel.
  • the indicator is provided by an empty header field without a capability tag, in other words, the missing of cap-tag in the P-DC-Cap header can be an indicator that the Multimedia Telephony Service for IMS with Data Channel supporting (DCMSTI) client (i.e. the UE) loses IMS DC capability temporarily.
  • DCMSTI Multimedia Telephony Service for IMS with Data Channel supporting
  • Table 2 is an extension of some tables of RFC3261 (e.g., table 2 and 3 in RFC3261) for the new P-DC-Cap SIP header:
  • a solution is proposed in the present disclosure to ensure that DCMTSI clients participating in one IMS DC session can invoke a common data channel application according to the real-time capabilities of participants and only the data channel applications that matching the DCMTSI clients’ capabilities will be displayed/downloaded.
  • the solution also ensures timely data channel application refresh on DCMTSI client during an IMS DC session according to the real-time capabilities changes. Consequently, the possibility of failure on data channel application invoking caused by unmatched capability is reduced to ensure an optimal user experience.
  • the solution of some embodiments may support the scenario where IMS DC session participants are served by different DCSFs and doesn’t require pre-exist bootstrap data channel.
  • a DCMTSI client may include its detailed capability list in P-DC-Cap header in the SIP request/response (e.g., INVITE and 183 Session Progress) .
  • the DCMTSI client may generate a SIP INFO request with P-DC-Cap header containing the real-time capabilities.
  • the DCMTSI clients may initiate an HTTP GET request on the root ( "/" ) URL through the bootstrap data channel to retrieve updated DC application list.
  • the IMS AS may notify the DCSF (s) the capability information of a DCMTSI client that received in P-DC-Cap header.
  • the IMS AS may send a SIP REFER request to relative participants to inform them to retrieve updated URL with updated DC application list.
  • the DCSF (s) may have the ability to utilize the capabilities of both participants as input to construct a URL that will be provided to DCMF (s) to allow for the downloading of a graphical user interface that contains data channel applications applicable to both participants.
  • the P-CSCF is optionally required to recognize and manipulate P-DC-Cap header per local privacy policy.
  • Fig. 4 illustrates a flowchart of a method 400 implemented at a terminal device according to some embodiments of the present disclosure.
  • the terminal device performing the method 400 may be the same as the first terminal device 210.
  • the terminal device may transmit, to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device.
  • SIP session initiation protocol
  • the capability information is associated with at least one data channel.
  • the capability information may comprise a first set of capabilities associated with at least one data channel, or an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities may be indicated by a set of capability tags comprised in the header field.
  • the indicator may be provided by an empty header field without a capability tag.
  • the network device may be an Internet protocol multimedia system (IMS) application server (AS) .
  • the terminal device may further establish a bootstrap data channel with a data channel media function (DCMF) for obtaining a data channel application list for the terminal device.
  • IMS Internet protocol multimedia system
  • DCMF data channel media function
  • the SIP message may be a first SIP message
  • the header field may be a first header field
  • the terminal device may be a first terminal device
  • the terminal device may further receive, from the network device, a second SIP message without a second header field.
  • the first SIP message may be a first SIP request for initiating the IMS data channel session
  • the second SIP message may be determined based on a response to the first SIP request.
  • the first SIP message may be a response to the second SIP message.
  • the second SIP message may be determined based on a second SIP request for initiating the IMS data channel session.
  • the SIP message may be used for updating previous capability information of the terminal device.
  • a second set of capabilities of the terminal device indicated by the previous capability information is updated based on the first set of capabilities.
  • the second set of capabilities is terminated.
  • the terminal device may further terminate unavailable data channel application associated with the terminal device to release at least one media resource of the data channel application.
  • the terminal device may further receive, from the network device, a third SIP message for informing the terminal device to obtain a data channel application list for the terminal device, and transmit a request for obtaining, via a bootstrap data channel established between the terminal device and a DCMF, the data channel application list.
  • the terminal device may further transmit, to the network device, a response to the third SIP message.
  • the terminal device may be a first terminal device
  • the capability information may be first capability information
  • the data channel application list is based on: the first capability information of the first terminal device, alternatively, the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, wherein the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel, alternatively, a set of data channel applications configured by the network device.
  • the first SIP message is transmitted to the network device via a proxy-call session control function (P-CSCF) , additionally or alternatively, the second SIP message and/or the third SIP message may be received from the network device via the P-CSCF.
  • P-CSCF proxy-call session control function
  • Fig. 5 illustrates a flowchart of a method 500 implemented at a network device according to some embodiments of the present disclosure.
  • the network device performing the method 500 may be a first network device, for example, the first network device 230.
  • the first network device may receive, from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device.
  • SIP session initiation protocol
  • the capability information is associated with at least one data channel.
  • the first network device may transmit, to a second network device, the capability information of the terminal device.
  • the capability information may comprise a first set of capabilities associated with at least one data channel.
  • the capability information may comprise an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities may be indicated by a set of capability tags comprised in the header field.
  • the indicator may be provided by an empty header field without a capability tag.
  • the terminal device may be a first terminal device
  • the second network device may be a first data channel signaling function (DCSF) serving the first terminal device
  • the first network device may further transmit, to a second DCSF serving a second terminal device, the capability information of the first terminal device.
  • DCSF data channel signaling function
  • the SIP message may be a first SIP message
  • the header field is a first header field
  • the capability information is first capability information
  • the first network device may further receive, from the second terminal device, a fourth SIP message comprising a second header field indicating second capability information of the second terminal device, wherein the second capability information is associated with at least one data channel, and transmit, to the first DCSF and the second DCSF, the second capability information.
  • the first network device may further transmit an identity of the first terminal device to at least one of the first DCSF and the second DCSF. Additionally or alternatively, the first network device may further transmit an identity of the second terminal device to at least one of the first DCSF and the second DCSF.
  • the first SIP message may be a first SIP request for initiating an IMS data channel session between the first terminal device and the second terminal device, and the fourth SIP message is a response to the first SIP request.
  • the first SIP message may a response to the fourth SIP message, in which the fourth SIP message may be a second SIP request for initiating the IMS data channel session.
  • the SIP message may be used for updating previous capability information of the terminal device.
  • a second set of capabilities of the terminal device indicated by the previous capability information is updated based on the first set of capabilities. In some other embodiments, in the event that the capability information comprises the indicator, the second set of capabilities is terminated.
  • the first network device may further transmit, to the terminal device, a response to the SIP message.
  • the first network device may further transmit, to the terminal device, a third SIP message for informing the terminal device to obtain a data channel application list for the terminal device.
  • the terminal device may be a first terminal device, and the first network device may further transmit, to a second terminal device, a fifth SIP message for informing the second terminal device to obtain a data channel application list for the second terminal device.
  • the first network device may further receive, from the first terminal device, a response to the third SIP message, additionally or alternatively, the first network device may receive, from the second terminal device, a response to the fifth SIP message.
  • the terminal device may be a first terminal device
  • the capability information may be first capability information
  • the data channel application list is based on the first capability information of the first terminal device, or based on the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel, or based on a set of data channel applications configured by the first network device.
  • the first SIP message is received from the terminal device via a proxy-call session control function (P-CSCF) , additionally or alternatively, at least one of the third SIP message or the fifth SIP message is transmitted to the terminal device via the P-CSCF.
  • P-CSCF proxy-call session control function
  • the network device is an Internet protocol multimedia system (IMS) application server (AS) .
  • IMS Internet protocol multimedia system
  • AS application server
  • Fig. 6 illustrates a flowchart of a method 600 implemented at a network device according to some other embodiments of the present disclosure.
  • the network device performing the method 600 may be a second network device, for example the second network device 240 mentioned above.
  • the second network device may receive, from a first network device, capability information of a terminal device served by the second network device, in which the capability information is associated with at least one data channel.
  • the second network device may construct, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • URL uniform resource locator
  • the capability information may comprise a first set of capabilities associated with at least one data channel.
  • the capability information may comprise an indicator indicating that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities may be indicated by a set of capability tags comprised in the header field.
  • the indicator is provided by an empty header field without a capability tag.
  • the terminal device may be a first terminal device
  • the capability information may be first capability information
  • the second network device may further receive, from the first network device, second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information is associated with at least one data channel.
  • the terminal device may be a first terminal device, the capability information may be first capability information.
  • the second network device may construct the URL based on the first capability information of the first terminal device.
  • the second network device may construct the URL based on the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel.
  • the second network device may construct the URL based on a set of data channel applications configured by the first network device.
  • the second network device may further receive, from the first network device, an identity of the first terminal device and/or an identity of the second terminal device.
  • the second network device constructs the URL, specifically, in the event that the first capability information and the second capability information have at least one common capability, the second network device may construct the URL based on the at least one common capability, alternatively, in the event that the first capability information and the second capability information have no common capability, the second network device may construct the URL based on the set of data channel applications, alternatively, in the event that at least one of the first capability information or the second capability information comprises an indicator, the second network device may construct the URL based on the set of data channel applications.
  • the indicator comprised in the first capability information may indicate that the first terminal device has no capability associated with at least one data channel
  • the indicator comprised in the second capability information may indicate that the second terminal device has no capability associated with at least one data channel.
  • the second network device may further terminate unavailable data channel application associated with the terminal device to release at least one media resource of the data channel application.
  • the first network device may be an IP multimedia system (IMS) application server (AS) .
  • the second network device may be a data channel signaling function (DCSF) .
  • Fig. 7 illustrates a flowchart of a method 700 implemented at a network device according to some further embodiments of the present disclosure.
  • the network device performing the method 700 may be a third network device, for example the third network device 250 above.
  • the third network device may receive, from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device.
  • SIP session initiation protocol
  • the capability information is associated with at least one data channel.
  • the third network device may generate a sixth SIP message by removing the header field from the first SIP message.
  • the third network device may transmit the sixth SIP message to a second terminal device.
  • the capability information may comprise a first set of capabilities associated with at least one data channel, alternatively, the capability information may comprise an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities may be indicated by a set of capability tags comprised in the header field.
  • the indicator may be provided by an empty header field without a capability tag.
  • the header field may be a first header field
  • the third network device may be associated with the second terminal device
  • the capability information is first capability information
  • the third network device may further receive, from the second terminal device, a fourth SIP message comprising a second header field indicating second capability information of the second terminal device, wherein the second capability information is associated with at least one data channel, and transmit, to the first network device, the second capability information.
  • the first SIP message may be a first SIP request for initiating an IMS data channel session between the first terminal device and the second terminal device, and the fourth SIP message may be a response to the first SIP request.
  • the first SIP message may be a response to the fourth SIP message, in which the fourth SIP message may be a second SIP request for initiating the IMS data channel session.
  • the third network device may further receive, from the first network device, a fifth SIP message for informing the second terminal device to obtain a data channel application list for the second terminal device, and transmit, to the second terminal device, the fifth SIP message.
  • the capability information may be first capability information.
  • the data channel application list is based on the first capability information of the first terminal device.
  • the data channel application list is based on the first capability information of the first terminal device and second capability information of the second terminal device participating an IMS data channel session with the first terminal device, wherein the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel.
  • the data channel application list is based on a set of data channel applications configured by the first network device.
  • the third network device may be a proxy-call session control function (P-CSCF) .
  • P-CSCF proxy-call session control function
  • an apparatus capable of performing any of the method 400 may comprise means for performing the respective steps of the method 400.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for transmitting, to a network device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, wherein the capability information is associated with at least one data channel.
  • SIP session initiation protocol
  • the capability information comprises a first set of capabilities associated with at least one data channel, or an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities is indicated by a set of capability tags comprised in the header field.
  • the indicator is provided by an empty header field without a capability tag.
  • the network device is an Internet protocol multimedia system (IMS) application server (AS)
  • the apparatus further comprises means for establishing a bootstrap data channel with a data channel media function (DCMF) for obtaining a data channel application list for the terminal device.
  • IMS Internet protocol multimedia system
  • DCMF data channel media function
  • the SIP message is a first SIP message
  • the header field is a first header field
  • the terminal device is a first terminal device
  • the apparatus further comprises means for receiving, from the network device, a second SIP message without a second header field.
  • the first SIP message is a first SIP request for initiating the IMS data channel session
  • the second SIP message is determined based on a response to the first SIP request.
  • the first SIP message is a response to the second SIP message, in which the second SIP message is determined based on a second SIP request for initiating the IMS data channel session.
  • the SIP message is used for updating previous capability information of the terminal device.
  • a second set of capabilities of the terminal device indicated by the previous capability information is updated based on the first set of capabilities.
  • the second set of capabilities is terminated.
  • the apparatus further comprises means for terminating unavailable data channel application associated with the terminal device to release at least one media resource of the data channel application.
  • the apparatus further comprises means for receiving, from the network device, a third SIP message for informing the terminal device to obtain a data channel application list for the terminal device, and means for transmitting a request for obtaining, via a bootstrap data channel established between the terminal device and a DCMF, the data channel application list.
  • the apparatus further comprises means for transmitting, to the network device, a response to the third SIP message.
  • the terminal device is a first terminal device
  • the capability information is first capability information.
  • the data channel application list is based on the first capability information of the first terminal device.
  • the data channel application list is based on the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel.
  • the data channel application list is based on a set of data channel applications configured by the network device.
  • the first SIP message is transmitted to the network device via a proxy-call session control function (P-CSCF) . Additionally or alternatively, the second SIP message and/or the third SIP message may be received from the network device via the P-CSCF.
  • P-CSCF proxy-call session control function
  • the apparatus further comprises means for performing other steps in some embodiments of the method 400.
  • the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing any of the method 500 may comprise means for performing the respective steps of the method 500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving, from a terminal device, a session initiation protocol (SIP) message comprising a header field indicating capability information of the terminal device, in which the capability information is associated with at least one data channel, and means for transmitting, to a second network device, the capability information of the terminal device.
  • SIP session initiation protocol
  • the capability information comprises a first set of capabilities associated with at least one data channel, or an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities is indicated by a set of capability tags comprised in the header field.
  • the indicator is provided by an empty header field without a capability tag.
  • the terminal device is a first terminal device
  • the second network device is a first data channel signaling function (DCSF) serving the first terminal device
  • the apparatus further comprises means for transmitting, to a second DCSF serving a second terminal device, the capability information of the first terminal device.
  • DCSF data channel signaling function
  • the SIP message is a first SIP message
  • the header field is a first header field
  • the capability information is first capability information
  • the apparatus further comprises means for receiving, from the second terminal device, a fourth SIP message comprising a second header field indicating second capability information of the second terminal device, wherein the second capability information is associated with at least one data channel; and means for transmitting, to the first DCSF and the second DCSF, the second capability information.
  • the apparatus further comprises means for transmitting an identity of the first terminal device to at least one of the first DCSF and the second DCSF; additionally or alternatively, the apparatus further comprises means for transmitting an identity of the second terminal device to at least one of the first DCSF and the second DCSF.
  • the first SIP message is a first SIP request for initiating an IMS data channel session between the first terminal device and the second terminal device
  • the fourth SIP message is a response to the first SIP request.
  • the first SIP message is a response to the fourth SIP message.
  • the fourth SIP message may be a second SIP request for initiating the IMS data channel session.
  • the SIP message is used for updating previous capability information of the terminal device.
  • a second set of capabilities of the terminal device indicated by the previous capability information is updated based on the first set of capabilities.
  • the second set of capabilities is terminated.
  • the apparatus further comprises means for transmitting, to the terminal device, a response to the SIP message.
  • the apparatus further comprises means for transmitting, to the terminal device, a third SIP message for informing the terminal device to obtain a data channel application list for the terminal device.
  • the terminal device is a first terminal device
  • the apparatus further comprises means for transmitting, to a second terminal device, a fifth SIP message for informing the second terminal device to obtain a data channel application list for the second terminal device.
  • the apparatus further comprises means for receiving, from the first terminal device, a response to the third SIP message. Additionally or alternatively, the apparatus further comprises means for receiving, from the second terminal device, a response to the fifth SIP message.
  • the terminal device is a first terminal device
  • the capability information is first capability information.
  • the data channel application list is based on the first capability information of the first terminal device.
  • the data channel application list is based on the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel.
  • the data channel application list is based on a set of data channel applications configured by the first network device.
  • the first SIP message is received from the terminal device via a proxy-call session control function (P-CSCF) . Additionally or alternatively, the third SIP message and/or the fifth SIP message may be transmitted to the terminal device via the P-CSCF.
  • P-CSCF proxy-call session control function
  • the network device is an Internet protocol multimedia system (IMS) application server (AS) .
  • IMS Internet protocol multimedia system
  • AS application server
  • the apparatus further comprises means for performing other steps in some embodiments of the method 500.
  • the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing any of the method 600 may comprise means for performing the respective steps of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving, from a first network device, capability information of a terminal device served by the second network device, wherein the capability information is associated with at least one data channel; and means for constructing, based on the capability information, a uniform resource locator (URL) for downloading of a graphical user interface which contains at least one data channel application applicable to the terminal device.
  • a uniform resource locator URL
  • the capability information comprises a first set of capabilities associated with at least one data channel; or an indicator indicating that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities is indicated by a set of capability tags comprised in the header field.
  • the indicator is provided by an empty header field without a capability tag.
  • the terminal device is a first terminal device
  • the capability information is first capability information
  • the apparatus comprises means for receiving, from the first network device, second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information is associated with at least one data channel.
  • the terminal device is a first terminal device
  • the capability information is first capability information
  • the means for constructing the URL constructs the URL based on the first capability information of the first terminal device, alternatively, based on the first capability information of the first terminal device and second capability information of a second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel, alternatively, based on a set of data channel applications configured by the first network device.
  • the apparatus further comprises means for receiving, from the first network device, at least one of an identity of the first terminal device or an identity of the second terminal device.
  • the means for constructing the URL comprises means for, in the event that the first capability information and the second capability information have at least one common capability, constructing the URL based on the at least one common capability; or means for, in the event that the first capability information and the second capability information have no common capability, constructing the URL based on the set of data channel applications; or means for in the event that at least one of the first capability information or the second capability information comprises an indicator, constructing the URL based on the set of data channel applications, in which the indicator comprised in the first capability information indicates that the first terminal device has no capability associated with at least one data channel, and the indicator comprised in the second capability information indicates that the second terminal device has no capability associated with at least one data channel.
  • the apparatus further comprises means for terminating unavailable data channel application associated with the terminal device to release at least one media resource of the data channel application.
  • the first network device is an IP multimedia system (IMS) application server (AS)
  • the second network device is a data channel signaling function (DCSF) .
  • the apparatus further comprises means for performing other steps in some embodiments of the method 600.
  • the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing any of the method 700 may comprise means for performing the respective steps of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving, from a first network device, a first session initiation protocol (SIP) message comprising a header field indicating capability information of a first terminal device, wherein the capability information is associated with at least one data channel; means for generating a sixth SIP message by removing the header field from the first SIP message; and means for transmitting the sixth SIP message to a second terminal device.
  • SIP session initiation protocol
  • the capability information comprises a first set of capabilities associated with at least one data channel; or an indicator that the terminal device has no capability associated with at least one data channel.
  • the first set of capabilities is indicated by a set of capability tags comprised in the header field.
  • the indicator is provided by an empty header field without a capability tag.
  • the header field is a first header field
  • the third network device is associated with the second terminal device
  • the capability information is first capability information
  • the apparatus further comprises means for receiving, from the second terminal device, a fourth SIP message comprising a second header field indicating second capability information of the second terminal device, wherein the second capability information is associated with at least one data channel; and means for transmitting, to the first network device, the second capability information.
  • the first SIP message is a first SIP request for initiating an IMS data channel session between the first terminal device and the second terminal device
  • the fourth SIP message is a response to the first SIP request.
  • the first SIP message is a response to the fourth SIP message, in which the fourth SIP message is a second SIP request for initiating the IMS data channel session.
  • the apparatus further comprises means for receiving, from the first network device, a fifth SIP message for informing the second terminal device to obtain a data channel application list for the second terminal device; and means for transmitting, to the second terminal device, the fifth SIP message.
  • the capability information is first capability information.
  • the data channel application list is based on the first capability information of the first terminal device.
  • the data channel application list is based on the first capability information of the first terminal device and second capability information of the second terminal device participating an IMS data channel session with the first terminal device, in which the second capability information indicates that the second terminal device has a third set of capabilities associated with at least one data channel.
  • the data channel application list is based on a set of data channel applications configured by the first network device.
  • the third network device is a proxy-call session control function (P-CSCF) .
  • P-CSCF proxy-call session control function
  • the apparatus further comprises means for performing other steps in some embodiments of the method 700.
  • the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • Fig. 8 is a simplified block diagram of a device 800 that is suitable for implementing embodiments of the present disclosure.
  • the device 800 may be provided to implement the communication device, for example the terminal device 110 or 120, the network device 140 or 150 or 160 as shown in Fig. 1.
  • the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.
  • the communication modules 840 is for bidirectional communications.
  • the communication modules 840 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 820 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.
  • a computer program 830 includes computer executable instructions that are executed by the associated processor 810.
  • the program 830 may be stored in the ROM 824.
  • the processor 810 may perform any suitable actions and processing by loading the program 830 into the RAM 822.
  • the embodiments of the present disclosure may be implemented by means of the program 830 so that the device 800 may perform any process of the disclosure as discussed with reference to Figs. 2 to 7.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 830 may be tangibly contained in a computer readable medium which may be included in the device 800 (such as in the memory 820) or other storage devices that are accessible by the device 800.
  • the device 800 may load the program 830 from the computer readable medium to the RAM 822 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • Fig. 9 shows an example of the computer readable medium 900 in form of CD or DVD.
  • the computer readable medium has the program 830 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 800 as described above with reference to Figs. 2-7.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Selon des modes de réalisation, la présente invention concerne des informations de capacité associées à des canaux de données. Selon un aspect, un dispositif de terminal transmet, à un dispositif de réseau, un message de protocole d'initiation de session (SIP) contenant un champ d'en-tête indiquant des informations de capacité du dispositif de terminal. Les informations de capacité sont associées à au moins un canal de données. Les modes de réalisation de la présente invention peuvent découvrir des changements de capacité détaillés d'un dispositif terminal associé à au moins un canal de données et synchroniser en temps opportun les participants d'une session de sous-système multimédia de protocole Internet par l'intermédiaire d'un nouvel en-tête de SIP contenant les capacités détaillées du dispositif de terminal.
PCT/CN2023/133385 2023-11-22 2023-11-22 Informations de capacité associées à des canaux de données Pending WO2025107198A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/133385 WO2025107198A1 (fr) 2023-11-22 2023-11-22 Informations de capacité associées à des canaux de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/133385 WO2025107198A1 (fr) 2023-11-22 2023-11-22 Informations de capacité associées à des canaux de données

Publications (1)

Publication Number Publication Date
WO2025107198A1 true WO2025107198A1 (fr) 2025-05-30

Family

ID=95825768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/133385 Pending WO2025107198A1 (fr) 2023-11-22 2023-11-22 Informations de capacité associées à des canaux de données

Country Status (1)

Country Link
WO (1) WO2025107198A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115059A (zh) * 2007-01-19 2008-01-30 华为技术有限公司 多媒体子系统中传递终端信息的方法、设备及系统
WO2009092263A1 (fr) * 2007-12-28 2009-07-30 Huawei Technologies Co., Ltd. Terminal, serveur, procédé pour gérer ledit terminal et procédé pour rapporter des informations de capacité relatives à ce terminal
KR20130041665A (ko) * 2011-10-17 2013-04-25 텔코웨어 주식회사 Ｇｒｕｕ 사용 가입자 간의 ｉｍｓ망에서의 ｓｉｐ 메시지 전송 방법 및 그 장치
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质
CN116939884A (zh) * 2022-03-29 2023-10-24 中国移动通信有限公司研究院 一种信息处理方法、装置、通信设备和存储介质
WO2023214853A1 (fr) * 2022-05-05 2023-11-09 Samsung Electronics Co., Ltd. Procédé et appareil permettant de mettre à jour une prise en charge de réseau pour une capacité dc ims à un ue après un enregistrement initial dans un système de communication sans fil

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115059A (zh) * 2007-01-19 2008-01-30 华为技术有限公司 多媒体子系统中传递终端信息的方法、设备及系统
WO2009092263A1 (fr) * 2007-12-28 2009-07-30 Huawei Technologies Co., Ltd. Terminal, serveur, procédé pour gérer ledit terminal et procédé pour rapporter des informations de capacité relatives à ce terminal
KR20130041665A (ko) * 2011-10-17 2013-04-25 텔코웨어 주식회사 Ｇｒｕｕ 사용 가입자 간의 ｉｍｓ망에서의 ｓｉｐ 메시지 전송 방법 및 그 장치
CN116939884A (zh) * 2022-03-29 2023-10-24 中国移动通信有限公司研究院 一种信息处理方法、装置、通信设备和存储介质
WO2023214853A1 (fr) * 2022-05-05 2023-11-09 Samsung Electronics Co., Ltd. Procédé et appareil permettant de mettre à jour une prise en charge de réseau pour une capacité dc ims à un ue après un enregistrement initial dans un système de communication sans fil
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质

Similar Documents

Publication Publication Date Title
CN112583982B (zh) 呼叫处理的方法和设备
KR101780843B1 (ko) 인터넷 프로토콜 멀티미디어 서브시스템 협력 세션들에서의 식별 및 이동을 위한 방법 및 장치
CN113163058B (zh) 会话参数更新方法、装置及通信设备、电子设备
US20250203677A1 (en) Communication establishment method and apparatus, terminal device, and network side device
EP3288230A1 (fr) Cadriciel et procédé pour réaliser une communication multimédia, équipement de fusion et équipement utilisateur (ue)
TW202245532A (zh) 用於行動通訊的方法及使用者設備
US20250071178A1 (en) Method and Apparatus for Processing Data Channel Application List, and Device
CN117062083A (zh) 通信方法、装置、终端、网络侧设备及介质
WO2025107198A1 (fr) Informations de capacité associées à des canaux de données
WO2025095598A1 (fr) Procédé et appareil permettant de prendre en charge un appel d'avatar dans un système de communication sans fil
US20240283829A1 (en) Call Exception Processing Method and Electronic Device
TWI789019B (zh) 用於呼叫添加控制之使用者代理及其方法
WO2025107179A1 (fr) Message sdp associé à des flux de canaux de données
WO2025171585A1 (fr) Sélection de fonction de réseau
WO2014091630A1 (fr) Système de communication sans fil, terminal mobile, serveur et procédé de communication sans fil
WO2025097394A1 (fr) Connexion directe de canal de données de sous-système multimédia de protocole internet
WO2025175442A1 (fr) Canal de données pour application dans un sous-système multimédia de protocole internet
CN119729892A (zh) 建立数据通道的方法、第一用户设备及网络侧功能
US20250365789A1 (en) Method and apparatus for establishing data channel, core network device, and storage medium
CN120302366A (zh) 通信的方法、装置及通信设备
US20230098402A1 (en) Providing multi-device service using network application programming interface
CN117425228A (zh) 数据通道的保持方法、装置、通信设备及可读存储介质
CN118740786A (zh) 地址、ims消息的发送方法、终端及网络侧设备
CN120454806A (zh) 通信的方法、装置、设备及存储介质
CN119316027A (zh) 呼叫建立方法、装置及网络侧设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23959172

Country of ref document: EP

Kind code of ref document: A1