Communication method and related device
By obtaining the delay parameters of non-periodic services in the 5G mobile communication system and determining the configuration cycle of transmission resources, the problem that non-periodic services cannot meet the delay requirements is solved, semi-static scheduling is realized, and transmission efficiency is improved.
Patent Information
- Application Number
- CN202310512669.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-08
- Publication Date
- 2024-11-08
AI Technical Summary
In 5G mobile communication systems, non-periodic services cannot meet the requirements of transmission delay because the wireless access network cannot provide semi-static scheduling and temporarily allocate resources.
By obtaining the delay parameters of non-periodic services, the configuration period of transmission resources is determined, so that the access network equipment can use the resources configured in cycles to transmit, realizing semi-static scheduling, and avoiding the delay caused by temporary resource allocation.
Meet the low-latency transmission requirements of non-periodic services, ensure that data packets can be sent within a specified time outside the configuration cycle, and improve the transmission efficiency of non-periodic services.
Smart Images

Figure CN118921748A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and in particular to a communication method and related devices. Background Art
[0002] At present, in some communication systems, such as the fifth generation (5G) mobile communication system, for some periodic services, the centralized network configuration (CNC) can be used to configure the sending time window and flow period for the 5G system, so as to realize the periodic scheduling (for example, semi-static scheduling) of the resources used to transmit the data packets of the periodic services by the radio access network (RAN). This scheduling method does not need to temporarily allocate scheduling resources, and can transmit data packets faster, thus ensuring the low latency requirements of the periodic services.
[0003] However, for some non-periodic services, RAN cannot provide semi-static scheduling and needs to allocate resources temporarily, so it may not be able to meet the transmission delay requirements of non-periodic services. Summary of the invention
[0004] The present application provides a communication method and related devices to ensure the transmission delay of non-periodic services.
[0005] In a first aspect, the present application provides a communication method, which includes: obtaining a delay parameter of a first service, wherein the delay parameter is related to a delay requirement, a packet delay budget (PDB) requirement or a PDB, and the first service is a non-periodic service; based on the delay parameter, determining a configuration period of a transmission resource, and the transmission resource is used to transmit data packets of the first service.
[0006] Taking downlink transmission as an example, the latency requirement refers to the time required for a data packet to enter the user plane function (UPF) on the core network side and be output from the terminal. The PDB requirement refers to the time required for a data packet to enter the UPF on the core network side and enter the terminal. That is, the PDB requirement is the difference between the latency requirement and the first processing duration of the terminal. Among them, PDB defines the upper limit of the time that a data packet may be delayed between the terminal and the N6 termination point of the UPF.
[0007] In the present application, based on the delay parameters of the non-periodic service, the configuration period of the transmission resources of the non-periodic service is determined, so that the access network equipment does not need to temporarily configure resources every time the non-periodic service is received, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by temporarily configuring resources when the service arrives, thereby helping to meet the transmission delay requirements of the non-periodic service.
[0008] In one possible implementation, the method is applied to a time-sensitive communication time synchronization function (TSCTSF), which can be executed by the TSCTSF, or by components configured in the TSCTSF (such as a chip, a chip system, etc.), or by a logic module or software that can implement all or part of the TSCTSF function, and the present application does not limit this.
[0009] In this implementation, the delay parameter may be the delay requirement.
[0010] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from an application function (AF) or a network exposure function (NEF), wherein the first request message indicates the delay requirement, and the delay requirement is the sum of the PDB requirement and the time length for the terminal to process the data packet.
[0011] Optionally, the sum of the configuration period and the PDB requirement is less than or equal to the latency requirement, and the method further includes: determining the PDB requirement based on the latency requirement; sending a second request message to a policy control function (PCF), wherein the second request message indicates the configuration period and the PDB requirement.
[0012] The PDB requirement is the difference between the delay requirement and the time length for the terminal to process a data packet.
[0013] Since the sum of the configuration period and the PDB requirement is less than the delay requirement of the first service, even if the access network device receives a data packet of the first service outside the configuration period, it can send the data packet through the terminal within the delay required by the first service, thereby meeting the low-latency transmission requirements of non-periodic services.
[0014] In another possible implementation, the method is applied to PCF and can be executed by PCF, or it can be executed by components configured in PCF (such as chips, chip systems, etc.), or it can be implemented by logic modules or software that can implement all or part of the PCF functions, which is not limited in this application.
[0015] In this implementation, the delay parameter may be the PDB requirement.
[0016] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from one of the following network elements, where the first request message indicates a PDB requirement of the first service: TSCTSF, AF, NEF.
[0017] It should be understood that receiving the first request message from one of the following network elements includes: receiving first information from a TSCTSF, receiving first information from an AF, or receiving first information from an NEF.
[0018] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from one of the following network elements, where the first request message indicates a delay requirement of the first service: AF, NEF.
[0019] It should be understood that receiving the first request message from one of the following network elements includes: receiving first information from an AF, or receiving first information from an NEF.
[0020] Optionally, the sum of the configuration period and the PDB is less than or equal to the PDB requirement, and the method further includes: determining the PDB based on the first request message; sending first information to a session management function (SMF), the first information including the configuration period and the PDB.
[0021] Since the sum of the configuration period and the PDB is less than the PDB requirement of the first service, even if the access network device receives a data packet of the first service outside the configuration period, it can send the data packet to the terminal within the delay required by the first service, thereby meeting the low-latency transmission requirements of non-periodic services.
[0022] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; the data network name (data network name, DNN) is a first value; single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) is a second value; or, the first request message does not include the period of the first service.
[0023] Among them, the first preset threshold and the second preset threshold are respectively a preset time length, and the two can be the same or different. For example, the first preset threshold is 4 milliseconds (ms) and the second preset threshold is 5ms; or, the first preset threshold and the second preset threshold are both 4ms.
[0024] The above-mentioned DNN and S-NSSAI may refer to the DNN corresponding to the protocol data unit (PDU) session, or the S-NSSAI may refer to the DNN or S-NSSAI in the request message from the AF as a specific DNN or S-NSSAI. The first value and the second value are respectively a predefined parameter value, for example, the first value is 2, and the second value is 3.
[0025] Optionally, the method further includes: generating indication information, the indication information being used to indicate that the first service is a non-periodic service; and sending the indication information.
[0026] Exemplarily, if the indication information is generated by TSCTSF, the TSCTSF sends the indication information to PCF; if the indication information is generated by PCF, the PCF sends the indication information to SMF.
[0027] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0028] For the description of the first preset threshold and the second preset threshold, please refer to the previous description and will not be repeated here.
[0029] Optionally, the method also includes: obtaining scheduling status information from a radio access network (RAN), the scheduling status information including uplink and downlink ratios of the air interface, scheduling timing and other parameters; determining the configuration period of the transmission resources based on the delay parameters includes: determining the configuration period based on the delay parameters and the scheduling status information.
[0030] Optionally, the method also includes: receiving an expected value of the configuration period from the RAN; determining the configuration period of the transmission resource based on the delay parameter includes: determining multiple values of the configuration period based on the delay parameter and the expected value; or determining a value range of the configuration period based on the delay parameter and the expected value.
[0031] Optionally, the method further includes: generating flow direction information; and sending the flow direction information. The flow direction information includes a flow direction, which refers to a transmission direction of a data packet, including uplink transmission and downlink transmission, that is, the flow direction refers to whether the data packet of the first service is an uplink transmission data packet or a downlink transmission data packet.
[0032] In another possible implementation, the method is applied to a RAN and can be executed by the RAN, or can be executed by a component configured in the RAN (such as a chip, a chip system, etc.), or can be implemented by a logic module or software that can implement all or part of the RAN functions, which is not limited in this application.
[0033] In this implementation, the delay parameter may be a PDB authorized by the PCF for the first service based on the PDB requirement.
[0034] Optionally, the acquiring the delay parameter of the first service includes: receiving the PDB from the SMF.
[0035] Optionally, before determining the configuration period of the transmission resources based on the delay parameter, the method further includes: receiving indication information indicating that the first service is a non-periodic service; and determining an access network AN PDB based on the indication information and the PDB.
[0036] Optionally, the method further includes: acquiring a data packet of the first service; and transmitting the data packet using the most recently configured transmission resources.
[0037] On the second aspect, the present application provides a communication method, which can be executed by PCF, or by components configured in PCF (such as chips, chip systems, etc.), or by logic modules or software that can implement all or part of the PCF functions, and the present application does not limit this.
[0038] Exemplarily, the method includes: receiving a second request message, the second request message indicating a configuration period and a PDB requirement of a transmission resource, the transmission resource being used to transmit data packets of a first service, the first service being a non-periodic service; determining a PDB, the PDB being less than or equal to the PDB requirement; and sending first information to an SMF, the first information indicating the PDB and the configuration period.
[0039] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving indication information, where the indication information is used to indicate that the first service is a non-periodic service.
[0040] Optionally, determining the PDB includes: determining the PDB based on at least one of the following: the PDB requirement, DNN or S-NSSAI.
[0041] In a third aspect, the present application provides a communication device, comprising a module or unit for executing a method in any possible implementation of any of the above aspects.
[0042] It should be understood that each module or unit can implement corresponding functions by executing a computer program.
[0043] In a fourth aspect, the present application provides another communication device, comprising a processor, wherein the processor is used to execute the method described in any aspect and any possible implementation of any aspect.
[0044] The device may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented.
[0045] The apparatus may further include a communication interface, and the communication interface is used for the apparatus to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
[0046] In a fifth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in any of the above aspects and any possible implementation of any of the aspects, for example, receiving or processing the data and / or information involved in the above method.
[0047] In one possible design, the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.
[0048] The chip system may be composed of the chip, or may include the chip and other discrete devices.
[0049] In a sixth aspect, the present application provides a computer program product, comprising: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of any of the above aspects.
[0050] In a seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program (also referred to as code, or instructions) which, when executed on a computer, enables the computer to execute a method in any possible implementation of any of the above aspects.
[0051] In an eighth aspect, the present application provides a communication system, including the aforementioned TSCTSF and PCF.
[0052] Optionally, the communication system may also include other network elements that interact with the TSCTSF and / or PCF in the solution provided in the present application.
[0053] It should be understood that the second to eighth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] Figure 1 It is a schematic diagram of a network architecture based on a service-oriented architecture provided in an embodiment of the present application;
[0055] Figure 2 It is a schematic diagram of a network architecture based on a point-to-point interface provided in an embodiment of the present application;
[0056] Figure 3 It is a 5G QoS model based on service quality flow provided in an embodiment of the present application;
[0057] Figure 4 It is a schematic diagram of the rule flow of mapping QoS flow to AN resources provided in an embodiment of the present application;
[0058] Figure 5 This is the system architecture diagram of the intercommunication between 3GPP network and TSN;
[0059] Figure 6 It is a schematic diagram of the relationship between latency requirements and PDB requirements;
[0060] Figure 7 is a schematic diagram of the burst arrival time;
[0061] Figure 8 It is a schematic diagram of the network architecture of the newly added TSCTSF network element;
[0062] Figures 9 to 12is a schematic flow chart of a communication method provided in an embodiment of the present application;
[0063] Fig.13 and Fig.14 It is a schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0064] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0065] The technical solution provided in this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) mobile communication system or new radio access technology (NR), satellite communication system, etc.
[0066] The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6G) mobile communication system, etc. This application does not limit this.
[0067] Before introducing the communication method provided in the embodiment of the present application, a brief introduction is first given to each network element involved in the present application:
[0068] 1. Terminal: may be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. In the embodiments shown below, terminal equipment, terminal, and UE may be used interchangeably, but their meanings are the same.
[0069] The terminal device can be a device that provides voice / data connectivity to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals can be: mobile phones, tablet computers (pad), computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile Internet devices (mobile internet devices, MIDs), virtual reality (virtual reality, VR) devices, augmented reality (augmented reality, AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistants) assistant, PDA), handheld devices with wireless communication function, computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolved public land mobile communication networks (public land mobile network, PLMN), etc.
[0070] In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.
[0071] In addition, terminal devices can also include sensors such as smart printers, train detectors, and gas stations. Their main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.
[0072] 2. Access network (AN) equipment: The access network can provide network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to the user level, business requirements, etc. The access network can be an access network that uses different access technologies. There are currently two types of wireless access technologies: 3rd generation partnership project (3GPP) access technology and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standards and specifications. For example, the access network equipment in the 5G system is called the next generation node base station (gNB). Non-3GPP access technology refers to access technology that does not comply with 3GPP standards and specifications, for example, air interface technology represented by access points (APs) in wireless fidelity (Wi-Fi).
[0073] An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN). The radio access network can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and user data between the terminal and the core network.
[0074] The wireless access network equipment may include, for example, but is not limited to: a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or homenode B, HNB), a baseband unit (BBU), an AP in a Wi-Fi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It may also be a gNB or a transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a BBU, or a distributed unit (DU), or a base station in a next-generation communication 6G system, etc. This application does not limit the specific technology and specific device form adopted by the wireless access network equipment. The wireless access network equipment may include a gNB-centralized unit (CU) and a gNB-DU. The gNB-CU and the gNB-DU are connected via an F1 interface. The CU and the core network are connected via a next generation (NG) interface. The gNB-DU includes the functions of the physical layer (PHY) / medium access control (MAC) / radio link control (RLC) layer, which are used to provide access services for the relay devices attached to the access network equipment. The gNB-DU can be connected to the gNB-CU via the F1 interface. The gNB-DU can also be connected to the mobile terminal (mobile-termination, MT) function of the terminal device or mobile relay via the Uu interface.
[0075] The gNB-CU is used to perform radio resource control (RRC) on all relay devices and terminal devices under it, for example, it can store the context of relay devices and terminal devices. The gNB-CU can be connected to the DU function of other relay devices through the F1 interface.
[0076] The following is an introduction to the network elements of the core network.
[0077] 3. Application function (AF) network element: It can be referred to as AF for short. It can provide some application layer services to terminal devices. When providing services to terminal devices, AF has requirements for QoS and charging policies (charging), and needs to notify the network. At the same time, AF also needs the core network to feedback application-related information.
[0078] 4. Policy control function (PCF) network element: PCF for short. It is used to generate and manage user, session, and quality of service (QoS) flow processing policies, support a unified policy framework to manage network behavior, provide policy rules to network entities for implementation, and access subscription information of the unified data repository (UDR).
[0079] 5. Session management function (SMF) network element: It can be referred to as SMF for short. It is mainly used for user plane function (UPF) network element selection, UPF network element reselection, Internet protocol (IP) address allocation, session establishment, modification and release, and quality of service (QoS) control.
[0080] 6. Access and mobility management function (AMF) network element: AMF for short. It is used to perform registration, connection, reachability, and mobility management; it provides a session management message transmission channel for UE and SMF, provides authentication and authorization functions for user access, and is the access point of the terminal and the wireless core network control plane.
[0081] 7. Unified data management (UDM) network element: It can be referred to as UDM for short. It is responsible for the management of user identification, contract data, authentication data, and user service network element registration management (such as AMF, SMF, etc. that currently provide services to the terminal. For example, when the user switches the AMF to access, UDM will also send a deregistration message to the old AMF, requiring the old AMF to delete user-related information).
[0082] 8. User plane function (UPF) network element: It can be referred to as UPF for short. It is responsible for forwarding and receiving user data in terminal devices. It can receive user data from the data network and transmit it to the terminal device through the access network device; the UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal devices in the UPF network element are managed and controlled by the SMF network element.
[0083] 9. Network exposure function (NEF) network element: It can be referred to as NEF for short. It is mainly used to support the exposure of capabilities and events.
[0084] 10. Data network (DN): refers to the service network that provides data transmission services to users, such as IP Multimedia Service (IMS), Internet, etc. UE accesses the data network through the protocol data unit (PDU) session established between UE and DN.
[0085] To facilitate understanding of the embodiments of the present application, Figure 1 and Figure 2 The 5G network architecture applicable to the embodiments of the present application is introduced in detail.
[0086] Figure 1 Schematic diagram of a network architecture based on a service-oriented architecture provided in an embodiment of the present application. Figure 1 As shown, the 5G network architecture may include three parts, namely the terminal part, the data network (DN) and the operator network part.
[0087] The operator network may include one or more of the following network elements: authentication server function (AUSF) network element, NEF network element, PCF network element, UDM network element, network repository function (NRF) network element, AF network element, AMF network element, SMF network element, AN network element, UPF network element, and network slice selection function (NSSF) network element, etc. In the above operator network, the part other than the radio access network part can be called the core network part. Figure 1 In the network shown, each network element can communicate based on a service-based interface, where: Figure 1Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nusf, Namf, and Npcf are service-based interfaces. It should be understood that the functions of some network elements can refer to the description in the network element introduction above, and the specific functions can refer to known technologies, which will not be repeated here.
[0088] Figure 2 It is a schematic diagram of a network architecture based on a point-to-point interface provided in an embodiment of the present application. Figure 2 The network elements included in the network shown and their related introduction can be referred to Figure 1 Description. Figure 2 The network architecture shown is similar to Figure 1 The difference is, Figure 2 In the network architecture shown, the interfaces between various network elements are point-to-point interfaces rather than service-oriented interfaces.
[0089] It should be understood that Figure 1 and Figure 2 This is just a schematic diagram. The network architecture may also include other network elements, such as TSCTSF. Figure 1 and Figure 2 Not drawn in.
[0090] At present, in communication systems, such as 5G systems (5G systems, 5GS), in order to ensure the end-to-end service quality of services, a 5G QoS model based on quality of service (QoS flow) is proposed (such as Figure 3 As shown). The 5G QoS model supports QoS flows with guaranteed bit rate (GBR QoS flow) and QoS flows without guaranteed bit rate (Non-GBR QoS flow). Whether a QoS flow is "GBR" or "Non-GBR" depends on its QoS configuration. The QoS configuration of a QoS flow includes the following parameters: 1. The QoS configuration of each QoS flow includes the following QoS parameters: 5QI, ARP; 2. The QoS configuration of each Non-GBR QoS flow may also include the following parameters: reflective QoS attribute (RQA); 3. The QoS configuration of each GBR QoS flow may also include the following parameters: guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR); 4. The QoS configuration of each GBR QoS flow may also include the following parameters: indication control, maximum packet loss rate.
[0091] A UE can establish one or more PDU sessions with the 5G network, and one or more QoS flows can be established in each PDU session. Each QoS flow is identified by a QoS flow identifier (QFI). In 5GS, QoS flows are controlled by SMF, which can be pre-configured or established and modified through PDU sessions.
[0092] The characteristics of a QoS flow are composed of the following three parts:
[0093] 1. QoS configuration (profile) on the AN side: The configuration is provided to the AN by the SMF through the N2 interface, or is pre-configured in the AN.
[0094] It should be noted that the characteristic information about a QoS flow sent by the SMF to the AN is called a "QoS profile", where the characteristic information of the QoS flow includes the content shown in the following Table 1:
[0095] Table 1
[0096]
[0097] 2. QoS rules on the UE side: They can be provided to the UE by the SMF through N1 (for example, explicitly configured to the UE through signaling in the PDU session establishment / modification process), or derived by the UE through the reflective QoS mechanism.
[0098] 3. Uplink and downlink packet detection rule(s), PDR(s) rules on the UPF side: PDR(s) is provided to UPF by SMF through the N4 interface.
[0099] In the NR system, the granularity of QoS is related to the protocol layer. In the IP layer, it is the IP flow, in the NAS layer, it is the QoS flow, and in the AS layer, it is the data radio bearer (DRB). In the NAS layer, the IP flow is mapped to the QoS flow through the QoS rules. In the AS layer, the QoS flow is mapped to the DRB. The protocol that completes the mapping of the QoS flow to the DRB in the AS layer is the service data adaptation protocol (SDAP). Figure 4As shown in the figure, for uplink data, the UE matches the data packets according to the QoS rules, and the data packets are transmitted upward from the matched QoS flow and its corresponding AN channel; for downlink data, the UPF matches the data packets according to the PDR, and the data packets are transmitted downward from the matched QoS flow and its corresponding AN channel. If a data packet does not match any QoS rule or PDR, the data packet will be discarded by the UE or UPF.
[0100] Exemplarily, the UE performs classification and marking of uplink user plane data services by associating uplink data to corresponding QoS flows according to QoS rules. QoS rules have the following characteristics: 1. A QoS rule contains: QFI, packet filter set (a filter list), and priority of the associated QoS flow; 2. A QoS flow can have multiple QoS rules; 3. Each PDU session must be configured with a default QoS rule, and the default QoS rule is associated with a QoS flow.
[0101] 5QI is a scalar used to index a 5G QoS feature. Some 5QIs are standardized, some are pre-configured, and some are dynamically defined. For standardized 5QI, it is sufficient to include 5QI in the signaling on the NG interface; for dynamically defined 5QI, the parameters mentioned in Table 2 below need to be explicitly configured in the signaling.
[0102] Table 2
[0103]
[0104]
[0105] The binding mechanism is the process of associating a service data flow (defined in PCC rules through a service data flow (SDF) template) with the QoS flow that is considered to transport the service data flow.
[0106] Since the PCC rule is at the SDF granularity, and the 5G QoS model is at the QoS Flow granularity, that is, RAN performs scheduling based on the QoS Flow granularity, it is necessary to map the SDF to the QoS flow for QoS control.
[0107] The binding mechanism includes the following three steps:
[0108] 1. Session binding: Make a one-to-one correspondence between AF session and PDU session.
[0109] 2. PCC rule authorization: This is performed by the PCF to authorize the PCC rules and allocate QoS parameters for the PCC rules.
[0110] 3. QoS flow binding: Match PCC rules with QoS flows. This is performed by SMF, associating PCC rules with QoS flows in PDU sessions. The following binding parameters can be used for binding: 5QI; ARP; QNC; priority; average window; maximum data burst capacity. That is, PCC rules with different attributes will be bound to different QoS flows.
[0111] Specifically, when the PCF provides the PCC rule, the SMF shall evaluate whether there is a QoS flow with the same QoS parameters as the binding parameters. If there is no such QoS flow, the SMF uses the parameters in the PCC rule to derive the QoS parameters of the new QoS flow. The PCC rule is bound to the QoS flow, and then a new QoS flow is established according to the QoS parameters; if there is a QoS flow with the same QoS parameters as the binding parameters, the SMF binds the PCC rule to the QoS flow.
[0112] In the 5G system, for some periodic services, a centralized network configuration (CNC) is used to configure a sending time window and a flow period for the 5G system, so as to implement periodic scheduling (e.g., semi-static scheduling) of resources used to transmit data packets of periodic services by the RAN.
[0113] Combine the following Figure 5 The architecture shown introduces a semi-scheduling approach for periodic services.
[0114] Figure 5 FIG. 1 shows a system architecture diagram of intercommunication between a 3rd Generation Partnership Project (3GPP) network and a time sensitive networking (TSN). Figure 5As shown in the figure, 3GPP 5GS and TSN translator (Translator) (TT for short) as a whole act as a logical TSN bridge. 5GS exchanges information with nodes in the TSN network through the control plane TT (AF). The exchanged information includes: 5GS bridge capability information, TSN configuration information, time scheduling information of TSN input and output ports, time synchronization information, etc. Among them, the TSN Translator on the UE side can be called the TSN Translator on the device side (DS-TT for short), which may be located inside the UE or outside; the TSN Translator on the UPF side can be called the TSN Translator on the network side (NW-TT for short), which is located inside the UPF.
[0115] For example, the 5GS as a whole acts as a TSN bridge. The CNC configures the sending time window and flow period for each TSN bridge according to the information reported by the 5GS bridge and other bridges to ensure end-to-end deterministic latency.
[0116] The following is an example of the user plane processing message. After the message is transmitted from the TSN system to NW-TT, NW-TT sends it to DS-TT, and DS-TT sends the message within the preconfigured time according to the sending time window (i.e., the gating scheduling parameter) configured by CNC. In order to ensure that the message can be sent in time, the message needs to arrive at DS-TT before the preset sending time and be cached at DS-TT to the sending time window.
[0117] like Figure 6 As shown in the figure, for specific messages with deterministic delay requirements, 5GS needs to determine the corresponding PDB according to the delay requirements of the messages, and ensure that the transmission time of the messages between UE and UPF is not greater than PDB. That is to say, the message will arrive at DS-TT in advance so that it can catch up with the sending time window configured by CNC. Among them, the delay requirement refers to the end-to-end delay requirement. For example, the delay requirement refers to the time required for the message to enter the core network and be sent from the terminal. PDB is determined by PCF based on PDB requirements, or as an example, the PDB requirement refers to the time required for the message to enter the core network and arrive at the terminal. Compared with the above delay requirements, the PDB requirement does not include the processing time of the terminal for the message. In other words, delay requirement = PDB requirement + terminal processing time (which can be called UE-DS-TT residence time).
[0118] Since 3GPP and TSN are connected and adopt a black box model, CNC can configure the time to arrive at 5GC and the time to leave 5GC according to the flow granularity. The uncertainty caused by air interface transmission and wired transmission between UE and UPF is eliminated by caching at the endpoint TT. For example, TSN AF determines the time when TSN flow arrives at the 5GS entrance based on the scheduling information of TSN flow obtained from CNC. The time of the flow entrance can be the time when the downlink TSN flow arrives at the NW-TT entrance, such as Figure 7 The burst arrival time of the downlink (DL) in the DS-TT or the time when the uplink TSN flow arrives at the DS-TT entrance. The TSN AF provides the scheduling information of the flow to the SMF in the time sensitive communication assistance container (TSCAC) through the PCF. The SMF further determines the time to reach the NG-RAN in the downlink direction based on the received information, such as Figure 7 The time sensitive communication assistance information (TSCAI) burst arrival time in the UE or the time it is sent from the UE in the uplink direction is provided to the RAN as TSCAI information so that the RAN node can reserve resources in advance.
[0119] Among them, the downlink direction TSCAI burst arrival time = DL burst arrival time + DL CN PDB.
[0120] TSCAI includes the following information: 1. Flow direction: indicates whether the TSC flow is in the uplink or downlink direction; 2. Period: refers to the interval between the start times of two adjacent bursts; 3. Burst arrival time: can be the burst arrival time in the downlink direction or the uplink direction. The downlink direction refers to the time when the burst arrives at the entrance of the RAN node, and the uplink direction refers to the time when the burst arrives at the UE exit.
[0121] It should be understood that SMF will bind a specific service to a QoS flow, that is, there is a corresponding relationship between the QoS flow and the service data flow. For delay-sensitive services, it is generally believed that there is a one-to-one correspondence between the QoS flow and the service data flow.
[0122] However, for non-TSN delay-sensitive service flows, also known as time-sensitive communication (TSC) service flows: By adding TSCTSF, TSC services in non-TSN scenarios are enabled. The network architecture of the newly added TSCTSF network element is as follows: Figure 8As shown. Among them, the functions of TSCTSF include:
[0123] 1. Associate the time synchronization service request from AF to the AF session;
[0124] 2. Interact with DS-TT / NW-TT PMIC / BMIC to manage and control DS-TT / NW-TT;
[0125] 3. Check the availability of 5GS bridge or 5GS node information reported by PCF;
[0126] 4. Create a TSC assistance container based on the service type parameters provided by the AF / NEF and provide it to the PCF;
[0127] Exemplarily, the AF sends a delay requirement (requested delay) to the TSCTSF, and the TSCTSF subtracts the terminal processing time from the delay requirement to obtain a PDB requirement (requested PDB), and sends the requested PDB to the PCF.
[0128] 5. Determine the 5GS bridge delay based on the UE-DS-TT dwell time and provide it to the PCF.
[0129] In summary, the above-mentioned periodic services facilitate periodic scheduling (such as semi-static scheduling) by RAN nodes. This scheduling method does not require temporary allocation of scheduling resources, and can transmit data packets faster, ensuring low latency data latency for periodic services. However, for non-periodic services, RAN cannot provide semi-static scheduling and requires temporary allocation of resources, so it may not be able to meet the latency requirements of some non-periodic services.
[0130] In view of this, an embodiment of the present application provides a communication method and related devices. In the method, based on the delay parameters of the non-periodic service, the configuration period of the resources used to transmit the non-periodic service is determined, so that the access network equipment that receives the non-periodic service no longer needs to temporarily configure resources for each non-periodic service received, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by the service reaching the temporarily configured resources, thereby helping to meet the transmission delay requirements of the non-periodic service.
[0131] Before introducing the method provided in the embodiments of the present application, the following points are explained.
[0132] First, in the embodiments of the present application, the use of prefixes such as "first" and "second" is only to facilitate the distinction and description of different things belonging to the same name category, and does not restrict the order, size or quantity of the things. For example, the "first request message" and the "second request message" are just different messages, and there is no size relationship or priority relationship between the two.
[0133] Second, "sending" and "receiving" in the embodiments of the present application indicate the direction of signal transmission. For example, "sending a second request message to PCF" can be understood as the destination end of the request message is PCF, which can include direct sending and indirect sending by other units or modules. "Receiving a first request message from AF or NEF" can be understood as the source end of the request message is AF or NEF, which can include receiving directly from AF or NE and indirectly receiving from AF or NE from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.
[0134] In other words, sending and receiving can be performed between network elements, for example, between TSCTSF and PCF; it can also be performed within a network element, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.
[0135] It is understandable that before the information is sent from the source end to the destination end, it may be subjected to necessary processing, such as encoding, modulation, etc. After receiving the information from the source end, the destination end may also perform corresponding processing, such as decoding, demodulation, etc., so as to interpret the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated.
[0136] Third, in the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but it does not exclude the situation where the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.
[0137] Combine the following Fig. 9 , describes in detail the communication method provided in the embodiment of the present application. The method can be applied to Figure 1 or Figure 2 The network architecture is shown, but the embodiments of the present application are not limited to this.
[0138] Fig. 9 900 is a schematic flow chart of a communication method 900 provided in an embodiment of the present application. It should be understood that the method can be executed by TSCTSF, PCF or RAN, or by a chip, chip system or processor supporting TSCTSF, PCF or RAN, and the present application does not limit this. Fig. 9 As shown, the method 900 includes S901 and S902. Fig. 9 The steps shown.
[0139] S901: Obtain a delay parameter of a first service.
[0140] The first service is a non-periodic service. For example, the first service may be a distributed energy service or a microgrid service.
[0141] The delay parameter is related to the delay requirement, the PDB requirement or the PDB. In other words, the delay parameter includes the delay requirement, the PDB requirement or the PDB.
[0142] For the description of latency requirements, PDB requirements, and PDB, refer to the above Figure 6 The description in will not be repeated here.
[0143] S902: Determine a configuration period of transmission resources based on the delay parameter.
[0144] The transmission resource is used to transmit a data packet of the first service. The data packet of the first service may also be referred to as a data flow of the first service or a service flow of the first service. It should be understood that the different names are due to different protocol sides, but the essence is the same, so this application does not limit this.
[0145] It should be understood that the configuration period refers to the period for configuring transmission resources. For example, the transmission resources may be configured once at intervals of time T, where T is the above configuration period.
[0146] Exemplarily, the delay parameter indicates that the delay requirement of the first service is 4 ms, and the determined configuration period should be no greater than 4 ms, for example, may be 1 ms.
[0147] In an embodiment of the present application, the configuration period of the transmission resources of the non-periodic service is determined based on the delay parameters of the non-periodic service, so that the access network device no longer needs to temporarily configure resources for each non-periodic service received, but can transmit the non-periodic service on the transmission resources periodically configured based on the configuration period, thereby ensuring the transmission delay of the non-periodic service.
[0148] The method of the embodiment of the present application is described in detail below by taking the method 900 applied to TSC TSF, PCF or RAN as an example.
[0149] Example 1: The method 900 is applied to TSCTSF, and the delay parameter is the delay requirement.
[0150] Optionally, the obtaining of the delay parameter of the first service includes: the TSCTSF receives a first request message from the AF or the NEF, where the first request message indicates a delay requirement (requested delay).
[0151] Optionally, the method 900 further includes: the TSCTSF determines a PDB requirement (requested PDB) based on the latency requirement, and the sum of the configuration period and the PDB requirement is less than or equal to the latency requirement; sends a second request message to the PCF, the second request message indicating the configuration period and the PDB requirement. Correspondingly, the PCF receives the second request message and determines a PDB, the PDB is less than or equal to the PDB requirement; sends a first message to the SMF, the first message including the PDB and the configuration period.
[0152] It should be understood that the requested PDB determined by the TSCTSF is the difference between the requested delay and the UE-DS-TTresidence time, and the sum of the requested PDB determined by the TSCTSF and the configuration period should not be greater than the requested delay.
[0153] For example, in 5GS, the delay requirement in this application can be expressed as requested 5GS delay, the PDB requirement can be expressed as requested 5GS PDB, and the configuration period can be expressed as periodicity.
[0154] Example 2: The method 900 is applied to PCF, and the above delay parameter is a PDB requirement.
[0155] In a possible implementation, the above-mentioned obtaining of the delay parameter of the first service may include: the PCF receives a first request message from one of the following network elements, where the first request message indicates the PDB requirement of the first service: TSCTSF, AF, NEF.
[0156] Exemplarily, obtaining the delay parameter of the first service includes: the PCF receives a first request message from the TSCTSF; the PCF receives a first request message from the AF; or the PCF receives a first request message from the NEF, and the first request message indicates a PDB requirement.
[0157] Optionally, the method 900 further includes: the PCF determines the PDB based on the PDB requirement, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; and sends first information to the SMF, where the first information indicates the configuration period and the PDB.
[0158] In another possible implementation, the above-mentioned obtaining of the delay parameter of the first service may include: the PCF receives a first request message from one of the following network elements, where the first request message indicates the delay requirement of the first service: AF, NEF.
[0159] Exemplarily, obtaining a delay parameter of a first service includes: the PCF receives a first request message from the AF; or the PCF receives a first request message from the NEF, and the first request message indicates a delay requirement.
[0160] Optionally, method 900 further includes: the PCF determines the PDB based on the latency requirement, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; and sends first information to the SMF, where the first information indicates the configuration period and the PDB.
[0161] It should be understood that the PDB requirement here is the difference between the received delay requirement and the time length for the terminal to process the data packet.
[0162] In combination with the above-mentioned example 1 and example 2, when method 900 is applied to TSCTSF or PCF, the method 900 may further include: obtaining scheduling status information from RAN, the scheduling status information including uplink and downlink ratio of the air interface, scheduling timing and other parameters.
[0163] Exemplarily, the determining of the configuration period of the transmission resources based on the delay parameter includes: determining the configuration period based on the delay parameter and scheduling status information.
[0164] In combination with the above-mentioned example 1 and example 2, when method 900 is applied to TSCTSF or PCF, the method 900 also includes: receiving an expected value of a configuration period from the RAN; and determining multiple values or value ranges of the configuration period based on the delay parameter and the expected value.
[0165] It should be understood that the expected value may be a value of a configuration period of transmission resources for transmitting the first service determined by the RAN based on the current resource configuration.
[0166] That is, the TSCTSF or PCF can determine multiple configuration cycles, or determine a value range of a configuration cycle based on the delay parameter and the expected value, so that the RAN can determine a suitable configuration cycle from the multiple configuration cycles or the value range of the configuration cycle.
[0167] In combination with the above-mentioned examples one and two, when method 900 is applied to TSCTSF or PCF, the above-mentioned configuration period is determined when at least one of the following items is met: the latency requirement is less than or equal to the first preset threshold; the PDB requirement is less than or equal to the second preset threshold; the data network name (data network name, DNN) is the first value; the single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) is the second value; or, the first request message does not include the period of the first service.
[0168] Among them, the first preset threshold and the second preset threshold are respectively a preset time length, and the two can be the same or different. For example, the first preset threshold is 4 milliseconds (ms) and the second preset threshold is 5ms; or, the first preset threshold and the second preset threshold are both 4ms.
[0169] DNN and S-NSSAI may refer to the DNN and S-NSSAI corresponding to the PDU session; or the DNN or S-NSSAI in the request message from the AF is a specific DNN or S-NSSAI. For example, when the first value is 1, the TSCTSF or PCF needs to determine the configuration period, and when the second value is 3, the TSCTSF or PCF needs to determine the configuration period.
[0170] Exemplarily, if the first request message does not include the period of the first service, it can be determined that the first service is not a periodic service. Therefore, based on this, the TSCTSF or PCF can determine that it is necessary to determine the configuration period corresponding to the first service.
[0171] In combination with the above-mentioned example 1 and example 2, when method 900 is applied to TSCTSF or PCF, the method 900 also includes: generating indication information, where the indication information is used to indicate that the first service is a non-periodic service; and sending the indication information.
[0172] Exemplarily, when the method 900 is executed by the TSCTSF, the TSCTSF sends indication information to the PCF, and correspondingly, the PCF receives the indication information.
[0173] Optionally, the PCF determining the PDB may include: determining the PDB based on the received indication information; or determining the PDB based on at least one of the following: PDB requirement, DNN or S-NSSAI.
[0174] It should be understood that the description of DNN and S-NSSAI can be referred to the previous description and will not be repeated here.
[0175] It should also be understood that, in the case where the PCF receives the indication information, the determined PDB should be less than or equal to the above PDB requirement. In the case where the PCF does not receive the indication information, the PCF may determine the PDB based on DNN or S-NSSAI, etc.
[0176] Exemplarily, when the method 900 is executed by the PCF, the PCF sends indication information to the SMF, and correspondingly, the SMF receives the indication information.
[0177] Exemplarily, the above indication information can be determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; the DNN is a first value; the S-NSSAI is a second value; or the first request message does not include the period of the first service.
[0178] For the description of the first preset threshold, the second preset threshold, DNN, S-NSSAI, etc., please refer to the relevant description in the previous text and will not be repeated here.
[0179] It should be understood that the content indicated by the above indication information and the content indicated by the second request message can be indicated by the same information; or, respectively, by different information.
[0180] Example 3, the method 900 is applied to RAN, and the above delay parameter is the PDB authorized by the PCF for the first service based on the PDB requirement.
[0181] Exemplarily, the above-mentioned obtaining of the delay parameter of the first service includes: receiving a PDB from a PCF.
[0182] Optionally, before determining the configuration period of the transmission resources based on the delay parameters, the method 900 also includes: receiving indication information from the SMF; determining the configuration period of the transmission resources based on the delay parameters, including: determining the configuration period based on the delay parameters and the indication information.
[0183] It should be understood that the RAN does not need to generate TSCAI, but can perform semi-persistent scheduling (SPS), configured grant (CG) or dynamic grant (DG) according to the period.
[0184] Optionally, the method 900 further includes: the RAN obtains a data packet, where the data packet is a data packet of the first service; and the RAN transmits the data packet using the most recently configured transmission resources.
[0185] Below Fig. 9 Based on the embodiment shown in the figure, the execution subjects are TSCTSF, PCF and RAN as examples, combined with Figures 10 to 12 The communication method provided by this application is introduced. Fig. 9 The contents already introduced in the illustrated embodiment will not be repeated here. Figures 10 to 12 In the flowchart shown, the method is illustrated from the perspective of network element interaction.
[0186] Fig.10 FIG. 1 is a schematic flow chart of another communication method 1000 provided in an embodiment of the present application. Fig.10 As shown, the method 1000 may include S1001 to S1012. Fig.10 The steps shown.
[0187] S1001, the terminal establishes a PDU session.
[0188] The process of establishing a PDU session will not be described in detail here.
[0189] S1002, AF / NEF sends a first request message to TSCTSF. Correspondingly, TSCTSF receives the first request message.
[0190] The first request message indicates the delay requirement of the first service, and the first service is a non-periodic service. For the description of the delay requirement, please refer to the above Figure 6 The relevant description in will not be repeated here.
[0191] S1003, TSCTSF determines the configuration period and PDB requirement of transmission resources based on the delay requirement.
[0192] The sum of the PDB requirement and the configuration period is less than or equal to the latency requirement minus the UE-DS-TT residence time. The UE-DS-TT residence time is the time required to forward data packets within the UE and the DS-TT, that is, the time required to forward data packets between the UE ingress and the DS-TT port in the DL direction in the downlink direction, or the time required to forward data packets between the DS-TT port and the UE egress in the uplink direction.
[0193] For the description of the TSCTSF generation configuration period and the description of the transmission resources, please refer to the relevant description in the above method 900, which will not be repeated here.
[0194] It should be understood that the TSCTSF in the above S1003 may also determine only the configuration period of the transmission resources based on the delay requirement, but not the PDB requirement.
[0195] Optionally, TSCTSF may subscribe to scheduling status information from RAN through PCF or SMF, and determine the requested PDB and configuration period based on the scheduling status information and latency requirements; or, when TSCTSF is based on the period of RAN feedback tendency (i.e., the expected value of the above-mentioned configuration period), it uses the period of RAN feedback tendency as a reference for determining the requested PDB and configuration period. For example, TSCTSF generates one or more periods (i.e., multiple values of the above-mentioned configuration period) or a period range (i.e., the value range of the above-mentioned configuration period) based on the period of RAN feedback tendency and latency requirements for selection by RAN.
[0196] S1004, the TSC TSF sends a second request message to the PCF. Correspondingly, the PCF receives the second request message.
[0197] The second request message indicates the PDB requirement and configuration period.
[0198] S1005: TSCTSF generates indication information, where the indication information indicates that the first service is a non-periodic service.
[0199] S1006, TSCTSF sends the indication information to PCF.
[0200] It should be understood that S1005 and S1006 are optional steps. When S1005 is not executed, S1006 does not need to be executed. When S1005 is executed, S1006 may be executed or not. This is not limited here. Whether to execute S1005 can be determined based on the conditions for generating indication information shown in the above method 1000. For example, when the delay requirement is greater than the first preset threshold, or the first request message indicates a configuration period, S1005 may not be executed.
[0201] In one design, the TSCTSF may also generate flow direction information, and send the information to the PCF, and the PCF sends the information to the SMF. The flow direction information refers to information carrying a flow direction, and the flow direction refers to the transmission direction of a data packet, including uplink transmission and downlink transmission, that is, the flow direction refers to whether the data packet of the first service is an uplink transmission data packet or a downlink transmission data packet.
[0202] S1007, PCF determines the PDB. The PDB is less than or equal to the PDB requirement.
[0203] For the relevant description of PCF determining PDB, please refer to the description in method 900, which will not be repeated here.
[0204] S1008, PCF sends PDB and configuration cycle to SMF. Correspondingly, SMF receives PDB and configuration cycle.
[0205] It should be understood that the PDB and the configuration cycle may be indicated by the same information, such as the first information in method 900 .
[0206] Optionally, when the PCF receives the indication information, it may continue to execute S1009, and the PCF sends the indication information to the SMF. Correspondingly, the SMF receives the indication information. It is understandable that when the PCF receives the indication information, it may not execute S1009.
[0207] S1010, SMF sends PDB and configuration cycle to RAN. Correspondingly, RAN receives PDB and configuration cycle.
[0208] As above, the PDB and the configuration period may be indicated by the same information, for example, the first information.
[0209] Optionally, when receiving the indication information from the PCF, the SMF may continue to execute S1011, and the SMF sends the indication information to the RAN.
[0210] Optionally, after receiving the indication information, the SMF may dynamically adjust the received configuration period and send the adjusted configuration period to the RAN. For example, if the SMF previously received the cumulative rate ratio from the UPF, the SMF uses the cumulative rate ratio to correct the period in the TSCAC and sets the TSCAI period to the corrected value.
[0211] Optionally, if the SMF receives the flow direction information, it can instruct the terminal or UPF to generate virtual (dummy) data packets periodically according to the flow direction carried in the flow direction information. For example, if no service data packet is received in the corresponding period, a dummy data packet is generated, and if a service data packet is received in the corresponding period, the service data packet is transmitted.
[0212] S1012, the RAN configures transmission resources based on the configuration period, and determines the AN PDB based on the PDB.
[0213] For the description of AN PDB, reference may be made to the description of the prior art and will not be repeated here.
[0214] Exemplarily, when the RAN obtains the data packet of the first service, it transmits the data packet using the most recently configured transmission resources.
[0215] Optionally, after receiving the indication information, if the RAN does not receive the data packet within the corresponding configuration period, it does not consider the packet to be lost; or, if the data packet is received in advance, it does not consider the packet to be lost even if the buffering time exceeds the PDB.
[0216] It should be noted that the indication information in method 1000 is not necessarily transparently transmitted when forwarded between network elements. For example, the non-periodic indication 1 in the indication information sent by PCF to SMF indicates that the SDF is a non-periodic service, and the non-periodic indication 2 in the indication information sent by SMF to RAN indicates that the QoS Flow is a non-periodic service.
[0217] In the embodiment of the present application, TSCTSF determines the configuration period of the transmission resources of the first service based on the delay parameters of the first service, so that the RAN does not need to temporarily configure resources every time a non-periodic service is received, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by the temporary configuration of resources when the service arrives, thereby helping to meet the transmission delay requirements of the non-periodic service. Secondly, since the sum of the configuration period and the PDB requirement is less than the delay requirement of the first service, even if the RAN receives the data packet of the first service at a time outside the configuration period, the data packet can be cached in the air interface for up to 1 period and can be sent out within the required PDB time, which can meet the low-latency transmission requirements of the non-periodic service.
[0218] Fig.11 A schematic flow chart of another communication method 1100 provided in an embodiment of the present application. Fig.11 As shown, the method 1100 may include S1101 to S1109. Fig.11 The steps shown.
[0219] S1101, the terminal establishes a PDU session. This process is the same as the above S1001.
[0220] S1102, AF / NEF / TSCTSF sends a first request message to PCF. Correspondingly, PCF receives the first request message.
[0221] The first request message indicates a delay requirement of the first service or a PDB requirement of the first service.
[0222] S1103: The PCF determines a configuration period and a PDB of transmission resources based on the first request message.
[0223] For the description of the PCF generating configuration cycle and the configuration cycle, please refer to the relevant description in the above method 900, which will not be repeated here.
[0224] Exemplarily, the first request message indicates a delay requirement of the first service, and the sum of the above configuration period and the PDB is less than or equal to the delay requirement plus the time for the terminal to process a data packet.
[0225] Exemplarily, the first request message indicates a PDB requirement of the first service, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement.
[0226] It should be understood that the configuration period determined by the PCF may be smaller than the PDB or AN PDB. Under this design, scheduling according to the configuration period will not cause the service transmission time to exceed the PDB or AN PDB.
[0227] Optionally, the PCF may subscribe to scheduling status information from the RAN through the PCF or SMF, and determine the requested PDB and the configuration period (periodicity) based on the scheduling status information and the latency requirement; or, when the PCF is based on the period of the RAN feedback tendency (i.e., the expected value of the above-mentioned configuration period), the PCF uses the period of the RAN feedback tendency as a reference for determining the requested PDB and the configuration period. For example, the TSCTSF generates multiple periods (i.e., multiple values of the above-mentioned configuration period) or a period range (periodicity range) (i.e., the value range of the above-mentioned configuration period) based on the period of the RAN feedback tendency and the latency requirement for selection by the RAN.
[0228] S1104, PCF sends PDB and configuration cycle to SMF. Correspondingly, SMF receives PDB and configuration cycle.
[0229] It should be understood that the PDB and the configuration cycle may be indicated by the same information, for example, the first information in the above method 900 .
[0230] S1105: The PCF generates indication information, wherein the indication information indicates that the first service is a non-periodic service.
[0231] S1106, the PCF sends the indication information to the SMF, and correspondingly, the SMF receives the indication information.
[0232] It should be understood that S1105 and S1106 are optional steps. When S1105 is not executed, S1106 does not need to be executed. When S1005 is executed, S1106 may be executed or not. This is not limited here. Regarding the description of whether S1105 is executed, reference may be made to the description of S1005 in method 1000, which will not be repeated here.
[0233] In one design, the PCF may also generate flow direction information and send the information to the SMF. For the description of the flow direction information, reference may be made to the relevant description in method 1000, which will not be repeated here.
[0234] S1107, SMF sends PDB and configuration cycle to RAN. Correspondingly, RAN receives PDB and configuration cycle.
[0235] As above, the PDB and the configuration cycle may be indicated by the same information, for example, the first information in the above method 900 .
[0236] Optionally, when receiving the indication information from the PCF, the SMF may continue to execute S1108, where the SMF sends the indication information to the RAN, and correspondingly, the RAN receives the indication information.
[0237] Optionally, upon receiving the indication information from the PCF, the SMF may dynamically adjust the received configuration period and send the adjusted configuration period to the RAN. For example, if the SMF previously received the cumulative rate ratio from the UPF, the SMF uses the cumulative rate ratio to correct the period in the TSCAC and sets the TSCAI period to the corrected value.
[0238] Optionally, if the SMF receives flow direction information, it can instruct the terminal or UPF to generate dummy data packets periodically according to the flow direction carried in the flow direction information.
[0239] S1109, the RAN configures transmission resources based on the configuration period, and determines the AN PDB based on the PDB.
[0240] For the description of AN PDB, please refer to the previous description and will not be repeated here.
[0241] Exemplarily, when the RAN obtains the data packet of the first service, it transmits the data packet using the most recently configured transmission resources.
[0242] Optionally, after receiving the indication information, if the RAN does not receive the data packet in the corresponding period, it does not consider the packet to be lost; or, if the data packet is received in advance, it does not consider the packet to be lost even if the buffering time exceeds the PDB.
[0243] It should be noted that the indication information in method 1100 is not necessarily transparently transmitted when forwarded between various network elements. Specifically, reference may be made to the relevant description in the above method 1000, which will not be repeated here.
[0244] In the embodiment of the present application, the PCF determines the configuration period of the transmission resources of the first service based on the delay parameters of the first service, so that the RAN does not need to temporarily configure resources every time a non-periodic service is received, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by the temporary configuration of resources when the service arrives, thereby helping to meet the transmission delay requirements of the non-periodic service. Secondly, since the sum of the configuration period and the PDB is less than the PDB requirement of the first service, even if the RAN receives the data packet of the first service at a time outside the configuration period, the data packet can be cached in the air interface for up to 1 period and can be sent out within the required PDB time, which can meet the low-latency transmission requirements of the non-periodic service.
[0245] Fig.12 A schematic flow chart of another communication method 1200 provided in an embodiment of the present application. Fig.12 As shown, the method 1200 includes S1201 to S1209. Fig.12 The steps shown.
[0246] S1201, the terminal establishes a PDU session. This process is the same as S1001.
[0247] S1202, AF / NEF / TSCTSF sends a first request message to PCF. Correspondingly, PCF receives the first request message.
[0248] The first request message indicates a delay requirement of the first service or a PDB requirement of the first service.
[0249] For a description of latency requirements and PDB requirements, see Figure 6 The relevant description in will not be repeated here.
[0250] S1203: The PCF determines a PDB based on the first request message, and the PDB is less than or equal to the PDB requirement.
[0251] For the description of PCF determining PDB, please refer to the relevant description in the above example 1 or example 2, which will not be repeated here.
[0252] S1204, PCF sends PDB to SMF, and SMF receives the PDB accordingly.
[0253] S1205: The PCF generates indication information, wherein the indication information indicates that the first service is a non-periodic service.
[0254] S1206, PCF sends the indication information to SMF.
[0255] It should be understood that S1205 and S1206 are optional steps. When S1205 is not executed, S1206 does not need to be executed. When S1205 is executed, S1206 may be executed or not. This is not limited here. Regarding whether S1205 is executed, please refer to the relevant description of S1005 in method 1000, which will not be repeated here.
[0256] In one design, the PCF may also generate flow direction information and send the information to the SMF. The description of the flow direction information may refer to the above description and will not be repeated here.
[0257] S1207, SMF sends PDB to RAN, and RAN receives PDB accordingly.
[0258] Optionally, when receiving the indication information from the PCF, the SMF may continue to execute S1208, where the SMF sends the indication information to the RAN, and correspondingly, the RAN receives the indication information.
[0259] S1209, RAN generates a configuration cycle of AN PDB and transmission resources based on PDB.
[0260] The sum of this configuration cycle and AN PDB is less than PDB.
[0261] Exemplarily, when the RAN obtains the data packet of the first service, it transmits the data packet using the most recently configured transmission resources.
[0262] Optionally, after receiving the indication information, if the RAN does not receive the data packet in the corresponding period, it does not consider the packet to be lost; or, if the data packet is received in advance, it does not consider the packet to be lost even if the buffering time exceeds the PDB.
[0263] It should be noted that the indication information in method 1200 is not necessarily transparently transmitted when forwarded between various network elements. Specifically, reference may be made to the relevant description in the above method 1000, which will not be repeated here.
[0264] In the embodiment of the present application, the RAN determines the configuration period of the transmission resources of the first service based on the delay parameters of the first service, so that the RAN does not need to temporarily configure resources every time a non-periodic service is received, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by the temporary configuration of resources when the service arrives, thereby helping to meet the transmission delay requirements of the non-periodic service. Secondly, since the sum of the configuration period and the AN PDB is less than the PDB of the first service, even if the RAN receives a data packet of the first service outside the configuration period, the data packet can be cached in the air interface for up to 1 period and can be sent out within the required AN PDB time, which can meet the low-latency transmission requirements of the non-periodic service.
[0265] It should be understood that the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0266] Combined with the above Figure 1 and Fig.12 , describes the method of the embodiment of the present application in detail, and will be combined with Fig.13 and Fig.14 , describe in detail the device of the embodiment of the present application.
[0267] Fig.13 1 is a schematic block diagram of a communication device 1300 provided in an embodiment of the present application. Fig.13 As shown, the device 1300 includes: a transceiver module 1310 and a processing module 1320. The device 1300 can be used to execute the method executed by the TSCTSF, PCF or RAN in the above method embodiment.
[0268] Among them, the transceiver module 1310 is used to: obtain the delay parameters of the first service, the delay parameters are related to the delay requirement, the packet delay budget PDB requirement or PDB, and the first service is a non-periodic service; the processing module 1320 is used to: determine the configuration period of the transmission resources based on the delay parameters, and the transmission resources are used to transmit the data packets of the first service.
[0269] In a possible implementation, the device 1300 is the above-mentioned TSCTSF, or a chip or chip system of TSCTSF.
[0270] Exemplarily, the transceiver module 1310 is specifically used to: receive a first request message from the application function AF or the network open function NEF, the first request message indicating the delay requirement, and the delay requirement is the sum of the PDB requirement and the time length for the terminal to process the data packet.
[0271] Optionally, the processing module 1320 is also used to: determine the PDB requirement based on the latency requirement, and the sum of the configuration period and the PDB requirement is less than or equal to the latency requirement; the transceiver module 1320 is also used to: send a second request message to the policy control function PCF, and the second request message indicates the configuration period and the PDB requirement.
[0272] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0273] Optionally, the processing module 1320 is further used to: generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; and the transceiver module 1310 is further used to: send the indication information.
[0274] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0275] Optionally, the transceiver module 1310 is further used to: obtain scheduling status information from a radio access network RAN, the scheduling status information; the processing module 1320 is specifically used to: determine the configuration period based on the delay parameter and the scheduling status information.
[0276] Optionally, the transceiver module 1310 is further used to: receive an expected value of the configuration period from the RAN; the processing module 1320 is specifically used to: determine multiple values of the configuration period based on the delay parameter and the expected value; or, determine a value range of the configuration period based on the delay parameter and the expected value.
[0277] For a more detailed description of the transceiver module 1310 and the processing module 1320, please refer to Fig. 9 The relevant description in the illustrated embodiment is directly obtained and will not be repeated here.
[0278] In another possible implementation, the device 1300 is the above-mentioned PCF, or a chip or chip system of the PCF.
[0279] In one design, the transceiver module 1310 is specifically used to: receive a first request message from one of the following network elements, where the first request message indicates a PDB requirement for the first service: TSCTSF, AF, NEF.
[0280] Optionally, the transceiver module 1310 is specifically used to: receive a first request message from one of the following network elements, where the first request message indicates a delay requirement of the first service: AF, NEF.
[0281] Optionally, the processing module 1320 is also used to: determine the PDB based on the first request message, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; the transceiver module 1310 is also used to: send first information to the MF, and the first information includes the configuration period and the PDB.
[0282] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0283] Optionally, the processing module 1320 is further used to: generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; and the transceiver module 1310 is further used to: send the indication information.
[0284] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0285] Optionally, the transceiver module 1310 is further used to: obtain scheduling status information from a radio access network RAN, the scheduling status information; the processing module 1320 is specifically used to: determine the configuration period based on the delay parameter and the scheduling status information.
[0286] Optionally, the transceiver module 1310 is further used to: receive an expected value of the configuration period from the RAN; the processing module 1320 is specifically used to: determine multiple values of the configuration period based on the delay parameter and the expected value; or, determine a value range of the configuration period based on the delay parameter and the expected value.
[0287] In another design, the transceiver module 1310 is also used to: receive a second request message, the second request message indicates a configuration period and a packet delay budget PDB requirement of a transmission resource, the transmission resource is used to transmit data packets of a first service, the first service is a non-periodic service; the processing module 1320 is also used to: determine a PDB, the PDB is less than or equal to the PDB requirement; the transceiver module 1310 is also used to: send a first information, the first information including the PDB and the configuration period.
[0288] Optionally, the transceiver module 1310 is further used to: receive indication information, where the indication information is used to indicate that the first service is a non-periodic service.
[0289] Optionally, the processing module 1320 is specifically used to: determine the PDB based on at least one of the following: the PDB requirement, DNN or S-NSSAI.
[0290] For a more detailed description of the transceiver module 1310 and the processing module 1320, please refer to Fig. 9 The relevant description in the illustrated embodiment is directly obtained and will not be repeated here.
[0291] In another possible implementation, the device 1300 is the above-mentioned RAN, or a chip or chip system of the RAN.
[0292] Exemplarily, the transceiver module 1310 is specifically used to: receive the PDB from the SMF.
[0293] Optionally, the transceiver module 1310 is further used to: receive indication information, where the indication information indicates that the first service is a non-periodic service.
[0294] Optionally, the transceiver module 1310 is further used to: obtain a data packet, where the data packet is a data packet of the first service; and transmit the data packet using the most recently configured transmission resources.
[0295] For a more detailed description of the transceiver module 1310 and the processing module 1320, please refer to Fig. 9 The relevant description in the illustrated embodiment is directly obtained and will not be repeated here.
[0296] It should be noted that the device 1300 may include a sending module but not a receiving module. Alternatively, the device 1300 may include a receiving module but not a sending module. Specifically, it depends on whether the above solution executed by the device 1300 includes a sending action and a receiving action.
[0297] Fig.14 is another schematic block diagram of a communication device provided in an embodiment of the present application. Fig.14As shown, the device 1400 includes one or more processors 1410. The processor 1410 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the device (such as TSCTSF, PCF, RAN or chip, etc.), execute the software program, and process the data of the software program.
[0298] Optionally, in one design, the processor 1410 may include a program (also referred to as code or instruction), which may be executed on the processor 1410 to enable the apparatus 1400 to perform the method performed by the TSCTSF, PCF or RAN in the above method embodiment. In another possible design, the apparatus 1400 includes a circuit ( Fig.14 (not shown), the circuit is used to implement the functions of TSCTSF, PCF or RAN in the above method embodiments.
[0299] For example, the processor 1410 may be configured to execute computer programs or instructions in the memory to implement Figures 9 to 12 Steps performed by the TSCTSF, PCF or RAN in the illustrated method embodiment in any one of the illustrated embodiments.
[0300] Optionally, the device 1400 may include one or more memories 1420 on which programs (sometimes also referred to as codes or instructions) are stored. The programs can be run on the processor 1410, so that the device 1400 executes the method performed by the TSCTSF, PCF or RAN in the above embodiments.
[0301] Optionally, the processor 1410 and / or the memory 1420 may include an artificial intelligence (AI) module, and the AI module is used to implement AI-related functions. The AI module may be implemented by software, hardware, or a combination of software and hardware. For example, the AI module may include a wireless intelligent controller (RIC) module. For example, the AI module may be a near real-time RIC or a non-real-time RIC.
[0302] Optionally, data may also be stored in the processor 1410 and / or the memory 1420. The processor and the memory may be provided separately or integrated together.
[0303] Optionally, the device 1400 may further include a communication interface 1430. The processor 1410 may also be sometimes referred to as a processing unit, which controls the device (e.g., TSCTSF, PCF, or RAN). The communication interface 1430 may also be sometimes referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which is used to implement the transceiver function of the device.
[0304] Optionally, the device 1400 further includes a communication interface 1430. The processor 1410 and the communication interface 1430 are coupled to each other. It can be understood that the communication interface 1430 can be a transceiver or an input-output interface.
[0305] When the device 1400 is used to implement Fig. 9 When the method is used, the processor 1410 is used to execute the functions of the above processing unit, and the communication interface 1430 is used to execute the functions of the above transceiver module. Whether the communication interface 1430 is used to send or receive can be determined by whether it is used to perform a sending action or a receiving action in the solution executed by the device 1400.
[0306] When the above device 1400 is a chip applied to TSCTSF, the chip implements the functions of TSCTSF in the above method embodiment. The chip of TSCTSF receives signals from other modules in TSCTSF, and the signals may be sent from AF or NEF to TSCTSF; or the chip of TSCTSF sends signals to other modules in TSCTSF, and the signals may be sent from TSCTSF to PCF.
[0307] When the above device 1400 is a chip applied to PCF, the chip implements the functions of PCF in the above method embodiment. The chip of the PCF receives signals from other modules in the PCF, and the signals may be sent from AF / NEF / TSCTSF to the PCF; or the chip of the PCF sends signals to other modules in the PCF, and the signals may be sent from the PCF to the SMF.
[0308] When the above device 1400 is a chip applied to RAN, the chip implements the functions of RAN in the above method embodiment. The chip of the RAN receives signals from other modules in the RAN, and the signals may be sent to the RAN by the SMF; or the chip of the RAN sends signals to other modules in the RAN (such as a radio frequency module or an antenna), and the signals may be sent to the terminal by the RAN.
[0309] It can be understood that when the device 1400 is a TSCTSF, PCF or RAN, the communication interface 1430 can be a transceiver, which can specifically include a transmitter and a receiver, the transmitter is used to send signals, and the receiver is used to receive signals. When the device 1400 is a chip applied to the TSCTSF, PCF or RAN, the communication interface 1430 can be an input and output circuit, wherein the input circuit can be used for receiving, and the output interface can be used for sending.
[0310] It should be noted that the above method embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
[0311] The processor may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component or any combination thereof. The general purpose processor may be a microprocessor or any conventional processor.
[0312] The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0313] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0314] The method provided in the above embodiment can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital user (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state hard disk (SSD)), etc.
[0315] The present application also provides a computer-readable medium on which a computer program is stored. When the computer program is executed by a computer, the function of the TSCTSF, PCF or RAN in any of the above method embodiments is implemented.
[0316] The present application also provides a computer program product, which, when executed by a computer, implements the functions of TSCTSF, PCF or RAN in any of the above method embodiments.
[0317] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0318] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0319] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0320] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0321] 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 separately, or two or more units may be integrated into one unit.
[0322] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.
[0323] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be covered by the protection scope of the present application.
Claims
1. A communication method, It is characterized in that include: Acquire a delay parameter of a first service, where the delay parameter is related to a delay requirement, a packet delay budget (PDB) requirement, or a PDB, and the first service is a non-periodic service; Based on the delay parameter, a configuration period of transmission resources is determined, and the transmission resources are used to transmit data packets of the first service.
2. The method according to claim 1, It is characterized in that The method is applied to a time-sensitive communication time synchronization function TSCTSF, and the delay parameter is the delay requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from an application function AF or a network opening function NEF, where the first request message indicates the delay requirement.
3. The method according to claim 2, It is characterized in that The sum of the configuration period and the PDB requirement is less than or equal to the delay requirement, and the method further includes: Based on the latency requirement, determining the PDB requirement; A second request message is sent to a policy control function PCF, where the second request message indicates the configuration period and the PDB requirement.
4. The method according to claim 3, It is characterized in that The PDB requirement satisfies: the PDB requirement = the delay requirement - the time length for the terminal to process a data packet.
5. The method according to claim 1, It is characterized in that The method is applied to PCF, and the delay parameter is the PDB requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from one of the following network elements, where the first request message indicates a PDB requirement for the first service: TSCTSF, AF, NEF.
6. The method according to claim 1, It is characterized in that The method is applied to PCF, and the delay parameter is the delay requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from one of the following network elements, where the first request message indicates a delay requirement of the first service: AF, NEF.
7. The method according to claim 5 or 6, It is characterized in that The sum of the configuration period and the PDB is less than or equal to the PDB requirement, and the method further includes: Determine the PDB based on the first request message; First information is sent to a session management function SMF, where the first information indicates the configuration period and the PDB.
8. The method according to any one of claims 2 to 7, It is characterized in that The configuration period is determined when at least one of the following conditions is met: The delay requirement is less than or equal to a first preset threshold; The PDB requirement is less than or equal to a second preset threshold; The network name DNN is the first value; The single network slice selection auxiliary information S-NSSAI is a second value; or, The first request message does not include a period of the first service.
9. The method according to any one of claims 2 to 8, It is characterized in that The method further comprises: Generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; The instruction information is sent.
10. The method according to claim 9, It is characterized in that The indication information is determined when at least one of the following is satisfied: The delay requirement is less than or equal to a first preset threshold; The PDB requirement is less than or equal to a second preset threshold; DNN is the first value; S-NSSAI is the second value; or, The first request message does not include a period of the first service.
11. The method according to any one of claims 1 to 10, It is characterized in that The method further comprises: Obtaining scheduling status information from a radio access network RAN; The determining, based on the delay parameter, a configuration period of the transmission resource includes: The configuration period is determined based on the delay parameter and the scheduling status information.
12. The method according to any one of claims 1 to 10, It is characterized in that The method further comprises: receiving an expected value of the configuration cycle from the RAN; Based on the delay parameter and the expected value, multiple values or value ranges of the configuration period are determined.
13. The method according to claim 1, It is characterized in that The method is applied to RAN, the delay parameter is the PDB authorized by the PCF for the first service based on the PDB requirement; The obtaining of the delay parameter of the first service includes: Receive the PDB from the SMF.
14. The method according to claim 13, It is characterized in that Before determining the configuration period of the transmission resource based on the delay parameter, the method further includes: receiving instruction information; Based on the indication information and the PDB, an access network AN PDB is determined.
15. The method according to claim 13 or 14, It is characterized in that The method further comprises: Acquire a data packet of the first service; The data packet is transmitted using the transmission resources that were most recently configured.
16. A communication method, It is characterized in that Applied to the policy control function PCF, the method comprises: receiving a second request message, where the second request message indicates a configuration period and a packet delay budget (PDB) requirement of a transmission resource, where the transmission resource is used to transmit a data packet of a first service, where the first service is a non-periodic service; Determining a PDB, the PDB being less than or equal to the PDB requirement; First information is sent to a session management function SMF, where the first information indicates the PDB and the configuration period.
17. The method according to claim 16, It is characterized in that The method further comprises: Indication information is received, where the indication information indicates that the first service is a non-periodic service.
18. The method according to claim 16, It is characterized in that Determining the PDB comprises: The PDB is determined based on at least one of: the PDB requirement, the DNN, or the S-NSSAI.
19. A communication device, It is characterized in that Comprising means for implementing the method as claimed in any one of claims 1 to 18.
20. A communication device, It is characterized in that The device comprises a processor configured to cause the communication device to implement the method according to any one of claims 1 to 18 by executing a computer program and / or a logic circuit.
21. The device according to claim 20, It is characterized in that The system also includes a memory for storing a computer program and / or a configuration file of the logic circuit.
22. The device according to claim 20 or 21, It is characterized in that A communication interface is also included for inputting and / or outputting signals.
23. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 18 is performed.
24. A computer program product, It is characterized in that The invention comprises a computer program which, when being executed, implements the method according to any one of claims 1 to 18.
