Source coding method and apparatus, communication device, and readable storage medium

Abstract

The present application relates to the technical field of wireless communications, and discloses a source coding method and apparatus, a communication device, and a readable storage medium. The source coding method in embodiments of the present application comprises: a first communication device sends a first data packet, the first data packet comprising a source coding header, the source coding header comprising first indication information, and the first indication information being used for indicating whether the first data packet has undergone source coding. The first data packet is mobile network internal data, and the mobile network internal data comprises at least one of the following: data that has been sent and received at any two of a terminal, a radio access network device and a core network device, and data that has been sent or received at any one of the terminal, the radio access network device and the core network device.

Description

Source coding method, device, communication equipment and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 5, 2023, with application number 202311657315.9 and invention name “Source Coding Method, Device, Communication Equipment and Readable Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of wireless communication technology, and specifically relates to a source coding method, apparatus, communication equipment, and readable storage medium. Background Art

[0004] Data is one of the core elements of mobile networks. User equipment (UE), radio access networks, and core networks can generate massive amounts of data. In addition to user-plane data, this data also includes a large amount of internal mobile network data. For example, terminals or base station equipment in the 6th Generation Mobile Communication Technology (6G) system can measure received signals while transmitting radio waves for communication, thereby wirelessly sensing the radio wave propagation environment and the target objects within it, obtaining perception data such as the target object's position, speed, direction, material, and imaging, thereby supporting a rich range of perception applications and scenarios. At the same time, with the research on artificial intelligence (AI) use cases in 5th Generation Mobile Communication Technology (5G) networks (such as AI models for channel state information (CSI) feedback, beam management and positioning, and user behavior prediction), AI model training requires a large amount of internal mobile network data. AI models ranging from tens of kilobytes to hundreds of megabytes also need to be transmitted between UEs, radio access networks, and core networks. As a ubiquitously connected system, 6G will generate a large amount of valuable basic data and information in the process of supporting the connection between the physical and digital worlds. Compared to 5G, which only provides limited data services such as UE positioning and network information disclosure, 6G will provide wireless sensing and positioning, enhancing network information disclosure. Furthermore, 6G can also collect industry-wide public information such as various sensor information and Geographic Information System (GIS) information, empowering a wide range of industries and avoiding the duplication of such data across various industry applications.

[0005] Therefore, as the internal data of the mobile network generated by the network functions of the aforementioned UE, radio access network and core network increases, the transmission resource overhead of the various functions for collecting and consuming data from each other also increases.

[0006] In order to solve the shortage of storage resources and transmission resources, it is necessary to consider a source coding method that supports data within the mobile network, thereby saving storage resources and transmission resources. Summary of the Invention

[0007] The embodiments of the present application provide a source coding method, apparatus, communication device, and readable storage medium, which can solve the problem of how to support a source coding method for internal data of a mobile network.

[0008] In a first aspect, a source coding method is provided, comprising:

[0009] A first communication device sends a first data packet, where the first data packet includes a source coding header, and the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0010] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0011] In a second aspect, a source coding method is provided, comprising:

[0012] A second communication device receives a first data packet, where the first data packet includes a source coding header, and the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0013] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0014] According to a third aspect, a source coding apparatus is provided, comprising:

[0015] A first sending module, configured to send a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0016] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0017] In a fourth aspect, a source coding apparatus is provided, comprising:

[0018] A first receiving module is configured to receive a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, and the first indication information is used to indicate whether the first data packet is source coded;

[0019] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0020] In a fifth aspect, a communication device is provided, which terminal includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0021] In a sixth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a first data packet, the first data packet comprising a source coding header, the source coding header comprising first indication information, the first indication information being used to indicate whether the first data packet is source encoded; wherein the first data packet is mobile network internal data, the mobile network internal data comprising at least one of the following: sending and receiving data terminated at any two of a terminal, a wireless access network device, and a core network device, and sending or receiving data terminated at any one of a terminal, a wireless access network device, or a core network device.

[0022] In the seventh aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a first data packet, the first data packet including a source coding header, the source coding header including first indication information, the first indication information being used to indicate whether the first data packet is source encoded; wherein the first data packet is mobile network internal data, the mobile network internal data including at least one of the following: sending and receiving data terminated at any two of a terminal, a wireless access network device and a core network device, and sending or receiving data terminated at any one of a terminal, a wireless access network device or a core network device.

[0023] In an eighth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0024] In a ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the method described in the first aspect or the second aspect.

[0025] In a tenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.

[0026] In the eleventh aspect, a wireless communication system is provided, comprising: a first communication device and a second communication device, wherein the first communication device can be used to execute the steps of the method described in the first aspect, and the second communication device can be used to execute the steps of the method described in the second aspect.

[0027] In an embodiment of the present application, a source coding header is set in the header of a data packet of internal data in a mobile network, and the source coding header includes first indication information for indicating whether the data packet is source encoded, thereby supporting the flexible use of source coding for each data packet, while improving data transmission efficiency and increasing the flexibility of source coding. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a block diagram of a wireless communication system applicable to embodiments of the present application;

[0029] FIG2 is a schematic diagram of a data plane protocol architecture terminated in a wireless access network;

[0030] Figure 3 is a schematic diagram of the data plane protocol architecture of the UE, radio access network, and core network;

[0031] FIG4 is a flow chart of a source coding method according to an embodiment of the present application;

[0032] FIG5 is a second flow chart of the source coding method according to an embodiment of the present application;

[0033] FIG6 is one of the example diagrams of the source coding header according to an embodiment of the present application;

[0034] FIG7 is a second example diagram of a source coding header according to an embodiment of the present application;

[0035] FIG8 is a third example diagram of a source coding header according to an embodiment of the present application;

[0036] FIG9 is a fourth example diagram of a source coding header according to an embodiment of the present application;

[0037] FIG10 is a fifth example diagram of a source coding header according to an embodiment of the present application;

[0038] FIG11 is a sixth example diagram of a source coding header according to an embodiment of the present application;

[0039] FIG12 is a seventh example diagram of a source coding header according to an embodiment of the present application;

[0040] FIG13 is a schematic diagram of a structure of a source coding device according to an embodiment of the present application;

[0041] FIG14 is a second structural diagram of the source coding device according to an embodiment of the present application;

[0042] FIG15 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0043] FIG16 is a schematic diagram of the hardware structure of a terminal according to an embodiment of the present application;

[0044] FIG17 is a schematic diagram of a hardware structure of a network-side device according to an embodiment of the present application;

[0045] FIG18 is a second schematic diagram of the hardware structure of the network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0047] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0048] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0049] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0050] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (homeevolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0051] The core network device may include the core network device may include but is not limited to at least one of the following: core network equipment, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data storage (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (Binding Support Function, BSF), application function (AF), location management function (LMF), gateway mobile location center (GMLC), network data analysis function (NWDAF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is taken as an example to introduce, and the specific type of the core network device is not limited.

[0052] The technical contents involved in this application are described below.

[0053] (1) Robust Header Compression (ROHC)

[0054] ROHC is an algorithm for compressing the headers of various Internet Protocol (IP) packets. In IPv4, the uncompressed IP header is 40 bytes, while in IPv6, it is 60 bytes. This isn't a significant issue for standard packet applications (such as file transfers or browsing), as the size of the transmitted data is very large compared to the size of the header. Therefore, the IP header overhead isn't a significant concern. However, in certain applications (such as Voice over Internet Protocol (VoIP), text messaging, and gaming), the amount of data transmitted is often small and transactions are frequent. In these cases, the IP header overhead can become significant. In such cases, any method to reduce the size of the IP header would be extremely beneficial, and ROHC is one such method defined in RFC 3095. The ideal compression ratio for ROHC is to reduce the header size (originally 40 or 60 bytes) to just 1 or 2 bytes.

[0055] The ROHC functional entity resides within the user-plane Packet Data Convergence Protocol (PDCP) entities of the UE and eNodeB / gNB and is solely responsible for header compression and decompression of user-plane data packets. In other words, ROHC primarily compresses the headers of user data packets carried by the mobile network from outside the network.

[0056] (2) Uplink Data Compression (UDC)

[0057] The UDC protocol is based on IETF RFC 1951 (DEFLATE Compressed Data Format Specification). The DEFLATE compression strategy uses the static Huffman coding tree defined in IETF RFC 1951. UDC data blocks must be byte aligned. Z_SYNC_FLUSH is used as the DEFLATE byte alignment, and the last four fixed bytes (0x00 0x00 0xFF 0xFF) are deleted before transmission.

[0058] PDCP entities associated with Data Radio Bearers (DRBs) may be configured by upper layers to use UDC. If UDC is configured, the UE shall apply UDC compression to PDCP Service Data Units (SDUs) received from upper layers corresponding to the configured DRBs. If a predefined dictionary is configured by upper layers, the UE shall pre-fill the compression buffer with the configured predefined dictionary when UDC is configured. If no predefined dictionary is configured by upper layers, the UE shall set the compression buffer to all zeros.

[0059] As can be seen, the UDC functional entity resides within the user-plane PDCP entities of the UE and eNodeB / gNB and is solely responsible for compressing and decompressing user-plane data packets. In other words, UDC primarily compresses user data packets carried by the mobile network from outside the network. Furthermore, each PDCP entity carrying user-plane data uses either UDC or ROHC, but not both simultaneously.

[0060] (3) Data Plane

[0061] In current discussions about 6G network architecture, many industry companies have proposed the data plane. The data plane comprises core network data plane functions, radio access network data plane functions, and UE data plane functions, providing end-to-end connectivity. The data plane is responsible for data control, including data collection coordination, data collection configuration, and data transmission configuration. It also handles at least one of the following functions: data acquisition, data transmission, data preprocessing, data privacy and security, data analysis, data storage, and data services.

[0062] (4) Source encoding and decoding

[0063] The basic communication model of source coding and decoding is as follows: source -> source encoder -> channel encoder -> channel -> channel decoder -> source decoder -> source decoder -> destination.

[0064] The source is the carrier that sends information. The default output here is binary.

[0065] A source encoder performs lossless encoding (or lossy encoding that meets the requirements) on the source output to reduce the redundancy of the source output information. This can be understood as compression.

[0066] The channel encoder encodes the output of the source encoder so that the resulting sequence can be transmitted well over the channel. Redundancy is generally added to enhance anti-interference capabilities.

[0067] Channel: Information is transmitted in the channel and sent to the receiving end.

[0068] The channel decoder decodes the received sequence and can recover certain transmission errors.

[0069] The source decoder decodes the output of the channel decoder to restore the original information sequence.

[0070] The destination requires a carrier of the original information.

[0071] Please refer to Figure 2, which is a schematic diagram of the data plane protocol architecture terminated in the wireless access network. Please refer to Figure 3, which is a schematic diagram of the data plane protocol architecture of the UE, wireless access network and core network.

[0072] The source coding method, apparatus, communication device, and readable storage medium provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0073] Referring to FIG4 , an embodiment of the present application provides a source coding method, including:

[0074] Step 11: The first communication device sends a first data packet, where the first data packet includes a source coding header, and the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded.

[0075] Source coding is a transformation of source symbols for the purpose of improving communication effectiveness, or in other words, a transformation of source symbols to reduce or eliminate source redundancy. It can achieve the effect of reducing the size of source symbols, so source coding can also be called data compression.

[0076] The first data packet in the embodiment of the present application is mobile network internal data, which may refer to data that can be parsed by the UE, radio access network, or core network in the 3GPP standard. Optionally, the mobile network internal data includes at least one of the following:

[0077] 1) Send and receive data that ends at any two of the terminals, wireless access network equipment, and core network equipment;

[0078] It can also be described as a peer-to-peer protocol for sending and receiving data located in the UE, radio access network, or core network.

[0079] For example, the data of the peer protocol layers of the Long Term Evolution Positioning Protocol (LTE Positioning Protocol, LPP) are respectively located in the location management function (LMF) of the UE and the core network; another example is the data of the peer protocol layers of the Radio Resource Control (RRC) are respectively located in the UE and the radio access network equipment (eNB / gNB, base station); another example is the data of the data plane protocol layers are respectively located in the UE and the radio access network equipment or in the UE and the core network equipment.

[0080] 2) Send or receive data that ends at any one of the terminals, wireless access network equipment, or core network equipment.

[0081] It can also be described as sending or receiving data where one end is located in the UE, radio access network, or core network. For example, an AI model generated by an application server or application function outside the mobile network is sent to the UE, radio access network equipment, or core network equipment, and the corresponding equipment needs to deploy and use the AI ​​model.

[0082] The terminal (UE) involved in the above mobile network content data refers to the protocol functions of user equipment (UE) defined by the 3GPP protocol, and does not include application functions.

[0083] For example, the mobile network internal data may include at least one of the following: perception data, positioning data, AI model, and AI model training data.

[0084] In some embodiments, optionally, a first communications device sends a first data packet to a second communications device, where the first data packet includes a source coding header, the source coding header including first indication information, the first indication information being used to indicate whether the first data packet is source coded. After receiving the first data packet, the second communications device may determine whether the first data packet is source coded based on the source coding header, and if it determines that the first data packet is source coded, perform source decoding. In embodiments of the present application, the first communications device may be a data provider, also referred to as a data provision function, and may be a UE, a radio access network device, or a core network device. The second communications device may be a data consumer, also referred to as a data consumption function. Alternatively, the second communications device may be a data plane function node, where data provided by the data provider is provided to the data consumer via the data plane function node. The data plane function node may provide the original data provided by the data provider, or may provide processed data. The second communications device may be a UE, a radio access network device, or a core network device.

[0085] In an embodiment of the present application, a source coding header is set in the header of a data packet of internal data in a mobile network, and the source coding header includes first indication information for indicating whether the data packet is source encoded, thereby supporting the flexible use of source coding for each data packet, while improving data transmission efficiency and increasing the flexibility of source coding.

[0086] In an embodiment of the present application, the first indication information may be an explicit indication of whether the first data packet is source encoded, or may be an implicit indication of whether the first data packet is source encoded. For example, if the first indication information indicates that the data type of the first data packet is control information on the data plane, it implicitly indicates that the first data packet is not source encoded. If the first indication information indicates that the data type of the first data packet is data information on the data plane, it implicitly indicates that the first data packet is source encoded.

[0087] In this embodiment of the present application, optionally, the source coding header further includes at least one of the following:

[0088] 1) Data type: For example, it can be a traceID in an existing protocol, or a task identifier for data collection, etc. It can also be control information on the data plane, or data information on the data plane, etc.

[0089] 2) second indication information, used to indicate whether the first data packet is encoded by a lossy source or a lossless source;

[0090] Since source coding is for mobile network internal data rather than user plane data, appropriate source coding can be used for the first data packet based on the data application scenario and data quality requirements, without being limited to lossless source coding algorithms.

[0091] 3) third indication information, used to indicate whether the source encoding buffer is reset;

[0092] The third indication information indicates whether the source coding buffer of the first communication device is reset.

[0093] 4) A source coding algorithm or algorithm identifier used by the first data packet; the source coding algorithm may include at least one of the following: an algorithm predefined in the protocol, a pre-deployed algorithm.

[0094] 5) A check bit, used to verify the correctness of the source encoding and decoding of the first data packet. The verification object can be a single source-coded data packet. For example, the source encoding end generates a check bit (check bit) by applying a check algorithm (such as parity check) to the data before source encoding. After receiving the data packet, the receiving end performs source decoding and uses the same check algorithm to generate check bits for the decoded data. If the check bits are consistent with the check bits received from the encoding end, the source encoding and decoding is considered correct; otherwise, it is an error.

[0095] In the embodiment of the present application, the check bit is the data before encoding corresponding to the first data packet by the first communication device.

[0096] The second communication device that receives the first data packet performs source decoding on the first data packet, and uses the same verification algorithm to generate a check bit for the decoded data. The check bit is compared with the received check bit. If the check bit is consistent with the received check bit, the source codec is considered to be correct; otherwise, it is an error.

[0097] 6) feedback information, used to indicate whether the source decoding of the source coded data received by the first communication device is correct;

[0098] When a decoding error or packet loss occurs at the receiving end of source-coded data, the error is reported via feedback information. The feedback information primarily provides source coding feedback, allowing the transmitting end of the source-coded data to determine whether source coding parameters need to be adjusted. Adjusting source coding parameters can include adjusting the used source coding parameters, such as the compression ratio, or changing the source coding algorithm. If each data packet can independently utilize source coding, and if decoding errors in a small number of data packets do not impact the use of the first data, retransmission or source coding parameter adjustment is unnecessary. If the transmitting end determines that decoding errors impact data use, one approach is to adjust the compression ratio upon receiving a source decoding error, thereby retaining more data. This process can utilize a unified source coding algorithm or modify the source coding algorithm, and also requires resetting the source coding buffer. The compression ratio can be defined as one of the following: the length of the data after source coding divided by the length of the data before source coding; the length of the data before source coding divided by the length of the data after source coding; or 1 - the length of the data after source coding / the length of the data before source coding.

[0099] When the first communication device receives source-encoded data, it can interpret the parity bit of the source-decoded data according to the protocol-defined parity algorithm and compare it with the received parity bit to determine whether the source decoding is correct. If the parity bit is incorrect, and the transmitting end of the source-encoded data needs to be informed, the aforementioned feedback information can be sent. If the parity bit is correct, or if the transmitting end does not need to know whether the decoding is correct, feedback information can be omitted to reduce overhead. For example, if no feedback is provided, the decoding is considered correct.

[0100] 7) fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted;

[0101] That is, when the first indication information indicates that the first data packet is source coded, the fourth indication information indicates that the first data packet is a data packet obtained by performing source coding on the data to be transmitted itself.

[0102] 8) fifth indication information, used to indicate that the first data packet is a data packet for providing feedback on a decoding result of source coded data received by the first communication device;

[0103] That is, when the first indication information indicates that the first data packet is source encoded, the fifth indication information indicates that the first data packet is a data packet for feedback.

[0104] 9) sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet use the same source coding mode;

[0105] 10) a first sequence number, the first sequence number being the sequence number of the first data packet;

[0106] 11) A second sequence number, where the second sequence number is the sequence number of the source coded data corresponding to the feedback information, and the feedback information is used to indicate whether the source decoding of the source coded data received by the first communication device is correct.

[0107] In an embodiment of the present application, optionally, the first data packet is a start data packet or an end data packet of source coding, and the method further includes: the first communication device sending a second data packet, where the second data packet is a data packet between the start data packet and the end data packet of source coding, and the second data packet does not include at least one of the following:

[0108] Data type;

[0109] the first indication information;

[0110] the second indication information;

[0111] the third indication information;

[0112] a source coding algorithm or algorithm identifier used by the second data packet;

[0113] the fourth indication information;

[0114] The sixth indication information.

[0115] It is understood that the second data packet between the start data packet and the end data packet can use the same source coding method as the first data packet, which can be said to have packet affinity. In this way, the second data packet with a sequence number between the sequence numbers of the start and end data packets does not need at least part of the source coding header information, thereby reducing the overhead of the source coding header.

[0116] In an embodiment of the present application, optionally, the first data packet includes at least one of the following: a data packet corresponding to control information on the data plane, a data packet corresponding to data information on the data plane, and a data packet on the control plane.

[0117] In an embodiment of the present application, optionally, whether the first data packet is source encoded is related to the data type of the first data packet.

[0118] It can be understood that whether the first data packet is source coded is related to the data type of the first data packet, and the first indication information is implicitly indicated by the data type of the source coding header.

[0119] In an embodiment of the present application, optionally, the source coding method further includes: the first communication device determines whether to perform source coding on the data to be transmitted according to data requirements.

[0120] In an embodiment of the present application, optionally, the data requirement includes at least one of the following:

[0121] The length of the data to be transmitted;

[0122] Real-time data transmission;

[0123] Data type;

[0124] The amount of available storage resources.

[0125] In an embodiment of the present application, optionally, the source coding method also includes: the first communication device receives a first message, the first message includes: seventh indication information, the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

[0126] In this embodiment of the present application, optionally, the first communication device receives the first message sent by the second communication device.

[0127] In this embodiment of the present application, optionally, the seventh indication information is used to indicate at least one of the following:

[0128] whether to use source coding for the first uplink data;

[0129] Whether to use source coding for the first downlink data.

[0130] In this embodiment of the present application, optionally, the first message further includes at least one of the following:

[0131] eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data;

[0132] The size of the buffer used for source encoding;

[0133] A source coding algorithm or an algorithm identifier used for the first data.

[0134] In the embodiment of the present application, optionally, the source coding method further includes: the first communication device sending source coding capability information of the first communication device, the source coding capability information including ninth indication information, the ninth indication information being used to indicate whether the first communication device supports source coding;

[0135] The source coding capability information is used to determine the first message.

[0136] In an embodiment of the present application, optionally, the ninth indication information may indicate whether the first communication device supports source coding in an explicit manner, or may indicate whether the first communication device supports source coding in an implicit manner.

[0137] Ninth indication information In an embodiment of the present application, when the first communication device is a UE, optionally, the source coding capability information of the first communication device can be carried in a UE capability report.

[0138] In this embodiment of the present application, optionally, the source coding capability information further includes at least one of the following:

[0139] The maximum number of entities supported using source coding; for example, the maximum number of radio bearers;

[0140] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0141] Supported source coding algorithms or algorithm identifiers. The supported source coding algorithms may include at least one of the following: a standard source coding algorithm (also called a dictionary), an operator-defined source coding algorithm (also called a dictionary). When the supported source coding algorithms include operator-defined source coding algorithms, the source coding capability information may also include the algorithm version and operator PLMN.

[0142] The standard source coding algorithm may include at least one of a lossy source coding algorithm and a lossless source coding algorithm.

[0143] The following example illustrates the lossless source coding algorithm:

[0144] 1) DEFLATE: A widely used lossless compression algorithm, commonly used in file formats such as ZIP and GZIP. This source coding algorithm is used in the existing UDC protocol.

[0145] 2) LZ77 / LZ78: A dictionary-based lossless compression algorithm, commonly used in file formats such as LZW and ZIP.

[0146] 3) Brotli: A lossless compression algorithm developed by Google that features high compression ratio and fast decompression and has become one of the standards for web content compression.

[0147] 4) Zstandard: A lossless compression algorithm developed by Facebook, which features high compression ratio and fast decompression and has become one of the standards in multiple application fields.

[0148] 5) LZ4: A lossless compression algorithm developed by Google that features high compression speed and fast decompression. It is commonly used in scenarios such as real-time data transmission and high-speed caching.

[0149] 6) Snappy: A lossless compression algorithm developed by Google that features high compression speed and fast decompression. It is often used in scenarios such as big data processing and real-time data transmission.

[0150] The following example illustrates the lossy source coding algorithm:

[0151] 1) JPEG: A widely used image compression algorithm that can compress images to 1 / 10 to 1 / 100 of their original size. It is commonly used in digital cameras, mobile devices, televisions, and other scenarios.

[0152] 2) MPEG: A widely used video compression algorithm that can compress videos to 1 / 100 to 1 / 1000 of their original size. It is commonly used in digital television, online video, video conferencing, and other scenarios.

[0153] 3) AAC: A widely used audio compression algorithm that can compress audio to 1 / 10 to 1 / 20 of its original size. It is commonly used in digital music, network audio, mobile devices, and other scenarios.

[0154] 4) Opus: An audio compression algorithm developed by Xiph.org that can compress audio to 1 / 10 to 1 / 20 of its original size while maintaining low latency and high quality. It has become one of the standards for WebRTC audio communication.

[0155] In an embodiment of the present application, optionally, the source coding capability information is defined by a capability parameter of a data plane protocol layer or indicated by a general parameter in a capability parameter of the first communication device.

[0156] Optionally, when the first communication device is a UE, the capability parameter of the first communication device is a UE capability parameter.

[0157] Referring to FIG5 , an embodiment of the present application provides a source coding method, including:

[0158] Step 21: The second communication device receives a first data packet, where the first data packet includes a source coding header, and the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded.

[0159] Source coding is a transformation of source symbols for the purpose of improving communication effectiveness, or in other words, a transformation of source symbols to reduce or eliminate source redundancy. It can achieve the effect of reducing the size of source symbols, so source coding can also be called data compression.

[0160] The first data packet in the embodiment of the present application is mobile network internal data, which may refer to data that can be parsed by the UE, radio access network, or core network in the 3GPP standard. Optionally, the mobile network internal data includes at least one of the following:

[0161] 1) Send and receive data that terminates at any two of the terminals, wireless access network equipment, and core network equipment;

[0162] It can also be described as a peer-to-peer protocol for sending and receiving data located in the UE, radio access network, or core network.

[0163] For example, the data of the peer protocol layers of the Long Term Evolution Positioning Protocol (LTE Positioning Protocol, LPP) are respectively located in the location management function (LMF) of the UE and the core network; another example is the data of the peer protocol layers of the Radio Resource Control (RRC) are respectively located in the UE and the radio access network equipment (eNB / gNB, base station); another example is the data of the data plane protocol layers are respectively located in the UE and the radio access network equipment or in the UE and the core network equipment.

[0164] 2) Send or receive data that ends at any one of the terminals, wireless access network equipment, or core network equipment.

[0165] It can also be described as sending or receiving data where one end is located in the UE, radio access network, or core network. For example, an AI model generated by an application server or application function outside the mobile network is sent to the UE, radio access network equipment, or core network equipment, and the corresponding equipment needs to deploy and use the AI ​​model.

[0166] The terminal (UE) involved in the above mobile network content data refers to the protocol functions of user equipment (UE) defined by the 3GPP protocol, and does not include application functions.

[0167] For example, the mobile network internal data may include at least one of the following: perception data, positioning data, AI model, and AI model training data.

[0168] In some embodiments, optionally, a second communication device receives a first data packet sent by a first communication device, where the first data packet includes a source coding header, the source coding header including first indication information, the first indication information being used to indicate whether the first data packet is source coded. After receiving the first data packet, the second communication device may determine whether the first data packet is source coded based on the source coding header, and if it is determined that the first data packet is source coded, perform source decoding. In embodiments of the present application, the first communication device may be a data provider, also referred to as a data provision function, and may be a UE, a radio access network device, or a core network device. The second communication device may be a data consumer, also referred to as a data consumption function. Alternatively, the second communication device may be a data plane function node, where data provided by the data provider is provided to the data consumer via the data plane function node. The data plane function node may provide the original data provided by the data provider, or may provide processed data. The second communication device may be a UE, a radio access network device, or a core network device.

[0169] In an embodiment of the present application, a source coding header is set in the header of a data packet of internal data in a mobile network, and the source coding header includes first indication information for indicating whether the data packet is source encoded, thereby supporting the flexible use of source coding for each data packet, while improving data transmission efficiency and increasing the flexibility of source coding.

[0170] In an embodiment of the present application, the first indication information may be an explicit indication of whether the first data packet is source encoded, or may be an implicit indication of whether the first data packet is source encoded. For example, if the first indication information indicates that the data type of the first data packet is control information on the data plane, it implicitly indicates that the first data packet is not source encoded. If the first indication information indicates that the data type of the first data packet is data information on the data plane, it implicitly indicates that the first data packet is source encoded.

[0171] In this embodiment of the present application, optionally, the source coding header further includes at least one of the following:

[0172] 1) Data type: For example, it can be a traceID in an existing protocol, or a task identifier for data collection, etc. It can also be control information on the data plane, or data information on the data plane, etc.

[0173] 2) second indication information, used to indicate whether the first data packet is encoded by a lossy source or a lossless source;

[0174] Since source coding is for mobile network internal data rather than user plane data, appropriate source coding can be used for the first data packet based on the data application scenario and data quality requirements, without being limited to lossless source coding algorithms.

[0175] 3) third indication information, used to indicate whether the source encoding buffer is reset;

[0176] The third indication information indicates whether the source coding buffer of the first communication device is reset.

[0177] 4) A source coding algorithm or algorithm identifier used by the first data packet; the source coding algorithm may include at least one of the following: an algorithm predefined in the protocol, a pre-deployed algorithm.

[0178] 5) A check bit, used to verify the correctness of the source encoding and decoding of the first data packet. The verification object can be a single source-coded data packet. For example, the source encoding end generates a check bit (check bit) by applying a check algorithm (such as parity check) to the data before source encoding. After receiving the data packet, the receiving end performs source decoding and uses the same check algorithm to generate check bits for the decoded data. If the check bits are consistent with the check bits received from the encoding end, the source encoding and decoding is considered correct; otherwise, it is an error.

[0179] In this embodiment of the present application, the check bit is generated by the first communication device that sends the first data packet using a check algorithm on the pre-encoded data corresponding to the first data packet. At this point, the second communication device performs source decoding on the received first data packet, generates a check bit using the same check algorithm on the decoded data, and compares it with the received check bit. If the check bit matches the received check bit, the source encoding and decoding is considered correct; otherwise, it is considered an error.

[0180] 6) feedback information, used to indicate whether the source decoding of the source coded data received by the first communication device is correct;

[0181] When a decoding error or packet loss occurs at the receiving end of source-coded data, the error is reported via feedback information. The feedback information primarily provides source coding feedback, allowing the transmitting end of the source-coded data to determine whether source coding parameters need to be adjusted. Adjusting source coding parameters can include adjusting the used source coding parameters, such as the compression ratio, or changing the source coding algorithm. If each data packet can independently utilize source coding, and if decoding errors in a small number of data packets do not impact the use of the first data, retransmission or source coding parameter adjustment is unnecessary. If the transmitting end determines that decoding errors impact data use, one approach is to adjust the compression ratio upon receiving a source decoding error, thereby retaining more data. This process can utilize a unified source coding algorithm or modify the source coding algorithm, and also requires resetting the source coding buffer. The compression ratio can be defined as one of the following: the length of the data after source coding divided by the length of the data before source coding; the length of the data before source coding divided by the length of the data after source coding; or 1 - the length of the data after source coding / the length of the data before source coding.

[0182] When the first communication device receives source-encoded data, it can interpret the parity bit of the source-decoded data according to the protocol-defined parity algorithm and compare it with the received parity bit to determine whether the source decoding is correct. If it is incorrect and the sender needs to know, the aforementioned feedback information can be sent. If it is correct or the sender does not need to know whether the decoding is correct, feedback information can be omitted to reduce overhead. For example, if no feedback is provided, it is assumed that the decoding is correct.

[0183] 7) fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted;

[0184] 8) fifth indication information, used to indicate that the first data packet is a data packet for providing feedback on a decoding result of source coded data received by the first communication device;

[0185] 9) sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet use the same source coding mode;

[0186] 10) a first sequence number, the first sequence number being the sequence number of the first data packet;

[0187] 11) A second sequence number, where the second sequence number is the sequence number of the source coded data corresponding to the feedback information, and the feedback information is used to indicate whether the source decoding of the source coded data received by the first communication device is correct.

[0188] In an embodiment of the present application, optionally, the first data packet is a start data packet or an end data packet of source coding, and the method further includes: the second communication device receiving a second data packet, where the second data packet is a data packet between the start data packet and the end data packet of source coding, and the second data packet does not include at least one of the following:

[0189] Data type;

[0190] the first indication information;

[0191] the second indication information;

[0192] the third indication information;

[0193] a source coding algorithm or algorithm identifier used by the second data packet;

[0194] the fourth indication information;

[0195] The sixth indication information.

[0196] In an embodiment of the present application, optionally, the first data packet includes at least one of the following: a data packet corresponding to control information on the data plane, a data packet corresponding to data information on the data plane, and a data packet on the control plane.

[0197] In an embodiment of the present application, optionally, whether the first data packet is source encoded is related to the data type of the first data packet.

[0198] In an embodiment of the present application, optionally, the source coding method also includes: the second communication device sends a first message, the first message includes: seventh indication information, the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

[0199] In this embodiment of the present application, optionally, the seventh indication information is used to indicate at least one of the following:

[0200] whether to use source coding for the first uplink data;

[0201] Whether to use source coding for the first downlink data.

[0202] In this embodiment of the present application, optionally, the first message further includes at least one of the following:

[0203] eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data;

[0204] The size of the buffer used for source encoding;

[0205] A source coding algorithm or an algorithm identifier used for the first data.

[0206] In the embodiment of the present application, optionally, the source coding method further includes:

[0207] The second communication device receives source coding capability information of the first communication device, where the source coding capability information of the first communication device includes ninth indication information, where the ninth indication information is used to indicate whether the first communication device supports source coding;

[0208] The source coding capability information is used to determine the first message.

[0209] In an embodiment of the present application, optionally, the ninth indication information may indicate whether the first communication device supports source coding in an explicit manner, or may indicate whether the first communication device supports source coding in an implicit manner.

[0210] In an embodiment of the present application, when the first communication device is a UE, optionally, the source coding capability information of the first communication device may be carried in a UE capability report.

[0211] In this embodiment of the present application, optionally, the source coding capability information further includes at least one of the following:

[0212] The maximum number of entities supported using source coding; for example, the maximum number of radio bearers;

[0213] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0214] Supported source coding algorithms or algorithm identifiers. The supported source coding algorithms may include at least one of the following: a standard source coding algorithm (also called a dictionary), an operator-defined source coding algorithm (also called a dictionary). When the supported source coding algorithms include operator-defined source coding algorithms, the source coding capability information may also include the algorithm version and operator PLMN.

[0215] The standard source coding algorithm may include at least one of a lossy source coding algorithm and a lossless source coding algorithm. For examples of the lossy source coding algorithm and the lossless source coding algorithm, see the description of the embodiment shown in FIG4 .

[0216] In an embodiment of the present application, optionally, the source coding capability information is defined by a capability parameter of a data plane protocol layer or indicated by a general parameter in a capability parameter of the first communication device.

[0217] The source coding method of the embodiment of the present application is described below with reference to specific embodiments.

[0218] Example 1:

[0219] In this embodiment, a method of flexibly using source coding for each data packet is supported.

[0220] This embodiment describes a method for supporting source coding in the data plane protocol stack. The protocol layer corresponding to the data plane protocol stack is referred to as the first sublayer. See Figure 2 for a schematic diagram of the data plane protocol stack, which terminates in a wireless access network. In the following embodiments, the first sublayer is referred to as the Data Plane Application Protocol (DPAP), although other names, such as the Data Service Application Protocol (DSAP), may also be used.

[0221] Since the main purpose of the data plane is to transmit large amounts of data within the mobile network, this embodiment assumes that all nodes supporting the data plane (UE, wireless access network equipment, core network equipment) support source coding, that is, source coding is one of the functions carried by the data plane.

[0222] In this embodiment, the first communication device is a UE, and the UE sends a first data packet.

[0223] The source coding method in the embodiment of the present application includes the following steps:

[0224] First, the UE sends its capability information to the network device. This capability information includes the UE's source coding capability information. This step is optional. Assuming that the protocol defines that both the UE and the network support source coding, the UE does not need to report its source coding capability information.

[0225] The source coding capability information may include at least one of the following:

[0226] The maximum number of entities supported using source coding; for example, the maximum number of radio bearers;

[0227] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0228] Supported source coding algorithms or algorithm identifiers. The supported source coding algorithms may include at least one of the following: a standard source coding algorithm (also called a dictionary), an operator-defined source coding algorithm (also called a dictionary). When the supported source coding algorithms include operator-defined source coding algorithms, the source coding capability information may also include the algorithm version and operator PLMN.

[0229] The standard source coding algorithm may include at least one of a lossy source coding algorithm and a lossless source coding algorithm. Examples of the lossy source coding algorithm and the lossless source coding algorithm can be found in the description of the above embodiment and will not be described in detail.

[0230] Because this application performs source coding on data within the mobile network, operators can define source coding algorithms based on the application scenarios of the collected and transmitted data. Similar to the lossy source coding described above, which focuses on a specific type of data, operator-defined source coding algorithms are expected to further reduce data transmission volume. Considering that a UE may have multiple SIM cards from different operators, the operator-defined source coding algorithm must indicate the algorithm version information and the corresponding PLMN identifier.

[0231] The following is a brief description of the interaction process between the UE and the network side based on the source coding header:

[0232] Step 1: The network side sends a second message to the UE, where the second message is used to instruct the establishment of a data plane bearer.

[0233] The network side may be, for example, a radio access network device, and the second message may be, for example, RRC signaling.

[0234] An example of a second message based on RRC signaling is shown below.

[0235] Step 2: The UE receives the second message and, if a data plane bearer is added, sends a response message to the network side, for example, an RRCReconfigurationComplete message.

[0236] Step 3: For the data plane bearer, the UE uses the source coding header to generate a service data unit (SDU) (ie, the first data packet) of the DPAP layer.

[0237] Consider that at least one of the control information and data information of the data plane may be transmitted in the data plane bearer. Therefore, a source coding scheme is to determine whether each first data packet uses source coding based on data requirements. For example, for the control information of the data plane (such as data collection configuration), since it can be represented by fewer bits using methods such as ASN.1, source coding may not be used for the control information. For the data information of the data plane (such as collected data or AI models, etc.), source coding can be used to reduce the amount of data.

[0238] An example of a source coding header is shown in Figure 6. In this embodiment, one bit (coding) can be used to indicate whether the first data packet is source coded. If the control information does not use source coding and the data information does, then one bit can also be used to indicate whether the data packet is control information or data information, thereby indirectly indicating whether it is source coded.

[0239] Another example method is:

[0240] 1-bit D / C field, used to indicate whether the first data packet is control information or data information;

[0241] 1-bit compression indication field: whether the first data packet is source coded; if it is determined that the control plane does not perform source coding, the compression indication field is only used to indicate whether the data information is source coded.

[0242] If the source coding header includes a check bit, the receiving end can verify the source codec of the first data packet based on the check bit. The first communication device can determine the length of the check bit based on the adopted check algorithm, such as a parity check algorithm. Referring to FIG. 7 , the check bit in the source coding header in FIG. 7 is 1 bit (check bit).

[0243] Optionally, if the UE supports more than one source coding algorithm, the source coding header also needs to include the source coding algorithm information used by the first data packet. An example of a source coding header is shown in Figure 8. In this embodiment, when coding indicates that the first data packet is source coded, the source coding header carries the L / N field and the algorithm field (Algorithm). 1 bit (L / N) is used to indicate whether it is a lossy compression algorithm or a lossless compression algorithm, and 2 bits (Algorithm) are used to indicate whether the source coding algorithm is a protocol-defined algorithm or an operator-defined algorithm.

[0244] Optionally, the source coding header can also be used to indicate whether the source coding buffer is reset. If the sender (UE) of the source coded data also receives the source coded data from the other end, then optionally, it can provide feedback on whether the source decoding of the received data is correct while sending the source coded data. That is, the source coding header is also used to indicate whether the source decoding of the received source coded data is correct. An example is shown in the figure below, where 1 bit (BuffR) is used to indicate whether the source coding buffer is reset, and 1 bit (ACK / NACK) is used to indicate whether the source decoding of the received source coded data is correct.

[0245] In order to avoid problems caused by disorder, optionally, a DPAP layer sequence number (first sequence number) may be defined, such as the 6-bit DPAPSN field in FIG9 , where the DPAPSN is used to indicate the sequence number of the protocol data unit (first data packet).

[0246] Optionally, during the source encoding and decoding process, source coding parameter adjustments may be required due to changes in the correctness of the source encoding and decoding, changes in the accuracy requirements for the transmitted data, or changes in air interface resources. Source coding parameter adjustments may include adjusting the parameters of the source coding used, such as the compression ratio, or may also include changing the source coding algorithm. An example of feedback information in the source coding header is a 1-bit ACK / NACK indicating whether the source decoding of the received source coded data is correct. When a decoding error or packet loss occurs at the receiver of the source coded data (such as the UE or network), this bit is used to report the error. The ACK / NACK primarily provides source coding feedback, allowing the transmitter of the source coded data to determine whether source coding parameters need to be adjusted. If each data packet can independently use source coding, decoding errors in a small number of data packets may not be processed. If the transmitter determines that decoding errors impact data usage, one approach is to adjust the compression ratio when receiving a source decoding error, thereby retaining more data. This process can utilize a unified source coding algorithm or modify the source coding algorithm, and also requires resetting the source coding buffer. The definition of the compression rate may include one of the following: the data length after source encoding divided by the data length before source encoding, the data length before source encoding divided by the data length after source encoding, 1-the data length after source encoding / the data length before source encoding.

[0247] If, according to the ACK / NACK indication, when a source decoding error occurs, the decoded erroneous data needs to be retransmitted, then it is also necessary to indicate which data packet the ACK or NACK corresponds to, so that the data packet corresponding to the NACK can be retransmitted based on the original source coding algorithm or re-source encoded after changing the source coding parameters and then retransmitted. An example of a source coding header is as follows: Type is used to indicate that the current data packet is source coded data or feedback on the decoding result of the received source coded data. Please refer to Figure 10. When the Type indication is feedback on the decoding result of the received source coded data, in addition to ACK / NACK, the lower 5 bits of the data packet sequence number corresponding to the ACK / NACK can also be included (here 5 is only an example below, and can be other values). Note that the SN here is the sequence number of the data packet corresponding to the ACK / NACK, which is different from the DPAPSN used to indicate the sequence number of the first data packet mentioned above.

[0248] Step 4: The network side receives the DPAPSDU (first data packet) sent by the UE and processes it based on the source coding header to obtain data.

[0249] When the network sends the first data packet and the UE receives the first data packet, the source coding header described in step 3 may also be used. In this process, the network generates an SDU based on the source coding header, and the UE performs source decoding on the received data based on the source coding header.

[0250] It should be noted that the various steps in this embodiment can be combined with the embodiments corresponding to the above-mentioned source coding method.

[0251] Example 2:

[0252] The advantage of the method described in Example 1 is its flexibility, as it can determine for each data packet whether to be source coded and which source coding algorithm to use. Further considering the tradeoff between source coding header overhead and flexibility, Example 2 provides a source coding method that supports packet affinity.

[0253] Example 2 also assumes that all nodes on the data plane (UE, radio access network equipment, core network equipment) support source coding, that is, source coding is one of the functions carried by the data plane.

[0254] In this embodiment, the first communication device is a UE, and the UE sends a first data packet.

[0255] The source coding method in the embodiment of the present application includes the following steps:

[0256] First, the UE sends its capability information to the network device. This capability information includes the UE's source coding capability information. This step is optional. Assuming that the protocol defines that both the UE and the network support source coding, the UE does not need to report its source coding capability information.

[0257] The source coding capability information is described in Example 1 and will not be repeated here.

[0258] The following is a brief description of the interaction process between the UE and the network side based on the source coding header:

[0259] Step 1: The network side sends a second message to the UE, where the second message is used to instruct the establishment of a data plane bearer.

[0260] The network side may be, for example, a radio access network device, and the second message may be, for example, RRC signaling.

[0261] An example of a second message based on RRC signaling is shown below.

[0262] Step 2: The UE receives the second message and, if a data plane bearer is added, sends a response message to the network side, for example, an RRCReconfigurationComplete message.

[0263] Step 3: For the data plane bearer, the UE uses the source coding header to generate a service data unit (SDU) (first data packet or second data packet) of the DPAP layer.

[0264] Considering the large amount of data carried on the data plane, if source coding is used for data within a period of time, the same source coding method is usually used. Therefore, an example of a source coding header is shown in Figure 11: Type indicates whether the data packet is a source coding start or end type data packet. When Type indicates that the data packet is a source coding start or end type data packet, the 1-bit S / E indicates whether it is a start data packet or an end data packet. Assuming that the data packet is the start data packet with sequence number M, the UE will use the aforementioned source coding when sending the data packet with sequence number M+1. Similarly, assuming that the data packet is the end data packet with sequence number N, the UE will no longer use the aforementioned source coding when sending the data packet with sequence number N+1. Therefore, the data packets between the start data packet and the end data packet use the same source coding method, which is said to have packet affinity. In this way, the data packet with a sequence number between the start data packet and the end data packet (the second data packet) does not require a source coding header, thereby saving the overhead of the source coding header.

[0265] Optionally, for the first data packet that requires a source coding header, if the UE supports more than one source coding algorithm, the source coding header also needs to include information about the source coding algorithm used by the first data packet. An example of a source coding header is shown in Figure 11. In this embodiment, the source coding header carries an L / N field and an algorithm field (Algorithm). One bit (L / N) is used to indicate whether it is a lossy compression algorithm or a lossless compression algorithm, and two bits (Algorithm) are used to indicate whether the source coding algorithm is a protocol-defined algorithm or an operator-defined algorithm.

[0266] For another example, a source coding header can be used to indicate whether a packet is control information or data information. One type of control information indicates the start or end of a packet. Similarly, data information between the control start and end is source encoded and source decoded based on the previous control information indication. As shown in Figure 12, a 1-bit D / C field is used to indicate whether a packet is control information or data information. The control information indicates that the packet only includes source coding-related indication information, while the data information indicates whether the packet contains source-coded or non-source-coded data. When the packet is control information, a 2-bit Type field is used to indicate the packet type, such as feedback information, a start packet or end packet, or whether the source coding buffer is reset. When the Type field indicates whether the packet is a source-coded start or end packet, the 1-bit S / E field indicates whether it is a start packet or an end data packet. For example, if the S / E field is 0, it indicates the packet is a start packet (assuming the packet sequence number is M). Data packets following this packet (i.e., packets with sequence numbers M+1 and later) are source encoded and transmitted. When the bit is 1, it indicates the end of the data packet (assuming that the data packet sequence number SN is N), then the data packets after this data packet (that is, data packets with sequence numbers N+1 and later) will no longer use source coding.

[0267] The 2-bit Type field is used to indicate feedback information, whether it is a start data packet or an end data packet, and whether the source encoding buffer is reset.

[0268] Step 4: The network side receives the DPAPSDU sent by the UE and processes it based on whether the DPAPSDU has a source coding header to obtain data.

[0269] When the network sends the first data packet and the UE receives the first data packet, the source coding header described in step 3 may also be used. In this process, the network generates an SDU based on the source coding header, and the UE performs source decoding on the received data based on the source coding header.

[0270] It should be noted that the various steps in this embodiment can be combined with the embodiments corresponding to the above-mentioned source coding method.

[0271] Example 3: Source coding for joint signaling bearer or data plane bearer configuration

[0272] This embodiment is aimed at the case where at least one of the signaling bearer and the data plane bearer is configurable source coding, and then the source coding header is combined to perform flexible source coding for each data packet, or flexible source coding for each group of data packets in Example 2.

[0273] The source coding method in the embodiment of the present application includes the following steps:

[0274] First, the UE sends its capability information to the network device. This capability information includes the UE's source coding capability information. This step is optional. Assuming that the protocol defines that both the UE and the network support source coding, the UE does not need to report its source coding capability information.

[0275] The source coding capability information may include at least one of the following:

[0276] The maximum number of entities supported using source coding; for example, the maximum number of radio bearers;

[0277] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0278] Supported source coding algorithms or algorithm identifiers. The supported source coding algorithms may include at least one of the following: a standard source coding algorithm (also called a dictionary), an operator-defined source coding algorithm (also called a dictionary). When the supported source coding algorithms include operator-defined source coding algorithms, the source coding capability information may also include the algorithm version and operator PLMN.

[0279] The network side adds, modifies or releases radio bearers based on the UE capability information.

[0280] The following is a brief description of the source coding interaction process between the UE and the network:

[0281] Step 1: The network side sends a first message to the UE, where the first message includes: seventh indication information, where the seventh indication information is used to indicate whether source coding is used for first data, and the first data is internal data of the mobile network.

[0282] For the radio access network device, the first message may be determined according to the data requirement of the radio access network, or the first message corresponding to the data required by the core network may be determined according to the configuration information sent by the core network.

[0283] Optionally, the configuration information includes at least one of the following:

[0284] Terminal identification;

[0285] Terminal characteristics;

[0286] Indication information indicating whether the data to be transmitted uses source coding;

[0287] Indication information indicating that the data to be transmitted is applicable to at least one of lossy source coding and lossless source coding;

[0288] Data characteristics of the data to be transmitted;

[0289] Source type;

[0290] Data type.

[0291] An example of a first message is control signaling of a control plane, which is transmitted via a signaling radio bearer (SRB), and the control signaling is, for example, an RRC reconfiguration message. For example, in current mobile communication protocols, DRBs and SRBs can be added, released, or modified via this message. When a data plane is added, similarly, a data plane bearer can also be added, released, or modified via control plane signaling. The first message indicates whether a signaling bearer (SRB) or a data plane bearer uses source coding.

[0292] Optionally, the seventh indication information is used to indicate at least one of the following:

[0293] whether to use source coding for the first uplink data;

[0294] Whether to use source coding for the first downlink data.

[0295] Optionally, the first message further includes at least one of the following:

[0296] eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data;

[0297] Buffer size for source encoding;

[0298] A source coding algorithm or an algorithm identifier used for the first data.

[0299] Step 2: The UE receives the first message and sends a response message to the network if a data plane bearer is added, such as an RRCReconfigurationComplete message.

[0300] Step 3: The UE processes the data mapped to the bearer based on the information in the first message. Considering that some of the data in the bearer requires source coding and some does not, the UE performs at least one of sending and receiving data based on the source coding header.

[0301] For a data packet that requires source coding, an example source coding header includes first indication information, where the first indication information is used to indicate whether the data packet (first data packet) is source coded; optionally, the source coding header may further include at least one of the following:

[0302] Data type;

[0303] Second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source;

[0304] The third indication information is used to indicate whether the source encoding buffer is reset;

[0305] a source coding algorithm or algorithm identifier used by the first data packet;

[0306] A check bit, used to check the correctness of the source encoding and decoding of the first data packet;

[0307] Feedback information, used to indicate whether source decoding of the source coded data received by the first communication device is correct;

[0308] Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted;

[0309] fifth indication information, used to indicate that the first data packet is a data packet for providing feedback on a decoding result of source coded data received by the first communication device;

[0310] Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode;

[0311] a first sequence number, where the first sequence number is the sequence number of the first data packet;

[0312] A second sequence number, where the second sequence number is a sequence number of the source coded data corresponding to the feedback information, and the feedback information is used to indicate whether the source decoding of the source coded data received by the first communication device is correct.

[0313] Step 4: Optionally, if the source coding header includes a check bit, then when the UE sends the source-coded data, it is also necessary to generate a check bit according to the protocol-defined check algorithm. The UE can send the check bit and the source-coded data.

[0314] Similarly, when a UE receives source-coded data, it interprets the parity bit of the source-decoded data according to the protocol-defined parity check algorithm and compares it with the received parity bit to determine whether the source decoding is correct. If it is incorrect, and the transmitter needs to know the parity, the aforementioned feedback information is sent. If it is correct, or if the transmitter does not need to know the decoding is correct, feedback information can be omitted to reduce overhead. For example, if no feedback is provided, the decoding is considered correct.

[0315] It should be noted that the various steps in this embodiment can be combined with the embodiments corresponding to the above-mentioned source coding method.

[0316] The source coding method provided in the embodiment of the present application can be executed by a source coding device. In the embodiment of the present application, the source coding device performing the source coding method is taken as an example to illustrate the source coding device provided in the embodiment of the present application.

[0317] Referring to FIG. 13 , an embodiment of the present application further provides a source coding device 30, comprising:

[0318] A first sending module 31 is configured to send a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0319] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0320] Optionally, the source coding header further includes at least one of the following:

[0321] Data type;

[0322] Second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source;

[0323] The third indication information is used to indicate whether the source encoding buffer is reset;

[0324] a source coding algorithm or algorithm identifier used by the first data packet;

[0325] A check bit, used to check the correctness of the source encoding and decoding of the first data packet;

[0326] Feedback information, used to indicate whether source decoding of the source coded data received by the first communication device is correct;

[0327] Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted;

[0328] fifth indication information, used to indicate that the first data packet is a data packet for providing feedback on a decoding result of source coded data received by the first communication device;

[0329] Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode;

[0330] a first sequence number, where the first sequence number is the sequence number of the first data packet;

[0331] A second sequence number, where the second sequence number is a sequence number of the source coded data corresponding to the feedback information, and the feedback information is used to indicate whether the source decoding of the source coded data received by the first communication device is correct.

[0332] Optionally, the first data packet is a start data packet or an end data packet of source coding, and the source coding device 30 further includes:

[0333] The second sending module is configured to send a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source encoding, and the second data packet does not include at least one of the following:

[0334] Data type;

[0335] the first indication information;

[0336] the second indication information;

[0337] the third indication information;

[0338] a source coding algorithm or algorithm identifier used by the second data packet;

[0339] the fourth indication information;

[0340] The sixth indication information.

[0341] Optionally, the first data packet includes at least one of the following: a data packet corresponding to control information on the data plane, a data packet corresponding to data information on the data plane, and a data packet on the control plane.

[0342] Optionally, whether the first data packet is source encoded is related to the data type of the first data packet.

[0343] Optionally, the information source encoding device 30 further includes:

[0344] The determination module is used to determine whether to perform source coding on the data to be transmitted according to data requirements.

[0345] Optionally, the data requirement includes at least one of the following:

[0346] The length of the data to be transmitted;

[0347] Real-time data transmission;

[0348] Data type;

[0349] The amount of available storage resources.

[0350] Optionally, the information source encoding device 30 further includes:

[0351] The receiving module is used to receive a first message, wherein the first message includes: seventh indication information, wherein the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

[0352] Optionally, the seventh indication information is used to indicate at least one of the following:

[0353] whether to use source coding for the first uplink data;

[0354] Whether to use source coding for the first downlink data.

[0355] Optionally, the first message further includes at least one of the following:

[0356] eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data;

[0357] The size of the buffer used for source encoding;

[0358] A source coding algorithm or an algorithm identifier used for the first data.

[0359] Optionally, the information source encoding device 30 further includes:

[0360] a third sending module, configured to send source coding capability information of the first communication device, where the source coding capability information includes ninth indication information, and the ninth indication information is used to indicate whether the first communication device supports source coding;

[0361] The source coding capability information is used to determine the first message.

[0362] Optionally, the source coding capability information further includes at least one of the following:

[0363] The maximum number of entities supported using source encoding;

[0364] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0365] Supported source coding algorithms or algorithm identifiers.

[0366] Optionally, the source coding capability information is defined by capability parameters of a data plane protocol layer or indicated by general parameters in capability parameters of the first communication device.

[0367] The source coding device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0368] The source coding device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0369] Referring to FIG. 14 , an embodiment of the present application further provides a source coding device 40, comprising:

[0370] A first receiving module 41 is configured to receive a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0371] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0372] Optionally, the source coding header further includes at least one of the following:

[0373] Data type;

[0374] Second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source;

[0375] The third indication information is used to indicate whether the source encoding buffer is reset;

[0376] a source coding algorithm or algorithm identifier used by the first data packet;

[0377] A check bit, used to check the correctness of the source encoding and decoding of the first data packet;

[0378] Feedback information, used to indicate whether source decoding of the source coded data received by the first communication device is correct;

[0379] Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted;

[0380] fifth indication information, used to indicate that the first data packet is a data packet for providing feedback on a decoding result of source coded data received by the first communication device;

[0381] Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode;

[0382] a first sequence number, where the first sequence number is the sequence number of the first data packet;

[0383] A second sequence number, where the second sequence number is a sequence number of the source coded data corresponding to the feedback information, and the feedback information is used to indicate whether the source decoding of the source coded data received by the first communication device is correct.

[0384] Optionally, the first data packet is a start data packet or an end data packet of source coding, and the source coding device 40 further includes:

[0385] The second receiving module is configured to receive a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source encoding, and the second data packet does not include at least one of the following:

[0386] Data type;

[0387] the first indication information;

[0388] the second indication information;

[0389] the third indication information;

[0390] a source coding algorithm or algorithm identifier used by the second data packet;

[0391] the fourth indication information;

[0392] The sixth indication information.

[0393] Optionally, the first data packet includes at least one of the following: a data packet corresponding to control information on the data plane, a data packet corresponding to data information on the data plane, and a data packet on the control plane.

[0394] Optionally, whether the first data packet is source encoded is related to the data type of the first data packet.

[0395] Optionally, the information source encoding device 40 further includes:

[0396] The sending module is used to send a first message, wherein the first message includes: seventh indication information, wherein the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

[0397] Optionally, the seventh indication information is used to indicate at least one of the following:

[0398] whether to use source coding for the first uplink data;

[0399] Whether to use source coding for the first downlink data.

[0400] Optionally, the first message further includes at least one of the following:

[0401] eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data;

[0402] The size of the buffer used for source encoding;

[0403] A source coding algorithm or an algorithm identifier used for the first data.

[0404] Optionally, the information source encoding device 40 further includes:

[0405] a third receiving module, configured to receive source coding capability information of a second communication device, where the source coding capability information of the second communication device includes ninth indication information, where the ninth indication information is used to indicate whether the second communication device supports source coding;

[0406] A determination module is used to determine the first message according to the source coding capability information of the first communication device.

[0407] Optionally, the source coding capability information further includes at least one of the following:

[0408] The maximum number of entities supported using source encoding;

[0409] Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding;

[0410] Supported source coding algorithms or algorithm identifiers.

[0411] Optionally, the source coding capability information is defined by capability parameters of a data plane protocol layer or indicated by general parameters in capability parameters of the first communication device.

[0412] The source coding device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0413] The source coding device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0414] As shown in Figure 15, an embodiment of the present application also provides a communication device 50, including a processor 51 and a memory 52, and the memory 52 stores a program or instruction that can be run on the processor 51. When the program or instruction is executed by the processor 51, the various steps of the source coding method embodiment executed by the above-mentioned first communication device or the second communication device are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0415] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figures 4 or 5. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 16 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0416] The terminal 60 includes but is not limited to: a radio frequency unit 61, a network module 62, an audio output unit 63, an input unit 64, a sensor 65, a display unit 66, a user input unit 67, an interface unit 68, a memory 69 and at least some of the components of the processor 610.

[0417] Those skilled in the art will appreciate that the terminal 60 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 610 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in Figure 616 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0418] It should be understood that in an embodiment of the present application, the input unit 64 may include a graphics processing unit (GPU) 661 and a microphone 662, and the graphics processor 661 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 66 may include a display panel 661, and the display panel 661 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 67 includes a touch panel 671 and at least one of other input devices 672. The touch panel 671 is also called a touch screen. The touch panel 671 may include two parts: a touch detection device and a touch controller. Other input devices 672 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0419] In the embodiment of the present application, after receiving downlink data from the network-side device, the RF unit 61 can transmit the data to the processor 610 for processing. In addition, the RF unit 61 can send uplink data to the network-side device. Generally, the RF unit 61 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0420] The memory 69 can be used to store software programs or instructions and various data. The memory 69 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 69 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 69 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0421] Processor 610 may include one or more processing units. Optionally, processor 610 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 610.

[0422] The radio frequency unit 61 is configured to send a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, and where the first indication information is configured to indicate whether the first data packet is source coded.

[0423] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0424] In an embodiment of the present application, a source coding header is set in the header of a data packet of internal data in a mobile network, and the source coding header includes first indication information for indicating whether the data packet is source encoded, thereby supporting the flexible use of source coding for each data packet, while improving data transmission efficiency and increasing the flexibility of source coding.

[0425] Alternatively, the radio frequency unit 61 is configured to receive a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded;

[0426] Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, wireless access network equipment and core network equipment, and sending or receiving data terminated at any one of the terminal, wireless access network equipment or core network equipment.

[0427] In an embodiment of the present application, a source coding header is set in the header of a data packet of internal data in a mobile network, and the source coding header includes first indication information for indicating whether the data packet is source encoded, thereby supporting the flexible use of source coding for each data packet, while improving data transmission efficiency and increasing the flexibility of source coding.

[0428] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 4 or Figure 5, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0429] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 4 or Figure 5. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0430] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 17, the network-side device 70 includes an antenna 71, a radio frequency device 72, a baseband device 73, a processor 74, and a memory 75. Antenna 71 is connected to radio frequency device 72. In the uplink direction, radio frequency device 72 receives information via antenna 71 and sends the received information to baseband device 73 for processing. In the downlink direction, baseband device 73 processes the information to be transmitted and sends it to radio frequency device 72. Radio frequency device 72 processes the received information and then sends it through antenna 71.

[0431] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 73 , which includes a baseband processor.

[0432] The baseband device 73 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 717, one of which is, for example, a baseband processor, which is connected to the memory 75 through a bus interface to call the program in the memory 75 and execute the network device operations shown in the above method embodiment.

[0433] The network side device may further include a network interface 76, which is, for example, a Common Public Radio Interface (CPRI).

[0434] Specifically, the network side device 70 of the embodiment of the present application also includes: instructions or programs stored in the memory 75 and executable on the processor 74. The processor 74 calls the instructions or programs in the memory 75 to execute the methods executed by the modules shown in FIG13 or FIG14 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0435] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG18 , the network-side device 80 includes a processor 81, a network interface 82, and a memory 83. The network interface 82 is, for example, a common public radio interface (CPRI).

[0436] Specifically, the network side device 80 of the embodiment of the present application also includes: instructions or programs stored in the memory 83 and executable on the processor 81. The processor 81 calls the instructions or programs in the memory 83 to execute the methods executed by the modules shown in FIG13 or FIG14 and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0437] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned source coding method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0438] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0439] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned source coding method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0440] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0441] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned source coding method embodiment and can achieve the same technical effects. To avoid repetition, they are not described here.

[0442] An embodiment of the present application further provides a wireless communication system, including: a first communication device and a second communication device, wherein the first communication device can be used to execute the steps of the source coding method as performed by the first communication device as described above, and the second communication device can be used to execute the steps of the source coding method as performed by the second communication device as described above.

[0443] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0444] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0445] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A source coding method, wherein: include: A first communication device sends a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded; Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, the wireless access network device and the core network device, and sending or receiving data terminated at any one of the terminal, the wireless access network device or the core network device.

2. The method according to claim 1, wherein: The source coding header further includes at least one of the following: Data type; second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source; The third indication information is used to indicate whether the source encoding buffer is reset; A source coding algorithm or algorithm identifier used by the first data packet; A check bit, used to check the correctness of the source encoding and decoding of the first data packet; Feedback information, used to indicate whether source decoding of source coded data received by the first communication device is correct; Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted; fifth indication information, used to indicate that the first data packet is a data packet for feeding back a decoding result of source coded data received by the first communication device; Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode; A first sequence number, where the first sequence number is a sequence number of the first data packet; A second sequence number, where the second sequence number is a sequence number of source coded data corresponding to feedback information, and the feedback information is used to indicate whether source decoding of the source coded data received by the first communication device is correct.

3. The method according to claim 2, wherein: The first data packet is a start data packet or an end data packet of source coding, and the method further includes: The first communication device sends a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source coding, and the second data packet does not include at least one of the following: Data type; the first indication information; the second indication information; the third indication information; A source coding algorithm or an algorithm identifier used by the second data packet; the fourth indication information; The sixth indication information.

4. The method according to claim 1, wherein: The first data packet includes at least one of the following: a data packet corresponding to the control information of the data plane, a data packet corresponding to the data information of the data plane, and a data packet of the control plane.

5. The method according to claim 1 or 4, wherein: Whether the first data packet is source encoded is related to the data type of the first data packet.

6. The method according to claim 1 or 4, wherein: Also includes: The first communication device determines whether to perform source coding on the data to be transmitted according to data requirements.

7. The method according to claim 6, wherein: The data requirement includes at least one of the following: The length of the data to be transmitted; Real-time data transmission; Data type; The amount of available storage resources.

8. The method according to claim 1, wherein: Also includes: The first communication device receives a first message, the first message includes: seventh indication information, the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

9. The method according to claim 8, wherein: The seventh indication information is used to indicate at least one of the following: whether to use source coding for the first uplink data; Whether to use source coding for the first downlink data.

10. The method according to claim 8 or 9, wherein: The first message also includes at least one of the following: eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data; The buffer size used for source encoding; A source coding algorithm or an algorithm identifier used for the first data.

11. The method according to claim 8, wherein: Also includes: The first communication device sends source coding capability information of the first communication device, the source coding capability information includes ninth indication information, and the ninth indication information is used to indicate whether the first communication device supports source coding; wherein the source coding capability information is used to determine the first message.

12. The method according to claim 11, wherein: The source coding capability information also includes at least one of the following: The maximum number of entities supported using source encoding; Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding; Supported source coding algorithms or algorithm identifiers.

13. The method according to claim 11 or 12, wherein: The source coding capability information is defined by capability parameters of a data plane protocol layer or indicated by common parameters in capability parameters of the first communication device.

14. A source coding method, wherein: include: A second communication device receives a first data packet, where the first data packet includes a source coding header, where the source coding header includes first indication information, where the first indication information is used to indicate whether the first data packet is source coded; Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, the wireless access network device and the core network device, and sending or receiving data terminated at any one of the terminal, the wireless access network device or the core network device.

15. The method according to claim 14, wherein: The source coding header further includes at least one of the following: Data type; second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source; The third indication information is used to indicate whether the source encoding buffer is reset; A source coding algorithm or algorithm identifier used by the first data packet; A check bit, used to check the correctness of the source encoding and decoding of the first data packet; Feedback information, used to indicate whether source decoding of source coded data received by the first communication device is correct; Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted; fifth indication information, used to indicate that the first data packet is a data packet for feeding back a decoding result of source coded data received by the first communication device; Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode; A first sequence number, where the first sequence number is a sequence number of the first data packet; A second sequence number, where the second sequence number is a sequence number of source coded data corresponding to feedback information, and the feedback information is used to indicate whether source decoding of the source coded data received by the first communication device is correct.

16. The method according to claim 15, wherein: The first data packet is a start data packet or an end data packet of source coding, and the method further includes: The second communication device receives a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source coding, and the second data packet does not include at least one of the following: Data type; the first indication information; the second indication information; the third indication information; A source coding algorithm or an algorithm identifier used by the second data packet; the fourth indication information; The sixth indication information.

17. The method according to claim 14, wherein: The first data packet includes at least one of the following: a data packet corresponding to the control information of the data plane, a data packet corresponding to the data information of the data plane, and a data packet of the control plane.

18. The method according to claim 14 or 17, wherein: Whether the first data packet is source encoded is related to the data type of the first data packet.

19. The method according to claim 14, wherein: Also includes: The second communication device sends a first message, the first message includes: seventh indication information, the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of the mobile network, and the first data packet belongs to the first data.

20. The method according to claim 19, wherein: The seventh indication information is used to indicate at least one of the following: whether to use source coding for the first uplink data; Whether to use source coding for the first downlink data.

21. The method according to claim 19 or 20, wherein: The first message also includes at least one of the following: eighth indication information, used to indicate whether lossy source coding or lossless source coding is used for the first data; The buffer size used for source encoding; A source coding algorithm or an algorithm identifier used for the first data.

22. The method according to claim 19, wherein: Also includes: The second communication device receives source coding capability information of the first communication device, where the source coding capability information of the first communication device includes ninth indication information, and the ninth indication information is used to indicate whether the first communication device supports source coding; The second communication device determines the first message according to the source coding capability information of the first communication device.

23. The method according to claim 22, wherein: The source coding capability information also includes at least one of the following: The maximum number of entities supported using source encoding; Tenth indication information, used to indicate support for at least one of lossy source coding and lossless source coding; Supported source coding algorithms or algorithm identifiers.

24. The method according to claim 22 or 23, wherein: The source coding capability information is defined by capability parameters of a data plane protocol layer or indicated by common parameters in capability parameters of the first communication device.

25. A source coding device, wherein: include: A first sending module, configured to send a first data packet, wherein the first data packet includes a source coding header, the source coding header includes first indication information, and the first indication information is used to indicate whether the first data packet is source coded; Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, the wireless access network device and the core network device, and sending or receiving data terminated at any one of the terminal, the wireless access network device or the core network device.

26. The device according to claim 25, wherein The source coding header further includes at least one of the following: Data type; second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source; The third indication information is used to indicate whether the source encoding buffer is reset; A source coding algorithm or algorithm identifier used by the first data packet; A check bit, used to check the correctness of the source encoding and decoding of the first data packet; Feedback information, used to indicate whether source decoding of source coded data received by the first communication device is correct; Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted; fifth indication information, used to indicate that the first data packet is a data packet for feeding back a decoding result of source coded data received by the first communication device; Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode; A first sequence number, where the first sequence number is a sequence number of the first data packet; A second sequence number, where the second sequence number is a sequence number of source coded data corresponding to feedback information, and the feedback information is used to indicate whether source decoding of the source coded data received by the first communication device is correct.

27. The device according to claim 26, wherein: The first data packet is a start data packet or an end data packet of source coding, and the source coding device further includes: The second sending module is used to send a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source coding, and the second data packet does not include at least one of the following: Data type; the first indication information; the second indication information; the third indication information; A source coding algorithm or an algorithm identifier used by the second data packet; the fourth indication information; The sixth indication information.

28. The device according to claim 26, wherein Also includes: The determination module is used to determine whether to perform source coding on the data to be transmitted according to data requirements.

29. The device according to claim 26, wherein: Also includes: The third transmission module is used to receive a first message, where the first message includes: seventh indication information, where the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of a mobile network, and the first data packet belongs to the first data.

30. The device according to claim 29, wherein: Also includes: A sending module, configured to send source coding capability information of a first communication device, wherein the source coding capability information includes ninth indication information, and the ninth indication information is used to indicate whether the first communication device supports source coding; The source coding capability information is used to determine the first message.

31. A source coding device, wherein: include: A first receiving module, configured to receive a first data packet, wherein the first data packet includes a source coding header, wherein the source coding header includes first indication information, and the first indication information is used to indicate whether the first data packet is source coded; Among them, the first data packet is internal data of the mobile network, and the internal data of the mobile network includes at least one of the following: sending and receiving data terminated at any two of the terminal, the wireless access network device and the core network device, and sending or receiving data terminated at any one of the terminal, the wireless access network device or the core network device.

32. The device according to claim 31, wherein The source coding header further includes at least one of the following: Data type; second indication information, used to indicate whether the first data packet is encoded by a lossy source or by a lossless source; The third indication information is used to indicate whether the source encoding buffer is reset; A source coding algorithm or algorithm identifier used by the first data packet; A check bit, used to check the correctness of the source encoding and decoding of the first data packet; Feedback information, used to indicate whether source decoding of source coded data received by the first communication device is correct; Fourth indication information, used to indicate that the first data packet is source-encoded data to be transmitted; fifth indication information, used to indicate that the first data packet is a data packet for feeding back a decoding result of source coded data received by the first communication device; Sixth indication information, used to indicate that the first data packet is a start data packet or an end data packet of source coding, wherein the data packets between the start data packet and the end data packet adopt the same source coding mode; A first sequence number, where the first sequence number is a sequence number of the first data packet; A second sequence number, where the second sequence number is a sequence number of source coded data corresponding to feedback information, and the feedback information is used to indicate whether source decoding of the source coded data received by the first communication device is correct.

33. The device according to claim 32, wherein: The first data packet is a start data packet or an end data packet of source coding, and the device further includes: The second receiving module is configured to receive a second data packet, where the second data packet is a data packet between a start data packet and an end data packet of the source coding, and the second data packet does not include at least one of the following: Data type; the first indication information; the second indication information; the third indication information; A source coding algorithm or an algorithm identifier used by the second data packet; the fourth indication information; The sixth indication information.

34. The device according to claim 31, wherein Also includes: The sending module is used to send a first message, wherein the first message includes: seventh indication information, wherein the seventh indication information is used to indicate whether the first data uses source coding, the first data is internal data of a mobile network, and the first data packet belongs to the first data.

35. The device according to claim 34, wherein Also includes: A third receiving module, configured to receive source coding capability information of a first communication device, where the source coding capability information of the first communication device includes ninth indication information, where the ninth indication information is used to indicate whether the first communication device supports source coding; A determination module is used to determine the first message according to the source coding capability information of the first communication device.

36. A communication device, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the source coding method according to any one of claims 1 to 13 are implemented, or when the program or instruction is executed by the processor, the steps of the source coding method according to any one of claims 14 to 24 are implemented.

37. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the source coding method as described in any one of claims 1 to 13, or when the program or instruction is executed by the processor, it implements the source coding method as described in any one of claims 14 to 24.

Images