Communication method and apparatus

Abstract

The application provides a communication method and device. The method comprises: a first core network element receiving a first data packet. For example, the first data packet can be a data packet allowing error transmission. The first information is sent to an access network device. For example, the first information can be used to instruct the access network device to use a first transmission mechanism to transmit the first data packet. The application sends the first information to the access network device to instruct the access network device to use the first transmission mechanism to transmit the data packet allowing error transmission. So that the access network device can identify the data packet allowing error transmission through the first information and perform subsequent operations on such data packet. It can avoid retransmission of the data packet allowing error transmission, and improve communication efficiency.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more particularly to communication methods and apparatus. Background Technology

[0002] Currently, Internet Protocol (IP) packets can include data packets arriving at access network devices from User Plane Function (UPF) entities. During processing at each protocol layer, the access network device can add a header for that layer and pass the packaged data packet to the next protocol layer for processing, until it reaches the Medium Access Control (MAC) layer. If a data packet at the MAC layer fails verification, it indicates a transmission error. One solution is to use a Hybrid Automatic Repeat Request (HARQ) mechanism to retransmit the data packet, ensuring the receiving device receives the correct packet. Of course, before receiving the correct packet, the receiving device can stop passing erroneous packets to higher protocol layers until it receives the correct packet, i.e., the packet verification passes. Only then does the receiving device perform subsequent operations.

[0003] However, for some services, there may be different data streams, each corresponding to one or more data packets. For example, if data packets in data stream A are lost or corrupted, the original data may not be recoverable. While data packets in another data stream, B, may also have lost or corrupted packets, the original data can still be roughly recovered. For instance, if the data stream is a media stream, then if data packets in data stream A are lost or corrupted, the video cannot be recovered; however, if data packets in data stream B are lost or corrupted, it will not affect video recovery.

[0004] However, currently, access network devices and terminals still need to retransmit each data packet during data transmission, resulting in low communication efficiency. Summary of the Invention

[0005] This application provides a communication method and apparatus that sends first information to an access network device to instruct the access network device to transmit data packets that are allowed to be transmitted erroneously using a first transmission mechanism. This allows the access network device to identify data packets that are allowed to be transmitted erroneously using the first information and to perform subsequent operations on such data packets. This avoids retransmission of data packets that are allowed to be transmitted erroneously, thus improving communication efficiency.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a communication method is provided, applied to a first core network element. This first core network element can be a component (e.g., a processor, circuit, chip, or chip system) applied to a core network element, or a logic module or software capable of implementing all or part of the functions of the first core network element. The first core network element can be a user plane function (UPF) entity. The method includes: receiving a first data packet. For example, the first data packet can be a data packet that allows error transmission. Sending first information to an access network device. For example, the first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism.

[0008] This application sends a first message to the access network device, instructing the access network device to transmit data packets that are allowed to be transmitted erroneously using a first transmission mechanism. This allows the access network device to identify data packets that are allowed to be transmitted erroneously through the first message and to perform subsequent operations on such data packets. This avoids retransmission of data packets that are allowed to be transmitted erroneously, thus improving communication efficiency.

[0009] In one possible design, the first information indicates that the access network device uses a first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that allows error transmission. In this application, the first data packet can be a data packet that allows error transmission. This first data packet can also be referred to as an error-tolerant data packet, a data packet that allows transmission errors, an error-allowed data packet, a data packet that allows error delivery, a data packet with low reliability requirements, etc. This application does not limit the specific name of the first data packet.

[0010] In other words, if the first data packet contains (or carries) some or all of the data that can be used or parsed even if errors occur (such as errors during transmission), then this type of data can be called data that allows error transmission, error-tolerant data, data that allows transmission errors, data that allows errors, data that allows error delivery, data with low reliability requirements, etc.

[0011] Accordingly, the data stream corresponding to the first data packet can also be considered to allow for error transmission. It is understood that an error can mean that the data packet's checksum (or verification check) fails (e.g., the receiver determines the checksum (or verification check) failed). Alternatively, the data packet's integrity protection fails (e.g., the receiver determines the integrity protection failed). Or, the data packet may experience errors, inversions, and / or loss of all or some bits during transmission. Here, the transmission process can refer to transmission between the terminal and the access network equipment, or transmission between the terminal and the server. The aforementioned receiver can be understood as the device that receives the data packet, such as a terminal in downlink communication.

[0012] In this application, the data packet that is allowed to be transmitted with errors can also be described as "error packet delivery", or it can be replaced with any equivalent description such as error packet transmission, allowing error transmission, allowing transmission errors, allowing data packet error transmission, insensitive to transmission errors, low importance, low accuracy, error tolerance, error packet recovery, etc. The embodiments of this application are not limited here.

[0013] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the medium access control (MAC) layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the radio link control (RLC) layer) in the event of a data packet transmission error. For example, the first transmission mechanism allows the terminal's MAC layer to submit a failed TB and / or MAC SDU to the RLC layer if the transport block (TB) and / or MAC service data unit (SDU) verification fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., hybrid automatic repeat-request (HARQ) retransmissions). Furthermore, the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0014] In one possible design, the first information may be included in the header of the first data packet. For example, the first information may be included in any protocol header used for user plane transmission, such as the General Packet Radioservice Tunneling Protocol User Plane (GTP-U) header, the Segment Routing Over Internet Protocol Version 6 (SRv6) header, or the Quick User Datagram Protocol Internet Connection (QUIC) header. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0015] This application provides a method for carrying first information in the header of a first data packet, thereby accurately indicating that the first data packet is a data packet that is allowed to be transmitted with errors.

[0016] In one possible design, the first information includes at least one of the following: second information corresponding to the first data packet; or, Quality of Service (QoS) flow identification information. For example, the second information can be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. For example, the second information can be an indication, such as a single bit. It can also be understood that the second information is used to indicate that the first data packet is a packet that allows error transmission. In some examples, each data packet can correspond to a single piece of second information. For example, QoS flow identification information can be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device can use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device can determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0017] This application provides multiple implementations of the first information so that the first information can be indicated in a way that is appropriate for the communication scenario in different communication scenarios, thereby improving universality.

[0018] In one possible design, the method may further include: determining whether the first data packet is a data packet that allows error transmission based on the characteristic information of the first data packet. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet that allows error transmission through this characteristic information. Alternatively, it can be considered that this characteristic information can be used to identify such data packets that allow error transmission.

[0019] This application can accurately distinguish between data packets that are allowed to be transmitted incorrectly and other data packets by using the characteristic information of the data packets. This allows for the indication of such data packets that are allowed to be transmitted incorrectly using first information, thereby improving communication efficiency.

[0020] In one possible design, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined based on artificial intelligence (AI) reasoning. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0021] This application provides various forms of feature information, thereby enabling the determination of feature information in different communication scenarios using a method suitable for that specific scenario. This allows for the subsequent determination of the first data packet based on the feature information.

[0022] In one possible design, when the characteristic information is included in the header of the first data packet, determining whether the first data packet is a data packet allowed to be transmitted with errors based on the characteristic information of the first data packet may include: determining whether the first data packet is a data packet allowed to be transmitted with errors based on the information in the protocol layer header of the first data packet and / or the protocol type of the first data packet. For example, the first core network element may determine whether the data packet is a data packet allowed to be transmitted with errors based on a single bit in the protocol layer header. For example, the information in the protocol layer header may be information from one or more protocol headers, such as the Real-Time Transport Protocol (RTP) header, the QUIC header, and the Transmission Control Protocol (TCP) header.

[0023] This application provides multiple implementations for determining a first data packet as a data packet that is allowed to be transmitted with errors, when the characteristic information is located in the header of the first data packet. This allows for the identification of the first data packet using a method suitable for that specific communication scenario, thereby improving system versatility.

[0024] In one possible design, at least one of the following information can be determined based on the information in the protocol layer header: Internet Protocol (IP) 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. The first core network element can determine that the data packet is a data packet that is allowed to transmit with errors based on certain characteristics of the above sequence number information (e.g., belonging to a certain range). Of course, the same applies to the location information of other protocols or other protocols, which will not be elaborated further in this application. It is understood that the specific position values ​​of the above bits are only exemplary descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., which are not limited in this application.

[0025] For example, the first core network element (such as the UPF element) can configure the mapping relationship between IP 5-tuples or IP ternaries and service identifiers / application identifiers locally or obtain them from other network elements. Then, the first core network element (such as the UPF element) can determine the service identifier / application identifier based on the IP 5-tuples or IP ternaries in the packet header of the data packet protocol layer.

[0026] For example, the first core network element (such as the UPF element) can configure the mapping between server domain names and server IPs locally or obtain them from other network elements. Therefore, the first core network element (such as the UPF element) can determine the corresponding server domain name based on the server IP in the packet header of the data packet protocol layer.

[0027] For example, a first core network element (such as a UPF element) can configure the mapping between terminal address information and sessions (such as session identifiers) locally or obtain it from other network elements. Then, the first core network element (such as a UPF element) can determine the corresponding session identifier based on the terminal address information in the packet header of the data packet protocol layer.

[0028] For example, the first core network element (such as the UPF element) can determine the QoS channel (such as QoS flow) corresponding to the data packet based on the configured rules for processing user plane data packets (such as the N4 rule).

[0029] This application provides multiple representations of feature information in the protocol layer header, so that feature information can be determined in different communication scenarios using a method suitable for that communication scenario, thereby accurately identifying the first data packet based on the feature information and improving communication efficiency.

[0030] In one possible design, feature information is determined based on AI inference. The method may further include using any one or more of the following: the data packet itself, data packet attribute information, and information in the protocol layer header as input parameters (or inference input parameters, etc.) to the AI ​​model. The AI ​​model then infers the inference result (or inference output parameters, etc.) from the above input parameters. This inference result can indicate whether the data packet is a data packet that allows erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. When the AI ​​model is deployed on other devices, the first core network element can interact with the aforementioned input and output parameters. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model may also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a data packet that allows erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0031] In one possible design, the method may further include receiving third information from a second core network element. This third information can be used to instruct the first core network element to send first information to the access network device upon receiving a first data packet (i.e., a data packet that allows erroneous transmission).

[0032] This application enables the second core network element to flexibly instruct the first core network element to send the first information to the access network device through the third information.

[0033] In one possible design, the third information may include the characteristic information of the first data packet. Alternatively, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0034] This application allows the second core network element to inform the first core network element of the characteristic information of the first data packet, so that the first core network element can accurately identify the first data packet based on the characteristic information, thereby improving communication efficiency.

[0035] Secondly, a communication method is provided, which is applied to a second core network element. This second core network element can also be a component (e.g., a processor, circuit, chip, or chip system) applied to a core network element, or a logic module or software capable of implementing all or part of the functions of the second core network element. For example, the second core network element can be a session management function (SMF) entity. The method includes: receiving policy information from a third core network element. This policy information can be used to indicate that a first service includes a first data packet. And / or, the policy information can be used to indicate that a first session transmits a first data packet. The first data packet is a data packet that allows erroneous transmission. Sending third information to a first core network element. This third information can be used to instruct the first core network element, upon receiving the first data packet, to send first information to an access network device. This first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism. For example, the third core network element can be a policy control function (PCF) entity.

[0036] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0037] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0038] In one possible design, policy information and / or third information can be used to indicate the characteristic information of the first data packet. This characteristic information of the first data packet can be used by the first core network element to determine data packets that are allowed to be transmitted erroneously. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet that is allowed to be transmitted erroneously. Alternatively, it can be considered that the characteristic information can be used to identify such data packets that are allowed to be transmitted erroneously. In other examples, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0039] In one possible design scheme, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined by the first core network element based on AI inference. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0040] In one possible design, when the feature information is included in the header of the first data packet, the feature information is related to at least one of the following: information contained in the protocol layer header; or, the protocol type of the data packet. For example, the feature information could be a bit in the protocol layer header. For example, the information in the protocol layer header could be information from one or more protocol headers, such as the RTP header, the QUIC header, and the TCP header.

[0041] In one possible design, at least one of the following information can be determined based on information in the protocol layer header: IP 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as a QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. Certain characteristics of the aforementioned sequence number information (e.g., belonging to a certain range) can be used to determine that the data packet is a packet allowed to transmit with errors. Of course, the same applies to location information for other protocols or other protocols, and this application will not elaborate further. It is understood that the specific position values ​​of the aforementioned bits are merely illustrative descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., and this application does not limit it.

[0042] In one possible design, when the feature information is determined by the first core network element based on AI inference, any one or more of the following—the data packet itself, the data packet attribute information, and the information in the protocol layer header—can be used as input parameters (or inference input parameters, etc.) for the AI ​​model. The AI ​​model then infers the results from these input parameters (or inference output parameters, etc.). This inference result indicates whether the data packet is a permissible data packet for erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a permissible data packet for erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0043] In one possible design, the method may further include sending fourth information to the access network device. This fourth information may be used to instruct the access network device to enable a first transmission mechanism for the first QoS flow or the first session.

[0044] This application can also flexibly instruct access network devices to enable the first transmission mechanism through fourth information, thereby improving the flexibility of communication system configuration.

[0045] In one possible design, the method may further include sending fifth information to the terminal. This fifth information may be used to instruct the terminal to enable a first transmission mechanism for the first QoS stream or the first session.

[0046] This application can also flexibly instruct the terminal to activate the first transmission mechanism through the fifth information, thereby improving the flexibility of communication system configuration.

[0047] In one possible design, the policy information can be determined by a third core network element based on sixth information. This sixth information can be used to indicate which services or terminals are permitted to execute the first transmission mechanism.

[0048] The third core network element in this application can obtain policy information through the sixth information, thereby enabling it to instruct the second core network element to send third information to the first core network element based on the policy information. This triggers the first core network element to send first information to the access network device upon receiving the first data packet. Furthermore, it instructs the access network device to use the first transmission mechanism to transmit the first data packet, thereby improving communication efficiency.

[0049] In one possible design, the sixth information may include the characteristic information of the first data packet. Alternatively, the sixth information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0050] The sixth piece of information in this application may include the characteristic information of the first data packet, so that the third core network element can determine policy information based on the characteristic information. Optionally, the characteristic information of the first data packet may also be carried in the policy information, so that the first core network element and the access network element can subsequently obtain the characteristic information of the first data packet to identify the first data packet.

[0051] Thirdly, a communication method is provided, which is applied to an access network device. This access network device can also be a component applied to an access network (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the access network device. The method includes: receiving first information from a first core network element. This first information can be used to instruct the access network device to transmit a first data packet using a first transmission mechanism. For example, the first data packet is a data packet that allows error transmission. The first transmission mechanism is then used to send the first data packet to a terminal.

[0052] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0053] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0054] In one possible design, the method may further include: receiving a first data packet from a first core network element.

[0055] In one possible design, the first information can be included in the header of the first data packet. For example, the first information can be included in any protocol header used for user plane transmission, such as the GTP-U header, SRv6 header, or QUIC header of the first data packet. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0056] In one possible design, the first information may include at least one of the following: second information corresponding to any first data packet; or QoS flow identification information. For example, the second information may be used to instruct the access network device to use the first transmission mechanism to transmit the first data packet. For example, the second information may be an indication, such as a single bit. It can also be understood that the second information is used to indicate that the first data packet is a data packet that is allowed to be transmitted incorrectly. In some examples, each data packet may correspond to a single piece of second information. For example, QoS flow identification information may be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device may use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device may determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0057] Fourthly, a communication device is provided, which is a first core network element, a communication module implementing the corresponding function of the first core network element, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip), a system-on-chip (SoC) containing a modem module, or a system-in-package (SIP) chip. It can also be a logic module or software capable of implementing all or part of the functions of the first core network element. For example, the first core network element can be a UPF. The communication device includes: a transceiver unit for receiving a first data packet. For example, the first data packet can be a data packet that allows error transmission. The transceiver unit is also used to send first information to an access network device. For example, the first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism.

[0058] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0059] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0060] In one possible design, the first information may be included in the header of the first data packet. For example, it may be any protocol header used for user plane transmission, such as the GTP-U header, SRv6 header, or QUIC header of the first data packet. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0061] In one possible design, the first information includes at least one of the following: second information corresponding to the first data packet; or, Quality of Service (QoS) flow identification information. For example, the second information can be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. For example, the second information can be an indication, such as a single bit. It can also be understood that the second information is used to indicate that the first data packet is a packet that allows error transmission. In some examples, each data packet can correspond to a single piece of second information. For example, QoS flow identification information can be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device can use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device can determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0062] In one possible design, the communication device further includes a processing unit, configured to determine, based on the characteristic information of the first data packet, that the first data packet is a data packet permissible for error transmission. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet permissible for error transmission. Alternatively, it can be considered that the characteristic information can be used to identify such data packets permissible for error transmission.

[0063] In one possible design, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined based on AI reasoning. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0064] In one possible design, when the characteristic information is included in the header of the first data packet, the processing unit is further configured to: determine whether the first data packet is a data packet that allows error transmission based on the information in the protocol layer header of the first data packet and / or the protocol type of the first data packet. For example, the processing unit is further configured to determine whether the data packet is a data packet that allows error transmission based on a bit in the protocol layer header. For example, the information in the protocol layer header may be information from one or more protocol headers, such as the RTP header, the QUIC header, and the TCP header.

[0065] In one possible design, the processing unit can determine at least one of the following information based on the information in the protocol layer packet header: IP 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer packet header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. The first core network element can determine that the data packet is a data packet that is allowed to transmit with errors based on certain characteristics of the above sequence number information (e.g., belonging to a certain range). Of course, the same applies to the location information of other protocols or other protocols, which will not be elaborated further in this application. It is understood that the specific position values ​​of the above bits are only exemplary descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., which are not limited in this application.

[0066] For example, the mapping between IP 5-tuples or IP ternaries and service identifiers can be configured locally (e.g., stored locally in the storage unit) or obtained from other network elements (e.g., received from other network elements by the transceiver unit). Then, the processing unit of the first core network element (such as the UPF element) is also used to determine the service identifier / application identifier based on the IP 5-tuple or IP ternary in the packet header of the data packet protocol layer.

[0067] For example, the first core network element (such as the UPF element) can configure the mapping between server domain names and server IPs locally (e.g., storage unit stores locally) or obtain them from other network elements (e.g., transceiver unit receives data from other network elements). Therefore, the processing unit of the first core network element (such as the UPF element) is also used to determine the corresponding server domain name based on the server IP in the packet header of the data packet protocol layer.

[0068] For example, the first core network element (such as the UPF element) can configure (e.g., store locally in the storage unit) or obtain (e.g., receive from other network elements in the transceiver unit) the mapping relationship between terminal address information and sessions (e.g., session identifiers). Therefore, the processing unit of the first core network element (such as the UPF element) is also used to determine the corresponding session identifier based on the terminal address information in the packet header of the data packet protocol layer.

[0069] For example, the processing unit of the first core network element (such as the UPF element) is also used to determine the QoS channel (such as QoS flow) corresponding to the data packet according to the configured rules for processing user plane data packets (such as the N4 rule).

[0070] In one possible design, the feature information is determined based on AI inference. The processing unit is further used to: use any one or more of the following as input parameters (or inference input parameters, etc.) of the AI ​​model: the data packet itself, data packet attribute information, and information in the protocol layer header. The AI ​​model then infers the inference result (or inference output parameters, AI model output parameters, etc.) from the above input parameters. This inference result can indicate whether the data packet is a data packet that allows erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. When the AI ​​model is deployed on other devices, the first core network element (e.g., through a transceiver unit) can interact with the device using the aforementioned input and output parameters. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a data packet that allows erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0071] In one possible design, the transceiver unit is further configured to receive third information from a second core network element. This third information can be used to instruct the first core network element to send first information to the access network device upon receiving a first data packet (i.e., a data packet that allows erroneous transmission).

[0072] In one possible design, the third information may include the characteristic information of the first data packet. Alternatively, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0073] Fifthly, a communication device is provided, which is a second core network element, a communication module implementing the corresponding function of the second core network element, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the second core network element. For example, the second core network element can be an SMF (Software-Defined Function). The communication device includes: a transceiver unit for receiving policy information from a third core network element. The policy information can be used to indicate that a first service includes a first data packet. And / or, the policy information can be used to indicate that a first session transmits a first data packet. The first data packet is a data packet that allows erroneous transmission. The transceiver unit is also used to send third information to the first core network element. The third information can be used to instruct the first core network element to send first information to an access network device upon receiving the first data packet. The first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism. For example, the third core network element can be a PCF (Power-Only Function) entity.

[0074] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0075] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0076] In one possible design, policy information and / or third information can be used to indicate the characteristic information of the first data packet. This characteristic information of the first data packet can be used by the first core network element to determine data packets that are allowed to be transmitted erroneously. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet that is allowed to be transmitted erroneously. Alternatively, it can be considered that the characteristic information can be used to identify such data packets that are allowed to be transmitted erroneously. In other examples, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0077] In one possible design scheme, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined by the first core network element based on AI inference. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0078] In one possible design, when the feature information is included in the header of the first data packet, the feature information is related to at least one of the following: information contained in the protocol layer header; or, the protocol type of the data packet. For example, the feature information could be a bit in the protocol layer header. For example, the information in the protocol layer header could be information from one or more protocol headers, such as the RTP header, the QUIC header, and the TCP header.

[0079] In one possible design, at least one of the following information can be determined based on information in the protocol layer header: IP 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as a QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. Certain characteristics of the aforementioned sequence number information (e.g., belonging to a certain range) can be used to determine that the data packet is a packet allowed to transmit with errors. Of course, the same applies to location information for other protocols or other protocols, and this application will not elaborate further. It is understood that the specific position values ​​of the aforementioned bits are merely illustrative descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., and this application does not limit it.

[0080] In one possible design, when the feature information is determined by the first core network element based on AI inference, any one or more of the following—the data packet itself, the data packet attribute information, and the information in the protocol layer header—can be used as input parameters (or inference input parameters, etc.) for the AI ​​model. The AI ​​model then infers the results from these input parameters (or inference output parameters, etc.). This inference result indicates whether the data packet is a permissible data packet for erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a permissible data packet for erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0081] In one possible design, the transceiver unit is further configured to: send fourth information to the access network device. This fourth information can be used to instruct the access network device to enable a first transmission mechanism for the first QoS flow or the first session.

[0082] In one possible design, the transceiver unit is further configured to: send fifth information to the terminal. This fifth information can be used to instruct the terminal to enable the first transmission mechanism for the first QoS stream or the first session.

[0083] In one possible design, the policy information can be determined by a third core network element based on sixth information. This sixth information can be used to indicate which services or terminals are permitted to execute the first transmission mechanism.

[0084] In one possible design, the sixth information may include the characteristic information of the first data packet. Alternatively, the sixth information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0085] Sixthly, a communication device is provided, which is an access network device, a communication module implementing the corresponding functions of the access network device, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the access network device. The communication device includes: a transceiver unit for receiving first information from a first core network element. This first information can be used to instruct the access network device to transmit a first data packet using a first transmission mechanism. For example, the first data packet is a data packet that allows error transmission. A processing unit for controlling the transceiver unit to send the first data packet to a terminal using the first transmission mechanism.

[0086] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0087] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0088] In one possible design, the transceiver unit is also used to: receive the first data packet from the first core network element.

[0089] In one possible design, the first information can be included in the header of the first data packet. For example, the first information can be included in any protocol header used for user plane transmission, such as the GTP-U header, SRv6 header, or QUIC header of the first data packet. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0090] In one possible design, the first information may include at least one of the following: second information corresponding to the first data packet; or QoS flow identification information. For example, the second information may be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. For example, the second information may be an indication, such as a single bit. It can also be understood as indicating that the first data packet is a data packet that is allowed to be transmitted incorrectly. In some examples, each data packet may correspond to a single piece of second information. For example, QoS flow identification information may be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device may use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device may determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0091] In a seventh aspect, a communication device is provided. This communication device is a first core network element, or a communication module implementing the corresponding function of the first core network element, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the first core network element. For example, the first core network element can be a UPF. The communication device includes: a transceiver for receiving a first data packet. For example, the first data packet can be a data packet that allows error transmission. The transceiver is also used to send first information to an access network device. For example, the first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism.

[0092] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0093] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0094] In one possible design, the first information may be included in the header of the first data packet. For example, it may be any protocol header used for user plane transmission, such as the GTP-U header, SRv6 header, or QUIC header of the first data packet. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0095] In one possible design, the first information includes at least one of the following: second information corresponding to the first data packet; or, Quality of Service (QoS) flow identification information. For example, the second information can be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. For example, the second information can be an indication, such as a single bit. It can also be understood that the second information is used to indicate that the first data packet is a packet that allows error transmission. In some examples, each data packet can correspond to a single piece of second information. For example, QoS flow identification information can be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device can use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device can determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0096] In one possible design, the communication device further includes a processor configured to determine, based on the characteristic information of the first data packet, whether the first data packet is a data packet permissible for error transmission. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet permissible for error transmission. Alternatively, it can be considered that the characteristic information can be used to identify such data packets permissible for error transmission.

[0097] In one possible design, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined based on AI reasoning. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0098] In one possible design, if the characteristic information is included in the header of the first data packet, the processor is further configured to: determine whether the first data packet is a data packet that allows error transmission based on the information in the protocol layer header of the first data packet and / or the protocol type of the first data packet. For example, the processor is further configured to determine whether the data packet is a data packet that allows error transmission based on a bit in the protocol layer header. For example, the information in the protocol layer header may be information from one or more protocol headers, such as the RTP header, the QUIC header, and the TCP header.

[0099] In one possible design, the processor can determine at least one of the following information based on the information in the protocol layer packet header: IP 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer packet header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. The first core network element can determine that the data packet is a data packet that is allowed to transmit with errors based on certain characteristics of the above sequence number information (e.g., belonging to a certain range). Of course, the same applies to the location information of other protocols or other protocols, which will not be elaborated further in this application. It is understood that the specific position values ​​of the above bits are only exemplary descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., which are not limited in this application.

[0100] For example, the first core network element (such as the UPF element) can configure the mapping relationship between the IP 5-tuple or IP 3-tuple and the service identifier / application identifier locally (e.g., stored locally in a memory) or obtain it from other network elements (e.g., received from other network elements by a transceiver). Then, the processor of the first core network element (such as the UPF element) is also used to determine the service identifier / application identifier based on the IP 5-tuple or IP 3-tuple in the packet header of the data packet protocol layer.

[0101] For example, the first core network element (such as the UPF element) can configure the mapping between server domain names and server IPs locally (e.g., through local storage in a memory) or obtain them from other network elements (e.g., through a transceiver receiving data from other network elements). Therefore, the processor of the first core network element (such as the UPF element) is also used to determine the corresponding server domain name based on the server IP in the packet header of the data packet protocol layer.

[0102] For example, the first core network element (such as the UPF element) can configure (e.g., store locally in memory) or obtain (e.g., receive from other network elements via transceiver) the mapping between terminal address information and sessions (e.g., session identifiers). Therefore, the processor of the first core network element (such as the UPF element) is also used to determine the corresponding session identifier based on the terminal address information in the packet header of the data packet protocol layer.

[0103] For example, the processor of the first core network element (such as the UPF element) is also used to determine the QoS channel (such as QoS flow) corresponding to the data packet according to the configured rules for processing user plane data packets (such as the N4 rule).

[0104] In one possible design, the feature information is determined based on AI inference. The processor is further used to: use any one or more of the following as input parameters (or inference input parameters, etc.) of the AI ​​model: the data packet itself, data packet attribute information, and information in the protocol layer header. The AI ​​model then infers the inference result (or inference output parameters, AI model output parameters, etc.) from the above input parameters. This inference result can indicate whether the data packet is a data packet that allows erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. When the AI ​​model is deployed on other devices, the first core network element (e.g., through a transceiver) can interact with the device to exchange the aforementioned input and output parameters. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a data packet that allows erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0105] In one possible design, the transceiver is also used to receive third information from a second core network element. This third information can be used to instruct the first core network element to send first information to the access network device upon receiving a first data packet (i.e., a data packet that allows erroneous transmission).

[0106] In one possible design, the third information may include the characteristic information of the first data packet. Alternatively, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0107] In one possible design, the communication device also includes a memory. This memory is used to store the necessary program instructions and data for the communication device.

[0108] Eighthly, a communication device is provided, which is a second core network element, a communication module implementing the corresponding function of the second core network element, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the second core network element. For example, the second core network element can be an SMF (Software-Defined Function). The communication device includes: a transceiver for receiving policy information from a third core network element. The policy information can be used to indicate that a first service includes a first data packet. And / or, the policy information can be used to indicate that a first session transmits a first data packet. The first data packet is a data packet that allows erroneous transmission. The transceiver is also used to send third information to the first core network element. The third information can be used to instruct the first core network element, upon receiving the first data packet, to send first information to an access network device. The first information can be used to instruct the access network device to transmit the first data packet using a first transmission mechanism. For example, the third core network element can be a PCF (Power-Only Function) entity.

[0109] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0110] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0111] In one possible design, policy information and / or third information can be used to indicate the characteristic information of the first data packet. This characteristic information of the first data packet can be used by the first core network element to determine data packets that are allowed to be transmitted erroneously. It should be understood that the characteristic information of the first data packet involved in this application does not mean that the characteristic information specifically refers to the characteristic information of a particular data packet, but should be understood as the ability to identify whether a data packet is a data packet that is allowed to be transmitted erroneously. Alternatively, it can be considered that the characteristic information can be used to identify such data packets that are allowed to be transmitted erroneously. In other examples, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0112] In one possible design scheme, the feature information can be represented in at least one of the following ways: the feature information is included in the header of the first data packet; the feature information is the attribute information of the data packet; or, the feature information is determined by the first core network element based on AI inference. For example, the attribute information of the data packet may include information such as the protocol type, packet size, and packet interval of the data packet.

[0113] In one possible design, when the feature information is included in the header of the first data packet, the feature information is related to at least one of the following: information contained in the protocol layer header; or, the protocol type of the data packet. For example, the feature information could be a bit in the protocol layer header. For example, the information in the protocol layer header could be information from one or more protocol headers, such as the RTP header, the QUIC header, and the TCP header.

[0114] In one possible design, at least one of the following information can be determined based on information in the protocol layer header: IP 5-tuple; IP triplet; service identifier; application identifier; domain name; session identifier; terminal address information; location information; or, the QoS channel (such as a QoS flow) corresponding to the data packet. This location information can be used to indicate the first bit in the protocol layer header. For example, the location information can indicate the sequence number information of bits 16-31 of the RTP header of the data packet. Certain characteristics of the aforementioned sequence number information (e.g., belonging to a certain range) can be used to determine that the data packet is a packet allowed to transmit with errors. Of course, the same applies to location information for other protocols or other protocols, and this application will not elaborate further. It is understood that the specific position values ​​of the aforementioned bits are merely illustrative descriptions and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., and this application does not limit it.

[0115] In one possible design, when the feature information is determined by the first core network element based on AI inference, any one or more of the following—the data packet itself, the data packet attribute information, and the information in the protocol layer header—can be used as input parameters (or inference input parameters, etc.) for the AI ​​model. The AI ​​model then infers the results from these input parameters (or inference output parameters, etc.). This inference result indicates whether the data packet is a permissible data packet for erroneous transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a permissible data packet for erroneous transmission. This application does not limit the specific form and acquisition method of the input and output parameters.

[0116] In one possible design, the transceiver is also used to send fourth information to the access network device. This fourth information can be used to instruct the access network device to enable a first transmission mechanism for the first QoS flow or the first session.

[0117] In one possible design, the transceiver is also used to: send fifth information to the terminal. This fifth information can be used to instruct the terminal to enable the first transmission mechanism for the first QoS stream or the first session.

[0118] In one possible design, the policy information can be determined by a third core network element based on sixth information. This sixth information can be used to indicate which services or terminals are permitted to execute the first transmission mechanism.

[0119] In one possible design, the sixth information may include the characteristic information of the first data packet. Alternatively, the sixth information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet.

[0120] In one possible design, the communication device also includes a memory. This memory is used to store the necessary program instructions and data for the communication device.

[0121] A ninth aspect provides a communication device, which is an access network device, a communication module implementing the corresponding functions of an access network device, or a chip responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of an access network device. The communication device includes: a transceiver for receiving first information from a first core network element. This first information can be used to instruct the access network device to transmit a first data packet using a first transmission mechanism. For example, the first data packet is a data packet that allows error transmission. A processor for controlling the transceiver to send the first data packet to a terminal using the first transmission mechanism.

[0122] In one possible design, the first information indicates that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors.

[0123] In one possible design, the first transmission mechanism can be understood as a mechanism that allows the first protocol layer (or lower layer, such as the MAC layer) to submit the erroneous data packet to the second protocol layer (or upper layer of the first protocol layer, such as the RLC layer) when a data packet transmission error occurs. For example, the first transmission mechanism allows the terminal's MAC layer to submit the failed TB and / or MAC SDU to the RLC layer when the TB and / or MACSDU checksum fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., HARQ retransmission). Yet another example is that the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0124] In one possible design, the transceiver is also used to: receive the first data packet from the first core network element.

[0125] In one possible design, the first information can be included in the header of the first data packet. For example, the first information can be included in any protocol header used for user plane transmission, such as the GTP-U header, SRv6 header, or QUIC header of the first data packet. Of course, the specific form of the first data packet header is not limited in the examples of this application.

[0126] In one possible design, the first information may include at least one of the following: second information corresponding to the first data packet; or QoS flow identification information. For example, the second information may be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. For example, the second information may be an indication, such as a single bit. It can also be understood as indicating that the first data packet is a data packet that is allowed to be transmitted incorrectly. In some examples, each data packet may correspond to a single piece of second information. For example, QoS flow identification information may be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet. Optionally, the access network device may use the first transmission mechanism to transmit all data packets of the first QoS flow. Optionally, the access network device may determine whether to use the first transmission mechanism to transmit the first data packet based on the first QoS flow identifier or based on whether the data packet originates from the first QoS flow.

[0127] In one possible design, the communication device also includes a memory. This memory is used to store the necessary program instructions and data for the communication device.

[0128] In a tenth aspect, a communication system is provided, comprising: a first core network element, a second core network element, and an access network device. The first core network element is used to execute the methods described in the first aspect and its various possible implementations, the second core network element is used to execute the methods described in the second aspect and its various possible implementations, and the access network element is used to execute the methods described in the third aspect and its various possible implementations.

[0129] Eleventhly, a chip is provided, comprising an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer program or instructions for implementing the functions described in the first, second, and third aspects. The one or more processors are capable of executing the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first, second, and third aspects. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0130] In a twelfth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are executed on a computer, the computer causes the computer to perform a communication method as designed in any of the foregoing aspects.

[0131] In a thirteenth aspect, a computer program product is provided. The computer program product includes a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as designed in any of the foregoing aspects.

[0132] The beneficial effects of the methods in any of the second to thirteenth aspects mentioned above can be referred to the description of the beneficial effects of the methods in the first aspect, and will not be repeated here. Attached Figure Description

[0133] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0134] Figure 2 A schematic diagram of a communication architecture provided in an embodiment of this application;

[0135] Figure 3 A schematic diagram of a quality of service architecture provided in an embodiment of this application;

[0136] Figure 4 This application provides a schematic diagram of data packet processing as an embodiment of the present application.

[0137] Figure 5A schematic diagram of a communication method provided in an embodiment of this application;

[0138] Figure 6 A schematic diagram of communication signaling interaction provided in an embodiment of this application;

[0139] Figure 7 This is another schematic diagram of communication signaling interaction provided in the embodiments of this application;

[0140] Figure 8 A schematic diagram of a communication device provided in an embodiment of this application;

[0141] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0142] Figure 1 This is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of this application. Figure 1 As shown, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., Figure 1 110a and 110b, collectively referred to as 110), may also include at least one terminal device (such as... Figure 1 RAN 100 (120a-120j, collectively referred to as 120) may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices. Terminal devices 120 are wirelessly connected to RAN nodes 110. Terminal devices and RAN nodes can be interconnected via wired or wireless means. Communication system 1000 may also include a core network 200. RAN nodes 110 are connected to the core network 200 via wireless or wired means. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 can be independent physical devices, or they can be the same physical device integrating the logical functions of the core network devices and the logical functions of the RAN nodes. Communication system 1000 may also include the Internet 300.

[0143] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a future communications network, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0144] A RAN node, also known as a radio access network device, radio access network equipment, RAN entity, or access node, is used to help terminal devices access a communication system wirelessly. In one application scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB / eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future communication network, a base station in a future mobile communication system, an access node in a WiFi system, or a non-terrestrial network device, i.e., a device or satellite that can be deployed on a low-altitude or high-altitude platform. A RAN node can also be a macro base station (such as...) Figure 1 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1 In 110b), it can also be a relay node or a master node. In some examples, the TRP can also be called a transmit receiver point.

[0145] In another application scenario, multiple RAN nodes can collaborate to help terminal devices achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). An RU can also be called a radio frequency unit. Here, the CU performs the functions of the base station's Radio Resource Control Protocol (RRCP) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). RUs can be included in radio frequency devices, such as remote radio units (RRUs) or active antenna units (AAUs). CUs can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0146] In different systems, RAN nodes may have different names. For example, in an open radio access network (O-RAN) system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, an RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0147] A terminal device is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminal devices can also be referred to as terminal equipment, terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device. A terminal device can also be a chip containing modulation and demodulation functions (e.g., a baseband chip), a system-on-a-chip (SoC) containing a modem module, or a system-in-package (SIP) chip.

[0148] In some examples, the core network 200 may include any core network device such as the access and mobility management function (AMF) entity, the session management function (SMF) entity, the user plane function (UPF) entity, the sensing service control function (SSCF), the sensing data processing function (SDPF), and the unified data management (UDM).

[0149] Base stations and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminal devices.

[0150] The roles of base stations and terminal devices can be relative, for example, Figure 1The helicopter or drone 120i can be configured as a mobile base station. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a base station; however, for base station 110a, 120i is a terminal device, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminal devices can be collectively referred to as communication devices. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal device functions.

[0151] Communication between base stations and terminal devices, between base stations, and between terminal devices can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0152] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can be executed by modules (such as chips or modems) within the terminal device, or by a device that includes terminal device functions.

[0153] In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. The communication devices can include network devices and terminal devices; the network devices can also be called base station devices, i.e., the aforementioned wireless access network devices. Air interface resources can include at least one of time-domain resources, frequency-domain resources, code resources, and spatial-domain resources. The communication devices can also be called communication equipment.

[0154] The solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication can include: wireless communication between network devices and terminal devices, wireless communication between network devices, and wireless communication between terminal devices. In this application, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0155] refer to Figure 2 This paper illustrates a communication architecture suitable for 5G. In this architecture, the UE, access network (AN) (e.g., RAN), and UPF constitute the user plane connection of the UE, while the AMF, SMF, network element function (NEF), network repository function (NRF), policy control function (PCF), UDM, and application function (AF), which are connected to the bus architecture, are control plane network elements. This architecture may also include a data network (DN). The UE can communicate with the AMF through the N1 interface, the RAN through the N2 interface, the RAN through the N3 interface, the UPF through the N4 interface, the UPF through the N6 interface, and different UPFs can communicate with each other through the N9 interface. The specific implementation process and interface definitions can be found in relevant technologies, and will not be elaborated further in this embodiment. For details on the specific manifestation of the 5G communication architecture, please refer to 3GPP Technical Specifications (TS) 23.501, which will not be elaborated further in this embodiment.

[0156] For example, the AMF (Access Frame Function) can be responsible for access and mobility management in mobile networks. This includes user registration management, connection management, and reachability management. Specific functions may include: non-access stratum signaling termination, registration area management, and access authentication.

[0157] For example, an SMF (Service Provider Function) can be responsible for session management in a mobile network, such as session establishment, modification, and release. Specific functions may include assigning IP addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding capabilities.

[0158] For example, PCF can support unified policy management of network behavior. PCF can also provide policy rules to network elements related to control plane functions so that they can be executed by these elements. PCF can also obtain policy-related information from the unified data repository (UDR) to determine policy decisions.

[0159] For example, UDM can manage user contracts, authorize access, and generate authentication information.

[0160] For example, AF can be used by service providers (such as third parties that provide edge application server (EAS) content) to indicate requirements to the core network and subscribe to user plane events.

[0161] For example, a UPF can be responsible for processing user packets, such as forwarding and billing statistics. A UPF directly connected to a DN via N6 in a session can be called a Protocol Data Unit Session Anchor (PSA), while a UPF used for local traffic splitting can be called a Local Protocol Data Unit Session Anchor (L-PSA). A UPF acting as a splitting point can be called a branching point (BP) or an uplink classifier (ULCL).

[0162] For example, the RAN can provide connectivity between the UE and core network elements. The RAN can be considered as a radio access network that isolates the core network and the radio network.

[0163] For example, a UE can be a device used by a user to communicate with a 3GPP network.

[0164] For example, the SMF can control the UE's session and quality of service (QoS) through network elements such as the UE, RAN, and UPF. The PCF can generate session policy information based on UE subscription, local configuration, and third-party AF information. The PCF can send this policy information to the SMF to instruct the SMF on how to configure session policies, such as QoS control policies. The AF can be a third-party controlled network element used to make requests or provide information to the operator. For example, company A can instruct operator B to provide better QoS control for its C service. The AF's instruction can be sent directly to the PCF; or it can be sent to the NEF first, and then to the PCF, etc. Of course, the specific interaction methods between network elements can be found in relevant technical implementations, which will not be elaborated in the embodiments of this application.

[0165] Taking 5G downlink communication as an example, Figure 3 This paper illustrates a 5G QoS architecture. For example, 5G QoS control is based on QoS flows, meaning the finest granularity of QoS control can be considered the QoS flow itself. The same QoS control is applied to some or all data packets within the same QoS flow. Different QoS controls can be applied to data packets within different QoS flows. In some examples, QoS control may include controlling packet delay budget, error rate, bit rate, etc. These parameters can be characterized, for example, through QoS parameter ranges and QoS characteristics. QoS control can influence the access network equipment's packet scheduling strategy and priority.

[0166] For example, QoS flows can be configured by the SMF network element configuring QoS rules on the UE, configuring QoS profiles on the RAN, and configuring quality of service enforcement rules (QERs) on the anchor UPF. QoS rules and QERs can associate uplink and downlink data packets with corresponding QoS flows. For instance, a QoS rule can instruct the UE to add the corresponding quality of service flow identifier (QFI) to the SDAP header. Similarly, a QER can instruct the UPF to add the corresponding QFI to the General Packet Radio Service Tunneling Protocol (GTP-U) header. Furthermore, the QoS profile can control the RAN's scheduling of different data packets. However, it should be noted that the UPF and UE can know the granularity of service flows, i.e., distinguish between different service flows. The RAN, on the other hand, can know the granularity of QoS flows but cannot distinguish between different service flows. In other words, the RAN can at most distinguish between different QoS flows, but it cannot distinguish between multiple service flows within the same QoS flow.

[0167] Back Figure 3 The GTP-U tunnel can be considered as session-level, such as one GTP-U tunnel corresponding to one session between the RAN and UPF. Essentially, this tunnel involves the RAN and UPF adding a GTP-U header to the outer layer of uplink and downlink data packets. This GTP-U header may include information indicating data packet attributes, such as QFI. The GTP-U header may also carry other indicative information to indicate the characteristics of the data packet; this application does not limit this. Figure 3In this configuration, the (anchor) UPF can assign data packets from service flow 1 and service flow 2 to QoS flow 1; data packets from service flow 3 to QoS flow 2; and data packets from service flow 4 to QoS flow 3. Assuming QoS flow 1, QoS flow 2, and QoS flow 3 correspond to the same GTP-U tunnel, the (anchor) UPF transmits these three QoS flows to the RAN. The RAN can then process the data based on these different QoS flows. For example, the RAN can transmit the data packets of QoS flow 1 to the UE via radio bearer 1, and the data packets of QoS flow 2 and QoS flow 3 to the UE via radio bearer 2.

[0168] The specific communication methods for 5G QoS mentioned above can be found in technical specification (TS) 23.501, and will not be repeated in the embodiments of this application.

[0169] for Figure 3 The RAN (Radio Access Controller) receives data packets of different QoS flows sent by the UPF (User Protocol Controller), also known as Internet Protocol (IP) packets. The RAN can add a header for each protocol layer and then pass the packaged data packets to the next protocol layer, up to the MAC layer. (See reference...) Figure 4 As shown, after the RAN receives an IP data packet, it can perform SDAP layer processing, adding an SDAP protocol layer header to obtain an SDAP Protocol Data Unit (PDU). During PDCP layer processing, this SDAP PDU can also be understood as a PDCP Service Data Unit (SDU). During PDCP layer processing, a PDCP protocol layer header is added to obtain a PCDP PDU. During radio link control (RLC) layer processing, this PDCP PDU can also be understood as an RLC SDU. An RLC protocol layer header is added to obtain an RLC PDU. During MAC layer processing, this RLC PDU can also be understood as a MAC SDU. A MAC protocol layer header is added to obtain a MAC PDU. For the MAC layer, the RAN can combine one or more MAC PDUs into a TB and send it, depending on the size of the transport block (TB). In some examples, the length of the TB can be a pre-configured value. Therefore, it is possible to split a portion of the RLC SDU into two parts and add MAC layer headers to each part separately. As... Figure 4The MAC PDUs generated from the data packets in radio bearer (RB) 1 are insufficient to form a TB. Therefore, a portion of the data packets in radio bearer 2 is split so that the data packets in radio bearer 1 can form a complete TB. Of course, regarding... Figure 4 The specific processing procedure for data packets can be found in 3GPP protocol TS 38.300, and will not be repeated in the embodiments of this application.

[0170] It should be understood that, although Figure 4 The headers added by different protocol layers are all represented by "H", but the content of the headers added by different protocol layers is usually different.

[0171] In some examples, each TB can have a check bit, such as a cyclic redundancy check (CRC). Each MAC SDU within each TB can also have its own check bit, used by the UE to determine whether the received data packet is correct. Of course, during the encapsulation process into a TB, a TB header can be encapsulated on top of one or more MAC PDUs.

[0172] On the UE side, there is the same protocol layer (or protocol stack), and each protocol layer parses its corresponding header and transmits it to the next higher protocol layer. It can be understood that the process of the UE layer processing downlink data is exactly the reverse of the process of the RAN layer processing downlink data. For the concepts of upper and lower protocol layers, please refer to [reference needed]. Figure 4 The protocol layer located above can be considered as the layer above the protocol layer below. The specific processing order of the protocol layers can be found in related technologies, and will not be elaborated further in this application.

[0173] In some cases, during the transmission of a Data Packet (TB) at the MAC layer, a hybrid automatic repeat-request (HARQ) retransmission mechanism exists between the UE and the RAN. Upon receiving a TB, the UE can check the checksum of each MAC Sub-Unit (MSU) and the entire TB. If all checks pass, the UE can reply with an ACK (acknowledgment) to the RAN. The UE can then pass the MAC SDU up to the RLC layer for further processing. If any checksum in the MAC SDU or TB fails, it indicates a transmission error. The UE can reply with a NACK (negative acknowledgement) to the RAN to trigger a HARQ retransmission. The UE stops submitting data packets to the RLC layer. Upon receiving a retransmitted TB from the RAN, the UE re-checks the data. If the checksum passes, the UE can reply with an ACK to the RAN as described above and pass the MAC SDU to the RLC layer. If the checksum fails, the retransmission process is repeated.

[0174] In some examples, a HARQ process can be a granularity or channel for MAC layer transmission between the RAN and UE. A single HARQ process can transmit one TB (Throughput), similar to concepts like QoS flows or bearers, and can be understood as a transmission channel. However, it should be noted that a single HARQ process can transmit data packets from one or more bearers or QoS flows, for example... Figure 4 As shown in the diagram. In some examples, the RAN can send radio resource control (RRC) signaling and downlink control information (DCI) to the UE to instruct the UE to disable a certain HARQ process. Disabling a HARQ process can be understood as not performing HARQ retransmission.

[0175] In media data transmission scenarios, there exists an algorithm that can divide the media data stream into two types of data streams. In the embodiments of this application, these two types of data streams can be referred to as data stream A and data stream B. For example, if data packets in data stream A are lost or corrupted, the media picture cannot be recovered. Conversely, if data packets in data stream B are lost or corrupted, it does not affect the recovery of the media picture, but may affect the picture quality to some extent. In some cases, data stream A accounts for a smaller proportion of the entire media data stream than data stream B, for example, it may account for about 5% to 20%.

[0176] For example, there are 2 A packets and 8 B packets out of 10 data packets. A packets can be considered as packets from data stream A, and B packets as packets from data stream B. Suppose that during communication, some bits in one B packet are corrupted, or the entire B packet is lost. Then, the video resolution displayed by the receiving device (i.e., the device receiving the aforementioned data packets) might decrease from 1080p progressive scan (p) to 720p. Of course, the decrease in video resolution might be small, almost imperceptible to the user. However, if there is a bit error in an A packet, or the entire A packet is lost, it could directly cause the video to fail to display, such as a black screen or being stuck on a particular frame.

[0177] However, currently, terminals and access network devices cannot effectively identify the aforementioned A and B data packets. Furthermore, terminals and access network devices are also unable to effectively continue transmitting B data packets to higher protocol layers in the event of packet errors or loss.

[0178] Therefore, embodiments of this application provide a communication method that sends first information to an access network device to instruct the access network device to transmit data packets that are allowed to be transmitted erroneously using a first transmission mechanism. This allows the access network device to identify data packets that are allowed to be transmitted erroneously using the first information and to perform subsequent operations on such data packets. This avoids retransmission of data packets that are allowed to be transmitted erroneously, thus improving communication efficiency.

[0179] The communication method and apparatus will be further described below with reference to the accompanying drawings. It is understood that the embodiments of this application use a terminal device and a network device as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. The method executed by the terminal device in this application can also be implemented by modules in the terminal device (e.g., circuits, processors, chips, or chip systems), or by logic nodes, logic modules, or software that can implement all or part of the functions of the terminal device. Similarly, the method executed by the network device in this application can also be implemented by modules in the network device (e.g., circuits, processors, chips, or chip systems), or by logic nodes, logic modules, or software that can implement all or part of the functions of the network device.

[0180] Figure 5 This is a schematic diagram of a communication method provided for an embodiment of this application.

[0181] This communication process may be applicable to, but is not limited to, the following: Figure 1 , Figure 2The method can be applied to the communication scenarios shown. It can be used in Long-Term Evolution (LTE), LTE Frequency Division Duplex (FDD) systems, LTE TDD, 5G or NR systems, future communication systems (such as future communication systems), and V2X. V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), long-term evolution-vehicle (LTE-V) communication, vehicle-to-everything (V2X), MTC, IoT, long-term evolution-machine (LTE-M) communication, machine-to-machine (M2M), and D2D wireless communication scenarios.

[0182] In the various embodiments of this application, the devices and network elements involved can be devices and network elements applicable to any of the above-mentioned communication systems, such as those applicable to 5G, NR, etc. Of course, they can also be devices and network elements applicable to future communication systems. Therefore, the embodiments of this application do not limit the names of the devices and network elements.

[0183] The method may include the following steps:

[0184] S101, the first core network element receives the first data packet.

[0185] For example, the first data packet can be a data packet that allows error transmission. This first data packet can also be called an error-tolerant data packet, a data packet that allows transmission errors, an error-tolerant data packet, an error-tolerant data packet, an error-tolerant data packet, a data packet with low reliability requirements, etc. This application embodiment does not limit the specific name of the first data packet. In other words, assuming that the first data packet contains (or carries) some or all of the data that can be used or parsed even if an error occurs (e.g., an error occurs during transmission), then this type of data can be called error-tolerant data, error-tolerant data, data that allows transmission errors, error-tolerant data, error-tolerant data, error-tolerant data packet, data with low reliability requirements, etc. Correspondingly, the data stream corresponding to the first data packet can also be considered to allow error transmission. It is understood that an error can refer to the data packet's checksum (or checksum) failing (e.g., the receiving end determines that the checksum (or checksum) fails). Or, the data packet's integrity protection fails (e.g., the receiving end determines that the integrity protection fails). Or, the data packet experiences errors, inversions, and / or loss of all or some bits during transmission. The transmission process can refer to transmission between the terminal and the access network device, or transmission between the terminal and the server. The receiving end mentioned above can be understood as a device that receives data packets, such as a terminal in downlink communication.

[0186] In the various embodiments of this application, the above-mentioned data packet that allows transmission errors can also be described as "error packet delivery", and can also be replaced by any equivalent description such as error packet transmission, allowing error transmission, allowing transmission errors, allowing data packet error transmission, insensitive to transmission errors, low importance, low accuracy, error tolerance, error packet recovery, etc. The embodiments of this application do not limit this.

[0187] It is understandable that the first data packet can be a data packet that, in the event of packet loss or error, does not affect subsequent data processing. For example, the first data packet can continue to be transmitted to subsequent protocol layers for data processing even in the event of packet loss or error. For example, the first data packet can be considered as the aforementioned B data packet.

[0188] In some cases, the first core network element can be a UPF.

[0189] In some embodiments, the first core network element can determine whether the first data packet is a data packet that is allowed to be transmitted with errors based on the characteristic information of the first data packet. In other words, the first core network element can determine whether the received data packet is the first data packet based on the characteristic information of the first data packet. This allows the access network device to be instructed to transmit the first data packet using a first transmission mechanism via first information.

[0190] This application embodiment can accurately distinguish between data packets that are allowed to be transmitted incorrectly and other data packets by using the characteristic information of the data packets. This allows for the indication of such data packets that are allowed to be transmitted incorrectly through first information, thereby improving communication efficiency.

[0191] In some cases, the aforementioned characteristic information can be included in the header of the first data packet. For example, the characteristic information may be contained in the header of a protocol layer of the first data packet. The first core network element can identify the data packet as the first data packet using the characteristic information in the protocol layer header.

[0192] For example, the first core network element can determine the IP 5-tuple based on the characteristic information in the protocol layer packet header. This IP 5-tuple may include the source IP address, source port, destination IP address, destination port, and transport layer protocol.

[0193] For example, the first core network element can determine the IP triplet based on the characteristic information in the protocol layer packet header. This IP triplet may include the source IP address, destination IP address, and transport layer protocol.

[0194] For example, the first core network element can determine the service identifier based on the feature information in the protocol layer packet header.

[0195] For example, the first core network element can determine the application identifier based on the feature information in the protocol layer packet header.

[0196] For example, the first core network element can determine the domain name based on the characteristic information in the protocol layer packet header.

[0197] For example, the first core network element can determine the session identifier based on the feature information in the protocol layer packet header.

[0198] For example, the first core network element can determine the terminal's address information based on the characteristic information in the protocol layer packet header. For instance, the terminal's address information could be its IP address.

[0199] For example, the first core network element can determine location information based on feature information in the protocol layer header. This location information can be used to indicate the first bit in the protocol layer header. For instance, a certain bit in the protocol layer header can be considered to indicate the aforementioned feature information. For example, the first bit is one bit and is located at the 7th bit in the protocol layer header. Assume that the 7th bit is 1, indicating that the data packet is the first data packet. Then, the first core network element can determine the value of the 7th bit in the protocol layer header of the data packet. If this bit is 1, then it can be determined that the data packet is a data packet that allows erroneous transmission, i.e., the first data packet.

[0200] For example, location information can indicate the sequence number information of bits 16-31 of the RTP header of a data packet. The first core network element can determine that the data packet is a packet that is allowed to be transmitted with errors based on certain characteristics of the sequence number information (e.g., belonging to a certain range). Of course, the same principle applies to location information for other protocols, and this application will not elaborate further. It is understood that the specific position values ​​of the bits mentioned above are merely illustrative and are not limited in this application. This location information can also be called protocol location information, protocol field information, etc., and this application does not limit its scope.

[0201] For example, when different service flows have the same IP 5-tuple or IP 3-tuple, the first core network element can determine which data packets are the first data packets based on the first bit in the protocol layer packet header.

[0202] It is understood that the embodiments of this application do not limit the number of bits of the first bit, nor do they limit which bit in the protocol layer header the first bit is located in.

[0203] For example, the first core network element can determine the QoS channel corresponding to the data packet based on the feature information in the protocol layer packet header. For instance, the QoS channel can be represented by the QoS flow.

[0204] For the aforementioned first core network element, information can be determined based on the feature information in the protocol layer packet header. One possibility is that the information is directly carried in the protocol layer packet header, and another possibility is that it is determined based on the information carried in the protocol layer packet header. This application embodiment does not limit this.

[0205] For example, a first core network element (such as a UPF element) can configure locally or obtain from other network elements the mapping between IP 5-tuples or IP 3-tuples and service / application identifiers. Then, the first core network element (such as a UPF element) can determine the service / application identifier based on the IP 5-tuples or IP 3-tuples in the packet header. Similarly, a first core network element (such as a UPF element) can configure locally or obtain from other network elements the mapping between server domain names and server IPs. Then, the first core network element (such as a UPF element) can determine the corresponding server domain name based on the server IP in the packet header. Furthermore, a first core network element (such as a UPF element) can configure locally or obtain from other network elements the mapping between terminal address information and session (such as session identifier) ​​information. Then, the first core network element (such as a UPF element) can determine the corresponding session identifier based on the terminal address information in the packet header. For example, the first core network element (such as the UPF element) can determine the QoS channel (such as QoS flow) corresponding to the data packet based on the configured rules for processing user plane data packets (such as the N4 rule).

[0206] This application provides various representations of feature information in the protocol layer header so that feature information can be determined in different communication scenarios using a method suitable for that communication scenario, thereby accurately identifying the first data packet based on the feature information and improving communication efficiency.

[0207] For example, the first core network element can determine the protocol type of the first data packet, and then determine the characteristic information in the protocol layer header corresponding to that protocol type based on the protocol layer header. Based on this characteristic information, the data packet is determined to be the first data packet. For instance, the first core network element can determine whether the data packet is a data packet that allows erroneous transmission based on a single bit in the protocol layer header. For example, the information in the protocol layer header can be information from one or more of the following protocol headers: Real-time Transport Protocol (RTP) header (or its extension header), Quick User Datagram Protocol Internet Connection (QUIC) header (such as the plaintext portion of the QUIC header), and Transmission Control Protocol (TCP) header.

[0208] This application provides various implementations for determining a first data packet as a data packet that is allowed to be transmitted with errors, when the feature information is located in the header of the first data packet. This allows for the identification of the first data packet using a method suitable for that specific communication scenario, thereby improving the system's versatility.

[0209] In other examples, the aforementioned characteristic information can be attribute information of the data packet. For instance, the attribute information of the data packet may include the protocol type, the packet size (which can be considered the length of the data packet), the packet interval, and other information. For example, a data packet using a certain protocol type can be considered the first data packet. Similarly, a data packet whose packet size meets a certain number of bytes (or a certain range of bytes) can be considered the first data packet. Furthermore, a data packet whose packet interval meets a certain duration can be considered the first data packet.

[0210] In some other embodiments, the aforementioned feature information can be determined based on artificial intelligence (AI) reasoning. For example, an AI model can be deployed on the first core network element, which predicts the feature information using this AI model. This allows the first core network element to identify the first data packet based on the feature information. Alternatively, the first core network element can directly predict whether a data packet is the first data packet using the AI ​​model. For instance, the attribute information of the aforementioned data packet can be used as input to the AI ​​model to predict whether the data packet is the first data packet.

[0211] For example, the first core network element can use any one or more of the following as input parameters (or inference input parameters, etc.) of the data packet itself, data packet attribute information, and information in the protocol layer header: the data packet itself, data packet attribute information, and information in the protocol layer header. The AI ​​model then infers the results from these input parameters (or inference output parameters, etc.). This inference result indicates whether the data packet is a permissible data packet for error transmission. In some examples, the AI ​​model used for inference can be deployed on the first core network element or other devices. When the AI ​​model is deployed on other devices, the first core network element can interact with those devices using the aforementioned input and output parameters. In some examples, the training of the AI ​​model can also be completed on the first core network element or other devices; this application does not impose any restrictions. The input and output parameters of the AI ​​model can also include any other possible information. It should be noted that the output parameters should be used to determine whether the data packet is a permissible data packet for error transmission. This application does not limit the specific form or acquisition method of the input and output parameters.

[0212] For example, for some encrypted service flows or service flows that are not tagged at the application layer, the first core network element can be pre-configured with an AI model to identify which data packets are the first data packets.

[0213] This application provides various forms of feature information to determine the feature information in different communication scenarios using a method suitable for that specific scenario. This allows for the subsequent determination of the first data packet based on the feature information.

[0214] It should be understood that the feature information of the first data packet involved in the embodiments of this application does not mean that the feature information specifically refers to the feature information of a certain data packet. Rather, it should be understood that the feature information can be used to identify whether a data packet is a data packet that allows for erroneous transmission. It can also be considered that the feature information can be used to identify such data packets that allow for erroneous transmission.

[0215] In some implementations, the first core network element can also trigger the transmission of first information to the access network via an instruction from the second core network element. For example, the method may further include: the second core network element can send third information to the first core network element. Correspondingly, the first core network element can receive the third information from the second core network element. This third information can be used to instruct the first core network element to send the first information to the access network device upon receiving the first data packet. Alternatively, the third information may include AI-related information (e.g., a model or model identifier) ​​used to determine the feature information of the first data packet. It is understood that in this case, the first core network element can determine which AI model to use to predict the feature information of the first data packet through this AI-related information.

[0216] In some examples, a third core network element can send policy information to a second core network element. Correspondingly, the second core network element can receive policy information from the third core network element. For example, the policy information can be used to indicate that a first service includes a first data packet. And / or, the policy information can be used to indicate that a first session transmits the first data packet. Optionally, the policy information can instruct a session to enable error packet delivery.

[0217] For example, a third core network element can use policy information to inform a second core network element that erroneous transmission is allowed for the first service, meaning that the data packets included in the first service are allowed to be transmitted erroneously. Here, a service can also be called a service flow, and a service flow can consist of multiple data packets. In this case, the first service can be considered a service that allows erroneous transmission. This service can be indicated, for example, through IP 5-tuples, IP 3-tuples, service identifiers, or domain names. Alternatively, a third core network element can use policy information to inform a second core network element that erroneous transmission is allowed for the first session, meaning that the data packets included in the first session are allowed to be transmitted erroneously. Here, a session can include one or more service flows. In this case, the first session can be considered a session that allows erroneous transmission.

[0218] Optionally, the policy information may also include characteristic information of the first data packet. Alternatively, the policy information may include AI-related information (e.g., a model or model identifier) ​​used to determine the characteristic information of the first data packet. It can be assumed that the third core network element can inform the second core network element how to identify the first data packet through the policy information. The second core network element can determine the data packet in the first service as the first data packet based on the characteristic information of the first data packet indicated by the policy information, or determine the data packet included in the first session as the first data packet.

[0219] Optionally, the characteristic information of the first data packet can also be pre-configured in the second core network element (such as SMF). Alternatively, the characteristic information of the first data packet can be provided by the terminal, such as by obtaining it through the terminal's PDU session establishment request. This method can be specifically described in the following embodiments.

[0220] In some cases, third core network elements (such as PCF) can determine the above policy information based on locally configured policies, such as any one or more of the UE's subscription information, AF request, PCF local logic, etc.

[0221] In some cases, policy information can be a PDU session policy or a policy and charging control (PCC) rule.

[0222] The following describes two methods for how the second core network element determines the first data packet.

[0223] Method 1:

[0224] The second core network element can determine, based on the policy information indicating the first session, that some or all of the data packets included in the first session are the first data packets. Optionally, it can determine, based on the characteristic information of the first data packets, that data packets in the first session that match the characteristic information of the first data packets are the first data packets.

[0225] For example, the first session mentioned above can be indicated by a session identifier or other means.

[0226] Method 2:

[0227] The second core network element can determine some or all of the data packets included in the first service as the first data packet based on the first service indicated by the policy information. Optionally, it can determine the data packets in the first service that match the characteristic information of the first data packet as the first data packet based on the characteristic information of the first data packet.

[0228] For example, the aforementioned first service can be indicated by IP quintuples, IP triples, domain names, service identifiers, etc.

[0229] For methods 1 and 2 above, the second core network element can process the header of the first data packet. For example, it can indicate the first data packet using the first bit in the protocol layer header of the first data packet. This allows the first core network element to determine that the data packet is the first data packet by using the first bit in the protocol layer header of the first data packet.

[0230] In some examples, based on the aforementioned policy information, the second core network element can send third information to the first core network element to instruct the first core network element to send first information to the access network device. Alternatively, the third information can trigger the first core network element to instruct the access network device to use the first transmission mechanism to transmit the first data packet.

[0231] The second core network element can instruct the first core network element to send the first information to the access network device in various ways.

[0232] Method C1:

[0233] The second core network element can instruct the first core network element to process the headers of data packets that meet the characteristic information of the first data packet in certain sessions or service flows. For example, the second core network element can instruct the first core network element to filter out data packets that meet the characteristic information of the first data packet in a packet detection rule (PDR). And, in a forwarding action rule (FAR), the second core network element can instruct the first core network element to process the headers of these data packets, such as adding first information to the header, or determining or sending the first information. In various embodiments of this application, header processing can be alternatively described as header handling control, or alternatively as marking.

[0234] In some cases, if the packet detection information of PDR is a wildcard or empty, it can be assumed that all packets in the session meet the PDR filtering / detection criteria.

[0235] In this case, the PDR may include packet detection information, such as wildcards, IP 5-tuples, IP triples, etc. The PDR may also include the characteristics of the first data packet. The PDR may also include a FAR, which instructs the UPF to process the header of the first data packet so that the RAN can subsequently use the first transport mechanism to transmit the first data packet. The PDR in this case can be seen in Table 1.

[0236] Table 1

[0237] PDR Packet inspection information (wildcards, IP 5-tuples, IP 3-tuples, etc.) The first data packet's characteristic information (such as the XXth bit of the RTP header). FAR logo ……

[0238] Method D2:

[0239] The second core network element can instruct the first core network element to process the headers of all data packets in certain service flows or QoS flows. For example, the first core network element can directly process the headers of the data packets in the aforementioned service flows or QoS flows, such as determining first information. Alternatively, the second core network element can instruct the first core network element in a PDR (Programmable Receiver) to process the headers of all data packets in certain service flows or QoS flows. This could involve adding first information to the header, or determining or sending first information.

[0240] In this case, the PDR may include packet detection information (or packet inspection information), such as wildcards, IP 5-tuples, IP 3-tuples, etc. The PDR may also include FAR, which instructs the UPF to process the header of the first data packet so that the RAN can subsequently use the first transport mechanism to transmit the first data packet. The PDR in this case can be seen in Table 2.

[0241] Table 2

[0242] PDR Packet inspection information (wildcards, IP 5-tuples, IP 3-tuples, etc.) FAR logo ……

[0243] The FAR identifiers in Tables 1 and 2 above can be used to index specific FARs. Accordingly, the FAR can include corresponding rules, such as the header processing of the first data packet, to indicate RAN error packet delivery.

[0244] In some examples, the second core network element can be a session management network element or a network element used for managing connections, such as an SMF. The third core network element can be a user plane network element or a network element used for forwarding user plane data, such as a UPF.

[0245] In some embodiments, the third information may include the characteristic information of the first data packet. That is, the second core network element can use the third information to inform the first core network element of the characteristic information of the first data packet, so that the first core network element can identify the first data packet based on this characteristic information.

[0246] In this embodiment, the second core network element can inform the first core network element of the characteristic information of the first data packet, so that the first core network element can accurately identify the first data packet based on the characteristic information, thereby improving communication efficiency.

[0247] In some examples, the third information involved in the above embodiments is signaling between control plane network elements and user plane network elements, such as the N4 rule.

[0248] In this embodiment of the application, the second core network element can flexibly instruct the first core network element to send the first information to the access network device through the third information.

[0249] In some examples, even if the third information does not include the characteristic information of the first data packet, the first core network element (such as the UPF) can pre-configure the characteristic information of the first data packet locally. Alternatively, if the UPF processes the headers of all data packets in the entire service flow or QoS flow, the UPF does not need to identify whether each data packet is the first data packet; therefore, the UPF does not need the characteristic information of the first data packet. For example, the first data packet may have already been distinguished from other data packets using IP addresses or other methods.

[0250] In some embodiments, the SMF can determine whether to use method C1 or method D2 by indicating in the AF request whether the IPs of different services are the same.

[0251] In some possible implementations, considering that the second core network element can instruct the first core network element to send first information to the access network device via third information, thereby triggering the access network device to transmit the first data packet using the first transmission mechanism, the second core network element can also accordingly inform the access network device and / or the terminal whether to execute the first transmission mechanism.

[0252] In some embodiments, the second core network element may also send fourth information to the access network device. Accordingly, the access network device may receive the fourth information from the second core network element. This fourth information may be used to instruct the access network device to enable a first transport mechanism for the first QoS flow or the first session.

[0253] For example, a second core network element can use the fourth information to instruct (or authorize) the access network device to enable the first transmission mechanism for the first session, that is, to allow error transmission of the data packets included in the first session. As another example, a second core network element can use the fourth information to instruct (or authorize) the access network device to enable the first transmission mechanism for the first QoS, that is, to allow error transmission of the data packets included in the first QoS flow.

[0254] Optionally, the access network device may send a first response message to the second core network element, that is, inform the second core network element that the access network device accepts or refuses to enable the first transmission mechanism. For example, the access network device may determine whether to accept the instruction of the aforementioned fourth information based on its own capabilities, load, and / or based on the capabilities, load, and authorization of the terminal device.

[0255] For example, the fourth piece of information can be carried by messages instructing access network devices to configure session tunnels, or by messages configuring access network devices to perform QoS control. Examples include N2 messages and QoS configuration files.

[0256] The embodiments of this application can also flexibly instruct access network devices to enable the first transmission mechanism through the fourth information, thereby improving the flexibility of communication system configuration.

[0257] In some embodiments, the second core network element may also send fifth information to the terminal. Accordingly, the terminal may receive the fifth information from the second core network element. This fifth information may be used to instruct the terminal to enable the first transmission mechanism for the first QoS flow or the first session.

[0258] For example, a second core network element can use the fifth information to instruct (or authorize) a terminal to enable the first transmission mechanism for the first session, that is, to allow the erroneous transmission of data packets included in the first session. As another example, a second core network element can use the fifth information to instruct (or authorize) a terminal to enable the first transmission mechanism for the first QoS, that is, to allow the erroneous transmission of data packets included in the first QoS flow.

[0259] For example, the fifth piece of information can be carried through methods such as receiving messages in a session, modifying messages in a session, or QoS rules, and this application does not limit the scope of the embodiments.

[0260] Optionally, the terminal may send a second response message to the second core network element, informing the second core network element whether the terminal accepts or refuses to enable the first transmission mechanism. For example, the terminal may determine whether to accept the instruction of the fifth information based on its own capabilities, load, and other factors.

[0261] The embodiments of this application can also flexibly instruct the terminal to enable the first transmission mechanism through the fifth information, thereby improving the flexibility of the communication system configuration.

[0262] It is understood that performing error transmission on the data packets included in the first QoS flow or the data packets included in the first session can mean performing error transmission on all or part of the data packets included in the first QoS flow or the first session. It can be considered that the first data packet can be all or part of the data packets included in the first QoS flow; or, the first data packet can be all or part of the data packets included in the first session.

[0263] In other examples, the access network device may instruct the terminal to enable the first transport mechanism for the first QoS flow or the first session. For example, the access network device may also send a seventh message to the terminal. Accordingly, the terminal may receive the seventh message from the access network device. This seventh message can be used to instruct the terminal to enable the first transport mechanism for the first QoS flow or the first session.

[0264] For example, the seventh information can be carried through configuration messages used between terminal devices and access network devices, such as RRC signaling.

[0265] In the communication method provided in this application embodiment, the third core network element can determine policy information in the following ways. For example, the third core network element can determine policy information based on sixth information. This sixth information can be used to indicate services that are allowed to perform the first transmission mechanism or terminals that are allowed to perform the first transmission mechanism.

[0266] For example, the sixth information can be sent by a device or network element inside or outside the core network. For instance, the sixth information could be an AF request message. For example, an AF or application server (AS) could send an AF request message to a third core network element to indicate whether the service or terminal authorized to perform the first transmission mechanism is permitted. The AF request message can be sent directly from the AF to the third core network element, or indirectly forwarded to the third core network element via one or more other network elements. During transmission, the message carrying the information, the structure / format of the information, and the content of the information can all change, as long as the function of the information remains the same, all conforming to the scheme of this application. For example, the AF request can be sent directly to the PCF; or the AF request can be forwarded to the PCF via the NEF; or it can be sent to the UDR via the NEF and then forwarded to the PCF. This application does not limit the process of how the AF request is transmitted to the PCF.

[0267] For example, the AF request may include a service identifier, such as an IP 5-tuple or IP triplet. The AF request may also include a UE identifier, such as a Subscription Permanent Identifier (SUPI) or International Mobile Subscriber Identity (IMSI). The AF request may also include information indicating the enabling of error packet delivery. Finally, the AF request may include the characteristics of the first data packet.

[0268] The identifiers involved in the various embodiments of this application may be identity identifiers (ID) or indexes.

[0269] In some cases, AF and AS can be the server for the application or the server for the business.

[0270] Optionally, the sixth information may also include feature information of the first data packet. Alternatively, the sixth information may include AI-related information (e.g., a model or model identifier) ​​used to determine the feature information of the first data packet. In other words, network elements such as AF or AS can inform the third core network element how to identify the first data packet. This allows the third core network element to perform subsequent operations in the aforementioned embodiments, knowing the feature information of the first data packet.

[0271] The sixth information in this embodiment may include the characteristic information of the first data packet, so that the third core network element can determine the policy information based on the characteristic information. Optionally, the characteristic information of the first data packet may also be carried in the policy information, so that the first core network element and the access network element can subsequently obtain the characteristic information of the first data packet to identify the first data packet.

[0272] In this embodiment, the third core network element can obtain policy information through the sixth information, thereby enabling it to instruct the second core network element to send third information to the first core network element based on the policy information. This triggers the first core network element to send first information to the access network device upon receiving the first data packet. Furthermore, it instructs the access network device to use the first transmission mechanism to transmit the first data packet, thereby improving communication efficiency.

[0273] In some possible implementations, the terminal can also send a PDU session establishment request to the SMF. For example, during the session establishment process, the UE can instruct the session to enable error packet delivery (or error packet delivery service) through a PDU session establishment request.

[0274] For example, the PDU session establishment request can be used to indicate one or more of the following information: the UE itself supports the capability of packet error delivery; the UE requests that packet error delivery be enabled in this session; the UE requests that packet error delivery be enabled for certain services; or, it can be indicated through the target data network name (DSS) / single network slice selection assistance information (S-NSSAI) in the PDU session establishment request. In other words, it indicates that packet error delivery is enabled in this session through the target DSS / S-NSSAI.

[0275] For example, different services can be distinguished as either the A-stream service or the B-stream service mentioned in the aforementioned embodiments. The A-stream service includes A data packets, and the B-stream service includes B data packets. The B data packet is the first data packet mentioned in the aforementioned embodiments of this application.

[0276] In some embodiments, a PDU session establishment request may include characteristic information of a first data packet.

[0277] In some cases, the SMF can obtain the UE's subscription information from the UDM. For example, this subscription information can be used to indicate whether the UE is authorized to enable packet delivery errors. For instance, the subscription information may indicate that the UE is authorized to enable packet delivery errors for a specific session or certain services. Based on this subscription information, the SMF determines whether to enable packet delivery errors for the UE's session, services, etc.

[0278] S102, the first core network element sends first information to the access network device. Correspondingly, the access network device receives the first information from the first core network element.

[0279] For example, the first information can be used to indicate that the first data packet is a data packet that is allowed to be transmitted with errors. For example, the first information can be used to instruct the access network device to transmit the aforementioned first data packet. Optionally, the first information can be used to instruct the access network device to use a first transmission mechanism to transmit the aforementioned first data packet. For example, the first transmission mechanism can be understood as a transmission mechanism that allows a first protocol layer (or lower layer, such as the medium access control (MAC) layer) to submit the erroneous data packet to a second protocol layer (or upper layer of the first protocol layer, such as the radio link control (RLC) layer) in the event of a data packet transmission error. For example, the first transmission mechanism allows the terminal's MAC layer to submit a failed TB and / or MAC SDU to the RLC layer in the event that the transport block (TB) and / or MAC service data unit (SDU) verification fails. Alternatively, the first transmission mechanism can disable or turn off retransmission mechanisms (e.g., hybrid automatic repeat-request (HARQ) retransmission). For example, the first transmission mechanism can modify the retransmission mechanism (e.g., reduce the number of HARQ retransmissions).

[0280] In other words, even if the first data packet is corrupted or lost, it is still passed to subsequent protocol layers to perform their relevant operations. For example, regardless of whether the first data packet is corrupted or lost, the MAC layer will pass it to the RLC layer for processing, and so on. In some examples, the first transmission mechanism may also be called a low-reliability MAC layer transmission mechanism. Of course, the first transmission mechanism may also be called a MAC layer corrupted packet transmission mechanism, etc., and the specific name of the first transmission mechanism is not limited in this application embodiment.

[0281] In some examples, the first core network element can also send the first data packet received in S101 to the access device. Accordingly, the access network device receives the first data packet from the first core network element.

[0282] In some embodiments, the aforementioned first information may be carried in the header of the first data packet. For example, the first core network element may add the first information to the header of the first data packet. This allows the first core network element to send the first data packet with the first information added to its header to the access network device. This process can be considered as the first core network element processing the header of the first data packet, the purpose of which is that the subsequent access network device can determine, based on the first information in the header, whether the first data packet is a data packet that is allowed to be transmitted with errors.

[0283] In some examples, the header of the first data packet can be any protocol header used for user plane transmission, such as a GTP-U header, a segment routing over internet protocol version 6 (SRv6) header, or a quick user datagram protocol internet connection (QUIC) header. Of course, this application does not limit the specific form of the first data packet header in the examples.

[0284] This application provides a method for carrying first information in the header of a first data packet, thereby accurately indicating that the first data packet is a data packet that allows error transmission.

[0285] In other examples, the first information can be independent of the first data packet. In this case, the first information can carry information indicating the first data packet, so that the access network device can accurately identify which data packets are the first data packets. For example, the first information may include information that identifies the first data packet, such as the packet's identifier, packet characteristic information, etc., so that the access network device can accurately identify the first data packet.

[0286] S103, the access network device uses the first transmission mechanism to send the first data packet to the terminal.

[0287] In some cases, upon receiving the first information, the access network device can determine that it will use a first transmission mechanism to transmit the first data packet. Then, the access network device can use this first transmission mechanism to send the first data packet to the terminal.

[0288] In some embodiments, the first information may instruct the access network device to transmit the aforementioned first data packet using a first transmission mechanism in any one or more of the following ways.

[0289] Method A:

[0290] The first information may include second information corresponding to the data packet. This second information can be used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet. Alternatively, the second information can be used to indicate that the data packet is a data packet that allows error transmission. For example, for each data packet, the second information corresponding to that data packet can indicate whether the data packet is the first data packet. For instance, a first core network element can use the second information corresponding to the first data packet to indicate that the first data packet is a data packet that allows error transmission. Alternatively, the second information corresponding to the first data packet can be considered as instructing the access network device to use the first transmission mechanism to transmit the first data packet. In some examples, the second information can be an indication, such as a single bit.

[0291] In this case, it can be considered that each data packet is individually indicated as the first data packet. For any data packet, the access network device can determine whether to use the first transmission mechanism to transmit the data packet based on the second information corresponding to that data packet.

[0292] In some examples, when a first core network element determines that a received data packet is a first data packet, it can add second information to the header of that first data packet. For instance, the first core network element can add second information to the GTP-U header of the first data packet to indicate that the first data packet is a packet that is allowed to be transmitted with errors. The first core network element performs this operation for each first data packet, thereby providing indication for each first data packet.

[0293] In some cases, access network devices can be configured according to... Figure 4 The method shown describes the processing of the first data packet sent by the first core network element. The first data packet sent by the first core network to the access network device can be understood as... Figure 4 The access network device adds headers for each protocol layer sequentially according to a certain protocol layer order to the IP data packet in the first data packet. For example, during MAC layer processing, the access network device can add indication information (i.e., second information) to the header or TB header of the MAC SDU including the first data packet. For example, depending on the implementation, the indication information may include first indication information and / or second indication information.

[0294] One implementation approach is for the access network device to place the first data packet, after adding the headers of each protocol layer, into a separate Data Block (TB). In other words, the access network device can generate a separate TB for data packets that are allowed to be transmitted erroneously. This means that all data in this TB is data that is allowed to be transmitted erroneously. The access network device can add a first indication to the TB header, which indicates that the TB is an erroneous TB. That is, this TB can be passed to subsequent protocol layers for processing if the checksum fails. For the terminal, upon receiving this TB and if its checksum fails, the data in the TB is passed to the RLC layer for further processing.

[0295] Another implementation approach is for the access network device to place the first data packet after adding the headers of each protocol layer into a separate MAC SDU. This means that the data in this MAC SDU is all data that allows error transmission. The access network device can add second indication information to the header of this MAC SDU, which indicates that the MAC SDU is an error-allowed MAC SDU. That is, this MAC SDU can be passed to subsequent protocol layers for processing if the checksum fails. For the terminal, upon receiving a TB containing an error-allowed MAC SDU and determining that the MAC SDU's checksum has failed, the terminal passes the MAC SDU to the RLC layer for subsequent processing.

[0296] In some embodiments, for the terminal, for the TB or MAC SDU that allow error transmission in the above embodiments, the terminal can also trigger retransmission of these data. The number of retransmissions can be set to be less than a first threshold. The first threshold can be the number of retransmissions in a regular HARQ retransmission, such as 5 times, 8 times, etc. The specific value can be determined according to the actual situation, and this application embodiment does not limit it. This achieves the goal of triggering fewer retransmissions for TB or MAC SDU that allow error transmission. Of course, for the data caching involved in the HARQ retransmission process, the data caching time can also be less than a second threshold. The second threshold can be the data caching duration in a regular HARQ retransmission, such as 10 seconds, 5 minutes, etc. The specific caching duration can be determined according to the actual situation, and this application embodiment does not limit it. Of course, the terminal can inform the RLC layer of the MAC layer's caching duration so that the RLC layer can wait for retransmitted data based on the caching duration. For cases where the caching duration is exceeded, subsequent processing can be directly performed on the erroneous data.

[0297] In some examples, the importance of a TB (Transmission Block) or a MAC SDU (Multi-User Code for MAC) that allows error transmission can also be indicated. For example, a first identifier can indicate the importance of different TBs, and TBs of certain importance can be considered as TBs that do not allow error transmission. Conversely, TBs of other importance can be considered as TBs that allow error transmission. For instance, the importance of a TB can be divided into five levels, such as levels 1 to 5, with higher levels indicating higher importance. For example, in scenario 1, TBs of levels 1 to 3 are TBs that allow error transmission; and in scenario 2, only TBs of level 1 are TBs that allow error transmission. In other examples, lower levels may indicate higher importance, which is not limited in this embodiment. Furthermore, the specific levels of TBs that allow error transmission can be flexibly adjusted according to actual circumstances, which is not limited in this embodiment. Similarly, for MAC SDUs that allow error transmission, different levels of importance can indicate whether different levels of MAC SDUs allow error transmission, which will not be elaborated further in this embodiment.

[0298] Method B:

[0299] The first information may include QoS flow identification information. For example, this QoS flow identification information can be used to indicate a first QoS flow. This first QoS flow can be used to transmit the first data packet and the first information. It can be considered that the first QoS flow is a QoS flow that allows for error transmission. For example, the first core network element can configure a separate QoS flow, such as the first QoS flow, for the received first data packet. See [reference needed] for details. Figure 3 The diagram illustrates the QoS flow in the GTP-U tunnel between the UPF and RAN. For example, QoS flow identification information can be used to identify the QoS flow corresponding to different data packets. A separate QoS flow can then be configured specifically for transmitting data packets that are allowed to be transmitted incorrectly; this type of QoS flow can be called the first QoS flow. The first core network element transmits the first data packet and the QoS flow identification information through the first QoS flow. The access network device can determine that the first data packet is a data packet in the first QoS flow based on the QoS flow identification information, thereby determining that the first data packet is a data packet that is allowed to be transmitted incorrectly.

[0300] In this scenario, the first data packet can be considered to be transmitted through a separate QoS stream (i.e., the first QoS stream). Therefore, all data packets included in this first QoS stream can be considered as data packets allowed to be transmitted with errors (i.e., the first data packet). The access network device can determine to use the first transmission mechanism to transmit the data packets included in the first QoS stream. Optionally, the access network device can use the first transmission mechanism to transmit all data packets of the first QoS stream. Optionally, the access network device can determine to use the first transmission mechanism to transmit the first data packet based on the first QoS stream identifier or based on the fact that the data packet originates from the first QoS stream.

[0301] In some cases, the first core network element can determine that the received data packet is the first data packet. Therefore, the first core network element can place the first data packet in a separate QoS stream, i.e., the first QoS stream. For example, the first core network element can indicate the first QoS stream through QoS stream identification information. The first core network element then sends the received first data packet through the first QoS stream. The first core network element's indication of the first QoS stream through QoS stream identification information achieves the indication of the first data packet.

[0302] In some cases, access network devices can be configured according to... Figure 4 The method shown describes the processing of the first data packet sent by the first core network element. The first data packet sent by the first core network to the access network device can be understood as... Figure 4 The access network device adds headers for each protocol layer sequentially according to a certain protocol layer order, up to the MAC layer. For example, during MAC layer processing, the access network device can add indication information to the header or TB header of the MAC SDU containing the first data packet. For example, depending on the implementation, the indication information may include first indication information and / or second indication information. The access network device can send the TB generated based on the first data packet to the terminal through the first QoS flow. It is understood that although data that allows erroneous transmission is sent through the first QoS flow in method B, indication information can still be added to the header or TB header of such data, such as the MAC SDU, to indicate that the MAC SDU and / or TB includes data that allows erroneous transmission. The specific implementation process can be referred to the description of method A, which will not be repeated in the embodiments of this application. Accordingly, the first QoS flow can correspond to a separate HARQ process or HARQ entity.

[0303] Access network devices can use RRC signaling or DCI to instruct the data packets of the HARQ process or HARQ entity to be submitted to subsequent protocol layers for processing if the data packet fails verification at a certain protocol layer. Similar to the corresponding embodiment in Method A, the terminal can also perform HARQ retransmission on the data packets of the HARQ process or HARQ entity. However, the number of retransmissions can be less than a first threshold, and the data buffering time can be less than a second threshold. For details, please refer to the description of the foregoing embodiments; this application's embodiments will not repeat them.

[0304] In some embodiments, for communication scenarios of mode A, the PDR can refer to the relevant descriptions in Tables 1 and 2 of the foregoing embodiments. For communication scenarios of mode B, the PDR corresponding to Table 1 can be replaced by Table 3, and the PDR corresponding to Table 2 can be replaced by Table 4. The specific implementation process can be referred to the description of the foregoing embodiments, and will not be repeated in the embodiments of this application.

[0305] Table 3

[0306] PDR Packet inspection information (wildcards, IP 5-tuples, IP 3-tuples, etc.) The first data packet's characteristic information (such as the XXth bit of the RTP header). QER logo ……

[0307] Table 4

[0308] PDR Packet inspection information (wildcards, IP 5-tuples, IP 3-tuples, etc.) QER logo ……

[0309] The QER identifiers in Tables 3 and 4 above can be used to index specific QERs. Accordingly, a QER can include corresponding rules, such as enabling the first QoS flow with misdelivered packets.

[0310] This application provides multiple implementations of the first information so that the first information can be indicated in a way that is appropriate for the communication scenario in different communication scenarios, thereby improving universality.

[0311] This application embodiment sends first information to the access network device to instruct the access network device to transmit data packets that are allowed to be transmitted erroneously using a first transmission mechanism. This allows the access network device to identify data packets that are allowed to be transmitted erroneously using the first information and to perform subsequent operations on such data packets. This avoids retransmitting data packets that are allowed to be transmitted erroneously, thus improving communication efficiency.

[0312] The above-described solution of this application will now be described in conjunction with more specific embodiments.

[0313] Figure 6 This is a schematic diagram of a communication signaling interaction provided for an embodiment of this application.

[0314] This communication process may be applicable to, but is not limited to, the following: Figure 1 , Figure 2 In the communication scenario shown. Figure 6 The signaling interaction process shown can be considered as a... Figure 5 A more detailed description of the method is provided below. In this embodiment, the terminal device is the UE, the access network device is the RAN, the first core network element is the UPF, the second core network element is the SMF, and the third core network element is the PCF. This signaling interaction process may also involve network elements such as UDM and AF / AS. Figure 6 The communication interaction process shown is described using the example of UPF indicating the second information for each first data packet.

[0315] The method may include the following steps:

[0316] S201, the UE sends a PDU session establishment request to the SMF.

[0317] For example, S201 is an optional step.

[0318] S202, SMF obtains UE's subscription information from UDM.

[0319] For example, S202 is an optional step.

[0320] S203, AF / AS sends the sixth message to PCF. Correspondingly, PCF receives the sixth message from AF / AS.

[0321] For example, the sixth piece of information could be an AF request, used to instruct the service and / or UE to enable error packet delivery.

[0322] Optionally, the sixth information may also indicate the characteristics of the data packet that is allowed to be transmitted erroneously, i.e., the characteristics of the first data packet.

[0323] For example, S203 is an optional step.

[0324] S204, the PCF sends policy information to the SMF. Correspondingly, the SMF receives the policy information from the PCF.

[0325] S205, the SMF sends a third message to the UPF. Correspondingly, the UPF receives the third message from the SMF.

[0326] For example, the SMF can instruct the UPF to mark the first data packet using third information based on the policy information sent by the PCF. This allows the RAN to instruct the RAN to use the first transmission mechanism to transmit the first data packet. Optionally, the third information may include the characteristic information of the first data packet.

[0327] S206, the SMF sends the fourth message to the RAN. Correspondingly, the RAN receives the fourth message from the SMF.

[0328] S207, the RAN sends a first response message to the SMF. Correspondingly, the SMF receives the first response message from the RAN.

[0329] For example, the SMF can use the fourth message to instruct / authorize the RAN to enable packet misdelivery for the session; or, it can authorize packet misdelivery to be enabled for one or more QoS flows. After being instructed / authorized by the SMF, the RAN can then execute subsequent related steps upon receiving the first message from the UPF. Alternatively, if the RAN is not authorized, it will not execute subsequent related steps upon receiving the first message from the UPF.

[0330] For example, steps S206 and S207 are optional. Since it can be assumed that the RAN receives the first UPF message by default, it can execute subsequent related steps, which can be understood as similar to enabling the error packet delivery function by default.

[0331] Optionally, the RAN can decide whether to accept or refuse to enable error packet delivery based on its own capabilities, load, and other factors.

[0332] S208, the SMF sends the fifth message to the UE. Accordingly, the UE receives the fifth message from the SMF.

[0333] S209, the RAN sends the seventh information to the UE. Accordingly, the UE receives the seventh information from the RAN.

[0334] Understandably, S208 and S209 can choose to execute either one, or neither, or both.

[0335] S210, AF / AS sends the first data packet to UPF. Correspondingly, UPF receives the first data packet from AF / AS.

[0336] S211, UPF determines the first information.

[0337] In step S212, the UPF sends the first data packet and the first information to the RAN. Correspondingly, the RAN receives the first data packet and the first information from the UPF.

[0338] S213, the RAN adds a first indication information to the TB header, or adds a second indication information to the MAC SDU header.

[0339] S214, the RAN sends a first data packet to the UE using the first transmission mechanism. Accordingly, the UE receives the first data packet from the RAN.

[0340] S215, the UE submits the first data packet that failed the verification to the subsequent protocol layer.

[0341] It is understood that the specific implementation process of each step in S201 to S215 above can be referred to the description of each embodiment in S101 to S103 above, and will not be repeated in the embodiments of this application.

[0342] This application embodiment addresses scenarios that support packet error delivery. The UPF can carry first information in the header of each first data packet to instruct the RAN to enable packet error delivery for that data packet. This allows the first transmission mechanism to prevent the error transmission of such data packets and service flows, improving communication efficiency.

[0343] Figure 7 This is another schematic diagram of communication signaling interaction provided for an embodiment of this application.

[0344] This communication process may be applicable to, but is not limited to, the following: Figure 1 , Figure 2 In the communication scenario shown. Figure 7 and Figure 6 Similar, the difference lies in Figure 7 The UPF configures a separate QoS flow for the first data packet, such as a first QoS flow. This method may include the following steps:

[0345] S301, the UE sends a PDU session establishment request to the SMF.

[0346] S302, SMF obtains UE's subscription information from UDM.

[0347] S303, AF / AS sends the sixth message to PCF. Correspondingly, PCF receives the sixth message from AF / AS.

[0348] S304, the PCF sends policy information to the SMF. Correspondingly, the SMF receives the policy information from the PCF.

[0349] It is understood that the implementation process of S301 to S304 is similar to that of S201 to S204, and will not be described again in the embodiments of this application.

[0350] S305, the SMF sends a third message to the UPF. Correspondingly, the UPF receives the third message from the SMF.

[0351] Understandably, the implementation process of S305 is similar to that of S205. The difference lies in that in S305, the SMF instructs the UPF to bind (place) the first data packet into a separate (or specific) QoS flow through third information, so as to instruct the RAN to perform error packet delivery. In other words, it lets the RAN know that error packet delivery should be performed for all packets in this QoS Flow.

[0352] Of course, some of the implementation methods in S305 are the same as those in S205, and will not be described again in this application embodiment.

[0353] S306, the SMF sends the fourth message to the RAN. Correspondingly, the RAN receives the fourth message from the SMF.

[0354] S307, the RAN sends a first response message to the SMF. Correspondingly, the SMF receives the first response message from the RAN.

[0355] For example, the SMF can use the fourth message to instruct the RAN to enable error packet delivery for one or more QoS flows. This allows the RAN to perform subsequent related steps upon receiving all packets for that QoS flow.

[0356] Of course, step S306 is a necessary step to be performed in this embodiment, because the SMF needs to inform the RAN which QoS flows are the first QoS flows.

[0357] It is understood that some of the implementation methods in S306 and S307 are the same as those in S206 and S207, and will not be repeated in the embodiments of this application.

[0358] S308, the SMF sends the fifth message to the UE. Correspondingly, the UE receives the fifth message from the SMF.

[0359] S309, the RAN sends the seventh information to the UE. Accordingly, the UE receives the seventh information from the RAN.

[0360] It is understood that the implementation process of S308 and S309 is similar to that of S208 and S209. The difference lies in which the fifth and seventh information indicate which QoS flows are the first QoS flows. This application embodiment will not elaborate further.

[0361] S310, AF / AS sends the first data packet to UPF. Correspondingly, UPF receives the first data packet from AF / AS.

[0362] S311, UPF determines the first information.

[0363] In step S312, the UPF sends the first data packet and the first information to the RAN. Correspondingly, the RAN receives the first data packet and the first information from the UPF.

[0364] For example, when the UPF receives the first data packet (such as the downstream data packet), it can identify the first data packet based on its characteristic information. The UPF can then bind (place) the first data packet into the first QoS flow. Alternatively, the UPF can bind (place) all data packets of a certain service flow or QoS flow into the first QoS flow. This allows the RAN to determine whether to enable error packet delivery based on whether the QoS flow is the first QoS flow.

[0365] Of course, some of the implementation methods in S310 to S312 are the same as those in S210 to S212, and will not be described again in the embodiments of this application.

[0366] S313, the RAN puts the first data packet into a separate HARQ process.

[0367] S314, the RAN sends the eighth message to the UE. Accordingly, the UE receives the eighth message from the RAN.

[0368] S315, the RAN sends a first data packet to the UE using the first transmission mechanism. Correspondingly, the UE receives the first data packet from the RAN.

[0369] S316, the UE submits the first data packet that failed the verification to the subsequent protocol layer.

[0370] Understandably, the implementation process of S313 to S316 is similar to that of S213 to S215, the difference being that the RAN places this type of first data packet in a separate HARQ process at the MAC layer. This separate HARQ process corresponds to the first QoS flow and can be considered as the HARQ process for that first QoS flow. The RAN can instruct the UE via RRC signaling or DCI that this HARQ process can continue to be submitted to subsequent protocol layers even if the verification fails.

[0371] Regarding UE implementation methods and Figure 6 The implementation methods of the UE are similar, and will not be described again in the embodiments of this application.

[0372] Of course, some of the implementations in S313 to S316 are the same as those in S213 to S215, and will not be described again in the embodiments of this application.

[0373] This application embodiment addresses scenarios that support packet error delivery. The UPF can bind (place) the first data packet into (or place) a first QoS flow to instruct the RAN to enable packet error delivery in that first QoS flow. This allows the first transmission mechanism to handle such data packets and service flows with errors, improving communication efficiency.

[0374] For information involving interaction between different network elements (or devices) in various embodiments of this application, the information can be sent directly between different network elements (or devices) or forwarded via other network elements (or devices). Accordingly, in the process of forwarding information via one or more other network elements (or devices), the function of the information is the same, and the format, structure, and content of the information are allowed to change. This application does not limit the scope of the embodiments.

[0375] It is understood that each of the above embodiments of this application can be implemented independently or in combination with each other; there is no absolute subordinate relationship between the embodiments, and they can be combined with each other under any conditions to obtain the corresponding effect.

[0376] It is understood that, in order to achieve the functions in the above embodiments, the terminal device and network device include hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0377] Figure 8 and Figure 9 This is a schematic diagram of a possible communication device provided for embodiments of this application. The communication device may include modules or units for implementing the solutions in the above method embodiments. These communication devices can be used to implement the functions of terminals, access network devices, or core network elements in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be as follows: Figure 1 The RAN node 110 shown can also be referred to as an access network device, access network apparatus, or network apparatus. This communication apparatus can also be as follows: Figure 1 The core network 200 shown is a network element. This communication device can also be a module (such as a chip) applied to a core network element. This communication device can also be a module (such as a chip) applied to access network equipment. This communication device can also be... Figure 1 The terminal device 120 shown. This communication device can also be a module (such as a chip) applied to the terminal.

[0378] In this embodiment, the device for implementing terminal functions can be a terminal or a device capable of supporting the terminal in implementing these functions, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal. In this embodiment, the device for implementing access network functions can be an access network device or a device capable of supporting the access network device in implementing these functions, such as a chip system. This device can be installed in the access network device or used in conjunction with the access network device. In this embodiment, the device for implementing core network functions can be a core network element or a device capable of supporting the core network element in implementing these functions, such as a chip system. This device can be installed in the core network element or used in conjunction with the core network element.

[0379] In this embodiment of the application, the chip system may be composed of chips, or it may include chips and other discrete devices.

[0380] like Figure 8 As shown, the communication device 800 includes a processing unit 810 and a transceiver unit 820. The communication device 800 is used to implement the above-mentioned... Figure 5 , Figure 6 , Figure 7 The methods illustrated in this embodiment include the functions of the terminal, access network equipment, and core network elements.

[0381] When the communication device 800 is used to implement Figure 5 In the method embodiment shown, the functions of the first core network element are as follows: the transceiver unit 820 is used to receive the first data packet. The transceiver unit 820 is also used to send the first information to the access network device. The processing unit 810 is used to perform operations other than the transceiver function.

[0382] When the communication device 800 is used to implement Figure 5 In the method embodiment shown, the function of the second core network element is as follows: the transceiver unit 820 is used to receive policy information from the third core network element. The transceiver unit 820 is also used to send third information to the first core network element. The processing unit 810 is used to perform operations other than the transceiver function.

[0383] When the communication device 800 is used to implement Figure 5 In the method embodiment shown, the access network device functions as follows: the transceiver unit 820 receives first information from a first core network element. The processing unit 810 controls the transceiver unit 820 to send a first data packet to the terminal using a first transmission mechanism.

[0384] For a more detailed description of the aforementioned processing unit 810 and transceiver unit 820, please refer to [reference needed]. Figure 5 , Figure 6 , Figure 7 The following is a description of the method embodiments shown.

[0385] like Figure 9 As shown, the communication device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 can be a transceiver or an input / output interface. Optionally, the communication device 900 may also include a memory 930 for storing instructions executed by the processor 910, or storing input data required for the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions. Sometimes, the interface circuit 920 can also be understood as part of the processor 910, in which case the communication device 900 includes the processor 910.

[0386] When the communication device 900 is used to implement Figure 5 , Figure 6 , Figure 7 In the method shown, the processor 910 is used to implement the functions of the processing unit 810, and the interface circuit 920 is used to implement the functions of the transceiver unit 820.

[0387] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. For example, when the terminal chip receives information from an access network device, it can be understood that the information is first received by other modules (such as an RF module or antenna) in the terminal, and then sent to the terminal chip by these modules. When the terminal chip sends information to the access network device, it can be understood that the information is sent down to other modules (such as an RF module or antenna) in the access network device, and then sent back to the access network device by these modules. As another example, when the terminal chip receives information from a core network element, it can be understood that the information is first received by other modules (such as an RF module or antenna) in the terminal, and then sent to the terminal chip by these modules. When the terminal chip sends information to a core network element, it can be understood that the information is sent down to other modules (such as an RF module or antenna) in the core network element, and then sent back to the core network element by these modules.

[0388] When the aforementioned communication device is a chip applied to an access network device, the access network device chip implements the functions of the access network device in the above method embodiments. For example, when the access network device chip receives information from a terminal, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in the access network device, and then sent to the access network device chip by these modules. When the access network device chip sends information to the terminal, it can be understood that the information is sent down to other modules (such as radio frequency modules or antennas) in the terminal, and then sent to the terminal by these modules. As another example, when the access network device chip receives information from a core network element, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in the access network device, and then sent to the access network device chip by these modules. When the access network device chip sends information to a core network element, it can be understood that the information is sent down to other modules (such as radio frequency modules or antennas) in the core network element, and then sent to the core network element by these modules.

[0389] When the aforementioned communication device is a chip applied to a core network element, the core network element chip implements the functions of the core network element in the above method embodiments. For example, when the core network element chip receives information from an access network device, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in the core network element, and then sent to the core network element chip by these modules. When the core network element chip sends information to the access network device, it can be understood that the information is sent down to other modules (such as radio frequency modules or antennas) in the access network device, and then sent back to the access network device by these modules. As another example, when the core network element chip receives information from a terminal, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in the core network element, and then sent back to the core network element chip by these modules. When the core network element chip sends information to the terminal, it can be understood that the information is sent down to other modules (such as radio frequency modules or antennas) in the terminal, and then sent back to the terminal by these modules.

[0390] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminal devices, or modules within RAN nodes or terminal devices. Information transmission and reception can be between RAN nodes and terminal devices, such as between a base station and a terminal device; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal device chip and other modules of the terminal device, or between a base station chip and other modules of the base station.

[0391] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or one or more of other general-purpose processors, digital signal processors (DSPs), microprocessor units (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), artificial intelligence processors (AI processors), or neural processing units (NPUs); or, the processor mentioned in the embodiments of this application can be application-specific integrated circuits (ASICs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components (or parts), or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor, etc.

[0392] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in memory, such as volatile memory and / or non-volatile memory. The non-volatile memory can be flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM). The volatile memory can be a cache or random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes a variety of forms, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). The memory can also be in registers, hard disks, portable hard disks, compact disc (CD) ROMs, or any other form of storage medium well known in the art.

[0393] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal device. The processor and storage medium can also exist as discrete components in a base station or terminal device.

[0394] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0395] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0396] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0397] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0398] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0399] The terms "first" and "second," etc., used in the specification and drawings of the embodiments of this application are used to distinguish different objects or to distinguish different processing of the same object. The terms "first" and "second," etc., can distinguish identical or similar items with substantially the same function and effect. For example, "first device" and "second device" are merely to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first" and "second," etc., do not limit the quantity or execution order, and that "first" and "second," etc., do not necessarily imply that they are different.

[0400] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of the embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0401] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0402] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of the embodiments of this application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of the embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0403] It is understood that in the embodiments of this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a time, nor do they require a judgment action during implementation, nor do they imply any other limitations.

[0404] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0405] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined to form new embodiments, implementation methods, methods, or implementation approaches based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method is applied to a first core network element, and the method includes: Receive a first data packet, wherein the first data packet is a data packet that allows for error transmission; Send first information to the access network device, wherein the first information is used to instruct the access network device to transmit the first data packet using a first transmission mechanism.

2. The method according to claim 1, characterized in that, The first information is included in the header of the first data packet.

3. The method according to claim 1 or 2, characterized in that, The first information includes at least one of the following: The second information corresponding to the first data packet is used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet; or, Quality of Service (QoS) flow identification information, wherein the QoS flow identification information is used to indicate a first QoS flow, and the first QoS flow is used to transmit the first data packet and the first information.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Based on the characteristic information of the first data packet, it is determined that the first data packet is a data packet that allows erroneous transmission.

5. The method according to claim 4, characterized in that, The feature information is represented in at least one of the following ways: The feature information is included in the header of the first data packet; The feature information is the attribute information of the data packet; or, The feature information is determined based on artificial intelligence (AI) reasoning.

6. The method according to claim 5, characterized in that, The feature information is included in the header of the first data packet; determining that the first data packet is a data packet that allows error transmission based on the feature information of the first data packet includes: Based on the information in the protocol layer header of the first data packet and / or the protocol type of the first data packet, the first data packet is determined to be a data packet that allows erroneous transmission.

7. The method according to claim 6, characterized in that, Determine at least one of the following pieces of information based on the information contained in the protocol layer header: Internet Protocol (IP) quintuple; IP triplet; Business identifier; Application identifier; domain name; Session identifier; Terminal address information; Location information, which is used to indicate the first bit in the protocol layer header; or, The QoS channel corresponding to the data packet.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The system receives third information from a second core network element, wherein the third information is used to instruct the first core network element to send the first information to the access network device upon receiving the first data packet.

9. The method according to claim 8, characterized in that, The third information includes the characteristic information of the first data packet.

10. A communication method, characterized in that, The method is applied to a second core network element, and the method includes: Receive policy information from a third core network element, the policy information being used to indicate that a first service includes a first data packet, and / or the policy information being used to indicate that a first session transmits the first data packet, wherein the first data packet is a data packet that is allowed to be transmitted incorrectly; Send a third message to a first core network element, wherein the third message is used to instruct the first core network element to send a first message to the access network device upon receiving a first data packet, and the first message is used to instruct the access network device to transmit the first data packet using a first transmission mechanism.

11. The method according to claim 10, characterized in that, The policy information and / or third information are used to indicate the characteristic information of the first data packet, wherein the characteristic information of the first data packet is used by the first core network element to determine the data packet that is allowed to be transmitted erroneously.

12. The method according to claim 11, characterized in that, The feature information is represented in at least one of the following ways: The feature information is included in the header of the first data packet; The feature information is the attribute information of the data packet; or, The feature information is determined by the first core network element based on artificial intelligence (AI) reasoning.

13. The method according to claim 12, characterized in that, The feature information is included in the header of the first data packet; the feature information is related to at least one of the following: Information contained in the protocol layer header; or, The protocol type of the data packet.

14. The method according to claim 13, characterized in that, At least one of the following pieces of information is determined based on the information contained in the protocol layer header: Internet Protocol (IP) quintuple; IP triplet; Business identifier; Application identifier; domain name; Session identifier; Terminal address information; Location information, which is used to indicate the first bit in the protocol layer header; or, The QoS channel corresponding to the data packet.

15. The method according to any one of claims 10-14, characterized in that, The method further includes: Send a fourth message to the access network device, the fourth message being used to instruct the access network device to enable the first transmission mechanism for the first QoS flow or the first session.

16. The method according to any one of claims 10-15, characterized in that, The method further includes: A fifth message is sent to the terminal, the fifth message being used to instruct the terminal to enable the first transmission mechanism for the first QoS stream or the first session.

17. The method according to any one of claims 10-16, characterized in that, The policy information is determined by the third core network element based on the sixth information, wherein the sixth information is used to indicate the services that are allowed to execute the first transmission mechanism or the terminals that are allowed to execute the first transmission mechanism.

18. The method according to claim 17, characterized in that, The sixth piece of information includes the characteristic information of the first data packet.

19. A communication method, characterized in that, The method is applied to an access network device, and the method includes: Receive first information from a first core network element, wherein the first information is used to instruct the access network device to transmit the first data packet using a first transmission mechanism, and the first data packet is a data packet that allows error transmission; The first data packet is sent to the terminal using the first transmission mechanism.

20. The method according to claim 19, characterized in that, The method further includes: Receive the first data packet from the first core network element.

21. The method according to claim 19 or 20, characterized in that, The first information is included in the header of the first data packet.

22. The method according to any one of claims 19-21, characterized in that, The first information includes at least one of the following: The second information corresponding to the first data packet is used to indicate that the access network device uses the first transmission mechanism to transmit the first data packet; or, Quality of Service (QoS) flow identification information, wherein the QoS flow identification information is used to indicate a first QoS flow, and the first QoS flow is used to transmit the first data packet and the first information.

23. A communication device, characterized in that, Includes a module for performing the method according to any one of claims 1-22.

24. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1-22 through logic circuits, executable code and / or instructions.

25. The apparatus according to claim 24, characterized in that, The device further includes a memory for storing the code or instructions.

26. A chip, characterized in that, include: At least one processor, the at least one processor being coupled to a memory for storing a program or instructions, the processor being configured to execute the program or instructions such that the chip performs the method as described in any one of claims 1 to 22.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-22.

28. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1-22.

Images