WO2018059317A1 - 一种网络切片的管理方法及装置、计算机存储介质 - Google Patents

一种网络切片的管理方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2018059317A1
WO2018059317A1 PCT/CN2017/102888 CN2017102888W WO2018059317A1 WO 2018059317 A1 WO2018059317 A1 WO 2018059317A1 CN 2017102888 W CN2017102888 W CN 2017102888W WO 2018059317 A1 WO2018059317 A1 WO 2018059317A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
network element
network
configuration information
different
Prior art date
Application number
PCT/CN2017/102888
Other languages
English (en)
French (fr)
Inventor
何青春
黄河
李楠
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP17854767.5A priority Critical patent/EP3522589A4/en
Publication of WO2018059317A1 publication Critical patent/WO2018059317A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present invention relates to the field of wireless communication systems, and in particular, to a network slice management method and apparatus, and a computer storage medium.
  • the delay-insensitive user plane function includes data header compression and encryption. Integrity protection, retransmission, sender serial number maintenance and receiver ordering, automatic repeat request (ARQ, Auto Repeat reQuest), etc.; delay-sensitive user plane functions include data segmentation, string Concatenation, re-segment, reassembly, multi-logical channel multiplexing, hybrid automatic repeat request (HARQ, Hybrid Automatic Repeat reQuest), etc.
  • Network slice refers to the classification of different services into different slices, which requires that each slice independent work does not affect each other. (Refer to FIG. 3), based on this, how to realize the independent work of each slice does not affect each other is a problem to be solved.
  • an embodiment of the present invention provides a network slice management method and device, and a computer storage medium.
  • An embodiment of the present invention provides a method for managing a network slice, where the method includes:
  • the first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the slices are divided according to different radio bearers, divided according to different cells, divided according to different frequencies, or divided according to different service types, or according to different types of services.
  • the indication of the core network is divided or divided according to different physical layer characteristics.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and a radio bearer (RB), a mapping relationship between a slice and a logical channel (LCH), a mapping relationship between a slice and a physical resource or a resource pool, and a slice priority.
  • RB radio bearer
  • LCH logical channel
  • a mapping relationship between a slice and a physical resource or a resource pool a mapping relationship between a slice and a physical resource or a resource pool
  • a slice priority The quality of service level of the level, the slice, the maximum transmission rate of the slice, and the percentage of the slice occupied resources.
  • the slice configuration information is configured using a dedicated process and/or a public process.
  • the slice occupation resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the medium access control (MAC) entity in the first network element for the slice;
  • MAC medium access control
  • the slice priority is used to indicate that a MAC entity in the first network element schedules the priority of the slice data
  • the quality of service level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the quality of service level.
  • the method further includes:
  • the MAC entity in the first network element allocates corresponding physical resources to one or more slices according to the slice configuration information.
  • the multiple RBs and/or LCHs are mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the first network element performs scheduling management on each slice on the access network side according to the slice configuration information, including:
  • the MAC entity in the first network element performs centralized scheduling management on one or more slices.
  • the first network element when the first network element requests the slice configuration information from the second network element, the first network element receives the slice configuration information sent by the second network element.
  • An embodiment of the present invention provides a method for managing a network slice, where the method includes:
  • the second network element generates slice configuration information
  • the second network element sends the slice configuration information to the first network element, so that the first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the slices are divided according to different radio bearers, divided according to different cells, divided according to different frequencies, or divided according to different service types, or according to the core network.
  • the instructions are divided or divided according to different physical layer characteristics.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service level of the slice, The maximum transfer rate of the slice, the percentage of the slice occupying resources.
  • the slice configuration information is configured using a dedicated process and/or a public process.
  • the slice occupation resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice;
  • the slice priority is used to indicate that a MAC entity in the first network element schedules the priority of the slice data
  • the quality of service level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the quality of service level.
  • the multiple RBs and/or LCHs are mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the second network element sends the slice configuration information to the first network element under the following trigger condition:
  • the second network element sends the slice configuration information to the first network element when a slice addition event, a slice deletion event, or a slice update event occurs on the access network side;
  • the second network element When the second network element receives the requesting slice configuration information sent by the first network element, the second network element sends the slice configuration information to the first network element;
  • the second network element sends the slice configuration information to the first network element when the RB and/or the LCH establishment, deletion, or reconfiguration process occurs; or
  • the second network element sends the slice configuration information to the first network element.
  • the embodiment of the invention provides a network slice management device, and the device includes:
  • a receiving unit configured to receive the slice configuration information sent by the second network element
  • the management unit is configured to perform scheduling management on each slice on the access network side according to the slice configuration information.
  • the slices are divided according to different radio bearers, divided according to different cells, divided according to different frequencies, or divided according to different service types, or according to different types of services.
  • the indication of the core network is divided or divided according to different physical layer characteristics.
  • the slice configuration information includes: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a service quality level of the slice, and a maximum transmission of the slice. Rate, the percentage of resources occupied by the slice.
  • the slice configuration information is configured using a dedicated process and/or a public process.
  • the slice occupation resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice;
  • the slice priority is used to indicate a priority order in which the MAC entity in the first network element schedules the slice data
  • the quality of service level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the quality of service level.
  • the management unit refers to a MAC entity in the first network element, and is configured to allocate corresponding physical resources to one or more slices according to the slice configuration information.
  • the multiple RBs and/or LCHs are mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the management unit refers to a MAC entity in the first network element, and is configured as a pair.
  • the apparatus further includes: a sending unit, configured to request the slice configuration information from the second network element.
  • the embodiment of the invention provides a network slice management device, and the device includes:
  • the sending unit is configured to send the slice configuration information to the first network element, so that the first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the slices are divided according to different radio bearers, divided according to different cells, divided according to different frequencies, or divided according to different service types, or according to the core network.
  • the instructions are divided or divided according to different physical layer characteristics.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service level of the slice, The maximum transfer rate of the slice, the percentage of the slice occupying resources.
  • the slice configuration information is configured using a dedicated process and/or a public process.
  • the slice occupation resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice;
  • the slice priority is used to indicate that a MAC entity in the first network element schedules the priority of the slice data
  • the quality of service level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the quality of service level.
  • the multiple RBs and/or LCHs are mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the sending unit sends the first network element to the first network element under the following triggering condition
  • the slice configuration information :
  • the second network element sends the slice configuration information to the first network element when a slice addition event, a slice deletion event, or a slice update event occurs on the access network side;
  • the second network element When the second network element receives the requesting slice configuration information sent by the first network element, the second network element sends the slice configuration information to the first network element;
  • the second network element sends the slice configuration information to the first network element when the RB and/or the LCH establishment, deletion, or reconfiguration process occurs; or
  • the second network element sends the slice configuration information to the first network element.
  • the computer storage medium provided by the embodiment of the present invention stores a computer program configured to execute the above-mentioned network slice management method.
  • the first network element requests slice configuration information from the second network element; the first network element receives the slice configuration information sent by the second network element, and may determine the correspondence between the RB or the LCH and the slice. Relationship, and the resource occupancy of the slice, etc.; the first network element performs resource allocation and logical channel priority processing for the slice according to the slice configuration information, and implements isolation between the access network side slices, thereby avoiding mutual interference between slices.
  • FIG. 1 is a schematic diagram of a CU/DU separation architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of CU/DU function division according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of mapping relationship between a slice and a radio bearer according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart 1 of a method for managing a network slice according to an embodiment of the present invention
  • FIG. 5 is a second schematic flowchart of a method for managing a network slice according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of generating and sending a slice common configuration information according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a process for sending slice configuration information of a DU request according to an embodiment of the present invention.
  • RB 8 is a RB and/or LCH establishment, deletion, reconstruction, user RB and / or the flow pattern of the LCH belongs to trigger the generation and/or transmission of the user-specific configuration information;
  • FIG. 9 is a flowchart of a slice scheduling selection performed by a DU according to a BSR reported by a terminal according to an embodiment of the present invention.
  • FIG. 10 is a first schematic structural diagram of a network slice management apparatus according to an embodiment of the present invention.
  • FIG. 11 is a second schematic structural diagram of a network slice management apparatus according to an embodiment of the present invention.
  • one of the solutions is that different service types are implemented on the access network side according to different slices. Due to the introduction of the access network side slice and the CU/DU separation based on the CU/DU separation, the configuration information of the slice needs to be configured by the CU to the DU through the fronthaul interface.
  • the MAC entity in the DU centrally manages and schedules the slice according to the slice configuration information, avoiding the slice. Interference between the two, to achieve the isolation of the slice.
  • FIG. 1 is a schematic diagram of a CU/DU separation architecture according to an embodiment of the present invention.
  • the fronthaul interface here can be an ideal fronthaul interface or a non-ideal fronthaul interface.
  • the ideal fronthaul interface has a small transmission delay, such as tens to hundreds of microseconds.
  • the transmission delay of the non-ideal fronthaul interface is relatively large, such as milliseconds.
  • the CU is distinguished by the distinction between ideal and non-ideal fronthaul interfaces.
  • the DU has different functional divisions, that is, in the case of non-ideal fronthaul interface transmission, delay-sensitive user plane functions such as media access control (MAC, Media Access Control) scheduling function need to be placed in the DU, and the delay requirement is required. Insensitive, such as the 5G-PDCP (5G-Packet Data Convergence Protocol) header compression, encryption and integrity containment functions are placed in the CU to meet the transmission delay requirements.
  • delay-sensitive user plane functions such as media access control (MAC, Media Access Control) scheduling function need to be placed in the DU, and the delay requirement is required.
  • Insensitive such as the 5G-PDCP (5G-Packet Data Convergence Protocol) header compression, encryption and integrity containment functions are placed in the CU to meet the transmission delay requirements.
  • 5G-PDCP 5G-Packet Data Convergence Protocol
  • FIG. 2 is a schematic diagram of CU/DU function division according to an embodiment of the present invention.
  • 5G-PDCP The entity is located in the CU, the MAC entity is located in the DU, and one or more DUs can be connected under one CU.
  • DU1 the 5G-PDCP SDU data packet from the core network is transmitted to the DU1 through the fronthaul interface after passing through the 5G-PDCP and the 5G-RLC entity, and the MAC entity performs scheduling transmission on the data packet from the CU according to the logical channel priority.
  • the one RB corresponds to one LCH
  • FIG. 1 corresponds to one LCH
  • the 5G-PDCP entity is placed in the CU, and the MAC entity is placed in the DU.
  • the location of the 5G-RLC entity is not limited.
  • the 5G-RLC entity is indicated by a virtual box in FIG. 2, and has two meanings here. First, the 5G-RLC entity is placed in the CU or placed in the DU; second, 5G.
  • Some functions of the RLC entity (such as ARQ function with less delay requirement) are placed in the CU, and other functions (such as segmentation, cascading, reassembly, re-segmentation, etc. with higher delay requirements) are placed in the DU. in.
  • FIG. 3 is a schematic diagram of mapping relationship between a slice and a radio bearer according to an embodiment of the present invention.
  • multiple RBs and/or LCHs can be mapped to one slice.
  • one or more slices are mapped to the MAC entity in the DU, ie one MAC entity manages one or more slices.
  • the configuration information such as the mapping relationship between the slice and the RB and/or the LCH, the resource required by the slice, the slice priority, and the QoS level of the slice are configured by the CU to the DU through the fronthaul interface, and the MAC entity in the DU is configured according to the slice configuration information of the fronthaul interface. Perform scheduling management to achieve isolation of slices and avoid interference between slices.
  • FIG. 2 The description of the CU/DU separation is as described in FIG. 2, and FIG. 3 only shows a scenario in which the CU/DU is separated.
  • the embodiment of the present invention only considers the scheduling function of the MAC entity in the distributed processing unit DU.
  • the function of part or all of the 5G-RLC may be in the CU or in the DU.
  • the embodiment of the present invention does not limit the location of the 5G-RLC entity.
  • Table 1 simply lists the mapping relationship between the slice and the RB/LCH. As can be seen from Table 1, multiple RBs and/or LCHs can be mapped to one slice, and the corresponding relationship is that the CU is configured to the DU through the fronthaul interface.
  • FIG. 4 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present invention.
  • the first network element is specifically a DU
  • the second network element is specifically a CU.
  • the network slice is managed. The method includes the following steps:
  • Step 401 The first network element receives the slice configuration information sent by the second network element.
  • the first network element requests slice configuration information from the second network element, and the first network element receives the slice configuration information sent by the second network element.
  • the slice is divided according to different radio bearers, or divided according to different cells, or divided according to different frequencies, or divided according to different service types. Or according to the instructions of the core network, or according to different physical layer features.
  • the first network element receives the slice configuration information sent by the second network element, including:
  • the first network element receives the slice configuration information sent by the second network element through the fronthaul interface.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and a radio bearer RB, a mapping relationship between a slice and a logical channel LCH, a mapping relationship between a slice and a physical resource or a resource pool, and a slice priority.
  • a mapping relationship between a slice and a radio bearer RB a mapping relationship between a slice and a logical channel LCH, a mapping relationship between a slice and a physical resource or a resource pool, and a slice priority.
  • the quality of service QoS level of the slice the maximum transmission rate of the slice, and the percentage of the slice occupied resources.
  • the mapping relationship between the slice and the radio bearer RB means which slice each RB belongs to.
  • the mapping relationship between the slice and the logical channel LCH means which slice each LCH belongs to.
  • the slice configuration information can be configured using a dedicated process and/or a public process.
  • the mapping relationship between slice and RB and/or LCH corresponds to the "X2" interface dedicated procedure, which is UE specific.
  • the maximum rate of the slice (such as slice AMBR), the reserved amount of the slice
  • the source block size or slice occupancy resource percentage is slice specific, corresponding to the "X2" interface public procedure.
  • the slice occupied resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice.
  • the slice priority is used to indicate that the MAC entity in the first network element schedules the priority order of the slice.
  • the QoS level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the QoS level.
  • Step 402 The first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the MAC entity in the first network element allocates corresponding physical resources to one or more slices according to the slice configuration information.
  • the multiple RBs and/or LCHs can be mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the first network element performs scheduling management on each slice on the access network side according to the slice configuration information, including:
  • the MAC entity in the first network element performs centralized scheduling management on one or more slices. or,
  • the MAC entity in the first network element performs centralized scheduling management on one or more users.
  • centralized scheduling management refers to unified or collective scheduling management of multiple slices or users.
  • FIG. 5 is a schematic flowchart of a method for managing a network slice according to an embodiment of the present invention.
  • the first network element is specifically a DU
  • the second network element is specifically a CU.
  • the network slice is managed. The method includes the following steps:
  • Step 501 The second network element generates slice configuration information.
  • the slice is divided according to different radio bearers, divided according to different cells, or divided according to different frequencies, or divided according to different service types, or according to different types of services.
  • the indication of the core network is divided or divided according to different physical layer characteristics.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, and a service quality of the slice.
  • the slice configuration information can be configured using a dedicated process and/or a public process.
  • the slice occupied resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice.
  • the slice priority is used to indicate that the MAC entity in the first network element schedules the priority of the slice data.
  • the QoS level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the QoS level.
  • the multiple RBs and/or LCHs can be mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • Step 502 The second network element sends the slice configuration information to the first network element, so that the first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the second network element sends the slice configuration information to the first network element under the following trigger condition:
  • the second network element sends the slice configuration information to the first network element;
  • the second network element sends the slice configuration information to the first network element when the RB and/or LCH establishment, deletion, or reconfiguration process occurs; or
  • the second network element sends the slice configuration information to the first network element.
  • 1) and 2) correspond to public processes
  • 3) and 4) correspond to dedicated processes.
  • FIG. 6 is a flowchart of generating and sending slice common configuration information according to an embodiment of the present invention.
  • the CU generates configuration information of one or more slices in a slice unit, and sends the configuration information to the DU through the fronthaul interface.
  • the DU performs centralized management and scheduling on one or more slices according to the slice configuration information, so as to achieve isolation between slices and avoid slices. Simple interference, the specific steps are described as follows:
  • Step 601 The slice adds or deletes or updates the trigger CU to generate slice configuration information.
  • the configuration information includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource. .
  • the triggering conditions generated by the configuration information include: adding or deleting or updating a slice.
  • the plurality of RBs and/or LCHs can be mapped to one slice, as shown in Table 1.
  • the MAC entity in the DU allocates resources for one or more slices according to the slice configuration information and performs priority processing of slices.
  • the slice occupation resource percentage is used to indicate a resource block size that the MAC entity in the DU needs to reserve for the slice.
  • the slice priority is used to indicate that the MAC entity in the DU schedules the priority order of the slice.
  • the QoS level of the slice is used to indicate that the MAC entity in the DU performs scheduling processing on the slice according to the QoS level.
  • the MAC entity has a scheduling function for centralized management and scheduling of one or more slices.
  • the slice is divided according to different radio bearers, divided according to different cells or frequencies, divided according to different service types, divided according to instructions of the core network, or divided according to different physical layer features.
  • Step 602 The slice adds or deletes or updates the trigger CU to send the slice configuration information to the DU.
  • Step 603 The CU sends the slice configuration information to the DU through the fronthaul interface.
  • the information unit (IE) transmitted by the fronthaul interface includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource.
  • the slice configuration information is sent by the CU to the DU when the slice is added or deleted or updated.
  • the slice configuration information that is sent by the CU to the DU further includes a mapping relationship between the random access resource and the slice, and the system message sends a mapping relationship between the resource and the slice.
  • the wired transmission mode or the wireless transmission mode is adopted between the CU and the distributed processing unit.
  • the fronthaul interface is ideal for fronthaul interfaces or for non-ideal fronthaul interfaces.
  • Step 604 The DU sends a receipt confirmation message of the slice configuration to the CU through the fronthaul interface.
  • the receiving confirmation message is used to indicate a receiving state of the slice configuration information described by the CU. That is, it indicates whether the CU needs to retransmit the slice configuration information.
  • Step 605 The DU allocates resources for each slice according to the slice configuration information, and performs slice scheduling and priority processing.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource.
  • the MAC entity allocates a resource block of a predetermined size to each slice according to the scheduling information in the slice configuration information, and performs scheduling priority processing to implement isolation between slices to avoid interference between slices.
  • FIG. 7 is a schematic diagram of a process of sending slice configuration information of a DU request according to an embodiment of the present invention.
  • the second embodiment is similar to the first embodiment, and is also a slice common configuration information flow. The difference is that the sending of the slice configuration information is triggered by the DU requesting the CU.
  • the specific steps are as follows:
  • Step 701 The slice adds or deletes or updates the trigger CU to generate slice configuration information.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource.
  • the trigger condition generated by the slice configuration information includes: adding or deleting or updating a slice.
  • the plurality of RBs and/or LCHs can be mapped to one slice, as shown in Table 1.
  • the MAC entity in the DU allocates resources for one or more slices according to the slice configuration information and performs priority processing of slices.
  • the slice occupation resource percentage is used to indicate a resource block size that the MAC entity in the DU needs to reserve for the slice.
  • the slice priority is used to indicate that the MAC entity in the DU schedules the priority order of the slice.
  • the QoS level of the slice is used to indicate that the MAC entity in the DU performs scheduling processing on the slice according to the QoS level.
  • the MAC entity has a scheduling function for centralized management and scheduling of one or more slices.
  • the slice is divided according to different radio bearers, divided according to different cells or frequencies, divided according to different service types, divided according to instructions of the core network, or divided according to different physical layer features.
  • Step 702 The DU requests slice configuration information from the CU through the fronthaul interface.
  • Step 703 The CU sends the slice configuration information to the DU through the fronthaul interface.
  • the information unit (IE) transmitted by the fronthaul interface includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource.
  • the slice configuration information is sent by the CU to the DU after the request of the DU to initiate the acquisition of the slice configuration information by the centralized processing unit.
  • the wired transmission mode or the wireless transmission mode is adopted between the CU and the distributed processing unit.
  • the fronthaul interface is ideal for fronthaul interfaces or for non-ideal fronthaul interfaces.
  • Step 704 Send the receiving confirmation message of the slice configuration to the CU through the fronthaul interface.
  • the receiving confirmation message is used to indicate a receiving state of the slice configuration information described by the CU. That is, it indicates whether the CU needs to retransmit the slice configuration information.
  • Step 705 The DU allocates resources for each slice according to the slice configuration information, and performs slice scheduling and priority processing.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a quality of service QoS level of a slice, a maximum transmission rate of a slice, and a percentage of a slice occupied resource.
  • the MAC entity allocates a resource block of a predetermined size to each slice according to the scheduling information in the slice configuration information, and performs scheduling priority processing to implement isolation between slices to avoid interference between slices.
  • FIG. 8 is a schematic diagram of a process for generating and/or transmitting user-specific configuration information triggered by a change of a RB and/or LCH establishment, deletion, reconstruction, user RB, and/or LCH belonging to a slice according to an embodiment of the present invention.
  • One or more user-specific configuration information is generated by the user, and is sent to the DU through the fronthaul interface.
  • the DU performs centralized management and scheduling on one or more users according to the user-specific configuration information. The specific steps are as follows:
  • Step 801 The user generates RB and/or LCH establishment, deletion, reconstruction, user RB and/or slice to which the LCH belongs, generates user-specific configuration information, and triggers the CU to send configuration information to the DU.
  • the configuration information includes at least one of the following: a mapping relationship between a slice and a radio bearer RB, and a slice The mapping relationship with the logical channel LCH.
  • the triggering condition generated by the configuration information includes at least one of the following: a user-generated RB and/or an LCH establishment, deletion, reconstruction, a user RB, and/or a slice to which the LCH belongs changes.
  • the plurality of RBs and/or LCHs can be mapped to one slice, as shown in Table 1.
  • the MAC entity in the DU allocates resources to one or more users according to the user-specific configuration information and performs priority processing of the user.
  • the MAC entity has a scheduling function for centralized management and scheduling of one or more users.
  • the slice is divided according to different radio bearers, divided according to different cells or frequencies, divided according to different service types, divided according to instructions of the core network, or divided according to different physical layer features.
  • Step 802 The CU sends the user-specific configuration information to the DU through the fronthaul interface.
  • the information unit (IE) transmitted by the fronthaul interface includes at least one of the following: a mapping relationship between a slice and a radio bearer RB, and a mapping relationship between a slice and a logical channel LCH.
  • the user-specific configuration information is sent by the CU to the DU when a RB and/or LCH establishment, deletion, reconstruction, user RB, and/or LCH belongs to the CU changes.
  • the wired transmission mode or the wireless transmission mode is adopted between the CU and the distributed processing unit.
  • the fronthaul interface is ideal for fronthaul interfaces or for non-ideal fronthaul interfaces.
  • Step 803 The DU sends a confirmation message of the user-specific configuration information to the CU through the fronthaul interface.
  • the receiving confirmation message is used to indicate a receiving status of the user-specific configuration information described by the CU. That is, it indicates whether the CU needs to retransmit the user-specific configuration information.
  • Step 804 The DU allocates resources for each user according to the user-specific configuration information, and performs user scheduling and priority processing.
  • the user configuration information includes at least one of the following: a mapping relationship between a slice and a radio bearer RB, and a mapping relationship between a slice and a logical channel LCH.
  • the MAC entity allocates resources for each user according to the user-specific configuration information, and performs centralized management of the user.
  • FIG. 9 is a flowchart of a slice scheduling selection performed by a DU according to a Buffer Status Report reported by a terminal according to an embodiment of the present invention.
  • the embodiment 4 describes how to perform the scheduling selection of the slice by the logical channel group information in the buffer status report BSR, and schedule the terminal data to be transmitted on the corresponding slice.
  • the specific steps are as follows.
  • Step 901 The terminal generates a BSR for the data cache information on the logical channel group.
  • the logical channel group is composed of one or more LCHs, and the logical channel group belongs to a certain slice.
  • the BSR reports data cache information in units of a logical channel group (LCG).
  • LCG logical channel group
  • Step 902 The terminal sends the BSR to the DU.
  • the MAC entity in the DU has a scheduling management function for the slice.
  • the scheduling management indication information of the slice is configured by the CU to the first network element through a fronthaul interface.
  • the scheduling management indication information of the slice includes a mapping relationship between a slice and an RB and/or an LCH.
  • Step 903 The DU performs scheduling selection according to the logical channel group information in the BSR reported by the terminal, and selects which slice to perform scheduling transmission.
  • the DU determines the LCH included in the logical channel group according to the logical channel group information in the BSR, and further determines the correspondence between the LCH and the slice.
  • the correspondence between slice and RB or LCH is shown in Table 1.
  • the plurality of RBs and/or LCHs can be mapped to one slice.
  • the mapping relationship between the slice and the RB or the LCH is configured by the CU through the fronthaul interface. Give the DU.
  • the MAC entity in the DU performs scheduling selection on the slice according to the BSR, determines how much resources are reserved for a certain slice, and schedules terminal data to be transmitted on the slice.
  • FIG. 10 is a first schematic structural diagram of a network slice management apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus includes:
  • the receiving unit 1001 is configured to receive slice configuration information sent by the second network element.
  • the management unit 1002 is configured to perform scheduling management on each slice on the access network side according to the slice configuration information.
  • the slice is divided according to different radio bearers, or divided according to different cells, or divided according to different frequencies, or divided according to different service types. Or according to the instructions of the core network, or according to different physical layer features.
  • the receiving unit 1001 is further configured to receive, by using the fronthaul interface, slice configuration information sent by the second network element.
  • the slice configuration information includes: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, a QoS level of a slice, and a maximum of a slice.
  • the transmission rate the percentage of the slice occupied by the resource.
  • the slice configuration information can be configured using a dedicated process and/or a public process.
  • the slice occupied resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice.
  • the slice priority is used to indicate a priority order in which the MAC entity in the first network element schedules the slice data.
  • the QoS level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the QoS level.
  • the management unit 1002 refers to a MAC entity in the first network element, and is configured to allocate corresponding physical resources to one or more slices according to the slice configuration information.
  • the multiple RBs and/or LCHs can be mapped to one slice, or Different RBs and/or LCHs are mapped to different slices.
  • the management unit 1002 refers to a MAC entity in the first network element, and is configured to perform centralized scheduling management on one or more slices.
  • the device further includes: a sending unit 1000, configured to request slice configuration information from the second network element.
  • the implementation functions of the units in the management apparatus of the network slice shown in FIG. 10 can be understood by referring to the related description of the foregoing management method of the network slice.
  • the functions of the units in the management device of the network slice shown in FIG. 10 can be realized by a program running on the processor, or can be realized by a specific logic circuit.
  • the management device of the network slice is set in the first network element, specifically the DU; wherein the functions implemented by each unit in the management device of the network slice may be managed by the network slice Central Processing Unit (CPU), or Microprocessor Unit (MPU), Digital Signal Processor (DSP), or Field Programmable Gate Array (FPGA) Array) and other implementations.
  • CPU Central Processing Unit
  • MPU Microprocessor Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • FIG. 11 is a second structural diagram of a network slice management apparatus according to an embodiment of the present invention. As shown in FIG. 11, the apparatus includes:
  • the generating unit 1101 is configured to generate slice configuration information
  • the sending unit 1102 is configured to send the slice configuration information to the first network element, so that the first network element performs scheduling management on each slice on the access network side according to the slice configuration information.
  • the slice is divided according to different radio bearers, divided according to different cells, or divided according to different frequencies, or divided according to different service types, or according to different types of services.
  • the indication of the core network is divided or divided according to different physical layer characteristics.
  • the slice configuration information includes at least one of the following: a mapping relationship between a slice and an RB, a mapping relationship between a slice and an LCH, a mapping relationship between a slice and a physical resource or a resource pool, a slice priority, and a service quality of the slice.
  • QoS level slice maximum transmission rate
  • slice The percentage of resources used.
  • the slice configuration information can be configured using a dedicated process and/or a public process.
  • the slice occupied resource percentage is used to indicate a resource block size or a resource occupation percentage reserved by the MAC entity in the first network element for the slice.
  • the slice priority is used to indicate that the MAC entity in the first network element schedules the priority of the slice data.
  • the QoS level of the slice is used to indicate that the MAC entity in the first network element performs scheduling processing on the slice according to the QoS level.
  • the multiple RBs and/or LCHs can be mapped to one slice, or different RBs and/or LCHs are mapped to different slices.
  • the sending unit 1102 sends the slice configuration information to the first network element:
  • the second network element sends the slice configuration information to the first network element;
  • the second network element When the second network element receives the request slice slice configuration information sent by the first network element, the second network element sends the slice configuration information to the first network element;
  • the second network element sends the slice configuration information to the first network element;
  • the second network element When the slice of the user RB and/or the LCH changes, the second network element sends the slice configuration information to the first network element.
  • each unit in the management device of the network slice shown in FIG. 11 can be realized by a program running on the processor, or can be realized by a specific logic circuit.
  • the management device of the network slice is set in the second network element, specifically a CU.
  • the functions implemented by each unit in the management device of the network slice may be managed by the network slice.
  • the CPU, or MPU, or DSP, or FPGA implementation In the CPU, or MPU, or DSP, or FPGA implementation.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow or block diagram of a flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in a block or blocks of a flow or a flow or block diagram of a flowchart.
  • an embodiment of the present invention further provides a computer storage medium, wherein a computer program is configured, and the computer program is configured to perform a network slice management method according to an embodiment of the present invention.
  • the first network element requests slice configuration information from the second network element; the first network element receives the slice configuration information sent by the second network element, and may determine the RB or the LCH. The correspondence with the slice, and the resource occupancy of the slice, etc.; the first network element performs resource allocation and logical channel for the slice according to the slice configuration information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种网络切片的管理方法及装置、计算机存储介质，所述方法包括：第一网元接收第二网元发送的切片配置信息；所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。

Description

一种网络切片的管理方法及装置、计算机存储介质
相关申请的交叉引用
本申请基于申请号为201610877932.3、申请日为2016年09月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及无线通信系统技术领域，尤其涉及一种网络切片的管理方法及装置、计算机存储介质。
背景技术
第五代移动通信(5G，Fifth Generation)中，海量连接以及用户更高的速率要求，对长期演进(LTE，Long Term Evolution)中射频拉远单元(BBU，Remote Radio Unit)与基带处理单元(RRU，Building Baseband Unit)之间的前传接口——通用公共无线电接口(CPRI，Common Public Radio Interface)的传输容量提出了极大挑战，由于CPRI接口传输的是经过物理层编码调制等处理后的IQ信号，CPRI接口对传输时延和带宽都有较大的要求。如果在5G空口速率提升到数十Gbps后，CPRI接口的流量需求将上升到Tbps级别，对网络部署成本和部署难度都带来了巨大的压力。因此，在5G中，需要重新定义前传接口的划分点，比如将时延不敏感的用户面功能放在集中处理单元(CU，Centralized Unit)中，将时延敏感的用户面功能放在分布式处理单元(DU，Distributed Unit)中，CU与DU之间通过理想和/或非理想前传接口(fronthaul)进行传输，参照图1。
基于上面的描述，时延不敏感的用户面功能包括数据头压缩、加密完 整性保护、重传、对高层业务数据的发送方序号维护和接收方排序、自动重传请求(ARQ，Auto Repeat reQuest)等；时延敏感的用户面功能包括数据分段(segment)、串接(concatenation)、重分段(re-segment)、重组(reassembly)、多逻辑信道复用、混合自动重传请求(HARQ，Hybrid Automatic Repeat reQuest)等。通过上面的CU、DU的功能划分，直观的看到，媒体接入控制(MAC，Media Access Control)层的功能(包括调度、逻辑信道优先级处理链路控制协议(LCP，Link Control Protocol)、逻辑信道复用及解复用等)将放在DU中实现(参照图2)，以使CU和DU的数据传输更加贴近空口能力、满足业务服务质量(QoS，Quality of Service)，以及满足CU和DU间的传输特性。
5G技术中研究的一个重点是上述方案中CU和DU之间的网络切片(slice)，网络切片是指：将不同的业务分类成不同的切片进行实现，这要求每个切片独立工作互不影响(参照图3)，基于此，如何实现每个切片独立工作互不影响是有待解决的问题。
发明内容
为解决上述技术问题，本发明实施例提供了一种网络切片的管理方法及装置、计算机存储介质。
本发明实施例提供了一种网络切片的管理方法，所述方法包括：
第一网元接收第二网元发送的切片配置信息；
所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
上述方案中，在所述接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
上述方案中，所述切片配置信息包括至少以下之一：切片与无线承载(RB)的映射关系、切片与逻辑信道(LCH)的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
上述方案中，所述切片配置信息使用专用过程和/或公共过程进行配置。
上述方案中，所述切片占用资源百分比用于指示所述第一网元中的媒体接入控制(MAC)实体为所述切片预留的资源块大小或资源占用百分比；
所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
上述方案中，所述方法还包括：
所述第一网元中的MAC实体根据所述切片配置信息为一个或多个切片分配相应的物理资源。
上述方案中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
上述方案中，所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理，包括：
所述第一网元中的MAC实体对一个或多个切片进行集中调度管理。
上述方案中，当所述第一网元向所述第二网元请求切片配置信息时，所述第一网元接收第二网元发送的切片配置信息。
本发明实施例提供了一种网络切片的管理方法，所述方法包括：
第二网元生成切片配置信息；
所述第二网元向所述第一网元发送所述切片配置信息，以使所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
上述方案中，在接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
上述方案中，所述切片配置信息包括至少以下之一：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
上述方案中，所述切片配置信息使用专用过程和/或公共过程进行配置。
上述方案中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
上述方案中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
上述方案中，在以下触发条件下，所述第二网元向所述第一网元发送所述切片配置信息：
在所述接入网侧，发生切片添加事件、或切片删除事件、或切片更新事件时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当所述第二网元接收到第一网元发送的请求切片配置信息时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当用户RB和/或LCH所属切片发生变化时，所述第二网元向所述第一网元发送所述切片配置信息。
本发明实施例提供了一种网络切片的管理装置，所述装置包括：
接收单元，配置为接收第二网元发送的切片配置信息；
管理单元，配置为根据所述切片配置信息对接入网侧的各个切片进行调度管理。
上述方案中，在所述接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
上述方案中，所述切片配置信息包括：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
上述方案中，所述切片配置信息使用专用过程和/或公共过程进行配置。
上述方案中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级顺序；
所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
上述方案中，所述管理单元是指第一网元中的MAC实体，配置为根据所述切片配置信息为一个或多个切片分配相应的物理资源。
上述方案中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
上述方案中，所述管理单元是指第一网元中的MAC实体，配置为对一 个或多个切片进行集中调度管理。
上述方案中，所述装置还包括：发送单元，配置为向第二网元请求切片配置信息。
本发明实施例提供了一种网络切片的管理装置，所述装置包括：
生成单元，配置为生成切片配置信息；
发送单元，配置为向所述第一网元发送所述切片配置信息，以使所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
上述方案中，在接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
上述方案中，所述切片配置信息包括至少以下之一：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
上述方案中，所述切片配置信息使用专用过程和/或公共过程进行配置。
上述方案中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
上述方案中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
上述方案中，在以下触发条件下，所述发送单元向所述第一网元发送 所述切片配置信息：
在所述接入网侧，发生切片添加事件、或切片删除事件、或切片更新事件时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当所述第二网元接收到第一网元发送的请求切片配置信息时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
当用户RB和/或LCH所属切片发生变化时，所述第二网元向所述第一网元发送所述切片配置信息。
本发明实施例提供的计算机存储介质存储有计算机程序，该计算机程序配置为执行上述的网络切片的管理方法。
本发明实施例的技术方案中，第一网元向第二网元请求切片slice配置信息；所述第一网元接收第二网元发送的slice配置信息，可以确定RB或LCH与slice的对应关系，以及slice的资源占用情况等；第一网元根据slice配置信息为slice进行资源分配以及逻辑信道优先级处理，实现了接入网侧slice间的隔离，避免了slice间的相互干扰。
附图说明
图1为本发明实施例的CU/DU分离架构示意图；
图2为本发明实施例的CU/DU功能划分示意图；
图3为本发明实施例的slice与无线承载的映射关系示意图；
图4为本发明实施例的网络切片的管理方法的流程示意图一；
图5为本发明实施例的网络切片的管理方法的流程示意图二；
图6为本发明实施例的slice公共配置信息的生成及发送流程图；
图7为本发明实施例的DU请求的slice配置信息发送流程示意图；
图8为本发明实施例的RB和/或LCH建立、删除、重建、用户RB和 /或LCH所属的slice发生变化触发用户专用配置信息的生成和/或发送流程示意图；
图9为本发明实施例的DU根据终端上报的BSR进行slice调度选择的流程图；
图10为本发明实施例的网络切片的管理装置的结构组成示意图一；
图11为本发明实施例的网络切片的管理装置的结构组成示意图二。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
考虑到未来5G业务的多样性以及网络切片(network slice)的诸多方案，其中一种方案是，不同的业务类型在接入网侧按不同的slice进行实现。由于接入网侧slice的引入以及基于CU/DU分离的考虑，slice的相关配置信息需要CU通过fronthaul接口配置给DU，DU中的MAC实体根据slice配置信息对slice进行集中管理和调度，避免slice间的干扰，实现slice的隔离。
图1为本发明实施例的CU/DU分离架构示意图。图1中，CU与DU之间通过fronthaul接口进行信息交互，针对不同的时延，这里的fronthaul接口可以是理想fronthaul接口或非理想fronthaul接口。理想fronthaul接口的传输时延比较小，比如大概为几十到几百微秒，非理想fronthaul接口的传输时延相对较大，比如为毫秒级，由于理想和非理想fronthaul接口的区分，导致CU、DU有不同的功能划分，即在非理想fronthaul接口传输的情况下，需要把时延敏感的用户面功能如媒体接入控制(MAC，Media Access Control)调度功能放在DU中，时延要求不敏感如第五代分组数据汇聚协议(5G-PDCP，5G-Packet Data Convergence Protocol)头压缩、加密和完整性包含等功能放在CU中，以满足传输时延要求。
图2为本发明实施例的CU/DU功能划分示意图。在图2中，5G-PDCP 实体位于CU中，MAC实体位于DU中，一个CU下可以连接一个或多个DU。以DU1为例，来自核心网的5G-PDCP SDU数据包经过5G-PDCP和5G-RLC实体后通过fronthaul接口传输到DU1，由MAC实体根据逻辑信道优先级对来自CU的数据包进行调度传输。在图2示意图中，为了方便说明，所述一个RB对应一个LCH，图2实例不对RB与LCH的对应关系进行限定，可以是一个RB对应一个LCH，也可以是一个RB对应多个LCH。同理，在图2中，5G-PDCP实体放在CU中，MAC实体放在DU中，在本发明实施例中不对5G-RLC实体的位置进行限定。其中，需要进一步说明的是，5G-RLC实体在图2中用虚框标示，在这里有两层含义，一是，5G-RLC实体放在CU中，或者放在DU中；二是，5G-RLC实体的一部分功能(如时延要求不高的ARQ功能)放在CU中，另一部分功能(如时延要求比较高的分段、级联、重组、重分段等功能)放在DU中。
图3为本发明实施例的slice与无线承载的映射关系示意图。其中，多个RB和/或LCH能够映射到一个slice。并且一个或多个slice映射到DU中的MAC实体，即一个MAC实体管理一个或多个slice。slice与RB和/或LCH的映射关系、slice需要的资源、slice优先级以及slice的QoS等级等配置信息由CU通过fronthaul接口配置给DU，DU中的MAC实体根据fronthaul接口的slice配置信息对slice进行调度管理，实现对slice的隔离，避免slice间的干扰。CU/DU分离的说明如图2中所述，图3也仅给出了一种CU/DU分离的场景，本发明实施例仅考虑MAC实体的调度功能在分布式处理单元DU中的情况，部分或全部5G-RLC的功能可以在CU中，也可以在DU中，本发明实施例不对5G-RLC实体的位置进行限定。
表1简单列出了slice与RB/LCH的映射关系，从表1可以看出，多个RB和/或LCH能够映射到一个slice，其对应关系是CU通过fronthaul接口配置给DU。
Figure PCTCN2017102888-appb-000001
Figure PCTCN2017102888-appb-000002
表1
图4为本发明实施例的网络切片的管理方法的流程示意图一，本示例中，第一网元具体为DU，第二网元具体为CU，如图4所示，所述网络切片的管理方法包括以下步骤：
步骤401：第一网元接收第二网元发送的slice配置信息。
本发明实施例中，第一网元向第二网元请求slice配置信息，第一网元接收第二网元发送的slice配置信息。
本发明实施例中，在所述接入网侧，所述slice按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
本发明实施例中，所述第一网元接收第二网元发送的slice配置信息，包括：
第一网元通过fronthaul接口接收第二网元发送的slice配置信息。
本发明实施例中，所述slice配置信息包括至少以下之一：slice与无线承载RB的映射关系、slice与逻辑信道LCH的映射关系、slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述slice与无线承载RB的映射关系的意思是每个RB属于哪个slice。
所述slice与逻辑信道LCH的映射关系的意思是每个LCH属于哪个slice。
这里，所述slice配置信息能够使用专用过程和/或公共过程进行配置。具体地，slice与RB和/或LCH之类的映射关系对应“X2”接口专用过程，是UE specific的。但是slice的最大速率(如slice AMBR)，slice预留的资 源块大小或slice占用资源百分比之类的是slice specific的，对应”X2”接口公共过程。
本发明实施例中，所述slice占用资源百分比用于指示所述第一网元中的MAC实体需要为所述slice预留的资源块大小或资源占用百分比。
本发明实施例中，所述slice优先级用于指示所述第一网元中的MAC实体调度所述slice的优先级顺序。
本发明实施例中，所述slice的QoS等级用于指示所述第一网元中的MAC实体按照所述QoS等级对所述slice进行调度处理。
步骤402：所述第一网元根据所述slice配置信息对接入网侧的各个slice进行调度管理。
本发明实施例中，所述第一网元中的MAC实体根据所述slice配置信息为一个或多个slice分配相应的物理资源。
本发明实施例中，所述多个RB和/或LCH能够映射到一个slice，或者，不同RB和/或LCH映射到不同的slice。
本发明实施例中，所述第一网元根据所述slice配置信息对接入网侧的各个slice进行调度管理，包括：
所述第一网元中的MAC实体对一个或多个slice进行集中调度管理。或者，
所述第一网元中的MAC实体对一个或多个用户进行集中调度管理。
这里，集中调度管理是指将多个slice或用户进行统一或一起调度管理。
图5为本发明实施例的网络切片的管理方法的流程示意图二，本示例中，第一网元具体为DU，第二网元具体为CU，如图5所示，所述网络切片的管理方法包括以下步骤：
步骤501：第二网元生成slice配置信息。
本发明实施例中，在接入网侧，所述slice按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
本发明实施例中，所述slice配置信息包括至少以下之一：slice与RB的映射关系、slice与LCH的映射关系、slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
本发明实施例中，所述slice配置信息能够使用专用过程和/或公共过程进行配置。
本发明实施例中，所述slice占用资源百分比用于指示所述第一网元中的MAC实体需要为所述slice预留的资源块大小或资源占用百分比。
本发明实施例中，所述slice优先级用于指示所述第一网元中的MAC实体调度所述slice数据的优先级。
本发明实施例中，所述slice的QoS等级用于指示所述第一网元中的MAC实体按照所述QoS等级对所述slice进行调度处理。
本发明实施例中，所述多个RB和/或LCH能够映射到一个slice，或者，不同RB和/或LCH映射到不同的slice。
步骤502：所述第二网元向所述第一网元发送所述slice配置信息，以使所述第一网元根据所述slice配置信息对接入网侧的各个slice进行调度管理。
本发明实施例中，在以下触发条件下，所述第二网元向所述第一网元发送所述slice配置信息：
1)在所述接入网侧，发生slice添加事件、或slice删除事件、或slice更新事件时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
2)当所述第二网元接收到第一网元发送的请求切片slice配置信息时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
3)当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
4)当用户RB和/或LCH所属slice发生变化时，所述第二网元向所述第一网元发送所述slice配置信息。
其中，1)和2)对应公共过程，3)和4)对应专用过程。
下面结合具体应用场景对本发明实施例的网络切片的管理方法做进一步描述。
实施例1
图6为本发明实施例的slice公共配置信息的生成及发送流程图。其中，CU以slice为单位生成一个或多个slice的配置信息，通过fronthaul接口发送到DU中，DU根据slice配置信息对一个或多个slice进行集中管理和调度，实现slice间的隔离，避免slice简的干扰，具体步骤描述如下：
步骤601：slice添加或删除或更新触发CU生成slice配置信息。
所述配置信息包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。。
所述配置信息生成的触发条件包括：slice的添加或删除或更新。
所述多个RB和/或LCH能够映射到一个slice，如表1所示。
所述DU中的MAC实体根据所述slice配置信息为一个或多个slice分配资源以及进行slice的优先级处理。
所述slice占用资源百分比用于指示所述DU中的MAC实体需要为所述slice预留的资源块大小。
所述slice优先级用于指示DU中的MAC实体调度所述slice的优先级顺序。
所述slice的QoS等级用于指示DU中的MAC实体按照所述QoS等级对所述slice进行调度处理。
所述MAC实体具有调度功能，用于对一个或多个slice进行集中管理和调度。
所述slice按照不同的无线承载进行划分、或者按照不同的小区或频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
步骤602：slice添加或删除或更新触发CU将slice配置信息发送到DU。
步骤603：CU将slice配置信息通过fronthaul接口发送到DU中。
所述fronthaul接口传输的信息单元(IE)包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述slice配置信息是所述CU在slice的添加或删除或更新的时候发送给所述DU的。
可选的，所述CU向所述DU发送的slice配置信息还包括随机接入资源与slice的映射关系，系统消息发送资源与slice的映射关系。
所述CU与所述分布式处理单元间采用有线传输方式或者采用无线传输方式。
针对不同的传输时延要求，所述fronthaul接口为理想fronthaul接口或者为非理想fronthaul接口。
步骤604：DU将slice配置的接收确认消息通过fronthaul接口发送给CU。
所述接收确认消息用于指示CU所述的slice配置信息的接收状态。即指示CU是否需要重传所述slice配置信息。
步骤605：DU根据slice配置信息为每个slice分配资源，进行slice调度及优先级处理。
所述slice配置信息包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述MAC实体根据所述slice配置信息中的调度信息为每个slice分配预定大小的资源块，以及进行调度优先级处理，实现slice间的隔离，避免slice间的干扰。
实施例2
图7为本发明实施例的DU请求的slice配置信息发送流程示意图。其中，实施例2与实施例1类似，也是slice公共配置信息流程，不同之处在于slice配置信息的发送由DU向CU请求后触发，具体步骤描述如下：
步骤701：slice添加或删除或更新触发CU生成slice配置信息。
所述slice配置信息包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述slice配置信息生成的触发条件包括：slice的添加或删除或更新。
所述多个RB和/或LCH能够映射到一个slice，如表1所示。
所述DU中的MAC实体根据所述slice配置信息为一个或多个slice分配资源以及进行slice的优先级处理。
所述slice占用资源百分比用于指示所述DU中的MAC实体需要为所述slice预留的资源块大小。
所述slice优先级用于指示DU中的MAC实体调度所述slice的优先级顺序。
所述slice的QoS等级用于指示DU中的MAC实体按照所述QoS等级对所述slice进行调度处理。
所述MAC实体具有调度功能，对一个或多个slice进行集中管理和调度。
所述slice按照不同的无线承载进行划分、或者按照不同的小区或频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
步骤702：DU通过fronthaul接口向CU请求slice配置信息。
步骤703：CU将slice配置信息通过fronthaul接口发送到DU中。
所述fronthaul接口传输的信息单元(IE)包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述slice配置信息是所述DU向所述集中处理单元发起获取slice配置信息的请求后，由CU发送给所述DU的。
所述CU与所述分布式处理单元间采用有线传输方式或者采用无线传输方式。
针对不同的传输时延要求，所述fronthaul接口为理想fronthaul接口或者为非理想fronthaul接口。
步骤704：将slice配置的接收确认消息通过fronthaul接口发送给CU。
所述接收确认消息用于指示CU所述的slice配置信息的接收状态。即指示CU是否需要重传所述slice配置信息。
步骤705：DU根据slice配置信息为每个slice分配资源，进行slice调度及优先级处理。
所述slice配置信息包括至少以下之一：slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice占用资源百分比。
所述MAC实体根据所述slice配置信息中的调度信息为每个slice分配预定大小的资源块，以及进行调度优先级处理，实现slice间的隔离，避免slice间的干扰。
实施例3
图8为本发明实施例的RB和/或LCH建立、删除、重建、用户RB和/或LCH所属的slice发生变化触发用户专用配置信息的生成和/或发送流程示意图。其中，以用户为单位生成一个或多个用户专用的配置信息，通过fronthaul接口发送到DU中，DU根据用户专用配置信息对一个或多个用户进行集中管理和调度，具体步骤描述如下：
步骤801：用户发生RB和/或LCH建立、删除、重建、用户RB和/或LCH所属的slice发生变化，生成用户专用配置信息，并触发CU将配置信息发送到DU。
所述配置信息包括至少以下之一：slice与无线承载RB的映射关系、slice 与逻辑信道LCH的映射关系。
所述配置信息生成的触发条件包括至少以下之一：用户发生RB和/或LCH建立、删除、重建、用户RB和/或LCH所属的slice发生变化。
所述多个RB和/或LCH能够映射到一个slice，如表1所示。
所述DU中的MAC实体根据所述用户专用配置信息为一个或多个用户分配资源以及进行用户的优先级处理。
所述MAC实体具有调度功能，用于对一个或多个用户进行集中管理和调度。
所述slice按照不同的无线承载进行划分、或者按照不同的小区或频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
步骤802：CU将用户专用配置信息通过fronthaul接口发送到DU中。
所述fronthaul接口传输的信息单元(IE)包括至少以下之一：slice与无线承载RB的映射关系、slice与逻辑信道LCH的映射关系。
所述用户专用配置信息是所述CU在用户发生RB和/或LCH建立、删除、重建、用户RB和/或LCH所属的slice发生变化的时候发送给所述DU的。
所述CU与所述分布式处理单元间采用有线传输方式或者采用无线传输方式。
针对不同的传输时延要求，所述fronthaul接口为理想fronthaul接口或者为非理想fronthaul接口。
步骤803：DU将用户专用配置信息的接收确认消息通过fronthaul接口发送给CU。
所述接收确认消息用于指示CU所述的用户专用配置信息的接收状态。即指示CU是否需要重传所述用户专用配置信息。
步骤804：DU根据用户专用配置信息为每个用户配置资源，进行用户调度及优先级处理。
所述用户配置信息包括至少以下之一：slice与无线承载RB的映射关系、slice与逻辑信道LCH的映射关系。
所述MAC实体根据所述用户专用配置信息为每个用户分配资源，进行用户的集中管理。
实施例4
图9为本发明实施例的DU根据终端上报的缓存状态报告(BSR，Buffer Status Report)进行slice调度选择的流程图。实施例4主要描述了如何通过终端上报缓存状态报告BSR中的逻辑信道组信息进行slice的调度选择，将终端数据调度在相应的slice上进行传输，具体步骤描述如下。
步骤901：终端针对逻辑信道组上的数据缓存信息生成BSR。
所述逻辑信道组由一个或多个LCH组成，所述逻辑信道组归属于某个slice。
所述BSR以逻辑信道组(LCG，Logical Channel Group)为单位进行数据缓存信息的上报。
步骤902：终端将BSR发送给DU。
所述DU中的MAC实体具有对slice的调度管理功能。
所述slice的调度管理指示信息由CU通过fronthaul接口配置给所述第一网元。
所述slice的调度管理指示信息包括slice与RB和/或LCH的映射关系。
步骤903：DU根据终端上报的BSR中的逻辑信道组信息进行调度选择，选择在哪个slice进行调度传输。
所述DU根据BSR中的逻辑信道组信息，确定所述逻辑信道组包含的LCH，进一步，确定LCH与slice的对应关系。slice与RB或LCH的对应关系如表1所示。
所述多个RB和/或LCH能够映射到一个slice。
所述slice与RB或LCH的映射关系由所述CU通过fronthaul接口配置 给所述DU。
所述DU中的MAC实体根据BSR，对slice进行调度选择，确定为某个slice预留多少资源，将终端数据调度在所述slice上进行传输。
图10为本发明实施例的网络切片的管理装置的结构组成示意图一，如图10所示，所述装置包括：
接收单元1001，配置为接收第二网元发送的slice配置信息；
管理单元1002，配置为根据所述slice配置信息对接入网侧的各个slice进行调度管理。
本发明实施例中，在所述接入网侧，所述slice按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
本发明实施例中，所述接收单元1001，还用于通过fronthaul接口接收第二网元发送的slice配置信息。
本发明实施例中，所述slice配置信息包括：slice与RB的映射关系、slice与LCH的映射关系、slice与物理资源或资源池的映射关系、slice优先级、slice的QoS等级、slice的最大传输速率、slice占用资源百分比。
本发明实施例中，所述slice配置信息能够使用专用过程和/或公共过程进行配置。
本发明实施例中，所述slice占用资源百分比用于指示所述第一网元中的MAC实体需要为所述slice预留的资源块大小或资源占用百分比。
本发明实施例中，所述slice优先级用于指示所述第一网元中的MAC实体调度所述slice数据的优先级顺序。
本发明实施例中，所述slice的QoS等级用于指示所述第一网元中的MAC实体按照所述QoS等级对所述slice进行调度处理。
本发明实施例中，所述管理单元1002是指第一网元中的MAC实体，配置为根据所述slice配置信息为一个或多个slice分配相应的物理资源。
本发明实施例中，所述多个RB和/或LCH能够映射到一个slice，或者， 不同RB和/或LCH映射到不同的slice。
本发明实施例中，所述管理单元1002是指第一网元中的MAC实体，配置为对一个或多个slice进行集中调度管理。
本发明实施例中，所述装置还包括：发送单元1000，配置为向第二网元请求slice配置信息。
本领域技术人员应当理解，图10所示的网络切片的管理装置中的各单元的实现功能可参照前述网络切片的管理方法的相关描述而理解。图10所示的网络切片的管理装置中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
在实际应用中，所述网络切片的管理装置设置在第一网元中，具体为DU；其中，所述网络切片的管理装置中的各个单元所实现的功能，均可由位于网络切片的管理装置中的中央处理器(CPU，Central Processing Unit)、或微处理器(MPU，Micro Processor Unit)、或数字信号处理器(DSP，Digital Signal Processor)、或现场可编程门阵列(FPGA，Field Programmable Gate Array)等实现。
图11为本发明实施例的网络切片的管理装置的结构组成示意图二，如图11所示，所述装置包括：
生成单元1101，配置为生成slice配置信息；
发送单元1102，配置为向所述第一网元发送所述slice配置信息，以使所述第一网元根据所述slice配置信息对接入网侧的各个slice进行调度管理。
本发明实施例中，在接入网侧，所述slice按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
本发明实施例中，所述slice配置信息包括至少以下之一：slice与RB的映射关系、slice与LCH的映射关系、slice与物理资源或资源池的映射关系、slice优先级、slice的服务质量QoS等级、slice的最大传输速率、slice 占用资源百分比。
本发明实施例中，所述slice配置信息能够使用专用过程和/或公共过程进行配置。
本发明实施例中，所述slice占用资源百分比用于指示所述第一网元中的MAC实体需要为所述slice预留的资源块大小或资源占用百分比。
本发明实施例中，所述slice优先级用于指示所述第一网元中的MAC实体调度所述slice数据的优先级。
本发明实施例中，所述slice的QoS等级用于指示所述第一网元中的MAC实体按照所述QoS等级对所述slice进行调度处理。
本发明实施例中，所述多个RB和/或LCH能够映射到一个slice，或者，不同RB和/或LCH映射到不同的slice。
本发明实施例中，所述发送单元1102向所述第一网元发送所述slice配置信息：
在所述接入网侧，发生slice添加事件、或slice删除事件、或slice更新事件时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
当所述第二网元接收到第一网元发送的请求切片slice配置信息时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述slice配置信息；或者，
当用户RB和/或LCH所属slice发生变化时，所述第二网元向所述第一网元发送所述slice配置信息。
本领域技术人员应当理解，图11所示的网络切片的管理装置中的各单元的实现功能可参照前述网络切片的管理方法的相关描述而理解。图11所示的网络切片的管理装置中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
在实际应用中，所述网络切片的管理装置设置在第二网元中，具体为CU；其中，所述网络切片的管理装置中的各个单元所实现的功能，均可由位于网络切片的管理装置中的CPU、或MPU、或DSP、或FPGA等实现。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图或方框图来描述的。应理解可由计算机程序指令实现流程图或方框图中的每一流程或方框、以及流程图或方框图中的流程或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程或方框图一个方框或多个方框中指定的功能的步骤。
相应地，本发明实施例还提供一种计算机存储介质，其中存储有计算机程序，该计算机程序配置为执行本发明实施例的网络切片的管理方法。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
工业实用性
本发明实施例的技术方案，第一网元向第二网元请求切片slice配置信息；所述第一网元接收第二网元发送的slice配置信息，可以确定RB或LCH 与slice的对应关系，以及slice的资源占用情况等；第一网元根据slice配置信息为slice进行资源分配以及逻辑信道。

Claims (33)

  1. 一种网络切片的管理方法，所述方法包括：
    第一网元接收第二网元发送的切片配置信息；
    所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
  2. 根据权利要求1所述的网络切片的管理方法，其中，在所述接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
  3. 根据权利要求1所述的网络切片的管理方法，其中，所述切片配置信息包括至少以下之一：切片与无线承载RB的映射关系、切片与逻辑信道LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
  4. 根据权利要求3所述的网络切片的管理方法，其中，所述切片配置信息使用专用过程和/或公共过程进行配置。
  5. 根据权利要求3所述的网络切片的管理方法，其中，
    所述切片占用资源百分比用于指示所述第一网元中的媒体接入控制MAC实体为所述切片预留的资源块大小或资源占用百分比；
    所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
    所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
  6. 根据权利要求1所述的网络切片的管理方法，其中，所述方法还包括：
    所述第一网元中的MAC实体根据所述切片配置信息为一个或多个切片分配相应的物理资源。
  7. 根据权利要求3所述的网络切片的管理方法，其中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
  8. 根据权利要求1所述的网络切片的管理方法，其中，所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理，包括：
    所述第一网元中的MAC实体对一个或多个切片进行集中调度管理。
  9. 根据权利要求1所述的网络切片的管理方法，其中，当所述第一网元向所述第二网元请求切片配置信息时，所述第一网元接收第二网元发送的切片配置信息。
  10. 一种网络切片的管理方法，所述方法包括：
    第二网元生成切片配置信息；
    所述第二网元向所述第一网元发送所述切片配置信息，以使所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
  11. 根据权利要求10所述的网络切片的管理方法，其中，在接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
  12. 根据权利要求10所述的网络切片的管理方法，其中，所述切片配置信息包括至少以下之一：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
  13. 根据权利要求12所述的网络切片的管理方法，其中，所述切片 配置信息使用专用过程和/或公共过程进行配置。
  14. 根据权利要求12所述的网络切片的管理方法，其中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
    所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
    所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
  15. 根据权利要求12所述的网络切片的管理方法，其中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
  16. 根据权利要求10所述的网络切片的管理方法，其中，在以下触发条件下，所述第二网元向所述第一网元发送所述切片配置信息：
    在所述接入网侧，发生切片添加事件、或切片删除事件、或切片更新事件时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当所述第二网元接收到第一网元发送的请求切片配置信息时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当用户RB和/或LCH所属切片发生变化时，所述第二网元向所述第一网元发送所述切片配置信息。
  17. 一种网络切片的管理装置，所述装置包括：
    接收单元，配置为接收第二网元发送的切片配置信息；
    管理单元，配置为根据所述切片配置信息对接入网侧的各个切片进行调度管理。
  18. 根据权利要求17所述的网络切片的管理装置，其中，在所述接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
  19. 根据权利要求17所述的网络切片的管理装置，其中，所述切片配置信息包括：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
  20. 根据权利要求19所述的网络切片的管理装置，其中，所述切片配置信息使用专用过程和/或公共过程进行配置。
  21. 根据权利要求19所述的网络切片的管理装置，其中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
    所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级顺序；
    所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
  22. 根据权利要求17所述的网络切片的管理装置，其中，所述管理单元是指第一网元中的MAC实体，配置为根据所述切片配置信息为一个或多个切片分配相应的物理资源。
  23. 根据权利要求19所述的网络切片的管理装置，其中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
  24. 根据权利要求17所述的网络切片的管理装置，其中，所述管理 单元是指第一网元中的MAC实体，配置为对一个或多个切片进行集中调度管理。
  25. 根据权利要求17所述的网络切片的管理装置，其中，所述装置还包括：发送单元，配置为向第二网元请求切片配置信息。
  26. 一种网络切片的管理装置，所述装置包括：
    生成单元，配置为生成切片配置信息；
    发送单元，配置为向所述第一网元发送所述切片配置信息，以使所述第一网元根据所述切片配置信息对接入网侧的各个切片进行调度管理。
  27. 根据权利要求26所述的网络切片的管理装置，其中，在接入网侧，所述切片按照不同的无线承载进行划分、或者按照不同的小区进行划分、或者按照不同的频率进行划分、或者按照不同的业务类型进行划分、或者按照核心网的指示进行划分、或者按照不同的物理层特征进行划分。
  28. 根据权利要求26所述的网络切片的管理装置，其中，所述切片配置信息包括至少以下之一：切片与RB的映射关系、切片与LCH的映射关系、切片与物理资源或资源池的映射关系、切片优先级、切片的服务质量等级、切片的最大传输速率、切片占用资源百分比。
  29. 根据权利要求28所述的网络切片的管理装置，其中，所述切片配置信息使用专用过程和/或公共过程进行配置。
  30. 根据权利要求28所述的网络切片的管理装置，其中，所述切片占用资源百分比用于指示所述第一网元中的MAC实体需要为所述切片预留的资源块大小或资源占用百分比；
    所述切片优先级用于指示所述第一网元中的MAC实体调度所述切片数据的优先级；
    所述切片的服务质量等级用于指示所述第一网元中的MAC实体按照所述服务质量等级对所述切片进行调度处理。
  31. 根据权利要求28所述的网络切片的管理装置，其中，所述多个RB和/或LCH映射到一个切片，或者，不同RB和/或LCH映射到不同的切片。
  32. 根据权利要求26所述的网络切片的管理装置，其中，在以下触发条件下，所述发送单元向所述第一网元发送所述切片配置信息：
    在所述接入网侧，发生切片添加事件、或切片删除事件、或切片更新事件时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当所述第二网元接收到第一网元发送的请求切片配置信息时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当用户发生RB和/或LCH建立、删除或重配置过程时，所述第二网元向所述第一网元发送所述切片配置信息；或者，
    当用户RB和/或LCH所属切片发生变化时，所述第二网元向所述第一网元发送所述切片配置信息。
  33. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令配置为执行权利要求1-9任一项所述的网络切片的管理方法，或者10-16任一项所述的网络切片的管理方法。
PCT/CN2017/102888 2016-09-30 2017-09-22 一种网络切片的管理方法及装置、计算机存储介质 WO2018059317A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP17854767.5A EP3522589A4 (en) 2016-09-30 2017-09-22 METHOD AND DEVICE FOR MANAGING A NETWORK LAYER AND COMPUTER STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610877932.3A CN107889155A (zh) 2016-09-30 2016-09-30 一种网络切片的管理方法及装置
CN201610877932.3 2016-09-30

Publications (1)

Publication Number Publication Date
WO2018059317A1 true WO2018059317A1 (zh) 2018-04-05

Family

ID=61762525

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/102888 WO2018059317A1 (zh) 2016-09-30 2017-09-22 一种网络切片的管理方法及装置、计算机存储介质

Country Status (3)

Country Link
EP (1) EP3522589A4 (zh)
CN (1) CN107889155A (zh)
WO (1) WO2018059317A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111385847A (zh) * 2018-12-27 2020-07-07 中国电信股份有限公司 网络切片构建、接入控制、处理方法和装置以及存储介质
CN112470525A (zh) * 2018-07-23 2021-03-09 诺基亚技术有限公司 无线网络中的网络切片约束的传输
EP3934173A4 (en) * 2019-02-28 2022-04-27 Tencent Technology (Shenzhen) Company Limited METHOD, SYSTEM, NETWORK SLOT PROCESSING DEVICE, AND MEDIA
WO2024036753A1 (en) * 2022-08-15 2024-02-22 Nokia Shanghai Bell Co., Ltd. Method and apparatus for slice scheduling

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3782401B1 (en) * 2018-05-03 2022-02-16 Huawei Technologies Co., Ltd. Client device, network control node and upf for transmission and reception of streams of data packets in multi-connectivity
CN110557761B (zh) * 2018-05-30 2023-05-09 中国移动通信有限公司研究院 基于无线资源的处理方法、装置及存储介质
CN110650029B (zh) 2018-06-26 2021-05-18 华为技术有限公司 一种配置方法及装置
CN110661638B (zh) * 2018-06-30 2021-04-20 华为技术有限公司 一种通信方法及装置
CN110662261B (zh) 2018-06-30 2022-06-28 华为技术有限公司 一种网络切片的资源分配方法及装置
CN110691382B (zh) * 2018-07-06 2023-05-09 中国移动通信有限公司研究院 无线资源分配方法及网元设备
GB2577055B (en) 2018-09-11 2021-09-01 Samsung Electronics Co Ltd Improvements in and relating to telecommunication networks
CN110312282B (zh) * 2018-09-28 2021-06-29 华为技术有限公司 数据传输的方法和装置
CN112789832B (zh) * 2018-10-11 2023-06-13 皇家Kpn公司 动态切片优先级处理
CN111148165B (zh) * 2018-11-06 2021-06-01 华为技术有限公司 一种处理网络切片中用户接入的方法及装置
CN110233803B (zh) * 2019-05-16 2021-07-23 中国科学院计算技术研究所 一种传输网络结点的调度装置及方法
CN112566246B (zh) * 2019-09-10 2024-02-27 中磊电子股份有限公司 主控基站及资源分配指示方法
EP4118869A4 (en) * 2020-04-10 2024-01-17 ZTE Corporation TRANSFER QUOTA MANAGEMENT METHOD
CN113709820A (zh) * 2020-05-22 2021-11-26 中国移动通信有限公司研究院 资源分配方法、数据处理方法及设备
CN114268546B (zh) * 2020-09-16 2024-04-09 中国电信股份有限公司 用于网络切片的控制方法及装置
WO2022116115A1 (zh) * 2020-12-03 2022-06-09 Oppo广东移动通信有限公司 上行逻辑信道复用的方法、终端设备及网络设备
CN112533243B (zh) * 2020-12-25 2023-05-26 中国联合网络通信集团有限公司 一种时延上报方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110004456A1 (en) * 2009-07-03 2011-01-06 Snu R&Db Foundation Virtual network embedding method in wireless test-bed network
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN105898894A (zh) * 2016-05-13 2016-08-24 华为技术有限公司 Rrc状态的控制方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102843351B (zh) * 2012-03-31 2016-01-27 华为技术有限公司 一种流媒体业务的处理方法、流媒体服务器及系统
JP6202100B2 (ja) * 2013-10-18 2017-09-27 日本電気株式会社 ネットワーク制御のためのシステム及び方法
CN105376176B (zh) * 2014-08-21 2019-03-19 中国电信股份有限公司 保障移动互联网视频业务服务质量的方法、装置和系统
US10039112B2 (en) * 2014-10-10 2018-07-31 Huawei Technologies Co., Ltd Methods and systems for provisioning a virtual network in software defined networks
CN105592110B (zh) * 2014-10-20 2020-06-30 中兴通讯股份有限公司 一种资源调度方法及装置
CN108282868B (zh) * 2017-01-05 2023-07-18 中兴通讯股份有限公司 控制信令配置方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110004456A1 (en) * 2009-07-03 2011-01-06 Snu R&Db Foundation Virtual network embedding method in wireless test-bed network
CN105813195A (zh) * 2016-05-13 2016-07-27 电信科学技术研究院 一种按需为终端选择移动性管理机制的方法及装置
CN105898894A (zh) * 2016-05-13 2016-08-24 华为技术有限公司 Rrc状态的控制方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP Draft; S2-163429_Update of Solution 6.1.1 v1.0, - 20160710 - 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France", 10 July 2016, article HUAWEI; HISILICON: "Update of Solution 6.1.1", XP051118028 *
ERICSSON: "Network functions virtualization and software management", 1 December 2014 (2014-12-01), pages 1 - 9, XP055303485, Retrieved from the Internet <URL:https://www.ericsson.com/res/docs/whitepapers/network-functions-virtualization-and-software-management.pdf> *
See also references of EP3522589A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112470525A (zh) * 2018-07-23 2021-03-09 诺基亚技术有限公司 无线网络中的网络切片约束的传输
CN111385847A (zh) * 2018-12-27 2020-07-07 中国电信股份有限公司 网络切片构建、接入控制、处理方法和装置以及存储介质
CN111385847B (zh) * 2018-12-27 2022-08-02 中国电信股份有限公司 网络切片构建、接入控制、处理方法和装置以及存储介质
EP3934173A4 (en) * 2019-02-28 2022-04-27 Tencent Technology (Shenzhen) Company Limited METHOD, SYSTEM, NETWORK SLOT PROCESSING DEVICE, AND MEDIA
US11979297B2 (en) 2019-02-28 2024-05-07 Tencent Technology (Shenzhen) Company Limited Network slice processing method, system and device, and storage medium
WO2024036753A1 (en) * 2022-08-15 2024-02-22 Nokia Shanghai Bell Co., Ltd. Method and apparatus for slice scheduling

Also Published As

Publication number Publication date
EP3522589A1 (en) 2019-08-07
CN107889155A (zh) 2018-04-06
EP3522589A4 (en) 2020-06-10

Similar Documents

Publication Publication Date Title
WO2018059317A1 (zh) 一种网络切片的管理方法及装置、计算机存储介质
US12058744B2 (en) Method and device for communication between network entities in cloud LAN environment
WO2018126865A1 (zh) 控制信令配置方法及装置
US10616913B2 (en) Method for supporting multiple scheduling requests in next-generation mobile communication system
US11968649B2 (en) Resource allocation method and device for supporting vehicle communication in next generation mobile communication system
WO2018059268A1 (zh) 网络切片的建立方法和装置
WO2018219229A1 (zh) 通信方法和网络设备
KR20180091050A (ko) 무선국 시스템, 무선 단말, 및 이들의 방법
KR20190116810A (ko) 차세대 이동통신 시스템에서 엑세스 제어 설정 정보를 효율적으로 제공하는 방법 및 장치
RU2656339C2 (ru) Способ конфигурации радионосителя, базовая станция и система
JP7467597B2 (ja) 通信方法、ｓｌｒｂ確立方法、および通信装置
CN106535337A (zh) 一种采用载波汇聚方式传输数据的方法、系统及装置
JP2017508364A (ja) セカンダリ基地局及びマスター基地局によって実行される通信方法、並びに対応する基地局
WO2014183688A1 (zh) 上报bsr的方法、基站和终端、计算机存储介质
WO2017143818A1 (zh) 一种多连接系统中的数据处理方法、装置及计算机存储介质
KR20180099135A (ko) 기지국간 캐리어 집적을 지원하기 위한 패킷 생성 및 분배 방법 및 장치
EP3883318A1 (en) Sidelink communication method and apparatus
CN109644100B (zh) 数据复制下的处理方法及相关设备
CN112567881A (zh) 在下一代移动通信系统中支持无丢失的pdcp版本改变的方法和设备
US20240284287A1 (en) Method and device for handover without suspension of data transmission and reception in next generation mobile communication system
CN112753243A (zh) 无线通信系统中的无线节点通信方法和装置
JP6139166B2 (ja) 移動通信システム
WO2011153927A1 (zh) 一种资源状态过程的映射方法和设备
KR20200089095A (ko) 차세대 이동통신 시스템에서 하위계층 전송결과에 의한 패킷 삭제를 수행하는 방법 및 장치
EP4068844A1 (en) User equipment layer 2 buffer operation in iab networks

Legal Events

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

Ref document number: 17854767

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017854767

Country of ref document: EP

Effective date: 20190430