EP3878239A1 - Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées - Google Patents

Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées

Info

Publication number
EP3878239A1
EP3878239A1 EP18939729.2A EP18939729A EP3878239A1 EP 3878239 A1 EP3878239 A1 EP 3878239A1 EP 18939729 A EP18939729 A EP 18939729A EP 3878239 A1 EP3878239 A1 EP 3878239A1
Authority
EP
European Patent Office
Prior art keywords
source node
network slice
network
access
access function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP18939729.2A
Other languages
German (de)
English (en)
Other versions
EP3878239A4 (fr
Inventor
Irfan Ali
Ravi Guntupalli
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Cisco Technology Inc filed Critical Cisco Technology Inc
Publication of EP3878239A1 publication Critical patent/EP3878239A1/fr
Publication of EP3878239A4 publication Critical patent/EP3878239A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication

Definitions

  • the present invention generally relates to network management.
  • the present invention relates to network slice management.
  • the network slices typically share an access function, such as an access and mobility management function (AMF), across the multiple network slices.
  • AMF access and mobility management function
  • the network slices are not fully independent.
  • FIG. 1 illustrates an example network environment, according to various embodiments of the subject technology
  • FIG. 2 illustrates an example network environment connecting a user device to two separated network slices, according to various embodiments of the subject technology
  • FIG. 3 illustrates an example method for transitioning the connection between user device and network slices between active and inactive states, according to various embodiments of the subject technology
  • FIG. 4 illustrates an example method for relocating connections network functions of network slices, according to various embodiments of the subject technology
  • FIG. 5 is a call flow diagram of an example registration procedure, according to various embodiments of the subject technology
  • FIG. 6 is a call flow diagram of an example active to idle transition procedure, according to various embodiments of the subject technology
  • FIG. 7 is a call flow diagram of an example idle to active transition procedure, according to various embodiments of the subject technology.
  • FIG. 8 is a call flow diagram of an example handover that involves access and mobility management function (AMF) relocation, according to various embodiments of the subject technology;
  • FIG. 9 illustrates an example network device, according to various embodiments of the subject technology.
  • AMF access and mobility management function
  • FIG. 10 illustrates an example computing device, according to various embodiments of the subject technology.
  • references to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure.
  • the appearances of the phrase“in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
  • various features are described which may be exhibited by some embodiments and not by others.
  • the terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Alternative language and synonyms may be used for any one or more of the terms discussed herein, and no special significance should be placed upon whether or not a term is elaborated or discussed herein.
  • a user device may need access to multiple totally independent network slices.
  • each network slice accessed by the user device may have a respective and unique access and mobility management function (AMF), among others.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • separate signaling radio bearers may be used for each access and mobility management function (AMF) so that each signaling radio bearer (SRB) may have differing levels of encryption and/or integrity protection. In effect, this may provide further isolation between traffic along different slices, including along, for example, a radio access network (RAN) shared between network slices.
  • RAN radio access network
  • SRB shared signaling radio bearer
  • AS autonomous system
  • the radio access network where the radio access network (RAN) has each of multiple keys associated with the respective signaling radio bearers (SRBs)
  • varied security levels may be applied to each autonomous system (AS).
  • the connecting user device may transmit non-access stratum (NAS) messages without having to provide an identification of which network slice to access because the respective signaling radio bearer (SRB) is connected to an individual network slice.
  • NAS non-access stratum
  • DRBs data radio bearers
  • AMFs associated with each network slice may be handled uniquely by a connecting node (e.g., a base station, gNB, etc.) because each network slice includes a unique signaling radio bearer (SRB) or data radio bearer (DRB).
  • SRB unique signaling radio bearer
  • DRB data radio bearer
  • CM communications manager
  • RRC radio resource control
  • RAN radio access network
  • a single state on the user device or radio access network (RAN) may reduce the complexity of network management involving multiple fully unique network slices.
  • a user device may be in a connected status in a radio access network (RAN) state (e.g., in a Connected radio resource control (RRC) state, etc.) while no access point connection is actually available for the user device.
  • RAN radio access network
  • RRC Radio resource control
  • AMF access and mobility management function
  • the paging request can be sent to the user device as a transport message for downlinked network access storage (NAS) and the like.
  • the user device can send a service request along a signaling radio bearer (SRB) for the associated network slice, which the radio access network (RAN) can use to select an appropriate access and mobility management function (AMF) (e.g., corresponding to the intended network slice).
  • SRB signaling radio bearer
  • AMF access and mobility management function
  • the radio access network (RAN) may then proceed with the service request over the network slice as usual.
  • one example makes use of a particular procedure in the radio access network (RAN).
  • paging is performed as a message for downlinked non-access stratum (NAS).
  • NAS downlinked non-access stratum
  • the radio access network (RAN) keeps for each access and mobility management function (AMF) independent states from, for example, respective communications manager (CM) states.
  • CM communications manager
  • the independent access and mobility management function (AMF) states provide useful redundancy when an access and mobility management function (AMF) fails.
  • a message can be sent as a page message to the respective radio access network (RAN).
  • the page message may indicate that the user device is in a connected state (e.g., resources are allocated to and serving the user device) or in an idle state (e.g., resources are currently not allocated to the user device).
  • the radio access network (RAN) may send the page message as a downlinked non-access stratum (NAS) transport message with a designator of which network slice the message is regarding.
  • NAS non-access stratum
  • the page message may include a S-TMSI rather than a network slice identifier.
  • the S-TMSI may include a respective temporary mobile subscriber identity (TMSI) and indicator of a respective access and mobility management function (AMF) (e.g., a pointer or such).
  • AMF access and mobility management function
  • each access and mobility management function (AMF) connected to, for example, a radio access network (RAN) node and the like has a unique indicator.
  • RAN radio access network
  • the user device may provide S-TMSIs to the respective radio access network (RAN) node when transmitting a service request (or rather after a service request transmission).
  • RAN radio access network
  • a respective node may request the access and mobility management function (AMF) for S-TMSI of the user device during release of resources.
  • the radio access network (RAN) node may maintain a listing of each S-TMSI from each access and mobility management function (AMF) where the user device has entered idle status.
  • each access and mobility management function may handle session management (SM) context with session management functions (SMFs) belonging to each respective network slice of the access and mobility management functions (AMFs).
  • SM session management
  • SMFs session management functions
  • the target node in this case may coordinate across each network slice so that only a single handover command is passed from the target node to the source node (e.g., during an access and mobility management function (AMF) relocation or other network function for which container migration may be necessary).
  • the handover request to be sent to the target node can be broken up into various components so that each network slice may receive and transmit a respective handover request component.
  • Each handover request component, along with SM context, may then be sent along the respective network slice to the target node.
  • a listing or similar indication of all network slices is included in the handover request components to the target node. The target node may then recompose all the handover response components and transmit a single complete handover response back to the source node and complete the handover process.
  • FIGS. 1 -2 depict networking environments over which network slices may be managed.
  • FIGS. 3-4 depict methods for managing network slices.
  • FIGS. 5-8 depict call flow diagrams for implementing some example methods of the underlying technology.
  • FIGS. 9-10 depict examples of hardware which may be used to implement the systems and methods of this disclosure. It is understood that while the examples discussed below refer to two network slices, the methods and systems disclosed may be applied to more than two network slices without deviating from the scope and spirit of the methods and systems discussed herein.
  • FIG. 1 depicts a networking environment 100 in which devices may connect to multiple network slices simultaneously.
  • a user device 102 may access, for example, a corporate network 104 or the Internet 106 via an access network 108.
  • Access network 108 can include, for example, a radio tower 109 which may include various components and functionality for servicing and maintaining telecommunication and data connections.
  • radio tower 109 may be a part of, and access network 108 may include, a radio access network (RAN).
  • RAN radio access network
  • References in this disclosure to nodes, base stations, and the like should be understood to include, for example, radio tower 109 and similar network access points.
  • access network 108 may connect to a provider infrastructure 150 include, for example, unified data management (UDM) 120, network slice selection function (NSSF) 130, and/or network repository function (NRF) 140, among other network services and functions.
  • UDM unified data management
  • NSSF network slice selection function
  • NRF network repository function
  • user device 102 can run various applications. Some applications run by user device 102, such as a work application 103A or a media application 103B, may utilize certain connection parameters such as security settings, routing requirements, Quality of Service (QoS) standards, and the like. In order to accommodate varied and, in some cases, conflicting connection parameters between multiple applications, multiple network slices 1 10A-B may be utilized to facilitate connections between user device 102 and corporate network 104 and/or the Internet 106. For example, and without imputing limitation, work application 103A may require a certain network security threshold that is incompatible with a Quality of Service (QoS) required by media application 103B. In such a case, network slices 1 10A-B may simultaneously attached to user device 102 and also fully separate from each other.
  • QoS Quality of Service
  • Network slices 1 10A-B may include respective network functions for managing data and connections.
  • network slices 1 10A-B can each include an access and mobility management function (AMF) 1 1 1 A-B, a network repository function (NRF) 1 12A-B, a session management function (SMF) 1 13A-B, a policy control function (PCF) 1 14A-B, and a user plane function (UPF) 1 15A-B, respectively.
  • AMF access and mobility management function
  • NRF network repository function
  • SMF session management function
  • PCF policy control function
  • UPF user plane function
  • network slices 1 10A-B may each communicate with provider infrastructure 150 to, for example, maintain records, policy consistency, etc.
  • network slice 1 10A can be dedicated to connections between work application 103A to corporate network 104, as indicated by the dashed line.
  • network slice 1 1 OB can be dedicated to connections between media application 103B and the Internet 106, as indicated by the dotted line.
  • Each dedicated network slice 1 10A-B may provide access and connection management for user device 102 running work and media applications 103A-B via respective access and mobility management functions (AMFs) 1 1 1 A-B intercommunicating with respective session management functions (SMFs) 1 13A-B.
  • AMFs access and mobility management functions
  • SMFs session management functions
  • FIG. 2 depicts a network environment 200, which may be substantially similar to network environment 100 discussed above, over which network slices 1 10A-B can be deployed.
  • network environment 200 includes user device 102 running work application 103A and media application 103B.
  • Network slice 1 10A connects user device 102 to corporate network 104 for communications, data transmissions, and the like using work application 103A.
  • Network slice 1 10B connects user device 102 to the Internet 106 for communications, data transmissions, and the like using media application 103B.
  • Network slices 1 10A-B respectively include access mobility functions (AMFs) 1 1 1 A- B, network repository functions (NRFs) 1 12A-B, session management functions (SMFs) 1 13A-B, policy control functions (PCFs) 1 14A-B, and user plane functions (UPFs) 1 15A-B.
  • AMFs access mobility functions
  • NRFs network repository functions
  • SMFs session management functions
  • PCFs policy control functions
  • UPFs user plane functions
  • network environment 200 includes a node 208 which, in some examples, may include radio tower 109 or, in other examples, other nodes included in access network 108 such as gNB (e.g., NodeB), ng-eNB, etc.
  • gNB e.g., NodeB
  • ng-eNB e.g., ng-eNB
  • unified data management (UDM) 120 can be accessed by both network slices 1 10A-B in order to manage resources and connections as well as to register each access and mobility management function (AMF).
  • AMF access and mobility management function
  • user device 102 may continuously receive data for work application 103A and/or media application 103B via protocol data unit (PDU) sessions using, for example and without imputing limitation, data radio bearer (DRB) and the like in order to provide security and integrity benefits.
  • PDU protocol data unit
  • DRB data radio bearer
  • work application 103A can transmit and receive data over a data radio bearer (DRB) stream 204 while media application 103B can transmit and receive data over a data radio bearer (DRB) stream 206.
  • data radio bearer (DRB) streams 204-206 may be transmitted via a data radio bearer (DRB).
  • Data radio bearer (DRB) streams 204-206 may each be handled by respective network slices 1 10A-B via associated user plane functions (UPFs) 1 15A-B.
  • UPFs user plane functions
  • Node 208 can transmit data radio bearer (DRB) streams to, for example, respective corporate network 104 or Internet 106 via respective network slices 1 10A-B and, more specifically, user plane functions (UPFs) 1 15A-B through general packet radio service tunneling protocol (GTP) or GTP-U (e.g., a user datagram protocol flavor of GTP) as managed by user plane functions (UPFs) 1 15A-B.
  • DRB data radio bearer
  • GTP general packet radio service tunneling protocol
  • GTP-U e.g., a user datagram protocol flavor of GTP
  • resources can be reconfigured for each data slice via a radio resource control (RRC) connection 202 as messages transmitted via signaling radio bearers (SRBs) 203A-B.
  • RRC radio resource control
  • signaling radio bearer 2 SRB2
  • NAS non-access stratum
  • SRB3 SRB3
  • RRC radio resource control
  • signaling radio bearer (SRB) messages 203A-B can be received by respective network slices 1 10A-B.
  • signaling radio bearer (SRB) messages 203A-B are received by respective access and mobility management functions (AMFs) 1 1 1 A- B and can be further processed or serviced by respective session management functions (SMFs) 1 13A-B in order to update network slices 1 10A-B as requested.
  • Node 208 may receive signaling radio bearer (SRB) messages 203A-B and transmit them via, for example, dedicated stream control transmission protocol (SCTP) connections to respective access and mobility management functions (AMFs) 1 1 1 1 A-B of respective network slices 1 10A-B.
  • SCTP dedicated stream control transmission protocol
  • FIG. 3 depicts a method 300 for releasing a resource.
  • a resource needing to be released is first identified (operation 302).
  • the resource to be released may be identified by, for example, network slice maintenance, monitoring, or reporting services and functions.
  • resources may be identified for release by the relevant network node (e.g., a base station to which the user device is attached).
  • a release request is then transmitted from a node to, for example, an access and mobility management function (AMF) attached to the user device (operation 304).
  • the access and mobility management function (AMF) may transmit back to the node an identification of the attached user device (operation 304).
  • the identification may be a temporary mobile subscriber identity (TMSI).
  • TMSI temporary mobile subscriber identity
  • a resource reconfiguration procedure between the identified user device and the node can be performed in order to release the resource (operation 308).
  • this procedure can include further calls, signals, and messages passed between, for example, the user device, node (or multiple nodes), and the network slice (and/or other network slices).
  • session information across the network slice may be updated (operation 310). In some examples, this may include updating other network slices or a data store shared between network slices and the like.
  • a user device may transition from coverage under a first node, or access point (e.g., base station), to coverage under a second node, or access point, and so trigger a handover process between the first and second node.
  • FIG. 4 depicts one method 400 for performing a handover procedure to transfer UE access to fully separated network slices across multiple nodes.
  • a source node first determines to provide a handover to another node (e.g., a“target” node) (operation 402).
  • the source node may determine to provide a handover node based on a request from connected UE and the like.
  • the source node may internally determine to provide a handover based on various factors such as UE session duration, UE location, UE geographic tracking, network connectivity, a network load taking place over the source node, etc.
  • the source node may then transmit a handover request for each connected network slice (operation 404).
  • requests may be particularly structured for respective access functions.
  • the target node receiving the handover request directly from the source node and following a first access function for a first network slice may receive a respective handover completion indication indirectly via a path request from the target node.
  • a second access function for a second network slice may receive a second respective handover request (e.g., a handover“requirement” or notice, etc.) directly from the source node.
  • the second handover request may trigger selection of a new access function (e.g., a target access and mobility management function (AMF), etc.) for managing a connection between the UE and the second fully separated network slice.
  • the new access function may transmit connection information to the target node for later synchronization and the like.
  • unique handover requests and procedures can be performed for each network slice connected to the UE in order to maintain separation between each of the network slices.
  • the source node receives access function information for each network slice (operation 406).
  • the received information may be particularized to each network slice and respective access functions.
  • the first network slice and respective access function may include a standard handover acknowledgement, while the second network slice and respective access function may contain detailed information related to the selected new access function.
  • the source node can then transmit a handover command to the UE for synchronizing the UE across the target node and to each of the fully separated network slices through respective access functions (operation 408).
  • the handover command may include consolidated information related to all of the network slices and/or access functions. In effect, the handover command provides an aggregated container or packet of all necessary network slice information for migrating to the target node.
  • FIG. 5 depicts call flow, or sequence, diagram 500 for handling registration requests.
  • each access and mobility management function (AMF) for each respective network slice can be registered by a node serving a user device (UE) 502.
  • UE user device
  • a slice identification may be provided in a resource reconfiguration request so that node 504 (e.g., NodeB (gNB), etc.) can select an appropriate access and mobility management function (AMF) of the identified slice.
  • AMF access and mobility management function
  • AUSF authentication server function
  • An external network which may include a unified data management (UDM), may furthermore receive a registration for each network slice and manage the registration of respective network slice access and mobility management functions (AMFs).
  • UDM unified data management
  • call 5.01 can include a radio resource control (RRC) message including a slice identification and a non-access stratum (NAS) level registration request.
  • RRC radio resource control
  • node 502 may perform call 5.02 to select access and mobility management function (AMF) 506 for continuing the registration sequence for network slice 525 (which includes access and mobility management function (AMF) 506).
  • AMF access and mobility management function
  • node 502 may perform call 5.02 through internal networks, lookups, and other architectures. Nevertheless, node 502 then sends to the identified access and mobility management function (AMF) 506 call 5.03 having a registration request message.
  • Access and mobility management function (AMF) 506 performs an authentication procedure 5.04 in response to registration request call 5.02.
  • Authentication procedure 5.04 can, in some examples, include calls spanning user device (UE) 502, node 504, network functions within network slice 525 such as access and mobility management function (AMF) 506, session management function (SMF) 508, user plane function (UPF) 510, and an External Network 518.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Access and mobility management function (AMF) 506 transmits to External Network 518 call 5.04 with External Network registration for network slice 525.
  • Access and mobility management function (AMF) 506 then transmits call 5.06 to user device (UE) 502 to notify user device (UE) 502 that registration has been accepted and is now complete.
  • another slice (e.g., slice 550) may be selected to receive registration of user device (UE) 502.
  • RRC radio resource control
  • UE User device
  • UE 502 transmits to node 504 call 5.07 including a resource reconfiguration request which, in some examples, may include a radio resource control (RRC) message with a slice identification (e.g., network slice 550) and a non-access stratum (NAS) level registration request.
  • RRC radio resource control
  • NAS non-access stratum
  • Node 502 responds to call 5.07 by performing call 5.08 to select an appropriate access and mobility management function (AMF), such as access and mobility management function (AMF) 512.
  • AMF access and mobility management function
  • call 5.08 is an internal call such as a lookup request or the like.
  • node 504 transmits a registration request call 5.09 to access and mobility management function (AMF) 512.
  • access and mobility management function (AMF) 512 may then perform authentication procedure 5.10 with user device (UE) 502, node 504, External Network 518, and across network slice 550 functions such as access and mobility management function (AMF) 512, session management function (SMF) 514, user plane function (UPF) 516, and such. Following authentication, access and mobility management function (AMF) 512 may then transmit to External Network 518 call 5.1 1 including an External Network registration for network slice 550. access and mobility management function (AMF) 512 then transmits to user device (UE) 502 a notice that registration has been accepted and is complete via call 5.12.
  • AMF Access and mobility management function
  • FIG. 6 depicts call sequence 600 where user device (UE) 502 transitions from active to idle for the same components as call sequence 500.
  • each network slice 525, 550 individually releases a respective network function (N2) connection.
  • node 504 serving the user device (UE) 502 can request a device identifier (e.g., temporary mobile subscriber identity (TMSI), etc.) from a respective access and mobility management function (AMF) (e.g., access and mobility management function (AMF) 506, 512).
  • the device identifier may be used for paging procedures and the like (discussed below in regards to FIG. 7).
  • user device (UE) 502 and node 504 may reconfigure the respective radio resource control (RRC) to release a signaling radio bearer (SRB) and/or data radio bearer (DRB) connection for the released network slice as the network slice no longer carries data for user device (UE) 502 or includes network functions connected to user device (UE) 502.
  • RRC radio resource control
  • N2 mobility management function
  • UE 502 may first send call 6.01 A to access and mobility management function (AMF) 506 creating a non-access stratum (NAS) connection between user device (UE) 502 and network slice 525 (e.g., as discussed above in regards to FIG. 5).
  • AMF access and mobility management function
  • NAS non-access stratum
  • user device (UE) 502 may also send call 6.01 B to user plane function (UPF) 510 for creating a protocol data unit (PDU) connection (e.g., for retrieving content from a corporate network 104 or the Internet 106, etc.) via user plane function (UPF) 510.
  • PDU protocol data unit
  • user device (UE) 502 may also send call 6.02A to access and mobility management function (AMF) 512 creating a non-access stratum (NAS) connection between user device (UE) 502 and network slice 550.
  • AMF access and mobility management function
  • User device (UE) 502 may also send call 6.02B to user plane function (UPF) 516 for creating a protocol data unit (PDU) connection via user plane function (UPF) 516.
  • UPF user plane function
  • node 504 can then transmit call 6.03 to decide to release a radio resource control (RRC) connection for network slice 525.
  • RRC radio resource control
  • node 504 may detect a level of activity below a certain threshold on the radio resource control (RRC) connection and thus may initiate call 6.03, which may include transmissions across internal services, functions, and the like.
  • node 504 may then send access and mobility management function (AMF) 506 call 6.04 to request a resource release.
  • call 6.04 may further include a request for a device identification of user device (UE) 502 (e.g., a temporary mobile subscriber identity (TMSI)).
  • UE user device
  • TMSI temporary mobile subscriber identity
  • access and mobility management function (AMF) 506 responds to node 504 with call 6.05 which includes a resource release command and can, in some examples, also include a device identification of user device (UE) 502.
  • Node 504 may then transmit to user device (UE) 502 call 6.06 performing a resource reconfiguration procedure (e.g., a radio resource control or RRC_Reconfig) for network slice 525, and thus a radio access network to access and mobility management function (N2) connection release for network slice 525 while retaining the radio resource control (RRC) connection still in use by, for example, network slice 550.
  • a resource reconfiguration procedure e.g., a radio resource control or RRC_Reconfig
  • RRC_Reconfig radio resource control
  • N2 radio resource control
  • node 504 may transmit to itself call 6.09 to release network slice 550 (e.g., the last remaining network slice), and thus a radio access network to access and mobility management function (N2) connection servicing network slice 550 as well.
  • Node 504 transmits to access and mobility management function (AMF) 512 (of network slice 550) call 6.10 requesting release of resources.
  • AMF access and mobility management function
  • AMF access and mobility management function
  • node 504 transmits back to node 504 call 6.1 1 including a resource release command.
  • call 6.12 is transmitted from node 504 to user device (UE) 502 to perform a resource release procedure, releasing the radio resource control (RRC) connection as a result.
  • RRC radio resource control
  • node 504 transmits to access and mobility management function (AMF) 512 call 6.13 providing notification that the resource release is complete.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • FIG. 7 depicts call sequence 700 for transitioning user device (UE) 502 from idle status to active status.
  • call sequence 700 includes nodes 702 which may refer to, for example and without imputing limitation, a collection or group of base stations, NodeB (gNB), and the like in a general area or vicinity of user device (UE) 502.
  • user device (UE) 502 can provide a device identification (e.g., temporary mobile subscriber identity (TMSI)) for a network slice with which it wants to establish a connection as well as device identifications for all other network slices for which user device (UE) 502 has relevant information (e.g., in the form of mobility management (MM) context and the like).
  • TMSI temporary mobile subscriber identity
  • MM mobility management
  • respective access and mobility management functions can transmit paging requests to relevant nodes (e.g., node 504, nodes 702, etc.) when, for example, a downlink data notification is received.
  • relevant nodes e.g., node 504, nodes
  • node 504 may update other access and mobility management functions (AMFs) of the new state using the device identifications (e.g., temporary mobile subscriber identity (TMSIs)) from above.
  • AMF access and mobility management function
  • an updated access and mobility management function (AMF) may send a page request to node 502 when, for example, a session management function (SMF) associated with the updated access and mobility management function (AMF) requests a downlink data notification (e.g., a page request) from access and mobility management function (AMF) 512 of network slice 550.
  • SMF session management function
  • AMF access and mobility management function
  • a packet from external data network arrives at user plane function (UPF) 510 (of network slice 525) call 7.01 including a downlink packet.
  • User plane function (UPF) 510 transmits to session management function (SMF) 508 call 7.02 having a resource notification (e.g., a notification over a user plane function to session management function (N4) connection between user plane function (UPF) 510 and session management function (SMF) 508).
  • Session management function (SMF) 508 then transmits to access and mobility management function (AMF) 506 call 7.03 including a downlink data notification.
  • AMF access and mobility management function
  • AMF 506 may then transmit call 7.04A for paging multiple nodes along with call 7.04B for paging node 504 via stored device identification (e.g., temporary mobile subscriber identity (TMSI)).
  • device identification e.g., temporary mobile subscriber identity (TMSI)
  • TMSIs temporary mobile subscriber identity
  • UE user device
  • TMSI temporary mobile subscriber identity
  • UE 502 then transmits to node 504 call 7.06 for resource reconfiguration.
  • call 7.06 may include a radio resource control (RRC) Reconfig message having one or more temporary mobile subscriber identity (TMSIs) and a non-access stratum (NAS) service request.
  • RRC radio resource control
  • TMSIs temporary mobile subscriber identity
  • NAS non-access stratum
  • Node 504 transmits to access and mobility management function (AMF) 506 call 7.07 for a service request, and so access and mobility management function (AMF) 506 then transmits to (and receives from) session management function (SMF) 508 call 7.08 for processing an update of protocol data unit (PDU) context for network slice 525.
  • SMF session management function
  • PDU protocol data unit
  • the protocol data unit (PDU) context updated, access and mobility management function (AMF) 506 transmits to node 504 call 7.09 denoting a successful resource reconfiguration.
  • Call 7.09 can include a radio access network to access and mobility management function (N2) connection for creating, for example, an evolved packet system radio access bearer (E-RAB) between network slice 525 along with a service acceptance via non-access stratum (NAS).
  • Node 504 then transmits a service acceptance call 7.10 to user device (UE) 502.
  • user device (UE) 502 may then transmit calls 7.1 1 associated with a protocol data unit (PDU) session via user plane function (UPF) 510 created as a result of the preceding sequence.
  • PDU protocol data unit
  • UPF user plane function
  • node 504 transmits connection notice to other network slices (e.g., network slice 550, etc.) in order to enable paging requests to be sent from access and mobility management function (AMF) 506 to node 504 if session management function (SMF) 508 requests a downlink data notification (e.g., a page request) from other access and mobility management functions (AMFs) of the other network slices (e.g., access and mobility management function (AMF) 512).
  • AMF access and mobility management function
  • AMF access and mobility management function
  • a downlink packet is sent from External Network 518 to user plane function (UPF) 516 via call 7.13.
  • user plane function (UPF) 516 then transmits to session management function (SMF) 514 a resource notification (e.g., user plane function to session management function (N4) connection notification) via call 7.14 and so session management function (SMF) 514 transmits to access and mobility management function (AMF) 512 call 7.15 including a downlink data notification.
  • a resource notification e.g., user plane function to session management function (N4) connection notification
  • AMF access and mobility management function
  • access and mobility management function (AMF) 512 transmits call 17.16A to nodes 702 (e.g., nodes in the area of user device (UE) 502) in order to perform paging procedures. Node 504 then also receives a page via call 17.6B from access and mobility management function (AMF) 512. Further, Nodes 702 transmit call 7.16C to perform respective pages to user device (UE) 502. Alternatively, such as in cases where call 7.12 above does occur, access and mobility management function (AMF) 512 transmits to node 504 call 7.17 including a page. Pages of calls 7.16A-C and 7.17 may, in some examples, each include a device identification (e.g., temporary mobile subscriber identity (TMSI)) associated with access and mobility management function (AMF) 512.
  • TMSI temporary mobile subscriber identity
  • node 504 transmits to user device (UE) 502 call 7.18 including a downlink information transfer rather than a paging call user device (UE) 502 then transmits to node 504 call 7.19 to request service.
  • RRC radio resource control
  • call 7.19 may be a non-access stratum (NAS) uplink transmission over radio resource control (RRC) including a device identification (e.g., temporary mobile subscriber identity (TMSI)) associated with access and mobility management function (AMF) 512 and other relevant device identifications (e.g., temporary mobile subscriber identity (TMSIs)) associated with other access and mobility management functions (AMFs) (and so other network slices).
  • RRC radio resource control
  • TMSI temporary mobile subscriber identity
  • AMF access and mobility management function
  • TMSIs temporary mobile subscriber identity
  • Node 504 transmits to access and mobility management function (AMF) 512 call 7.20 including a service request access and mobility management function (AMF) 512 and session management function (SMF) 514 then transmit between each other call 7.21 to update protocol data unit (PDU) context for network slice 550 accordingly before access and mobility management function (AMF) 512 transmits to node 504 call 7.22 including an radio access network to access and mobility management function (N2) connection for creating, for example, an evolved packet system radio access bearer (E-RAB) between network slice 550 along with a service acceptance via non-access stratum (NAS).
  • AMF access and mobility management function
  • N2 radio access network to access and mobility management function
  • E-RAB evolved packet system radio access bearer
  • Node 7.23 transmits to user device (UE) 502 call 7.23 to provide notification of service acceptance and so user device (UE) 502, node 504, and user plane function (UPF) 516 can perform a protocol data unit (PDU) session via call 7.24 between them.
  • PDU protocol data unit
  • FIG. 8 depicts call sequence 800 for performing a handover procedure (e.g., due to physical movement of UE or other events that may initiate an access and mobility management function (AMF) relocation).
  • call sequence 800 depicts a UE handover procedure between a source node (e.g., a first base station) and a target node (e.g., a second base station) for two fully separated network slices.
  • a source node e.g., a first base station
  • a target node e.g., a second base station
  • an inter-base station interface (Xn) handover procedure can be performed and a path switch request sent to the respective access and mobility management function (AMF) may update the first network slice.
  • Xn inter-base station interface
  • a respective handover procedure may include selecting a new access and mobility management function (AMF) for managing the network slice connection to the UE while keeping each network slice fully separated from each other.
  • AMF access and mobility management function
  • the source node may receive individual responses (e.g., handover acknowledgements, commands, etc.) from each fully separated network slice and consolidate the responses into a single handover command to be transmitted to the UE.
  • call sequence 800 depicts a handover procedure for two network slices
  • handovers for more than two fully separated network slices may be performed as described in call sequence 800 and, in particular, handover calls for second network slice 850 may be repeated as many times as necessary for respective third, fourth, or more fully separated network slices and the like.
  • a signal from source node 504 to source access and mobility management function (AMF) 512 that a handover is required can include a message that provides QoS flow information of network slice 850 and other content for configuring target access and mobility management function (AMF) 804.
  • the signal may also include a listing of other network slices to which user device (UE) 502 is connected. This information may also be relayed to target node 802 in order for target node 802 to determine whether handover requests have been received from all relevant network slices.
  • source node 504 determines target node 802 has received all necessary handover information, it can then transmit a handover command to user device (UE) 502 (e.g., via radio resource control (RRC), etc.) aggregating all handover information such as access and mobility management function (AMF) and respective network slice information for synchronizing UE 502 with target node 802 for PDU sessions with fully separated network slices 525 and 850 (e.g., via path switches, PDU session updates, etc.).
  • UE user device
  • RRC radio resource control
  • AMF access and mobility management function
  • user device (UE) 502 may participate in protocol data unit (PDU) sessions via user plane function (UPF) 510 and user plane function (UPF) 516 of network slice 525 and network slice 850 respectively via procedure call 8.01 and procedure call 8.02.
  • User device (UE) 502 then transmits to source node 504 call 8.03 including a measurement report (e.g., latency, connectivity, packet loss, or other measurements prompting a handover procedure).
  • Source node 504 internally transmits and processes call 8.04 triggering a handover procedure to target node 802 via handover requests particularized for each respective fully separated network slice 525 and 850.
  • an inter-base station interface (Xn) handover for transferring network slice 525 to target node 802 may be necessitated by source node 504 being down and the like, and also prompt a radio access network to access and mobility management function (N2) connection handover for network slice 850.
  • N2 access and mobility management function
  • multiple handover requests and/or requirements can be generated in order to maintain full separation of network slices 525 and 850 while transferring user device (UE) 502 to target node 802.
  • Source node 504 then transmits call 8.05 to target node 802 including a handover request.
  • the handover request includes information for network slice 525 and network slice 850 in order to facilitate downstream handover calls.
  • Target node 802 responds to source node 504 with call 8.06 including a handover acknowledgement.
  • network slice 525 may be fully prepared for a handover at this point (e.g., handover preparation within Xn standards has completed). However, where additional fully separated slices are associated with user device (UE) 502 (e.g., such as in a 5G network, etc.), further handover preparation may be performed in order to maintain full separation between each network slice (e.g., N2 handover prep).
  • UE user device
  • Source node 504 proceeds to transmit to source access and mobility management function (AMF) 512 call 8.07 indicating a handover is required along with, in some examples, network slice information.
  • AMF source access and mobility management function
  • AMF target access and mobility management function
  • SMF session management function
  • UPF user plane function
  • target access and mobility management function (AMF) 804 transmits to target node 802 call 8.1 1 including a handover requirement along with, in some examples, network slice information (e.g., for network slice 525 and network slice 850) and other information for completing handing over the user device (UE) 502 connection with network slice 850 to target node 802 (as further discussed below).
  • Target node 802 transmits to target access and mobility management function (AMF) 804 call 8.12 including a handover acknowledgement and, in some examples, a target to source container, or message, having a radio resource control (RRC) command for handover calls from user device (UE) 502.
  • RRC radio resource control
  • the handover acknowledgement includes a container, or message, to be transmitted to source node 504 and having an appropriate radio resource control (RRC) command.
  • RRC radio resource control
  • fully separated network slices 525 and 850 need not interact with each other or even be aware of each other throughout the handover procedure and so may maintain full separation.
  • Target access and mobility management function (AMF) 804, session management function (SMF) 514, and user plane function (UPF) 516 then transmit between themselves further protocol data unit (PDU) session updates via call 8.13.
  • PDU protocol data unit
  • Target access and mobility management function (AMF) 804 transmits to source access and mobility management function (AMF) 512 call 8.14 in order to acknowledge the forward relocation of call 8.09 discussed above.
  • Source access and mobility management function (AMF) 512 then transmits to source node 504 a handover command (e.g., including the radio resource control (RRC) command for handover calls from user device (UE) 502 above) via call 8.15.
  • RRC radio resource control
  • Source node 504 then uses the information in call 8.15 to transmit to user device (UE) 502 call 8.16 issuing a handover command. This triggers procedure calls 8.17 across user device (UE) 502, source node 504, and target node 802 for synchronizing devices. After synchronization is complete, user device (UE) 502 transmits to target node 802 call 8.18 confirming the handover.
  • Inter-base station interface handover may then occur as source node 502 transmits to target node 802 call 8.19 to transfer source node (SN) status and the like.
  • Target node 802 transmits to access and mobility management function (AMF) 506 call 8.20 including a path switch request.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • UE user device
  • UE source node
  • UPF user plane function
  • N2 handover for network slice 850 may then proceed.
  • Target node 802 transmits to target access and mobility management function (AMF) 804 call 8.24 including a handover notification.
  • Target access and mobility management function (AMF) 804 then transmits to source access and mobility management function (AMF) 512 call 8.25 notifying source access and mobility management function (AMF) 512 that forward relocation has been completed (e.g., target node 802 connects user device (UE) 502 to network slice 850 via target access and mobility management function (AMF) 804).
  • Target access and mobility management function (AMF) 804, session management function (SMF) 514, and user plane function (UPF) 516 may then update the protocol data unit (PDU) session via transmitting call 8.26 between themselves.
  • PDU protocol data unit
  • user device (UE) 502, target node 802, and user plane function (UPF) 516 may perform a protocol data unit (PDU) session via calls 8.27.
  • Source node 504 then transmits to source access and mobility management function (AMF) 512 call 8.28 to release user device (UE) 502 context and then user device (UE) 502, target access and mobility management function (AMF) 804, and External Network 518 may perform registration procedures for network slice 850 via calls 8.29 between themselves (e.g., via a unified data management (UDM) and the like).
  • UDM unified data management
  • the network device may employ one or more memories or memory modules (including memory 906) configured to store program instructions for the general-purpose network operations and mechanisms for roaming, route optimization and routing functions described herein.
  • the program instructions may control the operation of an operating system and/or one or more applications, for example.
  • the memory or memories may also be configured to store tables such as mobility binding, registration, and association tables, etc.
  • Memory 906 could also hold various software containers and virtualized execution environments and data.
  • the network device 900 can also include an application-specific integrated circuit (ASIC), which can be configured to perform routing, switching, and/or other operations.
  • ASIC application-specific integrated circuit
  • the ASIC can communicate with other components in the network device 900 via the connection 910, to exchange data and signals and coordinate various types of operations by the network device 900, such as routing, switching, and/or data storage operations, for example.
  • FIG. 10 is a schematic block diagram of an example computing device 1000 that may be used with one or more embodiments described herein e.g., as any of the discussed above or to perform any of the methods discussed above, and particularly as specific devices as described further below.
  • the device may comprise one or more network interfaces 1010 (e.g., wired, wireless, etc.), at least one processor 1020, and a memory 1040 interconnected by a system bus 1050, as well as a power supply 1060 (e.g., battery, plug-in, etc.).
  • Network interface(s) 1010 contain the mechanical, electrical, and signaling circuitry for communicating data over links coupled to the network 100, e.g., providing a data connection between device 1000 and the data network, such as the Internet.
  • the network interfaces may be configured to transmit and/or receive data using a variety of different communication protocols.
  • interfaces 1010 may include wired transceivers, wireless transceivers, cellular transceivers, or the like, each to allow device 1000 to communicate information to and from a remote computing device or server over an appropriate network.
  • the same network interfaces 1010 also allow communities of multiple devices 1000 to interconnect among themselves, either peer-to-peer, or up and down a hierarchy.
  • the nodes may have two different types of network connections 1010, e.g., wireless and wired/physical connections, and that the view herein is merely for illustration.
  • the network interface 1010 is shown separately from power supply 1060, for devices using powerline communication (PLC) or Power over Ethernet (PoE), the network interface 1010 may communicate through the power supply 1060, or may be an integral component of the power supply.
  • PLC powerline communication
  • PoE Power over Ethernet
  • Memory 1040 comprises a plurality of storage locations that are addressable by the processor 1020 and the network interfaces 1010 for storing software programs and data structures associated with the embodiments described herein.
  • the processor 1020 may comprise hardware elements or hardware logic adapted to execute the software programs and manipulate the data structures 1045.
  • An operating system 1042 portions of which are typically resident in memory 1040 and executed by the processor, functionally organizes the device by, among other things, invoking operations in support of software processes and/or services executing on the device. These software processes and/or services may comprise one or more functional processes 1046, and on certain devices, an illustrative “dynamic policy” process 1048, as described herein.
  • a router would be configured to operate as a router
  • a server would be configured to operate as a server
  • an access point (or gateway) would be configured to operate as an access point (or gateway), and so on.
  • processor and memory types including various computer-readable media, may be used to store and execute program instructions pertaining to the techniques described herein.
  • description illustrates various processes, it is expressly contemplated that various processes may be embodied as modules configured to operate in accordance with the techniques herein (e.g., according to the functionality of a similar process). Further, while the processes have been shown separately, those skilled in the art will appreciate that processes may be routines or modules within other processes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, un unique dispositif d'utilisateur (UE) peut être rattaché à de multiples tranches de réseau entièrement séparées. Chaque tranche de réseau peut comprendre des fonctions d'accès respectives. Un passage de l'état inactif à l'état actif peut être appliqué à travers les tranches de réseau entièrement séparées en libérant chaque tranche de réseau via une transmission sur un canal de ressources radio (RRC) avant de libérer le canal de RRC. Un passage de l'état actif à l'état inactif peut être appliqué à travers les tranches de réseau entièrement séparées en recevant un premier message de radiorecherche au niveau d'un UE afin d'initialiser un canal de RRC servant à connecter une première tranche de réseau, et en recevant un message de transfert d'informations de liaison descendante afin de connecter une seconde tranche de réseau sur le canal de RRC. Un transfert entre nœuds peut comprendre la transmission de demandes de transfert à des tranches de réseau individuelles et l'agrégation d'accusés de réception au niveau d'un nœud avant d'envoyer une commande de transfert à l'UE.
EP18939729.2A 2018-11-05 2018-11-05 Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées Pending EP3878239A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2018/059221 WO2020096564A1 (fr) 2018-11-05 2018-11-05 Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées

Publications (2)

Publication Number Publication Date
EP3878239A1 true EP3878239A1 (fr) 2021-09-15
EP3878239A4 EP3878239A4 (fr) 2023-08-23

Family

ID=70611005

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18939729.2A Pending EP3878239A4 (fr) 2018-11-05 2018-11-05 Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées

Country Status (2)

Country Link
EP (1) EP3878239A4 (fr)
WO (1) WO2020096564A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258017B (zh) * 2021-12-27 2024-01-30 中国电信股份有限公司 互斥切片接入方法、装置、电子设备及计算机可读介质
CN117858177A (zh) * 2022-09-30 2024-04-09 中兴通讯股份有限公司 一种切换方法及通信节点、存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109041137B (zh) * 2016-01-16 2020-01-17 华为技术有限公司 一种切换的方法、基站及终端设备
WO2017135858A1 (fr) * 2016-02-05 2017-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Nœuds de réseau radio, et procédés réalisés en leur sein
US10142994B2 (en) 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
WO2018082098A1 (fr) * 2016-11-07 2018-05-11 华为技术有限公司 Procédé de gestion d'état de réseau et dispositif pertinent
US10736072B2 (en) * 2016-11-27 2020-08-04 Lg Electronics Inc. De-registration method in wireless communication system and apparatus therefor
CN108696905B (zh) * 2017-02-20 2023-06-13 中兴通讯股份有限公司 一种无线资源的管理方法及装置
US10165546B2 (en) * 2017-03-17 2018-12-25 Nokia Technologies Oy Protection of privacy in paging of user equipment
KR102289879B1 (ko) * 2017-03-20 2021-08-13 삼성전자 주식회사 셀룰러망에서 세션의 다양한 ssc 모드 지원을 위한 upf 변경 방안

Also Published As

Publication number Publication date
WO2020096564A1 (fr) 2020-05-14
EP3878239A4 (fr) 2023-08-23

Similar Documents

Publication Publication Date Title
US11930397B2 (en) Session packet duplication
CN112740824B (zh) 恢复请求随后释放和重定向
US20190335365A1 (en) Network Handover Method and Related Device
US9769709B2 (en) Handover method, communication device and communication system
US11864103B2 (en) Network slicing method and device, and storage medium
CN109155909A (zh) 无线通信系统中用于更新ue配置的方法及其装置
US10219148B2 (en) Mobility support for virtual terminals
CN109819485B (zh) 一种通信方法、装置及系统
KR102263338B1 (ko) 통신 방법 및 장치
WO2017118186A1 (fr) Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur
CN110754112B (zh) 网络接入方法以及移动性支持和数据传送的方法和装置
US20230143942A1 (en) Managing a ue preferred configuration
US11602010B2 (en) Open control plane for mobile networks
WO2015188357A1 (fr) Dispositif de commande de commutation de porteuse et procédé de commande
WO2015161575A1 (fr) Procédé, station de base, entité de gestion mobile, et système de notification d'emplacement de terminal utilisateur
US20220150784A1 (en) Handover method and apparatus
JP2023534851A (ja) 統合アクセスおよびバックホールｉａｂシステムに適用される通信方法および通信装置
JP2023546462A (ja) 通信方法および装置、可読記憶媒体、ならびにシステム
KR20230041066A (ko) 데이터 송신 방법, 장치, 및 시스템
KR102246493B1 (ko) 이동통신 시스템에서 멀티 셀 네트워크 구축 방법 및 장치
WO2019238050A1 (fr) Procédé et appareil de communication
EP3878239A1 (fr) Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées
CN113993147B (zh) 信息处理方法、网元、存储介质及程序产品
WO2022067588A1 (fr) Procédé et appareil de communication
WO2023179231A1 (fr) Procédé et appareil de configuration d'informations de cellule, support de stockage lisible et système de puce

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210526

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230525

A4 Supplementary search report drawn up and despatched

Effective date: 20230725

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 68/00 20090101ALN20230719BHEP

Ipc: H04W 76/34 20180101ALI20230719BHEP

Ipc: H04W 76/15 20180101ALI20230719BHEP

Ipc: H04W 60/00 20090101ALI20230719BHEP

Ipc: H04W 36/00 20090101ALI20230719BHEP

Ipc: H04W 76/10 20180101ALI20230719BHEP

Ipc: H04W 76/30 20180101ALI20230719BHEP

Ipc: H04W 76/20 20180101AFI20230719BHEP