CN113170387B

CN113170387B - Managing access and mobility functions

Info

Publication number: CN113170387B
Application number: CN201880098609.3A
Authority: CN
Inventors: 梁爽; 朱进国; 叶敏雅; 卢飞
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-10-09
Filing date: 2018-10-09
Publication date: 2022-10-11
Anticipated expiration: 2038-10-09
Also published as: WO2020034371A1; CN113170387A

Abstract

A method of wireless communication, comprising: a first network function in a core network receiving a first message from an access network for initiating a procedure for a mobile device; a first network function sends a notification message to a second network function in a core network; the first network function receiving a second message from the second network function; the first network function identifies a context of the mobile device based on the first identity, and the first network function receives or sends a transfer message of the procedure via the access network based on the context of the mobile device.

Description

Managing access and mobility functions

Technical Field

The present application relates generally to wireless communications.

Background

Mobile communication technology is pushing the world to increasingly connected and networked society. The rapid growth of mobile communication technology and technological advances have resulted in greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectral efficiency, and latency are also important to meet the needs of various communication schemes. Various technologies are under discussion, including new ways to provide higher quality services, longer battery life, and improved performance.

Disclosure of Invention

This application describes, among other things, techniques for separating the functionality provided by access and mobility management functions into two network functions, such that mobility management may be self-contained, reusable, and independent.

In one example aspect, a method of wireless communication is provided. The method includes a first network function in a core network receiving a first message from an access network for initiating a procedure for a mobile device. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. The method comprises the first network function sending a notification message to a second network function in the core network. The second network function is for providing a mobility management function and the notification message comprises a first identity associated with the first network function and the mobile device. The method includes the first network function receiving a second message from the second network function. The method includes the first network function identifying a context of the mobile device based on the first identification. The method also includes the first network function receiving or sending a transfer message of the procedure via the access network based on the context of the mobile device.

In another example aspect, a method of wireless communication is provided. The method includes a first network function in a core network receiving a notification message from a second network function in the core network. The first network function is for providing mobility management functions and the second network function is dedicated to managing control plane communications between the core network and the one or more access networks. The notification message includes a second identification associated with the second network function and the mobile device, and the notification message further includes information about a procedure initiated by the mobile device. The method includes a first network function processing information of a procedure initiated by a mobile device. The method includes the first network function sending a message to the second network function.

In another example aspect, a method of wireless communication is provided. The method includes a network storage function (NRF) service in a core network receiving a request message from a first network function in the core network or a second network function in the core network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks and the second network function is used to provide mobility management functions. The method includes the NRF service transmitting a response message to the first network service or the second network function. The method includes the NRF service sending a first notification message to the first network function to notify the first network function of configuration information about the second network function. The method further includes the NRF service sending a second notification message to the second network function to notify the second network function of the configuration information about the first network function.

In another example aspect, a method of wireless communication is provided. The method comprises the first network function receiving a notification message from a network storage function, NRF, service in a core network. The first network function is dedicated to managing control plane communications between the core network and one or more access networks and the second network function is used to provide mobility management functions. The notification message includes configuration information regarding the second network function. The method includes the first network function sending an update message to the access network to inform the access network of the second network function. The update message includes an identification of the second network function based on configuration information regarding the second network function.

In another example aspect, a method of wireless communication is provided. The method includes a first network function receiving a message from an access network, the message including information of one or more configurations of the access network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. The method includes the first network function sending a response to the access network acknowledging receipt of the message. The method comprises sending an update message from a first network function to a network storage function, NRF, service in a core network to update the one or more configurations of the access network to trigger a notification from the NRF service to a second network function providing a mobility management function.

In another example aspect, a method of wireless communication is provided. The method includes a first network function in a core network receiving a message from a second network function in the core network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks, and the second network function is used to provide mobility management functions. The message includes information about the registration area of the mobile device. The method includes a first network function sending a paging request to an access network corresponding to a registration area of a mobile device.

In yet another example aspect, a wireless communications apparatus is provided. The apparatus includes a processor configured to implement the above-described method.

In yet another example aspect, a computer program storage medium is provided. The computer program storage medium includes code stored thereon. When executed by a processor, the code causes the processor to implement the described methods.

These and other aspects are described in the present application.

Drawings

Fig. 1 illustrates a service-based architecture of a 5G system.

Fig. 2 illustrates an example architecture of access and mobility management functions in accordance with one or more embodiments of the present technology.

Fig. 3 illustrates an example of identification used by an N1 communication service and an N2 communication service in accordance with one or more embodiments of the present technology.

Fig. 4 illustrates an example of an initiation or update procedure for an N1 communication service instance in accordance with one or more embodiments of the present technology.

Fig. 5 illustrates an example of an initiation or update procedure for an N2 communication service instance in accordance with one or more embodiments of the present technology.

Fig. 6 illustrates an example of a setup or update procedure for a NG-RAN in accordance with one or more embodiments of the present technology.

Fig. 7 illustrates an example of a non-access stratum procedure in accordance with one or more embodiments of the present technology.

Fig. 8 illustrates an example paging procedure in accordance with one or more embodiments of the present technology.

Fig. 9 is a flow diagram of a method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 10 is a flow diagram of another method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 11 is a flow diagram of another method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 12 is a flow diagram of another method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 13 is a flow diagram of another method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 14 is a flow diagram of yet another method for wireless communication in accordance with one or more embodiments of the present technology.

Fig. 15 illustrates an example of a wireless communication system in which one or more embodiments in accordance with the present technology may be applied.

Fig. 16 is a block diagram representation of a portion of a radio station in accordance with one or more embodiments to which the present techniques may be applied.

Detailed Description

Section headings are used in this application only to improve readability and not to limit the scope of the embodiments and techniques provided in each section to that section. Some features are described using an example of a 5G wireless protocol. However, the applicability of the provided techniques is not limited to 5G wireless systems.

New generation wireless communications 5G the development of new wireless (NR) communications is part of a growing mobile broadband evolution process to meet increasing network demands. In contrast to previous generations of wireless communication systems, the 5G system architecture is service based. A service-based architecture means that an architectural element is defined as a network function that provides a service to any network function that allows the use of the provided service through an interface of a common framework. Network storage function (NRF) allows network functions to discover services provided by other network functions. The architecture model further employs principles of modularity, reusability, network function self-containment, etc., thereby enabling deployments to take advantage of the latest virtualization and software technologies.

Fig. 1 illustrates a service-based architecture of a 5G system. The 5G system architecture 100 includes the following Network Functions (NFs):

1. access and mobility management functions (AMFs). The AMF includes functions such as User Equipment (UE) mobility management, reachability management, connection management, and the like. The AMF is located at the end of the Radio Access Network (RAN) Control Plane (CP) interface N2 and the non-access stratum (NAS) N1. The AMF assists the NAS to implement ciphering and integrity protection. The AMF also distributes the Session Management (SM) NAS to the appropriate Session Management Function (SMF) over the N11 interface. To improve transmission reliability, the concept of AMF groups is introduced. The AMF group includes the AMFs (i.e., a set of nearly independent business operations on a common physical infrastructure) that serve a given area and network slice. In some embodiments, an Unstructured Data Storage Function (UDSF) is used in the AMF group to store UE contexts. The AMF may be uniquely identified by a globally unique AMF identification (GUAMI). For example, GUAMI may be constructed as < MCC > < MNC > < AMF Region ID > < AMF Set ID > < AMF Pointer >.

2. Session Management Function (SMF). SMF includes UE Internet Protocol (IP) address assignment and management. SMF also includes selection and control of User Plane (UP) functions and Protocol Data Unit (PDU) connection management, etc.

3. User plane management function (UPF). The UPF is the anchor point for internal/intra Radio Access Technology (RAT) mobility. The UPF also acts as an external PDU session point for connection to the data network. The UPF routes and forwards packets indicated by the SMF. The UPF also buffers downlink data when the UE is in idle mode.

4. Unified Data Management (UDM). The UDM stores a subscription profile for the UE.

5. A Policy Control Function (PCF). The PCF generates policies that control network behavior based on subscriptions and directives from an Application Function (AF). It also provides policy rules to CP functions (e.g., AMF and SMF) to enforce them.

In fig. 1, interfaces such as N11 and N7 are service-based interfaces. Interactions between control plane Network Functions (NFs) over the service-based interface are specified by the respective NF services. The network functions may provide different functions, thereby providing different NF services to different consumers. To achieve network slicing, each NF service provided by a network function needs to be self-contained, reusable, and use a management scheme that is independent of other NF services provided by the same network function. However, the AMF is not a full service-based NF because it includes an access management function that handles communication over the N2 interface. The N2 interface is based on Stream Control Transmission Protocol (SCTP) which requires the establishment of a Next Generation Application Protocol (NGAP) association between a next generation radio access network (NG-RAN) and an AMF. Techniques are provided that may separate the functionality provided by the AMF into two network functions so that mobility management functionality may be provided as a service-based NF.

Fig. 2 depicts an example architecture of access and mobility management functions in accordance with one or more embodiments of the present technology. As shown in fig. 2, the AMF can be divided into two NFs:

n1 communication services

201a, 201b, 201c (denoted as N1 Comm) and

N2 communication services

202a, 202b (denoted as N2 Comm).

The N1Comm (201 a, 201b, 201 c) includes functions such as UE mobility management, reachability management, connection management for the NAS layer (including NAS ciphering and integrity protection), and relaying of NAS messages to the appropriate network (e.g., SMF, AUSF, etc.).

N2Comm (202 a, 202 b) includes functionality such as N2 interface termination and management. In particular, N2Comm collects and maintains information about NG-RAN. For example, N2Comm provides information about NG-RAN in the NF storage function (NRF), allowing N1Comm to subsequently retrieve such information from the NRF. If the NG-RAN updates its configuration or a new NG-RAN node is added, the N2Comm may update configuration information about the NG-RAN to the NRF. In some embodiments, N2Comm may retrieve information from the NRF that is registered or updated by N1Comm. N2Comm then decides whether to update the NG-RAN based on this information.

To improve transmission reliability, the concept of N1Comm group (211) and N2Comm group (212) was also introduced. The configuration information may be stored in UDSFs of respective groups, respectively. In some embodiments, if there is an N2Comm group, the NG-RAN connects to all N2 comms in the same N2Comm group. In some embodiments, to avoid any negative impact on NG-RAN, a one-to-one mapping may be established between the N2Comm group and the N1Comm group. In some embodiments, the N1Comm group and the N2Comm may be deployed independently. In some embodiments, if there is no N2Comm group, all N1 Comms in the N1Comm group map to one N2Comm. If there is no N1Comm group, all N2 Comms in the N2Comm group map to one N1Comm.

In some embodiments, an N1Comm may store an N2Comm name, an N2Comm Identification (ID), a Fully Qualified Domain Name (FQDN), or an IP address for each N2Comm in the N2 group. The N1Comm may store configuration information regarding a Tracking Area Identification (TAI) list, a Public Land Mobile Network (PLMN) list, or Discontinuous Reception (DRX) information. N1Comm may also store slice information for NG-RANs connected to each N2Comm in the N2 group. If N2Comm is already registered in the NRF, N1Comm may retrieve the above information from the NRF.

In some embodiments, for each N2 link, N2Comm stores a list of corresponding RAN node IDs. The N2Comm may store the name of the RAN node and/or configuration information about the TAI list, PLMN list or DRX information for each RAN node ID. The N2Comm may also store slice information supported by the RAN node. In some embodiments, N2Comm may store the name, GUAMI, FQDN, or IP address of N1Comm for each N1Comm. If N1Comm is already registered in the NRF, N2Comm may retrieve the above information from the NRF.

In some embodiments, the NG-RAN may store the name of N1Comm (or AMF name) for each N2 link. The NG-RAN may store, for each N1Comm name, a GUAMI list for N1Comm and a PLMN list supported by N1Comm.

In some embodiments, the NRF may store for each N1Comm the IP address of the N2Comm group ID, service area, name, GUAMMI, FQDN, and/or N1Comm. The NRF may also store a name, N1Comm group ID, service area, ID, FQDN, and/or IP address for each N2Comm. The NRF may also store configuration information such as TAI lists, PLMN lists, DRX information, and/or slice information of NG-RANs connected to each N2Comm in the N2Comm group.

Fig. 3 illustrates an example of identification used by an N1 communication service and an N2 communication service in accordance with one or more embodiments of the present technology. As shown in fig. 3, the RAN UE NGAP ID (301) is an identity that identifies the UE in the NG-RAN on the N2 reference point. AMF UE NGAP ID (302) is an identity that identifies the UE in N2Comm on the N2 reference point. In some embodiments, the RAN UE NGAP ID (301) and AMF UE NGAP ID (302) may be the same as the existing RAN UE NGAP ID and AMF UE NGAP ID between the NG-RAN and AMF to minimize any design impact on the NG-RAN.

Fig. 3 also shows additional identities that N1Comm and N2Comm may use to identify a UE. For example, the N2 UE ID (303) is an identity that may be used to identify a UE in N2Comm on an Nn reference point between N1Comm and N2Comm. N1 UE ID (304) is an identity that may be used to identify a UE in N1Comm on an Nn reference point between N1Comm and N2Comm.

FIG. 4 illustrates an example of an initiation or update process for an N1Comm instance in accordance with one or more embodiments of the present technology.

Step 401: an N1Comm instance is instantiated in the network. Alternatively, the configuration information for the N1Comm instance is updated.

Step 402: the N1Comm sends a message (e.g., NRF _ NFManagement _ NFRegister request or nrrf _ NFManagement _ NFUpdate request) to the NRF. The message may include a GUMAI for N1Comm to uniquely identify N1Comm service, N1Comm name, N1Comm group ID, and/or N1Comm service area.

Step 403: the NRF stores the information included in the message and sends a response (e.g., NRF _ NFManagement _ NFRegister response or NRF _ NFManagement _ NFUpdate response) to the N1Comm.

Step 404: if N1Comm subscribes to notification of N2Comm in the service area of N1Comm, the NRF determines whether there is a service area (e.g., N2 Comm) that overlaps with the service area of N1Comm or whether there is an N2Comm in the N2Comm group identified by the N2Comm group ID provided by N1Comm. If so, the NRF sends a message (e.g., nnrf _ NFmanagement _ NFStatusNotify) to the N1Comm to inform the N2Comm of the configuration information. The message may include information about N2Comm supported slices, tracking Areas (TAs), and/or PLMNs. In some embodiments, such information is transmitted in a response message in step 403.

Step 405: if N2Comm has registered with the NRF and subscribed to notification of N1Comm before the service area of N2Comm, the NRF determines whether the service area of N1Comm overlaps with the service area of N2Comm or whether there is an N2Comm in the N2Comm group identified by the N2Comm group ID provided by N1Comm. If so, the NRF sends a message (e.g., nnrf _ NFManagement _ NFStatusNotify) to the N2Comm to inform the N1Comm of the configuration information. The message may include information about the names of GUMAI and/or N1Comm.

Step 406: after the N2Comm receives a message (e.g., nrrf _ NFManagement _ nfstatusionnotify) from the NRF, the N2Comm sends an update message (e.g., AMF Configuration update) to update the AMF information stored in the NG-RAN. The update message may include information regarding the N1Comm supported GUMAI list and/or PLMN list.

Step 407: the NG-RAN updates the configuration information and sends an acknowledgement (e.g., AMF configuration update acknowledgement) to the N2Comm.

FIG. 5 illustrates an example of an initiation or update process for an N2Comm instance in accordance with one or more embodiments of the present technology.

Step 501: an N2Comm instance is instantiated in the network. Alternatively, the configuration information for the N2Comm instance is updated.

Step 502: the N2Comm collects information such as TAI lists, network slice lists, and/or PLMN lists from the NG-RAN, which will be discussed in detail in connection with fig. 6 shown below. Then, the N2Comm sends a message (e.g., NRF _ NFManagement _ NFRegister request or nrrf _ NFManagement _ NFUpdate request) to the NRF. The message may include information that the N2Comm has collected, such as information about TAI lists, network slice lists, and/or PLMN lists supported by the N2Comm. The message may also include the service area, name, and/or ID of the N2Comm to allow the N2Comm to be uniquely identified.

Step 503: the NRF stores the information included in the message and sends a second message (e.g., NRF _ NFManagement _ NFRegister response or nrrf _ NFManagement _ NFUpdate response) to the N2Comm.

Step 504: if N2Comm subscribes to the notification of N1Comm in the service area of N2Comm, the NRF determines whether the service area of another service (e.g., N1 Comm) overlaps with the service area of N2Comm or whether there is an N1Comm in the N1Comm group identified by the N1Comm group ID provided by N2Comm. If so, the NRF sends a message (e.g., nnrf _ NFManagement _ NFStatusNotify) to the N2Comm to inform the N1Comm of the configuration information. The message may include the name of the N1Comm and/or the GUMAI. In some embodiments, such information is transmitted in a response message in step 503.

Step 505: if the N2Comm receives a message (e.g., nrrf _ NFManagement _ nfstatustonotify in step 504 or a response message in step 503) from the NRF, it is determined whether to update information stored in the NG-RAN. If so, a message (e.g., an AMF configuration update) is sent to the NG-RAN to update the corresponding configuration information.

Step 506: NG-RAN updates configuration and sends an acknowledgement (e.g., AMF configuration update acknowledgement) to N2Comm.

Step 507: if N1Comm has registered with the NRF and is subscribed to notification of N2Comm in the service area of N1Comm, the NRF determines whether the service area of N2Comm overlaps with the service area of N1Comm or whether there is N1Comm in the N1Comm group identified by the N1Comm group ID provided by N2Comm. If so, the NRF sends a message (e.g., nnrf _ NFManagement _ NFStatusNotify) to the N1Comm service to inform the N2Comm of the configuration information. The message may include information about N2Comm supported slices, tracking areas, and/or PLMNs.

Step 601: a new NG-RAN has been added to the network. Alternatively, the NG-RAN updates its configuration.

Step 602: the NG-RAN sends a message (e.g., NG setup request, RAN configuration update, or NG reset) to the N2Comm. The message may include information about slices, TAs and/or PLMNs supported by the NG-RAN.

Step 603: after receiving the message from the NG-RAN, the N2Comm sends a response or acknowledgement to the NG-RAN (e.g., NG setup response or RAN configuration update acknowledgement).

Step 604: the N2Comm collects and compiles configuration information from the NG-RAN. Then, N2Comm sends a message (e.g., NRF _ NFManagement _ NFUpdate request) to the NRF to update the configuration information of N2Comm in the NRF.

Step 605: the NRF sends a message (e.g., NRF _ NFManagement _ NFUpdate response) to confirm the update.

Step 606: if N1Comm subscribes to notification of other services in the service area of N1Comm, the NRF determines whether the service area of another service (e.g., N2 Comm) overlaps with the service area of N1Comm or whether there is an N1Comm in the N1Comm group identified by the N1Comm group ID provided by N2Comm. If so, the NRF sends a message (e.g., nnrf _ NFManagement _ NFStatusNotify) to the N1Comm to notify of the updated configuration information. The message may include N2Comm configuration information.

FIG. 7 illustrates an example NAS process in accordance with one or more embodiments of the present technology. It should be noted that fig. 7 only shows the interaction between NG-RAN, N1Comm and N2Comm, and is not a complete description of the NAS process.

During the NAS procedure, to transmit UE NAS messages in N1Comm and N2Comm, N1 UE ID and N2 UE ID are introduced to uniquely identify UE contexts in the respective N1Comm and N2Comm groups. N2Comm allocates N2 UE ID and N1Comm allocates N1 UE ID. When the UE is in connected mode, N1Comm and N2Comm exchange N1 UE ID and N2 UE ID and store the mapping { N1 UE ID, N2 UE ID }. N1Comm and N2Comm may use the ID in subsequent NAS transmissions.

Step 701: the UE initiates a NAS procedure (e.g., a registration procedure or a service request procedure) and sends the NAS message through a message (e.g., a radio resource control message).

Step 702: the NG-RAN receives a message from the UE. If the message includes the GUMAI or 5G SAE temporary Mobile subscriber identity (S-TMSI) of the UE, the NG-RAN selects N2Comm based on GUMAI or 5G S-TMSI. Alternatively, if the message does not include the used GUMAI or 5G S-TMSI (or if N2Comm service is not selected), the NG-RAN determines an N2Comm group and selects N2Comm from the group. The selection may be performed randomly. The NG-RAN then sends a message (e.g., an initial NAS message) to the selected N2Comm. In some embodiments, the UE's GUMAI or 5G S-TMSI is forwarded to the N2Comm via a message. After N2Comm receives the message from NG-RAN, N2Comm selects N1Comm based on the message. For example, if the message includes the UE's GUIMI or 5G S-TMSI, then the N2Comm selects the N1Comm corresponding to GUMAI or 5G S-TMSI.

Steps

703 and 704 are skippable.

Step 703: in some cases, the message does not include the UE's GUIMI and 5G S-TMSI. An N2Comm may select an N2Comm in the N1Comm group based on information retrieved from the NRF or local configuration. For example, an N2Comm may send a message (e.g., nrrf _ NFDiscovery _ Request) to the NRF. The message may include an identification of the N1Comm group (e.g., the N1Comm group ID).

Step 704: after receiving a message from N2Comm, the NRF selects N1Comm based on the N1Comm group ID in the message. The NRF then sends a Response (e.g., nnrf _ NFdiscovery _ Response) to the N2Comm. The response may include the name, GUAMI, FQDN, or IP address of the N1Comm to uniquely identify the N1Comm.

Step 705: the N2Comm allocates an identity to identify the UE context (e.g., N2 UE ID). Then, the N2Comm sends a Message (e.g., nn2Comm _ N1N2Message _ Notification) to the selected N1Comm. The message may include the NAS message and/or an identification of the UE (e.g., N2 UE ID).

Step 706: after receiving the message from N2Comm, N1Comm processes the NAS message.

Step 707: the N1Comm allocates an identity to identify the UE context (e.g., N1 UE ID). If N1Comm needs to send a message back to NG-RAN, it will send a message to N2Comm (e.g., nn2Comm _ N1N2message transmission). The message includes the N1 UE ID and the N2 UE ID to identify the UE context. The message also includes a Downlink (DL) NAS message to the UE.

Step 708: the N2Comm identifies the UE context by the N2 UE ID in the message and stores the N1 UE ID. N2Comm transmits DL NAS message to NG-RAN.

Step 709: in some cases, the UE may send an Uplink (UL) NAS message to N1Comm via NG-RAN and N2Comm.

Step 710: NG-RAN and N2Comm exchange messages over the N2 interface by using RAN UE NGAP ID and AMF UE NGAP ID to uniquely identify the UE context.

Step 711: n2Comm and N1Comm exchange messages over the Nn interface using N2 UE ID and N1 UE ID to identify the UE context. For example, an N2Comm may send a Message (e.g., nn2Comm _ N1N2Message Notification) to notify the UL NAS of the N1Comm Message.

Step 801: when the UE is in idle mode and the N1Comm receives a downlink transfer message (e.g., namf _ Communication _ N1N2 MessageTransfer), the N1Comm may call the UE.

Step 802: n1Comm may select N2Comm based on its local information or through NRF. In some embodiments, an N1Comm sends a message (e.g., nrrf _ NFDiscovery _ Request) to the NRF to select an N2Comm in the N1Comm group.

Step 803: the NRF then returns a message (e.g., nnrf _ NFdiscovery _ Response) to the N1Comm that includes the name, GUAMI, FQDN, or IP address of the N2Comm.

Step 804: after selecting an N2Comm, the N1Comm sends a message (e.g., an Nn2Comm _ Page request) to the selected N2Comm. The message may include the UE registration area and/or the S-TMSI of the UE.

Step 805: after obtaining the UE registration area included in the message, N2Comm determines all NG-RANs within the registration area. The N2Comm then sends a message (e.g., an N2 paging request) to the selected NG-RAN.

Step 806: the NG-RAN pages the UE upon receiving the message from the N2Comm.

Step 807: the UE then initiates a service request procedure upon receiving the paging message.

Fig. 9 is a flow chart of a method 900 for wireless communication. Method 900 may be implemented in a scenario such as the embodiment depicted in fig. 7. The method 900 includes: a first network function (e.g., N2 Comm) in a core network receives a first message from an access network (e.g., NG-RAN) for initiating a procedure for a mobile device, step 901. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. In step 902, the first network function sends a notification message to a second network function (e.g., N1 Comm) in the core network. The second network function is for providing a mobility management function. The notification message includes a first identification (e.g., an N2 UE ID) associated with the first network function and the mobile device. The first network function receives a second message from the second network function, step 903. At step 904, the first network function identifies a context of the mobile device based on the first identification. The first network function receives or sends a transfer message of the process via the access network based on the context of the mobile device, step 905.

In some embodiments, the first message from the access network includes an identification of the mobile device. The method also includes determining, by the first network function, the second network service based on the identity of the mobile device.

In some embodiments, the first network function belongs to a first group of network functions and the second network function belongs to a second group of network functions. The first network function group and the second network function group are mapped one-to-one.

In some embodiments, the method includes the first network function sending a request to a network storage function (NRF) service, the request including an identification of the second network function group. The method further comprises the first network function receiving a response from the NRF service indicating an identity of the second network function.

In some embodiments, the method includes the first network function determining a first identity associated with the first network function and the mobile device.

In some embodiments, the notification message is transmitted over an Nn interface. In some embodiments, the second message from the second network function includes a second identification (e.g., an N1 UE ID) associated with the second network function and the mobile device. The second message from the second network function includes the first identification. In some embodiments, the method includes storing the second identification for use in identifying the second network function based on the mobile device in subsequent transmissions.

Fig. 10 is a flowchart representation of a method 1000 for wireless communication. Method 1000 may be implemented in a scenario such as the embodiment depicted in fig. 7. The method 1000 includes: in step 1001, a first network function (e.g., N1 Comm) in a core network receives a notification message from a second network function (e.g., N2 Comm) in the core network. The first network function is for providing mobility management functions and the second network function is dedicated to managing control plane communications between the core network and the one or more access networks. The notification message includes a second identification (e.g., an N2 UE ID) associated with the second network function and the mobile device, and also includes information about a procedure initiated by the mobile device. At step 1002, a first network function processes information about a process initiated by a mobile device. At step 1003, the first network function processes information about the process initiated by the mobile device.

In some embodiments, the method includes the first network function determining a first identification (e.g., an N1 UE ID) associated with the first network function and the mobile device for identifying a context of the mobile device. In some embodiments, the message sent to the second network function comprises the first identity. The message sent to the second network function may also include a second identification. In some embodiments, the method includes storing the second identification for use in identifying the second network function based on the mobile device in subsequent transmissions. In some embodiments, the notification message is transmitted over an Nn interface.

Fig. 11 is a flowchart representation of a method 1100 for wireless communication. The method 1100 may be implemented in a scenario such as the embodiments depicted in fig. 4 and 5. The method 1100 comprises: in step 1101, a network storage function (NRF) service in a core network receives a request message from a first network function (e.g., N2 Comm) or a second network function (e.g., N1 Comm) in the core network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks, and the second network function is used to provide mobility management functions. Step 1102, the nrf service sends a response message to the first network service or the second network function. In step 1103, the nrf service sends a first notification message to the first network function to notify the first network function of configuration information about the second network function. In step 1104, the nrf service sends a second notification message to the second network function to notify the second network function of the configuration information about the first network function.

In some embodiments, the method includes, upon receiving the request message from the first network function, determining that the second network function is a subscriber of the NRF service and that a first service area of the first network function overlaps with a second service area of the second network function before transmitting the second notification message. For example, the second network function (e.g., N1 Comm) is a subscriber to the NRF service. When the NRF service receives a request message indicating registration or update from a first network function (e.g., N2 Comm), the NRF service checks service areas of the first and second network functions. If the service areas overlap, the NRF service determines to notify the user (e.g., N1 Comm).

In some embodiments, the method includes determining that the first network function is a subscriber of the NRF service and that a first service area of the first network function overlaps with a second service area of the second network function upon receiving the request message from the second network function before transmitting the first notification message. For example, the first network function (e.g., N2 Comm) is a subscriber to the NRF service. When the NRF service receives a request message indicating registration or update from a second network function (e.g., N1 Comm), the NRF service checks the service areas of the first and second network functions. If the service areas overlap, the NRF service determines to notify the user (e.g., N2 Comm).

In some embodiments, the method includes determining, upon receiving a request message from a first network function, that a second network function (e.g., N1 Comm) belongs to a group of network functions identified by an identification (e.g., N1Comm group ID) provided by the first network function (e.g., N2 Comm) prior to sending a second notification message. For example, the second network function (e.g., N1 Comm) is a subscriber to the NRF service. When the NRF service receives a request message from a first network function (e.g., N2 Comm) indicating registration or update, the NRF service checks the mapping between the two network function groups (e.g., N1Comm group and N2Comm group). If the user belongs to a group of network functions (e.g., an N1Comm group) identified by the first network function, the NRF service determines to notify the user (e.g., the N1Comm group).

In some embodiments, the method includes determining, upon receiving a request message from a second network function prior to sending the first notification message, that the first network function (e.g., N2 Comm) belongs to a group of network functions identified by an identification (e.g., N2Comm group ID) provided by the second network function (e.g., N1 Comm). For example, the first network function (e.g., N2 Comm) is a subscriber to the NRF service. When the NRF service receives a request message indicating registration or update from a second network function (e.g., N1 Comm), the NRF service checks the mapping between the two network function groups (e.g., N1Comm group and N2Comm group). The NRF service determines to notify the user (e.g., N2Comm group) if the user belongs to a network function group (e.g., N2Comm group) identified by the second network function.

Fig. 12 is a flowchart representation of a method 1200 for wireless communication. Method 1200 may be implemented in a scenario such as the embodiments depicted in fig. 4 and 5. The method 1200 includes: in step 1201, a first network function (e.g., N2 Comm) receives a network storage function (NRF) service notification message from a core network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. The notification message includes configuration information regarding the second network function (e.g., N1 Comm). The second network function is for providing a mobility management function. At step 1202, the first network function sends an update message to the access network to inform the access network of the second network function, wherein the update message includes an identification of the second network function based on configuration information regarding the second network function.

In some embodiments, the configuration information about the second network function comprises a name or a globally unique identification of the second network function.

Fig. 13 is a flowchart representation of a method 1300 for wireless communication. Method 1300 may be implemented in a scenario such as the embodiment depicted in fig. 6. The method 1300 includes: in step 1301, a first network function (e.g. N2 Comm) receives a message from an access network (e.g. NG-RAN) including information about one or more configurations of the access network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. At step 1302, the first network function sends a response to the access network to acknowledge receipt of the message. Step 1303, sending an update message from the first network function to a network storage function (NRF) service in a core network to update said one or more configurations of said access network to trigger a notification (e.g. N1 Comm) from the NRF service to a second network function providing mobility management functions. In some embodiments, the one or more configurations of the access network include information about slices, tracking areas, or public land mobile networks supported by the access network.

Fig. 14 is a flowchart representation of a method 1400 for wireless communication. Method 1400 may be implemented in a scenario such as the embodiment depicted in fig. 9. The method 1400 comprises: in step 1401, a first network function (e.g., N2 Comm) in a core network receives a message from a second network function (e.g., N1 Comm) in the core network. The first network function is dedicated to managing control plane communications between the core network and the one or more access networks. The second network function is for providing mobility management functions. The message includes information about the registration area of the mobile device. At step 1402, the first network function sends a paging request to an access network corresponding to a registration area of the mobile device.

In some embodiments, the message is transmitted over an Nn interface. In some embodiments, the method includes the first network function determining all access networks within a registration area of the mobile device.

In some embodiments, the first network function belongs to a first network function group and the second network function belongs to a second network function group. The first network function group and the second network function group are mapped one-to-one.

Fig. 15 illustrates an example of a wireless communication system 1500 in which techniques according to one or more embodiments of the present application can be applied. The wireless communication system 1500 may include one or more Base Stations (BSs) 1505a, 1505b, one or

more wireless devices

1510a, 1510b, 1510c, 1510d, and a core network 1525. Base stations 1505a, 1505b may provide access services for

wireless devices

1510a, 1510b, 1510c, and 1510d in one or more wireless sectors. In some applications, base stations 1505a, 1505b include directional antennas to produce two or more directional beams to provide wireless coverage for different sectors.

The core network 1525 may communicate with one or more base stations 1505a, 1505 b. The core network 1525 provides connectivity to other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information relating to subscribed

wireless devices

1510a, 1510b, 1510c, and 1510 d. The first base station 1505a may provide wireless services based on a first radio access technology, while the second base station 1505b may provide wireless services based on a second radio access technology. Base stations 1505a and 1505b may be co-located or separately installed in the field, depending on the deployment scenario.

Wireless devices

1510a, 1510b, 1510c, and 1510d may support multiple different radio access technologies.

Fig. 16 is a block diagram representing a portion of a radio station. A radio station 1605, such as a base station or wireless device (or UE), may include a processor circuit 1610, such as a microprocessor that applies one or more wireless technologies presented herein. The radio 1605 may include transceiver circuitry 1615 to transmit and/or receive wireless signals over one or more communication interfaces, such as an antenna 1620. The radio station 1605 may include other communication interfaces for sending and receiving data. The radio station 1605 may include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some applications, processor circuitry 1610 may include at least portions of transceiver circuitry 1615. In some embodiments, at least some of the techniques, modules, or functions of the present application are implemented using a radio station 1605.

It should be appreciated that the present application provides techniques that may be implemented into a wireless communication system to provide fully service-based mobility management functionality. Using the techniques described herein, access management functions handling NGAP association may be independent of other functions provided in the current AMF, thereby providing self-contained and reusable service-based mobility management network functions.

Other embodiments, modules, and functional operations disclosed and described herein may be applied to digital electronic circuitry, or to computer software, firmware, or hardware, including the architectures disclosed herein and their equivalents, or combinations of one or more of them. Other embodiments disclosed and described may be implemented as one or more computer program products, such as one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable transmission of a signal, or a combination of one or more of them. The term "data processing apparatus" encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code for creating an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The transmission signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiving apparatus.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language publication), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this application can be performed by one or more programmable processors executing one or more programs to perform functions by operating to input data and generate output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose processors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operative to process data for, receiving or transmitting or receiving data from or to one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; a magneto-optical disk; and CD ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

Since this application contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Suitable features that are described in connection with different embodiments in this application may also be applied in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be applied in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, operations are depicted in the drawings in a particular order, which should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the components of the systems in the embodiments described in this application are provided separately, but this does not mean that the components in all embodiments are provided separately.

The present application describes only some applications and examples, and other applications, improvements and modifications that can be made based on the description and illustrations of the present application are within the scope of the present application.

Claims

1. A method for wireless communication, comprising:

receiving, by a first network function in a core network, a first message from an access network to initiate a procedure for a mobile device, wherein the first network function is dedicated to managing control plane communications between the core network and one or more access networks;

the first network function sending a notification message to a second network function in the core network, wherein the second network function is configured to provide a mobility management function, the notification message including a first identity associated with the first network function and the mobile device;

the first network function receiving a second message from the second network function;

the first network function identifying a context of the mobile device based on the first identity; and

the first network function receives or sends a transfer message of the procedure via the access network based on the context of the mobile device.

2. The method of claim 1, wherein the first message from the access network comprises an identification of the mobile device, wherein the method further comprises:

the first network function determines the second network function based on the identity of the mobile device.

3. The method of claim 1, wherein the first network function belongs to a first network function group and the second network function belongs to a second network function group, wherein there is a one-to-one mapping between the first network function group and the second network function group.

4. The method of claim 3, further comprising:

the first network function sending a request to a network storage function, NRF, service, wherein the request comprises an identification of the second network function group; and

the first network function receives a response from the NRF service, wherein the response indicates an identification of the second network function group.

5. The method according to any one of claims 1 to 4, comprising:

the first network function determines the first identity associated with the first network function and the mobile device.

6. The method of claim 1, wherein the second message from the second network function comprises a second identity associated with the second network function and the mobile device.

7. The method of claim 6, wherein the second message from the second network function comprises the first identifier.

8. The method according to claim 6 or 7, comprising:

storing the second identification for use in subsequent transmissions based on the mobile device identifying the second network function.

9. A method for wireless communication, comprising:

receiving, by a first network function in a core network, a notification message from a second network function in the core network, wherein the first network function is to provide a mobility management function, the second network function is dedicated to managing control plane communications between the core network and one or more access networks, the notification message includes a second identity associated with the second network function and a mobile device, and the notification message further includes information about a procedure initiated by the mobile device;

the first network function processes the information of the procedure initiated by the mobile device;

the first network function sends a message to the second network function.

10. The method of claim 9, wherein the first network function belongs to a first network function group and the second network function belongs to a second network function group, and wherein the first network function group and the second network function group are mapped one-to-one.

11. The method of claim 9, comprising:

the first network function determines a first identity associated with the first network function and the mobile device for identifying the mobile device context.

12. The method of claim 11, wherein the message sent to the second network function comprises the first identifier.

13. The method of claim 12, wherein the message sent to the second network function further comprises the second identifier.

14. The method according to any one of claims 9 to 13, comprising:

15. A method for wireless communication, comprising:

a network storage function, NRF, service in a core network receiving a request message from a first network function in the core network dedicated to managing control plane communications between the core network and one or more access networks or a second network function in the core network providing a mobility management function;

the NRF service transmitting a response message to the first network function or the second network function;

the NRF service transmitting a first notification message to the first network function to notify the first network function of configuration information of the second network function; and

the NRF service transmits a second notification message to the second network function to notify the second network function of the configuration information of the first network function.

16. The method of claim 15, comprising:

determining that the second network function is a subscriber of the NRF service and a first service area of the first network function overlaps with a second service area of the second network function upon receiving the request message from the first network function.

17. The method of claim 15, comprising:

determining that the first network function is a subscriber of the NRF service and a first service area of the first network function overlaps with a second service area of the second network function upon receiving the request message from the second network function.

18. The method according to any of claims 15 to 17, wherein the first network function belongs to a first group of network functions and the second network function belongs to a second group of network functions, wherein there is a one-to-one mapping between the first group of network functions and the second group of network functions.

19. A method for wireless communication, comprising:

a first network function receiving a notification message from a network storage function, NRF, service in a core network, wherein the first network function is dedicated to managing control plane communications between the core network and one or more access networks, and a second network function for providing a mobility management function, the notification message comprising configuration information about the second network function; and

the first network function sends an update message to an access network to notify the access network of the second network function, wherein the update message includes an identification of the second network function based on the configuration information about the second network function, wherein the first network function and the second network function are both located in the core network.

20. The method according to claim 19, wherein the configuration information about the second network function comprises a name or a globally unique identity of the second network function.

21. The method according to claim 19 or 20, wherein the first network function belongs to a first group of network functions and the second network function belongs to a second group of network functions, and wherein there is a one-to-one mapping between the first group of network functions and the second group of network functions.

22. A method for wireless communication, comprising:

receiving, by a first network function, a message from an access network, the message including one or more configuration information for the access network, wherein the first network function is dedicated to managing control plane communications between a core network and one or more access networks;

the first network function sending a response to the access network acknowledging receipt of the message;

sending an update message from the first network function to a network storage function, NRF, service in the core network to update the one or more configurations of the access network to trigger a notification from the NRF service to a second network function providing a mobility management function, wherein the first network function and the second network function are both located in the core network.

23. The method of claim 22, wherein the one or more configurations of the access network comprise information of slices, tracking areas, or public land mobile networks supported by the access network.

24. The method according to claim 22 or 23, wherein the first network function belongs to a first network function group and the second network function belongs to a second network function group, and wherein there is a one-to-one mapping between the first network function group and the second network function group.

25. A method for wireless communication, comprising:

a first network function in a core network receiving a message from a second network function in the core network, wherein the first network function is dedicated to managing control plane communications between the core network and one or more access networks, the second network function is configured to provide a mobility management function, and the message comprises information of a registration area of a mobile device;

the first network function sends a paging request to an access network corresponding to the registration area of the mobile device.

26. The method of claim 25, comprising:

the first network function determines all access networks within the registration area of the mobile device.

27. The method according to claim 25 or 26, wherein the first network function belongs to a first group of network functions and the second network function belongs to a second group of network functions, and wherein there is a one-to-one mapping between the first group of network functions and the second group of network functions.

28. A wireless communication apparatus comprising a processor configured to implement the method of any of claims 1 to 27.

29. A computer-readable storage medium storing program instructions executable by a computer to perform the method of any one of claims 1 to 27.