Apparatus and method for allocating delays to media processing and transmission in a mobile communication network - Patents.com

Abstract

To provide an apparatus and method for allocating delays for media processing and transmission in a mobile communication network. The present disclosure relates to a communication technique and system for converging a 5G communication system with IoT technology to support a higher data transmission rate than that of the 4G system. The present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart or connected cars, healthcare, digital education, smart retail, security and safety services, etc.) based on 5G communication technology and IoT related technologies. The present disclosure describes a method and apparatus for setting the state of a bundle after the bundle has been transmitted during a smart security media.

Description

[Technical field]

[0001] The present disclosure relates to media processing in a mobile communication network, and more particularly to an apparatus and method for media processing and transmission delay allocation in a mobile communication network. [Background technology]

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic after the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are called Beyond 4G Network or Post LTE systems. To achieve high data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate path loss and increase transmission distance in ultra-high frequency bands, beamforming, massive multiple-input multiple-output (MSMO), full dimensional MIMO (FD-MIMO), array antennas, analog beam-forming, and large scale antenna technologies are being discussed for 5G communication systems. Furthermore, to improve the system network, technologies being developed for the 5G communication system include advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication, wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding) and advanced connection technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non orthogonal multiple access), and SCMA (sparse code multiple access) are being developed for the 5G system.

[0003] Meanwhile, the Internet is evolving from a human-centered connection network where humans generate and consume information to an IOT (Internet of Things) network that exchanges and processes information between distributed components such as things. IoE (Internet of Everything) technology is also emerging, in which big data processing technology through connection to cloud servers and other technologies are combined with IoT technology. In order to realize IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required, and in recent years, technologies such as sensor networks, M2M (Machine to Machine), and MTC (Machine Type Communication) for connecting things are being researched. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated between connected things to create new value in human life. IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies and various industries.

[0004] As a result, various attempts are being made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, M2M (Machine to Machine), and MTC (Machine Type Communication) can be realized using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access network (cloud RAN) as the aforementioned big data processing technology can also be seen as an example of the convergence of 5G technology and IoT technology.

[0005] The above information is provided only as background information to aid in the understanding of the present disclosure. No determination has been made, nor any assertion made, as to whether any of the above is applicable as prior art with respect to the present disclosure. Summary of the Invention [Problem to be solved by the invention]

[0006] Aspects of the present disclosure are directed to solving the problems and / or shortcomings discussed above and providing the advantages discussed below.

[0007] In order to make the most of limited frequency resources and network infrastructure, a mobile communication network adjusts various parameters related to transmission and reception of each terminal according to channel conditions to achieve maximum quality and capacity. Such parameters include bit rate, power, frequency, etc., and when the bit rate is adjusted, parameters such as channel coding rate and modulation method can also be changed in conjunction with each other.

[0008] DBI Signaling technology, which meets these requirements, is a network operation technique that maintains a target bit rate by adjusting transmission time rather than adjusting the bit rate when a change in transmission method is required due to a change in channel condition. Although DBI provides a basic method to deal with the shortage of wireless sections and residual delay, it has the following problems.

[0009] (1) In a Time Division Duplex (TDD) network operation in which the uplink and downlink share the same frequency band, the channel conditions of the uplink and downlink are likely to be similar, but in a Frequency Division Duplex (FDD) network operation in which the uplink and downlink use different frequency bands, the channel conditions of the uplink and downlink may be different. As shown in Figures 8 and 10, the delay signal message format cannot indicate the direction of the spare or insufficient delay, so the same delay increase / decrease is applied to both directions, which limits the efficient operation of radio resources.

[0010] In addition, the DelayBudgetReport message in Figure 8 is defined only for the section between the UE and gNB, and the query / allocation delay shown in the message in Figure 10 cannot be confirmed by network nodes located in the middle of the transmission path, such as 5GC and IMS, and therefore cannot be used for overall delay adjustment. In particular, the MEC (Mobile Edge Computing) shown in Figure 5 can perform additional functions such as improving media quality or stitching multiple videos to create a 360 video, but if the MEC can grasp the remaining / shortage information of delay and use part of the delay, efficient network operation and service quality can be achieved. The delay increase / decrease function, which is currently available only in the wireless section, needs to be extended to apply to all end-to-end transmission paths, including the wired section.

[0011] Additional aspects of the present disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the embodiments provided. [Means for solving the problem]

[0012] In order to solve the above problems, the present invention is a method for operating a first terminal, comprising the steps of: determining whether a first delay related to the first terminal is necessary; if the first delay is necessary, transmitting a delay message including the first delay information from the second terminal; receiving an assignment message including one or more node information from the second terminal in response to the delay message; determining whether the one or more node information included in the assignment message includes information of the first terminal; and, if the information of the first terminal is included, allocating the first delay.

[0013] In some examples, the delay message and the allocation message are Real-time Transport Protocol Control Protocol (RTCP) messages.

[0014] In some examples, the RTCP message includes at least one of direction information, allocation information, and information on one or more nodes to be assigned, and the delay message and the allocation message are determined by at least one of the direction information, allocation information, and information on one or more nodes to be assigned.

[0015] Another example of the present invention is a method for requesting a delay for a network node, comprising the steps of receiving a delay message requesting a first delay from a first terminal, determining whether a second delay is required for the network node, and if the second delay is required, adding the second delay information to the delay message, and transmitting the delay message with the second delay information added from a second terminal.

[0016] In yet another example of the present invention, a method for operating a second terminal includes the steps of receiving a delay message including delay information of one or more nodes, determining whether the delay of the one or more nodes is allocable, allocating the delay to the allocable node if the delay of the one or more nodes is allocable, and transmitting an allocation message including information on the allocable node to the one or more nodes.

[0017] In another example of the present invention, a method for allocating a delay of a network node includes the steps of receiving an allocation message including one or more node information from a second terminal, determining whether information of the network node is included in the one or more node information included in the allocation message, applying a second delay related to the network node if the information of the network node is included, deleting the second delay information from the allocation message after applying the second delay, and transmitting a delay message from which the second delay information has been deleted.

[0018] In another example of the present invention, a first terminal includes a transceiver unit capable of transmitting and receiving at least one signal, and a control unit coupled to the transceiver unit, wherein the control unit is configured to determine whether a first delay related to the first terminal is necessary, and if the first delay is necessary, transmit a delay message including the first delay information to a second terminal, receive an assignment message including one or more node information from the second terminal in response to the delay message, determine whether the one or more node information included in the assignment message includes information of the first terminal, and assign the first delay if the information of the first terminal is included.

[0019] In another example of the present invention, a network node for requesting a delay includes a transceiver unit capable of transmitting and receiving at least one signal, and a control unit coupled to the network node, the control unit being configured to receive a delay message requesting a first delay from a first terminal, determine whether a second delay is required for the network node, and if the second delay is required, add the second delay information to the delay message, and transmit the delay message with the second delay information added to it from a second terminal.

[0020] In yet another example of the present invention, a second terminal includes a transceiver unit capable of transmitting and receiving at least one signal, and a control unit coupled to the transceiver unit, wherein the control unit is configured to receive a delay message including delay information of one or more nodes, determine whether the delay of the one or more nodes is allocable, and if the delay of the one or more nodes is allocable, assign the delay to the allocable node, and transmit an allocation message including information for the allocable node to the one or more nodes.

[0021] In another example of the present invention, a network node for allocating a delay includes: a transceiver unit capable of transmitting and receiving at least one signal; and a control unit coupled to the transceiver unit, wherein the control unit is configured to receive an allocation message including one or more node information from a second terminal, determine whether information of the network node is included in the one or more node information included in the allocation message, apply a second delay related to the network node if the information of the network node is included, delete the second delay information from the allocation message after applying the second delay, and transmit a delay message with the second delay information deleted. Effect of the Invention

[0022] The present invention relates to an apparatus and method for solving the technical problems of the prior art introduced to respond to changes in transmission conditions in a mobile communication network through compression and transmission time adjustment.

[0023] Specifically, unlike the conventional technology that can adjust only the delay between the UE and the gNB, the present invention allows network nodes in the middle of the transmission path to request the required amount of delay, making it possible to utilize delay efficiently. The delay request procedure can be initiated only by the terminal, and delay allocation is centralized in the message receiving terminal that can grasp the entire delay status, so that requests from the message transmitting UE and the network node do not collide.

[0024] In addition, since the Delay RTCP message format proposed in the present invention can indicate the directionality of the requested or allocated delay, radio resources can be operated more efficiently than in the conventional technology, which requires the same delay increase / decrease to be applied in both directions.

[0025] Other aspects, advantages and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the accompany drawings, disclose various embodiments of the present disclosure. [Brief description of the drawings]

[0026] [Figure 1] 1 is a diagram showing the network structure of Global System for Mobile Communications (GSM), a digital mobile communications network. [Diagram 2] 1 is a diagram showing a structure in which a voice codec and the time (delay) consumed by each transmission section are divided in a GSM uplink (MS → BTS direction). [Diagram 3] 1 is a diagram showing a voice compressor (encoder) and typical delay values ​​consumed in each section. [Figure 4]1 is a diagram showing an RTP / UDP / IP header structure for a compressed media frame in a packet-switched network. [Diagram 5] This is a diagram showing the structure of a 5G New Radio (NR) network consisting of a terminal (User Equipment, UE), a base station (gNB), a User Plane Function (UPF), and a Data Network (DN). [Figure 6] A diagram showing the User Plane (UP) protocol structure used for transmitting voice and video frames in an NR UE (a) and a gNB (b) and the Control Plane (CP) protocol structure used for transmitting control signals. [Figure 7] 1 is a diagram showing an example of an operation of a Delay Budget Information (DBI) Signaling function. [Figure 8] 13 is a diagram showing Delay in a DelayBudgetReport message format. [Figure 9] 13 is a diagram showing another example of the operation of DBI Signaling. [Figure 10] 13 is a diagram showing a Delay field consisting of 16 bits. [Figure 11] 13 is a diagram showing another example of the operation of the DBI signaling function. [Figure 12] 1 is a diagram showing Timestamp information in an RTP protocol header. [Figure 13] 1 is a diagram showing a Delay RTCP message proposed in the present invention. [Figure 14] 13 is a diagram showing the operation of a UE that configures and transmits a Delay RTCP message. [Figure 15] 13 is a diagram showing the operation of a UE that processes and returns a Delay RTCP message received via a network node in a transmission path. [Figure 16]1 is a diagram showing a procedure for a network node located on a transmission path between two UEs to process a Delay RTCP message. [Figure 17] This is a diagram showing an example of a procedure in which UE-1, UE-2, and intermediate network nodes request and allocate delay based on this procedure. [Figure 18] This is a diagram showing another example of a procedure in which UE-1, UE-2, and intermediate network nodes request and allocate delay based on the above procedure. [Figure 19] This is a diagram showing another example of a procedure in which UE-1, UE-2, and intermediate network nodes request and allocate delay based on this procedure. [Figure 20] 1 is a diagram showing an embodiment of the present invention; [Figure 21] 11 is a diagram showing another embodiment of the present invention. [Figure 22] 1 is a diagram showing still another embodiment of the present invention; [Diagram 23] 1 is a diagram showing still another embodiment of the present invention; [Figure 24] 2 is a diagram showing the structure of a terminal according to an embodiment of the present invention. [Diagram 25] 1 is a diagram showing the structure of a network node according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] The following description with reference to the accompanying drawings is provided to aid in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. Various specific details are included herein to aid in the understanding, but are considered to be merely exemplary. Thus, those skilled in the art will recognize that various changes and modifications of the various embodiments described in the present disclosure may be made without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of known functions and configurations may be omitted for clarity and conciseness.

[0028] The terms and words used in the following description and claims are not limited to their literary meanings, but are merely terms used to allow a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and is not intended to limit the present disclosure as defined by the appended claims and their equivalents.

[0029] The singular forms "a," "an," and "the" may be understood to include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to a "component surface" includes reference to one or more of such surfaces.

[0030] In describing the embodiments, technical content that is well known in the technical field to which the present disclosure pertains and is not directly related to the present disclosure will be omitted in order to clarify and more clearly convey the gist of the present disclosure by omitting unnecessary explanations.

[0031] For the same reason, in the accompanying drawings, some components are exaggerated, omitted or illustrated in a schematic manner, and the size of each component does not entirely reflect the actual size. The same reference numerals are used in each drawing to refer to the same or corresponding components.

[0032] The advantages and features of the present disclosure, and methods for achieving the same, will become clear with reference to the following detailed description of the embodiments together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be embodied in various different forms, and the embodiments are provided to complete the disclosure and fully inform those skilled in the art to which the disclosure pertains, and the disclosure is defined only by the scope of the claims. The same reference numerals refer to the same elements throughout the specification.

[0033] It will be understood that the combination of each block of the process flow chart and the diagrams of the flow chart can be implemented by computer program instructions. These computer program instructions can be loaded onto a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions executed by the processor of the computer or other programmable data processing equipment generate means for performing the functions described in the flow chart blocks. These computer program instructions can also be stored in a computer usable or computer readable memory that can direct the computer or other programmable data processing equipment to implement the functions in a particular manner, such that the instructions stored in the computer usable or computer readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flow chart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to generate a computer-implemented process, such that the instructions for the computer or other programmable data processing equipment provide steps for performing the functions described in the flow chart blocks.

[0034] Also, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of order. For example, two blocks shown adjacent to each other may in fact be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order depending on the corresponding functions.

[0035] In this embodiment, the term 'module' refers to software or hardware components such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the 'module' performs any function. However, the 'module' is not limited to software or hardware. The 'module' may be configured to reside in an addressable storage medium, and may be configured to implement one or more processors. Thus, as an example, the 'module' includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The components and functions provided in the 'module' may be combined into a smaller number of components and 'modules' or may be further separated into additional components and 'modules'. In addition, the components and 'modules' may be embodied to implement one or more CPUs in a device or a secure multimedia card.

[0036] Figure 1 shows the network structure of Global System for Mobile Communications (GSM), which is a digital mobile communication network. Conventionally, as shown in Figure 1, a Base Transceiver Station (BTS, 110), which is a base station that directly communicates with a terminal (Mobile Station, MS, 100), and a Base Station Controller (BSC, 120) that controls a number of BTSs, have bit rates, power, frequency, etc., and when the bit rate is adjusted, parameters such as a channel coding rate and a modulation method are adjusted, and when it is necessary to connect the MS100 to another BTS, the BSC120 can perform a handover of the MS100. The BSC120 can be connected to other mobile communication networks and a wired telephone network (Public Switched Telephone Network, PSTN, 140) through a Mobile Switching Center (MSC, 130).

[0037] In 2G and 3G circuit-switched networks such as GSM and Wideband Code Division Multiple Access (W-CDMA), once the transmission path for media such as voice and video is established before a call, it is not changed during the call unless a handover occurs, all media data is transmitted on the same path, and media compression and the time required for each transmission section are also kept similar. This is because the end-to-end transmission path assigned by the network must be maintained as it is, since the transmission path and location information of the sending and receiving terminals are not attached to the compressed media frame.

[0038] FIG. 2 shows a structure in which a voice codec and a time (delay) consumed by each transmission section are divided in the GSM uplink.

[0039] FIG. 3 shows a typical delay value consumed by each section of an audio compressor.

[0040] As shown in Figures 2 and 3, Figure 2 shows the delay consumed by the voice codec and each transmission section in the GSM uplink (MS → BTS direction), and Figure 3 shows the voice compressor (encoder) and typical delay values ​​consumed by each section (3GPP (registered trademark, same below) TR 26.975, Figure 14.1, Table 14.3). In a circuit network, this value does not change significantly depending on various conditions during a call, and the MS, BTS, BSC, and MSC shown in Figure 1 do not have the ability to change such delay values.

[0041] FIG. 4 shows the RTP / UDP / IP header structure for a compressed media frame in a packet-switched network.

[0042] As shown in Figure 4, in packet-switched networks introduced after 4G, RTP / UDP / IP headers are attached to compressed media frames, but since the IP header contains both the IP addresses (source and destination addresses) of the sending and receiving terminals, there is no need for the transmission section of each media packet to be the same.

[0043] In particular, the base station adjusts the delay of the wireless section, which has a wider range of rapid changes in network load, weather, terminal movement, etc., compared to the wired section, where the transmission conditions change less, through scheduling, to maximize the quality and capacity of the media. For example, the network can be operated in such a way that a large delay is assigned to a terminal located in the boundary area between cells with poor transmission and reception conditions so that multiple retransmissions can be made, and a small delay is assigned to a terminal with a smooth connection state near the base station. This delay adjustment must be performed while maintaining it below the maximum delay required for the service, and for example, in the case of voice calls, the radio wave time of the voice signal from the speaker's mouth to the other person's ear must be maintained within 280 ms.

[0044] FIG. 5 illustrates a network structure of a 5G New Radio (NR) network according to one embodiment of the present disclosure.

[0045] Referring to FIG. 5, the 5G New Radio (NR) network is composed of a terminal (User Equipment, UE, 500), a base station (gNB, 510, 520, 550), a User Plane Function (UPF, 540), and a Data Network (DN, 560). The gNB (510, 520) is composed of a Remote Radio Head (RRH, 510) including RF equipment such as an antenna and a Digital Unit (DU, 520) dedicated to digital signal processing, and a Mobile Edge Computing (MEC, 530) is connected to the gNB 520 to assist in additional processing of media, storage of frequently used data, etc. The NR network can be connected to other mobile communication networks and a wired telephone network (Public Switched Telephone Network, PSTN) 140 through a DN node.

[0046] Figure 6 shows the User Pane (UP) protocol structure used for transmitting voice and video frames from an NR UE (a) and a gNB (b) and the Control Plane (CP) protocol structure used for transmitting control signals.

[0047] Referring to Figure 6, the UP protocol structure consists of Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC) and Physical Layer (PHY), while the CP protocol structure consists of Radio Resource Control (RRC) and Non-Access Stratum (NAS). 4G LTE networks also have a similar protocol structure, except for SDAP, which was first introduced in NR. The gNB's MAC is responsible for adjusting the transmission delay in the wireless section between the UE and the gNB, and determines the uplink and downlink transmission opportunities of each terminal and notifies each terminal of the transmission time and method through Scheduling Grant. The MAC specifies the start point and width of the frequency band that the UE will use for the next transmission and reception, the transmission and reception time, and the modulation and channel coding method, and adjusts the delay in the wireless section through the maximum number of retransmissions (Hybrid Adaptive Repeat and Request) used for transmission and reception.

[0048] However, the end-to-end transmission path of compressed media packets generally includes two air interfaces, and when the MAC of a gNB is exclusively responsible for delay adjustment, there is a limitation that the uplink and downlink air interface delays of a partner UE connected to another gNB cannot be adjusted. To solve this problem, the Delay Budget Information (DBI) signaling function was introduced to LTE and NR networks, but it was not possible to adjust the overall delay of the end-to-end transmission section to support the adjustment of the utilization delay of each node such as MEC located in the middle of the transmission path, or to adjust the delay in the transmission and reception directions independently to efficiently manage radio resources.

[0049] FIG. 7 shows an example of the operation of a Delay Budget Information (DBI) Signaling function (3GPP TS 26.114, Annex V).

[0050] Referring to FIG. 7, the terminal UE-1 (710) can transmit compressed media at R0 kbps to the counterpart terminal UE-2 (770) (operation 701). RTP / UDP / IP headers are sequentially attached to the compressed frame by the media encoder of UE-1 (710) and transmitted to the modem, and the compressed frame can be restored by the media decoder of UE-2 through the wired / wireless section. UE-1 (710) and UE-2 (770) are connected to radio access networks ((Radio) Access Networks, AN-1 (720), AN-2 (760)) such as LTE and NR, and AN-1 (720) and AN-2 (760) are connected to packet core networks. The packet core network of NR is 5GC (730, 750), and the packet core network of LTE may be Enhanced Packet Core (EPC). In the network structure of Figure 5, AN-1 (720) corresponds to gNB, and 5GC (730) can include UPF and DN. The IP Multimedia Subsystem (IMS, 740) can connect two NR networks and ensure the Quality of Service (QoS) of the end-to-end transmission path.

[0051] When the channel condition of the wireless section between UE-1 (710) and AN-1 (720) deteriorates and the proportion of packets that AN-1 (720) cannot successfully receive increases even if they are transmitted up to the maximum number of retransmissions allowed by the gNB, mUE-1 (710) can request an increase in the transmission delay used by AN-1 (720) via an RRC message (operation 702). Here, AN-1 (720) can notify UE-1 (710) of the amount of delay that can be increased from the current level via an RRC message (operation 703). Compressed media can be transmitted from the terminal UE-1 (710) to the counterpart terminal UE-2 (770) at the maintained R0 kbps (operation 704).

[0052] FIG. 8 shows the Delay in the DelayBudgetReport message format.

[0053] Referring to FIG. 8, in the DelayBudgetReport message format shown in FIG. 8, the delay can be adjusted in units of -1280, -640, -320, -160, -80, -60, -40, -20, 0, 20, 40, 60, 80, 160, 320, 640, and 1280 ms (3GPP 36.331 (LTE), 38.331 (NR)). UE-1 can maintain a transmission speed of R0 kbps by increasing the number of retransmissions using the delay increased by AN-1. In this way, DBI is a technology that responds to deterioration of transmission conditions by adjusting the transmission delay rather than adjusting the bit rate, which is the traditional method.

[0054] FIG. 9 shows another example of the operation of DBI Signaling.

[0055] Referring to FIG. 9, in DBI signaling, compressed media can be transmitted from UE-1 (910) to UE-2 (970) at R0 kbps (operation 901). The channel condition of the wireless section between UE-2 (970) and AN-2 (960) becomes smooth, and the condition for reducing the delay required for transmission is achieved. AN-2 (960) can transmit the amount of spare delay to UE-2 (970) using the RRC message of FIG. 8, and UE-2 (970) can transmit the amount of additional delay that UE-1 (910) can use to UE-1 (910) using a 4 byte Delay message (operation 902). The Delay message may be a Delay RTCP message. The message can be transmitted by being included in a Real-Time Control Packet (RTCP) packet that is periodically transmitted between UEs to exchange packet transmission and reception information.

[0056] When the channel condition of the wireless section between UE-1 (910) and AN-1 (920) deteriorates and the ratio of packets that AN-1 (920) cannot successfully receive increases even if they are transmitted up to the maximum number of retransmissions allowed by the gNB, UE-1 (910) can request an increase in the transmission delay used by AN-1 (920) via an RRC message (operation 903). Here, AN-1 (920) can notify UE-1 (910) of the amount of delay that can be increased from the current level via an RRC message (operation 904). Compressed media can be transmitted from the terminal UE-1 (910) to the counterpart terminal UE-2 (970) at the maintained R0 kbps (operation 905).

[0057] FIG. 10 shows a Delay field consisting of 16 bits.

[0058] Referring to Figure 10, the Delay field consisting of 16 bits is -2 15 ~2 15It can indicate (32768) ms, and the Sign (S) bit can indicate +(1) or -(0). The Query (Q) bit is set to 1 when the message queries the current delay status and can be set to 0 when reporting the current status as shown in Figure 9. UE-1, which receives the RTCP message, can query AN-1 if it can use this amount of delay for additional transmission and reception with AN-1, and AN-1 can approve the use.

[0059] FIG. 11 shows another example of the operation of the DBI Signaling function.

[0060] FIG. 12 shows the Timestamp information in the RTP protocol header.

[0061] Referring to FIG. 11, the DBI signaling function can transmit compressed media at R0 kbps from UE-1 (1110) to UE-2 (1170) (operation 1101). When the condition of the wireless section between UE-1 (1110) and AN-1 (1120) deteriorates and the proportion of packets that AN-1 (1120) cannot successfully receive increases even if they are transmitted up to the maximum number of allowed retransmissions, UE-1 (1110) can query the amount of delay that can be used from UE-2 (1170) through an RTCP message (operation 1102). Here, UE-2 (1170), which has a smooth channel condition, can report the level of spare delay estimated using the timestamp information of the RTP protocol header shown in FIG. 12 using an RTCP message (operation 1103). UE-1 (1110) that receives this can negotiate with AN-1 (1120) to use the spare delay.

[0062] When the channel condition of the wireless section between UE-1 (1110) and AN-1 (1120) deteriorates and the ratio of packets that AN-1 (1120) cannot successfully receive increases even if they are transmitted up to the maximum number of retransmissions allowed by the gNB, UE-1 (1110) can request an increase in the transmission delay used by AN-1 (1120) via an RRC message (operation 1104). Here, AN-1 (1120) can notify UE-1 (1110) of the amount of delay that can be increased from the current level via an RRC message (operation 1105). Media compressed at the maintained R0 kbps can be transmitted from the terminal UE-1 (1110) to the counterpart terminal UE-2 (1170) (operation 1106).

[0063] Thus, DBI Signaling technology is a network operation technique that maintains a target bit rate by adjusting the transmission time rather than adjusting the bit rate when a change in the transmission method is required due to changes in channel conditions.

[0064] In a Time Division Duplex (TDD) network operation where the uplink and downlink share the same frequency band, the channel conditions of the uplink and downlink are likely to be similar, but in a Frequency Division Duplex (FDD) network operation where the uplink and downlink use different frequency bands, the channel conditions of the uplink and downlink may be different. The delay signal message formats shown in Figures 8 and 10 cannot indicate the direction of the spare or insufficient delay, so the same delay increase / decrease is applied to both directions, limiting efficient operation of radio resources.

[0065] In addition, the DelayBudgetReport message in Figure 8 is defined only for the section between the UE and gNB, and the query / allocation delay displayed in the message in Figure 10 cannot be confirmed by network nodes located in the middle of the transmission path such as 5GC and IMS, so it cannot be used for overall delay adjustment. In particular, the MEC shown in Figure 5 can perform additional functions such as improving media quality or stitching multiple videos to create a 360 video, but if the MEC can grasp the remaining / shortage information of delay and use part of the delay, efficient network operation and service quality can be achieved. The delay increase / decrease function, which is currently only available in the wireless section, needs to be extended to apply to all end-to-end transmission paths including the wired section.

[0066] FIG. 13 shows the Delay RTCP message proposed in the present invention.

[0067] 13 shows the Delay RTCP message proposed in the present invention. The Delay field, which is composed of 16 bits like the Delay message in FIG. 10, is -2 15 ~2 15 The Q field can indicate (32768) ms and the S bit can indicate +(1) or -(0). The Q field can be set to 1 when this message queries the current delay status. The Direction (D) bit (included in the IP address in Figure 4) can be set to 1 if it means the delay in the destination direction (Uplink Delay, UD) from the source, and can be set to 0 if it means the delay in the source direction (Downlink Delay, DD) from the destination position. The A bit can be set to 1 if the UE receiving the Delay RTCP message reflects the delay allocation request of the UE or node that first sent the Delay RTCP message.

[0068] The 12-bit Node_ID field is used to identify the UE and the network node. This field differs from the Delay RTCP message in Fig. 10 in that the network node in the transmission section can add or remove information including each delay-related request to the RTCP packet created and transmitted by the UE. Therefore, when the UE or the network node adds delay information in both directions, 8 bytes are added, and when the requested delay is allocated, the received Delay RTCP message reflects this and removes its own related information before forwarding it to the next node.

[0069] In the present invention, a UE transmits a Delay RTCP message to request or report a spare delay, to which a network node adds its own current delay status information, and the corresponding UE that receives this aggregates the current delay status of all transmission paths so that the spare delay can be efficiently allocated among all nodes of the transmission path.

[0070] FIG. 14 illustrates the operation of a UE in constructing and sending a Delay RTCP message.

[0071] Referring to FIG. 14, a call can be started (operation 1401). The UE monitoring the transmission and reception status checks the uplink and downlink delay status to determine whether a delay is currently required or there is a spare (whether the transmission time can be reduced), and stores the required or spare delay value in each UD_0 and DD_0 (operation 1402). It is determined that the stored UD_0 and DD_0 values ​​are 0 (operation 1403). If both UD_0 and DD_0 are 0, operation 1402 is performed again. Also, if both UD_0 and DD_0 are not 0, Delay RTCP can be configured and transmitted (operation 1404). At this time, if more delay is required, the S bit can be set to 1, and if there is a spare delay (if the transmission time can be reduced), it can be set to 0.

[0072] The transmitted Delay RTCP message arrives at the counterpart UE via the network nodes of the transmission path. The counterpart UE returns a Delay RTCP message with the delay-related request items added to the message (operation 1405). The UE that receives the returned Delay RTCP message can check whether there is a message corresponding to its Node_ID (operation 1406). The counterpart UE may prioritize other nodes according to the spare delay situation and may not be able to allocate the delay requested by this UE. In this case, the counterpart UE reserves the 4-byte reply associated with this UE's Node_ID until the requested delay is secured, or returns with the spare delay value set to 0. If a Delay RTCP message including its Node_ID is attached, the UE can apply the assigned UD_0 and DD_0 values ​​(operation 1407). Specifically, the UE can apply the assigned UD_0 and DD_0 values ​​to the transmission / reception stage through the procedures of operations 702 and 703 of FIG. 7 and operations 903 and 904 of FIG. 9. It can then be determined whether the call should continue (operation 1408). If the call should continue, operation 1402 is performed.

[0073] FIG. 15 shows the operation of a UE that processes and replies to a Delay RTCP message received via a network node in the transmission path.

[0074] Referring to Figure 15, a call can be started (operation 1501). The UE monitoring the transmission and reception status can check the uplink and downlink delay status and store spare delay values ​​in UD_N and DD_N, respectively (operation 1502). In the present invention, it is assumed that N-1 of the network nodes existing between two UEs can adjust delay. The bidirectional delay of the i-th network node is set to UD_i and DD_i, and a Delay RTCP message can be received (operation 1503). In this case, the UE corresponds to the N-th node.

[0075] The UE can distribute the determined spare delay to the UE and each node of the received Delay RTCP message (operation 1504). If the requested delay can be provided, the A bit can be set to 1. If the spare delay is insufficient to accept all requests, the Delay field can be set to 0 and returned, or the 4-byte message corresponding to this Node_ID can be deleted in the RTCP packet (operation 1505). It can then be determined whether to continue the call (operation 1506). If the call is to continue, operation 1502 is performed.

[0076] FIG. 16 illustrates a procedure for processing a Delay RTCP message by a network node located on the transmission path between two UEs.

[0077] Referring to FIG. 16, a call can be started (operation 1601). The i-th node monitoring the transmission and reception status checks the delay level in both directions and stores the necessary or remaining delay value in UD_i and DD_i, respectively (operation 1602). Then, it can be determined whether a Delay RTCP message has been received (operation 1603). If received, it can be determined whether the message is in a state where one UE has sent a Delay request and is being sent to another UE, or in a state where a response is being sent to process the requested Delay request (operation 1604). At this time, it can be determined whether the UE is in a state where it has sent a Delay request and is being sent to another UE, or in a state where a response is being sent to process the requested Delay request, through the Q bit of the Delay information input by the other UE.

[0078] In the case of a request, it can be determined whether UD_i and DD_i are both 0 (operation 1605). At this time, if UD_0 and DD_0 are both 0, operation 1603 is performed again. If UD_i and DD_i are not both 0, the UD_i and DD_i values ​​can be added to the Delay RTCP message (operation 1606). After that, the Delay RTCP message including the added UD_i and DD_i can be forwarded to the next node (operation 1607). Then, operation 1603 is performed.

[0079] In the case of a report, since the receiving UE returns the message to allocate a delay through the procedure shown in FIG. 15, it can check whether its own Node_ID (i-th node) is present (operation 1608). If its own Node_ID is not present, operation 1603 is performed again. On the other hand, if the Node_ID is present, the UD_i and DD_i included in the message can be applied to the corresponding section (operation 1609). Then, 4 or 8 bytes including its own delay information such as Node_ID, UD_i, and DD_i can be deleted from the Delay RTCP message (operation 1610). The Delay RTCP message including the deleted information can be forwarded to the next node (operation 1611). Then, it can be determined whether to continue the call (operation 1506). If the call is to be continued, operation 1602 is performed.

[0080] FIG. 17 shows an example of a procedure in which UE-1 (1700), UE-2 (1770), and intermediate network nodes request and allocate delay based on this procedure.

[0081] Referring to FIG. 17, DBI signaling allows UE-1 (1700) to transmit compressed media at R0 kbps in the direction of UE-2 (1770) (operation 1701). UE-1 (1700) can transmit a Delay RTCP message to AN-1 (1720) requesting a one-way spare Delay D0 (operation 1702). Then, AN-1 (1720) can transmit a Delay RTCP message to 5GC (1730) requesting a one-way spare Delay D0 (operation 1703). Then, 5GC (1730) can transmit a Delay RTCP message to IMS (1740) requesting a one-way spare Delay D0 (operation 1704). The Delay RTCP message requesting the spare Delay D0 travels toward UE-2 (1770), and the network node 1740 can add information related to Delay D1 used in its own transmission section to the RTCP message (operation 1705). Thereafter, the network node 1740 can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to the 5GC (1750) (operation 1706). Thereafter, the 5GC (1750) can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to the AN-2 (1760) (operation 1707). Thereafter, the AN-2 (1760) can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to the UE-2 (1770) (operation 1708). D1 may be in the same direction as D0 or in a different direction. This message can reach UE-2 (1770) via the core and access networks to which the remote UE 1700 is connected.

[0082] UE-2 (1770) can transmit a Delay RTCP message allocating one-way spare Delay D0 and Delay D1 to AN-2 (1760) (operation 1709). Then, AN-2 (1760) can transmit a Delay RTCP message allocating one-way spare Delay D0 and Delay D1 to 5GC (1750) (operation 1710). Then, 5GC (1750) can transmit a Delay RTCP message allocating one-way spare Delay D0 and Delay D1 to IMS 1740 (operation 1711). The Delay RTCP message allocating spare Delay D0 and Delay D1 travels toward UE-1 (1700), and network node 1740 can apply Delay D1 to its own transmission section (operation 1712). Thereafter, the network node 1740 can transmit a Delay RTCP message allocating a one-way spare Delay D0 to the 5GC (1730) (operation 1713). Thereafter, the 5GC (1730) can transmit a Delay RTCP message allocating a one-way Delay D0 to the AN-2 (1720) (operation 1714). Thereafter, the AN-2 (1760) can transmit a Delay RTCP message allocating a one-way spare Delay D0 to the UE-2 (1700) (operation 1715). Also, the UE-1 (1700) can request the use of the transmission Delay D0 to the AN-1 (1720) via an RRC message (operation 1716). Here, the AN-1 (1720) can approve the use of the Delay D0 (operation 1717). Compressed media can be transmitted at the maintained R0 kbps from the terminal UE-1 (1700) to the remote terminal UE-2 (1770) (operation 1718).

[0083] FIG. 18 shows an example of a procedure in which UE-1, UE-2, and intermediate network nodes request and allocate delay based on this procedure.

[0084] Referring to FIG. 18, DBI signaling allows media compressed at R0 kbps to be transmitted from UE-1 (1800) to UE-2 (1870) (operation 1801). UE-1 (1800) can transmit a Delay RTCP message requesting one-way spare Delay D0 to AN-1 (1820) (operation 1802). Then, AN-1 (1820) can transmit a Delay RTCP message requesting one-way spare Delay D0 to 5GC (1830) (operation 1803). Then, 5GC (1830) can transmit a Delay RTCP message requesting one-way spare Delay D0 to IMS 1840 (operation 1804). The Delay RTCP message requesting the spare Delay D0 travels toward UE-2 (1870), and the network node 1840 can add information related to Delay D1 used in its own transmission section to the RTCP message (operation 1805). Thereafter, the network node 1840 can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to 5GC (1850) (operation 1806). Thereafter, 5GC (1850) can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to AN-2 (1860) (operation 1807). Thereafter, AN-2 (1860) can transmit a Delay RTCP message requesting the one-way spare Delay D0 and the added Delay D1 to UE-2 (1870) (operation 1808). D1 may be in the same direction as D0 or in a different direction. This message can reach UE-2 (1870) via the core and access networks to which the remote UE (1800) is connected.

[0085] On the other hand, depending on the network situation, it may not be possible to accommodate all the delay allocation requests made by the UE or the network node. Figure 18 shows a case where UE-1 (1800) and one network node each request a delay as shown in Figure 17, but UE-2 (1870) only allocates D0 requested by UE-1 (1800) and rejects the allocation of D1 requested by the network node 1840. UE-2 (1870) can determine the priority of delay allocation according to the Node_ID information related to each request. The returned message can reach the network IMS node 1840 that requested D1 via AN-2 (1860) and 5GC (1850). At this time, the network node can confirm that its request has been rejected and forward the RTCP message after deleting 4 bytes related to D1. This message passes through 5GC (1830) and AN-1 (1820) and finally reaches UE-1 (1800), and UE-1 (1800) can request AN-1 (1820) to apply D0 assigned by UE-2 (1870), and after receiving approval, it can apply it to the corresponding radio section.

[0086] UE-2 (1870) can transmit a Delay RTCP message to AN-2 (1860) allocating a one-way spare Delay D0 and rejecting Delay D1 (operation 1809). AN-2 (1860) can then transmit a Delay RTCP message to 5GC (1850) allocating a one-way spare Delay D0 and rejecting Delay D1 (operation 1810). 5GC (1850) can then transmit a Delay RTCP message to IMS 1840 allocating a one-way spare Delay D0 and rejecting Delay D1 (operation 1811). The Delay RTCP message allocating the spare Delay D0 and rejecting Delay D1 travels toward UE-1 (1800), and network node 1840 can cancel the request for Delay D1 to be used in its own transmission section (operation 1812). Thereafter, the network node 1840 can transmit a Delay RTCP message allocating a one-way spare Delay D0 to the 5GC (1830) (operation 1813). Thereafter, the 5GC (1830) can transmit a Delay RTCP message allocating a one-way Delay D0 to the AN-2 (1820) (operation 1814). Thereafter, the AN-2 (1860) can transmit a Delay RTCP message allocating a one-way spare Delay D0 to the UE-2 (1800) (operation 1815). Also, the UE-1 (1800) can request the use of the transmission Delay D0 to the AN-1 (1820) via an RRC message (operation 1816). Here, the AN-1 (1820) can approve the use of the Delay D0 (operation 1817). Compressed media can be transmitted at the maintained R0 kbps from the terminal UE-1 (1800) to the remote terminal UE-2 (1870) (operation 1818).

[0087] FIG. 19 shows another example of a procedure in which UE-1, UE-2, and intermediate network nodes request and allocate delay based on this procedure.

[0088] In Figure 17, an IP Multimedia Subsystem (IMS) that manages each network is located between two core networks (5GC) to which UE-1 and UE-2 are respectively connected, but the IMS can only be used to negotiate or update call conditions as shown in Figure 19. Therefore, media packets and RTCP packets sent by UE-1 can be sent to UE-2's 5GC via an IP backbone network that connects networks at some DN nodes of UE-1's 5GC as shown in Figure 5.

[0089] With sufficient spare delay, UE-2 can accept and return the D0 and D1 requests requested by UE-1 and the network node. At this time, the A bit of the message corresponding to UE-1 and the network node can be set to 1, respectively. The returned message reaches the network node that requested D1 via AN-2 and 5GC, and this node can check the presence of a message containing its Node_ID, apply the assigned D1, delete the 4 bytes related to D1, and then forward the RTCP message. This message can finally reach UE-1 via 5GC and AN-1, and UE-1 can request AN-1 to apply the assigned D0 from UE-2, and apply it after it is approved.

[0090] FIG. 20 is a method according to one embodiment of the present invention.

[0091] Referring to FIG. 20, the first terminal may determine whether a first delay for the first terminal is necessary (operation 2001). If the first delay is necessary, the first terminal may transmit a delay message including the first delay information to the second terminal (operation 2002). In response to the delay message, the second terminal may receive an assignment message including one or more node information from the second terminal (operation 2003). The delay message and the assignment message may be a Real-time Transport Protocol Control Protocol (RTCP) message. The RTCP message may include at least one of direction information, assignment information, and one or more node information to be assigned, and the delay message and the assignment message may be determined by at least one of the direction information, assignment information, and one or more node information to be assigned. The first terminal may be included in the one or more node information included in the assignment message (operation 2004). If the first terminal information is included, the first delay may be assigned (operation 2005).

[0092] FIG. 21 shows a method according to one embodiment of the present invention.

[0093] Referring to FIG. 21, a network node may receive a delay message requesting a first delay from a first terminal (operation 2101). The delay message may be a Real-time Transport Protocol Control Protocol (RTCP) message, and the RTCP message may include at least one of direction information, allocation information, and information on one or more nodes to be assigned, and the delay message may be determined according to at least one of the direction information, allocation information, and information on one or more nodes to be assigned. It may be determined whether a second delay is required for the network node (operation 2102). If the second delay is required, the second delay information may be added to the delay message (operation 2103). A second terminal may transmit the delay message with the second delay information added thereto (operation 2104).

[0094] FIG. 22 is a method according to one embodiment of the present invention.

[0095] Referring to FIG. 22, a second terminal may receive a delay message including delay information of one or more nodes (operation 2201). It may determine whether the delay of the one or more nodes is allocable (operation 2202). If the delay of the one or more nodes is allocable, the delay may be allocated to the allocable nodes (operation 2203). An allocation message including information on the allocable nodes is sent to the one or more nodes (operation 2204). The delay message and the allocation message may be a Real-time Transport Protocol Control Protocol (RTCP) message. The RTCP message may include at least one of direction information, allocation information, and information on one or more nodes to be assigned, and the delay message and the allocation message may be determined by at least one of the direction information, allocation information, and information on one or more nodes to be assigned.

[0096] FIG. 23 is a method according to one embodiment of the present invention.

[0097] Referring to FIG. 23, a network node may receive an assignment message including one or more pieces of node information from a second terminal (operation 2301). The assignment message is a Real-time Transport Protocol Control Protocol (RTCP) message, and the RTCP message may include at least one of direction information, assignment information, and one or more pieces of node information to be assigned, and the delay message may be determined according to at least one of the direction information, assignment information, and one or more pieces of node information to be assigned. It may be determined whether the network node information is included in the one or more pieces of node information included in the assignment message (operation 2302). If the network node information is included, a second delay related to the network node may be applied (operation 2303). After applying the second delay in the removal period, the second delay information may be deleted from the assignment message (operation 2304). A delay message with the second delay information deleted may be transmitted (operation 2305).

[0098] FIG. 24 is a diagram showing the structure of a terminal according to an embodiment of the present invention.

[0099] 24, the terminal may include a transceiver 2410, a controller 2420, and a memory 2430. In the present invention, the controller may be defined as a circuit or an application specific integrated circuit, or at least one processor.

[0100] The transceiver 2410 may transmit and receive signals to and from other network entities, for example, the transceiver 2410 may receive system information from a network node, and may receive synchronization or reference signals.

[0101] The controller 2420 may control the overall operation of the terminal according to the embodiment of the present invention. For example, the controller 2420 may control the signal flow between each block to perform the operation according to the flowchart described above. Specifically, the controller 2420 may control the operation proposed in the present invention to receive residual system information (RMSI) in the multi-beam based system according to the embodiment of the present invention.

[0102] The memory unit 2430 may store at least one of information transmitted and received via the transceiver unit 2410 and information generated via the controller 2420. For example, the memory unit 2430 may store scheduling information related to RMSI transmission, RMSI-related PDCCH time axis position and periodicity information, and the like.

[0103] FIG. 25 is a diagram showing the structure of a network node according to one embodiment of the present invention.

[0104] 25, the network node may include a transceiver 2510, a controller 2520, and a memory 2530. In the present invention, the controller may be defined as a circuit or an application specific integrated circuit, or at least one processor.

[0105] The transceiver 2510 may transmit and receive signals to and from other network nodes. The transceiver B 2510 may, for example, transmit system information to the terminal, and may transmit a synchronization signal or a reference signal.

[0106] The controller 2520 may control the overall operation of the network node according to the embodiment of the present invention. For example, the controller 2520 may control the signal flow between each block to perform the operation according to the above-mentioned flowchart. Specifically, the controller 2520 may control the operation proposed in the present invention to transmit residual system information (RMSI) in the multi-beam based system according to the embodiment of the present invention.

[0107] The memory unit 2530 may store at least one of information transmitted and received via the transceiver unit 2510 and information generated via the controller 2520. For example, the memory unit 2530 may store scheduling information related to RMSI transmission, RMSI-related PDCCH time axis position and periodicity information, and the like.

[0108] The embodiments disclosed in the present specification and drawings are merely specific examples presented to facilitate the explanation and understanding of the present invention, and are not intended to limit the scope of the present invention. Therefore, the scope of the present invention should be interpreted as including all modifications and variations derived based on the technical characteristics of the present invention in addition to the embodiments disclosed herein. [Explanation of symbols]

[0109] 2410 Transmitter / Receiver 2420 Control Unit 2430 Storage section 2510 Transmitter / Receiver 2520 Control Unit 2530 Storage section

Claims

1. A method of operating a first terminal, comprising: determining whether a first delay associated with the first terminal is necessary; if the first delay is required, sending a delay message including first delay information to a second terminal; receiving an assignment message including one or more pieces of node information from the second terminal in response to the delay message; determining whether the one or more node information included in the assignment message includes information of the first terminal; and and assigning the first delay if the one or more node information includes information of the first terminal.

2. The delay message and the allocation message are Real-time Transport Protocol Control Protocol (RTCP) messages, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The method of claim 1 , wherein the delay message and the assignment message are determined by at least one of the direction information, assignment information, and information of one or more nodes to be assigned.

3. 1. A method for requesting a delay in a network node, comprising: receiving a delay message from a first terminal requesting a first delay; determining whether a second delay associated with the network node is necessary; if the second delay is required, adding second delay information to the delay message; and and transmitting to a second terminal a delay message to which the second delay information is added.

4. the delay message is a Real-time Transport Protocol Control Protocol (RTCP) message, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The method of claim 3, wherein the delay message is determined by at least one of the direction information, the assignment information, and information of one or more assigned nodes.

5. A method of operating a second terminal, comprising: receiving a delay message from the first terminal, the delay message including delay information of one or more nodes; determining whether the delay of the one or more nodes is assignable; if the delay of one or more of the nodes is assignable, assigning the delay to the assignable nodes; and and transmitting an assignment message to the one or more nodes including information regarding the available nodes.

6. The delay message and the allocation message are Real-time Transport Protocol Control Protocol (RTCP) messages, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The method of claim 5, wherein the delay message and the assignment message are determined by at least one of the direction information, assignment information, and information of one or more nodes to be assigned.

7. 1. A method for assigning delay to a network node, comprising the steps of: receiving an assignment message including one or more pieces of node information from a second terminal; The assignment message further includes first delay information and second delay information assigned to the one or more node information, determining whether the one or more node information included in the assignment message includes information of the network node; applying a delay according to second delay information assigned to the network node when the one or more node information includes information of the network node; After applying the delay, deleting second delay information assigned to the one or more node information included in the assignment message; and sending a delay message with the second delay information deleted to the first terminal.

8. The allocation message is a Real-time Transport Protocol Control Protocol (RTCP) message, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The method of claim 7, wherein the assignment message is determined by at least one of the direction information, assignment information, and information of one or more nodes to be assigned.

9. A first terminal, A transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver unit, The control unit is determining whether a first delay associated with the first terminal is necessary; If the first delay is required, sending a delay message including the first delay information to a second terminal; receiving an assignment message including one or more pieces of node information from the second terminal in response to the delay message; determining whether the one or more node information included in the assignment message includes information of the first terminal; and A first terminal configured to assign the first delay when the one or more node information includes information of the first terminal.

10. The delay message and the allocation message are Real-time Transport Protocol Control Protocol (RTCP) messages, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The first terminal of claim 9, wherein the delay message and the assignment message are determined according to at least one of the direction information, assignment information, and information on one or more nodes to be assigned.

11. A network node requesting a delay, comprising: A transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver unit, The control unit is receiving a delay message from a first terminal requesting a first delay; determining whether a second delay associated with the network node is necessary; If the second delay is required, adding second delay information to the delay message; and A network node, characterized in that it is configured to transmit to a second terminal a delay message to which said second delay information has been added.

12. the delay message is a Real-time Transport Protocol Control Protocol (RTCP) message, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The network node of claim 11, wherein the delay message is determined according to at least one of the direction information, the allocation information, and information of one or more assigned nodes.

13. A second terminal, A transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver unit, The control unit is receiving a delay message from the first terminal, the delay message including delay information of one or more nodes; determining whether the delay of the one or more nodes is assignable; if the delay of one or more of the nodes is assignable, assigning the delay to the assignable nodes; and A second terminal configured to transmit an assignment message to the one or more nodes comprising information on the assignable nodes.

14. The delay message and the allocation message are Real-time Transport Protocol Control Protocol (RTCP) messages, The RTCP message includes at least one of direction information, assignment information, and information on one or more assigned nodes, The second terminal of claim 13, wherein the delay message and the assignment message are determined according to at least one of the direction information, the assignment information, and information on one or more nodes to be assigned.

15. A network node, A transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver unit, The control unit is Receive an assignment message including one or more pieces of node information from a second terminal; The assignment message further includes first delay information and second delay information assigned to the one or more node information, determining whether the one or more node information included in the allocation message includes information of the network node; If the one or more node information includes information of the network node, applying a delay according to second delay information assigned to the network node; After applying the delay, delete second delay information assigned to the one or more node information included in the assignment message; and A network node configured to transmit a delay message from which the second delay information has been deleted to a first terminal.

Images