WO2022067700A1

WO2022067700A1 - Communication method, apparatus, and system

Info

Publication number: WO2022067700A1
Application number: PCT/CN2020/119475
Authority: WO
Inventors: 马景旺; 周彧; 胡国杰; 晋英豪
Original assignee: 华为技术有限公司
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-07

Abstract

The embodiments of the present application provide a communication method, an apparatus and a system. Said method comprises: an access network device determining a first uplink resource scheduling policy of a first terminal device and a second uplink resource scheduling policy of a second terminal device, the first uplink resource scheduling policy containing information of a first DRB, the first DRB being used to bear uplink peak data of the first terminal device, and the second uplink resource scheduling policy containing information of a second DRB, the second DRB being used to bear uplink peak data of the second terminal device, and the usage time periods of the first DRB and the second DRB doing not completely overlap; and sending the first uplink resource scheduling policy to the first terminal device, and sending the second uplink resource scheduling policy to the second terminal device. The access network device can configure different terminal devices with different uplink resource scheduling policies, so that different terminal devices send uplink peak data to the access network device in different time periods, improving the transmission quality of the terminal devices and ensuring the stability of the state of the access network device.

Description

Communication method, device and system

technical field

The present application relates to the field of communication technologies, and in particular, to a communication method, device, and system.

Background technique

At present, in some vertical industry scenarios, one access network device can provide data transmission for multiple terminal devices at the same time, and the access network device does not accurately perceive the data transmission period of the uplink data of the terminal device, and there is no communication between the terminal devices. In coordination, multiple terminal devices may simultaneously transmit data that requires higher transmission resources through the access network device, resulting in bursts of data traffic. When the processing capability of the access network equipment is exceeded, problems such as packet loss or retransmission may also occur, which reduces the transmission quality of the terminal equipment and the instability of the state of the access network equipment.

How to coordinate uplink data transmission among multiple terminal devices needs to be solved urgently.

SUMMARY OF THE INVENTION

The present application provides a communication method, apparatus and system for coordinating uplink data transmission between multiple terminal devices, so as to improve the transmission quality of the terminal devices and ensure the stability of the state of the access network devices.

In a first aspect, an embodiment of the present application provides a communication method, including: an access network device determining a first uplink resource scheduling policy of a first terminal device and a second uplink resource scheduling policy of a second terminal device, the first uplink resource scheduling policy The resource scheduling policy includes the information of the first data radio bearer DRB, the first DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes the information of the second DRB, the first DRB is The two DRBs are used to carry the uplink peak data of the second terminal device, and the usage time periods of the first DRB and the second DRB do not completely overlap; the access network device sends the data to the first terminal device. the first uplink resource scheduling policy, and sending the second uplink resource scheduling policy to the second terminal device.

Based on the above solution, the access network device can configure different uplink resource scheduling policies for different terminal devices, so that different terminal devices send uplink peak data to the access network device in different time periods, thereby helping to reduce the number of The data volume of the uplink peak data sent in the time period reduces the pressure on the access network equipment to process data, improves the transmission quality of the terminal equipment and ensures the stability of the access network equipment status.

In a possible implementation method, the access network device receives uplink peak data from the first terminal device and uplink peak data from the second terminal device within a first time period, the first terminal device The uplink peak data of the terminal device is carried in the first DRB, the uplink peak data of the second terminal device is carried in the second DRB, and the data volume of the uplink peak data of the first terminal device is the same as that of the second DRB. The sum of the data volume of the uplink peak data of the terminal equipment does not exceed the data volume threshold.

Based on this solution, the sum of the data streams of uplink peak data received by the access network equipment from different terminal equipment does not exceed the data volume threshold, which can reduce the load of the access network equipment.

In a possible implementation method, the access network device determines the first uplink resource scheduling policy of the first terminal device and the second uplink resource scheduling policy of the second terminal device, including: the access network device according to the The first uplink resource scheduling policy is determined by the information of the first terminal device, and the second uplink resource scheduling policy is determined according to the information of the second terminal device.

In a possible implementation method, the access network device receives information of the first terminal device and information of the second terminal device from a session management network element, and the information of the first terminal device includes the identification information of the first terminal device, feature information of the service data flow of the first terminal device, and first quality of service QoS information of the service data flow of the first terminal device, the service data flow of the first terminal device The characteristic information is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the first terminal device in a time period, and the first QoS information is used to indicate that the different time slices correspond to QoS level identifier QCI, the information of the second terminal device includes the identification information of the second terminal device, the feature information of the service data flow of the second terminal device, and the service data flow of the second terminal device. The second QoS information, the feature information of the service data flow of the second terminal device is used to indicate the traffic feature information corresponding to different time slices of the service data flow of the second terminal device in a time period, the The second QoS information is used to indicate the respective QCIs corresponding to the different time slices.

Based on this solution, the access network device determines the uplink resource scheduling policy of the terminal device based on the information of the terminal device, which can realize accurate determination of the uplink resource scheduling policy.

In a possible implementation method, the feature information of the service data flow of the first terminal device includes a first time period, at least two time slices corresponding to the first time period, and the at least two time slices The bit rates corresponding to the slices respectively, the first QoS information includes the QFI and the QCIs corresponding to the at least two time slices, and the QCIs corresponding to the at least two time slices are not exactly the same, and the first terminal The service data flow of the device is mapped to the QoS flow corresponding to the QFI; the feature information of the service data flow of the second terminal device includes a second time period, at least two time slices corresponding to the second time period and all The bit rates corresponding to the at least two time slices, the second QoS information includes the QFI and the QCIs corresponding to the at least two time slices, and the QCIs corresponding to the at least two time slices are not exactly the same , the service data flow of the second terminal device is mapped to the QoS flow corresponding to the QFI.

In a possible implementation method, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB; The determining, by the access network device, the first uplink resource scheduling policy according to the information of the first terminal device includes: determining, by the access network device, the type of the first DRB according to the first QoS information. The information of the second DRB includes the type of the second DRB, and the type of the second DRB is used to indicate the traffic characteristics of the service data flow carried by the second DRB; the access network device Determining the second uplink resource scheduling policy based on the information of the second terminal device includes: determining, by the access network device, the type of the second DRB according to the second QoS information.

In a possible implementation method, the information of the first DRB includes the initial usage time of the first DRB and the usage duration of the first DRB, the initial usage time of the first DRB and the The use duration of the first DRB is used for the first terminal device to determine the time for sending the uplink peak data; the access network device determines the first uplink resource scheduling policy according to the information of the first terminal device, including: The access network device determines the initial use time of the first DRB and the use time of the first DRB according to the characteristic information of the service data flow of the first terminal device. The information of the second DRB includes the initial usage time of the second DRB and the usage duration of the second DRB, and the initial usage time of the second DRB and the usage duration of the second DRB are used for all determining, by the second terminal device, the time to send the uplink peak data; and determining, by the access network device, the second uplink resource scheduling policy according to the information of the second terminal device, including: the access network device determining the second uplink resource scheduling policy according to the first The characteristic information of the service data flow of the two terminal devices determines the initial use time of the second DRB and the use time of the second DRB.

In a possible implementation method, the information of the first DRB includes configuration information of the first DRB, and the configuration information of the first DRB includes time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, One or more of listening reference signal resource indication and demodulation reference signal; the information of the second DRB includes configuration information of the second DRB, and the configuration information of the second DRB includes time domain resources, frequency domain resources One or more of resource, modulation and coding scheme, antenna port, listening reference signal resource indication, demodulation reference signal.

In a possible implementation method, the uplink peak data of the first terminal device carried by the first DRB includes I frame data, and the uplink peak data of the second terminal device carried by the second DRB includes I frame data.

In a possible implementation method, the first uplink resource scheduling policy further includes information of a third DRB, where the third DRB is used to carry the uplink general data of the first terminal device.

In a possible implementation method, the uplink normal data of the first terminal device includes P frame data.

In a second aspect, an embodiment of the present application provides a communication method, including: a first terminal device receiving a first uplink resource scheduling policy from an access network device, where the first uplink resource scheduling policy includes information of at least one DRB, The information of the at least one DRB includes the information of the first DRB, and the first DRB is used to carry the uplink peak data of the first terminal device; the first terminal device, according to the first uplink resource scheduling policy, The uplink peak data of the first terminal device is sent to the access network device on the first DRB.

Based on this solution, the terminal device sends the uplink peak data to the access network device on the DRB used to carry the uplink peak data according to the uplink resource scheduling policy configured by the access network device, which can improve the data transmission quality.

In a possible implementation method, the first terminal device sends the uplink peak data of the first terminal device to the access network device on the first DRB according to the first uplink resource scheduling policy , including: the first terminal device determines the first DRB according to the first uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the first terminal device; Send the uplink peak data of the first terminal device to the access network device on a DRB.

In a possible implementation method, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB; The determining, by the first terminal equipment, the first DRB according to the first uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the first terminal equipment includes: the first terminal equipment according to the first terminal equipment. The traffic characteristics of the uplink peak data of the device determine the DRB type corresponding to the uplink peak data of the first terminal device; the first terminal device determines the first DRB corresponding to the DRB type.

In a possible implementation method, the information of the first DRB includes the initial use time of the first DRB and the use time of the first DRB; the first terminal device is on the first DRB Sending the uplink peak data of the first terminal device to the access network device includes: the first terminal device, according to the initial use time of the first DRB and the use time of the first DRB, The uplink peak data of the first terminal device is sent to the access network device on the first DRB.

In a possible implementation method, the information of the first DRB includes a usage period of the first DRB, and the usage period is used to indicate a period during which the first terminal device sends uplink peak data.

Based on the above solution, the terminal device can periodically send uplink peak data to the access network device, reducing the number of times of DRB configuration, and improving data transmission efficiency.

In a possible implementation method, the information of the first DRB includes configuration information of the first DRB, and the configuration information of the first DRB includes time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, One or more of listening reference signal resource indication and demodulation reference signal.

In a possible implementation method, the uplink peak data of the first terminal device carried by the first DRB includes I-frame data.

In a possible implementation method, the use time period of the first DRB and the second DRB do not completely overlap, and the second DRB is used to carry the uplink peak data of the second terminal device; wherein, in the first time period The sum of the data volume of the uplink peak data of the first terminal device and the data volume of the uplink peak data of the second terminal device does not exceed the data volume threshold.

Based on the above solution, a terminal device can transmit both uplink peak data and uplink ordinary data, which improves the diversity of data transmission and improves data transmission capability and efficiency.

In a third aspect, an embodiment of the present application provides a communication apparatus, and the apparatus may be an access network device or a chip used for the access network device. The apparatus has the function of implementing the above-mentioned first aspect, or each possible implementation method of the first aspect. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fourth aspect, an embodiment of the present application provides a communication apparatus, and the apparatus may be a terminal device or a chip used for the terminal device. The apparatus has the function of implementing the above-mentioned second aspect or each possible implementation method of the second aspect. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fifth aspect, an embodiment of the present application provides a communication device, including a processor and a memory; the memory is used to store computer-executed instructions, and when the device is running, the processor executes the computer-executed instructions stored in the memory, so that the The apparatus performs any of the above-mentioned methods of the first to second aspects and possible implementation methods of the first to second aspects.

In a sixth aspect, an embodiment of the present application provides a communication device, including a communication device for performing each step of the methods of the first aspect to the second aspect and any of the possible implementation methods of the first aspect to the second aspect. Units or means.

In a seventh aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the methods of the first aspect to the second aspect and the first aspect to any of the possible implementations of the second aspect. The processor includes one or more.

In an eighth aspect, an embodiment of the present application provides a communication device, including a processor, which is connected to a memory and used to call a program stored in the memory to execute the methods of the first to second aspects and the first Any of the possible implementations of the aspect to the second aspect. The memory may be located within the device or external to the device. And the processor includes one or more.

In a ninth aspect, an embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the processor executes the above-mentioned first to second aspects The method and any of the possible implementation methods of the first aspect to the second aspect.

In a tenth aspect, an embodiment of the present application further provides a computer program product, the computer product includes a computer program, when the computer program runs, the methods of the first aspect to the second aspect and each of the first aspect to the second aspect are enabled. Any of the possible implementations.

In an eleventh aspect, an embodiment of the present application further provides a chip system, including: a processor configured to execute the methods of the first aspect to the second aspect and any of the possible implementation methods of the first aspect to the second aspect any method.

In a twelfth aspect, an embodiment of the present application further provides a communication system, including an access network device and a session management network element. The session management network element is configured to send the information of the first terminal device and the information of the second terminal device to the access network device. The access network device is configured to determine a first uplink resource scheduling policy according to the information of the first terminal device, and determine a second uplink resource scheduling policy according to the information of the second terminal device, the first uplink resource The scheduling policy includes the information of the first data radio bearer DRB, the first DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes the information of the second DRB, the second The DRB is used to carry the uplink peak data of the second terminal device, and the usage time periods of the first DRB and the second DRB do not completely overlap; sending the first uplink resource scheduling policy to the first terminal device , and sending the second uplink resource scheduling policy to the second terminal device.

In a thirteenth aspect, an embodiment of the present application further provides a communication method, including: a session management network element sending information of the first terminal device and information of the second terminal device to an access network device. The access network device determines a first uplink resource scheduling policy according to the information of the first terminal device, and determines a second uplink resource scheduling policy according to the information of the second terminal device, where the first uplink resource scheduling policy includes the first The data radio bears the information of the DRB, the first DRB is used to bear the uplink peak data of the first terminal device, and the second uplink resource scheduling policy includes the information of the second DRB, and the second DRB is used to bear all the data. the uplink peak data of the second terminal device, the usage time periods of the first DRB and the second DRB do not completely overlap; the access network device sends the first uplink resource scheduling policy to the first terminal device, and sending the second uplink resource scheduling policy to the second terminal device.

Description of drawings

FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application;

Figure 2(a) is a schematic diagram of a 5G network architecture based on a service-oriented architecture;

Figure 2(b) is a schematic diagram of a 5G network architecture based on a point-to-point interface;

Fig. 3 (a) is the data flow characteristic schematic diagram of the upstream data flow uploaded by terminal equipment;

Figure 3 (b) is a schematic diagram of the data flow characteristics of upstream data streams uploaded by multiple terminal devices simultaneously;

4 is a schematic diagram of a communication method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of another communication method provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another communication method provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of another communication method provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of another communication method provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of the configuration of this uplink resource scheduling policy;

FIG. 10 is a schematic diagram of a communication device provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another communication device provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of yet another communication device provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operation methods in the method embodiments may also be applied to the apparatus embodiments or the system embodiments. Wherein, in the description of the present application, unless otherwise specified, the meaning of "plurality" is two or more.

In order to solve the problems mentioned in the background art, as shown in FIG. 1 , the present application provides a communication system, which includes an access network device and a session management network element.

The session management network element is configured to send the information of the first terminal device and the information of the second terminal device to the access network device; the access network device is configured to determine according to the information of the first terminal device a first uplink resource scheduling policy, and determining a second uplink resource scheduling policy according to the information of the second terminal device, where the first uplink resource scheduling policy includes information of a first data radio bearer DRB, and the first DRB is used for Bearing the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes information of a second DRB, the second DRB is used to carry the uplink peak data of the second terminal device, the first The use time period of the DRB and the second DRB does not completely overlap; the first uplink resource scheduling policy is sent to the first terminal device, and the second uplink resource scheduling policy is sent to the second terminal device.

In a possible implementation method, the access network device is further configured to receive the uplink peak data from the first terminal device and the uplink peak data from the second terminal device within the first time period, The uplink peak data of the first terminal device is carried in the first DRB, the uplink peak data of the second terminal device is carried in the second DRB, and the data volume of the uplink peak data of the first terminal device is the same as that of the first terminal device. The sum of the data volume of the uplink peak data of the second terminal device does not exceed the data volume threshold.

In a possible implementation method, the access network device is further configured to receive the information of the first terminal device and the information of the second terminal device from a session management network element, and the information of the first terminal device The information includes the identification information of the first terminal device, the feature information of the service data flow of the first terminal device, and the first quality of service QoS information of the service data flow of the first terminal device. The characteristic information of the service data flow is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the first terminal device in a time period, and the first QoS information is used to indicate the different time slices. The QoS levels corresponding to the slices are identified as QCIs.

In a possible implementation method, the information of the second terminal device includes identification information of the second terminal device, feature information of the service data flow of the second terminal device, and service data of the second terminal device The second QoS information of the data flow, the characteristic information of the service data flow of the second terminal device is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the second terminal device in a time period , the second QoS information is used to indicate the respective QCIs corresponding to the different time slices; the access network device is used to determine the first uplink resource scheduling policy of the first terminal device and the second The uplink resource scheduling policy specifically includes: determining the first uplink resource scheduling policy according to the information of the first terminal device, and determining the second uplink resource scheduling policy according to the information of the second terminal device.

In a possible implementation method, the feature information of the service data flow of the first terminal device includes a first time period, at least two time slices corresponding to the first time period, and the at least two time slices The bit rates corresponding to the slices respectively, the first QoS information includes the QFI and the QCIs corresponding to the at least two time slices, and the QCIs corresponding to the at least two time slices are not exactly the same, and the first terminal The service data flow of the device is mapped to the QoS flow corresponding to the QFI.

In a possible implementation method, the feature information of the service data flow of the second terminal device includes a second time period, at least two time slices corresponding to the second time period, and the at least two time slices the bit rates corresponding to the slices respectively, the second QoS information includes the QFI and the QCIs corresponding to the at least two time slices, the QCIs corresponding to the at least two time slices are not exactly the same, the second terminal The service data flow of the device is mapped to the QoS flow corresponding to the QFI.

In a possible implementation method, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB; The access network device is configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, specifically including: determining the type of the first DRB according to the first QoS information.

In a possible implementation method, the information of the second DRB includes the type of the second DRB, and the type of the second DRB is used to indicate the traffic characteristics of the service data flow carried by the second DRB; The access network device is configured to determine the second uplink resource scheduling policy according to the information of the second terminal device, which specifically includes: determining the type of the second DRB according to the second QoS information.

In a possible implementation method, the information of the first DRB includes the initial usage time of the first DRB and the usage duration of the first DRB, the initial usage time of the first DRB and the The use duration of the first DRB is used for the first terminal device to determine the time for sending the uplink peak data; the access network device is configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, Specifically, the method includes: determining the initial usage time of the first DRB and the usage duration of the first DRB according to the characteristic information of the service data flow of the first terminal device.

In a possible implementation method, the information of the second DRB includes an initial usage time of the second DRB and a usage duration of the second DRB, and the initial usage time of the second DRB and the The use duration of the second DRB is used for the second terminal device to determine the time for sending uplink peak data; the access network device is configured to determine the second uplink resource scheduling policy according to the information of the second terminal device, Specifically, the method includes: determining the initial use time of the second DRB and the use time of the second DRB according to the characteristic information of the service data flow of the second terminal device.

In a possible implementation method, the information of the second DRB includes configuration information of the second DRB, and the configuration information of the second DRB includes time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, One or more of listening reference signal resource indication and demodulation reference signal.

The specific implementation of the above solution will be described in detail in the subsequent method embodiment section, and will not be repeated here.

The system shown in Figure 1 can be used in the fifth generation (5G) network architecture shown in Figure 2(a) or Figure 2(b), of course, it can also be used in future network architectures, such as the sixth generation (6th generation, 6G) network architecture, etc., which are not limited in this application.

Exemplarily, it is assumed that the communication system shown in FIG. 1 is applied to a 5G network architecture, as shown in FIG. 2( a ), which is a schematic diagram of a 5G network architecture based on a service-oriented architecture. The network element or entity corresponding to the access network device in FIG. 1 may be a radio access network (radio access network, RAN) device in the 5G network architecture shown in FIG. 2(a). The network element or entity corresponding to the session management network element in FIG. 1 may be a session management function (session management function, SMF) network element in the 5G network architecture shown in FIG. 2(a).

The 5G network architecture shown in Figure 2(a) can include three parts, namely the terminal equipment part, the data network (DN) and the operator network part. The following briefly describes the functions of some of the network elements.

The operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network element, Network Exposure Function (NEF) network element, Policy Control Function (Policy Control Function) Function, PCF) network element, unified data management (unified data management, UDM), unified database (Unified Data Repository, UDR), network storage function (Network Repository Function, NRF) network element, application function (Application Function, AF) network Elements, Access and Mobility Management Function (AMF) network elements, SMF network elements, RAN, and user plane function (UPF) network elements, etc. In the above-mentioned operator network, the part other than the radio access network part may be referred to as the core network part.

In specific implementation, the terminal device in this embodiment of the present application may be a device for implementing a wireless communication function. The terminal equipment may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station in a 5G network or a public land mobile network (PLMN) evolved in the future. , remote station, remote terminal, mobile device, wireless communication device, terminal agent or terminal device, etc. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. Terminals can be mobile or stationary.

The above-mentioned terminal device can establish a connection with the operator network through an interface (eg, N1, etc.) provided by the operator network, and use the data and/or voice services provided by the operator network. The terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party. Wherein, the above-mentioned third party may be a service party other than the operator's network and the terminal device, and may provide other data and/or voice services for the terminal device. Wherein, the specific expression form of the above third party can be specifically determined according to the actual application scenario, and is not limited here.

RAN is a sub-network of an operator's network, and is an implementation system between service nodes and terminal equipment in the operator's network. To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN. The RAN device in this application is a device that provides a wireless communication function for a terminal device, and the RAN device is also called an access network device. The RAN equipment in this application includes but is not limited to: next-generation base station (g nodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B in 5G (node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.

The AMF network element mainly performs functions such as mobility management, access authentication or authorization. In addition, it is also responsible for transferring user policies between UE and PCF.

The SMF network element mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and allocation of UE Internet Protocol (IP) addresses.

The UPF network element, as the interface UPF with the data network, implements functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation.

The UDM network element is mainly responsible for the management of contract data, user access authorization and other functions.

UDR is mainly responsible for the access function of contract data, policy data, application data and other types of data.

The NEF network element is mainly used to support the opening of capabilities and events.

The AF network element mainly conveys the requirements of the application side to the network side, such as QoS requirements or subscription of user status events. The AF may be a third-party functional entity or an application service deployed by an operator, such as an IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service. The AF network element may also be called an application server.

The PCF network element is mainly responsible for policy control functions such as charging for sessions and service data flow levels, QoS bandwidth guarantee and mobility management, and UE policy decision-making.

The NRF network element can be used to provide the network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements. NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.

AUSF network element: It is mainly responsible for authenticating users to determine whether to allow users or devices to access the network.

A DN is a network outside the operator's network. The operator's network can access multiple DNs, and multiple services can be deployed on the DNs, which can provide data and/or voice services for terminal devices. For example, DN is the private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices, and the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor. The sensor can communicate with the control server, obtain the instruction of the control server, and transmit the collected sensor data to the control server according to the instruction. For another example, the DN is an internal office network of a company. The mobile phones or computers of employees of the company can be terminal devices, and the mobile phones or computers of employees can access information and data resources on the internal office network of the company.

In Fig. 2(a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For the meanings of these interface serial numbers, refer to the meanings defined in the 3GPP standard protocol, which is not limited here.

Exemplarily, it is assumed that the communication system shown in FIG. 1 is applied to a 5G network architecture, as shown in FIG. 2(b), which is a schematic diagram of a 5G network architecture based on a point-to-point interface. The network element or entity corresponding to the access network device in FIG. 1 may be the RAN device in the 5G network architecture shown in FIG. 2(b). The network element or entity corresponding to the session management network element in FIG. 1 may be the SMF network element in the 5G network architecture shown in FIG. 2(b).

For the introduction of the functions of the network elements in FIG. 2( b ), reference may be made to the introduction of the functions of the corresponding network elements in FIG. 2( a ), and details are not repeated here. The main difference between Fig. 2(b) and Fig. 2(a) is that the interface between each network element in Fig. 2(b) is a point-to-point interface, not a service-oriented interface.

In the architecture shown in Figure 2(b), the interface names and functions between each network element are as follows:

1), N7: the interface between the PCF and the SMF, used to issue a protocol data unit (protocol data unit, PDU) session granularity and a business data flow granularity control policy.

2), N15: the interface between the PCF and the AMF, used for delivering UE policies and access control related policies.

3), N5: the interface between the AF and the PCF, used for application service request delivery and network event reporting.

4), N4: The interface between the SMF and the UPF, used to transmit information between the control plane and the user plane, including controlling the distribution of forwarding rules for the user plane, QoS control rules, traffic statistics rules, etc., and information on the user plane report.

5), N11: the interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control message sent to the UE, the radio resource control information sent to the RAN, and the like.

6), N2: the interface between the AMF and the RAN, used to transmit radio bearer control information from the core network side to the RAN, etc.

7), N1: the interface between the AMF and the UE, irrespective of access, used to deliver QoS control rules and the like to the UE.

8), N8: the interface between the AMF and the UDM, for the AMF to obtain the access and mobility management related subscription data and authentication data from the UDM, and the AMF to register the UE's current mobility management related information to the UDM.

9), N10: the interface between the SMF and the UDM, for the SMF to obtain the session management related subscription data from the UDM, and the SMF to register the UE's current session related information to the UDM.

10), N35: an interface between the UDM and the UDR, used for the UDM to obtain user subscription data information from the UDR.

11), N36: an interface between the PCF and the UDR, for the PCF to obtain the policy-related subscription data and application data-related information from the UDR.

12), N12: the interface between AMF and AUSF, used for AMF to initiate an authentication process to AUSF, which can carry SUCI as a contract identifier;

13), N13: the interface between the UDM and the AUSF, for the AUSF to obtain the user authentication vector from the UDM to execute the authentication process.

It can be understood that the above network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or may be implemented jointly by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

The session management network elements, policy control network elements, user plane network elements, and access network equipment in this application may be SMF, PCF, UPF, and RAN in Fig. 2(a) or Fig. 2(b), respectively, or may be In the future communication, such as the network element having the functions of the above-mentioned SMF, PCF, UPF, and RAN in the 6G network, this application does not limit this. For the convenience of description, the present application takes as an example that the session management network element, the policy control network element, the user plane network element, and the access network equipment are the above-mentioned SMF, PCF, UPF, and RAN, respectively. In addition, the terminal device is taken as an example of UE for description.

In the existing QoS model, when UPF receives downlink packets, UPF will filter packets with the same reliability requirements (Packet Detection Rule, PDR) configured in advance by SMF. packets) are encapsulated into the same QoS flow. Multiple QoS flows may exist in the same PDU session (PDU session), but each QoS flow has an independent and unique QoS flow identifier (QoS flow Identifier, QFI), and each QoS flow is associated with a QoS configuration file (QoS flow Identifier). profile). The network side will use the same QoS guarantee for packets belonging to the same QoS flow according to the parameters in the QoS profile, such as delay, forwarding priority, packet loss rate, etc.

When the RAN receives the downlink QoS flow from the UPF, the RAN will encapsulate multiple QoS flows into the same Data Radio Bearer (DRB) according to certain mapping rules, and the same DRB will enjoy the same reliability on the air interface side Assure.

As described in the background art, in some vertical industry scenarios, one access network device can provide data transmission for multiple terminal devices at the same time, and the RAN device does not accurately perceive the data transmission period of the uplink data of the terminal devices, and the communication between the terminal devices Without coordination, multiple terminal devices may simultaneously transmit data that requires high transmission resources through the RAN device, resulting in bursts of data traffic. The following description takes the terminal device as a camera as an example. In vertical industry scenarios such as ports, multiple cameras are deployed in the work area, and the video from the cameras sends audio and video data to the application server (ie AF) through the 5G network. The video transmission of the camera has the following characteristics: the QoS requirements of the media service data flow change within a certain time period. For example, in a time period corresponding to a group of pictures (GOP): when the GOP is 60, the frame rate is 60 frames per second, and the time period is 1 second, the initial frame in a time period can be an I frame, The rate required by QoS is 60MB/s, the transmission time length is 16.7ms, and the reliability requirement is 99.9%. During the remaining transmission time (ie, 16.8ms to 1s) in a time period, P frames are transmitted at a rate of 8MB/s, the packet loss rate can be relaxed to 1%. The deployed cameras also differ in their media transfer characteristics due to different technical specifications (resolution, frame rate, etc.). It should be noted that, because the I frame is the first frame, the amount of data is large, and the requirements for delay and reliability are relatively high.

As shown in FIG. 3( a ), it is a schematic diagram of the data flow characteristics of the uplink data flow uploaded by the UE. The time period is 1 second, and one time period is divided into 60 time slices, each of which is used to transmit one frame of image. Time slice 1 is used to transmit I frames, time slices 2-60 are used to transmit P frames, and each time slice transmits one P frame.

As shown in FIG. 3( b ), it is a schematic diagram of data flow characteristics of uplink data streams uploaded by multiple UEs simultaneously. In the figure, three UEs are used as cameras as an example, but in practice, there may be two or more cameras in any number. It can be seen that when multiple cameras transmit the I frame of time slice 1, they partially or completely overlap in time, which may cause the RAN device to receive a large amount of burst uplink data at a certain time point or time period. As a result, packet loss or retransmission occurs, which affects the quality of data transmission and causes instability of RAN equipment.

In the embodiment of the present application, the service data flow information includes one of the identification of the application (Application ID, App ID), the identification information of the service data flow, the characteristic information (Traffic model) of the service data flow, and the QoS requirement of the service data flow or multiple.

Wherein, the identifier of the application is used to identify a specific service, for example, it can be a set character.

The identification information of the service data stream includes but is not limited to one or more of the following information: IP triplet, Uniform Resource Locator (Uniform Resource Locator, URL). The IP triplet refers to the IP address, port number and protocol number of the application server (ie AF).

The feature information of the service data stream is used to describe the feature of the service data stream, and the feature information of the service data stream includes a time period, at least two time slices corresponding to the time period, and a bit rate corresponding to each time slice.

The QoS requirements of the service data flow include but are not limited to one or more of the following information: bit rate (bitrate), packet loss rate (Packet Error Rate, PER), and packet delay budget (Packet Delay Budget, PDB).

It should be noted that there is a corresponding relationship between the characteristic information of the service data flow and the QoS requirements of the service data flow. Each time slice in a time period in the characteristic information of the service data flow corresponds to a QoS requirement, and different time slices correspond to The QoS requirements may or may not be the same. Exemplarily, a time period is divided into 10 time slices, which are time slice 1 to time slice 10 respectively. Among them, time slice 1 corresponds to QoS requirement 1, time slices 2-3 all correspond to QoS requirement 2, and time slices 4-10 all correspond to QoS requirement 3.

To solve the problems mentioned in the background art, as shown in FIG. 4 , an embodiment of the present application provides a schematic diagram of a communication method. In this communication method, the RAN configures uplink resource scheduling policies for two UEs (ie, the first UE and the second UE) as an example. For the method for configuring uplink resource scheduling policies for multiple UEs, refer to configuring uplink resource scheduling for two UEs. How the strategy is implemented.

The method includes the following steps:

Step 401, the RAN determines the first uplink resource scheduling policy of the first UE and the second uplink resource scheduling policy of the second UE.

The first uplink resource scheduling policy includes information of one or more data radio bearers (Data Radio Bearers, DRBs), the information of the one or more DRBs at least includes information of the first DRB, and the first DRB is used to bear the first UE up peak data. It can be understood that the first uplink resource scheduling policy is used to enable the first UE to send uplink peak data on the first DRB and send uplink normal data on other DRBs (such as the third DRB). Uplink peak data refers to data with a high transmission rate, so the amount of data is large in a short period of time. Uplink common data refers to data with a normal or low transmission rate, so the amount of data is not large in a short period of time. Exemplarily, the uplink peak data of the first UE carried by the first DRB includes I-frame data. The uplink common data of the first UE carried by the third DRB includes P frame data.

The second uplink resource scheduling policy includes information of one or more DRBs, and the information of the one or more DRBs at least includes information of a second DRB, and the second DRB is used to carry the uplink peak data of the second UE. It can be understood that the second uplink resource scheduling policy is used to enable the second UE to send uplink peak data on the second DRB and send uplink normal data on other DRBs (eg, the fourth DRB). Exemplarily, the uplink peak data of the second UE carried by the second DRB includes I-frame data. The uplink normal data of the second UE carried by the fourth DRB includes P frame data.

Wherein, the usage time periods of the first DRB and the second DRB do not completely overlap. Specifically, the usage time periods of the first DRB and the second DRB may partially overlap, or do not overlap at all. In this way, the first UE and the second UE can stagger the time for sending the uplink peak data.

As an implementation method, the RAN may receive the information of the first UE from the SMF, and then determine the first uplink resource scheduling policy according to the information of the first UE. The information of the first UE includes identification information of the first UE, characteristic information of the service data flow of the first UE, and first QoS information of the service data flow of the first UE, and the characteristic information of the service data flow of the first UE is used In order to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the first UE in a time period, the first QoS information is used to indicate the QCI corresponding to different time slices respectively. Optionally, the feature information of the service data flow of the first UE includes a first time period, at least two time slices corresponding to the first time period, and bit rates corresponding to the at least two time slices respectively, and the first QoS information includes: The QFI and the QCIs corresponding to the at least two time slices respectively, the QCIs corresponding to the at least two time slices are not exactly the same, and the service data flow of the first UE is mapped to the QoS flow corresponding to the QFI. For example, the RAN determines the type of the first DRB according to the first QoS information, and determines the initial usage time of the first DRB, the usage duration of the first DRB, or the first DRB according to the characteristic information of the service data flow of the first UE. at least one of the life cycles. That is, the information of the first DRB includes at least one of the type of the first DRB, the initial use time of the first DRB, the use duration of the first DRB, or the use period of the first DRB.

As an implementation method, the RAN may receive the information of the second UE from the SMF, and then determine the second uplink resource scheduling policy according to the information of the second UE. The information of the second UE includes identification information of the second UE, characteristic information of the service data flow of the second UE, and second QoS information of the service data flow of the second UE, and the characteristic information of the service data flow of the second UE is used In order to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the second UE in a time period, the second QoS information is used to indicate the QCI corresponding to different time slices respectively. Optionally, the feature information of the service data flow of the second UE includes a second time period, at least two time slices corresponding to the second time period, and bit rates corresponding to the at least two time slices respectively, and the second QoS information includes: The QFI and the QCI corresponding to the at least two time slices respectively, the QCI corresponding to the at least two time slices are not exactly the same, and the service data flow of the second UE is mapped to the QoS flow corresponding to the QFI. For example, the RAN determines the type of the second DRB according to the second QoS information, and determines the starting use time of the second DRB, the use duration of the second DRB, or the second DRB according to the characteristic information of the service data flow of the second UE at least one of the life cycles. That is, the information of the second DRB includes at least one of the type of the second DRB, the starting time of use of the second DRB, the duration of use of the second DRB, or the use period of the second DRB.

Step 402, the RAN sends the first uplink resource scheduling policy to the first UE. Correspondingly, the first UE receives the first uplink resource scheduling policy.

Step 403, the RAN sends the second uplink resource scheduling policy to the second UE. Correspondingly, the second UE receives the second uplink resource scheduling policy.

The sequence of the above steps 402 and 403 is not limited.

Step 404, the first UE sends the uplink peak data of the first UE to the RAN on the first DRB according to the first uplink resource scheduling policy.

The first UE determines the first DRB according to the first uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the first UE, and then sends the uplink peak data of the first UE to the RAN on the first DRB. For example, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB, and the first UE can use the traffic characteristics of the uplink peak data of the first UE according to the traffic characteristics of the first UE. , determine the DRB type corresponding to the uplink peak data of the first UE, and then determine the first DRB corresponding to the DRB type.

As an example, a QoS Class Identifier (QCI) may be used to identify the DRB type. For example, the RAN configures DRB information 1, DRB information 2, and DRB information 3 for the first UE, wherein the DRB type carried in DRB information 1 is QCI 1, the DRB type carried in DRB information 2 is QCI 2, and the DRB information carried in DRB information 3 is QCI 2. The DRB type is QCI 3, the DRB 1 corresponding to the DRB information 1 is used to carry the uplink peak data, the DRB 2 corresponding to the DRB information 2 and the DRB 3 corresponding to the DRB information 3 are used to carry the uplink normal data. When the first UE determines that the DRB type corresponding to the traffic characteristics of the uplink data to be sent is QCI 1, the first UE determines to use the DRB 1 corresponding to the DRB information 1 to uplink the uplink data that needs to be sent (that is, the uplink peak data) .

Optionally, the information of the first DRB further includes the initial usage time of the first DRB and the usage duration of the first DRB, then the first UE may, according to the initial usage time of the first DRB and the usage duration of the first DRB, The uplink peak data of the first UE is sent to the RAN on the first DRB. That is, the first UE starts to send the uplink peak data from the initial use time of the first DRB, and the maximum duration of a single transmission does not exceed the use time of the first DRB.

Optionally, the information of the first DRB further includes the usage period of the first DRB, where the usage period is used to indicate the period during which the first UE sends the uplink peak data, and the first UE may periodically send the RAN based on the usage period. Upstream peak data. Wherein, when the information of the first DRB includes the initial use time of the first DRB, the use duration of the first DRB, and the use period of the first DRB, the first UE periodically sends the uplink peak data to the RAN, and the first sending is It starts to be sent at the initial usage time of the first DRB, and the maximum duration of each transmission does not exceed the usage duration of the first DRB.

Optionally, the information of the first DRB further includes one or more of time-domain resources, frequency-domain resources, modulation and coding scheme, antenna port, listening reference signal resource indication, and demodulation reference signal. Thus, the first UE may determine a specific manner of sending uplink peak data based on one or more of time domain resources, frequency domain resources, modulation and coding scheme, antenna port, listening reference signal resource indication, and demodulation reference signal.

Step 405, the second UE sends the uplink peak data of the second UE to the RAN on the second DRB according to the second uplink resource scheduling policy.

The second UE determines the second DRB according to the second uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the second UE, and then sends the uplink peak data of the second UE to the RAN on the second DRB. For example, the information of the second DRB includes the type of the second DRB, and the type of the second DRB is used to indicate the traffic characteristics of the service data flow carried by the second DRB, then the second UE can use the traffic characteristics of the uplink peak data of the second UE according to , determine the DRB type corresponding to the uplink peak data of the second UE, and then determine the second DRB corresponding to the DRB type.

As an example, a QoS Class Identifier (QCI) may be used to identify the DRB type. For example, the RAN configures DRB information 4, DRB information 5, and DRB information 6 for the second UE, wherein the DRB type carried in DRB information 4 is QCI 4, the DRB type carried in DRB information 5 is QCI 5, and the DRB information carried in DRB information 6 is QCI 5. The DRB type is QCI 6, the DRB 4 corresponding to the DRB information 4 is used to carry the uplink peak data, the DRB 5 corresponding to the DRB information 5 and the DRB 6 corresponding to the DRB information 6 are used to carry the uplink normal data. When the second UE determines that the DRB type corresponding to the traffic characteristics of the uplink data to be sent is QCI 4, the second UE determines to use the DRB 4 corresponding to the DRB information 4 to uplink the uplink data that needs to be sent (that is, the uplink peak data) .

Optionally, the information of the second DRB further includes the initial usage time of the second DRB and the usage duration of the second DRB, then the second UE may, according to the initial usage time of the second DRB and the usage duration of the second DRB, The uplink peak data of the second UE is sent to the RAN on the second DRB. That is, the second UE starts to send the uplink peak data from the start time of using the second DRB, and the maximum duration of a single transmission does not exceed the usage time of the second DRB.

Optionally, the information of the second DRB further includes the use period of the second DRB, and the use period is used to indicate the period during which the second UE sends the uplink peak data, and the second UE may periodically send the data to the RAN based on the use period. Upstream peak data. Among them, when the information of the second DRB includes the initial use time of the second DRB, the use duration of the second DRB, and the use period of the second DRB, the second UE periodically sends the uplink peak data to the RAN. The two DRBs start to be sent from the initial use time of the second DRB, and the maximum duration of each transmission does not exceed the use time of the second DRB.

Optionally, the information of the second DRB further includes one or more of time domain resources, frequency domain resources, modulation and coding scheme, antenna port, listening reference signal resource indication, and demodulation reference signal. Thus, the second UE may determine a specific manner of sending uplink peak data based on one or more of time domain resources, frequency domain resources, modulation and coding scheme, antenna port, listening reference signal resource indication, and demodulation reference signal.

The sequence of the above steps 404 and 405 is not limited.

It should be noted that the sum of the data volume of the uplink peak data received from the first UE in the first time period by the RAN and the data volume of the uplink peak data received from the second UE in the first time period does not exceed Data volume threshold. If multiple UEs are involved and need to send uplink peak data to the RAN at the same time, the sum of the data volumes of the uplink peak data received by the RAN from the multiple UEs within the first time period does not exceed the data volume threshold. The data volume threshold is determined by the data processing capability of the RAN, that is, the data volume threshold is related to the data processing capability of the RAN.

Based on the above solution, the RAN can configure different uplink resource scheduling policies for different UEs, so that different UEs send uplink peak data to the RAN in different time periods, thereby helping to reduce the amount of uplink peak data sent by multiple UEs in the same time period , thereby reducing the pressure on the RAN to process data, improving the UE transmission quality and ensuring the stability of the access network equipment status.

As an example, the embodiment shown in FIG. 4 will be described below with reference to the specific embodiments shown in FIG. 5 to FIG. 7 .

As shown in FIG. 5 , it is a schematic diagram of another communication method provided by the embodiment of the application. The method provides the configuration process of the service data flow information. Specifically, the AF provides the service data flow information to the network through the NEF. The service data flow information includes at least one of an application identifier, service data flow identification information, service data flow feature information, or service data flow QoS requirements. For details, refer to the foregoing description.

The method includes the following steps:

Step 501, the AF sends a first request to the NEF. Accordingly, the NEF may receive the first request.

The first request carries the newly added service data flow information or the updated service data flow information.

Optionally, the first request further carries a UE identifier (UE ID) or a group identifier (Group ID). Wherein, when the first request carries the UE identifier, it indicates that the service data flow information carried in the first request is related information of the service data flow of the UE. When the first request carries the group identifier, it indicates that the service data flow information carried in the first request is related information of the service data flows of all UEs corresponding to the group identifier.

In one implementation method, when the AF is ready to add new service data flow information, the AF sends a first request to the NEF. The first request may be a service data flow creation request, for example, it may be PFDManagement_Create Request, a service data flow creation request Carry the newly added service data flow information.

In another implementation method, when the AF is ready to update the existing service data flow information, the AF sends a first request to the NEF, and the first request may be a service data flow update request, such as a PFDManagement_Update Request, the service data flow The update request carries the updated service data flow information.

Step 502, the NEF updates the service data flow information stored on the NEF.

For example, the NEF first determines whether to allow the first request, and if so, updates the service data flow information stored on the NEF. For example, if the first request carries the newly added service data flow information, the NEF updates the service data flow information stored on the NEF according to the newly added service data flow information. For another example, if the first request carries updated service data flow information, the NEF updates the service data flow information stored on the NEF according to the updated service data flow information.

It should be noted that, if the first request also carries the UE ID or Group ID, when the NEF saves the service data flow information, it also saves the mapping relationship between the service data flow information and the UE ID or Group ID.

Step 503, the NEF sends a first response to the AF. Accordingly, the AF can receive the first response.

The first response is used to notify the AF that the request processing is successful.

Of course, if in the above step 502, the NEF determines that the first request is not allowed, or the NEF fails to update the service data flow information, the first response is used to notify the AF that the request processing fails.

Specifically, the first response may be a service data flow creation response, or a business data flow update response.

Step 504, the NEF sends a second request to the UDR. Accordingly, the UDR may receive the second request.

Wherein, the second request carries the newly added service data flow information or the updated service data flow information.

Optionally, the first request further carries a UE identifier (UE ID) or a group identifier (Group ID).

In one implementation method, when the NEF is ready to add new service data flow information, the NEF sends a second request to the UDR, the second request may be a data management creation request (DM_Create Request), and the data management creation request carries the newly added service Data flow information.

In another implementation method, when the NEF is ready to update the existing service data flow information, the NEF sends a second request to the UDR, the second request may be a data management update request (DM_Update Request), and the data management update request carries the updated Business data flow information.

Step 505, the UDR updates the service data flow information stored in the UDR.

For example, if the second request carries the newly added service data flow information, the UDR updates the service data flow information stored in the UDR according to the newly added service data flow information. For another example, if the second request carries updated service data flow information, the UDR updates the service data flow information stored in the UDR according to the updated service data flow information.

It should be noted that, if the second request also carries the UE ID or the Group ID, when the UDR saves the service data flow information, it also saves the mapping relationship between the service data flow information and the UE ID or the Group ID.

Step 506, the UDR sends a second response to the NEF. Accordingly, the NEF may receive the second response.

The second response is used to notify the NEF that the request processing is successful.

Of course, if in the above step 505, the UDR fails to update the service data flow information, the second response is used to notify the NEF that the request processing fails.

The second response may specifically be a data management create response (DM_Create Response) or a data management update response (DM_Update Response).

Step 507, the SMF determines that it needs to acquire service data flow information.

For example, a timer is set on the SMF, and the SMF is triggered to obtain service data flow information every time the set time period expires.

The SMF determines that it needs to acquire service data flow information, which may be to determine that it needs to acquire newly added service data flow information, or to determine that it needs to acquire updated service data flow information.

Step 508, the SMF sends a third request to the NEF. Accordingly, the NEF can receive the third request.

The third request is used to request to obtain service data flow information.

For example, the third request may be PFDManagement_Fetch Request.

Step 509, the NEF sends a third response to the SMF. Accordingly, the SMF can receive the third response.

The third response carries the newly added service data flow information or the updated service data flow information.

For example, the third response may be PFDManagement_Fetch Response.

After receiving the newly added service data flow information or the updated service data flow information, the SMF saves the newly added service data flow information or the updated service data flow information on the SMF.

It should be noted that if the third response also carries the UE ID or Group ID, when the SMF saves the service data flow information, it also saves the mapping relationship between the service data flow information and the UE ID or Group ID.

In the above steps 507 to 509, the SMF actively requests the NEF to obtain the service data flow information. As another implementation method, the NEF may also receive the newly added service data flow information or the updated service data flow information after the NEF receives the information. , and actively report the newly added service data flow information or the updated service data flow information to the SMF. Alternatively, as another implementation method, the SMF may actively request the UDR to obtain the service data flow information.

Step 510, the SMF sends a fourth request to the UPF. Accordingly, the UPF may receive the fourth request.

Wherein, the fourth request carries the identification information of the newly added service data flow, or the identification information of the updated service data flow.

For example, the fourth request may be a PFDManagement Request.

The UPF can perform data flow detection according to the identification information of the newly added service data flow or the identification information of the updated service data flow, and identify the new service data flow.

Step 511, the UPF sends a fourth response to the SMF. Accordingly, the SMF can receive the fourth response.

This step is optional.

In the above embodiment, the newly added service data flow information or the updated service data flow information is provided by the AF, and updated to the NEF, UDR and SMF in the network. In a specific implementation, it may only be updated to one or more network elements in the NEF, UDR, and SMF in the network, or may also be updated to other network elements in the network, such as AMF, PCF, and so on. And, the identification information of the service data flow in the service data flow information is also updated to the UPF, so that the UPF can start to detect a new service data flow. And, the service data flow information of a certain UE or a certain group may also be provided to the network.

Based on the above embodiment, the network can acquire and configure the specified service data flow information, so that the corresponding service data flow can be detected, and subsequently the data flow can be transmitted based on the service data flow information. However, the prior art does not support providing the service data flow feature information in the service data flow information to the network.

As shown in FIG. 6 , it is a schematic diagram of another communication method provided by the embodiment of the application. The method provides the configuration process of the characteristic information of the business data flow.

The method includes the following steps:

Step 601, the UE establishes a service data flow connection of the application with the AF.

The UE and the AF establish an application service data flow connection, for example, an application in the UE may establish an application layer service data flow connection with an application in the AF.

Wherein, the IP triplet or URL of the service data flow is consistent with the IP triplet or URL in the service data flow information provided by the AF to the network in advance. For example, if the AF provides service data flow information to the network according to the method in the embodiment of FIG. 5 , the IP triplet or URL of the service data flow in step 601 is the same as the IP triplet in the service data flow information in the embodiment of FIG. 5 . Groups or URLs remain the same.

Step 602, the UPF performs packet detection according to the configured packet detection rules, and when detecting a service data flow corresponding to a specified service, sends an event report to the PCF, and the event report carries the detected packet data flow description (Packet Flow Description, PFD) logo.

For example, if the service data flow information corresponding to the service is pre-configured on the UPF (for example, configured by step 510 in the embodiment of FIG. 5 ), the UPF can use the IP triplet or URL in the service data flow information as the packet detection rule parameters to perform packet inspection.

As another implementation method, the UPF can also send the event report to the SMF, and then the SMF sends the event report to the PCF.

Step 603, the PCF sends a Policy and Charging Control (PCC) rule to the SMF. Accordingly, the SMF can receive the PCC rules.

The PCF can first obtain service data flow information from network elements such as UDR or SMF, and then generate PCC rules according to the service data flow information. When the service is transmitted by multiple data streams, the PCF provides to generate a PCC rule for each service data stream, and then the PCF sends the PCC rule to the SMF. Each PCC rule includes an identification of the application, identification information of the service data flow, characteristic information of the service data flow, and QoS information of the service data flow. The QoS information of the service data flow is obtained according to the QoS requirement of the service data flow. The QoS information of the service data flow includes a QoS flow identity (QoS Flow Identity, QFI) and a QCI corresponding to each time slice in a time period in the characteristic information of the service data flow.

Optionally, the QoS information of the service data flow further includes configuration parameters corresponding to each QCI, and the configuration parameters include one or more of bit rate, packet loss rate, packet delay budget, and priority. For example, when the QCI is defined by the standard, the QoS information of the service data flow may not need to carry the configuration parameters corresponding to the QCI. When the QCI is customized, the QoS information of the service data flow may carry the configuration parameters corresponding to the QCI.

As an implementation method, in this step, the PCF may send the SMF initiated SM_Policy Association Modefication Request to the SMF, which carries the PCC rule.

Step 604, the SMF sends configuration information of at least one service data flow to the UPF. Accordingly, the UPF may receive configuration information of at least one service data flow.

Each service data flow corresponds to a piece of configuration information, and the configuration information includes the identification of the application, the identification information of the service data flow, the feature information of the service data flow, and the QoS information of the service data flow.

The SMF can send the configuration information of multiple service data streams to the UPF through N4 messages (such as N4 PDU Establishment Modification Request, or N4 PDU Session Modification Request).

The specific implementation method for the UPF to identify the service data flow or control the service data flow according to the characteristic information of the service data flow may refer to the relevant description of the embodiment in FIG.

Step 605, the SMF sends the configuration information of at least one service data flow to the RAN through the AMF. Correspondingly, the RAN may receive configuration information of at least one service data flow.

Each service data flow corresponds to a piece of configuration information, and the configuration information includes the identification of the application, the identification information of the service data flow, the feature information of the service data flow, and the QoS information of the service data flow. Optionally, the configuration information also carries a UE identity or a group identity.

Based on the above embodiment, after the application in the UE establishes the service data flow connection of the application with the AF, the configuration information of the service data flow can be sent to the RAN and the UPF, and the RAN and the UPF can schedule and transmit the service data flow according to the configuration information. control, so as to improve the transmission efficiency of business data flow.

As shown in FIG. 7 , it is a schematic diagram of another communication method provided by the embodiment of the application. The method provides a configuration process of service data flow information. Specifically, the UE provides the service data flow information to the network during the establishment of a protocol data unit (protocol data unit, PDU) session. The service data flow information includes at least one of an application identifier, service data flow identification information, service data flow feature information, or service data flow QoS requirements. For details, refer to the foregoing description.

The method includes the following steps:

Step 701, the UE sends a PDU session establishment request to the AMF. Accordingly, the AMF receives the PDU session establishment request.

The PDU session establishment request carries service data flow information. The PDU session establishment request may be, for example, a PDU Session Modification Request.

Step 702, the AMF sends a PDU session context update request to the SMF. Accordingly, the SMF receives the PDU session context update request.

The PDU session context update request carries service data flow information. The PDU session context update request may be, for example, Nsmf_PDUSession_UpdateSMContext Request.

Step 703, the SMF sends a session management policy modification request to the PCF. Accordingly, the PCF receives the session management policy modification request.

The session management policy modification request carries service data flow information.

As an example, the session management policy modification request may be an SMF initiated SM Policy Association Modification Request.

After receiving the service data flow information, the PCF generates PCC rules according to the service data flow information. When the service is transmitted by multiple data streams, the PCF provides to generate a PCC rule for each service data stream, and then the PCF sends the PCC rule to the SMF. For the content included in the PCC rule, reference may be made to the relevant description of the foregoing step 603, which will not be repeated here.

Step 704, the PCF sends the PCC rule to the SMF. Accordingly, the SMF receives the PCC rule.

Step 705, the SMF sends an N4 PDU session establishment/modification request to the UPF. Accordingly, the UPF receives the N4 PDU session establishment/modification request.

The N4 PDU session establishment/modification request carries the feature information of the service data flow and the QoS information of the service data flow.

Step 706, the UPF sends an N4 PDU session establishment/modification response to the SMF. Accordingly, the SMF receives the N4 PDU session establishment/modification response.

This step is optional.

Step 707, the SMF sends a PDU session context update response to the AMF. Accordingly, the AMF receives the PDU Session Context Update Response.

The PDU session context update response carries characteristic information of the service data flow and QoS information of the service data flow.

The PDU session context update response may be, for example, Nsmf_PDUSession_UpdateSMContext Response.

Step 708, the AMF sends an N2 message to the RAN. Accordingly, the RAN receives the N2 message.

The N2 message carries characteristic information of the service data flow and QoS information of the service data flow.

After step 708, the newly created data flow (Data Flow) is configured through a radio resource control (Radio Resource Control, RRC) connection configuration process between the RAN and the UE, and the SMF confirms from the RAN that the QoS Flow has been configured, and, The SMF notifies the UPF to activate the QoS Flow, etc.

In the above embodiment, the service data flow information is provided by the UE and updated to the RAN, SMF and PCF in the network.

As shown in FIG. 8 , it is a schematic diagram of another communication method provided by the embodiment of the application. The method provides a method for the RAN to configure the uplink resource scheduling policy for the UE. The SMF obtains feature information of the service data flow and QoS information of the service data flow according to the embodiment shown in FIG. 6 or FIG. 7 . Based on this method, the RAN can perform hash scheduling on the uplink traffic of multiple UEs to prevent multiple UEs from sending peak data at the same time.

In the following, two UEs (specifically, cameras) send uplink service data streams to the RAN as an example for description, and the characteristics of the uplink service data streams of each UE are shown in FIG. 3( a ).

The method includes the following steps:

Step 801, the RAN sends the uplink resource scheduling policy to the UE. Correspondingly, the UE receives the uplink resource scheduling policy.

For example, the RAN may send the uplink resource scheduling policy to the UE through an RRC configuration message.

The uplink resource scheduling policy includes at least one DRB information, and each DRB information includes one or more of DRB configuration information, DRB type, DRB usage start time, DRB usage duration or DRB usage period.

The DRB configuration information includes time domain resources, frequency domain resources, modulation and coding scheme (Modulation and Coding Scheme, MCS), antenna ports, sounding reference signal (Sounding Reference Signal, SRS) resource indication, demodulation reference signal (Demodulation Reference) Signal, DMRS) one or more. The DRB type is used to indicate the QCI corresponding to the DRB. For example, DRB type 1 corresponds to QCI 1, and DRB type 2 corresponds to QCI 2. The QoS control policies corresponding to different QCIs are different. For example, the QoS control policies corresponding to QCI 1 are: the rate is 60MB/s, the reliability requirement is 99.9%, and the QoS control policies corresponding to QCI 2 are: the rate is 8MB/s, packet loss rate of 1%. The DRB usage start time indicates the start time point of using the DRB, and the DRB usage duration indicates the maximum duration of occupying the DRB at one time. The DRB usage duration may also be referred to as the DRB allocation duration. The DRB usage period represents a time interval between two adjacent uses of the DRB, and the DRB usage period may also be referred to as a DRB scheduling period.

As shown in FIG. 9 , it is a schematic diagram of configuring an uplink resource scheduling policy. Among them, DRB 1 and DRB 2 are configured for UE 1. DRB 1 is used for data transmission (specifically, uplink peak data) of the service data stream of QCI 1, and the configured parameters such as time domain resources, frequency domain resources, modulation and coding scheme, antenna port, SRS resource indication, and DMRS are used to support QCI 1 The required quality of network transmission service, the use duration of DRB 1 is 16.7ms, the use period of DRB 1 is 1s, and the use start time of DRB 1 is T1. DRB 2 is used for data transmission (specifically, uplink common data) of the service data stream of QCI 2, and the configured time domain resources, frequency domain resources, modulation and coding scheme, antenna port, SRS resource indication, DMRS and other parameters are used to support QCI 2 The required quality of network transmission service, the use duration of DRB 2 is 16.7ms, the use period of DRB 2 is 1s, and the use start time of DRB 2 is T2.

DRB 3 and DRB 4 are configured for UE 2. DRB 3 is used for data transmission (specifically, uplink peak data) of the service data stream of QCI 3, and the configured time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, SRS resource indication, DMRS and other parameters are used to support QCI 3 The required quality of network transmission service, the use time of DRB 3 is 16.7ms, the use period is 1s, and the use start time is T3. DRB 4 is used for data transmission of the service data stream of QCI 4 (specifically, uplink ordinary data), and the configured time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, SRS resource indication, DMRS and other parameters are used to support QCI 4 The required quality of network transmission service, the use time of DRB 4 is 16.7ms, the use period is 1s, and the use start time is T4.

The use start time T1 of DRB 1 and the use start time T2 of DRB 3 need to be staggered. As an example, T2-T1 is greater than or equal to 16.7ms. Exemplarily, DRB 1 is used by UE 1 at 1 ms, and DRB 3 is used by UE 2 at 18 ms. The RAN can configure two definite starting time points for UE1 and UE2, and UE1 and UE2 use corresponding DRBs to transmit uplink peak data according to the starting time points.

Optionally, the frequency domain resources occupied by the DRB 1 configured by the RAN for the UE 1 are the same as the frequency domain resources occupied by the DRB 3 configured for the UE 2, that is, different UEs can reuse the frequency domain resources. Based on the implementation method, the frequency domain resources of the DRB can be shared and used before multiple UEs, and resources can be saved.

The above is the start time of using the DRB carried by the uplink resource scheduling policy. As another implementation method, the time when the UE receives the uplink resource scheduling policy sent by the RAN may also be used as the start time of using the DRB. For example, when UE 1 receives the uplink resource scheduling policy at time T1, it is determined that the use start time of DRB 1 is T1, and the use start time of DRB 2 is determined to be T1+16.7ms. When UE 2 receives the uplink resource scheduling policy at time T2, it determines that the start time of use of DRB 3 is T2, and the start time of use of DRB 2 is determined to be T2+16.7ms. And, T2-T1 is greater than or equal to 16.7ms.

As an implementation method, the uplink resource scheduling policy is determined by the RAN according to the received information of the UE, wherein the information of the UE includes the identification information of the UE, the feature information of the service data flow of the UE, and the QoS information of the service data flow. Specifically, the RAN determines the initial usage time, usage duration, and usage period of the DRB according to the characteristic information of the service data flow of the UE, and determines the type of the DRB according to the QoS information of the service data flow of the UE.

Exemplarily, taking the UE 1 of FIG. 9 as an example, the information of the UE 1 received by the RAN includes: the identifier of the UE 1, the feature information of the service data flow of the UE 1, and the QoS information of the service data flow, wherein the UE 1's The characteristic information of the service data stream includes: the time period is 1 second, the time slice is 60, the bit rate corresponding to time slice 1 is V1, the bit rate corresponding to time slice 2-60 is V2, and V1 is greater than V2 . The QoS information of the service data flow includes: QFI, time slice 1 corresponds to QCI 83, and time slices 2-60 correspond to QCI 87, wherein the level of QCI 83 is higher than that of QCI 87. Based on the received information of UE 1, the RAN determines the uplink resource scheduling policy of UE 1, which specifically includes the information of DRB 1 and the information of DRB 2. Among them, the information of DRB 1 includes: the type of DRB 1 is type 1 (this type 1 corresponds to QCI 83), the use start time of DRB 1 is T1, the use time is 16.7ms, and the use period is 1s. The information of DRB 2 includes: the type of DRB 2 is type 2 (this type 2 corresponds to QCI 87), the use start time of DRB 2 is T2, the use time is 983.3ms, and the use period is 1s. Subsequently, after UE 1 receives the uplink resource scheduling policy of UE 1, it can determine to use DRB 1 to send the uplink peak data of UE 1 in time slice 1, and use DRB 2 to send the uplink normal data of UE 1 in time slice 2-60.

For other UEs, such as UE 2, UE 3, etc., a similar method can be used to configure uplink resource scheduling policies for these UEs. For example, referring to FIG. 9, the uplink resource scheduling resources configured for UE 2 include the information of DRB 3 and the information of DRB 4. , and DRB 3 is used to send the uplink peak data of UE 2, and DRB 4 is used to send the uplink normal data of UE 3. In addition, the DRBs used by different UEs for transmitting uplink peak data are staggered from each other. For example, referring to FIG. 9 , the time periods when UE 1 and UE 2 send uplink peak data are staggered, so that the sum of the data volume of uplink peak data received by the RAN in the same time period does not exceed the preset data volume threshold. Avoid the impact of heavy traffic on the RAN and cause insufficient RAN processing capacity.

Step 802, the UE performs video capture and encoding.

After receiving the uplink resource scheduling policy, the UE determines the time point and time period at which uplink data transmission can be performed through DRB 1 and DRB 2, and then the UE can adjust its corresponding video capture and video encoding. For example, UE 1 collects video data in the transmission time window corresponding to DRB 1 and encodes the video data into I frames, and collects video data in the transmission time window corresponding to DRB 2 and encodes the video data into P frames.

Step 803, the UE sends uplink data to the RAN through the DRB. Correspondingly, the RAN receives the uplink data.

For example, UE 1 sends I frame data to the RAN within the transmission time window corresponding to DRB 1, and sends P frame data to the RAN within the transmission time window corresponding to DRB 2. UE 2 sends I frame data to RAN within the transmission time window corresponding to DRB 3, and sends P frame data to RAN within the transmission time window corresponding to DRB 4.

In this way, different UEs can be made to stagger the time of sending the I-frame data, so the overlapping possibility of the peak data can be staggered.

Based on the above solution, the RAN performs uplink data scheduling according to the characteristics of the uplink service data flow of the UE, so as to avoid the simultaneous transmission of peak data in the uplink transmission of multiple UEs, which may exceed the transmission capacity of the network, thereby ensuring the reliability of data transmission and the stability of the network status. stability.

The foregoing mainly introduces the solution provided by the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above-mentioned functions, each network element in the above-mentioned implementation includes corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should easily realize that the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

It can be understood that, in the above method embodiments, the steps or operations corresponding to the first policy control network element may also be implemented by components (such as chips or circuits) configured in the first policy control network element, and corresponding to the steps or operations implemented by the first policy control network element. The steps or operations implemented by the two-policy control network element may also be implemented by components (such as chips or circuits) configured in the second policy control network element, and corresponding to the steps or operations implemented by the binding support network element, they may also be implemented by The components (such as chips or circuits) that support the network element binding are implemented, and the steps or operations corresponding to the steps or operations implemented by the application function network elements may also be implemented by components (such as chips or circuits) configured in the application function network elements.

Referring to FIG. 10 , it is a schematic diagram of a communication apparatus according to an embodiment of the present application. The apparatus is used to implement each step performed by the corresponding access network device in the foregoing embodiment. As shown in FIG. 10 , the apparatus 1000 includes a transceiver unit 1010 and a processing unit 1020 .

The processing unit 1020 is configured to determine a first uplink resource scheduling policy of the first terminal device and a second uplink resource scheduling policy of the second terminal device, where the first uplink resource scheduling policy includes information of the first data radio bearer DRB, so The first DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes information of the second DRB, and the second DRB is used to carry the uplink peak value of the second terminal device data, the usage time periods of the first DRB and the second DRB do not completely overlap; the transceiver unit 1010 is configured to send the first uplink resource scheduling policy to the first terminal device, and send the first uplink resource scheduling policy to the second DRB. The terminal device sends the second uplink resource scheduling policy.

In a possible implementation method, the transceiver unit 1010 is further configured to receive the uplink peak data from the first terminal device and the uplink peak data from the second terminal device within the first time period, so The uplink peak data of the first terminal device is carried in the first DRB, the uplink peak data of the second terminal device is carried in the second DRB, and the data volume of the uplink peak data of the first terminal device is the same as that of the first terminal device. The sum of the data volume of the uplink peak data of the second terminal device does not exceed the data volume threshold.

In a possible implementation method, the processing unit 1020 is specifically configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, and determine the first uplink resource scheduling policy according to the information of the second terminal device The second uplink resource scheduling strategy.

In a possible implementation method, the transceiver unit 1010 is further configured to receive the information of the first terminal device and the information of the second terminal device from the session management network element, the information of the first terminal device Contains the identification information of the first terminal device, the feature information of the service data flow of the first terminal device, and the first quality of service QoS information of the service data flow of the first terminal device. The characteristic information of the service data flow is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the first terminal device in a time period, and the first QoS information is used to indicate the different time slices. the corresponding QoS level identifiers QCI, the information of the second terminal device includes the identification information of the second terminal device, the feature information of the service data flow of the second terminal device, and the service of the second terminal device. The second QoS information of the data flow, the characteristic information of the service data flow of the second terminal device is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the second terminal device in a time period , and the second QoS information is used to indicate the respective QCIs corresponding to the different time slices.

In a possible implementation method, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB; The processing unit 1020 is configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, and specifically includes: determining the type of the first DRB according to the first QoS information.

In a possible implementation method, the information of the second DRB includes the type of the second DRB, and the type of the second DRB is used to indicate the traffic characteristics of the service data flow carried by the second DRB; The processing unit 1020 is configured to determine the second uplink resource scheduling policy according to the information of the second terminal device, specifically including: determining the type of the second DRB according to the second QoS information.

In a possible implementation method, the information of the first DRB includes the initial usage time of the first DRB and the usage duration of the first DRB, the initial usage time of the first DRB and the The usage duration of the first DRB is used for the first terminal device to determine the time to send the uplink peak data; the processing unit 1020 is configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, specifically The method includes: determining the initial usage time of the first DRB and the usage duration of the first DRB according to the characteristic information of the service data flow of the first terminal device.

In a possible implementation method, the information of the second DRB includes an initial usage time of the second DRB and a usage duration of the second DRB, and the initial usage time of the second DRB and the The use duration of the second DRB is used for the second terminal device to determine the time to send the uplink peak data; the processing unit 1020 is configured to determine the second uplink resource scheduling policy according to the information of the second terminal device, specifically The method includes: determining the type of the second DRB according to the second QoS information.

Optionally, the above-mentioned communication apparatus 1000 may further include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or Features. For example, the processing unit 1020 may read data or instructions in the storage unit, so that the communication apparatus implements the methods in the above embodiments.

It should be understood that the division of units in the above apparatus is only a division of logical functions, and in actual implementation, it may be fully or partially integrated into one physical entity, or may be physically separated. And all the units in the device can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware. For example, each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing. Features. In addition, all or part of these units can be integrated together, and can also be implemented independently. The processing element described here can also become a processor, which can be an integrated circuit with signal processing capability. In the implementation process, each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.

In one example, a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above method, such as: one or more Application Specific Integrated Circuits (ASICs), or, one or more Multiple microprocessors (digital singnal processors, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), or a combination of at least two of these integrated circuit forms. For another example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can invoke programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above transceiver unit 1010 is an interface circuit of the device, and is used to send signals to or receive signals from other devices. For example, when the device is implemented in the form of a chip, the transceiver unit 1010 is an interface circuit used by the chip to send signals to or receive signals from other chips or devices.

Referring to FIG. 11 , it is a schematic diagram of a communication apparatus according to an embodiment of the present application. The apparatus is used to implement each step performed by the corresponding terminal device in the above embodiment. As shown in FIG. 11 , the apparatus 1100 includes a sending unit 1110 , a receiving unit 1120 and a processing unit 1130 .

A receiving unit 1120, configured to receive a first uplink resource scheduling policy from an access network device, where the first uplink resource scheduling policy includes information of at least one DRB, and the information of the at least one DRB includes information of the first DRB, so The first DRB is used to carry the uplink peak data of the first terminal device; the sending unit 1110 is configured to send the first DRB to the access network device on the first DRB according to the first uplink resource scheduling policy Upstream peak data of a terminal device.

In a possible implementation method, the processing unit 1130 is configured to determine the first DRB according to the first uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the first terminal device; the sending unit 1110, which is specifically configured to send the uplink peak data of the first terminal device to the access network device on the first DRB.

In a possible implementation method, the information of the first DRB includes the type of the first DRB, and the type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB; The processing unit 1130 is specifically configured to determine the DRB type corresponding to the uplink peak data of the first terminal device according to the traffic characteristics of the uplink peak data of the first terminal device; determine the first terminal device corresponding to the DRB type. a DRB.

In a possible implementation method, the information of the first DRB includes the initial usage time of the first DRB and the usage duration of the first DRB; the sending unit 1110 is specifically configured to The initial usage time of a DRB and the usage duration of the first DRB, and the uplink peak data of the first terminal device is sent to the access network device on the first DRB.

Optionally, the above-mentioned communication device 1100 may further include a storage unit, which is used to store data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or be coupled with the storage unit to implement corresponding methods or Features. For example, the processing unit 1130 may read data or instructions in the storage unit, so that the communication apparatus implements the methods in the above embodiments.

In one example, a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or, one or more DSPs, or, one or more FPGA, or a combination of at least two of these integrated circuit forms. For another example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a CPU or other processors that can invoke programs. For another example, these units can be integrated together and implemented in the form of SOC.

The above sending unit 1110 is an interface circuit of the device, and is used to send signals to other devices. For example, when the device is implemented in the form of a chip, the sending unit 1110 is an interface circuit used by the chip to send signals to other chips or devices.

The above receiving unit 1120 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the receiving unit 1120 is an interface circuit used by the chip to receive signals from other chips or devices.

Referring to FIG. 12 , a schematic diagram of a communication apparatus provided in an embodiment of the present application is used to implement the operations of the access network device or the terminal device in the above embodiment. As shown in FIG. 12 , the communication apparatus includes: a processor 1210 and an interface 1230 , and optionally, the communication apparatus further includes a memory 1220 . The interface 1230 is used to enable communication with other devices.

The method performed by the access network device or terminal device in the above embodiments can be implemented by the processor 1210 calling a program stored in a memory (which may be the memory 1220 in the access network device or the terminal device, or an external memory). That is, the access network device or the terminal device may include a processor 1210, and the processor 1210 executes the method performed by the access network device or the terminal device in the above method embodiments by invoking the program in the memory. The processor here may be an integrated circuit with signal processing capability, such as a CPU. An access network device or terminal device may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.

Specifically, the functions/implementation process of the transceiver unit 1010 and the processing unit 1020 in FIG. 10 may be implemented by the processor 1210 in the communication apparatus 1200 shown in FIG. 12 calling computer executable instructions stored in the memory 1220 . Alternatively, the function/implementation process of the processing unit 1020 in FIG. 10 may be implemented by the processor 1210 in the communication device 1200 shown in FIG. 12 calling the computer-executed instructions stored in the memory 1220, and the transceiver unit 1010 in FIG. 10 The function/implementation process of the can be implemented through the interface 1230 in the communication device 1200 shown in FIG. 12 .

Specifically, the functions/implementation process of the sending unit 1110, the receiving unit 1120 and the processing unit 1130 in FIG. 11 can be implemented by the processor 1210 in the communication apparatus 1200 shown in FIG. 12 calling the computer-executable instructions stored in the memory 1220 . Alternatively, the function/implementation process of the processing unit 1130 in FIG. 11 can be implemented by the processor 1210 in the communication device 1200 shown in FIG. 12 calling the computer-executed instructions stored in the memory 1220, the sending unit 1110 in FIG. 11 and the receiving unit 1110 in FIG. The function/implementation process of the unit 1120 may be implemented through the interface 1230 in the communication device 1200 shown in FIG. 12 .

Those of ordinary skill in the art can understand that the first, second, third, fourth and other numeral numbers involved in this application are only for the convenience of description, and are not used to limit the scope of the embodiments of the application, but also represent Sequentially. "And/or", which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one" means one or more. At least two means two or more. "At least one", "any one", or similar expressions, refers to any combination of these items, including any combination of single item(s) or plural item(s). For example, at least one item (single, species) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple. "Plurality" means two or more, and other quantifiers are similar.

It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present invention. implementation constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

The various illustrative logic units and circuits described in the embodiments of this application may be implemented by general purpose processors, digital signal processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions. A general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.

The steps of the method or algorithm described in the embodiments of this application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two. Software units can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or this. In any other form of storage media in the field. Illustratively, a storage medium may be coupled to the processor such that the processor may read information from, and store information in, the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium may be provided in the ASIC.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In one or more exemplary designs, the above-described functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on, or transmitted over, a computer-readable medium in the form of one or more instructions or code. Computer-readable media includes computer storage media and communication media that facilitate the transfer of a computer program from one place to another. Storage media can be any available media that a general-purpose or special-purpose computer can access. For example, such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other media in the form of program code that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. In addition, any connection is properly defined as a computer-readable medium, for example, if software is transmitted from a website site, server or other remote source over a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless, and microwave are also included in the definition of computer-readable media. The discs and magnetic discs include compact discs, laser discs, optical discs, digital versatile discs (English: Digital Versatile Disc, DVD for short), floppy discs and Blu-ray discs. Disks usually reproduce data magnetically, while Discs usually use lasers to optically reproduce data. Combinations of the above can also be included in computer readable media.

Those skilled in the art should appreciate that, in one or more of the above examples, the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

The specific embodiments described above further describe the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above descriptions are only specific embodiments of the present application, and are not intended to limit the The protection scope, any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application shall be included within the protection scope of the present application. The above description of the specification of this application can enable any skilled in the art to utilize or realize the content of this application, and any modifications based on the disclosed content should be considered obvious in the art, and the basic principles described in this application can be applied to other modifications without departing from the spirit and scope of the invention of the present application. Thus, the present disclosure is not intended to be limited only to the embodiments and designs described, but can be extended to the fullest extent consistent with the principles of this application and the novel features disclosed.

Although the application has been described in conjunction with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made therein without departing from the spirit and scope of the application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of this application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

A communication method, comprising:

The access network device determines a first uplink resource scheduling policy of the first terminal device and a second uplink resource scheduling policy of the second terminal device, where the first uplink resource scheduling policy includes information about the first data radio bearer DRB, and the first uplink resource scheduling policy A DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes information of the second DRB, and the second DRB is used to carry the uplink peak data of the second terminal device, The usage time periods of the first DRB and the second DRB do not completely overlap;

The access network device sends the first uplink resource scheduling policy to the first terminal device, and sends the second uplink resource scheduling policy to the second terminal device.
The method of claim 1, further comprising:

The access network device receives the uplink peak data from the first terminal device and the uplink peak data from the second terminal device within the first time period, and the uplink peak data of the first terminal device is carried in the The first DRB, the uplink peak data of the second terminal device is carried in the second DRB, the data volume of the uplink peak data of the first terminal device and the data volume of the uplink peak data of the second terminal device The sum does not exceed the data volume threshold.
The method according to claim 1 or 2, characterized in that,

The access network device determines the first uplink resource scheduling policy of the first terminal device and the second uplink resource scheduling policy of the second terminal device, including:

The access network device determines the first uplink resource scheduling policy according to the information of the first terminal device, and determines the second uplink resource scheduling policy according to the information of the second terminal device.
The method of claim 3, further comprising:

The access network device receives the information of the first terminal device and the information of the second terminal device from the session management network element, where the information of the first terminal device includes the identification information of the first terminal device, the feature information of the service data flow of the first terminal device and first quality of service QoS information of the service data flow of the first terminal device, and the feature information of the service data flow of the first terminal device is used to indicate the first Traffic characteristic information corresponding to different time slices of a service data flow of a terminal device in a time period, the first QoS information is used to indicate the QoS level identifiers QCI corresponding to the different time slices respectively, the first QoS information The information of the second terminal equipment includes the identification information of the second terminal equipment, the characteristic information of the service data flow of the second terminal equipment, and the second QoS information of the service data flow of the second terminal equipment. The characteristic information of the service data flow of the terminal device is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the second terminal device in a time period, and the second QoS information is used to indicate the QCIs corresponding to different time slices.
The method according to claim 4, wherein the information of the first DRB includes the type of the first DRB, the initial usage time of the first DRB and the usage duration of the first DRB, and the The type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB, and the initial usage time of the first DRB and the usage duration of the first DRB are used for the first terminal device Determine the time to send uplink peak data;

The access network device determines the first uplink resource scheduling policy according to the information of the first terminal device, including:

The access network device determines the type of the first DRB according to the first QoS information;

The access network device determines, according to the feature information of the service data flow of the first terminal device, the initial usage time of the first DRB and the usage duration of the first DRB;

The information of the second DRB includes the type of the second DRB, the initial use time of the second DRB, and the use time of the second DRB, and the type of the second DRB is used to indicate the second DRB. The traffic characteristics of the service data flow carried by the DRB, the initial usage time of the second DRB and the usage duration of the second DRB are used for the second terminal device to determine the time to send the uplink peak data;

The access network device determines the second uplink resource scheduling policy according to the information of the second terminal device, including:

The access network device determines the type of the second DRB according to the second QoS information;

The access network device determines an initial use time of the second DRB and a use time of the second DRB according to the characteristic information of the service data flow of the second terminal device.
The method according to claim 4 or 5, wherein the characteristic information of the service data flow of the first terminal device comprises a first time period, at least two time slices corresponding to the first time period and all The bit rates corresponding to the at least two time slices respectively, the first QoS information includes the QFI and the QCIs corresponding to the at least two time slices respectively, and the QCIs corresponding to the at least two time slices are not exactly the same , the service data flow of the first terminal device is mapped to the QoS flow corresponding to the QFI;

The feature information of the service data stream of the second terminal device includes a second time period, at least two time slices corresponding to the second time period, and bit rates corresponding to the at least two time slices respectively, and the The second QoS information includes the QFI and the QCIs corresponding to the at least two time slices, the QCIs corresponding to the at least two time slices are not exactly the same, and the service data flow of the second terminal device is mapped to the The QoS flow corresponding to the QFI.
The method according to any one of claims 1-6, wherein the information of the first DRB includes configuration information of the first DRB, and the configuration information of the first DRB includes time domain resources and frequency domain resources , one or more of modulation and coding scheme, antenna port, listening reference signal resource indication, and demodulation reference signal;

The information of the second DRB includes configuration information of the second DRB, and the configuration information of the second DRB includes time domain resources, frequency domain resources, modulation and coding schemes, antenna ports, listening reference signal resource indication, demodulation one or more of the reference signals.
The method according to any one of claims 1-7, wherein the uplink peak data of the first terminal device carried by the first DRB includes I-frame data, and the second DRB carried by the second DRB The uplink peak data of the terminal equipment includes I frame data.
The method according to any one of claims 1 to 8, wherein the first uplink resource scheduling policy further includes information of a third DRB, and the third DRB is used to carry the uplink normal data of the first terminal device. data.
A communication method, comprising:

The first terminal device receives the first uplink resource scheduling policy from the access network device, the first uplink resource scheduling policy includes information of at least one DRB, the information of the at least one DRB includes information of the first DRB, the first A DRB is used to carry the uplink peak data of the first terminal device;

The first terminal device sends the uplink peak data of the first terminal device to the access network device on the first DRB according to the first uplink resource scheduling policy.
The method of claim 10, wherein the first terminal device sends the first terminal device to the access network device on the first DRB according to the first uplink resource scheduling policy The upstream peak data of , including:

determining, by the first terminal device, the first DRB according to the first uplink resource scheduling policy and traffic characteristics of uplink peak data of the first terminal device;

The first terminal device sends the uplink peak data of the first terminal device to the access network device on the first DRB.
The method of claim 11, wherein the information of the first DRB includes a type of the first DRB, and the type of the first DRB is used to indicate the type of service data flow carried by the first DRB. traffic characteristics;

The first terminal device determines the first DRB according to the first uplink resource scheduling policy and the traffic characteristics of the uplink peak data of the first terminal device, including:

The first terminal device determines a DRB type corresponding to the uplink peak data of the first terminal device according to the traffic characteristics of the uplink peak data of the first terminal device;

The first terminal device determines the first DRB corresponding to the DRB type.
The method according to claim 11 or 12, wherein the information of the first DRB includes an initial usage time of the first DRB and a usage duration of the first DRB;

The first terminal device sends the uplink peak data of the first terminal device to the access network device on the first DRB, including:

The first terminal device sends the uplink of the first terminal device to the access network device on the first DRB according to the initial use time of the first DRB and the use duration of the first DRB peak data.
The method according to any one of claims 10-13, wherein the information of the first DRB includes a usage period of the first DRB, and the usage period is used to instruct the first terminal device to send an uplink peak value period of data.
The method according to any one of claims 10-14, wherein the information of the first DRB includes configuration information of the first DRB, and the configuration information of the first DRB includes time domain resources and frequency domain resources , modulation and coding scheme, antenna port, listening reference signal resource indication, one or more of demodulation reference signal.
The method according to any one of claims 10-15, wherein the uplink peak data of the first terminal device carried by the first DRB includes I-frame data.
The method according to any one of claims 10-16, wherein the use time period of the first DRB and the second DRB do not completely overlap, and the second DRB is used to carry uplink peak data of the second terminal device ; wherein, the sum of the data volume of the uplink peak data of the first terminal device and the data volume of the uplink peak data of the second terminal device within the first time period does not exceed the data volume threshold.
The method according to any one of claims 10-17, wherein,

The first uplink resource scheduling policy further includes information of a third DRB, where the third DRB is used to carry the normal uplink data of the first terminal device.
A communication device, comprising:

a processing unit, configured to determine a first uplink resource scheduling policy of the first terminal device and a second uplink resource scheduling policy of the second terminal device, where the first uplink resource scheduling policy includes information of the first data radio bearer DRB, the The first DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes information of the second DRB, and the second DRB is used to carry the uplink peak data of the second terminal device , the use time periods of the first DRB and the second DRB do not completely overlap;

A transceiver unit, configured to send the first uplink resource scheduling policy to the first terminal device, and send the second uplink resource scheduling policy to the second terminal device.
The apparatus according to claim 19, wherein the transceiver unit is further configured to receive uplink peak data from the first terminal device and uplink peak data from the second terminal device within a first time period data, the uplink peak data of the first terminal device is carried in the first DRB, the uplink peak data of the second terminal device is carried in the second DRB, the data of the uplink peak data of the first terminal device The sum of the data volume and the data volume of the uplink peak data of the second terminal device does not exceed the data volume threshold.
The device of claim 19 or 20, wherein:

The processing unit is specifically configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, and determine the second uplink resource scheduling policy according to the information of the second terminal device.
The apparatus according to claim 21, wherein the transceiver unit is further configured to receive the information of the first terminal device and the information of the second terminal device from a session management network element, the first terminal The information of the device includes the identification information of the first terminal device, the feature information of the service data flow of the first terminal device, and the first quality of service QoS information of the service data flow of the first terminal device. The characteristic information of the service data flow of the terminal device is used to indicate the traffic characteristic information corresponding to different time slices of the service data flow of the first terminal device in a time period, and the first QoS information is used to indicate the The QoS level identifiers QCI corresponding to different time slices respectively, the information of the second terminal device includes the identification information of the second terminal device, the feature information of the service data flow of the second terminal device, and the second terminal device. The second QoS information of the service data flow of the device, and the feature information of the service data flow of the second terminal device is used to indicate that the service data flow of the second terminal device corresponds to different time slices in a time period. Traffic characteristic information, where the second QoS information is used to indicate the QCIs corresponding to the different time slices respectively.
The apparatus according to claim 22, wherein the information of the first DRB includes the type of the first DRB, the initial usage time of the first DRB, and the usage duration of the first DRB, and the The type of the first DRB is used to indicate the traffic characteristics of the service data flow carried by the first DRB, and the initial usage time of the first DRB and the usage duration of the first DRB are used for the first terminal device Determine the time to send uplink peak data;

The processing unit, configured to determine the first uplink resource scheduling policy according to the information of the first terminal device, specifically includes: determining the type of the first DRB according to the first QoS information; The characteristic information of the service data flow of the first terminal device determines the initial usage time of the first DRB and the usage duration of the first DRB;

The information of the second DRB includes the type of the second DRB, the initial use time of the second DRB, and the use time of the second DRB, and the type of the second DRB is used to indicate the second DRB. The traffic characteristics of the service data flow carried by the DRB, the initial usage time of the second DRB and the usage duration of the second DRB are used for the second terminal device to determine the time to send the uplink peak data;

The processing unit, configured to determine the second uplink resource scheduling policy according to the information of the second terminal device, specifically includes: determining the type of the second DRB according to the second QoS information; The characteristic information of the service data flow of the second terminal device determines the starting time of use of the second DRB and the use time of the second DRB.
The apparatus according to claim 22 or 23, wherein the characteristic information of the service data flow of the first terminal device comprises a first time period, at least two time slices corresponding to the first time period and all The bit rates corresponding to the at least two time slices respectively, the first QoS information includes the QFI and the QCIs corresponding to the at least two time slices respectively, and the QCIs corresponding to the at least two time slices are not exactly the same , the service data flow of the first terminal device is mapped to the QoS flow corresponding to the QFI;

The feature information of the service data stream of the second terminal device includes a second time period, at least two time slices corresponding to the second time period, and bit rates corresponding to the at least two time slices respectively, and the The second QoS information includes the QFI and the QCIs corresponding to the at least two time slices, the QCIs corresponding to the at least two time slices are not exactly the same, and the service data flow of the second terminal device is mapped to the The QoS flow corresponding to the QFI.
A communication device, comprising:

a receiving unit, configured to receive a first uplink resource scheduling policy from an access network device, the first uplink resource scheduling policy includes information of at least one DRB, the information of the at least one DRB includes information of the first DRB, the The first DRB is used to carry the uplink peak data of the first terminal device;

A sending unit, configured to send the uplink peak data of the first terminal device on the first DRB to the access network device according to the first uplink resource scheduling policy.
The apparatus according to claim 25, wherein the apparatus further comprises a processing unit, configured to determine the the first DRB;

The sending unit is specifically configured to send the uplink peak data of the first terminal device to the access network device on the first DRB.
The apparatus of claim 26, wherein the information of the first DRB includes a type of the first DRB, and the type of the first DRB is used to indicate the type of service data flow carried by the first DRB. traffic characteristics;

The processing unit is specifically configured to determine the DRB type corresponding to the uplink peak data of the first terminal device according to the traffic characteristics of the uplink peak data of the first terminal device; determine the first terminal device corresponding to the DRB type. a DRB.
The apparatus according to claim 26 or 27, wherein the information of the first DRB includes an initial usage time of the first DRB and a usage duration of the first DRB;

The sending unit is specifically configured to send the first terminal device to the access network device on the first DRB according to the initial usage time of the first DRB and the usage duration of the first DRB up peak data.
A communication system, characterized in that it includes an access network device and a session management network element;

the session management network element, configured to send the information of the first terminal device and the information of the second terminal device to the access network device;

The access network device is configured to determine a first uplink resource scheduling policy according to the information of the first terminal device, and determine a second uplink resource scheduling policy according to the information of the second terminal device, the first uplink resource The scheduling policy includes the information of the first data radio bearer DRB, the first DRB is used to carry the uplink peak data of the first terminal device, the second uplink resource scheduling policy includes the information of the second DRB, the second The DRB is used to carry the uplink peak data of the second terminal device, and the usage time periods of the first DRB and the second DRB do not completely overlap; sending the first uplink resource scheduling policy to the first terminal device , and send the second uplink resource scheduling policy to the second terminal device.