Communication method and device

Abstract

The present application relates to a communication method and device. The method comprises: a terminal device receiving downlink data, wherein the downlink data carries a reverse mapping identifier; and on the basis of first-protocol-layer header information and second-protocol-layer header information of the downlink data, the terminal device generating a QoS rule for uplink data, wherein a first protocol layer comprises at least one of an IP layer, a TCP layer, and a UDP layer. The embodiments of the present application can improve the accuracy of performing QoS control over data streams.

Description

Communication methods and devices Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] In existing networks, supporting various new services may lead to complex and frequently updated Quality of Service (QoS) rules configured for UEs. Therefore, a reverse mapping QoS control mechanism has been introduced. The main idea of ​​the reverse mapping mechanism is to add a QoS Flow Identifier (QFI) and a reverse mapping indication to the downlink data packet header. The UE then generates its own QoS rules based on the received downlink data for uplink data transmission. Ensuring that the QoS rules generated by the terminal can correctly control uplink data is a key technical problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a communication method and device.

[0005] This application provides a communication method, including:

[0006] The terminal device receives downlink data, which carries a reverse mapping identifier;

[0007] The terminal device generates QoS rules for uplink data based on the first and second protocol layer header information of the downlink data; wherein,

[0008] The first protocol layer includes at least one of the IP layer, TCP layer, and UDP layer.

[0009] This application provides a communication method, including:

[0010] The first network element receives the downlink data stream;

[0011] The first network element uses IP data flow filters and additional data flow filters to identify the downlink data flow, and adds QoS flow identifiers and reverse mapping identifiers to the packet header of the downlink data flow;

[0012] The first network element sends the downlink data stream.

[0013] This application provides a communication method, including:

[0014] The third network element sends PCC rules, which include IP data flow filters and additional data flow filters for downlink data, as well as IP data flow filters and additional data flow filters for uplink data.

[0015] This application provides a terminal device, including:

[0016] The first transceiver module is used to receive downlink data, which carries a reverse mapping identifier.

[0017] The first processing module is used to generate QoS rules for uplink data based on the first protocol layer header information and the second protocol layer header information of the downlink data; wherein...

[0018] The first protocol layer includes at least one of the IP layer, TCP layer, and UDP layer.

[0019] This application provides a first network element, including:

[0020] The second transceiver module is used to receive downlink data streams and send the downlink data streams.

[0021] The second processing module is used to identify the downlink data stream using IP data stream filters and additional data stream filters, and to add QoS flow identifiers and reverse mapping identifiers to the packet header of the downlink data stream.

[0022] This application provides a third network element, including:

[0023] The third transceiver module is used to send PCC rules, which include IP data stream filters and additional data stream filters for downlink data, as well as IP data stream filters and additional data stream filters for uplink data.

[0024] This application provides a terminal device, including a transceiver, a processor, and a memory. The memory stores computer programs, the transceiver communicates with other devices, and the processor calls and runs the computer programs stored in the memory to enable the terminal device to perform the aforementioned communication method.

[0025] This application provides a network device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the network device to perform the aforementioned communication method.

[0026] This application provides a chip for implementing the above-described communication method.

[0027] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned communication method.

[0028] This application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to perform the aforementioned communication method.

[0029] This application provides a computer program product, including computer program instructions that cause a computer to execute the above-described communication method.

[0030] This application provides a computer program that, when run on a computer, causes the computer to perform the aforementioned communication method.

[0031] In this embodiment of the application, after receiving downlink data, the terminal device can perform reverse mapping on both the first protocol layer and the second protocol layer to generate QoS rules for uplink data, thereby ensuring normal QoS control. Attached Figure Description

[0032] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.

[0033] Figure 2A shows the 5G system architecture using the network element interface mode in the core network.

[0034] Figure 2B shows the 5G system architecture in which the core network adopts a service model using network elements.

[0035] Figure 3 is a multi-layer protocol framework diagram.

[0036] Figure 4 is a schematic flowchart of a communication method 400 according to an embodiment of this application.

[0037] Figure 5 is a schematic flowchart of a communication method 500 according to an embodiment of this application.

[0038] Figure 6 is a schematic diagram of the RTP protocol data packet header format.

[0039] Figure 7 is a flowchart of the implementation of Embodiment 1 of this application.

[0040] Figure 8 is a schematic flowchart of a communication method 800 according to an embodiment of this application.

[0041] Figure 9 is a flowchart of the implementation of Embodiment 2 of this application.

[0042] Figure 10 is a schematic block diagram of a terminal device 1000 according to an embodiment of the present application.

[0043] Figure 11 is a schematic block diagram of a first network element 1100 according to an embodiment of this application.

[0044] Figure 12 is a schematic block diagram of a third network element 1200 according to an embodiment of this application.

[0045] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of this application.

[0046] Figure 14 is a schematic structural diagram of a chip 1400 according to an embodiment of this application. Detailed Implementation

[0047] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0048] The technical solutions of this application embodiment can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Non-Terrestrial Networks (NTN) systems, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) systems, or other communication systems.

[0049] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0050] In one implementation, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0051] In one embodiment, the communication system in this application can be applied to unlicensed spectrum, wherein the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application can also be applied to licensed spectrum, wherein the licensed spectrum can also be considered as non-shared spectrum.

[0052] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0053] Terminal devices can be stations (STAION, ST) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0054] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).

[0055] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0056] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0057] In the embodiments of this application, the network device can be a device for communicating with mobile devices, such as an access point (AP) in a WLAN, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.

[0058] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located on land, water, or other similar locations.

[0059] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0060] Figure 1 illustrates an exemplary communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include other numbers of terminal devices 120; this embodiment does not limit the scope of the present application.

[0061] In one embodiment, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application.

[0062] Network equipment can be further divided into access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with the access network equipment. Access network equipment can be evolved Node Bs (eNBs or e-NodeBs) in Long-Term Evolution (LTE), Next-Generation Radio (NR) (mobile communication system), or Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) systems, such as macro base stations, micro base stations (also called "small base stations"), pico base stations, access points (APs), transmission points (TPs), or new generation Node Bs (gNodeBs).

[0063] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system shown in Figure 1 as an example, the communication device may include network devices and terminal devices with communication functions. The network devices and terminal devices can be specific devices in this application embodiment, which will not be described in detail here. The communication device may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely 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. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0065] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0066] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0067] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0068] The 5G network system architecture is shown in Figures 2A and 2B. In Figure 2A, core network elements are connected in pairs via agreed-upon interfaces. In Figure 2B, core network elements interact by calling services provided by the network elements. This invention does not limit the interface method or service call mode used between network elements. Specifically, the UE connects to the AN via the Uu interface for access layer communication, exchanging access layer messages and radio data transmission. The UE connects to the AMF via the N1 interface for non-access layer (NAS) communication, exchanging NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function. In addition to managing the UE's mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The UPF is the user plane function in the core network, transmitting data with the external data network via the N6 interface and with the AN via the N3 interface.

[0069] 5G networks perform QoS control at the flow level, where a single QoS flow can include multiple service data flows. For downlink packets, the UPF matches received downlink packets with service data flow filters to determine the QoS flow to which the service data flow belongs, thus enabling the network to perform QoS control on the QoS flow. For uplink packets, the UE matches the uplink packets it needs to send with service data flow filters to determine the QoS flow to which the service data flow belongs, again enabling the network to perform QoS control on the QoS flow. Service data flow filters are, for example, packet header fields in the Internet Protocol (IP) or Transmission Control Protocol (TCP), such as IP 5-tuple information including IP address and port number. The uplink service data flow filter is sent to the UE by the SMF located in the core network via control signaling, and is included in the QoS rules received by the UE. The UE uses the QoS rules to match uplink service data, mapping the uplink service data to the appropriate QoS flow for QoS control. In 5G networks, supporting various new services may lead to complex QoS rule construction and frequent updates for UEs. Therefore, a reverse mapping QoS control mechanism has been introduced in 5G networks. The main idea is to add a QoS Flow Identifier (QFI) and a reverse mapping indication to the downlink data packet header. The UE generates its own QoS rules based on the received downlink data for uplink data transmission, thereby reducing signaling interaction between the SMF and the UE.

[0070] For some new application-layer services, such as AR / VR / cloud gaming / artificial intelligence interactive services, multiple media streams, such as voice, video, and haptic feedback, may use the same transport layer connection. This means multiple media streams are multiplexed into a transport layer connection with the same IP 5-tuple. In this case, it is necessary to introduce protocol layer information above IP / TCP to further distinguish between the multiple media streams. As shown in the multi-layer protocol framework diagram in Figure 3, protocol layer information such as Real-Time Transport Protocol (RTP) / Real-Time Transport Control Protocol (RTCP) can be introduced to further differentiate the media streams. The current 5GS QoS framework cannot support differentiated QoS for multiple media streams in the above scenarios. In particular, the reverse mapping mechanism in the current 5GS QoS framework does not support reverse mapping for protocol layers above the IP layer. If the network uses protocol layers above the IP layer to distinguish multiple media streams, while the UE only performs reverse mapping for the IP / TCP protocol layer, it will cause confusion in the QoS control of uplink data streams for multiple media streams in the above scenarios. Downlink media streams transmitted in different QoS streams will be transmitted in the same QoS stream for uplink, making normal QoS control impossible and affecting user experience.

[0071] Figure 4 is a schematic flowchart of a communication method 400 according to an embodiment of this application. This method can optionally be applied to any of the systems shown in Figures 1-3, but is not limited thereto. The method includes at least a portion of the following:

[0072] S410. The terminal device receives downlink data, which carries a reverse mapping identifier.

[0073] S420. The terminal device generates QoS rules for uplink data based on the first protocol layer header information and the second protocol layer header information of the downlink data; wherein,

[0074] The first protocol layer includes at least one of the IP layer, TCP layer, and User Datagram Protocol (UDP) layer.

[0075] In some examples, this second protocol layer includes protocol layers above the IP layer, TCP layer, and / or UDP layer.

[0076] In some examples, the second protocol layer includes at least one of the RTP layer, the RTCP layer, and the Secure Real-time Transport Protocol (SRTP) layer.

[0077] Subsequently, when the terminal device needs to send uplink data, it matches the QoS rules used for uplink data, and the uplink data can be transmitted through the correct QoS stream.

[0078] Through the above process, after receiving downlink data, the terminal device can perform reverse mapping on both the first and second protocol layers to generate QoS rules for uplink data, thereby ensuring that uplink and downlink data are mapped to the same QoS stream and guaranteeing normal QoS control.

[0079] In some examples, where the second protocol layer includes an RTP layer, the aforementioned second protocol layer header information may include the Synchronization Source Identifier (SSRC identifier) ​​and / or Payload Type (PT) from the RTP protocol packet header. That is, the terminal device can generate QoS rules for uplink data based on the packet header information of the IP layer or TCP / UDP layer, as well as the SSRC and / or PT of the RTP layer.

[0080] In some examples, the terminal device can generate an IP data stream filter for uplink data based on the first protocol layer header information, and generate an additional data stream filter for uplink data based on the second protocol layer header information.

[0081] For example, the additional data stream filter may include packet header information read from the second protocol layer.

[0082] In this embodiment, the IP data stream filter and the additional data stream filter generated by the terminal device can be parallel or inclusive.

[0083] For example, the QoS rules generated by the terminal device for uplink data may include QFI, IP data stream filters for uplink data, and additional data stream filters for uplink data. That is, the two are parallel.

[0084] For example, the QoS rules generated by the terminal device for uplink data may include QFI and an IP data flow filter for uplink data, wherein the IP data flow filter for uplink data contains an additional data flow filter for uplink data. That is, the two are in a containment relationship.

[0085] This application also proposes a communication method. Figure 5 is a schematic flowchart of a communication method 500 according to an embodiment of this application. This method can optionally be applied to any of the systems shown in Figures 1-3, but is not limited thereto. The method includes at least a portion of the following:

[0086] S510, the first network element receives downlink data;

[0087] S520. The first network element uses IP data flow filter and additional data flow filter to identify the downlink data, and adds QoS flow identifier and reverse mapping identifier to the packet header of the downlink data;

[0088] S530, the first network element sends the downlink data.

[0089] The first network element may include a User Plane Function (UPF).

[0090] Through the above process, after the first network element identifies the downlink data, it adds a reverse mapping identifier to the downlink data and sends it to the terminal device, so that the terminal device can identify that the downlink data needs to be reverse mapped.

[0091] In some implementations, step S510 further includes: the first network element receiving an IP data flow filter, an additional data flow filter, a reverse mapping indication, and a QoS flow identifier for data transmission sent by the second network element. Using this information, the first network element can identify and add identifiers to downlink data.

[0092] The second network element may include a Session Management Function (SMF).

[0093] Regarding the communication methods shown in Figures 4 and 5 above, the following detailed description, in conjunction with the accompanying drawings, provides an example of a specific embodiment.

[0094] Example 1:

[0095] In this embodiment, the PCF located in the core network distinguishes between multiple data flows using the same transport layer connection and performs QoS control on each. For example, the data flow is a media flow. The PCF determines Policy and Charging Control (PCC) rules for each data flow, which include reverse mapping indications, IP data flow filters, and additional data flow filters.

[0096] IP service data flow filters include at least one of the following: IP layer packet header information and TCP / UDP layer packet header information. For example, IP service data flow filters include IP 5-tuple information, which includes the source IP address, source port number, destination IP address, destination port number, and transport protocol type (such as TCP).

[0097] Additional data stream filters include packet header information from the first protocol layer above the IP layer. For example, the first protocol layer can be a commonly used media data transmission protocol such as RTP, RTCP, SRTP, and / or SRTP; the packet header information from the first protocol layer is, for example, the Synchronization Source identifier (SSRC identifier) ​​and / or Payload Type (PT) information in the RTP protocol packet header. The format of the RTP protocol packet header is shown in Figure 6, and includes some or all of the following:

[0098] V: The version number of the RTP protocol, which is 2 bits long. The current version number is 2.

[0099] P: Padding flag, 1 bit in length;

[0100] X: Extended flag, 1 bit in length;

[0101] CC: CSRC counter, with a length of 4 bits or less, used to represent the number of CSRCs; when the length is 4 bits, it can represent up to 15 CSRCs; when the length is 3 bits, it can represent up to 7 CSRCs; and so on. If the length of CC is less than 4 bits, the length of other parts can be increased, such as increasing the length of P or X.

[0102] M: Flag bit, 1 bit in length;

[0103] PT: Payload type, 7 bits in length, used to describe the type of payload in the RTP message;

[0104] Sequence number: 16 bits in length, used to identify the sequence number of the RTP message sent by the sender. The sequence number increments by 1 for each message sent.

[0105] Timestamp: 32 bits in length, used to identify the sampling time of the first byte of the RTP message; the receiver uses the timestamp to calculate delay and jitter, and for synchronization control;

[0106] Synchronization Source Identifier (SSRC): 32 bits in length, used to identify the synchronization source. This identifier is randomly generated.

[0107] Contributing Source Identifier (CSRC): Each CSRC is 32 bits long, and there can be 0-15 CSRCs. Each CSRC identifies all the contributing sources contained in the payload of the RTP message.

[0108] In some implementations, the header of the RTP protocol includes some of the above-mentioned content, such as V, X, M, PT, sequence number, timestamp, SSRC, and a predetermined number of CSRCs.

[0109] Based on the PCC rules received from the PCF, the SMF sends the IP data flow filter, additional data flow filter, and reverse mapping indication for each data flow to the UPF, which then enables the reverse mapping mechanism in the user plane. After receiving the downlink data packet from the UPF, the UE generates QoS rules for uplink data based on the reverse mapping indication carried in the downlink data packet header. The QoS rules include the IP data flow filter and additional data flow filter for uplink data.

[0110] As shown in Figure 7, this embodiment includes the following steps:

[0111] S701: The Policy Control Function (PCF) distinguishes between multiple data streams (e.g., media streams in the background section) and performs QoS control on each. The PCF determines PCC rules for each data stream and sends them to a second network element (e.g., the SMF). The PCC rules include reverse mapping instructions, IP data stream filters, and additional data stream filters. A specific example is as follows:

[0112] For example, PCC rule a is used for data flow a, where the IP data flow filter is the IP 5-tuple {source IP address 1, source port number 1, destination IP address 2, destination port number 2, transport protocol type (e.g., TCP)}, and the additional data flow filter a is {SSRC1, PT1}.

[0113] For example, PCC rule b is used for data flow b, where the IP data flow filter is the same as the IP data flow filter of PCC rule a, which is the IP 5-tuple {source IP address 1, source port number 1, destination IP address 2, destination port number 2, transport protocol type (e.g., TCP)}, and the additional data flow filter b is {SSRC2, PT2}.

[0114] S702: The second network element (such as SMF) determines the QoS flow for transmitting each data flow based on the received PCC rules. For example, it determines that the data flow corresponding to PCC rule a will be transmitted through QoS flow 1, and the data flow corresponding to PCC rule b will be transmitted through QoS flow 2. The SMF sends the IP data flow filter, additional data flow filter, and reverse mapping indication for each data flow, as well as the QoS flow identifier for transmitting that data flow, to the first network element (such as UPF).

[0115] S703: For downlink data, the first network element (such as the UPF) identifies the corresponding data flow based on the IP data flow filter and additional data flow, and adds a QFI and reverse mapping identifier to the header of the data packet of the data flow, and sends the downlink data to the UE through the access network equipment. For example: The UPF uses the IP 5-tuple {source IP address 1, source port number 1, destination IP address 2, destination port number 2, transport protocol type (e.g., TCP)}, and the additional data flow filter a is {SSRC1, PT1}, to match the IP layer / TCP layer / RTP layer packet header of the received data, thereby identifying data flow a, and adding the QoS flow 1 QFIa and reverse mapping identifier to the header of the data packet of data flow a. UPF uses the IP 5-tuple {source IP address 1, source port number 1, destination IP address 2, destination port number 2, transport protocol type (e.g., TCP)} and an additional data flow filter b of {SSRC2, PT2} to match the IP layer / TCP layer / RTP layer packet headers of the received data, thereby identifying data flow b, and adding the QoS flow 2 QFIb and reverse mapping identifier to the packet header of data flow b.

[0116] S704: After receiving the downlink data packet, the UE determines, based on the reverse mapping identifier carried in the packet header, that it needs to generate QoS rules for the uplink data stream. The UE generates QoS rules for the uplink data stream based on the IP layer / TCP (or UDP) layer / first protocol layer packet header of the downlink data. Specifically, the UE generates an IP data stream filter for the uplink data based on the IP layer / TCP (or UDP) layer packet header information (source address, source port number, destination address, destination port number, transport protocol type) of the downlink data, and generates additional data stream filters for the uplink data based on the first protocol layer packet header information (SSRC, PT, etc.) of the downlink data. Example:

[0117] When a UE receives a downlink data packet belonging to data flow a, because the packet header of this downlink data packet carries a reverse mapping identifier, the UE decides to generate a QoS rule for uplink data. The QFI in this QoS rule uses the QFIa carried in the header of the downlink data packet. The IP data flow filter for uplink data in this QoS rule is set to {source IP address 2, source port number 2, destination IP address 1, destination port number 1, transport protocol type (e.g., TCP)}, and the additional data flow filter for uplink data in this QoS rule is set to {SSRC1, PT1}. In other examples, the IP data flow filter may contain additional data flow filters. For example, the UE generates a QoS rule for uplink data that includes a QFI and an IP data flow filter for uplink data, set to {source IP address 2, source port number 2, destination IP address 1, destination port number 1, transport protocol type (e.g., TCP), SSRC1, PT1}.

[0118] When the UE receives a downlink data packet belonging to data stream b, because the packet header carries a reverse mapping identifier, the UE decides to generate a QoS rule for uplink data. The QFI in this QoS rule uses the QFIb carried in the header of the downlink data packet. The IP data stream filter for uplink data in this QoS rule is set to {source IP address 2, source port number 2, destination IP address 1, destination port number 1, transport protocol type (e.g., TCP)}, and the additional data stream filter for uplink data in this QoS rule is set to {SSRC2, PT2}. In other examples, the IP data stream filter may contain additional data stream filters. For example, the UE generates a QoS rule for uplink data that includes a QFI and an IP data stream filter for uplink data, set to {source IP address 2, source port number 2, destination IP address 1, destination port number 1, transport protocol type (e.g., TCP), SSRC2, PT2}.

[0119] In this embodiment, the IP data stream filter and the additional data stream filter generated by the UE for uplink data can be parallel or inclusive (e.g., the IP data stream filter contains the additional data stream filter). For example, the QoS rule for uplink data generated by the terminal device includes a QFI, an IP data stream filter for uplink data, and an additional data stream filter for uplink data. As another example, the QoS rule for uplink data generated by the terminal device includes a QFI and an IP data stream filter for uplink data, wherein the IP data stream filter for uplink data contains the additional data stream filter for uplink data.

[0120] When a UE needs to send uplink data, it can be matched with the QoS rules generated by the UE for uplink data, and then the uplink data can be transmitted through the correct QoS stream.

[0121] This embodiment uses an IP data stream filter combined with an additional data stream filter to distinguish media streams, and carries a reverse mapping identifier in the downlink media stream packet header. The UE then generates QoS rules for uplink data based on the reverse mapping identifier. These QoS rules include both the IP data stream filter and the additional data stream filter for uplink data. This allows for the differentiation of uplink data from multiple media streams, ensuring transmission through the correct QoS stream.

[0122] The above example is an enhancement of the reverse mapping mechanism. When generating QoS rules for uplink data, the terminal device not only relies on the packet header information of the IP layer / TCP (or UDP) layer, but also on the packet header information of the upper protocol layer, such as the protocol layer above the IP layer, TCP layer and / or UDP layer.

[0123] This application also proposes a communication method in which a reverse mechanism is not employed, but rather the network side sends explicit QoS rules for matching uplink data flows to the terminal device. Figure 8 is a schematic flowchart of a communication method 800 according to an embodiment of this application. This method can optionally be applied to any of the systems shown in Figures 1-3, but is not limited thereto. The method includes at least a portion of the following.

[0124] S810, the third network element sends PCC rules, which include IP data flow filters and additional data flow filters for downlink data, as well as IP data flow filters and additional data flow filters for uplink data.

[0125] In one example, the PCC rule does not include a reverse mapping indication.

[0126] The third network element may include a Policy Control Function (PCF).

[0127] In this way, the PCC rules sent by the third network element do not instruct the terminal device to perform reverse mapping. Instead, they provide the terminal device with explicit IP data stream filters and additional data stream filters for uplink data, so that the data stream can be transmitted through the correct QoS rules, thereby improving the user experience.

[0128] In some implementations, the IP data stream filter includes packet header information of a first protocol layer, which includes at least one of the IP layer, TCP layer, and UDP layer.

[0129] In some implementations, the additional data stream filter includes packet header information of a second protocol layer, which includes protocol layers above the IP, TCP, and / or UDP layers.

[0130] For example, the second protocol layer includes at least one of the RTP layer, RTCP layer, and SRTP layer.

[0131] Taking the RTP layer as an example, the additional data stream filter may include SSRC and / or PT in the packet header of the RTP protocol.

[0132] Regarding the above communication method, the following detailed description, in conjunction with the accompanying drawings, provides an embodiment two.

[0133] Example 2:

[0134] The difference between this embodiment and Embodiment 1 is that, if the PCF determines to distinguish between multiple data streams using the same transport layer connection, it will not enable reverse mapping for these data streams. In other words, the reverse mapping indication in the PCC rule is mutually exclusive with the additional data stream filter. For cases where data stream distinction requires both IP layer and first protocol layer information, the network will send explicit QoS rules to the UE to match the uplink data stream.

[0135] As shown in Figure 9, this embodiment includes the following steps:

[0136] S901: The third network element (such as the PCF) determines to distinguish multiple data streams (the data stream is exemplified by the media stream in the background technology) and performs QoS control separately for each. The PCF determines PCC rules for each data stream and sends them to the SMF. The PCC rules include IP data stream filters and additional data stream filters. The PCC rules also include IP data stream filters and additional data stream filters for downlink data, and IP data stream filters and additional data stream filters for uplink data. When distinguishing multiple data streams using the same transport layer connection, that is, when the PCC rules include additional data stream filters, the PCC rules will not include reverse mapping indications.

[0137] S902: The SMF determines the QoS flow for each data flow based on the received PCC rules. The SMF sends the IP data flow filters and additional data flow filters for each data flow, as well as the QoS flow identifier for transmitting that data flow, to the UPF.

[0138] S903: For downlink data, the UPF identifies the corresponding data stream based on the IP data stream filter and additional data stream filter used for downlink data, and transmits the data stream through the corresponding QoS.

[0139] S904: The SMF also generates QoS rules for each uplink data stream. The QoS rules include IP data stream filters and additional data stream filters for uplink data, as well as a QoS stream identifier for transmitting the data stream. The SMF sends the QoS rules to the UE. Steps S904 and S902-S903 are not sequentially related.

[0140] S905: When the UE has uplink data to send, the UE uses the QoS rules for uplink data received from the SMF for matching, and then the uplink data can be transmitted through the correct QoS stream.

[0141] This embodiment uses an IP data stream filter combined with an additional data stream filter to distinguish media streams. When distinguishing multiple data streams using the same transport layer connection (i.e., when the PCC rule includes an additional data stream filter), the PCC rule does not include a reverse mapping indication. The PCC rule simultaneously includes IP data stream filters and additional data stream filters for downlink data, and IP data stream filters and additional data stream filters for uplink data. Therefore, the SMF can explicitly provide the UE with QoS rules for uplink data matching. This allows for the differentiation of uplink data from multiple media streams, ensuring transmission through the correct QoS stream.

[0142] This solution addresses the problem of QoS control confusion caused by multiple media streams being multiplexed into a transport layer connection with the same IP 5-tuple. The network uses protocol layers above the IP layer to distinguish between various media streams, while the UE only performs reverse mapping at the IP / TCP protocol layer. This results in uplink and downlink data of the same media stream being unable to be transmitted in the same QoS stream. With this solution, the UE can distinguish uplink data based on QoS rules explicitly provided by the SMF, or on QoS rules for uplink data generated by the UE itself using the reverse mapping mechanism, and transmit it through the correct QoS stream, thus improving the user experience.

[0143] Figure 10 is a schematic block diagram of a terminal device 1000 according to an embodiment of the present application. The terminal device 1000 may include:

[0144] The first transceiver module 1010 is used to receive downlink data, which carries a reverse mapping identifier.

[0145] The first processing module 1020 is used to generate QoS rules for uplink data based on the first protocol layer header information and the second protocol layer header information of the downlink data; wherein...

[0146] The first protocol layer includes at least one of the IP layer, TCP layer, and UDP layer.

[0147] In some examples, this second protocol layer includes the IP layer, TCP layer, and UDP layer, and / or more protocol layers.

[0148] In some implementations, the second protocol layer includes at least one of the RTP layer, the RTCP layer, and the SRTP layer.

[0149] In some implementations, the second protocol layer header information includes the SSRC and / or PT from the RTP protocol packet header.

[0150] In some implementations, the first processing module 1020 is configured to generate an IP data stream filter for uplink data based on the first protocol layer header information, and to generate an additional data stream filter for uplink data based on the second protocol layer header information.

[0151] In some implementations, the additional data stream filter includes packet header information read from the second protocol layer.

[0152] In some implementations, the QoS rules for uplink data include QFI, IP data stream filters for uplink data, and additional data stream filters for uplink data.

[0153] In some implementations, the QoS rules for uplink data include a QFI and an IP data stream filter for uplink data, wherein the IP data stream filter for uplink data includes an additional data stream filter for uplink data.

[0154] The terminal device 1000 of this application embodiment can implement the corresponding functions of the terminal device in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the terminal device 1000 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the terminal device 1000 of the application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0155] Figure 11 is a schematic block diagram of a first network element 1100 according to an embodiment of the present application. The first network element 1100 may include:

[0156] The second transceiver module 1110 is used to receive downlink data and send downlink data.

[0157] The second processing module 1120 is used to identify the downlink data using IP data flow filters and additional data flow filters, and to add QoS flow identifiers and reverse mapping identifiers to the packet header of the downlink data.

[0158] In some implementations, the second transceiver module 1110 is also used to receive IP data flow filters, additional data flow filters, reverse mapping indications, and QoS flow identifiers for data transmission sent by the second network element.

[0159] In some implementations, the first network element includes a UPF.

[0160] In some implementations, the second network element includes an SMF.

[0161] The first network element 1100 in this application embodiment can realize the corresponding function of the first network element in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the first network element 1100 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the first network element 1100 of the application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0162] Figure 12 is a schematic block diagram of a third network element 1200 according to an embodiment of the present application. The third network element 1200 may include:

[0163] The third transceiver module 1210 is used to send PCC rules, which include IP data stream filters and additional data stream filters for downlink data, as well as IP data stream filters and additional data stream filters for uplink data.

[0164] In some implementations, the PCC rule does not include a reverse mapping indication.

[0165] In some implementations, the IP data stream filter includes packet header information of a first protocol layer, which includes at least one of the IP layer, TCP layer, and UDP layer.

[0166] In some implementations, the additional data stream filter includes packet header information of a second protocol layer, which includes protocol layers above the IP, TCP, and / or UDP layers.

[0167] In some implementations, the second protocol layer includes at least one of the RTP layer, RTCP layer, SRTP layer, and SRTP layer.

[0168] In some implementations, additional data stream filters include SSRC and / or PT in the packet header of the RTP protocol.

[0169] In some implementations, the third network element includes a PCF.

[0170] The third network element 1200 in this application embodiment can realize the corresponding function of the third network element in the foregoing method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the third network element 1200 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the third network element 1200 of the application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0171] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of this application. The communication device 1300 includes a processor 1310, which can call and run computer programs from memory to enable the communication device 1300 to implement the methods in the embodiments of this application.

[0172] In one embodiment, the communication device 1300 may further include a memory 1320. The processor 1310 can retrieve and run computer programs from the memory 1320 to enable the communication device 1300 to implement the methods described in the embodiments of this application.

[0173] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0174] In one embodiment, the communication device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0175] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0176] In one embodiment, the communication device 1300 may be the first network element and the third network element in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the first network element and the third network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0177] In one embodiment, the communication device 1300 may be a terminal device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0178] Figure 14 is a schematic structural diagram of a chip 1400 according to an embodiment of this application. The chip 1400 includes a processor 1410, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0179] In one embodiment, chip 1400 may further include memory 1420. Processor 1410 can retrieve and run computer programs from memory 1420 to implement the methods executed by a terminal device or network device in this embodiment.

[0180] The memory 1420 can be a separate device independent of the processor 1410, or it can be integrated into the processor 1410.

[0181] In one embodiment, the chip 1400 may further include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0182] In one embodiment, the chip 1400 may further include an output interface 1440. The processor 1410 can control the output interface 1440 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips.

[0183] In one implementation, the chip can be applied to the first network element and the third network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first network element and the third network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0184] In one embodiment, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0185] The chips used in network equipment and terminal equipment can be the same chip or different chips.

[0186] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0187] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0188] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0189] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be 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 link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0190] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0191] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes 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.

[0192] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0193] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, comprising: The terminal device receives downlink data, which carries a reverse mapping identifier; The terminal device generates Quality of Service (QoS) rules for uplink data based on the first and second protocol layer header information of the downlink data; wherein... The first protocol layer includes at least one of the Internet Protocol (IP) layer, Transmission Control Protocol (TCP) layer, and User Datagram Protocol (UDP) layer.

2. The method according to claim 1, wherein, The second protocol layer includes at least one of the Real-time Transport Protocol (RTP) layer, Real-time Control Protocol (RTCP) layer, and Secure Real-time Transport Protocol (SRTP) layer.

3. The method according to claim 2, wherein, The second protocol layer header information includes the synchronization source identifier SSRC and / or payload type PT in the RTP protocol packet header.

4. The method of any one of claims 1-3, wherein, The terminal device generates QoS rules for uplink data based on the first protocol layer header information and the second protocol layer header information of the downlink data, including: The terminal device generates an IP data stream filter for uplink data based on the first protocol layer header information, and generates an additional data stream filter for uplink data based on the second protocol layer header information.

5. The method of claim 4, wherein, The additional data stream filter includes packet header information read from the second protocol layer.

6. The method of claim 4 or 5, wherein, The QoS rules for uplink data include the QoS Flow Identifier (QFI), the IP data flow filter for uplink data, and the additional data flow filter for uplink data.

7. The method of claim 4 or 5, wherein, The QoS rules for uplink data include QFI and the IP data stream filter for uplink data, wherein the IP data stream filter for uplink data includes the additional data stream filter for uplink data.

8. A communication method, comprising: The first network element receives downlink data; The first network element uses an IP data flow filter and an additional data flow filter to identify the downlink data, and adds a QoS flow identifier and a reverse mapping identifier to the data packet header of the downlink data; The first network element sends the downlink data.

9. The method according to claim 8, further comprising: The first network element receives the IP data flow filter, additional data flow filter, reverse mapping indication, and QoS flow identifier for data transmission sent by the second network element.

10. The method of claim 8 or 9, wherein, The first network element includes a User Plane Function (UPF).

11. The method of claim 9, wherein, The second network element includes a Session Management Function (SMF).

12. A communication method, comprising: The third network element transmission strategy and charging control (PCC) rules include IP data stream filters and additional data stream filters for downlink data, as well as IP data stream filters and additional data stream filters for uplink data.

13. The method of claim 12, wherein, The PCC rule does not include a reverse mapping indication.

14. The method of claim 12 or 13, wherein, The IP data stream filter includes packet header information of a first protocol layer, which includes at least one of the IP layer, TCP layer, and UDP layer.

15. The method of claim 12 or 13, wherein, The additional data stream filter includes packet header information of a second protocol layer, which includes protocol layers above the IP layer, TCP layer, and / or UDP layer.

16. The method according to claim 15, wherein, The second protocol layer includes at least one of the RTP layer, RTCP layer, and SRTP layer.

17. The method of claim 16, wherein, The additional data stream filters include SSRC and / or PT in the packet header of the RTP protocol.

18. The method of any one of claims 12-17, wherein, The third network element includes a policy control function (PCF).

19. A terminal device, comprising: The first transceiver module is used to receive downlink data, wherein the downlink data carries a reverse mapping identifier; The first processing module is configured to generate QoS rules for uplink data based on the first protocol layer header information and the second protocol layer header information of the downlink data; wherein... The first protocol layer includes at least one of the IP layer, TCP layer, and UDP layer.

20. The terminal device according to claim 19, wherein, The second protocol layer includes at least one of the RTP layer, RTCP layer, and SRTP layer.

21. The terminal device according to claim 20, wherein, The second protocol layer header information includes the synchronization source identifier SSRC and / or payload type PT in the RTP protocol packet header.

22. The terminal device of any one of claims 19-21, wherein, The first processing module is configured to generate an IP data stream filter for uplink data based on the first protocol layer header information, and to generate an additional data stream filter for uplink data based on the second protocol layer header information.

23. The terminal device of claim 22, wherein, The additional data stream filter includes packet header information read from the second protocol layer.

24. The terminal device of claim 22 or 23, wherein, The QoS rules for uplink data include QFI, the IP data stream filter for uplink data, and the additional data stream filter for uplink data.

25. The terminal device of claim 22 or 23, wherein, The QoS rules for uplink data include QFI and the IP data stream filter for uplink data, wherein the IP data stream filter for uplink data includes the additional data stream filter for uplink data.

26. A first network element, comprising: The second transceiver module is used to receive downlink data; And, send downlink data; The second processing module is used to identify the downlink data using IP data flow filters and additional data flow filters, and to add QoS flow identifiers and reverse mapping identifiers to the packet header of the downlink data.

27. The first network element according to claim 26, wherein the second transceiver module is further configured to receive an IP data flow filter, an additional data flow filter, a reverse mapping indication, and a QoS flow identifier for transmitting data sent by the second network element.

28. The first network element of claim 26 or 27, wherein, The first network element includes a UPF.

29. The first network element of claim 27, wherein, The second network element includes SMF.

30. A third network element, comprising: The third transceiver module is used to send PCC rules, which include IP data stream filters and additional data stream filters for downlink data, as well as IP data stream filters and additional data stream filters for uplink data.

31. The third network element of claim 30 wherein, The PCC rule does not include a reverse mapping indication.

32. The third network element according to claim 30 or 31, wherein, The IP data stream filter includes packet header information of a first protocol layer, which includes at least one of the IP layer, TCP layer, and UDP layer.

33. The third network element according to claim 30 or 31, wherein, The additional data stream filter includes packet header information of a second protocol layer, which includes protocol layers above the IP layer, TCP layer, and / or UDP layer.

34. The third network element according to claim 33, wherein, The second protocol layer includes at least one of the RTP layer, RTCP layer, and SRTP layer.

35. The third network element of claim 34 wherein, The additional data stream filters include SSRC and / or PT in the packet header of the RTP protocol.

36. The third network element according to any of claims 30-35, wherein, The third network element includes PCF.

37. A terminal device comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the terminal device to perform the method as described in any one of claims 1 to 7.

38. A network device comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the network device to perform the method as described in any one of claims 8 to 18.

39. A chip comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 18.

40. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as claimed in any one of claims 1 to 18.

41. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 18.

42. A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 18.

Images