WO2018126342A1 - Communication method and device - Google Patents

Abstract

A communication method and device. The method comprises: a terminal sends a first connection/session establishment request message to an access node; the terminal determines, according to the context of a network slice saved by the terminal, whether the terminal establishes an association with the network slice; if the terminal establishes the association with the network slice, the terminal carries a network slice temporary identifier of the terminal in the first connection/session establishment request message, so that the terminal establishes a connection with the network slice. The network slice provides a service for a first connection/session, and the network slice temporary identifier identifies the terminal in the network slice. According to embodiments of the present invention, the context of a network slice is saved by a terminal, and thus, the time of accessing the network slice by the terminal can be saved when the terminal initiates a connection/session request to a network.

Description

Communication method and device Technical field

The present invention relates to the field of mobile communication technologies, and in particular, to a communication method and device.

Background technique

Fast-growing mobile communication systems need to meet the business needs of multiple scenarios. For example, high-definition video mobile broadband services, mass machine communication, high-reliability mobile device communication such as vehicle communication, and the like.

In the 5G communication system, in order to meet the service requirements of different scenarios, a network slicing or Network Slicing (NS) method may be adopted. That is, the network may consist of multiple network slices, and a particular network slice may be defined as a collection of logical network functional entities that support the communication traffic requirements of a particular scenario. For example, network slicing that supports a large number of machine communication, network slicing that supports mobile broadband services, and the like. That is, 5G communication requires the support terminal to simultaneously access a plurality of different network slices, thereby using services provided by a plurality of different network slices. For example, the terminal can simultaneously access network slices supporting mobile broadband services and network slices supporting Critical Communication (CriC).

In the Evolved Packet System (EPS), when a terminal moves from one Tracking Area (TA) to another Tracking Area, location registration must be re-registered on the new tracking area to notify the network to change it. The location information of the stored terminal, this process is the Tracking Area Update (TAU). However, in a 5G communication system, different network slices are used to serve different service requirements of the terminal, and different network slices may require tracking area update.

That is to say, in the 5G communication system, how to select different network splicing schemes for different applications/services of the terminal has not been proposed, and how the terminal performs location area updating for different network shards has also become an urgent problem to be solved.

Summary of the invention

The present application provides a communication method and device, which can select different network slices for different applications/services of the terminal, that is, the terminal establishes association with different network slices; and when the location area of the terminal is updated, the terminal can update different networks. The location area of the slice.

A first aspect of the present application provides a communication method, where the method includes: a terminal sends a connection/session establishment request message to an access node; and the terminal determines, according to a network slice context saved by the terminal, whether the terminal is established with a network slice. Correlation; if the terminal is associated with the network slice, the terminal carries the network slice temporary identifier of the terminal in the connection/session establishment request message, so that the terminal establishes a connection with the network slice; The network slice provides service for the connection/session, and the network slice temporary identifier identifies the terminal in the network slice.

In the embodiment of the present invention, the terminal can save the network slice context, and the network slice context includes the network slice temporary identifier, and the terminal can establish a connection with the network slice according to the network slice temporary identifier; that is, the terminal does not need to perform network every time the connection is established. The slice selection function entity selects a network slice for the terminal, and reduces the time for the terminal to access the network slice.

In a possible implementation, the method further includes: if the terminal is not associated with the network slice, the terminal carries the public identifier and the service parameter of the terminal in the connection/session establishment request message. .

In a possible implementation manner, the public identifier of the terminal includes an international mobile subscriber identity of the terminal; or the network slice subscribed by the terminal is used to identify a terminal identifier of the terminal; or the terminal subscribes The default network slice is used to identify the terminal identity of the terminal.

In a possible implementation manner, the specific form of the network slice temporary identifier of the terminal includes the network slice identifier and the terminal temporary identifier, or a temporary identifier of the terminal.

A second aspect of the present application provides a communication method, where the method includes: an access node receiving a connection/session establishment request message sent by a terminal, where the connection/session establishment request message carries a network slice temporary identifier of the terminal; The access node determines that the network slice temporary identifier pair of the terminal is saved by itself a network slice context of the terminal, the network slice context of the terminal includes a network slice temporary identifier and a control plane function entity identifier of the terminal; and the access node selects the terminal according to the network slice context of the terminal a control plane functional entity; wherein the network slice provides service for the connection/session, and the network slice temporary identification identifies the terminal in the network slice.

In a possible implementation manner, the method further includes: if the access node does not save a terminal network slice context corresponding to a network slice temporary identifier of the terminal, the access node forwards the connection/session Establishing a request message to the network slice selection function entity, so that the network slice selection function entity selects a control plane function entity for the terminal, such that the control plane function entity belongs to the network slice, and the control plane function entity is caused And the access node belongs to the same service area of the network slice.

In a possible design, the terminal receives the first message sent by the access node, where the first message carries a mobility management area identifier or a mobility management area identifier list; the terminal determines the mobility management area identifier saved by the terminal or The mobility management area identifier list does not include the mobility management area identifier or the mobility management area identifier list in the first message; the terminal sends a mobility management area update request message to the access node.

In one possible design, the first message is a broadcast or multicast message sent by the access node.

In a possible design, the access node receives the mobility management area update request message sent by the terminal; the access node determines the mobility management area update request message; and when the mobility management area update request message is mobile And the access node forwards the mobility management area update request message to the mobility management function entity; when the mobility management area update request message is a session management request message, the access The node forwards the mobility management area update request message to the session management function entity.

A third aspect of the present application provides a communication method, the method comprising: a mobility management function entity receiving a mobility management area update request message of a terminal from an access node; determining a mobile terminal for the terminal according to the mobility management area update request a management area identifier and/or a mobility management area identifier list; the mobility management function entity determines a service area of the terminal associated network slice according to the mobility management area identifier and/or the mobility management area identifier list Determining whether the service area identifier of the network slice is included in the terminal network slice context saved by the terminal; if the network slice context of the terminal does not include the service area identifier of the network slice, then moving The sexual management function entity selects a session management function entity for the terminal; and sends a mobility management area update response message to the terminal.

In a possible implementation manner, if the network slice context of the terminal does not include the service area identifier of the network slice, the mobility management function entity selects a session management function entity for the terminal, including Selecting a session management function entity in the network slice for the terminal according to the terminal network slice temporary identifier and/or the service area identifier of the network slice in the network slice context, so that the session management function entity is The terminal selects a user plane function entity, the user plane function entity belongs to the network slice of the service area identifier, and the user plane function entity and the access node belong to the network slice whose service area identifier changes. a service area, sending a first message to the session management function entity, where the first message includes a service area update message, where the terminal network slice temporary identifier is that the network slice where the service area changes is the The temporary identifier assigned by the terminal.

The fourth aspect of the present application provides a communication method, the method includes: receiving, by a terminal, an access node, sending a first message, where the first message carries a service area list; and determining, by the terminal, a network slice service area identifier in a network slice context saved by the terminal. Whether it is included in the service area list; if the network slice service area identifier in the network slice context saved by the terminal is not included in the service area list, send a service area update request message to the access node; Receiving a network slice service area update response message sent by the access node, so that the terminal updates the network slice context saved by itself.

In a possible implementation manner, the first message is a broadcast message or a multicast message that is sent by the access node to the terminal.

A fifth aspect of the present application provides a communication method, where the method includes: a mobility management function entity receives a service area update request message of a terminal from an access node, where the service area update request message includes at least one network slice service area identifier; Comparing at least one network slice service area identifier of the terminal with at least one network slice service area identifier of the access node; if at least one network slice service area identifier of the terminal and at least one of the access node If the network slice service area identifier is different, the first session management function entity is selected according to the network slice temporary identifier of the terminal, where the network slice temporary identifier of the terminal is, the network slice where the service area changes is the The temporary identifier assigned by the terminal.

In a possible implementation manner, the method further includes: the mobility management function entity sending the network slice service area update request message to the session management function entity, so that the session management function entity is The terminal selects a user plane function entity, the user plane function entity belongs to a network slice in which the service area changes, and the user plane function entity and the access node belong to the same service area of the network slice.

In a possible implementation manner, the specific form of the network slice service area identifier includes a network slice identifier and a service area identifier, or a network slice service area identifier.

In another aspect, the embodiment of the present invention provides a terminal, where the terminal can implement the functions performed by the terminal in the foregoing implementation manner, and the functions may be implemented by using hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In one possible design, the structure of the terminal includes a processor and a transceiver configured to support the terminal to perform corresponding functions in the above methods. The transceiver is configured to support communication between the terminal and a mobility management function entity, an access node, or other network element. The terminal can also include a memory for coupling with the processor that retains the program instructions and data necessary for the terminal.

In still another aspect, the present application provides a mobility management function entity having a function of implementing the behavior of a mobility management function entity in the above embodiment. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the mobility management function entity includes a processor configured to support the mobility management function entity to perform corresponding functions in the above methods. Further, the mobility management function entity may further include a communication interface for supporting communication between the mobility management function entity and the session management function entity, the terminal, or other network elements. Further, the mobility management function entity may further include a memory for coupling with the processor, which stores program instructions and data necessary for the mobility management function entity.

In another aspect, an embodiment of the present invention provides an access node, where the access node has a function of implementing an access node behavior in the foregoing implementation manner. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the access node includes a processor configured to support the access node to perform corresponding functions in the methods described above. Further, the access node may further include a communication interface for supporting communication between the session management function entity and the mobility management function entity or other network elements. Further, the access node may further comprise a memory for coupling with the processor, which stores program instructions and data necessary for the access node.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the foregoing mobility management function entity, including a program designed to perform the above aspects.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing the computer software instructions used for the access node, including a program designed to perform the above aspects.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storage for the above Computer software instructions for use by the terminal, including programs designed to perform the above aspects.

In still another aspect, embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a mobility management function entity in the method design described above.

In still another aspect, embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform the functions performed by an access node in the method design described above.

In still another aspect, embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a terminal in the method design described above.

The network slicing context saved by the terminal, that is, the terminal can save the associated network slice, thereby saving the time for the terminal to access the network slice; and when the terminal moves, performing the service area update and the mobility management area update.

DRAWINGS

1 is a schematic diagram of a system network in the prior art;

2 is a schematic flowchart of a communication method according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart of a method for establishing a connection/session of a UE according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart of a method for establishing a connection/session of a UE according to another embodiment of the present invention;

FIG. 5 is a schematic flowchart of still another communication method according to an embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of a method for updating a mobility management area according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart diagram of still another communication method according to an embodiment of the present invention;

FIG. 8 is a schematic flowchart of a method for updating a service area according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an access node according to an embodiment of the present disclosure;

FIG. 9b is a schematic structural diagram of still another access node according to an embodiment of the present disclosure;

FIG. 10a is a schematic structural diagram of a mobility management function entity according to an embodiment of the present invention;

FIG. 10b is a schematic structural diagram of still another mobility management function entity according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 11b is a schematic structural diagram of still another terminal according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments.

FIG. 1 is a schematic diagram of a system network in the prior art. As shown in FIG. 1 , the user equipment UE accesses a core network (Core Network, CN) through an access network (AN). Specifically, the core network CN may include a Network Slice Selection Function (NSSF), a Subscriber Repository, and a Control Plane Mobility Management Network Function (CP-MM). ), hereinafter referred to as “mobility management function entity”; Control Plane Session Management Network Function (CP-SM), hereinafter referred to as “session management function entity”; user plane network function entity (User Plane Network Function), which may also be referred to as "user plane function entity" hereinafter. As shown in FIG. 1, the first network slice includes an access network AN, a control plane mobility management function entity CP-MM, a control plane session management function entity CP1-SM, and a user plane function entity UP1; the second network slice includes an AN, CP-MM, CP2-SM, and UP2; the third network slice includes AN, CP3-SM, and UP3. The terminal UE can simultaneously access multiple different network slices, and different network slices can support different service/application communication; multiple network slices can share the mobility management function entity CP-MM, such as the first network slice and the second The network slice shares the CP-MM; the plurality of network slices may share the access network AN, and the access network AN may be a Radio Access Network (RAN), such as a first network slice, a second network slice, and a The three network slices share the AN; each network slice has a specific control plane session management function entity and a user plane function entity.

3GPP TR 23.799 v0.5.0 describes the network slice selection function entity NSSF, the user repository, the mobility management control plane, the session management control plane, and the session management user plane in the core network CN, and details are not described herein.

It should be noted that, in the embodiment of the present invention, different network slices have different service area divisions, and service areas of different network slices may overlap each other.

The embodiments of the present invention are applicable to a communication system that supports terminal access network slicing. The techniques described in this disclosure may be applicable to subsequent evolution systems using LTE systems, such as fifth generation 5G systems and the like. For the sake of clarity, only the fifth generation 5G system will be described here as an example.

In the present application, the terms "network" and "system", "service area" and "service area" are often used interchangeably, but those skilled in the art can understand the meaning. In the present application, “first” and “second” are to be understood as a distinction between a request message or a response message, and are not to be construed as limiting the message, nor as a limitation on timing. The user equipment UE involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment) , referred to as UE), mobile station (MS), terminal, terminal equipment, and so on. For convenience of description, in the present application, the user equipment mentioned above is collectively referred to as a UE.

2 is a schematic flowchart of a communication method according to an embodiment of the present invention. As shown in FIG. 2, the method includes steps S201-S203.

S201. The UE sends a connection/session request message to the AN, where the connection/session request message carries the network slice temporary identifier of the UE.

The UE determines whether the UE is associated with the network slice according to the network slice context (NS context) saved by the UE. If the UE is associated with the network slice, the UE carries the network slice temporary identifier of the UE in the connection/session establishment request message; if the UE is not associated with the network slice, the UE is in the connection/session The establishment request message carries the public identity and service parameters of the UE.

It should be noted that the network slice provides services for the connection/session, and the network slice is The time identifier identifies the UE in the network slice.

The public identity of the UE includes the international mobile subscriber identity of the UE; or the network slice subscribed by the UE is used to identify the UE identity of the UE; or the default network slice subscribed by the UE is used to identify the UE. UE identification. The specific form of the network slice temporary identifier of the foregoing UE includes the network slice identifier and the UE temporary identifier; or a temporary identifier of the UE.

S202. The AN determines whether it saves the network slice context of the UE.

The AN determines that the network slice context of the UE corresponding to the network slice temporary identifier of the UE is saved, and the network slice context of the UE includes the network slice temporary identifier and the control plane function entity identifier of the UE. The AN selects a control plane functional entity for the UE according to the network slice context of the UE.

In an example, if the AN does not save the UE network slice context corresponding to the network slice temporary identifier of the UE, the AN forwards the connection/session establishment request message to the network slice selection function entity NSSF, so that the network The slice selection function entity NSSF selects a control plane function entity for the UE, such that the control plane function entity belongs to the network slice, and the control plane function entity and the access node belong to the same network slice Service area.

S203. The AN sends a connection/session establishment response message to the UE.

In the embodiment of the present invention, when the UE initiates a connection/session request to the AN, the UE itself saves the context of the network slice serving the connection/session, and the network slice context includes the network slice temporary identifier of the UE; the UE is connected. When the session is requested, the network slice temporary identifier of the UE is carried, and the network slice can be directly accessed, thereby saving the time for the UE to access the network slice.

The process will be described below by taking FIG. 3 and FIG. 4 as examples.

FIG. 3 is a schematic flowchart of a method for establishing a connection/session of a UE according to an embodiment of the present invention; FIG. 4 is a schematic flowchart of a method for establishing a connection/session of a UE according to another embodiment of the present invention. In Figures 3 and 4, CP1 is the control plane functional entity; CP1 may be a CP-SM, which represents the control plane for session management within a particular network slice. UP1 and UP2 are user plane functional entities that represent specific User plane for data transmission within the network slice. NSSF represents a network slice selection function entity.

As shown in FIG. 3 and FIG. 4, an embodiment of the present invention provides a method for selecting different network slices for different applications/services of a UE. A network slice refers to a set of logical network functional entities that support communication service requirements in a specific scenario. The UE network slice context is a description of a network slice serving the UE. Both the UE and the AN maintain a UE network slice context. The UE network slice context in the UE includes the UE usage type, service type, and/or application identification.

When the application X in the UE initiates a service request to the network side, the UE checks whether it saves the UE network slice context that is the same as the application X identifier or the UE usage type or service type to which the application X belongs. That is to say, the UE determines whether it has already established an association with a network slice serving the application X or a network slice matching the UE usage type or service type to which the application X belongs. The association of the UE with the network slice means that the UE is registered in the network slice or has been registered in the network slice, and the network slice can provide services for the UE.

If the UE is not associated with the network slice serving the application X, or is not associated with the network slice whose type or service type is matched by the application X to which the application X belongs; that is, if the UE does not save the application X, or If the UE to which the X belongs belongs to the UE network slice context whose type or service type matches, step 301 to step 311 shown in FIG. 3 are performed.

In step 301, the UE initiates a connection/session establishment request to an access node (Access Node, AN). The connection/session establishment request is triggered by application X. For example, when the application X needs to send data to the network side, the connection/session establishment request is triggered.

The connection/session establishment request includes the UE common id, the service parameters (ie, "application/service information"), and other parameters required to establish a connection/session. The service parameters may include: UE usage type, and/or service type, and/or application identification. Here, the UE public identity may be the UE's International Mobile Subscriber Identity (IMSI), or all the network slices that the UE subscribes to identify the UE's UE identity, or the UE's subscribed default network slice is used to identify the UE's UE identity. The UE public identity may be used to identify the UE and be shared by one or more network slices that the UE subscribes to. UE usage type, used to indicate the main purpose or usage scenario of the UE, for example: (use the UE as) ordinary instrument or general a sensor, a vehicle, a telemedicine device, an entertainment device, etc.; a service type for indicating a category of a service (corresponding to an application X), for example, a mobile broadband service, a machine communication, an emergency service; an application identifier for indicating a specific application Or an application, for example, application identifier 1 (for example: App-ID=011) is used to identify the WeChat WeChat application, and application identifier 2 (for example: App-ID=021) is used to identify the TaobaoTMall application.

It should be noted that the UE public identity may be pre-configured in the UE.

In step 302, the AN forwards the connection/session establishment request to the NSSF in the core network CN.

In step 303, the NSSF selects a specific network slice NS1 for the UE according to the UE public identity and service parameters in the connection/session establishment request. For example, the NSSF uses, according to at least one of the UE usage type, the service type, and the application identifier, and the UE's International Mobile Subscriber Identity (IMSI), all the network slices that the UE subscribes to identify the UE identity of the UE, and the default network slice that the UE subscribes to is used. At least one of the UE identifiers of the UE is identified, the network slice NS1 is selected for the UE, and the CP1 is selected for the UE. Here, the CP1 may be the mobility management function entity CP1-MM or the session management function entity CP1-SM, determined by the architecture of the specific network slice NS1 (eg, whether CP1-MM is included), the service parameters of the UE, and the like.

It is worth noting that the CP1 selected by the NSSF for the UE should meet the following conditions:

(1) CP1 belongs to a specific network slice NS1;

(2) CP1 and AN belong to the same service area of the specific network slice NS1.

In step 304, the NSSF sends a connection/session establishment request to CP1. The connection/session establishment request may include parameters such as a UE public identity, an identity of the AN, an address of the AN, and the like. The address of the AN may be the IP address of the AN.

In step 305, CP1 initiates an authentication and security request to the UE. In this step, CP1 completes authentication with the UE and establishes a security mechanism. For example, determine integrity protection and encryption algorithms and related parameters. The CP1 allocates a temporary identifier (UE NS1 temporary id, also referred to as “terminal network slice temporary identifier”) of the UE in the specific network slice NS1, and generates a UE network slice context, and allocates a connection/session identifier for the connection/session. . Here, CP1 belongs to a specific network slice NS1.

In the embodiment of the present invention, the UE network slice context may include: a temporary identifier, a service parameter, a network slice service area identifier, a network slice connection/session identifier of the UE in a specific network slice NS1, And safety parameters.

The specific form of the temporary identification of the UE in the specific network slice NS1 may include the following.

(1) Network Slice id + UE temporary id;

(2) UE temporary identification. At this time, it is required to ensure that different network slices have different UE temporary identification ranges. For example, the highest-order first four bits of the UE temporary identifier of the specific network slice NS1 are 0001, and the highest-order first four bits of the UE temporary identifier of the specific network slice NS2 are 0002, thereby distinguishing UE temporary identifiers of different network slices.

It should be noted that the UE may further include other parts in the temporary identifier in the NS1. For example, the CP1 identifier in the network slice NS1 is not described here.

In step 306, the control plane function entity CP1 selects UP1 for the UE, so that the UE establishes a user plane connection with the UP, and the user plane connection is used for transmitting data, and the data may include the UE to the network entity or the peer terminal. The business data transmitted between the two may include voice, video, text, and the like. The control plane functional entity CP1 sends a connection/session establishment request to UP1. The connection/session establishment request includes a UE network slice temporary identifier, an identifier of the AN, and an address of the AN.

The selected UP1 should meet the following conditions:

(1) UP1 belongs to a specific network slice NS1;

(2) UP1 and AN belong to the same service area of the specific network slice NS1.

In step 307, UP1 sends a connection/session establishment response to CP1. The connection/session establishment response may include: a UE network slice temporary identifier, a user plane function entity identifier (UP1 id), and/or an address of UP1. The address of the UP1 may be the IP address of the UP1.

In step 308, CP1 sends a connection/session establishment response to the NSSF. The connection/session establishment response may include: a UE network slice temporary identifier, a network slice service area identifier (NS1 service area id), a network slice connection/session identifier (NS1 connection/session id), and a control plane function entity identifier (CP1 id). The control plane function entity address (CP1 address), the user plane function entity identifier (UP1 id), and the user plane function entity address (UP1 address).

Here, the specific form of the network slice service area identifier may be the following.

(1) Form 1: Network Slice id + service area id;

(2) Form 2: The network slice service area identifier only contains the service area identifier. At this time, it is required to ensure that different network slices have different service area identification ranges. For example, the top four bits of the service area identifier of the first network slice NS1 are 0001, and the first four bits of the service area identifier of the second network slice NS2 are 0002, thereby distinguishing the service area identifiers of different network slices. .

It should be noted that the service area identifier may also include other parts. For example, the service area identifier also includes a control plane function entity identifier (NS CP1 id) in the network slice, which is not described here. The service area identifier can be configured in CP1, UP1, and/or AN in the corresponding network slice.

Optionally, if the network slice identifier and/or the network slice service area identifier does not include the network slice identifier, the connection/session establishment response in the step may also carry the network slice identifier.

In step 309, the NSSF forwards the connection/session establishment response to the AN.

In step 310, the AN sends a connection/session establishment response to the UE. The connection/session establishment response may include a UE network slice temporary identifier, a network slice service area identifier, a network slice connection/session identifier.

The specific AN1 may hold the context of the UE in the network slice NS1 (UE NS1 context, may also be referred to as "UE network slice context"). The context of the UE saved in the AN1 in the network slice NS1 may include the following contents: a UE network slice temporary identifier, a network slice service area identifier, a control plane function entity identifier, a control plane function entity address, a network slice connection/session identifier, and a user plane. Functional entity ID, user plane functional entity address.

In step 311, the UE saves the context of the UE in the network slice NS1. The context of the UE in the network slice NS1 may include the following: a service parameter, a UE network slice temporary identifier, a network slice service area identifier, a security key, a network slice connection/session identifier. The above service parameters may include: a user usage type, a service type, and/or an application identification.

In the embodiment of the present invention, the UE can establish a connection/session with multiple network slices, and does not need to perform network slice selection every time the connection/session of the application/service is established. This will be described below using FIG. 4 as an example.

If the UE has been associated with a network slice serving the application X, or has been associated with a network slice that matches the UE usage type or service type to which the application X belongs, in other words, if the UE is saved with the application X, Or, the UE network slice context to which the UE usage type or the service type matches is applied, and steps 401 to 408 shown in FIG. 4 are performed.

In step 401, the UE sends a connection/session establishment request to the AN. The UE network slice temporary identifier in the UE network slice context is carried in the connection/session establishment request. The UE network slice temporary identifier is a temporary identifier allocated by the control plane function entity CP to the UE in the network slice, and is used to identify the UE in the network slice.

Here, if the UE network slice matching the application type or service type to which the application X or the application X belongs is NS1, the user temporary identifier for the network slice NS1 is carried in the connection/session establishment request. The UE network slice temporary identity is used to identify the UE in the network slice NS1.

In step 402, the AN queries the UE network slice context saved in the AN according to the temporary identifier of the UE in the network slice, so as to determine that the temporary identifier of the UE in the network slice corresponds to the context of the UE in the network slice NS1. The parameters in the UE network slice context saved in the AN have the same parameters and different parameters as the parameters above and below the UE network slice saved in the UE. For example, the same parameter is the temporary identifier of the UE in the network slice, the network slice service area identifier, the network slice connection/session identifier; the difference is that the parameter saved in the AN has the control plane function entity identifier and its address, and the user plane function entity identifier And its address; the parameters stored in the UE have a security key and a service parameter. The network slice context saved in the UE is a network slice indicating that the UE is served, and is queried in the control plane function entity of the UE-provided service saved in the AN by using the shared UE network slice temporary identifier.

If the UE network slice context is not saved in the AN, or the UE network slice context corresponding to the UE network slice temporary identifier is not in the UE network slice context saved in the AN, the AN sends the connection/session establishment request to the NSSF, and then performs FIG. 3 In the similar steps 303 to 311.

At this time, when the similar steps 303 to 311 in FIG. 3 are performed, the difference from FIG. 3 is that:

(1) In step 303, the NSSF selects the previously selected network slice NS1 corresponding to the UE network slice temporary identifier for the UE according to the UE network slice temporary identifier, and selects the previous control plane. Functional entity CP1.

It should be noted that, when the previous CP1 and the AN are not in the same service area, or for load balancing purposes, the NSSF may reselect the control plane function entity, for example, select the control plane function entity CP2 other than the control plane function entity CP1. .

(2) Step 305 may be omitted, that is, the authentication and security request between the CP1 and the UE is not performed. After the NSSF sends a connection/session establishment request to CP1, CP1 sends a connection/session establishment request to UP1 in network slice NS1.

(3) In step 311, the UE updates the UE network slice context saved by the UE.

In step 402, if the UE network slice context is saved in the AN, and the UE network slice context corresponding to the UE network slice temporary identifier exists in the network slice context of the UE saved in the AN. The AN may be based on the UE network slice temporary identifier and/or AN, because the UE network slice context saved in the AN includes the network slice NS1 identifier corresponding to the UE network slice temporary identifier, and further includes the core network control plane function entity identifier and its address. The UE network slice context determines the network slice NS1 corresponding to the connection/session establishment request, and selects the CP1 of the core network in the UE network slice context stored in the AN, and performs the following steps.

In step 403, the AN sends a connection/session establishment request to CP1. The UE network slice temporary identifier may be carried in the connection/session establishment request.

In step 404, CP1 selects UP1 for the UE.

CP1 may also select a new user plane function entity UP2 for the UE and send a connection/session establishment request to UP2. The connection/session establishment request may carry the temporary identifier, the access node identifier, and the access node address of the UE in the network slice NS1.

The selected UP2 must meet the following conditions:

(1) UP2 belongs to a specific network slice NS1;

(2) UP2 and AN belong to the same service area of the specific network slice NS1;

(3) For the purpose of load balancing or the service area where UP1 and the UE are not in the same network slice N1, the priority of UP2 is higher than that of the previous UP1.

At this point, CP1 also assigns a connection/session ID (connection/session id 2) for the connection/session.

In step 405, UP2 sends a connection/session establishment response to CP1. The temporary identity, the user plane function entity identifier (UP2id), and the user plane function entity address of the UE in the network slice NS1 may be carried in the connection/session establishment response. The user plane function entity address may be an IP address of the user plane function entity.

In step 406, CP1 sends a connection/session establishment response to the AN. The connection/session establishment response may carry the temporary identifier of the UE in the network slice NS1, the service area identifier in the specific network slice NS1, the connection/session identifier of the specific network slice NS1, the control plane function entity identifier, the control plane function entity address, User plane function entity identifier, user plane function entity address. The service area identifier of the UE in the specific network slice NS1 is unchanged or the original service area identifier. When the UE changes in the network slice, the service area identifier in the specific network slice NS1 is a new service. Area identification.

In step 407, the AN sends a connection/session establishment response to the UE. The connection/session establishment response may carry a temporary identifier of the UE in the specific network slice NS1, a service area identifier of the specific network slice NS1, and a connection/session identifier of the specific network slice NS1.

The AN may also update the context of the UE in the AN at NS1. The UE saved in the AN may include the following in the context of the NS1: the temporary identifier of the UE in the network slice NS1, the service area identifier in the network slice NS1, the new connection/session identifier of the network slice NS1, and the control plane function entity identifier. , control plane function entity address, new user plane function entity identifier, new user plane function entity address. The service area identifier in the network slice NS1 may be different from the original service area identifier in the network slice NS1.

In step 408, the UE updates the context of the UE in the UE in the network slice NS1.

The context of the UE in the UE in the network slice NS1 may include the following: service parameters, the temporary identity of the UE in the network slice NS1, the service area identifier of the network slice NS1, the new connection/session identity of the network slice NS1, the security key . The service parameter may be a UE usage type, a service type, and/or an application identifier.

After the UE moves, the mobility management area of the UE may change. 5 and 6 will be described below as an example. In FIG. 5 and FIG. 6, MM represents a mobility management function entity, CP-MM represents a mobility management function entity, CP1-SM represents a session management function entity, and UP2 represents a user plane function entity. FIG. 5 is a schematic flowchart of still another communication method according to an embodiment of the present invention. As shown in FIG. 5, the method includes steps S501-S506.

S501: The AN sends a first message to the UE, where the first message carries a mobility management area identifier or a mobility management area identifier list.

The first message may be a broadcast or multicast message sent by the access node.

S502. The UE determines that the mobility management area changes.

In this step, the UE determines that the mobility management area identifier or the mobility management area identifier list that is saved by itself does not include the mobility management area identifier or the mobility management area identifier list in the first message, and the UE determines that the mobility management area has been A change has occurred.

S503. The UE sends a mobility management area update request message to the AN.

S504. The AN determines that the mobility management area update request message is a mobility management request message.

In this step, the AN determines the mobility management area update request message. If the mobility management area update request message is a mobility management request message, the AN forwards the mobility management area update request message to the mobility management function entity.

In one example, when the mobility management region update request message is a session management request message, the access node forwards the mobility management region update request message to a session management function entity message.

S505. The AN sends the mobility management area update request message to the MM.

The MM determines a mobility management area identifier and/or a mobility management area identifier list for the UE according to the mobility management area update request message. The mobility management area identity and/or mobility management zone identity list is a new mobility management zone identity of the UE, and/or a new mobility management zone identity list.

S506. The MM sends a mobility management area update response message to the UE.

In an example, the MM may further determine a service area identifier of the UE associated network slice according to the mobility management area identifier and/or the mobility management area identifier list; and the MM determines the terminal network slice saved by itself. Whether the service area identifier of the network slice is included in the context. If the service area identifier of the network slice is not included in the network slice context of the terminal, the MM selects a session management function entity for the UE.

In an example, the MM selects a session management function entity for the UE, and the MM selects, for the UE, the UE network slice temporary identifier and/or the service area identifier of the network slice in the network slice context. a session management function entity in the network slice, so that the session management function entity selects a user plane function entity for the terminal, the user plane function entity belongs to a network slice of the service area identifier, and the user plane function The entity and the access node belong to the same service area of the network slice whose service area identifier changes. The MM sends a first message to the session management function entity, the first message including a service area update message.

It should be noted that the terminal network slice temporary identifier is a temporary identifier that is allocated to the terminal by a network slice whose service area changes.

Specifically, FIG. 6 is a schematic flowchart diagram of a method for updating a mobility management area according to an embodiment of the present invention. In this embodiment, the terminal directly senses the change of the mobility management area and issues an update request to the network side.

In step 601, the mobility management area manages the location information, security, and service continuity of the mobile terminal to optimize the connection state between the terminal and the network, thereby providing guarantee for application of various network services. A network slice includes one or more mobility management areas.

When the UE moves, the mobility management area served for the UE changes, and the UE cannot receive the message through the previous mobility management area, so the UE needs to update the mobility management area. When it is determined that the mobility management area changes, the UE sends a mobility management area update request (MM area update request) to the AN. The mobility management area update request may carry one or more network slice identifiers, one or more UE network slice temporary identifiers, terminal saved or previously accessed mobility management area identifiers. The network slice identifier is used to identify the network slice, and the UE network slice temporary identifier It is used to identify the terminal; the one or more network slice identifiers respectively correspond to different network slices associated with the UE. Correspondingly, the one or more UE network slice temporary identifiers respectively correspond to temporary identifiers allocated by the UE to different UEs associated with the network slice.

It should be noted that there may be multiple conditions for triggering the mobility management area update request. For example, the UE receives a broadcast/multicast message sent by the AN. The broadcast/multicast message includes a mobility management area identifier (MM area id) or a mobility management area identifier list (MM area id list). The UE compares the mobility management area identifier or the mobility management area identifier list in the broadcast/multicast message with the mobility management area identifier or the mobility management area identifier list currently saved by the UE, and determines the mobility management area identifier or the mobile Whether the list of sexual management areas identifies changes. If the UE finds that the mobility management area identifier or the mobility management area identifier list changes, the UE sends a mobility management area update request to the AN. The UE may also determine whether the mobility management area changes in other manners, and details are not described herein again.

It should be noted that, when the UE performs registration or performs the mobility management area update, before the step 601, the mobility management function entity CP-MM may allocate the mobility management area identifier or the mobility management area identifier list to the UE, where The mobility management area identifier or the mobility management area identifier list may be carried in the registration response message or the mobility management area update response message and sent to the UE.

In step 602, the AN sends a mobility management area update request to the mobility management function entity CP-MM of the network slice sharing.

After the AN receives the mobility management area update request from the UE, the AN determines the mobility management area update request. It is determined whether the mobility management area update request is a mobility management request message or a session management request message. The AN determines according to the type parameter of the message in the mobility management area update request, where the mobility management message includes the UE registration, the current location of the UE, and the session management message includes the establishment, modification, and release of the session.

If the mobility management area update request is a mobility management request message, the AN transmits the mobility management request message to the mobility management function entity CP-MM shared by the plurality of network slices. If the mobility management area update request is a session management SM request message, the AN sends a session management request message The control plane function entity CP-SM of the specific network slice corresponding to the network slice temporary identifier sent to the UE.

In step 603, the CP-MM determines a new mobility management area identifier or a new mobility management area identifier list of the UE according to the mobility management area update request message.

The CP-MM may be configured according to a pre-configured mobility management area identifier (or mobility management area identifier list) information, for example, a pre-configured "AN and mobility management area identifier (or mobility management area identifier list) mapping" table. And determining, by the identifier or address of the AN that forwards the mobility management area update request, a new mobility management area identifier or a new mobility management area identifier list of the UE. Alternatively, in step 602, the AN sends a new mobility management area identifier (or mobility management area identifier list) to the CP-MM along with the mobility management area update request, and the CP-MM provides new mobility according to the AN. The management area identifier (or the mobility management area identifier list) determines a new mobility management area identifier of the UE or a new mobility management area identifier list. An AN can serve one or more mobility management areas, so the AN has a corresponding mobility management area identifier (or mobility management area identifier list).

In addition, the CP-MM determines, according to one or more UE network slice temporary identifiers in the mobility management area update request, or one or more network slice identifiers, the network slice currently associated with the UE, that is, the network associated with the UE. slice.

The CP-MM determines the service area identifier of the network slice to which the UE is associated. Specifically, the CP-MM may map the UE's new mobility management area identifier list (or new mobility management area identifier) to the network slice service area identifier of the network slice associated with the UE.

One network slice service area associated with the UE includes one or more mobility management areas, and one mobility management area may also belong to multiple different service areas of multiple network slices. That is to say, although the mobility management area identifier (or the mobility management area identifier list changes), the network slice service area identifier associated with the UE does not necessarily change. Therefore, the CP-MM determines whether the service area of the network slice associated with the UE changes.

Specifically, the CP-MM may compare the service area identifier in the UE network slice context saved by itself with the current service area identifier of the network slice associated with the UE determined by the CP-MM, to determine Whether the service area of one or more network slices associated with the UE changes. If the CP-MM finds that the service area identifier of one or more network slices associated with the UE changes, step 604 shown in FIG. 6 is performed, otherwise step 608 shown in FIG. 6 is performed.

It should be noted that the mapping table of the mapping relationship between the mobility management area identifier list (or mobility management area identifier) and the network slice service area identifier may be maintained by the CP-MM, and the mapping table may be pre-configured in mobility management. Functional entity CP-MM. The terminal can move within a specific mobility management area (same location at the same time).

The mapping table between the mobility management area identifier list (or mobility management area identifier) and the network slice service area identifier is as follows, that is, the following mapping exists between the two:

When the UE is moved to the MM Area (list) 2 by the MM Area (list) 1 (identified by the MM Area (list) ID1), the UE is in the Network Slice according to the above mapping table. The corresponding Service Area (identified by Service Area ID1) in 1 has not changed, but the corresponding Service Area in Network Slice 2 and Network Slice 3 has changed, that is, the Service Area 1 of Network Slice 2 is changed to Service Area 2; Changed from Service Area 1 of Network Slice 3 to Service Area 3 (identified by Service Area ID 2/4 and 3/5 in the above table). Therefore, CP-MM needs to send session messages to Network Slice 2 and Network Slice 3 respectively.

In step 604, if the CP-MM finds that the service area identifier of one or more network slices associated with the UE changes, the mobility management function entity CP-MM is based on the UE for each service area identifier that changes the network slice. The network slice temporary identifier and/or based on the new service area identifier, select the session management function entity CP-SM in the network slice, and send a message to the session management function entity CP-SM, the message including the service area update request (Service area update) Request) message or session management message. The session management message includes a session establishment message, a session release message, and a session modification message.

In the following steps 604 to 607, taking the specific network slice NS1 as an example, the flow of the service management area update by the mobility management function entity CP-MM is performed in the network slice where the identity of each service area changes:

If the specific network slice NS1 service area identifier (NS1 service area id) changes, the CP-MM determines the CP1-SM based on the UE network slice temporary identifier and/or based on the changed (new) specific network slice NS1 service area identifier. And send a session message to the CP1-SM. Since one session management function entity configures the service area identifier of one or more network slices, multiple session management function entities may configure the service area identifier of the same network slice, so the CP-MM may determine CP1-SM according to the service area identifier. . The session message includes a service area update request and/or a session management message. The session management message includes a session establishment message, a session release message, and a session modification message. The UE network slice temporary identifier may be carried in the service area update request or the session establishment request. The determined session management control plane function entity may also be a new session management control plane function entity CP2-SM in the specific network slice NS1.

In step 605, if the CP1-SM serving the UE changes, that is, the CP-MM selects a CP2-SM different from the CP1-SM that previously served the UE according to the new service area identifier, the new control plane function The entity CP2-SM may acquire the network slice context of the UE from the original CP1-SM according to the UE network slice temporary identifier, and/or obtain the subscription information of the UE from the network subscription management entity (for example, the Subscriber Repository), and complete the pair. UE authentication and authentication process.

Due to the change of the service area, the new control plane function entity CP2-SM can select a new user plane function entity UP2 for the UE and send a connection/session establishment request to UP2. The connection/session establishment request may carry parameters such as a UE network slice temporary identifier, an access node identifier, and an access node address.

UP2 should meet the following conditions:

(1) UP2 belongs to a specific network slice NS1;

(2) UP2 and the access node belong to the same service area of the specific network slice NS1.

The CP2-SM can also select a new user plane function entity UP2 according to the pre-configured user plane transmission path reselection/optimization rules. The rule of the user plane transmission path reselection/optimization may be a preferred specific user plane function entity UP2 within a specific service area NS1.

In step 606, UP2 sends a connection/session establishment response to CP1-SM. The connection/session establishment response may carry a UE network slice temporary identifier, a user plane function entity identifier, and a user plane function entity address.

In step 607, CP1-SM sends a service area update response to the CP-MM. The service area update response may carry a UE network slice temporary identifier, a new network slice service area identifier, a user plane function entity identifier, and a user plane function entity address.

In step 608, the CP-MM sends a mobility management area update response to the AN. The new mobility management service area identifier or the new mobility management service area identifier list and the UE network slice temporary identifier may be carried in the mobility management area update response. If the UE performs the update of the service area to the associated network slice, the mobility management area update response may also carry a new network slice service area identifier.

In step 609, the AN forwards the mobility management region update response to the UE.

In step 610, the UE updates the mobility management area identity or the mobility management zone identity list and updates the UE network slice context. The UE network slice context includes parameters such as a service parameter, a UE network slice temporary identifier, and a new network slice service area identifier. The service parameters include: UE usage type, service type, and/or application identification.

In the embodiment of the present invention, when the UE performs the update of the mobile area, the network (for example, the mobility management function entity) performs service area update on multiple network slices associated with the terminal according to the change of the mobile area, thereby quickly implementing the association associated with the terminal. The update of the terminal service node in the plurality of network slices, for example, the control plane function entity CP associated with the UE, or the update of the user plane function entity UP.

As can be seen from the above, when the UE moves, the service area of the UE may also change. Taking FIG. 7 and FIG. 8 as an example, after the UE directly perceives that the service area changes, the service area update is described. In FIG. 7 and FIG. 8, the description is made by the UE representing the terminal, the AN representing the access node, the MM or CP-MM representing the mobility management function entity, the CP1-SM representing the session management function entity, and the UP representing the user plane function entity. FIG. 7 is a schematic flowchart of still another communication method according to an embodiment of the present invention. As shown in FIG. 7, the method includes S701-S707.

S701. The AN sends a first message to the UE, where the first message carries a service area list.

The first message may be a broadcast message or a multicast message sent by the access node to the terminal.

S702. The UE determines that the service area sends a change.

In the changing step, the UE determines whether the network slice service area identifier in the network slice context saved by itself is included in the service area list. And if the network slice service area identifier in the network slice context saved by the terminal is not included in the service area list, send a first service area update request message to the access node.

S703. The UE sends a service area update request message to the AN, where the service area update request message carries a network slice service area identifier.

S704. The AN determines that the service area update request message is a mobility management request message.

The AN determines whether the service area update request message is a mobility management message or a session management message.

In one example, the AN determines that the service area update request message is the mobility management message, and the AN sends the service area update request message to the mobility management function entity of the network slice.

In one example, the AN determines that the service area update request message is the session management message, and sends the service area update request message to a session management function entity of the network slice.

S705. The AN sends a service area update request message to the MM.

S706, the MM determines that the service area changes, and selects a session management function entity.

In one example, the service area update request message includes at least one network slice service area identifier; the MM compares at least one network slice service area identifier of the UE with whether the at least one network slice service area identifier of the AN is the same. If the at least one network slice service area identifier of the UE is the same as the The at least one network slice service area identifier of the AN is different, and the session management function entity is selected according to the network slice temporary identifier of the UE;

It should be noted that the network slice temporary identifier of the terminal is a temporary identifier that is allocated to the terminal by a network slice whose service area changes.

In this step, the MM sends the network slice service area update request message to the session management function entity, so that the session management function entity selects a user plane function entity for the terminal, and the user plane function entity belongs to the The service area changes a network slice, and the user plane function entity and the AN belong to the same service area of the network slice.

It should be noted that the specific form of the network slice service area identifier includes a network slice identifier and a service area identifier; or a network slice service area identifier.

S707. The MM sends a service area update response to the AN, and the AN forwards the server update response to the UE.

The service area update of the network slice of the terminal will be described in detail below by taking FIG. 8 as an example. FIG. 8 is a schematic flowchart of a method for updating a service area according to an embodiment of the present invention. In this embodiment, the terminal directly perceives the change of the network slice service area, and then makes an update request.

In step 801, the UE receives a broadcast/multicast message sent by the AN, where the broadcast/multicast message includes a service area list. The service area list contains one or more service area identifiers for one or more network slices.

In step 802, the UE determines whether the service area of the network slice currently associated with the UE changes according to the service area list in the broadcast/multicast message and the UE network slice context saved by itself.

Specifically, the UE compares the network slice service area identifier in the UE network slice context with the network slice service area identifier in the service area list. It can be seen from the above step 408 that the service area identifier of the network slice has two forms. When comparing the service area identifiers of the two, the two forms are separately described.

(1) If the network slice service area identifier includes the network slice identifier, the UE may compare the same UE network slice context and the service area list with the network slice identifier to compare the service area identifiers therein. Is it the same?

(2) If the network slice identifier is not included in the network slice service area identifier, the UE may directly compare the UE network slice context and the service area list.

If the service area list in the broadcast/multicast message does not include at least one network slice service area identifier of the UE network slice context saved by the UE, the service area of the network slice currently associated with the UE is changed.

In step 803, if the service area of the network slice NS currently associated by the UE changes, the UE sends a service area update request to the AN. The service area update request may carry one or more UE network slice temporary identifiers and one or more saved network slice service area identifiers. The one or more saved network slice service area identifiers correspond to network slices whose service areas change. Correspondingly, the temporary identifier of the one or more UEs in the network slice corresponds to a temporary identifier allocated by the network slice that the service area changes. The service area of the network slice currently associated with the UE, the service area of the network slice has changed, and the service area of the network slice has not changed. The service area update request carries a network slice in which the service area currently associated with the UE changes.

In step 804, after receiving the service area update request from the UE, the AN determines whether the service area update request is a mobility management MM message or a session management SM message. If the service area update request is a mobility management MM message, the AN sends the service area update request to the mobility management function entity CP-MM shared by the plurality of network slices. If the service area update request is a session management SM message, the AN sends the service area update request to the control plane function entity CP-SM of the specific network slice corresponding to the network slice temporary identifier of the UE.

Optionally, the AN may also send one or more network slice service area identifiers corresponding to the AN to the CP-MM.

In step 805, the MM can determine whether the service area of the network slice currently associated with the UE is changed. Optionally, the CP-MM may also determine whether the service area of the network slice currently associated with the UE changes.

Specifically, the CP-MM compares one or more network slice service area identifiers saved by the UE included in the service area update request with one or more network slice service area identifiers corresponding to the AN. The one or more network slice service area identifiers saved by the UE correspond to network slices in which the service area changes.

(1) If the network slice service area identifier includes the network slice identifier, the CP-MM may have one or more network slice service area identifiers saved by the UE, and have the same one or more network slice service area identifiers corresponding to the AN. The network slice service area identifier of the network slice identifier is compared.

(2) If the network slice identifier is not included in the network slice service area identifier, the CP-MM may directly compare one or more network slice service area identifiers saved by the UE with one or more network slice service area identifiers corresponding to the AN. .

If the CP-MM finds that the one or more network slice service area identifiers corresponding to the AN do not include the network slice service area identifier saved by the UE, the service area of the network slice currently associated with the UE is changed, and step 806 is performed.

In step 806, for each service area identifier changed network slice, the CP-MM may select CP1-SM according to the UE network slice temporary identifier, and forward the service area update request to the selected CP1-SM. Correspondingly, the temporary identifier of the one or more UEs in the network slice is a temporary identifier allocated by the session management function entity to the UE in the network slice where the service area changes; and the session management function entity is before the service area update The functional entity, the control plane session management function entity selected by the mobility management function entity may be the same as or different from the session management function entity.

In the following steps 806 to 809, the network slice NS1 is taken as an example to describe the process of updating the service area of the CP-MM in the network slice whose identity is changed in each service area:

If the network slice service area identifier changes, the CP-MM may determine the CP1-SM according to the UE network slice temporary identifier, and send a service area update request to the determined CP1-SM. The service area update request may carry the UE network slice temporary identifier. It should be noted that when the CP-MM determines the session management function entity, the new session management function entity CP2-SM may also be selected, and the selected session management function entity serves the new service area.

In step 807, if the CP-SM serving the UE changes, that is, the CP-MM selects a CP2-SM different from the CP1-SM that previously served the UE according to the new service area identifier, the new control plane will The call management function entity CP2-SM may acquire the context of the UE from the original control plane session management function entity CP1-SM according to the UE network slice temporary identifier, and/or obtain the subscription information of the UE from the network subscription management entity (for example, the user information repository). To complete the authentication and authentication process for the UE.

Due to the change of the service area, CP1-SM (or CP2-SM, if a new session management function entity is selected) can select a new user plane function entity UP2 for the UE and send a connection/session establishment request to UP2. The UE network slice temporary identifier, the access node identifier, the access node address, and the like may be carried in the connection/session establishment request.

The new user plane function entity UP2 should meet the following conditions:

(1) UP2 belongs to network slice NS1;

(2) UP2 and AN belong to the same service area of network slice NS1.

CP1-SM (or CP2-SM, if a new session management function entity is selected) can also select UP2 according to the pre-configured user plane transmission path reselection/optimization rules. The rule of user plane transport path reselection/optimization may be to prefer a particular user plane functional entity within a particular service area.

In step 808, UP2 sends a connection/session establishment response to CP1-SM (or CP2-SM if a new session management function entity is selected). The connection/session establishment response may carry a UE network slice temporary identifier, a user plane function entity identifier, and a user plane function entity address.

In step 809, CP1-SM (or CP2-SM, if a new session management function entity is selected) sends a service area update response to the CP-MM. The service area update response may carry a UE network slice temporary identifier and a new network slice service area identifier.

In step 810, the CP-MM forwards the service area update response to the AN.

In step 811, the AN forwards the service area update response to the UE.

In step 812, the UE updates the context of the UE at NS1. The UE may include a service parameter, a UE network slice temporary identifier, and a new network slice service area identifier in the context of NS1. The service parameter may be a UE usage type, a service type, and/or an application identifier.

In the embodiment of the present invention, when the UE performs the update of the mobile area, the UE performs the service area update to multiple network slices simultaneously through the mobility management function entity, thereby quickly implementing multiple networks associated with the terminal. Update of the terminal service node (including the control plane function entity CP and the user plane function entity UP) in the slice.

The foregoing describes the solution of the embodiment of the present invention mainly from the perspective of interaction between the network elements. It can be understood that each network element, such as a mobility management function entity, a session management function entity, a terminal, etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiment of the present invention may divide the functional unit of the mobility management function entity, the session management function entity, the terminal, and the like according to the foregoing method example. For example, each functional unit may be divided according to each function, or two or more functions may be used. The functions are integrated in one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

In the case of an integrated unit, FIG. 9a shows a possible structural diagram of the access node involved in the above embodiment. The access node includes a processing unit 902 and a communication unit 903. The processing unit 902 is configured to perform control management on the action of the access node. For example, the processing unit 902 is configured to support the access node to perform processes S202 and S203 in FIG. 2, processes S302 and S310 in FIG. 3, and the process in FIG. S402, S403 and S407, processes S501, S504 and S505 in Fig. 5, processes S602 and S609 in Fig. 6, processes S701, S704, S705 and S707 in Fig. 7, processes S801, S804 and S811 in Fig. 8, And/or other processes for the techniques described herein. The communication unit 903 is configured to support communication between the mobility management function entity and other network entities, such as communication with the session management function entity, the mobility management function entity, the user plane function entity, and the like shown in FIG. Access node can also The storage unit 901 is configured to store program codes and data of the mobility management function entity.

The processing unit 902 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 903 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces. The storage unit 901 can be a memory.

When the processing unit 902 is a processor, the communication unit 903 is a communication interface, and the storage unit 901 is a memory, the mobility management function entity involved in the embodiment of the present invention may be the mobility management function entity shown in FIG. 9b.

Referring to FIG. 9b, the access node 910 includes a processor 912, a communication interface 911, and a memory 913. Alternatively, the access node 910 can also include a bus 914. The processor 912, the communication interface 911, and the memory 913 may be connected to each other through a bus 914. The bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on. The bus 914 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9b, but it does not mean that there is only one bus or one type of bus.

In the case of employing an integrated unit, FIG. 10a shows a possible structural diagram of the mobility management function entity involved in the above embodiment. The mobility management function entity 1000 includes a processing unit 1002 and a communication unit 1003. The processing unit 1002 is configured to control and manage the actions of the mobility management function entity. For example, the processing unit 1002 is configured to support the mobility management function entity to perform processes S306 and S308 in FIG. 3, processes S404 and S406 in FIG. Process S506 in 5, Figure 6 Processes S603, S604, and S608, processes S706 and S707 in FIG. 7, processes S805, S806, and S810 in FIG. 8, and/or other processes for the techniques described herein. The communication unit 1003 is configured to support communication between the mobility management function entity and other network entities, such as communication with the session management function entity, the access node, the user plane function entity, and the like shown in FIG. The mobility management function entity may further include a storage unit 1001 for storing program codes and data of the session management function entity.

The processing unit 1002 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 1003 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces. The storage unit 1001 may be a memory.

When the processing unit 1002 is a processor, the communication unit 1003 is a communication interface, and the storage unit 1001 is a memory, the session management function entity involved in the embodiment of the present invention may be the session management function entity shown in FIG. 10b.

Referring to FIG. 10b, the mobility management function entity 1010 includes a processor 1012, a communication interface 1011, and a memory 1013. Optionally, the mobility management function entity 1010 may further include a bus 1014. The processor 1012, the communication interface 1011, and the memory 1013 may be connected to each other through a bus 1014. The bus 1014 may be a PCI bus or an EISA bus. The bus 1014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 10b, but it does not mean that there is only one bus or one type of bus.

In the case of an integrated unit, FIG. 11a shows a possible structural diagram of the terminal involved in the above embodiment. The terminal includes a processing unit 1102 and a communication unit 1103. The processing unit 1102 is configured to perform control management on the action of the terminal. For example, the processing unit 1102 is configured to support the terminal to perform the process S201 in FIG. 2, the processes S301 and S311 in FIG. 3, and the processes S401 and S408 in FIG. 4, FIG. Processes S502 and S503, processes S601 and S610 in FIG. 6, processes S702 and S703 in FIG. 7, processes S802, S803, and S812 in FIG. 8, and/or other processes for the techniques described herein. The communication unit 1103 is for supporting communication between the terminal and other network entities, such as communication with the access node, mobility management function entity, etc. shown in FIG. The terminal may further include a storage unit 1101 for storing program codes and data of the terminal.

The processing unit 1102 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication unit 1103 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces. The storage unit 1101 may be a memory.

When the processing unit 1102 is a processor, the communication unit 1103 is a transceiver, and the storage unit 1101 is a memory, the terminal involved in the embodiment of the present invention may be the terminal shown in FIG. 11b.

Figure 11b shows a simplified schematic diagram of one possible design structure of a terminal involved in an embodiment of the present invention. The terminal 1110 includes a transmitter 1111, a receiver 1112, and a processor 1113. The processor 1113 may also be a controller, and is represented as "controller/processor 1113" in FIG. 11b. Optionally, the terminal 1110 may further include a modem processor 1115. The modem processor 1115 may include an encoder 1116, a modulator 1117, a decoder 1118, and a demodulator 1119.

In one example, the transmitter 1111 conditions (eg, analog transforms, filters, amplifies, and upconverts, etc.) the output samples and generates an uplink signal that is transmitted via an antenna to the AN described in the above embodiments. . On the downlink, the antenna receives the downlink signal transmitted by the base station in the above embodiment. Receiver 1112 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples. In modem processor 1115, encoder 1118 receives traffic data and signaling messages to be transmitted on the uplink and processes (e.g., formats, codes, and interleaves) the traffic data and signaling messages. Modulator 1118 further processes (eg, symbol mapping and modulation) the number of encoded services According to the signaling message and provide output samples. Demodulator 1119 processes (e.g., demodulates) the input samples and provides symbol estimates. The decoder 1118 processes (e.g., deinterleaves and decodes) the symbol estimate and provides decoded data and signaling messages that are sent to the terminal 1110. Encoder 1116, modulator 1117, demodulator 1119, and decoder 1118 may be implemented by a composite modem processor 1115. These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems). It should be noted that when the terminal 1110 does not include the modem processor 1115, the above functions of the modem processor 1115 may also be completed by the processor 1113.

Further, the terminal 1110 may further include a memory 1114 for storing program codes and data for the terminal 1110.

The steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions. The software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a mobility management functional entity, a session management functional entity, or a terminal. Of course, the processor and the storage medium may also exist as discrete components in a mobility management function entity, a session management function entity, or a terminal.

Those skilled in the art should appreciate that in one or more of the above examples, the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. The computer readable medium includes a computer storage medium and a communication medium, wherein the communication medium includes a computer program that facilitates transfer of the computer program from one location to another. Any medium. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

The specific embodiments of the present invention have been described in detail with reference to the embodiments of the embodiments of the present invention. The scope of the present invention is defined by the scope of the present invention. Any modifications, equivalents, improvements, etc., which are included in the embodiments of the present invention, are included in the scope of the present invention.

Claims (26)

1. A communication method, characterized in that the method comprises:

   The terminal sends a connection/session establishment request message to the access node;

   The terminal determines, according to the network slice context saved by the terminal, whether the terminal is associated with the network slice;

   If the terminal is associated with the network slice, the terminal carries the network slice temporary identifier of the terminal in the connection/session establishment request message, so that the terminal establishes a connection with the network slice;

   The network slice provides a service for the connection/session, and the network slice temporary identifier identifies the terminal in the network slice.
2. The method of claim 1 further comprising:

   If the terminal is not associated with the network slice, the terminal carries the public identifier and the service parameter of the terminal in the connection/session establishment request message.
3. The method of claim 2, wherein the public identity of the terminal comprises an international mobile subscriber identity of the terminal; or

   The network slice signed by the terminal is used to identify the terminal identifier of the terminal; or

   The default network slice subscribed by the terminal is used to identify the terminal identifier of the terminal.
4. The method according to claim 1, wherein the specific form of the network slice temporary identifier of the terminal comprises the network slice identifier and the terminal temporary identifier; or a temporary identifier of the terminal.
5. A communication method, characterized in that the method comprises:

   The access node receives the connection/session establishment request message sent by the terminal, where the connection/session establishment request message carries the network slice temporary identifier of the terminal;

   The access node determines that the network slice context of the terminal corresponding to the network slice temporary identifier of the terminal is saved, and the network slice context of the terminal includes the network slice temporary identifier and the control plane function entity identifier of the terminal;

   The access node selects a control plane functional entity for the terminal according to the network slice context of the terminal;

   The network slice provides service for the connection/session, and the network slice temporary identifier identifies the terminal in the network slice.
6. The method of claim 5, wherein the method further comprises:

   If the access node does not save the terminal network slice context corresponding to the network slice temporary identifier of the terminal, the access node forwards the connection/session establishment request message to the network slice selection function entity, so that the network The slice selection function entity selects a control plane function entity for the terminal, such that the control plane function entity belongs to the network slice, and causes the control plane function entity and the access node to belong to the same service of the network slice Area.
7. A communication method, characterized in that the method comprises:

   The mobility management function entity receives a mobility management area update request message of the terminal from the access node;

   Determining, according to the mobility management area update request message, a mobility management area identifier and/or a mobility management area identifier list for the terminal;

   Determining, according to the mobility management area identifier and/or the mobility management area identifier list, a service area identifier of a network slice associated with the terminal;

   Determining whether the service area identifier of the network slice is included in the terminal network slice context saved by itself;

   If the network slice context of the terminal does not include the service area identifier of the network slice, the mobility management function entity selects a session management function entity for the terminal.

   A mobility management area update response message is sent to the terminal.
8. The method according to claim 7, wherein if the network slice context of the terminal does not include the service area identifier of the network slice, the mobility management function entity selects session management for the terminal Functional entities, including:

   a service according to the terminal network slice temporary identifier and/or the network slice in the network slice context a service area identifier, the session management function entity in the network slice is selected by the terminal, so that the session management function entity selects a user plane function entity for the terminal, where the user plane function entity belongs to the service area identifier a changed network slice, and the user plane function entity and the access node belong to the same service area of the network slice whose service area identifier changes;

   Sending a first message to the session management function entity, where the first message includes a service area update message;

   The terminal network slice temporary identifier is a temporary identifier that is allocated to the terminal by a network slice whose service area changes.
9. A communication method, characterized in that the method comprises:

   Receiving, by the terminal, the access node, to send a first message, where the first message carries a service area list;

   Determining whether a network slice service area identifier in a network slice context saved by the terminal is included in the service area list;

   And if the network slice service area identifier in the network slice context saved by the terminal is not included in the service area list, send a service area update request message to the access node;

   Receiving a network slice service area update response message sent by the access node, so that the terminal updates the network slice context saved by itself.
10. The method according to claim 9, wherein the first message is a broadcast message or a multicast message sent by the access node to the terminal.
11. A communication method, characterized in that the method comprises:

    The mobility management function entity receives a service area update request message of the terminal from the access node, where the service area update request message includes at least one network slice service area identifier;

    Comparing at least one network slice service area identifier of the terminal with whether at least one network slice service area identifier of the access node is the same;

    If the at least one network slice service area identifier of the terminal is different from the at least one network slice service area identifier of the access node, selecting session management function according to the network slice temporary identifier of the terminal Entity

    The network slice temporary identifier of the terminal is a temporary identifier that is allocated by the network slice that is changed in the service area.
12. The method of claim 11 wherein the method further comprises:

    The mobility management function entity sends the network slice service area update request message to the session management function entity, so that the session management function entity selects a user plane function entity for the terminal, and the user plane function entity belongs to the A network slice in which the service area changes, and the user plane function entity and the access node belong to the same service area of the network slice.
13. The method according to claim 11 or 12, wherein the specific form of the network slice service area identifier comprises a network slice identifier and a service area identifier, or a network slice service area identifier.
14. A communication device, wherein the communication device is a terminal, the terminal includes a communication unit and a processing unit;

    The communication unit is configured to send a connection/session establishment request message to the access node;

    The processing unit is configured to determine whether the terminal saves a network slice context, where the network slice context is a context of a network slice serving the connection/session; if the terminal saves the network slice context, Transmitting, by the communication unit, the network slice temporary identifier of the terminal in the connection/session establishment request message, so that the terminal establishes a connection with the network slice; wherein the network slice temporarily identifies the network slice Identify the terminal.
15. The communication device according to claim 14, wherein the processing unit is further configured to: in the connection/session establishment request message, by the communication unit, if the terminal does not save the network slice context Carry the public identification and business parameters of the terminal.
16. The communication device according to claim 15, wherein the communication unit carries a public identifier and a service parameter of the terminal in the connection/session establishment request message;

    The public identifier of the terminal includes an international mobile subscriber identity of the terminal; or the network slice signed by the terminal is used to identify the terminal identifier of the terminal; or the default network slice of the terminal subscription The terminal identifier of the terminal is identified.
17. The communication device according to claim 14, wherein the communication unit carries a network slice temporary identifier of the terminal in the connection/session establishment request message;

    The specific form of the network slice temporary identifier of the terminal includes the network slice identifier and the terminal temporary identifier; or the temporary identifier of the terminal.
18. A communication device, wherein the communication device is an access node, and the access node includes a communication unit and a processing unit;

    The communication unit is configured to receive a connection/session establishment request message sent by the terminal, where the connection/session establishment request message carries a network slice temporary identifier of the terminal;

    The processing unit is configured to determine that the access node saves a network slice context, where the network slice context includes a network slice temporary identifier and a control plane function entity identifier of the terminal, and according to the network slice context, The terminal selects a control plane function entity, so that the terminal establishes a connection with the network slice; wherein the network slice context is a context of a network slice serving the connection/session, and the network slice is temporarily identified The terminal is identified in the network slice.
19. The communication device according to claim 18, wherein the processing unit is further configured to: if the access node does not save the network slice context, forward the connection/session establishment request message by using the communication unit Selecting a functional entity for the network slice to cause the network slice selection function entity to select a control plane functional entity for the terminal, such that the control plane functional entity belongs to the network slice, and the control plane functional entity and the The access node belongs to the same service area of the network slice.
20. A communication device, wherein the communication device is a mobility management function entity, the mobility management function entity includes a communication unit and a processing unit;

    The communication unit is configured to receive, by the access node, a mobility management area update request message of the terminal;

    The processing unit is configured to determine a move for the terminal according to the mobility management area update request message a dynamic management area identifier and/or a mobility management area identifier list; sending, by the communication unit, a mobility management area update response message to the terminal;

    The processing unit is further configured to determine, according to the mobility management area identifier and/or the mobility management area identifier list, a service area identifier of the terminal associated network slice; and determine, where the mobility management function entity saves Determining, in the terminal network slice context, the service area identifier of the network slice; if the network slice context of the terminal does not include the service area identifier of the network slice, the processing unit is the terminal Select the session management function entity.
21. The communication device according to claim 20, wherein the processing unit is configured to select, according to the terminal network slice temporary identifier and/or the service area identifier of the network slice in the network slice context, a session management function entity in the network slice, so that the session management function entity selects a user plane function entity for the terminal, the user plane function entity belongs to a network slice of the service area identifier, and the user plane function The entity and the access node belong to the same service area of the network slice whose service area identifier changes;

    Transmitting, by the communication unit, the first message to the session management function entity by using the communication unit, where the first message includes a service area update message;

    The terminal network slice temporary identifier is a temporary identifier that is allocated to the terminal by a network slice whose service area changes.
22. A communication device, wherein the communication device is a terminal, the terminal includes a communication unit and a processing unit;

    The communication unit is configured to receive, by the access node, a first message, where the first message carries a service area list;

    The processing unit is configured to determine whether a network slice service area identifier in a network slice context saved by the terminal is included in the service area list; if the network slice service area identifier in the network slice context saved by the terminal is not included in the Sending, in the service area list, a service area update request message to the access node by using the communication unit;

    The communication unit is further configured to receive a network slice service area update response message sent by the access node, so that the terminal updates the network slice context saved by itself.
23. The communication device according to claim 22, wherein the communication unit receives a first message sent by the access node, wherein the first message is a broadcast message sent by the access node to the terminal or Multicast message.
24. A communication device, wherein the communication device is a mobility management function entity, the mobility management function entity includes a communication unit and a processing unit;

    The communication unit is configured to receive, by the access node, a service area update request message of the terminal, where the service area update request message includes at least one network slice service area identifier;

    The processing unit is configured to compare, at least one network slice service area identifier of the terminal, with at least one network slice service area identifier of the access node, and at least one network slice service area identifier of the terminal The at least one network slice service area identifier of the access node is different, and the processing unit selects a session management function entity according to the network slice temporary identifier of the terminal, where the network slice temporary identifier of the terminal is, the service A network slice whose area changes is a temporary identifier assigned to the terminal.
25. The communication device according to claim 24, wherein the communication unit is configured to send the network slice service area update request message to the session management function entity, so that the session management function entity is a terminal Selecting a user plane function entity, the user plane function entity belongs to a network slice in which the service area changes, and the user plane function entity and the access node belong to the same service area of the network slice.
26. The communication device according to claim 24 or 25, wherein the communication unit is configured to receive a service area update request message of the terminal from the access node, where the service area update request message includes at least one network slice service area Identification; among them,

    The specific form of the network slice service area identifier includes a network slice identifier and a service area identifier; or a network slice service area identifier.

Images