CN114338404B - Network slice identifier distribution method and device, storage medium and electronic equipment - Google Patents
Network slice identifier distribution method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114338404B CN114338404B CN202111665480.XA CN202111665480A CN114338404B CN 114338404 B CN114338404 B CN 114338404B CN 202111665480 A CN202111665480 A CN 202111665480A CN 114338404 B CN114338404 B CN 114338404B
- Authority
- CN
- China
- Prior art keywords
- network slice
- service
- target
- tac
- tracking area
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 77
- 208000004605 Persistent Truncus Arteriosus Diseases 0.000 claims abstract description 177
- 208000037258 Truncus arteriosus Diseases 0.000 claims abstract description 177
- 238000004590 computer program Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 9
- 238000004891 communication Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 19
- 238000007726 management method Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 7
- 101100425947 Mus musculus Tnfrsf13b gene Proteins 0.000 description 6
- 238000011217 control strategy Methods 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 101000831616 Homo sapiens Protachykinin-1 Proteins 0.000 description 2
- 102100024304 Protachykinin-1 Human genes 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 101000655188 Homo sapiens Tachykinin-3 Proteins 0.000 description 1
- 101000669528 Homo sapiens Tachykinin-4 Proteins 0.000 description 1
- 102100033009 Tachykinin-3 Human genes 0.000 description 1
- 102100039365 Tachykinin-4 Human genes 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The disclosure provides a network slice identifier distribution method, a device, a storage medium and electronic equipment, relates to the technical field of communication, and can solve the problem that the number of network slice identifiers is more consumed when terminal access areas are limited through slicing in the related technology. The related network slice identifier allocation method comprises the following steps: acquiring a service request for accessing a target service area; determining a target tracking area code TAC corresponding to the target service area; if the target TAC comprises a single TAC, network slice identifiers used by single tracking area service are distributed to the target TAC, and if the target TAC comprises at least two TACs, network slice identifiers used by cross tracking area service are distributed to the target TAC, wherein in the network slice identifiers used by single tracking area service, the same network slice identifier is repeatedly used in different TACs. The embodiment of the disclosure can reduce the consumption of network slice identification when terminal access area limitation is performed through slicing.
Description
Technical Field
The disclosure relates to the technical field of communication, and in particular relates to a network slice identifier distribution method, a device, a storage medium and electronic equipment.
Background
At present, compared with 4G (4 th Generation Mobile Communication Technology, fourth generation mobile communication technology), 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) introduces richer QoS (Quality of Service ) characteristics, and can provide different forwarding scheduling policy guarantees for various services with different bandwidth, time delay and bit error rate requirements. With the deep development and application of 5G network technology in each vertical industry, more and more service applications put forward high guarantee requirements on wireless side air interface transmission quality, but the application experience of common 2C service (also called C2C or CTC, which is electronic commerce between individuals) or other lower priority services can be seriously affected by the massive use of air interface priority scheduling technologies such as GBR (Guaranteed Bit Rate ) scheduling in the existing network. Therefore, a terminal access area limitation mode for using absolute priority scheduling guarantee technology services such as GBR needs to be introduced, the service access area range of the 5G terminal is strictly limited, and reasonable allocation and scheduling of wireless resources are realized by combining resource checking and management and control means in the limited area range, so that the application experience influence of the GBR scheduling guarantee services on common 2C services or other lower priority services is reduced.
At present, a method of limiting a terminal access area by slicing needs to allocate a slice ID (identity identifier, hereinafter also referred to as identifier) to each service, and the slice ID is configured at a corresponding base station according to a service access area range to limit the service access area of the terminal, so that the number of slice IDs is more and the service expansion is not facilitated. If the mode of signing the tracking area access control strategy based on PCF (Policy Control Function, strategy control function) is adopted, the granularity of access area limitation is too coarse, which is not beneficial to the resource management and control of the wireless side.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The disclosure provides a network slice identifier distribution method, a device, a storage medium and electronic equipment, which at least overcome the problem that the number of network slice IDs is more consumed when terminal access areas are limited through slicing in the related technology to a certain extent.
According to a first aspect of the present disclosure, there is provided a network slice identifier allocation method, including: acquiring a service request for accessing a target service area; determining a target tracking area code TAC corresponding to the target service area; if the target TAC comprises a single TAC, network slice identifiers used by single tracking area service are distributed for the target TAC, and if the target TAC at least comprises two TACs, network slice identifiers used by cross tracking area service are distributed for the target TAC, wherein in the network slice identifiers used by single tracking area service, the same network slice identifier is repeatedly used in different TACs.
Optionally, the method further comprises: maintaining unassigned network slice identification lists for single tracking area service and cross tracking area service respectively, wherein the unassigned network slice identification list of the single tracking area service records network slice identifications used by the unassigned single tracking area service, and the unassigned network slice identification list of the cross tracking area service records network slice identifications used by the unassigned cross tracking area service; if the target TAC includes a single TAC, allocating a network slice identifier for single tracking area service usage to the target TAC, and if the target TAC includes at least two TACs, allocating a network slice identifier for cross tracking area service usage to the target TAC, including: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the single tracking area service; and if the target TAC at least comprises two TACs, selecting a network slice identifier allocated for the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
Optionally, the method further comprises: if the target TAC comprises a single TAC and the unassigned network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unassigned single tracking area service, selecting the network slice identifier assigned for the target TAC from the unassigned network slice identifier list corresponding to the cross tracking area service.
Optionally, the method further comprises: an assigned slice identity list is maintained for single tracking area traffic and cross tracking area traffic, respectively.
Optionally, the method further comprises: after the network slice identifier is allocated to the target TAC, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross tracking area service.
Optionally, the method further comprises: a used network slice identification list is maintained, wherein the used network slice identification list records network slice identifications which are used before the current network slice identification allocation is carried out.
Optionally, the method further comprises: after the network slice identifier is allocated to the target TAC, determining whether the network slice identifier allocated to the target TAC is used according to the used slice identifier list; if the network slice identifier allocated for the target TAC is used, performing network slice access area capacity expansion configuration; and if the network slice identifier allocated for the target TAC is not used, performing network slice end-to-end configuration.
Optionally, determining the target tracking area code TAC corresponding to the target service area includes: acquiring the information of the circled geographical area; determining a base station identifier or a cell identifier corresponding to the target service area according to the circled geographical area information; and determining the target TAC according to the base station identifier or the cell identifier.
According to a second aspect of the present disclosure, there is provided a network slice identifier allocation apparatus, comprising: the acquisition module is used for acquiring a service request of accessing the target service area; the first determining module is used for determining a target tracking area code TAC corresponding to the target service area; the distribution module is configured to distribute network slice identifiers used for a single tracking area service for the target TAC if the target TAC includes a single TAC, and distribute network slice identifiers used for a cross tracking area service for the target TAC if the target TAC includes at least two TACs, wherein the same network slice identifier is repeatedly used in different TACs in the network slice identifiers used for the single tracking area service.
According to a third aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any one of the network slice identifier assignment methods provided by the embodiments of the present disclosure via execution of the executable instructions.
According to a fourth aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements any one of the network slice identifier allocation methods provided by the embodiments of the present disclosure.
According to the network slice identifier distribution method, the device, the storage medium and the electronic equipment, after the corresponding target TAC is determined according to the acquired service request, network slice identifiers are distributed for the target TAC aiming at single tracking area service and cross tracking area service, and the network slice identifiers used by the single tracking area service can be multiplexed in different tracking areas, so that the use of the network slice identifiers can be reduced when terminal access area limitation is carried out through slicing.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
Fig. 2 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
FIG. 3 is a schematic diagram of a slice identity assignment module according to an embodiment of the present disclosure;
Fig. 4 is a flow diagram illustrating a network slice identity assignment method according to one or more embodiments of the present disclosure;
Fig. 5 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
Fig. 6 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
Fig. 7 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
fig. 8 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
Fig. 9 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
FIG. 10 is a schematic diagram of a network slice identity distribution system provided in accordance with one or more embodiments of the present disclosure;
FIG. 11 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
FIG. 12 is a schematic diagram of a network slice identity assignment device in accordance with one or more embodiments of the present disclosure;
fig. 13 is a schematic structural diagram of an electronic device according to one or more embodiments of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 is a flow diagram of a network slice identity assignment method, as shown in fig. 1, according to one or more embodiments of the present disclosure, the method comprising:
step S102: acquiring a service request for accessing a target service area;
Alternatively, the service request may be used to request access to a target service area, which may be provided as a geographical area.
Step S104: determining a target TAC corresponding to the target service area;
optionally, the target service area may be mapped to a set of base station or cell IDs, so that the target TAC may be mapped according to the base station ID or cell ID, so that the allocated network slice identifier performs slice configuration on the service access service area base station ID or cell ID, and slice access area restriction may be implemented.
Optionally, after determining the target TAC corresponding to the target service area, the resource checking module may be further invoked to initiate resource checking, and the checking may be performed for the service opening requirement, for example, whether the related base station meets the radio bearer resource reservation requirement of the service, whether the requirement of the slice ID configuration number is met, whether the requirement of the air interface scheduling guarantee requirement of the service is met, and after the resource checking is passed, the following step S106 is executed.
Step S106: if the target TAC comprises a single TAC, network slice identifiers used by single tracking area service are distributed for the target TAC, and if the target TAC at least comprises two TACs, network slice identifiers used by cross tracking area service are distributed for the target TAC, wherein in the network slice identifiers used by single tracking area service, the same network slice identifier is repeatedly used in different TACs.
Optionally, a service-allowed terminal access range may be referred to as a single tracking area service if both are within a certain tracking area range; conversely, if a service allows a terminal to access a range, the area where two or more tracking areas are located may be referred to as a cross-tracking area service. If the target TAC comprises a single TAC, the current service is the single tracking area service, network slice identifiers used by the single tracking area service are allocated for the target TAC on the basis of the single tracking area service, and if the target TAC comprises at least two TACs, network slice identifiers used by the cross tracking area service are allocated for the target TAC.
According to the network slice identifier distribution method, after the corresponding target TAC is determined according to the acquired service request, network slice identifiers are distributed for the target TAC aiming at the single tracking area service and the cross tracking area service, and the network slice identifiers used by the single tracking area service can be multiplexed in different tracking areas, so that the use of the network slice identifiers can be reduced when terminal access area limitation is carried out through slicing.
According to the network slice identifier distribution method, a mode based on combination of slice access area limitation and PCF subscription tracking area access control strategies is adopted, and fine control over the range of a terminal service access area can be achieved. By allocating different network slice identifiers for the services with overlapping PCF subscription tracking areas (such as the cross-tracking area service), slice ID multiplexing is performed between the services with non-overlapping PCF subscription tracking areas (such as the single-tracking area service), so that the problem that the number of service slice IDs is more consumed due to the fact that access areas are limited based on slices is solved, and the problem that fine access area management and control cannot be achieved based on the PCF subscription tracking area access control strategy is solved.
Fig. 2 is a flowchart of a network slice identifier assignment method according to one or more embodiments of the present disclosure, as shown in fig. 2, where the method may further include, on the basis of the method shown in fig. 1:
Step S202: maintaining unassigned network slice identification lists for single tracking area service and cross tracking area service respectively, wherein the unassigned network slice identification list of the single tracking area service records network slice identifications used by the unassigned single tracking area service of each tracking area, and the unassigned network slice identification list of the cross tracking area service records network slice identifications used by the unassigned cross tracking area service;
If the target TAC includes a single TAC, allocating a network slice identifier for single tracking area service to the target TAC, and if the target TAC includes at least two TACs, allocating a network slice identifier for cross tracking area service to the target TAC may include:
step S2062: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the single tracking area service;
Step S2064: and if the target TAC at least comprises two TACs, selecting a network slice identifier allocated for the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
Alternatively, the assignment of network slice identities to target TACs may be performed based on a slice identity assignment module. For example, fig. 3 is a schematic diagram of a slice identifier allocation module according to an embodiment of the present disclosure, as shown in fig. 3, in an unallocated network slice identifier list corresponding to a single tracking area service, a slice identifier P M：X1、X2、X3、X4…XM used by a single TAC may be repeatedly allocated in TAC1, TAC2, TAC3, and TAC4 …, where a slice identifier identified as "allocated" indicates that a slice identifier identified as "unallocated" has not yet been allocated; in the list of unassigned network slice identifiers corresponding to the cross-tracking area traffic, the slice identifier P N：Y1、Y2、Y3、Y4…YN used across TACs is not repeatedly assigned, and similarly, the slice identifier identified as "assigned" indicates that the slice identifier identified as "unassigned" has not been assigned.
By maintaining the unassigned network slice identifier list for the single tracking area service and the cross tracking area service respectively, unassigned network slice identifiers can be conveniently and quickly selected from the corresponding unassigned network slice identifier list according to the type of the current TAC service when assigning network slice identifiers for the tracking area service, so that the distribution efficiency of the network slice identifiers is improved.
In addition, because most of the services in the scene are single tracking area services, the network slice identifiers are multiplexed in the single tracking area, so that the required quantity of the network slice identifiers can be saved to a great extent, and the network slice identifiers are not multiplexed in the cross-tracking area scene and cannot cause excessive consumption of the network slice identifiers. The method of the embodiment of the disclosure is simple to implement, and complex network slice identification selection logic is not required to be added.
Fig. 4 is a flowchart illustrating a network slice identifier allocation method according to one or more embodiments of the present disclosure, as shown in fig. 4, where the method may further include, on the basis of the method shown in fig. 1:
Step S402: if the target TAC comprises a single TAC and the unassigned network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unassigned single tracking area service, selecting the network slice identifier assigned for the target TAC from the unassigned network slice identifier list corresponding to the cross tracking area service. Based on this, it can be ensured that the current service request is effectively responded to.
Fig. 5 is a flowchart of a network slice identifier assignment method according to one or more embodiments of the present disclosure, as shown in fig. 5, where the method may further include, on the basis of the method shown in fig. 1:
Step S502: a list of assigned network slice identifications is maintained for single tracking area traffic and cross tracking area traffic, respectively. Still referring to fig. 2 as an example, a network slice identifier identified as "divided" is an assigned network slice identifier. By maintaining the assigned network slice identifier list for the single tracking area service and the cross tracking area service respectively, the assigned network slice identifiers can be effectively recorded, the problem that the same network slice identifier is repeatedly assigned when the network slice identifiers are assigned later can be avoided, and the assignment efficiency of the network slice identifiers is improved.
Fig. 6 is a flowchart of a network slice identifier assignment method according to one or more embodiments of the present disclosure, as shown in fig. 6, where the method may further include, on the basis of the method shown in fig. 1:
Step S602: after the network slice identifier is allocated to the target TAC, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross tracking area service. If the currently allocated network slice identifier is the network slice identifier used by the single tracking area service, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service; if the currently allocated network slice identifier is the network slice identifier used by the cross-tracking area service, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service. After the network slice identifiers are allocated to the TACs each time, the allocated network slice identifiers and the unallocated network slice identifiers corresponding to the single tracking area service are updated in time, and a data basis is provided for the next allocation of the network slice identifiers to the TACs.
Fig. 7 is a flowchart of a network slice identifier assignment method according to one or more embodiments of the present disclosure, as shown in fig. 7, where the method may further include, on the basis of the method shown in fig. 1:
Step S702: a used network slice identification list is maintained, wherein the used network slice identification list records network slice identifications which are used before the current network slice identification allocation is carried out.
The used network slice identifier may be configured in other tracking areas, so that maintaining a used network slice identifier list in the service order system can effectively avoid the network slice identifier from being repeatedly allocated.
Fig. 8 is a flowchart of a network slice identifier assignment method according to one or more embodiments of the present disclosure, as shown in fig. 8, where the method may further include, on the basis of the method shown in fig. 1:
Step S802: after the network slice identifier is allocated to the target TAC, determining whether the network slice identifier allocated to the target TAC is used according to the used network slice identifier list;
Step S804: if the network slice identifier allocated for the target TAC is used, performing network slice access area capacity expansion configuration;
Optionally, if the network slice identifier allocated for the target TAC is already used, the service order system may transmit the network slice identifier allocated for the target TAC and related service parameters to the orchestration control module, so as to initiate capacity expansion configuration of the slice access area, and incorporate the base station identifier or the cell identifier corresponding to the current service access area into the slice access area.
Step S806: and if the network slice identifier allocated for the target TAC is not used, performing network slice end-to-end configuration.
Optionally, if the network slice identifier allocated for the target TAC is not used, the service order system may transmit the network slice identifier allocated for the target TAC and related service parameters to the orchestration control module, initiate an end-to-end new slice configuration flow, and update the used network slice identifier list after the slice configuration is completed.
Fig. 9 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 9, determining a target tracking area code TAC corresponding to the target service area may include:
step S2022: acquiring the information of the circled geographical area;
Optionally, when the service order system accepts the service request, the service area location management module may be invoked to provide a GIS (Geographic Information System or Geo-Information system, geographic information system) map visual circle selection interface, such as presenting a GIS map. Based on this, an access service area (which is one example of the above-described target service area) may be specified by circling a region area on a GIS map.
Step S2024: determining a base station ID or a cell ID corresponding to the target service area according to the circled geographical area information;
step S2026: and determining the target TAC according to the base station ID or the cell ID.
Optionally, the target TAC is mapped to a set of base station IDs or cell IDs according to the circled geographical area, and mapped out according to the base station IDs or cell IDs. Therefore, the distributed network slice identifier performs slice configuration on the service access service area base station ID/cell ID, and the slice access area limitation is realized.
Alternatively, the user may manually input the base station ID or the cell ID, or may define a mapping relationship between the geographical location description and the base station ID or the cell ID in advance, and may map the base station ID or the cell ID according to the location description.
Fig. 10 is a schematic structural diagram of a network slice identifier allocation system provided according to one or more embodiments of the present disclosure, and as shown in fig. 10, the system mainly includes a service order system 1012, a service area location management module 1014, a resource checking module 1016, a slice ID allocation module 1018, an orchestration control module 1020, a 5G core network element 1022, and the like, where the 5G core network element may include: AMF (ACCESS AND Mobility Management Function access and mobility management functions), SMF (Session Management Function, session management functions), UPF (User Plane Function, user plane functions), UDM (Unified DATA MANAGEMENT, unified data management functions), and PCF. The system combines the access control strategy based on the slice access area limitation and PCF subscription tracking area, and realizes the fine control of the terminal service access area range.
Dividing network slice identification into a single tracking area use slice identification group P M and a cross tracking area use slice identification group P N, denoted P M＝{X1,X2,…,XM},PN＝{Y1,Y2,…,YN }, anM+N is less than or equal to the maximum network slice identification number allowed to be configured by the base station.
The network slice identifiers are no longer multiplexed among all the cross-tracking area services, and are distributed in the cross-tracking area use slice identifier group P N no matter whether the areas of the cross-tracking area services coincide or not.
The slice ID allocation module maintains slice ID allocation tables for single tracking area traffic and cross tracking area traffic, respectively:
For single tracking area traffic: for each tracking area, a list of assigned network slice identifiers and a list of unassigned network slice identifiers are established, denoted P TACi and P TACi Undivided , respectively, where i represents the ith TAC, where P TACi Separated into ∪PTACi Undivided =pm,
For cross-tracking area traffic: a list of assigned network slice identifiers and a list of unassigned network slice identifiers, denoted P N Separated into and P N Undivided , respectively, are created, wherein P N Separated into ∪PN Undivided ＝PN,
When the service order system accepts the service request, the service area position management module capability is called, a GIS map visual circle selection interface is provided, an access service area is mapped into a group of base station ID/cell ID, TAC is mapped according to the base station ID/cell ID, and a resource checking module is called to initiate resource checking.
After the resource check is passed, the service order system obtains TAC according to the base station ID/cell ID mapping, and requests to distribute corresponding slice identification to the slice ID distribution module:
If the single tracking area is accessed, the single tracking area service using network slice identification is requested to be allocated to the slice ID allocation module according to the TAC, the slice ID allocation module selects one slice ID from the P TACi Undivided corresponding to the TAC to feed back to the service order system after receiving the request, and the P TACi Undivided list and the P TACi Separated into list are updated. In this step, e.g. corresponding to TAC The traffic is optionally denied or a slice ID assignment is selected from P N Undivided .
If the cross tracking area is accessed, the cross tracking area network slice identification is requested to be allocated to the slice ID allocation module, the slice ID allocation module selects one slice ID from the P N Undivided to feed back to the service order system after receiving the request, and the P N Undivided list and the P N Separated into list are updated.
The service order system maintains a used slice ID table P Has been used , and after the slice ID is obtained from the slice ID allocation module, the service order system firstly performs slice judgment: if it is (Wherein P' is used for indicating a used slice ID table before the current slice allocation, namely the current acquired slice ID is the used slice ID (other services are configured in other tracking areas), the service order system transmits the slice ID and related service parameters to the arrangement control module, initiates the capacity expansion configuration of a slice access area, and brings the base station ID/cell ID corresponding to the current service access area into the slice access area; if it isThe service order system transmits the slice ID and related service parameters to the arrangement control module, initiates a new end-to-end slice configuration flow, and updates the used slice ID table after the slice configuration is completed, so that P Has been used ＝P' Has been used U { acquire slice ID }.
In the slice configuration process, the arrangement control module transmits the TAC corresponding to the service access area to the PCF network element, and the PCF network element completes the creation of the service terminal access tracking area according to the TAC. PCF user access control strategy configuration is carried out on TAC mapped based on base station ID/cell ID, and terminal access tracking area limitation can be realized. Wherein, the creating of the service terminal access tracking area can comprise: configuring a service area; configuring usage rules outside the service area (blocking); configuring a strategy, and associating rules and triggering conditions; configuration packages, association policies, etc.
When a service initiating terminal number signs a service (which can comprise a correlation service slice and DNN, and related policy quotation is completed through signing configuration), the service order system issues signing information to a layout control module, the layout control module completes basic session signing configuration in a UDM network element, and the PCF completes access control policy quotation of a service terminal access tracking area. A configuration instruction may be generated in the PCF network element to reference the terminal number to the configured policy.
Fig. 11 is a flow diagram of a network slice identity assignment method, which may be implemented based on the network slice identity assignment system shown in fig. 10, as shown in fig. 11, in accordance with one or more embodiments of the present disclosure, including:
step S1101: a slicing special line service opening requirement inputting service order system;
The slicing private line service opening requirement can include: the equipment installation addresses at the two ends of the private line, the access mode of the private line, the service reliability requirement, the private line bandwidth requirement, the bandwidth guarantee requirement of the 5G terminal, the air interface 5QI scheduling requirement and the like.
Step S1102: the service order system calls GIS circle selection capability;
Step S1103: the service area position management module feeds back the service area obtained according to the circle selection mapping to the service order system;
step S1104: the business order system requests the resource check from the resource check module;
Step S1105: the resource checking module returns a resource checking result to the service order system;
step S1106: the service order system requests to distribute the service slice ID to the slice ID distribution module;
step S1107: the slice ID distribution module feeds back slice IDs to the service order system;
Step S1108: the service order system judges the slice ID again, if the slice ID is used, the capacity of the slice access area is expanded, and if the slice ID is not used, the slice end-to-end configuration is carried out;
Step S1109: the service order system issues a special slicing line service configuration request to the arrangement control module;
Step S1110: the arrangement control module issues a network element configuration instruction to the 5G core network element;
Step S1111: the arrangement control module returns a slicing special line service configuration result to the service order system;
Step S1112: the business order system receives the input of terminal number signing requirements;
Step S1113: the service order system issues a terminal number signing configuration requirement to the arrangement control module;
step S1114: the arrangement control module issues a network element configuration instruction to the 5G core network element;
Step S1115: the arrangement control module returns a terminal number signing configuration result to the service order system.
Fig. 12 is a schematic structural diagram of a network slice identifier assignment device according to one or more embodiments of the present disclosure, and as shown in fig. 12, the device 1210 includes:
An obtaining module 1212, configured to obtain a service request for accessing to a target service area;
a first determining module 1214, configured to determine a target tracking area code TAC corresponding to the target service area;
An allocation module 1216, configured to allocate a network slice identifier for single tracking area service to the target TAC if the target TAC includes a single TAC, and allocate a network slice identifier for cross tracking area service to the target TAC if the target TAC includes at least two TACs, where the same network slice identifier is reused in different TACs in the network slice identifier for single tracking area service.
In one or more embodiments of the present disclosure, the network slice identifier assigning apparatus may further include:
The first maintenance module is used for maintaining unassigned network slice identification lists for the single tracking area service and the cross-service TAC service respectively, wherein the unassigned network slice identification list of the single tracking area service records network slice identifications used by the unassigned single tracking area service, and the unassigned network slice identification list of the cross-tracking area service records network slice identifications used by the unassigned cross-tracking area service;
The distribution module is specifically configured to: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the single tracking area service; and if the target TAC comprises at least two TACs, selecting a network slice identifier allocated for the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
In one or more embodiments of the present disclosure, the allocation module is specifically configured to:
if the target TAC comprises a single TAC and the unassigned network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unassigned single tracking area service, selecting the network slice identifier assigned for the target TAC from the unassigned network slice identifier list corresponding to the cross tracking area service.
In one or more embodiments of the present disclosure, the network slice identifier assigning apparatus may further include:
and the second maintenance module is used for maintaining an allocated slice identification list for the single tracking area service and the cross tracking area service respectively.
In one or more embodiments of the present disclosure, the network slice identifier assigning apparatus may further include:
and the updating module is used for updating the allocated network slice identification list and the unallocated network slice identification list corresponding to the single tracking area service or updating the allocated network slice identification list and the unallocated network slice identification list corresponding to the cross tracking area service after the network slice identification is allocated for the target TAC.
In one or more embodiments of the present disclosure, the network slice identifier assigning apparatus may further include:
And the third maintenance module is used for maintaining a used network slice identification list, wherein the used network slice identification list records network slice identifications which are used before the current network slice identification allocation is carried out.
In one or more embodiments of the present disclosure, the network slice identifier assigning apparatus may further include:
A second determining module, configured to determine, according to the used slice identifier list, whether the network slice identifier allocated for the target TAC has been used after allocating the network slice identifier for the target TAC;
The first configuration module is used for performing network slice access area capacity expansion configuration if the network slice identifier allocated for the target TAC is used;
And the second configuration module is used for carrying out network slice end-to-end configuration if the network slice identifier allocated for the target TAC is not used.
In one or more embodiments of the present disclosure, the first determining module is specifically configured to:
acquiring information of a circled geographical area;
determining a base station identifier or a cell identifier corresponding to the target service area according to the information of the selected geographic area;
And determining the target TAC according to the base station identifier or the cell identifier.
One or more embodiments of the present disclosure also provide an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any one of the network slice identifier assignment methods provided by the embodiments of the present disclosure via execution of the executable instructions.
One or more embodiments of the present disclosure also provide a computer-readable storage medium having stored thereon a computer program that, when executed by a processor, implements any of the network slice identifier allocation methods provided by the embodiments of the present disclosure.
Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 1300 according to this embodiment of the invention is described below with reference to fig. 13. The electronic device 1300 shown in fig. 13 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 13, the electronic device 1300 is embodied in the form of a general purpose computing device. The components of the electronic device 1300 may include, but are not limited to: the at least one processing unit 1310, the at least one memory unit 1320, and a bus 1330 connecting the different system components (including the memory unit 1320 and the processing unit 1310).
Wherein the storage unit stores program code that is executable by the processing unit 1310 such that the processing unit 1310 performs steps according to various exemplary embodiments of the present invention described in the above section of the "exemplary method" of the present specification. For example, the processing unit 1310 may perform S102 as shown in fig. 1, and obtain a service request for accessing the target service area; s104, determining a target TAC corresponding to the target service area; s106, if the target TAC comprises a single TAC, allocating network slice identifiers used by single tracking area service for the target TAC, and if the target TAC comprises at least two TACs, allocating network slice identifiers used by cross tracking area service for the target TAC, wherein the network slice identifiers used by the single tracking area service are included in the network slice identifiers.
The storage unit 1320 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 13201 and/or cache memory 13202, and may further include Read Only Memory (ROM) 13203.
The storage unit 1320 may also include a program/utility 13204 having a set (at least one) of program modules 13205, such program modules 13205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 1330 may be a local bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or using any of a variety of bus architectures.
The electronic device 1300 may also communicate with one or more external devices 1400 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1300, and/or any device (e.g., router, modem, etc.) that enables the electronic device 1300 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1350. Also, the electronic device 1300 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, for example, the Internet, through a network adapter 1360. As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 over the bus 1330. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 1300, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
A program product for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read-only memory (CD-ROM) and comprise program code and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (11)
1. A network slice identifier allocation method, comprising:
Acquiring a service request for accessing a target service area;
Determining a target tracking area code TAC corresponding to the target service area;
If the target TAC comprises a single TAC, distributing network slice identifiers used by single tracking area service for the target TAC based on an unassigned network slice identifier list, and if the target TAC at least comprises two TACs, distributing network slice identifiers used by cross tracking area service for the target TAC, wherein the same network slice identifier is reused in different TACs in the network slice identifiers used by the single tracking area service;
And the unallocated network slice identifier list of the single tracking area service records network slice identifiers used by the unallocated single tracking area service.
2. The method according to claim 1, wherein the method further comprises:
Maintaining unassigned network slice identification lists for single tracking area service and cross tracking area service respectively, wherein the unassigned network slice identification list of the cross tracking area service records network slice identifications used by the unassigned cross tracking area service;
If the target TAC includes a single TAC, allocating network slice identifiers used by a single tracking area service for the target TAC based on an unallocated network slice identifier list, and if the target TAC includes at least two TACs, allocating network slice identifiers used by a cross tracking area service for the target TAC, including:
If the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the single tracking area service;
And if the target TAC at least comprises two TACs, selecting a network slice identifier allocated for the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
3. The method according to claim 2, wherein the method further comprises:
if the target TAC comprises a single TAC and the unassigned network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unassigned single tracking area service, selecting the network slice identifier assigned for the target TAC from the unassigned network slice identifier list corresponding to the cross tracking area service.
4. The method according to claim 2, wherein the method further comprises:
an assigned slice identity list is maintained for single tracking area traffic and cross tracking area traffic, respectively.
5. The method according to claim 4, wherein the method further comprises:
After the network slice identifier is allocated to the target TAC, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross tracking area service.
6. The method according to claim 1, wherein the method further comprises:
And maintaining a used network slice identifier list, wherein the used network slice identifier list records network slice identifiers which are used before the current network slice identifier distribution.
7. The method of claim 6, wherein the method further comprises:
After the network slice identifier is allocated to the target TAC, determining whether the network slice identifier allocated to the target TAC is used according to the used network slice identifier list;
if the network slice identifier allocated for the target TAC is used, performing network slice access area capacity expansion configuration;
and if the network slice identifier allocated for the target TAC is not used, performing network slice end-to-end configuration.
8. The method according to any one of claims 1 to 7, wherein determining the target tracking area code TAC corresponding to the target service area comprises:
acquiring the information of the circled geographical area;
determining a base station identifier or a cell identifier corresponding to the target service area according to the circled geographical area information;
And determining the target TAC according to the base station identifier or the cell identifier.
9. A network slice identifier allocation apparatus, comprising:
The acquisition module is used for acquiring a service request of accessing the target service area;
The first determining module is used for determining a target tracking area code TAC corresponding to the target service area;
The distribution module is used for distributing network slice identifiers used for the single tracking area service for the target TAC based on an unassigned network slice identifier list if the target TAC comprises a single TAC, and distributing network slice identifiers used for the cross tracking area service for the target TAC if the target TAC at least comprises two TACs, wherein the same network slice identifier is reused in different TACs in the network slice identifiers used for the single tracking area service;
And the unallocated network slice identifier list of the single tracking area service records network slice identifiers used by the unallocated single tracking area service.
10. An electronic device, comprising:
A processor; and
A memory for storing executable instructions of the processor;
wherein the processor is configured to perform the network slice identity allocation method of any one of claims 1 to 8 via execution of the executable instructions.
11. A computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the network slice identity allocation method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665480.XA CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665480.XA CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114338404A CN114338404A (en) | 2022-04-12 |
| CN114338404B true CN114338404B (en) | 2024-08-06 |
Family
ID=81020620
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111665480.XA Active CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114338404B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116170303A (en) * | 2022-12-02 | 2023-05-26 | 中国联合网络通信集团有限公司 | A data configuration method, device, server and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111586667A (en) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | Communication method, terminal equipment and core network equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109429274B (en) * | 2017-09-04 | 2021-10-01 | 华为技术有限公司 | A configuration method and corresponding device |
| US11696213B2 (en) * | 2018-03-15 | 2023-07-04 | Nokia Technologies Oy | Network slice discovery in overlapping network slice deployment |
| US20210392617A1 (en) * | 2020-06-10 | 2021-12-16 | Nokia Technologies Oy | Radio access network notification area (rna) configuration based on service class |
-
2021
- 2021-12-31 CN CN202111665480.XA patent/CN114338404B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111586667A (en) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | Communication method, terminal equipment and core network equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114338404A (en) | 2022-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7183416B2 (en) | Time-dependent networking communication method and apparatus | |
| US20140379928A1 (en) | Method for implementing network using distributed virtual switch, apparatus for performing the same, and network system based on distributed virtual switch | |
| WO2019012735A1 (en) | Ran slice resource management device and ran slice resource management method | |
| JP6024829B2 (en) | Spectrum management system and method | |
| CN109041248A (en) | A kind of car networking resource allocation methods, device, computing device and storage medium | |
| US20130148596A1 (en) | Resource management system and method of centralized base station in mobile communication network | |
| CN112398675B (en) | Network element allocation method and device | |
| US20230176929A1 (en) | Resource allocation method and apparatus based on edge computing | |
| WO2016095524A1 (en) | Resource allocation method and apparatus | |
| JP4995808B2 (en) | Method and apparatus for enhanced content delivery over a data network | |
| WO2020135250A1 (en) | Spectrum device, wireless communication system, wireless communication method and storage medium | |
| JP2023521398A (en) | Resource determination method and equipment | |
| US20060215628A1 (en) | Method and apparatus for providing open loop bandwidth allocation | |
| CN114338404B (en) | Network slice identifier distribution method and device, storage medium and electronic equipment | |
| CN114826920A (en) | Network slice opening method, device, equipment and storage medium | |
| CN115884197B (en) | Method, system and related equipment for managing shared network element based on X interface | |
| CN109076545A (en) | Check the capacity for being used for Multimedia session | |
| CN106973389B (en) | A kind of dynamic spectrum sharing method and device | |
| CN111447077A (en) | A network element configuration method, device and storage medium | |
| CN115002686A (en) | Terminal communication method, device, computer storage medium and electronic equipment | |
| JPH10308752A (en) | Communication device and communication system | |
| CN118316807B (en) | Intelligent campus system based on 5G slice network and access method | |
| CN114339773B (en) | A fair method for dynamic frequency allocation in 4G and 5G networks | |
| CN114340027B (en) | Method, device, system and medium for improving resource utilization of network slicing | |
| EP4426018A1 (en) | Techniques to reduce energy emission of a service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |