Communication with regenerative silence frames
By determining and signaling silence periods for media services, the method reduces unnecessary silence frame transmissions, improving efficiency and flexibility in satellite communication systems.
Patent Information
- Application Number
- PCT/CN2025/094019
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication systems face inefficiencies and overheads due to the transmission of silence frames during media services, particularly in satellite-based networks, leading to increased latency and power consumption.
An apparatus determines a silence period for a media service based on received data, transmitting a message indicating the silence period or a description of silence frames, allowing devices to generate these frames without actual transmission, thus reducing overhead and improving communication efficiency.
This approach reduces communication overhead and enhances flexibility by minimizing unnecessary silence frame transmissions, addressing latency and power consumption issues in satellite networks.
Smart Images

Figure CN2025094019_12112026_PF_FP_ABST
Abstract
Description
COMMUNICATION WITH REGENERATIVE SILENCE FRAMESFIELD
[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for communication with regenerative silence frames.BACKGROUND
[0002] A communication network may serve as a facility that enables communications between two or more communication devices or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.
[0003] The communication network may operate in accordance with standards such as those provided by Third Generation Partnership Project (3GPP) or European Telecommunications Standards Institute (ETSI) . Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular technology generations, such as 3GPP standards for 4G technology, 5G technology, 6G technology, and so on.SUMMARY
[0004] In a first aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and transmit, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.
[0005] In a second aspect of the present disclosure, there is provided a device. The device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the device at least to: receive, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and determine that no user data is to be transmitted during the silence period based on the message.
[0006] In a third aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and generate the at least one silence frame based on the message.
[0007] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: determining a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and transmitting, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.
[0008] In a fifth aspect of the present disclosure, there is provided a method. The method comprises: receiving, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and determining that no user data is to be transmitted during the silence period based on the message.
[0009] In a sixth aspect of the present disclosure, there is provided a method. The method comprises: receiving, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and generating the at least one silence frame based on the message.
[0010] In a seventh aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for determining a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and means for transmitting, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.
[0011] In an eighth aspect of the present disclosure, there is provided a device. The device comprises means for receiving, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and means for determining that no user data is to be transmitted during the silence period based on the message.
[0012] In a ninth aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for receiving, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; and means for generating the at least one silence frame based on the message.
[0013] In a tenth aspect of the present disclosure, there is provided a non-transitory computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
[0014] In an eleventh aspect of the present disclosure, there is provided a non-transitory computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifth aspect.
[0015] In a twelfth aspect of the present disclosure, there is provided a non-transitory computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixth aspect.
[0016] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0018] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0019] FIG. 2A illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0020] FIG. 2B illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0021] FIG. 2C illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0022] FIG. 3 illustrates a schematic diagram of communication with silence frames;
[0023] FIG. 4 illustrates a signaling flow of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0024] FIG. 5 illustrates a schematic diagram of an example process of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0025] FIG. 6 illustrates a schematic diagram of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0026] FIG. 7 illustrates a schematic diagram of an example process of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0027] FIG. 8 illustrates a schematic diagram of an example process of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0028] FIG. 9 illustrates a schematic diagram of an example process of communication with regenerative silence frames in accordance with some embodiments of the present disclosure;
[0029] FIG. 10 illustrates a schematic diagram of an example process of communication regenerative with silence frames in accordance with some embodiments of the present disclosure;
[0030] FIG. 11 illustrates a flowchart of a method implemented at an apparatus in accordance with some example embodiments of the present disclosure;
[0031] FIG. 12 illustrates a flowchart of a method implemented at a device in accordance with some example embodiments of the present disclosure;
[0032] FIG. 13 illustrates a flowchart of a method implemented at an apparatus in accordance with some example embodiments of the present disclosure;
[0033] FIG. 14 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0034] FIG. 15 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0035] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0036] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0037] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0038] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0039] It shall be understood that although the terms “first, ” “second, ” …, etc. in front of noun (s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun (s) . For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0040] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0041] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0042] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0043] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in analog, digital circuitry and / or quantum circuitry) and (b) combinations of hardware circuit (s) and software, such as (as applicable) : (i) a combination of analog, digital and / or quantum hardware circuit (s) with software / firmware and (ii) any or all portions of hardware processor (s) (including digital and / or quantum processor (s) ) with software, and memory (ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions) and (c) any or all portions of hardware circuit (s) , such as a microprocessor (s) , and / or quantum processor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0044] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0045] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0046] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0047] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0048] As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0049] A core network function as described herein may be implemented as a core network entity that includes a combination of hardware processing circuit and software and / or firmware comprising machine-readable instructions, or software comprising machine-readable instructions that are executable by at least one processor of hardware processing circuit of an apparatus. A hardware processing circuit includes at least one processor and at least one memory storing machine-readable instructions that are executable by the at least one processor of the hardware processing circuit. A processor includes any or some combination of an accelerator, a microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphic processing unit, a tensor processing unit. Memory includes any or some combination of volatile or non-volatile memory (e.g., a flash memory, cache, a random-access memory (RAM) , and / or a read-only memory (ROM) ) . The memory stores the machine-readable instructions of the software and / or firmware for execution by at least one processor of the hardware processing circuit. The machine-readable instructions are executable by at least one processor of the hardware processing circuit cause the hardware processing circuit to perform the actions or operations of the methods described herein. For example, the session management function described herein may be implemented as a session management entity and the session management policy control function described herein may be implemented as a session management policy control entity, respectively.
[0050] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. The communication environment 100 involves an apparatus 110, a device 120, and an apparatus 130. The apparatus 110 may communicate with the device 120 bidirectionally. The apparatus 110 may communicate with the apparatus 130 bidirectionally. The apparatus 130 may communicate with the device 120 bidirectionally.
[0051] Additionally, the communication between the apparatus 110 and the apparatus 130 may be performed via the device 120. In some example embodiments, the apparatus 110 and the apparatus 130 may communicate via the device 120 and a further network entity, e.g., a mobility management entity (MME) , an access and mobility function (AMF) entity (also referred to as “AMF” , for purpose of discussion) .
[0052] In the example of FIG. 1, the apparatus 110 may include a terminal device (e.g., a UE) . The device 120 may include a network device, e.g., a non-terrestrial network (NTN) eNB, a gNB, a base station, and / or the like. The apparatus 130 may include a further terminal device (e.g., a UE) , a network entity, e.g., a serving gateway (SGW) entity (also referred to as “SGW” , for purpose of discussion) , a server (e.g., an application server) , a user plane function (UPF) entity (also referred to as “UPF” , for purpose of discussion) and / or the like.
[0053] For example, in a 4G network, the UE may communicate with the SGW and MME via the NTN eNB . In a 5G network, the UE may communicate with the UPF and AMF via the NTN gNB . Additionally, the communication environment 100 may be applicable for a 6G network or a future communication network.
[0054] It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be deployed in the communication environment 100.
[0055] In the following, for the purpose of illustration, some example embodiments are described with the apparatus 110 operating as a terminal device and the device 120 operating as a network device. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.
[0056] In some example embodiments, a transmission direction from the device 120 to the apparatus 110 is referred to as a downlink (DL) , while a transmission direction from the apparatus 110 to the device 120 is referred to as an uplink (UL) . In DL, the device 120 is a transmitting (TX) device (or a transmitter) and the apparatus 110 is a receiving (RX) device (or a receiver) . In UL, the apparatus 110 is a TX device (or a transmitter) and the device 120 is a RX device (or a receiver) .
[0057] FIG. 2A illustrates an example communication environment 200A in which example embodiments of the present disclosure can be implemented. The example embodiments discussed with respect to FIG. 2A may be implementations of the example embodiments discussed with reference to FIG. 1.
[0058] The communication environment 200A involves a UE 201, an NTN eNB 202, a MME 203, and a SGW 204. The UE 201 may communicate with the NTN eNB 202, the NTN eNB 202 may communicate with the MME 203, and the MME 203 may communicate with the SGW 204. In some example embodiments, the UE 201 may communicate with the SGW 204 via the NTN eNB 202 and the MME 203. In some example embodiments, the NTN eNB 202 may be replaced with a base station, a gNB, and / or the like. The MME 203 may be replaced with an AMF, and the SGW 204 may be replaced with a UPF.
[0059] It is to be understood that the number of the device involved in the communication environment 200A are only for the purpose of illustration without suggesting any limitation. The communication environment 200A may include any suitable number of apparatus and / or devices configured to implement example embodiments of the present disclosure.
[0060] FIG. 2B illustrates an example communication environment 200B in which example embodiments of the present disclosure can be implemented. The example embodiments discussed with respect to FIG. 2B may be implementations of the example embodiments discussed with reference to FIG. 1.
[0061] The communication environment 200B involves a UE 211, an NTN eNB 212, and a server 213. The UE 211 may communicate with the NTN eNB 212. The UE 211 may communicate with the server 213. In some example embodiments, the UE 211 may communicate with the server 213 via the NTN eNB 212. In some example embodiments, the NTN eNB 202 may be replaced with a base station, a gNB, and / or the like.
[0062] It is to be understood that the number of the device involved in the communication environment 200B are only for the purpose of illustration without suggesting any limitation. The communication environment 200B may include any suitable number of apparatus and / or devices configured to implement example embodiments of the present disclosure.
[0063] FIG. 2C illustrates an example communication environment 200C in which example embodiments of the present disclosure can be implemented. The example embodiments discussed with respect to FIG. 2C may be implementations of the example embodiments discussed with reference to FIG. 1.
[0064] The communication environment 200C involves a UE 221, an NTN eNB 222, and a UE 225. The UE 221 may communicate with the NTN eNB 222. The UE 221 may communicate with the UE 225. In some example embodiments, the UE 221 may communicate with the UE 225 via the NTN eNB 222. In some example embodiments, the NTN eNB 202 may be replaced with a base station, a gNB, and / or the like.
[0065] It is to be understood that the number of the device involved in the communication environment 200C are only for the purpose of illustration without suggesting any limitation. The communication environment 200C may include any suitable number of apparatus and / or devices configured to implement example embodiments of the present disclosure.
[0066] Communications in the communication environment 100, the communication environment 200A, the communication environment 200B, or the communication environment 200C may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0067] In communication between a UE and a further UE via an NTN eNB, e.g., an NTN internet protocol (IP) multimedia service (IMS) voice service, discontinuous transmission may be applied for silence or background noise. For example, an adaptive multi-rate (AMR) codec may be used as a speech codec in a mobile communication system. An AMR silence insertion description (SID) frame may be a type of frame used in the AMR codec to efficiently transmit silence or background noise during speech encoding.
[0068] In the AMR codec, when an input signal is silent or contains only background noise, an encoder may generate a SID frame instead of a regular speech frame. The SID frame may be a compact representation of the silence or background noise and used to indicate a start of a period of silence, which allows for efficient transmission and decoding. The SID frame may be generated and sent during a silent period, e.g., every 160ms. The transmission of SID frames during the silent period may help a receiver to reconstruct the silence periods in an original speech signal.
[0069] It is to be understood that the 160ms interval may be a default value for AMR codecs. The 160ms interval may be adjusted or configured differently depending on the implementation and network requirements.
[0070] The AMR SID frame may include a header (e.g., 2 bits) . For example, the value of the 2 bits of the header may be 00, 01, 10, or 11, and one of the values may correspond to silence, background noise with low energy, background noise with high energy, or reserved for the AMR SID frame.
[0071] Additionally, the AMR SID frame may include a payload (e.g., 8 to 16 bits) . The payload may include a description of the background noise, including an energy of the background noise (e.g., 4 to 6 bits) , spectral characteristics of the background noise (4 to 10 bits) , and / or the like.
[0072] An enhanced voice services (EVS) codec or an adaptive multi-rate wideband (AMR-WB) codec may be a wideband audio codec developed by 3GPP for high-quality voice and audio transmission over IP-based networks. The silence frames (e.g., type 1 in the EVS codec and type 2 in the AMR-WB) containing encoded silence or comfort noise may be supported.
[0073] During an IMS voice call establishment procedure, how a UE selects audio codecs may be based on a priority of a payload format and session description protocol (SDP) protocols. The selection of the codec may depend on a UE device support and negotiation results.
[0074] In the communication with silence frames, semi-persistent scheduling (SPS) may be a feature that significantly reduces control channel overhead for data transmissions (e.g., voice over internet protocol (VoIP) applications) that require persistent radio resource allocations. In the LTE or the NR, both the DL and UL transmissions may be scheduled by a serving eNB since the DL and UL traffic channels are dynamically shared channels. A physical DL control channel (PDCCH) may provide access grant information to indicate which users may decode a physical DL shared channel (PDSCH) in each subframe and which users may be allowed to transmit on a physical UL shared channel (PUSCH) in each subframe.
[0075] Without the SPS, every DL or UL PRB allocation for the scheduled DL or UL transmission may be granted using DL control information (DCI) on the PDCCH, which may be affordable for most bursty best effort types of applications which may have large packet sizes and thus, a few users may be scheduled for each subframe. For applications (e.g., the VoIP applications) that require persistent allocations of small packets, DCI signaling overhead over the PDCCH may be reduced with the SPS. The SPS may introduce a persistent PRB allocation within a network / eNB / gNB configured SPS periodicity that a user may expect on the DL or may transmit on the UL. It is to be studied to develop an ultra-low bit rate codec for voice over the geostationary orbit (GEO) .
[0076] For an IMS voice data transmission (e.g., a voice call) via the GEO, the overheads of the SID and silence frames may be huge. FIG. 3 illustrates a schematic diagram 300 of communication with silence frames. In the example of FIG. 3, a UE 301, an NTN eNB 302, and a UE 303 are involved. The UE 301 may communicate with the UE 303 via the NTN eNB 302. The example of FIG. 3 may include a voice call example with 100s IMS voice data transmission via the GEO. In this case, the NTN eNB 302 may be implemented as a GEO eNB.
[0077] The UE 301 may talk for 20 seconds and listen to the UE 303 for 80 seconds. The NTN eNB 302 may schedule the UE 301 for voice data UL transmissions in 20 seconds, and schedules UE 301 for SID frame transmissions in 80 seconds. UE 303 may be scheduled with reverse ordering, e.g., the UE 303 may be scheduled for SID frame transmissions in 80s, and for voice data DL transmissions in 20s.
[0078] For example, a block 311, a block 313, or a block 315 may represent a word from the UE 301, and a block 312, a block 314 or a block 316 may represent a speech pause. In the example of FIG. 3, the block 316 may represent a speech pause for 80 seconds.
[0079] An end to end (E2E) latency may be larger than four times of a time of propagation delay between the UE 301 and the NTN eNB 302 (e.g., 120 ms) . An SGW may be on the ground. A UE SPS periodicity may be configured without GEO orbit consideration (e.g., 128ms) . A SID and silence frames may be filled for UL transmissions while each speech pause and silence period. In the example of FIG. 3, the SID and the silence frames may introduce huge unnecessary overheads to voice code rate and the UL transmissions on a Uu interface. Transmission power may be wasted, especially if the background noise is rather stable and does not change much during the silence period.
[0080] Since an NTN orbit is unaware of SPS configuration applied, an NTN eNB may periodically schedule UE for UL transmission, e.g., every 128ms. For example, a period for a media service, e.g., a voice service, may last for 100s. In this case, additional latency may be added to the voice service by each scheduling, which may increase power consumption of a GEO satellite and serving cell loads. There may be 5 SPS periodicity configured to the UE during an E2E latency (denoted as “E2E latency T”) . In this case, 4 UL retransmission (reTx) may happen due to weak NTN Uu link budget, even when the first transmission is on the way. The reTx may introduce additional latency to the voice service.
[0081] A current 3GPP codec code rate may need to be reduced to meet GEO voice service needs especially in Uu UL transmissions. Mechanisms to apply SPS configurations to minimize the E2E latency may also need to be considered.
[0082] Embodiments of the present disclosure propose a solution for communication with regenerative silence frames . In the solution, an apparatus determines a silence period for a media service based on received data for the media service. No user data associated with the media service is to be transmitted during the silence period. A length of the silence period is larger than a threshold length. The threshold length is associated with a periodicity of a resource configured for the media service. Then, the apparatus transmits, to a device, a message indicating the silence period or a description for at least one silence frame corresponding to the silence period.
[0083] In this way, the message indicating the silence period or the description of the at least one silence frame may be transmitted to the device from the apparatus instead of silence frames. Thus, overhead of the communication with regenerative silence frames can be reduced. The efficiency and flexibility of the communication can be improved.
[0084] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It is to be understood the order acts shown in FIGS. 4 to 13 are only for example but not limitation. Acts may be performed in any suitable manner. Example embodiments described with reference to FIGS. 4 to 13 may be implemented separately or combined in any manner. For example, one or more example embodiments shown in a single drawing may be combined with one or more example embodiments shown in one or more other drawings.
[0085] Additionally, procedures in FIGS. 4 to 13 are only an example but not limitation. The procedures illustrated in dotted lines in FIGS. 4 to 13 are optional and may be excluded in processes in accordance with some example embodiments of the present disclosure.
[0086] FIG. 4 illustrates a signaling flow 400 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. For the purposes of discussion, the signaling flow 400 will be discussed with reference to FIG. 1. The FIG. 4 involves the apparatus 110, the device 120, and the apparatus 130 of FIG. 1. In the example of FIG. 4, the apparatus 110, the device 120, or the apparatus 130 may support the remote regenerative silence frame (RRSF) .
[0087] In some example implementations, the apparatus 110 may be implemented as or include a terminal device, e.g., a UE. The device 120 may be implemented as or include a network device, a network entity, or a terminal device, e.g., a NTN base station, a SGW, a server, a UE, and / or the like. The apparatus 130 may be implemented as or include a network entity or a terminal device, e.g., a SGW, a server, or a UE. Additionally, in some example embodiments, the device 120 may include the apparatus 130.
[0088] In operation, the apparatus 110 determines (401) a silence period for a media service based on received data for the media service. No user data associated with the media service is to be transmitted during the silence period. A length of the silence period is larger than a threshold length. The threshold length is associated with a periodicity of a resource configured for the media service.
[0089] In some example embodiments, the media service may include an IMS service, e.g., an IMS voice call. The length of the silence period may include a time length. The threshold length may be a length of the periodicity. The periodicity may include a SPS periodicity of the resource configured for the media service. The threshold length for the silence period may be associated with the SPS periodicity to determine the silence period long enough for using the regenerative silence frame. Thus, overhead of the at least one silence frame corresponding to the silence period can be reduced. Efficiency of the communication with the silence frames can be improved.
[0090] It is to be understood that the SPS periodicity mentioned herein are only for the purpose of illustration, without suggesting any limitation. Embodiments of the present disclosure are not limited here. Any suitable periodicity may be involved in the embodiments of the present disclosure.
[0091] In some example embodiments, the device 110 may determine the periodicity based on an E2E latency between the apparatus 110 and the apparatus 130. Then, the device 110 may transmit information of the periodicity to the apparatus 110. In this way, the periodicity determined based on the E2E latency can be used to reduce interference caused by the E2E latency and retransmission associated with a Uu interface.
[0092] Additionally, the apparatus 110 may transmit, to the device 120, capability information of the apparatus 110. The capability information may indicate the apparatus 110 supports the RRSF. As such, the RRSF can be supported in the communication between the apparatus 110 and the device 120.
[0093] After determining (401) the silence period, the apparatus 110 transmits (402) , to the device 120, a message indicating the silence period or a description for at least one silence frame corresponding to the silence period. Correspondingly, the device 120 receives (403) the message. The apparatus 130 receives (404) the message.
[0094] The description for the at least one silence frame may indicate an energy level of background noise. For example, the description may indicate that the at least one silence frame is to be generated with silence, background noise with low energy, background noise with high energy, and / or the like. In this way, instead of the at least one silence frame, the description of the at least one silence frame may be transmitted to the apparatus 130 and used for generating the at least one silence frame. Overhead for the at least one silence frame can be reduced.
[0095] In some example implementations, the apparatus 110 may transmit the message to the apparatus 130 via the device 120. In some example embodiments, the apparatus 110 may transmit the message to the apparatus 130 via the device 120 and a further apparatus, e.g., a network entity. Specifically, the device 120 may transmit, to the apparatus 130 via the further apparatus, a further message indicating the silence period or the description for the at least one silence frame. In this case, the device 120 may include a network device, the further apparatus may include a network entity in a core network, e.g., a MME. Additionally, the apparatus 130 may include a network entity, e.g., an SGW.
[0096] After receiving (403) the message, the device 120 determines (405) that no user data is to be transmitted during the silence period based on the message. For example, in response to determining (405) that no user data is to be transmitted during the silence period, the device 120 may halt transmitting user data to the apparatus 130.
[0097] After receiving (404) the message, the apparatus 130 generates (406) the at least one silence frame based on the message. Specifically, the apparatus 130 may generate the at least one silence frame based on the silence period and the description of the at least one silence frame in the message. For example, the apparatus 130 may determine the number of the at least one silence frame based on the length of the silence period, and the energy level of the at least one silence frame based on the description of the at least one silence frame.
[0098] In some example embodiments, after generating (406) the at least one silence frame, the apparatus 130 may apply the at least one silence frame to the media service.
[0099] In some example implementations, the apparatus 110 may determine that incoming user data associated with the media service is to be transmitted. For example, if the media service is an IMS voice call, the apparatus 110 may determine that a user of the apparatus 110 is talking. In this case, the apparatus 110 may transmit, to the device 120, an indication to terminate generation of the at least one silence frame.
[0100] Thus, the incoming user data may be transmitted without interference caused by the at least one silence frame generated by the apparatus 130. Additionally, when the generation of the at least one silence frame is terminated, the at least one silence frame generated may correspond to the silence period determined by the apparatus 110.
[0101] The apparatus 110 may transmit the indication to the apparatus 130. In some example embodiments, the apparatus 110 may transmit the indication to the apparatus 130 via the device 120 and a further apparatus. Correspondingly, after receiving the indication, the apparatus 130 may stop generating the at least one silence frame. In this case, the device 120 may include a network device, and the further apparatus may include a network entity in a core network, e.g., a MME. Additionally, the apparatus 130 may include a network entity, e.g., an SGW.
[0102] In this way, the apparatus 110 may transmit, to the device 120, the message indicating the silence period or the description of the at least one silence frame instead of the silence frames. The at least one silence frame may be generated by the apparatus 130 for the media service. Thus, overhead of the communication between the apparatus 110 and the apparatus 130 via the device 120 can be reduced in a flexible and efficient way.
[0103] In some example embodiments, a network codec or a listener UE codec may perform voice activity detection and regenerate comfort noise aware silence frame, instead of a talker UE codec. Network signal UE flexible SPS periodicity configuration with NTN orbit consideration to tolerate high E2E call latency in the NTN may be used to support discontinuous UL transmission and address UE power saving and voice data rate and Uu load reduction.
[0104] Reference is made to FIG. 5, which illustrates a schematic diagram of an example process 500 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. The example embodiments discussed with respect to FIG. 5 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the process 500 will be discussed with reference to FIG. 1.
[0105] The example process 500 involves a UE 501, an NTN eNB 502, a network entity 503, and a device 504. The UE 501 may be an implementation of the apparatus 110 in FIG. 1. The NTN eNB 502, the network entity 503, and the device 504 may be an implementation of the device 120 in FIG. 1. In some example embodiments, the NTN eNB 502 may be replaced with a base station, a gNB, and / or the like. The network entity 503 and the device 504 may be an implementation of the apparatus 130 in FIG. 1. Additionally, the network entity 503 may include a MME, an SGW, an AMF, a UPF, and / or the like. The device 504 may include a server (e.g., an application server) , a peer UE, and / or the like.
[0106] In the example of FIG. 5, the UE 501 may communicate with the device 504 (e.g., the peer UE) by an IMS service, e.g., an IMS voice call. The NTN eNB 502 may be used to perform the communication. The network entity 503 or the device 504 may generate silence frames in the IMS voice call.
[0107] The UE 501 may have a capability to support the RRSF during long enough the silence periods or speech pauses, to reduce voice code rate on Uu UL transmissions. At 5010, the UE 501 may indicate the RRSF supporting capability to a network and trigger the NTN eNB 502 to configure the UE 501 with a SPS periodicity to align with an E2E latency.
[0108] Once the NTN eNB 502 obtains capability to support the RRSF of the UE 501, the NTN eNB 502 may determine the E2E latency according to an eNB orbit and a MME / SGW location, and configure the UE 501 with a SPS periodicity aligned with the determined E2E latency. The UE 501 may configure a codec to setup a time threshold for monitoring the speech pauses or the silence period.
[0109] The UE 501, upon initializing / receiving the IMS voice call, may decide to request network assistance to regenerate silence frames. If the speech pauses or the silence period exceeding the threshold is detected, the UE 501 may determine long enough silence periods for the network or the device 504 (e.g., the peer UE) to regenerate the silence frames and report the silence periods and silence frame descriptions to the network or the device 504 (e.g., the peer UE) . During the periods, the UE 501 may not send any buffer status report (BSR) .
[0110] The NTN eNB 502 may not schedule the UL transmission of the UE 501 during the reported silence periods. The network entity 503 (e.g., the SGW) or the device 504 may generate silence frames instead of the codec of the UE 501 during the reported silence periods using the reported silence frame descriptions.
[0111] For example, at 5020, if the UE 501 has no voice data to transmit in current SPS period and determines long silence periods ahead, the UE 501 may report the silence periods and the silence frame descriptions to the network or the device 504 (e.g., the peer UE) . During the silence periods, the NTN eNB 502 may stop or skip UE UL SPS. The network entity 503 (e.g., the SGW) and the device 504 may generate the silence frames instead of the UE 501.
[0112] If the UE 501 has a new speech frame transmission, the UE 501 may request the NTN eNB 502 to recover UL transmission by sending a buffer status report (BSR) for a non-access stratum (NAS) / application message, which is used to notice the network entity 503 or the device 504 to stop generating the silence frames.
[0113] In particular, at 5030, once the UE 501 has new voice data to be transmitted, the UE 501 may request the NTN eNB 502 to recover the UE UL SPS by indicating the network entity 503 or the device 504 to stop silence frames generation.
[0114] In this way, the UE 501 may determine the long enough silence periods and report to the network. The network entity 503 (e.g., the SGW) or the device 504 may generate the silence frames instead of receiving the silence frames from the UE 501. Thus, overhead of the communication between the UE 501 and the device 504 (e.g., the peer UE) can be reduced.
[0115] In some example embodiments, for the communication with the RRSF, the UE may report a new capability indicates that the UE may support a RRSF feature when camping a network device, e.g., an NTN eNB. Once the RRSF capable UE receives an SPS configuration, the UE may configure a codec with a silence period threshold using the SPS periodicity received in the SPS configuration.
[0116] During an IMS voice call, if a silence period exceeds the threshold detected by the codec, the UE may determine long enough silence periods for a network or a peer UE to regenerate silence frames. Up to a UE implementation, for determining the long enough silence periods, algorithms of the codec may include silence detection using energy thresholding, speech pause detection using pitch tracking, conversation state modeling using hidden Markov models (HMM) , artificial intelligence (AI) and machine learning (ML) -based approaches, and / or the like.
[0117] Specifically, for silence detection using energy thresholding, the UE may set a threshold for the audio signal's energy level to distinguish between speech (non-silence) and silence. When the energy level falls below the threshold, the UE may consider a potential silence period is detected.
[0118] For speech pause detection using pitch tracking, the UE may track a pitch of a speaker's voice over time. The UE may identify periods where the pitch of the speech remains relatively constant or decreases, indicating a potential pause or silence period. Then, the UE may utilize algorithms, e.g., voice activity detection (VAD) or speech activity detection (SAD) .
[0119] For conversation state modeling using HMMs, the UE may model a conversation as a sequence of states (e.g., a speech state, a silence state, a turn-taking state, and / or the like) . The UE may use the HMMs to predict a next state in the sequence based on a current state and observation probabilities.
[0120] Additionally, the UE may train ML or LLM models on large datasets of conversations to learn patterns and relationships between the speech and silence periods. The UE may use recurrent neural networks (RNN) , long short-term memory (LSTM) networks, or other deep learning architectures to model temporal dependencies in the conversation.
[0121] The UE may either report the determined silence periods and the silence frame descriptions to the eNB via a radio resource control (RRC) message, or to the server or to the peer UE via an application message. The silence frame description may include information of the silence or background noise energy, e.g., a header of a AMR SID frame. The UE may not request a UL transmission during the determined silence periods.
[0122] In some example embodiments, the UE may indicate the NTN eNB to recover the UL transmission by sending a BSR for either a NAS message or an application message, to notify a MME / SGW / server / peer UE to stop silence frames generation, while new speech frames are detected by the codec of the UE.
[0123] For example, if the silence frames is generated by the peer UE, when receiving the silence periods and silence frame descriptions from the UE during an IMS voice call, the codec of the peer UE may generate silence frames according to the received descriptions and silence periods. When receiving a silence frame generation stop indication from the UE during an IMS voice call, the codec of the peer UE may stop generating the silence frames.
[0124] For the NTN eNB, when receiving the UE capability indicating the RRSF is supported in an initial access, the NTN eNB may calculate an E2E latency using propagation delay between the UE and the NTN eNB according to an eNB orbit and a MME / SGW location. The NTN eNB may configure the UE with an SPS periodicity in an SPS configuration with a value aligned with the calculated E2E latency.
[0125] During the IMS voice call, when receiving a RRC message including the UE determined silence periods and the silence frame descriptions, the NTN eNB may forward the received information to the MME via an S1 interface.
[0126] Upon receiving the UE-determined silence periods, the NTN eNB may stop / skip the periodical UL transmission during the UE determined silence periods. Additionally, the NTN eNB may recover the periodical UL transmission when receiving a new BSR.
[0127] For the MME / SGW / server, when receiving the UE determined silence periods and the silence frame descriptions, e.g., via the NTN eNB, the MME may forward the received information to the SGW via an S11 interface. The SGW / server may generate the silence frames according to the silence frame descriptions and send the silence frames to the peer UE during the UE determined silence periods.
[0128] When receiving a NAS message indicating that the UE want to stop the silence frame generation, the MME may forward an indication to the SGW. The indicator may indicate to stop the silence frame generation. The SGW / server may stop the silence frames generation and wait for a new UL transmission from the NTN eNB.
[0129] In some example embodiments, the silence frames may not be transmitted to the network in the UE determined long silence periods. In this way, voice code rate and UE power consumption in UL transmission can be reduced. The NTN eNB may determine and configure the UE with a flexible SPS periodicity considering the E2E latency introduced by the propagation delay between the UE and the eNB orbit and the MME / SGW location, to minimize a UE schedule frequency and avoid any additional latency on the Uu interface.
[0130] FIG. 6 illustrates a schematic diagram 600 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. In the example of FIG. 6, a UE 601, an NTN eNB 602, and a UE 603 are involved. The UE 601 may communicate with the UE 603 via the NTN eNB 602. The example of FIG. 6 may include a voice call example with IMS voice data transmission via the NTN eNB 602.
[0131] The example embodiments discussed with respect to FIG. 6 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the schematic diagram 600 will be discussed with reference to FIG. 2C.
[0132] The example of FIG. 6 involves a UE 601, an NTN eNB 602, and a UE 603. The UE 601 may be an implementation of the UE 221 in FIG. 2C. The NTN eNB 602 may be an implementation of the NTN eNB 222 in FIG. 2C. The UE 603 may be an implementation of the UE 225 in FIG. 2C.
[0133] In the example of FIG. 6, the UE 601 may communicate with the UE 603, e.g., via the NTN eNB 602. The example of FIG. 6 may include a voice call with IMS voice data transmission via the GEO. In this case, the NTN eNB 602 may be implemented as a GEO eNB.
[0134] As illustrated, a block 611, a block 613, or a block 615 may represent a word from the UE 601, and a block 612, a block 614 or a block 616 may represent a speech pause. In the example of FIG. 6, the block 616 may represent a speech pause longer than a threshold length. The threshold length may be associated with an SPS periodicity, e.g., the threshold length may be equal to the SPS periodicity.
[0135] When the UE 601 determines that a length of a silence period corresponding to the speech pause of the block 616 is larger than the threshold length, the UE 601 may transmit, to the NTN eNB 602, a message including information of the silence period and a description of silence frames corresponding to the silence period. Correspondingly, after receiving the message, the NTN eNB 602 may determine that no user data is to be transmitted during the silence period based on the message. The UE 603 may receive the message via the NTN eNB 602, and may generate the silence frames based on the message.
[0136] Thus, the silence frames corresponding to the silence period (e.g., represented by the block 616) may be generated at the UE 603 based on the message transmitted from the UE 601. Overhead of the silence frames can be reduced.
[0137] Example embodiments of example signaling flows of the communication with the silence frames will be described in detail below with reference to the accompanying drawings. It is to be understood the order acts shown in FIGS. 7 to 10 are only for example but not limitation. Acts may be performed in any suitable manner. Example embodiments described with reference to FIGS. 7 to 10 may be implemented separately or combined in any manner. For example, one or more example embodiments shown in a single drawing may be combined with one or more example embodiments shown in one or more other drawings.
[0138] FIG. 7 illustrates a schematic diagram of an example process 700 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. The example embodiments discussed with respect to FIG. 7 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the process 700 will be discussed with reference to FIG. 1.
[0139] The example of FIG. 7 involves a UE 701, a NTN eNB 702, and a MME 703. The UE 701 may be an implementation of the apparatus 110 in FIG. 1. The NTN eNB 702 may be an implementation of the device 120 in FIG. 1. In some example embodiments, the NTN eNB 702 may be replaced with a base station, a gNB, and / or the like. The MME 703 may be replaced with an AMF.
[0140] In operation, at 7010, the UE 701 may report a RRSF supported capability of the UE 701 to the NTN eNB 702 in a message 5 (also referred to “Msg5” , for purpose of discussion) in an initial access procedure. The NTN eNB 702 and the MME 703 may accept the capability of the UE 701. Then, the UE 701 may the UE 701 may initialize or receive an IMS voice call.
[0141] At 7020, the NTN eNB 702 may calculate an E2E latency using a propagation delay between the UE 701 and an orbit of the NTN eNB 703 and a MME / SGW location. Then, the NTN eNB 702 may configure an SPS periodicity using the calculated E2E latency.
[0142] At 7030, the NTN eNB 702 may signal the UE 701 the SPS periodicity. For example, the NTN eNB 702 may transmit, to the UE 701, a RRC message including the SPS configuration.
[0143] Subsequently, the UE 701 may derive the SPS periodicity from the SPS configuration and configure a codec of the UE 701 with a silence period threshold using the SPS periodicity via a UE internal interfaces at 7040. For example, the silence period threshold may be equal to the SPS periodicity.
[0144] At 7050, the NTN eNB 702 may schedule the UE 701 periodically for the IMS voice call, . e.g., based on the SPS periodicity.
[0145] Thus, the UE 701 may be connected to the NTN eNB 702 and configured with the SPS periodicity determined by the NTN eNB 702 based on the E2E latency.
[0146] The example embodiments discussed with respect to FIGS. 8 to 10 may be implemented after the example embodiment discussed with respect to FIG. 7.
[0147] FIG. 8 illustrates a schematic diagram of an example process 800 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. The example embodiments discussed with respect to FIG. 8 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the process 800 will be discussed with reference to FIG. 2A.
[0148] The example of FIG. 8 involves a UE 801, a NTN eNB 802, a MME 803, and an SGW 804. The UE 801 may be an implementation of the UE 201 in FIG. 2A. The NTN eNB 802 may be an implementation of the NTN eNB 202 in FIG. 2A. The MME 803 may be an implementation of the MME 203 in FIG. 2A. The SGW 804 may be an implementation of the SGW 204 in FIG. 2A. In the example of FIG. 8, the UE 801 and / or the SGW 804 may support the RRSF. In some example embodiments, the NTN eNB 802 may be replaced with a base station, a gNB, and / or the like. The MME 803 may be replaced with an AMF, and the SGW 804 may be replaced with a UPF.
[0149] In operation, at 8010, the UE 801 (e.g., the codec of the UE 801) detects a speech pause or a silence period exceeding a configured threshold (e.g., the silence period threshold determined in the example of FIG. 7) . The UE 801 may determine long enough silence periods that take multiple thresholds. The UE 801 may decide silence frame descriptions for the long enough silence periods.
[0150] At 8020, the UE 801 sends a RRC message to the NTN eNB 802. The RRC message includes a silence frame pattern including the determined long enough silence periods and the silence frame descriptions. The NTN eNB 802 may forward the received information in the RRC message to the MME 803 via an S1 interface at 8030. Then the MME 803 may forward the information received from the NTN eNB 802 to the SGW 804 via an S11 interface at 8040.
[0151] Subsequently, the NTN eNB 802 stops or skips a UE UL transmission during the UE determined long enough silence periods at 8050. The SGW 804 generates silence frames using the received silence frame descriptions instead of the codec of the UE 801 during the received silence periods at 8060.
[0152] At 8070, the UE 801 (e.g., the codec of the UE 801) may detect speech frames for the next SPS periodicity. In this case, the UE 801 may need to request the NTN eNB 802 to recover the UL transmission.
[0153] At 8080, the UE 801 may send a BSR to the NTN eNB 802 for a NAS / application message transmission. At 8090, the UE 801 may sends a NAS message, adding an indication (e.g., a flag) to indicate the SGW 804 to stop generating the silence frames. The MME 803 may forward the indication to the SGW 804 at 8100. Then, the SGW 804 may stop generating the silence frames at 8110. At 8120, the NTN eNB 802 may schedule the UE 801 periodically for the IMS voice call.
[0154] As such, the SGW 804 may generate the silence frames based on the information received from the UE 801 via the NTN eNB 802 and the MME 803. Overhead for transmissions associated with the silence frames can be reduced.
[0155] FIG. 9 illustrates a schematic diagram of an example process 900 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. The example embodiments discussed with respect to FIG. 9 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the process 900 will be discussed with reference to FIG. 2B.
[0156] The example of FIG. 9 involves a UE 901, an NTN eNB 902, and a server 903. The UE 901 may be an implementation of the UE 211 in FIG. 2B. In the example of FIG. 9, the UE 901 and / or the server 903 may support the RRSF. The NTN eNB 902 may be an implementation of the NTN eNB 212 in FIG. 2B. The server 903 may be an implementation of the server 213 in FIG. 2B. The server 903 may include a function of a server, e.g., an application server. In some example embodiments, the NTN eNB 902 may be replaced with a base station, a gNB, and / or the like.
[0157] In operation, at 9010, the UE 901 (e.g., the codec of the UE 901) detects a speech pause or a silence period exceeding a configured threshold (e.g., the silence period threshold determined in the example of FIG. 7) . This step is similar to 8010 and thus will not be repeated here.
[0158] At 9020, the UE 901 sends a RRC message to the NTN eNB 902. The RRC message includes a silence frame pattern including the determined long enough silence periods and the silence frame descriptions. At 9030, the UE 901 sends information of the silence periods and the silence frame descriptions to the server 903 directly.
[0159] At 9040, the NTN eNB 902 stops or skips a UE uplink transmission during the UE determined long enough silence periods. At 9050, the server 903 generates silence frames using the received silence frame descriptions instead of the codec of the UE 901 during the received silence periods.
[0160] At 9060, the UE 901 (e.g., the codec of the UE 901) may detect speech frames for the next SPS periodicity. This step is similar to 8050 and thus will not be repeated here.
[0161] At 9070, the UE 901 may send a BSR to the NTN eNB 902 for a NAS / application message transmission. At 9080, the UE 901 may directly sends an indication indicating the server 903 to stop generating the silence frames. Then, at 9090, the server 903 may stop generating the silence frames. At 9100, the NTN eNB 902 may schedule the UE 901 periodically for the IMS voice call.
[0162] In this way, the server 903 may generate the silence frames based on the information from the UE 901. Overhead for transmissions associated with the silence frames can be reduced.
[0163] FIG. 10 illustrates a schematic diagram of an example process 1000 of communication with regenerative silence frames in accordance with some embodiments of the present disclosure. The example embodiments discussed with respect to FIG. 10 may be considered as implementations of the example embodiments discussed with reference to FIG. 4. For the purposes of discussion, the process 1000 will be discussed with reference to FIG. 2C.
[0164] The example of FIG. 10 involves a UE 1001, a NTN eNB 1002, and a UE 1003. The UE 1001 may be an implementation of the UE 221 in FIG. 2C. In the example of FIG. 10, the UE 1001 and / or the UE 1003 may support the RRSF. The NTN eNB 1002 may be an implementation of the NTN eNB 222 in FIG. 2C. The UE 1003 may be an implementation of the UE 225 in FIG. 2C. In some example embodiments, the NTN eNB 202 may be replaced with a base station, a gNB, and / or the like.
[0165] In operation, at 10010, the UE 1001 (e.g., the codec of the UE 1001) detects a speech pause or a silence period exceeding a configured threshold (e.g., the silence period threshold determined in the example of FIG. 7) . This step is similar to 8010 and thus will not be repeated here.
[0166] At 10020, the UE 1001 sends a RRC message to the NTN eNB 1002. The RRC message includes a silence frame pattern including the determined long enough silence periods and the silence frame descriptions. At 10030, the UE 1001 sends information of the silence periods and the silence frame descriptions to the UE 1003 directly.
[0167] At 10040, the NTN eNB 1002 stops or skips a UE UL transmission during the UE determined long enough silence periods. At 10050, the UE 1003 generates silence frames using the received silence frame descriptions instead of the codec of the UE 1001 during the received silence periods.
[0168] At 10060, the UE 1001 (e.g., the codec of the UE 1001) may detect speech frames for the next SPS periodicity. This step is similar to 8050 and thus will not be repeated here.
[0169] At 10070, the UE 1001 may send a BSR to the NTN eNB 1002 for a NAS / application message transmission. At 10080, the UE 1001 may directly sends an indication indicating the UE 1003 to stop generating the silence frames. Then, at 10090, the UE 1003 may stop generating the silence frames. At 10100, the NTN eNB 1002 may schedule the UE 1001 periodically for the IMS voice call.
[0170] In this way, the UE 1003 may generate the silence frames based on the information from the UE 1001. Overhead for transmissions associated with the silence frames can be reduced.
[0171] FIG. 11 shows a flowchart of an example method 1100 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the apparatus 110 in FIG. 1.
[0172] At block 1110, the apparatus 110 determines a silence period for a media service based on received data for the media service. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service. Thus, the silence period of which the overhead may be reduced by using the RRSF can be determined.
[0173] At block 1120, the apparatus 110 transmits, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period. In this way, the message may be used for generating the at least one silence frame instead of transmitting the at least one silence frame. The overhead for the silence period can be reduced.
[0174] In some example embodiments, the apparatus 110 may determine that incoming user data associated with the media service is to be transmitted. The apparatus 110 may transmit, to the device, an indication to terminate generation of the at least one silence frame. In this way, the incoming user data may be transmitted without interference caused by the at least one silence frame. Additionally, when the generation of the at least one silence frame is terminated, the at least one silence frame generated may correspond to the silence period determined by the apparatus 110.
[0175] In some example embodiments, the apparatus 110 may transmit the indication to the device via a further device and a further apparatus.
[0176] In some example embodiments, the apparatus 110 may transmit the message to the device via a further device and a further apparatus.
[0177] In some example embodiments, the further device may include a network device, and the further apparatus may include a network entity in a core network.
[0178] In some example embodiments, the apparatus 110 may receive information of the periodicity from the device. The periodicity is determined based on an end-to-end (E2E) latency between the apparatus and an apparatus. As such, the periodicity determined based on the E2E latency can be used to reduce interference caused by the E2E latency and retransmission associated with a Uu interface.
[0179] In some example embodiments, the threshold length may be a length of the periodicity.
[0180] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service. Thus, overhead of the at least one silence frame corresponding to the silence period can be reduced. Efficiency of the communication with the silence frames can be improved.
[0181] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0182] In some example embodiments, the apparatus 110 may transmit, to the device, capability information of the apparatus, wherein the capability information indicates the apparatus supports remote regenerative silence frame (RRSF) . In this way, the RRSF can be supported in the communication with the silence frames between the apparatus 110 and the device.
[0183] In some example embodiments, the apparatus may include a terminal device, and the device may include at least one of a network device, a network entity or a further terminal device.
[0184] FIG. 12 shows a flowchart of an example method 1200 implemented at a device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the device 120 in FIG. 1.
[0185] At block 1210, the device 120 receives, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service.
[0186] At block 1220, the device 120 determines that no user data is to be transmitted during the silence period based on the message.
[0187] In some example embodiments, the device 120 may transmit, to a further apparatus via a further device, a further message indicating at least one of the silence period or the description for the at least one silence frame.
[0188] In some example embodiments, the further apparatus may include a network entity, the further device may include a further network entity in a core network.
[0189] In some example embodiments, the device 120 may determine the periodicity based on an end-to-end (E2E) latency between the apparatus and a further apparatus. the device 120 may transmit information of the periodicity to the apparatus.
[0190] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.
[0191] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0192] In some example embodiments, the device 120 may receive, from the apparatus, capability information of the apparatus, wherein the capability information indicates the apparatus supports remote regenerative silence frame (RRSF) .
[0193] In some example embodiments, the apparatus may include a terminal device, and the device may include a network device.
[0194] FIG. 13 shows a flowchart of an example method 1300 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the apparatus 130 in FIG. 1.
[0195] At block 1310, the apparatus 130 receives, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service.
[0196] At block 1320, the apparatus 130 generates the at least one silence frame based on the message.
[0197] In some example embodiments, the apparatus 130 may apply the at least one silence frame to the media service.
[0198] In some example embodiments, the apparatus 130 may receive the message from the further apparatus via a device and a further device.
[0199] In some example embodiments, the apparatus 130 may receive, from the further apparatus, an indication to terminate generation of the at least one silence frame. The apparatus 130 may stop generating the at least one silence frame.
[0200] In some example embodiments, the apparatus 130 may receive, from the further apparatus via a device and a further device, an indication to terminate generation of the at least one silence frame. The apparatus 130 may stop generating the at least one silence frame.
[0201] In some example embodiments, the device may include a network device, and the further device may include a network entity in a core network.
[0202] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.
[0203] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0204] In some example embodiments, the apparatus may include a network entity or a terminal device, and the further apparatus may include a further terminal device.
[0205] In some example embodiments, an apparatus capable of performing any of the method 1100 (for example, the apparatus 110 in FIG. 1) may include means for performing the respective operations of the method 1100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the apparatus 110 in FIG. 1.
[0206] In some example embodiments, the apparatus includes means for determining a silence period for a media service based on received data for the media service. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service. The apparatus includes means for transmitting, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.
[0207] In some example embodiments, the apparatus may further include: means for determining that incoming user data associated with the media service is to be transmitted; and means for transmitting, to the device, an indication to terminate generation of the at least one silence frame.
[0208] In some example embodiments, the apparatus may further include: means for transmitting the indication to the device via a further device and a further apparatus.
[0209] In some example embodiments, the apparatus may further include: means for transmitting the message to the device via a further device and a further apparatus.
[0210] In some example embodiments, the further device may include a network device, and the further apparatus may include a network entity in a core network.
[0211] In some example embodiments, the apparatus may further include: means for receiving information of the periodicity from the device. The periodicity is determined based on an end-to-end (E2E) latency between the apparatus and an apparatus.
[0212] In some example embodiments, the threshold length may be a length of the periodicity.
[0213] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.
[0214] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0215] In some example embodiments, the apparatus may further include: means for transmitting, to the device, capability information of the apparatus. The capability information indicates the apparatus supports remote regenerative silence frame (RRSF) .
[0216] In some example embodiments, the apparatus may include a terminal device, and the device may include at least one of a network device, a network entity or a further terminal device.
[0217] In some example embodiments, a device capable of performing any of the method 1200 (for example, the device 120 in FIG. 1) may comprise means for performing the respective operations of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The device may be implemented as or included in the device 120 in FIG. 1.
[0218] In some example embodiments, the device includes means for receiving, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service. The device includes means for determining that no user data is to be transmitted during the silence period based on the message.
[0219] In some example embodiments, the device may further include: means for transmitting, to a further apparatus via a further device, a further message indicating at least one of the silence period or the description for the at least one silence frame.
[0220] In some example embodiments, the further apparatus may include a network entity, the further device may include a further network entity in a core network.
[0221] In some example embodiments, the device may further include: means for determining the periodicity based on an end-to-end (E2E) latency between the apparatus and a further apparatus; and means for transmitting information of the periodicity to the apparatus.
[0222] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.
[0223] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0224] In some example embodiments, the device may further include: means for receiving, from the apparatus, capability information of the apparatus. The capability information indicates the apparatus supports remote regenerative silence frame (RRSF) .
[0225] In some example embodiments, the apparatus may include a terminal device, and the device may include a network device.
[0226] In some example embodiments, an apparatus capable of performing any of the method 1300 (for example, the apparatus 130 in FIG. 1) may comprise means for performing the respective operations of the method 1300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the apparatus 130 in FIG. 1.
[0227] In some example embodiments, the apparatus includes means for receiving, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period. No user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service. The apparatus includes means for generating the at least one silence frame based on the message.
[0228] In some example embodiments, the apparatus may further include: means for applying the at least one silence frame to the media service.
[0229] In some example embodiments, the apparatus may further include: means for receiving the message from the further apparatus via a device and a further device.
[0230] In some example embodiments, the apparatus may further include: means for receiving, from the further apparatus, an indication to terminate generation of the at least one silence frame; and means for stopping generating the at least one silence frame.
[0231] In some example embodiments, the apparatus may further include: means for receiving, from the further apparatus via a device and a further device, an indication to terminate generation of the at least one silence frame; and means for stopping generating the at least one silence frame.
[0232] In some example embodiments, the device may include a network device, and the further device may include a network entity in a core network.
[0233] In some example embodiments, the periodicity may include a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.
[0234] In some example embodiments, the description for the at least one silence frame may indicate an energy level of background noise.
[0235] In some example embodiments, the apparatus may include a network entity or a terminal device, and the further apparatus may include a further terminal device.
[0236] FIG. 14 is a simplified block diagram of a device 1400 that is suitable for implementing example embodiments of the present disclosure. The device 1400 may be provided to implement a communication device, for example, the apparatus 110 , the device 120 or the apparatus 130 as shown in FIG. 1. As shown, the device 1400 includes one or more processors 1410, one or more memories 1420 coupled to the processor 1410, and one or more communication modules 1440 coupled to the processor 1410.
[0237] The communication module 1440 is for bidirectional communications. The communication module 1440 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1440 may include at least one antenna.
[0238] The processor 1410 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1400 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0239] The memory 1420 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1424, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 1422 and other volatile memories that will not last in the power-down duration.
[0240] A computer program 1430 includes computer executable instructions that are executed by the associated processor 1410. The instructions of the program 1430 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1430 may be stored in the memory, e.g., the ROM 1424. The processor 1410 may perform any suitable actions and processing by loading the program 1430 into the RAM 1422.
[0241] The example embodiments of the present disclosure may be implemented by means of the program 1430 so that the device 1400 may perform any process of the disclosure as discussed with reference to FIG. 4 to FIG. 13. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0242] In some example embodiments, the program 1430 may be tangibly contained in a computer readable medium which may be included in the device 1400 (such as in the memory 1420) or other storage devices that are accessible by the device 1400. The device 1400 may load the program 1430 from the computer readable medium to the RAM 1422 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0243] FIG. 15 shows an example of the computer readable medium 1500 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1500 has the program 1430 stored thereon.
[0244] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0245] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0246] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0247] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0248] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0249] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0250] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:determine a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andtransmit, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.2.The apparatus of claim 1, wherein the apparatus is caused to:determine that incoming user data associated with the media service is to be transmitted; andtransmit, to the device, an indication to terminate generation of the at least one silence frame.3.The apparatus of claim 2, wherein the apparatus is caused to:transmit the indication to the device via a further device and a further apparatus.4.The apparatus of any of claims 1 to 3, wherein the apparatus is caused to:transmit the message to the device via a further device and a further apparatus.5.The apparatus of claim 3 or claim 4, wherein the further device comprises a network device, and the further apparatus comprises a network entity in a core network.6.The apparatus of any of claims 1 to 5, wherein the apparatus is caused to:receive information of the periodicity from the device, wherein the periodicity is determined based on an end-to-end (E2E) latency between the apparatus and an apparatus.7.The apparatus of any of claims 1 to 6, wherein the threshold length is a length of the periodicity.8.The apparatus of any of claims 1 to 7, wherein the periodicity comprises a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.9.The apparatus of any of claims 1 to 7, wherein the description for the at least one silence frame indicates an energy level of background noise.10.The apparatus of any of claims 1 to 9, wherein the apparatus is caused to:transmit, to the device, capability information of the apparatus, wherein the capability information indicates the apparatus supports remote regenerative silence frame (RRSF) .11.The apparatus of any of claims 1 to 10, wherein the apparatus comprises a terminal device, and the device comprises at least one of a network device, a network entity or a further terminal device.12.A device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the device at least to:receive, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; anddetermine that no user data is to be transmitted during the silence period based on the message.13.The device of claim 12, wherein the device is caused to:transmit, to a further apparatus via a further device, a further message indicating at least one of the silence period or the description for the at least one silence frame.14.The device of claim 13, wherein the further apparatus comprises a network entity, the further device comprises a further network entity in a core network.15.The device of any of claims 12 to 14, wherein the device is caused to:determine the periodicity based on an end-to-end (E2E) latency between the apparatus and a further apparatus; andtransmit information of the periodicity to the apparatus.16.The device of any of claims 12 to 15, wherein the periodicity comprises a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.17.The device of any of claims 12 to 16, wherein the description for the at least one silence frame indicates an energy level of background noise.18.The device of any of claims 12 to 17, wherein the device is caused to:receive, from the apparatus, capability information of the apparatus, wherein the capability information indicates the apparatus supports remote regenerative silence frame (RRSF) .19.The device of any of claims 12 to 18, wherein the apparatus comprises a terminal device, and the device comprises a network device.20.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andgenerate the at least one silence frame based on the message.21.The apparatus of claim 20, wherein the apparatus is caused to:apply the at least one silence frame to the media service.22.The apparatus of claim 20 or 21, wherein the apparatus is caused to:receive the message from the further apparatus via a device and a further device.23.The apparatus of claims 20 to 22, wherein the apparatus is caused to:receive, from the further apparatus, an indication to terminate generation of the at least one silence frame; andstop generating the at least one silence frame.24.The apparatus of claims 20 to 22, wherein the apparatus is caused to:receive, from the further apparatus via a device and a further device, an indication to terminate generation of the at least one silence frame; andstop generating the at least one silence frame.25.The apparatus of claim 22 or claim 24, wherein the device comprises a network device, and the further device comprises a network entity in a core network.26.The apparatus of any of claims 20 to 25, wherein the periodicity comprises a semi-persistent scheduling (SPS) periodicity of the resource configured for the media service.27.The apparatus of any of claims 20 to 26, wherein the description for the at least one silence frame indicates an energy level of background noise.28.The apparatus of any of claims 20 to 27, wherein the apparatus comprises a network entity or a terminal device, and the further apparatus comprises a further terminal device.29.A method comprising:determining a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andtransmitting, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.30.A method comprising:receiving, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; anddetermining that no user data is to be transmitted during the silence period based on the message.31.A method comprising:receiving, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andgenerating the at least one silence frame based on the message.32.An apparatus comprising:means for determining a silence period for a media service based on received data for the media service, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andmeans for transmitting, to a device, a message indicating at least one of the silence period or a description for at least one silence frame corresponding to the silence period.33.A device comprising:means for receiving, from an apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andmeans for determining that no user data is to be transmitted during the silence period based on the message.34.An apparatus comprising:means for receiving, from a further apparatus, a message indicating at least one of a silence period for a media service or a description for at least one silence frame corresponding to the silence period, wherein no user data associated with the media service is to be transmitted during the silence period, a length of the silence period is larger than a threshold length, and the threshold length is associated with a periodicity of a resource configured for the media service; andmeans for generating the at least one silence frame based on the message.35.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of any of claims 29 to 31.
