Air interface configuration method and related apparatus

Abstract

Provided in the embodiments of the present application are an air interface configuration method and a related apparatus. The method is applied to a first device, and the method comprises: acquiring instance information of a deterministic network, wherein the instance information comprises one or more of a period cycle start time, a period length, an edge shaping configuration and a link rate of the deterministic network; and generating an air interface configuration of a network device on the basis of information of a physical resource block (PRB) of the network device, and the instance information, wherein the air interface configuration comprises one or more of an uplink / downlink transmission period size, a downlink slot start time, an uplink slot end time and an uplink / downlink slot resource configuration of an air interface. By means of the embodiments of the present application, an end station configuration (such as an air interface configuration) can be performed in a communication system formed by introducing a deterministic network (such as a DIP transport network) into a wireless communication architecture (such as a 5G system).

Description

Air interface configuration method and related devices

[0001] This application claims priority to Chinese Patent Application No. 202410928415.9, filed on July 10, 2024, entitled "Air Interface Configuration Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to air interface configuration methods and related devices. Background Technology

[0003] The system architecture of wireless communication networks (such as 5G) is divided into two parts: the access network and the core network. It mainly includes the following key logical network elements: Radio Access Network (RAN), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), User Data Management (UDM), Unified Data Repository (UDR), Application Function (AF), Data Network (DN), etc. As shown in Figure 1, among which:

[0004] RAN is a device that provides wireless access for terminal devices (such as mobile phones, IoT terminal devices, etc.), including but not limited to evolved Node B (eNodeB), Wi-Fi access point (AP), and Worldwide Interoperability for Microwave Access (WiMAX) base station (BS).

[0005] AMF is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0006] SMF is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider for Forwarding) to provide packet forwarding capabilities.

[0007] PCF is responsible for providing policies to AMF and SMF, such as slice selection policies and Quality of Service (QoS) policies.

[0008] UDM is used to store user data, such as subscription information and authentication / authorization information. Optionally, it may also include UDR, which provides storage capabilities for subscription data, policy data, and capability-related data.

[0009] The AF is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0010] UPF is primarily responsible for processing user messages, such as forwarding and billing.

[0011] DN is a carrier network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet.

[0012] NSSF (Network Slice Selection Function) provides the ability to select network slices.

[0013] AUSF (Authentication Service Function) is responsible for authenticating users' access to the 5G network.

[0014] UDM (Unified Data Management) is used for user contract management, access authorization, and authentication information generation.

[0015] The main function of NSACF (Network Slice Access Control) is to monitor and control the number of user equipment (UE) registered on each network slice, as well as the number of PDU (Protocol Data Unit) sessions established on each network slice.

[0016] NSSAAF (Network Slicing and SNPN (Standard Non-Public Network) authentication and authorization function) is used to authenticate devices requesting access to a network slice and determine whether they are authorized to access the slice. Terminal devices (such as UEs) establish a PDU session between the terminal device and the RAN, then to the UPF, and finally to the DN to access the DN.

[0017] Those skilled in the art are attempting to introduce deterministic networks into wireless communication architectures, such as configuring a deterministic network between the RAN and UPF. How to configure end stations after introducing deterministic networks into wireless communication architectures is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0018] This application discloses an air interface configuration method and related apparatus, which enables terminal station configuration in a communication system formed after introducing a deterministic network (such as a DIP transmission network) into a wireless communication architecture (such as a 5G system).

[0019] In a first aspect, embodiments of this application provide an air interface configuration method, which is applied to a first device, and the method includes:

[0020] Obtain instance information of a deterministic network, wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network;

[0021] The air interface configuration of the network device is generated based on the instance information, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0022] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0023] In conjunction with the first aspect, in one possible implementation of the first aspect, obtaining instance information of the deterministic network includes:

[0024] Send an instance request message, wherein the instance request message is used to request instance information of the deterministic network;

[0025] Receive instance information of the deterministic network from functional devices in the deterministic network.

[0026] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the functional device includes a control plane function (CPF).

[0027] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the first device includes the network device; the sending of the instance request message includes:

[0028] The instance request message is sent to the edge node of the deterministic network, wherein the instance request message is specifically used by the edge node to request instance information of the deterministic network from a functional device in the deterministic network.

[0029] In conjunction with the first aspect, or any of the above-mentioned possible implementations of the first aspect, another possible implementation of the first aspect further includes:

[0030] Perform the air interface configuration.

[0031] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the first device includes OAM; the sending of the instance request message includes:

[0032] The instance request message is sent to the functional devices in the deterministic network.

[0033] In conjunction with the first aspect, or any of the above-mentioned possible implementations of the first aspect, another possible implementation of the first aspect further includes:

[0034] Receive an air interface configuration request from the network device, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes information about the network device's PRB.

[0035] In conjunction with the first aspect, or any of the above-mentioned possible implementations of the first aspect, another possible implementation of the first aspect further includes:

[0036] Send the air interface configuration to the network device.

[0037] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the uplink time slot end time is obtained as a relative time offset derived from the periodic cycle start time of the deterministic network.

[0038] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the instance information further includes the link delay between the network device and the edge node of the deterministic network, and the parameter for deriving the relative time offset further includes the link delay.

[0039] In conjunction with the first aspect, or any of the possible implementations of the first aspect described above, in yet another possible implementation of the first aspect, the downlink time slot start time is obtained as a relative time offset derived from the cycle start time of the deterministic network and the shaping window in the edge shaping configuration. Optionally, the instance information further includes the link delay between the network device and the edge node of the deterministic network, and the parameter for deriving the relative time offset further includes the link delay.

[0040] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the uplink and downlink transmission cycle size is determined based on the cycle length of the deterministic network and the shaping window in the edge shaping configuration.

[0041] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the uplink and downlink time slot resource configuration is determined by the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic network cycle and the number of uplink PRBs required for the maximum uplink data volume that can be forwarded in one deterministic network cycle. The number of downlink PRBs and the number of uplink PRBs are calculated based on the edge shaping configuration, the link rate, and the PRB information of the network device.

[0042] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the edge shaping configuration includes a shaping rate and / or a shaping window configuration.

[0043] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, generating the air interface configuration of the network device based on the instance information includes:

[0044] The air interface configuration of the network device is generated based on the information of the physical resource block (PRB) of the network device and the instance information.

[0045] Secondly, embodiments of this application provide an air interface configuration method, which is applied to a network device, the method comprising:

[0046] Send an air interface configuration request to OAM, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes the PRB information of the network device;

[0047] The system receives the air interface configuration sent by the OAM, wherein the air interface configuration is generated based on the PRB information of the network device and the instance information of the deterministic network. The instance information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network. The air interface configuration includes one or more of the following: the transmission cycle size of the air interface, the downlink time slot start time, the uplink time slot end time, and the uplink and downlink time slot resource configuration.

[0048] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0049] Thirdly, embodiments of this application provide an air interface configuration method, which is applied to edge nodes of a deterministic network, the method comprising:

[0050] Receive an instance request message from a network device, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network;

[0051] Send the instance request message to the functional devices in the deterministic network;

[0052] Receive instance information of the deterministic network from the functional device;

[0053] The embodiment information is sent to the functional device, wherein the embodiment information is used to generate the air interface configuration of the network device.

[0054] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0055] Fourthly, embodiments of this application provide an air interface configuration method, which is applied to functional devices in a deterministic network, the method comprising:

[0056] Receive an instance request message, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network;

[0057] Send instance information of the deterministic network, wherein the instance information is used to generate the air interface configuration of the network device, and the air interface configuration includes one or more of the following: air interface transmission period size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0058] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0059] Fifthly, embodiments of this application provide a communication device, which can be a first device or a component or functional module within the first device, wherein:

[0060] The communication device includes a module for performing the method described in the first aspect or any possible implementation thereof;

[0061] Alternatively, the communication device includes a processor for performing the method described in the first aspect or any possible implementation thereof.

[0062] Sixthly, embodiments of this application provide a communication device, which can be a network device or a device or functional module within a network device, wherein:

[0063] The communication device includes a module for performing the method described in the second aspect or any possible implementation thereof;

[0064] Alternatively, the communication device includes a processor for performing the method described in the second aspect or any possible implementation thereof.

[0065] In a seventh aspect, embodiments of this application provide a communication device, which can be an edge node or a device or functional module within an edge node, wherein:

[0066] The communication device includes a module for performing the method described in the third aspect or any possible implementation of the third aspect;

[0067] Alternatively, the communication device includes a processor for performing the method described in the third aspect or any possible implementation thereof.

[0068] Eighthly, embodiments of this application provide a communication device, which can be a functional device or a component or module within a functional device, wherein:

[0069] The communication device includes a module for performing the method described in the fourth aspect or any possible implementation of the fourth aspect;

[0070] Alternatively, the communication device includes a processor for performing the method described in the fourth aspect or any possible implementation thereof.

[0071] Ninthly, embodiments of this application provide a communication device, characterized in that it includes a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, wherein:

[0072] The logic circuit is used to perform the method described in the first aspect or any possible implementation thereof, or...

[0073] The logic circuit is used to execute the method described in the second aspect or any possible implementation thereof, or...

[0074] The logic circuit is used to execute the method described in the third aspect or any possible implementation thereof, or...

[0075] The logic circuit is used to perform the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0076] Tenthly, embodiments of this application provide a computer-readable storage medium for storing a computer program, wherein:

[0077] When the computer program is executed, it is capable of implementing the first aspect or any possible implementation of the first aspect, or...

[0078] When the computer program is executed, it is capable of implementing the second aspect or any possible implementation of the second aspect, or...

[0079] When the computer program is executed, it is capable of implementing the third aspect or any possible implementation of the third aspect, or...

[0080] When the computer program is executed, it is capable of implementing the fourth aspect or any possible implementation of the fourth aspect.

[0081] Eleventhly, embodiments of this application provide a communication system, which includes a first device and other devices, wherein the other devices include network devices, edge nodes, and at least two devices in OAM, wherein:

[0082] The first device is used to perform the method described in the first aspect or any possible implementation thereof;

[0083] The network device is configured to perform the method described in the second aspect or any possible implementation thereof; or...

[0084] The edge node is used to execute the method described in the third aspect or any possible implementation thereof; or...

[0085] The OAM is used to perform the method described in the fourth aspect or any possible implementation of the fourth aspect. Attached Figure Description

[0086] The accompanying drawings used in the embodiments of this application are described below.

[0087] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0088] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0089] Figure 3 is a flowchart illustrating a terminal configuration method provided in an embodiment of this application;

[0090] Figure 4A is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0091] Figure 4B is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0092] Figure 5 is a schematic diagram of a DIP transmission network provided in an embodiment of this application;

[0093] Figure 6 is a flowchart illustrating an air interface configuration method provided in an embodiment of this application;

[0094] Figure 7 is a schematic diagram illustrating the principle of obtaining instance information according to an embodiment of this application;

[0095] Figure 8 is a schematic diagram of the periodic relationship between a RAN and a DIP transmission network provided in an embodiment of this application;

[0096] Figure 9 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0097] Figure 10 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0098] Figure 11 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0099] Figure 12 is a schematic diagram of a link latency scenario provided by an embodiment of this application;

[0100] Figure 13 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0101] Figure 14 is a flowchart illustrating an air interface configuration method provided in an embodiment of this application;

[0102] Figure 15 is a flowchart illustrating another air interface configuration method provided in an embodiment of this application;

[0103] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0104] Figure 17 is a schematic diagram of another communication device provided in an embodiment of this application;

[0105] Figure 18 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. Detailed Implementation

[0106] The embodiments of this application are described below with reference to the accompanying drawings.

[0107] Explanation of relevant concepts:

[0108] Deterministic IP (DIP): Explicit routing can be achieved through SRv6, and its network identifier (SID) can be used to identify the DIP transmission path planned at the node level.

[0109] Cycle length: refers to the duration of one DIP forwarding cycle;

[0110] Cycle count: refers to the maximum number of cycle counts supported by a DIP instance. For example, the Tagged Cyclic Queuing and Forwarding (TCQF) mechanism supports 3 or more cycle alternations.

[0111] DIP ingress edge node: can perform edge shaping on the service flow and distribute data packets to different DIP cycles for transmission.

[0112] DIP instances provide deterministic QoS guarantees for service flows, such as latency and jitter. Each instance has its own configuration information. A DIP transport network can have one or more instances, each instance can be a subnet, and each instance has its own configuration information.

[0113] Link speed: refers to the link speed that a DIP instance can provide for the transmission of service flow data packets, which generally corresponds to the interface speed of the DIP instance interface.

[0114] Please refer to Figure 2, which is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. This communication system introduces Time-Sensitive Networking (TSN) into cellular networks, such as 5G systems (5GS), i.e., the 5GS transmission network supports TSN.

[0115] The communication system includes UE201, RAN202, AMF203, SMF204, PCF205, AF206, CNC207, UPF208, DN209, TSN transmission network 210, etc., among which:

[0116] UE201 can be a mobile phone, IoT terminal device, etc.

[0117] RAN202 is a device that provides wireless access for terminal devices (such as mobile phones, IoT terminal devices, etc.), including but not limited to evolved Node B (eNodeB), Wi-Fi access point (AP), and Worldwide Interoperability for Microwave Access (WiMAX) base station (BS).

[0118] The AMF203 is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0119] The SMF / Centralized User Configuration (CUC) 204 is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding capabilities.

[0120] PCF205 is responsible for providing policies to AMF and SMF, such as slice selection policies and Quality of Service (QoS) policies.

[0121] TSN AF / TSCTSF206 is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0122] UPF208 is primarily responsible for processing user messages, such as forwarding and billing.

[0123] DN209 is an operator network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet.

[0124] To support the determinism of the 5GS transport network, the RAN and UPF can be configured as end users in the deterministic protocol and talkers and listeners in the TSN transport network 210, respectively. The SMF can act as the CUC or the CUC function can be merged with the SMF. The SMF provides user / network configuration information (Talker Group & Listener Group) to the CNC in the TN, also known as the merged flow requirements. The CNC provides the SMF with state group information containing end-station communication configurations.

[0125] Figure 3 illustrates a terminal station configuration method, which can be implemented based on the architecture shown in Figure 2. Taking the RAN supporting Access Network-Talker and Listener (AN-TL) functionality and the UPF supporting Core Network-Talker and Listener (CN-TL) functionality as an example, the method includes, but is not limited to, the following steps:

[0126] Step 1: RAN AN-TL initiates the Protocol Data Unit (PDU) session establishment process.

[0127] Step 2: The SMF's CUC interacts with the UPF's CN-TL to establish / modify the N4 session.

[0128] Step 3: The RAN's AN-TL interacts with the SMF's CUC to obtain N2 session information. Therefore, through steps 2 and 3, the SMF / CUC can obtain relevant information about the Talker or Listener group from the AN-TL or CN-TL.

[0129] Step 4: AF or TSCTSF sends a request to reserve resources for the AF session.

[0130] Step 5: The RAN's AN-TL initiates the PDU session modification process.

[0131] Step 6: The SMF's CUC interacts with the PCF to modify the session policy association.

[0132] Step 7: The SMF's CUC interacts with the UPF's CN-TL to modify the N4 session.

[0133] Step 8: The RAN's AN-TL interacts with the SMF's CUC to obtain new N2 session information.

[0134] Step 9: The SMF / CUC provides QoS-based flow requirements to the TN CNC through the User / Network Interface (UNI). The TN CNC uses the flow requirements as input to configure the corresponding paths and scheduling in the TN.

[0135] Step 10: The TN CNC feeds back a status group containing the end station communication configuration (also known as the merged end station communication-configuration) to the SMF / CUC.

[0136] Step 11: The RAN's AN-TL initiates the PDU session modification process.

[0137] Step 12: The SMF's CUC interacts with the UPF's CN-TL to modify the N4 session.

[0138] Step 13: The RAN's AN-TL interacts with the SMF's CUC to obtain new N2 session information. During the execution of steps 12 and 13, the SMF / CUC sends relevant information about the status group to the AN-TL or CN-TL, that is, sends the End Station configuration to the RAN and UPF. Subsequently, the RAN and UPF perform end station configuration according to the End Station configuration.

[0139] Please refer to Figures 4A and 4B. Figures 4A and 4B are schematic diagrams of the architecture of two communication systems provided in the embodiments of this application. These two communication systems introduce deterministic IP (DIP) networks into cellular networks, such as 5G systems (5GS), that is, the 5GS transmission network supports DIP.

[0140] The communication system includes UE401, RAN402, AMF403, SMF404, PCF405, AF406, UPF407, DN408, OAM409, and edge node 410, among which:

[0141] User equipment (UE) 401 can be such as mobile phones, Internet of Things (IoT) terminal devices, etc.

[0142] RAN402 is a device that provides radio access for UEs, including but not limited to evolved Node B (eNodeB), Wi-Fi access point (AP), and Worldwide Interoperability for Microwave Access (WiMAX) base station (BS).

[0143] The AMF403 is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0144] The SMF404 is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Packet Forwarder) to provide packet forwarding capabilities.

[0145] PCF405 is responsible for providing policies to AMF and SMF, such as slice selection policies and Quality of Service (QoS) policies.

[0146] AF406 is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0147] The UPF407 is primarily responsible for processing user messages, such as forwarding and billing.

[0148] DN408 is a carrier network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet.

[0149] Operations, Administration and Maintenance (OAM) 409: The network administrator responsible for the operation, administration and maintenance of each RAN (and its associated systems).

[0150] Edge node 410 refers to a network node located at the edge of the DIP transmission network, which is responsible for performing edge shaping and forwarding, flow control and other functions of the DIP transmission network.

[0151] It should be noted that the mapping in SMF, RAN, and UPF refers to the parameter mapping between 5GS and DIP transport network to support the interoperability of the two technical architectures. It can map 5GS parameters to corresponding parameters in DIP transport network or vice versa.

[0152] The system shown in Figure 4A is a distributed architecture. The CPF is located in the edge node of the DIP transport network. Therefore, it can either provide DIP transport network information (such as instance information) directly to the RAN through the edge node, and let the RAN generate the required configuration (such as air interface configuration) itself, or provide the DIP transport network information to the OAM and let the OAM generate the part of the configuration required by the RAN.

[0153] The system shown in Figure 4B is a centralized architecture. The CPF is located in the DetNet Controller (centralized controller) of the DIP transport network. Therefore, it can either forward DIP transport network information (such as instance information) to the RAN through edge nodes, and let the RAN generate the required configuration (such as air interface configuration) itself, or provide the DIP transport network information to the OAM and let the OAM generate the part of the configuration required by the RAN.

[0154] As can be seen, the deployment location of CPF differs between the architecture shown in Figure 4A and the architecture shown in Figure 4B.

[0155] Optionally, the CPF in a DIP transport network may include the network management of the DIP transport network.

[0156] A DIP transport network typically contains multiple instances, each of which can be a subnet. Different instances usually have their own instance information. For example, DIP instance 1, DIP instance 2, and DIP instance 3 in Figures 4A and 4B can be different instances in different DIP transport networks, each with its own instance information. Optionally, a DIP transport network may also have only one instance, i.e., only one instance information.

[0157] DIP (DetNet In-Place) transport network is a DetNet technology architecture. Figure 5 illustrates the technical principle of DIP transport network. It introduces a periodic scheduling mechanism for forwarding on the data plane and proposes efficient path planning and resource allocation algorithms on the control plane, aiming to achieve a large-scale, scalable, end-to-end deterministic low-latency network system. DIP transport network has the following characteristics: a) It does not allow arbitrary sending (receiving) of data packets, allocating a specific sending (receiving) time period for each data packet, thereby avoiding bursts, queuing delays within control nodes, and eliminating long-tail effects; b) It adopts a periodic shaping and scheduling mechanism, thereby forming isolation between periods and avoiding micro-bursts and their hop-by-hop accumulation; c) The upper bound of the system's end-to-end latency and the upper limit of jitter are determined. Specifically, DIP has the following main functions: 1) Implementing admission control on the control plane: The control plane of the ingress edge node can record the resource reservation status of each flow. Based on the resource reservation results, the ingress edge node can decide whether a deterministic flow is allowed to enter the network for deterministic forwarding. The resource reservation status of the data flow can be dynamically refreshed to achieve resource reservation renewal. 2) Path planning and resource reservation at the control plane: Deterministic path planning for data stream transmission is implemented, based on distributed routing algorithms or centralized path calculation, to plan transmission paths for data streams and support pre-reservation of necessary deterministic resources along the route. 3) Path binding at the data plane: Resource reservation for DIP transmission is reflected at the nodes of the data forwarding path; subsequent data packet transmissions need to be bound to this path; path binding technology can be coupled with label carrying technology. 4) Deterministic periodic forwarding at the data plane: Ingress edge nodes embed a time period number into the data packet based on the time it is sent. After receiving the packet, intermediate nodes perform deterministic periodic forwarding according to the period mapping, ensuring that the data packet carries a local time period number when it is sent, until the data packet reaches the egress edge node.

[0158] The specific implementation mechanisms of DIP transmission networks include Tagged Cyclic Queuing and Forwarding (TCQF) and Cycle Specified Queuing and Forwarding (CSQF), among others:

[0159] a) TCQF supports more than two cycles, indicating the cycle number through an existing or new packet header field called a tag, replacing the cycle mapping in TSN's purely synchronous receive clock-based Cyclic Queuing Forwarding (CQF) (the cyclic mapping is calculated by the controller plane, taking into account link, intra-node forwarding delays, and cycle clock offsets). The TCQF option helps the receiving port identify the time period from which packets are sent from the upstream router; it can be used to determine the output port cycle buffer for queuing packets. The target advantages of TCQF include low end-to-end jitter, ease of high-speed hardware implementation, the optional ability to support a large number of flows in large networks by applying TCQF to deterministic network DetNet() aggregations instead of applying it individually to each DetNet flow (via DiffServ-style aggregation), and support for wide-area DetNet networks with arbitrary link delays and delay variations, and low-precision clock synchronization.

[0160] b) CSQF improves upon CQF by explicitly specifying the transmission period of each node along the path (using SR segment identifiers (SIDs)), enabling end-to-end bounded latency. SR is a source routing technique that does not maintain per-flow status at intermediate and egress nodes. SR-based CSQF supports flow aggregation, which is beneficial for scaling to macro networks. CSQF defines a new field, Cycle Segment, to identify cycle periods. Cycle Segment identifies the interface / link and the cycle period of the interface / link. To specify which interface and cycle a packet should be transmitted to, simply append a cycle segment to the packet. By appending a list of cycle segments to a packet, not only can explicit packet routing be achieved, but the transmission period of each node along the path can also be specified without requiring per-flow status at intermediate and egress nodes.

[0161] In cellular networks (such as 5GS system transport network (5GS TN)) supporting DIP scenarios, due to the periodic forwarding characteristic of the DIP transport network, and the fact that the air interface time slot configuration of the cellular network is usually also periodic, when uplink / downlink data packets arrive at the RAN, additional waiting delays are easily introduced due to waiting for the transmission cycle of the DIP transport network edge nodes / air interface, causing backlogs. In view of this, the cellular network in this application embodiment is configured at the node level based on the DIP instance information provided by the DIP transport network to reduce the aforementioned waiting delays and optimize the use of uplink and downlink air interface resources. For ease of understanding, the air interface configuration process will be explained in detail below with reference to Figure 6.

[0162] It should be understood that, in this application, for the sake of simplicity, the name DIP is used as an example to illustrate deterministic networks (or deterministic network protocols, or deterministic network technologies, or technologies based on circular queuing and forwarding mechanisms), but this application does not limit the name of deterministic networks.

[0163] Please refer to Figure 6. Figure 6 illustrates an air interface configuration method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4A or Figure 4B. For example, the first device mentioned in this method can be a network device (such as RAN), OAM, or other network element in the architecture shown in Figure 4A or Figure 4B. The method includes, but is not limited to, the following steps:

[0164] Step S601: The first device obtains instance information of the deterministic network.

[0165] In this context, a deterministic network (such as a DIP transmission network) may have one or more subnets, each with corresponding instance information. Therefore, the instance information obtained by the first device may be one or more. When there are multiple subnets, the first device can obtain the instance information of all subnets (i.e., all instance information) or the instance information of some subnets (i.e., some instance information).

[0166] The following descriptions will be based on the deterministic network, specifically the DIP transmission network.

[0167] Each instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, link rate, etc., of the deterministic IP transport network. In addition to this information, the instance information may also include other information related to the DIP transport network, which will not be listed here.

[0168] Optionally, the cycle start time can be an absolute time; the edge shaping configuration can include one or more parameters such as shaping rate r and shaping window, where the shaping window is also called the forwarding window reserved for deterministic flow within the cycle; the link rate is also called the equivalent link speed or remaining bandwidth resources.

[0169] For ease of understanding, the parameters included in the instance information of the DIP transmission network are illustrated in Table 1 below.

[0170] Table 1

[0171] In this embodiment of the application, there may be multiple ways for the first device to obtain instance information, as illustrated below:

[0172] For example, if the first device stores the instance information itself, then the first device only needs to read the instance information from the storage location.

[0173] For example, the first device receives instance information sent by other devices. Optionally, the first device sends an instance request message, which is used to request instance information of the deterministic IP transport network. The first device can send the instance request message to a designated device or send it via broadcast. For example, when sending to a designated device, it can send the message directly to the designated device or forward it to the designated device through other relay devices. This forwarding can be transparent or after some processing. Then, the first device receives instance information of the deterministic IP transport network from functional devices in the deterministic IP transport network. Because the functional device belongs to the DIP transport network, it has the instance information of the network. For example, the functional device can be a Control Plane Function (CPF), which can be located at the edge node of the DIP transport network or in the DetNet controller. Optionally, the designated device can be a functional device in the DIP transport network or a device that has established a communication connection with the functional device. Figure 7 illustrates the process of a network device (such as a RAN) receiving instance information, using N instance information messages as an example.

[0174] Step S602: The first device generates the air interface configuration of the network device based on the instance information.

[0175] The network device can be an access network device, such as a RAN. Optionally, the network device may contain PRB information, such as the size (or specifications) of the PRB. The first device may store the network device's PRB information, or other devices may directly send or forward the network device's PRB information to the first device. For ease of understanding, the following example illustrates this:

[0176] For example, if the first device is a network device, then the first device itself stores the PRB information.

[0177] For example, if the first device is OAM, then the network device sends its PRB information directly to the first device, either by sending it directly or through other devices. It should be noted that when the first device is OAM, it can be a software entity. In this case, the first device can be understood as a logical device that can be deployed as software on the actual physical device.

[0178] As can be seen, the first device obtains the instance information of the DIP transmission network. Therefore, it further generates the air interface configuration of the network device based on the instance information. Optionally, the above-mentioned PRB information may also be used to generate the air interface configuration.

[0179] Optionally, the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0180] To facilitate understanding, the generation principles of parameters in air interface configuration will be introduced one by one below. Some parameters can be directly calculated to obtain a definite result, while others are calculated or have their range (or conditions) limited. Results within the range (or meeting the conditions) are all valid results.

[0181] Regarding the uplink and downlink transmission period size dl-UL-TransmissionPeriodicity:

[0182] Optionally, the uplink and downlink transmission cycle size is determined based on the cycle length of the deterministic IP transmission network and the shaping window in the edge shaping configuration, as illustrated below.

[0183] Case 1, when dl-UL-TransmissionPeriodicity≤DipCycleLength:

[0184] Where DipCycleLength is the cycle length of the DIP transmission network, and N is the number of instance information acquired by the first device. x DipCycleLength represents the cycle length contained in the x-th instance information out of N instance information.

[0185] When N=1, the above formula degenerates into: n*dl-UL-TransmissionPeriodicity=DipCycleLength;

[0186] Optionally, to ensure that a DIP instance simultaneously meets the configuration requirements for downlink time slot start time and uplink time slot end time, the following constraints can be added:

[0187] Among them, ShapingWindow x ShapingWindow is the integer window contained in the x-th instance information out of N instance information.

[0188] When N=1, the above formula degenerates into: m*dl-UL-TransmissionPeriodicity=ShapingWindow.

[0189] Where n and m are both positive integers, and m ≤ n.

[0190] Scenario 2, when dl-UL-TransmissionPeriodicity > DipCycleLength:

[0191] When N=1, the above formula degenerates into: dl-UL-TransmissionPeriodicity=k*DipCycleLength.

[0192] Where k is a positive integer.

[0193] Regarding the uplink slot end time UL-DipOffset:

[0194] Optionally, the uplink timeslot end time is obtained as a relative time offset derived from the periodic cycle start time DipStartTime of the deterministic IP transmission network. For example, the last uplink timeslot end time UL-DipOffset within a certain uplink / downlink transmission period (dl-UL-TransmissionPeriodicity) of the network device (such as RAN) air interface satisfies the following condition: UL-DipOffset = min 1≤x≤N {(DipStartTime x )mod(dl-UL-TransmissionPeriodicity)}

[0195] Among them, DipStartTime x DipStartTime is the cycle start time of the x-th instance information out of N instance information.

[0196] When N=1, the formula degenerates to: UL-DipOffset=(DipStartTime)mod(dl-UL-TransmissionPeriodicity)

[0197] The derivation and configuration of the uplink and downlink transmission period size dl-UL-TransmissionPeriodicity and the uplink timeslot end time UL-DipOffset can avoid the latency caused by uplink data packets waiting for scheduling. For example, this scheduling can be the air interface scheduling of uplink data packets at the UE, or the forwarding scheduling of the DIP transmission network at the RAN.

[0198] Regarding the downlink slot start time DL-DipOffset (which can be a relative time):

[0199] Optionally, the downlink timeslot start time is obtained based on the periodic cycle start time DipStartTime of the deterministic IP transmission network and the relative time offset derived from the shaping window in the edge shaping configuration. For example, the first downlink timeslot start time DL-DipOffset within a certain uplink / downlink transmission period (dl-UL-TransmissionPeriodicity) of the network device (such as RAN) air interface satisfies the following condition: DL-DipOffset = max 1≤x≤N {(DipStartTime x +ShapingWindow x )mod(dl-UL-TransmissionPeriodicity)}

[0200] Among them, DipStartTime x For the x-th instance information out of N instance information, the periodic cycle start time DipStartTime, ShapingWindow x The ShapingWindow is the integer window contained in the information of the xth instance.

[0201] When N=1, the formula degenerates into:

[0202] DL-DipOffset=(DipStartTime+ShapingWindow)mod(dl-UL-TransmissionPeriodicity)

[0203] The derivation and configuration of the uplink and downlink transmission period size dl-UL-TransmissionPeriodicity and the downlink timeslot start time DL-DipOffset can avoid the latency caused by downlink data packets waiting for scheduling. For example, this scheduling can be the air interface scheduling of downlink data packets at the RAN.

[0204] In the embodiments of this application, DL-DipOffset and DL-DipOffset are both derived time offsets. In some cases, they are used as the downlink time slot start time and the uplink time slot end time, respectively. It should be understood that in some cases, these parameters can be processed accordingly to derive the downlink time slot start time and the uplink time slot end time.

[0205] To better understand the solution of this application embodiment, the effect of the air interface configuration parameters generated above is illustrated below with reference to the accompanying drawings.

[0206] Figure 8 illustrates, using an example of a DIP transmission network with N=1 instance information, that the last uplink time slot within a certain uplink / downlink transmission cycle dl-UL-TransmissionPeriodicity of the network device (such as RAN) air interface ends at UL-DipOffset, and dl-UL-TransmissionPeriodicity≤DipCycleLength, specifically the case of 4*dl-UL-TransmissionPeriodicity=DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 1:2.

[0207] Figure 9 illustrates, using an example of a DIP transmission network with N=1 instance information, that the first downlink time slot in a certain uplink / downlink transmission cycle dl-UL-TransmissionPeriodicity of the network device (such as RAN) air interface starts at DL-DipOffset, and dl-UL-TransmissionPeriodicity≤DipCycleLength, specifically the case of 4*dl-UL-TransmissionPeriodicity=DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 1:2.

[0208] Figure 10 illustrates a DIP transmission network with N=1 instance information as an example. It shows that the last uplink time slot in a certain uplink-downlink transmission period dl-UL-TransmissionPeriodicity of the network device (such as RAN) ends at UL-DipOffset, and the first downlink time slot in the same uplink-downlink transmission period dl-UL-TransmissionPeriodicity starts at DL-DipOffset. Furthermore, dl-UL-TransmissionPeriodicity ≤ DipCycleLength, specifically 3*dl-UL-TransmissionPeriodicity = DipCycleLength and 2*dl-UL-TransmissionPeriodicity = ShapingWindow. In this case, the downlink (DL) and uplink (UL) time slot ratio is 1:3, and both uplink and downlink are matched.

[0209] Figure 11 illustrates the case where the number of instance information N=1 in a DIP transmission network. It shows that the last uplink time slot in a certain uplink-downlink transmission cycle dl-UL-TransmissionPeriodicity of the network device (such as RAN) air interface ends at UL-DipOffset, and dl-UL-TransmissionPeriodicity>DipCycleLength. Specifically, dl-UL-TransmissionPeriodicity=4*DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 4:2.

[0210] In one optional scheme, when the edge node of the DIP transport network is separated from the network device (such as RAN), as shown in Figure 12, the impact of the link delay Delay_EdgeNode2RAN between the edge node and the network device on the air interface configuration can be further considered. For example, the uplink timeslot end time is obtained by deriving a relative time offset based on the cycle start time of the deterministic IP transport network. The parameters for deriving the relative time offset also include the link delay Delay_EdgeNode2RAN between the network device and the edge node of the deterministic IP transport network, as detailed below:

[0211] (1) When deploying the network, the link length between the edge node and the network device (such as RAN) is configured to be very short compared to the total link length between the network device and the functional device (such as UPF). Therefore, the link delay Delay_EdgeNode2RAN between the edge node and the network device can be ignored at this time. In fact, the time when the last data packet in the ShapingWindow is sent out is difficult to align with the end time of the ShapingWindow, that is, there is a time surplus (guard band). The remaining window time eliminates part of the link delay impact.

[0212] (2) The above example information can also include link delay Delay_EdgeNode2RAN. Accordingly, the formulas for calculating the uplink slot end time UL-DipOffset and the downlink slot start time DL-DipOffset can be optimized, as follows:

[0213] The formula for calculating the uplink slot end time UL-DipOffset is optimized to: UL-DipOffset = min 1≤x≤N {(DipStartTime x -Delay_EdgeNode2RAN x)mod(dl-UL -TransmissionPeriodicity)}

[0214] The formula for calculating the downlink slot start time DL-DipOffset is optimized to: DL-DipOffset = max 1≤x≤N {(DipStartTime x +ShapingWindow x +Delay_EdgeNode2RAN x )mod(dl -UL-TransmissionPeriodicity)}

[0215] Among them, Delay_EdgeNode2RAN x Delay_EdgeNode2RAN is the link delay between the network device (e.g., RAN) and the functional device (e.g., UPF) contained in the x-th instance information out of N instance information.

[0216] Figure 13 illustrates the case where the number of instance information N=1 in a DIP transmission network, and the last uplink time slot within a certain uplink and downlink transmission cycle dl-UL-TransmissionPeriodicity of the network device (such as RAN) air interface ends at UL-DipOffset, and dl-UL-TransmissionPeriodicity≤DipCycleLength, taking into account the impact of link delay Delay_EdgeNode2RAN.

[0217] Regarding the allocation of uplink and downlink time slot resources:

[0218] Optionally, the uplink and downlink time slot resource configuration is determined by the number of downlink PRBs required for the maximum amount of downlink data to arrive in one deterministic IP cycle (referred to as the number of downlink time slot resources N_DL) and the number of uplink PRBs required for the maximum amount of uplink data that can be forwarded in one DIP cycle (referred to as the number of uplink time slot resources N_UL). Optionally, the uplink and downlink time slot resource configuration of the network device's air interface can be configured according to the PRB information (such as size), edge shaping configuration (such as shaping rate, shaping window, etc.), and link rate of the network device (such as RAN). An example is given below.

[0219] For example, the number of downlink time slot resources N_DL satisfies the following relationship:

[0220] For example, the number of uplink time slot resources N_UL satisfies the following relationship:

[0221] PRB is the basic unit of data resource allocation. For example, uplink and downlink service channels (PDSCH and PUSCH) can be scheduled in units of PRBs. N_DL is the number of downlink PRBs required for the maximum amount of downlink data arriving in one DIP cycle of air interface transmission, and N_UL is the number of uplink PRBs corresponding to the maximum amount of uplink data that can be forwarded in one DIP cycle of air interface transmission. ShapingWindow x It is the integer window contained in the x-th instance information out of N instance information, r1 x It is the downlink edge shaping rate or link (or interface) rate contained in the x-th instance information, r2 x It is the uplink edge shaping rate or link (or interface) rate contained in the xth instance information.

[0222] When N=1, the formulas for calculating the number of downlink time slot resources N_DL and the number of uplink time slot resources N_UL can be degenerated into:

[0223] Optionally, after determining the number of downlink time slot resources N_DL and the number of uplink time slot resources N_UL, the uplink and downlink transmission period length (dl-UL-TransmissionPeriodicity) and the uplink and downlink time slot ratio can be configured based on parameters such as N_DL and N_UL. That is, the derivation of the number of downlink time slot resources N_DL and the number of uplink time slot resources N_UL helps to rationally configure air interface transmission resources, optimize resource utilization, and avoid data packet backlog. For example, it can prevent downlink data packets from backing up at the RAN, or prevent uplink data packets from backing up at the UE or RAN.

[0224] Optionally, if the first device is a network device, then the network device can subsequently perform communication or scheduling based on the air interface configuration, i.e., execute the air interface configuration; if the first device is not a network device, then the first device needs to send the air interface configuration directly or through other devices to the network device so that the network device can subsequently perform communication or scheduling based on the air interface configuration, i.e., execute the air interface configuration.

[0225] In the method described in Figure 6, a deterministic IP transport network is applied to the architecture of a cellular network. In this architecture, the first device obtains instance information of the deterministic IP transport network. When generating the air interface configuration of a network device (such as a RAN), the period-related information and / or resource-related information in the instance information are used as a reference to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0226] In the method shown in Figure 6, the first device covers a variety of situations. To facilitate understanding, two specific scenarios of the first device are illustrated below with reference to Figures 14 and 15, and based on this, the specific process of obtaining instance information and generating air interface configuration is described.

[0227] Please refer to Figure 14. Figure 14 illustrates an air interface configuration method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4A or Figure 4B. For example, the first device mentioned in this method is a network device (such as a RAN) in the architecture shown in Figure 4A or Figure 4B. Some concepts, operations, and logical relationships in the method shown in Figure 14 can be referred to the relevant descriptions of the embodiments shown in Figure 4A or Figure 4B. The method shown in Figure 14 includes, but is not limited to, the following steps:

[0228] Step S1401: The network device prepares to perform air interface configuration.

[0229] This step requires the preparation of the relevant parameters in advance, such as when the network device is first connected to the network; alternatively, this step may not be necessary.

[0230] Step S1402: The network device sends an instance request message to the edge node of the deterministic network.

[0231] Specifically, the instance request message is used to request instance information of the deterministic IP transport network.

[0232] Step S1403: The edge node receives the instance request message.

[0233] Specifically, the edge node analyzes the instance request message and can learn that the network device needs instance information of a deterministic network (such as a DIP transport network). However, the edge node does not have this instance information, so the edge node needs to obtain the instance information from other devices.

[0234] Step S1404: The edge node sends an instance request message to the CPF in the deterministic network.

[0235] The edge node can process the previously received instance request message to obtain a new instance request message, such as adding the edge node's address information or device identification information, and then send the new instance request message to the CPF; optionally, the edge node can also directly forward the instance request message to the CPF, which is equivalent to the instance request message being transparently transmitted at the CPF.

[0236] Step S1405: CPF receives the instance request message.

[0237] The CPF (Content Provider Function) is a functional device in deterministic networks (such as DIP transport networks) used to maintain information within the deterministic network, such as instance information for each subnet. Other devices can obtain (or request) instance information from the CPF. Since the CPF receives the instance request message from the edge node, it can send instance information for one or more subnets to the edge node, i.e., send one or more instance information messages.

[0238] Step S1406: CPF sends the instance information of the deterministic network to the edge nodes.

[0239] Step S1407: The edge node receives the instance information of the deterministic network sent by the CPF.

[0240] Step S1408: The edge node sends the instance information of the deterministic network to the network device.

[0241] Edge nodes can process the received instance information before sending it to network devices.

[0242] Alternatively, the edge node can directly send the received instance information to the network device.

[0243] It is understandable that when an edge node sends instance information to a network device, it is in response to an instance request message from the network device.

[0244] Step S1409: The network device receives the instance information of the deterministic network.

[0245] It should be noted that the specific implementation of step S1409 can be referred to the relevant description of step S601, and will not be repeated here.

[0246] Step S1410: The network device generates the air interface configuration of the network device based on the instance information.

[0247] It should be noted that the specific implementation of step S1410 can be referred to the relevant description of step S602, and will not be repeated here.

[0248] Step S1411: The network device performs air interface configuration.

[0249] Please refer to Figure 15. Figure 15 illustrates an air interface configuration method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 4A or Figure 4B. For example, the first device mentioned in this method is the OAM in the architecture shown in Figure 4A or Figure 4B. Some concepts, operations, and logical relationships in the method shown in Figure 15 can be referred to the relevant descriptions of the embodiments shown in Figure 4A or Figure 4B. The method shown in Figure 15 includes, but is not limited to, the following steps:

[0250] Step S1501: The network device sends an air interface configuration request to the OAM.

[0251] The air interface configuration request is used to request air interface configuration. The air interface configuration request includes the PRB information of the network device. The air interface configuration request may also include other information of the network device, such as the device identifier of the network device.

[0252] Step S1502: OAM receives air interface configuration request.

[0253] Based on the air interface configuration request, the OAM can learn that air interface configuration is required for the network device. Therefore, the OAM needs to obtain the relevant parameters required for air interface configuration. The PRB information of the network device mentioned earlier is one of the input parameters for air interface configuration. In addition, other input parameters are also required, such as the instance information of the deterministic network (such as the DIP transmission network). Therefore, the OAM needs to obtain this instance information.

[0254] Step S1503: OAM sends an instance request message to the CPF in the deterministic network.

[0255] Step S1504: CPF receives the instance request message sent by OAM.

[0256] The CPF (Continuous Processing Unit) is a functional device in deterministic networks (such as DIP transport networks) used to maintain information within the DIP transport network, such as instance information for each subnet. Other devices can obtain (or request) instance information from the CPF. Since the CPF receives the instance request message from the edge node, it can send instance information for one or more subnets to the edge node, i.e., send one or more instance information messages.

[0257] Step S1505: CPF sends the instance information of the deterministic network to OAM.

[0258] Step S1506: OAM receives the instance information of the deterministic network.

[0259] It should be noted that the specific implementation of step S1506 can be referred to the relevant description of step S601, and will not be repeated here.

[0260] Step S1507: OAM generates the air interface configuration of the network device based on the instance information.

[0261] It should be noted that the specific implementation of step S1507 can be referred to the relevant description of step S602, and will not be repeated here.

[0262] Step S1508: OAM sends the air interface configuration to the network device.

[0263] Specifically, OAM sends air interface configuration to network devices in response to air interface configuration requests from network devices.

[0264] Step S1509: The network device receives the air interface configuration.

[0265] Step S1510: The network device performs the air interface configuration.

[0266] The following describes the communication device provided in the embodiments of this application.

[0267] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The communication device of the embodiments of this application will be described in detail below with reference to Figures 16 to 18.

[0268] Figure 16 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 16, the communication device includes a processing module 1801 and a transceiver module 1802. The transceiver module 1802 can implement corresponding communication functions, and the processing module 1801 is used for data processing. The transceiver module 1802 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0269] In some embodiments of this application, the communication device can be used to perform the actions performed by the transmitting end in the above method embodiments. For example, the transmitting end can be the device itself or a chip or functional module configurable within the device. The transceiver module 1802 is used to perform operations related to transmitting and receiving by the transmitting end in the above method embodiments, and the processing module 1801 is used to perform operations related to processing by the transmitting end in the above method embodiments. The processing module 1801 can perform corresponding operations by calling a computer program or by performing corresponding operations through corresponding hardware circuits. The transceiver module 1802 can perform transmitting and receiving operations independently or under the control of the processing module 1801.

[0270] For example, the communication device shown in FIG16 can be a first device or a component in the first device. The processing module 1801 and the transceiver module 1802 in the communication device can respectively perform the following operations:

[0271] Processing module 1801 is used to obtain instance information of a deterministic network, wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network.

[0272] The processing module 1801 is further configured to generate the air interface configuration of the network device based on the instance information, wherein the air interface configuration includes one or more of the following: the uplink and downlink transmission cycle size of the air interface, the downlink time slot start time, the uplink time slot end time, and the uplink and downlink time slot resource configuration.

[0273] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0274] In one possible implementation, regarding the acquisition of instance information of the deterministic network, the processing module 1801 is specifically used for:

[0275] The transceiver module 1802 sends an instance request message, wherein the instance request message is used to request instance information of the deterministic network;

[0276] The transceiver module 1802 receives instance information of the deterministic network from functional devices in the deterministic network.

[0277] In yet another possible implementation, the functional device includes a control plane function (CPF).

[0278] In yet another possible implementation, the first device includes the network device; regarding the sending of the instance request message, the transceiver module 1802 is specifically used for:

[0279] The instance request message is sent to the edge node of the deterministic network, wherein the instance request message is specifically used by the edge node to request instance information of the deterministic network from a functional device in the deterministic network.

[0280] In yet another possible implementation, the processing module 1801 is further configured to:

[0281] Perform the air interface configuration.

[0282] In yet another possible implementation, the first device includes OAM; regarding the sending of the instance request message, the transceiver module 1802 is specifically used for:

[0283] The instance request message is sent to the functional devices in the deterministic network.

[0284] In yet another possible implementation, the transceiver module 1802 is further configured to:

[0285] Receive an air interface configuration request from the network device, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes information about the network device's PRB.

[0286] In yet another possible implementation, the transceiver module 1802 is further configured to:

[0287] Send the air interface configuration to the network device.

[0288] In another possible implementation, the uplink time slot end time is obtained as a relative time offset derived from the periodic cycle start time of the deterministic network.

[0289] In another possible implementation, the instance information also includes the link delay between the network device and the edge node of the deterministic network, and the parameters for deriving the relative time offset also include the link delay.

[0290] In another possible implementation, the downlink slot start time is obtained as a relative time offset derived from the periodic cycle start time of the deterministic network and the shaping window in the edge shaping configuration.

[0291] In another possible implementation, the uplink and downlink transmission cycle size is determined based on the cycle length of the deterministic network and the shaping window in the edge shaping configuration.

[0292] In another possible implementation, the uplink and downlink time slot resource configuration is determined by the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic IP cycle and the number of uplink PRBs required for the maximum uplink data volume to be forwarded in one DIP cycle. The number of downlink PRBs and the number of uplink PRBs are calculated based on the edge shaping configuration, the link rate, and the PRB information of the network device.

[0293] In another possible implementation, the edge shaping configuration includes shaping rate and / or shaping window configuration.

[0294] In another possible implementation, generating the air interface configuration of the network device based on the instance information includes:

[0295] The air interface configuration of the network device is generated based on the information of the physical resource block (PRB) of the network device and the instance information.

[0296] Reusing Figure 16, in some other embodiments of this application, for example, the communication device shown in Figure 16 can be a network device or a component in a network device, and the processing module 1801 and / or transceiver module 1802 in the communication device can respectively perform the following operations:

[0297] The transceiver module 1802 is used to send an air interface configuration request to the OAM, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes the PRB information of the network device;

[0298] The transceiver module 1802 is also used to receive the air interface configuration sent by the OAM, wherein the air interface configuration is generated based on the PRB information of the network device and the instance information of the deterministic network. The instance information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network. The air interface configuration includes one or more of the following: the transmission cycle size of the air interface, the downlink time slot start time, the uplink time slot end time, and the uplink and downlink time slot resource configuration.

[0299] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0300] Reusing Figure 16, in some other embodiments of this application, exemplaryly, the communication device shown in Figure 16 can be an edge node or a device in an edge node, and the processing module 1801 and / or transceiver module 1802 in the communication device can respectively perform the following operations:

[0301] The transceiver module 1802 is used to receive an instance request message from a network device, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network;

[0302] Transceiver module 1802 is used to send the instance request message to the functional devices in the deterministic network;

[0303] The transceiver module 1802 is used to receive instance information of a deterministic network from the functional device;

[0304] The transceiver module 1802 is used to send the embodiment information to the functional device, wherein the embodiment information is used to generate the air interface configuration of the network device.

[0305] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0306] Reusing Figure 16, in some other embodiments of this application, exemplaryly, the communication device shown in Figure 16 can be a functional device (such as a CPF) or a component within a functional device, and the processing module 1801 and / or transceiver module 1802 in the communication device can respectively perform the following operations:

[0307] The transceiver module 1802 is used to receive an instance request message, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network;

[0308] The transceiver module 1802 is used to send instance information of the deterministic network, wherein the instance information is used to generate the air interface configuration of the network device, and the air interface configuration includes one or more of the following: air interface transmission period size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0309] This method applies deterministic networks (such as deterministic IP transport networks or DIP transport networks) to the architecture of cellular networks. In this architecture, the first device obtains instance information of the deterministic network. When generating the air interface configuration (a type of end-station configuration) of network devices (such as RAN), the period-related information and / or resource-related information in the instance information are used as references to generate the period-related parameters and / or resource-related parameters in the air interface configuration, thereby optimizing the quality of service (QoS) guarantee and resource utilization.

[0310] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0311] The communication device according to the embodiments of this application has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG16 above falls within the protection scope of the embodiments of this application.

[0312] The following description is merely an example and does not limit the product form of the communication device in the embodiments of this application to this.

[0313] In one possible implementation, in the communication device shown in FIG16, the processing module 1801 may be one or more processors, and the transceiver module 1802 may be a transceiver, or the transceiver module 1802 may also be a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver may be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method may be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method may be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.

[0314] As shown in Figure 17, the communication device 190 includes one or more processors 1920 and transceivers 1910. Exemplarily, the transceiver 1910 is used to perform the functions or steps implemented by the transceiver module 1802 shown in Figure 16, and the processor 1920 is used to perform the functions or steps implemented by the processing module 1801 shown in Figure 16. Detailed descriptions of the processor 1920 and transceiver 1910 can be found in Figure 16 or the method embodiments shown above, and will not be elaborated further here.

[0315] The descriptions of the relevant steps and information in the above embodiments can be found in the descriptions of the method embodiments above, and will not be detailed here.

[0316] In various implementations of the communication device shown in Figure 17, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0317] Optionally, the communication device 190 may further include one or more memories 1930 for storing program instructions and / or data. The memory 1930 is coupled to the processor 1920. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1920 may operate in conjunction with the memory 1930. The processor 1920 may execute program instructions stored in the memory 1930. Optionally, at least one of the above-mentioned memories may be included in the processor.

[0318] This embodiment does not limit the specific connection medium between the transceiver 1910, processor 1920, and memory 1930. In Figure 17, the memory 1930, processor 1920, and transceiver 1910 are connected via a bus 1940, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 17, but this does not imply that there is only one bus or one type of bus.

[0319] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0320] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code having instruction or data structure forms, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0321] Processor 1920 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. Memory 1930 is primarily used for storing software programs and data. Transceiver 1910 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0322] When the communication device is powered on, the processor 1920 can read the software program in the memory 1930, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1920 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1920. The processor 1920 converts the baseband signal back into data and processes the data.

[0323] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0324] The communication device shown in this application embodiment may also have more components than those in Figure 17, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above.

[0325] In another possible implementation, in the communication device shown in Figure 16, the processing module 1801 can be one or more logic circuits, and the transceiver module 1802 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1802 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface. As shown in Figure 18, the communication device shown in Figure 18 includes a logic circuit 2001 and an interface 2002. That is, the processing module 1801 can be implemented using the logic circuit 2001, and the transceiver module 1802 can be implemented using the interface 2002. The logic circuit 2001 can be a chip, a processing circuit, an integrated circuit, or a system-on-a-chip (SoC) chip, etc., and the interface 2002 can be a communication interface, an input / output interface, pins, etc. For example, Figure 18 illustrates the communication device as a chip, which includes the logic circuit 2001 and the interface 2002.

[0326] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 2001 can be used to execute the functions or steps implemented by the processing module 1801 shown in FIG. 16, and the interface 2002 can be used to execute the functions or steps implemented by the transceiver module 1802 shown in FIG. 16. For a detailed description of the logic circuit 2001 and the interface 2002, please refer to FIG. 16 or the method embodiment shown above, which will not be detailed here.

[0327] The above description of the communication device is only an example. For a detailed description of the communication device shown in Figure 18, please refer to the above method embodiment or Figure 16 or Figure 17. It will not be described in detail here.

[0328] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0329] The descriptions of relevant steps and information in the above embodiments can be found in the method embodiments described above, and will not be detailed here. For the specific implementation methods of the embodiments shown in Figure 18, please also refer to the above embodiments, which will not be detailed here.

[0330] This application also provides a communication system, which includes at least two of the following: a first device, a network device, an edge node, and an OAM. The first device, network device, edge node, and OAM can be the same as those mentioned in the previous embodiments. The interaction between the at least two devices can be used to execute all or part of the steps in any of the foregoing method embodiments.

[0331] In addition, this application also provides a computer program for implementing the operations and / or processes performed by various communication devices in the method provided in this application.

[0332] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by various communication devices in the methods provided in this application.

[0333] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by various entities in the method provided in this application to be executed.

[0334] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0335] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0336] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0337] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. An air interface configuration method, characterized in that, Applied to a first device, the method includes: Obtain instance information of a deterministic network, wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network; The air interface configuration of the network device is generated based on the instance information, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

2. The method according to claim 1, characterized in that, The acquisition of instance information of the deterministic network includes: Send an instance request message, wherein the instance request message is used to request instance information of the deterministic network; Receive instance information of the deterministic network from functional devices in the deterministic network.

3. The method according to claim 2, characterized in that, The functional device includes a control plane function (CPF).

4. The method according to claim 2 or 3, characterized in that, The first device includes the network device; the sending of the instance request message includes: The instance request message is sent to the edge node of the deterministic network, wherein the instance request message is specifically used by the edge node to request instance information of the deterministic network from a functional device in the deterministic network.

5. The method according to claim 2 or 3, characterized in that, Also includes: Perform the air interface configuration.

6. The method according to claim 2 or 3, characterized in that, The first device includes OAM; sending the instance request message includes sending the instance request message to a functional device in the deterministic network.

7. The method according to claim 6, characterized in that, Also includes: Receive an air interface configuration request from the network device, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes information about the network device's PRB.

8. The method according to claim 6 or 7, characterized in that, Also includes: Send the air interface configuration to the network device.

9. The method according to any one of claims 1-8, characterized in that, The uplink time slot end time is obtained by deriving the relative time offset based on the periodic cycle start time of the deterministic network.

10. The method according to any one of claims 1-9, characterized in that, The downlink time slot start time is obtained from the relative time offset derived from the periodic cycle start time of the deterministic network and the shaping window in the edge shaping configuration.

11. The method according to claim 9 or 10, characterized in that, The instance information also includes the link delay between the network device and the edge node of the deterministic network, and the parameters for deriving the relative time offset also include the link delay.

12. The method according to any one of claims 1-11, characterized in that, The uplink and downlink transmission cycle size is determined based on the cycle length of the deterministic network and the shaping window in the edge shaping configuration.

13. The method according to any one of claims 1-12, characterized in that, The uplink and downlink time slot resource configuration is determined by the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic network cycle and the number of uplink PRBs required for the maximum uplink data volume that can be forwarded in one deterministic network cycle. The number of downlink PRBs and the number of uplink PRBs are calculated based on the edge shaping configuration, the link rate, and the PRB information of the network device.

14. The method according to any one of claims 1-13, characterized in that, The edge shaping configuration includes shaping rate and / or shaping window configuration.

15. The method according to any one of claims 1-14, characterized in that, The step of generating the air interface configuration of the network device based on the instance information includes: The air interface configuration of the network device is generated based on the information of the physical resource block (PRB) of the network device and the instance information.

16. An air interface configuration method, characterized in that, Applied to network devices, the method includes: Send an air interface configuration request to OAM, wherein the air interface configuration request is used to request air interface configuration, and the air interface configuration request includes the PRB information of the network device; The system receives the air interface configuration sent by the OAM, wherein the air interface configuration is generated based on the PRB information of the network device and the instance information of the deterministic network. The instance information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network. The air interface configuration includes one or more of the following: the transmission cycle size of the air interface, the downlink time slot start time, the uplink time slot end time, and the uplink and downlink time slot resource configuration.

17. An air interface configuration method, characterized in that, The method, applied to edge nodes of a deterministic network, includes: Receive an instance request message from a network device, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network; Send the instance request message to the functional devices in the deterministic network; Receive instance information of the deterministic network from the functional device; The embodiment information is sent to the functional device, wherein the embodiment information is used to generate the air interface configuration of the network device.

18. An air interface configuration method, characterized in that, The method, applied to a functional device in a deterministic network, includes: Receive an instance request message, wherein the instance request message is used to request instance information of a deterministic network; wherein the instance information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network; Send instance information of the deterministic network, wherein the instance information is used to generate the air interface configuration of the network device, and the air interface configuration includes one or more of the following: air interface transmission period size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

19. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-15; or, the communication device includes a processor for performing the method as described in any one of claims 1-15.

20. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 16-18; or, the communication device includes a processor for performing the method as described in any one of claims 16-18.

21. A communication device, characterized in that, Includes logic circuits and interfaces, wherein the logic circuits and interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 1-18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1-18.

23. A communication system, characterized in that, Including the first device and other devices, wherein: The first device is the first device as described in any one of claims 1-15; The other device is a network device as described in claim 16, or an edge node as described in claim 17, or a functional device as described in claim 18.

Images