CN109845360B - A communication method and device - Google Patents

Abstract

A communication method and device, the method includes: a terminal sends a first connection/session establishment request message to an access node; the terminal determines whether the terminal is associated with a network slice according to a network slice context saved by itself; if The terminal has established an association with the network slice, and the terminal carries the network slice temporary identifier of the terminal in the first connection/session establishment request message, so as to facilitate the terminal to establish a connection with the network slice; wherein, the The network slice serves the first connection/session, and the network slice temporary identifier identifies the terminal in the network slice. In the embodiment of the present invention, the terminal saves the network slice context, so that when the terminal initiates a connection/session request to the network, the time for the terminal to access the network slice can be saved.

Description

A communication method and device

technical field

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

Background technique

The rapidly developing mobile communication system needs to meet the service requirements of various scenarios. For example, mobile broadband services for high-definition video, a large number of machine device communications, high-reliability mobile device communications such as vehicle communications, etc.

In the 5G communication system, in order to meet the service requirements of different scenarios, the method of network slicing or network slicing (NS) can be adopted. That is, a network can be composed of multiple network slices, and a specific network slice can be defined as a set of logical network functional entities that support the communication service requirements of a specific scenario. For example, network slicing that supports communication between a large number of machines and devices, and network slicing that supports mobile broadband services. That is, 5G communication requires supporting terminals to access multiple different network slices at the same time, so as to use the services provided by multiple different network slices. For example, a terminal can access a network slice supporting mobile broadband services and a network slice supporting emergency services (Critical Communication, CriC) at the same time.

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

That is, in the 5G communication system, how to select different network slicing solutions for different applications/services of the terminal has not been proposed, and how to update the location area of the terminal for different network slices 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 a terminal, that is, the terminal is associated with different network slices; at the same time, when the location area of the terminal is updated, the terminal can update different network slices The location area of the slice.

A first aspect of the present application provides a communication method, the method includes: a terminal sends a connection/session establishment request message to an access node; the terminal determines whether the terminal has established a network slice with the network slice according to the network slice context saved by itself association; if the terminal establishes an association with the network slice, the terminal carries the network slice temporary identifier of the terminal in the connection/session establishment request message, so as to facilitate the terminal to establish a connection with the network slice; wherein, The network slice serves the connection/session, and the network slice temporary identification identifies the terminal in the network slice.

In this embodiment of the present invention, the terminal can save the network slice context, the network slice context includes a 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 a network slice every time a connection is established The slice selection functional entity selects a network slice for the terminal, reducing the time for the terminal to access the network slice.

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

In a possible implementation manner, the public identity of the terminal includes the International Mobile Subscriber Identity of the terminal; or the network slice subscribed by the terminal is used to identify the terminal identity of the terminal; or the terminal subscribed by the terminal The default network slice is used to identify the terminal identifier 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 the temporary identifier of the terminal.

A second aspect of the present application provides a communication method, the method comprising: 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 The access node determines that it has stored the network slice context of the terminal corresponding to the network slice temporary identifier of the terminal, and the network slice context of the terminal includes the network slice temporary identifier of the terminal and the control plane function entity identifier; the access node The node selects a control plane functional entity for the terminal according to the network slice context of the terminal; wherein the network slice provides services for the connection/session, and the network slice temporary identifier identifies all the network slices in the network slice. described terminal.

In a possible implementation manner, the method further includes: 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 Create a request message to the network slice selection functional entity, so that the network slice selection functional entity selects a control plane functional entity for the terminal, so that the control plane functional entity belongs to the network slice, and the control plane functional entity is made and the access node belongs to the same service area of the network slice.

In a possible design, the terminal receives a first message sent by the access node, where the first message carries a mobility management area identifier or a list of mobility management area identifiers; the terminal determines the mobility management area identifier stored by itself 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 a 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 judges the mobility management area update request message; when the mobility management area update request message is a mobile When the mobility management area update request message is received, 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 node 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; and determining a mobility for the terminal according to the mobility management area update request The mobility management area identifier and/or the mobility management area identifier list; the mobility management functional entity determines the service area of the network slice associated with the terminal according to the mobility management area identifier and/or the mobility management area identifier list identify; determine whether the terminal network slice context saved by itself contains the service area identifier of the network slice; if the network slice context of the terminal does not contain the service area identifier of the network slice, then move The mobility 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 : select the 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 The terminal selects a user plane function entity, the user plane function entity belongs to the network slice of the service area identification, and the user plane function entity and the access node belong to the same network slice of the service area identification change. a service area; send a first message to the session management function entity, where the first message includes a service area update message; wherein, the terminal network slice temporary identifier is, the network slice whose service area has changed is the Temporary ID assigned by the terminal.

A fourth aspect of the present application provides a communication method, the method includes: a terminal receiving a first message sent by an access node, the first message carrying a service area list; judging 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; 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.

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

A fifth aspect of the present application provides a communication method, the method comprising: a mobility management function entity receiving 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; Compare at least one network slice service area identifier of the terminal to see whether it is the same as at least one network slice service area identifier of the access node; if the at least one network slice service area identifier of the terminal is the same as at least one network slice service area identifier of the access node If the service area identifiers of one network slice are different, the first session management function entity is selected according to the network slice temporary identifier of the terminal; wherein, the network slice temporary identifier of the terminal is that the network slice whose service area has changed is the network slice whose service area has changed. Temporary ID assigned by the terminal.

In a possible implementation manner, the method further includes: 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 is The terminal selects a user plane function entity, the user plane function entity belongs to the network slice whose 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, an embodiment of the present invention provides a terminal, which can implement the functions performed by the terminal in the foregoing embodiments, and the functions can be implemented by hardware or by executing corresponding software in hardware. The hardware or software includes one or more modules corresponding to the above functions.

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

In yet another aspect, the present application provides a mobility management functional entity, the mobility management functional entity has a function of implementing the behavior of the mobility management functional entity in the above embodiments. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In a possible design, the mobility management functional entity includes a processor configured to support the mobility management functional entity to perform corresponding functions in the above method. Further, the mobility management function entity may further include a communication interface, where the communication interface is used to support communication between the mobility management function entity and the session management function entity, a terminal or other network elements. Further, the mobility management functional entity may further include a memory, which is coupled to the processor and stores necessary program instructions and data for the mobility management functional entity.

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

In one possible design, the access node includes a processor configured to support the access node to perform the corresponding functions in the above method. 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 include a memory, which is coupled to the processor and stores necessary program instructions and data for the access node.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the above-mentioned mobility management functional entity, including the program designed for executing the above-mentioned aspects.

In 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 the program designed for executing the above aspects.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing the above computer software instructions used in a terminal, which includes a program designed for executing the above aspect.

In another aspect, an embodiment of the present invention provides a computer program product, which includes instructions, when the program is executed by a computer, the instructions cause the computer to perform the functions performed by the mobility management functional entity in the above method design.

In another aspect, an embodiment of the present invention provides a computer program product, which includes instructions, when the program is executed by a computer, the instructions cause the computer to perform the functions performed by the access node in the above method design.

In another aspect, an embodiment of the present invention provides a computer program product, which includes instructions, when the program is executed by a computer, the instructions cause the computer to perform the functions performed by the terminal in the above method design.

The present application uses the network slice 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, the service area update and the mobility management area update are performed.

Description of drawings

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

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

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

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 another communication method provided by an embodiment of the present invention;

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 of still another communication method provided by an embodiment of the present invention;

8 is a schematic flowchart of a method for updating a service area provided by an embodiment of the present invention;

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

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

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

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

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

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

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments.

FIG. 1 is a schematic diagram of a system network in the prior art. As shown in FIG. 1 , a user equipment UE accesses a core network (Core Network, CN) through an access network (Access Network, AN). Specifically, the core network CN may include a network slice selection function (Network Slice Selection Function, NSSF), a subscriber information repository (SubscriberRepository); a control plane mobility management network function (Control Plane Mobility Management Network Function, CP-MM), hereinafter referred to as "mobility management function entity"; control plane session management network 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), hereinafter also referred to as "user plane function entity". 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, UP3. The terminal UE can access multiple different network slices at the same time, 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 network slice. Network slices share CP-MM; multiple network slices may share an access network AN, and the access network AN may be a radio access network (Radio Access Network, RAN), such as the first network slice, the second network slice, and the third network slice. Three network slices share the AN; each network slice has a specific control plane session management function entity and user plane function entity.

3GPP TR 23.799v0.5.0 has introduced the network slice selection functional entity NSSF, user repository, mobility management control plane, session management control plane and session management user plane in the core network CN, and will not be repeated here.

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

The embodiments of the present invention can be applied to a communication system that supports terminal access to network slices. The technology described in the present invention can be applied to the subsequent evolution system using the LTE system, such as the fifth generation 5G system and the like. For the sake of clarity, only the fifth-generation 5G system is used as an example for illustration.

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

FIG. 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 a 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 (Network Slice context, NS context) saved by the UE. If the UE is associated with the network slice, the UE carries the temporary identifier of the UE's network slice 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 temporary identifier identifies the UE in the network slice.

The above-mentioned 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 identity. UE identity. The specific form of the above-mentioned network slice temporary identifier of the UE includes the network slice identifier and the UE temporary identifier; or the temporary identifier of the UE.

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

The AN determines that it has saved the network slice context of the UE corresponding to the network slice temporary identifier of the UE, and the network slice context of the UE includes the network slice temporary identifier and the control plane functional 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 store 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 functional entity NSSF selects a control plane functional entity for the UE, so that the control plane functional entity belongs to the network slice, and makes the control plane functional entity and the access node belong to the same one of the 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; When a session request is made, the temporary identifier of the network slice of the UE is carried, which can directly access the network slice, 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 a control plane functional entity; CP1 may be a CP-SM, which represents a control plane for session management within a specific network slice. UP1 and UP2 are user plane functional entities, which represent the user plane for data transmission within a specific network slice. NSSF stands for Network Slice Selection Functional 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 function entities that support communication service requirements in a specific scenario, and a UE network slice context is the description information of a network slice that provides services for the UE. Both the UE and the AN store the UE network slice context. The UE network slice context in the UE includes the UE usage type, service type, and/or application identity.

When application X in the UE initiates a service request to the network side, the UE checks whether it has the same UE network slice context as the identity of application X, or the UE usage type or service type to which application X belongs. That is, the UE determines whether it has currently established an association with a network slice serving application X, or established an association with a network slice that matches the UE usage type or service type to which application X belongs. The association between the UE and the network slice means that the UE has been 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 a network slice serving application X, or is not associated with a network slice that matches the UE usage type or service type to which application X belongs; Apply the UE network slice context that matches the UE usage type or service type to which X belongs, and execute steps 301 to 311 shown in FIG. 3 .

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 application X needs to send data to the network side, the connection/session establishment request is triggered.

The connection/session establishment request includes UE common id (UE common id), service parameters (ie, "application/service information"), and other parameters required for connection/session establishment. The service parameters may include: UE usage type, and/or service type, and/or application identifier. Here, the UE public identity may be the International Mobile Subscriber Identity IMSI of the UE, or all network slices subscribed by the UE are used to identify the UE identity of the UE, or the default network slice subscribed by the UE is used to identify the UE identity of the UE. The UE public identity can be used to identify the UE, and is shared by one or more network slices subscribed by the UE. UE usage type, which is used to represent the main purpose or usage scenario of the UE, such as: (using the UE as) ordinary instrument or ordinary sensor, vehicle, telemedicine equipment, entertainment equipment, etc.; service type, used to indicate (application X corresponds to) The category of the service, such as: mobile broadband service, machine communication, emergency service; application identifier, used to represent a specific application or application program, such as: application identifier 1 (for example: App-ID=011) is used to identify the WeChat application , the application identifier 2 (for example: App-ID=021) is used to identify the Taobao TMall application.

It should be noted that the UE public identity may be preconfigured 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 is used to identify the UE identity of the UE according to at least one of the UE usage type, service type, and application identity, as well as the UE's International Mobile Subscriber Identity IMSI, all network slices subscribed by the UE, and the default network slice subscribed by the UE. At least one of the UE identities identifying the UE, selects the network slice NS1 for the UE, and simultaneously selects the CP1 for the UE. Here, CP1 may be a mobility management function entity CP1-MM or a session management function entity CP1-SM, which is determined by the architecture of a specific network slice NS1 (for example, whether CP1-MM is included), 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) The CP1 and the AN both belong to the same service area (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 the public identity of the UE, the identity of the AN, and the address of the AN. The address of the AN may be the IP address of the AN.

In step 305, the CP1 initiates an authentication and security request to the UE. In this step, the CP1 and the UE complete the authentication and establish a security mechanism. For example, determine integrity protection and encryption algorithms and related parameters. The CP1 allocates the UE's temporary identity in a specific network slice NS1 (UE NS1 temporary id, also referred to as "terminal network slice temporary identity") to the UE, generates a UE network slice context, and assigns a connection/session identity to a connection/session. Here, CP1 belongs to a specific network slice NS1.

In this embodiment of the present invention, the UE network slice context may include: a temporary identifier of the UE in a specific network slice NS1, service parameters, network slice service area identifiers, network slice connection/session identifiers, and security parameters.

The specific forms of the temporary identity 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 identity ranges. For example, the most significant first four bits of the UE temporary identifier of the specific network slice NS1 are 0001, and the most significant 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 temporary identity of the UE in NS1 may also include other parts. For example, the CP1 identifier in the network slice NS1 will not be repeated here.

In step 306, the control plane functional 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 to transmit data, and the data may include the connection between the UE and the network entity or the opposite terminal. The business data transmitted between them can include voice, video, text and other types. The control plane functional entity CP1 sends a connection/session establishment request to UP1. The connection/session establishment request includes the UE network slice temporary identity, the identity of the AN, and the 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 a specific network slice NS1.

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

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

Here, the specific form of the network slicing service area identification can be as follows.

(1) Form 1: Network Slice ID + Service Area ID;

(2) Form 2: The network slice service area identifier only includes 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 highest-order first four bits of the service area identifier of the first network slice NS1 are 0001, and the highest-order first four bits of the service area identifier of the second network slice NS2 are 0002, thus 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 the control plane functional entity identifier (NS CP1 id) in the network slice, which will not be repeated here. The service area identifier may be configured in CP1, UP1 and/or AN in the corresponding network slice.

Optionally, if the UE's network slice temporary identifier and/or network slice service area identifier does not contain the network slice identifier, the connection/session establishment response in this step may also carry the network slice identifier.

In step 309, the NSSF forwards the connection/session setup 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 the UE network slice temporary identifier, the network slice service area identifier, and the network slice connection/session identifier.

A specific AN1 may hold the context of the UE in the network slice NS1 (UE NS1 context, which may also be referred to as "UE network slice context"). The context of the UE in the network slice NS1 stored in AN1 may include the following contents: UE network slice temporary identifier, network slice service area identifier, control plane functional entity identifier, control plane functional entity address, network slice connection/session identifier, user plane identifier Functional entity identifier and 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 contents: service parameters, UE network slice temporary identifier, network slice service area identifier, security keys, and network slice connection/session identifier. The above-mentioned service parameters may include: user usage type, service type, and/or application identifier.

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

If the UE has established an association with a network slice that provides services for application X, or has established an association with a network slice that matches the UE usage type or service type to which application X belongs, in other words, if the UE saves a network slice associated with application X, Or apply the UE network slice context matching the UE usage type or service type to which X belongs, then execute steps 401 to 408 shown in FIG. 4 .

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 to the UE by the control plane functional entity CP in the network slice, and is used to identify the UE in the network slice.

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

In step 402, the AN queries the UE network slice context stored in the AN according to the temporary identifier of the UE in the network slice, thereby determining 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 up and down the UE network slice saved in the UE. For example, the same parameters are the temporary identifier of the UE in the network slice, the network slice service area identifier, and the network slice connection/session identifier; the difference is that the parameters stored in the AN include the identifier of the control plane functional entity and its address, and the identifier of the user plane functional entity. and its address; the parameters stored in the UE include security keys and service parameters. The network slice context stored in the UE is the network slice that indicates the service provided for the UE, and the control plane functional entity stored in the AN that provides the service for the UE is queried through the shared temporary identifier of the UE network slice.

If the UE network slice context is not stored in the AN, or there is no UE network slice context corresponding to the UE network slice temporary identifier in the UE network slice context stored in the AN, the AN sends the connection/session establishment request to the NSSF, and then executes Figure 3 Similar steps 303 to 311 in .

At this time, when similar steps 303 to 311 in FIG. 3 are executed, the differences from FIG. 3 are:

(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 can select 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 the purpose of load balancing, the NSSF can reselect the control plane functional entity, for example, select the control plane functional entity CP2 other than the control plane functional 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 the connection/session establishment request to the CP1, the CP1 sends the connection/session establishment request to the UP1 in the 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 stored 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 stored in the AN. Since the UE network slice context saved in the AN includes the network slice NS1 identifier corresponding to the UE network slice temporary identifier, as well as the core network control plane functional entity identifier and its address, the AN can be based on the UE network slice temporary identifier and/or the AN's In the UE network slice context, the network slice NS1 corresponding to the connection/session establishment request is determined, and the CP1 of the core network in the UE network slice context stored in the AN is selected, and the following steps are performed.

In step 403, the AN sends a connection/session establishment request to the 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 can also select a new user plane functional entity UP2 for the UE, and send a connection/session establishment request to UP2. The connection/session establishment request may carry the temporary identity of the UE in the network slice NS1, the identity of the access node, and the address of the access node.

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 a specific network slice NS1; and

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

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

In step 405, UP2 sends a connection/session establishment response to CP1. The connection/session establishment response may carry the temporary identity of the UE in the network slice NS1, the identity of the user plane function entity (UP2id), and the address of the user plane function entity. The user plane functional entity address may be the IP address of the user plane functional 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 functional entity identifier, the control plane functional entity address, User plane functional entity identifier and user plane functional entity address. Wherein, if the service area identifier of the UE in the specific network slice NS1 does not change, it is the original service area identifier. When the UE changes in the network slice, the service area identifier in the specific network slice NS1 is the new service area identifier. District ID.

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

The AN may also update the context at NSl for the UEs in the AN. The context of the UE in NS1 stored in the AN may include the following contents: the temporary identity of the UE in the network slice NS1, the service area identity of the network slice NS1, the new connection/session identity of the network slice NS1, and the identity of the control plane functional entity , control plane functional entity address, new user plane functional entity identifier, and new user plane functional entity address. Wherein, 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 network slice NS1 among the UEs.

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

After the UE moves, the mobility management area of the UE may change. 5 and 6 are used as examples for description below. In FIG. 5 and FIG. 6 , MM represents the mobility management functional entity, CP-MM represents the mobility management functional entity, CP1-SM represents the session management functional entity, and UP2 represents the user plane functional entity. FIG. 5 is a schematic flowchart of another communication method provided by 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 list of mobility management area identifiers.

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

S502, the UE determines that the mobility management area has changed.

In this step, the UE determines that the mobility management area identifier or the mobility management area identifier list stored by itself does not contain 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 change.

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 judges 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 an example, when the mobility management area update request message is a session management request message, the access node forwards the mobility management area 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 list of mobility management area identifiers for the UE according to the mobility management area update request message. The mobility management area identifier and/or the mobility management area identifier list is a new mobility management area identifier of the UE, and/or a new mobility management area identifier list.

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

In an example, the MM may further determine the 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 stored by itself. Whether the service area identifier of the network slice is included in the context. If the network slice context of the terminal does not include the service area identifier of the network slice, the MM selects a session management function entity for the UE.

In an example, the MM selecting a session management function entity for the UE includes: the MM selects a session management function entity for the UE according to 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 the network slice identified by the service area, and the user plane function entity 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, where the first message includes a service area update message.

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

Specifically, FIG. 6 is a schematic flowchart 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 sends 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, so that the connection state between the terminal and the network is optimal, thereby providing guarantee for the application of various network services. A network slice includes one or more mobility management areas.

When the UE moves, the mobility management area serving the UE changes, and the UE cannot receive messages through the previous mobility management area, so the UE needs to update the mobility management area. When determining that the mobility management area has changed, 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, and mobility management area identifiers saved by the terminal or previously accessed. The network slice identifier is used to identify the network slice, and the UE network slice temporary identifier 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 the temporary identifiers allocated to the UE by different network slices associated with the UE.

It should be noted that there may be various conditions for triggering the mobility management area update request. For example, the UE receives broadcast/multicast messages 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 mobility management area identifier list in the broadcast/multicast message with the mobility management area identifier or mobility management area identifier list currently saved by the UE, and determines the mobility management area identifier or mobility management area identifier list. Whether the list of sex management area identifiers has changed. If the UE finds that the mobility management area identifier or the mobility management area identifier list has changed, the UE sends a mobility management area update request to the AN. The UE may also judge whether the mobility management area has changed in other ways, which will not be repeated here.

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

In step 602, the AN sends the mobility management area update request to the mobility management function entity CP-MM shared by the network slices.

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

If the mobility management area update request is a mobility management request message, the AN sends the mobility management request message to the mobility management function entity CP-MM shared by multiple network slices. If the mobility management area update request is a session management SM request message, the AN sends the session management request message to the control plane functional entity CP-SM of the specific network slice corresponding to the network slice temporary identifier of 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.

CP-MM can base on preconfigured mobility management area identifier (or mobility management area identifier list) information, such as: preconfigured "AN and mobility management area identifier (or mobility management area identifier list) mapping" table , the new mobility management area identifier or the new mobility management area identifier list of the UE is determined by the identifier or address of the AN that forwards the mobility management area update request. Alternatively, in step 602, the AN sends the new mobility management area identifier (or the mobility management area identifier list) together with the mobility management area update request to the CP-MM, and the CP-MM sends the new mobility management area identifier according to the new mobility provided by the AN. A management area identifier (or a list of mobility management area identifiers), to determine a new mobility management area identifier or a new mobility management area identifier list of the UE. An AN can serve one or more mobility management areas, so the AN has a corresponding mobility management area identifier (or a list of mobility management area identifiers).

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

The CP-MM determines the service area identity of the network slice with 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 identifiers) to the network slice service area identifier of the network slice associated with the UE.

A 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 has changed.

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 one or more service area identifiers associated with the UE. Whether the service area of each network slice has changed. If the CP-MM finds that the service area identifiers of one or more network slices associated with the UE have changed, 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 can be maintained by the CP-MM, and the mapping table can be pre-configured in the mobility management In the functional entity CP-MM. A terminal can move within a specific (same time and same place) mobility management area.

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 moves from MM Area(list)1 (identified by MM Area(list)ID1) to MM Area(list)2 (identified by MM Area(list)ID2), according to the above mapping table, the UE is in the Network Slice The corresponding ServiceArea (identified by Service Area ID1) in 1 has not changed, while the corresponding Service Area in Network Slice 2 and Network Slice 3 has changed, that is, changed from Service Area 1 of Network Slice 2 to Service Area2; by Service Area 1 of Network Slice 3 is changed to Service Area 3 (respectively identified by Service Area IDs 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 identifiers of one or more network slices associated with the UE have changed, then for each network slice whose service area identifiers have changed, the mobility management function entity CP-MM based on the UE 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, where the message includes a service area update request (Service area update request). ) message or session management message. Session management messages include session establishment messages, session release messages, and session modification messages.

The following steps 604 to 607 take a specific network slice NS1 as an example to illustrate the process of performing service area update by the mobility management functional entity CP-MM in each network slice whose service area identifier 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 CP1-SM. Since a session management function entity is configured with the service area identifiers of one or more network slices, multiple session management function entities may be configured with the service area identifiers of the same network slice, so the CP-MM can determine the CP1-SM according to the service area identifiers. . The session message includes a service area update request and/or a session management message. Session management messages include session establishment messages, session release messages, and session modification messages. The service area update request or session establishment request may carry the UE network slice temporary identifier. The determined session management control plane functional entity may also be the new session management control plane functional entity CP2-SM in the above-mentioned specific network slice NS1.

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

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

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 may also select a new user plane functional entity UP2 according to the preconfigured user plane transmission path reselection/optimization rule. The rule for reselection/optimization of the user plane transmission path may be to prefer a specific user plane functional 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 the UE network slice temporary identifier, the user plane functional entity identifier, and the user plane functional entity address.

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

In step 608, the CP-MM sends a mobility management area update response to the AN. The mobility management area update response may carry a new mobility management service area identifier or a new mobility management service area identifier list, and a UE network slice temporary identifier. If the UE updates the service area to its 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 area update response to the UE.

In step 610, the UE updates the mobility management area identifier or the mobility management area identifier list, and updates the UE network slice context. The UE network slice context includes parameters such as service parameters, 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 identifier.

In this embodiment of the present invention, when the UE updates the mobile area, the network (for example, a mobility management functional entity) updates the service area to multiple network slices associated with the terminal according to the change of the mobile area, so as to quickly realize the update of the mobile area associated with the terminal. The update of terminal service nodes in multiple network slices, for example, the update of the UE-related control plane functional entity CP, or the update of the user plane functional entity UP.

It can be seen from the above that, when the UE moves, the service area of the UE may also change. Taking FIG. 7 and FIG. 8 as an example, description will be given of updating the service area after the UE directly perceives the change of the service area. In FIGS. 7 and 8 , UE represents the terminal, AN represents the access node, MM or CP-MM represents the mobility management functional entity, CP1-SM represents the session management functional entity, and UP represents the user plane functional entity. FIG. 7 is a schematic flowchart of still another communication method provided by 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 the service area transmission change.

In the modification step, the UE determines whether the network slice service area identifier in the network slice context saved by the UE 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, a first service area update request message is sent 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 the 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 has changed, and selects a session management function entity.

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

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

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 A network slice whose service area changes, and the user plane functional 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.

Taking FIG. 8 as an example below, the service area update of the network slice of the terminal will be described in detail. 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 service area of the network slice, 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 of 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 there are two forms of service area identifiers for network slices, and when comparing the two service area identifiers, the two forms are described separately.

(1) If the network slice service area identifier includes the network slice identifier, the UE can compare the UE network slice context and the service area list with the same network slice identifier, so as to compare whether the service area identifiers are the same.

(2) If the network slice service area identifier does not include the network slice 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 contain at least one network slice service area identifier of the UE network slice context saved by the UE itself, it is considered that the service area of the network slice currently associated with the UE has changed.

In step 803, if the service area of the network slice NS to which the UE is currently associated 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. Wherein, the one or more stored network slice service area identifiers correspond to network slices whose service areas have changed. Correspondingly, the temporary identifiers of the one or more UEs in the network slice correspond to the temporary identifiers allocated to the UE by the network slice whose service area has changed. 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 the network slice whose service area currently associated with the UE has changed.

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 multiple 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 functional 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 changes. Optionally, the CP-MM may also determine whether the service area of the network slice to which the UE is currently associated changes.

Specifically, the CP-MM compares one or more network slice service area identifiers stored by the UE in the service area update request with one or more network slice service area identifiers corresponding to the AN. Wherein, one or more network slice service area identifiers stored by the UE correspond to network slices whose service areas have changed.

(1) If the network slice service area identifier includes the network slice identifier, the CP-MM may store one or more network slice service area identifiers saved by the UE with the same one or more network slice service area identifiers as the one or more network slice service area identifiers corresponding to the AN. Compare the network slice service area identifier with the network slice identifier.

(2) If the network slice service area identifier does not contain the network slice identifier, the CP-MM can 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 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, it considers that the service area of the network slice currently associated with the UE has changed, and executes step 806 .

In step 806, for each network slice whose service area identifier changes, the CP-MM may select a 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 identifiers of the one or more UEs in the network slice are the temporary identifiers allocated by the session management function entity to the UE in the network slice where the service area has changed; and the session management function entity is the one before the service area update. The functional entity, the control plane session management functional entity selected by the mobility management functional entity may be the same as or different from the session management functional entity.

The following steps 806 to 809 take the network slice NS1 as an example to illustrate the process of updating the service area of CP-MM in the network slice where the service area identifier changes:

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, it may also select a new session management function entity CP2-SM, and the selected session management function entity serves a new service area.

In step 807, if the CP-SM serving the UE changes, that is, the CP-MM selects a CP2-SM that is different from the CP1-SM previously serving the UE according to the new service area identifier, the new control plane session management The functional entity CP2-SM may obtain the context of the UE from the original control plane session management functional entity CP1-SM according to the UE network slice temporary identity, and/or obtain the subscription information of the UE from the network subscription management entity (such as the user information repository), so as to Complete the authentication and authentication process for the UE.

As the service area changes, 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 connection/session establishment request may carry parameters such as the temporary identifier of the UE network slice, the identifier of the access node, and the address of the access node.

The new user plane functional entity UP2 shall meet the following conditions:

(1) UP2 belongs to the network slice NS1;

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

The CP1-SM (or CP2-SM, if a new session management functional entity is selected) can also select UP2 according to the preconfigured rules for reselection/optimization of the transmission path of the user plane. The rule of user plane transmission path reselection/optimization may be to prefer a specific user plane functional entity in a specific 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 the UE network slice temporary identifier, the user plane functional entity identifier, and the user plane functional 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 CP-MM. The service area update response may carry the UE network slice temporary identifier and the 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 in NS1. The context of the UE in NS1 may include service parameters, the UE network slice temporary identifier, and the new network slice service area identifier. The service parameter may be UE usage type, service type, and/or application identifier.

In the embodiment of the present invention, when the UE updates the mobile area, the UE simultaneously updates the service area to multiple network slices through the mobility management functional entity, so as to quickly realize the terminal service node (including the terminal service node in the multiple network slices associated with the terminal) Update of the control plane functional entity CP and the user plane functional entity UP).

The foregoing mainly introduces the solutions of the embodiments of the present invention from the perspective of interaction between various network elements. It can be understood that each network element, such as a mobility management functional entity, a session management functional entity, a terminal, etc., includes hardware structures and/or software modules corresponding to executing each function in order to implement the above-mentioned functions. Those skilled in the art should easily realize that the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

In this embodiment of the present invention, functional units such as mobility management functional entities, session management functional entities, and terminals may be divided according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functional units may be divided into Functions are integrated in one processing unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that, the division of units in the embodiment of the present invention is schematic, and is only a logical function division, and there may be other division manners in actual implementation.

In the case of using an integrated unit, FIG. 9a shows a possible schematic 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 used to control and manage the actions of the access node. For example, the processing unit 902 is used to support the access node to perform the processes S202 and S203 in FIG. 2 , the processes S302 and S310 in FIG. 3 , and the processes in FIG. 4 . S402, S403 and S407, the processes S501, S504 and S505 in FIG. 5, the processes S602 and S609 in FIG. 6, the processes S701, S704, S705 and S707 in FIG. 7, the processes S801, S804 and S811 in FIG. 8, and/or other processes for the techniques described herein. The communication unit 903 is used to support the communication between the mobility management function entity and other network entities, for example, the communication with the session management function entity, the mobility management function entity, the user plane function entity and the like shown in FIG. 1 . The access node may further include a storage unit 901 for storing program codes and data of the mobility management functional entity.

The processing unit 902 may be a processor or a controller, such as a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit) Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication unit 903 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a general term and may include one or more interfaces. The storage unit 901 may 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 functional entity involved in the embodiment of the present invention may be the mobility management functional 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 . Optionally, the access node 910 may further include a bus 914 . The processor 912, the communication interface 911, and the memory 913 can be connected to each other through a bus 914; the bus 914 can be a Peripheral Component Interconnect (PCI for short) bus or an Extended Industry Standard Architecture (EISA for short) bus etc. 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 FIG. 9b, but it does not mean that there is only one bus or one type of bus.

In the case of using an integrated unit, FIG. 10a shows a possible schematic structural diagram of the mobility management functional entity involved in the above embodiment. The mobility management functional 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 functional entity. For example, the processing unit 1002 is configured to support the mobility management functional entity to perform the processes S306 and S308 in FIG. 3 , and the processes S404 and S406 in FIG. 4 . Process S506 in FIG. 5, Processes S603, S604 and S608 in FIG. 6, 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 used to support the communication between the mobility management function entity and other network entities, for example, the communication with the session management function entity, the access node, the user plane function entity and the like shown in FIG. 1 . 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, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, 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 general term 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 functional entity involved in the embodiment of the present invention may be the session management functional entity shown in FIG. 10b.

Referring to FIG. 10b , the mobility management functional entity 1010 includes: a processor 1012 , a communication interface 1011 , and a memory 1013 . Optionally, the mobility management functional 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, an EISA bus, or the like. The bus 1014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is shown in FIG. 10b, but it does not mean that there is only one bus or one type of bus.

In the case of using an integrated unit, FIG. 11a shows a possible schematic 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 used to control and manage the actions of the terminal. For example, the processing unit 1102 is used to support the terminal to perform the process S201 in FIG. 2 , the processes S301 and S311 in FIG. 3 , the processes S401 and S408 in FIG. 4 , and the process in FIG. 5 Processes S502 and S503 in FIG. 6 , 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 used to support the communication between the terminal and other network entities, for example, the communication with the access node, the mobility management function entity and the like shown in FIG. 1 . The terminal may further include a storage unit 1101 for storing program codes and data of the terminal.

The processing unit 1102 may be a processor or a controller, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication unit 1103 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a general term and may 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 this embodiment of the present invention may be the terminal shown in FIG. 11b .

FIG. 11b shows a simplified schematic diagram of a possible design structure of the terminal involved in the 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, which is represented as "controller/processor 1113" in FIG. 11b. Optionally, the terminal 1110 may further include a modem processor 1115 , where the modem processor 1115 may include an encoder 1116 , a modulator 1117 , a decoder 1118 and a demodulator 1119 .

In one example, transmitter 1111 conditions (eg, analog converts, 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. The receiver 1112 conditions (eg, filters, amplifies, downconverts, and digitizes, etc.) the signal received from the antenna and provides input samples. In modem processor 1115, encoder 1118 receives and processes (eg, formats, encodes, and interleaves) the traffic data and signaling messages to be sent on the uplink. Modulator 1118 further processes (eg, symbol mapping and modulation) the encoded traffic data and signaling messages and provides output samples. A demodulator 1119 processes (eg, demodulates) the input samples and provides symbol estimates. Decoder 1118 processes (eg, deinterleaves and decodes) the symbol estimates and provides decoded data and signaling messages for transmission to terminal 1110 . The encoder 1116 , modulator 1117 , demodulator 1119 and decoder 1118 may be implemented by a composite modem processor 1115 . These elements are processed according to the radio access technology employed by the radio access network (eg, access technology of LTE and other evolved systems). It should be noted that, when the terminal 1110 does not include the modulation and demodulation processor 1115, the above-mentioned functions of the modulation and demodulation processor 1115 may also be performed 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 conjunction with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions. Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (Random Access Memory, RAM), flash memory, read only memory (Read Only Memory, ROM), erasable programmable read only memory ( Erasable Programmable ROM, EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), registers, hard disks, removable hard disks, compact disks (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, such that the processor can 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 storage medium may reside in an ASIC. Additionally, the ASIC may be located in a mobility management function entity, a session management function entity or a terminal. Of course, the processor and the storage medium may also exist in the mobility management functional entity, the session management functional entity or the terminal as discrete components.

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

The specific embodiments described above further describe in detail the purposes, technical solutions and beneficial effects of the embodiments of the present invention. It should be understood that the above descriptions are only specific implementations of the embodiments of the present invention, and are not intended to be used for The protection scope of the embodiments of the present invention is limited, and any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the embodiments of the present invention shall be included within the protection scope of the embodiments of the present invention.

Claims (14)

1. A method of communication, the method comprising:

a mobility management functional entity receives a mobility management area update request message of a terminal from an access node;

determining a mobile management area identifier and/or a mobile management area identifier list for the terminal according to the mobile management area updating request message;

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

judging whether the self-stored context of the terminal network slice contains the service area identification of the network slice;

if the network slice context of the terminal does not contain the service area identification of the network slice, the mobility management functional entity selects a session management functional entity for the terminal;

and sending a mobility management area update response message to the terminal.

2. The method of claim 1, wherein if the service area identifier of the network slice is not included in a network slice context of the terminal, 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, so that the session management function entity selects a user plane function entity for the terminal, the user plane function entity belongs to the network slice with the changed service area identifier, and the user plane function entity and the access node belong to the same service area of the network slice with the changed service area identifier;

sending a first message to the session management function entity, wherein the first message comprises a service area update message;

the terminal network slice temporary identifier is a temporary identifier allocated to the terminal by the network slice with the changed service area.

3. A method of communication, the method comprising:

a terminal receives a first message sent by an access node, wherein the first message carries a service area list;

judging whether the network slice service area identification in the network slice context stored by the terminal is contained in the service area list or not;

if the network slice service area identification in the network slice context stored by the terminal is not included in the service area list, sending a service area update request message to the access node;

and receiving a network slice service area updating response message sent by the access node so that the terminal updates the network slice context stored by the terminal.

4. The method of claim 3, wherein the first message is a broadcast message or a multicast message sent by the access node to the terminal.

5. A method of communication, the method comprising:

a mobility management function entity receives a service area updating request message of a terminal from an access node, wherein the service area updating request message comprises at least one network slice service area identifier;

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

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 a session management function entity according to the network slice temporary identifier of the terminal;

the network slice temporary identifier of the terminal is a temporary identifier allocated to the terminal by the network slice with the changed service area.

6. The method of claim 5, further comprising:

and the mobility management functional entity sends the network slice service area updating request message to the session management functional entity so that the session management functional entity selects a user plane functional entity for the terminal, the user plane functional entity belongs to the network slice with the changed service area, and the user plane functional entity and the access node belong to the same service area of the network slice.

7. The method according to claim 5 or 6, 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.

8. A communication device is characterized in that the communication device is a mobility management function entity, and the mobility management function entity comprises a communication unit and a processing unit; wherein,

the communication unit is used for receiving a mobile management area update request message of the terminal from the access node;

the processing unit is used for determining a mobility management area identifier and/or a mobility management area identifier list for the terminal according to the mobility management area update request message; sending a mobility management area update response message to the terminal through the communication unit;

the processing unit is further configured to determine a service area identifier of the terminal-associated network slice according to the mobility management area identifier and/or the mobility management area identifier list; judging whether the context of the terminal network slice stored by the mobility management functional entity contains the service area identifier of the network slice; if the network slice context of the terminal does not contain the service area identifier of the network slice, the processing unit selects a session management function entity for the terminal.

9. The communication device according to claim 8, wherein the processing unit is configured to select a session management function entity in the network slice for the terminal according to a terminal network slice temporary identifier in the network slice context and/or a service area identifier of 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 the network slice with the service area identifier, and the user plane function entity and the access node belong to a same service area of the network slice with the changed service area identifier;

the processing unit sends a first message to the session management function entity through the communication unit, wherein the first message comprises a service area update message;

the terminal network slice temporary identifier is a temporary identifier allocated to the terminal by the network slice with the changed service area.

10. A communication device is characterized in that the communication device is a terminal, and the terminal comprises a communication unit and a processing unit; wherein,

the communication unit is used for receiving a first message sent by an access node, wherein 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 stored by the terminal is included in the service area list; if the network slice service area identification in the network slice context stored by the terminal is not included in the service area list, sending a service area update request message to the access node through 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 a network slice context stored by the terminal.

11. The apparatus according to claim 10, wherein the communication unit receives a first message sent by an access node, wherein the first message is a broadcast message or a multicast message sent by the access node to the terminal.

12. A communication device is characterized in that the communication device is a mobility management function entity, and the mobility management function entity comprises a communication unit and a processing unit; wherein,

the communication unit is used for receiving a service area updating request message of a terminal from an access node, wherein the service area updating request message comprises at least one network slice service area identifier;

the processing unit is configured to compare whether at least one network slice service area identifier of the terminal is the same as at least one network slice service area identifier of the access node; 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, the processing unit selects a session management function entity according to the network slice temporary identifier of the terminal; the network slice temporary identifier of the terminal is a temporary identifier allocated to the terminal by the network slice with the changed service area.

13. The communications device according to claim 12, wherein the communications 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 selects a user plane function entity for a terminal, the user plane function entity belongs to a network slice of 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.

14. The communication device according to claim 11 or 12, wherein the communication unit is configured to receive a service area update request message of a terminal from an access node, wherein the service area update request message comprises at least one network slice service area identifier; wherein,

the specific form of the network slice service area identification comprises a network slice identification and a service area identification; or a network slice service area identification.

Images