WO2022037097A1 - 通信方法、装置及系统 - Google Patents

通信方法、装置及系统 Download PDF

Info

Publication number
WO2022037097A1
WO2022037097A1 PCT/CN2021/088886 CN2021088886W WO2022037097A1 WO 2022037097 A1 WO2022037097 A1 WO 2022037097A1 CN 2021088886 W CN2021088886 W CN 2021088886W WO 2022037097 A1 WO2022037097 A1 WO 2022037097A1
Authority
WO
WIPO (PCT)
Prior art keywords
network coding
network
configuration parameter
qos
network element
Prior art date
Application number
PCT/CN2021/088886
Other languages
English (en)
French (fr)
Inventor
马景旺
袁立平
黄曲芳
董朋朋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022037097A1 publication Critical patent/WO2022037097A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method, device, and system.
  • the new services mainly supported by the fifth generation (5G) communication are the Extended Reality (XR) services represented by Virtual Reality (VR) services and Augmented Reality (AR) services.
  • XR Extended Reality
  • VR Virtual Reality
  • AR Augmented Reality
  • XR business is used in entertainment, education and health for ordinary consumers, as well as in vertical industries such as industrial manufacturing and engineering.
  • Data transmission of XR services requires high service rates and low latency.
  • 5G also supports Tactile Internet services, which are mainly used in personal education and entertainment, industrial control and other scenarios.
  • the data transmission of the tactile Internet also requires high service rate and low latency.
  • the XR service and the tactile Internet service are real-time media services, they are sensitive to delay. Therefore, the retransmission guarantee reliability mechanism in the prior art cannot satisfy real-time media services.
  • the frame rate of Cloud VR is 90 frames per second, so the downlink transmission time window of each frame is 11ms.
  • the sampling frequency of tactile data in the tactile Internet service is 500 frames per second, so the sampling time of each frame is 2ms, which basically does not allow retransmission to solve reliability problems such as packet loss in transmission.
  • the media service layer In order to support the reliability of data transmission, the media service layer generally adopts the forward error correction code (Forward Error Correction, FEC) method to generate redundant packet data of the media data through the FEC algorithm to avoid retransmission of lost packets. increased latency and low reliability.
  • FEC Forward Error Correction
  • the FEC mechanism does not take into account the real-time status of the network, FEC parameters cannot be determined based on the real-time status of the network. Therefore, the data redundancy may be too large and the network transmission load may be further increased, or the data redundancy may be too small to support reliable transmission.
  • Network coding technology provides another solution to the reliability of network transmission.
  • end-to-end data transmission involves multiple network nodes.
  • the problem to be solved is: how to configure the coding configuration parameters of each network node, so that the receiving end can decode correctly.
  • the present application provides a communication method, device and system, which are used to enable the receiving end to decode correctly by configuring the encoding configuration parameters of each network node.
  • an embodiment of the present application provides a communication method, including: receiving a QoS identifier and indication information, where the indication information is used to instruct to perform network coding on a QoS flow corresponding to the QoS identifier; Network coding configuration parameters, where the network coding configuration parameters are network coding configuration parameters used by nodes on the user plane path for transmitting the QoS flow.
  • the network coding scheme ensures the reliability and low latency of data transmission, and on the other hand, each node on the user plane path of the QoS flow uses the same network coding configuration parameters, thus ensuring the end-to-end Decoding correctness of data transmission.
  • determining the network coding configuration parameter corresponding to the QoS flow includes: determining the network coding configuration parameter according to the capability information of the node on the user plane path.
  • the network coding configuration parameters are determined according to the capability information of the nodes on the user plane path, so that the network coding configuration parameters supported by each node on the user plane path can be accurately determined, which helps to improve the decoding success Rate.
  • the capability information of the node includes the network coding type supported by the node and/or the data packet size of the network coding supported by the node.
  • the network coding configuration parameters include one or more of a network coding type, a network coding data packet size, or a network coding coefficient.
  • the network coding configuration parameter corresponding to the QoS flow is determined, it is determined according to the subscription data of the terminal device that the QoS flow corresponding to the QoS identifier is allowed to use network coding.
  • the QoS identifier and the network coding configuration parameter are sent to a session management network element and/or an application function network element.
  • an embodiment of the present application provides a communication device, and the device may be a policy control network element or a chip used for the policy control network element.
  • the apparatus has the function of implementing the above-mentioned first aspect or each possible implementation method of the first aspect. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, including a processor and a memory; the memory is used to store computer-executed instructions, and when the device is running, the processor executes the computer-executed instructions stored in the memory, so as to make The apparatus performs the above-mentioned first aspect or each possible implementation method of the first aspect.
  • an embodiment of the present application provides a communication apparatus, including units or means for executing the first aspect or each step of each possible implementation method of the first aspect.
  • an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the first aspect or each possible implementation method of the first aspect .
  • the processor includes one or more.
  • an embodiment of the present application provides a communication device, including a processor that is connected to a memory and used to call a program stored in the memory to execute the first aspect or each possible implementation of the first aspect method.
  • the memory may be located within the device or external to the device.
  • the processor includes one or more.
  • an embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the processor causes the processor to execute the first aspect or the first aspect of possible implementations.
  • an embodiment of the present application further provides a computer program product, the computer product includes a computer program, and when the computer program runs, the first aspect or each possible implementation method of the first aspect is executed.
  • an embodiment of the present application further provides a chip system, including: a processor configured to execute the foregoing first aspect or each possible implementation method of the first aspect.
  • an embodiment of the present application further provides a communication system, including a session management network element and a policy control network element.
  • the session management network element is configured to receive a quality of service QoS identifier and indication information from a terminal device, where the indication information is used to instruct network coding for the QoS flow corresponding to the QoS identifier; QoS identification and the indication information.
  • the policy control network element is configured to receive the QoS identifier and the indication information from the session management network element; determine the network coding configuration parameter corresponding to the QoS flow, and the network coding configuration parameter is used for transmitting all the information.
  • the network coding configuration parameters used by the nodes on the user plane path of the QoS flow is configured to receive a quality of service QoS identifier and indication information from a terminal device, where the indication information is used to instruct network coding for the QoS flow corresponding to the QoS identifier; QoS identification and the indication information.
  • the policy control network element is configured to receive the
  • FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of the 5G network architecture
  • FIG. 3 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a user plane protocol stack provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a communication device according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • the present application provides a communication system, which includes a session management network element and a policy control network element.
  • the system further includes access network equipment.
  • the system further includes a user plane network element.
  • the session management network element is configured to receive a quality of service QoS identifier and indication information from a terminal device, where the indication information is used to instruct network coding for the QoS flow corresponding to the QoS identifier; QoS identification and the indication information.
  • the policy control network element is configured to receive the QoS identifier and the indication information from the session management network element; determine the network coding configuration parameter corresponding to the QoS flow, and the network coding configuration parameter is used for transmitting all the information.
  • the policy control network element is used to determine the network coding configuration parameter corresponding to the QoS flow, and specifically includes: according to the capability information of the node on the user plane path, determine the The network coding configuration parameters described above.
  • the capability information of the node includes the network coding type supported by the node and/or the data packet size of the network coding supported by the node.
  • the network coding configuration parameters include one or more of a network coding type, a network coding data packet size, or a network coding coefficient.
  • the policy control network element is further configured to determine the QoS corresponding to the QoS identifier according to the subscription data of the terminal device before determining the network coding configuration parameter corresponding to the QoS flow Streams are allowed to use network encoding.
  • the nodes of the user plane path include terminal equipment and access network equipment; the policy control network element is further configured to send the QoS identifier and the session management network element to the session management network element. network coding configuration parameters; the session management network element is further configured to send the QoS identifier and the network coding configuration parameters to the access network device; the access network device is configured to send the terminal device the QoS identifier and the network coding configuration parameter.
  • the node of the user plane path includes a user plane network element; the policy control network element is further configured to send the QoS identifier and the network coding configuration to the session management network element parameter; the session management network element is further configured to send the QoS identifier and the network coding configuration parameter to the user plane network element.
  • the node of the user plane path includes an application function network element; the policy control network element is further configured to send the QoS identifier and the network coding configuration to the application function network element parameter.
  • the system shown in Figure 1 can be used in the 5th generation (5G) network architecture shown in Figure 2, and of course, it can also be used in future network architectures, such as the 6th generation (6G) network architecture, etc. , which is not limited in this application.
  • 5G 5th generation
  • 6G 6th generation
  • the network element or entity corresponding to the session management network element in FIG. 1 may be a session management function (session management function, SMF) network element in the 5G network architecture shown in FIG. 2 .
  • the network element or entity corresponding to the policy control network element in FIG. 1 may be a policy control function (Policy Control Function, PCF) network element in the 5G network architecture shown in FIG. 2 .
  • the network element or entity corresponding to the access network device in FIG. 1 may be a radio access network (radio access network, RAN) device in the 5G network architecture shown in FIG. 2 .
  • the network element or entity corresponding to the user plane network element in FIG. 1 may be a user plane function (user plane function, UPF) network element in the 5G network architecture shown in FIG. 2 .
  • the 5G network architecture shown in Figure 2 may include three parts, namely the terminal equipment part, the data network (DN) and the operator network part. The following briefly describes the functions of some of the network elements.
  • the operator network may include one or more of the following network elements: PCF network element, unified data management (unified data management, UDM) (not shown in the figure), unified data warehouse (Unified Data Repository, UDR) ( Not shown in the figure), application function (Application Function, AF) network element, access and mobility management function (Access and Mobility Management Function, AMF) network element, SMF network element, RAN equipment and UPF network element, etc.
  • PCF network element unified data management
  • UDM unified data management
  • UDR Unified Data Repository
  • AF Application Function
  • AMF Access and Mobility Management Function
  • SMF Serving Mobility Management Function
  • the terminal device in this embodiment of the present application may be a device for implementing a wireless communication function.
  • the terminal equipment may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station in a 5G network or a public land mobile network (PLMN) evolved in the future.
  • UE user equipment
  • PLMN public land mobile network
  • remote station remote terminal
  • mobile device wireless communication device
  • terminal agent or terminal device etc.
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. Terminals can be mobile or stationary.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a wireless communication Functional handheld devices computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving,
  • the above-mentioned terminal device can establish a connection with the operator network through an interface (eg, N1, etc.) provided by the operator network, and use the data and/or voice services provided by the operator network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and the terminal device, and may provide other data and/or voice services for the terminal device.
  • the specific expression form of the above third party can be specifically determined according to the actual application scenario, and is not limited here.
  • RAN is a sub-network of an operator's network, and is an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal device To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • the RAN device in this application is a device that provides a wireless communication function for a terminal device, and the RAN device is also called an access network device.
  • the RAN equipment in this application includes but is not limited to: next-generation base station (g nodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B in 5G (node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
  • next-generation base station g nodeB, gNB
  • evolved node B evolved node B
  • eNB evolved node B
  • RNC radio network controller
  • node B in 5G node B, NB
  • base station controller BSC
  • base transceiver station base transceiver station
  • BTS home base station
  • base station for example, home
  • the AMF network element mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between UE and PCF.
  • the SMF network element mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and allocation of UE Internet Protocol (IP) addresses.
  • IP Internet Protocol
  • the UPF network element as the interface UPF with the data network, implements functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation.
  • the UDM network element is mainly responsible for the management of contract data, user access authorization and other functions.
  • UDR is mainly responsible for the access function of contract data, policy data, application data and other types of data.
  • the AF network element mainly conveys the requirements of the application side to the network side, such as quality of service (Quality of Service, QoS) requirements or user status event subscriptions.
  • the AF may be a third-party functional entity or an application service deployed by an operator, such as an IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service.
  • IP Multimedia Subsystem IP Multimedia Subsystem
  • the PCF network element is mainly responsible for policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee and mobility management, and UE policy decision-making.
  • a DN is a network outside the operator's network.
  • the operator's network can access multiple DNs, and multiple services can be deployed on the DNs, which can provide data and/or voice services for terminal devices.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices, and the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain the instruction of the control server, and transmit the collected sensor data to the control server according to the instruction.
  • the DN is an internal office network of a company.
  • the mobile phones or computers of employees of the company can be terminal devices, and the mobile phones or computers of employees can access information and data resources on the internal office network of the company.
  • N7 the interface between PCF and SMF, used for delivering PDU session granularity and business data flow granularity control policy.
  • N15 the interface between the PCF and the AMF, used for delivering UE policies and access control related policies.
  • N5 the interface between the AF and the PCF, used for application service request delivery and network event reporting.
  • N4 The interface between the SMF and the UPF, used to transmit information between the control plane and the user plane, including controlling the distribution of forwarding rules for the user plane, QoS control rules, traffic statistics rules, etc., and information on the user plane report.
  • N11 the interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control message sent to the UE, the radio resource control information sent to the RAN, and the like.
  • N2 the interface between the AMF and the RAN, used to transmit radio bearer control information from the core network side to the RAN, etc.
  • N1 the interface between the AMF and the UE, irrespective of access, used to deliver QoS control rules and the like to the UE.
  • N8 the interface between the AMF and the UDM, for the AMF to obtain the access and mobility management related subscription data and authentication data from the UDM, and the AMF to register the UE's current mobility management related information to the UDM.
  • N10 the interface between the SMF and the UDM, for the SMF to obtain the session management related subscription data from the UDM, and the SMF to register the UE's current session related information to the UDM.
  • N35 an interface between the UDM and the UDR, used for the UDM to obtain user subscription data information from the UDR.
  • N36 an interface between the PCF and the UDR, for the PCF to obtain the policy-related subscription data and application data-related information from the UDR.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • a platform eg, a cloud platform
  • the foregoing network element or function may be implemented by one device, or may be implemented jointly by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the session management network elements, policy control network elements, application function network elements, access network equipment, and user plane network elements in this application may be SMF, PCF, AF, RAN, and UPF in Figure 2, respectively, or may be future communication
  • a network element having the functions of the above-mentioned SMF, PCF, AF, RAN, and UPF in the 6G network is not limited in this application.
  • the present application takes the above SMF, PCF, AF, RAN, and UPF as examples for the session management network element, the policy control network element, the application function network element, the access network equipment, and the user plane network element, respectively.
  • the terminal device is a UE as an example for description.
  • the UPF when the UPF receives downlink packets, the UPF will encapsulate the packets with the same reliability requirements into the same packet according to the Packet Detection Rule (PDR) filter (filter) configured in advance by the SMF.
  • PDR Packet Detection Rule
  • QoS flow QoS flow
  • multiple QoS flows may exist in a PDU session (PDU session), but each QoS flow has an independent and unique QoS flow identifier (QoS flow Identifier, QFI), and is associated with a QoS configuration file (QoS profile), the network side will use the same QoS guarantee for packets belonging to the same QoS flow according to the parameters in the QoS profile, such as delay, forwarding priority, packet loss rate, etc.
  • QFI QoS flow Identifier
  • the RAN When the RAN receives the downlink QoS flow from the UPF, the RAN will encapsulate multiple QoS flows into the same radio bearer (radio barrier) according to certain mapping rules, and the same radio barrier will enjoy the same air interface side reliability guarantee.
  • radio bearer radio barrier
  • Network coding integrates the concepts of coding and routing. By allowing information from different links to be coded and combined, network nodes can realize both routing and coding functions.
  • Network coding is an information exchange technology that integrates coding and routing. The original data can be restored by decoding according to the corresponding coding coefficients.
  • the advantages of using network coding technology for data transmission include: improving network throughput, improving network load balancing, improving bandwidth utilization, improving reliability, and saving wireless network node energy consumption.
  • Random Linear Network Coding (RLNC), Batched Sparse (BATS), Fountain code (FC), etc.
  • an embodiment of the present application provides a schematic diagram of a communication method. Executed on PCF components (such as chips).
  • the method includes the following steps:
  • Step 301 Receive a QoS identifier and indication information, where the indication information is used to instruct to perform network coding on a QoS flow corresponding to the QoS identifier.
  • Step 302 Determine network coding configuration parameters corresponding to the QoS flow, where the network coding configuration parameters are network coding configuration parameters used by nodes on the user plane path for transmitting the QoS flow.
  • the QoS identifier and network coding configuration parameters can be sent directly or through other network elements to the nodes on the user plane path (such as UE, UPF, SMF, AF), so that the user plane path
  • the nodes can be network encoded using the same network encoding configuration parameters.
  • the network coding scheme ensures the reliability and low latency of data transmission, and on the other hand, each node on the user plane path of the QoS flow uses the same network coding configuration parameters, thus ensuring the end-to-end Decoding correctness of data transmission.
  • the user plane path of the QoS flow between the UE and the AF includes the following nodes: UE, RAN, UPF, and AF. These four types of nodes on the user plane path can enhance support for network coding, and perform network coding processing and transmission for a specific service data stream.
  • the same network coding configuration parameters configured to the user plane nodes include but are not limited to:
  • Network coding type There are many types of network coding, and the network coding types supported by different user plane nodes may be different, so it is necessary to select a network coding type supported by each user plane node.
  • the size of the data packet of network coding After the network coding process, the original data packet will be encoded into an encoded data packet of a certain size. Other nodes on the transmission path do not need to decode the encoded data packet, but perform a re-encoding operation. The packet is sent to the next hop node. In this case, each network node on the user plane path needs to obtain network-coded data packets of the same size when performing encoding processing, so that each user plane node can successfully re-encode.
  • a network node that supports network coding outputs a network coding header (Coded Header) and a coded data packet (Coded Packet) after performing a network coding operation on the data packet. The length value of the data packet.
  • the size of the network-coded data packet is the sum of the length value of the network-coding header and the length value of the encoded data packet. As an example, a network encoded packet size is 1.5 kilobytes (kilobits).
  • Network coding coefficients There are various network coding coefficients in network coding, and the network coding coefficients supported by different user plane nodes may be different, so it is necessary to select a network coding coefficient supported by each user plane node.
  • the network coding coefficients are the coding vector parameters corresponding to RLNC network coding
  • BATS network coding the network coding coefficients are the coding vector parameters corresponding to BATS network coding.
  • determining the network coding configuration parameter corresponding to the QoS flow may be to determine the network coding configuration parameter according to the capability information of the node on the user plane path.
  • the network coding configuration parameter may be determined according to at least one of the capability information of the UE, the capability information of the RAN, the capability information of the UPF, and the capability information of the AF.
  • the capability information of the UE includes the network coding type supported by the UE and/or the data packet size of the network coding supported by the UE.
  • the capability information of the RAN includes the type of network coding supported by the RAN and/or the packet size of the network coding supported by the RAN.
  • the capability information of the UPF includes the network coding type supported by the UPF and/or the data packet size of the network coding supported by the UPF.
  • the capability information of the AF includes the type of network coding supported by the AF and/or the packet size of the network coding supported by the AF.
  • the network coding configuration parameters corresponding to the QoS flow are determined and sent to each user plane node to reduce unnecessary waste of resources.
  • the AF and UPF may network-encode the QoS flow at the protocol data unit (PDU) layer based on the configured network-coding configuration parameters, and the UPF and the RAN may be configured based on the configured network-coding configuration.
  • the parameters are transmitted after network coding the QoS flow at the GTP-U layer.
  • the UE and the RAN can network code the QoS flow at the Radio Resource Control (RRC) layer based on the configured network coding configuration parameters and transmit it.
  • RRC Radio Resource Control
  • UPF receives the network-encoded data packets of the specified QoS flow from the AF from the UPF PDU layer, and provides it to the UPF GPRS Tunneling Protocol-User (GTP-U) layer for network encoding processing , sent to RAN via UPF GTP-U.
  • GTP-U UPF GPRS Tunneling Protocol-User
  • the RAN GTP-U receives the network-coded data packets of the specified QoS flow
  • the RAN sends the data packets to the RAN Packet Data Convergence Protocol (PDCP) layer, and the RAN PDCP layer sends the data packets to the RAN RLC layer.
  • PDCP Packet Data Convergence Protocol
  • the RAN RLC layer obtains the parameters used by network coding according to the network coding header in the data packet, and adjusts the network coding configuration parameters and re-encodes according to the air interface state, and carries the adjusted network coding configuration parameters in the network coding header.
  • the network coding header and the coded data packet are sent to the UE through the RAN RLC layer, and the UE obtains the original data packet through a decoding operation according to the parameters in the network coding header.
  • the RAN receives the network-coded data packet of the specified QoS stream sent by the UE at the RAN RLC layer, and the RAN GTP-U layer re-encodes it according to the N3 GTP-U transmission state, and then re-encodes the recoded data packet.
  • the packet is sent to the UPF.
  • the UPF receives the network-coded data packet sent by the RAN at the UPF GTP-U layer, re-encodes the data packet and sends it to the UPF PDU layer, which is then sent to the AF by the UPF PDU layer.
  • the above embodiments of the present application provide an end-to-end data flow transmission control method when transmitted through a mobile network, which can be applied to real-time application scenarios such as AR, VR, and tactile networks, and can also be used in industrial control, etc.
  • it can ensure the reliable transmission of service flows, avoid the increase in transmission delay caused by data retransmission caused by air interface transmission and packet loss in WAN transmission, and can also enable specified service flows as needed.
  • the transmission of network coding increases the decoding success rate of the receiving end.
  • FIG. 5 and FIG. 6 below are specific implementation methods of the embodiment of FIG. 3 described above.
  • FIG. 5 a schematic diagram of another communication method provided by an embodiment of the present application is described.
  • This embodiment describes that a UE initiates a PDU Session modification (PDU Session modification) process and enables network coding transmission.
  • PDU Session modification PDU Session modification
  • the method includes the following steps:
  • Step 501 the UE sends a PDU Session Modification Request (PDU Session Modification Request) to the RAN. Accordingly, the RAN receives the PDU session modification request.
  • PDU Session Modification Request PDU Session Modification Request
  • the PDU session modification request carries a QoS identifier and indication information
  • the QoS identifier can be a 5G QoS identifier (5G QoS Identifier, 5QI)
  • the 5QI is used to identify the characteristic information of the QoS flow that needs to be established
  • the indication information is used to indicate that the The QoS flow is network coded.
  • the PDU session modification request may also carry a QoS identifier instead of the above-mentioned indication information.
  • the QoS identifier may be a newly defined 5QI, where the 5QI is used to identify the characteristic information of the QoS flow that needs to be established and used to indicate that the QoS flow is to be network-coded.
  • Step 502 the RAN sends a session management update request to the AMF. Accordingly, the RAN receives the session management update request.
  • the session management update request may be, for example, an Nsmf_PDUSession_UpdateSMContext Request.
  • the session management update request carries the QoS identifier and indication information, or carries the QoS identifier.
  • Step 503a the SMF sends a session management policy request to the PCF. Accordingly, the PCF receives the session management policy request.
  • the session management policy request may be an SMF initiated SM Policy Association Modification Request.
  • the session management policy request carries the QoS identifier and indication information, or carries the QoS identifier.
  • Step 503b the PCF sends a session management policy response to the SMF. Accordingly, the SMF receives the session management policy response.
  • the session management policy response may be, for example, an SMF initiated SM Policy Association Modification Response.
  • the session management policy response carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 501 .
  • the network coding configuration parameters include, but are not limited to, one or more of a network coding type, a network coding data packet size, or a network coding coefficient.
  • the PCF may first determine, according to the subscription data of the UE, that the QoS flow identified by the 5QI provided by the UE in the foregoing step 501 is allowed to use network coding. Then, the PCF determines the network coding configuration parameter according to at least one of the capability information of the UE, the capability information of the RAN, the capability information of the UPF, and the capability information of the AF.
  • the capability information of the UE includes the network coding type supported by the UE and/or the data packet size of the network coding supported by the UE.
  • the capability information of the RAN includes the type of network coding supported by the RAN and/or the packet size of the network coding supported by the RAN.
  • the capability information of the UPF includes the network coding type supported by the UPF and/or the data packet size of the network coding supported by the UPF.
  • the capability information of the AF includes the type of network coding supported by the AF and/or the packet size of the network coding supported by the AF.
  • the network coding type in the network coding configuration parameter determined by the PCF is the network coding type supported by each network node (ie, UE, RAN, UPF, AF).
  • the network coding data packet size in the network coding configuration parameter determined by the PCF is each The packet size of the network encoding supported by all network nodes.
  • the network coding data packet size in the network coding configuration parameter determined by the PCF may be a specific value, or may be a data rate corresponding to the data packet size.
  • Step 504 the SMF sends an N4 session request to the UPF. Accordingly, the UPF receives the N4 session request.
  • the N4 Session Request may be an N4PDU Session Establishment/Modification Request.
  • the N4 session request carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 501 . That is, the SMF notifies the UPF to create or modify the QoS flow, and provides the corresponding network coding configuration parameters to the UPF, and the UPF can enable the network coding transmission processing for the data flow corresponding to the QoS identifier according to the configured network coding configuration parameters.
  • Step 505 the UPF sends an N4 session response to the SMF. Accordingly, the SMF receives the N4 session response.
  • This step is optional.
  • Step 506 the SMF sends a session management update response to the AMF. Accordingly, the AMF receives the session management update response.
  • the session management update response may be, for example, the Nsmf_PDUSession_UpdateSMContext Response.
  • the session management update response carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 501 .
  • Step 507 the AMF sends an N2 message to the RAN. Accordingly, the RAN receives the N2 message.
  • the N2 message carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 501 . That is, the SMF provides the corresponding network coding configuration parameters to the RAN through the AMF, and the RAN can enable the network coding transmission processing for the data flow corresponding to the QoS identifier according to the configured network coding configuration parameters.
  • Step 508 the newly created QoS flow is configured through RRC Connection Reconfiguration (RRC Connection Reconfiguration) between the RAN and the UE, which includes determining that network coding is enabled at the Radio Link Control (Radio Link Control, RLC) layer.
  • RRC Connection Reconfiguration Radio Connection Reconfiguration
  • RLC Radio Link Control
  • the RAN provides the UE with network coding configuration parameters and QoS identifiers.
  • Step 509 the SMF notifies the PCF that the QoS configuration of the QoS flow has been activated.
  • the SMF may send a session management policy request (such as an SMF initiated SM Policy Association Modification Request) to the PCF, and the session management policy request may notify the PCF that the QoS configuration of the QoS flow has been activated.
  • a session management policy request such as an SMF initiated SM Policy Association Modification Request
  • step 510 the PCF sends a service event notification (Service Event Notification) to the AF through the NEF. Accordingly, the AF can receive business event notifications.
  • Service Event Notification Service Event Notification
  • the service event notification carries the above-mentioned QoS identifier and network coding configuration parameters.
  • the information of the service data flow is also carried.
  • the reliability and low latency of data transmission are guaranteed by the network coding scheme, and the network coding configuration parameters of each network node in network transmission are consistent, which can ensure the correctness of decoding end-to-end data transmission.
  • FIG. 6 a schematic diagram of another communication method provided by an embodiment of the present application is described. This embodiment describes the process of establishing a data connection between the UE and the AF through the PDU session modification process when the AF initiates an XR service.
  • the method includes the following steps:
  • Step 601 the AF sends an application service request (Application service request) to the PCF through the NEF. Accordingly, the PCF receives the application service request.
  • Application service request Application service request
  • the application service request carries the identity of the UE, the address of the UE, the QoS identity and indication information.
  • the QoS identifier may be a 5QI, and the 5QI is used to identify characteristic information of a QoS flow that needs to be established, and the indication information is used to indicate that network coding is performed on the QoS flow.
  • the application service request may also carry the identity of the UE, the address of the UE, and the QoS identity, without carrying the above-mentioned indication information.
  • the QoS identifier may be a newly defined 5QI, where the 5QI is used to identify the characteristic information of the QoS flow that needs to be established and used to indicate that the QoS flow is to be network-coded.
  • the PCF may first determine, according to the subscription data of the UE, that the QoS flow identified by the 5QI provided by the AF is allowed to use network coding. Then, the PCF determines the network coding configuration parameter according to at least one of the capability information of the UE, the capability information of the RAN, the capability information of the UPF, and the capability information of the AF.
  • the capability information of the UE includes the network coding type supported by the UE and/or the data packet size of the network coding supported by the UE.
  • the capability information of the RAN includes the type of network coding supported by the RAN and/or the packet size of the network coding supported by the RAN.
  • the capability information of the UPF includes the network coding type supported by the UPF and/or the data packet size of the network coding supported by the UPF.
  • the capability information of the AF includes the type of network coding supported by the AF and/or the packet size of the network coding supported by the AF.
  • the network coding type in the network coding configuration parameter determined by the PCF is the network coding type supported by each network node (ie, UE, RAN, UPF, AF).
  • the network coding data packet size in the network coding configuration parameter determined by the PCF is each The packet size of the network encoding supported by all network nodes.
  • the network coding data packet size in the network coding configuration parameter determined by the PCF may be a specific value, or may be a data rate corresponding to the data packet size.
  • Step 602a the SMF sends a session management policy request to the PCF. Accordingly, the PCF receives the session management policy request.
  • the session management policy request may be an SMF initiated SM Policy Association Modification Request.
  • Step 602b the PCF sends a session management policy response to the SMF. Accordingly, the SMF receives the session management policy response.
  • the session management policy response may be, for example, an SMF initiated SM Policy Association Modification Response.
  • the session management policy response carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 601 .
  • the network coding configuration parameters include, but are not limited to, one or more of a network coding type, a network coding data packet size, or a network coding coefficient.
  • the session management policy response further carries the PDU session identifier and the identifier of the UE.
  • Step 603 the SMF sends an N4 session request to the UPF. Accordingly, the UPF receives the N4 session request.
  • the N4 Session Request may be an N4PDU Session Establishment/Modification Request.
  • the N4 session request carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 601 . That is, the SMF notifies the UPF to create or modify the QoS flow, and provides the corresponding network coding configuration parameters to the UPF, and the UPF can enable the network coding transmission processing for the data flow corresponding to the QoS identifier according to the configured network coding configuration parameters.
  • the N4 session request also carries the PDU session identifier and the identifier of the UE.
  • Step 604 the UPF sends an N4 session response to the SMF. Accordingly, the SMF receives the N4 session response.
  • This step is optional.
  • Step 605 the SMF sends a session management update response to the AMF. Accordingly, the AMF receives the session management update response.
  • the session management update response may be, for example, the Nsmf_PDUSession_UpdateSMContext Response.
  • the session management update response carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 401 .
  • the session management update response further carries the PDU session identifier and the identifier of the UE.
  • Step 606 the AMF sends an N2 message to the RAN. Accordingly, the RAN receives the N2 message.
  • the N2 message carries the network coding configuration parameter and the QoS identifier, and the QoS identifier is the QoS identifier in the above step 401 . That is, the SMF provides the corresponding network coding configuration parameters to the RAN through the AMF, and the RAN can enable the network coding transmission processing for the data flow corresponding to the QoS identifier according to the configured network coding configuration parameters.
  • the N2 message also carries the PDU session identifier and the identifier of the UE.
  • Step 607 the newly created QoS flow is configured between the RAN and the UE through RRC Connection Reconfiguration, which includes determining that network coding is enabled at the Radio Link Control (Radio Link Control, RLC) layer.
  • RLC Radio Link Control
  • the RAN provides the UE with network coding configuration parameters and QoS identifiers.
  • step 608 the SMF informs the PCF that the QoS configuration of the QoS flow has been activated.
  • the SMF may send a session management policy request (such as an SMF initiated SM Policy Association Modification Request) to the PCF, and the session management policy request may notify the PCF that the QoS configuration of the QoS flow has been activated.
  • a session management policy request such as an SMF initiated SM Policy Association Modification Request
  • Step 609 the PCF sends a service event notification (Service Event Notification) to the AF through the NEF. Accordingly, the AF can receive business event notifications.
  • Service Event Notification Service Event Notification
  • the service event notification carries the above-mentioned QoS identifier and network coding configuration parameters.
  • the information of the service data flow is also carried.
  • the reliability and low latency of data transmission are guaranteed by the network coding scheme, and the network coding configuration parameters of each network node in network transmission are consistent, which can ensure the correctness of decoding end-to-end data transmission.
  • each network element in the above-mentioned implementation includes corresponding hardware structures and/or software modules for executing each function.
  • the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.
  • the steps or operations corresponding to the first policy control network element may also be implemented by components (such as chips or circuits) configured in the first policy control network element, and corresponding to the steps or operations implemented by the first policy control network element.
  • the steps or operations implemented by the two-policy control network element may also be implemented by components (such as chips or circuits) configured in the second policy control network element, and corresponding to the steps or operations implemented by the binding support network element, they may also be implemented by
  • the components (such as chips or circuits) that support the network element binding are implemented, and the steps or operations corresponding to the steps or operations implemented by the application function network elements may also be implemented by components (such as chips or circuits) configured in the application function network elements.
  • FIG. 7 it is a schematic diagram of a communication apparatus according to an embodiment of the present application.
  • the apparatus is used to implement each step performed by the corresponding policy control network element in the foregoing embodiment.
  • the apparatus 700 includes a transceiver unit 710 and a processing unit 720 .
  • the transceiver unit 710 is configured to receive a QoS identifier and indication information, where the indication information is used to instruct to perform network coding on a QoS flow corresponding to the QoS identifier.
  • the processing unit 720 is configured to determine a network coding configuration parameter corresponding to the QoS flow, where the network coding configuration parameter is a network coding configuration parameter used by a node on a user plane path for transmitting the QoS flow.
  • the processing unit 720 configured to determine the network coding configuration parameter corresponding to the QoS flow, specifically includes: determining the network coding configuration parameter according to the capability information of the node on the user plane path Network encoding configuration parameters.
  • the capability information of the node includes the network coding type supported by the node and/or the data packet size of the network coding supported by the node.
  • the network coding configuration parameters include one or more of a network coding type, a network coding data packet size, or a network coding coefficient.
  • the processing unit 720 is further configured to determine the QoS flow corresponding to the QoS identifier according to the subscription data of the terminal device before determining the network coding configuration parameter corresponding to the QoS flow Network coding is allowed.
  • the transceiver unit 710 is further configured to send the QoS identifier and the network coding configuration parameter to a session management network element and/or an application function network element.
  • the above-mentioned communication device 700 may further include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or Function.
  • the processing unit 720 may read data or instructions in the storage unit, so that the communication apparatus implements the methods in the above embodiments.
  • each unit in the above apparatus can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing. Function.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above method, such as: one or more Application Specific Integrated Circuits (ASICs), or, one or more Multiple microprocessors (digital singnal processors, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), or a combination of at least two of these integrated circuit forms.
  • ASICs Application Specific Integrated Circuits
  • DSP digital singnal processors
  • FPGA Field Programmable Gate Array
  • FPGA Field Programmable Gate Array
  • a unit in the apparatus can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can invoke programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above transceiver unit 710 is an interface circuit of the device, and is used to send signals to or receive signals from other devices.
  • the transceiver unit 710 is an interface circuit used by the chip to send signals to or receive signals from other chips or devices.
  • the communication apparatus includes: a processor 810 and an interface 830, and optionally, the communication apparatus further includes a memory 820.
  • the interface 830 is used to enable communication with other devices.
  • the method for executing the policy control network element in the above embodiment may be implemented by the processor 810 calling a program stored in a memory (which may be the memory 820 in the policy control network element, or an external memory). That is, the policy control network element may include a processor 810, and the processor 810 executes the method for executing the policy control network element in the above method embodiments by invoking the program in the memory.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the policy control network element may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
  • the functions/implementation process of the transceiver unit 710 and the processing unit 720 in FIG. 7 may be implemented by the processor 810 in the communication apparatus 800 shown in FIG. 8 calling computer-executable instructions stored in the memory 820 .
  • the function/implementation process of the processing unit 720 in FIG. 7 may be implemented by the processor 810 in the communication apparatus 800 shown in FIG. 8 calling the computer-executed instructions stored in the memory 820, and the function of the transceiver unit 710 in FIG. 7
  • the implementation process can be implemented through the interface 830 in the communication device 800 shown in FIG. 8 .
  • FIG. 9 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • Chip 900 includes one or more processors 901 and interface circuits 902 .
  • the chip 900 may further include a bus 903 . in:
  • the processor 901 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method may be completed by an integrated logic circuit of hardware in the processor 901 or an instruction in the form of software.
  • the above-mentioned processor 901 may be a general purpose processor, a digital communicator (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components .
  • DSP digital communicator
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the interface circuit 902 can be used for sending or receiving data, instructions or information.
  • the processor 901 can use the data, instructions or other information received by the interface circuit 902 to process, and can send the processing completion information through the interface circuit 902.
  • the chip further includes a memory, which may include a read-only memory and a random access memory, and provides operation instructions and data to the processor.
  • a portion of the memory may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory stores executable software modules or data structures
  • the processor may execute corresponding operations by calling operation instructions stored in the memory (the operation instructions may be stored in the operating system).
  • the chip may be used in a communication apparatus (including a terminal device, a user plane network element, and a control plane network element) involved in the embodiments of the present application.
  • the interface circuit 902 may be used to output the execution result of the processor 901 .
  • processor 901 and the interface circuit 902 can be implemented by hardware design, software design, or a combination of software and hardware, which is not limited here.
  • At least one item (single, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.
  • “Plurality" means two or more, and other quantifiers are similar.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.
  • a general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of this application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • Software units can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or this.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM memory read-only memory
  • EEPROM memory electrically erasable programmable read-only memory
  • registers hard disk, removable disk, CD-ROM or this.
  • a storage medium may be coupled to the processor such that the processor may read information from, and store information in, the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium may be provided in the ASIC.
  • the above-described functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on, or transmitted over, a computer-readable medium in the form of one or more instructions or code.
  • Computer-readable media includes computer storage media and communication media that facilitate the transfer of a computer program from one place to another. Storage media can be any available media that a general-purpose or special-purpose computer can access.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other media in the form of program code that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly defined as a computer-readable medium, for example, if software is transmitted from a website site, server or other remote source over a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless, and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the discs and magnetic discs include compact discs, laser discs, optical discs, digital versatile discs (English: Digital Versatile Disc, DVD for short), floppy discs and Blu-ray discs. Disks usually reproduce data magnetically, while Discs usually use lasers to optically reproduce data. Combinations of the above can also be included in computer readable media.
  • the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Abstract

本申请提供通信方法、装置及系统。该方法包括：接收QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。基于该方案，一方面通过网络编码方案保障了数据传输的可靠性和低时延要求，另一方面QoS流的用户面路径上的各个节点使用相同的网络编码配置参数，从而保障了端到端的数据传输的译码正确性。

Description

通信方法、装置及系统
相关申请的交叉引用
本申请要求在2020年08月18日提交中国专利局、申请号为202010833136.6、申请名称为“通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及通信方法、装置及系统。
背景技术
目前，第五代(5th generation，5G)通信主要支持的新业务是以虚拟现实(Virtual Reality，VR)业务、增强现实(Augmented Reality，AR)业务为代表的扩展现实(Extended Reality，XR)业务。XR业务应用于面向普通消费者的娱乐、教育和健康等领域，也可以应用于工业制造、工程等垂直行业。XR业务的数据传输，要求业务速率高、且时延低。除了XR业务，5G还支持触觉互联网(Tactile Internet)业务，主要用于个人教育和娱乐，工业控制等场景。触觉互联网的数据传输，也要求业务速率高、且时延低。
由于XR业务和触觉互联网业务都是实时性媒体业务，因而对时延比较敏感。因此，现有技术的重传保障可靠性机制不能满足实时性媒体业务。例如，云VR(Cloud VR)帧率为90帧/秒，因此每帧的下行传输时间窗为11ms。触觉互联网业务中触觉数据的采样频率为500帧/秒，因此每帧的采样时间为2ms，这基本不允许通过重传的方式解决传输中的丢包等可靠性问题。
为了支持数据传输的可靠性，媒体业务层一般采用前向纠错码(Forward Error Correction，FEC)方式，通过FEC算法产生媒体数据的冗余包数据，避免重传丢失的数据包而导致的时延增加和低可靠性。但是，由于FEC机制没有考虑到网络实时状态，因而不能根据网络实时状态确定FEC参数，从而可能数据冗余过大导致网络传输负荷进一步加重，或者数据冗余过小导致无法支持可靠性传输。
网络编码技术为解决网络传输可靠性提供了另一种解决方案，网络编码应用在5G移动网络时，端到端的数据传输涉及多个网络节点。由多网络节点参与的端到端的网络编码传输，需要解决的问题是：如何配置各网络节点的编码配置参数，以使得接收端可以正确译码。
发明内容
本申请提供通信方法、装置及系统，用以通过配置各网络节点的编码配置参数，使得接收端可以正确译码。
第一方面，本申请实施例提供一种通信方法，包括：接收QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点 使用的网络编码配置参数。
基于上述方案，一方面通过网络编码方案保障了数据传输的可靠性和低时延要求，另一方面QoS流的用户面路径上的各个节点使用相同的网络编码配置参数，从而保障了端到端的数据传输的译码正确性。
在一种可能的实现方法中，确定所述QoS流对应的网络编码配置参数，包括：根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
上述方案，根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数，可以实现准确确定用户面路径上的各个节点均支持的网络编码配置参数，有助于提升译码成功率。
在一种可能的实现方法中，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
在一种可能的实现方法中，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
在一种可能的实现方法中，所述确定所述QoS流对应的网络编码配置参数之前，根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
在一种可能的实现方法中，向会话管理网元和/或应用功能网元发送所述QoS标识和所述网络编码配置参数。
第二方面，本申请实施例提供一种通信装置，该装置可以是策略控制网元，还可以是用于策略控制网元的芯片。该装置具有实现上述第一方面或第一方面的各可能的实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面或第一方面的各可能的实现方法。
第四方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面或第一方面的各可能的实现方法的各个步骤的单元或手段(means)。
第五方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述第一方面或第一方面的各可能的实现方法。该处理器包括一个或多个。
第六方面，本申请实施例提供一种通信装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述第一方面或第一方面的各可能的实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第七方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述第一方面或第一方面的各可能的实现方法。
第八方面，本申请实施例还提供一种计算机程序产品，该计算机产品包括计算机程序，当计算机程序运行时，使得上述第一方面或第一方面的各可能的实现方法被执行。
第九方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面或第一方面的各可能的实现方法。
第十方面，本申请实施例还提供一种通信系统，包括会话管理网元和策略控制网元。 所述会话管理网元，用于接收来自终端设备的服务质量QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；向策略控制网元发送所述QoS标识和所述指示信息。所述策略控制网元，用于从所述会话管理网元接收所述QoS标识和所述指示信息；确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
附图说明
图1为本申请实施例提供的一种通信系统示意图；
图2为5G网络架构示意图；
图3为本申请实施例提供的一种通信方法示意图；
图4为本申请实施例提供的用户面协议栈示意图；
图5为本申请实施例提供的又一种通信方法示意图；
图6为本申请实施例提供的又一种通信方法示意图；
图7为本申请实施例提供的一种通信装置示意图；
图8为本申请实施例提供的又一种通信装置示意图；
图9为本申请实施例提供的一种芯片结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
为解决背景技术中提到的问题，如图1所示，本申请提供一种通信系统，该系统包括会话管理网元和策略控制网元。可选的，该系统还包括接入网设备。可选的，该系统还包括用户面网元。
所述会话管理网元，用于接收来自终端设备的服务质量QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；向策略控制网元发送所述QoS标识和所述指示信息。所述策略控制网元，用于从所述会话管理网元接收所述QoS标识和所述指示信息；确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
在一种可能的实现方法中，所述策略控制网元，用于确定所述QoS流对应的网络编码配置参数，具体包括：用于根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
在一种可能的实现方法中，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
在一种可能的实现方法中，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
在一种可能的实现方法中，所述策略控制网元，还用于在确定所述QoS流对应的网络编码配置参数之前，根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
在一种可能的实现方法中，所述用户面路径的节点包括终端设备和接入网设备；所述策略控制网元，还用于向所述会话管理网元发送所述QoS标识和所述网络编码配置参数；所述会话管理网元，还用于向所述接入网设备发送所述QoS标识和所述网络编码配置参数；所述接入网设备，用于向所述终端设备发送所述QoS标识和所述网络编码配置参数。
在一种可能的实现方法中，所述用户面路径的节点包括用户面网元；所述策略控制网元，还用于向所述会话管理网元发送所述QoS标识和所述网络编码配置参数；所述会话管理网元，还用于向所述用户面网元发送所述QoS标识和所述网络编码配置参数。
在一种可能的实现方法中，所述用户面路径的节点包括应用功能网元；所述策略控制网元，还用于向所述应用功能网元发送所述QoS标识和所述网络编码配置参数。
其中，上述方案的具体实现将在后续方法实施例部分详细阐述，在此不再赘述。
图1所示的系统可以用在图2所示的第五代(5th generation，5G)网络架构中，当然，也可以用在未来网络架构，比如第六代(6th generation，6G)网络架构等，本申请不做限定。
示例性的，假设图1所示的通信系统应用于5G网络架构，如图2所示，为5G网络架构示意图。图1中的会话管理网元所对应的网元或者实体可以为图2所示的5G网络架构中的会话管理功能(session management function，SMF)网元。图1中的策略控制网元所对应的网元或者实体可以为图2所示的5G网络架构中的策略控制功能(Policy Control Function，PCF)网元。图1中的接入网设备所对应的网元或者实体可以为图2所示的5G网络架构中的无线接入网(radio access network，RAN)设备。图1中的用户面网元所对应的网元或者实体可以为图2所示的5G网络架构中的用户面功能(user plane function，UPF)网元。
图2所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括以下网元中的一个或多个：PCF网元、统一数据管理(unified data management，UDM)(图中未示出)、统一数据仓库(Unified Data Repository，UDR)(图中未示出)、应用功能(Application Function，AF)网元、接入与移动性管理功能(Access and Mobility Management Function，AMF)网元、SMF网元、RAN设备以及UPF网元等。上述运营商网络中，除无线接入网部分之外的部分可以称为核心网络部分。
在具体实现中，本申请实施例中的终端设备，可以是用于实现无线通信功能的设备。其中，终端设备可以是5G网络或者未来演进的公共陆地移动网络(public land mobile network，PLMN)中的用户设备(user equipment，UE)、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无 线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，也可以是固定的。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供其他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
RAN是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过RAN，进而可通过RAN与运营商网络的业务节点连接。本申请中的RAN设备，是一种为终端设备提供无线通信功能的设备，RAN设备也称为接入网设备。本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
AMF网元，主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在UE与PCF间传递用户策略。
SMF网元，主要进行会话管理、PCF下发控制策略的执行、UPF的选择、UE互联网协议(internet protocol，IP)地址分配等功能。
UPF网元，作为和数据网络的接口UPF，完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。
UDM网元，主要负责管理签约数据、用户接入授权等功能。
UDR，主要负责签约数据、策略数据、应用数据等类型数据的存取功能。
AF网元，主要传递应用侧对网络侧的需求，例如，服务质量(Quality of Service，QoS)需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。
PCF网元，主要负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、UE策略决策等策略控制功能。
DN，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
在图2所示的架构中，各个网元之间的接口名称及功能如下：
1)、N7：PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
2)、N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
3)、N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
4)、N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5)、N11：SMF与AMF之间的接口，用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。
6)、N2：AMF与RAN之间的接口，用于传递核心网侧至RAN的无线承载控制信息等。
7)、N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
8)、N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
9)、N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
10)、N35：UDM与UDR间的接口，用于UDM从UDR中获取用户签约数据信息。
11)、N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请中的会话管理网元、策略控制网元、应用功能网元、接入网设备、用户面网元分别可以是图2中的SMF、PCF、AF、RAN、UPF，也可以是未来通信如6G网络中具有上述SMF、PCF、AF、RAN、UPF的功能的网元，本申请对此不限定。为方便说明，本申请以会话管理网元、策略控制网元、应用功能网元、接入网设备、用户面网元分别为上述SMF、PCF、AF、RAN、UPF为例进行说明。并且，以下描述中，以终端设备为UE为例进行说明。
下面对本申请实施例涉及的一些背景知识进行介绍。
一、QoS模型
现有QoS模型中，当UPF收到下行数据包，UPF会根据SMF提前配置好的包检测规则(Packet Detection Rule，PDR)过滤器(filter)将具有相同可靠性需求的数据包封装至同一个QoS流(QoS flow)，多个QoS flow可能存在于一个PDU会话(PDU session)中，但每一个QoS flow具有独立、唯一的QoS流标识(QoS flow Identifier，QFI)，并关联一个QoS配置文件(QoS profile)，网络侧会根据QoS profile里面的参数对同属一个QoS flow的数据包采用相同的QoS保障，如时延、转发优先级、丢包率等等。
当RAN收到来自UPF的下行QoS flow时，RAN会按照一定的映射规则将多个QoS flow封装至同一个无线承载(radio barrier)，同一个radio barrier会享有相同的空口侧可靠性保障。
二、网络编码技术
网络编码的基本思想是允许网络的中间节点参与编译码，网络编码融合编码和路由的概念，通过允许来自不同链路的信息进行编码组合，使得网络节点既实现路由功能又实现 编码功能。网络编码是一种融合编码和路由的信息交换技术，其原理表现为网络节点对接收到的多个数据分组进行编码融合，编码后的数据再被中间节点以多点传送方式进行转发，目的节点可依据相应的编码系数进行解码，还原出原始数据。
使用网络编码技术进行数据传输的优势包括：提升网络吞吐量、改善网络负载均衡、提高带宽利用率、提升可靠性、节省无线网络节点能量消耗。
网络编码技术方案包括：随机线性网络编码(Random Linear Network Coding，RLNC)，批处理稀疏(Batched Sparse，BATS)，喷泉码(Fountain code，FC)等。
为解决背景技术提到的问题，基于图1所示的系统和/或图2所示的架构，如图3所示，本申请实施例提供一种通信方法示意图，该方法可以由PCF或用于PCF的部件(如芯片)执行。
该方法包括以下步骤：
步骤301，接收QoS标识和指示信息，指示信息用于指示对QoS标识对应的QoS流进行网络编码。
步骤302，确定QoS流对应的网络编码配置参数，网络编码配置参数为用于传输QoS流的用户面路径上的节点使用的网络编码配置参数。
在确定QoS流对应的网络编码配置参数之后，可以直接或通过其他网元向用户面路径上的节点(如UE、UPF、SMF、AF)发送QoS标识和网络编码配置参数，使得用户面路径上的节点可以使用相同的网络编码配置参数进行网络编码。
基于上述方案，一方面通过网络编码方案保障了数据传输的可靠性和低时延要求，另一方面QoS流的用户面路径上的各个节点使用相同的网络编码配置参数，从而保障了端到端的数据传输的译码正确性。
其中，网络编码应用在5G网络时，UE和AF之间的QoS流的用户面路径包括以下节点：UE、RAN、UPF、AF。用户面路径上的这四类节点可增强支持网络编码，对某个特定的业务数据流进行网络编码处理和传输。
其中，配置给用户面节点的相同的网络编码配置参数，包括但不限于：
1)网络编码类型：网络编码存在多种类型，而且不同的用户面节点支持的网络编码类型可能存在差异，因此需要选择个各个用户面节点均支持的网络编码类型。
2)网络编码的数据包大小：网络编码处理后会将原始数据包编码为一定大小的编码数据包，传输路径上的其他节点对编码数据包不需要进行解码，而是进行重编码操作，将数据包发给下一跳节点。这种情况下需要用户面路径上各网络节点进行编码处理时得到相同大小的网络编码的数据包，以使得各个用户面节点能够实现成功重编码。示例性地，支持网络编码的网络节点对数据包进行网络编码操作后输出网络编码报头(Coded Header)和编码数据包(Coded Packet)，在一种实现方法中，网络编码的数据包大小为编码数据包的长度值，在又一种实现方法中，网络编码的数据包大小为网络编码报头的长度值与编码数据包的长度值之和。作为示例，网络编码的数据包大小为1.5千字节(kilobits)。
3)网络编码系数：网络编码存在多种网络编码系数，而且不同的用户面节点支持的网络编码系数可能存在差异，因此需要选择个各个用户面节点均支持的网络编码系数。作为示例，在采用RLNC网络编码时，网络编码系数为RLNC网络编码对应的编码向量(coding vector)参数，在采用BATS网络编码时，网络编码系数为BATS网络编码对应的 编码向量(coding vector)参数。
作为一种实现方法，上述步骤302中，确定QoS流对应的网络编码配置参数，可以是根据用户面路径上的节点的能力信息，确定网络编码配置参数。比如，可以根据UE的能力信息、RAN的能力信息、UPF的能力信息、AF的能力信息中的至少一个，确定网络编码配置参数。其中，UE的能力信息包括UE支持的网络编码类型和/或UE支持的网络编码的数据包大小。RAN的能力信息包括RAN支持的网络编码类型和/或RAN支持的网络编码的数据包大小。UPF的能力信息包括UPF支持的网络编码类型和/或UPF支持的网络编码的数据包大小。AF的能力信息包括AF支持的网络编码类型和/或AF支持的网络编码的数据包大小。
作为一种实现方法，上述步骤302之前，还可以根据UE的签约数据，确定QoS标识对应的QoS流被允许使用网络编码。也即在确定QoS标识对应的QoS流被允许使用网络编码的情况下，才确定QoS流对应的网络编码配置参数并发送给各个用户面节点，以减少不必要的资源浪费。
如图4所示，为本申请实施例提供的用户面协议栈示意图。基于该图，作为一个示例，AF和UPF可以基于配置的网络编码配置参数在协议数据单元(protocol data unit，PDU)层对QoS流进行网络编码后传输，UPF和RAN可以基于配置的网络编码配置参数在GTP-U层对QoS流进行网络编码后传输，UE和RAN可以基于配置的网络编码配置参数在无线资源控制(Radio Resource Control，RRC)层对QoS流进行网络编码后传输。
比如，针对下行数据，UPF从UPF PDU层接收来自AF的指定QoS流的网络编码的数据包，提供给UPF GPRS隧道协议-用户面(GPRS Tunneling Protocol-User，GTP-U)层进行网络编码处理，通过UPF GTP-U发送给RAN。RAN在RAN GTP-U收到指定QoS流的网络编码的数据包后，将数据包发送给RAN分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层，RAN PDCP层将数据包发送给RAN RLC层，RAN RLC层根据数据包中的网络编码报头获取网络编码使用的参数，并且根据空口状态调整网络编码配置参数以及进行重编码，在网络编码报头中携带调整后的网络编码配置参数，将更新的网络编码报头和编码数据包通过RAN RLC层发送给UE，UE根据网络编码报头中的参数通过解码操作获得原始数据包。
再比如，针对上行数据：RAN在RAN RLC层接收到UE发送的指定QoS流的网络编码的数据包，由RAN GTP-U层根据N3 GTP-U传输状态进行重编码，然后将重编码后的数据包发给UPF。UPF在UPF GTP-U层接收到RAN发送的网络编码的数据包，对数据包进行重编码后发送给UPF PDU层，由UPF PDU层发送给AF。
需要说明的是，本申请上述实施例提供了一种通过移动网络传输时的端到端的数据流的传输控制方法，可应用于AR、VR、触觉网络等实时应用场景，也可用于工业控制等对数据传输有高可靠性需求场景，可以保证业务流的可靠传输，避免因空口传输和广域网传输丢包造成的数据重传导致传输时延增加，并且还可以按需对指定的业务流进行启用网络编码的传输，增加了接收端译码成功率。
下面结合具体示例进行说明。以下图5和图6是上述图3实施例的具体实现方法。
如图5所示，为本申请实施例提供的另一种通信方法示意图，该实施例描述UE发起 PDU会话修改(PDU Session modification)流程，并且启用网络编码传输。
该方法包括以下步骤：
步骤501，UE向RAN发送PDU会话修改请求(PDU Session Modification Request)。相应地，RAN接收到PDU会话修改请求。
该PDU会话修改请求携带QoS标识和指示信息，该QoS标识可以是5G QoS标识(5G QoS Identifier，5QI)，该5QI用于标识需要请求建立的QoS流的特征信息，该指示信息用于指示对所述QoS流进行网络编码。
作为另一种实现方法，该PDU会话修改请求也可以携带QoS标识，不携带上述指示信息。该QoS标识可以是一个新定义的5QI，该5QI用于标识需要请求建立的QoS流的特征信息，以及用于指示对所述QoS流进行网络编码。
步骤502，RAN向AMF发送会话管理更新请求。相应地，RAN接收到会话管理更新请求。
该会话管理更新请求比如可以是Nsmf_PDUSession_UpdateSMContext Request。
该会话管理更新请求携带QoS标识和指示信息，或者携带QoS标识。
步骤503a，SMF向PCF发送会话管理策略请求。相应地，PCF接收会话管理策略请求。
该会话管理策略请求比如可以是SMF initiated SM Policy Association Modification Request。
该会话管理策略请求携带QoS标识和指示信息，或者携带QoS标识。
步骤503b，PCF向SMF发送会话管理策略响应。相应地，SMF接收会话管理策略响应。
该会话管理策略响应比如可以是SMF initiated SM Policy Association Modification Response。
该会话管理策略响应携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤501中的QoS标识。该网络编码配置参数包括但不限于：网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
具体的，PCF可以先根据UE的签约数据，确定上述步骤501中UE提供的5QI所标识的QoS流被允许使用网络编码。然后，PCF根据UE的能力信息、RAN的能力信息、UPF的能力信息、AF的能力信息中的至少一个，确定网络编码配置参数。其中，UE的能力信息包括UE支持的网络编码类型和/或UE支持的网络编码的数据包大小。RAN的能力信息包括RAN支持的网络编码类型和/或RAN支持的网络编码的数据包大小。UPF的能力信息包括UPF支持的网络编码类型和/或UPF支持的网络编码的数据包大小。AF的能力信息包括AF支持的网络编码类型和/或AF支持的网络编码的数据包大小。
PCF确定的网络编码配置参数中的网络编码类型是各网络节点(即UE、RAN、UPF、AF)均支持的网络编码类型，PCF确定的网络编码配置参数中的网络编码的数据包大小是各网络节点均支持的网络编码的数据包大小。
其中，PCF确定的网络编码配置参数中的网络编码的数据包大小可以是一个具体的数值，也可以是与数据包大小具有对应关系的数据速率。
步骤504，SMF向UPF发送N4会话请求。相应地，UPF接收N4会话请求。
该N4会话请求可以是N4PDU Session Establishment/Modification Request。
该N4会话请求携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤501中的QoS标识。也即，SMF通知UPF创建或修改QoS flow，并将对应的网络编码配置参数提供给UPF，UPF可以根据配置的网络编码配置参数，对QoS标识对应的数据流启用网络编码传输处理。
步骤505，UPF向SMF发送N4会话响应。相应地，SMF接收N4会话响应。
该步骤为可选步骤。
步骤506，SMF向AMF发送会话管理更新响应。相应地，AMF接收到会话管理更新响应。
该会话管理更新响应比如可以是Nsmf_PDUSession_UpdateSMContext Response。
该会话管理更新响应携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤501中的QoS标识。
步骤507，AMF向RAN发送N2消息。相应地，RAN接收到N2消息。
该N2消息携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤501中的QoS标识。也即，SMF通过AMF将对应的网络编码配置参数提供给RAN，RAN可以根据配置的网络编码配置参数，对QoS标识对应的数据流启用网络编码传输处理。
步骤508，RAN和UE之间通过RRC连接重配置(RRC Connection Reconfiguration)对新建的QoS流进行配置，其中包括确定在无线链路控制(Radio Link Control，RLC)层启用网络编码。
该过程中，RAN向UE提供网络编码配置参数和QoS标识。
步骤509，SMF通知PCF该QoS流的QoS配置已经激活。
比如，SMF可以向PCF发送会话管理策略请求(比如可以是SMF initiated SM Policy Association Modification Request)，该会话管理策略请求可以通知PCF该QoS流的QoS配置已经激活。
步骤510，PCF通过NEF，向AF发送业务事件通知(Service Event Notification)。相应地，AF可以接收到业务事件通知。
该业务事件通知携带上述QoS标识和网络编码配置参数。可选的，还携带业务数据流的信息。
基于上述方案，通过网络编码方案保障了数据传输的可靠性和低时延要求，并且网络传输的各网络节点的网络编码配置参数保持一致，可以保障端到端的数据传输的译码正确性。
如图6所示，为本申请实施例提供的另一种通信方法示意图，该实施例描述AF发起XR业务时通过PDU session modification流程建立UE和AF之间的数据连接的过程。
该方法包括以下步骤：
步骤601，AF通过NEF向PCF发送应用服务请求(Application service request)。相应地，PCF接收该应用服务请求。
该应用服务请求携带UE的标识、UE的地址、QoS标识和指示信息。该QoS标识可以是5QI,该5QI用于标识需要请求建立的QoS流的特征信息，该指示信息用于指示对所述QoS流进行网络编码。
作为另一种实现方法，该应用服务请求也可以携带UE的标识、UE的地址和QoS标 识，不携带上述指示信息。该QoS标识可以是一个新定义的5QI，该5QI用于标识需要请求建立的QoS流的特征信息，以及用于指示对所述QoS流进行网络编码。
基于该指示信息、或基于该QoS标识，PCF可以先根据UE的签约数据，确定AF提供的5QI所标识的QoS流被允许使用网络编码。然后，PCF根据UE的能力信息、RAN的能力信息、UPF的能力信息、AF的能力信息中的至少一个，确定网络编码配置参数。其中，UE的能力信息包括UE支持的网络编码类型和/或UE支持的网络编码的数据包大小。RAN的能力信息包括RAN支持的网络编码类型和/或RAN支持的网络编码的数据包大小。UPF的能力信息包括UPF支持的网络编码类型和/或UPF支持的网络编码的数据包大小。AF的能力信息包括AF支持的网络编码类型和/或AF支持的网络编码的数据包大小。
PCF确定的网络编码配置参数中的网络编码类型是各网络节点(即UE、RAN、UPF、AF)均支持的网络编码类型，PCF确定的网络编码配置参数中的网络编码的数据包大小是各网络节点均支持的网络编码的数据包大小。
其中，PCF确定的网络编码配置参数中的网络编码的数据包大小可以是一个具体的数值，也可以是与数据包大小具有对应关系的数据速率。
步骤602a，SMF向PCF发送会话管理策略请求。相应地，PCF接收会话管理策略请求。
该会话管理策略请求比如可以是SMF initiated SM Policy Association Modification Request。
步骤602b，PCF向SMF发送会话管理策略响应。相应地，SMF接收会话管理策略响应。
该会话管理策略响应比如可以是SMF initiated SM Policy Association Modification Response。
该会话管理策略响应携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤601中的QoS标识。该网络编码配置参数包括但不限于：网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
可选的，该会话管理策略响应还携带PDU会话标识和UE的标识。
步骤603，SMF向UPF发送N4会话请求。相应地，UPF接收N4会话请求。
该N4会话请求可以是N4PDU Session Establishment/Modification Request。
该N4会话请求携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤601中的QoS标识。也即，SMF通知UPF创建或修改QoS flow，并将对应的网络编码配置参数提供给UPF，UPF可以根据配置的网络编码配置参数，对QoS标识对应的数据流启用网络编码传输处理。
可选的，N4会话请求还携带PDU会话标识和UE的标识。
步骤604，UPF向SMF发送N4会话响应。相应地，SMF接收N4会话响应。
该步骤为可选步骤。
步骤605，SMF向AMF发送会话管理更新响应。相应地，AMF接收到会话管理更新响应。
该会话管理更新响应比如可以是Nsmf_PDUSession_UpdateSMContext Response。
该会话管理更新响应携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤401中的QoS标识。
可选的，该会话管理更新响应还携带PDU会话标识和UE的标识。
步骤606，AMF向RAN发送N2消息。相应地，RAN接收到N2消息。
该N2消息携带网络编码配置参数和QoS标识，该QoS标识即为上述步骤401中的QoS标识。也即，SMF通过AMF将对应的网络编码配置参数提供给RAN，RAN可以根据配置的网络编码配置参数，对QoS标识对应的数据流启用网络编码传输处理。
可选的，N2消息还携带PDU会话标识和UE的标识。
步骤607，RAN和UE之间通过RRC连接重配置(RRC Connection Reconfiguration)对新建的QoS流进行配置，其中包括确定在无线链路控制(Radio Link Control，RLC)层启用网络编码。
该过程中，RAN向UE提供网络编码配置参数和QoS标识。
步骤608，SMF通知PCF该QoS流的QoS配置已经激活。
比如，SMF可以向PCF发送会话管理策略请求(比如可以是SMF initiated SM Policy Association Modification Request)，该会话管理策略请求可以通知PCF该QoS流的QoS配置已经激活。
步骤609，PCF通过NEF，向AF发送业务事件通知(Service Event Notification)。相应地，AF可以接收到业务事件通知。
该业务事件通知携带上述QoS标识和网络编码配置参数。可选的，还携带业务数据流的信息。
基于上述方案，通过网络编码方案保障了数据传输的可靠性和低时延要求，并且网络传输的各网络节点的网络编码配置参数保持一致，可以保障端到端的数据传输的译码正确性。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
可以理解的是，上述各个方法实施例中，对应由第一策略控制网元实现的步骤或者操作，也可以由配置于第一策略控制网元的部件(例如芯片或者电路)实现，对应由第二策略控制网元实现的步骤或者操作，也可以由配置于第二策略控制网元的部件(例如芯片或者电路)实现，对应由绑定支持网元实现的步骤或者操作，也可以由配置于绑定支持网元的部件(例如芯片或者电路)实现，对应由应用功能网元实现的步骤或者操作，也可以由配置于应用功能网元的部件(例如芯片或者电路)实现。
参考图7，为本申请实施例提供的一种通信装置的示意图。该装置用于实现上述实施例中对应策略控制网元所执行的各个步骤，如图7所示，该装置700包括收发单元710和处理单元720。
收发单元710，用于接收QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码。处理单元720，用于确定所述QoS流对应的网络编码配 置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
在一种可能的实现方法中，所述处理单元720，用于确定所述QoS流对应的网络编码配置参数，具体包括：用于根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
在一种可能的实现方法中，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
在一种可能的实现方法中，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
在一种可能的实现方法中，所述处理单元720，还用于在确定所述QoS流对应的网络编码配置参数之前，根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
在一种可能的实现方法中，所述收发单元710，还用于向会话管理网元和/或应用功能网元发送所述QoS标识和所述网络编码配置参数。
可选的，上述通信装置700还可以包括存储单元，该存储单元用于存储数据或者指令(也可以称为代码或者程序)，上述各个单元可以和存储单元交互或者耦合，以实现对应的方法或者功能。例如，处理单元720可以读取存储单元中的数据或者指令，使得通信装置实现上述实施例中的方法。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上收发单元710是一种该装置的接口电路，用于向其它装置发送信号或从其他装置接收信号。例如，当该装置以芯片的方式实现时，该收发单元710是该芯片用于向其它芯片或装置发送信号、或从其它芯片或装置接收信号的接口电路。
参考图8，为本申请实施例提供的一种通信装置示意图，用于实现以上实施例中策略控制网元的操作。如图8所示，该通信装置包括：处理器810和接口830，可选的，该通 信装置还包括存储器820。接口830用于实现与其他设备进行通信。
以上实施例中策略控制网元执行的方法可以通过处理器810调用存储器(可以是策略控制网元中的存储器820，也可以是外部存储器)中存储的程序来实现。即，策略控制网元可以包括处理器810，该处理器810通过调用存储器中的程序，以执行以上方法实施例中策略控制网元执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。策略控制网元可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
具体的，图7中的收发单元710和处理单元720的功能/实现过程可以通过图8所示的通信装置800中的处理器810调用存储器820中存储的计算机可执行指令来实现。或者，图7中的处理单元720的功能/实现过程可以通过图8所示的通信装置800中的处理器810调用存储器820中存储的计算机执行指令来实现，图7中的收发单元710的功能/实现过程可以通过图8中所示的通信装置800中的接口830来实现。
图9为本申请实施例提供的一种芯片的结构示意图。芯片900包括一个或多个处理器901以及接口电路902。可选的，所述芯片900还可以包含总线903。其中：
处理器901可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器901中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器901可以是通用处理器、数字通信器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
接口电路902可以用于数据、指令或者信息的发送或者接收，处理器901可以利用接口电路902接收的数据、指令或者其它信息，进行加工，可以将加工完成信息通过接口电路902发送出去。
可选的，芯片还包括存储器，存储器可以包括只读存储器和随机存取存储器，并向处理器提供操作指令和数据。存储器的一部分还可以包括非易失性随机存取存储器(NVRAM)。
可选的，存储器存储了可执行软件模块或者数据结构，处理器可以通过调用存储器存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
可选的，芯片可以使用在本申请实施例涉及的通信装置(包括终端设备、用户面网元、控制面网元)中。可选的，接口电路902可用于输出处理器901的执行结果。关于本申请的一个或多个实施例提供的通信方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器901、接口电路902各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关 系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或 这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文：Digital Versatile Disc，简称：DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。本申请说明书的上述描述可以使得本领域技术任何可以利用或实现本申请的内容，任何基于所公开内容的修改都应该被认为是本领域显而易见的，本申请所描述的基本原则可以应用到其它变形中而不偏离本申请的发明本质和范围。因此，本申请所公开的内容不仅仅局限于所描述的实施例和设计，还可以扩展到与本申请原则和所公开的新特征一致的最大范围。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (25)

  1. 一种通信方法，其特征在于，包括：
    接收服务质量QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；
    确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
  2. 如权利要求1所述的方法，其特征在于，所述确定所述QoS流对应的网络编码配置参数，包括：
    根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
  3. 如权利要求2所述的方法，其特征在于，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
  5. 如权利要求1-4任一所述的方法，其特征在于，所述确定所述QoS流对应的网络编码配置参数之前，还包括：
    根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
  6. 如权利要求1-5任一所述的方法，其特征在于，还包括：
    向会话管理网元和/或应用功能网元发送所述QoS标识和所述网络编码配置参数。
  7. 一种通信装置，其特征在于，包括：
    收发单元，用于接收服务质量QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；
    处理单元，用于确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
  8. 如权利要求7所述的装置，其特征在于，所述处理单元，用于确定所述QoS流对应的网络编码配置参数，具体包括：
    用于根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
  9. 如权利要求7所述的装置，其特征在于，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
  10. 如权利要求7-9任一所述的装置，其特征在于，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
  11. 如权利要求7-10任一所述的装置，其特征在于，所述处理单元，还用于在确定所述QoS流对应的网络编码配置参数之前，根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
  12. 如权利要求7-11任一所述的装置，其特征在于，所述收发单元，还用于向会话管理网元和/或应用功能网元发送所述QoS标识和所述网络编码配置参数。
  13. 一种通信系统，其特征在于，包括：会话管理网元和策略控制网元；
    所述会话管理网元，用于接收来自终端设备的服务质量QoS标识和指示信息，所述指示信息用于指示对所述QoS标识对应的QoS流进行网络编码；向策略控制网元发送所述 QoS标识和所述指示信息；
    所述策略控制网元，用于从所述会话管理网元接收所述QoS标识和所述指示信息；确定所述QoS流对应的网络编码配置参数，所述网络编码配置参数为用于传输所述QoS流的用户面路径上的节点使用的网络编码配置参数。
  14. 如权利要求13所述的系统，其特征在于，所述策略控制网元，用于确定所述QoS流对应的网络编码配置参数，具体包括：
    用于根据所述用户面路径上的节点的能力信息，确定所述网络编码配置参数。
  15. 如权利要求14所述的系统，其特征在于，所述节点的能力信息包括所述节点支持的网络编码类型和/或所述节点支持的网络编码的数据包大小。
  16. 如权利要求13-15任一所述的系统，其特征在于，所述网络编码配置参数包括网络编码类型、网络编码的数据包大小或网络编码系数中的一个或多个。
  17. 如权利要求13-16任一所述的系统，其特征在于，所述策略控制网元，还用于在确定所述QoS流对应的网络编码配置参数之前，根据终端设备的签约数据，确定所述QoS标识对应的所述QoS流被允许使用网络编码。
  18. 如权利要求13-17任一所述的系统，其特征在于，所述用户面路径的节点包括终端设备和接入网设备；所述系统还包括所述接入网设备；
    所述策略控制网元，还用于向所述会话管理网元发送所述QoS标识和所述网络编码配置参数；
    所述会话管理网元，还用于向所述接入网设备发送所述QoS标识和所述网络编码配置参数；
    所述接入网设备，用于向所述终端设备发送所述QoS标识和所述网络编码配置参数。
  19. 如权利要求13-18任一所述的系统，其特征在于，所述用户面路径的节点包括用户面网元；所述系统还包括所述用户面网元；
    所述策略控制网元，还用于向所述会话管理网元发送所述QoS标识和所述网络编码配置参数；
    所述会话管理网元，还用于向所述用户面网元发送所述QoS标识和所述网络编码配置参数。
  20. 如权利要求13-19任一所述的系统，其特征在于，所述用户面路径的节点包括应用功能网元；
    所述策略控制网元，还用于向所述应用功能网元发送所述QoS标识和所述网络编码配置参数。
  21. 一种策略控制网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述策略控制网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述策略控制网元执行如权利要求1-6任一项所述的通信方法。
  22. 一种通信装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，以执行如权利要求1-6任一项所述的通信方法。
  23. 一种芯片系统，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，使得安装有所述芯片系统的设备执行如利要求1-6任一项所述的通信方法。
  24. 一种计算机可读存储介质，其特征在于，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如利要求1-6任一项所述的通信方法。
  25. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如利要求1-6任一项所述的通信方法。
PCT/CN2021/088886 2020-08-18 2021-04-22 通信方法、装置及系统 WO2022037097A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010833136.6 2020-08-18
CN202010833136.6A CN114079944A (zh) 2020-08-18 2020-08-18 通信方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2022037097A1 true WO2022037097A1 (zh) 2022-02-24

Family

ID=80281329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/088886 WO2022037097A1 (zh) 2020-08-18 2021-04-22 通信方法、装置及系统

Country Status (2)

Country Link
CN (1) CN114079944A (zh)
WO (1) WO2022037097A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108075861A (zh) * 2017-09-28 2018-05-25 河北工程大学 软件定义FiWi网络中基于多路径的网络编码传输方法
WO2019178205A1 (en) * 2018-03-14 2019-09-19 Qualcomm Incorporated Techniques for signaling qos class indicators

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108075861A (zh) * 2017-09-28 2018-05-25 河北工程大学 软件定义FiWi网络中基于多路径的网络编码传输方法
WO2019178205A1 (en) * 2018-03-14 2019-09-19 Qualcomm Incorporated Techniques for signaling qos class indicators

Also Published As

Publication number Publication date
CN114079944A (zh) 2022-02-22

Similar Documents

Publication Publication Date Title
WO2018028295A1 (zh) 切换场景下的QoS参数处理的方法及设备
WO2020001562A1 (zh) 一种通信方法及装置
WO2021227559A1 (zh) 通信方法、装置及系统
EP4106480A1 (en) Communication method and apparatus
WO2021232841A1 (zh) 通信方法和装置
WO2021249039A1 (zh) 通信方法、装置及系统
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
WO2021208561A1 (zh) 通信方法和装置
WO2022017113A1 (zh) 通信方法及装置
WO2019223476A1 (zh) 业务服务质量监测方法、设备及系统
WO2020169039A1 (zh) 一种策略管理的方法及装置
JP2017503407A (ja) パケット処理方法および装置
WO2022067700A1 (zh) 通信方法、装置及系统
WO2022047803A1 (zh) 通信方法及装置
WO2021134353A1 (zh) 通信方法、装置及系统
US20230050923A1 (en) Media packet transmission method, apparatus, and system
WO2022037097A1 (zh) 通信方法、装置及系统
US11757746B2 (en) Communication method, apparatus, and system
WO2021254116A1 (zh) 通信方法和装置
WO2021218244A1 (zh) 通信方法、装置及系统
WO2022067699A1 (zh) 业务数据流的传输方法、通信装置及通信系统
TWI821882B (zh) 丟包率的檢測方法、通信裝置及通信系統
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置
WO2023213156A1 (zh) 通信方法、通信装置及通信系统
JP7472279B2 (ja) 通信方法、装置、およびシステム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21857198

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21857198

Country of ref document: EP

Kind code of ref document: A1