WO2023160116A1 - 通信方法和装置 - Google Patents
通信方法和装置 Download PDFInfo
- Publication number
- WO2023160116A1 WO2023160116A1 PCT/CN2022/137911 CN2022137911W WO2023160116A1 WO 2023160116 A1 WO2023160116 A1 WO 2023160116A1 CN 2022137911 W CN2022137911 W CN 2022137911W WO 2023160116 A1 WO2023160116 A1 WO 2023160116A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- network element
- scheduling priority
- different types
- data blocks
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
Definitions
- the present application relates to the communication field, and more specifically, to a communication method and device.
- a quality of service (quality of service, QoS) flow (flow) is proposed.
- a terminal device user equipment, UE
- PDU packet data unit
- each PDU session can be established (also It can be called configuration) one or more QoS flows that carry business data flows.
- each QoS flow is expressed by a set of QoS parameters, and the QoS parameters include the 5G QoS identifier (5G QoS identifier, 5QI).
- the scheduling of data flow is based on QoS flow as the granularity. Therefore, it is impossible to perform differentiated scheduling on the same QoS flow according to the importance of the data flow to the user experience.
- the embodiment of the present application provides a communication method, by configuring multiple scheduling priorities corresponding to the same QoS flow, in order to realize differentiated scheduling of the same QoS flow.
- a communication method is provided.
- the method may be executed by an application network element, or may also be executed by a component (such as a chip or a circuit) of the application network element. This is not limited. For the convenience of description, the following uses The execution of the application network element is taken as an example for description.
- the method includes: applying a network element to determine the scheduling priority corresponding to each type of data block in multiple different types of data blocks, and the data packets in the multiple different types of data blocks are all mapped to the same quality of service (QoS) flow
- the application network element sends indication information to the policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, wherein each data block includes at least one data packet.
- the application network element can determine the scheduling priority of different types of data blocks corresponding to the same QoS flow, and notify the policy to control the scheduling priority corresponding to each type of data block of the network element through the instruction information, so that the policy
- the control network element learns that the same QoS flow has multiple different scheduling priorities, so as to realize differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- Multiple different types of data blocks correspond to the same QoS flow; or, it can be understood as multiple different types of data blocks carried in the same QoS flow; or it can also be understood as each of multiple different types of data blocks
- the scheduling priorities corresponding to the types of data blocks are used to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the above-mentioned application network element sending the instruction information to the policy control network element may be that the application network element directly sends the instruction information to the policy control network element, for example, the application network element uses the communication interface between the application network element and the policy control network element or Send the instruction information to the policy control network element through the service interface; it is also possible that the application network element indirectly sends the instruction information to the policy control network element, for example, the application network element sends the instruction information to the policy control network element through other functional network elements.
- the indication information is included in the quality of service QoS requirement, and the QoS requirement is used to configure the parameters of the QoS flow
- the method further includes: the application network element receiving the A response message from the policy control network element, which is used to indicate that the parameter configuration of the QoS flow is completed; the application network element sends downlink data to the user plane network element, and the downlink data includes a data packet and a An indication of the type of data block.
- the application network element can carry the indication information in the QoS requirement, that is, the above-mentioned scheduling priority corresponding to each type of data block in the same QoS flow can be understood as a kind of QoS requirement.
- the QoS requirement is used to configure the parameters of the QoS flow. After the parameter configuration of the QoS flow is completed, the application network element can be notified by a response message that the parameter configuration of the QoS flow is completed, so that the application network element can start to transmit downlink data.
- the downlink data in addition to the data packet to be transmitted, also includes indication information indicating the type of the data block to which the data packet belongs, so that the network element receiving the data packet can determine the data packet belongs to according to the type of indication information.
- the type of the data block and further determine the scheduling priority of the data packet according to the type of the data block to which the data packet belongs, and realize the differentiated scheduling of the data packets of different types of data blocks corresponding to the same quality of service QoS flow.
- the method further includes: the application network element sending the identification information of the data block to which the data packet belongs to the user plane network element.
- the application network element can send the identification information of the data block to which the data packet belongs to the user plane network element, so that the user plane network element can know the data block to which the data packet belongs according to the identification information.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication method is provided, and the method may be executed by a policy control network element, or may also be executed by a component (such as a chip or a circuit) of the policy control network element, which is not limited, and for ease of description, In the following, the execution of the network element controlled by the policy is taken as an example for description.
- the communication method includes: the policy control network element receives indication information from the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the multiple data blocks of different types The data packets in the data block are all mapped to the same QoS flow; the policy control network element sends the scheduling priority corresponding to each type of data block to the session management network element.
- the application network element notifies the policy control network element of the scheduling priority corresponding to each type of data block through the indication information, so that the policy control network element knows that the same QoS flow has multiple different scheduling priorities, in order to achieve Differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.
- the policy control network element can send the scheduling priority corresponding to each type of data block to the session management network element through the PCC rule, and the PCC rule includes information indicating the scheduling priority compared with other QoS flows , so as to determine the scheduling priority among QoS flows.
- the method further includes: the policy control network element receiving a response message from the session management network element, where the response message is used to indicate that the parameter configuration of the QoS flow is completed; The policy control network element sends the response message to the application network element.
- the application network element can be notified of the completion of the parameter configuration of the QoS flow through a response message, so that the subsequent application network element can perform downlink data transmission.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication method is provided, and the method may be executed by a session management network element, or may also be executed by a component (such as a chip or a circuit) of the session management network element, which is not limited, and for the convenience of description, In the following, the implementation by the session management network element is taken as an example for description.
- the communication method includes: the session management network element receives the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all Mapped to the same quality of service QoS flow; the session management network element sends the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate the user plane network element
- the scheduling priority corresponding to the received data packet is encapsulated in the data packet, wherein each data block includes at least one data packet.
- the session management network element can receive the scheduling priority corresponding to each type of data block from the policy control network element, and send the scheduling priority corresponding to each type of data block to the user plane network element, so that the user
- the plane network element learns that the same QoS flow has multiple different scheduling priorities, so as to realize differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.
- the policy control network element can send the scheduling priority corresponding to each type of data block to the session management network element through the PCC rule, and the PCC rule includes information indicating the scheduling priority compared with other QoS flows , so as to determine the scheduling priority among QoS flows.
- the method further includes: the session management network element configures the parameters of the QoS flow according to the PCC rule; the session management network element sends a response message to the policy control network element , the response message is used to indicate that the parameter configuration of the QoS flow is completed.
- the policy control network element can be notified through the response message that the parameter configuration of the QoS flow is completed, so that the subsequent application network element can perform downlink data transmission.
- the method further includes: the session management network element assigns a scheduling priority to each type of data block among the plurality of different types of data blocks A priority identifier, where the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block; the session management network element sends the user plane network element the scheduling priority identifier corresponding to each type of data block and A corresponding relationship, wherein the corresponding relationship includes a corresponding relationship between the scheduling priorities of the multiple different types of data blocks and multiple identifiers of the scheduling priorities.
- the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier.
- each type of data block can be The scheduling priority identifier and corresponding relationship corresponding to the data block are sent to the user plane network element, so that the user plane network element determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship.
- the method further includes: the session management network element sending multiple scheduling priorities of different types of data blocks and multiple scheduling priorities to the access network device Correspondence between level identifiers.
- the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier.
- multiple different types of The scheduling priority of the data block and the corresponding relationship between multiple scheduling priority identifiers are sent to the access network device, so that the access network device determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship .
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- the method further includes: the session management network element sending encapsulation information to the user plane network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information In the data packet, the identification information is used to identify the data block to which the data packet belongs.
- a communication method is provided, and the method may be executed by a user plane network element, or may also be executed by a component (such as a chip or a circuit) of the user plane network element, which is not limited, and for ease of description, The following takes the implementation by the user plane network element as an example for description.
- the communication method includes: a user plane network element receives downlink data from an application network element, the downlink data includes a plurality of different types of data blocks, and each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority , the data packets in the plurality of data blocks of different types are all mapped to the same quality of service QoS flow, and each data block includes at least one data packet; the user plane network element according to the type corresponding to each data packet and each A scheduling priority corresponding to a data block of the type determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet is encapsulated with information indicating the scheduling priority of the data packet .
- the user plane network element can encapsulate the indication information of the scheduling priority of different data packets in the data packet, so that the access network equipment can know the scheduling priority of different data packets in the same QoS flow, in order to achieve the same Differential scheduling of data packets of different types of data blocks corresponding to a QoS flow.
- the method further includes: the user plane network element receives scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, the The encapsulation indication information is used to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.
- the session management network element can send the scheduling priority corresponding to each type of data block to the user plane network element, so that the user plane network element knows that the same QoS flow has multiple different scheduling priorities.
- the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority
- the method further includes: receiving, by the user plane network element from The scheduling priority identifier and corresponding relationship of the session management network element, the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block, and the corresponding relationship includes the scheduling priorities of the multiple different types of data blocks Corresponding relationship with multiple scheduling priority identifiers.
- the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier.
- each type of data block can be The scheduling priority identifier and corresponding relationship corresponding to the data block are sent to the user plane network element, so that the user plane network element determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship.
- the method further includes: receiving, by the user plane network element, identification information of a data block to which the data packet belongs from the application network element.
- the identification information is encapsulated in the data packet
- the method further includes: the user plane network element receives the encapsulation information from the session management network element, and the encapsulation information It is used to instruct the user plane network element to encapsulate identification information in the data packet, where the identification information is used to identify the data block to which the data packet belongs.
- the transmission of packet granularity is extended to the transmission of data block granularity through data block identification, so as to avoid waste of resources and improve transmission efficiency.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication method is provided, and the method may be executed by an access network device, or may also be executed by a component (such as a chip or a circuit) of the access network device, which is not limited, and for the convenience of description, The following takes the implementation by the access network device as an example for description.
- the communication method includes: the access network device receives a plurality of data packets from a user plane network element, each of the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet; the plurality of data packets The packet belongs to multiple different types of data blocks, each type of data block in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same service In the quality of QoS flow; the access network device processes the data packet according to the scheduling priority.
- the user plane network element can encapsulate the indication information of the scheduling priority of different data packets in the data packet, so that the access network equipment can know the scheduling priority of different data packets in the same QoS flow, in order to achieve the same Differential scheduling of data packets of different types of data blocks corresponding to a QoS flow.
- the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority
- the method further includes: the access network device receives the information from the session The corresponding relationship between the scheduling priorities of multiple different types of data blocks of the network element and the multiple scheduling priority identifiers is managed.
- the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier.
- multiple different types of The scheduling priority of the data block and the corresponding relationship between multiple scheduling priority identifiers are sent to the access network device, so that the access network device determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship .
- the data packet further encapsulates identification information of the data block to which the data packet belongs, and the method further includes: the access network device determines whether to Scheduling and this data packet belong to other data packets in the same data block except this data packet.
- the transmission of packet granularity is extended to the transmission of data block granularity through data block identification, so as to avoid waste of resources and improve transmission efficiency.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication device is provided, and the communication device is used to execute the method provided in the first aspect above.
- the device includes: a processing unit, configured to determine a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS In the stream; a sending unit, configured to send indication information to a policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, wherein each data block includes at least one data packet.
- the indication information is included in the quality of service QoS requirement, and the QoS requirement is used to configure the parameters of the QoS flow
- the device further includes: a receiving unit configured to receive A response message from the policy control network element, the response message is used to indicate that the parameter configuration of the QoS flow is completed; the sending unit is also used to send downlink data to the user plane network element, the downlink data includes data packets and is used to indicate the An indication of the type of data block to which the packet belongs.
- the sending unit is further configured to send the identification information of the data block to which the data packet belongs to the user plane network element.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication device is provided, and the communication device is used to execute the method provided in the second aspect above.
- the communication device includes: a receiving unit, configured to receive indication information from an application network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, the plurality of different types of data blocks The data packets in each type of data block are mapped to the same QoS flow; the sending unit is configured to send the scheduling priority corresponding to each type of data block to the session management network element.
- the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes a parameter for indicating the Information about the scheduling priority of the QoS flow.
- the receiving unit is further configured to receive a response message from the session management network element, where the response message is used to indicate that the parameter configuration of the QoS flow is completed; the sending unit is also configured to It is used to send the response message to the application network element.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication device is provided, and the communication device is used to execute the method provided in the third aspect above.
- the communication device includes: a receiving unit, configured to receive the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS flow; the sending unit is used to send the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate that the user plane network
- the element encapsulates the scheduling priority corresponding to the received data packet into the data packet, wherein each data block includes at least one data packet.
- the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.
- the device further includes: a processing unit configured to configure the parameters of the QoS flow according to the PCC rule; the sending unit is also used to send a response to the policy control network element message, the response message is used to indicate that the parameter configuration of the QoS flow is completed.
- the apparatus further includes: a processing unit configured to allocate scheduling for a scheduling priority corresponding to each type of data block among the plurality of different types of data blocks A priority identifier, where the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block; the sending unit is also used to send the scheduling priority identifier corresponding to each type of data block to the user plane network element and a corresponding relationship, wherein the corresponding relationship includes a corresponding relationship between the scheduling priorities of the multiple different types of data blocks and multiple identifiers of the scheduling priorities.
- the sending unit is further configured to send the scheduling priorities of multiple different types of data blocks and the correspondence between multiple scheduling priority identifiers to the access network device relation.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- the sending unit is further configured to send encapsulation information to the user plane network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet
- the identification information is used to identify the data block to which the data packet belongs.
- a communication device is provided, and the communication device is used to execute the method provided in the fourth aspect above.
- the communication device includes: a receiving unit, configured to receive downlink data from an application network element, the downlink data includes a plurality of different types of data blocks, and each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority level, the data packets in the multiple different types of data blocks are all mapped to the same quality of service QoS flow, and each of the data blocks includes at least one data packet; the processing unit is used for according to the type corresponding to each data packet and each A scheduling priority corresponding to each type of data block determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet is encapsulated with the scheduling priority indicating the data packet. information.
- the receiving unit is further configured to receive scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, and the encapsulation indication information is used Instructing the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.
- the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority
- the receiving unit is further configured to receive a message from the session management network element
- the scheduling priority identifier and corresponding relationship the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block, the corresponding relationship includes the scheduling priorities of the multiple different types of data blocks and multiple of the Correspondence between scheduling priority identifiers.
- the receiving unit is further configured to receive, from the application network element, identification information of the data block to which the data packet belongs.
- the identification information is encapsulated in the data packet
- the receiving unit is further configured to receive encapsulation information from the session management network element, where the encapsulation information is used to indicate the
- the user plane network element encapsulates identification information in the data packet, and the identification information is used to identify the data block to which the data packet belongs.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication device is provided, and the communication device is used to execute the method provided in the fifth aspect above.
- the communication device includes: a receiving unit, configured to receive a plurality of data packets from a user plane network element, each of the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet; the plurality of The data packets belong to multiple different types of data blocks, and each type of data blocks in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same In the quality of service QoS flow; a processing unit, configured to process the data packet according to the scheduling priority.
- the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority
- the receiving unit is further configured to receive a message from the session management network element The corresponding relationship between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers.
- the data packet is further encapsulated with identification information of the data block to which the data packet belongs, and the processing unit is further configured to determine whether to schedule and the data block according to the identification information The packet belongs to other packets in the same data block than this one.
- the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.
- a communication device is provided, and the device is used to execute the methods provided in the first aspect to the fifth aspect.
- the communication device may include units and/or modules for performing the methods provided in the first aspect to the fifth aspect.
- the transceiver unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
- the transceiver may be a transceiver circuit.
- the input/output interface may be an input/output circuit.
- the transceiver unit may be a chip, a chip system, or an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on a circuit;
- the processing unit may be at least one processor, Processing circuits or logic circuits, etc.
- the present application provides a processor configured to execute the method provided in the foregoing aspects.
- the processor's output and reception, input and other operations can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
- a computer-readable storage medium stores program code for execution by a device, and the program code includes any implementation manner for performing the first aspect to the fifth aspect above provided method.
- a computer program product containing instructions is provided, and when the computer program product is run on a computer, the computer is made to execute the method provided by any one of the implementation manners of the first aspect to the fifth aspect above.
- a fifteenth aspect provides a chip, the chip includes a processor and a communication interface, the processor reads the instructions stored in the memory through the communication interface, and executes the method provided by any one of the above first to fifth aspects.
- the chip further includes a memory, in which computer programs or instructions are stored, and the processor is used to execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the processor is used to execute The method provided by any implementation manner of the first aspect to the fifth aspect above.
- a sixteenth aspect provides a communication system, including the notification devices shown in the sixth to tenth aspects.
- FIG. 1 are schematic diagrams of application scenarios applicable to the embodiments of the present application.
- Fig. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application.
- FIG. 3 is a schematic block diagram of an apparatus 300 provided by an embodiment of the present application.
- FIG. 4 is a schematic block diagram of an apparatus 400 provided by an embodiment of the present application.
- the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency Division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc.
- 5G fifth generation
- NR new radio
- long term evolution long term evolution
- LTE frequency Division duplex frequency division duplex
- FDD frequency division duplex
- TDD time division duplex
- the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
- the technical solution of the embodiment of the present application can also be applied to device to device (device to device, D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (machine to machine, M2M) communication, machine Type communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
- D2D device to device
- V2X vehicle-to-everything
- M2M machine to machine
- MTC machine Type communication
- IoT Internet of things
- the technical solution of the embodiment of the present application can be applied to the 5G network architecture shown in (a) in Figure 1 and/or (b) in Figure 1, and of course can also be used in future network architectures, such as the sixth generation (6th generation generation, 6G) network architecture, etc., which are not specifically limited in this embodiment of the present application.
- 5G 5G based on point-to-point interfaces in combination with (a) in Figure 1 and (b) in Figure 1.
- System framework and 5G system framework based on service interface.
- FIG. 1 shows a schematic architecture diagram of a 5G system 200a to which the embodiment of the present application is applicable.
- Figure 1 is a schematic diagram of a 5G network architecture based on a point-to-point interface.
- the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):
- User equipment user equipment, UE
- wireless access network equipment
- access and mobility management function access and mobility management function
- AMF access and mobility management function
- SMF session management function
- UPF user plane function
- policy control function policy control function
- PCF policy control function
- UDM unified data management
- application function application function, AF
- NSSF network slice selection function
- authentication server function authentication server function
- UDM network exposure function
- NEF network exposure function
- a terminal that communicates with (R)AN can also be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station (mobile station, MS), mobile terminal (mobile terminal) terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
- a terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
- examples of some terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self driving (self driving), wireless in remote medical (remote medical) Terminals, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless Telephones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or connected Other processing devices to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the 5G network or terminal devices in the future evolution of the public land mobile network (PLMN), etc.
- PLMN public land mobile network
- the terminal device may also be a terminal device in an Internet of Things (Internet of things, IoT) system.
- IoT Internet of things
- Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and object interconnection.
- IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.
- NB narrow band
- the terminal device may be any device that can access the network.
- a certain air interface technology may be used to communicate with each other between the terminal device and the access network device.
- the user equipment can be used as a base station.
- a user equipment may act as a scheduling entity, which provides sidelink signals between user equipments in V2X or D2D, etc.
- a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.
- (R)AN It is used to provide network access functions for authorized user equipment in a specific area, and can use transmission tunnels with different service qualities according to the level of user equipment and business requirements.
- (R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
- (R)AN can also be understood as a base station in a traditional network.
- the access network device in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with the user equipment.
- the access network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved Node B, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI ) system in the access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G , such as, NR, gNB in the system, or, transmission point (TRP or TP), one or a group (including multiple antenna panels
- a gNB may include a centralized unit (CU) and a DU.
- the gNB may also include an active antenna unit (AAU).
- the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
- the CU is responsible for processing non-real-time protocols and services, and realizing the functions of radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer.
- the DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical (physical, PHY) layer.
- the AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , or, sent by DU+AAU.
- the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
- the CU can be divided into access network devices in the access network (radio access network, RAN), and the CU can also be divided into access network devices in the core network (core network, CN). Do limited.
- User plane network element used for packet routing and forwarding and quality of service (QoS) processing of user plane data.
- QoS quality of service
- the user plane network element may be a UPF network element, which may include an intermediate user plane function (intermediate user plane function, I-UPF) network element, an anchor user Plane function (PDU Session anchor user plane function, PSA-UPF) network element.
- I-UPF intermediate user plane function
- PSA-UPF anchor user Plane function
- the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
- Data network a network used to provide data transmission.
- the data network may still be a DN, or may have other names, which are not limited in this application.
- the terminal equipment accesses the network, it can establish a protocol data unit (protocol data unit, PDU) session, and access the DN through the PDU session, and can communicate with the application function network element deployed in the DN (application function network element such as for the application server) interaction.
- PDU protocol data unit
- the network can select the UPF that accesses the DN as the PDU Session Anchor (PDU Session Anchor, PSA) according to the network policy, and access it through the N6 interface of the PSA Application function network element.
- PSA PDU Session Anchor
- Access and mobility management network element mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in the mobility management entity (MME) function, For example, functions such as lawful interception and access authorization/authentication.
- MME mobility management entity
- the access management network element may be an AMF network element.
- the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
- Session management network element mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, selection of manageable terminal equipment plane functions, termination points of policy control and charging function interfaces, and downlink Data Notification etc.
- IP network interconnection protocol
- the session management network element may be an SMF network element, and may include an intermediate session management function (intermediate session management function, I-SMF) network element, an anchor session Management function (anchor session management function, A-SMF) network element.
- I-SMF intermediate session management function
- A-SMF anchor session management function
- the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
- Policy control network element a unified policy framework used to guide network behavior, and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).
- the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
- policy control network element may be a PCF network element.
- the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
- Data management network element used to process terminal device identification, access authentication, registration, and mobility management.
- the data management network element may be a UDM network element or a UDR network element.
- the unified data management may still be UDM, UDR network element, or may have other names, which are not limited in this application.
- the UDM or UDR network element in this embodiment of the present application may refer to a user database. Can exist as a single logical repository for storing user data.
- Application function network elements can interact with 5G systems through application function network elements, and are used to access network open function network elements or interact with policy frameworks for policy control, etc.
- the application function network element may be an application function, AF network element.
- the application function network element may still be an AF network element, or may have other names, which are not limited in this application.
- Network slice selection network element mainly includes the following functions: select a group of network slice instances for the UE, determine the allowed network slice selection assistance information (network slice selection assistance information, NSSAI), and determine the AMF set that can serve the UE, etc.
- NSSAI network slice selection assistance information
- the network element selected for network slicing may be an NSSF network element.
- the network element selected for network slicing may still be an NSSF network element, or may have other names, which are not limited in this application.
- Authentication service network element used for authentication services, generating keys to realize two-way authentication of terminal equipment, and supporting a unified authentication framework.
- the authentication service network element may be an AUSF network element.
- the authentication service function network element may still be an AUSF network element, or may have other names, which are not limited in this application.
- Network opening function network element used to provide customized functions for network opening.
- the network exposure function network element may be a network exposure function (network exposure function, NEF) network element.
- NEF network exposure function
- the network exposure function network element is still It may be an NEF network element, or may have other names, which are not limited in this application.
- the 5G communication system can also open 5GC-supported capabilities to external application function network elements through NEF network elements, such as providing small data transmission capabilities.
- the above-mentioned network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
- the above-mentioned network elements or functions can be divided into one or more services, and further, there may also be services that exist independently of network functions.
- an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or a service instance existing independently of the network function may be referred to as a service instance.
- the AF network element may be referred to as AF
- the NEF network element may be referred to as NEF
- the AMF network element may be referred to as AMF. That is, the AF described in the subsequent application can be replaced by an application function network element, the NEF can be replaced by a network opening function network element, and the AMF can be replaced by an access and mobility management network element.
- the above-mentioned network element or functional network element may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
- the above-mentioned network elements or functions can be divided into one or more services, and further, there may also be services that exist independently of network functions.
- an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or a service instance existing independently of the network function may be referred to as a service instance.
- N1 the interface between the AMF and the terminal, which can be used to transmit QoS control rules and the like to the terminal.
- N2 the interface between the AMF and the RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.
- N3 the interface between the RAN and the UPF, mainly used to transfer the uplink and downlink user plane data between the RAN and the UPF.
- N4 The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. Information reporting.
- N5 the interface between the AF and the PCF, which can be used for sending application service requests and reporting network events.
- N6 the interface between UPF and DN, used to transfer the uplink and downlink user data flow between UPF and DN.
- N7 the interface between PCF and SMF, which can be used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.
- protocol data unit protocol data unit
- PDU protocol data unit
- N8 The interface between AMF and UDM, which can be used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register terminal current mobility management related information with UDM.
- N9 a user plane interface between UPF and UPF, used to transmit uplink and downlink user data flows between UPFs.
- N10 the interface between SMF and UDM, which can be used for SMF to obtain session management-related subscription data from UDM, and for SMF to register terminal current session-related information with UDM.
- N11 the interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to terminals, transfer radio resource control information sent to RAN, etc.
- N12 the interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, which can carry SUCI as a subscription identifier;
- N13 the interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.
- FIG. 1 shows a schematic architecture diagram of a 5G system 200b to which this embodiment of the present application applies.
- FIG. 1 is a schematic diagram of a 5G network architecture based on a service interface.
- the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):
- UE UE, (R)AN, AMF network element, SMF network element, UPF network element, PCF network element, UDM network element, AF network element, DN, NSSF, AUSF, UDM, NEF network element, UDR, etc.
- Nnssf, Nudr, Nausf, Nnef, Namf, Npcf, Nsmf, Nudm, and Naf in (b) in Figure 1 are the service interfaces provided by the above-mentioned NSSF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM, and AF, respectively , which is used to call the corresponding service-oriented operation.
- N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers may refer to the meanings defined in the third generation partnership project (3rd generation partnership project, 3GPP) standard agreement, and no limitation is made here.
- the AMF, SMF, UPF, PCF, NEF, etc. shown in (a) in Figure 1 or (b) in Figure 1 can be understood as network elements for implementing different functions, for example, they can be combined into Network slicing. These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
- the method provided in this embodiment of the present application may be applied to a 5G communication system, for example, the communication system shown in (a) in FIG. 1 or (b) in FIG. 1 .
- this embodiment of the present application does not limit the applicable scenarios of the method, for example, it is also applicable to other network architectures including network elements capable of implementing corresponding functions.
- the 6th generation communication the 6th generation, 6G system architecture, etc.
- the names of the various network elements used above in the embodiments of the present application may keep the same function in the future communication system, but the names will be changed.
- PDU session an association between a terminal device and a data network (DN), used to provide a PDU connection service.
- DN data network
- QoS flow mechanism The current standard stipulates that QoS flow is the minimum QoS control granularity, and each QoS flow has a corresponding QoS configuration.
- the QoS parameters included in the QoS configuration describe the specific QoS requirements.
- the QoS parameters mainly include:
- QoS flow index QoS flow index, QFI
- service quality identifier 5G quality of service identifier, 5QI
- allocation and reservation priority allocation and retention priority, ARP
- guaranteed flow bit rate guaranteed flow bit rate, GFBR
- maximum flow bit rate maximum flow bit rate, MFBR
- the 5QI in the QoS parameter is a set of QoS feature combination indexes, and the QoS features include:
- Resource type (resource type), priority (priority level, PL), packet delay budget (packet delay budget, PDB), packet error rate (packet error rate, PER), statistical period (averaging window) and maximum burst data volume (maximum data burst volume), etc.
- resource types include: non-guaranteed bit rate (non-GRB), minimum guaranteed bit rate (guaranteed bit rate, GRB), delay-sensitive GRB (delay-critical GBR); the maximum burst data volume is Delay-sensitive GRB-specific parameters.
- the PDB is used to indicate the upper limit of the transmission delay from the UE to the UPF, and the PDB of the uplink and downlink data is the same.
- PER represents the upper bound of the packet loss rate.
- PL is used to indicate that a PDB that cannot satisfy multiple QoS flows, prioritizes the QoS requirements with high priority (for example, a small PL value), for example, in the case of congestion, when one or more QoS flows cannot satisfy all QoS When required, the QoS flow can be prioritized according to the priority level.
- high priority for example, a small PL value
- 5QI is a scalar used to index to the corresponding 5G QoS feature.
- 5QI is divided into standardized 5QI, pre-configured 5QI and dynamically allocated 5QI.
- a standardized 5QI it corresponds to a set of standardized 5G QoS characteristic values;
- a pre-configured 5QI the corresponding 5G QoS characteristic value is pre-configured on the access network element;
- the characteristics are sent to the network elements of the access network by the core network equipment through the QoS profile (QoS profile).
- QFI is used to identify the unique identifier of different QoS flows within a PDU session.
- ARP includes priority level, preemption capability and preemption capability.
- GFBR represents the bit rate expected to be provided to the guaranteed bit rate (guaranteed bit rate, GBR) QoS flow (flow).
- MFBR limits the bit rate provided to GBR QoS flow, that is, the maximum bit rate provided to GBR QoS flow. Packets can be dropped if the bit rate is exceeded.
- the standard defines a part of 5QI QoS characteristic values, which can be used directly, and also allows operators and/or equipment manufacturers to allocate non-conflicting 5QIs and pre-set corresponding QoS characteristic values for use in operator networks.
- the 5G control plane network elements AMF and SMF deliver the QoS flow configuration to UE, RAN, and UPF.
- QoS model In order to ensure the end-to-end service quality of the business, a QoS model based on QoS flow (flow) is proposed.
- the QoS model supports QoS flow with guaranteed bit rate (ie GBR QoS flow) and QoS flow without guaranteed bit rate (ie non-GBR (non-GBR) QoS flow). Packets controlled by the same QoS flow receive the same transmission processing (such as scheduling, admission threshold, etc.).
- one or more data connection sessions (such as PDU sessions) can be established with the network; each data connection session can transmit data flows corresponding to one or more QoS flows.
- Each QoS flow is identified by a QoS flow identifier (QFI), which uniquely identifies a QoS flow in the same data connection session.
- QFI QoS flow identifier
- each QoS flow corresponds to a data radio bearer (data radio bearer, DRB), and a DRB can correspond to one or more QoS flows.
- a QoS flow is a GBR QoS flow or a Non-GBR QoS flow is determined by the corresponding QoS file (QoS profile).
- the corresponding QoS file contains the following QoS parameters: 5QI, ARP, GFBR, MFBR, and/or QNC.
- the GBR QoS flow is determined as the GRB QoS flow that needs notification control (notification control) and the GBR QoS flow that does not need notification control.
- the access network element detects that the corresponding QoS flow resource cannot be satisfied, the access network element notifies the session management function SMF of the event (that is, the QoS flow resource corresponding to the GBR QoS flow cannot satisfied). Further SMF can initiate QoS flow deletion or QoS flow modification process (for example, modify QoS parameters of QoS flow).
- the corresponding QoS file contains the following QoS parameters: 5QI, ARP and/or RQA.
- PL Indicates the priority of scheduling resources in the QoS Flow, which can be used to identify the QoS Flow corresponding to the data flow of the same UE, and can also be used to identify the QoS Flow corresponding to the data flow of different UEs. In the case of congestion, when the current resources cannot support one or more QoS Flows to meet the corresponding QoS requirements (such as PDB, PER, etc.), PL is used to select which QoS Flows correspond to the QoS requirements.
- General packet radio service tunneling protocol user (general packet radio service tunneling protocol user, GTP-U) tunnel: During the establishment of the PDU session, the connection between the RAN and the UPF will use the GTP-U tunnel, which will come from Data on the UE side or data destined for the UE side is added to the tunnel for transmission.
- GTP-U general packet radio service tunneling protocol user
- Tunnel Endpoint Identifier It is the tunnel endpoint of the GTP-U protocol, which can uniquely determine a section of tunnel between two network elements.
- QoE Quality of Experience
- XR Extended Reality
- each QoS flow is only expressed by a set of QoS parameters, and a QoS flow has only one parameter such as 5QI, that is, only one scheduling priority, which cannot be guaranteed when the network is blocked.
- 5QI the number of data streams to QoE.
- different data streams will not be scheduled differently according to the importance of data streams to QoE. For example, how to implement priority scheduling of data streams with high importance to QoE to meet the transmission of these data streams After the QoS requirements are met, the data flows with low importance to QoE are scheduled, and the differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow is realized.
- this application provides a communication method, by configuring multiple scheduling priorities for different types of data packets mapped by a QoS flow, in order to achieve different types of data blocks corresponding to a single QoS flow Differentiated scheduling of packets.
- the embodiments shown below do not specifically limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run to provide the method according to the embodiment of the present application.
- the execution subject of the method provided by the embodiment of the present application may be a core network device, or a functional module in the core network device that can call a program and execute the program.
- for indicating can be understood as “enabling”, and “enabling” can include direct enabling and indirect enabling.
- enabling can include direct enabling and indirect enabling.
- information for enabling A it may include that the information directly enables A or indirectly enables A, but it does not mean that A must be carried in the information.
- the information enabled by the information is called the information to be enabled.
- the information to be enabled can be directly enabled.
- the to-be-enabled information may also be indirectly enabled by enabling other information, where there is an association relationship between the other information and the to-be-enabled information.
- specific information can also be enabled by means of a pre-agreed (for example, protocol-specified) arrangement order of each information, thereby reducing the enabling overhead to a certain extent.
- common parts of each information can be identified and enabled uniformly, so as to reduce the enabling overhead caused by enabling the same information separately.
- pre-configuration may include pre-definition, for example, protocol definition.
- predefinition for example, protocol definition.
- "predefine” can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the device (for example, including each network element), and this application does not limit its specific implementation.
- the "storage" mentioned in the embodiment of the present application may refer to saving in one or more memories.
- the one or more memories may be provided independently, or may be integrated in an encoder or decoder, a processor, or a communication device.
- a part of the one or more memories may also be provided separately, and a part may be integrated in a decoder, a processor, or a communication device.
- the type of the storage may be any form of storage medium, which is not limited in this application.
- the "protocol” involved in the embodiment of this application may refer to a standard protocol in the communication field, for example, it may include 5G protocol, new radio (new radio, NR) protocol and related protocols applied in future communication systems. Applications are not limited to this.
- the access network device is RAN
- the mobility management function network element is AMF
- the application function network element is AF
- the session management function network element is SMF
- the user plane function network element is UPF
- the terminal is UE. Example to illustrate.
- Fig. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application, including the following steps:
- the AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks.
- the multiple data blocks of different types may be two or more data blocks of different types.
- the type of the data block involved in this embodiment of the present application may be a frame type such as an I frame, a P frame, a B frame, and the like.
- the type of the data block may also indicate the position of the user's field of vision, such as the center position and the edge position.
- the type of data block can also indicate the level corresponding to the data block, such as base layer, enhancement layer, etc.
- data blocks with different levels can be understood as: data blocks have different functions. For example, some are to ensure that the basic video can be played smoothly, but the definition may not be high. These are the basic layers; Better definition, more details, better user experience, these are enhancement layers.
- data blocks are just examples.
- the protection scope of the present application is not limited in any way, and data blocks can also be classified in other ways, for example, original stream, error correction stream, and so on. Examples are not given here.
- the AF may arbitrarily indicate that the two data blocks are data blocks of different types, and the scheduling priorities of the two data blocks are different.
- multiple data blocks of different types correspond to different scheduling priorities.
- I frame and P frame are data blocks of different types, and the scheduling priority corresponding to I frame is higher than the scheduling priority corresponding to P frame;
- the scheduling priority corresponding to the data block at the edge of the view is higher; for another example, the scheduling priority corresponding to the base layer data block is higher than the scheduling priority corresponding to the enhancement layer data block.
- the AF may determine that different types of data blocks correspond to different scheduling priorities according to the configuration information.
- the AF may determine that different types of data blocks correspond to different scheduling priorities according to an instruction of the network management device.
- the AF may determine that different types of data blocks correspond to different scheduling priorities according to historical data transmission results.
- the manner in which the above-mentioned AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks is only an example, and does not constitute any limitation on the protection scope of the present application. In this embodiment of the present application, there is no limitation on how the AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks.
- the data block involved in this embodiment of the present application includes at least one data packet, for example, the data block may be a frame, a slice (slice), or a block (tile).
- the data packets in the above-mentioned multiple data blocks of different types are all mapped to the same QoS flow.
- Multiple different types of data blocks correspond to the same quality of service QoS flow; or, it can be understood as multiple different types of data blocks carried in the same QoS flow; or it can also be understood as multiple different types of data blocks corresponding to multiple Different scheduling priorities are used to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the configuration of the scheduling priority corresponding to each type of data block can be realized through the control plane through the instruction information, as shown in Figure 2
- the method flow shown also includes:
- the AF sends indication information to the PCF.
- the indication information is used to indicate the scheduling priority corresponding to each type of data block.
- the AF sending the indication information to the PCF may be that the AF directly sends the indication information to the PCF, for example, the AF uses the communication interface between the AF and the PCF (for example, N5) or through the service interface (for example, Naf and Npcf) send indication information to the PCF.
- the communication interface between the AF and the PCF for example, N5
- the service interface for example, Naf and Npcf
- the sending of the indication information by the AF to the PCF may be that the AF indirectly sends the indication information to the PCF, for example, the AF sends the indication information to the PCF through other functional network elements (eg, NEF, etc.).
- the AF indirectly sends the indication information to the PCF, for example, the AF sends the indication information to the PCF through other functional network elements (eg, NEF, etc.).
- the indication information is used to indicate the scheduling priority corresponding to each type of data block. It can be understood that the AF sends indication information to the PCF, and the indication information indicates multiple scheduling priorities corresponding to multiple data blocks of different types. .
- the indication information is included in the message currently sending the QoS requirement, and the scheduling priority corresponding to each type of data block can also be understood as a QoS requirement.
- the indication information may be included in other messages (eg, existing or newly added messages between the AF and the PCF).
- the PCF After the PCF receives the above indication information, it can send the scheduling priority corresponding to each type of data block to the SMF, and the method flow shown in FIG. 2 also includes:
- the PCF sends the scheduling priority corresponding to each type of data block to the SMF.
- the PCF sends the scheduling priority corresponding to each type of data block to the SMF, which may be implemented by sending multiple scheduling priorities and mapping relationships corresponding to multiple data blocks of different types, wherein the mapping relationship includes Mapping relationships between multiple different types of data blocks and multiple scheduling priorities.
- the mapping relationship is used to indicate that the I frame corresponds to the scheduling priority #1, and the P frame corresponds to the scheduling priority #2.
- scheduling priority #1 is higher than scheduling priority #2.
- the mapping relationship is used to indicate that the data block in the center of the user's field of view corresponds to scheduling priority #3, and the The data blocks at the edge of the user's field of view correspond to scheduling priority #4, wherein scheduling priority #3 is higher than scheduling priority #4.
- the PCF sends the above mapping relationship to the SMF, so that the SMF configures the scheduling priority corresponding to the data block to the UPF.
- the scheduling priority corresponding to each type of data block above can be sent to SMF through the policy and charging control rule (PCC rule), that is, each type of data block
- PCC rule policy and charging control rule
- the corresponding scheduling priority is included in the PCC rule.
- the PCC rule also includes information for indicating the scheduling priority of the QoS flow.
- the scheduling priority of the differential scheduling of data packets of different types of data blocks corresponding to the same QoS flow (that is, the scheduling priority corresponding to each type of data block mentioned above) can be called the first scheduling priority ;
- the scheduling priority of this QoS flow may be called the second scheduling priority.
- the above-mentioned second scheduling priority may be included in the PCC rule.
- multiple first scheduling priorities are within the QoS flow, and a second scheduling priority is responsible for external scheduling priority comparisons.
- the QoS is determined by comparing the second scheduling priority with other QoS flows. After the scheduling priorities between flows, the scheduling priorities of different types of data packets inside the QoS flow are determined through multiple first scheduling priorities.
- the above-mentioned second scheduling priority may not be included in the PCC rule.
- the PCC rule includes multiple first scheduling priorities. Since the scheduling priority determination principles are the same, these multiple first scheduling priorities need to consider the scheduling priorities between QoS flows at the same time, which is equivalent to if the first scheduling priority It is QFI#1 packet 1 (scheduling priority is 1), QFI#1 packet 2 (scheduling priority is 3), but the scheduling priority of another QoS flow is QFI#2 packet 1 (scheduling priority is 2), Then the scheduling sequence is QFI#1 packet 1, QFI#2 packet 1, QFI#1 packet 2. In this case, the second scheduling priority may not be included in the PCC rule.
- the SMF receives the PCC rule, it performs UPF configuration, and the method flow shown in Figure 2 also includes:
- the SMF configures the UPF.
- the SMF configuring the UPF includes: the SMF sends encapsulation indication information to the UPF, and the encapsulation indication information is used to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.
- encapsulating the scheduling priority corresponding to the data packet in the data packet includes: encapsulating the scheduling priority corresponding to the data packet in a header of the data packet, for example, encapsulating in a GTP-U header.
- the scheduling priority corresponding to the data packet may also be encapsulated in the payload of the data packet, which is not limited in this application.
- the SMF in order to enable UPF to encapsulate the scheduling priority corresponding to the received data packet into the data packet, the SMF also needs to send the scheduling priority corresponding to each type of data block to the UPF during the process of configuring the UPF, so that After the UPF receives the data packet, it determines the scheduling priority of the data packet.
- the SMF sends the scheduling priority corresponding to each type of data block to the UPF, which can be realized by sending multiple scheduling priorities and mapping relationships corresponding to multiple different types of data blocks, wherein the mapping The relationship includes a mapping relationship between multiple data blocks of different types and multiple scheduling priorities.
- the SMF sends the scheduling priority corresponding to each type of data block to the UPF, which can be realized by sending the scheduling priority identifier and corresponding relationship corresponding to each type of data block, wherein the corresponding relationship includes The corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers.
- the SMF needs to assign a scheduling priority identifier to the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks.
- the method flow shown in FIG. 2 also includes:
- the SMF allocates a scheduling priority identifier.
- the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block.
- the SMF may notify the RAN of the scheduling priorities of multiple different types of data blocks and the correspondence between multiple scheduling priority identifiers.
- FIG. 2 The illustrated method flow may also include:
- the SMF sends the corresponding relationship to the RAN.
- the corresponding relationship is used to indicate the correspondence between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers.
- the SMF configuring the UPF may also include: the SMF also sends encapsulation information to the UPF, the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet, the identification The information is used to identify the data block to which the data packet belongs.
- the encapsulation indication information and the encapsulation information may be one indication information or multiple indication information.
- the identification information is encapsulated in the data packet, including: the identification information is encapsulated in the header of the data packet; or, the identification information may also be encapsulated in the payload of the data packet, which is not limited in this application.
- the SMF configures the parameters of the QoS flow according to the received PCC rule.
- the method flow shown in Figure 2 also includes:
- the SMF configures parameters of the QoS flow.
- SMF configures the parameters of QoS flow based on the above-mentioned multiple different scheduling priorities. It can be understood that one QoS flow corresponds to multiple scheduling priorities. Among them, the parameters for configuring QoS flow can be understood as the strategy for configuring QoS flow.
- SMF configures the parameter of QoS flow (also can be referred to as policy), also can be referred to as the parameter that SMF sends QoS flow to UPF, RAN and/or UE.
- QoS flow also can be referred to as policy
- SMF sends QoS flow to UPF, RAN and/or UE.
- Step 1 SMF determines the information of QoS flow (also called QoS policy) according to the PCC rule sent by PCF.
- QoS policy also called QoS policy
- Step 2 SMF issues corresponding QoS policies to UPF, RAN and UE respectively.
- the SMF sends the first QoS policy to the UPF
- the SMF sends the second QoS policy to the RAN
- the SMF sends the third QoS policy to the UE.
- the SMF sends the first QoS policy to the UPF, including: the SMF sends packet detection rules (Packet Detection Rule, PDRs) to the UPF.
- PDRs Packet Detection Rule
- the SMF sends the second QoS policy to the RAN, including: the SMF sends the QoS file (profile) to the RAN through the AMF.
- the SMF sends the third QoS policy to the UE, including: the SMF sends the QoS rule (QoS rule) to the UE through the AMF and the RAN, and the QoS rule includes QoS control information.
- QoS rule QoS rule
- the RAN establishes the DRB of the air interface according to the QoS file, and stores the binding relationship between the QoS flow and the DRB.
- the UE executes the uplink data packet according to the QoS rule The transmission.
- the UPF performs QFI identification on the downlink data packet according to the PDRs, and performs QFI verification on the uplink data packet.
- the AF may be notified through a response message so as to facilitate the AF to perform downlink data transmission.
- the method flow shown in FIG. 2 also includes:
- the SMF sends a response message to the PCF.
- the response message is used to indicate that the parameter configuration of the QoS flow is completed.
- the PCF sends a response message to the AF.
- the AF After the AF receives the response message, it knows that the parameter configuration of the QoS flow is completed, and the downlink data transmission can be performed; or it is understood that the AF performs downlink data transmission in response to the response message, and the method flow shown in FIG. 2 also includes:
- the AF sends downlink data to the UPF.
- the downlink data includes a data packet and indication information for indicating the type of the data block to which the data packet belongs.
- the indication information indicating the type of the data block to which the data packet belongs may be referred to as type indication information, and the type indication information may be used to indicate the type of the data block, for example, indicating whether the data block is an I frame or a P frame; For another example, indicate whether the data block is located at the center of the user's field of view or at the edge of the user's field of view; and for another example, indicate whether the data block is a base layer data block or an enhancement layer data block.
- the data packet and the indication information used to indicate the type of the data block to which the data packet belongs can be transmitted separately, for example, the data packet and the type indication information are two independent information elements, included in the same message middle.
- the data packet and the indication information used to indicate the type of the data block to which the data packet belongs can be transmitted at the same time, for example, the type indication information is encapsulated in the header of the data packet to indicate that the data packet The type of the data block it belongs to.
- the above-mentioned type indication information may be called first indication information, indication information, and so on.
- the downlink data may also include identification information of the data block to which the data packet belongs.
- the identification information of the data block includes, but not limited to, an identification (identify, ID) of the data block, attribute information of the data block, and other information that can be used to identify the data block.
- the identification information of the data block and the above-mentioned data packet and type indication information may be included in the same message.
- the application network element sends a message to the user plane network element, and the message includes a data packet, type indication information for indicating the data block to which the data packet belongs, and identification information of the data block to which the data packet belongs.
- the UPF After the UPF receives the downlink data, it can determine the scheduling priority of the data packet according to the configuration of the above-mentioned SMF (refer to the description in the above-mentioned step S240), the received data packet and the type indication information, and the method flow shown in FIG. include:
- the UPF determines the scheduling priority of the data packet.
- the UPF determines the type corresponding to the data block to which the data packet belongs according to the type indication information, and determines the scheduling priority of the received data packet according to a scheduling priority corresponding to each type of data block configured in the above SMF.
- the UPF encapsulates the information indicating the scheduling priority of the data packet in the data packet, and the method flow shown in FIG. 2 also includes:
- the UPF encapsulates the data packet.
- the UPF encapsulating the data packet includes: UPF encapsulating the scheduling priority of the data packet in the data packet.
- UPF encapsulates the scheduling priority of the data packet into the GTP-U packet header.
- the UPF encapsulating the data packet includes: the UPF encapsulating the scheduling priority identifier used to identify the scheduling priority in the data packet.
- the UPF encapsulates the scheduling priority identifier of the scheduling priority of the data packet into the GTP-U packet header.
- the UPF encapsulating the data packet includes: UPF encapsulating the identification information of the data block to which the data packet belongs in the data packet.
- UPF encapsulates the identification information of the data block to which the data packet belongs into the GTP-U packet header.
- the UPF can send the encapsulated data packet to the RAN, and the method flow shown in Figure 2 also includes:
- the UPF sends the data packet to the RAN.
- the UPF sends the GTP-U data packet to the RAN.
- the RAN may process the received data packet, and the method flow shown in FIG. 2 also includes:
- the RAN processes the data packet.
- the RAN processing the data packet includes the following steps 1 to 4:
- Step 1 The RAN decapsulates the data packet to determine the scheduling priority of the data packet.
- the RAN determines the scheduling priority of the data packet according to the information indicating the scheduling priority corresponding to the data packet encapsulated in the data packet (eg, GTP-U header).
- the scheduling priority corresponding to the data packet is encapsulated in the data packet, and the RAN can obtain the scheduling priority corresponding to the data packet after decapsulating the data packet.
- the data packet encapsulates the scheduling priority identifier of the scheduling priority corresponding to the data packet, and after the RAN decapsulates the data packet, obtains the scheduling priority of the scheduling priority corresponding to the data packet identification, and further determine the scheduling priority corresponding to the data packet according to the corresponding relationship received from the SMF (refer to the description of the above step S232).
- the RAN also performs the following step 2.
- Step 2 The RAN decapsulates the data packet to determine the identification information of the data block to which the data packet belongs.
- the RAN After the RAN determines the scheduling priority of the data packet, or determines the scheduling priority of the data packet and the identification information of the data block to which the data packet belongs, it can map the data packet according to the scheduling priority of the data packet and other parameters of the QoS flow of the data packet (for example, the 5QI specified in the current agreement) performs QoS processing; or, in the case of determining the identification information of the data block to which the data packet belongs, the data with the same identification information can be determined according to the identification information of the data block to which the data packet belongs Packet processing, including determining the scheduling of data packets with the same identification information.
- Step 3 RAN schedules the data packets.
- the scheduling priority of the data packet can also be understood as a kind of QoS parameter, which is a newly added QoS parameter.
- the RAN receives multiple data packets (eg, data packet #1, data packet #2 and data packet #3) mapped to the same QoS flow.
- the scheduling priorities corresponding to the plurality of data packets are different. For example, data packet #1 corresponds to scheduling priority #1, data packet #2 corresponds to scheduling priority #2, and data packet #3 corresponds to scheduling priority #3. Priority #1 is higher than scheduling priority #2, and scheduling priority #2 is higher than scheduling priority #3.
- Processing the data packets by the RAN includes: sending each data packet according to the scheduling priority corresponding to each data packet. For example, data packet #1 is scheduled (or sent) first, then data packet #2 is scheduled, and data packet #3 is finally scheduled to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the RAN processing the data packet further includes:
- the RAN expands the transmission granularity according to the identification information of the data block, from packet granularity transmission to data block (frame, tile or slice) granularity transmission. For example, if some data packets in a data block cannot be successfully received due to reasons such as discarding during transmission, the RAN may not schedule resources for other data packets with the same identification information of the data block. The scheduling of the association relationship between them can avoid the problem that although the data packet is successfully transmitted, it cannot be decoded to a certain extent, thereby improving the transmission efficiency.
- the RAN can schedule resources in advance for other data packets with the identification information of the same data block to which the successfully received data packets belong, which can reduce the number of data packets to a certain extent. transmission delay.
- the resource scheduling of the data packet by the RAN can be understood as allocating resources for the data packet, and the priority scheduling can be understood as prioritizing the allocation of RAN-related resources to the data packet according to the QoS requirements of the data packet, so that the data packet can be successfully sent .
- the RAN may send the received data packet to the UE, and perform step 4.
- Step 4 When the RAN receives the downlink data packet, according to the QFI in the data packet header and the binding relationship between the corresponding QoS flow and the DRB, the downlink data packet is placed on the corresponding DRB for transmission.
- the above is just the downlink data as an example to illustrate the differential scheduling of data packets of different types of data blocks corresponding to the same QoS flow.
- the QoS flow is determined according to the QoS rule, in order to realize the differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow, the terminal device is sending Before the uplink data packet, when informing the access network device that there is uplink data to be sent through the Physical Uplink Control Channel (PUCCH), the type of the data block to which the uplink data packet belongs must be informed at the same time, and the uplink scheduler according to the data
- the block type allocates the resources required for sending data packets to the terminal device. Different data block types may allocate different resources (size, location, etc.), so as to realize the data packets of different types of data blocks
- the network elements in the existing network architecture are mainly used as examples for illustration (such as AF, AMF, SMF, etc.), and it should be understood that the specific form of the network element
- the application examples are not limited. For example, network elements that can implement the same function in the future are applicable to this embodiment of the application.
- the methods and operations implemented by network equipment can also be implemented by components (such as chips or circuits) that can be used in network equipment.
- each network element includes a corresponding hardware structure and/or software module for performing each function.
- the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle.
- the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
- FIG. 3 is a schematic block diagram of an apparatus 300 provided by an embodiment of the present application.
- the device 300 includes a transceiver unit 310 and a processing unit 320 .
- the transceiver unit 310 can implement a corresponding communication function, and the processing unit 320 is used for data processing.
- the transceiver unit 310 may also be called a communication interface or a communication unit.
- the device 300 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 320 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
- a storage unit which may be used to store instructions and/or data
- the processing unit 320 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
- the apparatus 300 can be used to execute the actions performed by the network equipment (such as each network element, access network equipment, etc.) in the above method embodiments.
- the apparatus 300 can be a network equipment or a component that can be configured in the network equipment
- the transceiving unit 310 is configured to perform transceiving-related operations on the network device side in the above method embodiments
- the processing unit 320 is configured to perform processing-related operations on the network device side in the above method embodiments.
- the apparatus 300 is configured to perform the actions performed by the AF in the above method embodiments.
- the processing unit 320 is configured to determine a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS flow;
- the transceiver unit 310 is configured to send indication information to the policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, where each data block includes at least one data packet.
- the indication information is included in the quality of service QoS requirements, the QoS requirements are used to configure the parameters of the QoS flow, and the transceiver unit 310 is also used to receive a response message from the policy control network element, the response message is used to indicate The parameter configuration of the QoS flow is completed; the transceiver unit 310 is also configured to send downlink data to the user plane network element, the downlink data includes a data packet and indication information for indicating the type of the data block to which the data packet belongs.
- the apparatus 300 may implement steps or processes corresponding to the AF execution method in the method embodiment according to the embodiment of the present application, and the apparatus 600 may include a unit for executing the AF execution method in the method embodiment. Moreover, each unit in the apparatus 600 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in AF in the method embodiment.
- the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S220, S252 and S260; the processing unit 320 can be used to execute the processing steps in the method, such as step S210.
- the apparatus 300 is configured to perform the actions performed by the PCF in the above method embodiments.
- the transceiver unit 310 is configured to receive indication information from the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the plurality of data blocks of different types The data packets in are mapped to the same QoS flow; the transceiver unit 310 is configured to send the scheduling priority corresponding to each type of data block to the session management network element.
- the transceiving unit 310 is also configured to receive a response message from the session management network element, the response message is used to indicate that the parameter configuration of the QoS flow is completed; the transceiving unit 310 is also configured to send the response to the application network element information.
- the apparatus 300 may implement the steps or processes corresponding to the PCF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the PCF execution method in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in the PCF in the method embodiment.
- the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S220, S230 and S251; the processing unit 320 can be used to execute the processing steps in the method.
- the apparatus 300 is configured to perform the actions performed by the SMF in the above method embodiments.
- the transceiver unit 310 is configured to receive the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all mapped to the same In a quality of service QoS flow; the transceiver unit 310 is configured to send the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate that the user plane network element will receive
- the scheduling priority corresponding to the received data packet is encapsulated in the data packet, wherein each data block includes at least one data packet.
- the processing unit 320 is configured to configure the parameters of the QoS flow according to the PCC rule; the sending unit is also configured to send a response message to the policy control network element, and the response message is used to indicate that the parameter configuration of the QoS flow is completed.
- the processing unit 320 is configured to assign a scheduling priority identifier to the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, and the scheduling priority identifier is used to identify each type The scheduling priority corresponding to the data block; the sending unit is also used to send the scheduling priority identifier and corresponding relationship corresponding to each type of data block to the user plane network element, wherein the corresponding relationship includes the plurality of different types of The corresponding relationship between the scheduling priority of the data block and multiple identifiers of the scheduling priority.
- the transceiving unit 310 is further configured to send the correspondence between multiple scheduling priorities of different types of data blocks and multiple scheduling priority identifiers to the access network device.
- the transceiver unit 310 is also configured to send encapsulation information to the user plane network element, the encapsulation information is used to instruct the user plane network element to encapsulate identification information in the data packet, and the identification information is used to identify the data packet The data block it belongs to.
- the apparatus 300 may implement the steps or processes corresponding to the SMF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the SMF execution method in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the SMF in the method embodiment.
- the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S230, S232 and S251; the processing unit 320 can be used to execute the processing steps in the method, such as step S231, S240 and S250.
- the apparatus 300 is configured to perform actions performed by the UPF in the above method embodiments.
- the transceiver unit 310 is configured to receive downlink data from the application network element, the downlink data includes a plurality of different types of data blocks, each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority, and the plurality of different types of data blocks corresponds to a scheduling priority.
- the data packets in the different types of data blocks are all mapped to the same QoS flow, and each of the data blocks includes at least one data packet; the processing unit 320 is used for according to the corresponding type of each data packet and the value of each type A scheduling priority corresponding to the data block determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet encapsulates information indicating the scheduling priority of the data packet.
- the transceiving unit 310 is also configured to receive scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, where the encapsulation indication information is used to indicate the user plane network element to receive The scheduling priority corresponding to the data packet is encapsulated in the data packet.
- the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority
- the transceiver unit 310 is further configured to receive the scheduling priority identifier and the corresponding relationship from the session management network element, the scheduling The priority identifier is used to identify the scheduling priority corresponding to each type of data block, and the corresponding relationship includes the corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers.
- the transceiving unit 310 is further configured to receive, from the application network element, identification information of the data block to which the data packet belongs.
- the identification information is encapsulated in the data packet
- the transceiver unit 310 is further configured to receive encapsulation information from the session management network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet
- the identification information is used to identify the data block to which the data packet belongs.
- the apparatus 300 may implement the steps or processes corresponding to the UPF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the UPF execution method in the method embodiment.
- each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding procedures of the method embodiment in the UPF in the method embodiment.
- the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S260 and S290; the processing unit 320 can be used to execute the processing steps in the method, such as steps S240, S270 and S280.
- the apparatus 300 is configured to perform the actions performed by the RAN in the above method embodiments.
- the transceiver unit 310 is configured to receive a plurality of data packets from the user plane network element, each of the plurality of data packets is encapsulated with information indicating the scheduling priority corresponding to the data packet; the plurality of data packets belong to Multiple different types of data blocks, each type of data block in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same quality of service QoS flow Middle; the processing unit 320 is configured to process the data packet according to the scheduling priority.
- the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority
- the transceiver unit 310 is further configured to receive scheduling priority of multiple different types of data blocks from the session management network element The corresponding relationship between a level and multiple scheduling priority identifiers.
- the data packet is also encapsulated with identification information of the data block to which the data packet belongs, and the processing unit 320 is also configured to determine whether to schedule a data block belonging to the same data block as the data packet according to the identification information. Packets other than packets.
- the apparatus 300 may implement the steps or procedures corresponding to the execution of the RAN in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the method executed by the RAN in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in the RAN in the method embodiment.
- the transceiving unit 310 can be used to execute the transceiving steps in the method, such as steps S232 and S290; the processing unit 320 can be used to execute the processing steps in the method, such as step S291.
- the processing unit 320 in the above embodiments may be implemented by at least one processor or processor-related circuits.
- the transceiver unit 310 may be implemented by a transceiver or transceiver-related circuits.
- the storage unit can be realized by at least one memory.
- the embodiment of the present application further provides an apparatus 400 .
- the apparatus 400 includes a processor 410 and may further include one or more memories 420 .
- the processor 410 is coupled with the memory 420, and the memory 420 is used to store computer programs or instructions and/or data, and the processor 410 is used to execute the computer programs or instructions and/or data stored in the memory 420, so that the methods in the above method embodiments be executed.
- the apparatus 400 includes one or more processors 410 .
- the memory 420 may be integrated with the processor 410, or set separately.
- the apparatus 400 may further include a transceiver 430, and the transceiver 430 is used for receiving and/or sending signals.
- the processor 410 is configured to control the transceiver 430 to receive and/or send signals.
- the apparatus 400 is used to implement operations performed by devices (such as network elements, access network devices, etc.) in the above method embodiments.
- the embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the method performed by the network device (such as each network element, access network device, etc.) in the above method embodiment are stored.
- the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
- the embodiments of the present application also provide a computer program product containing instructions, which when executed by a computer enable the computer to implement the method performed by the network device (such as each network element, access network device, etc.) in the above method embodiment.
- the embodiment of the present application also provides a communication system, the communication system includes the network devices (such as network elements, access network devices, etc.) in the above embodiments, such as access network devices and core network devices.
- the network devices such as network elements, access network devices, etc.
- processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
- a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
- the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory.
- the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be random access memory (RAM).
- RAM random access memory
- RAM can be used as an external cache.
- RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
- static random access memory static random access memory
- dynamic RAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- SDRAM synchronous DRAM
- double data rate SDRAM double data rate SDRAM
- DDR SDRAM double data rate SDRAM
- ESDRAM enhanced synchronous dynamic random access memory
- SLDRAM synchronous connection dynamic random access memory
- Direct memory bus random access memory direct rambus RAM, DR RAM
- the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
- the memory storage module may be integrated in the processor.
- memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
- the disclosed devices and methods may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
- the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
- each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
- the computer may be a personal computer, a server, or a network 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 transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
- the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
- the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) etc.
- the aforementioned available medium may include But not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请实施例提供了一种通信方法和装置,应用于数据包的调度和服务质量保证的领域。该方法包括:应用网元确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,该应用网元向策略控制网元发送指示信息,该指示信息用于指示该每个类型的数据块对应的调度优先级,调度优先级用于指示对不同类型的数据块的数据包进行调度,每个数据块包括至少一个数据包。应用网元确定并下发同一个QoS流对应的多个不同调度优先级,从而实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度,提高用户体验。
Description
本申请要求于2022年2月28日提交中国专利局、申请号为202210184934.X、申请名称为“通信方法和装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信领域,并且更具体地,涉及一种通信方法和装置。
在第五代(5th generation,5G)***中,为了保证业务端到端的服务质量,提出了服务质量(quality of service,QoS)流(flow)。对于一个终端设备(user equipment,UE),当该UE有业务通信需求时,可以与5G网络建立一个或者多个分组数据单元(packet data unit,PDU)会话,每个PDU会话中可以建立(也可以称为配置)一个或者多个承载业务数据流的QoS flow。
目前协议中规定每个QoS flow由一组QoS参数表述,QoS参数包括5G QoS标识(5G QoS identifier,5QI)。对数据流的调度是以QoS flow为粒度。因此无法根据数据流对用户体验重要程度的不同而对同一个QoS flow进行差异化调度。
发明内容
本申请实施例提供一种通信方法,通过配置同一个QoS flow对应的多个调度优先级,以期实现同一个QoS流的差异化调度。
第一方面,提供了一种通信方法,该方法可以由应用网元执行,或者,也可以由应用网元的组成部件(例如芯片或者电路)执行,对此不作限定,为了便于描述,下面以由应用网元执行为例进行说明。
该方法包括:应用网元确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;该应用网元向策略控制网元发送指示信息,该指示信息用于指示该每个类型的数据块对应的调度优先级,其中,每个该数据块包括至少一个数据包。
基于上述技术方案,应用网元可以确定同一个QoS流对应的不同类型的数据块的调度优先级,并通过指示信息通知策略控制网元每个类型的数据块对应的调度优先级,以使得策略控制网元获知同一个QoS流具有多个不同的调度优先级,以期实现同一个QoS流的对应的不同类型的数据块的数据包的差异化调度。
需要说明的是,上述的多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,可以理解为:
多个不同类型的数据块对应同一个服务质量QoS流;或者,可以理解为多个不同类型的数据块承载在同一个QoS流中;或者还可以理解为多个不同类型的数据块中每个类型的数据块对应的调度优先级用于实现同一个QoS流对应的不同类型的数据块的数据包 的差异化调度。
另外,上述的应用网元向策略控制网元发送指示信息可以是应用网元直接向策略控制网元发送指示信息,如,应用网元通过应用网元和策略控制网元之间的通信接口或通过服务化接口向策略控制网元发送指示信息;还可以是,应用网元间接向策略控制网元发送指示信息,如,应用网元通过其他的功能网元向策略控制网元发送指示信息。
结合第一方面,在第一方面的某些实现方式中,该指示信息包括在服务质量QoS需求中,该QoS需求用于配置该QoS流的参数,该方法还包括:该应用网元接收来自策略控制网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该应用网元向用户面网元发送下行数据,该下行数据中包括数据包和用于指示该数据包所属的数据块的类型的指示信息。
基于上述技术方案,应用网元可以将指示信息携带在QoS需求中,即上述的同一个服务质量QoS流中每个类型的数据块对应的调度优先级可以理解为一种QoS需求。该QoS需求用于配置QoS流的参数,在QoS流的参数配置完成之后,可以通过响应消息通知应用网元QoS流的参数配置完成,从而应用网元可以开始传输下行数据。具体地,下行数据中除了包括需要传输的数据包之外,还包括指示该数据包所属的数据块的类型的指示信息,以便于接收数据包的网元根据该类型的指示信息确定数据包所属的数据块的类型,进一步地根据数据包所属的数据块的类型确定数据包的调度优先级,同一个服务质量QoS流对应的不同类型的数据块的数据包的实现差异化调度。
结合第一方面,在第一方面的某些实现方式中,该方法还包括:该应用网元向该用户面网元发送该数据包所属的数据块的标识信息。
基于上述技术方案,应用网元可以将数据包所属的数据块的标识信息发送给用户面网元,以便于用户面网元能够根据该标识信息获知数据包所属的数据块。
结合第一方面,在第一方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
本申请中不同类型的数据块的划分形式可以有多种,提高方案的灵活性。
第二方面,提供了一种通信方法,该方法可以由策略控制网元执行,或者,也可以由策略控制网元的组成部件(例如芯片或者电路)执行,对此不作限定,为了便于描述,下面以由策略控制网元执行为例进行说明。
该通信方法包括:策略控制网元接收来自应用网元的指示信息,该指示信息用于指示多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;该策略控制网元向会话管理网元发送该每个类型的数据块对应的调度优先级。
基于上述技术方案,应用网元通过指示信息通知策略控制网元每个类型的数据块对应的调度优先级,以使得策略控制网元获知同一个QoS流具有多个不同的调度优先级,以期实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
结合第二方面,在第二方面的某些实现方式中,该每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,该PCC rule中还包括用于指示该QoS流的调度优先级的信息。
基于上述技术方案,策略控制网元可以通过PCC rule向会话管理网元发送每个类型的数据块对应的调度优先级,并且该PCC rule中包括指示与其他QoS流相比的调度优先级的信息,以便于确定QoS流之间的调度优先级。
结合第二方面,在第二方面的某些实现方式中,该方法还包括:该策略控制网元接收来自会话管理网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该策略控制网元向该应用网元发送该响应消息。
基于上述技术方案,在QoS流的参数配置完成之后,可以通过响应消息通知应用网元QoS流的参数配置完成,以便于后续应用网元进行下行数据传输。
结合第二方面,在第二方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
本申请中不同类型的数据块的划分形式可以有多种,提高方案的灵活性。
第三方面,提供了一种通信方法,该方法可以由会话管理网元执行,或者,也可以由会话管理网元的组成部件(例如芯片或者电路)执行,对此不作限定,为了便于描述,下面以由会话管理网元执行为例进行说明。
该通信方法包括:会话管理网元接收来自策略控制网元的多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;该会话管理网元向用户面网元发送该每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中,其中,每个该数据块包括至少一个数据包。
基于上述技术方案,会话管理网元能够从策略控制网元接收每个类型的数据块对应的调度优先级,并向用户面网元发送每个类型的数据块对应的调度优先级,以使得用户面网元获知同一个QoS流具有多个不同的调度优先级,以期实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
结合第三方面,在第三方面的某些实现方式中,该每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,该PCC rule中还包括用于指示该QoS流的调度优先级的信息。
基于上述技术方案,策略控制网元可以通过PCC rule向会话管理网元发送每个类型的数据块对应的调度优先级,并且该PCC rule中包括指示与其他QoS流相比的调度优先级的信息,以便于确定QoS流之间的调度优先级。
结合第三方面,在第三方面的某些实现方式中,该方法还包括:该会话管理网元根据该PCC rule配置该QoS流的参数;该会话管理网元向策略控制网元发送响应消息,该响应消息用于指示该QoS流的参数配置完成。
基于上述技术方案,在QoS流的参数配置完成之后,可以通过响应消息通知策略控制网元QoS流的参数配置完成,以便于后续应用网元进行下行数据传输。
结合第三方面,在第三方面的某些实现方式中,该方法还包括:该会话管理网元为该多个不同类型的数据块中的每个类型的数据块对应的调度优先级分配调度优先级标识,该调度优先级标识用于标识该每个类型的数据块对应的调度优先级;该会话管理网元向用户面网元发送该每个类型的数据块对应的调度优先级标识和对应关系,其中,该对应关系包 括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
基于上述技术方案,每个类型的数据块对应的调度优先级可以由调度优先级标识进行标识,为了使得用户面网元获知每个类型的数据块对应的调度优先级,可以将每个类型的数据块对应的调度优先级标识和对应关系发送给用户面网元,以便于用户面网元根据调度优先级标识和对应关系确定不同类型的数据块的调度优先级。
结合第三方面,在第三方面的某些实现方式中,该方法还包括:该会话管理网元向接入网设备发送多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
基于上述技术方案,每个类型的数据块对应的调度优先级可以由调度优先级标识进行标识,为了使得接入网设备获知每个类型的数据块对应的调度优先级,可以将多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系发送给接入网设备,以便于接入网设备根据调度优先级标识和对应关系确定不同类型的数据块的调度优先级。
结合第三方面,在第三方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
本申请中不同类型的数据块的划分形式可以有多种,提高方案的灵活性。
结合第三方面,在第三方面的某些实现方式中,该方法还包括:该会话管理网元向用户面网元发送封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
第四方面,提供了一种通信方法,该方法可以由用户面网元执行,或者,也可以由用户面网元的组成部件(例如芯片或者电路)执行,对此不作限定,为了便于描述,下面以由用户面网元执行为例进行说明。
该通信方法包括:用户面网元接收来自应用网元的下行数据,该下行数据包括多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,每个该数据块包括至少一个数据包;该用户面网元根据各数据包对应的类型以及每个类型的数据块对应的一个调度优先级确定数据包的调度优先级;该用户面网元向接入网设备发送该数据包,该数据包中封装有指示该数据包的该调度优先级的信息。
基于上述技术方案,用户面网元可以将不同数据包的调度优先级的指示信息封装在数据包中,以使得接入网设备获知同一个QoS流中不同数据包的调度优先级,以期实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
结合第四方面,在第四方面的某些实现方式中,该方法还包括:该用户面网元接收来自会话管理网元的每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中。
基于上述技术方案,会话管理网元能够从向用户面网元发送每个类型的数据块对应的调度优先级,以使得用户面网元获知同一个QoS流具有多个不同的调度优先级。
结合第四方面,在第四方面的某些实现方式中,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该方法还包括:该用户面网元接收来自会话管理网元的调度优先级标识和对应关系,该调度优先级标识用于标识该每个类型的数据块对应的 调度优先级,该对应关系包括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
基于上述技术方案,每个类型的数据块对应的调度优先级可以由调度优先级标识进行标识,为了使得用户面网元获知每个类型的数据块对应的调度优先级,可以将每个类型的数据块对应的调度优先级标识和对应关系发送给用户面网元,以便于用户面网元根据调度优先级标识和对应关系确定不同类型的数据块的调度优先级。
结合第四方面,在第四方面的某些实现方式中,该方法还包括:该用户面网元接收来自该应用网元的该数据包所属的数据块的标识信息。
结合第四方面,在第四方面的某些实现方式中,该数据包中封装有该标识信息,该方法还包括:该用户面网元接收来自该会话管理网元的封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
基于上述技术方案,通过数据块标识将包粒度的传输扩展为数据块粒度的传输,避免资源浪费,提升传输效率。
结合第四方面,在第四方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
本申请中不同类型的数据块的划分形式可以有多种,提高方案的灵活性。
第五方面,提供了一种通信方法,该方法可以由接入网设备执行,或者,也可以由接入网设备的组成部件(例如芯片或者电路)执行,对此不作限定,为了便于描述,下面以由接入网设备执行为例进行说明。
该通信方法包括:接入网设备接收来自用户面网元的多个数据包,该多个数据包中的各数据包中封装有指示该数据包对应的调度优先级的信息;该多个数据包归属于多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;该接入网设备根据该调度优先级对该数据包进行处理。
基于上述技术方案,用户面网元可以将不同数据包的调度优先级的指示信息封装在数据包中,以使得接入网设备获知同一个QoS流中不同数据包的调度优先级,以期实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
结合第五方面,在第五方面的某些实现方式中,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该方法还包括:接入网设备接收来自会话管理网元的多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
基于上述技术方案,每个类型的数据块对应的调度优先级可以由调度优先级标识进行标识,为了使得接入网设备获知每个类型的数据块对应的调度优先级,可以将多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系发送给接入网设备,以便于接入网设备根据调度优先级标识和对应关系确定不同类型的数据块的调度优先级。
结合第五方面,在第五方面的某些实现方式中,该数据包中还封装有该数据包所属的数据块的标识信息,该方法还包括:该接入网设备根据该标识信息确定是否调度和该数据包属于同一个数据块中的除该数据包之外的其他数据包。
基于上述技术方案,通过数据块标识将包粒度的传输扩展为数据块粒度的传输,避免 资源浪费,提升传输效率。
结合第五方面,在第五方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
本申请中不同类型的数据块的划分形式可以有多种,提高方案的灵活性。
第六方面,提供了一种通信装置,该通信装置用于执行上述第一方面提供的方法。
该装置包括:处理单元,用于确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;发送单元,用于向策略控制网元发送指示信息,该指示信息用于指示该每个类型的数据块对应的调度优先级,其中,每个该数据块包括至少一个数据包。
结合第六方面,在第六方面的某些实现方式中,该指示信息包括在服务质量QoS需求中,该QoS需求用于配置该QoS流的参数,该装置还包括:接收单元,用于接收来自策略控制网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该发送单元还用于向用户面网元发送下行数据,该下行数据中包括数据包和用于指示该数据包所属的数据块的类型的指示信息。
结合第六方面,在第六方面的某些实现方式中,该发送单元还用于向该用户面网元发送该数据包所属的数据块的标识信息。
结合第六方面,在第六方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
以上第六方面及其可能的设计所示方法的有益效果可参照第一方面及其可能的设计中的有益效果。
第七方面,提供了一种通信装置,该通信装置用于执行上述第二方面提供的方法。
该通信装置包括:接收单元,用于接收来自应用网元的指示信息,该指示信息用于指示多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;发送单元,用于向会话管理网元发送该每个类型的数据块对应的调度优先级。
结合第七方面,在第七方面的某些实现方式中,该每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,该PCC rule中还包括用于指示该QoS流的调度优先级的信息。
结合第七方面,在第七方面的某些实现方式中,该接收单元还用于接收来自会话管理网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该发送单元还用于向该应用网元发送该响应消息。
结合第七方面,在第七方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
以上第七方面及其可能的设计所示方法的有益效果可参照第二方面及其可能的设计中的有益效果。
第八方面,提供了一种通信装置,该通信装置用于执行上述第三方面提供的方法。
该通信装置包括:接收单元,用于接收来自策略控制网元的多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;发送单元,用于向用户面网元发送该每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中,其中,每个该数据块包括至少一个数据包。
结合第八方面,在第八方面的某些实现方式中,该每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,该PCC rule中还包括用于指示该QoS流的调度优先级的信息。
结合第八方面,在第八方面的某些实现方式中,该装置还包括:处理单元,用于根据该PCC rule配置该QoS流的参数;该发送单元还用于向策略控制网元发送响应消息,该响应消息用于指示该QoS流的参数配置完成。
结合第八方面,在第八方面的某些实现方式中,该装置还包括:处理单元,用于为该多个不同类型的数据块中的每个类型的数据块对应的调度优先级分配调度优先级标识,该调度优先级标识用于标识该每个类型的数据块对应的调度优先级;该发送单元还用于向用户面网元发送该每个类型的数据块对应的调度优先级标识和对应关系,其中,该对应关系包括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
结合第八方面,在第八方面的某些实现方式中,该发送单元还用于向接入网设备发送多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
结合第八方面,在第八方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
结合第八方面,在第八方面的某些实现方式中,该发送单元还用于向用户面网元发送封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
以上第八方面及其可能的设计所示方法的有益效果可参照第三方面及其可能的设计中的有益效果。
第九方面,提供了一种通信装置,该通信装置用于执行上述第四方面提供的方法。
该通信装置包括:接收单元,用于接收来自应用网元的下行数据,该下行数据包括多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,每个该数据块包括至少一个数据包;处理单元,用于根据各数据包对应的类型以及每个类型的数据块对应的一个调度优先级确定数据包的调度优先级;该用户面网元向接入网设备发送该数据包,该数据包中封装有指示该数据包的该调度优先级的信息。
结合第九方面,在第九方面的某些实现方式中,该接收单元还用于接收来自会话管理网元的每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中。
结合第九方面,在第九方面的某些实现方式中,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该接收单元还用于接收来自会话管理网元的调度优先级标识和对应关系,该调度优先级标识用于标识该每个类型的数据块对应的调度优先级, 该对应关系包括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
结合第九方面,在第九方面的某些实现方式中,该接收单元还用于接收来自该应用网元的该数据包所属的数据块的标识信息。
结合第九方面,在第九方面的某些实现方式中,该数据包中封装有该标识信息,该接收单元还用于接收来自该会话管理网元的封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
结合第九方面,在第九方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
以上第九方面及其可能的设计所示方法的有益效果可参照第四方面及其可能的设计中的有益效果。
第十方面,提供了一种通信装置,该通信装置用于执行上述第五方面提供的方法。
该通信装置包括:接收单元,用于接收来自用户面网元的多个数据包,该多个数据包中的各数据包中封装有指示该数据包对应的调度优先级的信息;该多个数据包归属于多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;处理单元,用于根据该调度优先级对该数据包进行处理。
结合第十方面,在第十方面的某些实现方式中,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该接收单元还用于接收来自会话管理网元的多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
结合第十方面,在第十方面的某些实现方式中,该数据包中还封装有该数据包所属的数据块的标识信息,该处理单元还用于根据该标识信息确定是否调度和该数据包属于同一个数据块中的除该数据包之外的其他数据包。
结合第十方面,在第十方面的某些实现方式中,该不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,该层级包括基础层或增强层。
以上第十方面及其可能的设计所示方法的有益效果可参照第五方面及其可能的设计中的有益效果。
第十一方面,提供了一种通信装置,该装置用于执行上述第一方面至第五方面提供的方法。具体地,该通信装置可以包括用于执行第一方面至第五方面提供的方法的单元和/或模块。
在一种实现方式中,收发单元可以是收发器,或,输入/输出接口;处理单元可以是至少一个处理器。可选地,收发器可以为收发电路。可选地,输入/输出接口可以为输入/输出电路。
在另一种实现方式中,收发单元可以是芯片、芯片***或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等;处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第十二方面,本申请提供一种处理器,用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作,如果没有特殊说明,或者,如果未与其在相关描述中的实际作用或者内在逻辑相抵触,则可以理解为处理器输出和接收、输入等操作,也可以理解为由射频电路和天线所进行的发送和接收操作,本申请对此不做限定。
第十三方面,提供一种计算机可读存储介质,该计算机可读存储介质存储用于设备执行的程序代码,该程序代码包括用于执行上述第一方面至第五方面的任意一种实现方式提供的方法。
第十四方面,提供一种包含指令的计算机程序产品,当该计算机程序产品在计算机上运行时,使得计算机执行上述第一方面至第五方面的任意一种实现方式提供的方法。
第十五方面,提供一种芯片,芯片包括处理器与通信接口,处理器通过通信接口读取存储器上存储的指令,执行上述第一方面至第五方面的任意一种实现方式提供的方法。
可选地,作为一种实现方式,芯片还包括存储器,存储器中存储有计算机程序或指令,处理器用于执行存储器上存储的计算机程序或指令,当计算机程序或指令被执行时,处理器用于执行上述第一方面至第五方面的任意一种实现方式提供的方法。
第十六方面,提供一种通信***,包括第六方面至第十方面所示的通知装置。
图1中的(a)和(b)是适用本申请实施例的应用场景示意图。
图2是本申请实施例提供的一种通信方法的示意性流程图。
图3是本申请实施例提供的装置300的示意性框图。
图4是本申请实施例提供的装置400的示意性框图。
本申请实施例的技术方案可以应用于各种通信***,例如:第五代(5th generation,5G)***或新无线(new radio,NR)、长期演进(long term evolution,LTE)***、LTE频分双工(frequency division duplex,FDD)***、LTE时分双工(time division duplex,TDD)等。本申请提供的技术方案还可以应用于未来的通信***,如第六代移动通信***。本申请实施例的技术方案还可以应用于设备到设备(device to device,D2D)通信,车辆外联(vehicle-to-everything,V2X)通信,机器到机器(machine to machine,M2M)通信,机器类型通信(machine type communication,MTC),以及物联网(internet of things,IoT)通信***或者其他通信***。
为便于理解本申请实施例,首先结合图1中的(a)和(b)简单介绍本申请实施例适用的通信***。
本申请实施例的技术方案可以应用于图1中的(a)和/或图1中的(b)所示的5G网络架构中,当然也可以用在未来网络架构,比如第六代(6th generation,6G)网络架构等,本申请实施例对此不作具体限定。
下面将结合图1中的(a)和图1中的(b)举例说明本申请实施例适用的5G***。应理解,本文中描述的5G***仅是示例,不应对本申请构成任何限定。
还应理解,5G***中某些网元之间可以采用服务化接口,或点对点的接口进行通信,下面结合图1中的(a)和图1中的(b)分别介绍基于点对点接口的5G***框架,以及 基于服务化接口的5G***框架。
作为示例性说明,图1中的(a)示出了本申请实施例适用的5G***200a的架构示意图。图1中的(a)为基于点对点接口的5G网络架构示意图。如图1中的(a)所示,该网络架构可以包括但不限于以下网元(或者称为功能网元、功能实体、节点、设备等):
用户设备(user equipment,UE)、(无线)接入网设备(radio access network,(R)AN)、接入和移动性管理功能(access and mobility management function,AMF)网元、会话管理功能(session management function,SMF)网元、用户面功能(user plane function,UPF)网元、策略控制功能(policy control function,PCF)网元、统一数据管理(unified data management,UDM)网元、应用功能(application function,AF)网元、数据网络(data network,DN)、网络切片选择功能(network slice selection function,NSSF)、认证服务器功能(authentication server function,AUSF)、统一数据管理(unified data management,UDM)、能力开放功能(network exposure function,NEF)网元、统一数据存储(unified data repository,UDR)等。
下面对图1中的(a)中示出的各网元进行简单介绍:
1、UE:为与(R)AN通信的终端也可以称为终端设备(terminal equipment)、接入终端、用户单元、用户站、移动站、移动台(mobile station,MS)、移动终端(mobile terminal,MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是一种向用户提供语音/数据连通性的设备,例如,具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例可以为:手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑(如笔记本电脑、掌上电脑等)、移动互联网设备(mobile internet device,MID)、虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备,5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network,PLMN)中的终端设备等。
此外,终端设备还可以是物联网(Internet of things,IoT)***中的终端设备。IoT是未来信息技术发展的重要组成部分,其主要技术特点是将物品通过通信技术与网络连接,从而实现人机互连,物物互连的智能化网络。IoT技术可以通过例如窄带(narrow band,NB)技术,做到海量连接,深度覆盖,终端省电。
应理解,终端设备可以是任何可以接入网络的设备。终端设备与接入网设备之间可以采用某种空口技术相互通信。
可选地,用户设备可以用于充当基站。例如,用户设备可以充当调度实体,其在V2X或D2D等中的用户设备之间提供侧行链路信号。比如,蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信,而无需通过基站中继通信信号。
2、(R)AN:用于为特定区域的授权用户设备提供入网功能,并能够根据用户设备 的级别,业务的需求等使用不同服务质量的传输隧道。
(R)AN能够管理无线资源,为用户设备提供接入服务,进而完成控制信号和用户设备数据在用户设备和核心网之间的转发,(R)AN也可以理解为传统网络中的基站。
示例性地,本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于:演进型节点B(evolved Node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(home evolved Node B,HeNB,或home Node B,HNB)、基带单元(baseBand unit,BBU),无线保真(wireless fidelity,WIFI)***中的接入点(access point,AP)、无线中继节点、无线回传节点、传输点(transmission point,TP)或者发送接收点(transmission and reception point,TRP)等,还可以为5G,如,NR,***中的gNB,或,传输点(TRP或TP),5G***中的基站的一个或一组(包括多个天线面板)天线面板,或者,还可以为构成gNB或传输点的网络节点,如基带单元(BBU),或,分布式单元(distributed unit,DU)等。
在一些部署中,gNB可以包括集中式单元(centralized unit,CU)和DU。gNB还可以包括有源天线单元(active antenna unit,AAU)。CU实现gNB的部分功能,DU实现gNB的部分功能。比如,CU负责处理非实时协议和服务,实现无线资源控制(radio resource control,RRC),分组数据汇聚层协议(packet data convergence protocol,PDCP)层的功能。DU负责处理物理层协议和实时服务,实现无线链路控制(radio link control,RLC)层、媒体接入控制(media access control,MAC)层和物理(physical,PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息,或者,由PHY层的信息转变而来,因而,在这种架构下,高层信令,如RRC层信令,也可以认为是由DU发送的,或者,由DU+AAU发送的。可以理解的是,接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外,可以将CU划分为接入网(radio access network,RAN)中的接入网设备,也可以将CU划分为核心网(core network,CN)中的接入网设备,本申请对此不做限定。
3、用户面网元:用于分组路由和转发以及用户面数据的服务质量(quality of service,QoS)处理等。
如图1中的(a)所示,在5G通信***中,该用户面网元可以是UPF网元,可以包括中间用户面功能(intermediate user plane function,I-UPF)网元、锚点用户面功能(PDU Session anchor user plane function,PSA-UPF)网元。在未来通信***中,用户面网元仍可以是UPF网元,或者,还可以有其它的名称,本申请不做限定。
4、数据网络:用于提供传输数据的网络。
在未来通信***中,数据网络仍可以是DN,或者,还可以有其它的名称,本申请不做限定。
在5G通信***中,终端设备接入网络后可以建立协议数据单元(protocol data unit,PDU)会话,并通过PDU会话访问DN,可以与部署在DN中的应用功能网元(应用功能网元比如为应用服务器)交互。如图1中的(a)所示,根据用户访问的DN不同,网络可以根据网络策略选择接入DN的UPF作为为PDU会话锚点(PDU Session Anchor,PSA), 并通过PSA的N6接口访问应用功能网元。
5、接入与移动性管理网元:主要用于移动性管理和接入管理等,可以用于实现移动性管理网元(mobility management entity,MME)功能中除会话管理之外的其它功能,例如,合法监听以及接入授权/鉴权等功能。
如图1中的(a)所示,在5G通信***中,该接入管理网元可以是AMF网元。在未来通信***中,接入管理网元仍可以是AMF网元,或者,还可以有其它的名称,本申请不做限定。
6、会话管理网元:主要用于会话管理、终端设备的网络互连协议(internet protocol,IP)地址分配和管理、选择可管理终端设备平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
如图1中的(a)所示,在5G通信***中,该会话管理网元可以是SMF网元,可以包括中间会话管理功能(intermediate session management function,I-SMF)网元、锚点会话管理功能(anchor session management function,A-SMF)网元。在未来通信***中,会话管理网元仍可以是SMF网元,或者,还可以有其它的名称,本申请不做限定。
7、策略控制网元:用于指导网络行为的统一策略框架,为控制面功能网元(例如AMF,SMF网元等)提供策略规则信息等。
在4G通信***中,该策略控制网元可以是策略和计费规则功能(policy and charging rules function,PCRF)网元。如图1中的(a)所示,在5G通信***中,该策略控制网元可以是PCF网元。在未来通信***中,策略控制网元仍可以是PCF网元,或者,还可以有其它的名称,本申请不做限定。
8、数据管理网元:用于处理终端设备标识,接入鉴权,注册以及移动性管理等。
如图1中的(a)所示,在5G通信***中,该数据管理网元可以是UDM网元或UDR网元。在未来通信***中,统一数据管理仍可以是UDM、UDR网元,或者,还可以有其它的名称,本申请不做限定。
本申请实施例中的UDM或UDR网元可以是指用户数据库。可以作为一个存储用户数据的单一逻辑存储库存在。
9、应用功能网元:应用功能网元可以通过应用功能网元与5G***交互,用于接入网络开放功能网元或与策略框架交互进行策略控制等。
如图1中的(a)所示,在5G通信***中,该应用功能网元可以是application function,AF网元。在未来通信***中,应用功能网元仍可以是AF网元,或者,还可以有其它的名称,本申请不做限定。
10、网络切片选择网元:主要包括以下功能:为UE选择一组网络切片实例、确定允许的网络切片选择辅助信息(network slice selection assistance information,NSSAI)和确定可以服务UE的AMF集等。
如图1中的(a)所示,在5G通信***中,该网络切片选择网元可以是NSSF网元。在未来通信***中,网络切片选择网元仍可以是NSSF网元,或者,还可以有其它的名称,本申请不做限定。
11、认证服务网元:用于鉴权服务、产生密钥实现对终端设备的双向鉴权,支持统一的鉴权框架。
如图1中的(a)所示,在5G通信***中,该认证服务网元可以是AUSF网元。在未来通信***中,认证服务功能网元仍可以是AUSF网元,或者,还可以有其它的名称,本申请不做限定。
12、网络开放功能网元:用于提供网络开放的定制功能。
如图1中的(a)所示,在5G通信***中,该网络开放功能网元可以是网络开放功能(network exposure function,NEF)网元在未来通信***中,该网络开放功能网元仍可以是NEF网元,或者,还可以有其它的名称,本申请不做限定。
5G通信***还可以通过NEF网元,向外部的应用功能网元开放5GC支持的能力,譬如提供小数据传递能力等。
可以理解的是,上述网元或者功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行的软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。上述网元或者功能可划分出一个或多个服务,进一步,还可能会出现独立于网络功能存在的服务。在本申请中,上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
进一步地,可以将AF网元简称为AF,NEF网元简称为NEF,AMF网元简称为AMF。即本申请后续所描述的AF均可替换为应用功能网元,NEF均可替换为网络开放功能网元,AMF均可替换为接入与移动性管理网元。
可以理解的是,上述网元或者功能网元既可以是硬件设备中的网络元件,也可以是在专用硬件上运行软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。上述网元或者功能可划分出一个或多个服务,进一步,还可能会出现独立于网络功能存在的服务。在本申请中,上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
从图1中的(a)可以看出,图1中的(a)中的各个控制面网元之间的接口是点对点的接口。
在图1中的(a)所示的架构中,各个网元之间的接口名称及功能如下:
1)、N1:AMF与终端之间的接口,可以用于向终端传递QoS控制规则等。
2)、N2:AMF与RAN之间的接口,可以用于传递核心网侧至RAN的无线承载控制信息等。
3)、N3:RAN与UPF之间的接口,主要用于传递RAN与UPF间的上下行用户面数据。
4)、N4:SMF与UPF之间的接口,可以用于控制面与用户面之间传递信息,包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5)、N5:AF与PCF之间的接口,可以用于应用业务请求下发以及网络事件上报。
6)、N6:UPF与DN的接口,用于传递UPF与DN之间的上下行用户数据流。
7)、N7:PCF与SMF之间的接口,可以用于下发协议数据单元(protocol data unit,PDU)会话粒度以及业务数据流粒度控制策略。
8)、N8:AMF与UDM间的接口,可以用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据,以及AMF向UDM注册终端当前移动性管理相关信息等。
9)、N9:UPF和UPF之间的用户面接口,用于传递UPF间的上下行用户数据流。
10)、N10:SMF与UDM间的接口,可以用于SMF向UDM获取会话管理相关签约数据,以及SMF向UDM注册终端当前会话相关信息等。
11)、N11:SMF与AMF之间的接口,可以用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给终端的控制消息、传递发送给RAN的无线资源控制信息等。
12)、N12:AMF和AUSF间的接口,可以用于AMF向AUSF发起鉴权流程,其中可携带SUCI作为签约标识;
13)、N13:UDM与AUSF间的接口,可以用于AUSF向UDM获取用户鉴权向量,以执行鉴权流程。
作为示例性说明,图1中的(b)示出了本申请实施例适用的5G***200b的架构示意图。图1中的(b)为基于服务化接口的5G网络架构示意图。如图1中的(b)所示,该网络架构可以包括但不限于以下网元(或者称为功能网元、功能实体、节点、设备等):
UE、(R)AN、AMF网元、SMF网元、UPF网元、PCF网元、UDM网元、AF网元、DN、NSSF、AUSF、UDM、NEF网元、UDR等。
其中的网元的功能的介绍可以参考图1中的(b)中对应的网元的功能的介绍,不再赘述。图1中的(b)与图1中的(a)的主要区别在于:图1中的(b)中的各个控制面网元之间的接口是服务化的接口,图1中的(a)中的各个控制面网元之间的接口是点对点的接口。
图1中的(b)中Nnssf、Nudr、Nausf、Nnef、Namf、Npcf、Nsmf、Nudm、Naf分别为上述NSSF、UDR、AUSF、NEF、AMF、PCF、SMF、UDM和AF提供的服务化接口,用于调用相应的服务化操作。N1、N2、N3、N4,以及N6为接口序列号。这些接口序列号的含义可参见第三代合作伙伴计划(3rd generation partnership project,3GPP)标准协议中定义的含义,在此不做限制。
应理解,上述本申请实施例能够应用的网络架构仅是示例性说明,本申请实施例适用的网络架构并不局限于此,任何包括能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解,图1中的(a)或图1中的(b)所示的AMF、SMF、UPF、PCF、NEF等可以理解为用于实现不同功能的网元,例如可以按需组合成网络切片。这些网元可以各自独立的设备,也可以集成于同一设备中实现不同的功能,或者可以是硬件设备中的网络元件,也可以是在专用硬件上运行的软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能,本申请对于上述网元的具体形态不作限定。
还应理解,上述命名仅为便于区分不同的功能而定义,不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如,在6G网络中,上述各个网元中的部分或全部可以沿用5G中的术语,也可能采用其他名称等。
还应理解,图1中的(a)或图1中的(b)的各个网元之间的接口名称只是一个示例,具体实现中接口的名称可能为其他的名称,本申请对此不作具体限定。此外,上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例,对消息本身的功能不构成任何限定。
应理解,本申请实施例提供的方法可以应用于5G通信***,例如,图1中的(a)或 图1中的(b)所示的通信***。但是,本申请实施例中并不限定该方法能够应用的场景,例如,其他包括能够实现相应功能的网元的网络架构中同样适用。还例如,第六代通信(the 6th generation,6G)***架构等。并且,本申请实施例上述所使用的各个网元的名称,在未来通信***中,可能保持功能相同,但名称会改变。
为了便于理解本申请实施例的技术方案,对本申请实施例可能涉及到的一些术语或概念进行简单描述。
1、PDU会话:为终端设备与数据网络(data network,DN)之间的一个关联,用于提供一个PDU连接服务。
2、QoS flow机制:目前标准中规定QoS flow是最小QoS控制粒度,每个QoS flow都有对应的QoS配置。
QoS配置包括的QoS参数描述了具体的QoS需求,QoS参数主要包括:
QoS flow索引(QoS flow index,QFI)、5G网络下的服务质量标识(5G quality of service identifier,5QI)、分配和预留优先级(allocation and retention priority,ARP)、保证流比特率(guaranteed flow bit rate,GFBR)、最大流比特率(maximum flow bit rate,MFBR)。
进一步地,QoS参数中的5QI是一组QoS特征组合索引,QoS特征包括:
资源类型(resource type)、优先级(priority level,PL)、包时延预算(packet delay budget,PDB)、包错误率(packet error rate,PER)、统计周期(averaging window)和最大突发数据量(maximum data burst volume)等。
其中,资源类型包括:非最低保障速率(non guaranteed bit rate,non-GRB)、最低保障速率(guaranteed bit rate,GRB)、时延敏感型GRB(delay-critical GBR);最大突发数据量是时延敏感型GRB特有参数。PDB用于表示从UE到UPF传输时延的上限,上下行数据的PDB相同。PER表示丢包率上界。PL用于表示不能满足多个QoS flow的PDB时,优先满足优先级高的QoS需求(如,PL值小的),例如,在拥塞的情况下,当一个或多个QoS flow不能满足所有QoS需求时,可以根据优先级级别对QoS flow进行优先级排序。
5QI是一个标量,用于索引到对应的5G QoS特征。5QI分为标准化的5QI、预配置的5QI和动态分配的5QI。对于标准化的5QI,与一组标准化的5G QoS特征值一一对应;对于预配置的5QI,对应的5G QoS特征值预配置在接入网网元上,对于动态分配的5QI,对应的5G QoS特征由核心网设备通过QoS文件(QoS profile)发送给接入网网元。
QFI用于标识一个PDU会话内不同QoS流的唯一标识。
ARP包含优先等级、抢占能力和被抢占能力。
GFBR代表期望提供给保证比特率(guaranteed bit rate,GBR)QoS flow(流)的比特率。
MFBR限制提供给GBR QoS flow的比特率,即提供给GBR QoS flow的最大比特率。如超过该比特率时,数据包可以被丢弃。
具体地,标准定义了一部分5QI的QoS特征值,可直接使用,也允许运营商和/或设备制造商分配不冲突的5QI并预设置对应QoS特征值的方式,在运营商网络中使用。
QoS flow配置生成后,5G控制面网元AMF与SMF将QoS flow配置下发给UE、RAN和UPF。
3、QoS模型:为了保证业务端到端的服务质量,提出了基于QoS流(flow)的QoS模型。该QoS模型支持保证比特率的QoS flow(即GBR QoS flow)和不保证比特率的QoS flow(即非GBR(non-GBR)QoS flow)。使用同一个QoS flow控制的数据包接收相同的传输处理(如调度、准入门限等)。对于一个终端设备,可以与网络建立一个或者多个数据连接会话(比如PDU会话);每个数据连接会话中可以传输对应一个或者多个QoS flow的数据流。每个QoS flow由一个QoS流标识(QoS flow identifier,QFI)识别,QFI在同一个数据连接会话中唯一标识一个QoS flow。此外,每个QoS流对应一个数据无线承载(data radio bearer,DRB),一个DRB可以对应一个或多个QoS flow。
其中,一个QoS flow为GBR QoS flow还是Non-GBR QoS flow,由对应的QoS文件(QoS profile)确定。
对于GBR QoS flow,对应的QoS文件包含以下QoS参数:5QI、ARP、GFBR、MFBR,和/或QNC。根据QoS文件是否包含QNC将GBR QoS flow确定为需要通知控制(notification control)的GRB QoS flow和不需要通知控制的GBR QoS flow。对于需要通知控制的GBR QoS flow,当接入网网元检测到对应的QoS flow资源不能被满足时,接入网网元通知会话管理功能SMF该事件(即GBR QoS flow对应的QoS flow资源不能被满足)。进一步的SMF可以发起QoS flow删除或者QoS flow修改流程(如,修改QoS flow的QoS参数)。
对于Non-GBR QoS flow,对应的QoS文件包含以下QoS参数:5QI、ARP和/或RQA。
4、PL:指示QoS Flow中调度资源的优先级,可用于标识同一UE的数据流对应的QoS Flow,也可用于标识不同UE数据流对应的QoS Flow。在拥塞的情况下,目前的资源无法支持一个或多个QoS Flow都达到对应的QoS需求(如,PDB、PER等)不能满足时,PL用于选择优先满足哪些QoS Flow对应的QoS需求。
5、通用分组无线业务隧道协议-用户面(general packet radio service tunnelling protocol user,GTP-U)隧道:在PDU会话建立过程中,RAN与UPF之间的连接会用到GTP-U隧道,将来自UE侧的数据或发往UE侧的数据添加到隧道中进行发送。
6、隧道端点标识(Tunnel Endpoint Identifier,TEID):为GTP-U协议的隧道端点,可唯一确定两个网元之间的一段隧道。
7、用户体验(Quality of Experience,QoE):在扩展现实(Extended Reality,XR)业务中,QoE往往是最直观有效的衡量指标。示例性地,QoE可以体现为在同一个QoS flow中传输的数据流对用户体验的重要程度很可能是并不相同的,例如,I帧比P帧重要、位于视野中央的比位于视野边缘的重要、基础层数据比增强层数据重要等等。
由上述关于目前QoS flow的QoS参数描述可知:每个QoS flow仅由一组QoS参数来表述,一个QoS flow只有一个5QI等参数,即只有一个调度优先级,当网络发生阻塞等情况而无法保证所有数据流传输的QoS需求时,不会根据数据流对QoE重要程度的不同而对不同数据流进行差异化调度,例如,如何实现优先调度对QoE重要程度高的数据流,满足这些数据流传输的QoS需求之后,再调度对QoE重要程度低的数据流,实现同一个QoS flow对应的不同类型的数据块的数据包的差异化调度。
为了解决目前的数据流调度存在的缺点,本申请提供一种通信方法,通过针对一个QoS flow映射的不同类型的数据包配置多种调度优先级,以期实现单QoS flow对应的不 同类型的数据块的数据包的差异化调度。
上文结合图1中的(a)和图1中的(b)介绍了本申请实施例能够应用的场景,并且简单介绍了目前的数据流调度的方法存在的缺陷,还简单介绍了本申请中涉及的基本概念,下文中将结合附图详细介绍本申请提供的通信方法。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定,只要能够通过运行记录有本申请实施例的提供的方法的代码的程序,以根据本申请实施例提供的方法进行通信即可,例如,本申请实施例提供的方法的执行主体可以是核心网设备,或者是核心网设备中能够调用程序并执行程序的功能模块。
为了便于理解本申请实施例,做出以下几点说明。
第一,在本申请中,“用于指示”可以理解为“使能”,“使能”可以包括直接使能和间接使能。当描述某一信息用于使能A时,可以包括该信息直接使能A或间接使能A,而并不代表该信息中一定携带有A。
将信息所使能的信息称为待使能信息,则具体实现过程中,对待使能信息进行使能的方式有很多种,例如但不限于,可以直接使能待使能信息,如待使能信息本身或者该待使能信息的索引等。也可以通过使能其他信息来间接使能待使能信息,其中该其他信息与待使能信息之间存在关联关系。还可以仅仅使能待使能信息的一部分,而待使能信息的其他部分则是已知的或者提前约定的。例如,还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的使能,从而在一定程度上降低使能开销。同时,还可以识别各个信息的通用部分并统一使能,以降低单独使能同样的信息而带来的使能开销。
第二,在本申请中示出的第一、第二以及各种数字编号(例如,“#1”、“#2”等)仅为描述方便,用于区分的对象,并不用来限制本申请实施例的范围。例如,区分不同消息等。而不是用于描述特定的顺序或先后次序。应该理解这样描述的对象在适当情况下可以互换,以便能够描述本申请的实施例以外的方案。
第三,在本申请中,“预配置”可包括预先定义,例如,协议定义。其中,“预先定义”可以通过在设备(例如,包括各个网元)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现,本申请对于其具体的实现方式不做限定。
第四,本申请实施例中涉及的“保存”,可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器,可以是单独的设置,也可以是集成在编码器或者译码器,处理器、或通信装置中。所述一个或者多个存储器,也可以是一部分单独设置,一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质,本申请并不对此限定。
第五,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
第六,本申请实施例中涉及的“协议”可以是指通信领域的标准协议,例如可以包括5G协议、新空口(new radio,NR)协议以及应用于未来的通信***中的相关协议,本申请对此不做限定。
以下,不失一般性,以网元之间的交互为例详细说明本申请实施例提供的通信的方法。
为了便于描述,下文中以接入网设备为RAN、移动性管理功能网元为AMF、应用功 能网元为AF、会话管理功能网元为SMF、用户面功能网元为UPF、终端为UE为例进行说明。
需要说明的是,本申请中对于设备的名称不做任何的限定。
图2是本申请实施例提供的一种通信方法的示意性流程图,包括以下步骤:
S210,AF确定多个不同类型的数据块中每个类型的数据块对应的调度优先级。
具体地,多个不同类型的数据块可以是两个或两个以上不同类型的数据块。本申请实施例中涉及数据块的类型可以是帧的类型如,I帧、P帧、B帧等。数据块的类型还可以是指示用户视野位置,比如中心位置、边缘位置。数据块的类型还可以指示数据块对应的层级,比如基础层、增强层等.
其中,层级不同的数据块可以理解为:数据块作用不同,例如有些是为了保证基本视频可以流畅的被播放,但清晰度可能不高,这些就是基础层;有一些则负责增强,使图像的清晰度更好,有更多细节,用户体验感更好,这些就属于增强层。
应理解,上述的数据块的类型只是举例。对本申请的保护范围不构成任何的限定,还可以通过其他方式对数据块进行分类,例如,原始流、纠错流等。这里不一一举例说明。本申请实施例中对于不同类型的数据块具体是由于什么原因导致的类型不同不做限制。例如,可以是AF任意指示两个数据块为不同类型的数据块,该两个数据块的调度优先级不同。
示例性地,多个不同类型的数据块分别对应的不同的调度优先级。例如,I帧和P帧为不同类型的数据块,I帧对应的调度优先级比P帧对应的调度优先级高;还例如,位于用户视野中央的数据块对应的调度优先级,比位于用户视野边缘的数据块对应的调度优先级高;又例如,基础层数据块对应的调度优先级,比增强层数据块对应的调度优先级高。
作为一种可能的实现方式,AF可以根据配置信息确定不同类型的数据块对应不同的调度优先级。
作为另一种可能的实现方式,AF可以根据网络管理设备的指示确定不同类型的数据块对应不同的调度优先级。
作为又一种可能的实现方式,AF可以根据历史数据传输结果确定不同类型的数据块对应不同的调度优先级。
需要说明的是,上述AF确定多个不同类型的数据块中每个类型的数据块对应的调度优先级的方式只是举例,对本申请的保护范围不构成任何的限定。本申请实施例中对于AF如何确定多个不同类型的数据块中每个类型的数据块对应的调度优先级不做限定。
具体地,本申请实施例中涉及的数据块包括至少一个数据包,例如,数据块可以是帧、切片(slice)或块(tile)等。另外,需要说明的是,上述的多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中。
上述的多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,可以理解为:
多个不同类型的数据块对应同一个服务质量QoS流;或者,可以理解为多个不同类型的数据块承载在同一个QoS流中;或者还可以理解为多个不同类型的数据块对应的多个不同调度优先级用于实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
进一步地,AF确定多个不同类型的数据块中每个类型的数据块对应的调度优先级之后,可以通过指示信息经由控制面实现每个类型的数据块对应的调度优先级的配置,图2所示的方法流程还包括:
S220,AF向PCF发送指示信息。
该指示信息用于指示每个类型的数据块对应的调度优先级。
作为一种可能的实现方式,AF向PCF发送指示信息可以是AF直接向PCF发送指示信息,如,AF通过AF和PCF之间的通信接口(如,N5)或通过服务化接口(如,Naf和Npcf)向PCF发送指示信息。
作为另一种可能的实现方式,AF向PCF发送指示信息可以是AF间接向PCF发送指示信息,如,AF通过其他功能网元(如,NEF等)向PCF发送指示信息。
具体地,该指示信息用于指示每个类型的数据块对应的调度优先级可以理解为AF向PCF发送指示信息,且该指示信息指示多个不同类型的数据块分别对应的多个调度优先级。
作为一种可能的实现方式,该指示信息包括在目前发送QoS需求的消息中,该每个类型的数据块对应的调度优先级也可以理解为一种QoS需求。
作为另一种可能的实现方式,该指示信息可以包括在其他消息(如,AF和PCF之间已有的或新增的消息)中。
需要说明的是,上述只是举例说明AF将指示信息发送给PCF的可能方式,对本申请的保护范围不构成任何的限定。本申请实施例中对于AF如何将指示信息发送给PCF不做限制。
进一步地,PCF接收到上述的指示信息之后,可以将每个类型的数据块对应的调度优先级发送给SMF,图2所示的方法流程还包括:
S230,PCF向SMF发送每个类型的数据块对应的调度优先级。
示例性地,PCF向SMF发送所述每个类型的数据块对应的调度优先级,可以通过发送多个不同类型的数据块分别对应的多个调度优先级以及映射关系实现,其中,映射关系包括多个不同类型的数据块和多个调度优先级之间的映射关系。
例如,在AF通过上述的指示信息指示每个类型的数据块对应的调度优先级的情况下,映射关系用于指示I帧与调度优先级#1对应,P帧与调度优先级#2对应,其中,调度优先级#1高于调度优先级#2。
还例如,在AF通过上述的指示信息指示处于用户视野不同位置的数据块对应不同的调度优先级的情况下,映射关系用于指示位于用户视野中央的数据块与调度优先级#3对应,位于用户视野边缘的数据块与调度优先级#4对应,其中,调度优先级#3高于调度优先级#4。
应理解,PCF将上述的映射关系发送给SMF,以便于SMF向UPF配置数据块对应的调度优先级。
作为一种可能的实现方式,上述的每个类型的数据块对应的调度优先级可以通过策略和计费控制规则(policy and charging control rule,PCC rule)发送给SMF,即每个类型的数据块对应的调度优先级包括在PCC rule中。
可选地,该PCC rule中还包括用于指示所述QoS流的调度优先级的信息。
为了便于区分,同一个QoS流对应的不同类型的数据块的数据包的差异化调度的调 度优先级(即上述的每个类型的数据块对应的调度优先级)可以称为第一调度优先级;本QoS流的调度优先级可以称为第二调度优先级。
作为一种可能的实现方式,PCC rule中可以包括上述的第二调度优先级。具体地,多个第一调度优先级是在QoS flow内部的,一个第二调度优先级是负责对外的调度优先级比较,通过第二调度优先级先和其他的QoS flow作比较,确定了QoS flow之间的调度优先级后,再通过多个第一调度优先级确定QoS flow内部不同类型的数据包的调度优先级。
作为另一种可能的实现方式,PCC rule中可以不包括上述的第二调度优先级。PCC rule中包括多个第一调度优先级,由于调度优先级判定原则是一样的,所以这多个第一调度优先级同时需要考虑QoS flow间的调度优先级,相当于是如果第一调度优先级为QFI#1包1(调度优先级为1)、QFI#1包2(调度优先级为3),但另一个QoS flow的调度优先级为QFI#2包1(调度优先级为2),那么调度顺序为QFI#1包1、QFI#2包1、QFI#1包2。这种情况下PCC rule中可以不包括第二调度优先级。
进一步地,SMF接收到PCC rule之后,进行UPF配置,图2所示的方法流程还包括:
S240,SMF配置UPF。
该实施例中SMF配置UPF包括:SMF向UPF发送封装指示信息,所述封装指示信息用于指示所述用户面网元将接收到的数据包对应的调度优先级封装在所述数据包中。
可选地,数据包对应的调度优先级封装在所述数据包中,包括:数据包对应的调度优先级封装在所述数据包的包头中,例如,封装到GTP-U包头中。或者,数据包对应的调度优先级还可以封装在数据包的载荷中,本申请对此不做限定。
应理解,为了实现UPF将接收到的数据包对应的调度优先级封装在所述数据包中,SMF在配置UPF的过程中还需要向UPF发送每个类型的数据块对应的调度优先级,以便于UPF在接收到数据包后确定该数据包的调度优先级。
作为一种可能的实现方式,SMF向UPF发送每个类型的数据块对应的调度优先级,可以通过发送多个不同类型的数据块分别对应的多个调度优先级以及映射关系实现,其中,映射关系包括多个不同类型的数据块和多个调度优先级之间的映射关系。
作为另一种可能的实现方式,SMF向UPF发送每个类型的数据块对应的调度优先级,可以通过发送每个类型的数据块对应的调度优先级标识和对应关系实现,其中,对应关系包括所述多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。在该实现方式下,SMF需要为所述多个不同类型的数据块中的每个类型的数据块对应的调度优先级分配调度优先级标识,图2所示的方法流程还包括:
S231,SMF分配调度优先级标识。
调度优先级标识用于标识所述每个类型的数据块对应的调度优先级。
具体地,在SMF分配调度优先级标识的情况下,SMF可以通知RAN多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系,在该实现方式下,图2所示的方法流程还可以包括:
S232,SMF向RAN发送对应关系。
该对应关系用于指示多个不同类型的数据块的调度优先级和多个所述调度优先级标识的相对应。
可选地,该实施例中SMF配置UPF还可以包括:SMF还向UPF发送封装信息,所 述封装信息用于指示所述用户面网元将标识信息封装在所述数据包中,所述标识信息用于标识所述数据包所属的数据块。
可选地,封装指示信息和封装信息可以是一个指示信息,也可以是多个指示信息。
可选地,标识信息封装在所述数据包中,包括:标识信息封装在所述数据包的包头中;或者,标识信息还可以封装在数据包的载荷中,本申请对此不做限定。
完成上述的UPF配置之后,SMF根据接收到的PCC rule配置QoS flow的参数,图2所示的方法流程还包括:
S250,SMF配置QoS flow的参数。
SMF基于上述的多个不同的调度优先级配置QoS flow的参数。可以理解为该一个QoS flow对应多个调度优先级。其中,配置QoS flow的参数可以理解为配置QoS flow的策略。
示例性地,SMF配置QoS flow的参数(也可称为策略),也可以称为SMF向UPF、RAN和/或UE发送QoS flow的参数.包括如下步骤:
第一步:SMF根据PCF发送的PCC rule确定QoS flow的信息(也可称为QoS策略)。
第二步:SMF分别向UPF、RAN和UE下发对应的QoS策略。例如,SMF向UPF发送第一QoS策略、SMF向RAN发送第二QoS策略、SMF向UE发送第三QoS策略。
SMF向UPF发送第一QoS策略,包括:SMF向UPF发送包检测规则(Packet Detection Rule,PDRs)。
SMF向RAN发送第二QoS策略,包括:SMF通过AMF向RAN发送QoS文件(profile)。
SMF向UE发送第三QoS策略,包括:SMF通过AMF和RAN向UE发送QoS规则(QoS rule),QoS规则中包含QoS控制信息。
进一步的,UE,UE、RAN和UPF在接收到QoS flow的参数后,RAN根据QoS文件建立空口的DRB,并存储QoS flow与DRB的绑定关系可选的,UE根据QoS规则执行上行数据包的传输.以及UPF根据PDRs对下行数据包进行QFI标识,并对上行数据包的进行QFI验证。
应理解,上述只是简单说明SMF配置QoS flow的参数的流程对本申请的保护范围不构成任何的限定,配置QoS flow的参数的流程可以参考目前配置QoS flow的参数的描述,本申请中不赘述。
进一步地,QoS流的参数配置完成之后,可以通过响应消息通知AF以便于AF进行下行数据传输,图2所示的方法流程还包括:
S251,SMF向PCF发送响应消息。
响应消息用于指示所述QoS流的参数配置完成。
S252,PCF向AF发送响应消息。
具体地,AF接收到响应消息之后获知QoS流的参数配置完成,可以进行下行数据传输;或者理解为响应于的响应消息,AF进行下行数据传输,图2所示的方法流程还包括:
S260,AF向UPF发送下行数据。
所述下行数据中包括数据包和用于指示所述数据包所属的数据块的类型的指示信息。
示例性地,指示所述数据包所属的数据块的类型的指示信息可以称为类型指示信息,该类型指示信息可以用于指示数据块的类型,例如,指示数据块为I帧还是P帧;还例如,指示数据块为位于用户视野中央的数据块还是位于用户视野边缘的数据块;又例如,指示 数据块为基础层数据块还是增强层数据块。
作为一种可能的实现方式,数据包和用于指示该数据包所属数据块的类型的指示信息可以分开传输,例如,数据包和类型指示信息为两个独立的信元,包括在同一条消息中。
作为另一种可能的实现方式,数据包和用于指示该数据包所属数据块的类型的指示信息可以同时传输,例如,类型指示信息封装在该数据包的包头中,用于指示该数据包所属的数据块的类型。
需要说明的是,本申请中对于信息名称并不限定,例如,上述的类型指示信息可以称为第一指示信息,指示信息等。
可选地,下行数据中还可以包括所述数据包所属的数据块的标识信息。其中,数据块的标识信息包括但不限于数据块的标识(identify,ID)、数据块的属性信息等能够用于标识数据块的信息。
示例性地,数据块的标识信息和上述的数据包、类型指示信息可以包括在同一条消息中。例如,应用网元向用户面网元发送消息,该消息中包括数据包、用于指示该数据包所属的数据块的类型指示信息和该数据包所属的数据块的标识信息。
在UPF接收到下行数据之后,可以根据上述的SMF的配置(参考上述步骤S240中的描述)、接收到的数据包和类型指示信息确定数据包的调度优先级,图2所示的方法流程还包括:
S270,UPF确定数据包的调度优先级。
具体地,UPF根据类型指示信息确定数据包所属的数据块对应的类型,以及根据上述的SMF的配置的每个类型的数据块对应的一个调度优先级确定接收到的数据包的调度优先级。
进一步地,UPF将指示数据包的调度优先级的信息封装在数据包中,图2所示的方法流程还包括:
S280,UPF封装数据包。
作为一种可能的实现方式,UPF封装数据包包括:UPF将数据包的调度优先级封装在数据包中。
例如,UPF将数据包的调度优先级封装到GTP-U包头中。
作为另一种可能的实现方式,UPF封装数据包包括:UPF将用于标识所述调度优先级的调度优先级标识封装在数据包中。
例如,UPF将数据包的调度优先级的调度优先级标识封装到GTP-U包头中。
可选地,在上述的下行数据中包括数据包所属的数据块的标识信息情况下,UPF封装数据包包括:UPF将数据包所属的数据块的标识信息封装在数据包中。
例如,UPF将数据包所属的数据块的标识信息封装到GTP-U包头中。
在UPF完成数据包封装之后,UPF可以将封装后的数据包发送给RAN,图2所示的方法流程还包括:
S290,UPF向RAN发送数据包。
示例性地,UPF向RAN发送GTP-U数据包。
进一步地,RAN可以对接收到的数据包进行处理,图2所示的方法流程还包括:
S291,RAN处理数据包。
具体地,RAN处理数据包包括以下步骤一至步骤四:
步骤一:RAN解封装该数据包确定该数据包的调度优先级。
比如,RAN根据数据包(如,GTP-U包头)中封装的指示所述数据包对应的调度优先级的信息,确定该数据包的调度优先级。
作为一种可能的实现方式,在数据包中封装的为该数据包对应的调度优先级,RAN解封装该数据包之后,即可获得该数据包对应的调度优先级。
作为另一种可能的实现方式,数据包中封装的为该数据包对应的调度优先级的调度优先级标识,RAN解封装该数据包之后,获得该数据包对应的调度优先级的调度优先级标识,进一步地根据从SMF接收到的对应关系(参见上步骤S232的描述)确定该数据包对应的调度优先级。
可选地,在数据包(如,GTP-U包头)中封装有数据包所属的数据块的标识信息的情况下,RAN还执行下述的步骤二。
步骤二:RAN解封装该数据包确定该数据包所属的数据块的标识信息。
RAN确定数据包的调度优先级,或者确定数据包的调度优先级和数据包所属的数据块的标识信息之后,可以根据该数据包的调度优先级以及映射该数据包的QoS流的其他参数(如,目前协议中规定的5QI)进行QoS处理;或者,在确定该数据包所属的数据块的标识信息的情况下,可以根据该数据包所属的数据块的标识信息确定具有相同标识信息的数据包的处理方式,包括确定具有相同标识信息的数据包的调度。
步骤三:RAN对数据包进行调度。
可以理解,相比于目前协议中规定的QoS flow机制,该实施例中对数据包进行QoS处理是除了需要考虑映射该数据包的QoS流的其他参数(如,目前协议中规定的QoS参数),还需要考虑该数据包的调度优先级。其中,该数据包的调度优先级也可以理解为QoS参数的一种,为新增的一种QoS参数。
示例性地,当RAN接收到多个映射到同一个QoS流的数据包(如,数据包#1、数据包#2和数据包#3)。该多个数据包对应的调度优先级不同,如,数据包#1对应调度优先级#1、数据包#2对应调度优先级#2、数据包#3对应调度优先级#3,其中,调度优先级#1高于调度优先级#2、调度优先级#2高于调度优先级#3。RAN对数据包进行处理包括:根据各数据包对应的调度优先级发送各数据包。比如,优先调度(或者说发送)数据包#1,然后在调度数据包#2,最后调度数据包#3,实现同一个QoS流对应的不同类型的数据块的数据包的差异化调度。
可选地,在数据包(如,GTP-U包头)中封装有数据包所属的数据块的标识信息的情况下,RAN处理数据包还包括:
RAN根据数据块的标识信息扩大传输粒度,从包粒度的传输扩展为数据块(帧、tile或slice)粒度的传输。例如,某个数据块中一些数据包在传输过程中由于丢弃等原因无法被成功接收,那RAN可以先不为具有相同数据块的标识信息的其他数据包调度资源,这种考虑了数据包之间关联关系的调度,一定程度上可以避免虽然数据包传送成功了,但无法被解码的问题,从而提升传输效率。
还例如,RAN已成功接收某个数据块中一些数据包,那RAN可以提前为与成功被接收的数据包归属的相同数据块的标识信息的其他数据包调度资源,一定程度上可以降低数 据包传输的时延。
其中,RAN对数据包进行资源调度可以理解为为该数据包分配使用资源,而优先调度可以理解为优先按照该数据包的QoS需求对该数据包分配RAN相关资源,从而使数据包可以成功发送。进一步地,RAN可以将接收到的数据包发送给UE,执行步骤四。
步骤四:RAN接收到下行数据包时根据数据包头中的QFI以及对应的QoS flow和DRB的绑定关系,将该下行数据包放在对应的DRB上传输。
需要说明的是,上述只是以下行数据为例说明同一个QoS flow对应的不同类型的数据块的数据包的差异化调度,对于上行数据传输在完成同一个QoS flow内的不同调度优先级配置之后(如上述的步骤S252之后),终端设备确定发送上行数据包时,根据QoS规则确定QoS flow,为了实现同一个QoS flow对应的不同类型的数据块的数据包的差异化调度,终端设备在发送上行数据包前,在通过物理上行控制信道(Physical Uplink Control Channel,PUCCH)告知接入网设备有上行数据需要发送时,需同时告知该上行数据包所属的数据块的类型,上行调度器根据数据块类型为该终端设备分配发送数据包所需资源,不同的数据块类型可能分配的资源(大小、位置等)不同,从而实现上行数据的同一个QoS flow对应的不同类型的数据块的数据包的差异化调度。
应理解,本申请实施例中的图2所示的具体的例子只是为了帮助本领域技术人员更好地理解本申请实施例,而非限制本申请实施例的范围。还应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
还应理解,在本申请的各个实施例中,如果没有特殊说明以及逻辑冲突,不同的实施例之间的术语和/或描述具有一致性、且可以相互引用,不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
还应理解,在上述一些实施例中,主要以现有的网络架构中的网元为例进行了示例性说明(如AF、AMF、SMF等等),应理解,对于网元的具体形式本申请实施例不作限定。例如,在未来可以实现同样功能的网元都适用于本申请实施例。
可以理解的是,上述各个方法实施例中,由网络设备(如各个网元、接入网设备等)实现的方法和操作,也可以由可用于网络设备的部件(例如芯片或者电路)实现。
以上,结合图2详细说明了本申请实施例提供的通信方法。上述通信方法主要从各个网元之间交互的角度进行了介绍。可以理解的是,各个网元,为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。
本领域技术人员应该可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
以下,结合图3和图4详细说明本申请实施例提供的通信的装置。应理解,装置实施例的描述与方法实施例的描述相互对应,因此,未详细描述的内容可以参见上文方法实施例,为了简洁,部分内容不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的 划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图3是本申请实施例提供的装置300的示意性框图。该装置300包括收发单元310和处理单元320。收发单元310可以实现相应的通信功能,处理单元320用于进行数据处理。收发单元310还可以称为通信接口或通信单元。
可选地,该装置300还可以包括存储单元,该存储单元可以用于存储指令和/或数据,处理单元320可以读取存储单元中的指令和/或数据,以使得装置实现前述方法实施例。
该装置300可以用于执行上文方法实施例中网络设备(如各个网元、接入网设备等)所执行的动作,这时,该装置300可以为网络设备或者可配置于网络设备的部件,收发单元310用于执行上文方法实施例中网络设备侧的收发相关的操作,处理单元320用于执行上文方法实施例中网络设备侧的处理相关的操作。
作为一种设计,该装置300用于执行上文方法实施例中AF所执行的动作。
处理单元320,用于确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;收发单元310,用于向策略控制网元发送指示信息,该指示信息用于指示该每个类型的数据块对应的调度优先级,其中,每个该数据块包括至少一个数据包。
可选地,该指示信息包括在服务质量QoS需求中,该QoS需求用于配置该QoS流的参数,该收发单元310还用于接收来自策略控制网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该收发单元310还用于向用户面网元发送下行数据,该下行数据中包括数据包和用于指示该数据包所属的数据块的类型的指示信息。
该装置300可实现对应于根据本申请实施例的方法实施例中的AF执行的步骤或者流程,该装置600可以包括用于执行方法实施例中的AF执行的方法的单元。并且,该装置600中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的AF中的方法实施例的相应流程。
其中,当该装置300用于执行图2中的方法时,收发单元310可用于执行方法中的收发步骤,如步骤S220、S252和S260;处理单元320可用于执行方法中的处理步骤,如步骤S210。
应理解,各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明,为了简洁,在此不再赘述。
作为另一种设计,该装置300用于执行上文方法实施例中PCF所执行的动作。
收发单元310,用于接收来自应用网元的指示信息,该指示信息用于指示多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;收发单元310,用于向会话管理网元发送该每个类型的数据块对应的调度优先级。
可选地,该收发单元310还用于接收来自会话管理网元的响应消息,该响应消息用于指示该QoS流的参数配置完成;该收发单元310还用于向该应用网元发送该响应消息。
该装置300可实现对应于根据本申请实施例的方法实施例中的PCF执行的步骤或者流程,该装置300可以包括用于执行方法实施例中的PCF执行的方法的单元。并且,该装置300中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的PCF中的方法实施例的相应流程。
其中,当该装置300用于执行图2中的方法时,收发单元310可用于执行方法中的收发步骤,如步骤S220、S230和S251;处理单元320可用于执行方法中的处理步骤。
应理解,各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明,为了简洁,在此不再赘述。
作为又一种设计,该装置300用于执行上文方法实施例中SMF所执行的动作。
收发单元310,用于接收来自策略控制网元的多个不同类型的数据块中每个类型的数据块对应的调度优先级,该多个不同该类型的数据块中的数据包均映射到同一个服务质量QoS流中;收发单元310,用于向用户面网元发送该每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中,其中,每个该数据块包括至少一个数据包。
可选地,处理单元320,用于根据该PCC rule配置该QoS流的参数;该发送单元还用于向策略控制网元发送响应消息,该响应消息用于指示该QoS流的参数配置完成。
可选地,处理单元320,用于为该多个不同类型的数据块中的每个类型的数据块对应的调度优先级分配调度优先级标识,该调度优先级标识用于标识该每个类型的数据块对应的调度优先级;该发送单元还用于向用户面网元发送该每个类型的数据块对应的调度优先级标识和对应关系,其中,该对应关系包括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
可选地,该收发单元310还用于向接入网设备发送多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
可选地,该收发单元310还用于向用户面网元发送封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
该装置300可实现对应于根据本申请实施例的方法实施例中的SMF执行的步骤或者流程,该装置300可以包括用于执行方法实施例中的SMF执行的方法的单元。并且,该装置300中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的SMF中的方法实施例的相应流程。
其中,当该装置300用于执行图2中的方法时,收发单元310可用于执行方法中的收发步骤,如步骤S230、S232和S251;处理单元320可用于执行方法中的处理步骤,如步骤S231、S240和S250。
应理解,各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明,为了简洁,在此不再赘述。
作为又一种设计,该装置300用于执行上文方法实施例中UPF所执行的动作。
收发单元310,用于接收来自应用网元的下行数据,该下行数据包括多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,每个该数据块包括至少一个数据包;处理单元320,用于根据各数据包对应的类型以及每个类型的数据块对应的一 个调度优先级确定数据包的调度优先级;该用户面网元向接入网设备发送该数据包,该数据包中封装有指示该数据包的该调度优先级的信息。
可选地,该收发单元310还用于接收来自会话管理网元的每个类型的数据块对应的调度优先级和封装指示信息,该封装指示信息用于指示该用户面网元将接收到的数据包对应的调度优先级封装在该数据包中。
可选地,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该收发单元310还用于接收来自会话管理网元的调度优先级标识和对应关系,该调度优先级标识用于标识该每个类型的数据块对应的调度优先级,该对应关系包括该多个不同类型的数据块的调度优先级和多个该调度优先级标识的对应关系。
可选地,该收发单元310还用于接收来自该应用网元的该数据包所属的数据块的标识信息。
可选地,该数据包中封装有该标识信息,该收发单元310还用于接收来自该会话管理网元的封装信息,该封装信息用于指示该用户面网元将标识信息封装在该数据包中,该标识信息用于标识该数据包所属的数据块。
该装置300可实现对应于根据本申请实施例的方法实施例中的UPF执行的步骤或者流程,该装置300可以包括用于执行方法实施例中的UPF执行的方法的单元。并且,该装置300中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的UPF中的方法实施例的相应流程。
其中,当该装置300用于执行图2中的方法时,收发单元310可用于执行方法中的收发步骤,如步骤S260和S290;处理单元320可用于执行方法中的处理步骤,如步骤S240、S270和S280。
应理解,各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明,为了简洁,在此不再赘述。
作为又一种设计,该装置300用于执行上文方法实施例中RAN所执行的动作。
收发单元310,用于接收来自用户面网元的多个数据包,该多个数据包中的各数据包中封装有指示该数据包对应的调度优先级的信息;该多个数据包归属于多个不同类型的数据块,该多个不同类型的数据块中每个类型的数据块对应一个调度优先级,该多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;处理单元320,用于根据该调度优先级对该数据包进行处理。
可选地,该指示该调度优先级的信息包括用于标识该调度优先级的调度优先级标识,该收发单元310还用于接收来自会话管理网元的多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
可选地,该数据包中还封装有该数据包所属的数据块的标识信息,该处理单元320还用于根据该标识信息确定是否调度和该数据包属于同一个数据块中的除该数据包之外的其他数据包。
该装置300可实现对应于根据本申请实施例的方法实施例中的RAN执行的步骤或者流程,该装置300可以包括用于执行方法实施例中的RAN执行的方法的单元。并且,该装置300中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的RAN中的方法实施例的相应流程。
其中,当该装置300用于执行图2中的方法时,收发单元310可用于执行方法中的收发步骤,如步骤S232和S290;处理单元320可用于执行方法中的处理步骤,如步骤S291。
应理解,各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明,为了简洁,在此不再赘述。
上文实施例中的处理单元320可以由至少一个处理器或处理器相关电路实现。收发单元310可以由收发器或收发器相关电路实现。存储单元可以通过至少一个存储器实现。
如图4所示,本申请实施例还提供一种装置400。该装置400包括处理器410,还可以包括一个或多个存储器420。处理器410与存储器420耦合,存储器420用于存储计算机程序或指令和/或数据,处理器410用于执行存储器420存储的计算机程序或指令和/或数据,使得上文方法实施例中的方法被执行。可选地,该装置400包括的处理器410为一个或多个。
可选地,该存储器420可以与该处理器410集成在一起,或者分离设置。
可选地,如图4所示,该装置400还可以包括收发器430,收发器430用于信号的接收和/或发送。例如,处理器410用于控制收发器430进行信号的接收和/或发送。
作为一种方案,该装置400用于实现上文方法实施例中由设备(如各个网元、接入网设备等)执行的操作。
本申请实施例还提供一种计算机可读存储介质,其上存储有用于实现上述方法实施例中由网络设备(如各个网元、接入网设备等)执行的方法的计算机指令。
例如,该计算机程序被计算机执行时,使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品,该指令被计算机执行时使得该计算机实现上述方法实施例中由网络设备(如各个网元、接入网设备等)执行的方法。
本申请实施例还提供一种通信***,该通信***包括上文实施例中的网络设备(如各个网元、接入网设备等),如包括接入网设备和核心网设备。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例,此处不再赘述。
应理解,本申请实施例中提及的处理器可以是中央处理单元(central processing unit,CPU),还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解,本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM)。例如,RAM可以用作外部高速缓存。作为示例而非限定,RAM可以包括如下多种形式:静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
需要说明的是,当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时,存储器(存储模块)可以集成在处理器中。
还需要说明的是,本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的保护范围。
在本申请所提供的几个实施例中,应该理解到,所揭露的装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。此外,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外,在本申请各个实施例中的各功能单元可以集成在一个单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如,所述计算机可以是个人计算机,服务器,或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘(solid state disk,SSD)等。例如,前述的可用介质可以包括但不限于:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (30)
- 一种通信方法,其特征在于,包括:应用网元确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,所述多个不同类型的数据块中的数据包映射到同一个服务质量QoS流中;所述应用网元向策略控制网元发送指示信息,所述指示信息用于指示所述每个类型的数据块对应的调度优先级;所述调度优先级用于指示对不同类型的数据块的数据包进行调度,每个所述数据块包括至少一个数据包。
- 根据权利要求1所述的方法,其特征在于,所述指示信息包括在服务质量QoS需求中,所述QoS需求用于配置所述QoS流的参数,所述方法还包括:所述应用网元接收来自策略控制网元的响应消息,所述响应消息用于指示所述QoS流的参数配置完成;所述应用网元向用户面网元发送下行数据,所述下行数据中包括数据包和用于指示所述数据包所属的数据块的类型的指示信息。
- 根据权利要求2所述的方法,其特征在于,所述方法还包括:所述应用网元向所述用户面网元发送所述数据包所属的数据块的标识信息。
- 根据权利要求1至3中任一项所述的方法,其特征在于,所述不同类型的数据块包括以下任意一种:不同帧类型的数据块、处于用户视野不同位置的数据块、或不同层级的数据块,其中,所述层级包括基础层或增强层。
- 一种通信方法,其特征在于,包括:策略控制网元接收来自应用网元的指示信息,所述指示信息用于指示多个不同类型的数据块中每个类型的数据块对应的调度优先级,所述多个不同所述类型的数据块中的数据包映射到同一个服务质量QoS流中;所述策略控制网元向会话管理网元发送所述每个类型的数据块对应的调度优先级,所述调度优先级用于指示对不同类型的数据块的数据包进行调度。
- 根据权利要求5所述的方法,其特征在于,所述每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,所述PCC rule中还包括用于指示所述QoS流的调度优先级的信息。
- 根据权利要求6所述的方法,其特征在于,所述方法还包括:所述策略控制网元接收来自会话管理网元的响应消息,所述响应消息用于指示所述QoS流的参数配置完成;所述策略控制网元向所述应用网元发送所述响应消息。
- 一种通信方法,其特征在于,包括:会话管理网元接收来自策略控制网元的多个不同类型的数据块中每个类型的数据块对应的调度优先级,所述多个不同所述类型的数据块中的数据包映射到同一个服务质量QoS流中;所述会话管理网元向用户面网元发送所述每个类型的数据块对应的调度优先级和封装指示信息,所述封装指示信息用于指示所述用户面网元将接收到的数据包对应的调度优 先级封装在所述数据包中,其中,每个所述数据块包括至少一个数据包,所述调度优先级用于指示对不同类型的数据块的数据包进行调度。
- 根据权利要求8所述的方法,其特征在于,所述每个类型的数据块对应的调度优先级包括在策略和计费控制规则PCC rule中,所述PCC rule中还包括用于指示所述QoS流的调度优先级的信息。
- 根据权利要求9所述的方法,其特征在于,所述方法还包括:所述会话管理网元根据所述PCC rule配置所述QoS流的参数;所述会话管理网元向策略控制网元发送响应消息,所述响应消息用于指示所述QoS流的参数配置完成。
- 根据权利要求10所述的方法,其特征在于,所述方法还包括:所述会话管理网元为所述多个不同类型的数据块中的每个类型的数据块对应的调度优先级分配调度优先级标识,所述调度优先级标识用于标识所述每个类型的数据块对应的调度优先级;所述会话管理网元向用户面网元发送所述每个类型的数据块对应的调度优先级标识和对应关系,其中,所述对应关系包括所述多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
- 根据权利要求11所述的方法,其特征在于,所述方法还包括:所述会话管理网元向接入网设备发送多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
- 根据权利要求9至12中任一项所述的方法,其特征在于,所述方法还包括:所述会话管理网元向用户面网元发送封装信息,所述封装信息用于指示所述用户面网元将标识信息封装在所述数据包中,所述标识信息用于标识所述数据包所属的数据块。
- 一种通信方法,其特征在于,包括:用户面网元接收来自应用网元的下行数据,所述下行数据包括多个不同类型的数据块,所述多个不同类型的数据块中每个类型的数据块对应一个调度优先级,所述多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中,每个所述数据块包括至少一个数据包;所述用户面网元根据各数据包对应的类型以及每个类型的数据块对应的调度优先级确定数据包的调度优先级;所述用户面网元向接入网设备发送所述数据包,所述数据包中封装有指示所述数据包的调度优先级的信息,所述调度优先级用于指示对不同类型的数据块的数据包进行调度。
- 根据权利要求14所述的方法,其特征在于,所述方法还包括:所述用户面网元接收来自会话管理网元的每个类型的数据块对应的调度优先级和封装指示信息,所述封装指示信息用于指示所述用户面网元将接收到的数据包对应的调度优先级封装在所述数据包中。
- 根据权利要求14或15所述的方法,其特征在于,所述指示所述调度优先级的信息包括用于标识所述调度优先级的调度优先级标识,所述方法还包括:所述用户面网元接收来自会话管理网元的调度优先级标识和对应关系,所述调度优先级标识用于标识所述每个类型的数据块对应的调度优先级,所述对应关系包括所述多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
- 根据权利要求14至16中任一项所述的方法,其特征在于,所述方法还包括:所述用户面网元接收来自所述应用网元的所述数据包所属的数据块的标识信息。
- 根据权利要求17所述的方法,其特征在于,所述数据包中封装有所述标识信息,所述方法还包括:所述用户面网元接收来自所述会话管理网元的封装信息,所述封装信息用于指示所述用户面网元将标识信息封装在所述数据包中,所述标识信息用于标识所述数据包所属的数据块。
- 一种通信方法,其特征在于,包括:接入网设备接收来自用户面网元的多个数据包,所述多个数据包中的各数据包中封装有指示所述数据包对应的调度优先级的信息,所述多个数据包归属于多个不同类型的数据块,所述多个不同类型的数据块中每个类型的数据块对应一个调度优先级,所述调度优先级用于指示对不同类型的数据块的数据包进行调度,所述多个不同类型的数据块中的数据包均映射到同一个服务质量QoS流中;所述接入网设备根据所述调度优先级对所述数据包进行处理。
- 根据权利要求19所述的方法,其特征在于,所述指示所述调度优先级的信息包括用于标识所述调度优先级的调度优先级标识,所述方法还包括:接入网设备接收来自会话管理网元的多个不同类型的数据块的调度优先级和多个所述调度优先级标识的对应关系。
- 根据权利要求19或20所述的方法,其特征在于,所述数据包中还封装有所述数据包所属的数据块的标识信息,所述方法还包括:所述接入网设备根据所述标识信息确定是否调度和所述数据包属于同一个数据块中的除所述数据包之外的其他数据包。
- 一种通信装置,其特征在于,包括:用于执行如权利要求1至4中任一项所示的方法的单元或模块。
- 一种通信装置,其特征在于,包括:用于执行如权利要求5至7中任一项所示的方法的单元或模块。
- 一种通信装置,其特征在于,包括:用于执行如权利要求8至13中任一项所示的方法的单元或模块。
- 一种通信装置,其特征在于,包括:用于执行如权利要求14至18中任一项所示的方法的单元或模块。
- 一种通信装置,其特征在于,包括:用于执行如权利要求19至21中任一项所示的方法的单元或模块。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机指令,当所述计算机指令在计算机上运行时,如权利要求1至21中任一项所述的方法 被执行。
- 一种通信***,其特征在于,包括至少一个如权利要求22所述的通信装置、至少一个如权利要求23所述的通信装置、至少一个如权利要求24所述的通信装置、至少一个如权利要求25所述的通信装置和至少一个如权利要求26所述的通信装置。
- 一种通信方法,其特征在于,包括:应用网元确定多个不同类型的数据块中每个类型的数据块对应的调度优先级,所述多个不同类型的数据块中的数据包映射到同一个服务质量QoS流中;策略控制网元接收所述应用网元发送指示信息,所述指示信息用于指示所述每个类型的数据块对应的调度优先级;所述调度优先级用于指示对不同类型的数据块的数据包进行调度,每个所述数据块包括至少一个数据包。
- 根据权利要求29所述的方法,其特征在于,该方法进一步包括:所述策略控制网元向会话管理网元发送所述每个类型的数据块对应的调度优先级,所述调度优先级用于指示对不同类型的数据块的数据包进行调度。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210184934.XA CN116723582A (zh) | 2022-02-28 | 2022-02-28 | 通信方法和装置 |
CN202210184934.X | 2022-02-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023160116A1 true WO2023160116A1 (zh) | 2023-08-31 |
Family
ID=87764607
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/137911 WO2023160116A1 (zh) | 2022-02-28 | 2022-12-09 | 通信方法和装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116723582A (zh) |
WO (1) | WO2023160116A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117459525A (zh) * | 2023-12-20 | 2024-01-26 | 宁德时代新能源科技股份有限公司 | 文件上传方法、装置、设备和介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109076399A (zh) * | 2016-05-09 | 2018-12-21 | 高通股份有限公司 | 流内分组优先化和数据相关的灵活qos策略 |
CN110035018A (zh) * | 2018-01-12 | 2019-07-19 | 华为技术有限公司 | 确定网络服务质量流的方法、网元和*** |
CN111770531A (zh) * | 2019-04-01 | 2020-10-13 | 华为技术有限公司 | 获取数据包延迟参数的方法、***和装置 |
WO2022026056A1 (en) * | 2020-07-31 | 2022-02-03 | Intel Corporation | Predefined policy and charging control rules management |
-
2022
- 2022-02-28 CN CN202210184934.XA patent/CN116723582A/zh active Pending
- 2022-12-09 WO PCT/CN2022/137911 patent/WO2023160116A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109076399A (zh) * | 2016-05-09 | 2018-12-21 | 高通股份有限公司 | 流内分组优先化和数据相关的灵活qos策略 |
CN110035018A (zh) * | 2018-01-12 | 2019-07-19 | 华为技术有限公司 | 确定网络服务质量流的方法、网元和*** |
CN111770531A (zh) * | 2019-04-01 | 2020-10-13 | 华为技术有限公司 | 获取数据包延迟参数的方法、***和装置 |
WO2022026056A1 (en) * | 2020-07-31 | 2022-02-03 | Intel Corporation | Predefined policy and charging control rules management |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117459525A (zh) * | 2023-12-20 | 2024-01-26 | 宁德时代新能源科技股份有限公司 | 文件上传方法、装置、设备和介质 |
CN117459525B (zh) * | 2023-12-20 | 2024-04-12 | 宁德时代新能源科技股份有限公司 | 文件上传方法、装置、设备和介质 |
Also Published As
Publication number | Publication date |
---|---|
CN116723582A (zh) | 2023-09-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019158102A1 (zh) | 一种确定QoS描述信息的方法和装置 | |
WO2020019764A1 (zh) | 信息传输方法、设备及计算机可读存储介质 | |
CN112423340B (zh) | 一种用户面信息上报方法及装置 | |
US11432205B2 (en) | Data transmission method, communications apparatus, and user plane function entity | |
US20230116578A1 (en) | Data transmission method and apparatus | |
WO2020087509A1 (zh) | 无线通信方法、终端设备和网络设备 | |
US20230067851A1 (en) | Communication method and apparatus | |
WO2018228558A1 (zh) | 一种传输数据的方法、网络设备和终端设备 | |
US11824783B2 (en) | Maximum data burst volume (MDBV) determining method, apparatus, and system | |
WO2021069552A1 (en) | Identifying time sensitive network streams within a 3gpp qos flow | |
WO2023160116A1 (zh) | 通信方法和装置 | |
US20240163714A1 (en) | Communication method and communication apparatus | |
US20240214864A1 (en) | Communication method, apparatus, and system | |
WO2022012361A1 (zh) | 一种通信方法及装置 | |
US20220369154A1 (en) | Method and apparatus for indicating qos flow information | |
WO2020199034A1 (zh) | 用于中继通信的方法和装置 | |
US20240236756A9 (en) | Adaptive forwarding handling of data packets | |
WO2022170798A1 (zh) | 确定策略的方法和通信装置 | |
WO2021142669A1 (zh) | 业务传输的方法和设备 | |
WO2023185769A1 (zh) | 通信方法、通信装置和通信*** | |
CN113596909A (zh) | 通信方法、装置及*** | |
CN113906783A (zh) | 通信方法、装置及*** | |
WO2024001897A1 (zh) | 通信方法和装置 | |
WO2022222748A1 (zh) | 中继通信方法和装置 | |
WO2023185608A1 (zh) | 一种数据传输的方法及通信装置 |
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: 22928375 Country of ref document: EP Kind code of ref document: A1 |