WO2017202269A1 - 网络切片标识更新方法、网元、终端及存储介质 - Google Patents

网络切片标识更新方法、网元、终端及存储介质 Download PDF

Info

Publication number
WO2017202269A1
WO2017202269A1 PCT/CN2017/085402 CN2017085402W WO2017202269A1 WO 2017202269 A1 WO2017202269 A1 WO 2017202269A1 CN 2017085402 W CN2017085402 W CN 2017085402W WO 2017202269 A1 WO2017202269 A1 WO 2017202269A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
terminal
network element
currently available
receiving
Prior art date
Application number
PCT/CN2017/085402
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 中国移动通信有限公司研究院
Publication of WO2017202269A1 publication Critical patent/WO2017202269A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a method for updating a slice identifier, a network element, a terminal, and a storage medium.
  • Network Slicing is a logically independent virtual network structure formed by a combination of network functions.
  • the identifier (Identity, ID) of the network slice may be simply referred to as a slice ID.
  • the application scenario of the slice ID may include: when the terminal accesses the network, the slice ID is carried in the initially accessed message, and the network side performs authentication based on the slice ID and other information to determine whether to allow the terminal to access.
  • the terminal may determine a slice of the network slice that can be accessed according to the obtained slice ID.
  • the method for obtaining the slice ID by the terminal usually includes the following two types:
  • the first type pre-configured on the Universal Integrated Circuit Card (UICC) of the terminal;
  • UICC Universal Integrated Circuit Card
  • the communication carrier is configured by Over Air Technology (OTA).
  • OTA Over Air Technology
  • the first type the slice dynamic update cannot be implemented. If it needs to be updated, the terminal may need to hold the terminal to update the communication business hall.
  • the second method adopts the second method, which requires a dedicated application client installed in the terminal or an operating system support of the terminal to correctly parse the slice ID sent by the OTA. In addition, it is also issued The second method is adopted, and when the terminal roams to the outside, the dynamic configuration of the slice ID of the terminal cannot be realized.
  • the embodiment of the present invention is to provide a method for updating a slice identifier, a network element, a terminal, and a storage medium, to solve at least the above problem.
  • a first aspect of the embodiments of the present invention provides a method for updating a slice identifier.
  • the currently available slice ID provided by the storage network element, when the slice identifier ID stored in the terminal has an update requirement including:
  • a second aspect of the embodiments of the present invention provides a method for updating a slice identifier, including:
  • a third aspect of the embodiments of the present invention provides a method for updating a slice identifier, including:
  • the currently available slice ID stored in the subscription database is updated; wherein the slice ID is an identifier of the network slice;
  • the currently available slice ID is provided to the terminal.
  • a fourth aspect of the embodiments of the present invention provides a method for updating a slice identifier, including:
  • a fifth aspect of the embodiments of the present invention provides a network element, where the network element is an access network element, and includes:
  • the first receiving unit is configured to: when the slice identifier ID stored in the terminal has an update requirement, receive a slice ID currently available to the terminal provided by the storage network element;
  • the first sending unit is configured to send, to the terminal, control signaling that carries the currently available slice ID.
  • a sixth aspect of the embodiments of the present invention provides a terminal, where the terminal includes:
  • a second receiving unit configured to receive, by the access network element, a control plane instruction that carries a currently available slice identifier ID;
  • the first update unit is configured to update the slice ID stored in the slice configuration server according to the currently available slice ID.
  • a seventh aspect of the embodiments of the present invention provides a network element, where the network element is a storage network element, the storage network element includes a subscription database, and the subscription database includes:
  • a second update unit configured to: when it is determined that the slice identifier ID used by the terminal is changed, update the currently available slice ID stored in the subscription database; wherein the slice ID is an identifier of the network slice;
  • a third sending unit configured to provide the currently available slice ID to the terminal.
  • the eighth aspect of the embodiment of the present invention provides a network element, where the network element is a storage network element, and the storage network element includes a slice configuration server, where the slice configuration server includes:
  • a fourth receiving unit configured to receive, from the subscription database, a slice identifier ID currently available to the terminal, where the slice ID is an identifier of the network slice;
  • a third updating unit configured to update the slice ID stored in the slice configuration server according to the currently available slice ID.
  • a ninth aspect of the embodiments of the present invention provides a network element, including:
  • a memory configured to store a computer program
  • a communication interface configured to communicate with other devices
  • the processor is respectively connected to the memory and the communication interface, and is configured to implement a slice identifier update method provided by any one or more of the foregoing by executing the computer program.
  • a tenth aspect of the embodiments of the present invention provides a computer storage medium, where the computer storage medium stores a computer program, and after the computer program is executed, the slice identifier update method provided by any one or more of the foregoing can be implemented.
  • the method for updating the slice identifier, the network element, the terminal, and the storage medium provided by the embodiment of the present invention, when the slice ID stored in the terminal has an update requirement, sends a control plane instruction to the terminal, where the control plane instruction carries the currently available slice ID;
  • a terminal capable of communicating with the access network element can identify the control plane command sent by the access network element, so the terminal can obtain the currently available slice ID without installing a dedicated client or operating system;
  • the dynamic update of the slice ID stored in the terminal improves the convenience of dynamically updating the slice ID in the terminal.
  • FIG. 1 is a schematic flowchart of a first method for updating a slice identifier according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for updating a second slice identifier according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart diagram of a third method for updating a slice identifier according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart diagram of a fourth method for updating a slice identifier according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart diagram of a fifth method for updating a slice identifier according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of an access network element according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a subscription database according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a slice configuration server according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a control network element according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flowchart diagram of a sixth method for updating a slice identifier according to an embodiment of the present disclosure
  • FIG. 12 is a schematic flowchart diagram of a seventh method for updating a slice identifier according to an embodiment of the present disclosure
  • FIG. 13 is a schematic flowchart diagram of an eighth method for updating a slice identifier according to an embodiment of the present invention.
  • the slice ID of the authorized use of the terminal is stored.
  • the network element included in the network side may include a network element entity such as a subscription database, a mobility management entity MME, and a base station.
  • the embodiment provides a method for updating a slice identifier, which includes: providing a slice ID currently available to the terminal to the access network element when the slice identifier ID stored in the terminal has an update requirement; wherein the slice ID is a network slice
  • the currently available slice ID is used by the access network element to be sent to the terminal by using control plane signaling; the control plane signaling is a control indication for controlling the terminal to perform a corresponding operation.
  • the method for updating the slice ID in the embodiment is a method for dynamically updating the slice ID stored in the terminal.
  • the method may be a method applied to the storage network element.
  • the storage network element may be a subscription database; the subscription database may be a database set in the home registration server.
  • the subscription database is used to store subscription data.
  • the subscription data may include various subscription data such as a communication number used by the terminal, a communication package selected for use, and the like.
  • the storage network element may also be a new dedicated network element in the network, which may be referred to as a slice configuration server.
  • the slice configuration server is one of the network elements on the network side, and can be directly connected to the access network element, and can be used for storage.
  • the slice ID used by the terminal is a database of the slice ID of the storage terminal.
  • the storage network element in the embodiment determines that the slice ID stored in the terminal has an update requirement
  • the slice ID currently available to the terminal is sent to the access network element, and the access network element sends the identifier to the terminal.
  • the currently available slice ID is sent in the manner of a control plane instruction.
  • the communication network can be divided into a control plane and a data plane; usually, the control plane is used to transmit control commands, and the data plane is used to transmit service data.
  • the access network element is a type of control network element, It is a device capable of establishing a wireless connection directly with a terminal, for example, an evolved base station eNB.
  • the control plane command is information that can be directly recognized and parsed by the existing terminal. It is possible to complete the identification and analysis of the currently available ID without installing a dedicated client or an operating system with special functions, and on the other hand, the terminal is implemented.
  • the dynamic update of the stored slice ID ensures that the update is more convenient.
  • the storage network element is not a communication network element of the communication network, and is not a server such as a device management (DM) server corresponding to the OTA technology.
  • the DM server is a network device connected to a communication network, not a communication network element of the communication network.
  • the information exchanged between the communication network element and the terminal can be recognized by the terminal having the communication operating system.
  • the communication network element can realize the information exchange of each communication network element in different cities and different PLMNs.
  • the storage network element can still be accessed through the communication network to the communication network element to assist the network element. Update of the slice ID in the terminal.
  • the method includes multiple cases, and two types are provided below:
  • the slice ID authorized by the terminal changes.
  • the slice ID corresponds to the PLMN. If the correspondence between the ID and the PLMN changes, the slice ID used by the terminal is changed.
  • one of the PLMNs may correspond to one or more network slices, ie one or more slice IDs. For another example, if the terminal is authorized to use all or part of the network slice corresponding to one PLMN, the slice ID that the terminal is authorized to use may also change.
  • the terminal When the public land mobile network PLMN corresponding to the location of the terminal moves from the first public land mobile network PLMN to the second PLMN, the terminal needs to store the slice ID corresponding to the second PLMN.
  • a terminal using China Mobile's communication network may only store a slice ID corresponding to a China Mobile PLMN, but currently the terminal moves from one PLMN coverage to another PLMN. At this time, the terminal needs to use the current The slice ID corresponding to the PLMN. Obviously, the ID stored in the terminal at this time also has an updated requirement.
  • the method further includes: jointly storing the slice ID authorized by the terminal and the subscription information of the terminal.
  • the slice ID authorized by the terminal is stored together with the subscription information of the terminal.
  • the information of the terminal can be conveniently and collectively managed, and on the other hand, other network elements are not specifically configured to store the slice ID, and the existing The compatibility of the technology is large; in addition, since the subscription information is stored in the subscription database, it is the entire communication network, and different network areas can be accessed, so that when the terminal roams, the slice ID can still be updated.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • this embodiment provides a method for updating a slice identifier, including:
  • Step S110 Receive, when the slice identifier ID stored in the terminal has an update requirement, a slice ID currently available to the terminal provided by the storage network element, where the slice ID is an identifier of the network slice.
  • Step S120 Send, to the terminal, control signaling carrying the currently available slice ID, where the control plane signaling is a control indication for controlling the terminal to perform a corresponding operation.
  • the method for updating a slice identifier may be a method applied to an access network element.
  • the access network element in this embodiment may include an access device of various wireless networks, for example, a base station or the like.
  • the step S110 includes receiving, from the storage network element, a currently available slice ID of the terminal.
  • a control plane command is sent to the terminal, where the control plane command carries the currently available slice ID, and the control plane command received by the terminal does not need to set a special client or an operating system with special resolution function. Parsing the control plane command to extract the current available The slice ID is used to update the slice ID stored in the terminal.
  • the step S110 includes:
  • the step S110 may include: when receiving an access request sent by the terminal that does not carry a slice ID, sending a query request to the storage network element;
  • the terminal when the terminal switches the PLMN or receives the update indication, it finds that the slice ID stored by the terminal needs to be updated, and then sends an access request to the access network element, and the request does not carry the slice ID.
  • the incoming network element knows that it needs to assist the terminal to query the currently available slice ID, and then sends a query request to the storage network element; and then receives the currently available slice ID returned by the storage network element.
  • the storage network element may include a subscription database or a slice configuration server.
  • the step S110 may specifically include: when receiving an access request sent by the terminal that does not carry a slice ID, sending the query request to the slice configuration server; receiving the slice configuration server based on the query The currently available slice ID returned by the request.
  • the currently available slice ID is determined by the slice configuration server querying a local database; wherein the currently available slice ID is received by the slice configuration server from a subscription database in advance; or the currently available slice ID is The slice configuration server queries the contract database for determination.
  • the slice configuration server can obtain the latest from the subscription database.
  • the slice ID may also be accessed by the subscription database to obtain the currently available slice ID after receiving the query request.
  • the method further includes: receiving an update indication provided by the storage network element; sending the update indication to the terminal; wherein the update indication is used to indicate that the terminal deletes a current terminal The stored slice ID and the access request that does not carry the slice ID.
  • the update indication is actively sent, and the update indication triggers the terminal to initiate a slice ID update process.
  • the update indication is sent to the terminal through the access network element.
  • the terminal After receiving the update indication, the terminal initiates an access request that does not carry the slice ID.
  • the access network element such as the base station knows that the terminal needs to assist the terminal to query the currently available slice ID, so as to implement automatic update of the slice ID in the terminal. .
  • sending a query request to the storage network element including: receiving, when the terminal sends, does not carry When the access request of the slice ID is requested, the control network element sends a query request to the subscription database.
  • the step S110 may include: receiving, by the control network element, the currently available slice ID provided by the subscription database.
  • the control network element may be a functional entity such as a mobility management entity MME, a connection management network element, or an access management network element.
  • the step S120 may include:
  • the reconnect message is used to instruct the terminal to release the current connection, update the slice ID stored in the slice configuration server according to the currently available slice ID, and use the currently available after releasing the current connection.
  • the slice ID re-requests access.
  • the step S120 may include:
  • the offline message is used to instruct the terminal to release the current connection, and update the slice ID stored in the slice configuration server according to the currently available slice ID, and the next time there is an access requirement,
  • the current available slice ID requests access.
  • the method further includes: when the terminal is in the non-connected state, sending, to the terminal, paging signaling that carries the currently available slice ID;
  • the paging signaling is used to instruct the terminal to update a slice ID stored in the slice configuration server according to the currently available slice ID, and carry the currently available slice when there is an access requirement next time. ID request access.
  • the terminal that is not in the connected state is first switched to the connected state, and then the control plane command such as the reconnect message or the offline message is used to update the currently available slice ID stored in the terminal, so that it can be timely Dynamic update of the ID of the slice stored in the terminal is performed.
  • the control plane command such as the reconnect message or the offline message is used to update the currently available slice ID stored in the terminal, so that it can be timely Dynamic update of the ID of the slice stored in the terminal is performed.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • this embodiment provides a method for updating a slice identifier, including:
  • Step S210 Receive a control plane command that is sent by the access network element and that carries the currently available slice identifier ID.
  • the slice ID is an identifier of the network slice, and the control plane signaling is used to control the terminal to perform the corresponding Control indication of operation;
  • Step S220 Update the slice ID stored in the slice configuration server according to the currently available slice ID.
  • the method may further include: step S230.
  • the step S230 may include responding to the control plane instruction based on the currently available slice ID.
  • the method described in this embodiment is applied to a slice identifier update method in a terminal.
  • the terminal receives the currently available slice ID by receiving the control plane network element, and updates the slice ID stored in the terminal according to the currently available slice ID; and responds to the control plane instruction.
  • this method in this embodiment can obviously realize the dynamic of the slice ID stored in the middle end. Updates, without the need to install a dedicated client or a dedicated operating system with special features, simplifies the dynamic update of the slice ID in the terminal.
  • control plane instruction may be any control plane instruction
  • the currently available slice ID is carried in a control plane instruction
  • control plane signaling may include sending the current
  • the signaling of the available slice ID may also be non-dedicated control plane signaling.
  • the non-dedicated control plane signaling carries other control indications in addition to the currently available slice ID.
  • the control plane command can be used to perform the corresponding operation
  • the slice ID stored in the terminal can be updated, and the number of transmissions or the number of control plane signaling transmissions can be reduced, which is compared with the use of dedicated control plane signaling.
  • the currently available slice ID can reduce signaling overhead.
  • control plane instruction includes a reconnection message
  • step S230 may include:
  • an access request carrying the currently available slice ID is sent to the access network element.
  • control plane instruction includes an offline message
  • step S230 may include:
  • an access request carrying the currently available slice ID is sent to the access network element.
  • the slice ID of the PLMN corresponding to the current location may not be stored in the terminal, and the terminal may actively initiate an access request that does not carry the slice ID to trigger the slice ID.
  • Update operation For example, the foregoing first PLMN and the second PLMN are different PLMNs, and the second PLMN can be regarded as the PLMN where the terminal is currently located.
  • the method further includes: when the public land mobile network PLMN corresponding to the location of the terminal moves from the first public land mobile network PLMN to the second PLMN, and the second terminal is not stored in the terminal
  • the slice ID corresponding to the PLMN sends the access request that does not carry the slice ID to the access network element.
  • the slice ID used by the terminal is changed on the network side and is invisible to the terminal.
  • the terminal may receive an update indication of the access network element forwarding. Therefore, the method in this embodiment further includes: receiving an update indication sent by the access network element, where the update indication is provided by a storage network element; and deleting the currently stored slice ID according to the update indication; The access request that does not carry the slice ID is sent to the access network element.
  • the access network element such as the base station sends the control plane network element to the terminal. That is, the step S210 includes: after receiving the access request that does not carry the slice ID, the terminal receives the control plane instruction from the access network element.
  • the step S210 may be: a control plane instruction sent by the access network element after receiving the access request sent by the terminal that does not carry the slice ID.
  • the embodiment provides a method for dynamically updating a slice ID stored in a terminal, which has the characteristics of being simple to implement.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • this embodiment provides a method for updating a slice identifier, including:
  • Step S310 When it is determined that the slice identifier ID used by the terminal is changed, the currently available slice ID stored in the subscription database is updated; wherein the slice ID is an identifier of the network slice;
  • Step S320 The currently available slice ID is provided to the terminal, where the currently available slice ID is used by the access network element to be sent to the terminal in the control plane network element.
  • the slice identifier update method in this embodiment may be a method applied in a subscription database.
  • the subscription database stores the subscription information of the terminal together with the slice ID authorized by the terminal to facilitate information sharing in the communication network.
  • the step S310 or the like finds that the terminal stored in the subscription database is currently available when the slice ID authorized by the terminal changes.
  • the slice ID and the currently available slice ID are provided to the terminal to facilitate communication of the subsequent terminal. For example, by controlling the network element and the access network element, the control plane command carrying the currently available slice ID is sent to the terminal, so that the terminal can easily analyze the control plane command.
  • the step S320 may include:
  • the currently available slice ID is used by the control network element to control the access network element to send control plane signaling to the terminal; wherein the control plane signaling carries the currently available ID; the control plane
  • the signaling is a control indication for controlling the terminal to perform a corresponding operation.
  • the control plane network element here may be respectively connected to the subscription database and the network element connected to the access network element.
  • the subscription database and the access network element do not have a direct link before, and the direct link here is a point-to-point link that does not pass through other communication nodes.
  • the step S320 may include:
  • the currently available slice ID is used to be returned to the access network element when the slice configuration server receives the query request of the access network element, and is sent to the terminal by using the access network element.
  • the subscription server will update the currently available slice ID, so that the access network can be queried to the slice configuration server directly connected to the network, and the access network element is not received by the terminal.
  • the control network element needs to go to the subscription database to query the currently used slice ID, which can reduce information interaction, improve the update rate of the slice ID stored in the terminal, and reduce the delay.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • this embodiment provides a method for updating a slice identifier, including:
  • Step S410 Receive, from the subscription database, a slice identifier ID currently available to the terminal, where the slice ID is an identifier of the network slice.
  • Step S420 Update the slice configuration server according to the currently available slice ID.
  • the stored slice ID, where the currently available slice ID is stored for being sent to the terminal by the access network element.
  • the slice identifier update method provided in this embodiment may be a method applied to a slice configuration server.
  • the step S410 may be to receive the slice ID currently available to the terminal from the subscription database, and update the slice ID stored in the slice configuration server, so as to improve the update efficiency when the terminal initiates the slice ID update process.
  • the step S410 can include multiple implementations, and two are provided below:
  • the first one: the step S410 may include:
  • step S410 may further include:
  • the method provided in this embodiment is applied to a slice configuration server, which is a network element for dedicated storage and configuration of a slice ID authorized by the terminal, and can directly establish a connection with the access network element.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • this embodiment provides a method for updating a slice identifier, including:
  • Step S510 Receive a slice identifier ID currently available to the terminal, where the currently available slice ID is provided by the storage network element when the slice identifier ID stored in the terminal has an update requirement;
  • Step S520 Send the currently available slice ID to the access network element.
  • the slice ID is an identifier of the network slice, and the currently available slice ID is used for the access network element to send to the terminal by using control plane signaling; the control plane signaling is used for controlling the The terminal performs a control indication of the corresponding operation.
  • This embodiment provides a method for updating a slice identifier, which may be applied to an information processing method in a control network element.
  • the control network element in this embodiment may include a network entity such as an MME.
  • Step S510 may include receiving a slice ID currently available to the terminal, and sending the ID received from the storage network element to the access network element in step S520, and transmitting the identifier to the terminal by the access network element.
  • the storage network element in this embodiment may include a subscription database or a slice configuration server.
  • the method further includes:
  • the update indication is used to instruct the terminal to delete a slice ID currently stored in the terminal, and send the access request that does not carry a slice ID.
  • the control network element is in the trigger message, and the access network element is controlled to send an update indication to the terminal, and after receiving the update indication, the terminal sends the slice ID that is not carried.
  • the access request triggers the update of the slice ID in the terminal.
  • the method further includes:
  • the step S510 can include:
  • the control network element in this embodiment may include a network element such as a mobility management entity.
  • the control plane network element may control the access network element to send a control plane command to the terminal, and notify the terminal of the currently available slice ID in a manner of controlling the surface command, so that the terminal can dynamically update the stored slice ID, and the terminal does not need to install an additional client. end.
  • the embodiment provides a network element, where the network element is an access network element, and includes:
  • the first receiving unit 110 is configured to receive, when the slice identifier ID stored in the terminal has an update requirement, a slice ID currently available to the terminal provided by the storage network element, where the slice ID is an identifier of the network slice;
  • the first sending unit 120 is configured to send, to the terminal, control signaling that carries the currently available slice ID, where the control plane signaling is a control indication used to control the terminal to perform a corresponding operation.
  • the network element provided in this embodiment is an access network element such as a base station, and is a network element that can directly perform wireless interaction with the terminal.
  • the first receiving unit 110 and the first sending unit 120 in this embodiment may correspond to a communication interface in an access network element such as a base station.
  • the access network element in this embodiment sends a control plane command to the terminal, triggering the terminal to dynamically update the slice ID, and does not need to install an additional client or an operating system in the terminal, which is simple and efficient.
  • the first receiving unit 110 is configured to receive, by the control network element, control plane signaling that carries the currently available slice ID, where the currently available slice ID is the The storage network element is provided when it is determined that the slice ID authorized by the terminal has an update requirement.
  • the first sending unit 120 is further configured to: when receiving an access request sent by the terminal that does not carry a slice ID, send a query request to the storage network element;
  • the receiving unit 110 is further configured to receive the currently available slice ID provided by the storage network element, where the currently available slice ID is provided by the storage network element based on the query request.
  • the first sending unit 120 is configured to send the query request to the slice configuration server when receiving an access request sent by the terminal that does not carry a slice ID;
  • the first receiving unit 110 is configured to receive the slice configuration server based on the query The currently available slice ID returned by the request.
  • the network element of the slice ID authorized by the storage terminal may include a network element such as a subscription database and a slice configuration server, but is not limited to the two network elements.
  • the access network element queries the currently available slice ID from the slice service configurator, the currently available slice ID is determined by the slice configuration server querying a local database; wherein the currently available slice ID is The slice configuration server is received in advance from the subscription database; or the currently available slice ID is determined by the slice configuration server query subscription database.
  • the specific structure of the first sending unit 120 and the first receiving unit 110 may be as follows when the access network element obtains the currently available slice ID from the subscription database.
  • the first receiving unit 110 is further configured to receive an update indication provided by the storage network element; the first sending unit 120 is further configured to send the update indication to the terminal; wherein the update The indication is used to instruct the terminal to delete the slice ID currently stored in the terminal, and send the access request that does not carry the slice ID.
  • This triggers the update of the slice ID stored in the terminal by transmitting an update indication to the terminal.
  • the first sending unit 120 is further configured to: when receiving an access request that is sent by the terminal and does not carry a slice ID, send a query request to the subscription database by controlling the network element; the first receiving unit 110.
  • the method further includes receiving, by using the control network element, the currently available slice ID provided by the subscription database.
  • the update of the slice ID is triggered by the terminal itself.
  • the control plane instructions may include control plane signaling such as a reconnect message, an offline message, or a physical downlink control message.
  • the first sending unit 120 is configured to send, to the terminal, a reconnect message carrying the currently available slice ID when the terminal is in a connected state;
  • the reconnect message is used to instruct the terminal to release the current connection, and re-request access with the currently available slice ID after releasing the current connection.
  • the first sending unit is configured to send, when the terminal is in a connected state, a downlink message carrying the currently available slice ID to the terminal;
  • the offline message is used to instruct the terminal to release the current connection, and request access by using the currently available slice ID when there is an access requirement next time.
  • the terminal if the sent control plane command is a reconnect message, the terminal must re-initiate the connection within a predetermined time after the terminal disconnects the current connection. If the sent control plane command is an offline message, the terminal disconnects the current connection, and waits until there is a next access request, then sends a connection request, disconnects the current connection time point, and initiates the next access request.
  • the time interval between the time points is not fixed, which depends on the access requirements of the terminal. Usually, the terminal has data transmission, and there will be access requirements. If the terminal does not currently have access requirements, the access request will not be initiated again immediately.
  • the first sending unit 120 is further configured to: when the terminal is in a non-connected state, send paging signaling to the terminal; where the paging signaling is used to indicate the terminal and the terminal
  • the access network element establishes a connection and switches to the connection state.
  • the terminal is in the non-connected state, in order to update the slice ID in the terminal in time, in the embodiment, before sending the control plane instruction, the paging signaling is sent first, and the terminal is prompted to enter the connected state.
  • the access network element in this embodiment can assist the terminal to dynamically update the slice ID, and the implementation is simple.
  • the hardware implementation is provided for the slice identifier update method in the first embodiment.
  • the embodiment provides a terminal, where the terminal includes:
  • the second receiving unit 210 is configured to receive, by the access network element, a control plane instruction that carries a currently available slice identifier ID, where the slice ID is an identifier of a network slice, and the control plane signaling is used for control
  • the terminal performs a control indication of a corresponding operation
  • the first update unit 220 is configured to update the slice ID stored in the slice configuration server according to the currently available slice ID.
  • the terminal in this embodiment may be various types of terminals.
  • the terminal can be a multimode terminal or a single Mode terminal.
  • the second receiving unit 210 may be configured to receive the control plane command from the access network element, where the control plane command carries the currently available slice ID, and the terminal does not need to install a dedicated client or The operating system recognizes the currently available slice ID, and obviously the update process is simple.
  • the first updating unit 220 may correspond to an information processing structure such as a processor or a processing circuit in the terminal, and the information processing structure may be a central processing unit, a microprocessor, a digital signal processor, a programmable array or an application specific integrated circuit. Wait.
  • an information processing structure such as a processor or a processing circuit in the terminal
  • the information processing structure may be a central processing unit, a microprocessor, a digital signal processor, a programmable array or an application specific integrated circuit. Wait.
  • control plane instruction may include a reconnect message;
  • terminal further includes: a connection unit, configured to release the current connection in response to the reconnect message;
  • a second sending unit configured to: after releasing the current connection, send an access request that carries the currently available slice ID to the access network element.
  • connection unit and the second sending unit may be configured to communicate with the access network element.
  • control plane command is a reconnection message, and the terminal disconnects the current connection. And access again.
  • control plane instructions may include an offline message
  • the terminal further includes:
  • a connecting unit configured to release the current connection in response to the offline message
  • the second sending unit is configured to, when there is a next access request, send an access request carrying the currently available slice ID to the access network element.
  • connection unit and the second sending unit in this embodiment is the same or similar, but in the embodiment, the control plane instruction is an offline message.
  • the control plane instruction is an offline message.
  • the second receiving unit 210 is further configured to receive an update indication sent by the access network element, where the update indication is provided by a storage network element, and the terminal further includes: a second update unit, configured to delete the currently stored slice ID according to the update indication, and a connection unit, configured to send, to the access network element, an access request that does not carry a slice ID; the second receiving unit, specifically Receiving, by the access network element, the control plane instruction returned based on the access request that does not carry a slice ID.
  • the update process of the slice ID is initiated by receiving an update indication provided by the storage network element from the access network element.
  • the terminal further includes:
  • a second sending unit configured to move from the first public land mobile network PLMN to the second PLMN when the public land mobile network PLMN corresponding to the location of the terminal is located, and the second PLMN is not stored in the terminal
  • the slice ID can be initiated by the terminal itself.
  • the terminal provided in this embodiment is applicable to at least the method for updating the slice ID described in the second embodiment of the method, and has the characteristics of simple implementation.
  • the embodiment provides a network element, where the network element is a storage network element, and the storage network element includes a subscription database, including:
  • the second update unit 310 is configured to: when it is determined that the slice identifier ID used by the terminal is changed, update the currently available slice ID stored in the subscription database; wherein the slice ID is an identifier of the network slice;
  • the third sending unit 320 is configured to provide the currently available slice ID to the terminal, where the currently available slice ID is used for the access network element to be carried in the control plane network element and sent to the terminal.
  • the network element provided in this embodiment is a subscription database, and the subscription database may correspond to a network element such as an HSS.
  • the subscription database is originally a database storing subscription data of the terminal.
  • the subscription database in the example is further configured to store a slice ID authorized by the terminal.
  • the second update unit 310 may correspond to various information processing structures of the subscription database.
  • information processing structures refer to corresponding parts in the foregoing embodiments, which are not described in detail herein.
  • the third sending unit 320 is configured to send the currently available slice ID to the control network element, where the currently available slice ID is configured to allow the control network element to control the access network element direction.
  • the terminal sends control plane signaling, where the control plane signaling carries the currently available ID; the control plane signaling is a control indication used to control the terminal to perform a corresponding operation.
  • the subscription database is not directly connected to the terminal and the access network element, and the currently available slice ID can be sent to the terminal by using the control network element and the access network element.
  • the second update unit 310 is configured to send the currently available slice ID to a slice configuration server; the currently available slice ID is used when the slice configuration server receives the connection When the query request is sent to the network element, it is returned to the access network element, and is sent to the terminal by using the access network element.
  • the subscription database of the embodiment not only stores the subscription data, but also stores the slice ID authorized by the terminal, and facilitates the dynamic update of the slice ID in the terminal, and provides an implementation structure for the slice identifier update method provided in the third embodiment.
  • the embodiment provides a network element, where the network element is a storage network element, and the storage network element includes a slice configuration server, including:
  • the fourth receiving unit 410 is configured to receive, from the subscription database, a slice identifier ID currently available to the terminal, where the slice ID is an identifier of the network slice.
  • the third update unit 420 is configured to update the slice ID stored in the slice configuration server according to the currently available slice ID, where the currently available slice ID is used to be sent to the access network element.
  • the terminal is configured to update the slice ID stored in the slice configuration server according to the currently available slice ID, where the currently available slice ID is used to be sent to the access network element.
  • the fourth receiving unit 410 in this embodiment may correspond to a communication interface of the slice configuration server.
  • the communication interface here can be a wired interface or a wireless interface.
  • the slice configuration server may be connected to the foregoing subscription database, and the other end is connected to the access network element, and serves as an intermediate node between the subscription database and the access network element, so that the access network element needs to query the currently available slice ID of the terminal.
  • the database is poor from the contracted database, it can also be queried from the slicing configuration server, and the query is queried from the slicing configuration server. Since there is no need to pass through one or more control network elements in the middle, the speed is fast.
  • the network element further includes:
  • a fourth sending unit configured to: when receiving the query request sent by the access network element, send an acquisition request to the subscription database; the fourth receiving unit is configured to receive the subscription data and return according to the acquiring request The currently available slice ID;
  • the fourth receiving unit 410 is specifically configured to receive the currently available slice ID that is sent when the terminal database updates the slice ID authorized by the terminal.
  • the embodiment provides a subscription database, which can assist the terminal to dynamically update the stored slice ID, and can be shared in the entire network in the communication network, and the slice ID can be updated even if the terminal roams from one area to another.
  • this embodiment provides a network element, where the network element is a control network element, and includes:
  • the fifth receiving unit 510 is configured to receive a slice identifier ID currently available to the terminal, where the currently available slice ID is provided by the storage network element when the slice identifier ID stored in the terminal has an update requirement;
  • the fifth sending unit 520 is configured to send the currently available slice ID to the access network element
  • the slice ID is an identifier of the network slice, and the currently available slice ID is used for the access network element to send to the terminal by using control plane signaling; the control plane signaling is used for Controlling the terminal to perform a control indication of the corresponding operation.
  • the network element is a control network element, and may correspond to a structure such as an MME.
  • the network element is a network element directly connected to the access network element, and is generally preferably a network element that is also directly connected to the subscription database.
  • the control network element in this embodiment will assist the terminal to dynamically update the slice ID.
  • the fifth receiving unit 510 and the fifth sending unit 520 may correspond to a communication interface that controls a network element, and can be used for information interaction with other network elements.
  • the fifth receiving unit 510 is further configured to receive a trigger message sent by the storage network element.
  • the fifth sending unit 520 is further configured to send, by the access network element, an update indication to the terminal according to the trigger message, where the update indication is used to instruct the terminal to delete the terminal.
  • the control network element sends an update indication to the terminal, prompting the terminal to initiate an access request for the slice ID update.
  • the fifth receiving unit 510 is configured to receive an acquisition request sent by the access network element, where the obtaining request is that the access network element does not carry the terminal after receiving the terminal.
  • the fifth sending unit 520 is further configured to send the obtaining request to the storage network element, and the fifth receiving unit 510 is specifically configured to receive the storage network element.
  • the currently available slice ID returned based on the fetch request.
  • the control network element may consider that the terminal initiates the update process of the slice ID.
  • the embodiment of the invention provides a network element, including:
  • a memory configured to store a computer program
  • a communication interface configured to communicate with other devices
  • the processor is respectively connected to the memory and the communication interface, and is configured to implement the slice identifier update method provided by any one or more of the foregoing technical solutions by executing the computer program.
  • the network element provided in this embodiment may be the foregoing various communication devices that access the network, such as the storage network element and the terminal.
  • the processor can be a central processing unit, a microprocessor, a digital signal processor or application processor or a programmable array or the like.
  • the processor can be coupled to a memory and communication interface via a bus, such as an integrated circuit (IIC) bus.
  • IIC integrated circuit
  • the embodiment of the present invention provides a computer storage medium, wherein the computer storage medium stores a computer program, and the computer program is executed to implement the slice identification update method provided by any one or more of the foregoing technical solutions.
  • the computer storage medium provided in this embodiment may be a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes.
  • ROM read-only memory
  • RAM random access memory
  • Media optional as non-transitory storage media.
  • This example provides a method for updating a slice ID stored in a terminal, including:
  • the control plane signaling is sent to the terminal, and the control plane signaling carries the change.
  • the slice ID currently available to the terminal For example, the terminal is caused to reconnect with the connection, and the terminal acquires new slice ID access configuration information, and carries the new slice ID to access the network.
  • a functional entity or network element in the network serves as a slice access authorization storage entity of the terminal, such as an HSS subscribed by the terminal, corresponding to the storage network element, and a terminal is stored in a network (such as a PLMN).
  • the information of the slice ID used that is, the network slice access authorization information.
  • Such as a certain end A list of slice IDs can be used under a certain PLMN corresponding to the end IMSI.
  • the slice ID configuration information of a terminal in the slice access authorization storage entity changes, such as adding or deleting the correspondence relationship of the slice IDs under a certain PLMN.
  • the authorized storage entity determines that the terminal is currently accessing the network with a slice ID, and the right of the terminal to use the slice ID is modified, the subscription information network element (or network function) notifies the network first entity.
  • the first entity of the network may be a control plane network element or related network function, such as a mobility management MME, a connection management function, and the like, and a terminal connection management related function.
  • the first entity herein may correspond to the foregoing control network element and the like.
  • the network first entity may also be a slice configuration server.
  • the slice ID configuration server is an entity that can configure the terminal slice ID.
  • the first entity of the network provides a reconnect message or an offline message sent to the terminal.
  • the message cause value is reflected by the change of the slice subscription, such as the slice ID change.
  • the terminal When the terminal is in a certain signaling non-connection state, the terminal can be made reachable by paging or the like, that is, the terminal is in a connected state.
  • Subsequent processing operations corresponding to the slice ID may include multiple modes, which are respectively described below:
  • the first subsequent processing operation is provided herein, including:
  • Step 4.1 The first entity directly carries the PLMN and the updated slice ID in the reconnect message or the offline message, and sends the same to the terminal through the access network element.
  • Step 4.1 may be performed after receiving an update indication of the core network trigger slice ID.
  • the indication may be that the control plane network element is triggered, and the indication of the control plane instruction is directly sent to the terminal by the access network element.
  • Step 5.1 After receiving the slice ID, the UE updates the information of the slice ID corresponding to the PLMN configured on the mobile phone card, and specifically includes: the terminal receives the control plane command that is sent by the access network element and carries the slice ID.
  • Step 6.1 The terminal re-initiates the connection establishment request and carries the new slice ID in the connection message; the network provides the slice ID service for it.
  • the connection establishment request initiated by this step is as shown in Figure 11. Reconnection request.
  • a second subsequent processing operation including:
  • Step 4.2 The control plane network element carries a slice ID update indication in the reconnect or offline message, and sends the identifier to the terminal.
  • Step 5.2 After receiving the control plane command, the terminal deletes the slice ID list accessible by the terminal under the PLMN stored in the terminal; where the slice ID list is a table storing one or more slice IDs.
  • Step 6.2 The terminal initiates an access procedure, and the slice ID field is blank.
  • the network queries the slice ID configuration server for a new slice ID list corresponding to the PLMN.
  • the slice ID field is empty, which means that the slice ID is not carried.
  • Step 7.2 The slice configuration server queries the subscription information from the subscription information to the corresponding slice ID list of the terminal under the PLMN.
  • the slice configuration server notifies the terminal of the new slice authorization access information by using the signaling, and the method includes: the access network element sends a query request to the slice configuration server, and the slice configuration server obtains the currently available slice ID based on the query request, and returns the Access to the network element.
  • Step 8.2 After receiving the slice ID, the terminal re-initiates the access network process, where the information of the slice ID is included.
  • a third subsequent processing operation including:
  • the slice configuration server may be a database for storing the terminal slice ID; or may be a control network element or network function for performing terminal slice access authentication and ID configuration (network elements having functions similar to MME, connection management, access management, etc.) Entity or function).
  • Step 4.3 When the slice ID configuration information of the terminal changes, the signaling sent to the slice configuration server notifies that the slice configuration information of the terminal changes, that is, the subscription database sends an update indication to the slice configuration server.
  • Step 5.3 The slice configuration server further sends a control plane command to the associated control plane network element, or directly sends a control plane command to the access network element; that is, the slice configuration server sends the control network element to the control network element. New instructions.
  • Step 6.3 After receiving the control plane command, the terminal deletes the slice ID list accessible by the terminal under the PLMN stored on the terminal; the slice ID list here is a table storing one or more slice IDs.
  • Step 7.3 The terminal initiates an access procedure, and the slice ID field is blank.
  • the network queries the slice ID configuration server for a new slice ID list corresponding to the PLMN.
  • the slice ID field is empty, which means that the slice ID is not carried.
  • Step 8.3 The slice configuration server queries the subscription information from the subscription information to the corresponding slice ID list of the terminal under the PLMN.
  • the slice configuration server notifies the terminal of the new slice authorization access information by signaling.
  • the configuration server may access a slice ID storage device (such as a subscription information base) to query the slice subscription information of the terminal, and obtain the slice ID.
  • a slice ID storage device such as a subscription information base
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated in one process.
  • each unit may be separately used as one unit, or two or more units may be integrated into one unit; the integrated unit may be implemented in the form of hardware or a hardware plus software function unit. Formal realization.
  • the technical solution provided by the embodiment of the present invention when the slice identifier stored in the terminal has an update requirement, receives the currently available slice identifier from the storage network element, and forwards the slice identifier to the terminal, so that the terminal can receive the current slice identifier.
  • For communication it has the characteristics of being simple in the industry, and can avoid the client and the operating system dedicated to terminal installation, and obviously has an industrial positive effect.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种切片标识更新方法，包括：当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；向所述终端发送携带有所述当前可用的切片ID的控制信令；其中，所述控制面信令为用于控制所述终端执行对应操作的控制指示。本发明实施例还公开了网元、终端及存储介质。

Description

网络切片标识更新方法、网元、终端及存储介质
本申请基于申请号为201610366317.6、申请日为2016年05月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及无线通信领域，尤其涉及一种切片标识更新方法、网元、终端及存储介质。
背景技术
网络切片(Network Slicing,NS)是通过网络功能的组合形成逻辑独立的虚拟网络结构。网络切片的标识(Identity,ID)可简称为切片ID。
切片ID的应用场景可包括：终端接入网络时在初始接入的消息中携带该切片ID，网络侧基于该切片ID及其他信息进行鉴权，确定是否允许终端接入。终端可以根据通过获得对应的切片ID，确定出可以接入的网络切片的切片。终端获取切片ID方式通常包括以下两种：
第一种：在终端的通用集成电路卡(Universal Integrated Circuit Card，UICC)上预先配置；
第二种：通信运营商通过空中下载技术(Over Air Technology，OTA)方式配置。
上述两种方式存在着以下问题：
第一种：无法实现切片动态更新，若需要更新，可能需要终端持终端到通信营业厅进行更新。
第二种：采用第二种方法，需要终端内安装专用的应用客户端，或终端的操作系统支持，才能够正确解析利用OTA发送的切片ID。此外，还发 现采用第二种方法，终端漫游到外地时，也无法实现终端的切片ID的动态配置。
发明内容
有鉴于此，本发明实施例期望提供一种切片标识更新方法、网元、终端及存储介质，至少解决上述一个问题。
为达到上述目的，本发明的技术方案是这样实现的：
本发明实施例第一方面提供一种切片标识更新方法，当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；
向所述终端发送携带有所述当前可用的切片ID的控制信令。
基于上述方案，所述当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述当前可用的切片ID，包括：
接收到控制网元发送的携带有所述当前可用的切片ID的控制面信令。
本发明实施例第二方面提供一种切片标识更新方法，包括：
接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；其中，所述切片ID为网络切片的标识；
依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
本发明实施例第三方面提供一种切片标识更新方法，包括：
当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
将所述当前可用的切片ID提供给终端。
本发明实施例第四方面提供一种切片标识更新方法，包括：
从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
本发明实施例第五方面提供一种网元，所述网元为接入网元，包括：
第一接收单元，配置为当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；
第一发送单元，配置为向所述终端发送携带有所述当前可用的切片ID的控制信令。
本发明实施例第六方面提供一种终端，所述终端包括：
第二接收单元，配置为接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；
第一更新单元，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
本发明实施例第七方面提供一种网元，所述网元为存储网元，所述存储网元包括签约数据库，所述签约数据库包括：
第二更新单元，配置为当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
第三发送单元，配置为将所述当前可用的切片ID提供给终端。
本发明实施例第八方面提供一种网元，所述网元为存储网元，所述存储网元包括切片配置服务器，所述切片配置服务器包括：
第四接收单元，配置为从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
第三更新单元，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
本发明实施例第九方面提供一种网元，包括：
存储器，配置为存储计算机程序；
通信接口，配置为与其他设备进行通信；
处理器，分别与所述存储器及通信接口连接，配置为通过执行所述计算机程序，实现前述任意一项或多项提供的切片标识更新方法。
本发明实施例第十方面提供一种计算机存储介质，所述计算机存储介质中存储有计算机程序，所述计算机程序被执行后能够实实现前述任意一项或多项提供的切片标识更新方法
本发明实施例提供的切片标识更新方法、网元、终端及存储介质，当终端内存储的切片ID有更新需求时，向终端发送控制面指令，该控制面指令携带当前可用的切片ID；任何一个能够与接入网元通信的终端都能够识别接入网元发送的控制面指令，故终端无需安装专用的客户端或操作系统，就能够向获取所述当前可用的切片ID；一方面实现了终端内存储的切片ID的动态更新，另一方面提高了终端内切片ID动态更新的便捷性。
附图说明
图1为本发明实施例提供的第一种切片标识更新方法的流程示意图；
图2为本发明实施例提供的第二种切片标识更新方法的流程示意图；
图3为本发明实施例提供的第三种切片标识更新方法的流程示意图；
图4为本发明实施例提供的第四种切片标识更新方法的流程示意图；
图5为本发明实施例提供的第五种切片标识更新方法的流程示意图；
图6为本发明实施例提供的一种接入网元的结构示意图；
图7为本发明实施例提供的终端的结构示意图；
图8为本发明实施例提供的签约数据库的结构示意图；
图9为本发明实施例提供切片配置服务器的结构示意图；
图10为本发明实施例提供的一种控制网元的结构示意图；
图11为本发明实施例提供的第六种切片标识更新方法的流程示意图；
图12为本发明实施例提供的第七种切片标识更新方法的流程示意图；
图13为本发明实施例提供的第八种切片标识更新方法的流程示意图。
具体实施方式
在通信网络的网络侧，存储有终端的授权使用的切片ID。所述网络侧包括的网元可包括签约数据库、移动管理实体MME、基站等网元实体。本实施例提供一种切片标识更新方法，包括：当终端内存储的切片标识ID有更新需求时，向接入网元提供所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；所述当前可用的切片ID用于供所述接入网元通过控制面信令发送给所述终端；所述控制面信令为用于控制所述终端执行对应操作的控制指示。
本实施例所述切片ID更新方法，是一种终端内存储的切片ID动态更新的方法，在本实施例中所述方法可为应用于存储网元中的一种方法。在本实施例中，所述存储网元可为签约数据库；该签约数据库可为设置在归属地签约服务器中的数据库。所述签约数据库用于存储签约数据。所述签约数据可包括终端的使用的通信号码、选择使用的通信套餐等各种签约数据。当然所述存储网元也可以是网络中新增专用网元，可称为切片配置服务器，该切片配置服务器为网络侧的一个网元之一，能够与接入网元直接连接，可用于存储终端授权使用的切片ID，是存储终端的切片ID的一个数据库。
总之，本实施例中所述存储网元，当确定出终端内存储的切片ID有更新需求时，会向接入网元发送终端当前可用的切片ID，而接入网元会通过向终端发送控制面指令的方式发送所述当前可用的切片ID。
通信网络可分为控制面和数据面；通常控制面用于传输控制指令，数据面用于传输业务数据。在本实施例中所述接入网元为控制网元的一种， 是能够与终端直接建立无线连接的设备，例如，演进型基站eNB。控制面指令是能够被现有终端直接识别并解析的信息，无需安装专用的客户端或具有特殊功能的操作系统该，就能够完成当前可用的ID的识别和解析，一方面实现了终端内的存储的切片ID的动态更新，另一方面确保了更新更加方便。
此外，所述存储网元作为通信网络的一个通信网元，并不是如OTA技术对应的设备管理(Device Management，DM)服务器等服务器。所述DM服务器为连接到通信网络的网络设备，并非通信网络的通信网元。所述通信网元与终端交互的信息，具有通信操作系统的终端都能识别。且通信网元在网络侧，可以实现不同城市、不同PLMN内各个通信网元的信息交互，这样终端出现漫游到外地之后，依然可以通过通信网络到通信网元来访问该存储网元，以协助终端内的切片ID的更新。
所述当终端内存储的切片标识ID有更新需求时，包括多种情况，以下提供两种：
第一种：
当所述终端授权使用的切片ID发生变化时。通常所述切片ID是与PLMN相对应的，若ID与PLMN的对应关系发生变化时，就会导致终端授权使用的切片ID发生变化。通常一个所述PLMN可对应于一个或多个网络切片，即可对应一个或多个切片ID。再比如，所述终端被授权使用一个PLMN对应的全部或部分网络切片，则终端被授权使用的切片ID也会发生变化。
第二种：
当所述终端所在位置对应的公共陆地移动网络PLMN，从第一公共陆地移动网络PLMN移动到第二PLMN，导致所述终端需要存储第二PLMN对应的切片ID时。
例如，使用中国移动的通信网络的终端，可能仅存储了一个中国移动PLMN对应的切片ID，但是目前终端从一个PLMN覆盖范围移动到了另一个PLMN的覆盖范围内，这个时候，终端需要使用的当前所在PLMN对应的切片ID。显然，这个时候终端内存储的ID也有更新的需求。
在本实施例中，所述方法还包括：共同存储所述终端授权使用的切片ID与所述终端的签约信息。在本实施例中将终端授权使用的切片ID与终端的签约信息共同存储，一方面能够方便对该终端的信息统一集中管理，另一方面不用专门设置其他网元来存储切片ID，与现有技术的兼容性大；此外，由于签约信息你存储在签约数据库，是整个通信网络，不同网络区域都可以访问到的，这样终端漫游时，依然可以进行切片ID的更新。
以下结合说明书附图及具体实施例对本发明的技术方案做进一步的详细阐述，应当理解，以下所说明的优选实施例仅用于说明和解释本发明，并不用于限定本发明。
实施例一：
如图1所示，本实施例提供一种切片标识更新方法，包括：
步骤S110：当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；
步骤S120：向所述终端发送携带有所述当前可用的切片ID的控制信令；其中，所述控制面信令为用于控制所述终端执行对应操作的控制指示。
本实施例所述的切片标识更新方法，可为应用于接入网元中的方法。本实施例中所述接入网元可包括各种无线网络的接入设备，例如，基站等。
所述步骤S110中包括从存储网元接收终端的当前可用的切片ID。步骤S120中向终端发送控制面命令，该控制面命令内携带有所述当前可用的切片ID，终端接收到的控制面命令，不用设置专门的客户端或具有特殊解析功能的操作系统，就能够解析所述控制面命令，能够提取出所述当前可用 的切片ID，就能够更新所述终端内存储的切片ID。
在一个实施例中，所述步骤S110，包括：
接收到控制网元发送的携带有所述当前可用的切片ID的控制面信令；其中，所述当前可用的切片ID是所述存储网元在确定出所述终端授权使用的切片ID有更新需求时提供的。当存储网元检测到终端授权使用的切片ID发生变化时，当然就表示终端内存储的切片ID有更新需求，存储网元主动通过控制网元向接入网元发送所述控制面指令，且该控制面指令中携带有所述当前可用的切片ID。
具体的如，所述步骤S110可包括：当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求；
接收所述存储网元提供的所述当前可用的切片ID；其中，所述当前可用的切片ID是所述存储网元基于所述查询请求提供的。
本实施例中当终端切换了PLMN或接收到更新指示时，就会发现自己存储的切片ID需要更新，于是会向接入网元发送接入请求，该请求不携带切片ID，这个时候，接入网元知道需要协助终端查询当前可用的切片ID，于是向存储网元发送查询请求；然后接收存储网元返回的当前可用的切片ID。
所述存储网元可包括签约数据库或切片配置服务器。故所述步骤S110具体可包括：当接收到所述终端发送的未携带有切片ID的接入请求时，向所述切片配置服务器发送所述查询请求；接收所述切片配置服务器基于所述查询请求返回的所述当前可用切片ID。
当然，所述当前可用切片ID为所述切片配置服务器查询本地数据库确定的；其中，所述当前可用切片ID是所述切片配置服务器预先从签约数据库接收的；或，所述当前可用切片ID为所述切片配置服务器查询签约数据库确定的。此处，所述切片配置服务器，可以实现从签约数据库获取最新 的切片ID，也可以在接收到所述查询请求之后，再访问签约数据库获取所述当前可用的切片ID。
在一些实施例中，所述方法还包括：接收所述存储网元提供的更新指示；向所述终端发送所述更新指示；其中，所述更新指示，用于指示所述终端删除终端内当前存储的切片ID，并发送未携带有切片ID的所述接入请求。
当存储网元发现终端的当前可用的切片ID有发生变化时，主动发送更新指示，该更新指示触发终端发起切片ID更新流程。该更新指示通过接入网元发送给终端。终端接收到该更新指示之后，将发起未携带有切片ID的接入请求，这个时候，基站等接入网元就知道需要协助终端查询当前可用的切片ID，以实现终端内切片ID的自动更新。
在一些实施例中，所述当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求，包括：当接收到所述终端发送的未携带有切片ID的接入请求时，通过控制网元向签约数据库发送查询请求；所述步骤S110可包括：通过所述控制网元，接收所述签约数据库提供的所述当前可用的切片ID。所述控制网元可以为移动管理实体MME、连接管理网元或接入管理网元等功能实体。
在部分实施例中，所述步骤S120可包括：
当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的重连接消息；
其中，所述重连接消息用于指示所述终端释放当前连接，依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID，并在释放当前连接之后以所述当前可用的切片ID重新请求接入。
在部分实施例中，所述步骤S120可包括：
当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的 切片ID的下线消息；
其中，所述下线消息，用于指示所述终端释放当前连接，依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID，并在下一次有接入需求时以所述当前可用切片ID请求接入。
当然，当所述终端处于非连接状态时，所述方法还包括：当所述终端处于非连接状态时，向所述终端发送携带有所述当前可用的切片ID的寻呼信令；
其中，所述寻呼信令用于指示所述终端依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID，并在下次有接入需求时携带所述当前可用的切片ID请求接入。
这样的话，先将未处于连接状态的终端，切换到连接状态，再通过所述重连接消息或下线消息等控制面指令，更新所述终端内存储的当前可用的切片ID，这样就能够及时进行终端内存储的切片的ID的动态更新。
实施例二：
如图2所示，本实施例提供一种切片标识更新方法，包括：
步骤S210：接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；其中，所述切片ID为网络切片的标识；所述控制面信令为用于控制所述终端执行对应操作的控制指示；
步骤S220：依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。在具体的实现时，所述方法还可包括：步骤S230。所述步骤S230可包括：基于所述当前可用的切片ID，响应所述控制面指令。
本实施例所述的方法为应用于终端内的切片标识更新方法。在本实施例中所述终端通过接收控制面网元来接收所述当前可用的切片ID，根据接收的当前可用的切片ID更新终端内存储的切片ID；并会响应所述控制面指令。显然本实施例中这种方法，显然可以实现中端内存储的切片ID的动态 更新，且不用终端安装专用的客户端或具有特殊功能的专门的操作系统，简化了切片ID在终端内的动态更新。且在本发明任意一个实施例中所述控制面指令可以是任意的控制面指令，将所述当前可用的切片ID承载在控制面指令中，所述控制面信令可包括专用发送所述当前可用的切片ID的信令，还可以是非专用控制面信令。所述非专用控制面信令，除了承载有所述当前可用的切片ID外，还承载有其他的控制指示。这样的话，一方面可以利用控制面指令执行对应的操作，另一方面可以更新了终端内存储的切片ID，减少了控制面信令的发送次数或条数，相对于利用专用控制面信令发送所述当前可用的切片ID，可以减少信令开销。
例如，所述控制面指令包括重连接消息；所述步骤S230可包括：
响应所述重连接消息，释放当前连接；
释放当前连接之后，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
再例如，所述控制面指令包括下线消息；所述步骤S230可包括：
响应所述下线消息，释放当前连接；
当有下一次接入请求时，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
当然，当终端从一个PLMN移动到另一个PLMN时，可能终端内并未存储有当前所在位置对应的PLMN的切片ID，终端会可主动发起未携带有切片ID的接入请求，以触发切片ID的更新操作。例如，前述的第一PLMN和所述第二PLMN是不同的PLMN，所述第二PLMN就可认为是终端当前所在的PLMN。具体地如，所述方法还包括：当所述终端所在位置对应的公共陆地移动网络PLMN，从第一公共陆地移动网络PLMN移动到第二PLMN，且所述终端内未存储有所述第二PLMN对应的切片ID，向所述接入网元发送未携带有切片ID的所述接入请求。
另外一种情况是，终端授权使用的切片ID在网络侧发生变化，对终端是不可见的。此时，终端可能会接收到接入网元转发的更新指示。故在本实施例中所述方法还包括：接收所述接入网元发送的更新指示；其中，所述更新指示是由存储网元提供的；根据所述更新指示删除当前存储的切片ID；向所述接入网元发送未携带有切片ID的所述接入请求。此时，所述接入网元在接收到所述未携带有切片ID的所述接入请求之后，基站等接入网元会向终端发送所述控制面网元。即所述步骤S210包括：终端在发送所述未携带有切片ID的接入请求之后，从接入网元接收所述控制面指令。
总之，本实施例提供的所述切片标识更新方法中，所述步骤S210可为：接入网元在接收到所述终端发送的未携带有切片ID的接入请求之后发送的控制面指令。
总之，本实施例提供了一种动态更新终端内存储的切片ID的方法，具有实现简便的特点。
实施例三：
如图3所示，本实施例提供一种切片标识更新方法，包括：
步骤S310：当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
步骤S320：将所述当前可用的切片ID提供给终端；其中，所述当前可用的切片ID用于供接入网元携带在控制面网元中发送给所述终端。
本实施例所述切片标识更新方法，可为应用于签约数据库中的方法。所述签约数据库将终端的签约信息和所述终端授权使用的切片ID共同存储，方便通信网络内信息共享。
在本实施例中，所述步骤S310等根据外设输入或运营商指示，发现终端授权使用的切片ID发生变化时，更新签约数据库中存储的终端当前可用 的切片ID，并将当前可用的切片ID提供给终端，方便后续终端的通信。具体地如，通过控制网元及接入网元，向终端发送携带有当前可用的切片ID的控制面指令，方便终端可以简便解析控制面指令，
在一些实施例中，所述步骤S320可包括：
将所述当前可用的切片ID发送给控制网元；
所述当前可用的切片ID，用于供所述控制网元控制接入网元向终端发送控制面信令；其中，所述控制面信令携带有所述当前可用的ID；所述控制面信令为用于控制所述终端执行对应操作的控制指示。这里的控制面网元可分别与所述签约数据库和所述接入网元连接的网元。通常情况下，签约数据库与接入网元之前没有直连链路，这里的直连链路为不经过其他通信节点的点对点链路。
在另一些实施例中，所述步骤S320可，包括：
将所述当前可用的切片ID发送给切片配置服务器；
所述当前可用的切片ID，用于当所述切片配置服务器接收到接入网元的查询请求时返回给所述接入网元，并通过所述接入网元发送给所述终端。
在本实施例中所述签约服务器会将更新后的当前可用的切片ID，这样方便，接入网络到与其直接连接的切片配置服务器中查询，减少接入网元接收到终端发送的未携带有切片ID的接入请求之后，需要经过控制网元必须到签约数据库中查询当前使用的切片ID，能够减少信息交互，提高终端内存储的切片ID的更新速率，减少延时。
实施例四：
如图4所示，本实施例提供一种切片标识更新方法，包括：
步骤S410：从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
步骤S420：依据所述当前可用的切片ID，更新所述切片配置服务器内 存储的切片ID；其中，存储的所述当前可用的切片ID，用于通过接入网元发送给所述终端。
本实施例提供的切片标识更新方法可为应用于切片配置服务器内的方法。所述步骤S410可为从签约数据库中接收终端当前可用的切片ID，并更新切片配置服务器内存储的切片ID，方便当终端发起切片ID更新流程时，提高更新效率。
所述步骤S410可包括多种实现方式，以下提供两种：
第一种：所述步骤S410可包括：
当接收到接入网元发送的查询请求时，向所述签约数据库发送获取请求；
接收所述签约数据基于所述获取请求返回的所述当前可用的切片ID；
第二种：所述步骤S410还可包括：
接收所述终端数据库更新所述终端授权使用的切片ID时，发送的所述的当前可用的切片ID。
本实施例提供的方法应用于切片配置服务器中，该切片配置服务器为专用存储和配置终端授权使用的切片ID的网元，可与接入网元直接建立连接。
实施例五：
如图5所示，本实施例提供一种切片标识更新方法，包括：
步骤S510：接收终端当前可用的切片标识ID；其中，所述当前可用的切片ID为当终端内存储的切片标识ID有更新需求时，由存储网元提供的；
步骤S520：将所述当前可用的切片ID发送给接入网元；
其中，所述切片ID为网络切片的标识；所述当前可用的切片ID用于供所述接入网元通过控制面信令发送给所述终端；所述控制面信令为用于控制所述终端执行对应操作的控制指示。
本实施例提供一种切片标识更新方法可为应用于控制网元中的信息处理方法。本实施例中所述控制网元可包括MME等网络实体。
步骤S510可包括接收终端当前可用的切片ID，在步骤S520中将从存储网元接收的ID发送给接入网元，由接入网元发送给终端。本实施例中所述存储网元可包括签约数据库或切片配置服务器。
可选地，所述方法还包括：
接收存储网元发送的触发消息；
根据所述触发消息，通过所述接入网元向所述终端发送更新指示；
其中，所述更新指示，用于指示所述终端删除所述终端内当前存储的切片ID，并发送未携带有切片ID的所述接入请求。
当所述签约数据库更新了终端授权使用的切片ID时，控制网元介于该触发消息，会控制接入网元向终端发送更新指示，终端接收到更新指示之后，会发送未携带有切片ID的接入请求，触发终端内的切片ID的更新。
可选地，所述方法还包括：
接收所述接入网元发送的获取请求；其中，所述获取请求是所述接入网元在接收到所述终端未携带有切片ID的接入请求时发送的；
将所述获取请求发送给所述存储网元；
所述步骤S510可包括：
接收存储网元基于所述获取请求返回的当前可用的切片ID。
本实施例中所述控制网元可包括移动管理实体等网元。控制面网元可会控制接入网元向终端发送控制面指令，以控制面指令的方式告知终端当前可用的切片ID，方便终端动态更新存储的切片ID，终端内又不需要安装额外的客户端。
实施例六：
如图6所示，本实施例提供一种网元，所述网元为接入网元，包括：
第一接收单元110，配置为当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；
第一发送单元120，配置为向所述终端发送携带有所述当前可用的切片ID的控制信令；其中，所述控制面信令为用于控制所述终端执行对应操作的控制指示。
本实施例提提供的网元为基站等接入网元，为可以与终端直接进行无线交互的网元。
本实施例所述第一接收单元110和所述第一发送单元120都可以对应于基站等接入网元中的通信接口。
本实施例所述接入网元，通过向终端发送控制面指令，触发终端进行切片ID的动态更新，无需终端内安装额外的客户端或操作系统，实现简便且效率高。
在一些实施例中，所述第一接收单元110，配置为接收到控制网元发送的携带有所述当前可用的切片ID的控制面信令；其中，所述当前可用的切片ID是所述存储网元在确定出所述终端授权使用的切片ID有更新需求时提供的。
在另一些实施例中，所述第一发送单元120，还配置为当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求；所述第一接收单元110，还用于接收所述存储网元提供的所述当前可用的切片ID；其中，所述当前可用的切片ID是所述存储网元基于所述查询请求提供的。
此外，所述第一发送单元120，配置为当接收到所述终端发送的未携带有切片ID的接入请求时，向所述切片配置服务器发送所述查询请求；
所述第一接收单元110，配置为接收所述切片配置服务器基于所述查询 请求返回的所述当前可用切片ID。
存储终端授权使用的切片ID的网元可包括签约数据库及切片配置服务器等网元，但是不局限于这两个网元。当所述接入网元从切片服务配置器查询所述当前可用的切片ID时，所述当前可用切片ID为所述切片配置服务器查询本地数据库确定的；其中，所述当前可用切片ID是所述切片配置服务器预先从签约数据库接收的；或，所述当前可用切片ID为所述切片配置服务器查询签约数据库确定的。
当所述接入网元从签约数据库获取所述当前可用的切片ID时，所述第一发送单元120和所述第一接收单元110的具体结构可参见如下。
例如，所述第一接收单元110，还配置为接收所述存储网元提供的更新指示；所述第一发送单元120，还配置为向所述终端发送所述更新指示；其中，所述更新指示，用于指示所述终端删除所述终端内当前存储的切片ID，并发送未携带有切片ID的所述接入请求。这样通过向终端发送更新指示，来来触发终端内存储的切片ID的更新。在本例中是有存储网元触发终端内存储的切片ID的更新。
再例如，所述第一发送单元120，还配置为当接收到所述终端发送的未携带有切片ID的接入请求时，通过控制网元向签约数据库发送查询请求；所述第一接收单元110，还用于通过所述控制网元，接收所述签约数据库提供的所述当前可用的切片ID。在本例中是由终端自身触发切片ID的更新。
所述控制面指令可包括重连接消息、下线消息或物理下行链路控制消息等控制面信令。
例如，所述第一发送单元120，配置为当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的重连接消息；
其中，所述重连接消息用于指示所述终端释放当前连接，并在释放当前连接之后以所述当前可用的切片ID重新请求接入。
再例如，所述第一发送单元，配置为当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的下线消息；
其中，所述下线消息，用于指示所述终端释放当前连接，并在下一次有接入需求时以所述当前可用切片ID请求接入。
在本实施例中，若发送的控制面指令是重连接消息，则终端断开当前连接之后的预定时间内必然重新发起连接。若发送的控制面指令是下线消息，则终端会断开当前连接，当等到有下一次接入需求时，才会发送连接请求，断开当前连接的时间点，与发起下一接入请求的时间点之间的时间间隔是不固定，这决定于终端的接入需求。通常终端有数据传输，才会有接入需求，若终端当前没有接入需求则不会立即再次发起接入请求。
可选地，所述第一发送单元120，还配置为当所述终端处于非连接状态时，向所述终端发送寻呼信令；其中，所述寻呼信令用于指示所述终端与所述接入网元建立连接，切换到所述连接状态。当终端是处于非连接状态，为了及时的向更新终端内的切片ID，在本实施例中在发送所述控制面指令之前，先发送所述寻呼信令，促使所述终端进入连接状态。
总之，本实施例所述的接入网元能够协助终端，进行切片ID的动态更新，且实现简单，为实施例一所述切片标识更新方法提供了实现硬件。
实施例七：
如图7所示，本实施例提供一种终端，所述终端包括：
第二接收单元210，配置为接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；其中，所述切片ID为网络切片的标识；所述控制面信令为用于控制所述终端执行对应操作的控制指示；
第一更新单元220，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
本实施例所述终端可为各种类型的终端。所述终端可为多模终端或单 模终端。所述第二接收单元210可对应于终端的接收天线，能够从接入网元接收所述控制面指令，该控制面指令中携带有当前可用的切片ID，终端可以不用安装专用的客户端或操作系统来识别所述当前可用的切片ID，显然更新流程简单。
所述第一更新单元220可对应于终端内的处理器或处理电路等信息处理结构，所述信息处理结构可为中央处理器、微处理器、数字信号处理器、可编程阵列或专用集成电路等。
在一些实施例中，所述控制面指令可包括重连接消息；所述终端还包括：连接单元，用于响应所述重连接消息，释放当前连接；
第二发送单元，配置为释放当前连接之后，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
本实施例中所述连接单元和所述第二发送单元，均可为与接入网元进行通信的结构，在本实施例中所述控制面指令为重连接消息，终端会断开当前连接，并再次接入。
在另一些实施例中，所述控制面指令可包括下线消息；
所述终端还包括：
连接单元，配置为响应所述下线消息，释放当前连接；
第二发送单元，配置为当有下一次接入请求时，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
本实施例中所述连接单元和所述第二发送单元的结构相同或类似，但是在本实施例中所述控制面指令为下线消息。第二发送单元发送连接请求时，不用在当前连接断开之后，立即请求接入，可以在终端有接入需求时在请求接入。
可选地，所述第二接收单元210，还配置为接收所述接入网元发送的更新指示；其中，所述更新指示是由存储网元提供的；所述终端还包括：第 二更新单元，配置为根据所述更新指示删除当前存储的切片ID；连接单元，用于向所述接入网元发送未携带有切片ID的接入请求；所述第二接收单元，具体用于接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。本实施例中，通过从接入网元接收由存储网元提供的更新指示，来发起切片ID的更新流程。
所述终端还包括：
第二发送单元，配置为当所述终端所在位置对应的公共陆地移动网络PLMN，从第一公共陆地移动网络PLMN移动到第二PLMN，且所述终端内未存储有所述第二PLMN对应的切片ID，向所述接入网元发送未携带有切片ID的所述接入请求；所述第二接收单元210，具体用于接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。在本实施例中可由终端自身发起切片ID的更细。
本实施例提供的终端至少可用于实现方法实施二所述的切片ID更新方法，具有实现简单的特点。
实施例八：
如图8所示，本实施例提供一种网元，该网元为存储网元，该存储网元包括签约数据库，包括：
第二更新单元310，配置为当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
第三发送单元320，配置为将所述当前可用的切片ID提供给终端；其中，所述当前可用的切片ID用于供接入网元携带在控制面网元中发送给所述终端。
本实施例提供的网元为签约数据库，所述签约数据库可对应于HSS等网元。所述签约数据库原本为存储有终端的签约数据的数据库。在本实施 例中所述签约数据库还用于存储所述终端授权使用的切片ID。
所述第二更新单元310可对应于签约数据库的各种信息处理结构，所述信息处理结构的类型可以参见前述实施例中的对应部分，在此就不详细赘述了。
可选地，所述第三发送单元320，配置为将所述当前可用的切片ID发送给控制网元；所述当前可用的切片ID，配置为供所述控制网元控制接入网元向终端发送控制面信令；其中，所述控制面信令携带有所述当前可用的ID；所述控制面信令为用于控制所述终端执行对应操作的控制指示。在本实施例中所述签约数据库不直接与终端和接入网元连接，通过向控制网元及接入网元，才能将当前可用的切片ID发送给终端。
在另一实施例中，所述第二更新单元310，配置为将所述当前可用的切片ID发送给切片配置服务器；所述当前可用的切片ID，用于当所述切片配置服务器接收到接入网元的查询请求时返回给所述接入网元，并通过所述接入网元发送给所述终端。
总之，本实施例所述签约数据库不仅会存储签约数据，还会存储终端授权使用的切片ID，方便动态更新终端中的切片ID，为实施例三提供的切片标识更新方法提供了实现结构。
实施例九：
如图9所示，本实施例提供一种网元，该网元为存储网元，该存储网元包括切片配置服务器，包括：
第四接收单元410，配置为从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
第三更新单元420，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID；其中，存储的所述当前可用的切片ID，用于通过接入网元发送给所述终端。
本实施例中所述第四接收单元410可对应于所述切片配置服务器的通信接口。这里的通信接口可为有线接口或无线接口。所述切片配置服务器可一端与前述签约数据库连接，另一端与接入网元连接，充当所述签约数据库与接入网元的中间节点，这样接入网元需要查询终端的当前可用的切片ID时，可以从签约数据库差，也可以从切片配置服务器查询，从切片配置服务器查询，由于无需再经过中间的一个或多个控制网元，从而具有速度快的特点。
在一些实施例中，所述网元还包括：
第四发送单元，配置为当接收到接入网元发送的查询请求时，向所述签约数据库发送获取请求；所述第四接收单元，具体用于接收所述签约数据基于所述获取请求返回的所述当前可用的切片ID；
在另一些实施例中，所述第四接收单元410，具体用于接收所述终端数据库更新所述终端授权使用的切片ID时，发送的所述的当前可用的切片ID。
总之，本实施例提供了一种签约数据库，能够协助终端动态更新存储的切片ID，且可以在通信网络内全网共享，即便终端从一个区域漫游到另一个区域，也可以更新切片ID.
实施例十：
如图10所示，本实施例提供一种网元，所述网元为控制网元，包括：
第五接收单元510，配置为接收终端当前可用的切片标识ID；其中，所述当前可用的切片ID为当终端内存储的切片标识ID有更新需求时，由存储网元提供的；
第五发送单元520，配置为将所述当前可用的切片ID发送给接入网元；
其中，所述切片ID为网络切片的标识；所述当前可用的切片ID用于供所述接入网元通过控制面信令发送给所述终端；所述控制面信令为用于 控制所述终端执行对应操作的控制指示。
本实施例中所述网元为控制网元，可对应于MME等结构，该网元为与接入网元直接连接的网元，通常优选为还与签约数据库直接连接的网元。本实施例中所述控制网元，将协助终端进行切片ID的动态更新。
所述第五接收单元510和第五发送单元520可对应于控制网元的通信接口，能够用于与其他网元进行信息交互。
在一些实施例中，所述第五接收单元510，还用于接收存储网元发送的触发消息；
所述第五发送单元520，还配置为根据所述触发消息，通过所述接入网元向所述终端发送更新指示；其中，所述更新指示，用于指示所述终端删除所述终端内当前存储的切片ID，并发送未携带有切片ID的所述接入请求。在本实施例中所述控制网元会向终端发送更新指示，促使终端发起用于切片ID更新的接入请求。
在另一些实施例中，所述第五接收单元510，配置为接收所述接入网元发送的获取请求；其中，所述获取请求是所述接入网元在接收到所述终端未携带有切片ID的接入请求时发送的；所述第五发送单元520，还用于将所述获取请求发送给所述存储网元；所述第五接收单元510，具体用于接收存储网元基于所述获取请求返回的当前可用的切片ID。在本实施例中所述控制网元，在接收到未携带有切片ID的接入请求时，就可认为终端发起了切片ID的更新流程。
本发明实施例提供一种网元，包括：
存储器，配置为存储计算机程序；
通信接口，配置为与其他设备进行通信；
处理器，分别与所述存储器及通信接口连接，配置为通过执行所述计算机程序，实现前述任意一个或多个技术方案提供的切片标识更新方法。
本实施例提供的网元可为前述的存储网元及终端等接入到网络的各种通信设备。
所述处理器可为中央处理器、微处理器、数字信号处理器或应用处理器或可编程阵列等。
所述处理器可通过总线，例如，集成电路(IIC)总线，与存储器及通信接口连接。
本发明实施例提供一种计算机存储介质，所述计算机存储介质中存储有计算机程序，所述计算机程序被执行后能够实现前述任意一个或多个技术方案提供的切片标识更新方法。
本实施例提供的计算机存储介质可为移动存储设备、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质，可选为非瞬间存储介质。
以下结合上述任意实施例提供几个具体示例：
示例一：
本示例提供一种终端内存储的切片ID更新方法，包括：
当终端可接入网络切片授权信息发生变化时，如某个终端在某个PLMN下的切片ID的接入权限发生变化；向终端发送控制面信令，该控制面信令会携带有变化之后终端当前可用的切片ID。例如，促使终端发生连接重新接入，终端获取新的切片ID接入配置信息，并携带该新的切片ID接入网络。
示例二：
1)网络中某一功能实体或网元，作为终端的片接入授权存储实体，如终端签约的HSS，对应于上述存储网元，中存储了一个终端在某个网络(如PLMN)下可使用的切片ID的信息，即网络切片接入授权信息。如某个终 端IMSI下所对应的某个PLMN下可使用切片ID列表。
2)当切片接入授权存储实体中某终端的切片ID配置信息发生变化，如增加或删除某个PLMN下的切片ID的对应关系。当授权存储实体判断该终端当前在以某切片ID接入网络，而终端使用该切片ID的权限被修改时，签约信息网元(或网络功能)通知网络第一实体。
该网络第一实体可以是某控制面网元或相关网络功能，如移动性管理MME、连接管理功能等和终端连接管理相关的功能。此处的第一实体可对应于前述的控制网元等结构。
当网络中具有切片ID配置服务器时，该网络第一实体也可以是切片配置服务器。切片ID配置服务器是指能对终端切片ID进行配置的实体。
3)该网络第一实体提供发送给终端的重连接消息或下线消息。消息原因值中体现出由于切片签约的变化所引发，如切片ID变更。当终端处于某种信令非连接状态时，可通过寻呼等方式使得终端可达，即使得终端处于连接状态。
对应于切片ID的后续处理操作可以包括多种方式，下面分别介绍：
如图11所示，此处提供第一种后续处理操作，包括：
步骤4.1：第一实体直接在重连接消息或下线消息中携带PLMN和更新后的切片ID，通过接入网元发送给终端。步骤4.1可是在接收到核心网触发切片ID的更新指示之后执行的。该指示可为触发控制面网元，直接通过接入网元向终端发送控制面指令的指示。
步骤5.1：UE接收到该切片ID后，更新手机卡上配置的和该PLMN对应的切片ID的信息，，具体包括：终端接收接入网元发送的携带有切片ID的控制面指令。
步骤6.1：终端重新发起连接建立请求，并在连接消息中携带新的切片ID；网络为其提供切片ID服务。该步骤发起的连接建立请求即为图11中 的重连接请求。
如图12所示，此处提供第二种后续处理操作，包括：
步骤4.2：控制面网元在重连接或下线消息中携带一个切片ID更新指示，发送给终端。
步骤5.2：终端收到该控制面指令后，删除终端上存储的该PLMN下终端可接入的切片ID列表；这里的切片ID列表为存储一个或多个切片ID的表格。
步骤6.2：终端发起接入流程，切片ID字段为空。网络向切片ID配置服务器中查询该PLMN对应的新的切片ID列表。切片ID字段为空，即表示未携带有切片ID。
步骤7.2：切片配置服务器从签约信息中查询到终端在该PLMN下对应的切片ID列表。切片配置服务器，通过信令将新的切片授权接入信息告知终端，具体包括：接入网元向切片配置服务器发送查询请求，切片配置服务器基于查询请求，获取当前可用的切片ID，并返回给接入网元。
步骤8.2：终端收到切片ID后，重新发起接入网络流程，其中含有切片ID的信息。
如图13所示，此处提供第三种后续处理操作，包括：
切片配置服务器可以是一个存储终端切片ID的数据库；也可以是进行终端切片接入鉴权及ID配置的控制网元或网络功能(具有类似于MME、连接管理、接入管理等功能的网元实体或功能)。
步骤4.3：当终端的切片ID配置信息发生变化时，发送到切片配置服务器的信令告知该终端的切片配置信息有变化，即签约数据库向切片配置服务器发送更新指示；
步骤5.3：切片配置服务器进而发送控制面指令给相关控制面网元，或者直接发送控制面指令给接入网元；即切片配置服务器向控制网元发送更 新指示。
步骤6.3：终端收到该控制面指令后，删除终端上存储的该PLMN下终端可接入的切片ID列表；这里的切片ID列表为存储一个或多个切片ID的表格。
步骤7.3：终端发起接入流程，切片ID字段为空。网络向切片ID配置服务器中查询该PLMN对应的新的切片ID列表。切片ID字段为空，即表示未携带有切片ID。
步骤8.3：切片配置服务器从签约信息中查询到终端在该PLMN下对应的切片ID列表。切片配置服务器，通过信令将新的切片授权接入信息告知终端。
在步骤8.3中，配置服务器可以访问切片ID存储设备(如签约信息库)查询该终端的切片签约信息，获得所述切片ID。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个处理 模块中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，凡按照本发明原理所作的修改，都应当理解为落入本发明的保护范围。
工业实用性
本发明实施例提供的技术方案，在终端内存储的切片标识有更新需求时，会从存储网元接收到当前可用的切片标识，并转发给终端，这样终端就能够接收到当前的切片标识，以进行通信；具有在工业上实现简单的特点，且能够避免终端安装专用的客户端及操作系统，显然产生了工业上的积极效果。

Claims (36)

  1. 一种切片标识更新方法，包括：
    当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；其中，所述切片ID为网络切片的标识；
    向所述终端发送携带有所述当前可用的切片ID的控制信令。
  2. 根据权利要求1所述的方法，其中，
    所述当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述当前可用的切片ID，包括：
    接收到控制网元发送的携带有所述当前可用的切片ID的控制面信令。
  3. 根据权利要求1所述的方法，其中，
    所述当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述当前可用的切片ID，包括：
    当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求；
    接收所述存储网元提供的所述当前可用的切片ID。
  4. 根据权利要求3所述的方法，其中，
    所述当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求，包括：
    当接收到所述终端发送的未携带有切片ID的接入请求时，向所述切片配置服务器发送所述查询请求；
    所述接收所述存储网元提供的所述当前可用的切片ID，包括：
    接收所述切片配置服务器基于所述查询请求返回的所述当前可用切片ID。
  5. 根据权利要求3所述的方法，其中，
    所述方法还包括：
    接收所述存储网元提供的更新指示；
    向所述终端发送所述更新指示。
  6. 根据权利要求3所述的方法，其中，
    所述当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求，包括：
    当接收到所述终端发送的未携带有切片ID的接入请求时，通过控制网元向签约数据库发送查询请求；
    所述接收所述存储网元提供的所述当前可用的切片ID，包括：
    通过所述控制网元，接收所述签约数据库提供的所述当前可用的切片ID。
  7. 根据权利要求1所述的方法，其中，
    所述向所述终端发送携带有所述当前可用的切片ID的控制信令，包括：
    当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的重连接消息；
    或
    当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的下线消息。
  8. 根据权利要求7所述的方法，其中，
    当所述终端处于非连接状态时，所述方法还包括：
    在向所述终端发送携带有所述当前可用的切片ID的控制信令之前，向所述终端发送寻呼信令。
  9. 根据权利要求7所述的方法，其中，
    所述控制面信令中还包括消息原因值；其中，所述消息原因值用于指示终端释放当前连接的原因。
  10. 一种切片标识更新方法，包括：
    接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；其中，所述切片ID为网络切片的标识；
    依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
  11. 根据权利要求10所述的方法，其中，
    所述控制面指令包括重连接消息；
    所述方法还包括：
    响应所述重连接消息，释放当前连接；
    释放当前连接之后，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
  12. 根据权利要求10所述的方法，其中，
    所述控制面指令包括下线消息；
    所述方法还包括：
    响应所述下线消息，释放当前连接；
    当有下一次接入请求时，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
  13. 根据权利要求10所述的方法，其中，
    所述方法还包括：
    接收所述接入网元发送的更新指示；
    根据所述更新指示删除当前存储的切片ID；
    向所述接入网元发送未携带有切片ID的接入请求；
    所述接收接入网元发送的携带有当前可用的切片标识ID的控制面指令，包括：
    接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。
  14. 根据权利要求10所述的方法，其中，
    所述方法还包括：
    当终端所在位置对应的公共陆地移动网络PLMN，从第一公共陆地移动网络PLMN移动到第二PLMN，且所述终端内未存储有所述第二PLMN对应的切片ID，向所述接入网元发送未携带有切片ID的所述接入请求；
    所述接收接入网元发送的携带有当前可用的切片标识ID的控制面指令，包括：
    接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。
  15. 一种切片标识更新方法，包括：
    当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
    将所述当前可用的切片ID提供给终端。
  16. 根据权利要求15所述的方法，其中，
    所述将所述终端当前可用的切片ID提供给终端，包括：
    将所述当前可用的切片ID发送给控制网元；
    或
    将所述当前可用的切片ID发送给切片配置服务器。
  17. 一种切片标识更新方法，其中，包括：
    从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
    依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
  18. 根据权利要求17所述的方法，其中，
    所述从签约数据库接收终端当前可用的切片标识ID，包括：
    当接收到接入网元发送的查询请求时，向所述签约数据库发送获取请求；
    接收所述签约数据基于所述获取请求返回的所述当前可用的切片ID；
    或，
    接收所述终端数据库更新所述终端授权使用的切片ID时，发送的所述的当前可用的切片ID。
  19. 一种网元，其中，所述网元为接入网元，包括：
    第一接收单元，配置为当终端内存储的切片标识ID有更新需求时，接收存储网元提供的所述终端当前可用的切片ID；
    第一发送单元，配置为向所述终端发送携带有所述当前可用的切片ID的控制信令。
  20. 根据权利要求19所述的网元，其中，
    所述第一接收单元，配置为接收到控制网元发送的携带有所述当前可用的切片ID的控制面信令。
  21. 根据权利要求19所述的网元，其中，
    所述第一发送单元，还配置为当接收到所述终端发送的未携带有切片ID的接入请求时，向所述存储网元发送查询请求；
    所述第一接收单元，还配置为接收所述存储网元提供的所述当前可用的切片ID。
  22. 根据权利要求21所述的网元，其中，
    所述第一发送单元，配置为当接收到所述终端发送的未携带有切片ID的接入请求时，向所述切片配置服务器发送所述查询请求；
    所述第一接收单元，配置为接收所述切片配置服务器基于所述查询请求返回的所述当前可用切片ID。
  23. 根据权利要求21所述的网元，其中，
    所述第一接收单元，还配置为接收所述存储网元提供的更新指示；
    所述第一发送单元，还用于向所述终端发送所述更新指示。
  24. 根据权利要求19所述的网元，其中，
    所述第一发送单元，还配置为当接收到所述终端发送的未携带有切片ID的接入请求时，通过控制网元向签约数据库发送查询请求；
    所述第一接收单元，还配置为通过所述控制网元，接收所述签约数据库提供的所述当前可用的切片ID。
  25. 根据权利要求19所述的网元，其中，
    所述第一发送单元，配置为当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的重连接消息；或，具体用于当所述终端处于连接状态时，向所述终端发送携带有所述当前可用的切片ID的下线消息。
  26. 根据权利要求25所述的网元，其中，
    所述第一发送单元，还配置为当所述终端处于非连接状态时，在向所述终端发送携带有所述当前可用的切片ID的控制信令之前，向所述终端发送寻呼信令。
  27. 根据权利要求26所述的网元，其中，
    所述控制面信令中还包括消息原因值；其中，所述消息原因值用于指示终端释放当前连接的原因。
  28. 一种终端，所述终端包括：
    第二接收单元，配置为接收接入网元发送的携带有当前可用的切片标识ID的控制面指令；
    第一更新单元，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
  29. 根据权利要求28所述的终端，其中，
    所述控制面指令包括重连接消息；
    所述终端还包括：
    连接单元，配置为响应所述重连接消息，释放当前连接；
    第二发送单元，配置为释放当前连接之后，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
  30. 根据权利要求29所述的终端，其中，
    所述控制面指令包括下线消息；
    所述终端还包括：
    连接单元，配置为响应所述下线消息，释放当前连接；
    第二发送单元，配置为当有下一次接入请求时，向所述接入网元发送携带有所述当前可用的切片ID的接入请求。
  31. 根据权利要求29所述的终端，其中，
    所述第二接收单元，还配置为接收所述接入网元发送的更新指示；其中，所述更新指示是由存储网元提供的；
    所述终端还包括：
    第二更新单元，配置为根据所述更新指示删除当前存储的切片ID；
    连接单元，配置为向所述接入网元发送未携带有切片ID的接入请求；
    所述第二接收单元，配置为接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。
  32. 根据权利要求29所述的终端，其中，
    所述终端还包括：
    第二发送单元，配置为当所述终端所在位置对应的公共陆地移动网络PLMN，从第一公共陆地移动网络PLMN移动到第二PLMN，且所述终端内未存储有所述第二PLMN对应的切片ID，向所述接入网元发送未携带有切片ID的所述接入请求；
    所述第二接收单元，配置为接收所述接入网元基于所述未携带有切片ID的接入请求返回的所述控制面指令。
  33. 一种网元，所述网元为存储网元，所述存储网元包括为签约数据库，所述签约数据库包括：
    第二更新单元，配置为当确定出终端授权使用的切片标识ID发生变化时，更新签约数据库中存储的当前可用的切片ID；其中，所述切片ID为网络切片的标识；
    第三发送单元，配置为将所述当前可用的切片ID提供给终端。
  34. 一种网元，所述网元为存储网元，所述存储网元包括切片配置服务器，所述切片配置服务器包括：
    第四接收单元，配置为从签约数据库接收终端当前可用的切片标识ID；其中，所述切片ID为网络切片的标识；
    第三更新单元，配置为依据所述当前可用的切片ID，更新所述切片配置服务器内存储的切片ID。
  35. 一种网元，包括：
    存储器，配置为存储计算机程序；
    通信接口，配置为与其他设备进行通信；
    处理器，分别与所述存储器及通信接口连接，配置为通过执行所述计算机程序，实现权利要求1到17任一项所述的切片标识更新方法。
  36. 一种计算机存储介质，所述计算机存储介质中存储有计算机程序，所述计算机程序被执行后能够实现权利要求1到17任一项所述的切片标识更新方法。
PCT/CN2017/085402 2016-05-27 2017-05-22 网络切片标识更新方法、网元、终端及存储介质 WO2017202269A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610366317.6A CN107438245B (zh) 2016-05-27 2016-05-27 网络切片标识更新方法、网元及终端
CN201610366317.6 2016-05-27

Publications (1)

Publication Number Publication Date
WO2017202269A1 true WO2017202269A1 (zh) 2017-11-30

Family

ID=60412061

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085402 WO2017202269A1 (zh) 2016-05-27 2017-05-22 网络切片标识更新方法、网元、终端及存储介质

Country Status (2)

Country Link
CN (1) CN107438245B (zh)
WO (1) WO2017202269A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118120A (zh) * 2019-06-20 2020-12-22 中国电信股份有限公司 切片签约方法、系统和计算机可读存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109327883B (zh) * 2017-07-31 2023-07-14 华为技术有限公司 传输信息的方法和装置
WO2019119447A1 (en) 2017-12-22 2019-06-27 Qualcomm Incorporated Expedited release of a user equipment
CN109962806B (zh) * 2017-12-26 2021-10-19 中兴通讯股份有限公司 一种传送网子切片管理方法和装置
CN109891924B (zh) * 2018-01-19 2020-09-15 Oppo广东移动通信有限公司 一种配置网络切片标识的方法、设备及计算机存储介质
WO2019174115A1 (zh) * 2018-03-12 2019-09-19 Oppo广东移动通信有限公司 一种ue策略的更新方法及装置、计算机存储介质
CN109699072B (zh) * 2018-04-09 2020-03-10 华为技术有限公司 通信方法、装置和系统
CN110366241A (zh) 2018-04-09 2019-10-22 华为技术有限公司 通信方法、装置和系统
TWI733116B (zh) * 2018-05-21 2021-07-11 芬蘭商諾基亞科技公司 因本地plmn組態變更而在ue中管理vplmn組態更新之技術
CN111586716B (zh) * 2020-04-28 2022-08-12 中国联合网络通信集团有限公司 网络切片部署方法及装置
CN114449552B (zh) * 2020-11-06 2023-08-15 中移物联网有限公司 一种切片网络管理方法、装置及电子设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102244686A (zh) * 2011-06-24 2011-11-16 中国人民解放军国防科学技术大学 基于主从异构数传模块的虚拟网络接口实现方法
KR20130047489A (ko) * 2011-10-31 2013-05-08 한국과학기술정보연구원 글로벌 네트워크 슬라이스 관리 시스템 및 그 방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102244686A (zh) * 2011-06-24 2011-11-16 中国人民解放军国防科学技术大学 基于主从异构数传模块的虚拟网络接口实现方法
KR20130047489A (ko) * 2011-10-31 2013-05-08 한국과학기술정보연구원 글로벌 네트워크 슬라이스 관리 시스템 및 그 방법

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;. 'Feasibility Study on New Services and Markets Technology Enablers; Stage 1 (Release 14", 3GPP STANDARD; 3GPPTR 22.891, 31 March 2016 (2016-03-31), XP055443961 *
DEUTSCHE TELEKOM AG ET AL.: "Requirements for Next Generation Access Technologies", 3GPP DRAFT; RPA160003, 29 January 2016 (2016-01-29), Barcelona, Spain, XP051053203 *
NOKIA ET AL.: "Key Requirements and Principles for Network Slicing", 3GPP DRAFT; R3-160734, 11 April 2016 (2016-04-11), Bangalore , India, XP051082917 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118120A (zh) * 2019-06-20 2020-12-22 中国电信股份有限公司 切片签约方法、系统和计算机可读存储介质
CN112118120B (zh) * 2019-06-20 2023-04-07 中国电信股份有限公司 切片签约方法、系统和计算机可读存储介质

Also Published As

Publication number Publication date
CN107438245B (zh) 2022-09-13
CN107438245A (zh) 2017-12-05

Similar Documents

Publication Publication Date Title
WO2017202269A1 (zh) 网络切片标识更新方法、网元、终端及存储介质
US10659952B2 (en) Network slice selection policy updating method and apparatus
EP3552414B1 (en) Method and apparatus for selecting an access and mobility management function in a mobile communication system
KR102394891B1 (ko) 무선 통신 방법 및 장치
KR102314917B1 (ko) 통신 시스템에서 디바이스들 간의 연결 설정 방법 및 장치
CN108702692B (zh) 移动网络中的功能选择
US20200280911A1 (en) Core network selection method, apparatus, and system
KR101727090B1 (ko) 서비스를 등록 및 발견하는 방법, 기기, 및 시스템
EP2983399B1 (en) Method, device, and system for proximity service authorization
CN103209412B (zh) 建立设备到设备连接的方法、设备和系统
JP6908720B2 (ja) コアネットワーク制御プレーンデバイス選択方法および装置
CN105392185B (zh) 一种智能设备的联网方法、装置及系统
CN105848131A (zh) 一种通过云ac实现sta跨域漫游的方法
WO2016177106A1 (zh) 专用核心网的选择方法和装置
KR20140010206A (ko) 라디오 주파수 대역을 고려한 무선네트워크 접속 장치 및 방법
JP2022540445A (ja) 通信方法及びネットワーク要素
CN107409437A (zh) 一种plmn的dcn处理方法、ue及dcn服务节点
CN110268732A (zh) 数据传输方法、基站、本地疏导控制器、网关和系统
US20190110323A1 (en) Access method, apparatus, device, and system
EP3310117B1 (en) Method for establishing a connection of a mobile terminal to a mobile radio communication network and radio access network component
CN106211142B (zh) 一种WiFi AP终端广域网接入方法
US20150213133A1 (en) Method for providing network information for terminal, and notification server
KR20200114916A (ko) 이동 통신 시스템에서 네트워크 분석 정보를 udm을 통해 전달 할 때 nf의 동작과 동기화 방법
JP7168746B1 (ja) 通信制御装置、方法およびシステム
KR102015413B1 (ko) 로컬 네트워크에서의 인터페이스 설정장치 및 방법

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17802115

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01.03.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17802115

Country of ref document: EP

Kind code of ref document: A1