CN109845360B

CN109845360B - Communication method and device

Info

Publication number: CN109845360B
Application number: CN201780063516.2A
Authority: CN
Inventors: 段小嫣; 金辉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-01-03
Filing date: 2017-01-03
Publication date: 2020-10-16
Anticipated expiration: 2037-01-03
Also published as: WO2018126342A1; CN109845360A

Abstract

A communication method and device, the method comprising: the terminal sends a first connection/session establishment request message to the access node; the terminal judges whether the terminal establishes association with the network slice according to the network slice context stored by the terminal; if the terminal establishes association with the network slice, the terminal carries a network slice temporary identifier of the terminal in the first connection/session establishment request message so as to facilitate the establishment of connection between the terminal and the network slice; wherein the network slice serves the first connection/session and the network slice temporary identification identifies the terminal in the network slice. The embodiment of the invention saves the context of the network slice through the terminal, thereby saving the time for accessing the terminal into the network slice when the terminal initiates a connection/session request to the network.

Description

Communication method and device

Technical Field

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

Background

A rapidly developing mobile communication system needs to satisfy service demands of various scenes. For example, mobile broadband services of high definition video, mass machine device communication, highly reliable mobile device communication such as vehicle communication, and the like.

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

In an Evolved Packet System (EPS), when a terminal moves from one Tracking Area (TA) to another, location registration must be performed again on the new Tracking Area to notify the network to change its stored location information of the terminal, which is Tracking Area Update (TAU). However, in a 5G communication system, different network slices are used to serve different traffic needs of the terminal, and the different network slices may need to be updated with tracking areas.

That is, in the 5G communication system, how to select different network slice schemes for different applications/services of the terminal has not been proposed yet, and how to perform location area update for different network slices by the terminal also becomes a problem to be solved urgently.

Disclosure of Invention

The application provides a communication method and equipment, wherein the method can select different network slices for different applications/services of a terminal, namely the terminal establishes association with the different network slices; and meanwhile, when the position area of the terminal is updated, the terminal can update the position areas of different network slices.

A first aspect of the present application provides a communication method, including: the terminal sends a connection/session establishment request message to the access node; the terminal judges whether the terminal establishes association with the network slice according to the network slice context stored by the terminal; if the terminal establishes association with the network slice, the terminal carries a network slice temporary identifier of the terminal in the connection/session establishment request message so as to facilitate the establishment of connection between the terminal and the network slice; wherein the network slice serves the connection/session, and the network slice temporary identifier identifies the terminal in the network slice.

In the embodiment of the invention, the terminal can store the network slice context, the network slice context comprises the network slice temporary identifier, and the terminal can establish connection with the network slice according to the network slice temporary identifier; namely, the terminal does not need to establish connection each time, the network slice selection functional entity is carried out to select the network slice for the terminal, and the time for the terminal to access the network slice is reduced.

In one possible embodiment, the method further comprises: and if the terminal is not associated with the network slice, carrying the public identification and the service parameters of the terminal in the connection/session establishment request message by the terminal.

In a possible embodiment, the public identity of the terminal comprises an international mobile subscriber identity of the terminal; or the network slice signed by the terminal is used for identifying the terminal identification of the terminal; or the default network slice signed by the terminal is used for identifying the terminal identification 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 method of communication, the method comprising: an access node receives a connection/session establishment request message sent by a terminal, wherein the connection/session establishment request message carries a network slice temporary identifier of the terminal; the access node determines that a network slice context of the terminal corresponding to the network slice temporary identifier of the terminal is stored by the access node, wherein the network slice context of the terminal comprises the network slice temporary identifier of the terminal and a control plane function entity identifier; the access node selects a control plane function entity for the terminal according to the network slice context of the terminal; wherein the network slice serves the connection/session, and the network slice temporary identifier identifies the terminal in the network slice.

In one possible embodiment, the method further comprises: if the access node does not store the terminal network slice context corresponding to the network slice temporary identifier of the terminal, the access node forwards the connection/session establishment request message to a network slice selection functional entity so that the network slice selection functional entity selects a control plane functional entity for the terminal, the control plane functional entity belongs to the network slice, and the control plane functional entity and the access node belong to the same service area of the network slice.

In one possible design, a terminal receives a first message sent by an access node, wherein the first message carries a mobility management area identifier or a mobility management area identifier list; the terminal determines that a mobility management area identifier or a mobility management area identifier list stored by the terminal does not contain the mobility management area identifier or the mobility management area identifier list in the first message; and the terminal sends a mobility management area update request message to the access node.

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

In one possible design, an access node receives a mobility management area update request message sent by a terminal; the access node judges the mobility management area updating request message; when the mobile management area updating request message is a mobile management request message, the access node forwards the mobile management area updating request message to a mobile management functional entity; when the mobile management area updating request message is a session management request message, the access node forwards the mobile management area updating request message to a session management functional entity.

A third aspect of the present application provides a communication method, 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 mobility management area identifier and/or a mobility management area identifier list for the terminal according to the mobility management area updating request; the mobility management functional entity determines the service area identification of the terminal associated network slice according to the mobility management area identification and/or the mobility management area identification 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.

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 selecting, by the mobility management function entity, a session management function entity for the terminal includes: 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 of the 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.

A fourth aspect of the present application provides a communication method, including: 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.

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 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 identification of the terminal is different from the at least one network slice service area identification of the access node, selecting a first session management functional entity according to the network slice temporary identification 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.

In one possible embodiment, the method further comprises: 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.

In a possible implementation, 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, where the terminal may implement the functions executed by the terminal in the foregoing embodiments, and the functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions.

In one possible design, the terminal includes a processor and a transceiver in its structure, and the processor is configured to support the terminal to perform the corresponding functions in the method. The transceiver is used to support communication between the terminal and a mobility management function entity, access node or other network element. The terminal may also include a memory, coupled to the processor, that retains program instructions and data necessary for the terminal.

In another aspect, the present application provides a mobility management function entity, where the mobility management function entity has a function of implementing a behavior of the mobility management function entity in the foregoing embodiment. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

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

In another aspect, an embodiment of the present invention provides an access node, where the access node has a function of implementing an access node behavior in the foregoing embodiment. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described 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-described 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 also include a memory for coupling with the processor that retains program instructions and data necessary for the access node.

In another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the mobility management functional entity, which includes a program designed to execute the above aspects.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for an access node as described above, which includes a program designed to perform the above aspects.

In another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for a terminal, which includes a program designed to execute the above aspects.

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

In yet another aspect, the present invention provides a computer program product comprising instructions for causing a computer to perform the functions performed by the access node in the above method design when the program is executed by the computer.

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

According to the method and the device, the network slice context stored by the terminal is used, namely the terminal can store the network slice establishing the association, so that the time for accessing the terminal into the network slice is saved; and when the terminal moves, service area update and mobility management area update are performed.

Drawings

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

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

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

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

fig. 5 is a flowchart illustrating another communication method according to an embodiment of the present invention;

fig. 6 is a flowchart illustrating a mobility management area updating method according to an embodiment of the present invention;

fig. 7 is a flowchart illustrating a further communication method according to an embodiment of the present invention;

fig. 8 is a flowchart illustrating a service area update method according to 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;

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

fig. 10b is a schematic structural diagram of 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 Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and 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 (CN) through AN Access Network (AN). Specifically, the core Network CN may include a Network Slice Selection Function (NSSF), a subscriber information repository (subscriber repository); a Control Plane Mobility management network Function (CP-MM), hereinafter referred to as "Mobility management Function entity"; a Control Plane Session Management Network Function (CP-SM), hereinafter referred to as "Session Management Function entity"; the User Plane Network Function (User Plane Network Function) may also be referred to as "User Plane Function" in the following. As shown in fig. 1, the first network slice comprises 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 UP 1; the second network slice includes AN, CP-MM, CP2-SM, and UP 2; the third network slice includes AN, CP3-SM, UP 3. The terminal UE can be accessed to a plurality of different network slices simultaneously, and different network slices can support different services/application communication; a plurality of network slices may share a mobility management function entity CP-MM, such as a first network slice and a second network slice sharing the CP-MM; a plurality of Network slices may share AN Access Network AN, which may be a Radio Access Network (RAN), such as a first Network slice, a second Network slice, and a third Network slice sharing AN; each network slice has a specific control plane session management function entity and a user plane function entity.

3GPP TR 23.799v0.5.0 has already introduced the network slice selection functional entity NSSF, the user repository, the mobility management control plane, the session management control plane, and the session management user plane in the core network CN, and details thereof are not described herein again.

It should be noted that in the 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 embodiment of the invention can be applied to a communication system supporting the terminal to access the network slice. The technology described in the invention can be applied to a subsequent evolution system using an LTE system, such as a fifth generation 5G system. For clarity, the fifth generation 5G system is described herein as an example.

In the present application, the terms "network" and "system", "service area" and "service area" are often used interchangeably, but those skilled in the art will understand the meaning. In the present application, "first" and "second" should be understood as distinguishing between request messages and response messages, and should not be understood as limiting the messages, nor the timing. The UE referred to in this application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, and various forms of User Equipment (UE), Mobile Stations (MS), terminals (Terminal), Terminal devices (Terminal Equipment), and so on. For convenience of description, the above-mentioned user equipment is collectively referred to as UE in this application.

Fig. 2 is a flowchart illustrating a communication method according to an embodiment of the present invention, and as shown in fig. 2, the method includes steps S201 to S203.

S201, UE sends connection/conversation request information to AN, the connection/conversation request information carries network slice temporary identification of UE.

The UE determines whether the UE is associated with a Network Slice according to a Network Slice context (NS context) stored in the UE. If the UE establishes association with the network slice, the UE carries a network slice temporary identifier of the UE in the connection/session establishment request message; and if the UE is not associated with the network slice, carrying the public identification and the service parameters of the UE in the connection/session establishment request message by the UE.

It should be noted that the network slice serves the connection/session, and the network slice temporary identifier identifies the UE in the network slice.

The public identity of the UE comprises an International Mobile Subscriber Identity (IMSI) of the UE; or the UE-subscribed network slice is used for identifying the UE identity of the UE; or the default network slice subscribed by the UE is used for identifying the UE identification of the UE. The specific form of the network slice temporary identifier of the UE comprises the network slice identifier and the UE temporary identifier; or a temporary identity of the UE.

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

And the AN determines that the network slice context of the UE corresponding to the network slice temporary identifier of the UE is stored by the AN, wherein the network slice context of the UE comprises the network slice temporary identifier of the UE and a control plane function entity identifier. And the AN selects a control plane function entity for the UE according to the network slice context of the UE.

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

S203, the AN sends a connection/session setup response message to the UE.

In the embodiment of the invention, when UE initiates a connection/session request to AN, the UE self stores the context of a network slice for providing service for the connection/session, and the context of the network slice comprises the network slice temporary identifier of the UE; when the UE requests connection/conversation, the network slice temporary identifier of the UE is carried, and the UE can be directly accessed to the network slice, so that the time for the UE to be accessed to the network slice is saved.

This process will be described below by taking fig. 3 and 4 as an example.

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

As shown in fig. 3 and 4, a method for selecting different network slices for different applications/services of a UE is provided for the embodiments of the present invention. The network slice refers to a set of logical network functional entities supporting communication service requirements in a specific scene, and the UE network slice context is description information of a network slice providing services for the UE. Both the UE and the AN store UE network slice context. The UE network slice context in the UE includes UE usage type, traffic type, and/or application identification.

When an application X in the UE sends a service request to a network side, the UE checks whether the UE self stores a UE network slice context which is the same as an application X identifier, or a UE use type or a service type to which the application X belongs. That is, the UE determines whether it has currently established an association with a network slice that serves application X or a network slice that matches the UE usage type or traffic type to which application X belongs. The association of the UE with the network slice means that the UE is registered in the network slice or has been registered in the network slice, and the network slice can provide service for the UE.

If the UE does not establish the association with the network slice providing service for the application X or the network slice matched with the UE use type or the service type to which the application X belongs; that is, if the UE does not hold a UE network slice context matching application X, or a UE usage type or a traffic type to which application X belongs, steps 301 to 311 shown in fig. 3 are performed.

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

The connection/session establishment request includes a UE common identity (UE common id), service parameters (i.e., "application/service information"), and other parameters needed to establish the connection/session. The service parameters may include: the UE uses type, and/or traffic type, and/or application identification. Here, the UE public identity may be an international mobile subscriber identity IMSI of the UE, or a UE identity used for identifying the UE in all network slices subscribed by the UE, or a UE identity used for identifying the UE in a default network slice subscribed by the UE. The UE public identity may be used to identify the UE and is common to one or more network slices to which the UE subscribes. UE usage type, used to represent the UE's primary usage or usage scenario, for example: (use of the UE as) ordinary meters or ordinary sensors, vehicles, telemedicine equipment, entertainment equipment, etc.; the service type is used to indicate the category of the service (corresponding to application X), for example: mobile broadband service, machine communication, emergency service; an application identifier for indicating a specific application or application program, such as: application identification 1 (e.g., App-ID 011) is used to identify WeChat applications and application identification 2 (e.g., App-ID 021) is used to identify nam TMall applications.

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 based on the UE public identity and the service parameters in the connection/session setup request. For example, the NSSF selects a network slice NS1 for the UE and selects a CP1 for the UE according to at least one of a UE usage type, a service type, and an application identity, and at least one of an international mobile subscriber identity IMSI of the UE, a UE identity for identifying the UE for all network slices subscribed by the UE, and a UE identity for identifying the UE for a default network slice subscribed by the UE. Here, the CP1 may be a mobility management function entity CP1-MM or a session management function entity CP1-SM, determined by the architecture of the particular network slice NS1 (e.g., whether the CP1-MM is included), traffic parameters of the UE, etc.

Notably, the CP1 selected by the NSSF for the UE should satisfy the following condition:

(1) CP1 belongs to a particular network slice NS 1;

(2) the CP1 belongs to the same service area (service area) of the particular network slice NS1 as the AN.

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

In step 305, CP1 initiates an authentication and security request to the UE. In this step, CP1 completes authentication with the UE and establishes a security mechanism. For example, an integrity protection and ciphering algorithm and related parameters are determined. The CP1 assigns a UE a temporary identity (UE NS1 temporal identity, which may also be referred to as "terminal network slice temporary identity") within a particular network slice NS1 to the UE, generates a UE network slice context, and assigns a connection/session identity to the connection/session. Here, the CP1 belongs to a specific network slice NS 1.

In the embodiment of the present invention, the UE network slice context may include: temporary identification of the UE within a particular network slice NS1, traffic parameters, network slice service area identification, network slice connection/session identification, and security parameters.

Specific forms of temporary identification of the UE within a particular network slice NS1 may include the following.

(1) Network Slice identity (Network Slice id) + UE temporary identity (UE temporal id);

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

It should be noted that the UE may also include other parts in the temporary identifier in the NS 1. For example, CP1 identification in network slice NS1 is not described herein.

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

The UP1 selected should satisfy the following condition:

(1) the UP1 belongs to a particular network slice NS 1;

(2) the UP1 belongs to the same service area of a particular network slice NS1 as the AN.

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

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

Here, the specific form of the network slice service area identification may take the following several forms.

(1) The first form: a Network Slice identifier (Network Slice id) + service area identifier (service area id);

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

It should be noted that other parts may also be included in the service area identifier. For example, the service area identifier also includes a control plane functional entity identifier (NS CP1id) in the network slice, which is not described herein again. The service area identification may be configured in the CP1, UP1, and/or AN in the corresponding network slice.

Optionally, if the network slice temporary identifier and/or the network slice service area identifier of the UE do not include 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 establishment response to the AN.

In step 310, the AN sends a connection/session setup response to the UE. The connection/session setup response may contain UE network slice temporary identity, network slice service area identity, network slice connection/session identity.

A particular AN1 may maintain a context of a UE in network slice NS1 (UE NS1 context, which may also be referred to as "UE network slice context"). The context of the UE in network slice NS1 saved in AN1 may include the following: a UE network slice temporary identifier, a network slice service area identifier, a control plane functional entity address, a network slice connection/session identifier, a user plane functional entity address.

In step 311, the UE saves the context of the UE in the network slice NS 1. The UE context in network slice NS1 may include the following: service parameters, UE network slice temporary identifier, network slice service area identifier, security keys (securitykeys), network slice connection/session identifier. The service parameters may include: user usage type, service type, and/or application identification.

In the embodiment of the invention, the UE can establish connection/session with a plurality of network slices, and the selection of the network slices is not required to be carried out each time the connection/session of the application/service is established. This will be explained below by taking fig. 4 as an example.

If the UE has established an association with a network slice serving application X or a network slice matching the UE usage type or traffic type to which application X belongs, in other words, if the UE stores a UE network slice context matching the UE usage type or traffic type to which application X or application X belongs, steps 401 to 408 shown in fig. 4 are performed.

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

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

In step 402, the AN queries the UE network slice context stored in the AN according to the UE temporary identity in the network slice, thereby determining that the UE temporary identity in the network slice corresponds to the UE context in the network slice NS 1. The parameters in the context of the UE network slice stored in the AN have the same parameters as the parameters above and below the UE network slice stored in the UE, and also have different parameters. For example: the same parameters are a temporary identifier, a network slice service area identifier and a network slice connection/session identifier of the UE in the network slice; the difference is that the stored parameters in the AN include the control plane functional entity identifier and its address, the user plane functional entity identifier and its address; the UE stores parameters including security key and service parameters. The network slice context stored in the UE is a network slice indicating to provide service for the UE, and inquires a control plane function entity (CS-F) stored in the AN, wherein the UE is provided with service, through a common UE network slice temporary identifier.

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 performs similar steps 303 to 311 in fig. 3.

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

(1) in step 303, the NSSF selects, according to the UE network slice temporary identity, a previously selected network slice NS1 corresponding to the UE network slice temporary identity for the UE, and may select a previous control plane function entity CP 1.

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

(2) Step 305 may be omitted, i.e., no authentication and security requests between CP1 and the UE are performed. After the NSSF sends a connection/session establishment request to the CP1, the CP1 sends a connection/session establishment request to the UP1 in the network slice NS 1.

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

In step 402, if the AN stores the UE network slice context, and the network slice context of the UE stored in the AN stores the UE network slice context corresponding to the UE network slice temporary identifier. Since the UE network slice context stored in the AN includes the network slice NS1 identifier corresponding to the UE network slice temporary identifier and the core network control plane functional entity identifier and its address, the AN may determine the network slice NS1 corresponding to the connection/session establishment request based on the UE network slice temporary identifier and/or the UE network slice context of the AN, and select the CP1 of the core network in the UE network slice context stored in the AN, and perform the following steps.

In step 403, the AN sends a connection/session setup request to CP 1. The UE network slice temporary identity may be carried in the connection/session setup request.

In step 404, the CP1 selects UP1 for the UE.

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

The selected UP2 should satisfy the following condition:

(1) the UP2 belongs to a particular network slice NS 1;

(2) the UP2 belongs to the same service area of a particular network slice NS1 as the AN; and

(3) for load balancing purposes or the UP1 is not in the same network slice N1 service area as the UE, the UP2 has a higher priority than the previous UP 1.

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

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

In step 406, CP1 sends a connection/session setup response to the AN. The connection/session establishment response may carry a temporary identity of the UE in the network slice NS1, a service area identity in the specific network slice NS1, a connection/session identity of the specific network slice NS1, a control plane functional entity identity, a control plane functional entity address, a user plane functional entity identity, a user plane functional entity address. Wherein the service area id of the UE in the specific network slice NS1 is the original service area id, and when the UE changes in the network slice, the service area id of the specific network slice NS1 is the new service area id.

In step 407, the AN sends a connection/session setup response to the UE. The temporary identity of the UE in the specific network slice NS1, the service area identity of the specific network slice NS1, and the connection/session identity of the specific network slice NS1 may be carried in the connection/session setup response.

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

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

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

After the UE moves, the mobility management area of the UE may change. The following description will be given by taking fig. 5 and 6 as an example. In fig. 5 and 6, MM stands for mobility management function entity, CP-MM stands for mobility management function entity, CP1-SM stands for session management function entity, and UP2 stands for user plane function entity. Fig. 5 is a flowchart illustrating another communication method according to an embodiment of the present invention, and as shown in fig. 5, the method includes steps S501 to S506.

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

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

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

In this step, the UE determines that the mobility management area identifier or the mobility management area identifier list stored by the UE does not include the mobility management area identifier or the mobility management area identifier list in the first message, and the UE determines that the mobility management area has changed.

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

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

In this step, the AN determines the mobility management area update request message. And if the mobile management area updating request message is a mobile management request message, the AN forwards the mobile management area updating request message to a mobile management functional entity.

In one 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.

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

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

In an example, the MM may further determine a service area identifier of the UE-associated network slice according to the mobility management area identifier and/or the mobility management area identifier list; and the MM judges whether the context of the terminal network slice stored by the MM contains the service area identification of the network slice. And if the network slice context of the terminal does not contain the service area identification of the network slice, the MM selects a session management function entity for the UE.

In one example, the MM selects a session management function entity for the UE, including: and the MM selects a session management functional entity in the network slice for the UE according to the UE network slice temporary identifier in the network slice context and/or the service area identifier of the network slice, 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 of the service area identifier, and the user plane functional entity and the access node belong to the same service area of the network slice with the changed service area identifier. The MM sends a first message to the session management function entity, the first message comprising 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 changes.

Specifically, fig. 6 is a flowchart illustrating a mobility management area updating method 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 as to optimize the contact state between the terminal and the network, thereby providing a guarantee for the application of various network services. One 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 a message through the previous mobility management area, so the UE needs to update the mobility management area. When it is determined that the mobility management area is changed, the UE transmits 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, a mobility management area identifier saved by the terminal or previously accessed. The network slice identifier is used for identifying a network slice, and the UE network slice temporary identifier is used for identifying a terminal; the one or more network slice identities respectively correspond to different network slices associated with the UE. Correspondingly, the one or more UE network slice temporary identifications respectively correspond to temporary identifications allocated to the UE by different network slices associated with the UE.

It should be noted that the conditions for triggering the mobility management area update request may be various. For example, the UE receives a broadcast/multicast message sent by the AN. The broadcast/multicast message includes a mobility management area identity (MM area id) or a mobility management area identity list (MM area id list). The UE compares the mobile management area identifier or the mobile management area identifier list in the broadcast/multicast message with the mobile management area identifier or the mobile management area identifier list currently stored by the UE, and judges whether the mobile management area identifier or the mobile management area identifier list changes or not. If the UE finds that the mobile management area identifier or the mobile management area identifier list changes, the UE sends a mobile management area updating request to the AN. The UE may also determine whether the mobility management area changes in other manners, which is not described herein again.

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

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

After receiving the mobility management area update request from the UE, the AN determines the mobility management area update request. It is determined whether the mobility management area update request is a mobility management request message or a session management request message. The AN judges according to the type parameters of the messages in the mobility management area updating request, the mobility management messages comprise UE registration and the current position of the UE, and the session management messages comprise establishment, modification and release of the session.

If the mobility management area update request is a mobility management request message, the AN sends the mobility management request message to a mobility management functional entity CP-MM shared by a plurality of 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 a control plane function entity CP-SM of a 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 identity or a new list of mobility management area identities of the UE according to the mobility management area update request message.

The CP-MM may determine from preconfigured mobility management area identity (or mobility management area identity list) information, for example: a table of pre-configured "mapping of AN to a mobility management area identity (or a list of mobility management area identities)", determining a new mobility management area identity or a new list of mobility management area identities for the UE from the identity or address of the AN forwarding the mobility management area update request. Alternatively, in step 602, the AN sends a new mobility management area identifier (or a mobility management area identifier list) to the CP-MM together with the mobility management area update request, and the CP-MM determines a new mobility management area identifier or a new mobility management area identifier list of the UE according to the new mobility management area identifier (or the mobility management area identifier list) provided by the AN. One AN may serve one or more mobility management areas, and thus the AN has a corresponding mobility management area identity (or list of mobility management area identities).

In addition, the CP-MM determines a network slice with which the UE has currently established an association, i.e., a network slice with which the UE is associated, based on the one or more UE network slice temporary identifications or the one or more network slice identifications in the mobility management area update request.

The CP-MM determines the service area identity of the network slice with which the UE is associated. In particular, the CP-MM may map the UE new mobility management area identification list (or new mobility management area identification) to the network slice service area identification of the network slice with which the UE is associated.

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

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

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

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

when the UE moves from MM Area (list)1 (identified by MM Area (list) ID 1) to MM Area (list)2 (identified by MM Area (list) ID 2), according to the above mapping table, the corresponding Service Area (identified by Service Area ID 1) of the UE in Network Slice 1 is unchanged, while the corresponding Service Area in Network Slice 2, Network Slice 3 is changed, i.e., changed from Service Area 1 of Network Slice 2 to Service Area 2; change by Service Area 1 of Network Slice 3 to Service Area3 (identified by Service Area ID 2/4, 3/5 in the table above, respectively). Therefore, the CP-MM needs to send session messages to the Network Slice 2 and the Network Slice 3, respectively.

In step 604, if the CP-MM finds that the Service area identities of one or more network slices associated with the UE have changed, for each network slice whose Service area identity has changed, the mobility management function entity CP-MM selects a session management function entity CP-SM in the network slice based on the UE network slice temporary identity and/or based on a new Service area identity, and sends 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 a session management message. The session management messages include session setup messages, session release messages, and session modification messages.

The following steps 604 to 607, take the specific network slice NS1 as an example, to describe the procedure of performing the service area update by the mobility management function entity CP-MM in each network slice with a changed service area identity:

if the specific network slice NS1service area identity (NS1service area id) changes, the CP-MM determines CP1-SM based on the UE network slice temporary identity and/or based on the changed (new) specific network slice NS1service area identity, and sends a session message to CP 1-SM. Since one session management function entity is configured with the service area identifications of one or more network slices, and a plurality of session management function entities may be configured with the service area identifications of the same network slice, the CP-MM may determine the CP1-SM according to the service area identifications. The session message includes a Service area update request (Service area update request) and/or a session management message. The session management messages include session setup messages, session release messages, and session modification messages. The UE network slice temporary identifier may be carried in the service area update request or the session establishment request. The determined session management control plane functional entity may also be a new session management control plane functional entity CP2-SM in the above-mentioned specific network slice NS 1.

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

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

UP2 should satisfy the following condition:

(1) the UP2 belongs to a particular network slice NS 1;

(2) the UP2 belongs to the same service area of a particular network slice NS1 as the access node.

The CP2-SM may also select a new user plane functional entity UP2 according to pre-configured rules for user plane transmission path reselection/optimization. The rule of the user plane transmission path reselection/optimization may be that a specific user plane functional entity UP2 is preferred within a specific service area NS 1.

In step 606, the UP2 sends a connection/session establishment response to the CP 1-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 can 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, or a UE network slice temporary identifier. If the UE updates the service area to the network slice associated with the UE, 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 identity or the list of mobility management area identities and updates the UE network slice context. The UE network slice context includes parameters such as a service parameter, a UE network slice temporary identifier, a new network slice service area identifier, and the like. The service parameters comprise; the UE uses the type, the traffic type, and/or the application identification.

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

As can be seen from the above, the UE moves and the service area of the UE may change. Taking fig. 7 and 8 as an example, the UE directly senses that the service area has changed and then performs service area update will be described. In fig. 7 and 8, the UE represents the terminal, the AN represents the access node, the MM or CP-MM represents the mobility management function entity, the CP1-SM represents the session management function entity, and the UP represents the user plane function entity, for explanation. Fig. 7 is a flowchart illustrating a further communication method according to an embodiment of the present invention, and as shown in fig. 7, the method includes S701-S707.

S701, the AN sends a first message to the UE, wherein 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 a serving area transmission change.

In the step, the UE judges whether the network slice service area identifier in the network slice context stored by the UE is contained in the service area list. And if the network slice service area identification in the network slice context stored by the terminal is not contained in the service area list, sending a first service area updating request message to the access node.

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

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

The AN judges whether the service area updating 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 a mobility management function entity of the network slice.

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

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

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

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

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

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

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

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

The following describes in detail the service area update of the network slice of the terminal, taking fig. 8 as an example. Fig. 8 is a flowchart illustrating a service area updating method according to an embodiment of the present invention. In the embodiment, the terminal directly senses the change of the network slice service area and then makes an update request.

In step 801, the UE receives a broadcast/multicast message sent by the AN, where the broadcast/multicast message includes a service area list. The service area list includes one or more service area identifications 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 stored in the UE.

Specifically, the UE compares the network slice service area identity in the UE network slice context with the network slice service area identities in the service area list. As can be seen from the above step 408, the service area identifier of the network slice has two forms, and when the service area identifiers are compared, the two forms are described separately.

(1) If the network slice service area identifier includes a network slice identifier, the UE may 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 therein 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 with the service area list.

And 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 stored by the UE, determining that the service area of the network slice currently associated with the UE changes.

In step 803, if the service area of the network slice NS currently associated with the UE changes, the UE sends a service area update request to the AN. The service area update request may carry one or more UE network slice temporary identifications and one or more saved network slice service area identifications. Wherein the one or more saved network slice service areas identify network slices whose service areas have changed. Correspondingly, the temporary identifications of the one or more UEs in the network slice correspond to the temporary identifications allocated to the UE by the network slice with the changed service area. The service area of the network slice currently associated with the UE is changed, and the service area of the network slice is not changed. The service area update request carries the network slice with the changed service area currently associated with the UE.

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 updating request is a mobility management MM message, the AN sends the service area updating request to a mobility management function entity CP-MM shared by a plurality of network slices. And if the service area updating request is a session management SM message, the AN sends the service area updating request to a control plane function entity CP-SM of the specific network slice corresponding to the network slice temporary identifier of the UE.

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

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

Specifically, the CP-MM compares one or more network slice service area identifications saved by the UE and included in the service area update request with one or more network slice service area identifications corresponding to the AN. And one or more network slice service area identifications stored by the UE correspond to the network slices with changed service areas.

(1) If the network slice service area identifier includes a network slice identifier, the CP-MM may compare one or more network slice service area identifiers stored by the UE with a network slice service area identifier having the same network slice identifier among the one or more network slice service area identifiers corresponding to the AN.

(2) If the network slice service area identification does not contain the network slice identification, the CP-MM may directly compare one or more network slice service area identifications saved by the UE with one or more network slice service area identifications corresponding to the AN.

If the CP-MM finds that the one or more network slice service area identifiers corresponding to the AN do not include the network slice service area identifier stored by the UE, it determines that the service area of the network slice currently associated with the UE changes, and performs step 806.

In step 806, for each network slice with changed service area identities, the CP-MM may select a CP1-SM based on the UE network slice temporary identity and forward the service area update request to the selected CP 1-SM. Correspondingly, the temporary identifications of the one or more UEs in the network slice are temporary identifications allocated to the UEs by the session management function entity in the network slice with the changed service area; and the session management functional entity is a functional entity before the service area is updated, and 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, taking the network slice NS1 as an example, illustrate the flow of the service area update of CP-MM in each network slice with changed service area identity:

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

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

Due to the change of service area, the 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 the UP 2. The connection/session establishment request may carry parameters such as UE network slice temporary identifier, access node address, etc.

The new user plane function entity UP2 should satisfy the following condition:

(1) UP2 belongs to network slice NS 1;

(2) the UP2 belongs to the same service area of network slice NS1 as the AN.

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

In step 808, the UP2 sends a connection/session setup response to the 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, the CP1-SM (or CP2-SM if a new session management function entity is selected) sends a service area update response to the CP-MM. The service area update response may carry 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 UE context at NS 1. The context of the UE at NS1 may include traffic parameters, UE network slice temporary identity, new network slice service area identity. The traffic parameter may be a UE usage type, a traffic type, and/or an application identification.

In the embodiment of the invention, when the UE updates the mobile area, the UE updates the service areas to a plurality of network slices simultaneously through the mobility management functional entity, thereby rapidly realizing the updating of the terminal service nodes (comprising a control plane functional entity (CP) and a user plane functional entity (UP)) in the plurality of network slices associated with the terminal.

The above-mentioned embodiments of the present invention have been introduced mainly from the perspective of interaction between network elements. It is to be understood that each network element, for example, a mobility management function entity, a session management function entity, a terminal, etc., contains a hardware structure and/or a software module corresponding to each function for implementing the above functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

According to the method example, the embodiment of the present invention may perform functional unit division on the mobility management functional entity, the session management functional entity, the terminal, and the like, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In case of integrated units, fig. 9a shows a possible structural diagram of the access node involved in the above embodiment. The access node comprises: a processing unit 902 and a communication unit 903. Processing unit 902 is configured to control and manage actions of the access node, e.g., processing unit 902 is configured to support the access node to perform processes S202 and S203 in fig. 2, processes S302 and S310 in fig. 3, processes S402, S403 and S407 in fig. 4, processes S501, S504 and S505 in fig. 5, processes S602 and S609 in fig. 6, processes S701, S704, S705 and S707 in fig. 7, processes S801, S804 and S811 in fig. 8, and/or other processes for the techniques described herein. The communication unit 903 is configured to support communication between the mobility management function entity and other network entities, for example, communication between 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 comprise a storage unit 901 for storing program codes and data of the mobility management function entity.

The processing Unit 902 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 903 may be a communication interface, a transceiver circuit, etc., wherein the communication interface is a generic 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 function entity according to the embodiment of the present invention may be the mobility management function entity shown in fig. 9 b.

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 also include a bus 914. The processor 912, the communication interface 911 and the memory 913 may be connected to each other through a bus 914; the bus 914 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 914 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 9b, but this does not indicate only one bus or one type of bus.

In case of using integrated units, fig. 10a shows a possible structural diagram of the mobility management function entity involved in the above embodiment. The mobility management function entity 1000 includes: a processing unit 1002 and a communication unit 1003. The processing unit 1002 is configured to control and manage actions of the mobility management function entity, for example, the processing unit 1002 is configured to support the mobility management function entity to perform processes S306 and S308 in fig. 3, processes S404 and S406 in fig. 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 technologies described herein. The communication unit 1003 is configured to support communication between the mobility management function entity and other network entities, for example, a session management function entity, an access node, a user plane function entity, and the like shown in fig. 1. The mobility management function entity may further comprise 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, and may be, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 1003 may be a communication interface, a transceiver circuit, etc., wherein the communication interface is a generic 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 function entity according to the embodiment of the present invention may be the session management function entity shown in fig. 10 b.

Referring to fig. 10b, the mobility management function 1010 includes: processor 1012, communication interface 1011, memory 1013. Optionally, the mobility management function 1010 may also include a bus 1014. The processor 1012, the communication interface 1011, and the memory 1013 may be connected to each other by a bus 1014; the bus 1014 may be a PCI bus or an EISA bus, etc. The bus 1014 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10b, but this does not indicate only one bus or one type of bus.

In the case of an integrated unit, fig. 11a shows a possible structural diagram of the terminal involved in the above-described embodiment. The terminal includes: a processing unit 1102 and a communication unit 1103. Processing unit 1102 is configured to control and manage the actions of the terminal, e.g., processing unit 1102 is configured to support the terminal to perform processes S201 in fig. 2, processes S301 and S311 in fig. 3, processes S401 and S408 in fig. 4, processes S502 and S503 in fig. 5, 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 communication between the terminal and other network entities, such as the access node, the mobility management function entity, etc. 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, such as a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication unit 1103 may be a communication interface, a transceiver circuit, etc., where the communication interface is a generic 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 according to the embodiment of the present invention may be the terminal shown in fig. 11 b.

Fig. 11b shows a simplified schematic diagram of a possible design structure of a terminal involved in an embodiment of the present invention. The terminal 1110 includes a transmitter 1111, a receiver 1112, and a processor 1113. The processor 1113 may also be a controller, and is shown as "controller/processor 1113" in FIG. 11 b. 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, the transmitter 1111 conditions (e.g., converts to analog, filters, amplifies, and frequency upconverts, etc.) the output samples and generates AN uplink signal, which is transmitted via AN antenna to the AN as described in the embodiments above. On the downlink, the antenna receives the downlink signal transmitted by the base station in the above embodiment. Receiver 1112 conditions (e.g., filters, amplifies, frequency downconverts, and digitizes, etc.) the received signal from the antenna and provides input samples. Within modem processor 1115, an encoder 1118 receives and processes (e.g., formats, encodes, and interleaves) traffic data and signaling messages to be sent on the uplink. A modulator 1118 further processes (e.g., symbol maps and modulates) the coded traffic data and signaling messages and provides output samples. A demodulator 1119 processes (e.g., demodulates) the input samples and provides symbol estimates. A decoder 1118 processes (e.g., deinterleaves and decodes) the symbol estimates and provides decoded data and signaling messages for transmission to terminal 1110. Encoder 1116, modulator 1117, demodulator 1119, and decoder 1118 may be implemented by a combined modem processor 1115. These elements are processed in accordance with the radio access technology employed by the radio access network (e.g., the access technologies of LTE and other evolved systems). Note that when terminal 1110 does not include modem processor 1115, the above-described functions of modem processor 1115 may also be performed by processor 1113.

Further, terminal 1110 can also include a memory 1114, where memory 1114 is used to store program codes and data for terminal 1110.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware or in software executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, 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 reside as discrete components in a mobility management function, a session management function, or a terminal.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in connection with the embodiments of the invention may be implemented in 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 media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the embodiments of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only specific embodiments of the present invention, and are not intended to limit the scope of the embodiments of the present invention.

Claims

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;

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.