Method and apparatus for network-assisted stream synchronization of media services using network slices

Abstract

The present disclosure relates to a 5G or 6G communication system supporting a high data transmission rate. According to an embodiment, a method performed by an Application Function (AF) entity in a mobile communication system is provided. The method includes identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement, and synchronizing the first media data and the second media data.

Description

Technical Field

[0001] The present disclosure generally relates to multimedia devices and processes. More specifically, the present disclosure relates to methods and apparatus for network-assisted stream synchronization of media services using network slicing. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and these technologies can be applied not only to frequency bands "below 6 GHz", such as 3.5 GHz, but also to frequency bands "above 6 GHz", called millimeter waves, including 28 GHz and 39 GHz. In addition, in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology, 6G mobile communication technology (called Beyond 5G System) is considered to be implemented in the terahertz band (e.g., 95 GHz to 3 THz band).

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), standardization of the following technologies is already underway: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, support for dynamic operation of parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats for efficient use of millimeter wave resources, initial access technology supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large amounts of data transmission and polarization codes for highly reliable transmission of control information), L2 preprocessing, and network slicing that provides dedicated networks dedicated to specific services.

[0004] Currently, in view of the services that 5G mobile communication technology will support, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as: V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation in unlicensed frequency bands that complies with various regulatory requirements, NR UE power saving, NTN (Non-Terrestrial Network), which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] In addition, in terms of air interface architecture / protocol, standardization is being conducted on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (NR's 2-step RACH) for simplifying the random access procedure. Standardization is also being conducted on technologies such as the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication system and integrated operations of the connected devices will be necessary. To this end, new research related to the following technologies is planned: extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and RIS (reconfigurable smart surfaces), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for achieving services with a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] According to an embodiment, a method performed by an application function (AF) entity in a mobile communication system is provided. The method includes: identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement, and synchronizing the first media data and the second media data.

[0009] According to an embodiment, an application function (AF) entity in a mobile communication system is provided. The AF entity includes a transceiver and a controller coupled to the transceiver, the controller being configured to: identify first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of a UE via a second network slice configured with a second QoS requirement, and synchronize the first media data with the second media data.

[0010] According to an embodiment, a method performed by a user equipment (UE) in a mobile communication system is provided. The method includes: receiving first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and sending second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data.

[0011] According to an embodiment, a user equipment (UE) in a mobile communication system is provided. The UE includes a transceiver and a controller coupled to the transceiver, the controller being configured to: receive first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and send second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0013] Figure 1 An example communication system according to an embodiment of the present disclosure is shown;

[0014] Figure 2 An example electronic device according to an embodiment of the present disclosure is shown;

[0015] Figure 3 An example electronic device according to an embodiment of the present disclosure is shown;

[0016] Figure 4 An example architecture for enabling edge applications according to the present disclosure is shown;

[0017] Figure 5 An example architecture of media streaming according to the present disclosure is shown;

[0018] Figure 6 An example media communication service utilizing two network slices in accordance with the present disclosure is shown;

[0019] Figure 7 shows example intra-slice synchronization according to the present disclosure;

[0020] Figure 8 shows example inter-slice synchronization according to the present disclosure;

[0021] Fig. 9 An example of multi-slice collaboration for tracking media stream delivery status according to the present disclosure is shown;

[0022] Fig. 10A shows expected flow condition information configured by an application service provider according to the present disclosure;

[0023] Fig. 10B shows expected flow condition information configured by an application service provider according to the present disclosure;

[0024] Fig.11 shows example per-slice message transmission of inter-stream timing relation information according to the present disclosure;

[0025] Fig.12 An example tracking functional group according to the present disclosure is shown;

[0026] Fig.13 shows an example media component flow switching to different network slices according to the present disclosure;

[0027] Fig.14 Example multi-component flow segmentation according to the present disclosure is shown.

[0028] Fig.15 An example buffer compensation of a media component stream according to the present disclosure is shown;

[0029] Fig.16 An example flow chart of stream switching and segmentation for buffer compensation according to the present disclosure is shown;

[0030] Fig.17 An example method of network-assisted stream synchronization of media services using network slicing according to the present disclosure is shown;

[0031] Fig.18A An example workflow relocation according to the present disclosure is shown;

[0032] Fig.18B An example workflow relocation according to the present disclosure is shown;

[0033] Fig.19 shows an example server group relocation according to the present disclosure;

[0034] Fig. 20A shows an example workflow relocation to a user device in accordance with the present disclosure;

[0035] Fig. 20B shows an example workflow relocation to a user device in accordance with the present disclosure;

[0036] Fig. 20C shows an example workflow relocation to a user device in accordance with the present disclosure;

[0037] Fig.21 An example method of network-assisted stream synchronization of media services using network slicing according to the present disclosure is shown;

[0038] Fig. 22 The structure of a UE according to an embodiment of the present disclosure is shown;

[0039] Fig.23 shows the structure of a base station according to an embodiment of the present disclosure; and

[0040] Fig.24 is a block diagram showing the internal structure of a network entity according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] Described below Figures 1 to 24 The various embodiments used to describe the principles of the present disclosure are for illustrative purposes only and should not limit the scope of the present disclosure in any way. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any type of appropriately arranged device or system.

[0042] Network slicing is an architectural enabler that is natively built into 5G systems. Network slicing can help deliver applications with application components that have different QoS requirements, provided that different Quality of Service (QoS) is provided. Many 5G media services that require the delivery of media stream components with different delivery characteristics are being standardized, which can be achieved using multiple network slices. Media service application components delivered using network slicing may arrive at the destination out of order, which makes synchronization of streams important. The present disclosure describes methods and aspects related to synchronization of delivery of different media stream components delivered using different network slices. While traditional synchronization methods rely on techniques managed by clients and servers with packet and frame packing, the present disclosure proposes a network-assisted synchronization method that can be used with client-dependent synchronization methods.

[0043] Specifically, the present disclosure provides synchronization of media streams delivered within the same network slice and between different network slices. The present disclosure also provides slice collaboration to assist in stream synchronization, and provides network assistance to UEs and synchronization information for application buffer management. Inter-slice synchronization and intra-slice synchronization are described for the exchange of stream delivery information. The delivery of media streams transmitted in different slices can be tracked.

[0044] Network slicing is an important architectural enabler for 5G networks. Any service (e.g., a media service) can be delivered to end users in one or more network slices. Each network slice can have a different QoS configuration than other network slices. With the updated 5G architecture, more complex media services that require differentiated QoS treatment of constituent media streams are being developed. Network slicing can be used to provide the required QoS differentiation of different component streams of media services. However, taking advantage of differentiated QoS with network slicing brings service implementation complexities that do not exist using older media delivery technologies. One such complexity is the problem of stream synchronization. 5G media delivery technology using network slicing must solve the problem of stream synchronization, otherwise network slicing cannot be considered an enabler for implementing complex 5G media services.

[0045] When 5G network slicing is used to implement media services, different media component streams of the media service can be delivered to the end user (End User, EU) using different network slices, thereby providing different levels of QoS for different media component streams, which is required for updated 5G media services. For this delivery architecture using network slicing, an important issue that requires immediate attention is stream synchronization. Traditional stream synchronization methods rely on synchronization at the end user, because traditional media services deliver different media stream components that are multiplexed or interleaved as a packet stream, and the UE reassembles and repackages them into different streams at its end. However, in the case of network slicing, where different media streams may be delivered to end users at different levels of QoS, the media stream components are likely to be unavailable at the UE at the required time. The present disclosure proposes a method for stream synchronization in the above scenario.

[0046] The use of computing techniques for media processing is greatly expanding, primarily due to the availability, convenience, computing power, etc. of computing devices. Portable electronic devices, such as laptop computers and mobile smart phones, are becoming increasingly popular as the devices become more compact, while the processing power and resources included in a given device are also increasing. Even with the increase in processing power, portable electronic devices often have difficulty providing the processing power to handle new services and applications, as the newer services and applications often require more resources included in the portable electronic device. Improved methods and apparatus for configuring and deploying media processing in a network are needed.

[0047] Cloud media processing is gaining traction, where media processing workloads are built into a network (e.g., the cloud) to take advantage of the cloud's benefits, such as (theoretically) unlimited computing capacity, need-based automatic scaling, and on-demand processing. End-user clients can request network media processing providers to provision and configure media processing capabilities as needed.

[0048] The following Figure 1-Figure 3 Various embodiments are described that are implemented in a wireless communication system and using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figure 1-Figure 3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0049] The fifth generation (5G) network provides multiple architectural enablers that are not available in the case of old networks. An example of such an architectural enabler is network slicing, where operators can provision multiple logical networks using the same underlying physical and virtual resources. Each slice can provide different levels of QoS, which helps in deploying applications with different QoS requirements. In the case of network slicing, it becomes possible to use different network slices to deliver different data / media streams of applications with different QoS requirements. When such data or media streams of an application are delivered using different network slices, synchronization problems may arise due to different business processing of these streams between each slice. In addition, due to the presence of different virtual and physical computing resources in different network slices and different network configurations of different network slices, the streams delivered in different network slices are likely not to arrive at the required destination at the required time. Therefore, network-assisted synchronization methods are essential to help client-based synchronization methods.

[0050] The present disclosure provides methods and apparatus for network-assisted stream synchronization of media services using network slicing.

[0051] In an embodiment, an apparatus includes a communication interface and a processor operably coupled to the communication interface. The communication interface is configured to receive expected flow parameters of a plurality of media flows provided by at least one network slice from an application service provider. The communication interface is further configured to receive actual flow parameters of each of the media flows. The processor is configured to determine flow transmission condition information of each of the media flows, wherein the flow transmission condition information is based on a comparison of the actual flow parameters with the expected flow parameters. The processor is further configured to perform flow synchronization based on the flow transmission condition information.

[0052] In an embodiment, a method includes receiving expected stream parameters for a plurality of media streams provided through at least one network slice from an application service provider. The method also includes receiving actual stream parameters for each of the media streams. The method also includes determining stream transmission condition information for each of the media streams, wherein the stream transmission condition information is based on a comparison of the actual stream parameters with the expected stream parameters. The method also includes performing stream synchronization based on the stream transmission condition information.

[0053] In an embodiment, an apparatus includes a communication interface and a processor operably coupled to the communication interface. The communication interface is configured to receive streaming condition information from a slice synchronization function, wherein the streaming condition information is based on a comparison of actual stream information of a media stream and expected stream parameters associated with an application service provider. The processor is configured to determine a time to decode and present media content based on the streaming condition information. The processor is further configured to identify a parameter change between a current time and a determined time. The processor is further configured to update a buffer size based on the identified parameter change.

[0054] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.

[0055] Before the detailed description below, it may be helpful to define certain words and phrases used throughout this patent document. "Coupling" and its derivatives refer to direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. "Send", "receive" and "communication" and their derivatives cover both direct and indirect communication. "Include" and "comprise" and their derivatives mean inclusion and not limitation. "Or" is inclusive, meaning "and / or". The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to, connected to, coupled to, coupled to, communicable with, cooperative with, intertwined, juxtaposed, close to, combined with, combined with, have, have... attributes, have a relationship with, have a relationship with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0056] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in a suitable computer-readable program code. "Computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or other types of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and overwritten later, such as rewritable optical discs or erasable storage devices.

[0057] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most, instances, such definitions apply to prior and future uses of such defined words and phrases.

[0058] An apparatus includes a communication interface and a processor operably coupled to the communication interface. The communication interface is configured to receive expected flow parameters of a plurality of media flows provided through at least one network slice from an application service provider. The communication interface is further configured to receive actual flow parameters of each of the media flows. The processor is configured to determine flow transmission condition information for each of the media flows, wherein the flow transmission condition information is based on a comparison of the actual flow parameters with the expected flow parameters. The processor is further configured to perform flow synchronization based on the flow transmission condition information.

[0059] Figure 1 An example communication system 100 is shown in accordance with an embodiment of the present disclosure. Figure 1 The embodiment of the communication system 100 shown is for illustration only. Other embodiments of the communication system 100 may be used without departing from the scope of the present disclosure.

[0060] like Figure 1As shown, the communication system 100 includes a network 102 that facilitates communication between various components in the communication system 100. For example, the network 102 can communicate IP packets, frame relay frames, asynchronous transfer mode (ATM) cells, or other information between network addresses. The network 102 includes all or part of one or more local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), a global network (such as the Internet), or any other communication system at one or more locations.

[0061] For example, the network 102 facilitates communication between the server 104 and various client devices 106-116. The client devices 106-116 may be, for example, smart phones, tablet computers, laptop computers, personal computers, wearable devices, HMDs, etc. The server 104 may represent one or more servers. Each server 104 includes any suitable computing or processing device that can provide computing services to one or more client devices (such as client devices 106-116). For example, each server 104 may include one or more processing devices, one or more memories storing instructions and data, and one or more network interfaces that facilitate communication through the network 102. In an embodiment, each server 104 may include an encoder. In an embodiment, the server 104 may synchronize media component streams sent to the client devices 106-116 through multiple network slices.

[0062] Each client device (or user equipment (UE)) 106-116 represents any suitable computing or processing device that interacts with at least one server (such as server 104) or other computing device through network 102. Client devices 106-116 include desktop computers 106, mobile phones or mobile devices 108 (such as smart phones), PDAs 110, laptop computers 112, tablet computers 114, and / or HMDs 116. However, any other or additional client devices may be used in communication system 100. Smart phones represent a type of mobile device 108 that is a handheld device with an integrated mobile broadband cellular network connection and a mobile operating system for voice, Short Message Service (SMS), and Internet data communications.

[0063] For example, some of the client devices 108-116 communicate indirectly with the network 102. For example, the mobile device 108 and the PDA 110 communicate through one or more base stations 118, such as cellular base stations 120 or eNodeBs (eNBs). Similarly, the laptop 112, the tablet computer 114, and the HMD 116 communicate through one or more wireless access points 120, such as IEEE 802.11 wireless access points. Please note that these are for illustration only, and each client device 106-116 can communicate directly with the network 102 or indirectly with the network 102 through any suitable intermediate device or network.

[0064] In an embodiment, any client device 106-114 securely and efficiently sends information to other devices (such as, for example, server 104). In addition, any client device 106-116 can trigger information transmission between itself and server 104. When attached to a headset via a bracket, any client device 106-114 can operate as a VR display and work similarly to HMD 116. For example, when attached to a bracket system and worn on the user's eyes, mobile device 108 can work similarly to HMD 116. Mobile device 108 (or any other client device 106-116) can trigger information transmission between itself and server 104. In an embodiment, client device 106-114 can receive streaming condition information and update the buffer according to the decoding time indicated by the streaming condition information and the measured time.

[0065] although Figure 1 One example of a communication system 100 is shown, but may be used for Figure 1 Various changes may be made. For example, communication system 100 may include any number of each component in any suitable arrangement. In general, computing and communication systems have a wide variety of configurations, Figure 1 The scope of the present disclosure is not limited to any particular configuration. Figure 1 One operating environment is shown in which the various features disclosed in this patent document may be used, but these features may be used in any other suitable system.

[0066] Figure 2 and Figure 3 An example electronic device according to an embodiment of the present disclosure is shown. Specifically, Figure 2 An example server 200 is shown, which may represent Figure 1 Server 200 may represent one or more encoders, decoders, local servers, remote servers, cluster computers, and components of a single pool, cloud-based servers that act as seamless resources, etc. Server 200 may be composed of Figure 1 One or more of the client devices 106-116 or other servers access.

[0067] like Figure 2 As shown, the server 200 includes a bus system 205 that supports communication between at least one processing device (such as a processor 210 ), at least one storage device 215 , at least one communication interface 220 , and at least one input / output (I / O) unit 225 .

[0068] The processor 210 executes instructions that may be stored in the memory 230. The processor 210 may include any suitable number and type of processors or other devices in any suitable arrangement. Example types of processors 210 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuits. In an embodiment, the processor 210 may support synchronization of media streams transmitted over the same or separate network slices.

[0069] Memory 230 and persistent storage 235 are examples of storage devices 215, which represent any structure capable of storing and facilitating retrieval of information (such as data, program code, or other suitable information, whether temporary or permanent). Memory 230 may represent random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 235 may include one or more components or devices that support long-term storage of data, such as read-only memory, a hard disk, flash memory, or an optical disk.

[0070] Communication interface 220 supports communication with other systems or devices. For example, communication interface 220 may include interfaces that facilitate Figure 1 The communication interface 220 may include a wireless transceiver or network interface card for communication over the network 102. The communication interface 220 may support communication over any suitable physical or wireless communication link. For example, the communication interface 220 may send information associated with network-assisted stream synchronization of a media service using network slicing to other devices such as one of the client devices 106-116.

[0071] I / O unit 225 allows input and output of data. For example, I / O unit 225 can provide a connection for user input via a keyboard, mouse, keypad, touch screen or other suitable input device. I / O unit 225 can also send output to a display, printer or other suitable output device. However, it is noted that I / O unit 225 can be omitted, such as when I / O interaction with server 200 occurs via a network connection.

[0072] Note that although Figure 2 Described as indicating Figure 1104, but the same or similar structure can be used in one or more of the various client devices 106-116. For example, a desktop computer 106 or a laptop computer 112 can have a Figure 2 The same or similar structure shown.

[0073] Figure 3 An example electronic device 300 is shown, which may represent Figure 1 The electronic device 300 may be a mobile communication device, such as, for example, a mobile station, a subscriber station, a wireless terminal, a desktop computer (similar to Figure 1 Desktop computer 106 in, portable electronic device (similar to Figure 1 108, PDA 110, laptop computer 112, tablet computer 114 or HMD 116), etc. In an embodiment, Figure 1 One or more of the client devices 106-116 may include the same or similar configuration as the electronic device 300. In an embodiment, the electronic device 300 is an encoder, a decoder, or both. For example, the electronic device 300 is suitable for data transmission, image or video compression, image or video decompression, encoding, decoding, and media rendering applications.

[0074] The RF transceiver 310 receives an incoming RF signal from an antenna 305 transmitted from an access point (such as a base station, a Wi-Fi router, or a Bluetooth device) or other devices of the network 102 (such as Wi-Fi, Bluetooth, cellular, 5G, LTE, LTE-A, WiMAX, or any other type of wireless network). The RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency or baseband signal. The intermediate frequency or baseband signal is sent to the RX processing circuit, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or intermediate frequency signal. The RX processing circuit sends the processed baseband signal to the speaker 330 (such as for voice data) or to the processor 340 for further processing (such as for web browsing data).

[0075] The TX processing circuit receives analog or digital voice data from microphone 320, or other outgoing baseband data from processor 340. The outgoing baseband data may include web page data, email, or interactive video game data. The TX processing circuit encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or intermediate frequency signal. The RF transceiver 310 receives the outgoing processed baseband or intermediate frequency signal from the TX processing circuit and up-converts the baseband or intermediate frequency signal to an RF signal that is transmitted through antenna 305.

[0076] The processor 340 may include one or more processors or other processing devices. The processor 340 may execute instructions stored in the memory 360, such as the OS 361, to control the overall operation of the electronic device 300. For example, the processor 340 may control the reception of the forward channel signal and the transmission of the reverse channel signal of the RF transceiver 310 according to well-known principles. The processor 340 may include any suitable number and type of processors or other devices of any suitable arrangement. For example, in an embodiment, the processor 340 includes at least one microprocessor or microcontroller. Example types of processors 340 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuits. In an embodiment, the processor 340 may synchronize media streams delivered through separate network slices.

[0077] The processor 340 is also capable of executing other processes and programs residing in the memory 360, such as operations of receiving and storing data. The processor 340 can move data into or out of the memory 360 as required by the executed process. In an embodiment, the processor 340 is configured to execute one or more applications 362 based on the OS 361 or in response to a signal received from an external source or operator. For example, the application 362 may include an encoder, a decoder, a VR or AR application, a camera application (for still images and videos), a video call application, an email client, a social media client, an SMS messaging client, a virtual assistant, etc. In an embodiment, the processor 340 is configured to receive and send media content in multiple media streams through a separate network slice. The processor 340 can support synchronization of media streams sent to media devices.

[0078] Processor 340 is also coupled to I / O interface 345 , which provides electronic device 300 with the ability to connect to other devices, such as client devices 106 - 114 . I / O interface 345 is the communication path between these accessories and processor 340 .

[0079] The processor 340 is also coupled to the input 350 and the display 355. The operator of the electronic device 300 can use the input 350 to input data or input to the electronic device 300. The input 350 can be a keyboard, a touch screen, a mouse, a trackball, a voice input, or other devices that can act as a user interface to allow the user to interact with the electronic device 300. For example, the input 350 may include a voice recognition process, thereby allowing the user to enter a voice command. In another example, the input 350 may include a touch panel, a (digital) pen sensor, a key, or an ultrasonic input device. For example, the touch panel can recognize touch input with at least one scheme (such as a capacitive scheme, a pressure-sensitive scheme, an infrared scheme, or an ultrasonic scheme). The input 350 can be associated with the sensor 365 and / or the camera by providing additional input to the processor 340. In an embodiment, the sensor 365 includes one or more inertia measurement units (Inertia Measurement Unit, IMU) (such as accelerometers, gyroscopes and magnetometers), motion sensors, optical sensors, cameras, pressure sensors, heart rate sensors, altimeters, etc. The input 350 may also include a control circuit. In a capacitive scheme, the input 350 may recognize touch or proximity.

[0080] Display 355 may be a Liquid Crystal Display (LCD), a Light-Emitting Diode (LED) display, an Organic LED (OLED), an Active Matrix OLED (AMOLED), or other display capable of displaying text and / or graphics such as from a website, video, game, image, etc. Display 355 may be sized to fit within the HMD. Display 355 may be a single display screen or multiple display screens capable of creating a stereoscopic display. In an embodiment, display 355 may be a Heads-Up Display (HUD). Display 355 may display 3D objects such as 3D point clouds.

[0081] Memory 360 is coupled to processor 340. Portions of memory 360 may include RAM, while other portions of memory 360 may include flash memory or other ROM. Memory 360 may include a persistent storage device (not shown), which represents any structure capable of storing and facilitating retrieval of information (such as data, program code, and / or other suitable information). Memory 360 may include one or more components or devices that support long-term storage of data, such as a read-only memory, a hard disk, flash memory, or an optical disk. Memory 360 may also include media content. Media content may include various types of media, such as images, videos, three-dimensional content, VR content, AR content, 3D point clouds, etc.

[0082] The electronic device 300 also includes one or more sensors 365, which can measure physical quantities or detect the activation state of the electronic device 300, and convert the measured or detected information into electrical signals. For example, the sensor 365 may include one or more buttons for touch input, a camera, a gesture sensor, an IMU sensor (such as a gyroscope or gyro sensor and an accelerometer), an eye tracking sensor, an air pressure sensor, a magnetic sensor or a magnetometer, a grip sensor, a proximity sensor, a color sensor, a biophysical sensor, a temperature / humidity sensor, a brightness sensor, an ultraviolet (UV) sensor, an electromyography (EMG) sensor, an electroencephalogram (EEG) sensor, an electrocardiogram (ECG) sensor, an IR sensor, an ultrasonic sensor, an iris sensor, a fingerprint sensor, a color sensor (such as a red green blue (RGB) sensor), etc. The sensor 365 may also include a control circuit for controlling any sensor included therein.

[0083] although Figure 2 and Figure 3 An example of an electronic device is shown, but the Figure 2 and Figure 3 Make various changes. For example, Figure 2 and Figure 3 The various components in the embodiment may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, as with respect to computing and communications, electronic devices and servers may have a variety of configurations, and Figure 2 and Figure 3 The present disclosure is not limited to any particular electronic device or server.

[0084] Figure 4 An example architecture 400 for enabling edge applications according to the present disclosure is shown. Figure 4 The embodiment of the edge application architecture 400 shown in FIG. 4 is for illustration only. Figure 4 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0085] like Figure 4As shown, edge application architecture 400 includes network components 402-408 and interfaces 410-416 between these network components that can provide edge-based applications. Network components 402-408 may include user equipment (UE) 402, core network 404, edge network 406, and edge configuration server (ECS) 408. Interfaces 410-416 may include application client 410, edge enabler client 412, edge application server 414, and edge enabler server (EES) 416. Edge application server 414, edge enabler server 416, and edge configuration server 408 may be composed of Figure 2 The server 200 shown in FIG.

[0086] UE 402 is a device that generates volumetric content associated with a user and sends the volumetric content to an edge network. UE 402 receives mixed volumetric content of other users in a conference setting and renders the volumetric content in the conference setting. UE 402 may include an application client 410 and an edge enabler client 412. UE 402 may represent Figure 1 One or more client devices 106-114 and Figure 3 The electronic device 300 shown in FIG.

[0087] The core network 404 can assign the UE 402 to a particular node in the edge network 406. The core network 404 can direct volumetric content to the edge network 406 from the UE 402 and other UEs.

[0088] The edge network 406 may include a media resource function for processing and mixing volumetric content according to the UE 402, and mixing the content of other UEs into the conference scene provided back to the UE 402. The edge network 406 may include an edge application server 414 and an EES 416. The 3rd Generation Partnership Project (3GPP) System Architecture And Services (SA2) Sub Working Group (SWG) defines that the edge network can be implemented as a Local Area Data Network (LADN). The premise of the edge network is that it is closer to the UE and can therefore provide services with better latency. For faster application performance, application services deployed within the edge network handle media to / from the UE.

[0089] The ECS 408 is a configuration server deployed in the edge network 406 to provide services to the edge-enabled client 412 to discover the appropriate EES 416 and edge application server 414. The ECS 408 provides the support functions required for the edge-enabled client 412 to connect with the EES 416. The ECS 408 can supply edge configuration information to the edge-enabled client 412. The configuration information can include information for the edge-enabled client 412 to connect to the EES 416 and information for establishing a connection with the EES 416. The ECS 408 can support functions for registration (i.e., registration, update, and deregistration) of the EES 416.

[0090] The application client 410 is a client (eg, app) at the UE 402 that the service provider requires the user to use the service. The application client 410 is an application residing in the UE 402 that performs client functions.

[0091] The edge enabling client 412 is a client at the UE 402 that interfaces with services deployed at the edge of the mobile operator to provide the required data to the application client 410. The edge enabling client 412 abstracts the delivery of data to the application client 410, so the application client 410 is unaware that the data is retrieved through the edge network 406, the core network 404, or the service provider network. The edge enabling client 412 can retrieve and supply configuration information to enable the exchange of application data traffic with the edge application server 414.

[0092] Edge application server 414 is an application server of a mobile operator deployed in edge network 406. Edge application server 414 is an application service that performs server functions and resides in edge network 406. Application client 410 of UE 402 can connect to edge application server 414 to utilize the services of applications with the benefits of edge computing.

[0093] The EES 416 provides support functions to enable the exchange of traffic between the edge-enabled clients 412 and the edge application servers 414. Such functions include discovery of the edge application servers 414, connection management between the edge-enabled clients 412, the ECS 408, and the edge application servers 414.

[0094] The EES 416 may supply configuration information to the edge enablement client 412, so that application data services can be exchanged with the edge application server 414. The EES 416 may interact with the 3GPP core network 404 for access to network function capabilities. The EES 416 may support exposing 3GPP network and service capabilities to the edge application server 414; support registration (i.e., registration, update, and deregistration) functions of the edge enablement client 412 and the edge application server 414; and support functions for triggering instantiation of the edge application server 414 on demand.

[0095] although Figure 4 An edge application architecture 400 for enabling edge applications is shown. Figure 4 Various changes may be made. For example, the edge application architecture 400 and its various components may be changed as needed or desired. In addition, the number and placement of the various components of the edge application architecture 400 may be changed as needed or desired. In addition, the edge application architecture 400 may be used for any other suitable volumetric conferencing process, not limited to the specific process described above.

[0096] Figure 5 An example of an example architecture 500 for media streaming according to the present disclosure is shown. Figure 5 The embodiment of the media streaming architecture 500 shown in FIG. 5 is for illustration only. Figure 5 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0097] According to an embodiment, 5G media streaming is enabled by establishing application functions in the core network 504. A signaling application function server 518 performs signaling functions and a media application function server 520 performs media functions. Depending on application requirements, there may be multiple instances of these application functions in the core network 504. Different components of the UE 502 connect to these application functions to exchange signaling and media data to receive 4G media streaming services provided by mobile operators.

[0098] like Figure 5As shown, 3GPP TS26.512 specifies a reference for a media streaming architecture 500 for 5G media streaming (5GMS). 3GPP SA working group 4 (SA4) is standardizing media services for deployment in 5G networks. Different system components of the 5G media streaming architecture 500 may include a UE 502 and a data network 504. The UE 502 may include a perception application 510 and an edge enabling client 512 (5GMSd client). The data network 504 may include an application provider 514 (5GMSd application provider), a signaling application function server 518 (5GMSdAF), and a processing media application function server (5GMSd) 520. The 5GMSd client 512 may include a media session processor 522 and a media player 524. The 5GMSd client 512 may correspond to Figure 5 The edge-enabled client 512 shown in FIG.

[0099] The awareness application 510 is stored in the UE 502. The awareness application 510 receives application service information from the application provider. The application service information is then used to retrieve information and data related to the application from the data network. The awareness application 510 may correspond to Figure 4 The application client 410 shown in .

[0100] The signaling application function server 518 is a function that performs signaling functions for application services in the data network 504. The signaling application function server 518 provides various control functions to the media session processor and / or 5GMSd application provider on the UE 502. The signaling application function server 518 can relay or initiate requests for different policy or charging functions (PCF) 506 processing, or interact with other network functions.

[0101] The media application function server 520 is an application server that hosts media functions. The media application function server 520 is dedicated to media streaming. The media application function server 520 can stream volumetric media to the UE 502.

[0102] The media session processor 522 is a component of the UE 502 that enables communication with the signaling application function server 518 in the data network 504. The communication with the signaling application function server 518 is used to establish a related media channel between the UE 502 and the data network 504.

[0103] The media player 524 is a component of the UE 502. The media player 524 may receive media data from a media application function in the data network 504. The media player 524 may provide data to the 5GMSd aware application 510.

[0104] Although Figure 5 The media streaming architecture 500 is shown, but may be Figure 5 Various changes may be made. For example, the media streaming architecture 500 and its various components may be changed as needed or desired. In addition, the number and placement of the various components of the media streaming architecture 500 may be changed as needed or desired. In addition, the media streaming architecture 500 may be used in any other suitable media streaming process, not limited to the specific process described above.

[0105] Figure 6 An example media communication service 600 utilizing two network slices 602 in accordance with the present disclosure is shown. Figure 6 The embodiment of media communication service 600 shown in FIG. 6 is for illustration only. Figure 6 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0106] See also Figure 6, shows an example media communication service utilizing two network slices 602. A first network slice 602a may be connected to a first data network 604a (e.g., a 5G IMS data network) for a volumetric conversational service. A second network slice 602b may be connected to a different second data network 604b, for example, for downloading content using 5G media streaming as defined in 3GPP TS26.501 and 3GPP TS26.502. An application in a UE 606 may use the two network slices 602 based on the implementation of the application running on the UE 606. In this case, the UE application is responsible for utilizing two separate network slice connections and then bridging (or utilizing) content retrieved using two different network slices 602. However, since support for network slicing is not natively available to the UE 606 from the network, it is entirely possible that there may be synchronization issues for content retrieved using two different network slices 602. For example, two UEs 606 communicate with each other (volumetric conversational service) using the first network slice 602a. As part of the interaction, the UE 606 may agree to view certain content together (e.g. some 2D / 3D video content, images, shared collaboration, etc.), for which they retrieve the content using the second network slice 602b. The content that the two users attempt to retrieve using the second network slice 602b may not be available in a timely manner, possibly because the two services are not synchronized. This may be due to: a) different quality parameters attributed to the second network slice 602b compared to the first network slice 602a, and b) network issues with the second network slice 602b. In an embodiment, the UE 606 may negotiate similar QoS to both network slices 602, thereby alleviating some issues. However, it is still possible that the UE-initiated method of synchronizing content may not work as expected. The UE may be Figure 1 The client devices 106-116 and Figure 3 The electronic device 300 shown in FIG.

[0107] In the above scenario, there is no network support to help with synchronization of content across the two network slices 602. The following network support may be added to facilitate a seamless experience for hybrid and media communication services.

[0108] When establishing a media communication service, the network slice identifier may be carried in the signaling message of the other network slice 602. When the first network slice 602a is established, and the UE 606 and the network agree on a network slice identifier (e.g., the S-NSSAI of the first network slice 602a), then when establishing the second network slice 602b, the UE 606 may include the slice identifier of the first network slice 602a in the signaling connection for establishing media communication using the second network slice 602b (e.g., using the "component slices" field). Similarly, once the second network slice 602b is established, the first network slice 602a is updated with the slice identifier of the second network slice 602b, so that the control plane node of the first network slice 602a knows that the corresponding network slice 602 (with the slice identifier of the second network slice 602b) is established.

[0109] In addition, in order to let the control plane nodes of all network slices 602 know about other network slices 602 used for media communication / hybrid services, the "Media-Communication-Service Id" field can be included in all media service connection establishment requests for each of the network slices 602 used for the media communication service. Figure 6 The above steps and different signaling message fields for establishing a media communication service utilizing two network slices 602 are shown.

[0110] Figure 6 is an example of a media communication service utilizing two network slices 602, which can be extended to a media communication service utilizing any number of network slices 602. For a media communication service utilizing "N" network slices 602, the UE 606 may perform similar operations, i.e., for each subsequent connection request for a media communication service utilizing other network slices 602, the UE 606 may include a list of slice identifiers of all network slices 602 that have been established for the media communication service. In addition, for each establishment request for a media communication service utilizing a new network slice, the UE 606 may update the already established network slice 602 with the slice identifier of the newly established network slice 602. In an embodiment, when the UE 606 decides that the network slice 602 is no longer needed for the media communication service, the UE 606 may terminate the unneeded network slice 602 and update each other network slice 602 that the network slice 602 with the given slice identifier has been terminated.

[0111] As defined above, the 5G AF in each network slice 602 responsible for serving the UE 606 is aware of the other network slices 602 in the media communication service. Once all AFs in all connected network slices 602 know the other network slice identifiers, a common QoS and Quality of Experience (QoE) can be achieved. Experience, QoE) framework.

[0112] Network slicing can be used to provision a media service when the media service is expected to have multiple media flows (such as audio, video, text, control, etc.) that may require different QoS treatment during the service delivery phase.

[0113] Many such media services are being discussed in different 3GPP groups, which can benefit from establishing those services using multiple network slices. Examples of such media services are specified in 3GPP SA WG1 TR 22.847. The present disclosure provides Phase 1 use cases and potential 5G requirements for supporting tactile and multimodal communication services. Specifically, research, use cases and potential requirements for new scenarios such as immersive real-time experiences involving tactile and multimodal interactions (including collaborative network assistance, billing and security aspects, key performance indicators (KPIs)), and gap analysis are included in the scope of this technical specification. As part of the present disclosure, multiple use cases for tactile and multimodal communications are included. Among these use cases, media-related use cases are included, which are strong candidates for implementation using network slicing.

[0114] Examples of use cases include immersive multimodal virtual reality applications and immersive virtual reality games. Both use cases may require multiple multimodal media streams between the user and the 5G network. For example, the use case can be implemented by running the audio and video streams of the HMD device in the first network slice 602a, and running the tactile content based on the sensing device such as gloves in the second network slice 602b. Since the use case description mentions different QoS treatments of the above media streams, QoS can be differently provided for different network slices 602 carrying content of different modalities.

[0115] One consideration when using network slicing for media services is that different component streams (audio, video, haptic, etc.) of a media service may be delivered to a UE 606 using different network slices 602. Since the QoS of different network slices 602 are configured differently by the mobile operator, an application service provider may take advantage of the differences in quality settings of different network slices 602 to deliver content with different levels of QoS requirements to the UE 606. As an example, such an option may be to use the 3GPP standardized eMBB slice for delivering video content, and the 3GPP standardized uRLLC slice for delivering haptic data.

[0116] although Figure 6 A media communication service 600 is shown, but may be Figure 6 Various changes may be made. For example, the number and placement of the various components of the media communication service 600 may vary as needed or desired. In addition, the media communication service 600 may be used in any other suitable network slicing process and is not limited to the specific process described above.

[0117] When different media component streams are delivered using different network slices 602, stream synchronization may be a problem. Haptic data is delivered more frequently and in smaller messages, while video data may be delivered with relatively long packet durations and larger packet sizes. In this case, haptic and video data delivered using different network slices 602 may arrive at UE 606 at different times. These packets need to be buffered at UE 606, decoded by UE 606 based on decoding offsets, then combined into presentation views based on presentation offsets, and finally rendered to the user. Although buffering may work to some extent (e.g., out-of-order packets of different component streams, etc.), buffering may not be feasible if packets according to different component streams arrive with relatively large jitter, packet delays, etc. The amount of buffering available at UE 606 may not be sufficient to correctly collect the packets to be presented for all media component streams, decode them, and present them to the user. In this case, a network-supported stream synchronization facility is required to help UE 606 receive packets of different component streams to be properly decoded and presented to the application user in a timely manner.

[0118] Figure 7 Example intra-slice synchronization 700 according to the present disclosure is shown. Figure 7 The embodiment of intra-slice synchronization 700 shown in FIG. 7 is for illustration only. Figure 7 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0119] like Figure 7As shown, intra-slice synchronization 700 may use flow lookup functions in different network slices 602. Each network slice 602 may be provisioned with a flow information lookup function or synchronization function 704 (e.g., a 5G application server acting as a slice-specific synchronization function) that may look up flow information for component flows 702 passing through that network slice 602. The synchronization function 704 may be provided by Figure 2 The server 200 shown in FIG.

[0120] If more than one component stream 702 is delivered through the same network slice 602, the synchronization function 704 has the ability to individually look up the decoding and presentation offsets of the different media component packets, streams, and frames. Using this information, the synchronization function 704 can ensure that the different media component streams 702a and 702m within the network slice 602 are properly delivered to the UE 606.

[0121] The synchronization function 704 can look at the properties of the component streams 702 (inter-packet delay, packet size, jitter, etc.) and deliver the packets and frames based on the decoded offsets from the parent packets or frames based on these offsets. Even if the packets or frames of the different component streams 702a and 702m arrive from the source with some network artifacts (e.g., out of order / delayed / with jitter, etc.), the synchronization function 704 can correct these network artifacts and forward the component streams 702a and 702m in the proper order according to the stream or frame requirements. In order to facilitate the corrected network artifacts and forwarded component streams, the synchronization function 704 can construct the corrected stream transmission condition information for each stream parameter based on the information in Table 1.

[0122] Table 1 shows the streaming condition information.

[0123] [Table 1]

[0124]

[0125] For each stream parameter, the synchronization function 704 can determine the necessary adjustments required for proper delivery of the stream 702 so that the stream packets or frames can be properly decoded and presented at the UE 606. In addition, such adjustment information can be generated for each media component flow 702 through the network slice 602.

[0126] The packets or frames of the different media component streams 702a and 702m arriving from the synchronization function 704 may have a minimum (if any) number of packets or frames of the different media component streams 702a and 702m and may be appropriately decoded and presented to the application user.

[0127] although Figure 7 An example of intra-slice synchronization 700 is shown, but the Figure 7Various changes may be made. For example, the number and placement of the various components of intra-slice synchronization 700 may vary as needed or desired. In addition, intra-slice synchronization 700 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0128] Figure 8 Example inter-slice synchronization 800 according to the present disclosure is shown. Figure 8 The embodiment of inter-slice synchronization 800 shown in FIG. 8 is for illustration only. Figure 8 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0129] like Figure 8 As shown, to facilitate inter-slice synchronization 800 of component streams 702a, 702b, 702m, and 702n delivered across multiple network slices 602a and 602b, a synchronization function 704a and 704b of one of the network slices 602a and 602b may act as a parent synchronization function 802 (i.e., a media service level synchronization function) to view media component stream information delivered in all network slices 602a and 602b. The parent synchronization function 802 may be provided by Figure 2 The server 200 shown in FIG.

[0130] The parent synchronization function 802 may be responsible for synchronization of all media component streams 702a, 702b, 702m, and 702n of all network slices 602a and 602b. This responsibility may be achieved through the following two options.

[0131] Each independent synchronization function 704a and 704b in the network slices 602a and 602b can forward representative packets or frames (according to the media component streams 702a, 702b, 702m and 702n managed by the synchronization functions 704a and 704b) to the parent synchronization function 802. The parent synchronization function 802 may not need to look at each and every packet or frame of each and every media component stream 702a, 702b, 702m and 702n in all network slices 602a and 602b. Based on the representative set of packets or frames of the different media component streams 702a, 702b, 702m and 702n in all network slices 602a and 602b, the parent synchronization function 802 can follow the same process for determining appropriate streaming condition information, as described in the case of the previous inter-slice synchronization 800. Once the streaming condition information is determined for all media component streams 702a, 702b, 702m, and 702n in all network slices 602a and 602b, the parent synchronization function 802 can forward the information about the relevant media component streams 702a, 702b, 702m, and 702n to the corresponding stream synchronization functions 704a and 704b of the independent (individual) network slices 602a and 602b. When the independent slice-specific synchronization functions 704a and 704b receive the information from the parent synchronization function 802, each independent synchronization function 704a and 704b can forward the corresponding media component streams 702a, 702b, 702m, and 702n or frames in the corresponding network slices 602a and 602b according to the recommended information, as described in the case of intra-slice synchronization 700.

[0132] Instead of forwarding representative packets or frames of all media component streams 702a, 702b, 702m and 702n within network slices 602a and 602b to the parent synchronization function 802 (i.e., the media level synchronization function), the slice-specific synchronization functions 704a and 704b can construct a stream parameter state table as shown in Table 2.

[0133] Table 2 shows an example of stream parameter status.

[0134] [Table 2]

[0135]

[0136] For each media component stream 702a, 702b, 702m, and 702n in the network slices 602a and 602b, the slice-specific synchronization functions 704a and 704b may build current state information of all applicable parameters and share this information with the parent synchronization function 802. Based on this information, the parent synchronization function 802 may build streaming condition information, as described previously in the case of inter-slice synchronization 800. Once this streaming information is generated, the parent synchronization function 802 (i.e., the media service level synchronization function) may follow the same process as described above.

[0137] To allow intra-slice synchronization 700 or inter-slice synchronization 800, a reference clock can be used to compare decoding offsets, presentation offsets, and timing-based parameters. To allow such references, each slice-specific synchronization function 704a and 704b and the media service level parent synchronization function 802 can be configured with a reference clock, such as a Network Time Protocol (NTP) server. All levels of synchronization functions 704a, 704b, and 802 can use the reference clock to make decisions for building streaming condition information and stream parameter tables.

[0138] If different media service component streams are delivered over different network slices without adequate network support, the UE 606 may be at risk of not having the correct packets or frames for presentation to the application user. If the QoS delivery parameters of the different network slices 602a and 602b are not properly aligned (due to improper slice configuration or slice parameter changes during the session process), the packets or frames of the different media component streams 702a, 702b, 702m and 702n delivered over different network slices 602a and 602b may arrive at the UE 606 at different times, which may render the buffering mechanism useless at the UE 606. Even if the application configures large application buffers, these buffers may sometimes be useless because the existing synchronization mechanisms cannot perform the required media component packaging to facilitate the user's complete application experience. In order to allow better synchronization at the UE 606 in these cases, the network can be queried for synchronization information. The following are the processes and architectural enhancements to support this synchronization.

[0139] The UE 606 may request synchronization information from each of the slice-specific synchronization functions 704a and 704b. When such a request comes from the UE 606, the slice-specific synchronization functions 704a and 704b may provide the flow parameter state table information for the network slices 602a and 602b. However, since the previously described flow parameter state table has current flow parameter state information, such information may be enhanced with the timing information shown in Table 3.

[0140] Table 3 shows an example of flow parameter status with time.

[0141] [Table 3]

[0142] time Status Information T0 <![CDATA[The previously described flow parameter status table information for all flows at time T 0 > <![CDATA[T 1 ]]> <![CDATA[The previously described flow parameter status table information for all flows at time T 1 > <![CDATA[T 2 ]]> .. .. .. .. .. <![CDATA[T N ]]> ..

[0143] When UE 606 requests synchronization information, UE 606 may request information at a specific time "t", and slice-specific synchronization functions 704a and 704b may return such information at a specific time "t". In an embodiment, UE 606 may request all information, i.e., information at all times, and when UE 606 receives a response, relevant information may be extracted. When UE 606 knows that decoding and presentation at a specific time "t" is acceptable, the values ​​of different parameters at that time compared to the current values ​​allow UE 606 to determine how the parameters are moved or transformed. Using such transformation information, UE 606 can estimate the buffer size required to hold packets / frames of different media service components.

[0144] Similar to the slice-specific synchronization function, the UE 606 may similarly request status information for all network slices 602a and 602b from the media service level parent synchronization function 802. The parent synchronization function 802 may deliver similar information with timing information to the previously described slice-specific synchronization functions 704a and 704b, but for all media component streams 702a, 702b, 702m, and 702n in all network slices 602a and 602b.

[0145] although Figure 8 Inter-slice synchronization 800 is shown, but may be Figure 8 Various changes may be made. For example, the number and placement of the various components of inter-slice synchronization 800 may vary as needed or desired. In addition, inter-slice synchronization 800 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0146] Fig. 9 An example multi-slice collaboration 900 for tracking media stream delivery status according to the present disclosure is shown. Fig. 9 The embodiment of multi-slice collaboration 900 shown in FIG. 9 is for illustration only. Fig. 9 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0147] like Fig. 9 As shown, multi-slice collaboration 900 allows for the exchange of synchronization information. When there are multiple slices 602a and 602b for the delivery of a stream of a media service, all slices 602a and 602b may collaborate to exchange synchronization information.

[0148] A set of tracking functions 902a and 902b may be established in all network slices 602a and 602b. Each tracking function 902a and 902b in each network slice 602a and 602b may communicate with each other tracking function 902a and 902b in each network slice 602a and 602b to exchange synchronization information. Such synchronization information includes details such as the information shown in Table 4.

[0149] Table 4 - Synchronization information exchanged between tracking functions in different network slices

[0150]

[0151] For each media component flow through the network slices 602a and 602b, the tracking functions 902a and 902b can record details such as a packet counter (packet number) or a frame counter (frame number) and the time instance (e.g., transit time) when the packet / frame was delivered through the network slice 602a and 602b. For other parameters such as latency, bandwidth, throughput, packet loss rate, jitter, etc., average or median values ​​can be stored along with the time they were calculated. When such information is exchanged between different tracking functions 902a and 902b in each network slice 602a and 602b, all network slices 602a and 602b can have information about when each packet, frame counter or number was transmitted through a given network slice 602a and 602b, or the value corresponding to the additional parameter.

[0152] When each tracking function 902a and 902b has the above information, each network slice 602a and 602b knows the relative time of the packet number or frame number of the media component stream relative to other media component streams in other network slices 602a and 602b. However, in order to convert this information into actionable information, the application service provider must indicate possible inter-relation timing information between all media component streams. In order to facilitate the exchange of this information, the application service provider configures the inter-stream timing related information, as shown in Table 5.

[0153] Table 5 - Inter-stream timing related information

[0154]

[0155] For each network slice 602a and 602b, Table 5 shows the possible delivery, bit rate, bandwidth, allowed packet loss rate, jitter, and throughput of packets / frames through the slice for an interval period (e.g., 0-M milliseconds for any m, e.g., 1000 milliseconds). Based on the above configuration information, each tracking function 902a and 902b knows when each network slice 602a and 602b must send packets or frames belonging to a flow relative to other flow components within the same network slice 602a and 602b. The information in Table 5 and the state information shown in Table 4 provided by the application service provider can allow each tracking function 902a and 902b to know when to transmit packets or frames of each flow relative to other flows within the network slice 602a and 602b.

[0156] As a result of the exchange of the above information between the different tracking functions 902a and 902b in the different network slices 602a and 602b, each tracking function 902a and 902b knows the relative delivery information of the flow components relative to the other flow components in the network slices 602a and 602b. Therefore, the tracking functions 902a and 902b can apply packet or frame forwarding actions to each packet or frame belonging to each flow in the network slices 602a and 602b.

[0157] The action may include a positive or negative delay for the flow. If the available information indicates that the flow packets or frames are delivered earlier or later than required, the positive or negative delay action may be selected by the tracking functions 902a and 902b. Applying the positive or negative delay action may delay or speed up the delivery of the packets or frames belonging to the flow by a certain value. The amount of time delayed or accelerated is based on the difference between the timing information between the corresponding flow components of Table 5 for the delay parameter.

[0158] Other actions may include a positive or negative offset to the bit rate of the stream. If the available information indicates that the stream packet or frame is delivered at a lower or higher bit rate than required, a positive or negative offset action to the bit rate may be selected by tracking functions 902a and 902b. The positive or negative offset action to the bit rate will be applied to increase or decrease the delivery bit rate of the packet or frame belonging to the stream by a certain offset value. The bit rate amount to be increased or decreased may be based on the difference between the bit rate parameter values ​​of the corresponding stream components of Table 5.

[0159] An action may include a positive or negative offset to the throughput of a flow. If the available information indicates that the flow packets or frames are being delivered at a lower or higher throughput than required, a positive or negative offset action to the throughput may be selected by tracking functions 902a and 902b. Applying a positive or negative offset action to the throughput may increase or decrease the delivery throughput of the packets or frames belonging to the flow by a certain offset value. The amount of throughput to be increased or decreased is based on the difference between the throughput parameter values ​​of the corresponding flow components of Table 5.

[0160] Other actions may include a positive or negative offset to the jitter of a component stream. If the available information indicates that a stream packet or frame is delivered with a lower or higher jitter than allowed, a positive or negative offset action to jitter may be selected by tracking functions 902a and 902b. Applying a positive or negative offset action to jitter may increase or decrease the allowed delivery jitter of a packet or frame belonging to a stream by a certain offset value. The amount of jitter to be increased or decreased is based on the difference between the jitter parameter values ​​of the corresponding stream components of Table 5.

[0161] Other actions may include a positive or negative offset to the packet loss rate.The positive or negative offset action to the packet loss rate has a behavior similar to the positive or negative offset action to jitter described above, but it uses the packet loss rate value.

[0162] Other actions may include a positive or negative offset to the bandwidth. The positive or negative offset to bandwidth action has similar behavior to the throughput behavior described above, but the comparison uses the bandwidth value.

[0163] The various aspects described in the above disclosure may be configured by an application service provider's control function in an MNO network, e.g., a 5G AF responsible for managing multiple network slices. Below is the information that an application service provider may provision as part of the service provisioning process to establish a media service to be delivered using multiple network slices, as shown in Table 6.

[0164] Table 6 - Application provider service configuration to facilitate stream synchronization

[0165]

[0166]

[0167]

[0168] although Fig. 9 An example multi-slice collaboration 900 for tracking the status of media stream delivery is shown, but may be used for Fig. 9 Various changes may be made. For example, the number and placement of various components of multi-slice collaboration 900 may vary as needed or desired. In addition, multi-slice collaboration 900 may be used in any other suitable network slicing process and is not limited to the specific process described above.

[0169] Fig. 10A and 10B Example expected flow condition information 1000 and 1002 configured by an application service provider according to the present disclosure are shown. Fig. 10A and 10B The embodiments of expected flow condition information 1000 and 1002 shown in FIG. 1 are for illustration only. Fig. 10A and 10BThe scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0170] In the described embodiment of querying the network for synchronization information, the MNO network components (i.e., the slice-specific synchronization functions 704a and 704n and the media service level parent synchronization function 802) assist the UE 606 with the flow parameter information that the UE 606 can use to update the application buffer configuration. In an embodiment, the application service provider 1004 can assist the UE 606 in the same task. To enable this, the application service provider 1004 configures the expected relative flow condition information 1008, as shown in Table 7. The application service provider 1004 can be configured by Figure 2 The server 200 shown in FIG.

[0171] Table 7 - Expected relative flow condition information

[0172]

[0173] As shown in Table 7, all parameters for the stream whose "reference stream" attribute is set to true are set to zero. For each other stream whose "reference stream" attribute is set to false, all corresponding parameters are configured with the relative difference of the value of the corresponding parameter. For example, if the inter-packet delay of stream Id 2 is set to +5 milliseconds, this means that stream Id 2 should have an inter-packet delay exceeding 5 milliseconds compared to the reference stream as the stream with stream Id 1.

[0174] All of this information is configured by the application service provider in the 5G AF that manages the media service, which can be configured in the media level parent synchronization function 802. In an embodiment, the application service provider 1004 can also configure the independent flow level information 1010a and 1010b according to Table 7 into the slice-specific synchronization functions 704a and 704b. Once such information is available at the media service level parent synchronization function 802 or the slice-specific synchronization functions 704a and 704n, these functions can perform the tasks of intra-slice synchronization 700 or inter-slice synchronization 800 described earlier in this disclosure.

[0175] like Fig. 10A As shown, a method is established in which one or more tracing functions 902a and 902b are established in each network slice 602a and 602b, and the tracing functions 902a and 902b collaborate with each other to exchange synchronization information, which is then compared with values ​​configured by an application service provider 1004 to apply certain actions to the component flow.

[0176] The tracking functions 902a and 902b may be simple application services whose responsibility is to record the above information. In an embodiment, the slice-specific synchronization functions 704a and 704b may perform the role of the tracking function to assist the multi-slice collaboration process.

[0177] In the embodiment, various processes of intra-slice synchronization 700, inter-slice synchronization 800, UE querying the network for synchronization information and multi-slice collaboration are described. These processes describe the exchange of different types of information between different synchronization functions and tracking functions.

[0178] In an embodiment, the application service provider 1004 can supply a synchronization directory database in which all of this information is persisted. Each synchronization function and tracking function can persist all of the above information into the directory database. Once this information is persisted into the database, all synchronization functions and tracking functions in all network slices, as well as the 5G AF and the application service provider 1004, can access the directory database. Therefore, each synchronization function or tracking function does not need to communicate separately with other synchronization functions or tracking functions in the same or different network slices 602a and 602n. All of these functions can retrieve the necessary information from the shared directory database.

[0179] although Fig. 10A and 10B 1000 and 1002 are shown as example expected flow condition information 1000 and 1002 configured by an application service provider, but may be Fig. 10A and 10B Various changes may be made. For example, the number and placement of various components of the expected flow condition information 1000 and 1002 may vary as needed or desired. In addition, the expected flow condition information 1000 and 1002 may be used in any other suitable network slicing process and is not limited to the specific process described above.

[0180] Fig.11 An example sliced ​​messaging 1100 of inter-stream timing-related information according to the present disclosure is shown. Fig.11 The embodiment of sliced ​​message transmission 1100 shown in FIG. 1 is for illustration only. Fig.11 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0181] like Fig.11As shown, the application service provider 1004 configures the information 1102a and 1102n related to inter-flow timing, which is used by the tracking functions 902a and 902b to compare the current state information to perform some predetermined actions. In an embodiment, the information 1102a and 1102n related to inter-flow timing is directly shared by the application service provider 1004 to each slice synchronization function 704a and 704n in each network slice 602a and 602b and each tracking function 902a and 902n.

[0182] When each network slice 602a and 602b receives inter-stream timing related information 1102a and 1102n from the application service provider 1004, the tracking functions 902a and 902n and the synchronization functions 704a and 704n can use the current state information of these parameters to derive actions to be performed for those media component flows. Using the information provided by the application service provider 1004, each network slice 602a and 602n can adapt to changing network conditions.

[0183] although Fig.11 An example message transmission 1100 by slice is shown, but may be Fig.11 Various changes may be made. For example, the number and placement of the various components of the message transmission by slice 1100 may vary as needed or desired. In addition, the message transmission by slice 1100 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0184] Fig.12 An example tracking functional group 1200 according to the present disclosure is shown. Fig.12 The embodiment of tracking functional group 1200 shown in FIG. 1 is for illustration only. Fig.12 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0185] like Fig.12 As shown, each tracking function 902a and 902n communicates with each other tracking function 902a and 902n in the same network slice 602a and 602n and each tracking function 902a and 902n in each other network slice 602a and 602n. Using this communication, these tracking functions 902a and 902n exchange synchronization information of the flow components passing through their network slices 602a and 602n.

[0186] In an embodiment, instead of the tracing functions 902a and 902n interacting with each other tracing function 902a and 902n in all network slices 502a and 602n, the application service provider 1004 may define a tracing function group 1202. Each tracing function group 1202 may include at least one tracing function 902a and 902b in each network slice 602a and 602b. The tracing functions 902a and 902b within the tracing function group 1202 may interact with each other to exchange synchronization information 1204 required for flow synchronization. In an embodiment, the tracing functions 902a and 902b within the tracing function group 1202 only exchange synchronization information with other tracing functions 902a and 902b within the tracing function group 1202.

[0187] The application service provider 1004 has a clear understanding of the stream synchronization requirements and knows what each media stream delivery state operates in each network slice. In other words, at any time during the media service and at different locations of the network slice, the application service provider 1004 has an estimate of how many packets or frames of each media stream in each network slice 602a and 602b should have been sent from the corresponding network slice from that location of the slice. With this understanding, the application service provider 1004 can configure the tracking function group 1202 to signal that the communication between the tracking functions 902a and 902b in each tracking function group 1202 is important for the flow synchronization aspect. By defining the tracking function group 1202, a more practical tracking of the flow state can be performed, and thus the synchronization method described in the present disclosure can be utilized.

[0188] The application service provider 1004 may deem it more practical for the tracing function A_1 to interact with the tracing function B_1 for exchanging synchronization information, and group the two tracing functions within the same tracing function group 1202. As described above, the application service provider 1004 may group the two functions because it knows that at any instance of time, the media component flows flowing through network slice A and network slice B will benefit by exchanging flow synchronization information. Similar groupings may be defined for other tracing functions 902 in all network slices 602.

[0189] In the previous embodiments, various processes were described in which synchronization information 1204 was exchanged between synchronization tracking functions 902 in different network slices 602 and between tracking functions 902 in different network slices 602. These processes provide for the exchange of synchronization information 1204. However, continuously exchanging synchronization information 1204 between all tracking functions in the network may be cumbersome, i.e., time consuming, and using the synchronization information 1204 to perform the necessary actions is performance intensive.

[0190] In an embodiment, different options are described to signal when to exchange synchronization information 1204. Marking points may be used where the application service provider 1004 may tag certain packets or frames of the media stream of the network slice 602. When the different synchronization functions 704 and tracking functions 902 defined in this disclosure receive packets or frames with these marking points, this is a signal for the above functions to exchange synchronization information 1204.

[0191] A separate signaling message (e.g., "Perform synchronization") may be sent from the 5G AF to each synchronization function 704 and tracking function 902 in each network slice 602. The signaling message may optionally have a time (relative or absolute) of when to start the synchronization process. The option for starting synchronization is configured by the application service provider during the service configuration phase.

[0192] although Fig.12 Tracking functionality group 1202 is shown, but can be Fig.12 Various changes may be made. For example, the number and placement of the various components of the tracking function group 1202 may vary as needed or desired. In addition, the tracking function group 1202 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0193] Fig.13 An example media component stream switching 1300 to a different network slice in accordance with the present disclosure is shown. Fig.13 The embodiment of media component stream switching 1300 shown in FIG. 1 is for illustration only. Fig.13 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0194] like Fig.13 As shown, network-assisted media component stream switching 1300 can be performed for a media service component stream 1304 between different network slices 602a and 602n. When media component streams 1304 and 1306 are delivered using different network slices 602a and 602n, and the UE 606 and the network can observe that the network slice 602a cannot provide the required QoS of the media component stream 1304, the media component stream 1304 can be switched to a different network slice 602n to enhance the performance of the media service component stream 1304 relative to all other media component streams 1306 in the network slice 602.

[0195] To allow switching, the application service provider provides certain types of information as shown below. Switching condition information can be provided for parameters. The switching condition information indicates when to switch a specific media component flow from one network slice to another. Such information can be in the following form as shown in Table 8.

[0196] Table 8-Switching condition information

[0197]

[0198] For each media component stream, the application service provider can configure the switching value of the set of application and slice parameters. During the execution of the media service, if one of the parameters related to the stream drops below the indicated switching value, the media component stream is switched to the configured slice ID. The switching interval information indicates the amount of time to perform the switch before the media component streams are restored to the original slices they were supplied to run. The switching time information indicates the time when the switch is allowed. The switching stream priority information provides priority information about the slice to which each media component stream can be switched among the set of slices to which the stream can be switched. The coverage area information indicates that users in the coverage area (e.g., a geographic area, such as a cell ID list, geographic coordinates, etc.) can be switched to other slices. The UE 606 list indicates a list of users whose streams can be switched (e.g., a priority user list).

[0199] UE 606 may request switching of media component streams between different network slices. In addition to network-assisted switching of media component streams between different network slices, the UE may also request stream switching of media component streams between different network slices.

[0200] The UE 606 has metrics related to the media component streams and buffer status information of different media component streams. Based on this information, the user equipment 606 can trigger a message to the application function managing the media service to switch one or more media component streams 1304 to different network slices 602n. Such a message according to the UE 606 can include the following information shown in Table 9.

[0201] Table 9 - Information elements in a UE-based message for requesting switching of a media component stream to a different slice

[0202]

[0203] When the application function in the network receives the above information from UE 606, the application function can reconfigure the delivery parameters to assist in sending the requested media component stream in the slice requested by UE 606. In addition, based on the cause information received from UE 606, the application function can perform the following functions.

[0204] If the cause indicates that one or more parameters of the network slice are performing poorly, the application function may perform any of the following operations. One function may include reorganizing slice resources, such as adding or removing network functions in the network slice to help enhance slice performance. Other functions may include increasing computing capacity or removing bottlenecks based on parameter performance information. Other functions may include reconfiguring network parameters of the slice, such as allowed throughput, bandwidth, etc.

[0205] If the cause indicates that the network slice is unreachable by the user equipment, the application function may perform any of the following actions. The application function may check with a network analysis function (such as 3GPP NWDAF) to collect metrics about the unreachable slice in question. If the unreachable slice for the UE is also unreachable for all users as indicated above, the application function may restart all physical and virtual resources. If all users have the same experience for this network slice, the application function may interface with the application service provider to see if the unreachable network slice can be de-provisioned and de-allocated.

[0206] although Fig.13 An example media component flow switching 1300 to a different network slice is shown, but may be Fig.13 Various modifications may be made. For example, the number and placement of the various components of the media component flow switch 1300 may vary as needed or desired. In addition, the media component flow switch 1300 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0207] Fig.14 An example multi-component flow segmentation 1400 is shown in accordance with the present disclosure. Fig.14 The embodiment of multi-component stream segmentation 1400 shown in FIGURE 1 is for illustration only. Fig.14 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0208] like Fig.14 As shown, network-assisted stream splitting can be performed on the media service component stream 1304. In the event that the complete stream 1304 cannot be switched from the network slice 602a to another network slice 602n, as is not possible as previously described, the media service component stream 1304 in the underperforming network slice can be split into a first media service component stream 1304a and a second media service component stream 1304b. The second media service component stream 1304b can be transmitted to the alternative network slice 1304n.

[0209] In order to facilitate stream segmentation, the stream switching condition information previously described in the present disclosure is enhanced with the following information shown in FIG. 10 .

[0210] Table 10 - Information elements in UE-specific messages for media component stream splitting

[0211] Stream Id Split function Send the split stream to the slice id (instead of slice) Stream id 1 ..

[0212] For each flow, the application service provider can provide split function information to split the flow and send the split flow in a specific network slice. Possible values ​​of the split function include an even split value, a every nth packet / frame value, a every "time interval" value, etc. The even split value may indicate that the packet or frame is split evenly between the original network slice and the configured alternative slice. The every nth packet / frame value indicates that every nth packet / frame is sent on the configured alternative slice. The every "time interval" value indicates that the packet / frame is to be sent in the alternative network slice when the configured time interval expires. Once the packet / frame is sent, the timer is reset and the AS can wait until it expires again to send in the alternative network slice.

[0213] although Fig.14 A multi-component stream split 1400 is shown, but may be Fig.14 Various modifications may be made. For example, the number and placement of the various components of multi-component flow segmentation 1400 may vary as needed or desired. Furthermore, multi-component flow segmentation 1400 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0214] Fig.15 Example buffer compensation 1500 for a media component stream according to the present disclosure is shown. Fig.15 The embodiment of buffer compensation 1500 shown in FIG. 1 is for illustration only. Fig.15 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0215] like Fig.15 As shown, UE 606 requests splitting of media component streams 1304 between different network slices 602. In addition to network-assisted splitting of media component streams between different network slices, UE 606 may also request stream splitting of media component streams between different network slices 602a and 602n.

[0216] The UE 606 has metrics related to the media component streams and buffer status information of different media component streams. Based on this information, the UE 606 can trigger a message to the application function 1502 managing the media service to split one or more media component streams and send packets / frames of the split streams in different network slices. The application function can be Figure 2 The server 200 shown in FIG. 6 shows that such a message according to the UE 606 may include the following information.

[0217] Table 11 - Information elements of a UE-based message for requesting splitting of a media component stream

[0218]

[0219]

[0220] When the application function 1502 in the network receives the above information from the UE 606, the application function 1502 can reconfigure the delivery parameters to assist in segmenting the requested media component stream requested by the UE 606. In addition, based on the cause information received from the UE 606, the application function 1502 can perform certain functions. If the cause indicates that one or more parameters of the network slice are not performing well, the application function 1502 can perform any of reorganizing slice resources, increasing computing capacity or removing bottlenecks, reconfiguring network parameters, and reconfiguring network parameters. The application function 1502 can reorganize slice resources, such as adding or removing network functions in the network slice to help enhance slice performance. The application function 1502 can increase computing capacity or remove bottlenecks based on parameter performance information. The application function 1502 can reconfigure network parameters of the slice, such as allowed throughput, bandwidth, etc.

[0221] If the cause indicates that the network slice is unreliable for the UE 606, the application function 1502 may perform other functions. The application function 1502 may check with a network analysis function (such as 3GPP NWDAF) to collect metrics about the unreliable slice in question. If the unreliable slice of the UE as indicated above is also unreliable for all users, the application function 1502 may restart all physical and virtual resources. If all users have the same experience for the slice, the application function 1502 may interface with the application service provider to see if the unreliable network slice can be de-provisioned and de-allocated. The application function 1502 may add UPF / MEC for synchronization.

[0222] If a stream switching or splitting decision cannot be made to resolve the synchronization issue, an alternative approach is to enhance the QoS of the network slice where the media component stream is being exploited. To facilitate performance enhancement, the options available to the UE / network may include adding additional UPF / ULCL classifiers / branching points, adding additional AS servers, adding edge computing capabilities, etc.

[0223] Adding additional UPF / ULCL classifiers / branching points may include requesting to add UPF / ULCL classifiers / branching points to the network slice. These new capabilities may provide quantitative and qualitative enhancements to the network slice. Adding additional AS servers may include requesting to add application servers to the network slice. These new application servers may provide additional capacity for processing to the network slice, which may help in situations where synchronization is not possible due to insufficient computing resources in the network slice. Adding edge computing capabilities may include deploying edge application servers and connecting to the network slice. The edge application servers will provide additional computing capacity to help with any processing related to ensuring synchronization issues.

[0224] The present application previously described a process in which the network will split or switch media component streams between different network slices. To allow stream splitting / switching, the application function 1502 in the network can implement a splitting / switching strategy. For this process, the UE will send a buffer status message with information of each of the media component streams of the service to the application function 1502 in the network. When the application function 1502 in the network receives this information from the UE 606, a splitting / switching strategy can be defined.

[0225] The application function 1502 may decide that the flow with the lower or lowest buffer status may be compensated by sending the flow service for "n" number of seconds / milliseconds (the flow compensation time) via the highest performing network slice. The highest performing network slice may be inferred based on: a) the buffer status of the constituent media component flows (e.g., which media component flows have full or nearly full buffer status compared to other media component flows); or b) may be based on network measurements to show the performance of the network slice of interest. The amount of splitting or switching may be based on the processes previously described in this disclosure.

[0226] The above process of compensating for a lower or lowest buffered media component flow may be enhanced by an alternative process wherein, instead of sending "n" number of seconds or milliseconds of streaming traffic via the highest performance network slice, the number of seconds or milliseconds to be sent is determined based on the difference in buffer status information of the lower buffered media component flow compared to the higher buffered media component flow. The difference may be normalized based on packet / frame size to determine the number of seconds / milliseconds of media component streaming traffic to be sent via the higher or highest performance network slice.

[0227] The above process of compensating for a lower or lowest buffer status media component stream can be enhanced in an alternative process wherein such compensation process a) is performed every "m" milliseconds / seconds (compensation interval); or b) is performed whenever there are other updates regarding the lower or lowest performance media component stream based on UE 606.

[0228] The above two compensation processes can be further enhanced in an alternative process, wherein such compensation for the lower / lowest buffered media component stream is performed for the following time period (total compensation time): a) the total time period "t" specified by the application service provider; or b) until the UE 606 returns to the application function 1502 in the network and all buffers have returned to normal, i.e., they are properly compensated. When the application function 1502 in the network receives such a message from the UE 606, the compensation process can be stopped for the amount of time "t", or until the UE 606 issues another compensation request message.

[0229] although Fig.15 Buffer compensation 1500 is shown, but can be Fig.15 Various modifications may be made. For example, the size, shape, and dimensions of the buffer compensation 1500 and its various components may vary as needed or desired. In addition, the number and placement of the various components of the buffer compensation 1500 may vary as needed or desired. In addition, the buffer compensation 1500 may be used in any other suitable network slicing process, not limited to the specific process described above.

[0230] Fig.16 An example flow chart 1600 for stream switching and segmentation for buffer compensation according to the present disclosure is shown. For ease of illustration, Fig.16 The flow switching and segmentation flow diagram 1600 is described as using Figure 2 and Figure 3 However, the stream switching and segmentation flowchart 1600 can be used with any other suitable system and any other suitable electronic device.

[0231] like Fig.16 As shown, the server 200 may receive buffer status information of all media component streams from the UE 606 at step 1601. The UE 606 may measure the component streams related to the buffer status. The buffer status information may be processed by the UE and transmitted to the server 200.

[0232] In step 1602, the server 200 may determine whether the media component streams are synchronized. The QoS of each of the media component streams may be identified by the server 200 and compared to the expected QoS of the media. The media component streams may be compared to other media component streams for synchronization of the corresponding services.

[0233] In step 1604, when the media component streams are synchronized, the server 200 may continue the media component stream delivery. When the media component streams are determined to be synchronized in step 1602, the media component streams may continue to be transmitted through the current network slice.

[0234] In step 1606, when the media component stream is determined to be out of sync, the server 200 may determine whether the network slice is unreachable. When the media component stream is determined to be out of sync in step 1602, information may be requested from the network slice to determine the communicability of the network slice.

[0235] In step 1608, when the network slice is determined to be not unreachable, the server 200 may determine whether the network slice is unreliable. When the network slice is determined to be reachable in step 1606, the information received from the network slice may be analyzed for reliability.

[0236] In step 1610, when the network slice is determined to be unreachable, the server 200 may perform stream switching. When the network slice is determined to be unreachable in step 1606, all media component streams may be moved to other network slices that are reachable and can handle the QoS of the media component streams.

[0237] In step 1612, when the network slice is determined to be unreliable, the server 200 may perform stream splitting. When the network slice is determined to be unreliable in step 1608, splitting may be performed on the media component stream. The media component stream may be split into at least two sub-component streams. The server 200 may determine whether one or more of the sub-component streams can remain on the original network slice. The sub-component streams may be moved to other network slices that can handle the transmission.

[0238] In step 1614, the server 200 may deliver the media component stream based on the stream segmentation or the stream switching. The switched media component stream or the segmented media subcomponent stream may continue to be monitored for synchronization of the corresponding media.

[0239] To facilitate stream synchronization when different media component streams are delivered using different network slices, the application service provider can configure the following information for the media service. This configuration can be applied to the M1 service provisioning interface defined in TS 26501 and TS 26512.

[0240] Table 12 - Service configuration information according to the application service provider to enable stream switching and splitting for stream synchronization purposes

[0241]

[0242]

[0243]

[0244]

[0245] In the main embodiment, a method is described for splitting a media component stream delivered in a network slice, so that the split stream can be delivered using multiple alternative network slices in order to maintain synchronization aspects between different media components delivered through multiple network slices. To this end, a method is proposed for splitting the media component stream through a split function configuration specified by an application service provider.

[0246] In an alternative embodiment, a variation of stream segmentation may be performed using the type of media component packet / frame. For example, if a video stream delivered using a network slice (e.g., an emBB network slice) is affected by poor QoS for any reason, the UE / network may make a stream segmentation decision 1504 to segment the stream packets / frames into multiple network slices. Instead of simply looking at the packet count for the segmentation decision, the type of video packet / frame (e.g., "I" frame, "P" frame, "B" frame) may be looked at for the segmentation function. Examples of such segmentation decisions include:

[0247] Stream segmentation enables all "I" frames to be delivered through the same network slice, while "P" and "B" frames can be offloaded to different network slices. Stream reconstruction at the UE may be easier if all "I" frames are delivered through the same network slice.

[0248] Stream segmentation based on GOP (Group of Pictures) size, i.e. all frames belonging to the same GOP are delivered on the same network slice, while different GOPs may be decided to be delivered in alternative network slices.

[0249] Stream segmentation enables “n” consecutive GOPs to be delivered through the same network slice, while the next GOP frames can be offloaded to a different network slice.

[0250] In different embodiments of the present disclosure, methods for stream segmentation based on the segmentation function configuration according to the application service provider and the type of media stream packets / frames are described. This alternative embodiment describes a method for stream segmentation based on stream resolution.

[0251] Some media services require sending multi-resolution streams to end users to avoid lossy conditions at the UE. For example, depending on the UE viewport, a high-quality stream covering the UE viewport can be sent to the UE, and for all other parts of the view, a lower quality stream is sent. In this case, the goal is that the user will have continuity of service even if there are rapid viewport changes, and until the high-quality stream of the updated viewport is retrieved and displayed to the UE. This method of sending multiple quality streams can be advantageous during the stream segmentation decision 1504. If the network slice carrying the video stream is affected by poor QoS, other stream segmentation decisions 1504 can be made, that is, sending higher or lower quality streams through different network slices. The conditions for when to call this process are configured by the application service provider. When these conditions are met, the media synchronization function (both the slice-specific synchronization function and the parent media service level synchronization function) can perform stream segmentation and send these segmented streams through different network slices.

[0252] although Fig.16 An example of an example flow chart 1600 for stream switching and segmentation for buffer compensation is shown, but may be used for Fig.16 For example, although shown as a series of steps, Fig.16 The various steps in can overlap, occur in parallel, or occur any number of times.

[0253] Fig.17 An example method 1700 for network-assisted stream synchronization of media services using network slicing according to the present disclosure is shown. For ease of illustration, Fig.17 The method 1700 is described as using Figure 2 and Figure 3 However, the method 1700 may be used with any other suitable system and any other suitable electronic device.

[0254] like Fig.17 As shown, at step 1702, the server 200 receives expected stream parameters. The expected stream parameters of multiple media streams provided by at least one network slice may be received from an application service provider. A stream transmission threshold may also be received from the application service provider.

[0255] At step 1704, the server 200 receives actual stream parameters. The actual stream parameters may be received for each of the media streams. The multiple media streams may be provided via multiple network slices. The actual stream parameters may be received from the multiple network slices as sample frames for each of the media streams. The actual stream parameters may be measured based on the sample frames.

[0256] At step 1706, the server 200 determines streaming condition information. The streaming condition information may be determined for each of the media streams. The streaming condition information is based on a comparison of actual stream parameters with expected stream parameters.

[0257] A set of tracing functions may be established in each network slice to exchange synchronization information with each other tracing function. A tracing group of tracing functions may also be established in the network slice. Each tracing function in the tracing function group may be configured to exchange synchronization information only with each other tracing function in the tracing function group. Packet forwarding actions may be performed based on the exchanged synchronization information.

[0258] At step 1708, the server 200 performs stream synchronization based on the stream transmission condition information. When the stream transmission condition information of the media stream exceeds the stream transmission threshold, the media stream may be switched to a different network slice, or may be split into a first media stream and a second media stream, wherein the second media stream is switched to a different network slice from the first media stream.

[0259] although Fig.17 An example of a method 1700 for network-assisted stream synchronization of a media service using network slicing is shown, but may be used for Fig.17 For example, although shown as a series of steps, Fig.17 The various steps in can overlap, occur in parallel, or occur any number of times.

[0260] Fig.18A and Fig.18B Example workflow relocations 1800 - 1804 are shown in accordance with the present disclosure. Fig.18A and Fig.18B The embodiments of workflow relocation 1800-1804 shown in FIG. 1 are for illustration only. Fig.18A and Fig.18B The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0261] like Fig.18A As shown, the complete workflow relocation 1800 transfers all application service components 1806 that are part of the workflow running within the source network 1808 to the target network 1810. The application service components 1806 (components 1, 2, 3, and 4) of the workflow in the source network 1808 are moved to the target network 1810. All configurations of the application service components 1806, properties of the network paths, and expected key performance indicators (KPIs) can be migrated to the target network 1810 as is. In the case of deployment in this manner, relocating the application service components 1806 is seamless, and the performance of the application will be very similar to the performance of all application service components 1806 in the source network 1808, provided that appropriate resources are provisioned in the target network 1810 based on the expected KPIs.

[0262] like Fig.18B As shown, partial workflow relocation 1802 can transfer a subset of application service components 1806 that are part of a workflow running in a source network 1808 to a target network 1810. In the case of partial workflow relocation 1802, a subset of application service components 1806 (components 2 and 4) of the workflow in the source network 1808 are moved to the target network 1810, while the remaining application service components 1806 (components 1 and 3) can remain in the source network 1808.

[0263] although Fig.18A and Fig.18B An example workflow relocation is shown, but Fig.18A and Fig.18B Various changes may be made. For example, the number and placement of the various components of workflow relocation 1800-1804 may vary as needed or desired. Furthermore, workflow relocation 1800-1804 may be used for any other suitable network slicing process, not limited to the specific process described above.

[0264] Fig.19 An example server group relocation 1900 according to the present disclosure is shown. Fig.19 The embodiment of server group relocation 1900 shown in FIG. 1 is for illustration only. Fig.19 The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0265] like Fig.19 As shown, server group relocation 1900 can be used to transfer application service components 1806 that have functional dependencies. Some application service components 1806 within a workflow have tight dependencies on other application service components 1806 in the workflow. This tight dependency may be due to a variety of reasons, such as performance, security, compliance, etc. In the case of tight dependencies, when there is a functional dependency between different application service components 1806 in the workflow, and if a decision is made to relocate one or more application service components 1806, the dependent application service components 1806 may also be relocated.

[0266] Prior to the server group relocation, application servers 2 and 4 were part of the relocated server group 1902. If the decision to relocate server 2 is made by the application manager, AF, UE, or ASP, then the dependent server 4 will also be relocated along with server 2. If for any reason the dependent application service component 1806 cannot be relocated, then the application service components in the relocated server group 1902 may not be relocated.

[0267] For multiple relocation server groups 1902 within a workflow, as part of the service provisioning process, the ASP configures the relocation server groups 1902. When a decision is made to relocate an application service component 1806, all relocation server groups 1902 of which the application service currently to be relocated is found to be a member are checked to view all dependencies between them and other application service components 1806 in the workflow, and a decision is also made to relocate all of these dependent application service components 1806. If a dependent application service component 1806 cannot be relocated, the application service provider can determine whether only the application service component currently to be relocated can be relocated individually.

[0268] although Fig.19 An example server group relocation is shown, but Fig.19 Various changes may be made. For example, the number and placement of the various components of server group relocation 1900 may vary as needed or desired. In addition, server group relocation 1900 may be used in any other suitable network slicing process, not just limited to the specific process described above.

[0269] FIG. 20A to FIG. 20C Example workflow relocation 2000-2004 to a user device according to the present disclosure is shown. FIG. 20A to FIG. 20C The embodiments of workflow relocation 2000-2004 shown in FIG. 2 are for illustration only. FIG. 20A to FIG. 20C The scope of the present disclosure is not limited to any particular implementation of an electronic device.

[0270] like FIG. 20A to FIG. 20C As shown, application service component 1806 can be moved by UE 2006 workflow relocation. UE 2006 can receive a workflow description from the AF or application manager that manages the session in the source network. Based on the expectation of certain conditions (for example, UE 2006 may move to a different location at some time), UE 2006 can request the AF that manages the session to relocate the workflow. To request the relocation of the workflow, use Figure 4 The UE 2006 of the M5d interface shown may send an API request for workflow relocation to the target location. As part of the API request, the following information elements in Table 13 may be provided to the AF.

[0271] Table 13

[0272]

[0273]

[0274] When the AF managing the session receives an API request with the above information elements, the AF can attempt to perform workflow relocation, provided that the KPIs in the API can be met. If the KPIs can be met, the AF can communicate with an appropriate target network 1810 that is closer to the expected location of UE 2006 within a given relocation time period. The AF can send detailed workflow profile information to the application manager in the target network 1810 to instantiate different application service components and necessary network paths, so that the service can be started and run before relocation can occur. Once the relocation time period is approaching, the target network 1810 can wait for the time period indicated in the "relocation test interval" to see if the UE service arrives at the target network 1810. If the UE 2006 service arrives at the target network 1810 before the expiration of the above relocation test interval, the relocation attempt is considered successful and the session should continue as expected. On the other hand, if the UE 2006 service does not arrive within the above relocation test interval time period, the relocation condition is not evaluated (for example, the UE 2006 may decide not to change the location after sending the API request to the AF). In this case, relocating resources can be terminated.

[0275] When UE 2006 receives the workflow profile information, UE 2006 can request to relocate the workflow resources to the target network 1810. Alternatively, UE 2006 can have certain processing capabilities, and UE 2006 can use these capabilities to perform workflow processing. In this case, UE 2006 may be interested (for example, authorized by the end user through certain actions) or be supplied to perform certain processing on the workflow of the media service. Therefore, UE 2006 can request that certain processing tasks of the workflow be loaded onto the device, thereby facilitating the end-to-end processing of the workflow. With this facility, some application service components that were originally running in a network (for example, a cloud, edge, etc.) can now run in UE 2006 to utilize the processing capabilities of UE 2006.

[0276] In order to load some processing tasks of the workflow, UE 2006 can exchange the same information elements with the AF managing the session through the M5d interface. However, in this case, the semantics of some fields are as follows.

[0277] The reduced application service component list field may indicate a list of application service components that the UE 2006 is willing to run on the device. Therefore, any associated processing of these application service components may now be released from the network.

[0278] The list field of the application data descriptor acts as a pointer to a structure where the AF can fill in data before allowing the task to run in the UE 2006. The sub-elements of this information element will be used as intermediate configuration data, binary application data and log data.

[0279] The intermediate configuration data provides current configuration data of the task running in the network before the task is moved to the UE 2006. When the application service component is moved to run in the UE 2006, the configuration data will be used to configure the application service component.

[0280] The binary application data provides application data corresponding to the execution data of the application service components running in the network. When the application service components are relocated to the UE 2006, the binary application data can be used by the application service components to continue their execution instead of restarting the execution of the components.

[0281] The log data includes log information related to the application service components running in the network before the application service components are determined to be relocated to the UE 2006. When the application service components are relocated to the UE 2006, the log data can be used for important tasks (eg, tracing).

[0282] Determining the split point of network processing is one of the evolving problems in AI. Using the above structure, UE 2006 can signal the split point of processing to the network, so UE 2006 can indicate certain parts of processing in the device, thereby offloading some processing in the network (cloud).

[0283] In addition to the end-to-end KPIs for a service or session configured by the application service provider, KPIs can also be defined for a relocated server group. Some of the KPI parameters that can be defined for a relocated server group include application latency, throughput, bandwidth, packet error rate, reliability, coverage, and inter-task delay.

[0284] For example, the end-to-end KPI defines the expected KPI of the application service components in the service, and the KPI of the relocation service group defines the expected KPI of the application service components in the relocation server group. The AF managing the session ensures that the given KPI of the relocation service group and the application service components in the relocation server group jointly meet the KPI condition. Based on the above, it can be clearly seen that the KPI of the relocation server group is a subset of the end-to-end KPI configured for the entire service.

[0285] For different relocation service groups configured by the application service provider for media services, a set of KPIs can be defined by the application service provider for each application service in each relocation service group (node ​​KPI). In addition, for each link of interconnected relocation service components in the main workflow, link KPIs can be supplied by the application service provider.

[0286] When there are different node KPIs for application service components within the relocated service group and the link KPIs that interconnect them, the AF managing the session can check whether the provisioned KPIs can be provided at the target network for the relocated server group. If the KPIs cannot be guaranteed after relocation of the relocated server group, the decision can be left to the application service provider to determine whether the failure to meet the KPIs for the relocated service group can be ignored and the relocation can still occur.

[0287] To support the relocation server group KPI, the service provisioning information may be enhanced to include the following information shown in Table 14 as part of the M1d provisioning information from the application service provider to the AF when the service is provisioned.

[0288] Table 14

[0289]

[0290]

[0291] although FIG. 20A to FIG. 20C An example workflow relocation is shown, but FIG. 20A to FIG. 20C Various changes may be made. For example, the number and placement of the various components of workflow relocation 2000-2004 may vary as needed or desired. Furthermore, workflow relocation 2000-2004 may be used for any other suitable network slicing process, not limited to the specific process described above.

[0292] Fig.21 An example of a network-assisted stream synchronization method 2100 for a media service using network slicing according to the present disclosure is shown. For ease of illustration, Fig.21 The method 2100 is described as using Figure 2 and Figure 3 However, the method 2100 may be used with any other suitable system and any other suitable electronic device.

[0293] like Fig.21 As shown, at step 2102, the electronic device 300 receives streaming condition information. The streaming condition information may be received from a slice synchronization function. The streaming condition information may be based on a comparison of actual stream information of the media stream and expected stream parameters associated with an application service provider.

[0294] In step 2104, the electronic device 300 can determine the time to decode and present the media content. The time to decode and present the media content can be determined based on the streaming condition information. The time to decode and present the media content can be provided in one or more of the media component streams, and directly from the synchronization application function. In an embodiment, the time to decode and present the media content can be provided from an application service provider.

[0295] In step 2106, the electronic device 300 can identify parameter changes between the current time and the determined time. The components of the media content can be identified in the specified component stream with the timestamp. The timestamp can be compared with the time of decoding and presenting the media. The difference between the timestamp and the time of decoding the media can be used as the parameter change of the specified media component stream.

[0296] At step 2108, the electronic device 300 may update the buffer size. The tracking function or synchronization application function in the specified network slice may adjust the timing or buffering of the media component stream to accommodate the identified parameter changes. The updated buffer size allows the media content to be synchronized when received through different network slices.

[0297] although Fig.21 An example of a method 2100 for network-assisted stream synchronization of a media service using network slicing is shown, but may be used for Fig.21 For example, although shown as a series of steps, Fig.21 The various steps in can overlap, occur in parallel, or occur any number of times.

[0298] Although the present disclosure has been described by exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. Any description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

[0299] According to an embodiment, a method performed by an application function (AF) entity in a mobile communication system is provided. The method includes: identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement, and synchronizing the first media data and the second media data.

[0300] According to an embodiment, an application function (AF) entity in a mobile communication system is provided. The AF entity includes a transceiver and a controller coupled to the transceiver, the controller being configured to: identify first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of a UE via a second network slice configured with a second QoS requirement, and synchronize the first media data with the second media data.

[0301] According to an embodiment, a method performed by a user equipment (UE) in a mobile communication system is provided. The method includes: receiving first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and sending second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data.

[0302] According to an embodiment, a user equipment (UE) in a mobile communication system is provided. The UE includes a transceiver and a controller coupled to the transceiver, the controller being configured to: receive first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and send second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data.

[0303] According to an embodiment, a method performed by an application function (AF) entity in a mobile communication system is provided. The method includes: identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement, and synchronizing the first media data and the second media data.

[0304] The method also includes: switching a network slice of the first media data from a first network slice configured with a first QoS requirement to a third network slice configured with a third QoS requirement higher than the first QoS requirement. The first media data is sent to the UE via the third network slice.

[0305] The method also includes receiving information associated with the UE from a media session processor of the UE using an M5d interface.

[0306] The information associated with the UE is used to establish a media channel between the AF and the UE.

[0307] According to an embodiment, an application function (AF) entity in a mobile communication system is provided. The AF entity includes a transceiver and a controller coupled to the transceiver, the controller being configured to: identify first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of a UE via a second network slice configured with a second QoS requirement, and synchronize the first media data with the second media data.

[0308] The controller is further configured to: switch a network slice of the first media data from a first network slice configured with a first QoS requirement to a third network slice configured with a third QoS requirement higher than the first QoS requirement. The first media data is sent to the UE via the third network slice.

[0309] The controller is also configured to receive information associated with the UE from a media session processor of the UE using the M5d interface.

[0310] The information associated with the UE is used to establish a media channel between the AF and the UE.

[0311] According to an embodiment, a method performed by a user equipment (UE) in a mobile communication system is provided. The method includes: receiving first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and sending second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data.

[0312] The method also includes: receiving first media data from the AS entity via a third network slice configured with a third QoS requirement higher than the first QoS requirement.

[0313] The method also includes sending information associated with the UE to an application function (AF) entity using an M5d interface.

[0314] The information associated with the UE is used to establish a media channel between the AF and the UE.

[0315] According to an embodiment, a user equipment (UE) in a mobile communication system is provided. The UE includes a transceiver and a controller coupled to the transceiver, the controller being configured to: receive first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement, and send second media data to the AS entity via a second network slice configured with a second QoS requirement. The first media data is synchronized with the second media data.

[0316] The controller is also configured to receive first media data from the AS entity via a third network slice configured with a third QoS requirement higher than the first QoS requirement.

[0317] The controller is also configured to send information associated with the UE to an application function (AF) entity using an M5d interface.

[0318] Fig. 22 The structure of a UE according to an embodiment of the present disclosure is shown.

[0319] like Fig. 22 As shown, the UE according to the embodiment may include a transceiver 2210, a memory 2220, and a processor 2230. The transceiver 2210, the memory 2220, and the processor 2230 of the UE may operate according to the communication method of the above-mentioned UE. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 2230, the transceiver 2210, and the memory 2220 may be implemented as a single chip. In addition, the processor 2230 may include at least one processor. In addition, Fig. 22 The UEs correspond to some of the client devices 108 - 116 .

[0320] The transceiver 2210 is collectively referred to as a UE receiver and a UE transmitter, and can send signals to / receive signals from a base station or a network entity. The signals sent to or received from a base station or a network entity may include control information and data. The transceiver 2210 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the low noise and down-converting the frequency of the received signal. However, this is only an example of the transceiver 2210, and the components of the transceiver 2210 are not limited to the RF transmitter and the RF receiver.

[0321] In addition, the transceiver 2210 may receive and output a signal to the processor 2230 through a wireless channel, and may transmit a signal output from the processor 2230 through a wireless channel.

[0322] The memory 2220 may store programs and data required for the operation of the UE. In addition, the memory 2220 may store control information or data included in the signal obtained by the UE. The memory 2220 may be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0323] The processor 2230 may control a series of processes so that the UE operates in the above manner. For example, the transceiver 2210 may receive a data signal including a control signal sent by a base station or a network entity, and the processor 2230 may determine the result of receiving the control signal and the data signal sent by the base station or the network entity.

[0324] Fig.23 The structure of a base station according to an embodiment of the present disclosure is shown.

[0325] like Fig.23 As shown, the base station according to the embodiment may include a transceiver 2310, a memory 2320, and a processor 2330. The transceiver 2310, the memory 2320, and the processor 2330 of the base station may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 2330, the transceiver 2310, and the memory 2320 may be implemented as a single chip. In addition, the processor 2330 may include at least one processor. In addition, Fig.23 The base station can be Figure 1 Network 102 Management in. Fig.23 The base station may support communications between a number of client devices 108 - 116 .

[0326] The transceiver 2310 is collectively referred to as a base station receiver and a base station transmitter, and can send / receive signals to / from a terminal (UE) or a network entity. The signals sent to or received from a terminal or a network entity may include control information and data. The transceiver 2310 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the frequency of the low noise and down-converting the received signal. However, this is only an example of the transceiver 2310, and the components of the transceiver 2310 are not limited to the RF transmitter and the RF receiver.

[0327] In addition, the transceiver 2310 may receive and output a signal to the processor 2330 through a wireless channel, and may transmit a signal output from the processor 2330 through a wireless channel.

[0328] The memory 2320 may store programs and data required for the operation of the base station. In addition, the memory 2320 may store control information or data included in the signal obtained by the base station. The memory 2320 may be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0329] The processor 2330 may control a series of processes so that the base station operates in the above manner. For example, the transceiver 2310 may receive a data signal including a control signal sent by the terminal, and the processor 2330 may determine the result of receiving the control signal and the data signal sent by the terminal.

[0330] Fig.24 is a block diagram showing the internal structure of a network entity according to an embodiment of the present disclosure.

[0331] like Fig.24 As shown, the network entity of the present disclosure may include a transceiver 2410, a memory 2420, and a processor 2430. The transceiver 2410, the memory 2420, and the processor (or controller) 2430 of the network entity may operate according to the communication method of the above-mentioned network entity. However, the components of the terminal are not limited thereto. For example, the network entity may include more or fewer components than those described above. In addition, the processor 2430, the transceiver 2410, and the memory 2420 may be implemented as a single chip. In addition, the processor 2430 may include at least one processor. In addition, Fig.24 The network entities include Figure 1 in network 102.

[0332] According to the present invention, the network entity includes at least one entity of the core network. For example, the network entity includes access and mobility management function (Access And Mobility Management Function, AMF), session management function (Session Management Function, SMF), policy control function (Policy control function, PCF), network resource library function (Network Repository Function, NRF), user plane function (User Plane Function, UPF), network slice selection function (Network Slicing Selection Function, NSSF), authentication server function (Authentication Server Function, AUSF), unified data management (Unified Data Management, UDM) and network exposure function (Network Exposure Function, NEF). However, the network entity is not limited to this.

[0333] The transceiver 2410 is collectively referred to as a network entity receiver and a network entity transmitter, and can send / receive signals to / from a base station or UE. The signals sent to or received from a base station or UE may include control information and data. In this regard, the transceiver 2410 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying low noise and down-converting the frequency of the received signal. However, this is only an example of the transceiver 2410, and the components of the transceiver 2410 are not limited to the RF transmitter and the RF receiver.

[0334] In addition, the transceiver 2410 may receive and output a signal to the processor 2430 through a wireless channel, and transmit a signal output from the processor 2430 through a wireless channel.

[0335] The memory 2420 may store programs and data required for the operation of the network entity. In addition, the memory 2420 may store control information or data included in the signal obtained by the network entity. The memory 2420 may be a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media.

[0336] The processor 2430 may control a series of processes so that the network entity operates according to the above contents. For example, the transceiver 2410 may receive a data signal including a control signal, and the processor 2430 may determine a result of receiving the data signal.

[0337] According to an embodiment, an apparatus includes: a communication interface configured to receive expected stream parameters of multiple media streams provided through at least one network slice from an application service provider, and to receive actual stream parameters of each of the media streams; and a processor operably coupled to the communication interface, the processor configured to determine stream transmission condition information for each of the media streams, wherein the stream transmission condition information is based on a comparison of the actual stream parameters with the expected stream parameters, and to perform stream synchronization based on the stream transmission condition information.

[0338] Wherein, multiple media streams are provided through a single network slice, and the processor is configured to measure actual stream parameters in the single network slice to receive the actual stream parameters.

[0339] A plurality of media streams are provided through a plurality of network slices. The communication interface is configured to receive sample frames of each of the media streams from the plurality of network slices to receive actual stream parameters, and the processor is configured to measure the actual stream parameters based on the received sample frames.

[0340] The plurality of media streams are provided through the plurality of network slices. The processor is further configured to establish a set of tracking functions in each of the network slices, each tracking function is configured to exchange synchronization information with other tracking functions, and the communication interface is further configured to perform packet forwarding actions based on the exchanged synchronization information.

[0341] Multiple media streams are provided through multiple network slices, the processor is further configured to set up a group of tracing functions in the network slices, each tracing function in the tracing function group is configured to exchange synchronization information only with each other tracing function in the tracing function group, and the communication interface is further configured to perform packet forwarding actions based on the exchanged synchronization information.

[0342] The communication interface is also configured to receive a streaming condition threshold from an application service provider, and the processor is further configured to switch the media stream to a different network slice when the streaming condition information of the media stream exceeds the streaming condition threshold.

[0343] The communication interface is also configured to receive a streaming condition threshold from an application service provider, and the processor is also configured to split the media stream into a first media stream and a second media stream when the streaming condition information of the media stream exceeds the streaming condition threshold, and to switch the second media stream to a network slice different from the first media stream.

[0344] The communication interface is also configured to receive a request to switch at least part of the media stream from the user equipment, and the processor is also configured to switch at least part of the media stream to a different network slice.

[0345] The method includes receiving expected stream parameters of a plurality of media streams provided through at least one network slice from an application service provider, receiving actual stream parameters of each of the media streams, determining stream transmission condition information for each of the media streams, wherein the stream transmission condition information is based on a comparison of the actual stream parameters with the expected stream parameters, and performing stream synchronization based on the stream transmission condition information.

[0346] Multiple media streams are provided through a single network slice, and the method includes: measuring actual stream parameters in the single network slice for receiving the actual stream parameters.

[0347] A plurality of media streams are provided through a plurality of network slices, and the method comprises: receiving a sample frame of each of the media streams from the plurality of network slices for receiving an actual stream parameter, and measuring the actual stream parameter based on the received sample frame.

[0348] Multiple media streams are provided through multiple network slices, and the method also includes establishing a set of tracking functions in each of the network slices, each tracking function is configured to exchange synchronization information with each other tracking function, and perform packet forwarding operations based on the exchanged synchronization information.

[0349] Multiple media streams are provided through multiple network slices, and the method also includes establishing a group of tracing functions in the network slice, each tracing function in the tracing function group is configured to exchange synchronization information only with each other tracing function in the tracing function group, and perform packet forwarding operations based on the exchanged synchronization information.

[0350] The method also includes receiving a streaming condition threshold from an application service provider, and when the streaming condition information of the media stream exceeds the streaming condition threshold, switching the media stream to a different network slice.

[0351] The method also includes receiving a streaming condition threshold from an application service provider, and when streaming condition information of the media stream exceeds the streaming condition threshold, segmenting the media stream into a first media stream and a second media stream, and switching the second media stream to a network slice different from the first media stream.

[0352] The method also includes receiving a request to switch at least part of the media stream from the user equipment, and switching at least part of the media stream to a different network slice.

[0353] An apparatus comprises: a communication interface configured to receive streaming condition information from a slice synchronization function, wherein the streaming condition information is based on a comparison of actual stream information of a media stream and expected stream parameters associated with an application service provider; and a processor operably coupled to the communication interface, the processor configured to determine a time to decode and present media content based on the streaming condition information, identify a parameter change between a current time and the determined time, and update a buffer size based on the identified parameter change.

[0354] The processor is also configured to receive a streaming condition threshold from an application service provider when streaming condition information of the media stream exceeds the streaming condition threshold, request the media stream to be switched to a different network slice, and receive the media stream from the different network slice.

[0355] The processor is also configured to, when the streaming condition information of the media stream exceeds the streaming condition threshold, receive the streaming condition threshold from the application service provider, request the media stream to be segmented into the first media stream and the second media stream, switch the second media stream to a network slice different from the first media stream, and receive the second media stream from a network slice different from the first media stream.

[0356] The processor is further configured to send a request to the application function over the network slice to switch at least a portion of the media flow to a different network slice; and

[0357] At least a portion of a media stream is received from a different network slice.

Claims

1. A method performed by an application function (AF) entity in a mobile communication system, the method comprising: identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement; as well as The first media data and the second media data are synchronized.

2. The method according to claim 1, further comprising: Switching a network slice of the first media data from a first network slice configured with a first QoS requirement to a third network slice configured with a third QoS requirement higher than the first QoS requirement, The first media data is sent to the UE via the third network slice.

3. The method according to claim 1, further comprising: The M5d interface is used to receive information associated with the UE from the media session processor of the UE.

4. The method according to claim 3, wherein: The information associated with the UE is used to establish a media channel between the AF and the UE.

5. An application function (AF) entity in a mobile communication system, the AF entity comprising: Transceiver; as well as A controller is coupled to the transceiver and is configured to: identifying first media data of a user equipment (UE) via a first network slice configured with a first quality of service (QoS) requirement and second media data of the UE via a second network slice configured with a second QoS requirement; as well as The first media data and the second media data are synchronized.

6. The AF entity according to claim 5, wherein: The controller is also configured to: Switching a network slice of the first media data from a first network slice configured with a first QoS requirement to a third network slice configured with a third QoS requirement higher than the first QoS requirement, The first media data is sent to the UE via the third network slice.

7. The AF entity according to claim 5, wherein: The controller is also configured to: The M5d interface is used to receive information associated with the UE from the media session processor of the UE.

8. The AF entity according to claim 7, wherein: The information associated with the UE is used to establish a media channel between the AF and the UE.

9. A method performed by a user equipment (UE) in a mobile communication system, the method comprising: receiving first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement; as well as Sending second media data to the AS entity via a second network slice configured with a second QoS requirement; The first media data is synchronized with the second media data.

10. The method according to claim 9, further comprising: The first media data is received from the AS entity via a third network slice configured with a third QoS requirement higher than the first QoS requirement.

11. The method according to claim 9, further comprising: The M5d interface is used to send information associated with the UE to the Application Function (AF) entity.

12. The method according to claim 11, wherein: The information associated with the UE is used to establish a media channel between the AF and the UE.

13. A user equipment (UE) in a mobile communication system, the UE comprising: Transceiver; as well as A controller is coupled to the transceiver and is configured to: receiving first media data from an application server (AS) entity via a first network slice configured with a first quality of service (QoS) requirement; as well as Sending second media data to the AS entity via a second network slice configured with a second QoS requirement; The first media data is synchronized with the second media data.

14. The UE according to claim 13, wherein: The controller is also configured to: The first media data is received from the AS entity via a third network slice configured with a third QoS requirement higher than the first QoS requirement.

15. The UE according to claim 13, wherein: The controller is also configured to: The M5d interface is used to send information associated with the UE to the Application Function (AF) entity.

Images