WO2024096562A1 - Procédé et dispositif pour fournir une application de canal de données dans un système de communication mobile - Google Patents

Procédé et dispositif pour fournir une application de canal de données dans un système de communication mobile Download PDF

Info

Publication number
WO2024096562A1
WO2024096562A1 PCT/KR2023/017238 KR2023017238W WO2024096562A1 WO 2024096562 A1 WO2024096562 A1 WO 2024096562A1 KR 2023017238 W KR2023017238 W KR 2023017238W WO 2024096562 A1 WO2024096562 A1 WO 2024096562A1
Authority
WO
WIPO (PCT)
Prior art keywords
data channel
application
sdp
bootstrap
terminal
Prior art date
Application number
PCT/KR2023/017238
Other languages
English (en)
Korean (ko)
Inventor
양현구
Original Assignee
삼성전자 주식회사
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 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2024096562A1 publication Critical patent/WO2024096562A1/fr

Links

Images

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/40—Support for services or applications
    • 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/1083—In-session procedures

Definitions

  • This disclosure relates to a method and apparatus for providing data channel applications in a communication system.
  • 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave.
  • 'Sub 6GHz' sub-6 GHz
  • mm millimeter wave
  • Wave ultra-high frequency band
  • 6G mobile communication technology which is called the system of Beyond 5G
  • Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.
  • ultra-wideband services enhanced Mobile BroadBand, eMBB
  • ultra-reliable low-latency communications URLLC
  • massive machine-type communications mMTC
  • numerology support multiple subcarrier interval operation, etc.
  • dynamic operation of slot format initial access technology to support multi-beam transmission and broadband
  • definition and operation of BWP Band-Width Part
  • New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information
  • L2 pre-processing L2 pre-processing
  • dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.
  • V2X Vehicle-to-Everything
  • NR-U New Radio Unlicensed
  • UE Power Saving NR terminal low power consumption technology
  • NTN Non-Terrestrial Network
  • IAB provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links.
  • Intelligent factories Intelligent Internet of Things, IIoT
  • Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover
  • 2-step Random Access (2-step RACH for simplification of random access procedures)
  • Standardization in the field of wireless interface architecture/protocol for technologies such as NR is also in progress
  • a 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • FD-MIMO full dimensional MIMO
  • array antennas to ensure coverage in the terahertz band of 6G mobile communication technology.
  • multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end.
  • This disclosure discloses a method for providing and obtaining data channel applications in a communication system.
  • a method of a terminal in a communication system includes selecting an individual data channel application based on a portal data channel application provided through a first bootstrap data channel; transmitting an SDP offer associated with a second bootstrap data channel for the selected individual data channel application to a first network entity; Receiving an SDP response corresponding to the SDP proposal from the first network entity; and acquiring the individual data channel application through the second bootstrap data channel based on the SDP response.
  • a method of a network entity in a communication system providing a SDP offer associated with a second bootstrap data channel for a selected individual data channel application selected based on a portal data channel application provided through a first bootstrap data channel to a terminal.
  • a method of a network entity in a communication system receiving, via a first bootstrap data channel used to provide a portal data channel application, a request for an individual data channel application selected based on the portal data channel application.
  • FIG. 1 is a diagram illustrating an example of a web application provision structure according to various embodiments of the present disclosure.
  • FIG. 2 is a diagram illustrating an IMS (IP Multimedia Subsystem) network structure according to various embodiments of the present disclosure.
  • IMS IP Multimedia Subsystem
  • Figure 3 is a diagram illustrating an example of interaction between IMS and 5GC according to various embodiments of the present invention.
  • FIG. 4 is a diagram illustrating an example of a SIP operation procedure in a mobile communication system according to various embodiments of the present disclosure.
  • FIG. 5 is a diagram illustrating an example of an SDP negotiation procedure for a real-time interaction service in a communication system according to various embodiments of the present disclosure.
  • FIG. 6 is a diagram illustrating an example of a network structure including a data channel server in a communication system according to various embodiments of the present disclosure.
  • FIG. 7 is a diagram illustrating an example of a protocol stack of a user terminal supporting a data channel application in a communication system according to various embodiments of the present disclosure.
  • FIGS. 8A and 8B are diagrams illustrating an example of a procedure for obtaining a data channel application for a terminal in a communication system according to various embodiments of the present disclosure.
  • FIG. 9 is a diagram illustrating an example of a client-driven procedure for acquiring an individual data channel application in a communication system according to various embodiments of the present disclosure.
  • FIG. 10 is a diagram illustrating an example of a server-driven procedure for acquiring an individual data channel application in a communication system according to various embodiments of the present disclosure.
  • FIG. 11 is a diagram illustrating the structure of a terminal according to various embodiments of the present disclosure.
  • FIG. 12 is a diagram illustrating the structure of an IMS AS (Application Server) according to various embodiments of the present disclosure.
  • FIG. 13 is a diagram illustrating the structure of a data channel server according to various embodiments of the present disclosure.
  • FIG. 14 is a diagram illustrating the structure of a network entity according to various embodiments of the present disclosure.
  • each block of the processing flow diagrams and combinations of the flow diagram diagrams may be performed by computer program instructions.
  • These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions.
  • These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory
  • the instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s).
  • Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operations are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer and generates a computer or other programmable data. Instructions that perform processing equipment may also provide operations for executing the functions described in the flow diagram block(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s).
  • the base station is an entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network.
  • a terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.
  • 5G (NR) or 5G (NR) system may be described as an example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel type.
  • this disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge.
  • This disclosure relates to a method and apparatus for providing data channel applications in a communication system.
  • the present disclosure relates to a method and device for providing data channel applications in a communication system that provides Real-Time Interaction services.
  • Telephony was first invented at the end of the 19th century, and mobile telephony became popular at the end of the 20th century.
  • mobile communication technology video telephony services that allow people to make calls while watching each other's videos have been supported, and the 5th generation (5G) mobile communication system allows contact (touch) with a distant party through the phone. It is expected to be able to provide a new level of real-time interaction service including tactile, feel, etc.
  • IMS IP Multimedia Subsystem
  • IP Internet Protocol
  • IMS basically pursues improved price competitiveness of services and rapid service development and change by using general-purpose Internet-based technologies and standardized network functions.
  • IMS is independent of the access network, and with improved session management functions, applications from different networks can be easily linked, promoting global interconnection between services and conversion of wired and wireless networks.
  • IMS was initially proposed for interoperability and conversion between different mobile communication systems in the all-IP network broadband code division multiple access (W-CDMA) network, but it is currently used not only for mobile communication systems but also for various wired and wireless integrated networks based on IP networks. Supported technologies are expanding.
  • W-CDMA broadband code division multiple access
  • the IMS supports the use of data channels that can carry not only voice and video, but also arbitrary data streams within the same session.
  • the data channel may have transmission requirements such as latency, robustness, and bandwidth depending on the purpose of use and the characteristics of the data to be transmitted, and the IMS operator establishes a data channel in consideration of the above requirements. You can set it.
  • the phone service provided by the operator may provide global user identification and contact based on phone number, user authentication, mobility, session control, QoS (Quality-of-Service), security, robustness, etc., and data combined with the phone service.
  • QoS Quality-of-Service
  • Web applications hosted on the Internet can be identified and obtained by HTTP URL, and in order for multiple users to use services provided by the same web application, services such as URLs must be provided through a separate method not provided by the web application. Access information may be shared.
  • Data channel applications utilizing the IMS data channel can be selected by the operator based on call context information (e.g., user identifier), and the selected data channel application can be selected by the data channel server through a special-purpose data channel called a bootstrap data channel.
  • the terminal can download HTML web documents, JavaScript, images, style sheets, etc. that make up the data channel application by sending a root URL (“/”) request to the bootstrap data channel.
  • the same data channel application or data channel applications that are linked according to the service provider's intention must be provided. Since the root URL does not contain information that can identify the data channel application, the other party must be provided with information that can identify the application that is the same as the data channel application that the user selected in real time during the call or that is linked according to the intention of the service provider. A means of conveying it is needed.
  • a method of providing a data channel application in a mobile communication system includes the steps of an operator providing a portal data channel application according to call situation information; identifying a data channel application selected by the user through the portal data channel application; Transmitting bootstrap data channel setting information for transmitting the data channel application selected by the user or a data channel application associated with the data channel application selected by the user to service users; and transmitting the selected data channel application or the data channel application associated with the selected data channel application through the bootstrap data channel to service users.
  • a method of receiving a data channel application in a mobile communication system includes: receiving a portal data channel application from an operator; A user selecting a data channel application through the portal data channel application; Receiving bootstrap data channel setting information through which the data channel application selected by the user or a data channel application associated with the data channel application selected by the user will be transmitted; and receiving the selected data channel application or the data channel application associated with the selected data channel application through the bootstrap data channel.
  • a real-time interaction service can be provided by providing the same data channel application or data channel applications that are linked according to the intention of the service provider to real-time communication service participants.
  • FIG. 1 is a diagram illustrating an example of a web application provision structure according to various embodiments of the present disclosure.
  • user 100 may consume a web application using user device 110.
  • a web browser 111 running on the user device 110 may perform a presentation function of a web application.
  • the web browser 111 may receive data input from the user 100, render the results of processing the user data on a display device, etc., and provide the results to the user 100.
  • Information for web application presentation of the web browser 111 may include HTML (Hyper Text Markup Language), CSS (Cascading Style Sheet), and JavaScript, and may be provided through HTTP (Hypertext Transfer Protocol) URL (Uniform Resource Locator). It can be downloaded from the web application server (120) upon request. While HTML provides the structure of web applications and CSS controls how web applications are displayed to users, JavaScript, a programming language, provides tools to change the behavior of various components included in web applications. You can.
  • the user data processing is, for example, the web browser 111 transmits a request for data processing to the web application server 120, and a response to the data processing is sent to the regular web application server 120.
  • the web application server 120 may include application logic 121, a file management system 122, and a database 123 for processing the user data.
  • the HTTP URL is an identifier that describes the location where resources such as documents, images, and videos are stored on a specific server.
  • the HTTP URL may have the following structure.
  • Scheme refers to the protocol to be used, and uses http or https.
  • the server may require a username and password to access data.
  • Host refers to the IP or domain address of a web application server with resources, and port refers to each socket when the host communicates data through multiple sockets. This is identifiable information. In HTTP, if the port number is not specified, port 80 is used as the default.
  • Path refers to the path to the resource provided by the host.
  • a query is also called a query string, and can include parameters necessary when a web browser requests a resource.
  • HTML can assign an id attribute to each element, and when a fragment is passed to the URL, the web browser scrolls to the location where the id is located.
  • http://www.example.com/test.html indicates the location of a resource called 'test.html' that can be obtained from a web application server in the 'www.example.com' domain using HTTP.
  • FIG. 2 is a diagram illustrating an IMS network structure according to various embodiments of the present disclosure.
  • a UE (User Equipment) 210 configures an IM CN subsystem with another UE (not shown) located in a remote IMS network 280 through an IP Multimedia Core Network (IM CN) subsystem.
  • IM CN IP Multimedia Core Network
  • the IM CN subsystem may include P-CSCF (220), I/S-CSCF (230), IMS AS (240), IMS HSS (250), IMS AGW (260), and/or MRF (270). and the above components can perform the following functions.
  • P-CSCF Provided Call Session Control Function
  • P-CSCF can perform the first contact point function for the UE to access the IMS.
  • I-CSCF can perform a contact point function for subscribers of a network operator or roaming users currently located in the service area of the network operator. S-CSCF can cope with the actual user session state of the network.
  • IMS AS can provide and execute IM (Internet Multimedia) value added services. Additionally, IMS AS can influence SIP (Session Initiation Protocol) sessions by acting as a proxy for services supported in the operator network.
  • IM Internet Multimedia
  • SIP Session Initiation Protocol
  • IMS HSS can serve as a database that stores information about users.
  • IMS-AGW (Access Gateway) (260): IMS-AGW is located in the media transmission path and can manage network addresses associated with inbound and outbound media streams.
  • MRF Media Resource Function
  • MRF can perform various processing tasks related to media streams.
  • MRF can be divided into MRFC (Multimedia Resource Function Controller), which is responsible for control, and MRFP (Multimedia Resource Function Processor), which is responsible for media processing.
  • MRFC Multimedia Resource Function Controller
  • MRFP Multimedia Resource Function Processor
  • the interface between the components can be expressed by the following reference points.
  • Reference point Gm can support communication between the UE and IM CN subsystem.
  • the UE may request network registration and session control through the Gm reference point.
  • SIP which will be described later, can be used for the Gm reference point.
  • Reference point Mw can support signaling message exchange and transmission between CSCFs.
  • Reference point ISC can support the exchange of information between the S-CSCF and a service platform (for example, IMS AS) necessary for the service provided by the service platform.
  • a service platform for example, IMS AS
  • Reference point Sh can support the exchange of information between HSS and a service platform (for example, IMS AS) necessary for the service provided by the service platform.
  • a service platform for example, IMS AS
  • Reference point Cx can support information transmission between HSS and CSCF.
  • Reference point Mr' can support interaction for session control between IMS AS and MRFC
  • reference point Cr can support interaction for media control between IMS AS and MRFC.
  • Reference point Iq can support information exchange required for allocation and release of transport addresses between P-CSCF and IMS AGW.
  • Reference point Mb can support IMS media transmission between IMS components.
  • a wireless communication system may be a 5G system (5GS).
  • the 5G system may be composed of a 5G radio access network (NG-RAN: Next Generation Radio Access Network) and a 5G core network (5GC: 5G Core Network).
  • 5GS interworks with existing LTE and can also be connected to non-3GPP wireless access technologies such as Wi-Fi.
  • 5GC is located between NG-RAN and the external packet data network (PDN: Public Data Network) and can provide various types of data services, including voice, to users.
  • the control plane components of 5GC can be considered virtualized network functions (VNFs), and communication between the VNFs is a RESTful-based API exchange where one VNF communicates with other VNFs. It can be considered as providing a service.
  • the API-based communication interface between the VNFs is called SBI (Service Based Interface).
  • Figure 3 is a diagram illustrating an example of interaction between IMS and 5GC according to various embodiments of the present invention.
  • the P-CSCF 320 supporting SBI can communicate with the PCF (Policy Control Function) 330, which can be represented by the reference point N5.
  • the PCF (330) can support policy establishment and distribution for managing network operations
  • the P-CSCF (320) supporting the SBI is an application function that uses services provided by the PCF (330) to other VNFs ( AF: Application Function).
  • HSS 360 supporting SBI can communicate with I/S-CSCF 340 supporting SBI via reference point N70 and IMS AS 350 supporting SBI via reference point N71. there is.
  • the I/S-CSCF 340 supporting SBI and the IMS AS 350 supporting SBI can be regarded as AF using the service provided by the HSS 360 supporting SBI, and the above reference point
  • the functions provided by N70 and N71 may be equivalent to the functions provided by reference point Cx and reference point Sh, respectively.
  • the SIP is an application layer signaling protocol that specifies procedures for intelligent terminals that want to communicate on the Internet to identify each other, find their locations, and create or delete/change multimedia communication sessions between them.
  • SIP is a request/response structure that controls the creation, modification, and termination of multimedia service sessions such as Internet-based conferences, telephone calls, voice mail, event notification, and instant messaging. It can be used for both TCP and UDP, and uses email to distinguish each user.
  • SIP URL similar to the address, services are provided without being dependent on the IP address.
  • SIP is text-based, developed using many parts of HTTP and SMTP, so it is easy to implement, and has the flexibility and scalability to create various services by combining with many other protocols used on the Internet.
  • SIP is a simpler protocol that corresponds to ITU-T's H.323.
  • RFC 2543 After being proposed as RFC 2543 by the IETF MMUSIC (Multiparty Multimedia Session Control) Working Group in 1999, revisions were carried out by a separate ITEF SIP Working Group.
  • the RFC3261 standard was established in July 2002.
  • FIG. 4 is a diagram illustrating an example of a SIP operation procedure in a mobile communication system according to various embodiments of the present disclosure.
  • Alice uses her UE (SIP UE) 410 to call Bob's UE (SIP UE) 440, and to establish the call session, Alice's proxy server (SIP proxy server)
  • SIP proxy server Alice's proxy server
  • the following communication procedure involving 420 and Bob's proxy server (SIP proxy server) 430 may be performed.
  • Step 1 Alice's UE 410 transmits a SIP INVITE request containing an SDP offer, which will be described later, to Alice's proxy server 420.
  • the SIP INVITE may include the SIP URI of the sender (Alice), the SIP URI of the recipient (Bob), and information for establishing a call session.
  • Alice's proxy server 420 receives the SIP INVITE request sent in step 1 and transmits a 100 Trying response to Alice's UE 410.
  • the 100 Trying response means that the INVITE has been received and Alice's proxy server 420 is operating to deliver the INVITE request to the recipient (Bob).
  • Alice's proxy server 420 verifies the network address of Bob's proxy server 430 using a method such as DNS (Domain Name Service) and transmits the SIP INVITE to Bob's proxy server 430. do. At this time, Alice's proxy server 420 may add the network address of Alice's proxy server 420 to the Via header field of the SIP INVITE to be transmitted to Bob's proxy server 430.
  • DNS Domain Name Service
  • Step 4 Bob's proxy server 430 receives the SIP INVITE and sends 100 Trying to Alice's proxy server 420, so that Bob's proxy server 430 receives the SIP INVITE and makes a request. It conveys that processing is in progress.
  • Bob's proxy server 430 uses a database, etc. to check the network address of Bob's UE (440) and transmits the SIP INVITE to Bob's UE (440). At this time, Bob's proxy server 430 may add the network address of Bob's proxy server 430 to the Via header field of the SIP INVITE to be transmitted to Bob's UE 440.
  • Bob's UE 440 receives the INVITE and notifies Bob through sound, vibration, screen, etc. that a call request has been received from Alice. Additionally, Bob's UE 440 notifies Bob's proxy server 430 that the operation is being performed through a 180 Ringing response. At this time, the network address of Bob's proxy server 430 can be identified from the information added to the Via header field in step 5 above.
  • Step 7 Bob's proxy server 430 forwards the received 180 Ringing response to Alice's proxy server 420.
  • the network address of Alice's proxy server 430 can be identified from the information added to the Via header field in step 3 above.
  • Alice's proxy server 420 delivers the received 180 Ringing response to Alice's UE (410).
  • Alice's UE 410 which has received the 180 Ringing response, can inform Alice of this through a ring-back tone.
  • Step 9 When Bob decides to receive the call, Bob's UE 440 notifies that the call has been answered through a 200 OK response including an SDF Answer, which will be described later. As a result, the SDP is delivered from Alice's UE 410 to Bob's UE 440, and then again from Bob's UE 440 to Alice's UE 410, which results in media processing using SDP offer/answer, which will be described later. This corresponds to media capability negotiation.
  • the 200 OK response may include a network address that can communicate directly with Bob's UE 440 in the Contact header field.
  • Step 10 Bob's proxy server 430 forwards the received 200 OK response to Alice's proxy server 420.
  • the network address of Alice's proxy server 430 can be identified from the information added to the Via header field in step 3 above.
  • Alice's proxy server 420 delivers the received 200 OK response to Alice's UE 410.
  • Alice's UE 410 may stop the ring tone and inform Alice that the call has been answered.
  • Alice's UE 410 transmits an ACK message to Bob's UE 440 indicating that the final response (200 OK) has been received.
  • the ACK message uses the network address of Bob's UE (440) included in the Contact header field in step 9, and is sent to Bob's UE (440) without going through Alice's proxy server 420 and Bob's proxy server 430. ) can be transmitted.
  • Alice or Bob can change the characteristics of the media session, and this can be performed with a re-INVITE/200/ACK handshake that includes an SDP offer reflecting the changed characteristics of the media session.
  • Step 13 If Bob ends the call first, Bob's UE 440 transmits a BYE message to Alice's UE 410.
  • Step 14 Alice's UE, which has received the BYE message, sends a 200 OK response indicating receipt of the BYE message, and the call session is terminated.
  • SDP Session Description Protocol
  • SDP Session Description Protocol
  • the SDP is an ASCII sentence-based protocol for describing multimedia sessions and related schedule information.
  • SDP conveys information about the media stream of a multimedia session so that one can participate in the session.
  • a multimedia session is defined as a set of media streams for a duration, and the duration of the session does not need to be continuous.
  • a multicast-based session on the Internet basically has two purposes: a means of notifying the existence and time of the session and a means of conveying session participation information, and in a unicast environment, the latter purpose is the purpose.
  • SDP information content may include the name and purpose of the session, session progress time, session configuration medium, and media reception information.
  • the SDP description is in document form and may include a session-level section and zero or more media descriptions that follow.
  • An example of the SDP description is shown in [Table 1] below.
  • connection-field Information required to establish a network connection.
  • the RTP/AVP refers to the Audio Video Profile of RTP (Real-time Transport Protocol).
  • a communication system may perform agreement on the media session through SDP negotiation in order to provide a service (eg, real-time interaction service).
  • a service eg, real-time interaction service
  • FIG. 5 is a diagram illustrating an example of an SDP negotiation procedure for a real-time interaction service in a communication system according to various embodiments of the present disclosure.
  • FIG. 5 only considers the SDP exchange procedure and does not include the SIP operation procedure described above.
  • SDP negotiation of a real-time interaction service in a communication system may be performed through the following procedure.
  • Step 1 Alice's UE 510 transmits an SDP offer to Bob's UE 520.
  • Video stream 1 UDP port 51372, H.261 codec (payload type 31)
  • Video stream 2 UDP port 53000, MPEG codec (payload type 32)
  • Video stream 2 UDP port 53000, MPEG codec (payload type 32)
  • Step 3 While the call session is in progress, Bob's UE (520) changes the UDP port number through which it receives voice from 49920 to 65422 and adds a separate receive-only voice stream for event reception.
  • Bob's UE 520 creates an SDP offer reflecting the above contents and transmits it to Alice's UE 510.
  • [Table 4] below shows an example of the SDP proposal. Referring to [Table 4] above, Bob proposes media technologies for the following four media streams: ⁇ Voice stream 1: Change UDP port 49920 to 65422, G.711 ulaw codec (G.711)
  • Video stream 2 UDP port 53000, MPEG codec (payload type 32)
  • ⁇ Voice stream 2 UDP port 51434, DTMF (Dual Tone Multiple Frequency) event (payload type 110), receive only (recvonly)
  • Video stream 1 Unopened video stream using H.261 codec (UDP port set to 0)
  • Video stream 2 UDP port 53000, MPEG codec (payload type 32)
  • ⁇ Voice stream 2 UDP port 53122, DTMF (Dual Tone Multiple Frequency) event (payload type 110), sendonly
  • a web application for providing a service (eg, real-time interaction service) in a communication system may be provided from a data channel server (DCS: Data Channel Server).
  • the data channel server may be located in an IMS operator network or a third party network.
  • the web application provided by the data channel server may be referred to as a data channel application (DCA: Data Channel Application).
  • DCA Data Channel Application
  • a terminal participating in a service (e.g., real-time interaction service) provided by the data channel application uses a data channel (DC: Data Channel) with other terminals participating in the same service to directly or intermediately transmit data required by the service.
  • a data channel application may be identified by an application identifier such as an HTTP URL or a URI having a predefined format.
  • an HTTP URL or a URI having a predefined format.
  • FIG. 6 is a diagram illustrating an example of a network structure including a data channel server in a communication system according to various embodiments of the present disclosure.
  • the communication system may include a UE 610 and an IM CN subsystem.
  • UE 610 may communicate via the IM CN subsystem with other UEs located in a remote IMS network 680 and with components of the IM CN subsystem.
  • the IM CN subsystem includes P-CSCF (620), I/S-CSCF (630), IMS AS (640), IMS HSS (650), IMS AGW (660), and/or data channel server (670). It can be included.
  • P-CSCF 620, I/S-CSCF 630, IMS AS 640, IMS HSS 650, and IMS AGW 660 of the communication system of FIG. 6 is e.g.
  • UE 210,310
  • P-CSCF 220,320
  • I/S-CSCF 230, 340
  • IMS AS 240, 350
  • IMS HSS 250, 360
  • IMS AGW 260
  • Data channel server 670 may include a data channel signaling function 671, a data channel application repository 672, a data channel media function 673, and/or an MRF 674.
  • the data channel signaling function 671 may perform the following functions:
  • the data application storage 672 can store and manage data channel applications and may be located inside or outside the data channel server 670.
  • the data channel media function 673 and MRF 674 can perform the following functions:
  • the data channel media function 673 and the MRF (674) provide equivalent functions through different interfaces, and the operator considers compatibility with other network equipment and user terminals to provide the data channel media function 673 and the MRF ( 674) may be included in the data channel server 670, or both may be included.
  • FIG. 7 is a diagram illustrating an example of a protocol stack of a user terminal supporting a data channel application in a communication system according to various embodiments of the present disclosure.
  • video, voice, still images, and text can be encapsulated in an RTP payload and then transmitted as RTP/UDP/IP packets, allowing real-time interaction.
  • Data for real-time interactive application can be transmitted as SCTP/DTLS/UDP/IP packets through data channels.
  • One SCTP association may include one or more data channels, and each data channel may be identified with a stream identifier (stream ID) provided by SCTP.
  • stream ID stream identifier
  • Data for the real-time interaction application may include, for example, pose information indicating the user's location and gaze, tactile information to be used as input to a haptic device, and/or various sensor information.
  • a user terminal can download a data channel application from a data channel server through a bootstrap data channel.
  • the bootstrap data channel may use HTTP as an internal protocol (subprotocol) of the SCTP stream, and communication including data channel application download between the user terminal and the data channel server uses typical HTTP requests and responses. It can be done.
  • the terminal can download HTML web documents, JavaScript, images, style sheets, etc. that make up the data channel application by sending a root URL (“/”) request to the bootstrap data channel.
  • FIGS. 8A and 8B are diagrams illustrating an example of a procedure for obtaining a data channel application for a terminal in a communication system according to various embodiments of the present disclosure.
  • the terminal can acquire a data channel application through the following procedure.
  • a portal data channel application is illustrated as an example of a data channel application, but the present invention is not limited thereto.
  • the embodiment of FIG. 8 may be applied not only to a portal data channel but also to an individual data channel application, which will be described later. That is, the data channel application in the embodiment of FIG. 8 may be a portal data channel application or an individual data channel application.
  • the user terminal (UE#1) 610 transmits a SIP INVITE request including an SDP proposal to the IMS AS 640 via the P-CSCF 620 and I/S-CSCF 630.
  • the "a max-message-size:” property
  • the "a sctp-port:” property
  • the data channel stream identifier of the bootstrap data channel may be mapped to the data channel application provider.
  • the data channel stream identifier “0” is the network operator to which the user terminal 610 is registered
  • “10” is a subscriber of the network operator to which the user terminal 610 is registered
  • “100” is the remote operator.
  • Network operator 680, “110” may represent a subscriber of the remote network operator 680. Therefore, the media technology in [Table 6] proposes all possible providers of the four data channel applications.
  • a terminal participating in a service eg, real-time interaction service
  • may further include an "a targetApp:" attribute, which will be described later, in the SDP proposal for acquiring a data channel application.
  • IMS AS which has received the SIP INVITE request, analyzes the bootstrap data channel media technology of the SDP proposal and communicates with the data channel server 670 to open a bootstrap data channel and perform data channel application. Allocate resources for distribution. For example, according to the operator policy, the IMS AS 640 may determine that the data channel application first provided to the call session is an application provided by the network operator (e.g., stream identifier (data channel stream identifier) "0" or "100") - Step 3: IMS AS 640 modifies the bootstrap data channel media description of the SDP proposal and transmits a SIP INVITE request including this to I/S-CSCF 630.
  • the network operator e.g., stream identifier (data channel stream identifier) "0" or "100
  • the SDP proposal modification may include the above-described operator policy or the resource allocation results of the data channel server 670.
  • I/S-CSCF 630 transmits a SIP INVITE request including the modified SDP (modified SDP proposal) to the receiving network 680.
  • the receiving network 680 may be referred to as a terminating network.
  • Step 5 SIP operation of the receiving network 680 is performed.
  • the receiving UE transmits an 18x response to the I/S-CSCF (630) through the receiving network (680).
  • the 18x response may include an answer (SDP response) to the SDP offer related to the bootstrap data channel.
  • I/S-CSCF (630) transmits the 18x response including the SDP response to IMS AS (640).
  • IMS AS 640 analyzes the SDP response and, if necessary, according to the analysis result, communicates with the data channel server 670 to reallocate resources related to the bootstrap data channel and modify the SDP response.
  • IMS AS 640 transmits the 18x response including the SDP response (or modified SDP response) to the user UE 610 through the I/S-CSCF 640 and P-CSCF 620. do.
  • Step 10 The remaining call session establishment procedures between the originating network (originating network) and the receiving network (receiving network) are performed.
  • Data channel applications can be provided to the sending terminal and the receiving terminal by the DCS (680).
  • a DCA acquisition procedure from the sending DCS may be performed (Alt#1).
  • a bootstrap data channel (e.g., bootstrap DC with data channel stream identifier (stream ID) “0”) may be established between the user UE 610 and the originating DCS 670, and the user UE ( 610) may request DCA to the originating DCS 670 through the established bootstrap data channel and obtain (e.g., download) the DCA from the originating DCS 670.
  • stream ID data channel stream identifier
  • a bootstrap data channel (e.g., bootstrap DC with data channel stream identifier (stream ID) “100”) may be established between the sending DCS 670 and the receiving user UE 680, and the user UE 680 may request DCA from the originating DCS 670 through the established bootstrap data channel and obtain (e.g., download) the DCA from the originating DCS 670.
  • a DCA acquisition procedure from the receiving DCS may be performed (Alt#2).
  • a bootstrap data channel (e.g., bootstrap DC with data channel stream identifier (stream ID) “100”) may be established between the user UE 610 and the receiving DCS 680, and the user UE ( 610) may request DCA to the receiving DCS 680 through an established bootstrap data channel and obtain (e.g., download) the DCA from the receiving DCS 680. Additionally, the receiving user UE may obtain DCA from the receiving DCS (680).
  • the procedure for acquiring DCA from the receiving DCS 680 of the receiving user of Alt #2 may be the same as the procedure for obtaining DCA from the transmitting DCS 670 of the transmitting user of Alt # 1 described above.
  • a bootstrap data channel (e.g., bootstrap DC with data channel stream identifier (stream ID) “0”) may be established between the receiving user UE and the receiving DCS 680, and the receiving user UE may be established.
  • the UE may request DCA from the receiving DCS 680 through the established bootstrap data channel and obtain (e.g. download) the DCA from the receiving DCS 680.
  • the data channel application acquisition procedure of FIGS. 8A/8B described above may omit some of the steps described above and/or may further include additional steps. Additionally, the above-described steps of the data channel application acquisition procedure of FIGS. 8A/8B may be performed in a different order than that shown. Additionally, the embodiment of the data channel application acquisition procedure of FIGS. 8A/8B is similar to the embodiment of the individual data channel application acquisition procedure of FIG. 9, which will be described later, and/or the embodiment of the individual data channel application acquisition procedure of FIG. 10, which will be described later. They can be used in combination/modified with each other within the scope of non-contradiction.
  • a data channel application for providing a service may provide an entry point (e.g., HTTP URL) to enter another data channel application.
  • an entry point e.g., HTTP URL
  • a data channel application that includes an entry point to another data channel application is referred to as a portal data channel application
  • a data channel application accessible through the portal data channel application is referred to as an individual data channel application. refers to
  • Web applications hosted on the Internet can be identified and obtained by HTTP URL, and in order for multiple users to use services provided by the same web application, services such as URLs must be provided through a separate method not provided by the web application. Access information may be shared.
  • Data channel applications utilizing the IMS data channel can be selected by the operator based on call context information (e.g., user identifier), and the selected data channel application is selected by the data channel server through a special-purpose data channel called a bootstrap data channel.
  • the terminal can download HTML web documents, JavaScript, images, style sheets, etc. that make up the data channel application by sending a root URL (“/”) request to the bootstrap data channel.
  • the same individual data channel application or individual data channel applications that are linked according to the service provider's intention must be provided.
  • the root URL does not contain information that can identify an individual data channel application, it contains information that can identify the application that is the same as the individual data channel application selected in real time by the user during a call or an application that is linked according to the service provider's intention. A means of conveying it to the other party is required.
  • the entry point for the individual data channel application is, for example, the DNS of the user network or the user terminal. It may be an interpretable HTTP URL or an application identifier that can identify an individual data channel application selected by the data channel server 670.
  • the ⁇ host> part that makes up the HTTP URL can be included, and the ⁇ path> part can be omitted.
  • the individual data channel application may be acquired through the same bootstrap data channel as the bootstrap data channel used to acquire the portal data channel application or a separate bootstrap data channel.
  • the user terminal or network transmits an SDP proposal to the other user terminal and/or network and acquires an open data channel application using the separate bootstrap data channel according to the other party's SDP response. can be started.
  • FIG. 9 is a diagram illustrating an example of a terminal-led procedure for acquiring an individual data channel application in a communication system according to various embodiments of the present disclosure.
  • distribution of individual data channel applications is performed through the data channel server of the sending network operator, but the present invention is not limited thereto.
  • distribution of individual data channel applications may be accomplished through the data channel server of the receiving network operator.
  • terminals participating in a service can obtain the same or related individual data channel application through the following procedure.
  • the user or user terminal (UE#1) 610 may select an individual data channel application from the portal data channel application.
  • the portal data channel application recognizes that an individual data channel application selection event has occurred through the user interface, triggers a SIP INVITE transmission suggesting the addition of a new bootstrap data channel in response to the selection event, and triggers a new bootstrap data channel application.
  • application logic that requests acquisition of individual data channel applications through the corresponding bootstrap data channel can be provided.
  • the application logic may be a JavaScript code included in the portal data channel application or a combination of JavaScript code included in the portal data channel application and another software module of the user terminal.
  • the portal data channel application may provide an HTTP URL or application identifier to identify the individual data channel application as an attribute for the selection event.
  • the user terminal 610 sends a SIP INVITE request containing an SDP proposal for adding a new bootstrap data channel to the IMS AS 640 through the P-CSCF 620 and the I/S-CSCF 630.
  • SIP reINVITE request e.g. SIP reINVITE request
  • the new bootstrap data channel may be a bootstrap data channel for a selected individual data channel application.
  • a bootstrap data channel for distributing the identified individual data channel application may be opened, and resources for distributing the individual data channel application may be allocated.
  • provision of other individual data channel applications related to the individual data channel application to be provided to the calling terminal 610 can be prepared.
  • IMS AS 640 may modify the bootstrap data channel media technology of the SDP proposal and transmit a SIP INVITE request (e.g., SIP reINVITE request) including this to the I/S-CSCF 630.
  • SDP proposal modification modified SDP proposal
  • step 5 of FIG. 9 may be the same as step 4 of FIG. 8A
  • step 6 of FIG. 9 may be the same as step 5 of FIG. 8A
  • step 7 of FIG. 9 may be the same as step 6 of FIG. 8.
  • Step 8 of FIG. 9 may be the same as step 7 of FIG. 8A
  • step 9 of FIG. 9 may be the same as step 8 of FIG. 8A
  • step 11 of FIG. 9 may be the same as step 10 of FIG. 8A.
  • steps 12 to 15 of FIG. 9 may be the same as the DCA retrieval procedure (alt #1) from the originating DCS in step 11 of FIG. 8B.
  • the individual data channel application acquisition procedure of FIG. 9 described above may omit some of the steps described above and/or may further include additional steps. Additionally, the above-described steps of the individual data channel application acquisition procedure of FIG. 9 may be performed in an order different from the order shown.
  • the embodiment of the individual data channel application acquisition procedure of FIG. 9 is different from the embodiment of the data channel application acquisition procedure of FIGS. 8A/8B described above and/or the embodiment of the individual data channel application acquisition procedure of FIG. 10 to be described later. They can be used in combination/modified with each other within the scope of non-contradiction.
  • FIG. 10 is a diagram illustrating an example of a server-driven procedure for acquiring an individual data channel application in a communication system according to various embodiments of the present disclosure.
  • distribution of individual data channel applications is performed through the data channel server of the sending network operator, but the present invention is not limited to this.
  • distribution of individual data channel applications may be accomplished through the data channel server of the receiving network operator.
  • terminals participating in a service can acquire the same or related individual data channel application through the following procedure.
  • the user or user terminal (UE#1) 610 may select an individual data channel application from the portal data channel application.
  • the portal data channel application may recognize that an individual data channel application selection event has occurred through the user interface and provide an HTTP URL or application identifier to identify the individual data channel application corresponding to the selection event.
  • the user terminal 610 may transmit an HTTP Request (e.g., HTTP GET Request) to acquire an individual data channel application to the bootstrap data channel (e.g., stream id 0) that downloaded the portal data channel application. there is.
  • HTTP Request e.g., HTTP GET Request
  • the bootstrap data channel e.g., stream id 0
  • the data channel server 670 which has received the HTTP Request request, opens a new bootstrap data channel for distributing the requested individual data channel application and allocates resources for distributing the individual data channel application. You can.
  • the data channel server 670 can prepare to provide the individual data channel application requested through the HTTP Request to both the sending terminal 610 and the receiving terminal 680.
  • the data channel server 670 provides the individual data channel application requested in the HTTP Request to the sending terminal 610 and sends the sending terminal 680 to the receiving terminal 680 according to the intention of the business operator or real-time interaction service provider. Provision of other individual data channel applications related to the individual data channel application to be provided to the side terminal 610 may be prepared.
  • the data channel server 670 may send a Redirection 3xx response to the sending terminal 610 in response to the request for acquiring an individual data channel application in step 2.
  • the sending terminal 610 which has received the Redirection 3xx response, may request acquisition of an individual data channel application through the new bootstrap data channel after the new bootstrap data channel setup is completed.
  • the data channel server 670 may report the resource allocation result to the IMS AS (640). Before reporting the resource allocation results, a parameter adjustment process for resource allocation between the IMS AS 640 and the data channel server 670 may be performed.
  • IMS AS transmits a SIP INVITE including an SDP offer for adding a new bootstrap data channel to the receiving terminal (610) and the sending terminal (680).
  • the new bootstrap data channel may be a bootstrap data channel for a selected individual data channel application.
  • a call session modification procedure is performed, including a process where the receiving terminal 610 and the calling terminal 680 transmit an SDP response to the SDP proposal.
  • steps 7 to 10 of FIG. 10 may be the same as the DCA retrieval procedure (alt #1) from the originating DCS in step 11 of FIG. 8B.
  • the individual data channel application acquisition procedure of FIG. 10 described above may omit some of the steps described above and/or may further include additional steps. Additionally, the above-described steps of the individual data channel application acquisition procedure of FIG. 10 may be performed in a different order than that shown. Additionally, the embodiment of the individual data channel application acquisition procedure of FIG. 10 does not contradict the embodiment of the data channel application acquisition procedure of FIGS. 8A/8B and/or the embodiment of the individual data channel application acquisition procedure of FIG. 9 described above. They can be used in combination/modified with each other within the scope not permitted.
  • a bootstrap data channel for individual data channel application transmission is an SDP offer/response (Offer)/response ( Answer) It can be established through a process.
  • SDP offer/response Offer
  • Answer Answer
  • - StreamID Data channel stream identifier for bootstrap data channel identification.
  • AppID Identifier of the individual data channel application that the terminal will acquire as a bootstrap data channel identified by StreamID.
  • the format of AppID may be HTTP URL or URI (Uniform Resource Identifier).
  • AppID may include the ⁇ host> part that makes up the HTTP URL, and the ⁇ path> part may be omitted.
  • - TransactionID Identifier of the HTTP request (HTTP request message) sent by the terminal to the bootstrap data channel through which the portal data channel application is transmitted in order to acquire an individual data channel application.
  • Source Identifier of the service participant (e.g., real-time interaction service participant) who selected the individual data channel application.
  • Source may be a SIP URI, a network identifier, or a display name given by the application.
  • a user terminal participating in a service (e.g., real-time interaction service) in a communication system may make an SDP proposal (e.g., an SDP proposal in step 1 of FIG. 8A, an SDP proposal in step 2 of FIG. 9) etc.) may include bootstrap data channel media technology for individual data channel application transmission.
  • AppID Identifier of the individual data channel application selected by the user or user terminal.
  • AppID is the application logic included in the portal data channel application (for example, JavaScript code included in the portal data channel application or a combination of JavaScript code included in the portal data channel application and other software modules of the user terminal), real-time interaction It may be a value obtained in real time through a separate communication channel with the service provider, or it may be a preset value.
  • the format of the AppID may be HTTP URL or URI (Uniform Resource Identifier).
  • AppID may include the ⁇ host> part that makes up the HTTP URL and the ⁇ path> part may be omitted.
  • Source Identifier of the service participant (e.g., real-time interaction service participant) who selected the individual data channel application.
  • Source may be a SIP URI, a network identifier, or a display name given by the application. Source is optionally included depending on the application.
  • an IMS network including a data channel server for a service may generate an SDP proposal (e.g., SDP proposal in step 3/4 of FIG. 8A, FIG. 9 SDP proposal of step 4/5, SDP proposal of step 5 of FIG. 10, etc.) or SDP response (e.g., SDP response of step 6/7 of FIG. 8A, SDP response of step 8/9 of FIG. 8A, FIG. 9
  • SDP response of step 7 may include a bootstrap data channel media technology for individual data channel application transmission.
  • - StreamID Data channel stream identifier for bootstrap data channel identification.
  • AppID Identifier of the individual data channel application to be transmitted on the bootstrap data channel.
  • AppID is the application logic of the data channel server for the portal data channel application (for example, monitoring and parameter extraction of individual data channel application acquisition requests received by the portal data channel application through the transmitted bootstrap data channel), real-time interaction service provider and It may be a value acquired in real time through a separate communication channel, etc., or it may be a preset value. SDP proposals with different AppID values may be sent to the same service participant (eg, the same real-time interaction service participant).
  • the format of the AppID may be HTTP URL or URI (Uniform Resource Identifier). When using the above HTTP URL, the ⁇ host> part that makes up the HTTP URL can be included and the ⁇ path> part can be omitted.
  • - TransactionID Identifier of the individual data channel application acquisition request received through the bootstrap data channel transmitted by the portal data channel application, and is optionally included depending on the application.
  • Source Identifier of the service participant (e.g., real-time application service participant) who requested acquisition of an individual data channel application through the bootstrap data channel through which the portal data channel application was transmitted.
  • Source may be a SIP URI, a network identifier, or a display name given by the application. Source is optionally included depending on the application.
  • a data channel application and resources referenced by the data channel may be identified by an http URL, and the user terminal may generate a resource acquisition request message using the http URL.
  • the path through which the user terminal will transmit the resource acquisition request message can be determined as follows:
  • the IMS AS and/or data channel server may establish a list of URLs that can process acquisition requests received on a specific bootstrap data channel.
  • the URL may include the ⁇ host> part, and the ⁇ path> part may be omitted.
  • the user terminal can obtain mappin information of the bootstrap data channel (Stream ID) and URL list through the IMS network.
  • the information acquisition process may be an IMS network registration process of the terminal, direct communication between the IMS AS and the terminal, SDP proposal/request exchange with the data channel server, and/or a terminal setup procedure of the network operator.
  • the user terminal may identify a bootstrap data channel to transmit the resource acquisition request message by comparing the http URL included in the resource acquisition request message with the mapping information.
  • the user terminal can resolve the http URL using a DNS (Domain Name System) server provided by the network operator.
  • DNS Domain Name System
  • the bdcDomain parameter in [Table 7] above can be used as follows: - “all” is the bootstrap data that requests for all resources referred to by the data channel application obtained by the bootstrap data channel identified by stream-id are the same This may mean that it must be transmitted through a channel.
  • portion may mean that only requests for some of the resources referenced by the data channel application obtained through the bootstrap data channel identified by stream-id should be transmitted to the same bootstrap data channel.
  • the 'pos-list' parameter can contain a list of URLs to which requests should be sent to the bootstrap channel identified by stream-id.
  • the 'neg-list' parameter may contain a list of URLs that should not send requests to the bootstrap channel identified by stream-id.
  • URLs included in the 'pos-list' and 'neg-list' may include the ⁇ host> part and the ⁇ path> part may be omitted.
  • a user terminal may acquire an individual data channel application through a second bootstrap data channel that is different from the first bootstrap data channel for acquiring the portal data channel application.
  • FIG. 11 is a diagram illustrating the structure of a terminal according to various embodiments of the present disclosure.
  • the terminal may include a transceiver 1110, a control unit 1120, and a storage unit 1130.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 1110 can transmit and receive signals with other entities.
  • the transceiver 1110 may receive data from, for example, a base station or a network entity.
  • the control unit 1120 can control the overall operation of the terminal according to the embodiment proposed by the present disclosure.
  • the control unit 1120 may control signal flow between each block to perform the operations according to FIGS. 1 to 10 described above.
  • the terminal or control unit 1120 may select an individual data channel application based on the portal data channel application provided through the first bootstrap data channel.
  • the terminal or control unit 1120 may transmit an SDP proposal associated with the second bootstrap data channel for the selected individual data channel application to the first network entity.
  • the terminal or control unit 1120 may receive an SDP response corresponding to the SDP proposal from the first network entity.
  • the terminal or control unit 1120 may obtain the individual data channel application through the second bootstrap data channel based on the SDP response.
  • the SDP proposal includes a media description for the second bootstrap data channel, wherein the media description includes a target application property, wherein the target application property is: to identify the selected individual data channel application. May include application identifier information.
  • the target application properties include: data channel stream identifier information for identifying the second bootstrap data channel; And it may further include identifier information for identifying the service participant who selected the individual data channel application.
  • the SDP proposal may be included in a SIP INVITE request message or a SIP reINVITE request message.
  • the storage unit 1130 may store at least one of information transmitted and received through the transmitting and receiving unit 1110 and information generated through the control unit 1120.
  • the storage unit 1130 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 10.
  • FIG. 12 is a diagram illustrating the structure of an IMS AS according to various embodiments of the present disclosure.
  • the IMS AS may include a transceiver 1210, a control unit 1220, and a storage unit 1230.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 1210 can transmit and receive signals with other entities.
  • the transceiver unit 1210 may receive data from a terminal or network entity.
  • the control unit 1220 can control the overall operation of the IMS AS according to the embodiment proposed by the present invention.
  • the control unit 1220 may control signal flow between each block to perform the operations according to FIGS. 1 to 10 described above.
  • the IMS AS or control unit 1220 receives from the terminal an SDP proposal associated with a second bootstrap data channel for a selected individual data channel application selected based on the portal data channel application provided through the first bootstrap data channel. can do.
  • the IMS AS or control unit 1220 may modify the SDP proposal and transmit the modified SDP proposal to the second terminal.
  • the IMS AS or control unit 1220 may include transmitting an SDP response corresponding to the SDP proposal to the terminal.
  • the SDP proposal and the modified SDP proposal each include a media description for the second bootstrap data channel, each media description includes a target application property, and each target application property is: the selected individual It may contain application identifier information to identify the data channel application.
  • the value of the application identifier information included in the target application attribute of the SDP proposal may be different from the value of the application identifier information included in the target application attribute of the modified SDP proposal.
  • each target application attribute includes: data channel stream identifier information for identifying the second bootstrap data channel; And it may further include identifier information for identifying the service participant who selected the individual data channel application.
  • the SDP proposal may be included in a SIP INVITE request message or a SIP reINVITE request message.
  • the storage unit 1230 may store at least one of information transmitted and received through the transmitting and receiving unit 1210 and information generated through the control unit 1220.
  • the storage unit 1230 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 10.
  • FIG. 13 is a diagram illustrating the structure of a data channel server according to various embodiments of the present disclosure.
  • the data channel server may include a transceiver 1310, a control unit 1320, and a storage unit 1330.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 1310 can transmit and receive signals with other entities.
  • the transceiver unit 1310 may receive data from a terminal or network entity.
  • the control unit 1320 can control the overall operation of the data channel server according to the embodiment proposed by the present disclosure.
  • the control unit 1320 may control signal flow between each block to perform the operations according to FIGS. 1 to 10 described above.
  • the data channel server or control unit 1320 sends a request for an individual data channel application selected based on the portal data channel application through the first bootstrap data channel used to provide the portal data channel application. It can be received from.
  • the data channel server or control unit 1320 may allocate resources for a second bootstrap data channel for the selected individual data channel based on the request.
  • the data channel server or control unit 1320 may transmit information about the allocated resources to a second network entity.
  • the information about the allocated resources is used in the second network entity to generate an SDP proposal associated with the second bootstrap data channel, and the generated SDP proposal is transmitted to the terminal and the second terminal. It can be.
  • the SDP proposal each includes a media description for the second bootstrap data channel, wherein the media description includes a target application property, wherein the target application property: identifies the selected individual data channel application. May include application identifier information for
  • the value of the application identifier information included in the target application attribute of the SDP proposal transmitted to the terminal may be different from the value of the application identifier information included in the target application attribute of the SDP proposal transmitted to the second terminal.
  • the target application properties include: data channel stream identifier information for identifying the second bootstrap data channel; And it may further include identifier information for identifying the service participant who selected the individual data channel application.
  • the SDP proposal may be included in a SIP INVITE request message.
  • the storage unit 1330 may store at least one of information transmitted and received through the transmitting and receiving unit 1310 and information generated through the control unit 1320.
  • the storage unit 1330 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 10.
  • FIG. 14 is a diagram illustrating the structure of a network entity according to various embodiments of the present disclosure.
  • the network entity in FIG. 14 may be, for example, one of the base stations of FIGS. 1 to 10, P-CSCF, I/S-CSCF, IMS HSS, IMS-AGW, 5G NF(s), and DC application server.
  • the network entity may include a transceiver 1410, a control unit 1420, and a storage unit 1430.
  • the control unit may be defined as a circuit or application-specific integrated circuit or at least one processor.
  • the transceiver unit 1410 can transmit and receive signals with other entities.
  • the transceiver unit 1410 may receive data from a terminal or another network entity.
  • the control unit 1420 can control the overall operation of the network entity according to the embodiment proposed by the present invention.
  • the control unit 1420 may control signal flow between each block to perform the operations according to FIGS. 1 to 10 described above.
  • the storage unit 1430 may store at least one of information transmitted and received through the transmitting and receiving unit 1410 and information generated through the control unit 1420.
  • the storage unit 1430 may store information/data/commands, etc. for performing the operations according to FIGS. 1 to 10.
  • Electronic devices that implement, operate, and perform various embodiments of the present disclosure may be of various types.
  • Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances.
  • portable communication devices e.g., smartphones
  • computer devices e.g., smartphones
  • portable multimedia devices e.g., portable medical devices
  • cameras e.g., wearable devices, or home appliances.
  • Electronic devices according to embodiments of the present disclosure are not limited to the above-described devices.
  • first, second, or first or second may be used simply to distinguish one component from another, and to refer to those components in other respects (e.g., importance or order) is not limited.
  • One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.”
  • module used in various embodiments of the present disclosure may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used negatively.
  • a module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions.
  • the module may be implemented in the form of an application-specific integrated circuit (ASIC).
  • ASIC application-specific integrated circuit
  • a storage medium e.g., internal memory or external memory
  • a machine e.g., electronic device
  • a processor e.g., processor
  • a device e.g. electronic device
  • the one or more instructions may include code generated by a compiler or code that can be executed by an interpreter.
  • a storage medium that can be read by a device may be provided in the form of a non-transitory storage medium.
  • 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between cases where it is temporarily stored.
  • signals e.g. electromagnetic waves
  • methods according to various embodiments of the present disclosure may be included and provided in a computer program product.
  • Computer program products are commodities and can be traded between sellers and buyers.
  • the computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or through an application store (e.g. Play StoreTM) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online.
  • a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
  • each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components.
  • one or more of the components or operations described above may be omitted, or one or more other components or operations may be added.
  • multiple components eg, modules or programs
  • the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components prior to the integration. .
  • operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or , or one or more other operations may be added.

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)

Abstract

La présente divulgation concerne un système de communication 5G ou 6G destiné à prendre en charge un débit supérieur de transmission de données. Un procédé relatif à un terminal dans un système de communication de la présente divulgation comprend les étapes consistant à : sélectionner une application de canal de données individuelle en fonction d'une application de canal de données de portail fournie par l'intermédiaire d'un premier canal de données d'amorçage ; transmettre à une première entité réseau une recommandation SDP associée à un deuxième canal de données d'amorçage pour l'application de canal de données individuelle sélectionnée ; recevoir une réponse SDP correspondant à la recommandation SDP provenant de la première entité de réseau ; et, selon la réponse SDP, acquérir l'application de canal de données individuelle par l'intermédiaire du deuxième canal de données d'amorçage.
PCT/KR2023/017238 2022-11-02 2023-11-01 Procédé et dispositif pour fournir une application de canal de données dans un système de communication mobile WO2024096562A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020220144314A KR20240062604A (ko) 2022-11-02 2022-11-02 이동 통신 시스템에서 데이터 채널 응용 제공 방법 및 장치
KR10-2022-0144314 2022-11-02

Publications (1)

Publication Number Publication Date
WO2024096562A1 true WO2024096562A1 (fr) 2024-05-10

Family

ID=90931091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/017238 WO2024096562A1 (fr) 2022-11-02 2023-11-01 Procédé et dispositif pour fournir une application de canal de données dans un système de communication mobile

Country Status (2)

Country Link
KR (1) KR20240062604A (fr)
WO (1) WO2024096562A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021112727A1 (fr) * 2019-12-03 2021-06-10 Telefonaktiebolaget Lm Ericsson (Publ) Premier nœud de réseau, second dispositif sans fil et procédés mis en œuvre dans ceux-ci
WO2022033278A1 (fr) * 2020-08-11 2022-02-17 华为技术有限公司 Procédé et dispositif de communication à base d'un canal de données ims

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021112727A1 (fr) * 2019-12-03 2021-06-10 Telefonaktiebolaget Lm Ericsson (Publ) Premier nœud de réseau, second dispositif sans fil et procédés mis en œuvre dans ceux-ci
WO2022033278A1 (fr) * 2020-08-11 2022-02-17 华为技术有限公司 Procédé et dispositif de communication à base d'un canal de données ims

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (Release 18)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 26.114, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG4, no. V18.0.0, 23 September 2022 (2022-09-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 484, XP052210981 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system architecture enhancement for next generation real time communication; Phase 2 (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-87, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.0.0, 5 September 2022 (2022-09-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 112, XP052211590 *
YI JIANG, CHINA MOBILE, HUAWEI, HISILICON, ZTE: "KI#1, Update of solution #20.", 3GPP DRAFT; S2-2209041; TYPE PCR; FS_NG_RTC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Online; 20221010 - 20221017, 30 September 2022 (2022-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052208801 *

Also Published As

Publication number Publication date
KR20240062604A (ko) 2024-05-09

Similar Documents

Publication Publication Date Title
WO2018236145A1 (fr) Appareil et procédé de découverte de services de liaison montante et d'accès à ceux-ci dans un système de communication sans fil
US10341610B2 (en) Method and apparatus using an integrated femtocell and residential gateway device
WO2017138782A1 (fr) Procédés et appareil permettant d'améliorer la fourniture d'un contenu mbms et son introduction
WO2022211476A1 (fr) Procédé et appareil pour prendre en charge une téléconférence et une téléprésence contenant de multiples vidéos à 360 degrés
EP3311534A1 (fr) Procédé et appareil pour une distribution multimédia à trajets multiples
US11330041B2 (en) Providing communication services using sets of I/O user devices
WO2015041469A1 (fr) Procédé et système pour intégrer une visualisation de contenu et une communication dans une session de centre social immersif
US9100729B2 (en) Method for handling a telecommunications connection, telecommunications arrangement, switching device and network coupling device
WO2024039173A1 (fr) Procédé et appareil pour fournir des qos à base multimédia pour un service de communication en temps réel dans des systèmes de communication mobile
EP1521412B1 (fr) Commutation entre systèmes de communication avec commutation sur circuits et sur paquets
WO2024096562A1 (fr) Procédé et dispositif pour fournir une application de canal de données dans un système de communication mobile
CN103414867B (zh) 多媒体通话控制方法、终端及系统
WO2017099514A1 (fr) Procédé et dispositif destinés à des services multiples dans un système de communication sans fil
WO2023106721A1 (fr) Procédé et dispositif de fourniture d'un calcul divisé sur la base de la capacité d'un dispositif
WO2022270997A1 (fr) Procédés et appareil permettant une relocalisation d'un service d'application destinée à des services périphériques multimédias
WO2024101855A1 (fr) Procédé et appareil basés sur des supports pour transmettre des données d'ia dans un système de communication mobile
US11637783B2 (en) Providing communication services using sets of I/O user devices
WO2020036428A1 (fr) Procédé de transmission de données non ip dans un réseau 5g
WO2022191401A1 (fr) Dispositif électronique d'invitation à une conférence téléphonique au moyen d'un message textuel et procédé de commande dudit dispositif
WO2024096390A1 (fr) Procédé et dispositif pour effectuer un service d'appel multimédia
WO2023214712A1 (fr) Procédé et appareil permettant de fournir un service de communication en temps réel dans un système de communication sans fil
WO2023003354A1 (fr) Dispositif d'émission de données de nuage de points, procédé d'émission de données de nuage de points, dispositif de réception de données de nuage de points et procédé de réception de données de nuage de points
WO2023153787A1 (fr) Procédés et appareil de gestion de politique dans des applications multimédias à l'aide d'un découpage en tranches de réseau
WO2023014085A1 (fr) Dispositif d'émission de données de nuage de points, procédé d'émission de données de nuage de points, dispositif de réception de données de nuage de points, et procédé de réception de données de nuage de points
WO2023055089A1 (fr) Procédé et système de création, mise à jour et suppression du rattachement d'un alias fonctionnel à un groupe de mcx